Changes between Version 2 and Version 3 of 2018WP/AGRIF-03_jchanut-TOOLS
- Timestamp:
- 2018-02-20T10:55:43+01:00 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2018WP/AGRIF-03_jchanut-TOOLS
v2 v3 1 = '''''AGRIF-03_jchanut-TOOLS''''' 1 = '''''AGRIF-03_jchanut-TOOLS''''' = 2 == Summary == #summary 3 ||= '''Action''' =|| AGRIF-03_jchanut-TOOLS || 4 ||= '''PI(S)''' =|| Jérôme Chanut || 2 5 3 == Summary #summary4 5 ||= '''Action''' =|| AGRIF-03_jchanut-TOOLS ||6 ||= '''PI(S)''' =|| Jérôme Chanut ||7 6 {{{#!th 8 7 9 8 '''Digest''' 10 9 11 }}} 12 {{{#!td 10 }}} {{{#!td 13 11 14 AGRIF nesting tools update. 15 On-line nesting pre-processing tools are outdated and need complete revision to work with the most recent code. We propose in this task: 16 (i) To correct the tool by gathering various fixes done by users, remove obsolete features and test it. 17 (ii) Investigate an alternative, in collaboration with people from the CONFIG MANAGER group. It could be based on the use of the AGRIF library itself, thus making it simpler to navigate through the grid hierarchy. 12 AGRIF nesting tools update. On-line nesting pre-processing tools are outdated and need complete revision to work with the most recent code. We propose in this task: (i) To correct the tool by gathering various fixes done by users, remove obsolete features and test it. (ii) Investigate an alternative, in collaboration with people from the CONFIG MANAGER group. It could be based on the use of the AGRIF library itself, thus making it simpler to navigate through the grid hierarchy. 18 13 19 }}} 20 |- 21 ||= '''Dependencies''' =|| 22 ||= '''Target''' =||||23 ||= '''Trac Ticket''' =|| #0000||24 ||= '''SVN branch''' 25 ||= '''Previewer(s)''' =|| 26 ||= '''Reviewer(s)''' =||||27 ||= '''Link''' =|| [[ExtractUrl(.)]]||14 }}} |- 15 16 ||= '''Dependencies''' =|| || 17 ||= '''Target''' =|| || 18 ||= '''Trac Ticket''' =|| #2017 || 19 ||= '''SVN branch''' =|| [source:/branches/$YEAR/dev_r{REV}_{WG|STREAM|INSTITUTE}-{NUM}_{PIS}-{KEYWORDS}] || 20 ||= '''Previewer(s)''' =|| Clément Rousset || 21 ||= '''Reviewer(s)''' =|| || 22 ||= '''Link''' =|| [[ExtractUrl(.)]] || 28 23 29 24 {{{#!comment … … 32 27 33 28 }}} 29 34 30 == == 35 31 {{{#!comment … … 39 35 }}} 40 36 41 {{{#!Fold title=Abstract tag=h2 42 [=#abstract] 37 {{{#!Fold title=Abstract tag=h2 [=#abstract] 43 38 44 39 This section should be completed before starting to develop the code, in order to find agreement on the method beforehand. 45 40 46 {{{#!TracForm 47 #!subcontext abstract 48 #!submit_label 'Save Abstract' 49 #!keep_history yes 41 {{{#!TracForm #!subcontext abstract #!submit_label 'Save Abstract' #!keep_history yes 50 42 51 === Description 43 === Description === 44 [tf.textarea:description -id=piform -class=taform 'Describe the goal of development, and the methodology.\n\nAdd reference documents or publications if relevant.' 0 20] 52 45 53 [tf.textarea:description -id=piform -class=taform 'Describe the goal of development, and the methodology.\n\nAdd reference documents or publications if relevant.' 0 20] 46 === Implementation === 47 [tf.textarea:implementation -id=piform -class=taform 'Describe flow chart of the changes in the code.\n\nList the .F90 files and modules to be changed.\n\nDetailed list of new variables (including namelists) to be defined. Give for each the chosen name (following coding rules) and definition.' 0 20] 54 48 55 === Implementation 56 57 [tf.textarea:implementation -id=piform -class=taform 'Describe flow chart of the changes in the code.\n\nList the .F90 files and modules to be changed.\n\nDetailed list of new variables (including namelists) to be defined. Give for each the chosen name (following coding rules) and definition.' 0 20] 58 59 === Reference manual and web pages updates 60 61 [tf.textarea:manual -id=piform -class=taform 'Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files), and in the content of web pages.' 0 20] 49 === Reference manual and web pages updates === 50 [tf.textarea:manual -id=piform -class=taform 'Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files), and in the content of web pages.' 0 20] 62 51 63 52 '''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' … … 69 58 }}} 70 59 71 {{{#!Fold title=Preview tag=h2 72 [=#preview] 60 {{{#!Fold title=Preview tag=h2 [=#preview] 73 61 74 Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request. \\ 75 For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions. 62 Since the preview step must be completed before the PI starts the coding, the previewer(s) answers are expected to be completed within the two weeks after the PI has sent his request. \\ For each question, an iterative process should take place between PI and previewer(s) in order to reach a "YES" answer for each of the following questions. 76 63 77 {{{#!TracForm 78 #!subcontext preview_ 79 #!submit_label 'Save Preview' 64 {{{#!TracForm #!subcontext preview_ #!submit_label 'Save Preview' 80 65 81 66 ||= Questions =||= Answer =||= Comment =|| … … 94 79 }}} 95 80 96 {{{#!Fold title=Tests tag=h2 97 [=#tests] 81 {{{#!Fold title=Tests tag=h2 [=#tests] 98 82 99 83 Once the development is done, the PI should complete this section below and ask the reviewers to start their review in the lower section. 100 84 101 {{{#!TracForm 102 #!subcontext tests 103 #!submit_label 'Save Tests' 85 {{{#!TracForm #!subcontext tests #!submit_label 'Save Tests' 104 86 105 87 ||= Questions =||= Answer =||= Comment =|| … … 122 104 }}} 123 105 124 {{{#!Fold title=Review tag=h2 125 [=#review] 106 {{{#!Fold title=Review tag=h2 [=#review] 126 107 127 108 A successful review is needed to schedule the merge of this development into the future NEMO release during next Merge Party (usually in November). 128 109 129 {{{#!TracForm 130 #!subcontext review 131 #!submit_label 'Save Review' 110 {{{#!TracForm #!subcontext review #!submit_label 'Save Review' 132 111 133 === Code changes and documentation 134 112 === Code changes and documentation === 135 113 ||= Question =||= Answer =||= Comment =|| 136 114 || Is the proposed methodology now implemented? || [tf.select:3.11 -id=revform '' Yes No NR] || [tf.textarea:3.11c -id=revform 'Add a comment?' 50 10] || … … 144 122 || ... ... ... || [tf.select:3.XX -id=revform '' Yes No NR] || [tf.textarea:3.XXc -id=revform 'Add a comment?' 50 10] || 145 123 146 ==== Review Summary 147 124 ==== Review Summary ==== 148 125 Is the review fully successful? [tf.select:status -id=revform '' Yes No] 149 126
