Laurent Courty

One great addition would be to be able to add or remove objects from the simulation. As of now, the objects are stored in arrays of structs. My basic C...

@bemcdonnell it's a ton of commits, yes. Most of them are already in main. I don't know if there is a plan to fix the CI. So far, I haven't...

I tried rebasing, but the issue is that I would need to fix the conflicts for every new commit on the dev branch. Since all the code moved location, this...

Adding to the potential for confusion, the [Region class from pygrass](https://grass.osgeo.org/grass85/manuals/libpython/_modules/pygrass/gis/region.html) does not include the 3D resolution attributes. Only `tbres` could be set and retrieved, but there is no `nsres3`...

[The wiki page about computational region](https://grasswiki.osgeo.org/wiki/Computational_region) might need an update as well.

> > Adding to the potential for confusion, the [Region class from pygrass](https://grass.osgeo.org/grass85/manuals/libpython/_modules/pygrass/gis/region.html) does not include the 3D resolution attributes. Only `tbres` could be set and retrieved, but there is...

I added a note in the wiki. I can open a PR to modify the g.region docs and the 3d raster introduction. As for the `g.region` parameters, it seems that...

I am working on an update of `g.region` to set `nsres3` and `ewres3` independently.

It's an issue that bothers me a bit, so I could try to fix it. However, I am not sure when I'll have time for it. Hopefully before the warnings...

As I understand it, the timestamp converters are now implicit in GRASS, and they need to be explicit in future Python versions. My approach to testing would be to verify...