#1565: change default of IOUtil::out_save_parameters to true --------------------------+------------------------------------------------- Reporter: rhaas | Owner: Type: enhancement | Status: review Priority: optional | Milestone: Component: Cactus | Version: development version Resolution: | Keywords: --------------------------+-------------------------------------------------
Comment (by hinder):
Replying to [comment:7 eschnett]:
Thorn Formaline's design goal is to store sufficient information about
simulations to make them reproducible. Most people know that it stores the complete source code by default. It also stores all parameter values, as well as regular updates if parameters ares steered. It uses a simple "KEY=VALUE" format for this, but can also generate several other formats (XML, or submit to a web server in real-time so that simulation progress can be more easily observed).
I'd be happy to modify the output format to make it easier to parse.
I propose that you use the "ini" file format. It is easy to parse this in Python, and hence from a shell script:
{{{ #!/bin/bash
function read-key() { python -c "import ConfigParser; import sys; config = ConfigParser.ConfigParser(); config.read(sys.argv[1]); print config.get(sys.argv[2],sys.argv[3])" "$1" "$2" "$3" }
function read-sections() { python -c "import ConfigParser; import sys; config = ConfigParser.ConfigParser(); config.read(sys.argv[1]) for s in config.sections(): print s" "$1" }
read_sections "file.ini" read_key "file.ini" "sectionname" "keyname"
}}}
It is a (relatively) standard format, and there should be similar libraries for whatever analysis framework one might be using. We might have to tweak things like quoting and multi-element values to work with different readers, but I think this is still preferable to using a new format.