|
| 1 | ++++ |
| 2 | +title = "Ensemble Contour Maps" |
| 3 | +weight = 40 |
| 4 | ++++ |
| 5 | + |
| 6 | + |
| 7 | + |
| 8 | +ResInsight can create contour maps from an ensemble of grid models based on different forms of aggregation of 3D Eclipse data onto a 2D plane. |
| 9 | + |
| 10 | +## Creating Contour Maps |
| 11 | + |
| 12 | +Import grid models using the **Create Grid Case Ensemble**. The grid models can have individually specified geometry. For grids with equal geometry, consider using [Grid Case Group]({{% relref "casegroupsandstatistics" %}}). The formation information is imported for each grid. |
| 13 | + |
| 14 | + |
| 15 | + |
| 16 | +Select "New Statistics Contour Map" from the right-click menu on the grid ensemble. |
| 17 | + |
| 18 | +## Properties of the Contour Maps |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | +The **General** group is used to define how to compute the contour map. See [Contour Map]({{% relref "contourmaps" %}}) for details. |
| 23 | + |
| 24 | +The grid case model defined by *"Primary Case"* is used for fault and simulation well visualization. The 2D area used to evaluate the contour map values is based on the bounding box of the **Primary Case**. Use **Bounding Box Expansion** to ensure that the area covers the geometry variation within the ensemble. |
| 25 | + |
| 26 | +### Time Step Selection |
| 27 | + |
| 28 | +Select the time steps to compute the contour map for. |
| 29 | + |
| 30 | +### Formation Selection |
| 31 | + |
| 32 | +Select the formations to compute the contour map for. |
| 33 | + |
| 34 | +### Result Definition |
| 35 | + |
| 36 | +Select the property to compute the contour map for. |
| 37 | + |
| 38 | +## Performance Considerations |
| 39 | + |
| 40 | +When working with multiple grid models, importing and processing data will take time. Understand how to limit the data involved in calculations, and consider a test run with a small number of realizations before using the full ensemble. |
| 41 | + |
| 42 | +As the grid geometry can be defined individually, grid cell geometry needs to be imported for each case. To ensure the import of only required geometry, use the **opm-common (beta)** grid reader and make sure to import only active cell geometry, as configured in [Preferences]({{% relref "performancehints" %}}). |
| 43 | + |
| 44 | +Consider setting the **Sampling Resolution** to coarse to improve performance. Note that this option will introduce interpolation effects. |
| 45 | + |
| 46 | +Click the **Compute** button in the **Property Editor** to start the computation. |
| 47 | + |
| 48 | +## Display of Contour Map Data |
| 49 | + |
| 50 | +A view is automatically created and displayed when the computation is completed. Select the **Map Projection** object to control the display. Create additional views from the right-click menu of the **Statistics Contour Map** object. |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +Select the current statistical property from **Statistics Type**. A value filter can be used to filter the display of the contour map. |
| 55 | + |
| 56 | +## Create Polygon |
| 57 | + |
| 58 | +Select "*Create Polygon from Contour Map*" from the right-click menu. This will create a polygon of the outline of the contour map. The shape of the polygon can be simplified using the right-click menu of the generated polygon. |
| 59 | + |
| 60 | +### References |
| 61 | + |
| 62 | +[Contour Map]({{% relref "contourmaps" %}}) |
| 63 | + |
| 64 | +[Grid Case Group]({{% relref "casegroupsandstatistics" %}}) |
0 commit comments