Skip to content

filter out containers from paramsSummaryLog #194

Description

@mashehu

With the upcoming seqera container conversion in nf-core, we will get a lot of container entries in the paramsSummaryLog, e.g.

Core Nextflow options
  runName                                : furious_shaw
  container.COLLECT_RESULTS              : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.CONSOLIDATE_RESULTS          : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.CV_SPLIT                     : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.EVALUATE_FINAL               : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.EVALUATE_FIND_MAX            : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.FINAL_SPLIT                  : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.FIT_CURVES                   : community.wave.seqera.io/library/python_pip_curve_curator:3b584472647bda92
  container.HPAM_SPLIT                   : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.LOAD_RESPONSE                : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.MAKE_MODEL_CHANNEL           : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.POSTPROCESS_CURVECURATOR_DATA: community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.PREDICT_FULL                 : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.PREPROCESS_RAW_VIABILITY     : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.RANDOMIZATION_SPLIT          : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.RANDOMIZATION_TEST           : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.ROBUSTNESS_TEST              : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.TRAIN_AND_PREDICT_CV         : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.TRAIN_FINAL_MODEL            : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.TUNE_FINAL_MODEL             : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680
  container.UNZIP                        : community.wave.seqera.io/library/p7zip:16.02--94efedc6cfea7db9
  container.VISUALIZE_RESULTS            : community.wave.seqera.io/library/python_pip_drevalpy:af9bf54ab78b9680

(taken from our POC in nf-core/drugresponseeval#80)
this pipeline is a special case with many reused containers, but I still think this will be quite wordy for pipelines with many modules.
Is there a way to quickly removing them from paramsSummaryLog? Or do we need to write a specific prettyPrint function for that?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions