Skip to content
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]: rFBP: Replicated Focusing Belief Propagation algorithm #2589

Closed
whedon opened this issue Aug 20, 2020 · 32 comments
Closed

[PRE REVIEW]: rFBP: Replicated Focusing Belief Propagation algorithm #2589

whedon opened this issue Aug 20, 2020 · 32 comments
Assignees

Comments

@whedon
Copy link

whedon commented Aug 20, 2020

Submitting author: @Nico-Curti (Nico Curti)
Repository: https://github.com/Nico-Curti/rFBP
Version: v1.0.0
Editor: @arokem
Reviewers: @bblais, @justusschock
Managing EiC: Kevin M. Moerman

⚠️ JOSS reduced service mode ⚠️

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.

Author instructions

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

The author's suggestion for the handling editor is @arokem.

@Nico-Curti 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
Copy link
Author

whedon commented Aug 20, 2020

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

⚠️ JOSS reduced service mode ⚠️

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
Copy link
Author

whedon commented Aug 20, 2020

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

/app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:in parse': (tmp/2589/paper/paper.md): did not find expected alphabetic or numeric character while scanning an alias at line 16 column 19 (Psych::SyntaxError) from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:in parse_stream'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:325:in parse' from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:252:in load'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:473:in block in load_file' from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:in open'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:in load_file' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/lib/whedon.rb:125:in load_yaml'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/lib/whedon.rb:85:in initialize' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/lib/whedon/processor.rb:36:in new'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/lib/whedon/processor.rb:36:in set_paper' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/bin/whedon:55:in prepare'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-0e09ec0a48e3/bin/whedon:119:in <top (required)>' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in `

'

@Kevin-Mattheus-Moerman
Copy link
Member

@openjournals/dev can you help trouble shoot this error ☝️

@arfon
Copy link
Member

arfon commented Aug 21, 2020

The metadata header is non-standard (see contributions block added):

---
title: 'rFBP: Replicated Focusing Belief Propagation algorithm'
tags:
  - belief-propagation
  - deep-neural-networks
  - sping-glass
  - statistical-mechanics
  - learning-algorithm
  - machine-learning-algorithms
  - python3
  - cpp17
authors:
 - name: Nico Curti
   orcid: 0000-0001-5802-1195
   affiliation: 1
   contributions: *
 - name: Daniele Dall'Olio
   orcid: 0000-0003-0196-6870
   affiliation: 2
   contributions: *
 - name: Daniel Remondini
   orcid: 0000-0003-3185-7456
   affiliation: 2
 - name: Gastone Castellani
   orcid: 0000-0003-4892-925X
   affiliation: 1
- name: Enrico Giampieri
   orcid: 0000-0003-2269-2338
   affiliation: 1
affiliations:
 - name: Department of Experimental, Diagnostic and Specialty Medicine of Bologna University
   index: 1
 - name: Department of Physics and Astronomy of Bologna University
   index: 2
contributions:
 - name: Both authors contributed equally to this work
   index: *

date: 18 August 2020
bibliography: paper.bib
---

@Nico-Curti - please format your metadata exactly as specified in the example paper. If you want to denote equal authorship you will need to use footnotes.

@Nico-Curti
Copy link

@arfon Thanks for the help!
I should have fixed the error in the last commit by moving the footnote to the end of the document.
I also tested the new version of the document using whedon and it seems to work now.

I'm sorry for the inconvenience.
Let me know if there are any other issues.

@arokem
Copy link

arokem commented Aug 21, 2020

@whedon assign me as editor

@whedon
Copy link
Author

whedon commented Aug 21, 2020

OK, the editor is @arokem

@arokem
Copy link

arokem commented Aug 21, 2020

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Aug 21, 2020

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

/app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:in parse': (tmp/2589/paper/paper.md): did not find expected key while parsing a block mapping at line 2 column 1 (Psych::SyntaxError) from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:in parse_stream'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:325:in parse' from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:252:in load'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:473:in block in load_file' from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:in open'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:in load_file' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/lib/whedon.rb:125:in load_yaml'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/lib/whedon.rb:85:in initialize' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/lib/whedon/processor.rb:36:in new'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/lib/whedon/processor.rb:36:in set_paper' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/bin/whedon:55:in prepare'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in run' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in dispatch' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-132474d2711b/bin/whedon:119:in <top (required)>' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in `

'

@arfon
Copy link
Member

arfon commented Aug 21, 2020

@Nico-Curti - this PR should fix your paper Nico-Curti/rFBP#1

@arokem
Copy link

arokem commented Aug 22, 2020

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Aug 22, 2020

@arokem
Copy link

arokem commented Aug 24, 2020

Hi @Nico-Curti and co-authors: thank you for this submission. I have now read the article and looked through the software. The next steps are for me to offer some comments on this initial submission and for us to find appropriate reviewers.

First, my comments on the article:

  1. The readership of JOSS is expected to be very broad, so you will need to provide a bit more context for the software. For example, the first sentence of the article really drops the reader off the deep end, where more general context would have been helpful.

  2. Since an important element in a JOSS paper is the potential research applications of the software, it would be good to flesh out the examples that you provided as bullet points. How was the software used in these applications? What kinds of research questions were answered? In general, as I understand it, since this is a re-implementation of an existing algorithm, what is the need that is addressed through this implementation of the algorithm?

Second: do you have particular suggestions for people who would be appropriate reviewers for your paper? If you include their GitHub handles here, please do not use the "@" sign before their name, so that I can take a look before tagging them into this issue.

@arokem
Copy link

arokem commented Aug 30, 2020

👋 @justusschock : would you be willing to review this article for JOSS? This submissions seems like a good match for your expertise.

@arokem
Copy link

arokem commented Aug 30, 2020

👋 @georgiastuart : would you be willing to review this article for JOSS? It seems like a good match for your expertise.

@justusschock
Copy link

@arokem Sure!

@arokem
Copy link

arokem commented Aug 31, 2020

@whedon assign @justusschock as reviewer

@whedon whedon assigned arokem and justusschock and unassigned arokem Aug 31, 2020
@whedon
Copy link
Author

whedon commented Aug 31, 2020

OK, @justusschock is now a reviewer

@arokem
Copy link

arokem commented Aug 31, 2020

Thanks! Let's wait until I find one more person, before starting the review.

@Nico-Curti
Copy link

@arokem Thanks for your comments. We will provide an updated version of the paper with your suggestions in few days.
As for the second reviewer we would like to suggest professor Brian Blais since he is an expert in the field and a very competent Python programmer.

@arokem
Copy link

arokem commented Sep 1, 2020

Hi @bblais -- would you be willing to review this software contribution to The Journal of Open Source Software? The reviews are conducted openly, through a GitHub issue. More instructions are available here

@arokem
Copy link

arokem commented Sep 10, 2020

👋 @DanielLenz : would you be willing to review this article for JOSS?

@arokem
Copy link

arokem commented Sep 10, 2020

👋 @zbeekman : would you be willing to review this article for JOSS?

@bblais
Copy link

bblais commented Sep 10, 2020

Hi @bblais -- would you be willing to review this software contribution to The Journal of Open Source Software? The reviews are conducted openly, through a GitHub issue. More instructions are available here

Sure, I can review (didn't notice this invite the first time). I see the editorial guide, but is there a guide for the process of submitting a review? is it by individual issues or all at once? is there a deadline or expected timeframe for review? thanks!

@arokem
Copy link

arokem commented Sep 10, 2020

@whedon assign @bblais as reviewer

@whedon whedon assigned arokem and bblais and unassigned arokem and justusschock Sep 10, 2020
@whedon
Copy link
Author

whedon commented Sep 10, 2020

OK, @bblais is now a reviewer

@arokem
Copy link

arokem commented Sep 10, 2020

@whedon add @justusschock as reviewer

@whedon whedon assigned arokem, bblais and justusschock and unassigned arokem and bblais Sep 10, 2020
@whedon
Copy link
Author

whedon commented Sep 10, 2020

OK, @justusschock is now a reviewer

@arokem
Copy link

arokem commented Sep 10, 2020

@whedon start review

@whedon
Copy link
Author

whedon commented Sep 10, 2020

OK, I've started the review over in #2663.

@whedon whedon closed this as completed Sep 10, 2020
@arokem
Copy link

arokem commented Sep 10, 2020

@bblais , @justusschock : please head over to #2663. There you will have a checklist with items to check off. As you go along, feel free to comment and make suggestions in that review issue, or to post issues on the software repository (might want to mention that the issue stems from the JOSS review). And please do let me know if you have any further questions.

@arokem
Copy link

arokem commented Sep 10, 2020

@DanielLenz, @zbeekman : sorry for the false alarm. Looks like we will not your service as reviewers this time around

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants