Changes between Version 3 and Version 4 of addnewNR


Ignore:
Timestamp:
11/15/14 14:12:24 (10 years ago)
Author:
Mathieu Morlighem
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • addnewNR

    v3 v4  
    1 Create a testXXX.m file with the simulation test and put in field_names, field_tolerances and field_values the names of the field you want to check for your test with the tolerances associated (because every computer is different) and the path to the values.
    2 Put the name of your test in `IdToName.m` and run
     1 == Introduction ==
     2
     3ISSM relies on regression tests to check that no bug is introduced during code development. All the tests are located in `$ISSM_DIR/test/test/NightlyRun` and all the tests whose number are less than 1000 are run after each change pushed to the svn repository (through jenkins) and 4 times a day (through cron jobs).
     4
     5If a new capability is being added to ISSM, it is critical that a new test is created.
     6
     7 == Files to change/create ==
     8
     9Create a `testXXX.m` file with the simulation test and put in `field_names`, `field_tolerances` and `field_values` the names (no space) of the fields you want to check for your test with the tolerances associated (because every computer is different).
     10
     11Put the name of your test in `IdToName.m` and run the following command to create the archive (the archive gives the reference values for all the fields that are checked):
    312
    413{{{
     
    716}}}
    817
    9 to create an archive in test/Archives where the reference values will be. This archive is the same for the Python test. Now if you run
     18This archive is located in `$ISSM_DIR/test/test/archives` in NetCDF format, and is the same for the Python test if you create one as well. Now if you run
    1019
    1120{{{
     
    1423}}}
    1524
    16 it should write SUCCESS everywhere. If not, you may have used a too big coefficient like 10^48 in your code and every machine won’t give the same result.
     25you should see SUCCESS everywhere. If not, you have to adjust the tolerances slightly.
    1726
    18 NB : do the same thing for testXXX.py and IdToName.py without creating the archive this time.
     27NB : do the same thing for `testXXX.py` and `IdToName.py` without creating the archive this time.
    1928
    20 You can `svn add` the files and `svn commit –m “CHG : description”`.
     29 == Checking in the new test ==
     30
     31You can `svn add` the new files (`testXXX.m`, `testXXX.py` and archiveXXX.nc) and `svn commit –m "NEW: added test to check ...”`.