Personal tools
You are here: Home / Software / Simulation / XNS / XNS Validation

XNS Validation

Even small modifications to EWD or XNS should be followed by (more or less) automatic validation step. The xns CVS module includes cases directory Cases and script Validate. Older scripts Validate.<arch> where <arch> can be powerpc, i386, or crayt3e, are also still available.

The steps required are:

  • Make sure that Cases/adv.0400, Cases/dallas.0153 etc. directories are present and that they contain required mesh files.
  • Edit Validate and modify two lines at the top that define old and new release name, like R1204a. These will become a suffix to the newly-obtained log files. For just testing the current XNS and not committing it, the new release name should be set to none which disables saving the new log files. The old release name will be used to try and locate log files from a previous validation run, in the work directories. If this is a first validation run, one can comment out the diff lines; note that in this case we will not be able to compare new results to any old results.
  • It simplifies debugging of later releases to save the XNS executable with the release suffix, e.g., xns.R1204a.
  • Start 8 PE interactive job if necessary and run the script. On the RZ Xeon or Bull cluster, small interactive MPI jobs can be run from the command line with mpiexec and it is not necessary to interact with the job system.
  • This will run all the validation cases in sequence (less than 30 s per case), stopping after each of them and comparing new log to an old log. Scroll through the diff output, ignoring slight timing differences. There should be no differences other than timing, or the second line in the log file that contains the date. If there are differences in residual history, make sure you know where they come from, or start debugging! If some cases slowed down dramatically, that also needs to be explained. It is not necessary to justify dramatic speed-ups, should they occur.

Only following a successful validation, one should push major changes to the central Git branches, or tag a particular set of revisions.

« May 2013 »
May
MoTuWeThFrSaSu
12345
6789101112
13141516171819
20212223242526
2728293031
Upcoming Events
Marine 2013 May 29, 2013 - May 31, 2013 — Hamburg, Germany
MPF 2013 Jun 11, 2013 - Jun 14, 2013 — Sardinia, Italy
Coupled Problems 2013 Jun 17, 2013 - Jun 19, 2013 — Ibiza, Spain
USNCCM 12 Jul 22, 2013 - Jul 25, 2013 — Raleigh, North Carolina
GACM 2013 Sep 30, 2013 - Oct 02, 2013 — Hamburg, Germany
Upcoming events…