Changes between Version 8 and Version 9 of GroupActivities/Various


Ignore:
Timestamp:
2020-03-31T10:33:06+02:00 (4 years ago)
Author:
jgipsl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GroupActivities/Various

    v8 v9  
    44== Josefine critical activities (to be backed up during her maternity leaves) == 
    55 
    6 * '''Trusting Chain''': contact person: Patricia Cadule 
    7   * Objectif: Running the trusting chain at every new commit on the ORCHIDEE trunk (source code and experiment set up). 
    8   
     6* '''Trusting Chain''', Contact person: Patricia Cadule 
     7  * Goal: Make sure the ORCHIDEE trunk is passing all technical tests after each commit 
     8  * Patrica runs the trusting chain  
     9    * after every new commit or nearly done the ORCHIDEE trunk (source code ORCHIDEE and experiment set up ORCHIDEE_OL). 
     10    * at irene, jean-zay and obelix after each commit 
     11  * The person who made the commit is responsible of the results and making sure all tests by the trusting are OK 
    912 
    10 * '''Creation of user account for svn and forge''': Use orchidee-help mailing list. Contact person: Fabienne Maignan 
    11   * objectif: xxx 
     13* '''Creation of new user account for svn and forge''', Contact person: Fabienne Maignan 
     14  * Goal: create svn and forge login for new ORCHIDEE users. Set up read and write permission on different branches. 
     15  * Use orchidee-help mailing list for these demands 
     16  * Several persons in the ORCHIDEE project group can create the logins. Contact Fabienne in case of problem. 
     17  * Read here about the different login:  [wiki:Documentation/UserGuide/DifferentLogin] 
    1218 
    13 * '''Commit on the trunk'''. Requirements for a valid commit:  
    14  - Always use "svn diff" to carefully check what will be committed and to avoid committing unintended WRITE statements, hacks and/or changes in flags and parameters.  
    15  - Always test the modification in prod and debug mode with a land-only configuration. Use strict error settings for these tests ERR_ACT = 3 (to be set in PARAM/orchidee.def) 
    16  - Big intrusive commits, commits related to the coupling to the atmosphere, or related to parallelisation should be discussed in the group before changing the code. 
    17  - If the commit requires changes in the default configurations, parameters values, and/or input files, these changes should be discuss in the group to avoid unintended changes in other parts of the code. Remember that such changes will need some coordination between the land-only and the coupled land-atmosphere setup.  
    18  - For big intrusive commits, the coupled land-atmosphere configuration should be tested in addition to the previous tests. 
    19  - If possible, all trusting tests should be completed and passed prior to a big intrusive commit. While Josefine is on leave, Patricia will be responsible for the trusting. If it is not possible to do the trusting prior to the commit, commit first and then contact the person responsible for the trusting to run the trusting. Tell the person responsible for the trusting whether the commit is expected to change the results or not. 
    20  - If the trusting was not passed correctly for all test cases (the person responsible for the trusting should send the outcomes of the tests to the person responsible for the commit), correcting the code should be a priority of the person responsible for the commit. If it turns out to be too difficult to find a solution, revert the commit. 
     19* '''Commit on the trunk ORCHIDEE and ORCHIDEE_OL''', Contact person: ORCHIDEE project group 
     20 * Goal: Continue commits on the trunk 
     21 * Who can commit on the trunk: most of the persons in ORCHIDEE project group. See set up in the autz file at forge. If someone is missing, this can be added.  
     22 * Requirements for a valid commit, before commit:  
     23  - For important or big changes, discuss with the group during the ORCHIDEE Tuesday meeting before commit 
     24  - Always use "svn diff" to carefully check what will be committed and to avoid committing unintended WRITE statements, hacks and/or changes in flags and parameters.  
     25  - Always test the modification in prod and debug mode with a land-only configuration. Use strict error settings for these tests ERR_ACT = 3 (default option in the libIGCM set up, to be set in PARAM/orchidee.def) 
     26  - Big intrusive commits, commits related to the coupling to the atmosphere, or related to parallelization or new set up (new input files), they should be: 
     27   - discussed in the group during a Tuesday meeting before changing the code 
     28   - the coupled land-atmosphere configuration with LMDZ should be tested in addition to the previous tests. 
     29  - If the commit requires changes in the default configurations, parameters values, and/or input files, these changes should be discuss in the group to avoid unintended changes in other parts of the code. Remember that such changes will need some coordination between the land-only and the coupled land-atmosphere setup.  
     30  - If possible, all trusting tests should be completed and passed prior to a big intrusive commit. While Josefine is on leave, Patricia will be responsible for the trusting. If it is not possible to do the trusting prior to the commit, commit first and then contact the person responsible for the trusting to run the trusting. Tell the person responsible for the trusting whether the commit is expected to change the results or not. 
     31  * After commit: 
     32   - Contact Patrica so she can launch the trusting. Give here the following information: 
     33    - revision of the commit 
     34    - if you expect changes in the results 
     35    - if there are changes in the output variables, if you added or removed variables 
     36    - if there are changes in the set up 
     37   - If the trusting was not passed correctly for all test cases (Patricia will send the outcomes of the tests to the person responsible for the commit), correcting the code should be a priority of the person responsible for the commit. If it turns out to be too difficult to find a solution, revert the commit. 
    2138 
    22 * '''Budget Labex''' : Qui s'occupe ?  
     39* '''Budget Labex''', Contact person: ???  
     40 * Goal: Make sure the money are used in the delay 
     41 * Discussion in the group before using the money should be done.  
     42 * The contact person is responsible to remember the ORCHIDEE project group if there are money left or if there are not enough money. 
     43 
     44* '''Coupled configurations''', Contact person: Anne Cozic and Arnaud Caubel 
     45 * Goal: Coupled configurations are diffused using ORCHIDEE trunk, ORCHIDEE_2_0, ORCHIDEE_2_2 and ORCHIDEE_3. If changes in any of these versions needs changes in the set up, this must be coordinated with the Plateforme groupe (Anne, Arnaud) 
     46 * Before such modifications in the trunk (or other version) , this should be disucssed during the Tuesday ORCHIDEE meeting. Nicolas Vuichard centralizes the communication with Anne and Arnaud.  
     47 
     48* '''Input files at synchronized repository IGCM''', Contact person Anne Cozic and Arnaud Caubel 
     49 * Goal: Add or remove files on repositories IGCM at obelix, TGCC, IDRIS, ciclad/ClimServ  
     50 *