Closed editorialbot closed 11 months ago
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
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:
``` cff-version: "1.2.0" authors: - family-names: Hegemann given-names: Nando orcid: "https://orcid.org/0000-0003-3953-9006" - family-names: Heidenreich given-names: Sebastian orcid: "https://orcid.org/0000-0002-1909-5770" contact: - family-names: Hegemann given-names: Nando orcid: "https://orcid.org/0000-0003-3953-9006" doi: 10.5281/zenodo.8329459 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Hegemann given-names: Nando orcid: "https://orcid.org/0000-0003-3953-9006" - family-names: Heidenreich given-names: Sebastian orcid: "https://orcid.org/0000-0002-1909-5770" date-published: 2023-09-15 doi: 10.21105/joss.05489 issn: 2475-9066 issue: 89 journal: Journal of Open Source Software publisher: name: Open Journals start: 5489 title: "PyThia: A Python package for Uncertainty Quantification based on non-intrusive polynomial chaos expansions" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05489" volume: 8 title: "PyThia: A Python package for Uncertainty Quantification based on non-intrusive polynomial chaos expansions" ```
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.
πππ π Toot for this paper π πππ
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Congratulations to @Nando-Hegemann and co-author!!
And thanks to @ziyiyin97 and @timokoch for reviewing, and to @vissarion for editing! JOSS depends on volunteers, and we couldn't do this without you
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
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.05489/status.svg)](https://doi.org/10.21105/joss.05489)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05489">
<img src="https://joss.theoj.org/papers/10.21105/joss.05489/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05489/status.svg
:target: https://doi.org/10.21105/joss.05489
This is how it will look in your documentation:
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:
Thanks a lot @ziyiyin97 and @timokoch for the review, and @vissarion and @danielskatz for editing. Both the article and especially the code improved a lot due to your suggestions!
It was a pleasure to work with you all.
Submitting author: !--author-handle-->@Nando-Farchmin<!--end-author-handle-- (Nando Farchmin) Repository: https://gitlab.com/pythia-uq/pythia Branch with paper.md (empty if default branch): paper/joss Version: v4.0.3 Editor: !--editor-->@vissarion<!--end-editor-- Reviewers: @ziyiyin97, @timokoch Archive: 10.5281/zenodo.8329459
Status
Status badge code:
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
@ziyiyin97 & @timokoch, 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:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @vissarion 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 @ziyiyin97
π Checklist for @timokoch