User Manual Outputs: Binary Output Format Update?

[johodges]

I remember Glenn making some changes in the binary data outputs a few weeks ago in https://github.com/firemodels/fds/commit/7aa1d5d006c3f0c5d2333ab9ad61caa120862c8a

I think it is just the debug outputs which are not described in the user guide, but I wanted to verify with Glenn. Are there any updates needed to the user guide before the release for these changes?

[briannak7]

Hey all,

I'm collaborating on a package utilizing FDS simulations that are read in with fdsreader. Fdsreader uses .bnd files to read in boundary file data and we noticed the most recent update to FDS have changed these files. When reading the .bf file we're not seeing what we expect to based on the most recent FDS User Guide posted on the NIST website. Is the current user guide consistent with how these files are structured?

There also seems to be inconsistency with how the .bf files are named. The user guide states that "the boundary files defined under the namelist group BNDF are named CHID_n.bf (n=0001,0002...)..." on page 457 however, with CHID='out_0_cat' the .bnd files created are named out_0_cat_1_1.sf.bnd through out_0_cat_1_49.sf.bnd. The simulation we're testing on contains one mesh and we were wondering if the first '1' is in relation to mesh number.

Any insight on these issues being user error or due to a new update would be appreciated!

[mcgratta]

Are you looking at the most recent manuals, 6.9.0?

[briannak7]

I believe so. I'm referencing the sixth edition with the following publish date and revision:

• March 21, 2024 Revision: FDS-6.9.0-0-g6339569.

[mcgratta]

The numbering of files is outdated. We now drop the leading zeros.

[mcgratta]

The first integer is the mesh, the second is the quantity.

[mcgratta]

I think the .bnd file has changed, but the basic format of the boundary (bf) has not. I will double check.

[gforney]

the main change in the .bnd files is that they now only contain the min and max values over up to the time that the values are output not bounds for each time step. I'll double check

On Wed, Mar 27, 2024 at 3:30 PM Kevin McGrattan @.***> wrote:

I think the .bnd file has changed, but the basic format of the boundary (bf) has not. I will double check.

— Reply to this email directly, view it on GitHub https://github.com/firemodels/fds/issues/12529#issuecomment-2023806361, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6UCRRYQA6TJVKNH32YWBTY2MM43AVCNFSM6AAAAABDYAPROOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHAYDMMZWGE . You are receiving this because you were assigned.Message ID: @.***>

-- Glenn Forney