fix(qpx): emit dataset as qpx_output/* files instead of a directory#39
Conversation
Emit the QPX Parquet dataset as individual files (`qpx_output/*`) rather than the `qpx_output/` directory. This lets downstream pipelines publish the dataset files flat (e.g. into a single `qpx/` results folder alongside the `.h5mu`) via a `publishDir` saveAs, instead of being forced to keep an intermediate `qpx_output/` subdirectory. The stub still produces a single `qpx_output/stub.parquet`, so the existing stub test (qpx_dataset.size() == 1) is unaffected.
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR refines the QPX module's output specification by changing the ChangesQPX output specification refinement
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Up to standards ✅🟢 Issues
|
…older) Publish the QPX Parquet dataset files and the .h5mu MuData file directly under results/qpx/, removing the intermediate qpx/qpx_output/ level. - modules/bigbio/qpx: emit the dataset as qpx_output/* files instead of the qpx_output/ directory (mirrors bigbio/nf-modules#39), so publishDir can flatten the files. A directory output and the sibling .h5mu race in publishDir and one is dropped, so flattening config-only is not reliable. - conf/modules/shared.config: QPX_EXPORT publishDir now strips the qpx_output/ prefix via saveAs (tokenize('/').last()) and publishes to qpx/. Pin bump for modules.json follows once bigbio/nf-modules#39 lands on main. Docs (output.md, usage.md) already describe the flat results/qpx/ layout.
Update modules.json qpx git_sha to the merge commit of bigbio/nf-modules#39, which emits the QPX dataset as qpx_output/* files. Keeps nf-core check_local_copy green for the flattened output change.
What
Change the
qpx_datasetoutput of thebigbio/qpxmodule from theqpx_output/directory to the files it contains (qpx_output/*).Why
Emitting a directory forces downstream pipelines to publish the QPX Parquet dataset under an intermediate
qpx_output/subfolder. With a NextflowpublishDir, a directory output and a sibling file output (the.h5mu) targeting the same results folder race against each other and one is silently dropped — so the dataset cannot be flattened into a single results folder reliably.Emitting
qpx_output/*lets consumers publish the dataset files flat (e.g. directly intoqpx/next to<prefix>.h5mu) via asaveAsthat strips theqpx_output/prefix.Compatibility
mudataandversionsoutputs are unchanged.qpx_output/stub.parquet, so the stub test (qpx_dataset.size() == 1) still holds (a glob with multiple matches is emitted as one list).meta.ymlupdated to describe the output as files.Consumed by bigbio/quantmsdiann to flatten QPX export results into a single
qpx/folder.Summary by CodeRabbit