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

Duplicate subject, bug with selected anatomical files #758

Open
Moo-Marc opened this issue Jan 13, 2025 · 1 comment
Open

Duplicate subject, bug with selected anatomical files #758

Moo-Marc opened this issue Jan 13, 2025 · 1 comment

Comments

@Moo-Marc
Copy link
Collaborator

Hi team!

When duplicating a subject (right click on subject > file > duplicate subject), Bst gets confused as to which file is selected for each type of anatomy and surfaces.

In my case, I had two MRIs and two head surfaces, and for each of these file types, the second file to be created or imported was selected. After duplicating the subject, on the copy it still shows the same selected items, but this is at least partly incorrect. If I reload the subject or protocol, it updates the selection to the first anatomy or surface files. And running other things before reloading produces unexpected things.

I was able to reproduce this on another more typical subject with one MRI, one head surface, and multiple cortical surfaces. After duplicating and reloading, the selected cortical surface changed.

The main issue is not so much that the selection changes when duplicating, but that the displayed selection is incorrect for the duplicate subject until reloading.

If there's no time to investigate this right away, a quick partial fix would be to force reloading the duplicated subject after it's created. This would at least correctly display the selected items, even though they could change.

@chinmaychinara91
Copy link
Collaborator

@Moo-Marc I was able to reproduce the issue at my end. Thank you for reporting this. I will have a look at it as soon as I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants