FLAMEGPU2
FLAMEGPU2 copied to clipboard
FLAMEGPU
FLAME GPU 2 is a GPU accelerated agent based modelling framework for CUDA C++ and Python
### Discussed in https://github.com/FLAMEGPU/FLAMEGPU2/discussions/1204 Originally posted by **bytetec** May 13, 2024 Hi everyone Since the update from FLAME GPU 2.0.0-rc to FLAME GPU 2.0.0-rc.1 the export of the logfile in...
Remove libnvrtc-builtins.so dependency via patchelf on manylinux2014 (centos 7) Closes #1193 (though this will continue to effect users for 2.0.0-rc.1 using CUDA 12 wheels forever). --- Once merged and released,...
`DeviceMacroProperty` has operator overloading for `+` and `-` which is incorrect within the API docs as it suggests that this atomically modifies the value (it does not). We should add...
CUDA supports using ICC as the host compiler. Users may wish for FLAME GPU 2 to be usable with ICC as the host compiler as well, on x86_64 systems. This...
Add Manylinux_2_28 workflow to test compatibility prior to expected manylinux2014 EOL (due to cent7 EOL) + [x] add standalone manylinux 2_28 workflow for regular testing + [ ] add /...
Originally identified as part of #1191, although nvrtc sonames are now major version only (since 11.3, using `.so.11.2` or `.so.12.0`), `libnvrtc-builtins.so` is still explicitly versioned, and is dependended upon by...
> Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. + [ ] Update CI actions to node...
Replace deprecated github actions with latest versions * actions/checkout due to nodejs 16 actions deprecation * actions/setup-python due to nodejs 16 actions deprecation * actions/upload-artifact due to v3 deprecation *...
@Robadob found that manylinux builds were failing, this appears to be due to a new swig release 4.1.0 8 days ago which has since been incorporated into the manylinux containers...
In case of a function-not-found warning during code generation, only tree-relative line numbers are given in the warning message, an explicit function name is added for finding the culprit quickly.
