Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Criteria for successful runs. #13

Open
365andreas opened this issue Nov 13, 2020 · 0 comments
Open

Criteria for successful runs. #13

365andreas opened this issue Nov 13, 2020 · 0 comments

Comments

@365andreas
Copy link

365andreas commented Nov 13, 2020

I am Andreas Triantafyllos from Huawei and I would like to ask for some clarification about the evaluation of a simulation.

I was wondering if there are specific references that explain the criteria to consider a simulation run as successful.

In particular, I am referring to:

miniMD/ref/run_one_test

Lines 131 to 132 in 7576016

x=sqrt(2)*(0.5+atan2($1-d*'"${precision}"',50)/3.1415);\
v=sqrt($2*$2); if(v>stddev_t*x+add_t) t=t+1;\

How was the formula that takes into account the precision of floating-point numbers derived?

and

if(t+e+p>3*0.38*total) print " Failed (" t/total " ; " e/total " ; " p/total " ; Expected 0.32+-0.06)";}' out.compare

Why do total errors compared to the reference output have to be in the range 32% ± 6% in order to consider a run as successful? How was this range chosen?

I would be grateful if anyone could share any explanation or reference to the literature about the above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant