Craig Warren
Craig Warren
In the case where you have multiple models to simulate and are using the GPU-based solver: - is it possible to run the build phase (which always happens on CPU)...
Quoted post from our Google Group - https://groups.google.com/g/gprmax/c/KLyUH4pnPxE/m/tEWRC3XpAQAJ > Hi everyone, > > I generate database with gprMax on different computers and I found differences between the values of the...
This seems to be an issue with the opencl implementation in 10.14 - https://github.com/inducer/pyopencl/issues/276 Setting the environment variable `PYOPENCL_NO_CACHE=1` fixes the issue for now.
I think this is an error with how the memory usage is being reported when run with the solver on GPU, i.e. it is not the estimated memory that is...
When the GPU-based solver is used along with the `--geometry-fixed` argument, the simulation crashes with the attached CUDA error. It think this has to do with re-using the `G` structure...
We recently noticed a bug in the code concerning the setting of magnetic material properties for `#plate` objects. When a plate is specified the electric material properties of the `#material`...
Currently the `#snapshot` and `#transmission_line` commands cannot be used in models when the `-gpu` command line argument is given, i.e. to use the GPU-accelerated solver. The reasons for this are:...
Paraview (5.2 and 5.3) on Mac OS locks up my machine when using the `gprMax_info` macro to threshold and render materials. This seems to happen with models that contain >~50...
The current algorithm for estimating the amount of RAM a model will require does not account for the extra memory required for setting up the `#fractal_box` and its associated modifiers,...