Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add validation for fasta input and tests #20

Merged
merged 28 commits into from
May 13, 2024

Conversation

JoseEspinosa
Copy link
Member

@JoseEspinosa JoseEspinosa commented May 8, 2024

  • Validate fasta input.
  • Branching samplesheet into samplesheet_query and samplesheet_fasta and refactor code accordingly.
  • Add test for fasta, run with -profile test_fasta.
  • Run test_fasta on CI.
  • Other minor fixes.

Closes #17

PR checklist

  • This comment contains a description of changes (with reason).
  • If you've fixed a bug or added code that should be tested, add tests!
  • Make sure your code lints (nf-core lint).
  • Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
  • Usage Documentation in docs/usage.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

Copy link

github-actions bot commented May 8, 2024

nf-core lint overall result: Passed ✅ ⚠️

Posted for pipeline commit cc50269

+| ✅ 216 tests passed       |+
!| ❗  13 tests had warnings |!

❗ Test warnings:

  • files_exist - File not found: conf/igenomes.config
  • readme - README contains the placeholder zenodo.XXXXXXX. This should be replaced with the zenodo doi (after the first release).
  • pipeline_todos - TODO string in README.md: Add citation for pipeline after first release. Uncomment lines below and update Zenodo doi and badge at the top of this file.
  • pipeline_todos - TODO string in base.config: Check the defaults for all processes
  • pipeline_todos - TODO string in base.config: Customise requirements for specific processes.
  • pipeline_todos - TODO string in usage.md: Add documentation about anything specific to running your pipeline. For general topics, please point to (and add to) the main nf-core website.
  • pipeline_todos - TODO string in ci.yml: You can customise CI pipeline run tests as required
  • pipeline_todos - TODO string in ci.yml: You can customise CI pipeline run tests as required
  • pipeline_todos - TODO string in awsfulltest.yml: You can customise AWS full pipeline tests as required
  • pipeline_todos - TODO string in main.nf: Optionally add in-text citation tools to this list.
  • pipeline_todos - TODO string in main.nf: Optionally add bibliographic entries to this list.
  • pipeline_todos - TODO string in main.nf: Only uncomment below if logic in toolCitationText/toolBibliographyText has been filled!
  • pipeline_todos - TODO string in methods_description_template.yml: #Update the HTML below to your preferred methods description, e.g. add publication citation for this pipeline

✅ Tests passed:

Run details

  • nf-core/tools version 2.14.1
  • Run at 2024-05-13 09:57:38

Copy link
Collaborator

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

The code looks good, hopefully it is tested as I have very little knowledge of nf-schema. Should we not update the readme and usage to reflect the changes in the input format?

Copy link
Collaborator

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

Looks good, just some very minor comments

README.md Outdated Show resolved Hide resolved
docs/usage.md Outdated
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | User-defined identifier. It is used to identify output files for the protein. Can be anything descriptive, as long as it does not contain spaces. |
| `query` | The query of the user-specified type. It should be a valid Uniprot accession. |
| `fasta` | It should be a valid path to a FASTA file. |

An [example samplesheet](../assets/samplesheet.csv) has been provided with the pipeline.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we want an example for FASTA samplesheet as well?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is changed in line 33, or are you referring to something else?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Line 43 mentions a separate samplesheet file, I wonder if we need a similar one for FASTA. Just a question to consider, not necessarily demanding it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done in 195ab8d

Co-authored-by: Igor Trujnara <[email protected]>
Copy link
Collaborator

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

Final tiny tweak

docs/usage.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

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

LGTM

@JoseEspinosa JoseEspinosa merged commit 8ba2862 into nf-core:dev May 13, 2024
6 checks passed
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.

Add validation for fasta file input
2 participants