Open croquemadame opened 4 months ago
I went ahead and made the suggested modification, and now I am getting an error message in accordance to the simulation results. I am attaching a patch.
0001-fixed-minMaxTemperatureFieldOutOfRange-parallel-issu.patch
Edit: Added proper patch file.
Describe the bug When running in parallel, I am getting a warning similar to the one pasted below.
Attempt to use rho2ReactionThermo out of temperature range 263635 times during this iteration. Thigh: 40000 < 240000
The second line caught my attention since it is an exact multiple of the number of processors I am using, np, times Thigh, i.e, np*Thigh.
I looked in the code and it seems to me the problem lies in the following lines
https://github.com/hystrath/hyStrath/blob/984e3000a5f8d2e47cee555ec466d58ea9a6315d/src/thermophysicalModels/strath/strathReactionThermo/reactionThermo/rho2ReactionThermo/rho2ReactionThermo.H#L319
and
https://github.com/hystrath/hyStrath/blob/984e3000a5f8d2e47cee555ec466d58ea9a6315d/src/thermophysicalModels/strath/strathReactionThermo/reactionThermo/rho2ReactionThermo/rho2ReactionThermo.H#L320
To Reproduce Any case where the temperature limit is exceeded, running in parallel. In my case it is actually the lower bound that is exceeded, but I am receiving a warning about the upper bound. I believe this is happening because the check that is made
https://github.com/hystrath/hyStrath/blob/984e3000a5f8d2e47cee555ec466d58ea9a6315d/src/thermophysicalModels/strath/strathReactionThermo/reactionThermo/rho2ReactionThermo/rho2ReactionThermo.H#L328
returns false since the value stored in minMaxTemperatureFieldOutOfRange[0] is something close to 600 (6*100) instead of the lowest temperature in the domain, which I can see in my simulation results before the crash is 100 K.
Expected behavior The code should report the highest/lowest offending temperature in the domain. I believe the issue can be fixed by substituting
sumOp<scalar>()
bymaxOp<scalar>()
andsumOp<scalar>()
byminOp<scalar>()
, accordingly.Environment
Additional context [ ] Is the bug specifically related to hyStrath? Yes [ ] Have you read the documentation on the hyStrath website? Yes [ ] Has it been covered in one or more Issues before? Not to the best of my knowledge
Add any other context about the problem here.
NB: You may be asked to attach a test case in a later stage.