I've got an interesting potential S-SAD solution that crops up rarely in a script I was using to trawl parameter space in phenix.hyss. Since I was not optimistic of the outcome I did not save all output files. Hyss appears to use a random number generator and allows the seed to be specified on the command line, so is there any way to figure out what random number seed it used based on the information written to stdout while the program is running ? Merely running the command again does not trivially recreate the solution and egrep -i 'rand|seed' LOG only pulls out: Nigel Moriarty, Reetal Pai, Randy Read, Jane Richardson, David Richardson, time_log: p1_recycling random_omit: 990 1.49 0 0.00151 time_log: random_omit: 891 0.62 0 0.000696 Cheers Phil Jeffrey Princeton
On Sat, Aug 18, 2012 at 3:40 AM, Jeffrey, Philip D.
I've got an interesting potential S-SAD solution that crops up rarely in a script I was using to trawl parameter space in phenix.hyss. Since I was not optimistic of the outcome I did not save all output files. Hyss appears to use a random number generator and allows the seed to be specified on the command line, so is there any way to figure out what random number seed it used based on the information written to stdout while the program is running ?
From the Python documentation for randon.seed(x):
"If x is omitted or None, current system time is used; current system time is also used to initialize the generator when the module is first imported." My guess is it's going to be very difficult to reproduce this. -Nat
participants (2)
-
Jeffrey, Philip D. -
Nathaniel Echols