firemodels
Smokeview and AMPUA on GEOM
See the input file in Issue #8606
The first time I ran the case in #8606 Smokeview successfully showed the AMPUA on the GEOM. I went to reload during the run and it stopped showing the AMPUA (everything was zero value). I tried deleting files and rerunning, rebooting, installing the lastest SMV from the Google drive test directory, and rebooting again. Smokeview never showed values on the GEOM again.
smokeview has some problems which I'm looking at but I'm seeing all zero's in the AMPUA geometry boundary file when I look with the debugger. Is that what you were expecting?
Changes made for the related issue #8606 have fixed the original issue reported here; however, there is another issue I am seeing. If I load the GEOM BNDF data while FDS is running, I see what I expect on the GEOM. If I try and reload I get two sets of behavior.
-If I have both the OBST and GEOM BNDF data loaded, when I reload I get the OBST and the first mesh of GEOM. The other two meshes loose their data. -If I have only the GEOM BNDF data loaded, when I reload I loose all the data.
If I unload all and then load, then all the data is there.
Glenn -- I would suggest that we combine the BNDF menu item for the conventional OBSTs and the new "geometry" boundaries. That might eliminate these kinds of discrepancies.
I reran the case in #8606. In smokeview when I have just the OBST BNDF loaded, I can set the min/max in the file/bounds dialog. With the GEOM BNDF, I cannot type anything in the min/max boxes.
I think Kevin's suggestion in the prior post is still good rather than having to load the same BNDF QUANTITY twice.