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

Update docs #498

Merged
merged 15 commits into from
May 4, 2022
Merged

Update docs #498

merged 15 commits into from
May 4, 2022

Conversation

FriederikeHanssen
Copy link
Contributor

@FriederikeHanssen FriederikeHanssen commented Mar 11, 2022

#504

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!
    • If you've added a new tool - add to the software_versions process and a regex to scrape_software_versions.py
    • If you've added a new tool - have you followed the pipeline conventions in the contribution docs
    • If necessary, also make a PR on the nf-core/sarek branch on the nf-core/test-datasets repository.
  • Make sure your code lints (nf-core lint .).
  • Ensure the test suite passes (nextflow run . -profile test,docker).
  • Usage Documentation in docs/usage.md is updated.
  • Output Documentation in docs/output.md is updated.
  • CHANGELOG.md is updated.
  • README.md is updated (including new tool citations and authors/contributors).

docs/output.md Outdated Show resolved Hide resolved
@FriederikeHanssen
Copy link
Contributor Author

I am more or less content with the restructuring/rewritting/overhauling of the section for "Input Smaplesheets", if anyone wants give some feedback on the current state @maxulysse @nickhsmith, pretty much anyone who will need to use this in the future.

@nickhsmith
Copy link
Contributor

It looks good to me. I just think automatic input detection is a great feature, but it is at odds with the mandatory params input. That's my understanding of it.

@FriederikeHanssen
Copy link
Contributor Author

FriederikeHanssen commented Mar 17, 2022

We are planning on having this. Do you think this descirbes it well enough?:

The `Sarek`-generated `CSV` file is stored under `results/Preprocessing/CSV/duplicates_marked_no_table.csv` and will automatically be used as an input when specifying the parameter `--step prepare_recalibration`.

so rather maybe having a separate section on automatic restart?

@nickhsmith
Copy link
Contributor

I think I'm confused on what we are discussing. This is for the documentation on how to use the different entry points correct? But The requirement of line 57 of main.nf which calls WorkflowMain.initialise(workflow, params, log) which requires:

if (!params.input) {                                                                                            
     log.error "Please provide an input samplesheet to the pipeline e.g. '--input samplesheet.csv'"              
     System.exit(1)                                                                                              
 }

no matter what the params.input must be provided or it will not start the pipeline

is unaddressed. If the user provides params.input = 'recalibrated.csv' params.step = 'prepare_recalibration' (or whatever) that's a different behavior than just params.step = 'prepare_recalibration'

@FriederikeHanssen
Copy link
Contributor Author

Yes, nothing is fixed here, it is just about the update to the usage.md and in there about the input samplesheets section: https://github.com/nf-core/sarek/blob/486aec71fbf0426f6b2eab54b52679a6fc54836f/docs/usage.md

The code fixes will be done in a separate PR

@nickhsmith
Copy link
Contributor

Ok now I understand a bit more thanks for the added info! I think it's clear :)

@FriederikeHanssen
Copy link
Contributor Author

ok, sorry I could have added more info. I was in the zone and I knew what I meant :D

FriederikeHanssen and others added 2 commits March 18, 2022 11:25
Co-authored-by: Maxime U. Garcia <maxime.garcia@scilifelab.se>
@FriederikeHanssen FriederikeHanssen marked this pull request as ready for review May 4, 2022 08:51
@maxulysse
Copy link
Member

why is there changes in workflows/sarek.nf?

@maxulysse
Copy link
Member

It seems there's some conflicts as well

@FriederikeHanssen
Copy link
Contributor Author

why is there changes in workflows/sarek.nf?

🤔 I'll rebase and see what happens. Just finishing up quickly the other PR

@FriederikeHanssen
Copy link
Contributor Author

ok still irritated about the workflow changes. I think I'll just manually change them to what is in dev at the moment.

@maxulysse maxulysse merged commit bb769b5 into nf-core:dev May 4, 2022
@FriederikeHanssen FriederikeHanssen deleted the documentation branch July 10, 2023 19:00
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.

3 participants