FLAMEGPU2
FLAMEGPU2 copied to clipboard
FLAMEGPU
FLAME GPU 2 is a GPU accelerated agent based modelling framework for CUDA C++ and Python
[#1089](https://github.com/FLAMEGPU/FLAMEGPU2/pull/1089) will add support for host-device accessible graph data structures, which can be constructed from the host, then iterated from the device. Edge/Vertex attributes can be mutated from the host,...
Current/planned graphs only allow a single edge between each source-destination vertex pair. Some use cases may include multiple edges between a source and destination (i.e. a road network which has...
Inital graphs / networks implemented are directed graphs. Undirected graphs are more memory efficient, but not always appropriate, and all undirected graphs can be represented by a directed graph with...
[#1089](https://github.com/FLAMEGPU/FLAMEGPU2/pull/1089) will add support for host-device accessible graph data structures, which can be constructed from the host, then iterated from the device. Edge/Vertex attributes can be mutated from the host,...
Completely deterministic simulations are probably required by some users. Currenlty atomics are only used during message datastructure construction for non-brute force messages (i.e. pbm construction for bucket messaging, spatial etc)....
The initial python binary distributioin(s) will be / are Release mode, seatbelts ON only. This is the default, sensible choice for python users to be able to develop models that...
To ease installation of `pyflamegpu` we likely want to provide one or more pypi package(s), so that users may install the latest pyflamegpu, using the default CUDA for that version...
If users provide custom state names, methods which optionally take a state name as an argument will fail at run time if one is not provide with an exception stating...
### Discussed in https://github.com/FLAMEGPU/FLAMEGPU2/discussions/1076 Python native function's cannot be detected when executed via PyCharm's PyDev debugger. This is unconfirmed, but seems like the most likely cause based on this stack...
Currently 2 environment variables are required to jitify/rtc compilation: + `CUDA_PATH` pointing to the root of the relevant CUDA version + `FLAMEGPU2_INC_DIR` pointint to `flamegpu2_dev/include` This could be improved by:...