feat: updated Nextflow workflows with profiles, auto-assess, rehoming#108
Open
FIrgolitsch wants to merge 2 commits into
Open
feat: updated Nextflow workflows with profiles, auto-assess, rehoming#108FIrgolitsch wants to merge 2 commits into
FIrgolitsch wants to merge 2 commits into
Conversation
This was referenced Apr 28, 2026
a3a7b86 to
c19c4d7
Compare
3487c56 to
74f3e60
Compare
This was referenced Apr 30, 2026
c19c4d7 to
5e7482c
Compare
FIrgolitsch
added a commit
that referenced
this pull request
Apr 30, 2026
74f3e60 to
6c5ef92
Compare
5e7482c to
d47cbd7
Compare
FIrgolitsch
added a commit
that referenced
this pull request
Apr 30, 2026
6c5ef92 to
2d467fc
Compare
d47cbd7 to
31f7811
Compare
FIrgolitsch
added a commit
that referenced
this pull request
Apr 30, 2026
2d467fc to
cbafa1b
Compare
This was referenced May 1, 2026
Two fixes that together stop temp zarrs from filling /tmp: 1. Default dir from None (=> tempfile.gettempdir() => /tmp) to '.' (CWD, typically the Nextflow task work dir). Even if the temp dir leaks, it's reclaimed when the work dir is cleaned, and never lands on small /tmp partitions. 2. Replace TemporaryDirectory(...).name (which discards the cleanup handle the moment .name is read; cleanup then depends on a fragile weakref finalizer that doesn't run on SIGKILL) with mkdtemp() plus atexit.register(shutil.rmtree, ..., ignore_errors=True). atexit fires on normal interpreter shutdown regardless of which file handles zarr still holds open. Symptom: 14 stale tmp*.zarr dirs (~5 GB) in /tmp on the lab server, contributing to ENOSPC on /tmp during reconstruction.
31f7811 to
1e8a7d1
Compare
cbafa1b to
375b146
Compare
This was referenced May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #108 — Updated Nextflow Workflows (profiles, auto-assess, rehoming)
Replaces the accidentally-merged-then-reverted #102. Modernises the Nextflow workflows to consume the new library and script outputs from #97–#101.
Workflow changes
local,beluga,dockerexecutionlinum_assess_slice_quality.py)linum_detect_rehoming.py)linum_stitch_3d_refined.py)linum_align_to_ras.py)Nextflow v26 strict-DSL compatibility
The follow-up commit
fix(workflows): make Nextflow v26 strict-DSL compatibleensures the workflow runs cleanly under Nextflow ≥ 26.04 (still compatible with the declared>= 23.10minimum):getAvailableCpus()into thebeforeScriptclosure (top-leveldefno longer allowed in v26 config DSL)(int)(...)casts withas int(v26 parses the C-style form as a method call)publishDirpaths that reference$task.*in closures (lazy eval is now required)nextflow lintclean on bothreconst_3dandpreprocpipelines under Nextflow 26.04.0Streamline + extract refactor (lives downstream on #110)
The configs are further streamlined on #110 (
refactor(workflows): streamline configs, extract cpu_limits.config and Helpers.groovy) — kept there because it depends on thecorrect_bias_fieldprocess introduced by #109. Reviewers reviewing the Nextflow stack should look at #108 first, then #109, then #110.