question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[JOSS review] Manuscript corrections

See original GitHub issue

Statement of need

AFAIK, this section must be explicit in the manuscript. I suppose that such a section would include the sentence of lines 13-14. I would further suggest to make it a “self-contained” sentence (that does not require reading any other part of the manuscript to fully understand it), hence I would add:

The aim of agentpy is to provide an intuitive syntax for the creation of **agent-based** models together with
advanced tools for scientific applications.

Figure and code snippets

  • Figure 1: it may be better to use a code snippet rather than a figure to display code, e.g., users might want to copy-paste them
  • lines 27-30: it is better that the text refers to some code snippet in the manuscript (e.g., Figure 1). For instance: from the current manuscript, one may ask: what is agents? I had to open a notebook, instantiate some example agentpy.Model, inspect the class via dir and it is only then that I found the agents attribute

Clarify some concepts and definitions

  • line 30: what is the “record” action? I needed to go to the docstring of the record method to fully understand what it means. It may be a good idea to add a brief sentence to clarify it within the manuscript so that the reader can get a clearer picture there.
  • line 45: “direct integration of analysis tools within the same framework” as somebody familiar with scientific Python, I suppose that you mean NumPy, pandas, NetworkX and the like, but it may be better to make it more explicit.

Other

  • line 29: IMHO “attribute” seems more Pythonic than “variable”
  • links: it might be better to put URLs explicitly (e.g., although unlikely in JOSS, people might print the paper). Line 18 is fine since we can easily find the documentation without clicking the link, but not so much for line 46, where I believe that the word “here” should be replaced by the actual URL.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
martiboschcommented, May 31, 2021

Indeed, my mistake, thank you for pointing it out!

Closing this then.

0reactions
JoelForamitticommented, May 31, 2021

The agents are declared not in the agent (WealthAgent, lines 48-49), but in the model (WealthModel, lines 53-54, which is the snippet that i copied here). Does that explain it?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Submitting a paper to JOSS - Journal of Open Source Software
We ask that authors indicate whether related publications (published, in review, or nearing submission) exist as part of submitting to JOSS.
Read more >
Author Instructions - JOSS - Jaypee Journals
The journal follows a double-blind review process, where both the reviewer and author remain anonymous throughout the process. Please remove all identifying ...
Read more >
Publishing Policies ⋆ - jossonline
The original article will reflect that a correction has been made within, with an online link to the Corrigendum and corrected text. To...
Read more >
About the Journal of Open Source Software
All authors are obliged to provide retractions or corrections of any mistakes of which they become aware. · JOSS does not charge any...
Read more >
Instructions for authors - Journal of Spinal Surgery
On submission, editors review all submitted manuscripts initially for ... It may not be possible to incorporate corrections received after that period.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found