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

How to share #4

Open
ferponcem opened this issue Nov 10, 2023 · 2 comments
Open

How to share #4

ferponcem opened this issue Nov 10, 2023 · 2 comments

Comments

@ferponcem
Copy link
Collaborator

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

@bthirion
Copy link
Member

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.

@ferponcem
Copy link
Collaborator Author

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.

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

2 participants