8000 Q: Nipypecli crash utility in pydra · Issue #149 · nipype/pydra · GitHub
[go: up one dir, main page]
Skip to content

< 8000 bdi class="js-issue-title markdown-title">Q: Nipypecli crash utility in pydra #149

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.

Sign up for GitHub

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

Jump to bottom
Open
adswa opened this issue Sep 5, 2019 · 3 comments
Open

Q: Nipypecli crash utility in pydra #149

adswa opened this issue Sep 5, 2019 · 3 comments
Assignees
@djarecka
Labels
feature Feature requests

Comments

@adswa
Copy link
adswa commented Sep 5, 2019

@djarecka and I talked about this briefly at the INCF and she asked me to make an issue out of it: Will there be (something like) the nipypecli crash utility in Pydra?
(this is not an urgent question, just making a note as promised)
@adswa adswa added the question Further information is requested label Sep 5, 2019
@effigies effigies added the enhancement New feature or request label Sep 5, 2019
@effigies
Copy link
Contributor
effigies commented Sep 5, 2019

There definitely should be, IMO.

@satra
Copy link
Contributor
satra commented Sep 5, 2019

the complexities of such a tool are a bit more in pydra, such as tasks/workflows running in containers, but in general there will be a cli (for various reasons), and nipype 2.0 will have it's own cli to be more specific to the neuroimaging use cases.

@tclose tclose moved this to Proposed in Pydra Roadmap Apr 1, 2025
@tclose tclose added the to consider suggesting changes that require more discussion label Apr 1, 2025
@tclose tclose removed the to consider suggesting changes that require more discussion label Apr 10, 2025
@tclose tclose added feature Feature requests and removed enhancement New feature or request question Further information is requested labels Apr 29, 2025
@tclose tclose moved this from Proposed to temp in Pydra Roadmap Apr 29, 2025
@tclose tclose moved this from temp to To do (v1.0) in Pydra Roadmap Apr 29, 2025
@tclose tclose moved this from Triage to v1.0 in Pydra Roadmap May 19, 2025
@tclose
Copy link
Contributor
tclose commented May 19, 2025

Since the run-cache now gets created /Users/<user>/Library/Caches/pydra/1.0a1/run-cache by default (by platformdirs on Mac, will be different on Windows and Linux), (need separate issue about versioning caches), we could specify a directory called /Users/<user>/Library/Caches/pydra/1.0a1/runs (or similar), which contains timestamped symlinks to the top-level cache directory that was submitted, e.g. /Users/<user>/Library/Caches/pydra/1.0a1/runs/20250520065430, which the last run could be picked up when a specific cache directory isn't specified by pydra crash

@effigies effigies mentioned this issue May 19, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@djarecka djarecka

Labels
feature Feature requests
Projects
Pydra Roadmap
Status: v1.0
Milestone
No milestone
Development

No branches or pull requests
5 participants
@effigies @satra @tclose @djarecka @adswa
0