Robert Chisholm

`MessageBruteForce::CDescription::newVariable()` and `MessageBruteForce::CDescription::newVariableArray()` are both currently public within builds of the Python interface (https://github.com/FLAMEGPU/FLAMEGPU2/pull/980). This is due to the refactor, and removal of references throughout the API. Changes to messages,...

Our SWIG interface does not currently allow numpy arrays to be passed to std::vector, they must first be converted to Pythonic lists. https://numpy.org/doc/stable/reference/swig.interface-file.html

[Test Failure] Swig RunPlan != can't compare with None?

2

Couple of Python test failures (debug/windows) whilst investigating the SWIG 4.2.1 issue, note this is with the Python wheel built with SWIG 4.2.1. Although, I've built it with 4.0.2 and...

After this change, all tests (besides the 2 in #1233) pass. Worth @ptheywood giving this a test build, to make sure I'm not fooling myself. See #956 for more info

RunPlanVector file IO

1

Currently just an (untested) minimal viable product Still required for merge - [ ] Throw exception if steps=0 is loaded, and model doesn't have an exit condition. - [ ]...

Ensemble Enhancements

2

These were left over from the PR, but none-blocking * Import/export `RunPlanVec` to file ability. * There was originally a plan to have code that estimates max concurrent models by...