Abses

Latest version: v0.6.10

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 6

0.5.7

Fixed bugs

- [x] bug🐛 Fixing default getter setter for `ActorsList`, `Actor`, and `PatchCell`
- [x] bug🐛 AttributeError when getting value with wrong key

Documentation changes

- [x] docs📄 adding authors' ORCID of the paper
- [x] docs📄 correcting installation from source tutorial
- [x] docs📄 fixing Mantilla Ibarra name and capitalizing refers

<a id='changelog-0.5.6'></a>

0.5.6

Refactoring

- [x] refactor♻️ improve code formats

Documentation changes

- [x] docs📄 updated fundings in paper
- [x] docs📄 updated README contributors

<a id='changelog-0.5.5'></a>

0.5.5

Refactoring

- [x] refactor♻️ Improved code formats

Documentation changes

- [x] **LINE 30**: Missing space between "...tools (Schlüter et al., 2023)" and "to implement...". Should appear as "...tools (Schlüter et al., 2023) to implement..."
- [x] **LINE 42**: The figure reference "(Figure 1)" should not be bold but instead use formatting that enables linking to the actual figure. You can see how this is done in other JOSS publications such as [https://joss.theoj.org/papers/10.21105/joss.06294](https://joss.theoj.org/papers/10.21105/joss.06294)[](https://www.sci-hub.ee/10.21105/joss.06294). I'll only mention this for This figure, but note that this should be done for all figure references in your paper.
- [x] **LINE 48**: The statement "...but somehow enhanced." should be changed here. Perhaps use "...but with enhanced functionality." or the something similar.
- [x] **LINE 49**: Since YAML is a data serialization language, it should be referenced by its name here instead of the extension which sometimes varies. So instead of "...through .yaml files." you could use "...through the use of YAML configuration files." or something similar. You can read more about YAML [here](https://yaml.org/) if you like. Note that there are several of these usages throughout the paper that you may need to correct.
- [x] **LINE 53**: Wording is off here. Instead of "...(2) enhancing reality and manageability of ABMs." something like the following would be more clear "...(2) enhancing the reality and manageability of ABMs." This is phrased several times like this throughout the paper, so please let me know if it should be written as stated. I'll not mention the other occurrences, but address those if needed.
- [x] **LINE 56**: "...and can be..." should be "...which can be..."
- [x] **LINE 63**: "(Schlüter et al., 2017), (Beckage et al., 2022)" should appear as "(Schlüter et al., 2017; Beckage et al., 2022)"
- [x] **LINE 87-88**: You use the formatting `{"start: '2022-12-31', "end": 2024-01-01, year: 1}` please add in what I believe should be the correct, consistent formatting as following: `{"start: "2022-12-31", "end": "2024-01-01", "year": 1}`. Please correct me if I am wrong. I am also assuming "year" requires an integer as you have written.
- [x] **LINE 88**: "...to the 'time' module..." should be formatted as "...to the `time` module..." where backticks are used.
- [x] **LINE 102**: You use "input/output" though earlier in the paper you use "Input/Ouput" please choose one method to be consistent.
- [x] **LINE 131**: Your reference for the Janssen et al. paper is not formatted correctly. See [https://www.jasss.org/11/2/6/citation.html](https://www.jasss.org/11/2/6/citation.html)
- [x] **LINE 135**: Should have a colon after "In". See [https://link.springer.com/chapter/10.1007/978-3-030-61255-9_30#citeas](https://link.springer.com/chapter/10.1007/978-3-030-61255-9_30#citeas)[](https://www.sci-hub.ee/10.1007/978-3-030-61255-9_30)
- [x] **LINE 159**: Missing colon after "In" see [https://link.springer.com/chapter/10.1007/978-3-319-67217-5_2#citeas](https://link.springer.com/chapter/10.1007/978-3-319-67217-5_2#citeas)[](https://www.sci-hub.ee/10.1007/978-3-319-67217-5_2)

<a id='changelog-0.5.4'></a>

0.5.4

Documentation changes

- [x] docs📄 Line 24: 'research' not 'researches'
- [x] docs📄 Line 44: rather than 'et al.' maybe use actual words (e.g. 'and others') so as not to confuse against the file suffixes which are similar abbreviations
- [x] docs📄  Line 55: What do you mean by 'practicing' here? This doesn't seem right. Please edit to clarify
- [x] docs📄  Lines 57-65: I'm surprised these three points (Perceptions, Decision-making, Response) don't match the words used in Fig 2 (Options, Evaluate, Behaviour). Or are the latter three (in the Fig) all part of the 'decision-making' step? Aligning the steps in the list with the figure would be useful, I think
- [x] docs📄  Line 76: I think 'vary' should be 'varying'
- [x] docs📄  Line 93: 'more accurate' - this is a relative statement, so please clarify 'more accurate' than what?
- [x] docs📄  Line 99: ( wang2022h? )) is not included in the reference list
- [x] docs📄  Line 100: it's good that you recognise the similarity here to `AgentPy` but you don't then clearly explain how `absespy` is beneficial for SES researchers - maybe you could highlight the explicit functionality for representing the 'nature' side of CHANS (`AgentPy` really focuses on the 'human' side).
- [x] docs📄  Line 108: 'merely heuristic' - I think this is a little over-critical of NetLogo, which can incorporate 'real-world' (I think you mean 'empirical'?) data although not at the scale `absespy` could. I suggest you edit here to focus on the value of `absespy` for working with large-scale, empirical data so that models can run more efficiently than would be possible for the same data in NetLogo. You might also highlight your `TimeDriver` module which is a benefit over NetLogo's more simple 'ticks'

- [x] docs📄  L105 & L151: netlogo and Netlogo should be NetLogo
- [x] docs📄  L42, L98, L101 & L153 : mesa-geo and Mesa-geo should be Mesa-Geo
- [x] docs📄  L95, L97, L98, L102, L129 & L153 : mesa should be Mesa
- [x] docs📄  L96: abce should be ABCE
- [x] docs📄  L128, L148 & L154: python should be Python

- [x] docs📄 Update project readme
- [x] docs📄 Improve JOSS paper overall.

<a id='changelog-0.5.3'></a>

0.5.3

Fixed bugs

- [x] bug🐛 Only alive actors can apply default methods by decorator `alive_required` now.
- [x] bug🐛 now moving has a return to control continue to move or not.
- [x] bug🐛 now update the position attribute correctly after moving
- [x] bug🐛 fixing release drafter to the latest version

<a id='changelog-0.5.2'></a>

0.5.2

Performance improvements

- [x] zap⚡️ improve getting performance from container

New Features

- [x] feat✨ now getting link name can be with a default empty return
- [x] feat✨ getting an attr value from a `ActorsList`
- [x] feat✨ before moving, `Actor` may do something
- [x] feat✨ possible to control max length when customize `PatchCell`
- [x] feat✨ getting an item or None from `ActorsList` or container

<a id='changelog-0.5.1'></a>

Page 3 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.