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
HistogramVectorPostprocessor only works with VPPs whose vectors are defined at construction #18459
Comments
The fix for this is pretty simple -- we just move some code that was run at construction to |
Turns out that we can actually solve this problem by having our other VPP figure out its vectors at construction time. However, I'm keeping this ticket open because we should improve the error behavior of this. Currently, this is the error message you get if your other VPP doesn't have any vectors:
We need to change this to give an error message that actually tells you what is going on here. |
idaholab#18459 - Generate an error if no vectors are provided in the VPP that is used as input. - Move the initialization to initialSetup() to remove order dependence of VPPs in input file. - Add a test of the newly-added error. - Add empty VPP testing object used by this test.
idaholab#18459 - Generate an error if no vectors are provided in the VPP that is used as input. - Move the initialization to initialSetup() to remove order dependence of VPPs in input file. - Add a test of the newly-added error. - Add empty VPP testing object used by this test.
idaholab#18459 - Generate an error if no vectors are provided in the VPP that is used as input. - Move the initialization to initialSetup() to remove order dependence of VPPs in input file. - Add a test of the newly-added error. - Add empty VPP testing object used by this test.
Bug Description
HistogramVectorPostprocessor
computes a histogram from the values in the vectors computed by anotherVectorPostprocessor
. TheHistogramVectorPostprocessor
declares its vectors based on the names of the vectors in the other VPP at construction time. If those are not yet created at that time, it errors out.Steps to Reproduce
Use
HistogramVectorPostprocessor
with a VPP that delays its creation of vectors. I ran into this problem in Grizzly with a VPP that has to delay when it declares its vectors because the number of vectors is only known at theinitialize()
phase. I don't know whether there are VPPs like that in MOOSE.Impact
This is preventing us from using this VPP.
The text was updated successfully, but these errors were encountered: