-
-
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]: TEAM: Tensegrity Engineering Analysis Master #1507
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
What happens now? This submission is currently in a You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here. |
|
PDF failed to compile for issue #1507 with the following error: Can't find any papers to compile :-( |
Hi @ramaniitrgoyal92, thanks for your submission to JOSS. Please rename your paper to |
The suggested reviewers: |
For the editor, once they're assigned: However, I'd like to quickly check about JOSS' Conflict of Interest policy (https://joss.readthedocs.io/en/latest/reviewer_guidelines.html), since I'm still new to open review (not blind). The submitting author @ramaniitrgoyal92 and I are professional acquaintances who have discussed research before and compared our past publications, but have not collaborated on funded work or authorship, and are not members of the same institution. Normally this wouldn't be a problem for single-blind review, but does it pose a challenge for open review? Either way, I believe I can provide an "impartial assessment," but would like to disclose our relationship before agreeing to be a reviewer. |
Hello. Thank you for invitation but I do not have the expertise to review this:
I will have to pass on this, sorry. |
@whedon generate pdf |
|
PDF failed to compile for issue #1507 with the following error: /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-18b9a37e7f54/lib/whedon/orcid_validator.rb:12:in |
@whedon assign @Kevin-Mattheus-Moerman as editor |
OK, the editor is @Kevin-Mattheus-Moerman |
@apsabelhaus thanks for raising the conflict of interest issue. I'll add you as a reviewer but will also recruit others. Thanks |
@whedon assign @apsabelhaus as reviewer |
OK, the reviewer is @apsabelhaus |
@vaishnavtv @ctdegroot since you were involved with #1042, would you be interested in helping with this review? |
@ramaniitrgoyal92 Please rename your paper to |
@Kevin-Mattheus-Moerman Yes, I can help with this review. |
@apsabelhaus @ctdegroot thanks for helping with this review. We have to iron out some things with the paper and I hope to recruit an additional reviewer. I'll ping you again when we are ready to start the review process. |
@Kevin-Mattheus-Moerman, I would love to help with the review, but under full disclosure, I'd like to state that the submitting author and I are personally acquainted and are pursuing a graduate degree from the same institution. We have not officially collaborated on any research, but our advisors have worked together in the past. If this violates any reviewer policies based on a conflict of interest, kindly let me know. |
Thanks @vaishnavtv (sorry I accidentally tagged you in the comment above I just edited) for reporting that potential conflict of interest. If you'd like to help your help is still appreciated. I will however recruit an additional reviewer. |
@arfon @Kevin-Mattheus-Moerman Thanks for reminding! I have changed the file name. |
@whedon generate pdf |
|
@whedon generate pdf |
@whedon generate pdf |
|
great, happy to be a reviewer. @ramaniitrgoyal92 I'll probably need at least three weeks to get around to this - my dissertation draft is due to my committee ASAP - so you can expect my first round of comments during mid-July. @Kevin-Mattheus-Moerman let me know when the process is ready to start and that checklist is up. 👍 |
@Jfriesen222 would you be interested in reviewing this work on tensegrity modelling for JOSS? The review process will focus on the software and this short paper. |
@Kevin-Mattheus-Moerman is the review thread started for this submission yet? I'm available to start the review process, but can't seem to find the link to e.g. the checklist. |
@ramaniitrgoyal92 while we're waiting for the official review to open, I added a first issue in the repo about organization and documentation, so there's something to start on! Also, the paper is missing references [???], probably a bug in the latex. |
@whedon add @vaishnavtv as reviewer |
OK, @vaishnavtv is now a reviewer |
@whedon add @ctdegroot as reviewer |
OK, @ctdegroot is now a reviewer |
@Jfriesen222 would you be interested in reviewing this work on tensegrity modelling for JOSS? The review process will focus on the software and this short paper. |
@whedon start review |
OK, I've started the review over in #1613. Feel free to close this issue now! |
The review has started over at #1613 however additional reviewers are still welcome. Contact me if interested. |
Submitting author: @ramaniitrgoyal92 (Raman Goyal)
Repository: https://github.com/ramaniitrgoyal92/Tensegrity_Engineering_Analysis_Master-TEAM-
Version: v2.1
Editor: @Kevin-Mattheus-Moerman
Reviewers: @apsabelhaus, @vaishnavtv, @ctdegroot
Author instructions
Thanks for submitting your paper to JOSS @ramaniitrgoyal92. Currently, there isn't an JOSS editor assigned to your paper.
@ramaniitrgoyal92 if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
The text was updated successfully, but these errors were encountered: