# How to adapt institutional Nextflow pipelines to Include a GUI for parameters

**URL:** <https://community.seqera.io/t/how-to-adapt-institutional-nextflow-pipelines-to-include-a-gui-for-parameters/1183>\
**Category:** Ask for help\
**Created:** [September 11, 2024, 2:51pm UTC](https://community.seqera.io/t/how-to-adapt-institutional-nextflow-pipelines-to-include-a-gui-for-parameters/1183 "2024-09-11T14:51:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![geek](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/geek/32/1064_2.png) [@geek](https://community.seqera.io/u/geek)\
**Post date:** [September 11, 2024, 2:51pm UTC](https://community.seqera.io/t/how-to-adapt-institutional-nextflow-pipelines-to-include-a-gui-for-parameters/1183/1 "2024-09-11T14:51:20Z")

</div>

Hi all,  
Many Nextflow pipelines are not fully compatible with the Seqera platform. By “fully compatible” I mean that when adding one of these pipelines to Seqera and clicking “launch” there is no page to specify inputs, outputs, or other parameters. Some of these pipelines are designed by institutions that actively use dedicated HPC systems.  
I would like to understand how to make these pipelines compatible with the platform. What steps and considerations should be kept in mind for this process?

To explore this in a real case, I think the following example would be useful for discussion: [GitHub - bioinfo-pf-curie/ChIP-seq: Nextflow pipeline for ChIP-seq data quality controls and analysis](https://github.com/bioinfo-pf-curie/ChIP-seq)

---

<div class="post-metadata">

**Author:** ![kenibrewer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/kenibrewer/32/963_2.png) [@kenibrewer](https://community.seqera.io/u/kenibrewer)\
**Post date:** [September 11, 2024, 3:58pm UTC](https://community.seqera.io/t/how-to-adapt-institutional-nextflow-pipelines-to-include-a-gui-for-parameters/1183/2 "2024-09-11T15:58:05Z")

</div>

Hi The Geek!

My first recommendation would probably be to see if there is a different pipeline that is already Seqera compatible. You can start by looking at [Seqera Pipelines](https://seqera.io/pipelines/chipseq--nf-core/) which is a curated list of pipelines (both nf-core and not) that meet standards for being portable and deployable to any infrastructure. From searching in that list, you can see that [nf-core/chipseq](https://seqera.io/pipelines/chipseq--nf-core/) also exists might meet your needs for this type of data anlysis.

If you can’t find an alternative pipeline that in nf-core or Seqera pipelines, then you’ll have to go through the process of manually verifying if the pipeline was written to be portable by testing it on your infrastructure. Sometimes pipelines are written with a lot of hard-coded variables and things specific to their infrasturcture and you won’t find those until you test it out.

Once you confirm that the pipeline runs, you can very easily generate the `nextflow-schema.json` file that Seqera Platform uses to generate the beautiful launchpad interface. Easiest way to do that is with the nf-core cli and the command `nf-core schema build`. See these [docs](https://nf-co.re/docs/nf-core-tools/pipelines/schema) for details.

Happy sciencing!

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/system/32/2402_2.png) [@system](https://community.seqera.io/u/system)\
**Post date:** [September 18, 2024, 3:58pm UTC](https://community.seqera.io/t/how-to-adapt-institutional-nextflow-pipelines-to-include-a-gui-for-parameters/1183/3 "2024-09-18T15:58:45Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.