Re: Is it safe to have multiple jobs output epsilon.h5 into the same directory? Can the epsilon.h5 output be disabled?

Just posting an alternative to disabling epsilon.h5 output: adding a
filename prefix based on parameters:

You can change the name by setting the "filename-prefix"
variable.
ex:
(set! filename-prefix "fromH5-mesh_size_3-")

Then you can build filename prefixes based on parameters using
"string-append" and "number->string":
(define a 42)
(set! filename-prefix (string-append "foo" (number->string a)))


On 04/10/13 17:48, Mike Taverne wrote:
> Hi,
> 
> I'm running an MPB script multiple times in parallel, using different
> parameters, but always outputting in the same common directory (writing
> results to separate files).
> This means a single epsilon.h5 file gets written to by multiple jobs.
> 
> It seems to work fine so far, except for a few crashes, which I now
> attribute to this simultaneous writing.
> 
> Do MPB runs still use the epsilon.h5 file once it has been written or
> not? i.e. could one job affect the results of another one due to
> changing the epsilon.h5 file?
> 
> Otherwise, is there a way to disable the epsilon.h5 output or specify a
> different filename/directory?
> 
> Regards,
> Mike
>

_______________________________________________
mpb-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/mpb-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSy+xkAAoJEAsx6g3o8ssJrf0P/jIoPulPMmbkzncGoUUQmDV9
dR6/Uhgrf6zHfVoHsOuiONUL7AHwYl+ZA1fq4gpjIKecxX6RlXNS9P4PGWE6MXm1
aO4FHljn7+pr2kRFmHpvJjbD328IRNHePebHxckcxx5cE7FP1EDzTEc28fa0VsBr
uACWcMxWDG1BBXA4V+QCWgevB7q3ezv2DspIoSSxxNz4o9iODc4twTG6D77ldmGr
XJxM9UpIUBCsEilkgrC07d1zbNFOYW7zg/X4SYmM2lMNk/SCl8pPazzvlhb2h2xJ
iPINlRQ1qDg7qzHugt6JmDUupfuWxfqEQJtvxdWAxoBcvaTchKh6CDSgF1mvbeXd
fZm9PDBx/nYrATCVY9UHMlVx/sCdEBXcPp18qDxCBVlCApQkDgw5A9TufJ6H36KG
69fVO0Z2IY9sIxhQRY1OfBa72I6uZwMvjRUtiDmJCzCSTM9ysKzQlEsirgMV6QhM
vtK2b90k6D+AxFKxQLTGXgZ5q+HgmOWtcVeY0RsUX59sj148tz5LyMobF7boGz8B
ZksL7XmaArCFeYXiw4YCmXH+7CAxPSxD3+J1esHQrmWFaMnCmQI8WOSLZvvIE04Y
lJtnPpkmRzB1M5E6IyQxK3MeweEb4CuVu3WQsiV+P4tY4ivNejIbm7WUAO1Iu8nd
FICQEDKMvN7dpGapWW3B
=4gfB
-----END PGP SIGNATURE-----