Page Comparison

Adding a new test to acme_developer or integration

Under most situations, tests should be added to one of the acme categories.

1. Edit <ACME>/cime/scripts/acmelib/update_acme_tests.py

2. You'll

   see

   a

   python

   dict

   at

   the

   top

   of

   the

   file

   called

   TEST_SUITES,

   find

   the

   test

   category

   you

   want

   to

   change

   in

   this

   dict

   and

   add

   your

   testcase

   to

   the

   list
3. cd <ACME>/scripts/ccsm_utils/Testlistxml
4. update_acme_tests <category> ./testlist.xml

Adding a testcase to a non-acme category

1. cd <ACME>/scripts/ccsm_utils/Testlistxml

2. manage_xml_entries -query -outputlist -machine <machine> -compiler <compiler> -category <category> > SOME_FILE

3. edit SOME_FILE
4. add a line for you new test anywhere in the file, save

5. manage_xml_entries -addlist -file SOME_FILE -category <category>

6. The above command will produce a new file: "testlist-<date>-<time>.xml"
7. Replace testlist.xml with the above file
8. If a test is being run on a machine for the first time, you'll need to generate a baseline for it
   1. ./create_test -testname <new-test-case>.<machine>_<compiler> -testroot <any-path> -project <batch-project> -generate <some-name-for-your-baselines>

Adding a new compset to a test XML file

...

<compset name="CMPASO-NYF">

    <grid name="T62_m120">

        <test name="ERS">

            <machine compiler="intel" testtype="mpas_developer">mustang</machine>

            <machine compiler="gnu" testtype="mpas_developer">mustang</machine>

            <machine compiler="pgi" testtype="mpas_developer">mustang</machine>

        </test>

    </grid>

...

1. list.  Note the comment at the top of this file indicating that you add a test with this format: test>.<grid>.<compset>, and then there is a second argument for mods.

NOTE: acme_integration is a superset of acme_developer (IE, every test in acme_developer automatically goes into acme_integration as well).

Test definition modifiers

The following modifiers can be used in the test name
_CG = gregorian calendar
_D = debug
_E = esmf interfaces
_IOP*= PnetCDF IO test where * is A(atm), C(cpl), G(glc) , I(ice), L(clm), O(ocn), W(wav) or blank (all components)
_L* = set run length y, m, d, h, s, n(nsteps) plus integer (ie _Lm6 for 6 months)
_M* = set the mpilib to *, where * is default, mpi-serial, mpich, etc
_N* = set NINST_ env value to *, where * is an integer
_P* = set pecount to *, where * are specific values which include T, S, M, L, X, 1, 1x1, 16, 16x1, 4x4, etc...
_R* = PTS_MODE test case, valid values are LA, LB, OA, OB

Related articles