RELAP-7 and MARMOT take too long to load in Model Builder
Modeling and Simulation made NiCE!
Brought to you by:
amccaskey,
jayjaybillings
Alright, this is a of consequence of the
MOOSEModel.mergeInputIntoYaml()method being so daggum complicated. In particular, when I comment out the entireelse ifblock starting at line 1220, the loading time instantly improved dramatically.The section in question would come into play when a top-level block was read in that wasn't found in the YAML file. It would try to discern if the unmatched block is left-over from the last loaded YAML tree (in which case, toss it out), or is a custom block created by the user (in which case, keep it).
This was a duct-tapey fix I implemented when we were running into trouble with the "Output" vs. "Outputs" block names not matching (due to our YAML files being out of date), and can be really inefficient. I can try to fix it up to be more efficient, or we can just do away with it altogether as the BISON team did say there should never be any custom top-level blocks.
Given what the Bison team said, I vote to dump it.
Jay
On Oct 27, 2014 3:38 PM, "Anna Wojtowicz" awoj@users.sf.net wrote:
Related
MOOSE Bugs:
#18I GOT 99 PROBLEMS BUT TOGGLING BETWEEN TREES AIN'T ONE OF THEM