-
Notifications
You must be signed in to change notification settings - Fork 170
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
Smokeview not displaying boundary data at mesh interface #1845
Comments
Ill take a look
…On Wed, Mar 20, 2024, 8:37 AM Jason Floyd ***@***.***> wrote:
When loading the bndf file using last night's build the OBST at the MESH
boundary does not have BNDF data being displayed. Using fds2ascii, if I
extract the -1 direction data I can see that we are writing the data.
&HEAD CHID='bndf_test'/
&MESH IJK=10,1,10,XB=0,1,0,1,0,1/
&MESH IJK=10,1,10,XB=1,2,0,1,0,1/
&TIME T_END=1/
&OBST XB=1,1.1,0,1,0,1/
&OBST XB=0.4,0.5,0,1,0,1/
&BNDF QUANTITY='WALL TEMPERATURE'/
bndf_test_0002.png (view on web)
<https://github.com/firemodels/smv/assets/12799217/d5cd898b-474d-4019-9481-4f2a192eafff>
—
Reply to this email directly, view it on GitHub
<#1845>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6UCRQ2NTNKRX2ZUNLZXC3YZF7HPAVCNFSM6AAAAABE7MONWSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TONBTGEYTAMY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
should be fixed in smokeview posted here. hopefully this is not a whackamole bug - that is let me know if you see boundary files displayed at mesh interfaces without blockages (I didn't see any instances of this) |
I see the boundary files but smokeview isn't setting the initial color bar to the bounds for BNDF. The colorbar should be ~0 - 25 kW/m2 for incident flux but it is 0 - 0 kW/m2. The case is an 80 mesh DNS case but it is 2D so running single core won't take long to get to 0.01 s |
Ill take a look
…On Sun, Mar 31, 2024, 8:59 AM Jason Floyd ***@***.***> wrote:
I see the boundary files but smokeview isn't setting the initial color bar
to the bounds for BNDF. The colorbar should be ~0 - 25 kW/m2 for incident
flux but it is 0 - 0 kW/m2.
The case is an 80 mesh DNS case but it is 2D so running single core won't
take long to get to 0.01 s
sensor_25_0598.png (view on web)
<https://github.com/firemodels/smv/assets/12799217/ea7d1f13-73f5-4dcc-a358-41b192b908d1>
sensor_25.txt
<https://github.com/firemodels/smv/files/14815942/sensor_25.txt>
—
Reply to this email directly, view it on GitHub
<#1845 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6UCRWO3R5SRXAPZJFZ53DY3ACB7AVCNFSM6AAAAABE7MONWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYG4YTCNZZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
try smokeview posted at link below or update your smv repo and rebuild. cell centered and node centered boundary files (and slice files) output the same amount of data. when cell centered data is output the first row and first column is ignored. smokeview had a flaw in how it was ignoring data in this case (was using the mod function wrong) https://github.com/firemodels/test_bundles/releases/tag/SMOKEVIEW_TEST2 |
looks ok now. Thanks. |
When loading the bndf file using last night's build the OBST at the MESH boundary does not have BNDF data being displayed. Using fds2ascii, if I extract the -1 direction data I can see that we are writing the data.
&HEAD CHID='bndf_test'/
&MESH IJK=10,1,10,XB=0,1,0,1,0,1/
&MESH IJK=10,1,10,XB=1,2,0,1,0,1/
&TIME T_END=1/
&OBST XB=1,1.1,0,1,0,1/
&OBST XB=0.4,0.5,0,1,0,1/
&BNDF QUANTITY='WALL TEMPERATURE'/
The text was updated successfully, but these errors were encountered: