You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mdbenchmark analyze should show a performance of 0 or some other value (e.g. "simulation not finished"), if it can't find the Performance line in the output file.
Actual behavior
It exits due to this line and the user is shown the typical python stack trace, caused by the warnings.warn.
Currently version of MDBenchmark:
$ mdbenchmark --version
mdbenchmark, version 1.1.1
Proposal
We previously just showed a default value of "0" for all the performances that were not found. We most definitely should go ahead and warn the user that specific systems have not finished yet/correctly, but the current implementation only works if all the runs have finished successfully.
I noticed when GROMACS was not able to do domain decomposition on more than 1 node, so these benchmarks crashed right after starting. The benchmark with one node did work, but mdbenchmark didn't show the actual results.
The text was updated successfully, but these errors were encountered:
Error report
Expected behavior
mdbenchmark analyze
should show a performance of 0 or some other value (e.g. "simulation not finished"), if it can't find thePerformance
line in the output file.Actual behavior
It exits due to this line and the user is shown the typical python stack trace, caused by the
warnings.warn
.Currently version of MDBenchmark:
Proposal
We previously just showed a default value of "0" for all the performances that were not found. We most definitely should go ahead and warn the user that specific systems have not finished yet/correctly, but the current implementation only works if all the runs have finished successfully.
I noticed when GROMACS was not able to do domain decomposition on more than 1 node, so these benchmarks crashed right after starting. The benchmark with one node did work, but
mdbenchmark
didn't show the actual results.The text was updated successfully, but these errors were encountered: