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

making resume work...? #2

Open
BioinfoTongLI opened this issue Nov 9, 2023 · 3 comments
Open

making resume work...? #2

BioinfoTongLI opened this issue Nov 9, 2023 · 3 comments
Labels
question Further information is requested

Comments

@BioinfoTongLI
Copy link
Contributor

BioinfoTongLI commented Nov 9, 2023

Filed here:
https://github.com/embl-cba/ome-zarr-image-analysis-nextflow/issues/8

But let's continue the discussion here.
@krokicki @bugraoezdemir @sebgoti @tischi (somehow I cannot christian) @folterj

@tischi
Copy link
Contributor

tischi commented Nov 10, 2023

Thanks, @tischi is correct.

Due you think that resume would work without saving any file in the work dir?

@tischi tischi added the question Further information is requested label Nov 10, 2023
@BioinfoTongLI
Copy link
Contributor Author

Not for now. I am curiose what @krokicki's solution here. Do you use groovy scripting for resuming?

@krokicki
Copy link
Contributor

One way to make resume work here is to use process.cache = 'lenient' in the nextflow.config file. This ignores the changed date stamps on files and only checks to make sure the files are there and correct size.

I typically don't use resume because we haven't found a way to make it work with Spark/Dask clusters. Instead, I have a --skip parameter and just add the steps I want to skip. So --skip=blur,segment would skip the first two steps and just run morphometry. Since all the data is outside the work dir, this is effectively resuming the processing from a given point.

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

No branches or pull requests

3 participants