search

DUNE / dist-comp

Action items for DUNE distributed computing, and common scripts that are used.
2 stars 0 forks source link

Follow ISO-8601 for justIN-generated timestamps in filenames. #183

Open kherner opened 2 weeks ago

kherner commented 2 weeks ago

I saw a recent file from a tutorial run and it looks like timestamps get added to outputs of the form

YYYY-mm-ddT_HHMMSSZ.

The canonical ISO-8601 form for UTC is of course

YYYY-mm-ddTHH:MM:SSZ (or a space instead of the T)

But I doubt we want to be putting whitespace or colons in filenames. A valid alternate format is

YYYYmmddTHHMMSSZ

But justIN currently seems to be mixing in hyphens and then (inexplicably to me, at least) adding an underscore, which doesn't correspond with what's been used for far and doesn't seem to follow the usual timestamps standards (also not valid rfc-3339). I don't see any reason not to follow the convention. Also I doubt we need sub-second accuracy in the filenames.

Andrew-McNab-UK commented 2 weeks ago

Yes, this is one of the jobscripts the tutorial refers to, so it's easy to change. I think the timestamps originally came from test POMS workflows! I've changed it to the last format, and that will appear in the next minor release. Thanks!