Jan Niederau

@istrous see here: https://github.com/GeorgeLiang3/GemPyTF

Don't know whether this is still ongoing... but I saw, that next to the toc2 extension, the Exercise extension uses the `fa-mortar-board`, too. To avoid a potential clash, I changed...

implemented in #61

No, not yet

Hi @Wrobs38 > File ~\Anaconda3\lib\site-packages\gempy\core\model.py:1575 > match type(field_at_surface_points): > ^ > SyntaxError: invalid syntax match statements were introduced with Python 3.10. But I see, you created your conda environment with...

short question: This only affects the visual presentation of the fault plane, right? Not the distortion of the scalar field, i.e. the displacement caused by the fault? We could think...

So, you still have this issue after downgrading pandas? Or does downgrade not work in your environment? GemPy won't work with pandas 2.0.2, but 2.0 and 2.0.1

> There seems to be a change in data type from pandas 2.0.1 to 2.0.2. So we need to track down the location where the DataFrame is constructed. > >...

One point I was thinking of...how does this behave, when the same instance is called repeatedly? As `pv.convert_array()`"Convert a NumPy array to a vtkDataArray or vice versa."... Naive question: Could...

maybe. Is there a huge benefit? Cause `pv.convert_array` also uses `numpy_to_vtk` as far as I can tell? And pyvista also relies on vtk, so we cannot ditch that import altogether.