VARIOUS actitivies / information

Josefine critical activities (to be backed up during her maternity leaves)

• Trusting Chain, Contact person: Patricia Cadule
  • Goal: Make sure the ORCHIDEE trunk is passing all technical tests after each commit
  • ​http://webservices.ipsl.fr/trusting, see tab ORCHIDEE
  • Patrica runs the trusting chain
    • after every new commit or nearly done the ORCHIDEE trunk (source code ORCHIDEE and experiment set up ORCHIDEE_OL).
    • at irene, jean-zay and obelix after each commit
  • The person who made the commit is responsible of the results and making sure all tests by the trusting are OK

• Creation of new user account for svn and forge, Contact person: Fabienne Maignan
  • Goal: create svn and forge login for new ORCHIDEE users. Set up read and write permission on different branches.
  • Use orchidee-help mailing list for these demands
  • Several persons in the ORCHIDEE project group can create the logins. Contact Fabienne in case of problem.
  • Read here about the different login: Documentation/UserGuide/DifferentLogin

• Commit on the trunk ORCHIDEE and ORCHIDEE_OL, Contact person: ORCHIDEE project group
  • Goal: Continue commits on the trunk
  • 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.
  • Requirements for a valid commit, before commit:
    • For important or big changes, discuss with the group during the ORCHIDEE Tuesday meeting before commit
    • 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.
    • 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)
    • 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:
      • discussed in the group during a Tuesday meeting before changing the code
      • the coupled land-atmosphere configuration with LMDZ should be tested in addition to the previous tests.
    • 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.
    • 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.
    • After commit:
      • Contact Patrica so she can launch the trusting. Give here the following information:
        • revision of the commit
        • if you expect changes in the results
        • if there are changes in the output variables, if you added or removed variables
        • if there are changes in the set up
      • 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.

• Budget Labelisation, Contact person: Bertrand Guenet
  • Goal: Make sure the money are used in the delay
  • Discussion in the group before using the money should be done.
  • The contact person is responsible to remember the ORCHIDEE project group if there are money left or if there are not enough money.
  • Budget used 2020/04/03 : TTC 227,96€ at Ardoise (crous) for lunch during Documentation working day 28of February
  • Contact Pascale DUMOULIN, Gestionnaire Financière IPSL, Tel 01 80 28 50 12, email : pascale.dumoulin _at_ ipsl.fr

• Coupled configurations, Contact person: Nicolas Vuichard centralizes the problems to Anne Cozic and Arnaud Caubel
  • Goal: Modify default set up and revision number in coupled configurations. Coupled configurations are diffused using ORCHIDEE trunk, ORCHIDEE_2_0, ORCHIDEE_2_2 and ORCHIDEE_3. If changes in any of these versions need changes in the set up, this must be coordinated with the Anne and/or Arnaud (Plateforme groupe)
  • 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.
  • Note: Do not contact Anne and Arnaud for problems running the configurations. Problems running coupled configurations should be resolved as usual, using ​Plateforme documentation igcmg_doc or the mailing list platform-users.

• Input files at synchronized repository IGCM, Contact person: Nicolas Vuichard centralizes the problems to Anne Cozic and Arnaud Caubel
  • Goal: Add or remove files on repositories IGCM at obelix, TGCC, IDRIS, ciclad/ClimServ
  • For all new files, following needs to be done:
    • The name of the folder must be unique and new. We never replace an existing folder.
    • Script used to transform the data should be added to SVN, for example here: ​https://forge.ipsl.jussieu.fr/orchidee/browser/trunk/TOOLS
    • A README file must come with each folder of data. The README should contain the following information:
      • Date and name of the person who prepared the data.
      • Explication of origine of the data.
      • Explications of the transformation done, if any.
      • Link to scripts on SVN if transformations have been done. Set revision numer and path to SVN.
      • Information about policy for usage, if any.
    • If files are transformed, add global attribut Description to describe the files. L'information in the README can be used in the attribut in the file. Use ncatted to manipulate the attributes.
    • The files are preferend in netcdf-4 format.
    • Avoid links in the folders.