-
Notifications
You must be signed in to change notification settings - Fork 272
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
Store event-wise pointing at least for MC #1484
Comments
what is |
yes, sorry. fixed. |
yes, at least adding an obs_id I think is useful. Eventwise pointing could be done too, but it's really overkill to have the pointing position per event when it changes on a much slower rate (once per second + interpolation to the event time is usually enough). So far simulations only have fixed alt/az - we will have to consider something better when and if we do ra/dec simulations. I had always assumed we'd just have a function that just provides event_wise pointing based on the monitoring data, like a |
I think we should optionally enable storing
dl1/event/telescope/pointing
withTelEventIndex
at least for simulations sincethe timestamp based approach will not work for mcs since they are produced in parallel.
Alternatively, we should atleast include an
obs_id
in the monitoring table.This will create problems when merging files that do not only contain a single pointing position.
The text was updated successfully, but these errors were encountered: