Closed stkroe closed 6 months ago
Hmm... really strange bug. For my test system it worked yesterday evening. On what kind of machine did you run this simulation?
I'll have a look at it later today.
On the CPU_rune cluster. It seems that also on the local machine it does not work ... very strange. Maby I have a wrong setting.
It seems to be fixed now in tag 0.3.8.1 - Could you please try it yourself?
It tried it. It works now. Thanks.
Describe the bug
The new feature keyword
qm_loop_time_limit
does not allow running the simulation properly. If the keyword is set to a value, the simulation is stuck during the first simulation step. No trajectory and even nodetailed.out
of the DFTB+ calculation is written. After the loop time limit is reached, the calculation will be stopped. Also higher time limit does not make a difference. If the keyword is not set, everything works fine.To Reproduce
A QMMD simulation was running on our cluster using DFTB+ with the PQ v.0.3.8.0. For reproducibility, an input file is attached:
input-file.zip
Expected behavior
If the keyword is set, the user specifies a loop time limit for QM calculations. If the limit is reached, the calculation will be stopped.
Screenshots
The files after the simulation is stopped due to the time limit: The
run.out
file: The slurm output: