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

Timezone handling across elements #57

Open
kabilar opened this issue Oct 11, 2022 · 0 comments
Open

Timezone handling across elements #57

kabilar opened this issue Oct 11, 2022 · 0 comments

Comments

@kabilar
Copy link
Collaborator

kabilar commented Oct 11, 2022

Manually moved from datajoint/datajoint-elements#63:

NWB exports require time information as UTC with timezone offset as ISO 8601 extended formatted strings (docs and original discussion).

Our current approach in the elements is to ask the user to provide datetime information in UTC and assume local time zone when importing. This introduces inaccuracies if the local offset has changed since time of recording (e.g., daylight savings), or the user performing the export is in a different location from data collection. Modalities will differ in how they record metadata, so we may also encounter issues combining our session UTC with modality-specific recording start times.

I propose (a) adding timezone offset to session.Session and (b) treating modality-specific timestamps as encoded with this offset. This will permit analyses within DataJoint to consider local time, but will require NWB export functions to remove the offset from all modality-specific tables.

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

1 participant