hi@javoha ,

thanks forthe answer,

My thought is that if IDs and STRAT_UNIT names are all the time “together” in all the steps from input data through geomodel to property model . To have more control over what is placed where would make things a lot more robust, I assume though.

Have built a property model (Porosity model ) from Geomodel but have little means of control if Strat_units are placed correctly.

I also think some facilitation of “printing/visualization” function for surface names and strat_units, in 3d, down the line (input files- geomodel- property model ) would be very good, for both geomodel and property model.

Presently in the current Gempy version , that is possible, in a way, but very hard to put together with a visualized geomodel or visualized property model.

But as you wrote geo_model.solutions.raw_arrays.lith_block, might hold the”key”

By the way probably importantto say thati am taking Porosities from wells, porosities connected to Strat_units, I made a separate file for this and had to match with geo_model.surface_points_copy.df so geomodel and property model will be in sync, at least tried. Got results interpolated but have suspicion geomodel and por model strat_units (interpolated porosities ) r not in sync.

p.s
with this "I have bulit geomodel and trying to propagate in the right order to property model, strat units however seem somewhat not in the right position."-I meant right order- when it comes to Strat_units, i got gaps so assuming that order of Strat_units down the line has not been taken correct by the script -

Rgds

Marin Mirošević
mail:marin.mirosevic@gmail.com

Hi,

you are probably right that things can always be improved. But let's try to get exactly on the same page regarding the target. Populating a structural geological model with properties is not an inherent part of gempy. Very generally speaking this is a step I would perfom after I computed this model.

The way I do it:

1. Compute a strucural geologicial model

2. Coordinates of the regular grid are stored undergeo_model.grid.regular_grid.values

3. The corresponding lithology are stored undergeo_model.solutions.raw_arrays.lith_block

4. If you have a one to one mapping e.g porosity of x for formation y, you can just map them to a copy of the lithology block. Alternatively you can also perform something like kriging in a single element to get a more realistic property distribution. Here is an example of how this might look (performed on this model:https://docs.gempy.org/examples/geometries/g07_combination.html#sphx-glr-examples-geometries-g07-combination-py)

5. I have visualized this separately in pyvista in this case.

Is this generally what you aim for or am I not getting the point?

Hello Jan@javoha

to explain better, initally i have input files for surfaces and orientations (classical input files for gempy) . I sucessfuly built structural model with clear start_units(formations) defined in 2 input files.

Structural model has 1 fault.

I have also produced a file (holding well ) data that basically have same surfaces depths as defined in the initial file (surface points) , vertically points , you could say, r grouped by X and Y and that thing I used when placing wells vertically through each Formation (strat_unit). On this file I have defined porosities connected to each Well and Formation.

Since it is not possible or feasible with gempy to import Well logs (values , for e porosity), that will be upscaled down theline , I have determined on each Formation(start_unit) single porosity value.

I want to match formations from structural model and this file to distribute porosities on wells . I want to distribute in a such way that POR is kriging distibuted each/separate in its Formation(strat_unit).

I have succeeded to a degree when it comes distributing well porosities but have no meaning of displaying formations (strat_units) with POR model.

So I would say matching in this case is the problem, I have also spotted error messages when it comes to grid_points as non-existing or not matching arrays.

Perhaps we can have a short chat on teams or similar about or I can send you files on your email, my e-mail, if you are interested:marin.mirosevic@gmail.com

P.S maybe not so important but maybe i should mention that I am using Anaconda Spyder.

Kind regards,

Marin Mirošević

Hi@IoTNoobie,

thanks for your interest! In this very simple example I extracted the grid coordinates and the respective lthology ID (stored ingeo_model.solutions.raw_arrays.lith_block) from gempy. I converted this information to a block/voxel model using the pyvista package.
I extracted a single structural element by ID and performed a Gaussian Simulation only within this structural element using the GSTools package.
Note that a completely arbitrary varigoram was used here and variogram modeling in these settings can get rather tricky (depending on things like data availability and coverage as well as anisotropies, etc.).

The code for this example is available here:
https://github.com/cgre-aachen/egu25_gempy_workshop/blob/main/outlook_notebooks/Property_modeling_EGU25.ipynb

We are also hoping to provide a gempy-plugin in the feature to streamline this functionality a bit.

I hope this helps and let me know if you have any further questions.

Cheers,
Jan