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

[REVIEW]: QuaC: A Pipeline Implementing Quality Control Best Practices for Genome Sequencing and Exome Sequencing Data #5313

Closed
editorialbot opened this issue Mar 30, 2023 · 64 comments
Assignees
Labels
accepted Jinja published Papers published in JOSS recommend-accept Papers recommended for acceptance in JOSS. review Shell TeX Track: 2 (BCM) Biomedical Engineering, Biosciences, Chemistry, and Materials

Comments

@editorialbot
Copy link
Collaborator

editorialbot commented Mar 30, 2023

Submitting author: @ManavalanG (Manavalan Gajapathy)
Repository: https://github.com/uab-cgds-worthey/quac
Branch with paper.md (empty if default branch): joss_manuscript
Version: 1.6
Editor: @lpantano
Reviewers: @brentp, @Redmar-van-den-Berg
Archive: 10.5281/zenodo.10002036

Status

status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/29354a9f9b0e02ec16fdc08c7c7648a6"><img src="https://joss.theoj.org/papers/29354a9f9b0e02ec16fdc08c7c7648a6/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/29354a9f9b0e02ec16fdc08c7c7648a6/status.svg)](https://joss.theoj.org/papers/29354a9f9b0e02ec16fdc08c7c7648a6)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@brentp & @Redmar-van-den-Berg, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @lpantano know.

Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest

Checklists

📝 Checklist for @brentp

📝 Checklist for @Redmar-van-den-Berg

@editorialbot editorialbot added Jinja review Shell TeX Track: 2 (BCM) Biomedical Engineering, Biosciences, Chemistry, and Materials labels Mar 30, 2023
@editorialbot
Copy link
Collaborator Author

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

@editorialbot
Copy link
Collaborator Author

Software report:

github.com/AlDanial/cloc v 1.88  T=0.11 s (526.9 files/s, 47955.6 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
YAML                            21             71             29           1213
Python                          14            318            306           1183
Markdown                        17            324              0            874
Jinja Template                   1             19              0            591
TeX                              1             24              0            208
Bourne Shell                     1             17             10             39
JSON                             1              0              0             23
INI                              1              5              0             17
TOML                             1              1              0              7
-------------------------------------------------------------------------------
SUM:                            58            779            345           4155
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

@editorialbot
Copy link
Collaborator Author

Wordcount for paper.md is 1877

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1093/bioinformatics/btw354 is OK
- 10.1038/s41436-020-01084-8 is OK
- 10.1038/s41525-020-00154-9 is OK
- 10.1093/bioinformatics/btv566 is OK
- 10.1093/bioinformatics/btx699 is OK
- 10.1093/gigascience/gix090 is OK
- 10.1093/gigascience/giab008 is OK
- 10.1101/gr.246934.118 is OK
- 10.1186/s13073-020-00761-2 is OK
- 10.12688/f1000research.15931.2 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@lpantano
Copy link

From @Redmar-van-den-Berg:
I'm trying to follow along with https://quac.readthedocs.io/en/stable/system_testing/, and I've run into 2 issues

The pipeline does not create the output and log folders automatically, so the user has to create the folders manually before the pipeline is started
There is no automatic way to fetch the required reference files that are described in configs/workflow.yaml

@ManavalanG
Copy link

ManavalanG commented Apr 2, 2023

@Redmar-van-den-Berg Thanks for accepting to review our pipeline and providing us an initial feedback.

The pipeline does not create the output and log folders automatically, so the user has to create the folders manually before the pipeline is started

We chose this setup deliberately as this acts as a sanity check for us to be certain that the output and log directories were chosen correctly by the user.

There is no automatic way to fetch the required reference files that are described in configs/workflow.yaml

Good point. I have now automated retrieval and processing of the necessary datasets. Docs are updated to reflect this change, and workflow-config is now updated to utilize the datasets downloaded using above script.

PS- Please be sure to use latest version of the docs. This can be chosen by clicking version button on the bottom right in the docs website.

@Redmar-van-den-Berg
Copy link

We chose this setup deliberately as this acts as a sanity check for us to be certain that the output and log directories were chosen correctly by the user.

I don't think this adds a lot of safety, and it does make it more difficult to run the pipeline.

Good point. I have now automated retrieval and processing of the necessary datasets. Docs are updated to reflect this change, and workflow-config is now updated to utilize the datasets downloaded using above script.

The .test/setup_test_datasets.sh does not run on my system. It uses the module system, which is not available in the quac conda environment. It also refers to /data/project/worthey_lab/samples/NA12878, which will not exist on most users systems. Would it be possible to include a small example bam file in the repository for testing purposes? That way, QuaC could also use automated tests on github, which is one of the recommendations from JOSS.

@ManavalanG
Copy link

The .test/setup_test_datasets.sh does not run on my system.

We make output of this script readily available in the repo. Please see .test/ngs-data/test_project/analysis for the output. This includes bam, vcf, etc. .test/setup_test_datasets.sh was included to show the steps taken to create the files used in system testing, and we do not expect most users to execute the script :)

@ManavalanG
Copy link

Please note that, once the requirements and configs listed here are satisfied, one should be able to run system testing without any further setup. Please let me know if you run into any issues :)

@brentp
Copy link

brentp commented Apr 3, 2023

Review checklist for @brentp

Conflict of interest

  • I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

General checks

  • Repository: Is the source code for this software available at the https://github.com/uab-cgds-worthey/quac?
  • License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
  • Contribution and authorship: Has the submitting author (@ManavalanG) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
  • Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
  • Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
  • Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
  • Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

  • Installation: Does installation proceed as outlined in the documentation?
  • Functionality: Have the functional claims of the software been confirmed?
  • Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

  • A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
  • Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
  • Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
  • Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
  • Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
  • Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

  • Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
  • A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
  • State of the field: Do the authors describe how this software compares to other commonly-used packages?
  • Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
  • References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

@Redmar-van-den-Berg
Copy link

Please note that, once the requirements and configs listed here are satisfied, one should be able to run system testing without any further setup. Please let me know if you run into any issues :)

Maybe we are talking about two different things. The file configs/workflow.yaml refers to a number of reference files, but it is not clear how to get them. Ideally, QuaC would include either a reduced test version of these files, or a script to fetch them automatically.

@ManavalanG
Copy link

Ideally, QuaC would include either a reduced test version of these files, or a script to fetch them automatically.

QuaC includes script src/setup_dependency_datasets.sh to fetch all the datasets listed under datasets in configs/workflow.yaml. If those are not the files you were referring to, please let me know.

I cleaned up the docs a bit for clarity on this topic. I hope this helps.

@Redmar-van-den-Berg
Copy link

Thanks for pointing me to the script, I was able to download the required reference files!

However, I run into a crash when I try to run the pipeline itself, following along to the documentation.

 python src/run_quac.py       --project_name test_project       --projects_path ".test/ngs-data/"       --pedigree ".test/configs/${PRIOR_QC_STATUS}/${PROJECT_CONFIG}.ped"       --outdir "$USER_SCRATCH/tmp/quac/results/test_${PROJECT_CONFIG}_exome-${PRIOR_QC_STATUS}/analysis"       --quac_watch_config "configs/quac_watch/exome_quac_watch_config.yaml"       --exome       $USE_SLURM       -e="--conda-create-envs-only"
########################################
Command to run the pipeline:
snakemake \
	--snakefile '/home/username/devel/quac/workflow/Snakefile' \
	--config project_name='test_project' projects_path='/home/username/devel/quac/.test/ngs-data' ped='/home/username/devel/quac/.test/configs/no_priorQC/project_2samples.ped' quac_watch_config='/home/username/devel/quac/configs/quac_watch/exome_quac_watch_config.yaml' workflow_config='/home/username/devel/quac/configs/workflow.yaml' unique_id='2ad58efa-8557-4807-b85d-ed1d4752ff2f' out_dir='/home/username/devel/quac/scratch/tmp/quac/results/test_project_2samples_exome-no_priorQC/analysis' log_dir='/home/username/devel/quac/scratch/tmp/quac/logs' exome='True' include_prior_qc_data='False' allow_sample_renaming='False' \
	--restart-times 1 \
	--use-conda \
	--use-singularity \
	--singularity-args '--cleanenv --bind /home/username/devel/quac/scratch/tmp/quac/tmp:/tmp --bind /home/username/devel/quac/.test/ngs-data/test_project/analysis,/home/username/devel/quac/scratch/tmp/quac/logs,/home/username/devel/quac/scratch/tmp/quac/results/test_project_2samples_exome-no_priorQC/analysis,data/external/dependency_datasets/somalier,data/external/dependency_datasets/verifyBamID,data/external/dependency_datasets/reference_genome,/home/username/devel/quac/.test/configs/no_priorQC,/home/username/devel/quac/configs/quac_watch/exome_quac_watch_config.yaml,data/external/dependency_datasets/verifyBamID/exome' \
	--profile '/home/username/devel/quac/src/slurm/slurm_profile' \
	--conda-create-envs-only
########################################

Slurm job name   : "quac-2023-04-05T10.10.34.732874"
Slurm job script : "/home/username/devel/quac/scratch/tmp/quac/logs/quac-2023-04-05T10.10.34.732874.sh"
// Processing project: test_project
// Project path: "/home/username/devel/quac/.test/ngs-data/test_project/analysis"
// Exome mode: True
// Include prior QC data: False
// WARNING: '.test' present in the path supplied via --projects_path. So testing mode is used.
Building DAG of jobs...
Pulling singularity image docker://continuumio/miniconda3:4.7.12.
Pulling singularity image docker://brentp/somalier:v0.2.13.
Creating conda environment configs/env/quac_watch.yaml...
Downloading and installing remote packages.
CreateCondaEnvironmentException:
Could not create conda environment from /home/username/devel/quac/configs/env/quac_watch.yaml:
FATAL:   container creation failed: unable to add /home/username/devel/quac/data/external/dependency_datasets/somalier to mount list: destination must be an absolute path

  File "/home/username/miniconda3/envs/quac/lib/python3.6/site-packages/snakemake/deployment/conda.py", line 389, in create
Traceback (most recent call last):
  File "src/run_quac.py", line 372, in <module>
    main(ARGS)
  File "src/run_quac.py", line 202, in main
    submit_slurm_job(pipeline_cmd, job_dict)
  File "/home/username/devel/quac/src/slurm/submit_slurm_job.py", line 60, in submit_slurm_job
    job_id = slurm_job.run(**params_dict)
  File "/home/username/miniconda3/envs/quac/lib/python3.6/site-packages/slurmpy/slurmpy.py", line 171, in run
    res = subprocess.check_output(args).strip()
  File "/home/username/miniconda3/envs/quac/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/home/username/miniconda3/envs/quac/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bash', '/home/username/devel/quac/scratch/tmp/quac/logs/quac-2023-04-05T10.10.34.732874.sh']' returned non-zero exit status 1.

@ManavalanG
Copy link

@Redmar-van-den-Berg I created an issue (uab-cgds-worthey/quac#68) to troubleshoot this error. I hope this works for you.

@ManavalanG
Copy link

@Redmar-van-den-Berg

The pipeline does not create the output and log folders automatically, so the user has to create the folders manually before the pipeline is started

We have now refactored QuaC to auto-create these folders (uab-cgds-worthey/quac#67). Please see here for updated docs - https://quac.readthedocs.io/en/latest/

@ManavalanG
Copy link

ManavalanG commented Apr 24, 2023

@Redmar-van-den-Berg @brentp I would like to inform that we have refactored QuaC to move away from creation of conda environment within singularity containers. QuaC now simply depends on webserver-hosted container images, retrieves them automatically as part of the pipeline and uses them for snakemake-initiated jobs (uab-cgds-worthey/quac#70).

@lpantano
Copy link

lpantano commented May 7, 2023

Hi @brentp, @Redmar-van-den-Berg, could you give an update on the current status of your review. I saw some work done but it is unclear how much work is left. Thanks

@Redmar-van-den-Berg
Copy link

@lpantano I'm still having issues running the pipeline, so I haven't been able to review the pipeline any further.

@brentp
Copy link

brentp commented May 12, 2023

@ManavalanG would you show how to install the software and run on a fresh system?

If possible, I also suggest that you have someone else install and run the example without any guidance from you, perhaps while you watch. Please do this outside of your usual cluster. You have spent much time documenting and building this, but I also am not able to get it running. Currently, I see:

$ python src/run_quac.py       --project_name test_project       --projects_path ".test/ngs-data/"       --pedigree ".test/configs/${PRIOR_QC_STATUS}/${PROJECT_CONFIG}.ped"       --outdir "$USER_SCRATCH/tmp/quac/results/test_${PROJECT_CONFIG}_exome-${PRIOR_QC_STATUS}/analysis"       --quac_watch_config "configs/quac_watch/exome_quac_watch_config.yaml"       --exome       $USE_SLURM
Created directory: /scratch/ucgd/lustre-work/quinlan/u6000771/src/quac/tmp/quac/results/test_project_2samples_exome-no_priorQC/analysis
ERROR: Following directories that are part of your input were not found: 
/scratch/ucgd/lustre-work/quinlan/u6000771/src/quac/data/external/dependency_datasets/somalier
/scratch/ucgd/lustre-work/quinlan/u6000771/src/quac/data/external/dependency_datasets/reference_genome
/scratch/ucgd/lustre-work/quinlan/u6000771/src/quac/data/external/dependency_datasets/verifyBamID
/scratch/ucgd/lustre-work/quinlan/u6000771/src/quac/data/external/dependency_datasets/verifyBamID/exome

It's not clear to me how to resolve this.

@lpantano
Copy link

@editorialbot generate pdf

@lpantano
Copy link

lpantano commented Oct 13, 2023

Post-Review Checklist for Editor and Authors

Additional Author Tasks After Review is Complete

  • Double check authors and affiliations (including ORCIDs)
  • Make a release of the software with the latest changes from the review and post the version number here. This is the version that will be used in the JOSS paper.
  • Archive the release on Zenodo/figshare/etc and post the DOI here.
  • Make sure that the title and author list (including ORCIDs) in the archive match those in the JOSS paper.
  • Make sure that the license listed for the archive is the same as the software license.

Editor Tasks Prior to Acceptance

  • Read the text of the paper and offer comments/corrections (as either a list or a PR)
  • Check the references in the paper for corrections (e.g. capitalization)
  • Check that the archive title, author list, version tag, and the license are correct
  • Set archive DOI with @editorialbot set <DOI here> as archive
  • Set version with @editorialbot set <version here> as version
  • Double check rendering of paper with @editorialbot generate pdf
  • Specifically check the references with @editorialbot check references and ask author(s) to update as needed
  • Recommend acceptance with @editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@lpantano
Copy link

@editorialbot check references

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1093/bioinformatics/btw354 is OK
- 10.1038/s41436-020-01084-8 is OK
- 10.1038/s41525-020-00154-9 is OK
- 10.1093/bioinformatics/btv566 is OK
- 10.1093/bioinformatics/btx699 is OK
- 10.1093/gigascience/gix090 is OK
- 10.1093/gigascience/giab008 is OK
- 10.1101/gr.246934.118 is OK
- 10.1186/s13073-020-00761-2 is OK
- 10.12688/f1000research.15931.2 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@ManavalanG
Copy link

ManavalanG commented Oct 13, 2023

Post-Review Checklist for Editor and Authors

Additional Author Tasks After Review is Complete

  • Double check authors and affiliations (including ORCIDs)
  • Make a release of the software with the latest changes from the review and post the version number here. This is the version that e used in the JOSS paper. - 1.6
  • Archive the release on Zenodo/figshare/etc and post the DOI here. - https://doi.org/10.5281/zenodo.10002036
  • Make sure that the title and author list (including ORCIDs) in the archive match those in the JOSS paper.
  • Make sure that the license listed for the archive is the same as the software license.

@ManavalanG
Copy link

ManavalanG commented Oct 16, 2023

@lpantano Zenodo is going through a major upgrade, and it is not working fully as expected atm. QuaC's repo is already part of zenodo, but it doesn't let me update it to the recent QuaC version 1.6. As soon as zenodo is fully working again, I will update the version and will follow up here. Sorry about the delay!

@ManavalanG
Copy link

ManavalanG commented Oct 17, 2023

@lpantano I have created a new release 1.6 and archived it in Zenodo (DOI - https://doi.org/10.5281/zenodo.10002036). With this, I believe I have completed all the necessary tasks. Please let me know if I missed any :)

@lpantano
Copy link

@editorialbot set v1.6 as version

@editorialbot
Copy link
Collaborator Author

Done! version is now v1.6

@lpantano
Copy link

@editorialbot set 10.5281/zenodo.10002036 as archive

@editorialbot
Copy link
Collaborator Author

Done! archive is now 10.5281/zenodo.10002036

@lpantano
Copy link

@editorialbot recommend-accept

@editorialbot
Copy link
Collaborator Author

Attempting dry run of processing paper acceptance...

@editorialbot
Copy link
Collaborator Author

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1093/bioinformatics/btw354 is OK
- 10.1038/s41436-020-01084-8 is OK
- 10.1038/s41525-020-00154-9 is OK
- 10.1093/bioinformatics/btv566 is OK
- 10.1093/bioinformatics/btx699 is OK
- 10.1093/gigascience/gix090 is OK
- 10.1093/gigascience/giab008 is OK
- 10.1101/gr.246934.118 is OK
- 10.1186/s13073-020-00761-2 is OK
- 10.12688/f1000research.15931.2 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@editorialbot
Copy link
Collaborator Author

👋 @openjournals/bcm-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#4707, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

@editorialbot editorialbot added the recommend-accept Papers recommended for acceptance in JOSS. label Oct 19, 2023
@Kevin-Mattheus-Moerman
Copy link
Member

@editorialbot set 1.6 as version

@editorialbot
Copy link
Collaborator Author

Done! version is now 1.6

@Kevin-Mattheus-Moerman
Copy link
Member

@ManavalanG As EiC on this track I have the honor of helping to process the last steps. I have just checked your repository, this review, the paper, and the archive link, and all seems in order. I will now proceed to accept this work.

@Kevin-Mattheus-Moerman
Copy link
Member

@editorialbot accept

@editorialbot
Copy link
Collaborator Author

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator Author

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

cff-version: "1.2.0"
authors:
- family-names: Gajapathy
  given-names: Manavalan
  orcid: "https://orcid.org/0000-0002-8606-0113"
- family-names: Wilk
  given-names: Brandon M.
  orcid: "https://orcid.org/0000-0002-4110-2324"
- family-names: Worthey
  given-names: Elizabeth A.
  orcid: "https://orcid.org/0000-0003-4083-7764"
contact:
- family-names: Gajapathy
  given-names: Manavalan
  orcid: "https://orcid.org/0000-0002-8606-0113"
- family-names: Worthey
  given-names: Elizabeth A.
  orcid: "https://orcid.org/0000-0003-4083-7764"
doi: 10.5281/zenodo.10002036
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Gajapathy
    given-names: Manavalan
    orcid: "https://orcid.org/0000-0002-8606-0113"
  - family-names: Wilk
    given-names: Brandon M.
    orcid: "https://orcid.org/0000-0002-4110-2324"
  - family-names: Worthey
    given-names: Elizabeth A.
    orcid: "https://orcid.org/0000-0003-4083-7764"
  date-published: 2023-10-23
  doi: 10.21105/joss.05313
  issn: 2475-9066
  issue: 90
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 5313
  title: "QuaC: A Pipeline Implementing Quality Control Best Practices
    for Genome Sequencing and Exome Sequencing Data"
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.05313"
  volume: 8
title: "QuaC: A Pipeline Implementing Quality Control Best Practices for
  Genome Sequencing and Exome Sequencing Data"

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

@editorialbot
Copy link
Collaborator Author

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

@editorialbot
Copy link
Collaborator Author

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.05313 joss-papers#4716
  2. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05313
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Oct 23, 2023
@Kevin-Mattheus-Moerman
Copy link
Member

@ManavalanG congratulations on this JOSS publication!

@lpantano thanks for editing!

And a special thanks to the reviewers: @brentp, @Redmar-van-den-Berg 🎉

@editorialbot
Copy link
Collaborator Author

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.05313/status.svg)](https://doi.org/10.21105/joss.05313)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05313">
  <img src="https://joss.theoj.org/papers/10.21105/joss.05313/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05313/status.svg
   :target: https://doi.org/10.21105/joss.05313

This is how it will look in your documentation:

DOI

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted Jinja published Papers published in JOSS recommend-accept Papers recommended for acceptance in JOSS. review Shell TeX Track: 2 (BCM) Biomedical Engineering, Biosciences, Chemistry, and Materials
Projects
None yet
Development

No branches or pull requests

6 participants