Custom Query (196 matches)


Show under each result:

Results (4 - 6 of 196)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#399 fixed Output from SAVE XSPEC command is faulty in fork-based runs peter peter

When using the SAVE XSPEC command in a fork-based grid run, the resulting FITS file will contain many blocks of only zeros. This is because the results are not communicated between the various forked instances of the code. MPI-based and sequential runs are fine. MPI-based runs use MPI_Reduce() to communicate the results. There is no equivalent for fork-based runs.

#398 fixed DRIVE CASE B command is broken nobody peter

When you run the DRIVE CASE B, it will fail on a TotalInsanity() because the molecular network is not set up.

#394 fixed check_data() may use uninitialized variable nobody peter

The routine check_data() suppresses cautions about md5sum mismatches when the NO TIME command is in effect. Hence it reads the variable prt.lgPrintTime. This variable is first set in the routine InitDefaultsPreparse(). The problem is that by then some data files have already been read and check_data() will have read the "uninitialized" version of prt.lgPrintTime (actually since the data is global, it will have been set to zero / false by default which is the wrong initialization).

There are two solutions.

1) give t_prt a ctor that sets lgPrintTime. This guarantees consistent behavior when the NO TIME command is not in effect, but not when the NO TIME command is used. The latter is a problem because some files are read before the parsing starts, leading to inconsistent behavior of check_data() before and after parsing.

2) revert the change to check_data() and give a caution despite the NO TIME command. This way check_data() no longer needs to access prt.lgPrintTime. However, this will lead to more frequent breaking of the repeatability tests whenever a datafile on a release branch has been updated without updating the md5sum file.

I am not sure yet which is the better solution...

1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.