computations/root_digger

Random seed

Closed this issue · 5 comments

stitam commented

Hi, I tried to run the program with a fixed seed to ensure my analysis was fully reproducible. I expected that the numeric value I set with --seed would be the same as the value listed in the console output after Seed:. However, these values do not match. Should these values match? I am running root digger in a container which was built using the Dockerfile in this repo.

They should, and in fact they do on my end. HOWEVER: rootdigger always reloads from a checkpoint if possible, and the seed is stored in the checkpoint. Please make sure that you aren't loading from a checkpoint. There should be a line like

[0.00] [Warning] Loading options from the checkpoint file. Some cli options are ignored. If the program is not working, try deleting the checkpoint file

if you are.

stitam commented

Thanks @computations, where can I find this checkpoint file? Also, I noticed when running the container with --no-home option (do not mount the home dir) it didn't find the checkpoint file: There was an error during processing: Failed to open the checkpoint file. I am wondering, is it possible to read/write this file from/to the working directory?

The checkpoint is name <PREFIX>.ckp, and the default prefix is the name of the tree file.

I am wondering, is it possible to read/write this file from/to the working directory?

I'm a little unclear what you mean here, however I am going to try and answer it. The checkpoint file contains all the results (along with some other details), and is written to continuously throughout the run. So, the location of the checkpoint file requires both read and write permissions.

stitam commented

Failed to open the checkpoint file only came up because of some silly container mistake on my end. Thanks @computations for your clarification around the checkpoint file. All clear, --seed works as intended.

No problem, happy to help!