-
-
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]: PyExperimenter: Easily distribute experiments and track results #5149
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:
|
|
Wordcount for |
|
@ArsamAryandoust, @schnorr, see above for instructions to review. If anything is unclear, just let me know. Please finish your reviews within six weeks at the very latest. I will add a reminder in two weeks from now for both of you. |
@editorialbot remind @ArsamAryandoust in two weeks |
Reminder set for @ArsamAryandoust in two weeks |
@editorialbot remind @schnorr in two weeks |
Reminder set for @schnorr in two weeks |
Review checklist for @ArsamAryandoustConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
👋 @ArsamAryandoust, please update us on how your review is going (this is an automated reminder). |
👋 @schnorr, please update us on how your review is going (this is an automated reminder). |
Review checklist for @schnorrConflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
|
Hi @ArsamAryandoust and @schnorr, can you let us know how the review is going? Half of the review time has elapsed and I'll set another reminder for both of you to let you know when the review time is almost over. |
@editorialbot remind @schnorr in two weeks |
Reminder set for @schnorr in two weeks |
@editorialbot remind @ArsamAryandoust in two weeks |
Reminder set for @ArsamAryandoust in two weeks |
Hi @timtroendle, I've started my review and hope to finish this week. |
Great, thanks for letting us know. |
So, just to let you know that I've completed my review. My opinion after regarding the source code, documentation, testing the commands suggested by the authors, etc, is that the About the Functionality, I think the tool is very useful because usually R or Python packages are focused on generating the experimental project without handling the experiment run. The PyExperimenter let the user define a function that will receive the configuration parameters. The function must then run the experiment itself with those parameters and let PyExperimenter know that everything went okay. So, the functionality provides a way to define the experiment project and also run it (eventually in parallel with the I've checked all the bullet points in the review, running Thank you once again for considering my for JOSS @timtroendle ! |
Done! version is now v1.2.0 |
@editorialbot check references |
@editorialbot generate pdf |
|
@tornede, it all looks good to me and I am happy to move forward. Thanks again @schnorr and @ArsamAryandoust for your reviews! |
@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#4138, then you can now move forward with accepting the submission by compiling again with the command |
|
@timtroendle It looks good to me, too. Do I have to tell it to the editorial bot, or do you do it? Thanks again everyone :) |
@tornede, there is nothing you need to do at this point. One of the editors-in-chief will take over from here. :) |
@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. |
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦 |
🐘🐘🐘 👉 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... |
@ArsamAryandoust, @schnorr – many thanks for your reviews here and to @timtroendle 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 ✨ @tornede – 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: @tornede (Tanja Tornede)
Repository: https://github.com/tornede/py_experimenter
Branch with paper.md (empty if default branch): develop
Version: v1.2.0
Editor: @timtroendle
Reviewers: @ArsamAryandoust, @schnorr
Archive: 10.5281/zenodo.7838280
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
@ArsamAryandoust & @schnorr, 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 @timtroendle 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 @ArsamAryandoust
📝 Checklist for @schnorr
The text was updated successfully, but these errors were encountered: