search

xpdAcq / mission-control

Releases, Installers, Specs, and more!
0 stars 4 forks source link

timestamps in filenames are different. #173

Open MehmetTopsakal opened 5 years ago

MehmetTopsakal commented 5 years ago

timestamps in filenames are different.

Expected Behavior

Timestamp in all files should be the same.

Current Behavior

From our recent beamtime (measured ~300 samples), I realized that timestamps on files generated are a few seconds different.

An example is here: /tiff_base/LaB6_disc/dark_sub/LaB6_disc_20190307-090406_acb844_0001_dark_corrected_img.tiff /tiff_base/LaB6_disc/integration/LaB6_disc_20190307-090404_acb844_0001_mean_tth.chi /tiff_base/LaB6_disc/mask/LaB6_disc_20190307-090404_acb844_0001_mask.npy /tiff_base/LaB6_disc/meta/LaB6_disc_20190307-090403_acb844.yaml

I have seen this on many other runs.

CJ-Wright commented 5 years ago

When was this data taken? Those are the timestamps of the analysis. If you want I can reprocess the data with the timestamps of the start document.

CJ-Wright commented 5 years ago

(also which beamline was this?)

MehmetTopsakal commented 5 years ago

@CJ-Wright

The date is seen on the filenames: "20190307" We used workstation#2 of XPD.

For me, this is not a big problem. I can reprocess the data with the timestamps of the start document.

CJ-Wright commented 5 years ago

Ok, I think this will be fixed in a new release which should be deployed soon (the DAMA group is doing a deployment so this should be part of that)