PerformanceData Postprocessor Error #16625
-
I am trying to obtain the jacobian compute metrics for a simulation in Bison app using the PerformanceData postprocessor and keep getting the following error: Unknown section_name: FEProblem::computeJacobianInternal in PerfGraph::getTime() If I change the I tried to debug it. Looking at the top frame when it is about to error out: it tries to find When I remove this postprocessor and turn on the I am wondering why is the PerformanceData postprocessor failing to retrieve the jacobian compute information. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 3 replies
-
@friedmud Can you help with this? |
Beta Was this translation helpful? Give feedback.
-
Just wondering if someone could help with this. Let me know if you need any information. |
Beta Was this translation helpful? Give feedback.
-
I believe this is what you're looking for:
See here for more information: https://mooseframework.inl.gov/source/postprocessors/PerfGraphData.html |
Beta Was this translation helpful? Give feedback.
-
Alright, found the issue. Postprocessors by default run on For the time being, your solution is to set This isn't a very friendly error. We actually register the section very early on (well before |
Beta Was this translation helpful? Give feedback.
-
#16704 will resolve this issue in the future - valid sections will return zero if they have not ran yet. |
Beta Was this translation helpful? Give feedback.
Alright, found the issue. Postprocessors by default run on
TIMESTEP_END
. If the section that you are executing has not been called yet beforeTIMESTEP_END
, it doesn't exist it'll error out that it can't find the section.For the time being, your solution is to set
execute_on
to something on your own that occurs after the section has been called, which in your case is almost anything butTIMESTEP_END
. Something likeNONLINEAR
orFINAL
.This isn't a very friendly error. We actually register the section very early on (well before
INITIAL
), therefore we do know that it exists. I'll work on a change that makes this more meaningful. I'd prefer that it just return 0 in all cases if it has been r…