Closed rhodesch closed 9 months ago
Hi @rhodesch Thanks for reaching out!
To answer your questions:
main
branch contains the source code only. This source code needs to be build into the nextflow and docker artifacts which can be used to actually run the pipeline. These can be found on main_build
. However, the main_build
branch is the development branch for this project, and changes constantly. If you would like to use a stable release, I would suggest that you use one of the tags, like 0.9.0
.Let me know how it goes! Dries
Hi @rhodesch I am going to close this issue because it has become inactive. Please reopen if you feel it is necessary
For setting up pipelines on nextflow tower, can you confirm I am adding a pipeline properly? As an example, I am trying to add Cell Ranger mapping (cellranger count) pipeline from the Ingestion workflow, using google life science as a compute environment platform:
Go to
Launchpad
, thenAdd pipeline
Name:
pipeline_name
Pipeline to launch:https://github.com/openpipelines-bio/openpipeline
Revision number:main_build
<-- Is this correct? Or usemain
branch? Config profiles:target/nextflow/mapping/cellranger_count/nextflow.config
<-- Is this needed? I've seen examples where this appears to be omitted. Main script:target/nextflow/mapping/cellranger_count/main.nf
Schema name:target/nextflow/mapping/cellranger_count/nextflow_schema.json
Head Job CPUs:2
<-- Pipeline doesn't appear to build properly (dropdown not rendered upon run launch without numeric value) Head Job memory:256
<-- Pipeline doesn't appear to build properly (dropdown not rendered upon run launch without numeric value)Any suggestions or reproducible examples would be greatly appreciated. Thanks in advance