[Developers] Changing the output directory at run time

[Erik Schnetter]

On Apr 16, 2007, at 06:30:55, Thomas Radke wrote:

> Bela Szilagyi wrote:
>> I am always in favor of steerability.
>>
>> Question: would non-ASCII output files be closed in case the  
>> output file path
>> changes between two IO iterations?  If not, adding this feature  
>> could be
>> useful.
>
> Making IO::out_dir fully steerable is certainly doable but - for
> consistency - requires changes in all I/O thorns which share this I/O
> parameter. I'd rather limit necessary changes to individual thorns for
> now, making their own output/checkpoint directory parameters  
> steerable.
> One could start with CarpetIOHDF5 and CarpetIOASCII.
>
> Before implementing anything we should clearly define what should  
> happen
> when switching to a different output directory. HDF5 files will surely
> be created anew. What about existing ASCII output files, should they
> also be split or appended in the old outdir ? Would it suffice to make
> the checkpoint directory steerable ?

I think ASCII files should be created anew.  That is, the old part of  
the output will remain in the old output directory, and the new  
output will be in the new output directory.

The checkpoint directory is not that important, because checkpointing  
requires only a constant amount of space, since old checkpoint files  
are deleted.  As some ASCII output files are large, all output files  
should go into the new directory.  For consistency, all output should  
stay together.

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20070416/2ad89c68/attachment.bin