Re-read of prng state sometimes fails on loewe (Defect #716)


Added by Christopher Pinke almost 3 years ago. Updated almost 3 years ago.


Status:Feedback Start date:29 Sep 2014
Priority:Normal Due date:
Assignee:Christopher Pinke % Done:

0%

Category:-
Target version:-

Description

It happened that the saved prng-state could not be reused although the same hardware was used.
This happened only scarcely, but currently the programme does not give further information why the state is not valid.

Matthias, do you know how one could improve this use-case? It should only depend on the number of processors? Perhaps one could save some metainformation with the seeds.


History

Updated by Matthias Bach almost 3 years ago

Besides adding some more logging I don't see what can be done to solve the issue. The number of random states is already stored within the file, and I don't know what other meta information could help.

I am not even sure what can go wrong. Do you have the output of such a run? What exactly is the error shown? Is there some systematic to the failures, e.g. they happen always on the same machines? I fear there might be some bad GPUs in that system. In those cases it might be better to exclude those systems in the SLURM scheduling requests.

  • Assignee changed from Matthias Bach to Christopher Pinke
  • Status changed from New to Feedback

Also available in: Atom PDF