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

[ENH] handle bagel files that contain data coming from several datasets #58

Open
1 task done
Remi-Gau opened this issue Jun 2, 2023 · 4 comments
Open
1 task done
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again

Comments

@Remi-Gau
Copy link
Contributor

Remi-Gau commented Jun 2, 2023

Is there an existing issue for this?

  • I have searched the existing issues

New feature

I am thinking to automatically generate a bagel.csv file when using the cohort_creator.
But as this one combines data from several datasets, it may be useful to allow for an optional column that contains the dataset name and to allow filterting with this column.

In practice this may mean that records would be a unique for a dataset / sub / ses combination and not just for a sub / ses combination.

Unclear documentation

No response

@Remi-Gau
Copy link
Contributor Author

Remi-Gau commented Jun 4, 2023

adding an example of bagel.csv for this use case:

bagel.zip

@Remi-Gau
Copy link
Contributor Author

Remi-Gau commented Jun 4, 2023

adding one that leads to an error because of

Index contains duplicate entries, cannot reshape

bagel_duplicate_entries.zip

@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Aug 18, 2023
@github-actions
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days.
We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
Projects
Status: No status
Development

No branches or pull requests

1 participant