[PRE REVIEW]: LBR-Stack: ROS 2 and Python Integration of KUKA FRI for Med and IIWA Robots

[editorialbot]

Submitting author: @mhubii (Martin Huber)
Repository: https://github.com/lbr-stack/lbr_stack_doc
Branch with paper.md (empty if default branch): main
Version: v1.0.0
Editor: @adi3
Reviewers: @CameronDevine, @bmagyar, @vincentberenz
Managing EiC: George K. Thiruvathukal

Status

Status badge code:

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

Author instructions

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

The AEiC suggestion for the handling editor is @adi3.

@mhubii 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:

@editorialbot commands

[editorialbot]

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:

@editorialbot commands

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

@editorialbot generate pdf

[editorialbot]

Couldn't check the bibtex because branch name is incorrect: https://github.com/KCL-BMEIS/lbr_fri_ros2_stack_doc

[editorialbot]

Couldn't check the bibtex because branch name is incorrect: https://github.com/KCL-BMEIS/lbr_fri_ros2_stack_doc

[editorialbot]

⚠️ An error happened when generating the pdf.

[gkthiruvathukal]

@editorialbot invite @adi3 as editor

[editorialbot]

Invitation to edit this submission sent!

[adi3]

@editorialbot assign @adi3 as editor

[editorialbot]

Assigned! @adi3 is now the editor

[adi3]

@mhubii - I'll be the editor for thisreview. To get things going, could you please suggest 5-6 reviewers from this list that you consider appropriate to vet this paper? While selecting, you should confirm that the domain expertise of the reviewer matches the subject matter of your paper and software. Thanks!

Thank you!

[mhubii]

hi @adi3 and thank you very much for your help! Yes, I will suggest reviewers once access got granted.

[gkthiruvathukal]

Thank you, @adi3, for helping to edit this submission.

[adi3]

@mhubii can you check if you have access now and suggest reviewers? Thanks!

[mhubii]

hi @adi3 , yes we have access now.

After searching the list thoroughly, we found 5 great candidates for reviewing:

• @sea-bass (PickNik)
• @destogl (ros2_control)
• @SteveMacenski (nav2 and ros2 paper)
• @traversaro (IIT, ros conda, osqp eigen...)
• @SeungBack (ros2 contributor)

We understand that they might be exceptionally busy and are happy to search for other reviewers, too.

[adi3]

@mhubii thanks for the suggestions. I know some of these folks are really busy so would be a great idea to find as many reviewers as possible from the list. I'll reach out to your suggestions in the meantime.

[adi3]

@destogl @SteveMacenski @traversaro @SeungBack - Are any of you available to review this ROS paper?

[mhubii]

this is our full list

• @bxtbold
• @abougouffa
• @Crocodyl
• @askuric
• @jingnanshi
• @jcarpent
• @CameronDevine
• @mosteo

[SteveMacenski]

While I don't argue against the utility of what they've put together, I don't see any research impact / value that would be meet the journal's requirements. It appears to me to be another wrapper on a company's SDK to expose to ROS - no different than a new sensor driver or robot hardware integration layer. I'd be happy to review the paper once its generated, but I'm not sure this work is appropriate for any journal publication.

[mhubii]

Thank you for the early feedback @SteveMacenski , we are trying our best to find a solution to the paper generation.

In the meantime, the paper is accessible in the documenting repository https://github.com/lbr-stack/lbr_fri_ros2_stack_doc/actions/runs/5749570650.

The compilation does not work through @editorialbot right now because the documentation bundles the entire lbr-stack and lives in a separate repository. We do want to apologize for the inconvenience.

[mhubii]

@editorialbot commands

[editorialbot]

Hello @mhubii, here are the things you can ask me to do:

# List all available commands
@editorialbot commands

# Get a list of all editors's GitHub handles
@editorialbot list editors

# Check the references of the paper for missing DOIs
@editorialbot check references

# Perform checks on the repository
@editorialbot check repository

# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist

# Set a value for branch
@editorialbot set joss-paper as branch

# Generates the pdf paper
@editorialbot generate pdf

# Generates a LaTeX preprint file
@editorialbot generate preprint

# Get a link to the complete list of reviewers
@editorialbot list reviewers

[mhubii]

Hi @adi3 , is it possible to re-submit? Not sure how to get the @editorialbot to change the repository.

The submission is regarding the lbr-stack, which also includes ROS bindings but much more. Think that is what caused the confusion for @SteveMacenski. This is our mistake. Really sorry.

[adi3]

@arfon is there way for the authors to change the submitted repo? Or would they need to kick off a new submission?

[mhubii]

@editorialbot set https://github.com/lbr-stack/lbr_fri_ros2_stack_doc as repository

[editorialbot]

I'm sorry @mhubii, I'm afraid I can't do that. That's something only editors are allowed to do.

[mhubii]

@editorialbot set https://github.com/lbr-stack/lbr_fri_ros2_stack_doc as repository

[editorialbot]

I'm sorry @mhubii, I'm afraid I can't do that. That's something only editors are allowed to do.

[mhubii]

hi @adi3, editorial bot allows editors to change repositories (https://joss.readthedocs.io/en/latest/editorial_bot.html#the-complete-list-of-available-commands). Could you please set the repository to:

@editorialbot set https://github.com/lbr-stack/lbr_stack_doc as repository

this should fix the issue hopefully. My dearest apologies again

[editorialbot]

Five most similar historical JOSS papers:

biorbd: A C++, Python and MATLAB library to analyze and simulate the human body biomechanics
Submitting author: @pariterre
Handling editor: @trallard (Retired)
Reviewers: @trallard, @abhishektha
Similarity score: 0.8044

Phobos: A tool for creating complex robot models
Submitting author: @Amudtogal
Handling editor: @gkthiruvathukal (Active)
Reviewers: @CameronDevine, @trallard
Similarity score: 0.7996

CoreRobotics: An object-oriented C++ library with cross-language wrappers for cross-platform robot control
Submitting author: @CoreRobotics
Handling editor: @danielskatz (Active)
Reviewers: @bmagyar @amjaeger17
Similarity score: 0.7930

kiwiPy: Robust, high-volume, messaging for big-data and computational science workflows
Submitting author: @muhrin
Handling editor: @danielskatz (Active)
Reviewers: @dghoshal-lbl, @uellue
Similarity score: 0.7927

SLAM Toolbox: SLAM for the dynamic world
Submitting author: @stevemacenski
Handling editor: @arfon (Active)
Reviewers: @mosteo, @carlosjoserg
Similarity score: 0.7882

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before before considering asking the reviewers of these papers to review again for JOSS.

[arfon]

@adi3 – this list of most similar historical papers could be a good source of reviewers? Please start with the previous authors first before asking previous reviewers.

[adi3]

@pariterre @Amudtogal @CoreRobotics @muhrin @trallard @abhishektha - would you be available to review this submission? Thank you in advance!

[pariterre]

Hi @adi3 !
I've had a quick look at the paper and I believe the article is beyond my expertise

Sorry about that!

[CameronDevine]

I was another author of the CoreRobotics paper/software and a reviewer for one of the papers listed above. I am willing to review this paper if you are still searching for reviewers.

[adi3]

@CameronDevine absolutely! Thank you for your help!

[adi3]

@editorialbot add @CameronDevine as reviewer

[editorialbot]

@CameronDevine added to the reviewers list!

[mhubii]

@editorialbot generate pdf

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[editorialbot]

Five most similar historical JOSS papers:

biorbd: A C++, Python and MATLAB library to analyze and simulate the human body biomechanics
Submitting author: @pariterre
Handling editor: @trallard (Retired)
Reviewers: @trallard, @abhishektha
Similarity score: 0.8073

Phobos: A tool for creating complex robot models
Submitting author: @Amudtogal
Handling editor: @gkthiruvathukal (Active)
Reviewers: @CameronDevine, @trallard
Similarity score: 0.8045

CoreRobotics: An object-oriented C++ library with cross-language wrappers for cross-platform robot control
Submitting author: @CoreRobotics
Handling editor: @danielskatz (Active)
Reviewers: @bmagyar @amjaeger17
Similarity score: 0.8002

kiwiPy: Robust, high-volume, messaging for big-data and computational science workflows
Submitting author: @muhrin
Handling editor: @danielskatz (Active)
Reviewers: @dghoshal-lbl, @uellue
Similarity score: 0.7884

The o80 C++ templated toolbox: Designing customized Python APIs for synchronizing realtime processes
Submitting author: @vincentberenz
Handling editor: @gkthiruvathukal (Active)
Reviewers: @traversaro, @vissarion
Similarity score: 0.7884

⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before considering asking the reviewers of these papers to review again for JOSS.

[adi3]

@abhishektha @Amudtogal @bmagyar @amjaeger17 @muhrin @dghoshal-lbl @uellue @vincentberenz @traversaro @vissarion - would you be available to review this submission? We'd appreciate your help!

[vissarion]

@adi3 I am editing for JOSS, hence there is not time unfortunately for reviewing

[uellue]

Dear @adi3, unfortunately I don't have experience with industrial robots, so I can't review this submission competently.

[bmagyar]

I'm happy to jump in!

[vincentberenz]

@adi3 I am happy to review. I will only have time in January.

[adi3]

@bmagyar @vincentberenz thank you for taking this up!

[adi3]

@editorialbot add @bmagyar as reviewer

[editorialbot]

@bmagyar added to the reviewers list!

[adi3]

@editorialbot add @vincentberenz as reviewer

[editorialbot]

@vincentberenz added to the reviewers list!

[adi3]

@editorialbot commands

[editorialbot]

Hello @adi3, here are the things you can ask me to do:

# List all available commands
@editorialbot commands

# Add to this issue's reviewers list
@editorialbot add @username as reviewer

# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers

# Get a list of all editors's GitHub handles
@editorialbot list editors

# Assign a user as the editor of this submission
@editorialbot assign @username as editor

# Remove the editor assigned to this submission
@editorialbot remove editor

# Remind an author, a reviewer or the editor to return to a review after a 
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks

# Check the references of the paper for missing DOIs
@editorialbot check references

# Perform checks on the repository
@editorialbot check repository

# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist

# Set a value for version
@editorialbot set v1.0.0 as version

# Set a value for branch
@editorialbot set joss-paper as branch

# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository

# Set a value for the archive DOI
@editorialbot set set 10.5281/zenodo.6861996 as archive

# Mention the EiCs for the correct track
@editorialbot ping track-eic

# Generates the pdf paper
@editorialbot generate pdf

# Recommends the submission for acceptance
@editorialbot recommend-accept

# Generates a LaTeX preprint file
@editorialbot generate preprint

# Flag submission with questionable scope
@editorialbot query scope

# Get a link to the complete list of reviewers
@editorialbot list reviewers

# Creates a post-review checklist with editor and authors tasks
@editorialbot create post-review checklist

# Open the review issue
@editorialbot start review

[adi3]

@editorialbot start review

[editorialbot]

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