[PRE REVIEW]: Benchmarking Hierarchical Reasoning with HierarchyCraft

[editorialbot]

Submitting author: @MathisFederico (Mathis Federico)
Repository: https://github.com/IRLL/HierarchyCraft
Branch with paper.md (empty if default branch):
Version: v1.2.4
Editor: @logological
Reviewers: @lwu9, @Christopher-Henry-UM
Managing EiC: Arfon Smith

Status

Status badge code:

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

Author instructions

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

@MathisFederico 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]

Software report:

github.com/AlDanial/cloc v 1.88  T=0.16 s (649.0 files/s, 138921.9 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          71           2002           1538           7945
SVG                              5              5              5           7817
Jinja Template                   5             27             39            527
CSS                              4            108             48            523
Markdown                         4            133              0            268
TeX                              1             22              0            225
YAML                             7             21             12            209
TOML                             1             19              7             88
JavaScript                       1              4              6             20
PowerShell                       2              0              0              2
-------------------------------------------------------------------------------
SUM:                           101           2341           1655          17624
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

[editorialbot]

Wordcount for paper.md is 1449

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- None

MISSING DOIs

- 10.1016/s0004-3702(99)00052-1 may be a valid DOI for title: Between MDPs and semi-MDPs: A framework for temporal abstraction in reinforcement learning
- 10.1613/jair.5699 may be a valid DOI for title: Revisiting the arcade learning environment: Evaluation protocols and open problems for general agents
- 10.1613/jair.3912 may be a valid DOI for title: The arcade learning environment: An evaluation platform for general agents

INVALID DOIs

- None

[editorialbot]

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

[editorialbot]

Five most similar historical JOSS papers:

DeepSynth: Scaling Neural Program Synthesis with Distribution-based Search
Submitting author: @Theomat
Handling editor: @arfon (Active)
Reviewers: @njuaplusplus, @bzz
Similarity score: 0.7941

fishStan: Hierarchical Bayesian models for fisheries
Submitting author: @rerickson-usgs
Handling editor: @marcosvital (Active)
Reviewers: @MikeKaller, @Cole-Monnahan-NOAA
Similarity score: 0.7934

HARDy: Handling Arbitrary Recognition of Data in Python
Submitting author: @MariaPoliti
Handling editor: @gkthiruvathukal (Active)
Reviewers: @andrewtarzia, @alberto-battistel
Similarity score: 0.7901

Application Skeleton: Generating Synthetic Applications for Infrastructure Research
Submitting author: @zhaozhang
Handling editor: @arfon (Active)
Reviewers: @krother
Similarity score: 0.7882

s4rdm3x: A Tool Suite to Explore Code to Architecture Mapping Techniques
Submitting author: @tobias-dv-lnu
Handling editor: @gkthiruvathukal (Active)
Reviewers: @kinow, @xirdneh
Similarity score: 0.7880

⚠️ 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.

[arfon]

@MathisFederico - thanks for your submission to JOSS. We're currently managing a large backlog of submissions and the editor most appropriate for your area is already rather busy.

For now, we will need to waitlist this paper and process it as the queue reduces. Thanks for your patience!

[MathisFederico]

@arfon Any news ?

[arfon]

@editorialbot invite @logological as editor

👋 @logological – would you be willing to edit this submission for JOSS?

[editorialbot]

Invitation to edit this submission sent!

[logological]

@editorialbot assign @logological as editor

[editorialbot]

Assigned! @logological is now the editor

[logological]

@editorialbot commands

[editorialbot]

Hello @logological, 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

[logological]

Thank you for your submission, @MathisFederico! I will be serving as its editor. At this point I'd like to invite you to suggest to me any reviewers who may be qualified to review this submission. You can search our reviewer database or nominate people you may know from your professional network or through familiarity with their work, but please do not nominate anyone who may have a conflict of interest. I'll meanwhile compile my own list of candidate reviewers.

[logological]

Well, in the interest of getting things started, I'll go ahead and approach some reviewers. @lucaferranti, @lwu9, and @TimKam, would you be willing and able to review this JOSS submission?

[lwu9]

Hi Tristan, I'm interested in reviewing this work. Thanks Best, Lili

…

On Fri, 23 Feb 2024 at 16:15, Tristan Miller ***@***.***> wrote: Well, in the interest of getting things started, I'll go ahead and approach some reviewers. @lucaferranti <https://github.com/lucaferranti>, @lwu9 <https://github.com/lwu9>, and @TimKam <https://github.com/TimKam>, would you be willing and able to review this JOSS submission? — Reply to this email directly, view it on GitHub <#6251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG4SWUKANRTOO6XEA7NO4ITYVEBFZAVCNFSM6AAAAABCDALEXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHE4TQMRQGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[logological]

Thanks, @lwu9. I'll add you as a reviewer and start the review process once I locate a second reviewer.

[lwu9]

Sounds good, thanks!

…

On Mon, 26 Feb 2024 at 16:25, Tristan Miller ***@***.***> wrote: Thanks, @lwu9 <https://github.com/lwu9>. I'll add you as a reviewer and start the review process once I locate a second reviewer. — Reply to this email directly, view it on GitHub <#6251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AG4SWUPZZ36YSSZVYUSAG3TYVT4WFAVCNFSM6AAAAABCDALEXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVGMYTSOBXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[logological]

@nathanael-fijalkow and @jorgedch, would you be willing and able to review this JOSS submission?

[logological]

@MathisFederico I haven't received a response to my message of February 20. Are you still interested in having this submission reviewed? If so, please let me know if you have any suggestions for reviewers.

[lucaferranti]

@logological apologies for the delay. Unfortunately, I am at full bandwidth at the moment. I could start my review late March. If you haven't found a reviewer by the end of the month, do not hesitate to ping me again

[logological]

Thanks, @lucaferranti. We'll see if we can scare up another reviewer in the next couple weeks.

[MathisFederico]

@MathisFederico I haven't received a response to my message of February 20. Are you still interested in having this submission reviewed? If so, please let me know if you have any suggestions for reviewers.

Hello @logological, sorry I didn't see the notification ! I don't really have suggestions for reviewers I'm quite new to this, but I'm still interested in getting reviews for this work.

[logological]

@MathisFederico No problem; I'll continue to approach reviewers, as so far we have only one.

[logological]

@seba-1511 and @cst0, would you be willing and able to review this JOSS submission?

[jorgedch]

Hi @logological, unfortunately I have to pass as my plate is full at the moment. Cheers, J

[logological]

@editorialbot add @lwu9 as reviewer

[editorialbot]

@lwu9 added to the reviewers list!

[logological]

@editorialbot add @Christopher-Henry-UM as reviewer

[editorialbot]

@Christopher-Henry-UM added to the reviewers list!

[logological]

@editorialbot start review

[editorialbot]

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

[cst0]

@seba-1511 and @cst0, would you be willing and able to review this JOSS submission?

Hi @logological, sorry for my delay (I've been away from internet for the last few weeks)-- is there further action for me to take here? Happy to help if reviewers are still needed.

[logological]

Thanks for getting back to me, @cst0. We've currently got two reviewers for the submission, which is the bare minimum. But if you're willing and able to serve as a third reviewer, I'd be happy to add you. Let me know if you're interested.