Skip to content

Specifying non-standard rule-specific cluster resource settings #25

@kpj

Description

@kpj

Hello,

In order to specify e.g. a time limit (which can be needed to select an appropriate queue) for a certain rule, one needs to create lsf.yaml (see also #7 and #13). This file needs to be in the working directory of the pipeline.

This can be difficult/slightly annoying to handle when lsf.yaml needs to be moved manually to the correct working directory before executing the pipeline is possible.

Is there a better way of doing this that I am missing?
Or asked differently, what is the difference between standard and non-standard resources?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions