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 W- messages:  These are serious problems.
  2) Whether the PROBLEM, WARNING, 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 W- messages: good, none found.

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 1 lines of text in the file minor.txt.

Looking for WARNING string in the output files:
WARNING messages were found.  Check warnings.txt for names.
There are 2019 lines of text in the file warnings.txt.

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.

306 sims are present, 306 are OK.
Minor problems were found, this is normal, list is in minor.txt
WARNING messages were found, list is in warnings.txt
The test suite was successful; you have a valid executable.

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 W- messages:  These are serious problems.
  2) Whether the PROBLEM, WARNING, 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 W- messages: good, none found.

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

Looking for WARNING string in the output files:
WARNING messages were found.  Check warnings.txt for names.
There are 6 lines of text in the file warnings.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.

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

31 sims are present, 31 are OK.
WARNING messages were found, list is in warnings.txt
The test suite was successful; you have a valid executable.

Looking for unmatched wavelengths: good, none found.