You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do we want to share task that belong to a battery?
This issue involves tasks such as CamCAN (EmoMem, EmoReco, Catell, ...), Aomic (Harriri, WM, Stroop, ...), Preferences, and so on. These are groups of tasks that come all from a battery but in the documentation and in the files, they are reported as individual tasks, and then in the text we make the clarification that they belong to a battery.
The issue is that here in public_protocols we are so far grouping them in batteries, i.e. Aomic folder and inside we go into the separation. I would like to change this and have separated folders, as we treat them as individual tasks, which would result into, for example, 4 folders: HarririAomic, StroopAomic, etc... insted. @bthirion
The text was updated successfully, but these errors were encountered:
Thank you for the discussion !
Well, if you consider downstream tasks (e.g. re-using the output of IBC for cognitive mapping), the battery aspect is not meaningful.
Second, it is not meaningful either if you think in terms of BIDS organization (the "battery" level does not exist --- and it is probably not needed).
To me, public_protocols is there for another reason: make it possible to reproduce / re-run IBC analyses on more people; but I guess that the battery structure is a bit more useful here, because when it comes to undertaking new acquisitions/experiments each battery has its own logic and it has to be understood.
Overall, I'm happy with the current organization and I don't think it could create confusion --- but this is open to discussion.
For me, the issue comes when a user is looking at the documentation or for example, a poster where we present some maps for a task that it's part of a battery, so they come to public_protocols and they don't see the task at a first glance. On the other hand, I've been working on having a small github icon on the implementation tab where we can put a link to each task dir on the repo, so maybe with that it will be bullet proof.
How do we want to share task that belong to a battery?
This issue involves tasks such as
CamCAN
(EmoMem, EmoReco, Catell, ...),Aomic
(Harriri, WM, Stroop, ...),Preferences
, and so on. These are groups of tasks that come all from a battery but in the documentation and in the files, they are reported as individual tasks, and then in the text we make the clarification that they belong to a battery.The issue is that here in
public_protocols
we are so far grouping them in batteries, i.e.Aomic folder
and inside we go into the separation. I would like to change this and have separated folders, as we treat them as individual tasks, which would result into, for example, 4 folders:HarririAomic
,StroopAomic
, etc... insted.@bthirion
The text was updated successfully, but these errors were encountered: