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

uploaded predictor persists in cloned analysis bundle even if removed [bug report] #1048

Open
jsmentch opened this issue Apr 19, 2022 · 0 comments
Assignees
Labels

Comments

@jsmentch
Copy link
Contributor

(using the web interface)

I am seeing some odd behavior where if I clone an analysis with a custom predictor that I uploaded, this feature will persist in the cloned analyses even if it is unselected, like a "ghost predictor". For example:

  • as a test: rq2o2 was cloned from another analysis, say b758b. I then removed all predictors and only added one 'face' predictor and submitted this analysis. You can see that 'speech_edited' custom feature is still listed as a predictor in this new analysis that should just have 'face'. Interestingly, 'speech_edited' is not included in the bids stats model but it is downloaded in the bundle.

  • another example is npqie. I ran an older analysis with a 'speech_edited' custom predictor, then I re-uploaded an updated 'speech_edited' custom predictor and then cloned the older analysis to create npqie and tweaked it to how I wanted it. You can see though that 'speech_edited' is listed twice under the list of features, but only the new version is downloaded in the bundle and only one is in the BIDS stats model.

may be specific to my unique case of uploading a feature, creating an analysis, re-uploading a feature of the same name, then cloning the analysis that has this out of date feature?

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

No branches or pull requests

3 participants