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

Print out intial timestamps and counters in nsec instead of seconds #565

Closed
morcuended opened this issue Nov 16, 2020 · 3 comments
Closed
Assignees

Comments

@morcuended
Copy link
Member

Since r0_to_dl1 uses timestamps and the corresponding counters in nsec (integers) as input, we should print out those same values in nsecs instead of seconds to avoid confusion.

@morcuended morcuended self-assigned this Nov 16, 2020
@morcuended
Copy link
Member Author

This is how it currently looks:

Using first event as time reference for counters, this will lead to wrong timestamps / trigger types for all but the first subrun
Using first event as time reference for dragon. UCTS timestamp: 1582059789516171575 dragon_counter: 2516171300
Using first event as time reference for TIB. UCTS timestamp: 1582059789516171575 tib_counter: 2516170900

@maxnoe
Copy link
Member

maxnoe commented Mar 1, 2021

This is now in ctapipe_io_lst, where a log.critical message has the timestamp values in ns.

However, I think we probably should make a dedicated tool to produce these night summary files, right?

@morcuended
Copy link
Member Author

Closing this. Run summaries are produced now with the script made in #614.

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

2 participants