Changes between Version 9 and Version 10 of Scientific Advisory Board/Agenda/2017-06-27


Ignore:
Timestamp:
2017-05-30T14:34:26+02:00 (3 years ago)
Author:
vancop
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Scientific Advisory Board/Agenda/2017-06-27

    v9 v10  
    1 = Developer's Committee meeting Tuesday 27 June 2017 
    2  
     1= Developer's Committee meeting Tuesday 27 June 2017 = 
    32[[PageOutline(2-3)]] 
    43 
    54Last edition: '''[[Wikinfo(changed_ts)]]''' by '''[[Wikinfo(changed_by)]]''' 
    65 
    7 == Proposed agenda 
    8  
     6== Proposed agenda == 
    97After the sucessful meeting of « Enlarged Developer’s Committee » in Barcelona in April, this message to propose an agenda and find a date for the next videoconference meeting of Developer’s Committee in June. 
    108 
    11 The expected participants to this meeting are the members of Developer’s Committee, including the leader of each NEMO Working Group, and the NEMO System Team members as permanent invitees. 
    12 For this meeting, all members of Writing Group of NEMO Development Strategy update will also be invited (see below) 
    13 Taking in account the discussions in Barcelona, please find below a preliminary agenda (for which all suggestions welcome): 
     9The expected participants to this meeting are the members of Developer’s Committee, including the leader of each NEMO Working Group, and the NEMO System Team members as permanent invitees. For this meeting, all members of Writing Group of NEMO Development Strategy update will also be invited (see below) Taking in account the discussions in Barcelona, please find below a preliminary agenda (for which all suggestions welcome): 
    1410 
    1511'''Meeting will start at 10:00 am Paris time''' 
    1612 
     13=== 1) NEMO System Team brief report on the status of 2017 workplan actions at this date === 
     14=== 2) Exchange of information on the existing Working Groups : AGRIF (J. Chanut), Configuration Manager (S. Ciliberti), Robustness and Test Cases (S. Flavoni), HPC (M. Bell), data assimilation and interface (M. Martin), parametrisation of mesoscale eddies (M. Bell), sea-ice (M. Vancoppenolle) === 
     15For each Working Group, its leader to briefly present : 
    1716 
    18 === 1) NEMO System Team brief report on the status of 2017 workplan actions at this date 
     17 * one slide on the work done during the past 6 months 
     18 * one slide on the open issues, i.e. the list of questions to be answered before end of 2017 
     19 * one slide on the perspectives for 2018 
    1920 
    20 === 2) Exchange of information on the existing Working Groups : AGRIF (J. Chanut), Configuration Manager (S. Ciliberti), Robustness and Test Cases (S. Flavoni), HPC (M. Bell), data assimilation and interface (M. Martin), parametrisation of mesoscale eddies (M. Bell), sea-ice (E. Blockley)  
    21 For each Working Group, its leader to briefly present : 
    22 - one slide on the work done during the past 6 months 
    23 - one slide on the open issues, i.e. the list of questions to be answered before end of 2017 
    24 - one slide on the perspectives for 2018 
     21=== 3) Discussion on the draft of NEMO Development Strategy version 2, draft to be sent to Committee beginning of June 2017 (C. Lévy) === 
     22Is the document fulfilling the goal: design NEMO development for the next 5 years? What could be improved in the draft? 
    2523 
    26 === 3) Discussion on the draft of NEMO Development Strategy version 2, draft to be sent to Committee beginning of June 2017 (C. Lévy) 
    27 Is the document fulfilling the goal: design NEMO development for the next 5 years? 
    28 What could be improved in the draft? 
     24'''END of first half day ''' 
    2925 
    30 '''END of first half day 
    31 ''' 
    32 === 4) Preparing 2018 and mid-term 
    33  
    34 4-a) Evolutions of Working Groups (XX) 
    35 Developer’s Committee to elaborate proposal for each Working Group by the end of 2017. 
    36 Important reminder: the best possible results for a Working Group is to come to an end, meaning that all the open issues have been solved. 
    37 If relevant, list of new Working Groups to be created, and selection of their members 
     26=== 4) Preparing 2018 and mid-term === 
     274-a) Evolutions of Working Groups (XX) Developer’s Committee to elaborate proposal for each Working Group by the end of 2017. Important reminder: the best possible results for a Working Group is to come to an end, meaning that all the open issues have been solved. If relevant, list of new Working Groups to be created, and selection of their members 
    3828 
    39294-b) First ideas on 2018 Workplan (presented by System Team), and discussion 
    4030 
    41 === 5) Review of the role of Developer’s Committee (XX) 
    42 What is working? 
    43 What could be improved, especially regarding the link between scientific projects going on and NEMO development workplan? 
     31=== 5) Review of the role of Developer’s Committee (XX) === 
     32What is working? What could be improved, especially regarding the link between scientific projects going on and NEMO development workplan? 
    4433 
    45 '''END of the meeting 
     34'''END of the meeting''' 
    4635 
    47 ''' 
    48 == Videoconference connection information 
    49 '''Please use a videconferencing system if possible. 
    50 Do not connect by phone. 
    51 If connecting using a laptop, you need to use headphones to avoid echoing problems.''' 
     36== Videoconference connection information == 
     37'''Please use a videconferencing system if possible. Do not connect by phone. If connecting using a laptop, you need to use headphones to avoid echoing problems.''' 
    5238 
    53 === NEMO Dev Com am 
     39=== NEMO Dev Com am === 
    5440{{{ 
    5541To join the conference from your system: 
     
    7864How to connect: https://renavisio.renater.fr/user_guide 
    7965}}} 
    80 === NEMO Dev Com pm 
    81  
     66=== NEMO Dev Com pm === 
    8267{{{ 
    8368To join the conference from your system: 
     
    10691How to connect: https://renavisio.renater.fr/user_guide 
    10792}}} 
    108  
    109  
    110 == List of participants 
     93== List of participants == 
    11194''Please try to join in one place if connecting from the same city'' 
    11295 
    113 || Name         || Role           || Connecting from        || 
    114 ||Claire Lévy   ||Project manager ||Paris LOCEAN 4ème étage || 
    115 ||Joanna Staneva||External expert ||Hamburg                 || 
    116 ||Emanuela Clementi||INGV officer, WAVE-WG leader||Bologna                 || 
    117 ||Simona Flavoni ||  CNRS Officer, Robustness and Test Cases WG leader  ||Paris|| 
    118 ||Stefania Ciliberti||CMCC Member of the System Team, CONF MAN WG leader||Lecce|| 
    119 ||              ||                ||                        || 
    120 ||              ||                ||                        || 
    121 ||              ||                ||                        || 
    122 ||              ||                ||                        || 
    123  
    124  
     96|| Name || Role || Connecting from || 
     97||Claire Lévy ||Project manager ||Paris LOCEAN 4ème étage || 
     98|| Joanna Staneva ||External expert ||Hamburg || 
     99|| Emanuela Clementi || INGV officer, WAVE-WG leader ||Bologna || 
     100||Simona Flavoni ||  CNRS Officer, Robustness and Test Cases WG leader  || Paris || 
     101|| Stefania Ciliberti || CMCC Member of the System Team, CONF MAN WG leader || Lecce || 
     102|| Martin Vancoppenolle || Sea Ice WG leader || Paris || 
     103|| || || || 
     104|| || || || 
     105|| || || ||