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

Input from Marco Cattaneo #11

Open
petitcactusorange opened this issue Oct 14, 2015 · 1 comment
Open

Input from Marco Cattaneo #11

petitcactusorange opened this issue Oct 14, 2015 · 1 comment

Comments

@petitcactusorange
Copy link

  • Dataset content: is the TurboDST idea the right direction, how do we deal with global event data (e.g. isolation variables), how do we ensure independence of stripping line outputs etc.
  • How do people interact with the event model objects: role and evolution of LoKi, Turbo/MDST vs. NTuples, role of ROOT (what are the use cases for directly accessing our event data interactively from with Root?)
  • Is it still necessary to have an XML description of our event classes (à la GaudiObjDesc), what are the use cases?
@petitcactusorange petitcactusorange changed the title Input from Marco Input from Marco Cattaneo Oct 14, 2015
@petitcactusorange
Copy link
Author

Chat with Roel.
FSR, more generally a collection of not event level information :

  • Luminosity.
  • MC stats.
  • Production information (DB tags)
    need a review.

Roel will contact ROOT people to discuss their plan of allowing asynchronous writing of trees.

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

No branches or pull requests

1 participant