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

--replace flag, check if bidsmreye output has been produced already and skip processing of files that already have data [ENH] #168

Closed
1 task done
Michael-Sun opened this issue Sep 18, 2023 · 4 comments · Fixed by #216
Labels
enhancement New feature or request
Milestone

Comments

@Michael-Sun
Copy link

Michael-Sun commented Sep 18, 2023

Is there an existing issue for this?

  • I have searched the existing issues

New feature

Running bidsmreye on a cluster compute gpu node can run into issues if the process gets killed because of memory errors, timeout, or other miscellaneous issues (e.g., administration-level malicious code detection wrongly kills your process). It would be good if bidsmreye can pick up where it left off instead of starting processing all over again.

Unclear documentation

No response

@Remi-Gau
Copy link
Contributor

yeah I was thinking of possibly using a proper workflow manager for this.
nipype / pydra or bidsnake?

this may not happen fast but it would be useful to have

@Remi-Gau
Copy link
Contributor

for now I may make the default behavior to reuse pre-existing files and pass a --force flag to overwrite previous results

@Remi-Gau Remi-Gau added the enhancement New feature or request label Sep 18, 2023
@Remi-Gau
Copy link
Contributor

Not sure if you are using it. But splitting the processing by running one action at a time may help a bit as well.

https://bidsmreye.readthedocs.io/en/latest/usage_notes.html#named-arguments

@Remi-Gau
Copy link
Contributor

Remi-Gau commented Aug 5, 2024

for now I may make the default behavior to reuse pre-existing files and pass a --force flag to overwrite previous results

files that already have an output should now be skipped unless the --force argument is passed in the CLI

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

Successfully merging a pull request may close this issue.

2 participants