0x10001
0x20002
0x40004
0x80008
0x100010
0x200020
0x400040
0x800080
0x1000100
0x2000200
0x4000400
0x8000800
0x10001000
0x20002000
0x40004000
0x80008000





========================================
      Checking auto test suite          
========================================

This script checks for problems in the output from the Cloudy test suite.
  It checks for three things in the simulations:
  1) Botched monitors or warnings:  These are serious problems.
  2) Whether the PROBLEM or DEBUG string were printed.
  3) Crashes, in which the code did not end - these are also serious problems.

Looking for crashes, botched results and warnings:
WARNING! crashes, failures, botches or warnings were found. This is a serious problem.
Cloudy crashed in 1 sims.
Check the file serious.txt for names, serious.asr for botched monitors.

Looking for PROBLEM string in the output files:
PROBLEM string was found.  Check minor.txt for a list of names.
This can occur a few times and is not a serious concern.
There are 2281 lines of text in the file minor.txt.

Some sims are close to a monitor.  Check close.txt for a list of names.
This is for information only, not a problem.

Looking for DEBUG string or TestCode call: good, none found.

Now I will check whether the output in func_test_cycle.out repeats exactly:
all sims are equal

Now I will check whether the output in func_test_grid.out repeats exactly:
all sims are equal

Looking for skipped sims: good: no sims were skipped.

301 sims are present, 1 crashed, 300 are OK.
Minor problems were found, this is normal, list is in minor.txt
Serious problems were found. See serious.txt for a summary

Looking for unmatched wavelengths: good, none found.




========================================
      Checking slow test suite          
========================================

This script checks for problems in the output from the Cloudy test suite.
  It checks for three things in the simulations:
  1) Botched monitors or warnings:  These are serious problems.
  2) Whether the PROBLEM or DEBUG string were printed.
  3) Crashes, in which the code did not end - these are also serious problems.

Looking for crashes, botched results and warnings: good, none found.

Looking for PROBLEM string in the output files: good, none found.

Some sims are close to a monitor.  Check close.txt for a list of names.
This is for information only, not a problem.

Looking for DEBUG string or TestCode call: good, none found.

Looking for skipped sims: good: no sims were skipped.

31 sims are present, 31 are OK.
The test suite was successful; you have a valid executable.

Looking for unmatched wavelengths: good, none found.