More of a question first, which may lead to a proposal later.
Is there a consensus on how to represent the concept of an age at session in the BIDS metadata hierarchy?
The context concerns longitudinal studies where imaging visits span a large period of time (several years typically), and the age at session is necessary for modeling disease progression.
On first read, I thought this attribute may go in sub-<label>_sessions.tsv#age which would override participants.tsv#age as per the inheritance rule. But that contradicts the rule in the sessions file section mandating the use of distinct attributes between participants and sessions tabular data.
A BIDS-compliant alternative could be to introduce an age_at_session attribute in the sessions file.
What are your thoughts?
More of a question first, which may lead to a proposal later.
Is there a consensus on how to represent the concept of an age at session in the BIDS metadata hierarchy?
The context concerns longitudinal studies where imaging visits span a large period of time (several years typically), and the age at session is necessary for modeling disease progression.
On first read, I thought this attribute may go in
sub-<label>_sessions.tsv#agewhich would overrideparticipants.tsv#ageas per the inheritance rule. But that contradicts the rule in the sessions file section mandating the use of distinct attributes between participants and sessions tabular data.A BIDS-compliant alternative could be to introduce an
age_at_sessionattribute in the sessions file.What are your thoughts?