Multiple slices at same coordinate about smv HOT 8 CLOSED

the source of the problem is that the vertical grid solution in 2 of your meshes is 0.2 m but you specify two slices 0.1 m apart. I do not see the problem when slices are 0.2 m or a greater distance apart (If you do see a problem in tthis case then submit a another test case). Until I come up with a fix I suggest you do not pick slices that are closer together than the grid you specified.

from smv.

Thanks, that is useful to know!

Is it OK to ask for one quantity at one Z-value and a different quantity at another, nearby Z-value? For example, temperature at Z=1.5m and visibility at Z=1.8m, in a model with some 0.4m-size cells? (Those two quantities are actually required for standard analysis in the UK -- the logic being that Z=1.5m could represent a firefighter crouching to avoid a hot smoke layer, and Z=1.8m is a reasonable height for sightlines to emergency signs.) I tried that combination as an example, and it turned out OK, but this has always seemed to be an intermittent problem.

from smv.

from smv.

There was some discussion earlier (#1026) about slices being given IDs. Would it be possible to use the ID, as well as the other attributes you mention, to group related slices together (or, more importantly, to separate unrelated slices)? Then, if a user is determined to have closely-spaced slices, they can give them different IDs. (At first it sounds unreasonable to ask for closely-spaced slices, but they are closely-spaced according to the coarsest mesh. In the finest mesh, which is presumably where the important stuff is happening, there may be separate results to look at.)

Anyway, for my purposes, the QUANTITY difference is enough to keep all the slices I want separate, so I'll mark this issue as closed. Thanks for your time!

from smv.

I forgot about slice ids. fds outputs an integer slice id to the .smv file for each &SLCF enty in the input file. i used it and the label (Temperature ,density etc) fds also outputs to group slices together . that seems to work a lot better and makes the code simpler. I still have a lot of testing to do but take a look at your cases with smokeviews posted here
https://drive.google.com/drive/folders/0B_wB1pJL2bFQc1F4cjJWY2duWTA?resourcekey=0-J_yHat7iJoBp1fk6QS8gMA&usp=sharing

from smv.

I took the smokeviews down. they seem to work for your case but were not working for other cases I tested on. (loading wrong slice) I'm taking a look

from smv.

smokeview is back up. let me know if it fixed your issue or if you see any other problems
https://drive.google.com/drive/folders/0B_wB1pJL2bFQc1F4cjJWY2duWTA?resourcekey=0-J_yHat7iJoBp1fk6QS8gMA&usp=sharing

from smv.

I've tried that test version of smokeview on the case that I sent (as run in FDS6.7.9), and it works: the slice at z=1.5m shows results at 1.5m in the finer mesh and at 1.6m in the coarser mesh; there is a single slice to select at z=1.6m, and it shows results from all meshes. So I'll mark this as closed. Thanks for your efforts!

from smv.