Smokeview: How to hide obstacles

[helios]

Dear all,

I have done a simulation of a fire in a tunnel. In order to have
better visualization of the results, I want to make part of the tunnel
to be INVISIBLE. Is there any way to make some obstacles INVISIBLE
after the simulation has finished (I haven't define the INVISIBLE
option is the input file)?

Thanks in advanced,
ilias

[Dave McGill]

Hi Ilias,

Create a new folder and alter your input file to make the desired
areas invisible, run the program long enough to generate a new
Smokeview file (.smv), and then replace the old .smv file with the
new .smv file. The file names will have to be the same, and ensure
that you run the second iteration in a separate folder so you don't
overwrite all your existing data.

Dave

[dr_jfloyd]

If you have devices that change state (like a sprinkler), then you may wish to take the extra step of opening the old and the new .smv files and copying the tail end of the old smv file (which is where all the device state changes are written) to new one.

[helios]

Thank you all very much.

[Andrew Louie]

Isn't the slice file information also saved in the smv file? if you rerun the simulation to generate an new smv file, you'll lose your entire menu of results plots. I think it's easier to generate that 2nd SMV file with the hidden obst's that you want, then diff it against your original SMV file, and only copy over the changes to the OBST areas of the file, There should be like 2 lines changed per changed OBST. You have to leave the bottom of the file that contains all the information about the results data, and the one line at the top "VIEWTIMES" alone in the original SMV file. 

Save the newly patched SMV file as another name in case you mess up. 

Also Note: Transparency only works if you specify a color for the OBST first. If you want to make a particular obst invisible with TRANSPARENCY=0.0, you have to put COLOR='GREEN' in front first for the transparency effect to work. 

 

> On Wednesday, May 30, 2012 7:00:46 AM UTC-4, Dave McGill wrote:
>
> > Hi Ilias,
>
> > Create a new folder and  alter your input file to make the desired
> > areas invisible, run the program long enough to  generate a new
> > Smokeview file (.smv), and then replace the old .smv file with the
> > new .smv file. The file names will have to be the same, and ensure
> > that you run the second iteration in a separate folder so you don't
> > overwrite all your existing data.
>
> > Dave
>
> > On May 30, 4:08 am, helios <eliasc...@hotmail.com> wrote:
> > > Dear all,
>
> > > I have done a simulation of a fire in a tunnel. In order to have
> > > better visualization of the results, I want to make part of the tunnel
> > > to be INVISIBLE. Is there any way to make some obstacles INVISIBLE
> > > after the simulation has finished (I haven't define the INVISIBLE
> > > option is the input file)?
>
> > > Thanks in advanced,
> > > ilias

--
-Andrew Louie :wq

[GF]

FDS writes out most of the information smokeview use when FDS first
starts up. So slice file and other file info should not be lost.
What is not written out is as Jason said various state changes -
device activation/deactivation . PLOT3D file info is written out as
FDS creates the files. So you will lose PLOT3D file info. You will
need to copy this info over the the new .smv file.

[N_ Sh]

hi.would you please help me to download fds 5.5.5. i can't download it from the sight. when i select download link, gmail will appear.