-
-
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]: lenstronomy II: A gravitational lensing software ecosystem #3283
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @smsharma, @coljac it looks like you're currently assigned to review this paper 🎉. Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post. ⭐ Important ⭐ If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿 To fix this do the following two things:
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:
|
PDF failed to compile for issue #3283 with the following error:
|
@smsharma and @coljac - Thanks for agreeing to review this submission. Both reviewers have checklists at the top of this thread with the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. There are also links to the JOSS reviewer guidelines. Please read the first couple of comments in this issue carefully, so that you can accept the invitation from JOSS and be able to check items, and so that you don't get overwhelmed with notifications from other activities in JOSS. The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention We aim for reviews to be completed within about 2-4 weeks. Please let me know if either of you require some more time. We can also use Whedon (our bot) to set automatic reminders if you know you'll be away for a known period of time. Please feel free to ping me (@danielskatz) if you have any questions/concerns. |
|
@whedon generate pdf from branch JOSS_paper |
|
@whedon check references from branch JOSS_paper |
|
|
👋 @sibirrer - I forgot to ask before: Is this submission associated with a paper submitted to a AAS journal? |
@danielskatz No, this is a stand-alone submission. There was an original paper in 2018 (Physics of the Dark Universe) (without code review, highlighting the design feature). |
Thanks - it doesn't really matter in terms of the review process, but it would lead to a minor difference in the publication at the end - see https://blog.joss.theoj.org/2018/12/a-new-collaboration-with-aas-publishing for details |
I see, thanks for the pointer! Was not fully aware of this, but also think that a full-fledged paper is too much work in writing. I hear your argument of financial support through AAS submissions. Perhaps future papers that are responsible for implementing specific features in lenstronomy might be worth going through a JOSS review (it would only be specific modules of lenstronomy). This would both ensure a steady high quality of added features and a rewarding structure for both JOSS and the authors that implemented specific features (it's not just me at this point). It's just a thought but it would also also put more work on JOSS and more frequent reviews. |
Note that one of our (JOSS) sensitivities is in being sure that submissions are substantial units of work, in some equivalent to a science paper, so this might be an issue. In any case, the question has been answered for this submission :) |
@danielskatz I'm just turning to this review. I thought I accepted the invite but it appears I did not and it has expired. Can this be reissued? |
OK, the reviewer has been re-invited. @coljac please accept the invite by clicking this link: https://github.com/openjournals/joss-reviews/invitations |
👋 @coljac, please update us on how your review is going (this is an automated reminder). |
👋 @smsharma, please update us on how your review is going (this is an automated reminder). |
@danielskatz Likewise would it be possible to re-issue the invitation? Thank you! |
OK, the reviewer has been re-invited. @smsharma please accept the invite by clicking this link: https://github.com/openjournals/joss-reviews/invitations |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#2372 If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#2372, then you can now move forward with accepting the submission by compiling again with the flag
|
@danielskatz Yes, can do that. Do I need to regenerate a Zenodo DOI and GitHub release or can I just add it to the branch on GitHub? |
You don't need to update the code repository if changes are just in the paper. But tell me which branch (if not main/master) I need to build the paper from |
I also have suggested some small edits in the paper in https://github.com/sibirrer/lenstronomy/pull/261 - please merge this, or let me know what you disagree with. |
Thank you @danielskatz ! I added the DOI and merged the JOSS_paper branch to main. So you can trigger either from the JOSS_paper branch or main branch. |
@whedon recommend-accept |
|
|
👋 @openjournals/joss-eics, this paper is ready to be accepted and published. Check final proof 👉 openjournals/joss-papers#2373 If the paper PDF and Crossref deposit XML look good in openjournals/joss-papers#2373, then you can now move forward with accepting the submission by compiling again with the flag
|
@whedon accept deposit=true |
|
🐦🐦🐦 👉 Tweet 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... |
I'm going to leave this open until the DOI resolves, which hopefully will be soon and normally would have already happened, but the internet was broken earlier today and might still be catching up |
I had also some issues with automatic zenodo pushes from GitHub and needed to do it manually. Hope it gets resolved but it's not urgent. Thank you very much! |
something is weird with the DOI, earlier and later announcements by JOSS did result in a link (the twitter announcement is kind of lost without the DOI link). Is there a way to re-trigger the DOI generation @danielskatz? |
Yes, I'm aware of this and we are looking into it |
The DOI should now be resolving! |
🎉🎉🎉 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! 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:
|
Thank you @danielskatz @smsharma @coljac on behalf of all authors! |
Submitting author: @sibirrer (Simon Birrer)
Repository: https://github.com/sibirrer/lenstronomy
Version: 1.8.2_JOSS
Editor: @danielskatz
Reviewer: @smsharma, @coljac
Archive: 10.5281/zenodo.4913700
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@smsharma & @coljac, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @danielskatz 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 ✨
Review checklist for @smsharma
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @coljac
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
The text was updated successfully, but these errors were encountered: