Closed editorialbot closed 3 months ago
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
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.48550/arXiv.0909.2331 is OK
- 10.1093/oso/9780198534891.001.0001 is OK
- 10.1007/978-1-4612-0979-9 is OK
- 10.1017/CBO9780511535024 is OK
- 10.1017/CBO9780511628832 is OK
- 10.1093/acprof:oso/9780198568490.001.0001 is OK
- 10.48550/arXiv.1110.6703 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Software report:
github.com/AlDanial/cloc v 1.90 T=0.09 s (1470.3 files/s, 269525.9 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
HTML 50 1607 150 10380
SVG 3 0 0 2689
CSS 6 223 57 1014
JavaScript 12 131 221 880
Python 22 411 422 800
Markdown 5 77 0 382
TeX 2 73 10 368
Jupyter Notebook 10 0 3371 277
reStructuredText 17 124 214 172
YAML 2 7 12 51
DOS Batch 1 8 1 26
TOML 1 4 0 16
make 1 4 7 9
-------------------------------------------------------------------------------
SUM: 132 2669 4465 17064
-------------------------------------------------------------------------------
Commit count by author:
38 thraraujo
5 Thiago Araujo
Paper file info:
📄 Wordcount for paper.md
is 531
✅ The paper includes a Statement of need
section
License info:
🟡 License found: GNU General Public License v3.0
(Check here for OSI approval)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @AnnikaStein, thanks. I will work on these things in the next few days. Talk soon.
I haven't looked at the paper in detail yet, but I will start by opening a few issues on the repo for some things I noticed in the code. I'm going to be using this book to get some background on symmetric polynomials, (there is also this other book). It may be a good idea to cite these as newer, accessible introductions to this topic.
Hi @eliotwrobson,
I'll address the last issue here as it's pertinent to concerns raised by @AnnikaStein. It's worth noting that both @phibeck and @AnnikaStein are fellow physicists.
Regarding your comment:
One of the review checklist items is a discussion of the "state of the field" about other software packages. Some discussion of this would be very useful, even if it is just stating what operations are supported by this package that do not exist elsewhere (i.e. not in sympy).
Regarding your comment:
The section on the core features of the package would be much stronger if there were an example of the analysis that could be done with the package in relation to the discussion of CFTs. As someone with a pure combinatorics background, it's a little hard to tell what types of analysis can be done with the package in the context of theoretical physics.
Describing the types of analyses possible isn't straightforward, given the myriad combinatorial problems in physics. However, I've appended references to Okounkov's and Marino's papers, which align with my interests. In any case, you might check examples ranging from condensed matter physics Zinn-Justin to string theory Nekrasov-Okounkov.
One relevant example within your interests is in representation theory. Quantum mechanics operators (representing measurable objects) are unitary (Lie groups SU(n)), and through the Schur-Weyl duality, their representations are labeled by Young diagrams, related to symmetric group representations. Schur polynomials serve as characters in these representations.
While I refrain from self-citation, I've conducted research leveraging this software to examine objects called tau functions, as elaborated in this paper. These objects were expanded in terms of Schur and Hall-Littlewood polynomials.
Lastly, I aim to keep the paper concise, adhering to <700 words, as per @phibeck's comments.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@thraraujo your changes look good! The main item from the review checklist was the discussion of the state of other packages, and that section is clear. I'll go ahead and close the issue and check that item off of my list 👍🏽
Hi @eliotwrobson and @AnnikaStein, thanks for all the comments.
Hi @phibeck, the only missing point appears to be the Summary in @AnnikaStein's checklist. @eliotwrobson's checklist agrees that the summary already provides a high-level description understandable even to non-specialists. In my opinion, key terms like Manipulation, Polynomials, and Symmetric are very precise, so I don't want to give an additional high-level description of the types of manipulations or symmetric polynomials the package deals with. Since this is a minor point, I'll leave the decision to you.
Sorry @thraraujo for not being clear on what I meant with this point - I was a bit hesitant to check it as the summary contains abbreviations, "AdS/CFT" which, in my opinion, a "diverse, non-specialist audience" would likely not understand without further reading. For someone with a physics background, one may always infer that field theories are meant when you see the letters FT next to each other :), but if one looks at it from a different perspective, it's a non-trivial set of abbreviations.
Hi @AnnikaStein, actually, it is a fair take, and I'd missed it. Now it's fixed. Thanks
Dear @phibeck , it appears that the reviewers have completed their evaluations; and I am awaiting your decision or further instructions. Could you please provide an update on the next steps in the process? Best
Hi @thraraujo thanks for checking in. I'm travelling this week but will look into it tomorrow. I believe we are ready to proceed, but let me get back to you tomorrow.
Thank you very much for an incredibly speedy and thorough review, @AnnikaStein and @eliotwrobson! :rocket: And thank you @thraraujo for addressing all comments timely and adequately. :raised_hands: This is by far the fastest review I have seen so far, thank you all! :1st_place_medal:
@thraraujo the reviewers have recommended the submission for publication. There are a few more steps before we finalize the publication. At this point could you please:
I can then move forward with recommending acceptance of the submission.
@editorialbot set <DOI here> as archive
@editorialbot set <version here> as version
@editorialbot generate pdf
@editorialbot check references
and ask author(s) to update as needed@editorialbot recommend-accept
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.48550/arXiv.0909.2331 is OK
- 10.1093/oso/9780198534891.001.0001 is OK
- 10.1007/978-1-4612-0979-9 is OK
- 10.1017/CBO9780511535024 is OK
- 10.1017/CBO9780511628832 is OK
- 10.1093/acprof:oso/9780198568490.001.0001 is OK
- 10.48550/arXiv.1110.6703 is OK
- 10.5281/zenodo.593563 is OK
- 10.1142/9789812704016_0037 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @phibeck , thanks
Thank you very much for an incredibly speedy and thorough review, @AnnikaStein and @eliotwrobson! 🚀 And thank you @thraraujo for addressing all comments timely and adequately. 🙌 This is by far the fastest review I have seen so far, thank you all! 🥇
Kudos to @AnnikaStein and @eliotwrobson! They were indeed very fast, and I sincerely believe the package is much better now.
- [X] Make a tagged release of your software, and list the version tag of the archived version here.
I have already done this, version v0.1.2
- [X] Archive the reviewed software in Zenodo or a similar service (e.g., figshare, an institutional repository)
Archived here: https://zenodo.org/records/11214737
- [X] Check the archival deposit (e.g., in Zenodo) has the correct metadata. This includes the title (should match the paper title) and author list (make sure the list is correct and people who only made a small fix are not on it). You may also add the authors' ORCID.
Done.
- [X] Please list the DOI of the archived version here.
Hi @phibeck, any news?!?
@editorialbot set v0.1.2 as version
Done! version is now v0.1.2
@editorialbot set 10.5281/zenodo.11214737 as archive
Done! archive is now 10.5281/zenodo.11214737
@thraraujo thanks for the reminder. I'm away for a workshop since last week so response is a bit slow. Here are a few more comments/suggestions for the manuscript. Please have a look when you have a moment.
Blah blah [@doe99; @smith2000; @smith2004]
should render them as one block (see https://pandoc.org/MANUAL.html#extension-citations)Hi @phibeck, it's done. Thanks.
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.48550/arXiv.0909.2331 is OK
- 10.1093/oso/9780198534891.001.0001 is OK
- 10.1007/978-1-4612-0979-9 is OK
- 10.1017/CBO9780511535024 is OK
- 10.1017/CBO9780511628832 is OK
- 10.1093/acprof:oso/9780198568490.001.0001 is OK
- 10.48550/arXiv.1110.6703 is OK
- 10.5281/zenodo.593563 is OK
- 10.1142/9789812704016_0037 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
:wave: @thraraujo looks good, thank you. I'll hand this over to the Track Editor-in-chief!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.48550/arXiv.0909.2331 is OK
- 10.1093/oso/9780198534891.001.0001 is OK
- 10.1007/978-1-4612-0979-9 is OK
- 10.1017/CBO9780511535024 is OK
- 10.1017/CBO9780511628832 is OK
- 10.1093/acprof:oso/9780198568490.001.0001 is OK
- 10.48550/arXiv.1110.6703 is OK
- 10.5281/zenodo.593563 is OK
- 10.1142/9789812704016_0037 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/pe-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/5409, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@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: Araujo given-names: Thiago orcid: "https://orcid.org/0000-0001-5792-2530" doi: 10.5281/zenodo.11214737 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Araujo given-names: Thiago orcid: "https://orcid.org/0000-0001-5792-2530" date-published: 2024-05-30 doi: 10.21105/joss.06724 issn: 2475-9066 issue: 97 journal: Journal of Open Source Software publisher: name: Open Journals start: 6724 title: PySymmPol - Symmetric Polynomials type: article url: "https://joss.theoj.org/papers/10.21105/joss.06724" volume: 9 title: PySymmPol - Symmetric Polynomials ```
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 @thraraujo on your article's publication in JOSS! Please consider signing up as a reviewer if you haven't already.
Many thanks to @eliotwrobson and @AnnikaStein for reviewing this, and @phibeck for editing.
: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.06724/status.svg)](https://doi.org/10.21105/joss.06724)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06724">
<img src="https://joss.theoj.org/papers/10.21105/joss.06724/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06724/status.svg
:target: https://doi.org/10.21105/joss.06724
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: !--author-handle-->@thraraujo<!--end-author-handle-- (Thiago Rocha Araujo) Repository: https://github.com/thraraujo/pysymmpol Branch with paper.md (empty if default branch): paper Version: v0.1.2 Editor: !--editor-->@phibeck<!--end-editor-- Reviewers: @eliotwrobson, @AnnikaStein Archive: 10.5281/zenodo.11214737
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
@eliotwrobson & @AnnikaStein, 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 @phibeck 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 @AnnikaStein
📝 Checklist for @eliotwrobson