-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
[PRE REVIEW]: dia: An R package for the National Oceanic and Atmospheric Administration dam impact analysis #7397
Comments
Hello human, 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: 🟡 License found: |
|
👋 @danStich - note that your paper does not compile. Please follow the example paper and note that you can click on the error above to find out more about it. |
@editorialbot generate pdf I think it may have been an un-indented "index" tag but I quoted the affiliations just in case (they were all single). Checking here. |
Five most similar historical JOSS papers: stacomiR : a common tool for monitoring fish migration fishRman: A Shiny R Dashboard improving Global Fishing Watch data availability Reference Point Calculator (RPC): A Shiny app for exploration of limit reference points for fisheries management nsink: An R package for flow path nitrogen removal estimation mmrefpoints: Projecting long-term marine mammal abundance with bycatch |
Hi @kthyng, |
Hi @danStich and thanks for your submission! I am looking for some specific items to make sure your submission fits our requirements at a high level (not at the more detailed review level) before moving on to finding an editor or putting this on our waitlist if no relevant editors are available. I'll comment over time as I have a chance to go through them:
In the meantime, please take a look at the comments above ⬆️ from the editorialbot to address any DOI, license, or paper issues if you're able (there may not be any), or suggest reviewers. For reviewers, please suggest 5 reviewers from the database listed above or your own (non-conflicted) extended network. Their github handles are most useful to receive but please don't use "@" to reference them since it will prematurely ping them. |
Sounds great, thank you. I can find the 'skipped' DOIs from the reference check in the meantime and start putting together a list of potential reviewers. |
@danStich This looks ready to go though an example plot in your docs would be great — something to look at, a little more of a tutorial sort of thing. Just a suggestion. |
@kthyng Thank you, I can add an example plot. I think we may have had one in an earlier internal draft as well. I have another MS in revision that has a short turnaround time so it may be Monday before I address the items I added for myself to the list below.
Potential ReviewersFrom the JOSS reviewer database from most similar to least based on tags and profiles:
From the 5 most similar JOSS submissions listed for this submission:
From extended, non-conflicted network
|
@editorialbot generate pdf Checking that PDF compiles following updated DOIs and addition of example figure (Figure 1). |
Five most similar historical JOSS papers: mmrefpoints: Projecting long-term marine mammal abundance with bycatch Reference Point Calculator (RPC): A Shiny app for exploration of limit reference points for fisheries management stacomiR : a common tool for monitoring fish migration Shiny tools for management rules: interactive applications that aid in conservation strategies for North Atlantic right whales nsink: An R package for flow path nitrogen removal estimation |
@cheginit Could you edit this submission? |
@editorialbot invite @cheginit as editor |
Invitation to edit this submission sent! |
@kthyng Yes, I can edit this. |
@editorialbot assign @cheginit as editor |
Assigned! @cheginit is now the editor |
👋🏼 @rmk118, @Fabbiologia, and @k-doering-NOAA, Would you like to review this submission to the Journal for Open Source Software? Our reviews are checklist-driven and openly conducted on GitHub over a timeline of 4–6 weeks. Because the process is much more iterative and interactive than a traditional paper review, we would ask you to start within the next 2 weeks. Here are reviewer guidelines for reference: joss.readthedocs.io/en/latest/reviewer_guidelines.html Thanks for your consideration. |
Hi @cheginit! I would be happy to edit this submission. This will be my first JOSS review, so I apologize in advance if I am not the smoothest at navigating the logistics of reviewing on GitHub. |
@rmk118 Thanks for agreeing to review this submission and welcome to the JOSS community! I will provide detailed instructions for the review, and you can also read JOSS's guideline for more information. Once I find another reviewer, I will open a new issue and ping you with instructions to being the review. Thanks! |
hi @cheginit sorry for the delay, I was on the field. Will be happy to review this work. |
Checklists can only be created once the review has started in the review issue |
@Fabbiologia Thanks for agreeing to review this submission! I will open a new issue with instructions to being the review. |
@editorialbot add @Fabbiologia as reviewer |
@Fabbiologia added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7475. |
Submitting author: @danStich (Daniel Stich)
Repository: https://github.com/danStich/dia
Branch with paper.md (empty if default branch): main
Version: v1.0.0
Editor: @cheginit
Reviewers: @Fabbiologia
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @danStich. Currently, there isn't a JOSS editor assigned to your paper.
@danStich if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: