Skip to content

Conversation

@ggabernet
Copy link
Member

Update amulety modules: in amulety>=2.0 the command syntax and subcommands have changed and I updated the nf-core modules are accordingly.

@ggabernet ggabernet requested review from a team as code owners January 15, 2026 20:51
Copy link
Contributor

@Joon-Klaps Joon-Klaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some rules on deprecating modules. https://nf-co.re/docs/guidelines/components/module_deprecation

Think it might be better to make a amulety2? What do you think?

@ggabernet
Copy link
Member Author

Ah thanks, I wasn't aware of this. I don't think it's needed to use AMULETY2, since the deprecated commands are no longer available. Instead of deleting the old modules I will deprecate them.

@ggabernet ggabernet requested a review from Joon-Klaps January 16, 2026 18:13
@ggabernet
Copy link
Member Author

Hi @Joon-Klaps I've deprecated the old modules now instead of just removing them. Let me know if the PR now looks good to you when you have a minute

@ggabernet ggabernet requested review from maxulysse and removed request for maxulysse January 16, 2026 18:56
Copy link
Contributor

@Joon-Klaps Joon-Klaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor suggestions, everything else looks good to me!

Comment on lines +34 to +38
- chain:
type: string
description: |
The chain to use for the embeddings. Can be either 'H' (high diversity chain: BCR heavy or TCR beta or delta),
'L' (low diversity chain: BCR light or TCR alpha or gamma) or 'HL' (BCR heavy + light, and TCR alpha + beta or gamma + delta).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- chain:
type: string
description: |
The chain to use for the embeddings. Can be either 'H' (high diversity chain: BCR heavy or TCR beta or delta),
'L' (low diversity chain: BCR light or TCR alpha or gamma) or 'HL' (BCR heavy + light, and TCR alpha + beta or gamma + delta).
- chain:
type: string
description: |
The chain to use for the embeddings. Can be either 'H' (high diversity chain: BCR heavy or TCR beta or delta),
'L' (low diversity chain: BCR light or TCR alpha or gamma) or 'HL' (BCR heavy + light, and TCR alpha + beta or gamma + delta).
enum: ['L', 'H', 'HL']

type: file
description: TSV with embeddings of BCR or TCR amino acid sequences.
pattern: "*.tsv"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change


script:
def args = task.ext.args ?: ''
def prefix = task.ext.prefix ?: "${meta.id}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't suspect a filename clash, as both input and output files are tsv files? If so, here is the suggestion

Suggested change
def prefix = task.ext.prefix ?: "${meta.id}"
def prefix = task.ext.prefix ?: "${meta.id}"
if ("${tsv}" == "${prefix}.tsv") error "Input and output names are the same, use \"task.ext.prefix\" to disambiguate!"

"""

stub:
def prefix = task.ext.prefix ?: "${meta.id}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
def prefix = task.ext.prefix ?: "${meta.id}"
def prefix = task.ext.prefix ?: "${meta.id}"
if ("${input}" == "${prefix}") error "Input and output names are the same, use \"task.ext.prefix\" to disambiguate!"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants