Jan von Harten

Hi, one of the problems of defining the fault offset (or throw and heave) is the 3D environment. The offset of your fault probaly varies. Are you sure that you...

Hi @fabiojdf, the code for continuous property kriging and simulation in gempy is pretty basic and not very powerful regarding runtime. I wrote some code to use gempy with gstools...

Hi, sorry for not replying faster: We were busy working on gempy v3 moving away from theano and aesara (due to issues like yours). The legacy version of gempy can...

Hi, sorry for the very late reply, I think we were note sure how to solve this and additionally working on the new gempy version. Have you tried this uisng...

Hi and sorry for the late reply. Gempy v3 is available now and should hopefully solve these problems as you mentioned. Please feel free to reopen the issue if you...

Resolved? Please feel free to reopen if not. I am also not sure how much of this is a gempy issue. But definitely a useful discussion.

Hi, I think this is a little tricky due to the Theano dependency. I havent done it myself and hopefully it will be resolved with a new gempy version moving...

Hi @SiBoh716, sorry for the very late response. If this is still of interest: The ```sol.scalar_field_matrix``` has multiple dimensions depending on the number of scalar fields in your model (normally...

Hi, you can access the different ndarrays of the solution using: `geo_data.solutions.raw_arrays` I guess the most important results would be the vertices of the grid and the corresponding solutions: ```...

Hopefully resolved, feel free to reopen if issue persists.