search

openjournals / joss-reviews

Reviews for the Journal of Open Source Software
Creative Commons Zero v1.0 Universal
721 stars 38 forks source link

[PRE REVIEW]: ORION2: A magnetohydrodynamics code for star formation #3559

Closed whedon closed 3 years ago

whedon commented 3 years ago

Submitting author: @soffner (Stella Offner) Repository: https://bitbucket.org/orionmhdteam/orion2_release1/src/master/ Version: v1.0.0 Editor: @dfm Reviewers: @zingale, @changgoo Managing EiC: Kevin M. Moerman

:warning: JOSS reduced service mode :warning:

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

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/c8c824a316e16f6929ad490ee93d9f5d"><img src="https://joss.theoj.org/papers/c8c824a316e16f6929ad490ee93d9f5d/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/c8c824a316e16f6929ad490ee93d9f5d/status.svg)](https://joss.theoj.org/papers/c8c824a316e16f6929ad490ee93d9f5d)

Author instructions

Thanks for submitting your paper to JOSS @soffner. Currently, there isn't an JOSS editor assigned to your paper.

@soffner if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).

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:

@whedon commands
whedon commented 3 years ago

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.

:warning: JOSS reduced service mode :warning:

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.

For a list of things I can do to help you, just type:

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf
whedon commented 3 years ago

Wordcount for paper.md is 814

whedon commented 3 years ago

PDF failed to compile for issue #3559 with the following error: 

 Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
Invalid ORDIC digit (x)
/app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon.rb:155:in `block in check_orcids': Problem with ORCID (xxxx-xxxx-xxxx-xxxx) for Pak Shing Li (RuntimeError)
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon.rb:153:in `each'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon.rb:153:in `check_orcids'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon.rb:90:in `initialize'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon/processor.rb:38:in `new'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/lib/whedon/processor.rb:38:in `set_paper'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/bin/whedon:58:in `prepare'
    from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
    from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
    from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
    from /app/vendor/bundle/ruby/2.6.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
    from /app/vendor/bundle/ruby/2.6.0/bundler/gems/whedon-b63fc70cc085/bin/whedon:131:in `<top (required)>'
    from /app/vendor/bundle/ruby/2.6.0/bin/whedon:23:in `load'
    from /app/vendor/bundle/ruby/2.6.0/bin/whedon:23:in `<main>'
whedon commented 3 years ago 
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1093/mnras/stz653 is OK
- 10.1093/mnras/stx2611 is OK
- 10.1093/mnras/stv1437 is OK
- 10.1088/0004-637X/747/1/22 is OK
- 10.1016/j.jcp.2007.07.035 is OK
- 10.1016/j.jcp.2007.09.032 is OK
- 10.1086/421935 is OK
- 10.1088/0004-637X/745/2/139 is OK
- 10.1086/305329 is OK
- 10.1086/310975 is OK
- 10.1088/0004-637X/740/2/107 is OK
- 10.1088/0004-637X/811/2/146 is OK
- 10.1086/426051 is OK
- 10.1086/590238 is OK
- 10.1088/0004-6256/136/1/404 is OK
- 10.1088/0004-637X/703/1/131 is OK
- 10.1088/0004-637X/693/1/914 is OK
- 10.1088/0004-637X/704/2/L124 is OK
- 10.1093/mnras/stu052 is OK
- 10.1038/nature13662 is OK
- 10.1088/0004-637X/783/1/50 is OK
- 10.1038/s41550-018-0566-1 is OK
- 10.3847/1538-4357/ab584b is OK

MISSING DOIs

- 10.1016/s0377-0427(99)00156-9 may be a valid DOI for title: Star formation with 3-D adaptive mesh refinement: the collapse and fragmentation of molecular clouds.

INVALID DOIs

- None
whedon commented 3 years ago 
Software report (experimental):

github.com/AlDanial/cloc v 1.88  T=1.65 s (882.4 files/s, 271977.5 lines/s)
--------------------------------------------------------------------------------
Language                      files          blank        comment           code
--------------------------------------------------------------------------------
C++                             516          32029          31720         184833
C/C++ Header                    504          17559          35231          64419
C                               127           6463          10161          21534
Python                           46           1326           1426           5013
Fortran 77                       15            325           3158           4388
IDL                              50           1707           2938           4257
Perl                             25            900           1755           3580
make                             79            857            931           1599
SWIG                              7            827              0           1472
reStructuredText                 33            697            171           1057
HTML                              1            390              1            881
INI                              14            248              0            824
Bourne Shell                     17             99            114            560
Bourne Again Shell                3             57            170            439
TeX                               1             45              0            427
diff                              1             34            160            232
MATLAB                            1             24              5            134
Markdown                          1             16              0            111
C Shell                           8             28              3            103
awk                               1              1              4             37
Fortran 90                        1              6              0             28
CMake                             1              5             11             10
--------------------------------------------------------------------------------
SUM:                           1452          63643          87959         295938
--------------------------------------------------------------------------------

Statistical information for the repository 'ff21fd31d97ce34ab8922504' was
gathered on 2021/08/03.
The following historical commit information, by author, was found:

Author                     Commits    Insertions      Deletions    % of changes
Offner                           1        298269              0          100.00

Below are the number of rows from each author that have survived and are still
intact in the current revision:

Author                     Rows      Stability          Age       % in comments
Stella Offner            298269          100.0          0.0               15.55
soffner commented 3 years ago

@whedon generate pdf

@whedon commands

On Tue, Aug 3, 2021 at 7:05 AM whedon @.***> wrote:

Software report (experimental): github.com/AlDanial/cloc v 1.88 T=1.65 s (882.4 files/s, 271977.5 lines/s)

Language files blank comment code

C++ 516 32029 31720 184833 C/C++ Header 504 17559 35231 64419 C 127 6463 10161 21534 Python 46 1326 1426 5013 Fortran 77 15 325 3158 4388 IDL 50 1707 2938 4257 Perl 25 900 1755 3580 make 79 857 931 1599 SWIG 7 827 0 1472 reStructuredText 33 697 171 1057 HTML 1 390 1 881 INI 14 248 0 824 Bourne Shell 17 99 114 560 Bourne Again Shell 3 57 170 439 TeX 1 45 0 427 diff 1 34 160 232 MATLAB 1 24 5 134 Markdown 1 16 0 111 C Shell 8 28 3 103 awk 1 1 4 37 Fortran 90 1 6 0 28 CMake 1 5 11 10

SUM: 1452 63643 87959 295938

Statistical information for the repository 'ff21fd31d97ce34ab8922504' was gathered on 2021/08/03. The following historical commit information, by author, was found:

Author Commits Insertions Deletions % of changes Offner 1 298269 0 100.00

Below are the number of rows from each author that have survived and are still intact in the current revision:

Author Rows Stability Age % in comments Stella Offner 298269 100.0 0.0 15.55

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3559#issuecomment-891753589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFACUYJZHXNRB5CZ5CP6XDT27EN7ANCNFSM5BOTAOGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

whedon commented 3 years ago

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

Kevin-Mattheus-Moerman commented 3 years ago

@soffner since all editors in this domain are currently preoccupied with other submissions I have assigned the waitlisted label here for now. We will assign an editor as soon as one becomes available. Thanks for your patience.

Kevin-Mattheus-Moerman commented 3 years ago

@dfm @xuanxu do you think one of you could edit this submission once you are available to? Thanks.

dfm commented 3 years ago

@whedon assign me as editor

Sorry about the delay! I'm happy to edit, but as @Kevin-Mattheus-Moerman mentioned, things are a little backed up at the moment so it'll be a week or two before I can get the process started. Thanks for your patience!

In the meantime, @soffner I'm a little confused about the relationship between paper authorship and commit history. I assume that the bulk of the code was written outside of version control? Would you mind clarifying the history of the project, the role/contribution of other authors, and the plans for future open development of the software?

whedon commented 3 years ago

OK, the editor is @dfm

soffner commented 3 years ago

Hi @dfm. Thanks for agreeing to edit!

Regarding the version and commit history -- ORION2 was developed in a private repository, developed and maintained by a relatively small collaboration. It was private because of functionality (the radiative transfer module) that was developed through collaboration with researchers at LLNL, which has fairly strict release restrictions. In order to make ORION2 public we needed to strip out all the embargoed code and code that is still under active development and then migrate this cleaned version to a public repository.

Regarding the authorship. PS Li is responsible for implementing the most major component of the released ORION2, which is the ideal AMR MHD method, which is why he is first author on the JOSS paper. The rest of the contributors are listed alphabetically. I am the corresponding author (and the one mostly responsible for the public branch), since I have been leading the collaboration through the steps necessary for public release.

Let me know if you have any other questions.

On Wed, Aug 11, 2021 at 12:47 PM Dan Foreman-Mackey < @.***> wrote:

@whedon https://github.com/whedon assign me as editor

Sorry about the delay! I'm happy to edit, but as @Kevin-Mattheus-Moerman https://github.com/Kevin-Mattheus-Moerman mentioned, things are a little backed up at the moment so it'll be a week or two before I can get the process started. Thanks for your patience!

In the meantime, @soffner https://github.com/soffner I'm a little confused about the relationship between paper authorship and commit history. I assume that the bulk of the code was written outside of version control? Would you mind clarifying the history of the project, the role/contribution of other authors, and the plans for future open development of the software?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3559#issuecomment-897025599, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFACU5KO3FJEXIGBLHKTDTT4KZUPANCNFSM5BOTAOGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

dfm commented 3 years ago

@soffner: I'm really sorry about the slow response over here! I've been working on recruiting reviewers, but things have been slow (in large part my fault!) so hopefully I'll have two lined up soon. Thanks for your patience!

In response to your comments above:

  1. I can see some inconsistency between the closed development model that you describe and the JOSS "Community guidelines" checklist requirement, but this is certainly manageable. Perhaps you can double check that the workflow for submitting contributions, issues, and support requests is documented and available to potential reviewers?
  2. We also have a checklist item related to authorship where reviewers might need a little more info. One approach that has worked in the past is to open an issue on the source repository and have a public discussion/sign-off from the co-authors about the contribution history.

Thanks again for your patience and I'll keep you up to date on the reviewer search.

soffner commented 3 years ago

Hi @dfm

Thanks. Any luck in the reviewer search?

For (1) I think we can be more explicit in the documentation about how to submit issues. Right now it mentions our google group email (which reaches all the current developers) but doesn't mention submitting a ticket to the repository. Do you want me to make a change now to the documentation?

(2) I don't totally understand what you are suggesting in your point (2). You want all the coauthors to acknowledge their contributions by commenting on the repository?

Thanks. Stella

On Tue, Sep 7, 2021 at 10:49 AM Dan Foreman-Mackey @.***> wrote:

@soffner https://github.com/soffner: I'm really sorry about the slow response over here! I've been working on recruiting reviewers, but things have been slow (in large part my fault!) so hopefully I'll have two lined up soon. Thanks for your patience!

In response to your comments above:

  1. I can see some inconsistency between the closed development model that you describe and the JOSS "Community guidelines" checklist requirement https://joss.readthedocs.io/en/latest/review_checklist.html#documentation, but this is certainly manageable. Perhaps you can double check that the workflow for submitting contributions, issues, and support requests is documented and available to potential reviewers?
  2. We also have a checklist item related to authorship https://joss.readthedocs.io/en/latest/review_checklist.html#general-checks where reviewers might need a little more info. One approach that has worked in the past is to open an issue on the source repository and have a public discussion/sign-off from the co-authors about the contribution history.

Thanks again for your patience and I'll keep you up to date on the reviewer search.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3559#issuecomment-914422567, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFACU7XLWPPKW6ZL6PJ7ADUAYX7DANCNFSM5BOTAOGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

dfm commented 3 years ago

@soffner: Still coming up empty, but hopefully I'll have some reviewers soon. This time of year is definitely tricky, but I'm also having worse luck than usual. Thanks again for your patience!

For (1) I think we can be more explicit in the documentation about how to submit issues. Right now it mentions our google group email (which reaches all the current developers) but doesn't mention submitting a ticket to the repository. Do you want me to make a change now to the documentation?

Yes - this will be a requirement for publication so any progress you can make on it before the review starts won't be wasted time. Thanks!

(2) I don't totally understand what you are suggesting in your point (2). You want all the coauthors to acknowledge their contributions by commenting on the repository?

That's how we have handled submissions like this in the past, but that doesn't need to be your specific approach. Another option might be to add more details about the development model and history to the documentation. The JOSS checklist is designed to be applied to projects with open development models where the contribution history is clear from the commit logs. In this case, since your project follows a different model, we'll just need to make sure that the reviewers understand this history.

dfm commented 3 years ago

@whedon add @zingale as reviewer

Mike has agreed to be one of our reviewers - thanks!! I'm hoping to have another on lined up soon so we can finally get started. Thanks again @soffner for your patience.

whedon commented 3 years ago

OK, @zingale is now a reviewer

soffner commented 3 years ago

Great!

@dfm I addressed one of your recent comments and I'm consulting with the rest of the developer team on how to address the other.

On Tue, Sep 21, 2021 at 1:43 PM Dan Foreman-Mackey @.***> wrote:

@whedon https://github.com/whedon add @zingale https://github.com/zingale as reviewer

Mike has agreed to be one of our reviewers - thanks!! I'm hoping to have another on lined up soon so we can finally get started. Thanks again @soffner https://github.com/soffner for your patience.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3559#issuecomment-924271922, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFACUZ2GN2ST64MH7JGLIDUDDG6XANCNFSM5BOTAOGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

dfm commented 3 years ago

@whedon add @changgoo as reviewer

And... we have our second reviewer. Thanks Chang-Goo!

I'll get the review started in a new issue thread with more information. Thanks all for agreeing to participate in this review process and let me know if you have any questions, comments, or issues as we go. I'm here to help!

whedon commented 3 years ago

OK, @changgoo is now a reviewer

dfm commented 3 years ago

@whedon start review

whedon commented 3 years ago

OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/3771.