Conversation
|
Job Documentation, step Sync to remote on 510ae3c wanted to post the following: View the site here This comment will be updated on new commits. |
simopier
left a comment
There was a problem hiding this comment.
This is not a full review, I'm just providing suggestions to solve the current test failures.
Also, make sure to add a reference to the issue number in the PR message at the top of the page.
|
Hi @simopier , I had a question regarding the reaction Could you please advise on how to ensure the equilibrium law is respected in TMAP8? I tried to illustrate this in the last Python subplot figure, but the equilibrium isn’t fully reached yet. Also, I set an arbitrary reaction rate constant Thanks in advance for your help! |
simopier
left a comment
There was a problem hiding this comment.
You're on the right track!
Here's a partial review with some suggestions. I'll need to do a deeper review once you have all the pieces together.
This comment was marked as duplicate.
This comment was marked as duplicate.
1 similar comment
Great questions! You correctly identified that while TMAP7 uses an equilibrium condition, we probably want to use a kinetic description in TMAP8 to be more general. However, we need to reconcile the two to obtain the same equilibrium condition. at equilibrium: So, to obtain the same equilibrium as in TMAP7, you can define Please double check the math above, but that should give you all you need to address your questions above. Here, you'll need to add blocks for the chemical reactions (feel free to check other cases if you are unsure how to do it), and select appropriate values for I hope that helps! Let me know if you have other questions. |
Co-authored-by: Pierre-Clement Simon <pierreclement.simon@gmail.com>
|
Hi @simopier, |
|
The ver-1kc branch has already been merged in your previous PR. Right now, you are getting failures because you have not updated ver-1kc.md into ver-1kc-1.md everywhere. For example, in the test specification file for ver-1kc-1, it still says instead of |
simopier
left a comment
There was a problem hiding this comment.
Here's a new round of reviews. Let me know if you have any questions.
Co-authored-by: Pierre-Clement Simon <pierreclement.simon@gmail.com>
simopier
left a comment
There was a problem hiding this comment.
Things are looking good!
My main remaining concerns are:
- the very loose tolerances. They should be much smaller.
- the fact that we do not match the right equilibrium condition (very likely due to large tolerances and large time steps)
- The discussion about K1 and K2 in the documentation, where we are not exactly on the same page.
As you try to refine the tolerances, feel free to play with the values of K_1 and K_2. Try to make them lower and higher (still with eta=2) to understand their impact on the results and on convergence.
Co-authored-by: Pierre-Clement Simon <pierreclement.simon@gmail.com>
simopier
left a comment
There was a problem hiding this comment.
The equilibrium is much better with tighter tolerances! But I think we still have some room for improvement, especially for enclosure 2.
What was your experience playing with the tolerances and seeing their impact on the results?
Compared to the previous solving parameters, the results are noticeably better and faster. Specifically, increasing the growth factor has helped reduce the testing time, as larger time steps can be used. In this case, I set Moreover, this is quite strange that, while both the standard and heavy tests fail here, running them locally works without issues (no mismatches in the CSV files). |
|
Hi @simopier, |
simopier
left a comment
There was a problem hiding this comment.
I played around locally and realized the heavy test did not pass on my machine.
I also cleaned up a couple things as simple review suggestions.
|
Hey @lkadz, we usually don't use JFNK. NEWTON and PJFNK often provide much better performances in terms of accuracy and costs. See some of the solve type descriptions in https://mooseframework.inl.gov/TMAP8/source/executioners/Steady.html#steady. So I moved to PJFNK with a pre-conditioner and it allowed me to tighten the tolerance a lot (from 1e-8 to 1e-50 for nl-abs and from 1e-6 to 1e-8 for nl_rel, which are the default values) while making the tests a lot faster. Using smaller tolerances might help with the tests failures we were experiencing before (fingers crossed, we'll see how testing goes). Please look at my latest commits to make sure to learn from these changes. |
simopier
left a comment
There was a problem hiding this comment.
Looks good, thank you!
|
@cticenhour, this looks good to me. But could you please take a look at my latest commits and either (1) agree that these correspond to review suggestions and do not require a secondary review, or (2) review my commits. |
|
I went ahead and reviewed everything. Looks good. Thanks @lkadz! |
(Ref. #12)