FLAMEGPU2 icon indicating copy to clipboard operation
FLAMEGPU2 copied to clipboard

FLAME GPU 2 is a GPU accelerated agent based modelling framework for CUDA C++ and Python

Results 124 FLAMEGPU2 issues
Sort by recently updated
recently updated
newest added

CUDA Occupancy api provides largest block size that achieves best occupancy. Profiling of spatial messaging has however demonstrated that the smallest block size that achieves the best occupancy is the...

optimisation

For F1 parity need to be able to write out state lists to disk every N iterations, when `simulate` is used. via the config / cli: + specify format +...

v1.5-parity

Currently device side curve accesses only confirm that type size matches. This is clearly flawed (most types are 4-byte). This same flaw is present in `unregisterVariableByHash()` Temporary solution, also confirm...

bug
Priority: High

Now with extra environment variables, and rtc/swig/python implementation having an install step makes sense. This would need to set environment variables, copy files to appropriate locations etc. Care must be...

enhancement

Cmake uses the appropriate compiler based on the extension of teh file. i.e `.cpp` files will use `g++` while `.cu` files will use `nvcc`. Visual studio with cuda enabled will...

Priority: Low
v1.5-parity
breaking-change

Add instrumentation tools for simple performance analysis, along with NVTX based markers for more advanced profiling. Introduce a profile build configuration which enables this + [ ] Instrumentation + [x]...

enhancement
Priority: Low
v1.5-parity

Currently we have `CUDAEnsemble`, but no base `Ensemble` class (i.e. to match `Simualtion` and `CUDASimulation`. We could: + Add a very simple `Ensemble` base class which would intend to be...

String literals for reserved variable names such as `_stepCount`, `_id`, `_agent_birth` etc. are bad. RTC/Jitify means there is a lot of forward declaration in headers, rather than includes, so we...

enhancement

I have requested this from ITS and started an issue to capture thoughts on this to share with @willfurnass. Requested info from Will and initial thoughts. > Are you wanting...

`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,...

bug
SWIG