Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full metadata in output #5

Open
hansenjo opened this issue Sep 26, 2013 · 2 comments
Open

Full metadata in output #5

hansenjo opened this issue Sep 26, 2013 · 2 comments

Comments

@hansenjo
Copy link
Member

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
Copy link
Member Author

hansenjo commented Nov 10, 2013

Some ideas as to what specific metadata to include:

  • Analyzer version (version & git commit)
  • Actual ROOT version loaded at run time
  • EVIO version loaded at run time
  • Build time, host, compiler, user, directory
  • Build flags (CXXFLAGS, others?)
  • Replay time, host, user, work dir
  • Analyzer flags configured (scalers, helicity)
  • Analyzer class, decoder class
  • Database type, URL (DB_DIR, SQL host, etc.)
  • All database keys & values loaded, load times
  • Replay script? Copy of source?
  • Output & cut definition files (full copies)
  • All output definitions
  • Full paths of input & output file(s)

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
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant