Changes between Version 2 and Version 3 of 2018WP/ENHANCE-03_jchanut-ZTILDE
- Timestamp:
- 2018-02-20T11:16:44+01:00 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
2018WP/ENHANCE-03_jchanut-ZTILDE
v2 v3 1 = '''''ENHANCE-3_Jerome_ztilde''''' 1 = '''''ENHANCE-03_jchanut_ZTILDE''''' = 2 == Summary == #summary 3 ||= '''Action''' =|| ENHANCE-03_jchanut_ZTILDE || 4 ||= '''PI(S)''' =|| Jérôme Chanut || 2 5 3 == Summary #summary4 5 ||= '''Action''' =|| ENHANCE-3_Jerome_ztilde ||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 Revisited z-tilde coordinate. 12 Revisited z-tilde coordinate. 15 13 16 }}} 17 |- 18 ||= '''Dependencies''' =|| 19 ||= '''Target''' =||||20 ||= '''Trac Ticket''' =|| #0000||21 ||= '''SVN branch''' 22 ||= '''Previewer(s)''' =|| 23 ||= '''Reviewer(s)''' =||||24 ||= '''Link''' =|| [[ExtractUrl(.)]]||14 }}} |- 15 16 ||= '''Dependencies''' =|| || 17 ||= '''Target''' =|| || 18 ||= '''Trac Ticket''' =|| #2019 || 19 ||= '''SVN branch''' =|| [source:/branches/$YEAR/dev_r{REV}_{WG|STREAM|INSTITUTE}-{NUM}_{PIS}-{KEYWORDS}] || 20 ||= '''Previewer(s)''' =|| Alex Megann || 21 ||= '''Reviewer(s)''' =|| || 22 ||= '''Link''' =|| [[ExtractUrl(.)]] || 25 23 26 24 {{{#!comment … … 29 27 30 28 }}} 29 31 30 == == 32 31 {{{#!comment … … 36 35 }}} 37 36 38 {{{#!Fold title=Abstract tag=h2 39 [=#abstract] 37 {{{#!Fold title=Abstract tag=h2 [=#abstract] 40 38 41 39 This section should be completed before starting to develop the code, in order to find agreement on the method beforehand. 42 40 43 {{{#!TracForm 44 #!subcontext abstract 45 #!submit_label 'Save Abstract' 46 #!keep_history yes 41 {{{#!TracForm #!subcontext abstract #!submit_label 'Save Abstract' #!keep_history yes 47 42 48 === Description 43 === Description === 44 [tf.textarea:description -id=piform -class=taform 'Describe the goal of development, and the methodology. Add reference documents or publications if relevant.' 0 20] 49 45 50 [tf.textarea:description -id=piform -class=taform 'Describe the goal of development, and the methodology. Add 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. List the .F90 files and modules to be changed. Detailed list of new variables (including namelists) to be defined. Give for each the chosen name (following coding rules) and definition.' 0 20] 51 48 52 === Implementation 53 54 [tf.textarea:implementation -id=piform -class=taform 'Describe flow chart of the changes in the code. List the .F90 files and modules to be changed. Detailed list of new variables (including namelists) to be defined. Give for each the chosen name (following coding rules) and definition.' 0 20] 55 56 === Reference manual and web pages updates 57 58 [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] 59 51 60 52 '''''Updated on [tf.form_updated_on:] by [tf.form_updater:]''''' … … 66 58 }}} 67 59 68 {{{#!Fold title=Preview tag=h2 69 [=#preview] 60 {{{#!Fold title=Preview tag=h2 [=#preview] 70 61 71 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. \\ 72 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. 73 63 74 {{{#!TracForm 75 #!subcontext preview_ 76 #!submit_label 'Save Preview' 64 {{{#!TracForm #!subcontext preview_ #!submit_label 'Save Preview' 77 65 78 66 ||= Questions =||= Answer =||= Comment =|| … … 91 79 }}} 92 80 93 {{{#!Fold title=Tests tag=h2 94 [=#tests] 81 {{{#!Fold title=Tests tag=h2 [=#tests] 95 82 96 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. 97 84 98 {{{#!TracForm 99 #!subcontext tests 100 #!submit_label 'Save Tests' 85 {{{#!TracForm #!subcontext tests #!submit_label 'Save Tests' 101 86 102 87 ||= Questions =||= Answer =||= Comment =|| … … 119 104 }}} 120 105 121 {{{#!Fold title=Review tag=h2 122 [=#review] 106 {{{#!Fold title=Review tag=h2 [=#review] 123 107 124 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). 125 109 126 {{{#!TracForm 127 #!subcontext review 128 #!submit_label 'Save Review' 110 {{{#!TracForm #!subcontext review #!submit_label 'Save Review' 129 111 130 === Code changes and documentation 131 112 === Code changes and documentation === 132 113 ||= Question =||= Answer =||= Comment =|| 133 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] || … … 141 122 || ... ... ... || [tf.select:3.XX -id=revform '' Yes No NR] || [tf.textarea:3.XXc -id=revform 'Add a comment?' 50 10] || 142 123 143 ==== Review Summary 144 124 ==== Review Summary ==== 145 125 Is the review fully successful? [tf.select:status -id=revform '' Yes No] 146 126
