BNDF XB control

[drjfloyd]

I have a case with a large number of meshes where in only some locations I want boundary output. The smokeview domain limit feature takes some extra processing time as smokeview has to figure out whether or not to load a specific mesh or output patch. On the FDS input file size, it is a complicated geometry and having to one-by-one figure out which OBST need to have BNDF_OBST set would take a bit of time. I could bulk select in Pyrosim but many OBST extend beyond the region where I care about output and having to break all those up for more fine grained control would take time.

I think it would be useful to either have XB on BNDF or something like a DUMP_BNDF flag on MESH. Given how we generate the list of OBST and VENT patches for the BNDF output and write them, XB might be tricky to implement. DUMP_BNDF on MESH should be pretty easy to do as we would just skip calling any BNDF setup or output routine if that flag was FALSE for the current MESH. I think the MESH approach would not impact Smokeview as it can already deal with loading a partial set of BNDF files in cases whjere not all bf files in the smv file are present.

[drjfloyd]

Recent smokeview changes now limit loading to meshes within or touched by an XB but still think would be useful to not even write the data if not needed to make file transfer faster from an HPC to a local drive.

[drjfloyd]

Added BNDF_MESH (default T) to MESH. When set to F it does not output any BNDF files for that MESH.