JeffersonLab / analyzer

HallA C++ Analyzer
BSD 3-Clause "New" or "Revised" License
7 stars 54 forks source link

Full metadata in output #5

Open hansenjo opened 11 years ago

hansenjo commented 11 years ago

Write all available analysis metadata (replay time/host/directory, user, database keys loaded, etc.) to the ROOT output file to make data provenance as transparent as possible.

hansenjo commented 10 years ago

Some ideas as to what specific metadata to include:

This is just a brainstormed list. Some of the items may not be realistic to include, and I'm sure I'm forgetting quite a bit. Feel free to add/modify.

Also, THaRun should be improved to include more or more accurate information about the run data.

hansenjo commented 10 years ago

Add to this list: A map of variable name prefixes (like "L.s0") to the name of the class using the prefix (e.g. THaScintillator). With this map, one can tell the meaning of each variable without working through the details of the replay script. Admittedly, one still doesn't always know which exact detector is referenced (e.g.: what exactly are "L" and "s0" in this example?), but at least one then knows what code was used to calculate the values.