Sanitize cal_tools.tools.get_creation_date
1 unresolved thread
1 unresolved thread
Compare changes
Files
2+ 34
− 22
@@ -2,8 +2,9 @@ from collections import OrderedDict
@@ -2,8 +2,9 @@ from collections import OrderedDict
@@ -11,6 +12,7 @@ from typing import Optional
@@ -11,6 +12,7 @@ from typing import Optional
@@ -229,47 +231,57 @@ def get_run_info(proposal, run):
@@ -229,47 +231,57 @@ def get_run_info(proposal, run):
@@ -280,7 +292,7 @@ def save_const_to_h5(device, constant, condition, data,
@@ -280,7 +292,7 @@ def save_const_to_h5(device, constant, condition, data,
this use
MetadataClient
. Do we also havebegin_at
information somewhere in metadata of the run? We could then simply useextra_data
we have begin_at in the metadata saved at myMDC, yes.
But this part only works in production as communication with MetadataClient needs the secrets written in the webservice yaml configurations.
How?
the new HDF5 files (since ~February) have a few more metadata, they maybe contain all required information?
example:
so this would have the same
creationDate
asMetadataClient
or it just shows last time the file was modified?Oh, I didn't know that. That is very useful.
I'd expect the
creationDate
field to match the information from the metadata, but I'd check before :DIs there an
extra_data
way to retrieve it, or is using h5py directly okay?EXtra-data doesn't read these yet (it's on the todo list :) so h5py would be the way to go at the moment
Ok, I'm cool to use the
creationDate
from the files, but there will still be a loop, as not all files are created at once:Just to link things up, here's the issue for this in EXtra-data: https://github.com/European-XFEL/EXtra-data/issues/27
It's also partly stuck on a similar question: how do we efficiently present metadata in 200 separate files as metadata for a run?