-
Notifications
You must be signed in to change notification settings - Fork 7
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
Lookup table to generate FileKey
Database
#79
Conversation
…aving outputs on disk in a save_tier
…cesses writing a validity at the same time
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #79 +/- ##
==========================================
+ Coverage 39.05% 41.76% +2.70%
==========================================
Files 27 26 -1
Lines 1987 1942 -45
==========================================
+ Hits 776 811 +35
+ Misses 1211 1131 -80 ☔ View full report in Codecov by Sentry. |
The introduction of |
The last commit (setting |
99d3264
to
eb308e1
Compare
Thanks, this looks good from my side now |
eb308e1
to
5ebcc64
Compare
I cleaned up the commit history a bit (stashing the fixes into the initial commits and omitting the merge commits) |
c9aeb28
to
8b63b60
Compare
This PR includes look-up functionality to generate a
FileKey
database. The database can be generated with:To search for a
FileKey
a LEGEND timestamp belongs to, you can use thefind_filekey
function.For convenience, plot recipes have been added to plot a specific timestamp, either from
phy
or fromcal
data.