[Developers] cactus feature request: source code saves

[Erik Schnetter]

On Sunday 22 May 2005 13:28, Denis Pollney wrote:
> Hi,
> I had some discussion with frank and erik yesterday regarding the
> reproducability of runs. We often introduce small changes to the code
> we're running in our local directories without commiting them to CVS,
> since we're just trying something out. We then might later use the
> same source tree, forgetting that it is slightly modified.
>
> Ideally each run output directory should have a copy of the source
> code that was used to produce the output.

We just checked, and it turns out that a copy of all thorns uses only 
about 20 MB, which is definitely feasible for any production run.

I would suggest to put the source code together with the other meta 
information (parameter file etc.) into a central storage location so 
that this information is not "accidentally" deleted when the output 
directory is removed.  The meta information should contain a unique ID 
for this run, and this ID should be present in all output files as 
well, so that it is always possible to find out where a file came from.

We are currently thinking how to reduce the 20 MB further when there are 
many copies of the source code stored; this should be easily possible, 
because the source files will be mostly identical.

-erik

-- 
Erik Schnetter <schnetter at aei.mpg.de>   http://www.aei.mpg.de/~eschnett/

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: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.cactuscode.org/pipermail/developers/attachments/20050524/b3c44dae/attachment-0002.bin