-
Notifications
You must be signed in to change notification settings - Fork 62
Improve APBS test cases with intermediate result analysis #64
Comments
This is a great idea. I'm not sure how to implement it though. On one hand, if all of the intermediate calculations are not available via .in file commands, then we'll need to add support for those. The bigger issue in my mind is: where do we get the ground truth values to compare against? These may both be non-issues, and I just don't know it. |
Hi Keith -- There is intermediate output from various ELEC blocks that could be parsed On Mon, Aug 31, 2015 at 3:21 PM, Keith T. Star [email protected]
|
And for ground truth? Where can I go to find the expected values for each of the intermediate steps, for each of the tests? |
This is primarily a regression test, so referring to results from past On Tue, Sep 1, 2015 at 6:03 AM, Keith T. Star [email protected]
|
Did you mean to assign this to Keith? On Tue, Dec 15, 2015 at 4:25 PM, Liz [email protected] wrote:
|
@sobolevnrm were you thinking on something like writing the intermediate charge or pot from the elec block to files and then compare them to previous apbs versions? |
I think writing the intermediate energies in mg-para and mg-auto On Wed, Dec 30, 2015 at 11:51 AM Juan [email protected] wrote:
|
Reading intermediate results and comparing them, but need to modify all the test cases and run against builds. Still in progress (moving to next milestone). |
…As soon as testing is done I'll merge with master.
(issue #64) Finished updating the test_cases.cgf file to contain the intermediate results.
Finish the python code to extract intermediate energies and added the the expected values to the cfg file as well (34edf403d74cd0acd4061b44d117647cc6acb29d)[64edf40]). Do we want to keep this issue open in case we add more test instances or can we close it? |
we can close it! |
Many of the APBS test cases produce results at the intermediate stages of the calculations that can provide additional information for ensuring agreement between versions (and identifying the source of disagreement when it occurs). In addition to using the final output (e.g., from the PRINT statement), we should include this intermediate output in our test cases' checking behavior.
The text was updated successfully, but these errors were encountered: