-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
add integrator parameters to the InterfaceKinetics::advanceCoverages … #610
add integrator parameters to the InterfaceKinetics::advanceCoverages … #610
Conversation
…& ImplicitSurfChem constructor to allow users to modfiy
Codecov Report
@@ Coverage Diff @@
## master #610 +/- ##
==========================================
+ Coverage 68.52% 68.53% +<.01%
==========================================
Files 363 363
Lines 39957 39978 +21
==========================================
+ Hits 27382 27400 +18
- Misses 12575 12578 +3
Continue to review full report at Codecov.
|
Yes, I think your first suggested test is a good one. For the tolerances, I agree that creating |
Not sure why the OSX TravisCI job timed out? |
@arghdos I restarted the job, let's see what happens |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a little bit of cleanup to be done, but this looks pretty good as far as the actual user-facing part of it goes.
fe5e75f
to
995a758
Compare
…hon interface, and test
995a758
to
8634242
Compare
@speth -- updated this, should be good now |
…& ImplicitSurfChem constructor to allow users to modfiy
Please fill in the issue number this pull request is fixing:
Fixes #608
Changes proposed in this pull request:
@speth -- what would be a good test here? Something like simultaneously limiting the maximum step-size to
t_out/N
while limiting the maximum number of steps toN-1
would be a good test from the cython interface for those values, but I'm not sure how to test that the rtol / atol or error test failures are correctly set without lowering the tests into C++? I guess I could add some information methods (similar to those in the base Integrator class) to query these directly, but that doesn't seem to fit well with the very short lived nature of the integrator inside of InterfaceKinetics...