Problems using the “Renderall” and “Renderdir”commands.

[GoogleCodeExporter]

Please complete the following lines...

Application Version: 5.3.10
SVN Revision Number: FDS_5[1].3.0-SMV_5.3.10_Windows
Compile Date:17/7/2009
Operating System: Windows XP SP3

Describe details of the issue below:

I am having some problems writing smokeview scripts. In particular using
the “Renderall” and “Renderdir”commands.

I am trying to write scripts so that I can quickly load a large number of
slices and export images to make videos; without having to navigate all the
menus for each slice. I am trying to “renderall” (every 2 secs) pngs of
slices to chosen directories to make videos.

Problem:
When using “Renderdir “command and the “renderall” command: When 
specifying
the suffix/prefix for the png file, Smokeview does “renderall” into the
chosen directory but doesn’t rename the png files for every time step (ie
just writes over the original filename_001 for every time step.

Here is a sample of the script im using:

RENDERDIR
 C:\Documents and Settings\sam.hayhurst\Desktop\London_Project\Visibility
LOADSLICE
 soot VISIBILITY
 2 393.000000
LOADSLICE
RENDERALL
2
L11_visibility

This should render every two seconds of the slice and dump it in a set
directory in my C: drive. All pngs should be named: 
L11_visibility_0001
L11_visibility_0002
L11_visibility_0003
Etc.

What happens is it names each file 
L11_visibility_0001
L11_visibility_0001
L11_visibility_0001 etc, so each png of a timestep overwrites the previous
timestep.

I have also tried to work around the problem by setting render directories
in the casename.ini but no joy.

Does anyone have any suggestions for this?

Many thanks

Sam

Original issue reported on code.google.com by samhayhu...@gmail.com on 17 Jul 2009 at 11:33

[GoogleCodeExporter]

I'll take a look at it

Original comment by gfor...@gmail.com on 17 Jul 2009 at 11:35

• Changed state: Accepted

[GoogleCodeExporter]

try out the test smokeview (revision 4397) I just posted for win32.  Make sure 
though
you don't have a LOADSLICE command just before your RENDERALL line as in the 
above -
this by itself would cause the RENDERALL command to not work (because smokeview 
would
think it was an option for the previous LOADSLICE command)

Report back to confirm the fix.

Original comment by gfor...@gmail.com on 17 Jul 2009 at 1:08

• Changed state: Fixed

[GoogleCodeExporter]

Great it works perfectly, the loadslice information must have got lost in the
copy/pasting.

Thanks for getting this seen to and fixed so quickly!

Many Thanks

Sam

Original comment by samhayhu...@gmail.com on 21 Jul 2009 at 4:23

[GoogleCodeExporter]

thanks for reporting back - I'll mark this as verified

Original comment by gfor...@gmail.com on 21 Jul 2009 at 4:27

• Changed state: Verified

[GoogleCodeExporter]

Hi

I have tried to use a script to generate a image for every timesteep as below:

RENDERDIR
 C:\CFD\FigTest
LOADFILE
 plume5c_01.sf
 2 400.0000
RENDERALL
2
hast

I get the same problem as samhayhurst has described. I am using following 
version:
(FDS)
Application Version: 5.4.3
SVN Revision Number: 5210
Compile Date: Thu, 03, Dec 2009 

(Smokeview)
Version: 5.4.8
Revision Number: 5220
compile Date: Dec 3 2009
Operating System: Windows XP

Original comment by toger...@gmail.com on 5 Mar 2010 at 1:58

[GoogleCodeExporter]

I'll take a look at it.

Original comment by gfor...@gmail.com on 5 Mar 2010 at 2:11

• Changed state: Accepted

[GoogleCodeExporter]

If I delete the string "hast" then it runs fine. It will then give every 
picture the 
name plume5c_000X.png

Original comment by toger...@gmail.com on 5 Mar 2010 at 2:25

[GoogleCodeExporter]

upload your .fds input file - is that your entire script in comment 5?  If not 
then
upload that too.

Original comment by gfor...@gmail.com on 5 Mar 2010 at 2:44

[GoogleCodeExporter]

should be fixed in the test smokeview just posted.  Try it out and report back
whether it works for your case.

Original comment by gfor...@gmail.com on 14 Mar 2010 at 12:21

• Changed state: Fixed

[GoogleCodeExporter]

is it working for your case now?

Original comment by gfor...@gmail.com on 16 Mar 2010 at 7:28

[GoogleCodeExporter]

presume verified

Original comment by gfor...@gmail.com on 20 Mar 2010 at 3:20

• Changed state: Verified