-
-
Notifications
You must be signed in to change notification settings - Fork 38
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]: HiddenMarkovModels.jl: generic, fast and reliable latent variable modeling #6436
Comments
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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🔴 Failed to discover a valid open source license |
|
@DanielRivasMD, @dmbates - thank you for accepting our invitation. Please, firstly create your checklist before starting your review. Thank you in advance @gdalle - One of your citation entries in the BibTeX seems incorrect, could you please consider correcting it? Thank you. |
I'll take a look at the citation. The bot seems to expect that the paper is located on a branch where the rest of the code lives too. I'm gonna merge |
@gdalle - As expressed at the top of the page, the default branch of your paper is |
Yeah but there's no code on it, just the markdown, so that's why the bot can't find the license or get an accurate LOC count |
Also the version of the package is now 0.5.0 |
@editorialbot set v0.5.0 as version |
Done! version is now v0.5.0 |
@editorialbot commands |
Hello @gdalle, here are the things you can ask me to do:
|
@editorialbot set joss2 as branch |
Done! branch is now joss2 |
@editorialbot check references |
|
@editorialbot check repository |
Software report:
Commit count by author:
|
@editorialbot recommend-accept |
|
|
Element doi: [facet 'pattern'] The value '10/cswph2' is not accepted by the pattern '10\.[0-9]{4,9}/.{1,200}'. |
@gdalle - The problem is about the DOI entry of the bibtex item
Could you please fix it and then ping me again? |
@openjournals/dev - Interestingly the doi is resolved by DOI.org however we get this error:
|
@gdalle - using
|
I just made the modification, anything to make our little bot happy ;) @editorialbot generate pdf |
@editorialbot check references |
|
@editorialbot generate pdf |
@editorialbot recommend-accept |
|
|
👋 @openjournals/dsais-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#5217, then you can now move forward with accepting the submission by compiling again with the command |
looks good to me |
@editorialbot accept |
|
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
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... |
@DanielRivasMD, @dmbates – many thanks for your reviews here and to @jbytecode for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨ @gdalle – your paper is now accepted and published in JOSS ⚡🚀💥 |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
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:
|
Submitting author: @gdalle (Guillaume Dalle)
Repository: https://github.com/gdalle/HiddenMarkovModels.jl
Branch with paper.md (empty if default branch): joss2
Version: v0.5.1
Editor: @jbytecode
Reviewers: @DanielRivasMD, @dmbates
Archive: 10.5281/zenodo.10931812
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
@DanielRivasMD & @dmbates, 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 @jbytecode 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 @dmbates
📝 Checklist for @DanielRivasMD
The text was updated successfully, but these errors were encountered: