Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@andersgs
Copy link
Contributor

Closes #1782

PR checklist

  • If you've added a new tool - have you followed the module conventions in the contribution docs
  • Remove all TODO statements.
  • Emit the versions.yml file.
  • Follow the naming conventions.
  • Follow the parameters requirements.
  • Follow the input/output options guidelines.
  • Add a resource label
  • Use BioConda and BioContainers if possible to fulfil software requirements.
  • Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
    • PROFILE=docker pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
    • PROFILE=singularity pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
    • PROFILE=conda pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware

Copy link
Contributor

@edmundmiller edmundmiller left a comment

Choose a reason for hiding this comment

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

Great work! Just a few things.

Would it be over-kill to test the other input formats? Again, I'm not familiar with goalign.

- aln:
type: file
description: MultiFASTA/Phylip alignment file
pattern: "*.{fasta,phy}"
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
pattern: "*.{fasta,phy}"
pattern: "*.{fasta,fas,fa,phy}"

This is what's in the output.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That is true, plus as mentioned below, it can be gzipped. So, I have changed the output file to mirror the input file's extension:

 path("*.${aln.getExtension()}"), emit: aln

- aln:
type: file
description: MultiFASTA/Phylip alignment file
pattern: "*.{fasta,phy}"
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not familiar with goalign, but should this be *.{fasta,fas,fa,phy}?

Copy link
Contributor

Choose a reason for hiding this comment

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

The tools also supports compressed inputs, so it should account for those too

- aln:
type: file
description: MultiFASTA/Phylip alignment file
pattern: "*.{fasta,phy}"
Copy link
Contributor

Choose a reason for hiding this comment

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

The tools also supports compressed inputs, so it should account for those too

@andersgs
Copy link
Contributor Author

@emiller88 and @matthdsm thank you for the review. I'll work on it over the weekend.

@edmundmiller
Copy link
Contributor

@andersgs I think you didn't push your work? You added comments but there's no new commits. No rush, just wanted to review them if you were ready!

@andersgs
Copy link
Contributor Author

@emiller88 that is true. I am working on adding the extra tests for different formats. I am also trying to work upstream to allow for compressed output. While the tool allows compressed input, it always outputs uncompressed output. I'll make the push as soon as I can get the test datasets into the test data repo.

-t ${task.cpus} \\
$args \\
-o ${prefix}.${aln.getExtension()} \\
-i $aln
Copy link

@fredericlemoine fredericlemoine Jul 4, 2022

Choose a reason for hiding this comment

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

If input format is phylip, the option -p/--phylip should be specified. Otherwise, if --auto-detect is given, goalign tries to detect the input format in the following order: 1) fasta, 2) nexus, 3) phylip, 4) clustal .

@muffato muffato added the new module Adding a new module label Sep 27, 2022
@matthdsm
Copy link
Contributor

matthdsm commented Mar 7, 2023

@andersgs, are you still to work on this? No pressure, we're just cleaning up for the upcoming nf-core hackathon.

@edmundmiller edmundmiller requested a review from a team October 19, 2023 16:26
@SPPearce
Copy link
Contributor

Does anyone have an interest in getting this finished off? I can help get it updated to recent structural changes (including nf-test). @andersgs , @matthdsm , @fredericlemoine ?

@SPPearce SPPearce added the stale Stale label Aug 16, 2024
@SPPearce
Copy link
Contributor

SPPearce commented Mar 7, 2025

Closing due to lack of activity. Can be reopened if someone wants to take over (but will need significant changes to meet the newer module specifications)

@SPPearce SPPearce closed this Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new module Adding a new module stale Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

new module: goalign/cleanseqs

7 participants