Changes between Version 37 and Version 38 of DevelopersCommittee/Agenda/2017-06-27
- Timestamp:
- 2017-07-21T12:58:41+02:00 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevelopersCommittee/Agenda/2017-06-27
v37 v38 32 32 33 33 ==== AGRIF (J. Chanut) 34 The list of needed developments and their priority has been build by the working group. The development work now needs to be done (and has been delayed due to lack of res sources and H2020 COPPER project not funded). Still the working group's view on the future is to take the needed time to validate and publish the existing and announced features.34 The list of needed developments and their priority has been build by the working group. The development work now needs to be done (and has been delayed due to lack of resources and H2020 COPPER project not funded). Still the working group's view on the future is to take the needed time to validate and publish the existing and announced features. 35 35 Open questions on update of Nesting tools versus Configuration Manager developments. 36 36 37 ==== Configuration Manager (S. Ciliberti) 38 37 39 38 40 ==== Robustness and test cases (S. Flavoni) 39 41 All the development and simplification is now done inside NEMO 40 First test cases available in NEMOGCM, so as associated tools to build and use them 42 First test cases available in NEMOGCM, so as associated tools to build and use them. 41 43 Now need to define the location of all test cases (existing ones build build consortium members, so as future ones coming from the community), so as the acceptable procedure for all to ensure sufficient quality control (including the responsibilities of System Team on one side, and of the developer on the other). 44 Very good job done on this major task. 42 45 Interest expressed (by D. Marshall) to start using test cases for students. 43 46 44 ==== Data assimilation and interface ()47 ==== Data assimilation and interface 45 48 Some inputs have been included in the strategy document, but role and perspectives of this working group are unclear for now, after the decision made concerning TAM, so as the leave of Pierre-Antoine Bouttier from his position. 49 For now this WG has no leader anymore, nor clear perspectives for now. 46 50 47 51 ==== Parametrisation of mesoscale eddies (M. Bell) … … 51 55 [attachment:DevCommJune2017_WG_PME_MJB.pptx Mike Bell's presentation] 52 56 57 ==== HPC ( ) 58 53 59 ==== TOP (C. Ethé, O. Aumont) 60 Up to now, only a discussion group. 54 61 No new developments for now, but focus on consolidation of modularity with regards to the different BGC models (PISCES, BFM, MEDUSA...) 55 62 A meeting on PISCES development, with representatives of BFM and MEDUSA will take place in Paris beginning of July. Scope of WG may be updated afterwards, so as the corresponding section of NEMO Development Strategy document … … 58 65 59 66 ==== Wave coupling (E. Clementi) 67 The development of large scale coupling with waves in now done, and included in the trunk so that is will be available in the next NEMO release. 68 Working group is now focused on coupling at smaller space and time scale. 60 69 61 70 It is noted that whereas large scale wave coupling is indeed part of NEMO development strategy, coupling at small scales has to be scoped. It is clearly an interesting scientific question, but probably out of scope of NEMO, expect maybe for shore. 62 71 63 72 === 3) Discussion on the draft of NEMO Development Strategy version 2017 (C. Lévy) === … … 77 86 === 4) Preparing 2018 and mid-term === 78 87 ==== Evolutions of Working Groups 79 Developer’s Committee to make recommendations for each Working Group by the end of 2017. If relevant, list of new Working Groups to be created, and selection of their members.88 Developer’s Committee to make recommendations for each Working Group by the end of 2017. More specifically, the Committee is expected to validate the list of questions each Woking Group is expected to address. If relevant, list of new Working Groups to be created, and selection of their members. 80 89 81 * AGRIF: WG shoud contribute to choose a unique tool where tools to set up AGRIF configuration are developed: to be discussed with Configuration Manager and Test cases WGs: need to make one choice between nesting tools (needing update), future configuration manager, or tools build for test cases 90 * AGRIF: 91 * WG is expected as proposed to organise validation of existing and expected developments, in order to ensure robustness of AGRIF in the future release 92 * Question on compatibility between AGRIF and OpenMP should be explored and answered in the next months 93 * WG shoud contribute to decision on how to configure an application using AGRIF, to be discussed with Configuration Manager and Test cases WGs: need to make one choice between nesting tools (needing update), future configuration manager, or tools build for test cases 82 94 83 * Configuration Manager: Following mid-term strategy, should focus on the tool to set up NEMO configuration only, leaving aside the coupling module with other models. Objective is to define a strategy with existing resources to decide where to drive the future for next generation, starting from SIREN. Same comment as for AGRIF WG. Overlap with Nesting Tools of AGRIF and tools developed for test cases should be clarified by deciding a unique tool for each functionality. 95 * Configuration Manager: 96 * WG should focus on the tool to set up NEMO configuration only, leaving aside the coupling module with other models. Objective is to define a strategy with existing resources to decide where to drive the future for next generation, starting from SIREN. 97 * Same item as for AGRIF WG. Overlap with Nesting Tools of AGRIF and tools developed for test cases should be clarified by deciding a unique tool for each functionality. 84 98 85 * Robustness and test cases : Very good job to be continued, focusing on the ways to set up, accept and distribute test cases. Same comment as for AGRIF WG 99 * Robustness and test cases : 100 * WG should now focusing on the ways to set up, accept and distribute test cases. 101 * Same item as for AGRIF WG 86 102 87 103 * Data assimilation and interface: 104 * Without any leader for now and taking in account the new status of TAM within NEMO (no further developments than what is now in place in 3_4_STABLE release), the need for this WG is not clear for now 105 * Committee requests that Matt Martin, with the other members of the WG, prepare an answer for next meeting, taking in account also NEMO data interface NEMO-OBS and NEMO-ASM, to decide if a WG is still useful on these subjects 88 106 89 * Parametrisation of mesoscale eddies: as suggested by WG, it is now disbanded. 107 * Parametrisation of mesoscale eddies 108 * As suggested by WG, it is now disbanded. 109 110 * HPC 111 90 112 91 113 * TOP 92 114 93 115 * Sea-ice 116 * WG should continue to elaborate the development phases of the new component, details expected for next meeting of the Committee 117 * Committee suggests to include some test cases for sea-ice from the beginning of the development of this new european sea-ice component 118 * Working with wave coupling has been suggested but will be envisaged alter on 94 119 95 120 * Wave coupling: reorganise this WG to air-sea coupling, including waves (aligned with Chapter 9 of Dev. Strategy document). Proposal for this renewed WG to be presented by E. Clementi and L. Brodeau during next meeting end of the year … … 106 131 * Role of the Committee 107 132 The NEMO Developer's Committee is the Scientific advisory board of NEMO Consortium. The role of the external experts is important and could be enhanced: need for regular attendance of these experts also to the meetings of the Committee. 108 Somme addit onnal external experts are proposed: Eric Chassignet133 Somme additional external experts are proposed: Eric Chassignet 109 134 110 135 * What is working? … … 113 138 * Getting the complete view on what is going on through the meetings twice a year 114 139 * Giving advices on yearly workplan (although messages to SC not really followed up to now) 140 115 141 * What could be improved? (including link between scientific projects going on and NEMO development workplan) 116 Meetings of Developer's Committee are too long (up to now, it seemed important to have information on each group or team (System Team, Working Groups...). The committee proposes to have from now on a subgroup to examine all ongoing actions in order to limit the agenda of the meetings to the points needing discussion. Claire Lévy to propose the organisation, list of members and tasks of this subgroup before next meeting. 142 * Committee suggest to try having a list of WG corresponding to the Chapter of the Development Strategy document 143 * Meetings of Developer's Committee are too long (up to now, it seemed important to have information on each group or team (System Team, Working Groups...). The committee proposes to have from now on a subgroup to examine all ongoing actions in order to limit the agenda of the meetings to the points needing discussion. Claire Lévy to propose the organisation, list of members and tasks of this subgroup before next meeting. 117 144 145 END of the meeting 118 146 119 147 == List of participants ==
