[Users] CactusIO::IOJpeg standard vs. remove mode / output format

Ole Weidner oweidner at cct.lsu.edu
Mon Dec 3 14:24:36 CST 2007


Aloha,

I'm using the IOJpeg thorn for continuous output slice generation for  
an oceanographic model recently "ported" to cactus. The jpeg files are  
used to create an mpeg4 movie once the simulation is done.
Since I'm also using the HTTPD thorn for monitoring/steering, I'm  
wondering if there's a rationale behind the fact that the IOJpeg thorn  
doesn't generate the single "remove-mode"-style advertised jpeg file  
that is used by the HTTPD thorn to provide a preview for the current  
time-step. I modified my local copy of the IOJpeg (dev) thorn to  
achieve this. Would it be in general interest to have a feature like  
this in the Cactus development CVS?

Another rather minor annoyance (IMHO;-) is the naming of the  
continuous output files: the scheme is varname_2D.it_timestep.jpeg  
which results in something like:

varname_2D.it_1.jpeg
varname_2D.it_2.jpeg
varname_2D.it_3.jpeg
...
varname_2D.it_10.jpeg
...

which makes a lexicographic ordering unnecessary difficult and usually  
(depending on the processing tool - in my case mencoder) requires an  
additional sorting step. Would it make sense to prepend a couple of  
zeros to the format string (Write.c)? Like:

sprintf (filename, "%s%s_%s.it_%08d.jpeg", myGH->out_dir, alias,  
slicename,
             GH->cctk_iteration);

instead of:

sprintf (filename, "%s%s_%s.it_%d.jpeg", myGH->out_dir, alias,  
slicename,
             GH->cctk_iteration);

Cheers,
Ole


More information about the Users mailing list