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.

Sign up for GitHub

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

[FIX] Clarify that acq_time in scans.json refers to first data point acquired #506

Merged
merged 3 commits into from
Jul 17, 2020
Merged

[FIX] Clarify that acq_time in scans.json refers to first data point acquired #506

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
590363b
Clarify that acquisition time corresponds to start of acquisition.
tsalo Jun 19, 2020
c36a92a
Merge branch 'master' into doc/acq-time
tsalo Jul 7, 2020
6ed459b
Change "SHOULD correspond" to "refers".
tsalo Jul 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion src/03-modality-agnostic-files.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -336,12 +336,14 @@ imaging acquisition sequence (each run `.nii[.gz]` file) within one session.
Each `.nii[.gz]` file should be described by at most one row.
Relative paths to files should be used under a compulsory `filename` header.
If acquisition time is included it should be under `acq_time` header.
Acquisition time SHOULD correspond to when the first data point in each run
was acquired.
Datetime should be expressed in the following format
`2009-06-15T13:45:30[.000000]` (year, month, day, hour (24h), minute, second,
and optionally fractional second; this is equivalent to the RFC3339 "date-time"
format, time zone is always assumed as local time).
No specific precision is required for fractional seconds, but the precision
SHOULD be consistent across the dataset
SHOULD be consistent across the dataset.
For anonymization purposes all dates within one subject should be shifted by a
randomly chosen (but consistent across all runs etc.) number of days.
This way relative timing would be preserved, but chances of identifying a
Expand Down