Comments (3)
For the first problem, you have probably modified the spacing (or the number of cells) in the z direction (sz must be 0.5 and nz must be 50). Consequentely, the grid now is too big in this direction (its top is at 50 (or higher) instead of 25).
For the second problem, I'm not sure but probably the issue is the covariance models (variograms) used. These define the range of spatial correlation that the surface (and facies) can have. Here we nearly observed a straight line which indicates that no spatial correlation is considered. Probably because the extent of this correlation (the range) is too small.
In the example below (taken from notebook 2), it shows the different parameter defined for unit B. The surface covmodel is shown at the first line and is called by the gcm.CovModel2D
function. See the geone documentation for more information. But what you will have to change is probably the list after the "r"
which is [15, 5]
here. These two numbers indicate the maximal distance of correlation in x direction and y, respectively. This means that two points that are spaced by a distance greater than these distances, there will be no correlation. Ensure to have a sufficient distance that is representative of your data (you can make experimental variogram for this, see the inference notebook but note that some widgets are not working...) or you can adjust manually the value until you find something that looks good for you.
## B
#surface B
covmodel_b = gcm.CovModel2D(elem = [("cubic", {"w":2, "r" : [15,5]})]) # Surface covariance model
dic_surf_b = {"covmodel" : covmodel_b, "int_method" : "grf_ineq"}
Sb = ArchPy.base.Surface(name = "Sb", dic_surf=dic_surf_b)
#dic facies b
dic_facies_b = {"f_method" : "SIS", "f_covmodel" : covmodel_SIS, "probability" : [0.7, 0.3]}
B = ArchPy.base.Unit(name = "B",
order = 2, #order in pile
color = "greenyellow", #color
surface=Sb, # top surface
ID = 2, #ID
dic_facies=dic_facies_b #facies dictionnary
)
Also make sure that the top of your model does not exceed the top of your boreholes. Here it seems that it is the case. Adjust the grid of your model accordingly. (oz + nz*sz = top elevation, or you can directly set the top elevation by specfifying it, e.g.
T1.agg_grid(dimensions, spacing, origin, top=top_elevation)
from archpy.
Dear Ludovic,
Thank you for your response. My first issue is solved. However, the second issue not solved yet. I have been trying different values for the COVmodel but the issue still persist. Please help
from archpy.
The variance of the covmodel (w
parameter) must also be modified according to the expected variance of the surface that you want to model. In the example it is equal to 2 but must be equal to the variance of the elevation data of the top surface of this unit.
To know this value you can type the following command:
np.var(Unit.surface.z)
Where you replace Unit
by the variable that you have chosen for your unit.
But I also strongly suggest to use the following command to automatically infer the variograms for each unit if you have enough data.
T1.estimate_surf_params(auto=True, hmax=500)
Just make sure to adjust the hmax parameter to value large enough, it is site specific so there is no general rule to choose it but should be around 10-50% of the maximal distance possible in your modeling area.
Finally, note that these informations only stand for the surfaces and for the facies you will also have to define variograms, with appropriate variances (which are not defined in the same way that for surface covmodels) and ranges.
from archpy.
Related Issues (14)
- Segmentation fault (core dumped) running 1_the_very_basic HOT 4
- Import of ArchPy fails (windows 11 - miniconda) - Missing geos_c.dll? HOT 1
- [Suggestion] rename getXX methods to get_XX HOT 1
- [Suggestion] add plot_grid method HOT 1
- Adding gaps HOT 1
- borehole X, Y and Z coordinate initialization HOT 4
- Computing facies HOT 2
- Making units HOT 3
- Compute Surface
- plot facies error
- Probability map HOT 1
- shannon entropy plots HOT 2
- Facies computations
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from archpy.