diff --git a/3d-main-window/3dviews/index.html b/3d-main-window/3dviews/index.html
index 91f7f79517..8561ea6196 100644
--- a/3d-main-window/3dviews/index.html
+++ b/3d-main-window/3dviews/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Views :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,33 +1802,29 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#common-view-features">Common view features</a>
-<ul>
-<li><a href="#view-properties">View properties</a></li>
-<li><a href="#cell-result">Cell Result</a></li>
-<li><a href="#range-filters-and-property-filters">Range Filters and Property Filters</a></li>
-<li><a href="#info-box">Info Box</a>
-<ul>
-<li><a href="#statistics-options">Statistics Options</a></li>
-</ul></li>
-<li><a href="#grids">Grids</a></li>
-<li><a href="#intersections">Intersections</a></li>
-<li><a href="#activate-items-by-clicking">Activate items by clicking</a></li>
-</ul></li>
-<li><a href="#eclipse-features">Eclipse features</a>
-<ul>
-<li><a href="#cell-edge-results">Cell Edge Results</a></li>
-<li><a href="#separate-fault-result">Separate Fault Result</a></li>
-<li><a href="#simulation-wells">Simulation Wells</a></li>
-<li><a href="#well-connection-factors">Well Connection Factors</a></li>
-<li><a href="#fractures">Fractures</a></li>
-<li><a href="#faults">Faults</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#common-view-features">Common view features</a>
+      <ul>
+        <li><a href="#view-properties">View properties</a></li>
+        <li><a href="#cell-result">Cell Result</a></li>
+        <li><a href="#range-filters-and-property-filters">Range Filters and Property Filters</a></li>
+        <li><a href="#info-box">Info Box</a></li>
+        <li><a href="#grids">Grids</a></li>
+        <li><a href="#intersections">Intersections</a></li>
+        <li><a href="#activate-items-by-clicking">Activate items by clicking</a></li>
+      </ul>
+    </li>
+    <li><a href="#eclipse-features">Eclipse features</a>
+      <ul>
+        <li><a href="#cell-edge-results">Cell Edge Results</a></li>
+        <li><a href="#separate-fault-result">Separate Fault Result</a></li>
+        <li><a href="#simulation-wells">Simulation Wells</a></li>
+        <li><a href="#well-connection-factors">Well Connection Factors</a></li>
+        <li><a href="#fractures">Fractures</a></li>
+        <li><a href="#faults">Faults</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1819,130 +1849,77 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/3DViewOverview.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3DViewOverview.png" alt=""></p>
 <p>3D Views are the windows displaying the Grid Models. The visualization is controlled by the <strong>Project Tree</strong> item representing the <strong>View</strong> and their sub items.</p>
-
-<p><img src="/images/3d-main-window/ViewTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ViewTree.png" alt=""></p>
 <p>Each item has a set of properties that can be edited in the <strong>Property Editor</strong>.</p>
-
 <p>Several views can be added to the same case by right-clicking the case or a view and select <strong>New View</strong>. You can also <strong>Copy</strong> and then <strong>Paste</strong> a view into a Case. All the settings are then copied to the new view.</p>
-
 <p>Views of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.</p>
-
 <h2 id="common-view-features">Common view features</h2>
-
 <h3 id="view-properties">View properties</h3>
-
 <p>Grid appearance can be controlled from the <strong>Property Editor</strong> when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.</p>
-
-<p><img src="/images/3d-main-window/ViewProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ViewProperties.png" alt=""></p>
 <p>Visibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using <strong>Show Grid Box</strong>.</p>
-
 <h3 id="cell-result">Cell Result</h3>
-
 <p>The <strong>Cell Result</strong> <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
  item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the <strong>Cell Result</strong> item. The mapping between cell values and color is defined by the <strong>Legend Definition</strong><img src="https://resinsight.org/images/3d-main-window/Legend.png" style="display:inline; vertical-align:middle; margin:0">
  along with some appearance settings on the Legend itself. (Number format etc.)</p>
-
 <p>Please refer to <a href="/3d-main-window/resultcolorlegend/">Result Color Legend</a> for details.</p>
-
 <h3 id="range-filters-and-property-filters">Range Filters and Property Filters</h3>
-
 <p>In order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to <a href="/3d-main-window/filters/">Cell Filters</a> to read more about them.</p>
-
 <h3 id="info-box">Info Box</h3>
-
 <p>The <strong>Info Box</strong> controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.</p>
-
 <p>The <strong>Animation Progress</strong> shows which time step you are viewing.</p>
-
-<p><img src="/images/3d-main-window/AnimationProgress.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/AnimationProgress.png" alt=""></p>
 <p>The <strong>Info Text</strong> shows general info about the case, the selected results, and some statistics. <strong>Mobile Volume Weighted Mean</strong> is the mean of the current <strong>Cell Property</strong> weighted by the <strong>Mobile pore volume</strong>. Mobile pore volume is defined in every cell as: MULTPV <em>*</em> PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.</p>
-
-<p><img src="/images/3d-main-window/infoBox.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/infoBox.png" alt=""></p>
 <p>The <strong>Histogram</strong> shows a histogram of the complete time series of the currently loaded <strong>Cell Result</strong> together with:</p>
-
 <ul>
 <li>The mean value ( a blue line )</li>
 <li>P10 and P90 ( red lines )</li>
 </ul>
-
-<p><img src="/images/3d-main-window/HistogramExample.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/HistogramExample.png" alt=""></p>
 <h4 id="statistics-options">Statistics Options</h4>
-
 <ul>
-<li><strong>Statistics Time Range</strong> &ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.<br /></li>
+<li><strong>Statistics Time Range</strong> &ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.</li>
 <li><strong>Statistics Cell Range</strong> &ndash; controls if visible cells or all active cells is included when statistics is computed.</li>
 </ul>
 
-
-<div class="notices note" ><p>The <b>Info Box</b> settings can be activated by clicking on the Info Text in the 3D view.</p>
+<div class="notices note" ><p>The <!-- raw HTML omitted -->Info Box<!-- raw HTML omitted --> settings can be activated by clicking on the Info Text in the 3D view.</p>
 </div>
 
-
 <h3 id="grids">Grids</h3>
-
-<p><img src="/images/3d-main-window/ViewTreeGrids.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ViewTreeGrids.png" alt=""></p>
 <p>The <strong>Grids</strong> <img src="https://resinsight.org/images/3d-main-window/draw_style_meshlines_24x24.png" style="display:inline; vertical-align:middle; margin:0">
  node contains child nodes for <strong>Main Grid</strong>, <strong>LGRs</strong> and <strong>Temporary LGRs</strong> where each grid&rsquo;s visibilty can be controlled. The <strong>LGRs</strong> node contains all LGRs loaded from file, while <strong>Temporary LGRs</strong> contains all temporary LGRs (see <a href="/wells-and-completions/completionslgr/">Completions LGR</a>).
 Toggling <strong>Grids</strong> off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called <em>Hide grid cells</em>.</p>
-
 <h3 id="intersections">Intersections</h3>
-
 <p>Intersections <img src="https://resinsight.org/images/3d-main-window/CrossSections16x16.png" style="display:inline; vertical-align:middle; margin:0">
  are used to cut the geometry and show result values mapped onto this geometry.
 Please refer to <a href="/3d-main-window/intersections/">Intersections</a> for details.</p>
-
 <h3 id="activate-items-by-clicking">Activate items by clicking</h3>
-
 <p>Selected overlay items in the 3D view can activate a corresponding item in the <strong>Property Editor</strong>. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.</p>
-
 <h2 id="eclipse-features">Eclipse features</h2>
-
 <h3 id="cell-edge-results">Cell Edge Results</h3>
-
-<p><img src="/images/3d-main-window/CellEdgeExample.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CellEdgeExample.png" alt=""></p>
 <p>The <strong>Cell Edge Result</strong> <img src="https://resinsight.org/images/3d-main-window/EdgeResult_1.png" style="display:inline; vertical-align:middle; margin:0">
  visualization mode is one of ResInsight&rsquo;s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values <em>different from 1.0</em> along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.</p>
-
 <p>ResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.</p>
-
 <p>When selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the <strong>Legend Definition</strong> item belonging to the <strong>Cell Edge Result</strong> item.</p>
-
 <p>Select <strong>Custom Edge Result</strong> to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The <strong>Custom Edge Result</strong> can either be a static or dynamic result.</p>
-
 <h3 id="separate-fault-result">Separate Fault Result</h3>
-
 <p>Default result mapping on faults is using the result specified in <strong>Cell Result</strong>. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the <strong>Property Editor</strong>. A second legend for the fault result is added to the view.</p>
-
 <h3 id="simulation-wells">Simulation Wells</h3>
-
 <p>This item controls the visualization of the Eclipse simulation wells.
 Please refer to <a href="/wells-and-completions/simulationwells/">Simulation Wells</a> to read more.</p>
-
 <h3 id="well-connection-factors">Well Connection Factors</h3>
-
 <p>This item controls the visualization of well connection factors.
 See <a href="/wells-and-completions/completions/#visualization-and-inspection-of-well-connection-factors">Visualization and Inspection of Well Connection Factors</a> for details.</p>
-
 <h3 id="fractures">Fractures</h3>
-
 <p>This item controls the visualization of fractures.
 See <a href="/wells-and-completions/completions/#fractures">Fractures</a> for details.</p>
-
 <h3 id="faults">Faults</h3>
-
-<p>Visualization of the faults in the model is controlled by this item.
+<p>Visualization of the faults in the model is controlled by this item. 
 Please refer to <a href="/3d-main-window/faults/">Faults</a> to read more.</p>
 
 
@@ -2119,6 +2096,19 @@ Please refer to <a href="/3d-main-window/faults/">Faults</a> to read more.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2129,6 +2119,9 @@ Please refer to <a href="/3d-main-window/faults/">Faults</a> to read more.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3276,20 +3269,20 @@ Please refer to <a href="/3d-main-window/faults/">Faults</a> to read more.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/annotations/index.html b/3d-main-window/annotations/index.html
index b79c715b4f..b3bc2316c7 100644
--- a/3d-main-window/annotations/index.html
+++ b/3d-main-window/annotations/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Annotations :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,14 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#global-scope-vs-local-scope-annotations">Global scope vs local scope annotations</a></li>
-<li><a href="#text-annotations">Text Annotations</a></li>
-<li><a href="#reach-circle-annotations">Reach Circle Annotations</a></li>
-<li><a href="#user-defined-polyline-annotations">User Defined Polyline Annotations</a></li>
-<li><a href="#polyline-imported-from-file">Polyline Imported From File</a></li>
-<li><a href="#annotations-visibility">Annotations visibility</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#global-scope-vs-local-scope-annotations">Global scope vs local scope annotations</a></li>
+    <li><a href="#text-annotations">Text Annotations</a></li>
+    <li><a href="#reach-circle-annotations">Reach Circle Annotations</a></li>
+    <li><a href="#user-defined-polyline-annotations">User Defined Polyline Annotations</a></li>
+    <li><a href="#polyline-imported-from-file">Polyline Imported From File</a></li>
+    <li><a href="#annotations-visibility">Annotations visibility</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,95 +1834,65 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.</p>
-
 <ul>
 <li>Text annotations</li>
 <li>Reach circle annotations</li>
 <li>Polyline annotations
-
 <ul>
 <li>User defined polylines</li>
 <li>Polylines imported from file</li>
-</ul></li>
 </ul>
-
-<p><img src="/images/3d-main-window/Annotations.png" alt="" /></p>
-
+</li>
+</ul>
+<p><img src="/images/3d-main-window/Annotations.png" alt=""></p>
 <h2 id="global-scope-vs-local-scope-annotations">Global scope vs local scope annotations</h2>
-
 <p>Global annotations may be displayed in all views and are located in the <strong>Annotations</strong> project tree node right below <strong>Grid Models</strong> (Global annotations sub tree). Local annotations are associated with a specific view and are located in the <strong>Annotations</strong> project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.</p>
-
 <p>All global annotations also have a representation in the local <strong>Annotation</strong> tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with <strong>Global</strong>.</p>
-
-<p><img src="/images/3d-main-window/LocalAnnotationsTree.png" alt="" /><br/>
+<p><img src="/images/3d-main-window/LocalAnnotationsTree.png" alt=""><!-- raw HTML omitted -->
 Local annotations sub tree</p>
-
-<p><img src="/images/3d-main-window/GlobalAnnotationsTree.png" alt="" /><br/>
+<p><img src="/images/3d-main-window/GlobalAnnotationsTree.png" alt=""><!-- raw HTML omitted -->
 Global annotations sub tree</p>
-
 <h2 id="text-annotations">Text Annotations</h2>
-
 <p>There are two ways of creating a new text annotation.</p>
-
 <ul>
 <li>Right click <strong>Annotations</strong> or <strong>Text Annotations</strong> tree node in either the global annotatyion sub tree or the local annotations sub tree. The scope of the annotation depends on which node was clicked. When text annotations are created this way, all text annotation fields must be entered manunally in the property editor.</li>
 <li>Right click on an object in the view and select <strong>Create Text Annotation</strong>. ResInsight will then create a text annotation at the clicked point. In this case, only th text must be entered manually in the property editor. When creating a text annotation this way, it will become a local annotation by default.</li>
 </ul>
-
-<p><img src="/images/3d-main-window/TextAnnotationPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/TextAnnotationPropertyEditor.png" alt=""></p>
 <ul>
 <li><strong>Anchor Point</strong> - The interesting point in the view</li>
 <li><strong>Label Point</strong> - The point where the text label is placed</li>
 <li><strong>Text</strong> - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree</li>
 <li><strong>Text appearance</strong> - Set font size, font color, background color and anchor line color</li>
 </ul>
-
 <p>When a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.</p>
-
 <h2 id="reach-circle-annotations">Reach Circle Annotations</h2>
-
 <p>To create a reach circle annotation, right click <strong>Annotations</strong> or <strong>Reach Circle Annotations</strong> tree node in the global annotations sub tree. Then enter values in the property editor.</p>
-
-<p><img src="/images/3d-main-window/CircleAnnotationPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CircleAnnotationPropertyEditor.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> - Name of the circle annotation</li>
 <li><strong>Center Point</strong> - Center point of the circle. Format &lsquo;x-pos y-pos depth&rsquo;</li>
 <li><strong>Radius</strong> - Circle radius</li>
 <li><strong>Line Appearance</strong> - Set circle color and line thickness</li>
 </ul>
-
 <h2 id="user-defined-polyline-annotations">User Defined Polyline Annotations</h2>
-
 <p>To create a user defined polyline annotation, right click <strong>Annotations</strong> or <strong>User Defined Polyline Annotations</strong> tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click <strong>Stop Picking Points</strong> in the property editor.</p>
-
-<p><img src="/images/3d-main-window/UserDefinedPolylineAnnotationPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/UserDefinedPolylineAnnotationPropertyEditor.png" alt=""></p>
 <ul>
 <li><strong>Targets</strong> - Polyline points. Can be edited in the table or interactively in the view</li>
 <li><strong>Start Picking Points / Stop Picking Points</strong> - Button to start / stop picking mode</li>
 <li><strong>Line Appearance</strong> - Set line color and thickness</li>
 </ul>
-
 <p>When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.</p>
-
 <h2 id="polyline-imported-from-file">Polyline Imported From File</h2>
-
 <p>To import a polyline annotation from file, right click <strong>Annotations</strong> or <strong>Polylines From File</strong> tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.</p>
-
-<p><img src="/images/3d-main-window/PolylineFromFileAnnotationPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PolylineFromFileAnnotationPropertyEditor.png" alt=""></p>
 <ul>
 <li><strong>File</strong> - Name of the imported file</li>
 <li><strong>Line Appearance</strong> - Set line color and line thickness</li>
 </ul>
-
 <h2 id="annotations-visibility">Annotations visibility</h2>
-
 <p>Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.</p>
 
 
@@ -2068,6 +2069,19 @@ Global annotations sub tree</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2078,6 +2092,9 @@ Global annotations sub tree</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3228,20 +3245,20 @@ Global annotations sub tree</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/casegroupsandstatistics/index.html b/3d-main-window/casegroupsandstatistics/index.html
index 5190d4127b..4d6eba5fb8 100644
--- a/3d-main-window/casegroupsandstatistics/index.html
+++ b/3d-main-window/casegroupsandstatistics/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Case Groups and Statistics :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,26 +1802,22 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#creating-grid-case-groups">Creating Grid Case Groups</a>
-<ul>
-<li><a href="#from-files">From Files</a></li>
-<li><a href="#manually">Manually</a></li>
-</ul></li>
-<li><a href="#viewing-special-source-cases">Viewing Special Source Cases</a></li>
-<li><a href="#statistics">Statistics</a>
-<ul>
-<li><a href="#setting-up-and-calculate">Setting Up and Calculate</a>
-<ul>
-<li><a href="#percentile-methods">Percentile Methods</a></li>
-</ul></li>
-<li><a href="#viewing-the-results">Viewing the Results</a></li>
-<li><a href="#adding-statistics-cases">Adding Statistics Cases</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#creating-grid-case-groups">Creating Grid Case Groups</a>
+      <ul>
+        <li><a href="#from-files">From Files</a></li>
+        <li><a href="#manually">Manually</a></li>
+      </ul>
+    </li>
+    <li><a href="#viewing-special-source-cases">Viewing Special Source Cases</a></li>
+    <li><a href="#statistics">Statistics</a>
+      <ul>
+        <li><a href="#setting-up-and-calculate">Setting Up and Calculate</a></li>
+        <li><a href="#viewing-the-results">Viewing the Results</a></li>
+        <li><a href="#adding-statistics-cases">Adding Statistics Cases</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1812,62 +1842,38 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/GridCaseGroupTree.png" alt="" /></p>
-
-<p><strong>Grid Case Group</strong>&rsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled <em>realizations</em>).</p>
-
+<p><img src="/images/3d-main-window/GridCaseGroupTree.png" alt=""></p>
+<p><strong>Grid Case Group</strong>&lsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled <em>realizations</em>).</p>
 <p>If you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.</p>
-
 <h2 id="creating-grid-case-groups">Creating Grid Case Groups</h2>
-
 <h3 id="from-files">From Files</h3>
-
 <p>The easiest way to create a <strong>Grid Case Group</strong> is to use the Import command:
 <strong>File-&gt;Import-&gt;Eclipse Cases-&gt;Create Grid Case Group from Files</strong> or <strong>File-&gt;Import-&gt;Eclipse Cases-&gt;Create Grid Case Group from Files Recursively</strong></p>
-
 <p>The latter command will display the recursive file import dialog described on the <a href="/plot-window/summaryplots/#recursive-summary-file-import">Summary Plots page</a>.</p>
-
 <p>The first command will display the &ldquo;old&rdquo; import dialog:
-<img src="/images/3d-main-window/CreateGridCaseGroupFromFileDialog.png" alt="" /></p>
-
+<img src="/images/3d-main-window/CreateGridCaseGroupFromFileDialog.png" alt=""></p>
 <ol>
 <li>Add one or more search folders to the list on the left.</li>
 <li>The EGRID or GRID files found in these directories and sub directories are shown in the list to the right.</li>
 <li>If you want to remove some EGRID files from the list, select them and press the <strong>Remove</strong> button.</li>
 <li>When you are ready, press the <strong>OK</strong> button.</li>
 </ol>
-
 <p>ResInsight then creates a <strong>Grid Case Group</strong> for you, and populates its <strong>Source Cases</strong> with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.</p>
-
 <h3 id="manually">Manually</h3>
-
-<p>A Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. <strong>Source Cases</strong> can then be added by using the mouse to <em>drag and drop</em> cases with equal grids into the <strong>Grid Case Group</strong>&rsquo;s <strong>Source Case</strong> folder.
+<p>A Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. <strong>Source Cases</strong> can then be added by using the mouse to <em>drag and drop</em> cases with equal grids into the <strong>Grid Case Group</strong>&lsquo;s <strong>Source Case</strong> folder.
 This is useful if you want to create statistics based only on a subset of the source cases in an already created <strong>Grid Case Group</strong>.</p>
-
 <p><strong>Drag and Drop</strong> of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the <strong>Shift</strong> key while dropping.</p>
-
 <h2 id="viewing-special-source-cases">Viewing Special Source Cases</h2>
-
 <p>To reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, select <strong>New view</strong> from the right-click menu. A new 3D View will the be created on that particular case.</p>
 
-
-<div class="notices note" ><p><h5>How to limit system resource allocation</h5>
-To reduce memory usage, project loading time etc. remember to delete the 3D Views you do not need. 3D Views uses a lot of system resources.</p>
+<div class="notices note" ><!-- raw HTML omitted -->
 </div>
 
-
 <h2 id="statistics">Statistics</h2>
-
 <p>After creating a grid case group, an empty <strong>Statistics Case</strong> is created for you in the <strong>Derived Statistics</strong> folder of the <strong>Grid Case Group</strong>.</p>
-
 <h3 id="setting-up-and-calculate">Setting Up and Calculate</h3>
-
 <p>The properties of non-calculated and calculated <strong>Statistics Case</strong> is shown below:</p>
-
-<p><img src="/images/3d-main-window/StatisticsCaseProperties.png" alt="" />  <img src="/images/3d-main-window/StatisticsCasePropertiesCalculated.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/StatisticsCaseProperties.png" alt="">  <img src="/images/3d-main-window/StatisticsCasePropertiesCalculated.png" alt=""></p>
 <ul>
 <li><strong>Compute</strong> &ndash;  Starts to calculate requested statistical Properties.</li>
 <li><strong>Edit</strong> &ndash; Deletes the calculated results, and makes the controls to edit the setup available.</li>
@@ -1876,11 +1882,8 @@ To reduce memory usage, project loading time etc. remember to delete the 3D View
 <li><strong>Percentile Setup</strong> &ndash; Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations.</li>
 <li><strong>Well Data Source Case</strong> &ndash; This option selects which set of <strong>Simulation Wells</strong> to be shown along with the statistical results. You can select one of the <strong>Source Cases</strong>.</li>
 </ul>
-
 <h4 id="percentile-methods">Percentile Methods</h4>
-
 <p>Three Percentile methods are implemented:</p>
-
 <ul>
 <li><strong>Interpolated Observation</strong> &ndash;
 The values are sorted, and the two observations representing the probabilities closest to the percentile are interpolated to find the value for the percentile. This is the default method.</li>
@@ -1889,13 +1892,9 @@ The values are sorted, and the first observation representing a probability high
 <li><strong>Histogram based estimate</strong> &ndash;
 A histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.</li>
 </ul>
-
 <h3 id="viewing-the-results">Viewing the Results</h3>
-
 <p>When the computation is complete, you have to create a 3D View on the <strong>Statistics Case</strong> to view the results. Use the right-click menu of the <strong>Statistics Case</strong> to create it.</p>
-
 <h3 id="adding-statistics-cases">Adding Statistics Cases</h3>
-
 <p>A new statistical calculation can be created by activating the right-click menu for <strong>Derived Statistic-&gt;New Statistics Case</strong>.</p>
 
 
@@ -2072,6 +2071,19 @@ A histogram is created and the percentile is calculated based on the histogram.
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2082,6 +2094,9 @@ A histogram is created and the percentile is calculated based on the histogram.
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3232,20 +3247,20 @@ A histogram is created and the percentile is calculated based on the histogram.
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/cellresults/index.html b/3d-main-window/cellresults/index.html
index 5d615a7fe7..7e871e0f3b 100644
--- a/3d-main-window/cellresults/index.html
+++ b/3d-main-window/cellresults/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Cell Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,27 +1802,20 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#eclipse-result-types">Eclipse Result Types</a>
-<ul>
-<li><a href="#flow-diagnostic-results">Flow Diagnostic Results</a>
-<ul>
-<li><a href="#method">Method</a></li>
-<li><a href="#cross-flow-and-opposite-flow">Cross Flow and Opposite Flow</a></li>
-<li><a href="#defining-results">Defining Results</a></li>
-<li><a href="#on-demand-calculation">On-Demand Calculation</a></li>
-</ul></li>
-<li><a href="#injection-flooding">Injection Flooding</a></li>
-</ul></li>
-<li><a href="#geomechanical-results">Geomechanical Results</a>
-<ul>
-<li><a href="#relative-result-options">Relative Result Options</a></li>
-</ul></li>
-<li><a href="#select-color-result">Select Color Result</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#eclipse-result-types">Eclipse Result Types</a>
+      <ul>
+        <li><a href="#flow-diagnostic-results">Flow Diagnostic Results</a></li>
+        <li><a href="#injection-flooding">Injection Flooding</a></li>
+      </ul>
+    </li>
+    <li><a href="#geomechanical-results">Geomechanical Results</a>
+      <ul>
+        <li><a href="#relative-result-options">Relative Result Options</a></li>
+      </ul>
+    </li>
+    <li><a href="#select-color-result">Select Color Result</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1813,15 +1840,10 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/CellResultsOverview.png" alt="" /></p>
-
-<p>The main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per
+<p><img src="/images/3d-main-window/CellResultsOverview.png" alt=""></p>
+<p>The main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per 
 cell over a region of the grid. A Cell Result is also referred to as a <em>Property</em>.</p>
-
 <p>Cell Results are used in several operations and settings:</p>
-
 <ul>
 <li><strong>Cell Colors</strong></li>
 <li><strong>Cell Edge Result</strong> (Eclipse Only)</li>
@@ -1830,156 +1852,115 @@ cell over a region of the grid. A Cell Result is also referred to as a <em>Prope
 <li><strong>Well Log Extraction Curves</strong></li>
 <li><strong>Cell Result Time History Curves</strong></li>
 </ul>
-
-<p>In the property panel of all those, the same options are used to define the Cell Result of interest.<br />
+<p>In the property panel of all those, the same options are used to define the Cell Result of interest.<br>
 In the following we will describe these options.</p>
-
 <h2 id="eclipse-result-types">Eclipse Result Types</h2>
-
 <p>Results and difference options are displayed by the Property Editor.</p>
-
-<p><img src="/images/3d-main-window/CellResultTypes.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CellResultTypes.png" alt=""></p>
 <p>The different result types are:</p>
-
 <ul>
-<li><strong>Dynamic</strong> &ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f.
+<li><strong>Dynamic</strong> &ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f. 
 <a href="/3d-main-window/derivedresults/">Derived Results</a></li>
 <li><strong>Static</strong> &ndash; Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. <a href="/3d-main-window/derivedresults/">Derived Results</a></li>
 <li><strong>SourSimRL</strong> &ndash; Available if SourSimRL results have been imported, c.f. <a href="/import/soursimrlresults/">SourSimRL Import</a></li>
 <li><strong>Generated</strong> &ndash; Results generated by an Octave Script</li>
 <li><strong>Input Property</strong> &ndash; Directly imported Eclipse properties from ascii files</li>
 <li><strong>Formation Names</strong> &ndash; Lists only the Active Formation Names selected on the case, c.f. <a href="/3d-main-window/formations/">Formations</a></li>
-<li><strong>Flow Diagnostics</strong> &ndash; Flow diagnostic results derived from a flux field,
+<li><strong>Flow Diagnostics</strong> &ndash; Flow diagnostic results derived from a flux field, 
 c.f. <a href="/3d-main-window/cellresults/#flow-diagnostic-results">below</a></li>
-<li><strong>Injection Flooding</strong> &ndash; Calculation of derived property based on one or more selected simulation tracers,
+<li><strong>Injection Flooding</strong> &ndash; Calculation of derived property based on one or more selected simulation tracers, 
 c.f. <a href="/3d-main-window/cellresults/#injection-flooding">below</a></li>
 </ul>
-
 <p>Difference options are:</p>
-
 <ul>
 <li><strong>Difference Case</strong> &ndash; Base case for calculation of difference</li>
 <li><strong>Base Time Step</strong> &ndash; Base time step for calculation of difference</li>
 </ul>
 
-
 <div class="notices note" ><p>The difference option is not applicable for TERNARY result display.</p>
 </div>
 
-
 <h3 id="flow-diagnostic-results">Flow Diagnostic Results</h3>
-
-<p>ResInsight has embedded Flow Diagnostics calculations made available using the <strong>Flow Diagnostics</strong> result type.
-These results make it easier to see how and where wells interact with the reservoir and each other.
+<p>ResInsight has embedded Flow Diagnostics calculations made available using the <strong>Flow Diagnostics</strong> result type. 
+These results make it easier to see how and where wells interact with the reservoir and each other. 
 It is possible to select exactly what wells to investigate, and even the possible <em>opposite flow</em> part of the well.</p>
-
 <p>See also <a href="/plot-window/flowdiagnosticsplots/"> Flow Diagnostics Plots</a> and <a href="/plot-window/flowdiagnosticsplots/#flow-characteristics-plot"> Flow Characteristics Plot</a></p>
-
 <h4 id="method">Method</h4>
-
 <p>The calculations are performed by a library called <a href="https://github.com/OPM/opm-flowdiagnostics">opm-flowdiagnostics</a> developed by <a href="http://www.sintef.no/sintef-ikt/#/">SINTEF Digital</a>.</p>
-
 <p>This method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.</p>
-
 <p>A more elaborate description of the technique and how it can be  utilized, can be found at Sintef&rsquo;s <a href="http://www.sintef.no/projectweb/mrst/modules/diagnostics/">web site</a>. The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.</p>
-
-<p>The methodology is also described in:
-<a href="http://folk.ntnu.no/andreas/papers/diagnostics.pdf">The application of flow diagnostics for reservoir management</a> SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: <a href="https://dx.doi.org/10.2118/171557-PA">10.<sup>2118</sup>&frasl;<sub>171557</sub>-PA</a></p>
-
+<p>The methodology is also described in: 
+<a href="http://folk.ntnu.no/andreas/papers/diagnostics.pdf">The application of flow diagnostics for reservoir management</a> SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: <a href="https://dx.doi.org/10.2118/171557-PA">10.2118/171557-PA</a></p>
 <h4 id="cross-flow-and-opposite-flow">Cross Flow and Opposite Flow</h4>
-
 <p>The <em>opposite flow</em> of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections.
 Each well is assigned an opposite flow name by adding &ldquo;-XF&rdquo; to the end of the name. &ldquo;-XF&rdquo; was chosen as a reference to Cross Flow.</p>
-
 <p>In this way, a producer will have two tracer names: The &ldquo;well name&rdquo; as a producer tracer, and &ldquo;well name-XF&rdquo; as an injector tracer.</p>
-
 <h4 id="defining-results">Defining Results</h4>
-
 <p>There are several options available to define the particular result you want to target, as shown below:</p>
-
-<p><img src="/images/3d-main-window/CellResultFlowDiagnostics.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CellResultFlowDiagnostics.png" alt=""></p>
 <p>There are two main selections you need to make: The tracers and the result property</p>
-
 <ul>
 <li><strong>Tracers</strong> &ndash; Option to select how/what tracers to use. Available options are:
-
 <ul>
 <li><strong>All Injectors and Producers</strong> &ndash;  Selects all the wells, including the opposite flow tracers</li>
 <li><strong>All Producers</strong> &ndash; Selects all producer tracers, including the opposite flow tracers of injectors.</li>
 <li><strong>All Injectors</strong> &ndash; Selects all injector tracers, including the opposite flow tracers of producers.</li>
 <li><strong>By Selection</strong> &ndash; Displays lists of all the injector tracers and producer tracers side-by-side allowing any to be selected freely.
-
 <ul>
 <li>Both lists of selectable tracers can be filtered by typing in parts of the name.</li>
 <li>The tracers will have a suffix of [I/P] if they are both injector and producer, thus appearing in both lists.</li>
 <li>All producers communicating with the selected injectors (and vice-versa) can be selected with the &ldquo;Add Communicator&rdquo; buttons.</li>
-</ul></li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li><strong>Phases</strong> &ndash; Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the <em>Time Of Flight</em> result property will be available in the list below.</li>
 <li><strong>Result property</strong> &ndash; Displays a list of the available results:
-
 <ul>
-<li><strong>Residence Time</strong> &ndash; The time for some fluid in the cell to reach a producer,
+<li><strong>Residence Time</strong> &ndash; The time for some fluid in the cell to reach a producer, 
 or the time it takes to reach the cell from an injector. The option changes name depending on the selection of injectors and producers and will be Forward Time of Flight if only injectors are selected and Reverse Time of Flight if only producers are selected.
-When selecting several tracers, the time of flight values from each of the tracers are weighted
+When selecting several tracers, the time of flight values from each of the tracers are weighted 
 by their cell fraction before they are averaged. The suffix (Average) will then be added to the option label.</li>
-<li><strong>Tracer Cell Fraction (Sum)</strong> &ndash; The volume fraction of a cell occupied by the selected tracers.
-The injector and producer tracers counts as independent in this regard, so the sum of fractions for
-all the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers
+<li><strong>Tracer Cell Fraction (Sum)</strong> &ndash; The volume fraction of a cell occupied by the selected tracers. 
+The injector and producer tracers counts as independent in this regard, so the sum of fractions for 
+all the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers 
 are selected, the total sum will normally reach 2.0.</li>
-<li><strong>Drainage/Flooding Regions</strong> &ndash; Shows which of the selected tracers that has the largest fraction in each cell.
+<li><strong>Drainage/Flooding Regions</strong> &ndash; Shows which of the selected tracers that has the largest fraction in each cell. 
 This is shown as a category result displaying a color for each tracer, and the names in the legend. If only injectors are selected, this option will be labelled <strong>Drainage Regions</strong> and if only producers are selected, it is called <strong>Flooding Regions</strong>.</li>
-<li><strong>Injector Producer Communication</strong> &ndash; The communication in a cell between a set of producers and a set of injectors
-is calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell.
-This produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers
+<li><strong>Injector Producer Communication</strong> &ndash; The communication in a cell between a set of producers and a set of injectors 
+is calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell. 
+This produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers 
 have a high influence.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <h4 id="on-demand-calculation">On-Demand Calculation</h4>
-
 <p>The flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.</p>
-
 <h3 id="injection-flooding">Injection Flooding</h3>
-
 <p>This result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is <strong>Water Flooded PV</strong>. Please refer to <a href="/3d-main-window/derivedresults/">Derived Results</a> for more information.</p>
-
-<p><img src="/images/3d-main-window/InjectionFloodingPropertyPanel.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/InjectionFloodingPropertyPanel.png" alt=""></p>
 <ul>
 <li><strong>Tracers</strong> &ndash; Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter &ldquo;F&rdquo;. Select the tracers you want to investigate.</li>
 <li><strong>Result Property</strong> &ndash; Select the variable you want to calculate. (<em>Number Of Flooded PV</em> is currently the only one)</li>
 </ul>
-
 <h2 id="geomechanical-results">Geomechanical Results</h2>
-
 <p>Geomechanical results are sorted in different <strong>Result Position</strong>s:</p>
-
 <ul>
 <li><strong>Nodal</strong> &ndash; Results given a value per node in the grid</li>
 <li><strong>Element Nodal</strong> &ndash; Results with values per element node</li>
 <li><strong>Integration Point</strong> &ndash; Results with values per integration point. These are displayed in the same way as element nodal results.</li>
-<li><strong>Element Nodal on Face</strong> &ndash; Results with values transformed to element faces or intersections.
-See <a href="/3d-main-window/derivedresults/#element-nodal-on-face">Element Nodal on Face</a> for more information</li>
+<li><strong>Element Nodal on Face</strong> &ndash; Results with values transformed to element faces or intersections. 
+See <a href="/3d-main-window/derivedresults/">Element Nodal on Face</a> for more information</li>
 <li><strong>Formation Names</strong> &ndash; Lists the <strong>Active Formation Names</strong> selected on the case. ( See <a href="/3d-main-window/formations/">Formations</a> )</li>
 <li><strong>Element</strong> &ndash; Imported element property table results. One value pr element. See <a href="/import/elementpropertytable/">Element Property Table Import</a></li>
 </ul>
-
 <p>Several derived cell properties are calculated. Please refer to <a href="/3d-main-window/derivedresults/">Derived Results</a> for more information.</p>
-
 <h3 id="relative-result-options">Relative Result Options</h3>
-
-<p>This group of options controls time-lapse results to be calculated. ( See <a href="/3d-main-window/derivedresults/#relative-results-time-lapse-results">Relative Results</a> for more information )</p>
-
+<p>This group of options controls time-lapse results to be calculated. ( See <a href="/3d-main-window/derivedresults/">Relative Results</a> for more information )</p>
 <h2 id="select-color-result">Select Color Result</h2>
-
-<p><img src="/images/3d-main-window/SelectColorResult.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SelectColorResult.png" alt=""></p>
 <p>In the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing <strong>Select Color Result</strong>. The corresponding result property will be shown in the Property Editor.</p>
-
-<p><img src="/images/3d-main-window/SelectColorResultPropertyEditor.png" alt="" /></p>
+<p><img src="/images/3d-main-window/SelectColorResultPropertyEditor.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2155,6 +2136,19 @@ See <a href="/3d-main-window/derivedresults/#element-nodal-on-face">Element Noda
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2165,6 +2159,9 @@ See <a href="/3d-main-window/derivedresults/#element-nodal-on-face">Element Noda
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3315,20 +3312,20 @@ See <a href="/3d-main-window/derivedresults/#element-nodal-on-face">Element Noda
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/comparisonview/index.html b/3d-main-window/comparisonview/index.html
index 25cfc69200..b032a73888 100644
--- a/3d-main-window/comparisonview/index.html
+++ b/3d-main-window/comparisonview/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Comparison View :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,14 +1802,11 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#creating-a-comparison-view">Creating a Comparison View</a></li>
-<li><a href="#comparison-view-divider">Comparison View Divider</a></li>
-<li><a href="#view-properties-and-settings">View Properties and Settings</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#creating-a-comparison-view">Creating a Comparison View</a></li>
+    <li><a href="#comparison-view-divider">Comparison View Divider</a></li>
+    <li><a href="#view-properties-and-settings">View Properties and Settings</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1800,51 +1831,35 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/3DComparisonView.png" alt="" /></p>
-
-<p>ResInsight offers a <strong>Comparison View</strong> to compare two existing views in terms of grid geometry, results, intersections and more.
+<p><img src="/images/3d-main-window/3DComparisonView.png" alt=""></p>
+<p>ResInsight offers a <strong>Comparison View</strong> to compare two existing views in terms of grid geometry, results, intersections and more. 
 The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view.
 This improves efficiency and simplifies the workflow when working with related but different models.</p>
-
-<p>The figure above exemplifies a Comparison View for comparison of two different simulations models and results.
+<p>The figure above exemplifies a Comparison View for comparison of two different simulations models and results. 
 The left hand side is used to display grid and results of an <a href="/import/eclipsecases/">Eclipse simulation</a>
 while the right hand side displays an ABAQUS grid and simulation results from <a href="/import/geomechanicaldata/">geomechanical analysis</a>.</p>
-
-<p>A different way to use the Comparison View is to compare the same geometrical grid with different <a href="/3d-main-window/cellresults/">Cell Results</a>.
+<p>A different way to use the Comparison View is to compare the same geometrical grid with different <a href="/3d-main-window/cellresults/">Cell Results</a>. 
 Thus two cell results can easily be seen together in the same view.</p>
-
 <h2 id="creating-a-comparison-view">Creating a Comparison View</h2>
-
 <p>A Comparison View can be created as follows:</p>
-
 <ul>
 <li>In <strong>Project Tree</strong>, select a view and specify <strong>Comparison View</strong> in the <strong>Viewer</strong> section of <strong>Property Editor</strong></li>
 <li>Right-click a 3D View, and select <strong>Compare To&hellip;</strong></li>
 </ul>
-
-<p><img src="/images/3d-main-window/3DComparisonViewCreate.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3DComparisonViewCreate.png" alt=""></p>
 <h2 id="comparison-view-divider">Comparison View Divider</h2>
-
 <p>In the figure below, the Comparison View is used to compare two different grids in the same view, one to the left and the other to the right of the  divider between them.  The screen aligned divider is  possible to drag right and left by clicking the handle marked by a green circle.</p>
-
-<p><img src="/images/3d-main-window/3DComparisonViewDividerHandle.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3DComparisonViewDividerHandle.png" alt=""></p>
 <h2 id="view-properties-and-settings">View Properties and Settings</h2>
-
-<p>Properties of an individual view included in a Comparison View are controlled by their respective settings, notably
-<a href="/3d-main-window/3dviews/">3D Views</a>,
-<a href="/3d-main-window/cellresults/">Cell Results</a>,
-<a href="/3d-main-window/resultcolorlegend/">Result Color Legend</a>,
+<p>Properties of an individual view included in a Comparison View are controlled by their respective settings, notably 
+<a href="/3d-main-window/3dviews/">3D Views</a>, 
+<a href="/3d-main-window/cellresults/">Cell Results</a>, 
+<a href="/3d-main-window/resultcolorlegend/">Result Color Legend</a>, 
 <a href="/3d-main-window/filters/">Cell Filters</a>,
 and <a href="/3d-main-window/intersections/">Intersections</a>.</p>
-
 <p>Setting up <a href="/3d-main-window/linkedviews/">Linked Views</a> may also be relevant, e.g. to syncronize <a href="/3d-main-window/cellresults/">cell results</a>
 and <a href="/3d-main-window/filters/">cell filters</a>.</p>
 
-
 <div class="notices note" ><p><a href="/3d-main-window/intersections/#polyline-intersection">Polyline Intersections</a> does not facilitate picking points across the Comparison View divider. However, an intersection can be copied betweens views, see <a href="/3d-main-window/intersections/">Intersections</a> for details.</p>
 </div>
 
@@ -2023,6 +2038,19 @@ and <a href="/3d-main-window/filters/">cell filters</a>.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2033,6 +2061,9 @@ and <a href="/3d-main-window/filters/">cell filters</a>.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3183,20 +3214,20 @@ and <a href="/3d-main-window/filters/">cell filters</a>.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/contourmaps/index.html b/3d-main-window/contourmaps/index.html
index 88cfab84a4..6dc08bc095 100644
--- a/3d-main-window/contourmaps/index.html
+++ b/3d-main-window/contourmaps/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Contour Maps :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,19 +1802,17 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#creating-new-contour-maps">Creating New Contour Maps</a></li>
-<li><a href="#properties-of-the-contour-maps">Properties of the Contour Maps</a></li>
-<li><a href="#map-projection-properties">Map Projection Properties</a>
-<ul>
-<li><a href="#weighting-means-by-cell-result">Weighting Means by Cell Result</a></li>
-</ul></li>
-<li><a href="#difference-options">Difference options</a></li>
-<li><a href="#contour-map-export">Contour Map Export</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#creating-new-contour-maps">Creating New Contour Maps</a></li>
+    <li><a href="#properties-of-the-contour-maps">Properties of the Contour Maps</a></li>
+    <li><a href="#map-projection-properties">Map Projection Properties</a>
+      <ul>
+        <li><a href="#weighting-means-by-cell-result">Weighting Means by Cell Result</a></li>
+      </ul>
+    </li>
+    <li><a href="#difference-options">Difference options</a></li>
+    <li><a href="#contour-map-export">Contour Map Export</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1805,47 +1837,30 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/ContourMaps.png" alt="" /></p>
-
-<p>ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.
+<p><img src="/images/3d-main-window/ContourMaps.png" alt=""></p>
+<p>ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. 
 ResInsight is able to <a href="/export/contourmapexport/">export a contour map</a> to a text file.</p>
-
 <h2 id="creating-new-contour-maps">Creating New Contour Maps</h2>
-
 <p>Contour Maps can be created in many different ways:</p>
-
 <ul>
 <li>New Contour Map from the right-click menu of case or the <strong>Contour Maps</strong> project tree item underneath the case. These will create contour maps with default values.</li>
 <li>New Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result.</li>
 <li>Duplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.</li>
 </ul>
-
-<p><img src="/images/3d-main-window/NewContourMapFromCase.png" alt="" /> <img src="/images/3d-main-window/NewContourMapFromFolder.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/NewContourMapFromView.png" alt="" /> <img src="/images/3d-main-window/NewContourMapFromExisting.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/NewContourMapFromCase.png" alt=""> <img src="/images/3d-main-window/NewContourMapFromFolder.png" alt=""></p>
+<p><img src="/images/3d-main-window/NewContourMapFromView.png" alt=""> <img src="/images/3d-main-window/NewContourMapFromExisting.png" alt=""></p>
 <h2 id="properties-of-the-contour-maps">Properties of the Contour Maps</h2>
-
-<p><img src="/images/3d-main-window/ContourMapViewProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ContourMapViewProperties.png" alt=""></p>
 <p>A contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the <strong>2d Intersection Views</strong> with optional Axis Lines controlled with the <strong>Show Axis Lines</strong> toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See <strong>Map Projection Properties</strong> for the two latter).</p>
-
 <h2 id="map-projection-properties">Map Projection Properties</h2>
-
-<p><img src="/images/3d-main-window/ContourMapProjectionProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ContourMapProjectionProperties.png" alt=""></p>
 <p>The Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.</p>
-
 <p>A set of parameters governs this projection:</p>
-
 <ul>
 <li>The first option <strong>Sample Spacing Factor</strong> controls how many 2D Grid Cells are used in the map. The factor is multiplied by the characteristic cell length/width of the 3D grid to get the 2D Cell Size. A smaller factor will thus create a finer Contour Map.</li>
 <li>The second option <strong>Show Contour Lines</strong> toggles on/off the contour lines in the view.</li>
 <li>The final control in the <strong>Projection Settings</strong> box is the <strong>Result Aggregation</strong>. Here the following options are available:</li>
 </ul>
-
 <table>
 <thead>
 <tr>
@@ -1853,83 +1868,65 @@ ResInsight is able to <a href="/export/contourmapexport/">export a contour map</
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Oil Column</td>
 <td>A sum of SOIL * NTG * PORO * dZ</td>
 </tr>
-
 <tr>
 <td>Gas Column</td>
 <td>A sum of SGAS * NTG * PORO * dZ</td>
 </tr>
-
 <tr>
 <td>Hydrocarbon Column</td>
 <td>A sum of (SOIL + SGAS)* NTG * PORO * dZ</td>
 </tr>
-
 <tr>
 <td>Arithmetic Mean</td>
 <td>A volume weighted arithmetic mean of the specified cell result</td>
 </tr>
-
 <tr>
 <td>Harmonic Mean</td>
 <td>A volume weighted harmonic mean of the specified cell result</td>
 </tr>
-
 <tr>
 <td>Geometric Mean</td>
 <td>A volume weighted geometric mean of the specified cell result</td>
 </tr>
-
 <tr>
 <td>Volume Weighted Sum</td>
 <td>A volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO</td>
 </tr>
-
 <tr>
 <td>Sum</td>
 <td>A sum of the specified cell result. Suitable for absolute quantities.</td>
 </tr>
-
 <tr>
 <td>Top Value</td>
 <td>The first value encountered downwards vertically</td>
 </tr>
-
 <tr>
 <td>Min Value</td>
 <td>The minimum cell result value in the volume underneath the 2D Element</td>
 </tr>
-
 <tr>
 <td>Max Value</td>
 <td>The maximum cell result value in the volume underneath the 2D Element</td>
 </tr>
 </tbody>
 </table>
-
 <p>For the Column options, no <strong>Cell Result</strong> is available in the property tree under the Contour Map.</p>
-
 <h3 id="weighting-means-by-cell-result">Weighting Means by Cell Result</h3>
-
-<p><img src="/images/3d-main-window/ContourMapProjectionWeights.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ContourMapProjectionWeights.png" alt=""></p>
 <p>For the <strong>Arithmetic Mean</strong>, <strong>Geometric Mean</strong> and <strong>Harmonic Mean</strong> it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.</p>
-
 <h2 id="difference-options">Difference options</h2>
-
-<p>Creating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the
+<p>Creating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the 
 <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Cell Result</strong> item
 underneath the actual <strong>Contour Map</strong> in the project tree. This will display the <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
- <strong>Cell Result</strong> <a href="/3d-main-window/cellresults/#eclipse-result-types">Property Editor</a> to specify base case and/or base time step.</p>
-
+ <strong>Cell Result</strong> [Property Editor]
+(/3d-main-window/cellresults/#eclipse-result-types) to specify base case and/or base time step.</p>
 <h2 id="contour-map-export">Contour Map Export</h2>
-
 <p>ResInsight is able to <a href="/export/contourmapexport/">export a contour map</a> to a text file.</p>
 
 
@@ -2106,6 +2103,19 @@ underneath the actual <strong>Contour Map</strong> in the project tree. This wil
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2116,6 +2126,9 @@ underneath the actual <strong>Contour Map</strong> in the project tree. This wil
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3266,20 +3279,20 @@ underneath the actual <strong>Contour Map</strong> in the project tree. This wil
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/derivedresults/index.html b/3d-main-window/derivedresults/index.html
index e9b479c314..2aa7eaa78b 100644
--- a/3d-main-window/derivedresults/index.html
+++ b/3d-main-window/derivedresults/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Derived Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,51 +1802,24 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#derived-results-for-eclipse-cases">Derived Results for Eclipse Cases</a>
-<ul>
-<li><a href="#transmissibility-normalized-by-area">Transmissibility Normalized by Area</a></li>
-<li><a href="#overall-transmissibility-multiplier">Overall Transmissibility Multiplier</a></li>
-<li><a href="#directional-combined-results">Directional Combined Results</a></li>
-<li><a href="#completion-type">Completion Type</a></li>
-<li><a href="#identification-of-questionable-nncs">Identification of Questionable NNCs</a></li>
-<li><a href="#water-flooded-pv">Water Flooded PV</a></li>
-</ul></li>
-<li><a href="#derived-geomechanical-results">Derived Geomechanical results</a>
-<ul>
-<li><a href="#relative-results-time-lapse-results">Relative Results (Time Lapse Results)</a></li>
-<li><a href="#derived-result-fields">Derived Result Fields</a>
-<ul>
-<li><a href="#definitions-of-derived-results">Definitions of Derived Results</a>
-<ul>
-<li><a href="#case-constants">Case Constants</a></li>
-<li><a href="#compaction">COMPACTION</a></li>
-<li><a href="#st-total-stress">ST - Total Stress</a></li>
-<li><a href="#stm-total-mean-stress">STM - Total Mean Stress</a></li>
-<li><a href="#q-deviatoric-stress">Q - Deviatoric Stress</a></li>
-<li><a href="#gamma-stress-path">Gamma - Stress Path</a></li>
-<li><a href="#se-effective-stress">SE - Effective Stress</a></li>
-<li><a href="#sem-effective-mean-stress">SEM - Effective Mean Stress</a></li>
-<li><a href="#sfi">SFI</a></li>
-<li><a href="#dsm">DSM</a></li>
-<li><a href="#fos">FOS</a></li>
-<li><a href="#e-strain">E - Strain</a></li>
-<li><a href="#ev-volumetric-strain">EV - Volumetric Strain</a></li>
-<li><a href="#ed-deviatoric-strain">ED - Deviatoric Strain</a></li>
-<li><a href="#element-nodal-on-face">Element Nodal On Face</a></li>
-<li><a href="#sn-stress-component-normal-to-face">SN - Stress component Normal to face</a></li>
-<li><a href="#tph-horizontal-in-plane-shear-component">TPH - Horizontal in-plane shear component</a></li>
-<li><a href="#tnqv-horizontal-in-plane-shear-component">TNQV - Horizontal in-plane shear component</a></li>
-<li><a href="#tp-total-in-plane-shear">TP - Total in-plane shear</a></li>
-<li><a href="#tpinc-direction-of-tp">TPinc - Direction of TP</a></li>
-<li><a href="#pinc-and-pazi-face-inclination-and-azimuth">Pinc and Pazi - Face Inclination and Azimuth</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#derived-results-for-eclipse-cases">Derived Results for Eclipse Cases</a>
+      <ul>
+        <li><a href="#transmissibility-normalized-by-area">Transmissibility Normalized by Area</a></li>
+        <li><a href="#overall-transmissibility-multiplier">Overall Transmissibility Multiplier</a></li>
+        <li><a href="#directional-combined-results">Directional Combined Results</a></li>
+        <li><a href="#completion-type">Completion Type</a></li>
+        <li><a href="#identification-of-questionable-nncs">Identification of Questionable NNCs</a></li>
+        <li><a href="#water-flooded-pv">Water Flooded PV</a></li>
+      </ul>
+    </li>
+    <li><a href="#derived-geomechanical-results">Derived Geomechanical results</a>
+      <ul>
+        <li><a href="#relative-results-time-lapse-results">Relative Results (Time Lapse Results)</a></li>
+        <li><a href="#derived-result-fields">Derived Result Fields</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1837,127 +1844,86 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.</p>
-
 <h2 id="derived-results-for-eclipse-cases">Derived Results for Eclipse Cases</h2>
-
 <p>ResInsight calculates several derived cell properties that is made available as <strong>Static</strong> or <strong>Dynamic</strong> cell properties.
 The derived results listed at the bottom of the <strong>Static</strong> result properties, are shown below.</p>
-
-<p><img src="/images/appendix/DerivedStaticResults.png" alt="" /></p>
-
+<p><img src="/images/appendix/DerivedStaticResults.png" alt=""></p>
 <h3 id="transmissibility-normalized-by-area">Transmissibility Normalized by Area</h3>
-
 <p>The transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named <strong>riTRANXbyArea</strong>, <strong>riTRANYbyArea</strong> and <strong>riTRANZbyArea</strong> respectively.</p>
-
 <p>The normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.</p>
-
 <h3 id="overall-transmissibility-multiplier">Overall Transmissibility Multiplier</h3>
-
 <p>Transmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named <strong>riTRANX</strong>, <strong>riTRANY</strong> and <strong>riTRANZ</strong> respectively.</p>
-
 <p>The TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named <strong>riMULTX</strong>, <strong>riMULTY</strong> and <strong>riMULTZ</strong> respectively. The derived properties are listed under <strong>Static</strong> properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.</p>
-
 <h3 id="directional-combined-results">Directional Combined Results</h3>
-
 <p>Cell properties with names ending in I, J, K, X, Y, or Z, and an optional &ldquo;+&rdquo; or &ldquo;-&rdquo; are combined into derived results post-fixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).</p>
-
-<p>These combined cell properties visualize the property as a color in all directions combined when selected in
+<p>These combined cell properties visualize the property as a color in all directions combined when selected in 
 as a <strong>Cell Result</strong> and <strong>Separate Fault Result</strong>.</p>
-
 <p>The face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.</p>
-
 <p>The directional combined parameters available are:</p>
-
 <ul>
 <li>Static Properties
-
 <ul>
 <li><strong>TRANXYZ</strong> (inluding NNCs)</li>
 <li><strong>MULTXYZ</strong></li>
 <li><strong>riTRANXYZ</strong> (inluding NNCs)</li>
 <li><strong>riMULTXYZ</strong> (inluding NNCs)</li>
 <li><strong>riTRANXYZbyArea</strong> (inluding NNCs)</li>
-</ul></li>
+</ul>
+</li>
 <li>Dynamic Properties
-
 <ul>
 <li><strong>FLRWATIJK</strong> (inluding NNCs)</li>
 <li><strong>FLROILIJK</strong> (inluding NNCs)</li>
 <li><strong>FLRGASIJK</strong> (inluding NNCs)</li>
-</ul></li>
+</ul>
+</li>
 <li>Generated
-
 <ul>
 <li>Octave generated results with same name but ending with I,J and K will also be combined into a <em><code>&lt;name&gt;IJK</code></em> cell property.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <h3 id="completion-type">Completion Type</h3>
-
-<p><img src="/images/appendix/CompletionTypes.png" alt="" /></p>
-
+<p><img src="/images/appendix/CompletionTypes.png" alt=""></p>
 <p>The dynamic cell property named <strong>Completion Type</strong> is calculated from the intersections between <a href="/wells-and-completions/completions/">Completions</a> and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.</p>
-
 <p>If a cell is completed with multiple completions, the following priority is used : <strong>Fracture</strong>, <strong>Fishbones</strong>, and <strong>Perforation Interval</strong>.</p>
-
 <h3 id="identification-of-questionable-nncs">Identification of Questionable NNCs</h3>
-
 <p>In the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the <strong>Faults/NNCs With No Common Area</strong> folder. These NNCs are questionable since flow normally is associated with a flow area.</p>
-
-<p><img src="/images/appendix/ResInsight_NNCsWithNoCommonArea.png" alt="" /></p>
-
+<p><img src="/images/appendix/ResInsight_NNCsWithNoCommonArea.png" alt=""></p>
 <h3 id="water-flooded-pv">Water Flooded PV</h3>
-
 <p>Water Flooded PV, also called <em>Number of flooded porevolumes</em> shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.</p>
-
 <h2 id="derived-geomechanical-results">Derived Geomechanical results</h2>
-
 <p>ResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.</p>
-
 <h3 id="relative-results-time-lapse-results">Relative Results (Time Lapse Results)</h3>
-
 <p>ResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results.
 When enabled, every result variable is calculated as :</p>
-
 <p>Value&rsquo;(t) = Value(t) - Value(BaseTime)</p>
-
 <p>Enable the <strong>Enable Relative Result</strong>  option in the <strong>Relative Result Options</strong> group, and select the appropriate <strong>Base Time Step</strong>.</p>
-
-<p><img src="/images/appendix/DerivedRelativeResults.png" alt="" /></p>
-
+<p><img src="/images/appendix/DerivedRelativeResults.png" alt=""></p>
 <p>Each variable is then post-fixed with &ldquo;_D<em>TimeStepIndex</em>&rdquo; to distinguish them from the native variables.</p>
-
 <p>Note: Relative Results calculated based on Gamma values are calculated slightly differently:</p>
-
 <p>Gamma_D<em>n</em> = ST_D<em>n</em> / POR_D<em>n</em></p>
-
 <h3 id="derived-result-fields">Derived Result Fields</h3>
-
 <p>The calculated result fields are:</p>
-
 <ul>
 <li>Nodal
-
 <ul>
 <li>COMPACTION (Magnitude of compression)</li>
-</ul></li>
+</ul>
+</li>
 <li>Element Nodal and Integration Points
-
 <ul>
 <li>ST (Total Stress)
-
 <ul>
 <li>All tensor components</li>
-<li>Principals, with directions (S<sub>i</sub>inc, S<sub>i</sub>azi)</li>
+<li>Principals, with directions (S<!-- raw HTML omitted -->i<!-- raw HTML omitted -->inc, S<!-- raw HTML omitted -->i<!-- raw HTML omitted -->azi)</li>
 <li>STM (Mean total stress)</li>
 <li>Q (Deviatoric stress)</li>
-</ul></li>
+</ul>
+</li>
 <li>Gamma (Stress path)</li>
 <li>SE (Effective Stress)
-
 <ul>
 <li>All tensor components</li>
 <li>Principals, with directions</li>
@@ -1965,179 +1931,118 @@ When enabled, every result variable is calculated as :</p>
 <li>SFI</li>
 <li>FOS</li>
 <li>DSM</li>
-</ul></li>
+</ul>
+</li>
 <li>E (Strain)
-
 <ul>
 <li>All tensor components</li>
 <li>EV (Volumetric strain)</li>
 <li>ED (Deviatoric strain)</li>
-</ul></li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li>Element Nodal On Face
-
 <ul>
-<li>Plane</li>
+<li>Plane
+<ul>
 <li>Pinc (Face inclination angle)</li>
 <li>Pazi (Face azimuth angle)</li>
-<li>Transformed Total and Effective Stress</li>
+</ul>
+</li>
+<li>Transformed Total and Effective Stress
+<ul>
 <li>SN (Stress component normal to face)</li>
 <li>TP (Total in-plane shear)</li>
 <li>TPinc (Direction of TP)</li>
 <li>TPH ( Horizontal in-plane shear component )</li>
 <li>TPQV ( Quasi vertical in-plane shear component )</li>
 <li>FAULTMOB</li>
-<li>PCRIT
-<br /></li>
-</ul></li>
+<li>PCRIT</li>
+</ul>
+</li>
+</ul>
+</li>
 </ul>
-
 <h4 id="definitions-of-derived-results">Definitions of Derived Results</h4>
-
 <p>In this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.</p>
-
 <p>Components with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.</p>
-
 <p>Components with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to  X, Y, and Z and thus also easting, northing, and depth.</p>
-
 <ul>
 <li>Inclination is measured from the downwards direction</li>
 <li>Azimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.</li>
 </ul>
-
 <h5 id="case-constants">Case Constants</h5>
-
 <p>Two constants can be assigned to a Geomechanical case:</p>
-
 <ul>
 <li>Cohesion</li>
 <li>Friction angle</li>
 </ul>
-
 <p>In the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.</p>
-
-<p><img src="/images/appendix/GeoMechCasePropertyPanel.png" alt="" /></p>
-
+<p><img src="/images/appendix/GeoMechCasePropertyPanel.png" alt=""></p>
 <h5 id="compaction">COMPACTION</h5>
-
 <p>Compaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer.
 The reference K layer is specified in the property editor.</p>
-
-<p>For each node <i>n</i> in the grid, a node <i>nref</i> in the reference K layer is found by vertical intersection from the node <i>n</i>.</p>
-
-<p>If Depth<sub>n</sub> &lt;= Depth<sub>nref</sub>:</p>
-
-<p>COMPACTION<sub>n</sub> = -(U3<sub>n</sub> - U3<sub>nref</sub>)</p>
-
+<p>For each node <!-- raw HTML omitted -->n<!-- raw HTML omitted --> in the grid, a node <!-- raw HTML omitted -->nref<!-- raw HTML omitted --> in the reference K layer is found by vertical intersection from the node <!-- raw HTML omitted -->n<!-- raw HTML omitted -->.</p>
+<p>If Depth<!-- raw HTML omitted -->n<!-- raw HTML omitted --> &lt;= Depth<!-- raw HTML omitted -->nref<!-- raw HTML omitted -->:</p>
+<p>COMPACTION<!-- raw HTML omitted -->n<!-- raw HTML omitted --> = -(U3<!-- raw HTML omitted -->n<!-- raw HTML omitted --> - U3<!-- raw HTML omitted -->nref<!-- raw HTML omitted -->)</p>
 <p>else:</p>
-
-<p>COMPACTION<sub>n</sub> = -(U3<sub>nref</sub> - U3<sub>n</sub>)</p>
-
-<h5 id="st-total-stress">ST - Total Stress</h5>
-
-<p>ST<sub>ii</sub> = -Sa<sub>ii</sub> + POR (i= 1,2,3)</p>
-
-<p>ST<sub>ij</sub> = -Sa<sub>ij</sub> (i,j = 1,2,3 and i not equal j)</p>
-
+<p>COMPACTION<!-- raw HTML omitted -->n<!-- raw HTML omitted --> = -(U3<!-- raw HTML omitted -->nref<!-- raw HTML omitted --> - U3<!-- raw HTML omitted -->n<!-- raw HTML omitted -->)</p>
+<h5 id="st---total-stress">ST - Total Stress</h5>
+<p>ST<!-- raw HTML omitted -->ii<!-- raw HTML omitted --> = -Sa<!-- raw HTML omitted -->ii<!-- raw HTML omitted --> + POR (i= 1,2,3)</p>
+<p>ST<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> = -Sa<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> (i,j = 1,2,3 and i not equal j)</p>
 <p>We use a value of POR=0.0 where it is not defined.</p>
-
-<p>ST<sub>i</sub> = Principal value i of ST</p>
-
-<h5 id="stm-total-mean-stress">STM - Total Mean Stress</h5>
-
-<p>STM = (ST<sub>11</sub> + ST<sub>22</sub> + ST<sub>33</sub>)/3</p>
-
-<h5 id="q-deviatoric-stress">Q - Deviatoric Stress</h5>
-
-<p>Q = sqrt( (<sup>3</sup>&frasl;<sub>2</sub>) * ( (ST<sub>1</sub> – STM)<sup>2</sup>  + (ST<sub>2</sub> – STM)<sup>2</sup>  + (ST<sub>3</sub> – STM)<sup>2</sup> ))</p>
-
-<h5 id="gamma-stress-path">Gamma - Stress Path</h5>
-
-<p>Gamma<sub>ii</sub> = ST<sub>ii</sub>/POR (i= 1,2,3)</p>
-
-<p>Gamma<sub>i</sub> = ST<sub>i</sub>/POR</p>
-
+<p>ST<!-- raw HTML omitted -->i<!-- raw HTML omitted --> = Principal value i of ST</p>
+<h5 id="stm---total-mean-stress">STM - Total Mean Stress</h5>
+<p>STM = (ST<!-- raw HTML omitted -->11<!-- raw HTML omitted --> + ST<!-- raw HTML omitted -->22<!-- raw HTML omitted --> + ST<!-- raw HTML omitted -->33<!-- raw HTML omitted -->)/3</p>
+<h5 id="q---deviatoric-stress">Q - Deviatoric Stress</h5>
+<p>Q = sqrt( (3/2) * ( (ST<!-- raw HTML omitted -->1<!-- raw HTML omitted --> – STM)<!-- raw HTML omitted -->2<!-- raw HTML omitted -->  + (ST<!-- raw HTML omitted -->2<!-- raw HTML omitted --> – STM)<!-- raw HTML omitted -->2<!-- raw HTML omitted -->  + (ST<!-- raw HTML omitted -->3<!-- raw HTML omitted --> – STM)<!-- raw HTML omitted -->2<!-- raw HTML omitted --> ))</p>
+<h5 id="gamma---stress-path">Gamma - Stress Path</h5>
+<p>Gamma<!-- raw HTML omitted -->ii<!-- raw HTML omitted --> = ST<!-- raw HTML omitted -->ii<!-- raw HTML omitted -->/POR (i= 1,2,3)</p>
+<p>Gamma<!-- raw HTML omitted -->i<!-- raw HTML omitted --> = ST<!-- raw HTML omitted -->i<!-- raw HTML omitted -->/POR</p>
 <p>In these calculations we set Gamma to <em>undefined</em> if abs(POR) &gt; 0.01 MPa.</p>
-
-<h5 id="se-effective-stress">SE - Effective Stress</h5>
-
-<p>SE<sub>ij</sub> = -Sa<sub>ij</sub> (Where POR is defined)</p>
-
-<p>SE<sub>ij</sub> = <em>undefined</em> (Were POR is not defined)</p>
-
-<p>SE<sub>i</sub> = Principal value i of SE</p>
-
-<h5 id="sem-effective-mean-stress">SEM - Effective Mean Stress</h5>
-
-<p>SEM = (SE<sub>11</sub> + SE<sub>22</sub> + SE<sub>33</sub>)/3</p>
-
+<h5 id="se---effective-stress">SE - Effective Stress</h5>
+<p>SE<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> = -Sa<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> (Where POR is defined)</p>
+<p>SE<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> = <em>undefined</em> (Were POR is not defined)</p>
+<p>SE<!-- raw HTML omitted -->i<!-- raw HTML omitted --> = Principal value i of SE</p>
+<h5 id="sem---effective-mean-stress">SEM - Effective Mean Stress</h5>
+<p>SEM = (SE<!-- raw HTML omitted -->11<!-- raw HTML omitted --> + SE<!-- raw HTML omitted -->22<!-- raw HTML omitted --> + SE<!-- raw HTML omitted -->33<!-- raw HTML omitted -->)/3</p>
 <h5 id="sfi">SFI</h5>
-
-<p>SFI  =   ( (s0/tan(fa)  + 0.5*(SE<sub>1</sub> + SE<sub>3</sub>))<em>sin(fa)  ) /(0.5</em>(SE<sub>1</sub>-SE<sub>3</sub>) )</p>
-
+<p>SFI  =   ( (s0/tan(fa)  + 0.5*(SE<!-- raw HTML omitted -->1<!-- raw HTML omitted --> + SE<!-- raw HTML omitted -->3<!-- raw HTML omitted -->))*sin(fa)  ) /(0.5*(SE<!-- raw HTML omitted -->1<!-- raw HTML omitted -->-SE<!-- raw HTML omitted -->3<!-- raw HTML omitted -->) )</p>
 <h5 id="dsm">DSM</h5>
-
 <p>DSM = tan(rho)/tan(fa)</p>
-
 <p>where</p>
-
-<p>rho = 2 * (arctan (sqrt (( SE<sub>1</sub> + a)/(SE<sub>3</sub> + a)) ) – pi/4)</p>
-
+<p>rho = 2 * (arctan (sqrt (( SE<!-- raw HTML omitted -->1<!-- raw HTML omitted --> + a)/(SE<!-- raw HTML omitted -->3<!-- raw HTML omitted --> + a)) ) – pi/4)</p>
 <p>a = s0/tan(fa)</p>
-
 <h5 id="fos">FOS</h5>
-
 <p>FOS = 1/DSM</p>
-
-<h5 id="e-strain">E - Strain</h5>
-
-<p>E<sub>ij</sub> = -Ea<sub>ij</sub></p>
-
-<h5 id="ev-volumetric-strain">EV - Volumetric Strain</h5>
-
+<h5 id="e---strain">E - Strain</h5>
+<p>E<!-- raw HTML omitted -->ij<!-- raw HTML omitted --> = -Ea<!-- raw HTML omitted -->ij<!-- raw HTML omitted --></p>
+<h5 id="ev---volumetric-strain">EV - Volumetric Strain</h5>
 <p>EV = E11 + E22 + E33</p>
-
-<h5 id="ed-deviatoric-strain">ED - Deviatoric Strain</h5>
-
+<h5 id="ed---deviatoric-strain">ED - Deviatoric Strain</h5>
 <p>ED = 2*(E1-E3)/3</p>
-
 <h5 id="element-nodal-on-face">Element Nodal On Face</h5>
-
-<p>For each face displayed, (might be an element face or an intersection/intersection box face),
+<p>For each face displayed, (might be an element face or an intersection/intersection box face), 
 a coordinate system is established such that:</p>
-
 <ul>
 <li>Ez is normal to the face, named N - Normal</li>
 <li>Ex is horizontal and in the plane of the face, named H - Horizontal</li>
 <li>Ey is in the plane pointing upwards, named QV - Quasi Vertical</li>
 </ul>
-
 <p>The stress tensors in that particular face are then transformed to that coordinate system.  The following quantities are derived from the transformed tensor named TS in the following:</p>
-
-<h5 id="sn-stress-component-normal-to-face">SN - Stress component Normal to face</h5>
-
-<p>SN = TS<sub>33</sub></p>
-
-<h5 id="tph-horizontal-in-plane-shear-component">TPH - Horizontal in-plane shear component</h5>
-
-<p>TPH = TS<sub>31</sub> = TS<sub>ZX</sub></p>
-
-<h5 id="tnqv-horizontal-in-plane-shear-component">TNQV - Horizontal in-plane shear component</h5>
-
-<p>TPQV = TS<sub>32</sub> = TS<sub>ZY</sub></p>
-
-<h5 id="tp-total-in-plane-shear">TP - Total in-plane shear</h5>
-
-<p>TP = sqrt(TPH<sup>2</sup> + TPQV<sup>2</sup>)</p>
-
-<h5 id="tpinc-direction-of-tp">TPinc - Direction of TP</h5>
-
+<h5 id="sn---stress-component-normal-to-face">SN - Stress component Normal to face</h5>
+<p>SN = TS<!-- raw HTML omitted -->33<!-- raw HTML omitted --></p>
+<h5 id="tph---horizontal-in-plane-shear-component">TPH - Horizontal in-plane shear component</h5>
+<p>TPH = TS<!-- raw HTML omitted -->31<!-- raw HTML omitted --> = TS<!-- raw HTML omitted -->ZX<!-- raw HTML omitted --></p>
+<h5 id="tnqv---horizontal-in-plane-shear-component">TNQV - Horizontal in-plane shear component</h5>
+<p>TPQV = TS<!-- raw HTML omitted -->32<!-- raw HTML omitted --> = TS<!-- raw HTML omitted -->ZY<!-- raw HTML omitted --></p>
+<h5 id="tp---total-in-plane-shear">TP - Total in-plane shear</h5>
+<p>TP = sqrt(TPH<!-- raw HTML omitted -->2<!-- raw HTML omitted --> + TPQV<!-- raw HTML omitted -->2<!-- raw HTML omitted -->)</p>
+<h5 id="tpinc---direction-of-tp">TPinc - Direction of TP</h5>
 <p>Angle of the total in-plane shear relative to the Quasi Vertical direction</p>
-
 <p>TPinc = acos(TPQV/TP)</p>
-
-<h5 id="pinc-and-pazi-face-inclination-and-azimuth">Pinc and Pazi - Face Inclination and Azimuth</h5>
-
+<h5 id="pinc-and-pazi---face-inclination-and-azimuth">Pinc and Pazi - Face Inclination and Azimuth</h5>
 <p>These are the directional angles of the face-normal itself.</p>
 
 
@@ -2314,6 +2219,19 @@ a coordinate system is established such that:</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2324,6 +2242,9 @@ a coordinate system is established such that:</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3474,20 +3395,20 @@ a coordinate system is established such that:</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/faults/index.html b/3d-main-window/faults/index.html
index d8ffb394c2..29e892bd86 100644
--- a/3d-main-window/faults/index.html
+++ b/3d-main-window/faults/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Faults :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,37 +1802,23 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#fault-detection">Fault Detection</a>
-<ul>
-<li><a href="#information-from-data-files">Information from <code>*.DATA</code>-files</a>
-<ul>
-<li><a href="#fault-information">Fault Information</a></li>
-<li><a href="#nnc-data">NNC Data</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#fault-visualization-options">Fault Visualization Options</a>
-<ul>
-<li><a href="#fault-visibility">Fault Visibility</a></li>
-<li><a href="#fault-color">Fault Color</a></li>
-<li><a href="#separate-fault-result">Separate Fault Result</a></li>
-<li><a href="#toolbar-control">Toolbar Control</a></li>
-<li><a href="#faults-properties">Faults Properties</a>
-<ul>
-<li>
-<ul>
-<li><a href="#fault-labels">Fault Labels</a></li>
-<li><a href="#fault-options">Fault Options</a></li>
-<li><a href="#fault-face-visibility">Fault Face Visibility</a></li>
-<li><a href="#nnc-visibility">NNC Visibility</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-<li><a href="#fault-export">Fault Export</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#fault-detection">Fault Detection</a>
+      <ul>
+        <li><a href="#information-from-data-files">Information from <code>*.DATA</code>-files</a></li>
+      </ul>
+    </li>
+    <li><a href="#fault-visualization-options">Fault Visualization Options</a>
+      <ul>
+        <li><a href="#fault-visibility">Fault Visibility</a></li>
+        <li><a href="#fault-color">Fault Color</a></li>
+        <li><a href="#separate-fault-result">Separate Fault Result</a></li>
+        <li><a href="#toolbar-control">Toolbar Control</a></li>
+        <li><a href="#faults-properties">Faults Properties</a></li>
+      </ul>
+    </li>
+    <li><a href="#fault-export">Fault Export</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1823,140 +1843,93 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/FaultsIllustration.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FaultsIllustration.png" alt=""></p>
 <p>This section describes how Faults are detected and visualized. NNC&rsquo;s are a part of the Faults visualization and are thus also mentioned in this section.</p>
-
 <h2 id="fault-detection">Fault Detection</h2>
-
 <p>ResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.</p>
-
 <p>All the tagged cell faces are then compared to the faults possibly imported from the <em><code>*.DATA</code></em> file in order to group them. If a particular face is <em>not</em> found among the fault faces defined in the <em><code>*.DATA</code></em> file (or their opposite faces), the cell face is added to one of two predefined faults:</p>
-
 <ul>
 <li><strong>Undefined grid faults</strong></li>
 <li><strong>Undefined grid faults With Inactive</strong></li>
 </ul>
-
 <p>The first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.</p>
-
 <p>These particular Faults will always be present, even when reading of fault information from the <em><code>*.DATA</code></em> file is disabled.</p>
-
 <h3 id="information-from-data-files">Information from <code>*.DATA</code>-files</h3>
-
 <h4 id="fault-information">Fault Information</h4>
-
 <p>If enabled in <strong>Preferences</strong>, ResInsight will import fault information from the <em><code>*.DATA</code></em> files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.</p>
 
-
-<div class="notices info" ><p>The <b>DATA</b> file is parsed for the <b>FAULT</b> keyword while respecting any <b>INCLUDE</b> and <b>PATH</b> keywords.<br>
-As import of faults can be time consuming, reading of faults can be disabled from <b>Preferences-&gt;Import faults</b></p>
+<div class="notices info" ><p>The <!-- raw HTML omitted -->DATA<!-- raw HTML omitted --> file is parsed for the <!-- raw HTML omitted -->FAULT<!-- raw HTML omitted --> keyword while respecting any <!-- raw HTML omitted -->INCLUDE<!-- raw HTML omitted --> and <!-- raw HTML omitted -->PATH<!-- raw HTML omitted --> keywords.<!-- raw HTML omitted -->
+As import of faults can be time consuming, reading of faults can be disabled from <!-- raw HTML omitted -->Preferences-&gt;Import faults<!-- raw HTML omitted --></p>
 </div>
 
-
 <h4 id="nnc-data">NNC Data</h4>
-
-<p>If enabled in <strong>Preferences</strong>, ResInsight will read Non Neighbor Connections from the Eclipse output file (<em><code>*.INIT</code></em>), and create explicit visualizations of those.
+<p>If enabled in <strong>Preferences</strong>, ResInsight will read Non Neighbor Connections from the Eclipse output file (<em><code>*.INIT</code></em>), and create explicit visualizations of those. 
 The NNC&rsquo;s are sorted onto the Fault&rsquo;s and their visibility is controlled along with them.</p>
-
 <h2 id="fault-visualization-options">Fault Visualization Options</h2>
-
 <h3 id="fault-visibility">Fault Visibility</h3>
-
 <p>Faults can be hidden and shown in several ways.</p>
-
 <ul>
 <li>Checking or unchecking the checkbox in front of the fault will show or hide the fault.</li>
 <li>Visibility for multiple faults can be controlled at the same time by selecting multiple faults and use the right-click menu: <strong>On</strong>, <strong>Off</strong> and <strong>Toggle</strong>.</li>
 <li>Hide the fault from the  right-click menu of a Fault in the 3D View.</li>
 </ul>
-
 <h3 id="fault-color">Fault Color</h3>
-
 <p>Each named Fault is given a color on import. This color can be controlled by selecting the fault and edit its  <strong>Fault color</strong> in the <strong>Property Editor.</strong></p>
-
 <h3 id="separate-fault-result">Separate Fault Result</h3>
-
 <p>The default result mapping used on faults are to use the same as specified in <strong>Cell Result</strong>. If a different result mapping is wanted, enable the checkbox at <strong>Separate Fault Result</strong> and select the result from the result selection dialog in the <strong>Property Editor</strong>. A second legend for the fault result is then added to the view.</p>
-
 <h3 id="toolbar-control">Toolbar Control</h3>
-
 <p>Visualization mode and mesh lines can be controlled from the toolbar.</p>
-
 <ul>
 <li><img src="https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png" style="display:inline; vertical-align:middle; margin:0">
-<strong>Faults-Only</strong> visualization mode.
-<br>When turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless <strong>Show faults outside filters</strong> are turned on. See below.)</li>
+<strong>Faults-Only</strong> visualization mode. 
+<!-- raw HTML omitted -->When turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless <strong>Show faults outside filters</strong> are turned on. See below.)</li>
 <li><img src="https://resinsight.org/images/3d-main-window/draw_style_surface_24x24.png" style="display:inline; vertical-align:middle; margin:0">
  Turns faces on and mesh off</li>
 <li><img src="https://resinsight.org/images/3d-main-window/draw_style_surface_w_fault_mesh_24x24.png" style="display:inline; vertical-align:middle; margin:0">
  Turns on all faces, and shows mesh lines on faults only.
-<br> This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining.</li>
+<!-- raw HTML omitted --> This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining.</li>
 <li><img src="https://resinsight.org/images/3d-main-window/draw_style_faults_label_24x24.png" style="display:inline; vertical-align:middle; margin:0">
- Shows labels for faults<br /></li>
+ Shows labels for faults</li>
 </ul>
-
 <h3 id="faults-properties">Faults Properties</h3>
-
 <p>By clicking the <img src="https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Faults</strong> item in the <strong>Project Tree</strong>, the following options common to all the faults are displayed:</p>
-
-<p><img src="/images/3d-main-window/FaultProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FaultProperties.png" alt=""></p>
 <h5 id="fault-labels">Fault Labels</h5>
-
 <ul>
 <li><strong>Show labels</strong> &ndash; Displays one label per fault with the name defined in the <em><code>*.DATA</code></em> file</li>
 <li><strong>Label color</strong> &ndash; Defines the label color</li>
 </ul>
-
 <h5 id="fault-options">Fault Options</h5>
-
 <ul>
 <li><strong>Show faults outside filters</strong> &ndash; Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.</li>
 </ul>
-
 <h5 id="fault-face-visibility">Fault Face Visibility</h5>
-
 <p>This group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.</p>
-
 <p>First of all, these options are only available in <strong>Faults-only</strong> visualization mode ( See <a href="#toolbar-control">Toolbar Control</a> ). When not in <strong>Faults-Only</strong> mode, ResInsight overrides the options, and the controls are inactive.</p>
-
 <p>Secondly, the option you would normally want to adjust is <strong>Dynamic Face Selection</strong> ( See below ).</p>
-
 <ul>
 <li><strong>Show defined faces</strong> &ndash; Displays the fault cell faces that are defined on the Eclipse input file (<em><code>*.DATA</code></em>)</li>
-<li><strong>Show opposite faces</strong> &ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.<br />
-*These two options should normally be left <strong>On</strong>. They are useful when investigating the exact faults information provided on the <code>*.DATA</code> file. If you need to use them, it is normally wise to set the <strong>Dynamic Face Selection</strong> to &ldquo;Show Both&rdquo;.*</li>
-<li><strong>Dynamic Face Selection</strong> &ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.<br />
-This option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.<br />
+<li><strong>Show opposite faces</strong> &ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.<br>
+<em>These two options should normally be left <strong>On</strong>. They are useful when investigating the exact faults information provided on the <code>*.DATA</code> file. If you need to use them, it is normally wise to set the <strong>Dynamic Face Selection</strong> to &ldquo;Show Both&rdquo;.</em></li>
+<li><strong>Dynamic Face Selection</strong> &ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.<br>
+This option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.<br>
 This means that ResInsight turns on or off the faces based on your view position and this option to make sure that you always see the faces (and thus the result property) you request.</li>
 </ul>
-
 <h5 id="nnc-visibility">NNC Visibility</h5>
-
 <ul>
 <li><strong>Show NNCs</strong> &ndash; Toggles whether to display the Non Neighbor Connections, or not.</li>
 <li><strong>Hide NNC geometry if no NNC result is available</strong> &ndash; Automatically hides NNC geometry if no NNC results are available</li>
 </ul>
 
-
 <div class="notices info" ><p>The color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.</p>
 </div>
 
-
 <h2 id="fault-export">Fault Export</h2>
-
 <p>Faults can be exported to separate files in the <em><code>*grdecl</code></em> file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.</p>
-
 <p>To export some faults, select the faults you want to export in the <strong>Project Tree</strong>, and select the command <strong>Export Faults &hellip;</strong> from the right-click menu.</p>
-
-<p><img src="/images/3d-main-window/ExportFaultsMenu.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ExportFaultsMenu.png" alt=""></p>
 <p>You are then prompted to select a destination folder. Each Fault is exported to a file named <em><code>Faults_&lt;fault name&gt;_&lt;case name&gt;.grdecl</code></em> and stored in the selected folder.</p>
-
 <p>The fault name of <strong>Undefined Grid Faults</strong> is simplified to <em><code>UNDEF</code></em>, while <strong>Undefined Grid Faults With Inactive</strong> is simplified to <em><code>UNDEF_IA</code></em>. All other faults keep their original name.</p>
 
 
@@ -2133,6 +2106,19 @@ This means that ResInsight turns on or off the faces based on your view position
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2143,6 +2129,9 @@ This means that ResInsight turns on or off the faces based on your view position
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3293,20 +3282,20 @@ This means that ResInsight turns on or off the faces based on your view position
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/filters/index.html b/3d-main-window/filters/index.html
index 2338539ea3..a4680640c4 100644
--- a/3d-main-window/filters/index.html
+++ b/3d-main-window/filters/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Cell Filters :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,21 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#common-properties-for-range-and-property-filters">Common Properties for Range and Property Filters</a></li>
-<li><a href="#range-filters">Range filters</a></li>
-<li><a href="#property-filters">Property Filters</a>
-<ul>
-<li><a href="#property-value-range">Property Value Range</a>
-<ul>
-<li><a href="#range-behavior-for-flow-diagnostic-results">Range Behavior for Flow Diagnostic Results</a></li>
-</ul></li>
-<li><a href="#category-selection">Category Selection</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#common-properties-for-range-and-property-filters">Common Properties for Range and Property Filters</a></li>
+    <li><a href="#range-filters">Range filters</a></li>
+    <li><a href="#property-filters">Property Filters</a>
+      <ul>
+        <li><a href="#property-value-range">Property Value Range</a></li>
+        <li><a href="#category-selection">Category Selection</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1807,95 +1836,61 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/FiltersOverview.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FiltersOverview.png" alt=""></p>
 <p>Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:</p>
-
 <ul>
 <li><strong>Range Filter</strong> &ndash; Extracts an IJK subset of the model.</li>
 <li><strong>Property Filter</strong> &ndash; Extracts cells with a property value matching a value range.</li>
 </ul>
 
-
-<div class="notices note" ><p>The visibilities of cells connection to wells, and fences based on these cells can be controlled from <b> <a href="/wells-and-completions/simulationwells/">Simulation Wells</a> </b>.<br>
-<small><i>(Not applicable for Geomechanical cases)</i></small></p>
+<div class="notices note" ><p>The visibilities of cells connection to wells, and fences based on these cells can be controlled from <!-- raw HTML omitted --> <!-- raw HTML omitted -->Simulation Wells<!-- raw HTML omitted --> <!-- raw HTML omitted -->.<!-- raw HTML omitted --> 
+<!-- raw HTML omitted --><!-- raw HTML omitted -->(Not applicable for Geomechanical cases)<!-- raw HTML omitted --><!-- raw HTML omitted --></p>
 </div>
 
-
 <h2 id="common-properties-for-range-and-property-filters">Common Properties for Range and Property Filters</h2>
-
 <p>Both filter types can be turned on or off using the toggle in the <strong>Project Tree</strong> and controlled from their corresponding <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/3d-main-window/FiltersInTreeView.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FiltersInTreeView.png" alt=""></p>
 <p>Range Filters and Property filters can either be set to <strong>Include</strong> cells or to <strong>Exclude</strong> them.</p>
-
-<p>The <strong>Exclude</strong> setting is used to explicitly remove cells from the visualization, regardless of what other filters say.
+<p>The <strong>Exclude</strong> setting is used to explicitly remove cells from the visualization, regardless of what other filters say. 
 The <strong>Include</strong> setting behaves differently for Range filters and Property Filters but marks the cells as visible.
 The icon in front of the filters show a + or - sign to indicate the setting <img src="https://resinsight.org/images/3d-main-window/FilterIncEx.png" style="display:inline; vertical-align:middle; margin:0">
 </p>
-
 <h2 id="range-filters">Range filters</h2>
-
 <p>Range filters enables the user to define a set of visible regions in the 3D view based on IJK boxes.
 Each <em>Include</em> range filter will <em>add more cells</em> to the visualization. The view will show the union of all the <em>Include</em> range filters.</p>
-
 <p>A new range filter can be added by activating the right-click menu for the <strong>Range Filters</strong> collection in the <strong>Project Tree</strong>.</p>
 
-
-<div class="notices note" ><p>An I,J or K-slice range filter can be added directly from a Cell in the <b>3D View</b> by right-clicking the cell and using the right-click menu.</p>
+<div class="notices note" ><p>An I,J or K-slice range filter can be added directly from a Cell in the <!-- raw HTML omitted -->3D View<!-- raw HTML omitted --> by right-clicking the cell and using the right-click menu.</p>
 </div>
 
-
 <p>Below is a snapshot of the <strong>Property Editor</strong> of the <strong>Range Filter</strong> :</p>
-
-<p><img src="/images/3d-main-window/RangeFilterProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/RangeFilterProperties.png" alt=""></p>
 <ul>
 <li><strong>Filter Type</strong> &ndash; The filter can either make the specified range visible ( <em>Include</em> ), or remove the range from the View ( <em>Exclude</em> ).</li>
 <li><strong>Grid</strong> &ndash;  This option selects which of the grids the range is addressing.</li>
-<li><strong>Apply to Subgrids</strong> &ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR&rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.<br /></li>
+<li><strong>Apply to Subgrids</strong> &ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR&rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.</li>
 </ul>
-
-<p>The <strong>Start</strong> and <strong>Width</strong> labels in front of the sliders features a number in parenthesis denoting maximum available value.<br>
-The <strong>Start</strong> labels shows the index of the start of the active cells.<br>
+<p>The <strong>Start</strong> and <strong>Width</strong> labels in front of the sliders features a number in parenthesis denoting maximum available value.<!-- raw HTML omitted -->
+The <strong>Start</strong> labels shows the index of the start of the active cells.<!-- raw HTML omitted -->
 The <strong>Width</strong> labels shows the number of active cells from the start of the active cells.</p>
-
 <h2 id="property-filters">Property Filters</h2>
-
 <p><strong>Property Filters</strong> applies to the results of the <strong>Range Filters</strong> and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.</p>
-
 <p>A new property filter can be made by activating the right-click menu on <strong>Property Filters</strong> or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.</p>
+<p>The name of the property filter is automatically set to <em>&ldquo;propertyname (min .. max)&quot;</em> as you edit the property filter.</p>
 
-<p>The name of the property filter is automatically set to <em>&ldquo;propertyname (min .. max)&rdquo;</em> as you edit the property filter.</p>
-
-
-<div class="notices note" ><p>The context command <b>Apply As Cell Result</b> on a property filter, sets the Cell Color Result to the same values as the selected property filter.</p>
+<div class="notices note" ><p>The context command <!-- raw HTML omitted -->Apply As Cell Result<!-- raw HTML omitted --> on a property filter, sets the Cell Color Result to the same values as the selected property filter.</p>
 </div>
 
-
 <p>Below is a snapshot of the <strong>Property Editor</strong> of the <strong>Property Filter</strong>.</p>
-
-<p><img src="/images/3d-main-window/PropertyFilterProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PropertyFilterProperties.png" alt=""></p>
 <h3 id="property-value-range">Property Value Range</h3>
-
 <p>The filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the <strong>Filter Type</strong> (<em>Include</em>/<em>Exclude</em>). Exclude-filters removes the selected cells from the <strong>View</strong> even if some other filter includes them.</p>
-
 <h4 id="range-behavior-for-flow-diagnostic-results">Range Behavior for Flow Diagnostic Results</h4>
-
 <p>Normally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.</p>
-
 <p>We still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.</p>
-
 <h3 id="category-selection">Category Selection</h3>
-
 <p>If the property is representing integer values, well tracer names or <a href="/3d-main-window/formations"> formation names </a>, the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.</p>
-
-<p><img src="/images/3d-main-window/PropertyFilterWithCategories.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PropertyFilterWithCategories.png" alt=""></p>
 <p>If it is more convenient to filter the values using a value range, toggle the <strong>Category Selection</strong> option off.</p>
 
 
@@ -2072,6 +2067,19 @@ The <strong>Width</strong> labels shows the number of active cells from the star
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2082,6 +2090,9 @@ The <strong>Width</strong> labels shows the number of active cells from the star
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3232,20 +3243,20 @@ The <strong>Width</strong> labels shows the number of active cells from the star
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/formations/index.html b/3d-main-window/formations/index.html
index 14ba2f7bf9..e205d9011c 100644
--- a/3d-main-window/formations/index.html
+++ b/3d-main-window/formations/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> Zonations/Formations :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,35 +1802,21 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#formations-for-k-layers">Formations for k-layers</a>
-<ul>
-<li><a href="#import-of-formation-names-files">Import of Formation Names Files</a>
-<ul>
-<li><a href="#formation-names-description-files-lyr">Formation Names description files (<em><code>*.lyr</code></em>)</a></li>
-<li><a href="#fmu-layer-zone-table-layer-zone-table-txt">FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>)</a></li>
-</ul></li>
-<li><a href="#select-the-formation-file-in-a-case">Select the Formation File in a Case</a>
-<ul>
-<li><a href="#reload-of-formation-data">Reload of formation data</a></li>
-</ul></li>
-<li><a href="#viewing-the-formation-information">Viewing the Formation Information</a>
-<ul>
-<li><a href="#formations-in-3d-view">Formations in 3D View</a></li>
-<li><a href="#property-filter-based-on-formations">Property Filter Based on Formations</a></li>
-<li><a href="#picking-in-3d-view">Picking in 3D View</a></li>
-<li><a href="#annotations-on-plots">Annotations on Plots</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#well-picks">Well Picks</a>
-<ul>
-<li><a href="#import-of-well-pick-files">Import of Well Pick Files</a></li>
-<li><a href="#viewing-the-well-picks">Viewing the Well Picks</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#formations-for-k-layers">Formations for k-layers</a>
+      <ul>
+        <li><a href="#import-of-formation-names-files">Import of Formation Names Files</a></li>
+        <li><a href="#select-the-formation-file-in-a-case">Select the Formation File in a Case</a></li>
+        <li><a href="#viewing-the-formation-information">Viewing the Formation Information</a></li>
+      </ul>
+    </li>
+    <li><a href="#well-picks">Well Picks</a>
+      <ul>
+        <li><a href="#import-of-well-pick-files">Import of Well Pick Files</a></li>
+        <li><a href="#viewing-the-well-picks">Viewing the Well Picks</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1821,54 +1841,35 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/formations_legend.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/formations_legend.PNG" alt=""></p>
 <p>This section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.</p>
-
 <h2 id="formations-for-k-layers">Formations for k-layers</h2>
-
 <p>Formation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the <strong>Result info</strong> panel when selecting single cells.</p>
-
 <p>To use this functionality you will need to :</p>
-
 <ol>
 <li>Import one or more Formation Names file(s)</li>
 <li>Select the correct Formation Names file in the Case of interest</li>
 </ol>
-
 <h3 id="import-of-formation-names-files">Import of Formation Names Files</h3>
-
 <p>Formation Names files can be imported by using the command: <strong>File-&gt;Import-&gt;Import Formation Names</strong>.</p>
-
 <p>Supported Formation Names files are:</p>
-
 <ul>
 <li>Formation Names description files (<em><code>*.lyr</code></em>)</li>
 <li>FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>)</li>
 </ul>
-
-<p>To select the appropriate file type, use the button to the right of file name in the <em>Import Formation Names</em> dialog.
+<p>To select the appropriate file type, use the button to the right of file name in the <em>Import Formation Names</em> dialog. 
 The imported Formation Names files are then listed in the <strong>Project Tree</strong> in a folder named <strong>Formations</strong>.</p>
-
-<h4 id="formation-names-description-files-lyr">Formation Names description files (<em><code>*.lyr</code></em>)</h4>
-
-<p>Formation Names description files (<em><code>*.lyr</code></em>) consist of a list of formation names and their k-range.
+<h4 id="formation-names-description-files-_lyr_">Formation Names description files (<em><code>*.lyr</code></em>)</h4>
+<p>Formation Names description files (<em><code>*.lyr</code></em>) consist of a list of formation names and their k-range. 
 Below is an example of a Formation Names description file:</p>
-
 <pre><code>-- Any text as comment
 'MyFormationName'                 4 - 12
 'MySecondFormationName'          15 - 17
 '3 k-layer thick 18,19 and 20'    3
 'Last Name'                      21 - 21 
-</code></pre>
-
-<h4 id="fmu-layer-zone-table-layer-zone-table-txt">FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>)</h4>
-
-<p>The FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>) contains two columns to correlate each grid k-layer with a formation name.
+</code></pre><h4 id="fmu-layer-zone-table-_layer_zone_tabletxt_">FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>)</h4>
+<p>The FMU Layer Zone Table (<em><code>layer_zone_table.txt</code></em>) contains two columns to correlate each grid k-layer with a formation name. 
 Below is an example of a <em><code>layer_zone_table.txt</code></em> file:</p>
-
 <pre><code>1   UpperReek
 2   UpperReek
 3   UpperReek
@@ -1883,68 +1884,39 @@ Below is an example of a <em><code>layer_zone_table.txt</code></em> file:</p>
 12  LowerReek
 13  LowerReek
 14  LowerReek
-</code></pre>
-
-<h3 id="select-the-formation-file-in-a-case">Select the Formation File in a Case</h3>
-
+</code></pre><h3 id="select-the-formation-file-in-a-case">Select the Formation File in a Case</h3>
 <p>If only one formation file is imported, the formation will automatically be set in the active view&rsquo;s case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the <strong>Property Editor</strong> for a case. The formation is selected in the combo box for property <strong>Formation Names File</strong>.</p>
-
-<p><img src="/images/3d-main-window/formations_property_editor.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/formations_property_editor.PNG" alt=""></p>
 <h4 id="reload-of-formation-data">Reload of formation data</h4>
-
 <p>If the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu <strong>Formations-&gt;Reload</strong>. This command will import formations for the selected formation files.</p>
-
 <h3 id="viewing-the-formation-information">Viewing the Formation Information</h3>
-
 <h4 id="formations-in-3d-view">Formations in 3D View</h4>
-
 <p>The formations can be visualized as a result property in <strong>Cell Results</strong>, <strong>Cell Edge Result</strong>, and <strong>Separate Fault Result</strong>. When selected, a special legend displaying formation names is activated.</p>
-
 <h4 id="property-filter-based-on-formations">Property Filter Based on Formations</h4>
-
 <p>Formation names are available in Property Filters as Result Type <strong>Formation Names</strong>. This makes it easy to filter geometry based on formation specifications.</p>
-
 <p>See <a href="/3d-main-window/filters/"> Cell Filters </a> for details.</p>
-
 <h4 id="picking-in-3d-view">Picking in 3D View</h4>
-
 <p>Picking on a cell being part of a formation will display the formation name in the <strong>Result Info</strong> windows, in addition to other pick info for the cell.</p>
-
 <h4 id="annotations-on-plots">Annotations on Plots</h4>
-
 <p>Formation can be used to annotate the following plot types:</p>
-
 <ul>
 <li><a href="/plot-window/welllogsandplots/">Well Log Plots</a></li>
 <li><a href="/plot-window/rftplot/">RFT Plots</a></li>
 <li><a href="/plot-window/pltplot/">PLT Plots</a></li>
 <li><a href="/plot-window/flowdiagnosticsplots/">Well Allocation Plots</a></li>
 </ul>
-
-<p><img src="/images/3d-main-window/formOnPlot.PNG" alt="" /> MANGLER BILDE</p>
-
+<p><img src="/images/3d-main-window/formOnPlot.PNG" alt=""> MANGLER BILDE</p>
 <p>For RFT and PLT Plots, <strong>Zonation/Formation Names</strong> can be found in the plot&rsquo;s <strong>Property Editor</strong>. Tick &ldquo;Show Formations&rdquo; and choose the case with the desired formations.</p>
-
 <p>In Well Log Plots and Well Allocation Plots, <strong>Zonation/Formation Names</strong> can be found in the <strong>Property Editor</strong> for a <strong>Track</strong> or <strong>Branch</strong>. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.</p>
-
-<p><img src="/images/3d-main-window/caseFormationsPropEditor.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/caseFormationsPropEditor.PNG" alt=""></p>
 <h2 id="well-picks">Well Picks</h2>
-
 <p>Well Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a <em>fluid</em> or a <em>formation</em>.</p>
-
 <h3 id="import-of-well-pick-files">Import of Well Pick Files</h3>
-
 <p>Well Pick files can be imported by using the command: <strong>File-&gt;Import-&gt;Well Data-&gt;Import Well Picks</strong>.
 The user is asked to select <em><code>*.csv</code></em> files for import.</p>
-
 <p>The imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in <strong>Wells</strong> in the <strong>Project Tree</strong>. The file path of the formations can be found in a well path&rsquo;s <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/3d-main-window/wellPathFormationsInPropertyEditor.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/wellPathFormationsInPropertyEditor.PNG" alt=""></p>
 <p>A Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:</p>
-
 <pre><code>Well name; Column name; Unit name; Top MD; Base MD
 B-3H; FLUID; GAS;2203.2;2317.4
 B-3H; FLUID; OIL;2317.4;2459
@@ -1965,22 +1937,13 @@ B-2H; STRAT; FANGST GP. ;2144.199951;2158.389893
 B-2H; STRAT;   Ile Fm. ;2144.199951;2158.389893
 B-2H; STRAT;     Ile Fm. 2 ;2144.201416;2156.197266
 B-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501
-</code></pre>
-
-<p>The file must have the columns &ldquo;Well name&rdquo;, &ldquo;Unit name&rdquo; (i.e. formation name), &ldquo;Top MD&rdquo; and &ldquo;Base MD&rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.</p>
-
+</code></pre><p>The file must have the columns &ldquo;Well name&rdquo;, &ldquo;Unit name&rdquo; (i.e. formation name), &ldquo;Top MD&rdquo; and &ldquo;Base MD&rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.</p>
 <p>The three unit names <em>OIL</em>, <em>GAS</em> and <em>WATER</em> are interpreted as <em>fluids</em>. Other unit names with only capital letters are <em>groups</em>. A unit name without an index is simply a <em>formation</em>. Unit names with one number is a <em>formation 1</em>, unit names with <em>one</em> punctuation is a <em>formation 2</em>, two punctuations, <em>formation 3</em> and so on. Indentions in column name will be ignored.</p>
-
 <h3 id="viewing-the-well-picks">Viewing the Well Picks</h3>
-
 <p>See <a href="#annotations-on-plots">Annotations on plots</a>. Annotations are added to plots in the same way as for k-layered formations, but the source is different.</p>
-
-<p><img src="/images/3d-main-window/wellFormationsPropEditor.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/wellFormationsPropEditor.PNG" alt=""></p>
 <p>In the <strong>Property Editor</strong>, choose <strong>Well Path</strong> as <strong>Source</strong>, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the <strong>Well Pick Filter</strong> can be used.</p>
-
-<p><img src="/images/3d-main-window/wellPickFilter.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/wellPickFilter.png" alt=""></p>
 <p>The <strong>Well Pick Filter</strong> will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as <em>Fluids</em> are only shown by ticking the <strong>Show Fluids</strong> mark.</p>
 
 
@@ -2157,6 +2120,19 @@ B-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2167,6 +2143,9 @@ B-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3317,20 +3296,20 @@ B-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/gridstatisticsdialog/index.html b/3d-main-window/gridstatisticsdialog/index.html
index 682a9dd0a1..9ed3221355 100644
--- a/3d-main-window/gridstatisticsdialog/index.html
+++ b/3d-main-window/gridstatisticsdialog/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Statistics Dialog :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,22 +1802,21 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#grid-statistics-dialog-fields">Grid Statistics Dialog Fields</a>
-<ul>
-<li><a href="#info-text">Info Text</a></li>
-<li><a href="#histogram">Histogram</a></li>
-<li><a href="#cumulative-histogram">Cumulative Histogram</a></li>
-</ul></li>
-<li><a href="#grid-statistics-configuration">Grid Statistics Configuration</a>
-<ul>
-<li><a href="#statistics-options">Statistics Options</a></li>
-</ul></li>
-<li><a href="#snapshot">Snapshot</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#grid-statistics-dialog-fields">Grid Statistics Dialog Fields</a>
+      <ul>
+        <li><a href="#info-text">Info Text</a></li>
+        <li><a href="#histogram">Histogram</a></li>
+        <li><a href="#cumulative-histogram">Cumulative Histogram</a></li>
+      </ul>
+    </li>
+    <li><a href="#grid-statistics-configuration">Grid Statistics Configuration</a>
+      <ul>
+        <li><a href="#statistics-options">Statistics Options</a></li>
+      </ul>
+    </li>
+    <li><a href="#snapshot">Snapshot</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1808,60 +1841,38 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/GridStatisticsDialog.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/GridStatisticsDialog.png" alt=""></p>
 <p>ResInsight 3D Views has an <a href="/3d-main-window/3dviews/#info-box">info box</a> in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select <strong>Grid Statistics</strong> to bring up the dialog.</p>
-
 <h2 id="grid-statistics-dialog-fields">Grid Statistics Dialog Fields</h2>
-
 <p>The dialog consist of three information parts.</p>
-
 <ul>
 <li>Info text</li>
 <li>Histogram</li>
 <li>Cumulative Histogram</li>
 </ul>
-
 <h3 id="info-text">Info Text</h3>
-
 <p>The Info Text field shows general info about the case, the selected results, and some statistics.</p>
-
 <h3 id="histogram">Histogram</h3>
-
 <p>The histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:</p>
-
 <ul>
 <li>The mean value ( a blue line )</li>
 <li>P10 and P90 ( red lines )</li>
 </ul>
-
 <h3 id="cumulative-histogram">Cumulative Histogram</h3>
-
 <p>The cumulative histogram shows av accumulated version of the histogram above.</p>
-
 <h2 id="grid-statistics-configuration">Grid Statistics Configuration</h2>
-
 <p>A grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The Statistics Options of the info box is shown in the figure below with default settings. These settings become available by clicking in the info box or the info box node in <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/InfoBoxConfig.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/InfoBoxConfig.png" alt=""></p>
 <p>The options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.</p>
-
 <h3 id="statistics-options">Statistics Options</h3>
-
 <ul>
 <li><strong>Statistics Time Range</strong> -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.</li>
 <li><strong>Statistics Cell Range</strong> -– Controls if visible cells or all active cells is included when statistics is computed.</li>
 </ul>
-
 <h2 id="snapshot">Snapshot</h2>
-
 <p>The Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system&rsquo;s clipboard, while the rightmost button creates a file containing the snapshot.</p>
 
-
-<div class="notices note" ><p>The main window also has a snapshot toolbar containing the button <a href="/export/snapshots/#snapshot-all-viewsplots-to-file-">Snapshot All Views</a>. This button will include a snapshot of the Grid Statistics dialog if opened.</p>
+<div class="notices note" ><p>The main window also has a snapshot toolbar containing the button <!-- raw HTML omitted -->Snapshot All Views<!-- raw HTML omitted -->. This button will include a snapshot of the Grid Statistics dialog if opened.</p>
 </div>
 
 
@@ -2039,6 +2050,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2049,6 +2073,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3199,20 +3226,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/index.html b/3d-main-window/index.html
index 04b99941f7..ec7c14a2ab 100644
--- a/3d-main-window/index.html
+++ b/3d-main-window/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Main Window :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,12 +1820,10 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/getting-started/ResInsightUIMediumSize.png" alt="ResInsight User Interface" /></p>
-
-<p>This is the main window of ResInsight for all 3D related functionality and visualization.
-As seen, the <strong>3D Main Window</strong> has a central area and several docking windows surrounding it.
+	<p><img src="/images/getting-started/ResInsightUIMediumSize.png" alt="ResInsight User Interface"></p>
+<p>This is the main window of ResInsight for all 3D related functionality and visualization. 
+As seen, the <strong>3D Main Window</strong> has a central area and several docking windows surrounding it. 
 The different docking windows cover the following:</p>
-
 <ul>
 <li><strong>Project Tree</strong> &ndash; contains all application objects in a tree structure.</li>
 <li><strong>Property Editor</strong> &ndash; displays all properties for selected object in the <strong>Project Tree</strong></li>
@@ -1800,7 +1832,6 @@ The different docking windows cover the following:</p>
 <li><strong>Result Plot</strong> &ndash; displays curves based on result values for the selected cells in the 3D scene</li>
 <li><strong>Messages</strong> &ndash; displays occasional info and warnings related to operations executed.</li>
 </ul>
-
 <p>In addition, a selected subset of actions are presented as controls in the toolbar.
 The following subchapters describe the functionality and visualization pertinent to the <strong>3D Main Window</strong>.</p>
 
@@ -1980,6 +2011,19 @@ The following subchapters describe the functionality and visualization pertinent
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1990,6 +2034,9 @@ The following subchapters describe the functionality and visualization pertinent
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3123,7 +3170,7 @@ The following subchapters describe the functionality and visualization pertinent
 	 
 	 
 		
-			<a class="nav nav-prev" href="/getting-started/modelnavigation/" title="Model Navigation"> <i class="fa fa-chevron-left"></i></a>
+			<a class="nav nav-prev" href="/getting-started/other/" title="Other"> <i class="fa fa-chevron-left"></i></a>
 		
 		
 			<a class="nav nav-next" href="/3d-main-window/3dviews/" title="3D Views" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
@@ -3136,20 +3183,20 @@ The following subchapters describe the functionality and visualization pertinent
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/index.xml b/3d-main-window/index.xml
index 7b3e17a93f..d55636f650 100644
--- a/3d-main-window/index.xml
+++ b/3d-main-window/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>3D Main Window on ResInsight</title>
@@ -49,7 +49,7 @@ Cell Results are used in several operations and settings:
       
       <guid>https://resinsight.org/3d-main-window/comparisonview/</guid>
       <description>ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.
-The figure above exemplifies a Comparison View for comparison of two different simulations models and results.</description>
+The figure above exemplifies a Comparison View for comparison of two different simulations models and results. The left hand side is used to display grid and results of an Eclipse simulation while the right hand side displays an ABAQUS grid and simulation results from geomechanical analysis.</description>
     </item>
     
     <item>
@@ -79,7 +79,7 @@ Visualization The tensor arrows visualize the principal vectors in three directi
       
       <guid>https://resinsight.org/3d-main-window/resultinspection/</guid>
       <description>The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. The selected cells will be highlighted, text information displayed in the Result Info docking window, and the time-history values plotted in the Result Plot, if available.
-Visibility of the docking widows can be controlled from the Windows menu.
+Visibility of the docking widows can be controlled from the Windowsmenu.
 Result Info Clicking cells will display slightly different information text based on the case type as described in the following tables.</description>
     </item>
     
@@ -90,8 +90,7 @@ Visibility of the docking widows can be controlled from the Windows menu.
       
       <guid>https://resinsight.org/3d-main-window/filters/</guid>
       <description>Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:
- Range Filter &amp;ndash; Extracts an IJK subset of the model. Property Filter &amp;ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from  Simulation Wells .
-(Not applicable for Geomechanical cases)</description>
+ Range Filter &amp;ndash; Extracts an IJK subset of the model. Property Filter &amp;ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from Simulation Wells.(Not applicable for Geomechanical cases)Common Properties for Range and Property Filters Both filter types can be turned on or off using the toggle in the Project Tree and controlled from their corresponding Property Editor.</description>
     </item>
     
     <item>
@@ -101,7 +100,7 @@ Visibility of the docking widows can be controlled from the Windows menu.
       
       <guid>https://resinsight.org/3d-main-window/intersections/</guid>
       <description>Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.
-There are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line.</description>
+There are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate 2D Intersection View</description>
     </item>
     
     <item>
@@ -144,7 +143,7 @@ Grid Statistics Dialog Fields The dialog consist of three information parts.
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/3d-main-window/casegroupsandstatistics/</guid>
-      <description>Grid Case Group&amp;rsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).
+      <description>Grid Case Group&amp;lsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).
 If you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.</description>
     </item>
     
@@ -175,7 +174,7 @@ When ResInsight is in measurement mode, clicking on an surface in the 3D view wi
       
       <guid>https://resinsight.org/3d-main-window/annotations/</guid>
       <description>ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.
- Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file   Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree).</description>
+ Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file    Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree).</description>
     </item>
     
     <item>
diff --git a/3d-main-window/intersections/index.html b/3d-main-window/intersections/index.html
index c0570e617b..5a65e150c5 100644
--- a/3d-main-window/intersections/index.html
+++ b/3d-main-window/intersections/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Intersections :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,24 +1802,19 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#curve-based-intersections">Curve Based <strong>Intersections</strong></a>
-<ul>
-<li><a href="#common-curve-based-intersection-options">Common Curve Based Intersection Options</a>
-<ul>
-<li><a href="#direction">Direction</a></li>
-</ul></li>
-<li><a href="#well-path-intersection">Well Path Intersection</a></li>
-<li><a href="#simulation-well-intersection">Simulation Well Intersection</a></li>
-<li><a href="#polyline-intersection">Polyline Intersection</a></li>
-<li><a href="#azimuth-and-dip">Azimuth and Dip</a></li>
-<li><a href="#2d-intersection-views">2D Intersection Views</a></li>
-</ul></li>
-<li><a href="#intersection-box-and-intersection-planes">Intersection Box and Intersection Planes</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#curve-based-intersections">Curve Based <strong>Intersections</strong></a>
+      <ul>
+        <li><a href="#common-curve-based-intersection-options">Common Curve Based Intersection Options</a></li>
+        <li><a href="#well-path-intersection">Well Path Intersection</a></li>
+        <li><a href="#simulation-well-intersection">Simulation Well Intersection</a></li>
+        <li><a href="#polyline-intersection">Polyline Intersection</a></li>
+        <li><a href="#azimuth-and-dip">Azimuth and Dip</a></li>
+        <li><a href="#2d-intersection-views">2D Intersection Views</a></li>
+      </ul>
+    </li>
+    <li><a href="#intersection-box-and-intersection-planes">Intersection Box and Intersection Planes</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1810,44 +1839,26 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/IntersectionOverview.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionOverview.png" alt=""></p>
 <p>Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.</p>
-
 <p>There are two main types of intersections. The first one which simply is called <strong>Intersection</strong>, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate <a href="/3d-main-window/intersections/#2d-intersection-views">2D Intersection View</a></p>
-
 <p>The second intersection type is called an <strong>Intersection Box</strong>. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.</p>
-
 <p>All types of intersections are stored in a folder named <strong>Intersections</strong> in a <strong>View</strong> as shown below. Once created, the intersections may be copied to other views by selecting the <strong>Copy intersections to all views in case</strong> option from the right-click menu of each intersection.</p>
-
-<p><img src="/images/3d-main-window/IntersectionInTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionInTree.png" alt=""></p>
 <p>Once created, the intersections may be copied to other views by selecting the <strong>Copy intersections to all views in case</strong> option from the right-click menu of each intersection.</p>
-
-<p><img src="/images/3d-main-window/IntersectionInTreeCopy.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionInTreeCopy.png" alt=""></p>
 <h2 id="curve-based-intersections">Curve Based <strong>Intersections</strong></h2>
-
 <p>There are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane&rsquo;s extrusion direction can be defined by the two angles.</p>
-
 <p>Any of these intersections can be created by activating <img src="https://resinsight.org/images/3d-main-window/CrossSection16x16.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>New Intersection</strong> from the right-click menu of the <strong>Intersections</strong> item in the Project Tree.</p>
-
 <p>They can also be created from the right-click menu in the 3D view, as described below.</p>
 
-
-<div class="notices info" ><p>To be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the <b>Grids</b> item in the Project Tree or activating the <b>Hide Grid Cells</b> toolbar button.</p>
+<div class="notices info" ><p>To be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the <!-- raw HTML omitted -->Grids<!-- raw HTML omitted --> item in the Project Tree or activating the <!-- raw HTML omitted -->Hide Grid Cells<!-- raw HTML omitted --> toolbar button.</p>
 </div>
 
-
 <h3 id="common-curve-based-intersection-options">Common Curve Based Intersection Options</h3>
-
 <p>The property panel of a well path based intersection is shown below:</p>
-
-<p><img src="/images/3d-main-window/IntersectionWellPath.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionWellPath.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path.</li>
 <li><strong>Intersecting Geometry</strong> &ndash; These options controls the curve to be used for the cross section, and depends on the type of intersection you choose.</li>
@@ -1855,143 +1866,102 @@ if (!doNotTrack) {
 <li><strong>Extent Length</strong> &ndash; Defines how far an intersection for well path or simulation Well is extended at intersection ends.</li>
 <li><strong>Show Inactive Cells</strong> &ndash; Controls if inactive cells are included when creating the intersection geometry.</li>
 </ul>
-
 <h4 id="direction">Direction</h4>
-
 <p>The direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.</p>
-
 <p>When selection the <strong>Horizontal</strong> option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.</p>
-
 <p>When <strong>Defined by two points</strong> is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.</p>
-
 <ul>
 <li>The background color of this list is set to light pink when adding points by picking in the 3D view is active.</li>
 <li>To finish adding points, click the button <strong>Stop picking points</strong> in the <strong>Property Editor</strong>.</li>
 <li>The background color of the point list is then set to white.</li>
 </ul>
-
 <h3 id="well-path-intersection">Well Path Intersection</h3>
-
 <p>A new <strong>Well Path</strong> intersection can be created by right-clicking the well path in the 3D view or in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/IntersectionWellPath.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionWellPath.png" alt=""></p>
 <p>When a well path intersection is created, the source well path can be changed by using the <strong>Well Path</strong> selection combo box in the <strong>Property Editor</strong>.</p>
-
 <h3 id="simulation-well-intersection">Simulation Well Intersection</h3>
-
 <p>A new <strong>Simulation Well</strong> intersection can be created by right-clicking the simulation well in the 3D view or in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/IntersectionSimulationWellProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionSimulationWellProperties.png" alt=""></p>
 <p>When a simulation well intersection is created, the source simulation well can be changed by using the <strong>Simulation Well</strong> selection combo box in the <strong>Property Editor</strong>.</p>
-
 <p>If the well contains more than one branch, the intersection geometry will be created for the selected branch in the <strong>Branch</strong> combo box.</p>
-
 <h3 id="polyline-intersection">Polyline Intersection</h3>
-
 <p>A new <strong>Polyline</strong> intersection can be created from the right-click menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/3d-main-window/IntersectionPolyline.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionPolyline.png" alt=""></p>
 <ul>
 <li>The background color of this list is set to light pink when adding points by picking in the 3D view is active.</li>
 <li>To finish adding points, click the button <strong>Stop picking points</strong> in the <strong>Property Editor</strong>.</li>
 <li>The background color of the point list is then set to white.</li>
 </ul>
-
 <p>The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button <strong>Start picking points</strong> again.</p>
-
 <p>The points in the list can be copied to clipboard using <strong>CTRL-C</strong> when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using <strong>CTRL-V</strong>.</p>
-
 <h3 id="azimuth-and-dip">Azimuth and Dip</h3>
-
 <p>A new <strong>Azimuth and Dip</strong> intersection can be created from the right-click menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/3d-main-window/IntersectionAzimuthDip.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionAzimuthDip.png" alt=""></p>
 <ul>
 <li>The background color of this list is set to light pink when adding points by picking in the 3D view is active.</li>
 <li>To finish adding points, click the button <strong>Stop picking points</strong> in the <strong>Property Editor</strong>.</li>
 <li>The background color of the point list is then set to white.</li>
 </ul>
-
 <p>The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button <strong>Start picking points</strong> again.</p>
-
 <p>The points in the list can be copied to clipboard using <strong>CTRL-C</strong> when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using <strong>CTRL-V</strong>.</p>
-
 <p>When two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees <strong>Dip</strong>, and the <strong>Azimuth</strong> angle calculated from the two points. The two angles can be edited in the <strong>Property Editor</strong> of the intersection, and is defined by the following:</p>
-
 <ul>
 <li><strong>Dip</strong> is the angle between the horizontal plane and down.</li>
 <li><strong>Azimuth</strong> is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.</li>
 </ul>
-
 <p>The length of the plane can also be set manually in the <strong>Property Editor</strong>.</p>
-
 <ul>
 <li><strong>Length Up</strong> is the distance from the user defined horizontal line, to the top of the plane intersecting the model.</li>
 <li><strong>Length Down</strong> is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.</li>
 </ul>
-
-<p><img src="/images/3d-main-window/azimuthDip3DView.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/azimuthDip3DView.PNG" alt=""></p>
 <h3 id="2d-intersection-views">2D Intersection Views</h3>
-
 <p>A 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.</p>
-
-<p><img src="/images/3d-main-window/IntersectionView.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionView.png" alt=""></p>
 <p>Each of the curve based intersections have a corresponding <strong>2D Intersection View</strong>. Management of these views are automatic. They will be created and deleted along with the intersection.</p>
-
 <p>The view can be shown either by right clicking the intersection and select the command <strong>Show 2D intersection View</strong>, or by toggling the view in the project tree directly.</p>
-
-<p><img src="/images/3d-main-window/IntersectionViewsProjectTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/IntersectionViewsProjectTree.png" alt=""></p>
 <p>Scales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.</p>
-
 <p>The view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.</p>
-
-<p><img src="/images/3d-main-window/2DIntersectionViewProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/2DIntersectionViewProperties.png" alt=""></p>
 <ul>
 <li><strong>Viewer</strong>
-
 <ul>
 <li><strong>Name</strong> &ndash; User editable name of the view. The default name is set by combining the name of the origin view and the intersection name.</li>
 <li><strong>Background</strong> &ndash; Color of the viewer background</li>
 <li><strong>Disable Results Lighting</strong> &ndash; Toggle the light effect. When the lighting is turned off, the colors are easier to compare with the legend, but the colors carry no visual cue to visualize the 3D shape. The effect is tiny on 2D Intersection Views.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Grid Appearance</strong> &ndash; Controls the drawstyle of the grid geometry
-
 <ul>
 <li><strong>Z Scale</strong> &ndash; Scales the view in Z(depth) direction to make slim K-layers easier to see</li>
-<li><strong>Grid Lines</strong> &ndash; Controls what mesh lines to draw</li>
+<li><strong>Grid Lines</strong> &ndash; Controls what mesh lines to draw
+<ul>
 <li><strong>All</strong> &ndash; All mesh lines are drawn</li>
 <li><strong>Faults Only</strong> &ndash; Only mesh lines associated with faults are drawn</li>
 <li><strong>None</strong> &ndash; Mesh lines are not drawn at all</li>
-<li><strong>Grid Surface</strong> &ndash; Controls what grid surface geometry to draw</li>
+</ul>
+</li>
+<li><strong>Grid Surface</strong> &ndash; Controls what grid surface geometry to draw
+<ul>
 <li><strong>All</strong> &ndash; All grid faces are drawn</li>
 <li><strong>Faults Only</strong> &ndash; Only faces that are included in a fault is drawn</li>
 <li><strong>None</strong> &ndash; Do not draw any faces</li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li><strong>Defining Points</strong>
-
 <ul>
 <li><strong>Show points</strong> &ndash; Toggle the display of the defining points for Polyline or Azimuth and Dip intersections.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <p>These options are similar to the options for a regular 3D view (See <a href="/3d-main-window/3dviews/#view-properties">View Properties</a> )</p>
-
 <h2 id="intersection-box-and-intersection-planes">Intersection Box and Intersection Planes</h2>
-
 <p>A new <strong>Intersection Box</strong> or <strong>Intersection Plane</strong> can be created from the right-click menu in the 3D view or the right-click menu in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/3d_view_context_menu.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3d_view_context_menu.png" alt=""></p>
 <p>The following list describes the properties for an <strong>Intersection Box</strong>:</p>
-
 <ul>
 <li><strong>Name</strong> &ndash; Automatically created based on the item specifying the intersection</li>
 <li><strong>Box Type</strong> &ndash; Box or x-plane, y-plane or z-plane</li>
@@ -2002,10 +1972,8 @@ if (!doNotTrack) {
 <li><strong>XY Slider Step Size</strong> &ndash; Defines how much the value changes when the slider for XY values is changed, default value 1.0</li>
 <li><strong>Depth Slider Step Size</strong> &ndash; Defines how much the value changes when the slider for depth values is changed, default value 0.5</li>
 </ul>
-
 <p>Direct interaction in a 3D view is activated when <strong>Show 3D manipulator</strong> is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.</p>
-
-<p><img src="/images/3d-main-window/IntersectionBoxWithHandles.png" alt="" /></p>
+<p><img src="/images/3d-main-window/IntersectionBoxWithHandles.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2181,6 +2149,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2191,6 +2172,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3341,20 +3325,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/linkedviews/index.html b/3d-main-window/linkedviews/index.html
index e7e4eb69fe..74ec799ace 100644
--- a/3d-main-window/linkedviews/index.html
+++ b/3d-main-window/linkedviews/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Linked Views :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,17 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#establish-linked-views">Establish Linked Views</a></li>
-<li><a href="#linked-view-options">Linked View Options</a>
-<ul>
-<li>
-<ul>
-<li><a href="#link-options">Link Options</a></li>
-<li><a href="#link-cell-filters">Link Cell Filters</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#toggle-linking-from-the-project-tree">Toggle Linking from the <strong>Project Tree</strong></a></li>
-<li><a href="#project-tree-right-click-menu">Project Tree right-click menu</a></li>
-<li><a href="#3d-view-right-click-menu">3D View right-click menu</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#establish-linked-views">Establish Linked Views</a></li>
+    <li><a href="#linked-view-options">Linked View Options</a>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+    <li><a href="#toggle-linking-from-the-project-tree">Toggle Linking from the <strong>Project Tree</strong></a></li>
+    <li><a href="#project-tree-right-click-menu">Project Tree right-click menu</a></li>
+    <li><a href="#3d-view-right-click-menu">3D View right-click menu</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,31 +1837,18 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/LinkedViewsOverview.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/LinkedViewsOverview.png" alt=""></p>
 <p>One or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.</p>
-
 <h2 id="establish-linked-views">Establish Linked Views</h2>
-
 <p>To establish a link between views, select <img src="https://resinsight.org/images/3d-main-window/chain.png" style="display:inline; vertical-align:middle; margin:0">
 <strong>Link Visible Views</strong> from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the <strong>Linked Views</strong> items are displayed in the top of the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/LinkedViewsInProjectTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/LinkedViewsInProjectTree.png" alt=""></p>
 <p>It is also possible to link specific views by selecting them and choosing <strong>Link Selected Views</strong> from the right-click menu. The following image shows the linking of a regular view with a <strong>Contour Map</strong>. Note that contour maps can never be the Master View.</p>
-
-<p><img src="/images/3d-main-window/LinkedContourMap.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/LinkedContourMap.png" alt=""></p>
 <h2 id="linked-view-options">Linked View Options</h2>
-
 <p>When selecting a linked view in the project tree, the different options are available in the <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/3d-main-window/LinkedViewsProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/LinkedViewsProperties.png" alt=""></p>
 <h4 id="link-options">Link Options</h4>
-
 <ul>
 <li><strong>Camera</strong> &ndash; Navigation in any of the views where this option is active will be applied to the other linked views with this option set. This option is not available for Contour Maps.</li>
 <li><strong>Show Cursor</strong> &ndash; Shows the position of the mouse cursor in the other views as a cross-hair. This option is not available for Contour Maps.</li>
@@ -1841,40 +1856,29 @@ if (!doNotTrack) {
 <li><strong>Cell Color Result</strong> &ndash; Change of cell result in the master view will be applied to all dependent views where this option is active. <strong>Cell Color Result</strong> is only supported between views of the <em>same type</em>.</li>
 <li><strong>Legend Definition</strong> &ndash; Links the legend between views already linking the <strong>Cell Results Color</strong>.</li>
 </ul>
-
 <h4 id="link-cell-filters">Link Cell Filters</h4>
-
 <ul>
 <li><strong>Range Filters</strong> &ndash; Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case.</li>
 <li><strong>Property Filters</strong> &ndash; Property filters in master view will be applied to all dependent views where this option is active. This option is only enabled between views of the <em>same case</em>.</li>
 </ul>
-
 <h2 id="toggle-linking-from-the-project-tree">Toggle Linking from the <strong>Project Tree</strong></h2>
-
 <p>A linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item <strong>Linked Views</strong>.</p>
-
 <h2 id="project-tree-right-click-menu">Project Tree right-click menu</h2>
-
 <p>Right-clicking one of the linked view entries in the <strong>Project Tree</strong> displays the following menu entries:</p>
-
 <ul>
 <li><strong>Open All Linked Views</strong> &ndash; Open all the views which is part of the linked view group.</li>
 <li><strong>Delete All Linked Views</strong> &ndash; Delete the linked views group, and thereby unlink all the views.</li>
 <li><strong>Delete</strong> &ndash; Remove an individual view from the group of linked views.</li>
 </ul>
-
 <h2 id="3d-view-right-click-menu">3D View right-click menu</h2>
-
-<p>To activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model.
+<p>To activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model. 
 Depending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:</p>
-
 <ul>
 <li><strong>Show Link Options</strong> &ndash; Activate the linked view item in the project tree, and show its properties.</li>
 <li><strong>Set As Master View</strong> &ndash; Use the view as Master View. This option is not available for Contour Maps.</li>
 <li><strong>Link View</strong> &ndash; Add the view to list of linked views.</li>
 <li><strong>Unlink View</strong> &ndash; Delete the view from list of linked views.</li>
 </ul>
-
 <p>Master views have no available linking commands.</p>
 
 
@@ -2051,6 +2055,19 @@ Depending on whether the view is a dependent-, or an unlinked view, some of the
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2061,6 +2078,9 @@ Depending on whether the view is a dependent-, or an unlinked view, some of the
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3211,20 +3231,20 @@ Depending on whether the view is a dependent-, or an unlinked view, some of the
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/measurement/index.html b/3d-main-window/measurement/index.html
index 4a63fe36ba..f535ad67b1 100644
--- a/3d-main-window/measurement/index.html
+++ b/3d-main-window/measurement/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Measurement :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1791,29 +1825,20 @@ if (!doNotTrack) {
 
 
 
-<p><img src="/images/3d-main-window/Measurement.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Measurement.png" alt=""></p>
 <p>ResInsight supports measurements in the 3D views. To enter measurement mode, press the ruler toolbar button <img src="https://resinsight.org/images/3d-main-window/MeasurementButton.png" style="display:inline; vertical-align:middle; margin:0">
  or the keyboard shortcut <strong>Ctrl-M</strong>. This mode can also be activated from the right-click menu in a 3D view.</p>
-
-<p><img src="/images/3d-main-window/MeasurementToolbar.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/MeasurementToolbar.png" alt=""></p>
 <p>When ResInsight is in measurement mode, clicking on an surface in the 3D view will set the first measurement point. Clicking on a different surface will set the second measurement point, and display a label with measurements. Additional clicking will start a new measurement between two points.</p>
-
 <p>The measurement label contains the following:</p>
-
 <ul>
 <li><strong>Length</strong> - The length of the measurement segment</li>
 <li><strong>Horizontal Length</strong> - The length of the measurement segment projected onto the XY plane</li>
 </ul>
-
 <p>ResInsight also supports measuring a polyline (a set of line segments), which can be activated with the polyline ruler toolbar button <img src="https://resinsight.org/images/3d-main-window/PolylineMeasurementButton.png" style="display:inline; vertical-align:middle; margin:0">
  or <strong>Ctrl-Shift-M</strong>. The measurement label will now contain additional measurements.</p>
-
-<p><img src="/images/3d-main-window/PolylineMeasurement.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PolylineMeasurement.png" alt=""></p>
 <p>The measurement label contains several lengths.</p>
-
 <ul>
 <li><strong>Segment Length</strong> - The length of the last segment</li>
 <li><strong>Segment Horizontal Length</strong> - The length of the last segment projected onto the XY plane</li>
@@ -1821,7 +1846,6 @@ if (!doNotTrack) {
 <li><strong>Total Horizontal Length</strong> - The total length of the measurement polyline projected onto the XY plane</li>
 <li><strong>Horizontal area</strong> - The area of the polyline projected onto the XY plane</li>
 </ul>
-
 <p>To leave measurement modes, press the toolbar button, press the <strong>Esc</strong> button  or press the keyboard shortcut used to activate the mode again.</p>
 
 
@@ -1998,6 +2022,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2008,6 +2045,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3158,20 +3198,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/resultcolorlegend/index.html b/3d-main-window/resultcolorlegend/index.html
index 6045971a38..28e5bf6b47 100644
--- a/3d-main-window/resultcolorlegend/index.html
+++ b/3d-main-window/resultcolorlegend/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Result Color Legend :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1792,38 +1826,34 @@ if (!doNotTrack) {
 
 
 <p>The color mapping of the displayed cell result is controlled by the <strong>Color Legend</strong> located below a result node in the <strong>Project Tree</strong>. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.</p>
-
-<p><img src="/images/3d-main-window/legend_configuration.PNG" alt="Legend Configuration" /></p>
-
+<p><img src="/images/3d-main-window/legend_configuration.PNG" alt="Legend Configuration"></p>
 <ul>
 <li><strong>Number of levels</strong> &ndash; Defines the number of tick marks displayed next to the color legend</li>
 <li><strong>Significant digits</strong> &ndash; Defines the number of significant digits in the number formatting</li>
 <li><strong>Number format</strong> &ndash; Defines how the numbers are formatted</li>
 <li><strong>Colors</strong> &ndash; Defines the color palette</li>
 <li><strong>Mapping</strong> &ndash; This option defines how the values are mapped onto the color distribution
-
 <ul>
 <li><strong>Discrete Linear</strong> &ndash; Legend divided into linear levels defined by <strong>Number of levels</strong></li>
 <li><strong>Continuous Linear</strong> &ndash; Continuous linear legend with tick mark count defined by <strong>Number of levels</strong></li>
 <li><strong>Continuous Logarithmic</strong> &ndash; Continuous logarithmic legend with tick mark count defined by <strong>Number of levels</strong></li>
 <li><strong>Discrete Logarithmic</strong> &ndash; Logarithmic legend divided into levels defined by <strong>Number of levels</strong></li>
-<li><strong>Category</strong> &ndash; Special legend with one level for each category, either integer values or formation names.<br />
+<li><strong>Category</strong> &ndash; Special legend with one level for each category, either integer values or formation names.<br>
 Only available for result names ending with <em><code>NUM</code></em> or formation names.</li>
-</ul></li>
-<li><strong>Range type</strong>
-
-<ul>
-<li><strong>All Timesteps</strong> &ndash; values for all time steps are used to find min and max value of
-the result values represented by the color legend.<br />
-(Not available for Flow Diagnostics results)</li>
-<li><strong>Current Timestep</strong> &ndash; use current (one) time step to find min and max values<br /></li>
-<li><strong>User Defined Range</strong> &ndash; user specifies numeric values for min and max<br /></li>
-</ul></li>
 </ul>
-
+</li>
+<li><strong>Range type</strong>
+<ul>
+<li><strong>All Timesteps</strong> &ndash; values for all time steps are used to find min and max value of 
+the result values represented by the color legend.<br>
+(Not available for Flow Diagnostics results)</li>
+<li><strong>Current Timestep</strong> &ndash; use current (one) time step to find min and max values</li>
+<li><strong>User Defined Range</strong> &ndash; user specifies numeric values for min and max</li>
+</ul>
+</li>
+</ul>
 <p>Furthermore the legend can have a semi-transparent background applied to it by selecting the *<em>Show Box around Legends</em> option in the Preferences dialog.</p>
-
-<p><img src="/images/3d-main-window/legend_background.png" alt="Legend Background" /> <img src="/images/3d-main-window/legend_with_background.png" alt="Show Box around legends" /></p>
+<p><img src="/images/3d-main-window/legend_background.png" alt="Legend Background"> <img src="/images/3d-main-window/legend_with_background.png" alt="Show Box around legends"></p>
 
 
 <footer class=" footline" >
@@ -1999,6 +2029,19 @@ the result values represented by the color legend.<br />
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2009,6 +2052,9 @@ the result values represented by the color legend.<br />
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3159,20 +3205,20 @@ the result values represented by the color legend.<br />
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/resultinspection/index.html b/3d-main-window/resultinspection/index.html
index 007a9cfa18..55c5320c99 100644
--- a/3d-main-window/resultinspection/index.html
+++ b/3d-main-window/resultinspection/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Result Inspection :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,22 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#result-info">Result Info</a>
-<ul>
-<li><a href="#eclipse-model">Eclipse Model</a></li>
-<li><a href="#geomechanical-model">Geomechanical Model</a></li>
-</ul></li>
-<li><a href="#result-plot">Result Plot</a>
-<ul>
-<li><a href="#adding-the-curves-to-a-summary-plot">Adding the Curves to a Summary Plot</a></li>
-</ul></li>
-<li><a href="#pvt-plot-eclipse-cases-only">PVT Plot (Eclipse Cases Only)</a></li>
-<li><a href="#relative-permeability-plot-eclipse-cases-only">Relative Permeability Plot (Eclipse Cases Only)</a></li>
-<li><a href="#mohr-s-circle-plot-geo-mechanical-models-only">Mohr&rsquo;s Circle Plot (Geo Mechanical Models Only)</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#result-info">Result Info</a>
+      <ul>
+        <li><a href="#eclipse-model">Eclipse Model</a></li>
+        <li><a href="#geomechanical-model">Geomechanical Model</a></li>
+      </ul>
+    </li>
+    <li><a href="#result-plot">Result Plot</a>
+      <ul>
+        <li><a href="#adding-the-curves-to-a-summary-plot">Adding the Curves to a Summary Plot</a></li>
+      </ul>
+    </li>
+    <li><a href="#pvt-plot-eclipse-cases-only">PVT Plot (Eclipse Cases Only)</a></li>
+    <li><a href="#relative-permeability-plot-eclipse-cases-only">Relative Permeability Plot (Eclipse Cases Only)</a></li>
+    <li><a href="#mohrs-circle-plot-geo-mechanical-models-only">Mohr&rsquo;s Circle Plot (Geo Mechanical Models Only)</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,24 +1842,16 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/ResultInspectionOverview.png" alt="" /></p>
-
-<p>The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view.
+<p><img src="/images/3d-main-window/ResultInspectionOverview.png" alt=""></p>
+<p>The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. 
 The selected cells will be highlighted, text information displayed in the <strong>Result Info</strong> docking window, and the time-history values plotted in the <strong>Result Plot</strong>, if available.</p>
 
-
-<div class="notices note" ><p>Visibility of the docking widows can be controlled from the <b>Windows</b> menu.</p>
+<div class="notices note" ><p>Visibility of the docking widows can be controlled from the <!-- raw HTML omitted -->Windows<!-- raw HTML omitted --> menu.</p>
 </div>
 
-
 <h2 id="result-info">Result Info</h2>
-
 <p>Clicking cells will display slightly different information text based on the case type as described in the following tables.</p>
-
 <h3 id="eclipse-model">Eclipse Model</h3>
-
 <table>
 <thead>
 <tr>
@@ -1834,32 +1859,26 @@ The selected cells will be highlighted, text information displayed in the <stron
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Reservoir cell</td>
 <td>Displays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section <strong>&ndash; Grid cell result details &ndash;</strong></td>
 </tr>
-
 <tr>
 <td>Fault face</td>
 <td>Displays the same info as for a <em>Reservoir cell</em>. In addition the section <strong>&ndash; Fault result details &ndash;</strong> containing Fault Name and Fault Face information.</td>
 </tr>
-
 <tr>
 <td>Fault face with NNC</td>
 <td>Displays the same info as <em>Fault face</em>, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section <strong>&ndash; NNC details &ndash;</strong> is geometry information of the two cells connected by the NNC.</td>
 </tr>
-
 <tr>
 <td>Formation names</td>
 <td>Displays name of formation the cell is part of</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="geomechanical-model">Geomechanical Model</h3>
-
 <table>
 <thead>
 <tr>
@@ -1867,73 +1886,48 @@ The selected cells will be highlighted, text information displayed in the <stron
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Closest result</td>
 <td>Closest node ID and result value</td>
 </tr>
-
 <tr>
 <td>Element</td>
 <td>Element ID and IJK coordinate for the element</td>
 </tr>
-
 <tr>
 <td>Intersection point</td>
 <td>Location of left-click intersection of the geometry</td>
 </tr>
-
 <tr>
 <td>Element result details</td>
 <td>Lists all integration point IDs and results with associated node IDs and node coordinates</td>
 </tr>
-
 <tr>
 <td>Formation names</td>
 <td>Displays name of formation the cell is part of</td>
 </tr>
 </tbody>
 </table>
-
 <h2 id="result-plot">Result Plot</h2>
-
 <p>If a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window <strong>Result Plot</strong> as one curve for each cell.</p>
-
 <p>Additional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.</p>
-
 <p>To clear the cell-selection, left-click outside the visible geometry.</p>
-
 <h3 id="adding-the-curves-to-a-summary-plot">Adding the Curves to a Summary Plot</h3>
-
 <p>The time history curves of the selected cells can be added to a Summary Plot by right-clicking in the <strong>Result Plot</strong> or in the 3D View.</p>
-
-<p><img src="/images/3d-main-window/ResultPlotToSummaryPlotCommand.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ResultPlotToSummaryPlotCommand.png" alt=""></p>
 <p>A dialog will appear to prompt you to select an existion plot, or to create a new one.</p>
-
-<p><img src="/images/3d-main-window/ResultPlotToSummaryPlotDialog.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ResultPlotToSummaryPlotDialog.png" alt=""></p>
 <h2 id="pvt-plot-eclipse-cases-only">PVT Plot (Eclipse Cases Only)</h2>
-
 <p>Show the PVT Plot window by selecting <strong>Windows -&gt; PVT Plot</strong>. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.</p>
-
-<p><img src="/images/3d-main-window/pvtOil.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/pvtGas.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/pvtOil.png" alt=""></p>
+<p><img src="/images/3d-main-window/pvtGas.png" alt=""></p>
 <p>The PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots <em>Phase Formation Volume Factor</em> and the other plots <em>Phase Viscosity</em>, both against pressure. The <em>Phase</em> can be either oil or gas, and can be selected in the top left corner of the window.</p>
-
 <p>Pressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.</p>
-
 <h2 id="relative-permeability-plot-eclipse-cases-only">Relative Permeability Plot (Eclipse Cases Only)</h2>
-
 <p>Show the Relative Permeability Plot window by selecting <strong>Windows -&gt; Relative Permeability Plot</strong>.  When it is turned on, it will only be visible when the active view is a view of an Eclipse case.</p>
-
-<p><img src="/images/3d-main-window/RelativePermeability.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/RelativePermeability.png" alt=""></p>
 <p>The Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:</p>
-
 <table>
 <thead>
 <tr>
@@ -1942,38 +1936,32 @@ The selected cells will be highlighted, text information displayed in the <stron
 <th>Axis</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>KRW</td>
 <td>Relative permeability water</td>
 <td>KR (Left)</td>
 </tr>
-
 <tr>
 <td>KRG</td>
 <td>Relative permeability gas</td>
 <td>KR (Left)</td>
 </tr>
-
 <tr>
 <td>KROW</td>
 <td>Relative permeability oil water</td>
 <td>KR (Left)</td>
 </tr>
-
 <tr>
 <td>KROG</td>
 <td>Relative permeability oil gas</td>
 <td>KR (Left)</td>
 </tr>
-
 <tr>
 <td>PCOW</td>
 <td>Capilar pressure oil water</td>
 <td>PC (Right)</td>
 </tr>
-
 <tr>
 <td>PCOG</td>
 <td>Capilar pressure oil gas</td>
@@ -1981,9 +1969,7 @@ The selected cells will be highlighted, text information displayed in the <stron
 </tr>
 </tbody>
 </table>
-
 <p>Saturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.</p>
-
 <table>
 <thead>
 <tr>
@@ -1991,36 +1977,28 @@ The selected cells will be highlighted, text information displayed in the <stron
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Log Scale Kr Axis</td>
 <td>Enable logarithmic Kr-axis</td>
 </tr>
-
 <tr>
 <td>Show Unscaled</td>
 <td>Display curves unscaled</td>
 </tr>
-
 <tr>
 <td>Fixed [0, 1] X-axis</td>
 <td>Use a fixed range on X-axis</td>
 </tr>
-
 <tr>
 <td>Fixed [0, 1] Kr-axis</td>
 <td>Use a fixed range on Kr-axis</td>
 </tr>
 </tbody>
 </table>
-
-<h2 id="mohr-s-circle-plot-geo-mechanical-models-only">Mohr&rsquo;s Circle Plot (Geo Mechanical Models Only)</h2>
-
+<h2 id="mohrs-circle-plot-geo-mechanical-models-only">Mohr&rsquo;s Circle Plot (Geo Mechanical Models Only)</h2>
 <p>Show the Mohr&rsquo;s Circle Plot window by selecting <strong>Windows -&gt; Mohr&rsquo;s Circle Plot</strong>.  When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.</p>
-
-<p><img src="/images/3d-main-window/mohrsCircles.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/mohrsCircles.png" alt=""></p>
 <p>The Mohr&rsquo;s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the <em>cohesion</em> and <em>friction angle</em> given in the geo mechanical view&rsquo;s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).</p>
 
 
@@ -2197,6 +2175,19 @@ The selected cells will be highlighted, text information displayed in the <stron
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2207,6 +2198,9 @@ The selected cells will be highlighted, text information displayed in the <stron
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3357,20 +3351,20 @@ The selected cells will be highlighted, text information displayed in the <stron
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/tensors/index.html b/3d-main-window/tensors/index.html
index 95ea3dad06..f1c3d9c709 100644
--- a/3d-main-window/tensors/index.html
+++ b/3d-main-window/tensors/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Tensor Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,19 +1802,17 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#visualization">Visualization</a></li>
-<li><a href="#properties">Properties</a>
-<ul>
-<li><a href="#value">Value</a></li>
-<li><a href="#visibility">Visibility</a></li>
-<li><a href="#vector-colors">Vector Colors</a></li>
-<li><a href="#vector-size">Vector Size</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#visualization">Visualization</a></li>
+    <li><a href="#properties">Properties</a>
+      <ul>
+        <li><a href="#value">Value</a></li>
+        <li><a href="#visibility">Visibility</a></li>
+        <li><a href="#vector-colors">Vector Colors</a></li>
+        <li><a href="#vector-size">Vector Size</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1805,45 +1837,25 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/tensorArrows.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/tensorArrows.png" alt=""></p>
 <p>Tensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.</p>
-
 <p>The tensor results editor is found in a geo mechanical model&rsquo;s <strong>View</strong> in the project tree as seen below.</p>
-
-<p><img src="/images/3d-main-window/tensorProjectTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/tensorProjectTree.png" alt=""></p>
 <h2 id="visualization">Visualization</h2>
-
-<p><img src="/images/3d-main-window/tensorPressureTension.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/tensorPressureTension.png" alt=""></p>
 <p>The tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal.
 In the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.</p>
-
 <h2 id="properties">Properties</h2>
-
-<p><img src="/images/3d-main-window/tensorPropEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/tensorPropEditor.png" alt=""></p>
 <h3 id="value">Value</h3>
-
 <p>Tensor Results of an element can be calculated from one of the three result values <em>SE, ST</em> and <em>E</em>.</p>
-
 <h3 id="visibility">Visibility</h3>
-
 <p>Choose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.</p>
-
 <h3 id="vector-colors">Vector Colors</h3>
-
 <p>Choose which color palette to use for the three arrows. The colors appear in &ldquo;correct&rdquo; order (first color = principal 1).</p>
-
 <p>The vector color <strong>Result Colors</strong> is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.</p>
-
-<p><img src="/images/3d-main-window/tensorsResultColor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/tensorsResultColor.png" alt=""></p>
 <h3 id="vector-size">Vector Size</h3>
-
 <p>Scale method <strong>Result</strong> scales the arrows relative to the maximum result value of all components in the model. With scale method <strong>Constant</strong>, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the <strong>Size Scale</strong>.</p>
 
 
@@ -2020,6 +2032,19 @@ In the example above, the orange and blue arrows represent pressures and the whi
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2030,6 +2055,9 @@ In the example above, the orange and blue arrows represent pressures and the whi
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3180,20 +3208,20 @@ In the example above, the orange and blue arrows represent pressures and the whi
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/404.html b/404.html
index 05b7b34189..aa7b39ef17 100644
--- a/404.html
+++ b/404.html
@@ -9,13 +9,13 @@
   <title>404 Page not found</title>
 
    
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 <style>
     :root #header + #content > #left > #rlblock_left {
diff --git a/_footer/index.html b/_footer/index.html
index f45f75923f..ea153dd696 100644
--- a/_footer/index.html
+++ b/_footer/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1762,17 +1796,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#about-hahahugoshortcode-s0-hbhb"><a href="HAHAHUGOSHORTCODE-s0-HBHB">About</a></a></li>
-<li><a href="#ceetron-solutions-http-www-ceetronsolutions-com-in-collaboration-with-equinor-asa-https-www-equinor-com"><a href="http://www.ceetronsolutions.com">Ceetron Solutions</a> in collaboration with <a href="https://www.equinor.com/">Equinor ASA</a></a></li>
-<li><a href="#support-hahahugoshortcode-s1-hbhb"><a href="HAHAHUGOSHORTCODE-s1-HBHB">Support</a></a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#abouthahahugoshortcode-s0-hbhb"><a href="HAHAHUGOSHORTCODE-s0-HBHB">About</a></a></li>
+        <li><a href="#ceetron-solutionshttpwwwceetronsolutionscom-in-collaboration-with-equinor-asahttpswwwequinorcom"><a href="http://www.ceetronsolutions.com">Ceetron Solutions</a> in collaboration with <a href="https://www.equinor.com/">Equinor ASA</a></a></li>
+        <li><a href="#supporthahahugoshortcode-s1-hbhb"><a href="HAHAHUGOSHORTCODE-s1-HBHB">Support</a></a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1797,13 +1829,9 @@ if (!doNotTrack) {
 
 
 
-
-
-<h3 id="about-hahahugoshortcode-s0-hbhb"><a href="/about/">About</a></h3>
-
-<h3 id="ceetron-solutions-http-www-ceetronsolutions-com-in-collaboration-with-equinor-asa-https-www-equinor-com"><a href="http://www.ceetronsolutions.com">Ceetron Solutions</a> in collaboration with <a href="https://www.equinor.com/">Equinor ASA</a></h3>
-
-<h3 id="support-hahahugoshortcode-s1-hbhb"><a href="/support/">Support</a></h3>
+<h3 id="abouthahahugoshortcode-s0-hbhb"><a href="/about/">About</a></h3>
+<h3 id="ceetron-solutionshttpwwwceetronsolutionscom-in-collaboration-with-equinor-asahttpswwwequinorcom"><a href="http://www.ceetronsolutions.com">Ceetron Solutions</a> in collaboration with <a href="https://www.equinor.com/">Equinor ASA</a></h3>
+<h3 id="supporthahahugoshortcode-s1-hbhb"><a href="/support/">Support</a></h3>
 
 
 <footer class=" footline" >
@@ -1979,6 +2007,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1989,6 +2030,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3129,20 +3173,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/_header/index.html b/_header/index.html
index a7bb7e6a03..d375f444b2 100644
--- a/_header/index.html
+++ b/_header/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1785,7 +1819,7 @@ if (!doNotTrack) {
 
 
 
-<p><a href="/"><img src="/images/ResInsightCroppedIconPicture.png" alt="logo" /></a></p>
+<p><!-- raw HTML omitted --><img src="/images/ResInsightCroppedIconPicture.png" alt="logo"><!-- raw HTML omitted --></p>
 
 
 <footer class=" footline" >
@@ -1961,6 +1995,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1971,6 +2018,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3111,20 +3161,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/about/index.html b/about/index.html
index b868dfc517..1be2d449c6 100644
--- a/about/index.html
+++ b/about/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>About :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1762,22 +1796,20 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#efficient-user-interface">Efficient User Interface</a></li>
-<li><a href="#data-support">Data Support</a></li>
-<li><a href="#updating-and-refining-eclipse-simulation-models">Updating and Refining Eclipse simulation models</a></li>
-<li><a href="#flow-diagnostics">Flow Diagnostics</a></li>
-<li><a href="#octave-integration">Octave Integration</a></li>
-<li><a href="#project-organization">Project organization</a></li>
-<li><a href="#licensing">Licensing</a></li>
-<li><a href="#web-site-programming-and-design">Web site programming and design</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#efficient-user-interface">Efficient User Interface</a></li>
+        <li><a href="#data-support">Data Support</a></li>
+        <li><a href="#updating-and-refining-eclipse-simulation-models">Updating and Refining Eclipse simulation models</a></li>
+        <li><a href="#flow-diagnostics">Flow Diagnostics</a></li>
+        <li><a href="#octave-integration">Octave Integration</a></li>
+        <li><a href="#project-organization">Project organization</a></li>
+        <li><a href="#licensing">Licensing</a></li>
+        <li><a href="#web-site-programming-and-design">Web site programming and design</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1802,59 +1834,37 @@ if (!doNotTrack) {
 
 
 
-
-
-<p>ResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations.
+<p>ResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations. 
 It can also be configured to visualize geomechanical simulations from ABAQUS.</p>
-
 <p>The system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.</p>
-
 <h3 id="efficient-user-interface">Efficient User Interface</h3>
-
 <p>The user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.</p>
-
 <h3 id="data-support">Data Support</h3>
-
 <p>The main input data is
-<em><code>*.GRID</code></em> and <em><code>*.EGRID</code></em> files along with their <em><code>*.INIT</code></em> and restart files <em><code>*.XNNN</code></em> and <em><code>*.UNRST</code></em>.
+<em><code>*.GRID</code></em> and <em><code>*.EGRID</code></em> files along with their <em><code>*.INIT</code></em> and restart files <em><code>*.XNNN</code></em> and <em><code>*.UNRST</code></em>. 
 Summary vectors can be imported from <em><code>*.SMSPEC</code></em> files.
-ResInsight also supports selected parts of Eclipse input files and can read grid
-information and corresponding cell property data sets from <em><code>*.GRDECL</code></em> files.
+ResInsight also supports selected parts of Eclipse input files and can read grid 
+information and corresponding cell property data sets from <em><code>*.GRDECL</code></em> files. 
 Well log data can be imported from <em><code>*.LAS</code></em> files.</p>
-
 <p>ResInsight can also be built with support for Geomechanical models from ABAQUS in the <em><code>*.odb</code></em> file format.</p>
-
 <h3 id="updating-and-refining-eclipse-simulation-models">Updating and Refining Eclipse simulation models</h3>
-
 <p>ResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:</p>
-
 <ul>
 <li>Adding <strong>Well Path Completions</strong> such as fractures, fishbones and perforations to well paths, including transmissibility calculations to allow for simulation in Eclipse.</li>
 <li>Easily and visually generate setup files for <strong>Local Grid Refinement</strong> (LGR)</li>
 <li>The generation of Eclipse <strong>Multi Segment Well</strong>-models for well path completions.</li>
 </ul>
-
 <h3 id="flow-diagnostics">Flow Diagnostics</h3>
-
-<p>Flow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called <a href="https://github.com/OPM/opm-flowdiagnostics">opm-flowdiagnostics</a> developed by <a href="http://www.sintef.no/digital">SINTEF Digital</a>. <a href="/3d-main-window/cellresults/#flow-diagnostic-results">More&hellip;</a></p>
-
+<p>Flow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called <a href="https://github.com/OPM/opm-flowdiagnostics">opm-flowdiagnostics</a> developed by <a href="http://www.sintef.no/digital">SINTEF Digital</a>. <a href="/3d-main-window/cellresults/">More&hellip;</a></p>
 <h3 id="octave-integration">Octave Integration</h3>
-
 <p>Integration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.</p>
-
 <h3 id="project-organization">Project organization</h3>
-
-<p>ResInsight is developed by <a href="https://www.ceetronsolutions.com/">Ceetron Solutions</a> in collaboration with with <a href="https://www.equinor.com/">Equinor</a>.</p>
-
+<p>ResInsight is developed by <a href="https://www.ceetronsolutions.com/">Ceetron Solutions</a> in collaboration with with [Equinor] (<a href="https://www.equinor.com/)">https://www.equinor.com/)</a>.</p>
 <p>ResInsight is a part of the <a href="http://opm-project.org/">Open Porous Media Initiative</a>.
 The software is hosted at <a href="https://github.com/OPM/ResInsight">GitHub</a>, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.</p>
-
 <h3 id="licensing">Licensing</h3>
-
 <p>The software is licensed under GPL 3+, see <a href="https://github.com/OPM/ResInsight/blob/master/COPYING">Licensing details</a>.</p>
-
 <h3 id="web-site-programming-and-design">Web site programming and design</h3>
-
 <p>Web site is built with <a href="https://getgrav.org">Grav</a> and <a href="https://gohugo.io">Hugo</a></p>
 
 
@@ -2031,6 +2041,19 @@ The software is hosted at <a href="https://github.com/OPM/ResInsight">GitHub</a>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2041,6 +2064,9 @@ The software is hosted at <a href="https://github.com/OPM/ResInsight">GitHub</a>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3181,20 +3207,20 @@ The software is hosted at <a href="https://github.com/OPM/ResInsight">GitHub</a>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/categories/index.html b/categories/index.html
index 80e0f43d65..c1005c274f 100644
--- a/categories/index.html
+++ b/categories/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Categories :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1746,7 +1780,13 @@ if (!doNotTrack) {
                     
           
           
-            Categories
+            
+            
+          
+          
+            <a href='/'>ResInsight</a> > Categories
+          
+         
           
         
                  
@@ -1959,6 +1999,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1969,6 +2022,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3109,20 +3165,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/categories/index.xml b/categories/index.xml
index bfaf086887..2a63b1acd3 100644
--- a/categories/index.xml
+++ b/categories/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Categories on ResInsight</title>
diff --git a/export/completionexport/index.html b/export/completionexport/index.html
index e7a5ab1fca..f90013dc47 100644
--- a/export/completionexport/index.html
+++ b/export/completionexport/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,40 +1802,23 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#transmissibility-calculations">Transmissibility Calculations</a></li>
-<li><a href="#fracture-export">Fracture Export</a>
-<ul>
-<li><a href="#pressure-differential-depletion-scaling">Pressure Differential Depletion Scaling</a></li>
-<li><a href="#fracture-report-header">Fracture Report Header</a>
-<ul>
-<li><a href="#description-of-derived-data">Description of Derived Data</a></li>
-</ul></li>
-<li><a href="#differential-depletion-fracture-output">Differential Depletion Fracture Output</a></li>
-</ul></li>
-<li><a href="#export-of-fishbone-completion-data">Export of Fishbone Completion Data</a></li>
-<li><a href="#completions-for-lgr-welspecl-and-compdatl">Completions for LGR (WELSPECL and COMPDATL)</a></li>
-<li><a href="#lgr-for-completions-temporary-lgrs">LGR for completions (Temporary LGRs)</a></li>
-</ul></li>
-<li><a href="#multi-segment-well-model">Multi Segment Well Model</a>
-<ul>
-<li><a href="#exported-msw-data">Exported MSW Data</a>
-<ul>
-<li>
-<ul>
-<li><a href="#welsegs">WELSEGS</a></li>
-<li><a href="#compsegs">COMPSEGS</a></li>
-<li><a href="#wsegvalv">WSEGVALV</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#export-of-fractures-and-perforations-as-multi-segment-wells">Export of Fractures and Perforations as Multi-Segment Wells</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#transmissibility-calculations">Transmissibility Calculations</a></li>
+        <li><a href="#fracture-export">Fracture Export</a></li>
+        <li><a href="#export-of-fishbone-completion-data">Export of Fishbone Completion Data</a></li>
+        <li><a href="#completions-for-lgr-welspecl-and-compdatl">Completions for LGR (WELSPECL and COMPDATL)</a></li>
+        <li><a href="#lgr-for-completions-temporary-lgrs">LGR for completions (Temporary LGRs)</a></li>
+      </ul>
+    </li>
+    <li><a href="#multi-segment-well-model">Multi Segment Well Model</a>
+      <ul>
+        <li><a href="#exported-msw-data">Exported MSW Data</a></li>
+        <li><a href="#export-of-fractures-and-perforations-as-multi-segment-wells">Export of Fractures and Perforations as Multi-Segment Wells</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1826,100 +1843,85 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>The completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands <strong>Export Completion Data For Visible Wells</strong>, <strong>Export Completion Data For Visible Simulation Wells</strong> and <strong>Export Completion Data For Selected Wells</strong> can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the <strong>Project Tree</strong>. The first command is available from the <strong>File-&gt;Import</strong> menu as well.</p>
-
-<p><img src="/images/export/Completions_ExportCompletionData.png" alt="" /></p>
-
+<p><img src="/images/export/Completions_ExportCompletionData.png" alt=""></p>
 <ul>
 <li><strong>Export Settings</strong>
-
 <ul>
 <li><strong>Calculated Transmissibilities</strong> &ndash; The transmissibilities calculated based on the case and completion data are exported directly</li>
 <li><strong>Default Connection Factors and WPIMULT</strong> &ndash; The information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT/COMPDATL keywords. In addition, the same transmissibility calculation is performed by ResInsight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword.</li>
-<li><strong>Case to Apply</strong> &ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case.<br /></li>
+<li><strong>Case to Apply</strong> &ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case.</li>
 <li><strong>Use NTG Horizontally</strong> &ndash; Toggles whether NTG in I and J directions is included in the calculation</li>
 <li><strong>Include Multi Segment Well Model</strong> &ndash; Toggles whether to also export the completions as Multi Segment Wells.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>File Settings</strong>
-
 <ul>
-<li><strong>File Split</strong> &ndash; Controls how ResInsight splits the export in different files</li>
+<li><strong>File Split</strong> &ndash; Controls how ResInsight splits the export in different files
+<ul>
 <li><strong>Unified File</strong> &ndash; One file with all the completions.</li>
 <li><strong>Split on Well</strong> &ndash; One file for each well</li>
 <li><strong>Split on Well and Completion Type</strong> &ndash; One file for each well and completion type (Perforation Interval, Fishbone, &hellip;)</li>
-<li><strong>Export Completion Types</strong> &ndash; Control how several completions of different type in the same cell are handled</li>
-<li><strong>Individually</strong> &ndash; Completions of each type are exported to separate sections in the file and not combined in any way.<br /></li>
-<li><strong>Combined</strong> &ndash; Connection factors from different completion types are added together producing one number for each cell.</li>
-<li><strong>Export Folder</strong> &ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.</li>
-</ul></li>
-<li><strong>Completions Export Selection</strong>
-
-<ul>
-<li><strong>Perforations</strong> &ndash; Option to include or exclude perforation intervals in the export.</li>
-<li><strong>Time step</strong> &ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.</li>
-<li><strong>Fractures</strong> &ndash; Option to include or exclude fracture completions from the export.</li>
-<li><strong>Pressure Differential Depletion Scaling</strong> &ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion.</li>
-<li><strong>Fishbones</strong> &ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to.</li>
-<li><strong>Exclude Main Bore Transmissibility</strong> &ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.</li>
-</ul></li>
 </ul>
-
+</li>
+<li><strong>Export Completion Types</strong> &ndash; Control how several completions of different type in the same cell are handled
+<ul>
+<li><strong>Individually</strong> &ndash; Completions of each type are exported to separate sections in the file and not combined in any way.</li>
+<li><strong>Combined</strong> &ndash; Connection factors from different completion types are added together producing one number for each cell.</li>
+</ul>
+</li>
+<li><strong>Export Folder</strong> &ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.</li>
+</ul>
+</li>
+<li><strong>Completions Export Selection</strong>
+<ul>
+<li><strong>Perforations</strong> &ndash; Option to include or exclude perforation intervals in the export.
+<ul>
+<li><strong>Time step</strong> &ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.</li>
+</ul>
+</li>
+<li><strong>Fractures</strong> &ndash; Option to include or exclude fracture completions from the export.
+<ul>
+<li><strong>Pressure Differential Depletion Scaling</strong> &ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion.</li>
+</ul>
+</li>
+<li><strong>Fishbones</strong> &ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to.
+<ul>
+<li><strong>Exclude Main Bore Transmissibility</strong> &ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.</li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
 <h3 id="transmissibility-calculations">Transmissibility Calculations</h3>
-
 <p>The transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.</p>
-
-<p>Taking the X direction as an example, we first calculate the relevant permeability <em>K</em> from the Eclipse properties <em>PERMY</em> (K<sub>y</sub>) and PERMZ (K<sub>z</sub>):</p>
-
-<p><img src="/images/export/Equation_PerfInterval_K.png" alt="" /></p>
-
-<p>The Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (D<sub>y</sub> and D<sub>z</sub>):</p>
-
-<p><img src="/images/export/Equation_PerfInterval_Peaceman.png" alt="" /></p>
-
-<p>The x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (l<sub>x</sub>), the well radius (r<sub>w</sub>) and skin factor (S):</p>
-
-<p><img src="/images/export/Equation_PerfInterval_Trans.png" alt="" /></p>
-
+<p>Taking the X direction as an example, we first calculate the relevant permeability <em>K</em> from the Eclipse properties <em>PERMY</em> (K<!-- raw HTML omitted -->y<!-- raw HTML omitted -->) and PERMZ (K<!-- raw HTML omitted -->z<!-- raw HTML omitted -->):</p>
+<p><img src="/images/export/Equation_PerfInterval_K.png" alt=""></p>
+<p>The Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (D<!-- raw HTML omitted -->y<!-- raw HTML omitted --> and D<!-- raw HTML omitted -->z<!-- raw HTML omitted -->):</p>
+<p><img src="/images/export/Equation_PerfInterval_Peaceman.png" alt=""></p>
+<p>The x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (l<!-- raw HTML omitted -->x<!-- raw HTML omitted -->), the well radius (r<!-- raw HTML omitted -->w<!-- raw HTML omitted -->) and skin factor (S):</p>
+<p><img src="/images/export/Equation_PerfInterval_Trans.png" alt=""></p>
 <p>The y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:</p>
-
-<p><img src="/images/export/Equation_PerfInterval_TotalT.png" alt="" /></p>
-
+<p><img src="/images/export/Equation_PerfInterval_TotalT.png" alt=""></p>
 <p>If the <em>Export Calculated Transmissibilities</em> is chosen in the export setting (see <a href="#exporting-completion-data-to-eclipse">Exporting Completion Data to Eclipse</a>), this value is exported in the COMPDAT/COMPDATL keywords directly. If the <em>Export Default Connection Factors and WPIMULT</em> the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT/COMPDATL keywords (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.</p>
-
 <p>For an example of <em>COMPDAT</em> files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.</p>
-
 <h3 id="fracture-export">Fracture Export</h3>
-
 <h4 id="pressure-differential-depletion-scaling">Pressure Differential Depletion Scaling</h4>
-
 <p>For cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a <strong>Well Bore Hole Pressure</strong> (<strong>WBHP</strong>) larger than zero in the Summary Case information.</p>
-
-<p><img src="/images/export/Completions_Export_PDD_TimeStep.png" alt="" /></p>
-
+<p><img src="/images/export/Completions_Export_PDD_TimeStep.png" alt=""></p>
 <p>Having chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If <strong>WBHP From Summary Case</strong> is picked, the <strong>WBHP</strong> value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in <strong>WBHP Before Production Start</strong> is used.</p>
-
-<p><img src="/images/export/Completions_Export_PDD_WBHP.png" alt="" /></p>
-
+<p><img src="/images/export/Completions_Export_PDD_WBHP.png" alt=""></p>
 <p>If, however, a <strong>Fixed User Defined WBHP</strong> is chosen, the provided <strong>WBHP</strong> value is used for all wells.</p>
-
-<p><img src="/images/export/Completions_Export_PDD_User_WBHP.png" alt="" /></p>
-
+<p><img src="/images/export/Completions_Export_PDD_User_WBHP.png" alt=""></p>
 <h4 id="fracture-report-header">Fracture Report Header</h4>
-
 <p>At the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.</p>
-
 <h5 id="description-of-derived-data">Description of Derived Data</h5>
-
 <p>One of the tables displays derived data, see the example here:</p>
-
 <pre><code>               Tr   #con       Fcd       Area     KfWf         Kf      Wf       Xf        H       Km
 [cP.rm3/day/bars]               []       [m2]    [mDm]       [mD]     [m]      [m]      [m]     [mD]
 ----------------------------------------------------------------------------------------------------
           110.834     24   276.168   9315.748   54.889   3805.029   0.014   61.628   75.580   13.778
 </code></pre>
-
 <ul>
 <li><strong>Tr</strong> &ndash; Accumulated computed transmissibilies for all reservoir cells intersected by the fracture</li>
 <li><strong>#con</strong> &ndash; Number of reservoir cells intersected by the fracture</li>
@@ -1932,11 +1934,8 @@ if (!doNotTrack) {
 <li><strong>H</strong> &ndash; Longest continuous distance with fracture cells open for flow along a fracture grid column</li>
 <li><strong>Km</strong> &ndash; Area weighted average of matrix transmissibility (using Area defined above)</li>
 </ul>
-
 <h4 id="differential-depletion-fracture-output">Differential Depletion Fracture Output</h4>
-
 <p>In addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (<strong>WBHP From Summary Case</strong> or <strong>Fixed User Defined WBHP</strong>). For <strong>WBHP From Summary Case</strong> the <strong>User WBHP</strong> column will describe the well pressure used for all time steps before the production starts according to the summary case information and the <strong>Actual WBHP</strong> will describe the well pressure used in the scaling, which will be different from the <strong>User WBHP</strong> if the scaling is performed for a time step following the well productions start. Finally the columns <strong>Min Pressure Drop</strong> and <strong>Max Pressure Drop</strong> describes the minimum and maximum well drawdown for this particular fracture.</p>
-
 <pre><code>--
 -- Pressure Depletion Time step: 01.Feb 2001
 -- WBHP Source: WBHP From Summary Case
@@ -1948,13 +1947,9 @@ if (!doNotTrack) {
 -- B-4DH   Fracture_07   200.00000     28.21733            97.34970            
 -- 
 </code></pre>
-
 <h3 id="export-of-fishbone-completion-data">Export of Fishbone Completion Data</h3>
-
 <p>The transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.</p>
-
 <p>An example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.</p>
-
 <pre><code>WELSPECS
 -- Well          Grp   I   J    RefDepth   WellType   
    Well Path B   GR    26  45   1230       Oil        \
@@ -1972,11 +1967,8 @@ COMPDAT
    Well Path B     27     41     15     15     OPEN       1*      2.645858E-01      /
 /
 </code></pre>
-
 <p>For export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.</p>
-
 <p>The <em>WPIMULT</em> parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the <em>WPIMUT</em> keyword.</p>
-
 <pre><code>WELSPEC
 -- Well          Grp   I   J    RefDepth   WellType   
    Well Path B   GR    26  45   1230       Oil        \
@@ -1999,11 +1991,8 @@ WPIMULT
    Well Path B     25.11396     27     41     15      /
 /
 </code></pre>
-
 <h3 id="completions-for-lgr-welspecl-and-compdatl">Completions for LGR (WELSPECL and COMPDATL)</h3>
-
 <p>Completion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by &ldquo;_LGR&rdquo;. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns <strong>LGR</strong> and <strong>LgrName</strong>, respectively. The extra columns contains the name of the LGR grid.</p>
-
 <pre><code>WELSPECL
 -- Well      Grp   LGR      I   J   RefDepth   WellType   
    UWell-1   1*    WELLI1   2   9   1*         OIL         /
@@ -2016,35 +2005,24 @@ COMPDATL
 -- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679
    UWell-1   WELLI1    2   8   6    6    OPEN     1*    6.106791E+00   0.21600   1*   0.00000   1*   'Y'    /
 </code></pre>
-
 <h3 id="lgr-for-completions-temporary-lgrs">LGR for completions (Temporary LGRs)</h3>
-
 <p>The previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs.
 To accomplish this, do the following:</p>
-
 <ul>
 <li>Create LGRs for completions on selected well paths. See <a href="/wells-and-completions/completionslgr/">Completions LGR</a></li>
 <li>Export completions the usual way. See <a href="/export/completionexport/">Completion Export</a></li>
 </ul>
 
-
 <div class="notices info" ><p>In addition to the completion data, the geometrical definition of all temporary LGRs is also exported into &ldquo;*.dat&rdquo; files.</p>
 </div>
 
-
 <h2 id="multi-segment-well-model">Multi Segment Well Model</h2>
-
-<p>It is possible to export all the completions to a text file containing the Eclipse input data
+<p>It is possible to export all the completions to a text file containing the Eclipse input data 
 keywords needed to represent the completions as a Multi Segment Well. This is done by checking the <strong>Include Multi Segment Well Model</strong>. All completions are supported and are exported in somewhat different ways.</p>
-
 <h3 id="exported-msw-data">Exported MSW Data</h3>
-
 <p>In the output file there are data for three Eclipse keyword specified.</p>
-
 <h5 id="welsegs">WELSEGS</h5>
-
 <p>WELSEGS defines multi-segment wells. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for.  Example:</p>
-
 <pre><code>WELSEGS
 -- Name            Dep 1          Tlen 1       Vol 1     Len&amp;Dep     PresDrop     
    Well Path A     4137.09154     87.00000     1*        ABS         H--           /
@@ -2062,36 +2040,32 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
    53            53           27             52             2.34748       -0.81635         0.00960     0.00100      /
 /
 </code></pre>
-
 <ul>
-<li><p>The first <em>WELSEGS</em> entry contains information about the well:</p>
-
+<li>
+<p>The first <em>WELSEGS</em> entry contains information about the well:</p>
 <ul>
 <li><strong>Name</strong> - Name of well</li>
-<li><strong>Dep 1</strong> - TVD of start MD point, as given by the user in the Fishbones <strong>Start MD</strong> field.<br /></li>
-<li><strong>Tlen 1</strong> - Point given by the user in the Fishbones <strong>Start MD</strong> field.<br /></li>
+<li><strong>Dep 1</strong> - TVD of start MD point, as given by the user in the Fishbones <strong>Start MD</strong> field.</li>
+<li><strong>Tlen 1</strong> - Point given by the user in the Fishbones <strong>Start MD</strong> field.</li>
 <li><strong>Len&amp;Dep</strong> - incremental or absolute, as specified by the user in the Fishbones property editor.</li>
 <li><strong>PresDrop</strong> - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.</li>
-</ul></li>
-
-<li><p>The following <em>WELSEGS</em> entries contains information about each segment:</p>
-
+</ul>
+</li>
+<li>
+<p>The following <em>WELSEGS</em> entries contains information about each segment:</p>
 <ul>
 <li><strong>First Seg</strong>, <strong>Last Seg</strong> &ndash; Values are being exported pr segment, so both first and last segment number is the number of the segment being exported.</li>
 <li><strong>Branch Num</strong> &ndash; Branch number for segment being exported.</li>
-<li><strong>Outlet Seg</strong> &ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.<br /></li>
+<li><strong>Outlet Seg</strong> &ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.</li>
 <li><strong>Length</strong> &ndash; Length of segment (if incremental Len&amp;Dep above) or length of segments including this along well (if absolute Len&amp;Dep above). For ICDs length is set to 0.1.</li>
 <li><strong>Depth Change</strong> &ndash; Depth of segment, incremental or absolute as for Length. For ICDs depth is set to 0.</li>
-<li><strong>Diam</strong> &ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.<br /></li>
-<li><strong>Rough</strong> &ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.<br />
-<br /></li>
-</ul></li>
+<li><strong>Diam</strong> &ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.</li>
+<li><strong>Rough</strong> &ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.</li>
+</ul>
+</li>
 </ul>
-
 <h5 id="compsegs">COMPSEGS</h5>
-
 <p>An example of the COMPSEGS keyword as exported is shown below.</p>
-
 <pre><code>COMPSEGS
 -- Name            
    Well Path A      /
@@ -2101,19 +2075,14 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
    28     40     8      27            2.34748          2.96577         /
 /
 </code></pre>
-
 <p>The first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and containing the following field:</p>
-
 <ul>
 <li><strong>I</strong>, <strong>J</strong> and <strong>K</strong> &ndash; The Eclipse cell index</li>
 <li><strong>Branch no</strong> &ndash; Branch number for the segment</li>
 <li><strong>Start Length</strong>, <strong>End Length</strong> &ndash; Start and end length along the well for the relevant segment.</li>
 </ul>
-
 <h5 id="wsegvalv">WSEGVALV</h5>
-
 <p>An example of the WSEGVALV keyword as exported is shown below.</p>
-
 <pre><code>WSEGVALV
 -- Well Name       Seg No     Cv          Ac          
    Well Path A     3          1.50000     0.00008      /
@@ -2121,21 +2090,15 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
    Well Path A     7          1.50000     0.00008      /
 /
 </code></pre>
-
 <p>The parameters exported in the WEGVALV keyword are</p>
-
 <ul>
 <li><strong>Well Name</strong> &ndash; The name of the well.</li>
 <li><strong>Seg No</strong> &ndash; Segment number along the well.</li>
 <li><strong>Cv</strong> &ndash; The ICD Flow Coefficient, as entered by the user.</li>
-<li><strong>Ac</strong> &ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.<br />
-<br /></li>
+<li><strong>Ac</strong> &ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.</li>
 </ul>
-
 <h3 id="export-of-fractures-and-perforations-as-multi-segment-wells">Export of Fractures and Perforations as Multi-Segment Wells</h3>
-
 <p>Fractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the <strong>Diam</strong> and <strong>Rough</strong> parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.</p>
-
 <pre><code>WELSEGS
 -- Name      Dep 1          Tlen 1         Vol 1     Len&amp;Dep     PresDrop     
    C-1 H     2575.39553     2919.53029     1*        INC         H--           /
@@ -2154,9 +2117,7 @@ COMPSEGS
    27     43     1      2             11.27214         11.28214        /
    26     44     1      2             11.27214         11.28214        /
 </code></pre>
-
 <p>The entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.</p>
-
 <pre><code>WELSEGS
 -- Name       Dep 1          Tlen 1         Vol 1     Len&amp;Dep     PresDrop     
    B-1 AH     2530.38706     3137.28258     1*        INC         H--           /
@@ -2357,6 +2318,19 @@ COMPSEGS
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2367,6 +2341,9 @@ COMPSEGS
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3517,20 +3494,20 @@ COMPSEGS
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/contourmapexport/index.html b/export/contourmapexport/index.html
index 8b7d3555e9..aa94a95cc8 100644
--- a/export/contourmapexport/index.html
+++ b/export/contourmapexport/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Contour Map Export :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,14 +1802,11 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#export-of-contour-map-data">Export of Contour Map Data</a></li>
-<li><a href="#export-file-format">Export file format</a></li>
-<li><a href="#python-interface-for-export-of-contour-maps">Python interface for export of contour maps</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#export-of-contour-map-data">Export of Contour Map Data</a></li>
+    <li><a href="#export-file-format">Export file format</a></li>
+    <li><a href="#python-interface-for-export-of-contour-maps">Python interface for export of contour maps</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1800,45 +1831,29 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/export/ExportContourMap.png" alt="" /></p>
-
+<p><img src="/images/export/ExportContourMap.png" alt=""></p>
 <p>ResInsight can create <a href="/3d-main-window/contourmaps/">contour maps</a> based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.</p>
-
 <h2 id="export-of-contour-map-data">Export of Contour Map Data</h2>
-
 <p>To export a contour map, invoke one of the following options (c.f. figure above):</p>
-
 <ul>
 <li>Select context command <strong>Export Contour Map to text</strong> in the graphics window showing a contour map.</li>
 <li>Select context command <strong>Export Contour Map to text</strong> for a contour map in the <strong>Project Tree</strong></li>
 </ul>
-
 <p>This initiates the following dialog for export options:</p>
-
-<p><img src="/images/export/ExportContourMapDialog.png" alt="" /></p>
-
+<p><img src="/images/export/ExportContourMapDialog.png" alt=""></p>
 <p>As seen, the dialog facilitates the following options:</p>
-
 <ul>
 <li>Setting the file name for export.</li>
 <li>Export of local coordinates, i.e. coordinates measured from local origo defined in lower, left corner of contour map. Default is export of full UTM coordinates.</li>
 <li>Defining a text label to exclude undefined values. Default label is <em>NaN</em>.</li>
 <li>Exclude undefined values based on the given label.</li>
 </ul>
-
 <h2 id="export-file-format">Export file format</h2>
-
 <p>The file format for export of contour maps supports use of Python and numpy. For instance, an exported file may can be imported into numpy using the <em>loadtxt()</em> function.</p>
-
 <p>Metadata is included as comments in the beginning of the file. The character <em>#</em> as first character denotes a comment line.</p>
-
 <p>If local coordinates are exported, the UTM coordinate offset is included as a comment in the header of the export file (c.f. example file below).
 To anonymize the data, the UTM coordinate offset may be removed from file.</p>
-
 <p>Example file:</p>
-
 <pre><code># case name : 1_R001_REEK-0
 # sampling points : nx=90 ny=100
 # time and date : 01.Jan 2000
@@ -1858,14 +1873,12 @@ x               y               value
 5590.36204      381.16105       341.86177
 5717.41572      381.16105       342.34527
 ...             ...             ...
-</code></pre>
-
-<h2 id="python-interface-for-export-of-contour-maps">Python interface for export of contour maps</h2>
-
-<p>The <a href="/scripting/pythonrips/">ResInsight Python Interface</a>
-allows the user to
-<a href="/scripting/pythonrips/#contour-maps-map-type-contourmaptype-eclipse-1">access all contour maps</a> belonging to a project.
-A <a href="/scripting/pythonrips/">Python script</a> for exporting contour maps to a text file is included as one of the <a href="/scripting/pythonexamples/">Python examples</a>.</p>
+</code></pre><h2 id="python-interface-for-export-of-contour-maps">Python interface for export of contour maps</h2>
+<p>The [ResInsight Python Interface] (/scripting/pythonrips/)
+allows the user to 
+<a href="/scripting/pythonrips/">access all contour maps</a> belonging to a project.
+A <a href="/scripting/pythonrips/">Python script</a> for exporting contour maps to a text file is included as one of the [Python examples]
+(/scripting/pythonexamples/).</p>
 
 
 <footer class=" footline" >
@@ -2041,6 +2054,19 @@ A <a href="/scripting/pythonrips/">Python script</a> for exporting contour maps
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2051,6 +2077,9 @@ A <a href="/scripting/pythonrips/">Python script</a> for exporting contour maps
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3201,20 +3230,20 @@ A <a href="/scripting/pythonrips/">Python script</a> for exporting contour maps
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/eclipseproperties/index.html b/export/eclipseproperties/index.html
index e0917adba3..8f567685be 100644
--- a/export/eclipseproperties/index.html
+++ b/export/eclipseproperties/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Eclipse Properties :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,16 +1802,14 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#export-command">Export Command</a></li>
-<li><a href="#file-format">File Format</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#export-command">Export Command</a></li>
+        <li><a href="#file-format">File Format</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1802,32 +1834,21 @@ if (!doNotTrack) {
 
 
 
-
-
-<p>Eclipse Properties can be exported to Eclipse ASCII files.
-This is particularly useful when a new property is generated using Octave.
+<p>Eclipse Properties can be exported to Eclipse ASCII files. 
+This is particularly useful when a new property is generated using Octave. 
 The generated property can be exported for further use in the simulator.</p>
-
 <h3 id="export-command">Export Command</h3>
-
 <p>To export the property currently active in the 3D View, activate the right-click menu on a <strong>Cell Result</strong> item in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/export/ExportProperty.png" alt="" /></p>
-
+<p><img src="/images/export/ExportProperty.png" alt=""></p>
 <p>The following dialog will appear:</p>
-
-<p><img src="/images/export/ExportPropertyDialog.png" alt="" /></p>
-
+<p><img src="/images/export/ExportPropertyDialog.png" alt=""></p>
 <ul>
 <li><strong>Export File Name</strong> &ndash; The path to exported file</li>
 <li><strong>Eclipse Keyword</strong> &ndash; The keyword to use for the property in the eclipse file</li>
 <li><strong>Undefined Value</strong> &ndash; This value is written to the file for all values that are flagged as undefined in ResInsight</li>
 </ul>
-
 <h3 id="file-format">File Format</h3>
-
 <p>The exported file has the following format, that matches the Eclipse input format:</p>
-
 <pre><code>-- Exported from ResInsight
 &lt;keyword&gt;
 &lt;One number per cell separated by spaces&gt;
@@ -2008,6 +2029,19 @@ The generated property can be exported for further use in the simulator.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2018,6 +2052,9 @@ The generated property can be exported for further use in the simulator.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3168,20 +3205,20 @@ The generated property can be exported for further use in the simulator.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/exportwellpaths/index.html b/export/exportwellpaths/index.html
index 510ddb55f3..cb91811ca3 100644
--- a/export/exportwellpaths/index.html
+++ b/export/exportwellpaths/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1792,11 +1826,8 @@ if (!doNotTrack) {
 
 
 <p>In order to export well paths to dev files, select the menu item <strong>File -&gt; Export -&gt; Export Visible Well Paths</strong> or select one or more well paths and then select one of the items in the context sub menu <strong>Export Well Paths</strong>.</p>
-
 <p>A dialog appears after selecting an export well path command.</p>
-
-<p><img src="/images/export/ExportWellPathsDialog.png" alt="" /></p>
-
+<p><img src="/images/export/ExportWellPathsDialog.png" alt=""></p>
 <ul>
 <li><strong>Export Folder</strong> - Folder for the exported well path file(s). The folder will be created when performing the export and the names of the exported file(s) will be on the format &lt;well name&gt;.dev</li>
 <li><strong>MD Step Size</strong> - Spacing (measured depth) between samples along the well path in the exported file</li>
@@ -1976,6 +2007,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1986,6 +2030,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3136,20 +3183,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/fluxnummultnum/index.html b/export/fluxnummultnum/index.html
index c8d7ddf584..bf0dbefbf4 100644
--- a/export/fluxnummultnum/index.html
+++ b/export/fluxnummultnum/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>FLUXNUM/MULTNUM :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1792,19 +1826,14 @@ if (!doNotTrack) {
 
 
 <p>The visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.</p>
-
 <p>You can do this by using the command <strong>Export Visible Cells as FLUXNUM/MULTNUM</strong> found by right clicking:</p>
-
 <ul>
 <li><strong>View</strong> in the Project Tree.</li>
 <li><strong>Cell Result</strong> in the Project Tree.</li>
 <li>In any Eclipse <strong>3D View</strong>.</li>
 </ul>
-
 <p>The command can also be found in <strong>File -&gt; Export</strong>. If the command is used in the project tree, the visible cells from the selected view are used for calculation. In the 3D view and from File -&gt; Export, the visible cells from the currently active 3D view are used.</p>
-
-<p><img src="/images/export/fluxnumMultnum.png" alt="" /></p>
-
+<p><img src="/images/export/fluxnumMultnum.png" alt=""></p>
 <ul>
 <li><strong>Export Filename</strong> &ndash; Name of the file to export to.</li>
 <li><strong>Export Keyword</strong> &ndash; Selects the Eclipse keyword to export.</li>
@@ -1987,6 +2016,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1997,6 +2039,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3147,20 +3192,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/index.html b/export/index.html
index f4a59c8cdf..73dad9881a 100644
--- a/export/index.html
+++ b/export/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Export :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,10 +1820,8 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/export/ExportSectorModel_RightClick.png" alt="" /></p>
-
+	<p><img src="/images/export/ExportSectorModel_RightClick.png" alt=""></p>
 <p>ResInsight features the following capabilities for export of data to reporting or further analysis:</p>
-
 <ul>
 <li>convenient export of snapshots of 3D views and plots, either by direct export or automated modification of Eclipse 3D Views</li>
 <li>export of Eclipse properties, either direct or subsequent to post-processing by ResInsight, for input to further simulations</li>
@@ -1799,7 +1831,6 @@ if (!doNotTrack) {
 <li>export of sub-sections of an Eclipse Grid with Parameters and Faults to Eclipse ASCII files to perform additional simulations</li>
 <li>export of a contour map to text file</li>
 </ul>
-
 <p>The following subchapters details the functionality and capabilites.</p>
 
 
@@ -1978,6 +2009,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1988,6 +2032,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3134,20 +3181,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/index.xml b/export/index.xml
index c378a90950..923c20d286 100644
--- a/export/index.xml
+++ b/export/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Export on ResInsight</title>
diff --git a/export/sectormodel/index.html b/export/sectormodel/index.html
index 2b0bf2c37f..8c80ad9e7f 100644
--- a/export/sectormodel/index.html
+++ b/export/sectormodel/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Sector Model :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#exporting-an-eclipse-sector-model">Exporting an Eclipse Sector Model</a></li>
-<li><a href="#exporting-grid-and-faults">Exporting Grid and Faults</a>
-<ul>
-<li><a href="#grid-export">Grid Export</a></li>
-<li><a href="#grid-box-selection">Grid Box Selection</a></li>
-<li><a href="#grid-refinement">Grid Refinement</a></li>
-<li><a href="#faults">Faults</a></li>
-</ul></li>
-<li><a href="#exporting-parameters">Exporting Parameters</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#exporting-an-eclipse-sector-model">Exporting an Eclipse Sector Model</a></li>
+        <li><a href="#exporting-grid-and-faults">Exporting Grid and Faults</a></li>
+        <li><a href="#exporting-parameters">Exporting Parameters</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,59 +1835,37 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new
 Simulations on the sub-section.</p>
-
 <h3 id="exporting-an-eclipse-sector-model">Exporting an Eclipse Sector Model</h3>
-
 <p>To launch the export dialog, right-click on either the <strong>3D-view</strong> in question or the <strong>Cell Result</strong>.</p>
-
-<p><img src="/images/export/ExportSectorModel_RightClick.png" alt="" /></p>
-
+<p><img src="/images/export/ExportSectorModel_RightClick.png" alt=""></p>
 <h3 id="exporting-grid-and-faults">Exporting Grid and Faults</h3>
-
-<p><img src="/images/export/ExportSectorModel_Grid.png" alt="" /></p>
-
+<p><img src="/images/export/ExportSectorModel_Grid.png" alt=""></p>
 <h4 id="grid-export">Grid Export</h4>
-
 <p>The Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the <strong>Export Grid Data</strong> option.
 If the option <strong>Export in Local Coordinates</strong> is checked, the UTM-portion of the coordinates will be stripped and the Grid will
 be exported in a local coordinate system with no reference to actual location.</p>
-
 <h4 id="grid-box-selection">Grid Box Selection</h4>
-
 <p>The Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:</p>
-
 <ul>
 <li><strong>All Visible Cells</strong> &ndash; Controlled by range and property filters in the current view.</li>
 <li><strong>All Active Cells</strong> &ndash; All active cells in the Grid.</li>
 <li><strong>The Full Grid</strong> &ndash; The complete grid including inactive cells.</li>
 <li><strong>User Defined Selection</strong> &ndash; This will make the min and max IJK selection available to the user.</li>
 </ul>
-
 <p>Furthermore, by checking <strong>Make Invisible Cells Inactive</strong> any cells that are within the IJK bounding box, but are invisible, will be made
 inactive (ACTNUM = 0) in the exported grid.</p>
-
 <h4 id="grid-refinement">Grid Refinement</h4>
-
 <p>The grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.</p>
-
 <h4 id="faults">Faults</h4>
-
 <p>Optionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing &ldquo;Do not Export&rdquo; from the
 <strong>Export Fault Data</strong> drop down list.</p>
-
 <h3 id="exporting-parameters">Exporting Parameters</h3>
-
-<p><img src="/images/export/ExportSectorModel_Parameters.png" alt="" /></p>
-
-<p>The Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are
+<p><img src="/images/export/ExportSectorModel_Parameters.png" alt=""></p>
+<p>The Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are 
 EQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.</p>
-
 <p>Other statuc result variables may be selected.</p>
-
 <p>By default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to
 append them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the <strong>Export Parameters</strong> drop down list.</p>
 
@@ -2039,6 +2043,19 @@ append them to the grid file, export them all into a single parameter file or om
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2049,6 +2066,9 @@ append them to the grid file, export them all into a single parameter file or om
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3199,20 +3219,20 @@ append them to the grid file, export them all into a single parameter file or om
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/snapshots/index.html b/export/snapshots/index.html
index aea930c50e..f094522cb6 100644
--- a/export/snapshots/index.html
+++ b/export/snapshots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Snapshots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,18 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#snapshots-of-existing-views">Snapshots of Existing Views</a>
-<ul>
-<li><a href="#snapshot-to-clipboard">Snapshot to Clipboard</a></li>
-<li><a href="#snapshot-to-file">Snapshot to File</a></li>
-<li><a href="#snapshot-all-views-plots-to-file">Snapshot All Views/Plots to File</a></li>
-</ul></li>
-<li><a href="#advanced-snapshot-export">Advanced Snapshot Export</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#snapshots-of-existing-views">Snapshots of Existing Views</a>
+      <ul>
+        <li><a href="#snapshot-to-clipboard">Snapshot to Clipboard</a></li>
+        <li><a href="#snapshot-to-file">Snapshot to File</a></li>
+        <li><a href="#snapshot-all-viewsplots-to-file">Snapshot All Views/Plots to File</a></li>
+      </ul>
+    </li>
+    <li><a href="#advanced-snapshot-export">Advanced Snapshot Export</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1804,54 +1836,34 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.</p>
-
 <h2 id="snapshots-of-existing-views">Snapshots of Existing Views</h2>
-
 <p>The commands to snapshot existing views and plots are available from the toolbar and the <strong>Edit</strong> and <strong>File</strong>-&gt;<strong>Export</strong> menus in the main windows <img src="https://resinsight.org/images/export/SnapShotToolBar.png" style="display:inline; vertical-align:middle; margin:0">
 </p>
-
 <h3 id="snapshot-to-clipboard">Snapshot to Clipboard</h3>
-
 <p>A snapshot of the active view is copied to the clipboard using <strong>Edit -&gt; Copy Snapshot To Clipboard</strong>  <img src="https://resinsight.org/images/export/SnapShot.png" style="display:inline; vertical-align:middle; margin:0">
 .</p>
-
 <h3 id="snapshot-to-file">Snapshot to File</h3>
-
 <p>Image export of the currently active 3D View or Plot Window can be launched from <strong>File -&gt; Export -&gt; Snapshot To File</strong> <img src="https://resinsight.org/images/export/SnapShotSave.png" style="display:inline; vertical-align:middle; margin:0">
 .</p>
-
-<h3 id="snapshot-all-views-plots-to-file">Snapshot All Views/Plots to File</h3>
-
+<h3 id="snapshot-all-viewsplots-to-file">Snapshot All Views/Plots to File</h3>
 <p>If a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using <strong>File -&gt; Export -&gt; Snapshot All Views To File</strong>  <img src="https://resinsight.org/images/export/SnapShotSaveViews.png" style="display:inline; vertical-align:middle; margin:0">
 . This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.</p>
-
 <p>The files generated are stored in a folder named <em><code>snapshots</code></em> within the folder where the Project File resides.</p>
 
-
-<div class="notices note" ><p>Snapshots of existing views can also be created and saved from the command line
- ( See <a href="/scripting/commandlineinterface/">Command Line Interface</a> ).</p>
+<div class="notices note" ><p>Snapshots of existing views can also be created and saved from the command line 
+( See <!-- raw HTML omitted -->Command Line Interface<!-- raw HTML omitted --> ).</p>
 </div>
 
-
 <h2 id="advanced-snapshot-export">Advanced Snapshot Export</h2>
-
 <p>The <strong>Advanced Snapshot Export</strong>  <img src="https://resinsight.org/images/export/SnapShotSaveViews.png" style="display:inline; vertical-align:middle; margin:0">
  command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.</p>
-
-<p>The <strong>Advanced Snapshot Export</strong> is available from the <strong>File</strong>-&gt;<strong>Export</strong> menu in the <strong>3D Main Window</strong>
+<p>The <strong>Advanced Snapshot Export</strong> is available from the <strong>File</strong>-&gt;<strong>Export</strong> menu in the <strong>3D Main Window</strong> 
 Invoking the command will display the following dialog:</p>
-
-<p><img src="/images/export/SnapshotAdvancedExport.png" alt="" /></p>
-
+<p><img src="/images/export/SnapshotAdvancedExport.png" alt=""></p>
 <p>This table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.</p>
-
 <p>To edit a row, the row must be activated by toggling it on in the <strong>Active</strong> column, then double click on the cell to edit.</p>
-
 <p>Options represented by columns:</p>
-
 <ul>
 <li><strong>View</strong> &ndash; Selects the view to modify.</li>
 <li><strong>Result Type</strong>, <strong>Properties</strong> &ndash; Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row.</li>
@@ -1859,11 +1871,8 @@ Invoking the command will display the following dialog:</p>
 <li><strong>Range Filter Slice</strong>, <strong>Range Start</strong>, <strong>Range End</strong> &ndash; Defines a range filter slice that will be added to the view, and then cycled from <em>Range Start</em> to <em>Range End</em> when creating snapshots.</li>
 <li><strong>Cases</strong> &ndash; Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.</li>
 </ul>
-
 <p>The number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.</p>
-
 <p>Rows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.</p>
-
 <p>The snapshots will be generated and saved to the folder displayed in the <strong>Export Folder</strong> field, when pressing the <strong>Export</strong> button. This might take quite some time, depending on you settings.</p>
 
 
@@ -2040,6 +2049,19 @@ Invoking the command will display the following dialog:</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2050,6 +2072,9 @@ Invoking the command will display the following dialog:</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3197,20 +3222,20 @@ Invoking the command will display the following dialog:</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/download-and-install/buildinstructions/index.html b/getting-started/download-and-install/buildinstructions/index.html
index a2a178182b..60c034589a 100644
--- a/getting-started/download-and-install/buildinstructions/index.html
+++ b/getting-started/download-and-install/buildinstructions/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Build Instructions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1774,42 +1808,25 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#source-code">Source code</a></li>
-<li><a href="#dependencies-and-prerequisites">Dependencies and Prerequisites</a>
-<ul>
-<li><a href="#windows-compiler">Windows Compiler</a></li>
-<li><a href="#gcc-compiler">GCC Compiler</a></li>
-<li><a href="#qt5">Qt5</a>
-<ul>
-<li><a href="#qt4-deprecated">Qt4 (Deprecated)</a></li>
-</ul></li>
-<li><a href="#cmake">CMake</a></li>
-</ul></li>
-<li><a href="#build-instructions">Build Instructions</a>
-<ul>
-<li><a href="#windows">Windows</a></li>
-<li><a href="#linux">Linux</a></li>
-<li><a href="#cmake-options-for-resinsight">CMake Options for ResInsight</a>
-<ul>
-<li><a href="#advanced-options">Advanced Options</a></li>
-<li><a href="#configuration-parameters-for-python-beta">Configuration parameters for Python (beta)</a></li>
-</ul></li>
-<li><a href="#optional-libraries-and-features">Optional Libraries and features</a>
-<ul>
-<li><a href="#python-beta">Python (Beta)</a></li>
-<li><a href="#octave">Octave</a>
-<ul>
-<li><a href="#octave-dependencies-for-debian-based-distributions">Octave Dependencies for Debian Based Distributions</a></li>
-</ul></li>
-<li><a href="#odb-support">ODB support</a></li>
-<li><a href="#hdf5">HDF5</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#source-code">Source code</a></li>
+    <li><a href="#dependencies-and-prerequisites">Dependencies and Prerequisites</a>
+      <ul>
+        <li><a href="#windows-compiler">Windows Compiler</a></li>
+        <li><a href="#gcc-compiler">GCC Compiler</a></li>
+        <li><a href="#qt5">Qt5</a></li>
+        <li><a href="#cmake">CMake</a></li>
+      </ul>
+    </li>
+    <li><a href="#build-instructions">Build Instructions</a>
+      <ul>
+        <li><a href="#windows">Windows</a></li>
+        <li><a href="#linux">Linux</a></li>
+        <li><a href="#cmake-options-for-resinsight">CMake Options for ResInsight</a></li>
+        <li><a href="#optional-libraries-and-features">Optional Libraries and features</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1834,60 +1851,36 @@ if (!doNotTrack) {
 
 
 
-
-
 <h2 id="source-code">Source code</h2>
-
 <p>The source code is hosted at <a href="https://github.com/opm/resinsight">GitHub</a></p>
-
 <p>In a git enabled shell do: <code>git clone https://github.com/OPM/ResInsight.git</code></p>
-
 <h2 id="dependencies-and-prerequisites">Dependencies and Prerequisites</h2>
-
 <h3 id="windows-compiler">Windows Compiler</h3>
-
 <p>Visual Studio 2015 and later is supported.</p>
-
 <h3 id="gcc-compiler">GCC Compiler</h3>
-
 <p>GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with</p>
-
 <pre><code>source /opt/rh/devtoolset-3/enable
 </code></pre>
-
 <h3 id="qt5">Qt5</h3>
-
 <p><a href="http://download.qt.io/archive/qt/">Qt</a> Qt5 version 5.6.0 or later is supported.</p>
-
 <p>On some configurations you will be asked to specify the location of Qt5. Example for Windows :
 <code>Qt5_DIR=d:\Qt\5.11.3\msvc2017_64\lib\cmake\Qt5</code></p>
-
 <h4 id="qt4-deprecated">Qt4 (Deprecated)</h4>
 
-
 <div class="notices info" ><p>Qt4 is marked as deprecated and support for using Qt4 will soon be removed.</p>
 </div>
 
-
 <p><a href="http://download.qt.io/archive/qt/">Qt</a> Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.</p>
-
 <p><code>RESINSIGHT_BUILD_WITH_QT5=FALSE</code></p>
-
-<p>You will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this :
+<p>You will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this : 
 <a href="https://github.com/appleseedhq/appleseed/wiki/Making-Qt-4.8.7-compile-with-Visual-Studio-2015">Qt-patch</a></p>
-
 <h3 id="cmake">CMake</h3>
-
 <p><a href="https://cmake.org/download/">CMake</a> version 2.8 or later is supported.</p>
-
 <h2 id="build-instructions">Build Instructions</h2>
-
-<p>The ResInsight build may be configured in different ways, with optional support for Octave plugins,
+<p>The ResInsight build may be configured in different ways, with optional support for Octave plugins, 
 ABAQUS ODB API, HDF5, Pyton, and OpenMP. This is configured using options in CMake.</p>
-
-<p>If you check the button &lsquo;Grouped&rsquo; in the CMake GUI, the CMake variables are grouped by prefix.
+<p>If you check the button &lsquo;Grouped&rsquo; in the CMake GUI, the CMake variables are grouped by prefix. 
 This makes it easier to see all of the options for ResInsight.</p>
-
 <ul>
 <li>Open the CMake GUI</li>
 <li>Set the path to the source code</li>
@@ -1897,24 +1890,17 @@ This makes it easier to see all of the options for ResInsight.</p>
 <li>Click <strong>Generate</strong> to generate the makefiles or solution file and project files in the build directory</li>
 <li>Run the compiler using the generated makefiles or solution file/project files to build ResInsight</li>
 </ul>
-
 <h3 id="windows">Windows</h3>
-
-<p>ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio <sup>2015</sup>&frasl;<sub>2017</sub>.
-Typical usage on Windows is to follow the build instructions above, and then open the generated
+<p>ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015/2017. 
+Typical usage on Windows is to follow the build instructions above, and then open the generated 
 solution file in Visual Studio to build the application.</p>
-
 <h3 id="linux">Linux</h3>
-
 <p>Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:</p>
-
 <ul>
 <li>make</li>
 <li>make install</li>
 </ul>
-
 <p>To build from the command line without using the CMake GUI:</p>
-
 <ul>
 <li>mkdir ResInsight_build</li>
 <li>cd ResInsight_build</li>
@@ -1925,11 +1911,8 @@ solution file in Visual Studio to build the application.</p>
 <li>make</li>
 <li>make install</li>
 </ul>
-
 <p>You will find the ResInsight binary under the Install directory in your build directory.</p>
-
 <h3 id="cmake-options-for-resinsight">CMake Options for ResInsight</h3>
-
 <table>
 <thead>
 <tr>
@@ -1938,32 +1921,27 @@ solution file in Visual Studio to build the application.</p>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td><code>RESINSIGHT_BUILD_DOCUMENTATION</code></td>
 <td>OFF</td>
 <td>Use Doxygen to create the HTML based API documentation. Doxygen must be properly installed.</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_ENABLE_GRPC</code></td>
 <td>OFF</td>
 <td>Enable gRPC scripting server. Required to be able to use ResInsight from Python</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_HDF5_DIR</code></td>
 <td>Blank</td>
 <td>Windows Only: Optional path to HDF5 libraries on Windows</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_ODB_API_DIR</code></td>
 <td>Blank</td>
 <td>Optional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_USE_OPENMP</code></td>
 <td>ON</td>
@@ -1971,11 +1949,8 @@ solution file in Visual Studio to build the application.</p>
 </tr>
 </tbody>
 </table>
-
 <h4 id="advanced-options">Advanced Options</h4>
-
 <p>To be able to modify <strong>Advanced Options</strong> from the CMake User Interface, tick the checkbox <strong>Advanced</strong></p>
-
 <table>
 <thead>
 <tr>
@@ -1984,56 +1959,47 @@ solution file in Visual Studio to build the application.</p>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td><code>RESINSIGHT_BUILD_WITH_QT5</code></td>
 <td>ON</td>
 <td>If ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed)</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_QT5_BUNDLE_LIBRARIES</code></td>
 <td>OFF</td>
 <td>Linux only: Include Qt5 libraries in the installation package</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_BUNDLE_OPENSSL</code></td>
 <td>OFF</td>
 <td>Bundle the OpenSSL library DLLs in the Windows installer package</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_ENABLE_COTIRE</code></td>
 <td>OFF</td>
 <td>Experimental speedup of compilation using cotire</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING</code></td>
 <td>ON</td>
 <td>Enable Souring features</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_INCLUDE_APPFWK_TESTS</code></td>
 <td>OFF</td>
 <td>Include unit tests from thirdparty libraries AppFwk and VizFwk</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS</code></td>
 <td>OFF</td>
 <td>Include Application Code Unit Tests</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_PRIVATE_INSTALL</code></td>
 <td>ON</td>
 <td>Linux only: Include libecl libraries in the installation package</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_HDF5_BUNDLE_LIBRARIES</code></td>
 <td>OFF</td>
@@ -2041,11 +2007,8 @@ solution file in Visual Studio to build the application.</p>
 </tr>
 </tbody>
 </table>
-
 <h4 id="configuration-parameters-for-python-beta">Configuration parameters for Python (beta)</h4>
-
 <p>These parameters are considered beta, and might change.</p>
-
 <table>
 <thead>
 <tr>
@@ -2054,20 +2017,17 @@ solution file in Visual Studio to build the application.</p>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td><code>RESINSIGHT_ENABLE_GRPC</code></td>
 <td>OFF</td>
 <td>Enable gRPC scripting server. Required to be able to use ResInsight from Python</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_GRPC_PYTHON_EXECUTABLE</code></td>
 <td>Blank</td>
 <td>Location of Python3 executable</td>
 </tr>
-
 <tr>
 <td><code>RESINSIGHT_GRPC_INSTALL_PREFIX</code></td>
 <td>Blank</td>
@@ -2075,52 +2035,33 @@ solution file in Visual Studio to build the application.</p>
 </tr>
 </tbody>
 </table>
-
 <h3 id="optional-libraries-and-features">Optional Libraries and features</h3>
-
 <h4 id="python-beta">Python (Beta)</h4>
-
 <p>Scripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.</p>
-
 <p>The current build instructions are specified in text files in the ResInsight repository.</p>
-
 <ul>
 <li><a href="https://github.com/OPM/ResInsight/blob/dev/GRPC_install_instructions.txt">Grpc install instructions</a></li>
 <li><a href="https://github.com/OPM/ResInsight/blob/dev/build_grpc_linux.sh">Helper script for Linux</a></li>
 </ul>
-
 <p>See <a href="/scripting/pythonrips/"> Python API </a> for how to use the Python library.</p>
-
 <h4 id="octave">Octave</h4>
-
 <p>Octave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:</p>
-
 <p><code>OCTAVE_CONFIG_EXECUTABLE : d:\octave\Octave-4.0.0\bin\octave-config.exe</code></p>
-
-<p>It is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for
-the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like &lsquo;Failed to find mkoctfile&rsquo;.
+<p>It is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for 
+the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like &lsquo;Failed to find mkoctfile&rsquo;. 
 This will not break the build or compilation of ResInsight.</p>
-
 <p>ResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.</p>
-
 <h5 id="octave-dependencies-for-debian-based-distributions">Octave Dependencies for Debian Based Distributions</h5>
-
 <p>The following command line can be used as a starting point to install required libraries
 <code>sudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev</code></p>
-
 <h4 id="odb-support">ODB support</h4>
-
-<p>ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API
-from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library
-files must be specified. Leaving this option blank gives a build without ODB support.
+<p>ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API 
+from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library 
+files must be specified. Leaving this option blank gives a build without ODB support. 
 ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.</p>
-
 <h4 id="hdf5">HDF5</h4>
-
 <p>HDF5 is used to read SourSimRL result files. On Windows this is optional, while on Linux the installed HDF5 library will be used if present.</p>
-
 <p>Use an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.</p>
-
 <p>Tested with 1.8.18 on windows, and default installation on RedHat 6.</p>
 
 
@@ -2306,6 +2247,19 @@ ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windo
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2316,6 +2270,9 @@ ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windo
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3458,20 +3415,20 @@ ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windo
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/download-and-install/index.html b/getting-started/download-and-install/index.html
index 9d0ffcf567..5fafb7d494 100644
--- a/getting-started/download-and-install/index.html
+++ b/getting-started/download-and-install/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Download and Install :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,13 +1802,10 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#installation">Installation</a></li>
-<li><a href="#what-s-new">What&rsquo;s new</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#installation">Installation</a></li>
+    <li><a href="#whats-new">What&rsquo;s new</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1800,40 +1831,39 @@ if (!doNotTrack) {
 
 
 
-	
-
-<h2 id="installation">Installation</h2>
-
+	<h2 id="installation">Installation</h2>
 <p>See the following for common install procedures and options:</p>
-
 <ul>
-<li><p><a href="/getting-started/download-and-install/linux-installation/"> Linux Installation </a></p></li>
-
-<li><p><a href="/getting-started/download-and-install/windows-installation/"> Windows Installation </a></p></li>
+<li>
+<p><a href="/getting-started/download-and-install/linux-installation/"> Linux Installation </a></p>
+</li>
+<li>
+<p><a href="/getting-started/download-and-install/windows-installation/"> Windows Installation </a></p>
+</li>
 </ul>
-
-<p>See <a href="/getting-started/download-and-install/buildinstructions/"> Build Instructions </a> for the complete list of configuration options including support for
+<p>See <a href="/getting-started/download-and-install/buildinstructions/"> Build Instructions </a> for the complete list of configuration options including support for 
 Octave plugins, ABAQUS ODB API, and HDF5.</p>
-
-<h2 id="what-s-new">What&rsquo;s new</h2>
-
-<p>ResInsight is under continuous development targeting two major releases per year.
+<h2 id="whats-new">What&rsquo;s new</h2>
+<p>ResInsight is under continuous development targeting two major releases per year. 
 For an overview of some of its new and exciting features, see the following:</p>
-
 <ul>
-<li><p><a href="/getting-started/whats-new/releasenotes_2019_12_1/"> ResInsight 2019.12.1 </a></p></li>
-
-<li><p><a href="/getting-started/whats-new/releasenotes_2019_12/"> ResInsight 2019.12 </a></p></li>
-
-<li><p><a href="/getting-started/whats-new/releasenotes_2019_08/"> ResInsight 2019.08 </a></p></li>
-
-<li><p><a href="/getting-started/whats-new/releasenotes_2019_04/"> ResInsight 2019.04 </a></p></li>
-
-<li><p><a href="/getting-started/whats-new/releasenotes_2018_11/"> ResInsight 2018.11 </a></p></li>
+<li>
+<p><a href="/getting-started/whats-new/releasenotes_2019_12_1/"> ResInsight 2019.12.1 </a></p>
+</li>
+<li>
+<p><a href="/getting-started/whats-new/releasenotes_2019_12/"> ResInsight 2019.12 </a></p>
+</li>
+<li>
+<p><a href="/getting-started/whats-new/releasenotes_2019_08/"> ResInsight 2019.08 </a></p>
+</li>
+<li>
+<p><a href="/getting-started/whats-new/releasenotes_2019_04/"> ResInsight 2019.04 </a></p>
+</li>
+<li>
+<p><a href="/getting-started/whats-new/releasenotes_2018_11/"> ResInsight 2018.11 </a></p>
+</li>
 </ul>
-
 <p><a href="/getting-started/other/releasenotification/"> Sign up to be notified of new releases </a></p>
-
 <p>For the complete list of releases and updates, please visit <a href="https://github.com/OPM/ResInsight/releases/">ResInsight on Github</a>.</p>
 
 
@@ -2017,6 +2047,19 @@ For an overview of some of its new and exciting features, see the following:</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2027,6 +2070,9 @@ For an overview of some of its new and exciting features, see the following:</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3169,20 +3215,20 @@ For an overview of some of its new and exciting features, see the following:</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/download-and-install/index.xml b/getting-started/download-and-install/index.xml
index 2b8636458c..1301422a8e 100644
--- a/getting-started/download-and-install/index.xml
+++ b/getting-started/download-and-install/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Download and Install on ResInsight</title>
@@ -18,7 +18,7 @@
       <guid>https://resinsight.org/getting-started/download-and-install/linux-installation/</guid>
       <description>Install ResInsight From Binary Packages on Linux Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.
 Red Hat Enterprise Linux 6 or 7 Login as root and do:
-yum-config-manager --add-repo https://opm-project.org/package/opm.repo yum install resinsight yum install resinsight-octave  Then you are good, and can start ResInsight by typing: ResInsight
+yum-config-manager --add-repo https://opm-project.org/package/opm.repoyum install resinsightyum install resinsight-octave Then you are good, and can start ResInsight by typing: ResInsight
 Ubuntu Linux 16.04-64bit On the command line do:</description>
     </item>
     
@@ -43,7 +43,7 @@ Ubuntu Linux 16.04-64bit On the command line do:</description>
 In a git enabled shell do: git clone https://github.com/OPM/ResInsight.git
 Dependencies and Prerequisites Windows Compiler Visual Studio 2015 and later is supported.
 GCC Compiler GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with
-source /opt/rh/devtoolset-3/enable  Qt5 Qt Qt5 version 5.6.0 or later is supported.
+source /opt/rh/devtoolset-3/enable Qt5 Qt Qt5 version 5.6.0 or later is supported.
 On some configurations you will be asked to specify the location of Qt5.</description>
     </item>
     
diff --git a/getting-started/download-and-install/linux-installation/index.html b/getting-started/download-and-install/linux-installation/index.html
index 5f8ae9a378..db25dfa452 100644
--- a/getting-started/download-and-install/linux-installation/index.html
+++ b/getting-started/download-and-install/linux-installation/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Linux Installation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1774,25 +1808,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#install-resinsight">Install ResInsight</a>
-<ul>
-<li><a href="#from-binary-packages-on-linux">From Binary Packages on Linux</a>
-<ul>
-<li><a href="#red-hat-enterprise-linux-6-or-7">Red Hat Enterprise Linux 6 or 7</a></li>
-<li><a href="#ubuntu-linux-16-04-64bit">Ubuntu Linux 16.04-64bit</a></li>
-</ul></li>
-<li><a href="#from-downloaded-tarball">From downloaded tarball</a>
-<ul>
-<li><a href="#display-menu-icons-in-gnome-optional">Display Menu Icons in GNOME (Optional)</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#setup-octave-interface-optional">Setup Octave Interface (optional)</a></li>
-<li><a href="#workaround-for-crash-using-virtual-box">Workaround for crash using Virtual Box</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#install-resinsight">Install ResInsight</a>
+      <ul>
+        <li><a href="#from-binary-packages-on-linux">From Binary Packages on Linux</a></li>
+        <li><a href="#from-downloaded-tarball">From downloaded tarball</a></li>
+      </ul>
+    </li>
+    <li><a href="#setup-octave-interface-optional">Setup Octave Interface (optional)</a></li>
+    <li><a href="#workaround-for-crash-using-virtual-box">Workaround for crash using Virtual Box</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1817,32 +1842,21 @@ if (!doNotTrack) {
 
 
 
-
-
 <h2 id="install-resinsight">Install ResInsight</h2>
-
 <h3 id="from-binary-packages-on-linux">From Binary Packages on Linux</h3>
 
-
 <div class="notices info" ><p>Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.</p>
 </div>
 
-
 <h4 id="red-hat-enterprise-linux-6-or-7">Red Hat Enterprise Linux 6 or 7</h4>
-
 <p>Login as root and do:</p>
-
 <pre><code>yum-config-manager --add-repo https://opm-project.org/package/opm.repo
 yum install resinsight
 yum install resinsight-octave
 </code></pre>
-
 <p>Then you are good, and can start ResInsight by typing: ResInsight</p>
-
-<h4 id="ubuntu-linux-16-04-64bit">Ubuntu Linux 16.04-64bit</h4>
-
+<h4 id="ubuntu-linux-1604-64bit">Ubuntu Linux 16.04-64bit</h4>
 <p>On the command line do:</p>
-
 <pre><code>sudo apt-get update
 sudo apt-get install software-properties-common
 sudo apt-add-repository ppa:opm/ppa
@@ -1850,62 +1864,45 @@ sudo apt-get update
 sudo apt-get install resinsight
 sudo apt-get install octave-resinsight
 </code></pre>
-
 <p>Start ResInsight by typing : <code>ResInsight</code></p>
 
-
 <div class="notices info" ><p>For further installation details, see the ResInsight distribution on <a href="http://opm-project.org/?page_id=36">Opm Project Downloading and Installing</a>.</p>
 </div>
 
 
-
-<div class="notices info" ><p>The binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see
+<div class="notices info" ><p>The binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see 
 <a href="/getting-started/download-and-install/buildinstructions/">Build Instructions</a>.</p>
 </div>
 
-
 <h3 id="from-downloaded-tarball">From downloaded tarball</h3>
-
 <ol>
 <li>Download TAR.GZ binary distribution from <a href="https://github.com/OPM/ResInsight/releases" title="release section on GitHub">https://github.com/OPM/ResInsight/releases</a></li>
 <li>Extract content from TAR file</li>
 <li>Start ./ResInsight</li>
 </ol>
-
 <h4 id="display-menu-icons-in-gnome-optional">Display Menu Icons in GNOME (Optional)</h4>
-
 <p>By default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :</p>
-
 <pre><code>gconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true
 gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true
-</code></pre>
-
-<p>This fix was taken from reply number 11 in this <a href="https://bbs.archlinux.org/viewtopic.php?id=117414">thread</a></p>
-
+</code></pre><p>This fix was taken from reply number 11 in this <a href="https://bbs.archlinux.org/viewtopic.php?id=117414">thread</a></p>
 <h2 id="setup-octave-interface-optional">Setup Octave Interface (optional)</h2>
-
 <ol>
 <li>Install Octave directly from the package manager in Linux. See the documentation for your particular distribution.</li>
 <li>Launch ResInsight, open <strong>Edit-&gt;Preferences</strong></li>
 <li>Enter the path to the Octave command line interpreter executable <code>octave-cli</code> (for older version of octave use <code>octave</code>)</li>
 </ol>
 
-
-<div class="notices info" ><p>The precompiled octave interface distributed in the tarball is only tested for RedHat 6. <br>
-It is <b>not</b> expected to work for other configurations.
-(ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)<br>
-<br>
-If you need the octave interface to work on a different OS, you need to build ResInsight yourself.<br>
-See <a href="/getting-started/download-and-install/buildinstructions/">Build Instructions</a></p>
+<div class="notices info" ><p>The precompiled octave interface distributed in the tarball is only tested for RedHat 6. <!-- raw HTML omitted -->
+It is <!-- raw HTML omitted -->not<!-- raw HTML omitted --> expected to work for other configurations.
+(ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
+If you need the octave interface to work on a different OS, you need to build ResInsight yourself.<!-- raw HTML omitted --> 
+See <!-- raw HTML omitted -->Build Instructions<!-- raw HTML omitted --></p>
 </div>
 
-
 <h2 id="workaround-for-crash-using-virtual-box">Workaround for crash using Virtual Box</h2>
-
 <p>Uncheck <strong>Settings-&gt;Display-&gt;Enable 3D Acceleration</strong>. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.</p>
-
 <p>Here is a pointer addressing the issue with Virtual Box, this is not testes by us:</p>
-
 <p><a href="https://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox">https://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox</a></p>
 
 
@@ -2088,6 +2085,19 @@ See <a href="/getting-started/download-and-install/buildinstructions/">Build Ins
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2098,6 +2108,9 @@ See <a href="/getting-started/download-and-install/buildinstructions/">Build Ins
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3240,20 +3253,20 @@ See <a href="/getting-started/download-and-install/buildinstructions/">Build Ins
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/download-and-install/windows-installation/index.html b/getting-started/download-and-install/windows-installation/index.html
index 04cfeca5af..2e437acc14 100644
--- a/getting-started/download-and-install/windows-installation/index.html
+++ b/getting-started/download-and-install/windows-installation/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Windows Installation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1774,16 +1808,14 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#resinsight-installation">ResInsight Installation</a></li>
-<li><a href="#octave-installation-optional">Octave Installation (optional)</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#resinsight-installation">ResInsight Installation</a></li>
+        <li><a href="#octave-installation-optional">Octave Installation (optional)</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1808,38 +1840,30 @@ if (!doNotTrack) {
 
 
 
-
-
 <h3 id="resinsight-installation">ResInsight Installation</h3>
-
 <ol>
 <li>Download ZIP binary distribution from <a href="https://github.com/OPM/ResInsight/releases" title="release section on GitHub">https://github.com/OPM/ResInsight/releases</a></li>
 <li>Extract content from ZIP file</li>
 <li>Start ResInsight.exe</li>
 </ol>
 
-
-<div class="notices info" ><p>The binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see
+<div class="notices info" ><p>The binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see 
 <a href="/getting-started/download-and-install/buildinstructions/">Build Instructions</a>.</p>
 </div>
 
-
 <h3 id="octave-installation-optional">Octave Installation (optional)</h3>
-
 <ol>
 <li>Download <a href="ftp://ftp.gnu.org/gnu/octave/windows">Octave-4.0.0</a> and install it. (Newer versions will not work)</li>
 <li>Launch ResInsight.exe, open <strong>Edit-&gt;Preferences</strong>.</li>
-<li>On the <strong>Octave</strong> tab, enter the path to the Octave command line interpreter executable.<br />
+<li>On the <strong>Octave</strong> tab, enter the path to the Octave command line interpreter executable.<br>
 ( Usually <em><code>C:\Your\Path\To\Octave-x.x.x\bin\octave-cli.exe</code></em> )</li>
 </ol>
 
-
-<div class="notices info" ><p>A binary package of ResInsight will normally <b>not</b> work with other Octave versions than the one it is compiled with.</p>
+<div class="notices info" ><p>A binary package of ResInsight will normally <!-- raw HTML omitted -->not<!-- raw HTML omitted --> work with other Octave versions than the one it is compiled with.</p>
 </div>
 
 
-
-<div class="notices info" ><p>You <b>have</b> to point to the <b>cli</b> binary in the windows octave installation. The <code>octave.exe</code> will not work as it is launching the octave GUI.</p>
+<div class="notices info" ><p>You <!-- raw HTML omitted -->have<!-- raw HTML omitted --> to point to the <!-- raw HTML omitted -->cli<!-- raw HTML omitted --> binary in the windows octave installation. The <!-- raw HTML omitted -->octave.exe<!-- raw HTML omitted --> will not work as it is launching the octave GUI.</p>
 </div>
 
 
@@ -2026,6 +2050,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2036,6 +2073,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3178,20 +3218,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/index.html b/getting-started/index.html
index 750e90d5aa..41971a1582 100644
--- a/getting-started/index.html
+++ b/getting-started/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Getting Started :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,11 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents">
+  <ul>
+    <li><a href="#resinsight-documentation-overview">ResInsight Documentation Overview</a></li>
+  </ul>
+</nav>
     </div>
 </div>
 
@@ -1786,10 +1824,15 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/getting-started/usingResinsight.png" alt="Using ResInsight" /></p>
-
-<p>ResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations.
+	<p><img src="/images/getting-started/usingResinsight.png" alt="Using ResInsight"></p>
+<p>ResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations. 
 This chapter provides an overview of its functionality and installation.</p>
+<h2 id="resinsight-documentation-overview">ResInsight Documentation Overview</h2>
+<ul>
+<li><a href="https://resinsight.org/">resinsight.org</a> - Documentation for latest stable release</li>
+<li><a href="https://api.resinsight.org/">api.resinsight.org</a> - Documentation of Python API</li>
+<li><a href="http://beta.resinsight.org">beta.resinsight.org</a> - Latest documentation (not yet released)</li>
+</ul>
 
 
 
@@ -1968,6 +2011,19 @@ This chapter provides an overview of its functionality and installation.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1978,6 +2034,9 @@ This chapter provides an overview of its functionality and installation.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3120,20 +3179,20 @@ This chapter provides an overview of its functionality and installation.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/index.xml b/getting-started/index.xml
index 0e1ff642d9..204e32d3e4 100644
--- a/getting-started/index.xml
+++ b/getting-started/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Getting Started on ResInsight</title>
@@ -28,7 +28,7 @@ Docking Windows Each of the main windows has a central area and several docking
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_04/</guid>
       <description>ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.
-Grid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot.</description>
+Grid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.</description>
     </item>
     
     <item>
@@ -39,7 +39,7 @@ Grid Cross Plots ResInsight supports the creation of cross plots of two results
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_08/</guid>
       <description>ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.
 Python scripting Basic example on how to update views from Python
-import rips # Connect to ResInsight instance resInsight = rips.Instance.find() # Check if connection worked if resInsight is not None: # Get a list of all cases cases = resInsight.</description>
+import rips# Connect to ResInsight instanceresInsight = rips.Instance.find()# Check if connection workedif resInsight is not None:# Get a list of all casescases = resInsight.</description>
     </item>
     
     <item>
@@ -49,7 +49,7 @@ import rips # Connect to ResInsight instance resInsight = rips.Instance.find() #
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_12/</guid>
       <description>ResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12 is a major update bringing a range of significant new and enhanced features. Some of the most important extensions are listed below.
-Comparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more.</description>
+Comparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view.</description>
     </item>
     
     <item>
@@ -83,34 +83,11 @@ Well Path Creation ResInsight lets the user create new/custom well paths by clic
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/getting-started/modelnavigation/</guid>
-      <description>ResInsight comes with four navigation modes. The active mode can be selected in the Preferences dialog.
+      <description>ResInsight comes with four navigation modes. The active mode can be selected in the [Preferences dialog] (/misc/preferences/).
 Note that changing the navigation mode applies to the currently active view only, and views created after the change.
 These abbreviations are used in the tables below:
    Abbreviation Meaning     LMB Press the left mouse button   MMB Press the middle mouse button or scroll wheel button   RMB Press the right mouse button    The following applies to all navigation modes:</description>
     </item>
     
-    <item>
-      <title>Release Notification Subscription</title>
-      <link>https://resinsight.org/getting-started/other/releasenotification/</link>
-      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
-      <guid>https://resinsight.org/getting-started/other/releasenotification/</guid>
-      <description>LinkedIn Feel free to join ResInsight on LinkedIn
-Newsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.
-Subscribe</description>
-    </item>
-    
-    <item>
-      <title>Testimonials</title>
-      <link>https://resinsight.org/getting-started/other/testimonials/</link>
-      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-      
-      <guid>https://resinsight.org/getting-started/other/testimonials/</guid>
-      <description>“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”
-David Baxendale
-Senior Petroleum Engineering Advisor, RPS Energy
-&amp;ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&amp;rdquo;</description>
-    </item>
-    
   </channel>
 </rss>
\ No newline at end of file
diff --git a/getting-started/modelnavigation/index.html b/getting-started/modelnavigation/index.html
index eb1365675e..434f99aad9 100644
--- a/getting-started/modelnavigation/index.html
+++ b/getting-started/modelnavigation/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Model Navigation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,21 +1802,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#rms-navigation-mode">RMS navigation mode</a></li>
-<li><a href="#cad-navigation-mode">CAD navigation mode</a></li>
-<li><a href="#geoquest-navigation-mode">GeoQuest navigation mode</a></li>
-<li><a href="#ceetron-navigation-mode">Ceetron navigation mode</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1807,14 +1833,9 @@ if (!doNotTrack) {
 
 
 
-
-
-<p>ResInsight comes with four navigation modes. The active mode can be selected in the <a href="/misc/preferences/">Preferences dialog</a>.</p>
-
+<p>ResInsight comes with four navigation modes. The active mode can be selected in the [Preferences dialog] (/misc/preferences/).</p>
 <p>Note that changing the navigation mode applies to the currently active view only, and views created after the change.</p>
-
 <p>These abbreviations are used in the tables below:</p>
-
 <table>
 <thead>
 <tr>
@@ -1822,27 +1843,22 @@ if (!doNotTrack) {
 <th>Meaning</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>LMB</td>
 <td>Press the left mouse button</td>
 </tr>
-
 <tr>
 <td>MMB</td>
 <td>Press the middle mouse button or scroll wheel button</td>
 </tr>
-
 <tr>
 <td>RMB</td>
 <td>Press the right mouse button</td>
 </tr>
 </tbody>
 </table>
-
 <p>The following applies to all navigation modes:</p>
-
 <table>
 <thead>
 <tr>
@@ -1850,22 +1866,18 @@ if (!doNotTrack) {
 <th>Action</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>RMB single click</td>
 <td>Right-click menu (context menu)</td>
 </tr>
-
 <tr>
 <td>LMB single click</td>
 <td>Update status bar and <strong>Result Info</strong></td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="rms-navigation-mode">RMS navigation mode</h4>
-
 <table>
 <thead>
 <tr>
@@ -1873,32 +1885,26 @@ if (!doNotTrack) {
 <th>Action</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>LMB + drag</td>
 <td>Zoom model</td>
 </tr>
-
 <tr>
 <td>MMB + drag</td>
 <td>Rotate model</td>
 </tr>
-
 <tr>
 <td>Scroll wheel</td>
 <td>Zoom to mouse pointer location</td>
 </tr>
-
 <tr>
 <td>RMB + drag</td>
 <td>Pan model</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="cad-navigation-mode">CAD navigation mode</h4>
-
 <table>
 <thead>
 <tr>
@@ -1906,32 +1912,26 @@ if (!doNotTrack) {
 <th>Action</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>LMB + drag</td>
 <td>Pan model</td>
 </tr>
-
 <tr>
 <td>MMB + drag</td>
 <td>Rotate model</td>
 </tr>
-
 <tr>
 <td>MMB + Shift</td>
 <td>Pan model</td>
 </tr>
-
 <tr>
 <td>Scroll wheel</td>
 <td>Zoom to mouse pointer location</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="geoquest-navigation-mode">GeoQuest navigation mode</h4>
-
 <table>
 <thead>
 <tr>
@@ -1939,27 +1939,22 @@ if (!doNotTrack) {
 <th>Action</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>LMB + drag</td>
 <td>Rotate model</td>
 </tr>
-
 <tr>
 <td>MMB + drag</td>
 <td>Pan model</td>
 </tr>
-
 <tr>
 <td>Scroll wheel</td>
 <td>Zoom to mouse pointer location</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="ceetron-navigation-mode">Ceetron navigation mode</h4>
-
 <table>
 <thead>
 <tr>
@@ -1967,23 +1962,19 @@ if (!doNotTrack) {
 <th>Action</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>LMB + drag</td>
 <td>Pan model</td>
 </tr>
-
 <tr>
 <td>MMB + drag</td>
 <td>Zoom to mouse pointer location</td>
 </tr>
-
 <tr>
 <td>Scroll wheel</td>
 <td>Zoom to mouse pointer location</td>
 </tr>
-
 <tr>
 <td>RMB + drag</td>
 <td>Rotate model</td>
@@ -2167,6 +2158,22 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                        
+                        
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2177,14 +2184,14 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
                 
                     
-                        
-                        
-                    
                 
                 
 
@@ -3312,7 +3319,7 @@ if (!doNotTrack) {
 			<a class="nav nav-prev" href="/getting-started/download-and-install/buildinstructions/" title="Build Instructions"> <i class="fa fa-chevron-left"></i></a>
 		
 		
-			<a class="nav nav-next" href="/3d-main-window/" title="3D Main Window" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
+			<a class="nav nav-next" href="/getting-started/other/" title="Other" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
 		
 	
     </div>
@@ -3322,20 +3329,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/other/index.html b/getting-started/other/index.html
new file mode 100644
index 0000000000..6b759af304
--- /dev/null
+++ b/getting-started/other/index.html
@@ -0,0 +1,3199 @@
+<!DOCTYPE html>
+<html lang="en" class="js csstransforms3d">
+  <head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <meta name="generator" content="Hugo 0.65.3" />
+    <meta name="description" content="">
+
+
+    <link rel="icon" href="/images/favicon.png" type="image/png">
+
+    <title>Other :: ResInsight</title>
+
+    
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
+    
+
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
+
+    <style>
+      :root #header + #content > #left > #rlblock_left{
+          display:none !important;
+      }
+      
+    </style>
+    
+  </head>
+  <body class="" data-url="/getting-started/other/">
+    <nav id="sidebar" class="">
+
+
+
+  <div id="header-wrapper">
+    <div id="header">
+      <a id="logo" href="https://resinsight.org/">
+  <img src="https://resinsight.org//images/ResInsightCroppedIconPicture.png">
+</a>
+
+    </div>
+    
+        <div class="searchbox">
+    <label for="searchbox"><i class="fas fa-search"></i></label>
+    <form action="/search/" method="GET" id="search-form">
+      <input type="search" name="q" id="searchbox" placeholder="Search">
+    </form>
+    <span data-search-clear=""><i class="fas fa-times"></i></span>
+</div>
+
+
+    
+  </div>
+
+    <div class="highlightable">
+    <ul class="topics">
+
+        
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/" title="Getting Started" class="dd-item 
+        parent
+        
+        
+        ">
+      <a href="/getting-started/">
+          Getting Started
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+            
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/getting-started/overview/" title="Overview" class="dd-item ">
+        <a href="/getting-started/overview/">
+        Overview
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/download-and-install/" title="Download and Install" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/download-and-install/">
+          Download and Install
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/getting-started/download-and-install/linux-installation/" title="Linux Installation" class="dd-item ">
+        <a href="/getting-started/download-and-install/linux-installation/">
+        Linux Installation
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/getting-started/download-and-install/windows-installation/" title="Windows Installation" class="dd-item ">
+        <a href="/getting-started/download-and-install/windows-installation/">
+        Windows Installation
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/getting-started/download-and-install/buildinstructions/" title="Build Instructions" class="dd-item ">
+        <a href="/getting-started/download-and-install/buildinstructions/">
+        Build Instructions
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+             
+            
+          
+             
+            
+          
+             
+            
+          
+             
+            
+          
+             
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/getting-started/modelnavigation/" title="Model Navigation" class="dd-item ">
+        <a href="/getting-started/modelnavigation/">
+        Model Navigation
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        parent
+        active
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+             
+            
+          
+             
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/3d-main-window/" title="3D Main Window" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/3d-main-window/">
+          3D Main Window
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/3dviews/" title="3D Views" class="dd-item ">
+        <a href="/3d-main-window/3dviews/">
+        3D Views
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/cellresults/" title="Cell Results" class="dd-item ">
+        <a href="/3d-main-window/cellresults/">
+        Cell Results
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/resultcolorlegend/" title="Result Color Legend" class="dd-item ">
+        <a href="/3d-main-window/resultcolorlegend/">
+        Result Color Legend
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/comparisonview/" title="Comparison View" class="dd-item ">
+        <a href="/3d-main-window/comparisonview/">
+        Comparison View
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/contourmaps/" title="Contour Maps" class="dd-item ">
+        <a href="/3d-main-window/contourmaps/">
+        Contour Maps
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/tensors/" title="Tensor Results" class="dd-item ">
+        <a href="/3d-main-window/tensors/">
+        Tensor Results
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/resultinspection/" title="Result Inspection" class="dd-item ">
+        <a href="/3d-main-window/resultinspection/">
+        Result Inspection
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/filters/" title="Cell Filters" class="dd-item ">
+        <a href="/3d-main-window/filters/">
+        Cell Filters
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/intersections/" title="Intersections" class="dd-item ">
+        <a href="/3d-main-window/intersections/">
+        Intersections
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/faults/" title="Faults" class="dd-item ">
+        <a href="/3d-main-window/faults/">
+        Faults
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/formations/" title=" Zonations/Formations" class="dd-item ">
+        <a href="/3d-main-window/formations/">
+         Zonations/Formations
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/gridstatisticsdialog/" title="Grid Statistics Dialog" class="dd-item ">
+        <a href="/3d-main-window/gridstatisticsdialog/">
+        Grid Statistics Dialog
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/casegroupsandstatistics/" title="Grid Case Groups and Statistics" class="dd-item ">
+        <a href="/3d-main-window/casegroupsandstatistics/">
+        Grid Case Groups and Statistics
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/linkedviews/" title="Linked Views" class="dd-item ">
+        <a href="/3d-main-window/linkedviews/">
+        Linked Views
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/measurement/" title="Measurement" class="dd-item ">
+        <a href="/3d-main-window/measurement/">
+        Measurement
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/annotations/" title="Annotations" class="dd-item ">
+        <a href="/3d-main-window/annotations/">
+        Annotations
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/3d-main-window/derivedresults/" title="Derived Results" class="dd-item ">
+        <a href="/3d-main-window/derivedresults/">
+        Derived Results
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/plot-window/" title="Plot Main Window" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/plot-window/">
+          Plot Main Window
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/summaryplots/" title="Summary Plots" class="dd-item ">
+        <a href="/plot-window/summaryplots/">
+        Summary Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/summarysourcestepping/" title="Summary Plot Source Stepping" class="dd-item ">
+        <a href="/plot-window/summarysourcestepping/">
+        Summary Plot Source Stepping
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/summaryploteditor/" title="Summary Plot Editor" class="dd-item ">
+        <a href="/plot-window/summaryploteditor/">
+        Summary Plot Editor
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/summarycrossplots/" title="Summary Cross Plot" class="dd-item ">
+        <a href="/plot-window/summarycrossplots/">
+        Summary Cross Plot
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/summaryplottemplate/" title="Summary Plot Template" class="dd-item ">
+        <a href="/plot-window/summaryplottemplate/">
+        Summary Plot Template
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/ensembleplotting/" title="Ensemble Plotting" class="dd-item ">
+        <a href="/plot-window/ensembleplotting/">
+        Ensemble Plotting
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/curvecalculator/" title="Curve Calculator" class="dd-item ">
+        <a href="/plot-window/curvecalculator/">
+        Curve Calculator
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/welllogsandplots/" title="Well Log Plots" class="dd-item ">
+        <a href="/plot-window/welllogsandplots/">
+        Well Log Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/wellborestabilityplots/" title="Well Bore Stability Plots" class="dd-item ">
+        <a href="/plot-window/wellborestabilityplots/">
+        Well Bore Stability Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/rftplot/" title="RFT Plot" class="dd-item ">
+        <a href="/plot-window/rftplot/">
+        RFT Plot
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/ensemblerftplot/" title="Ensemble RFT Plot" class="dd-item ">
+        <a href="/plot-window/ensemblerftplot/">
+        Ensemble RFT Plot
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/pltplot/" title="PLT Plot" class="dd-item ">
+        <a href="/plot-window/pltplot/">
+        PLT Plot
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/flowdiagnosticsplots/" title="Flow Diagnostics Plots" class="dd-item ">
+        <a href="/plot-window/flowdiagnosticsplots/">
+        Flow Diagnostics Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/gridcrossplots/" title="Grid Cross Plots" class="dd-item ">
+        <a href="/plot-window/gridcrossplots/">
+        Grid Cross Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/plot-window/saturationpressureplots/" title="Saturation Pressure Plots" class="dd-item ">
+        <a href="/plot-window/saturationpressureplots/">
+        Saturation Pressure Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/wells-and-completions/" title="Wells and Completions" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/wells-and-completions/">
+          Wells and Completions
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/simulationwells/" title="Simulation Wells" class="dd-item ">
+        <a href="/wells-and-completions/simulationwells/">
+        Simulation Wells
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/wellpaths/" title="Well Paths" class="dd-item ">
+        <a href="/wells-and-completions/wellpaths/">
+        Well Paths
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/createnewwellpaths/" title="Create Well Paths" class="dd-item ">
+        <a href="/wells-and-completions/createnewwellpaths/">
+        Create Well Paths
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/3dwelllogcurves/" title="3D Well Log Plots" class="dd-item ">
+        <a href="/wells-and-completions/3dwelllogcurves/">
+        3D Well Log Plots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/completions/" title="Completions" class="dd-item ">
+        <a href="/wells-and-completions/completions/">
+        Completions
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/wells-and-completions/completionslgr/" title="Completions LGR" class="dd-item ">
+        <a href="/wells-and-completions/completionslgr/">
+        Completions LGR
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/import/" title="Import" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/import/">
+          Import
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/eclipsecases/" title="Eclipse Cases" class="dd-item ">
+        <a href="/import/eclipsecases/">
+        Eclipse Cases
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/lasfile/" title="Log ASCII Standard File" class="dd-item ">
+        <a href="/import/lasfile/">
+        Log ASCII Standard File
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/geomechanicaldata/" title="Geomechanical Data" class="dd-item ">
+        <a href="/import/geomechanicaldata/">
+        Geomechanical Data
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/soursimrlresults/" title="SourSimRL Results" class="dd-item ">
+        <a href="/import/soursimrlresults/">
+        SourSimRL Results
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/elementpropertytable/" title="Element Property Table" class="dd-item ">
+        <a href="/import/elementpropertytable/">
+        Element Property Table
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/observeddata/" title="Observed Time History Data" class="dd-item ">
+        <a href="/import/observeddata/">
+        Observed Time History Data
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/import/pasteexceltimedata/" title="Paste Excel Time History Data" class="dd-item ">
+        <a href="/import/pasteexceltimedata/">
+        Paste Excel Time History Data
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/export/" title="Export" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/export/">
+          Export
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/snapshots/" title="Snapshots" class="dd-item ">
+        <a href="/export/snapshots/">
+        Snapshots
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/eclipseproperties/" title="Eclipse Properties" class="dd-item ">
+        <a href="/export/eclipseproperties/">
+        Eclipse Properties
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/fluxnummultnum/" title="FLUXNUM/MULTNUM" class="dd-item ">
+        <a href="/export/fluxnummultnum/">
+        FLUXNUM/MULTNUM
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/completionexport/" title="Completions" class="dd-item ">
+        <a href="/export/completionexport/">
+        Completions
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/exportwellpaths/" title="Well Paths" class="dd-item ">
+        <a href="/export/exportwellpaths/">
+        Well Paths
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/sectormodel/" title="Sector Model" class="dd-item ">
+        <a href="/export/sectormodel/">
+        Sector Model
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/export/contourmapexport/" title="Contour Map Export" class="dd-item ">
+        <a href="/export/contourmapexport/">
+        Contour Map Export
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/scripting/" title="Scripting" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/scripting/">
+          Scripting
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/commandlineinterface/" title="Command Line Interface" class="dd-item ">
+        <a href="/scripting/commandlineinterface/">
+        Command Line Interface
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/commandfile/" title="Command File" class="dd-item ">
+        <a href="/scripting/commandfile/">
+        Command File
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/pythonexamples/" title="Python Examples" class="dd-item ">
+        <a href="/scripting/pythonexamples/">
+        Python Examples
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/pythonrips/" title="Python API - rips" class="dd-item ">
+        <a href="/scripting/pythonrips/">
+        Python API - rips
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/pythonconfiguration/" title="Python Configuration" class="dd-item ">
+        <a href="/scripting/pythonconfiguration/">
+        Python Configuration
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/octaveinterface/" title="Octave Interface" class="dd-item ">
+        <a href="/scripting/octaveinterface/">
+        Octave Interface
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/scripting/octaveinterfacereference/" title="Octave Interface Reference" class="dd-item ">
+        <a href="/scripting/octaveinterfacereference/">
+        Octave Interface Reference
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+          
+
+
+ 
+  
+    
+    <li data-nav-id="/misc/" title="Miscellaneous" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/misc/">
+          Miscellaneous
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/misc/preferences/" title="Preferences" class="dd-item ">
+        <a href="/misc/preferences/">
+        Preferences
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/misc/memorymanagement/" title="Memory Management" class="dd-item ">
+        <a href="/misc/memorymanagement/">
+        Memory Management
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/misc/keyboardshortcuts/" title="Keyboard Shortcuts" class="dd-item ">
+        <a href="/misc/keyboardshortcuts/">
+        Keyboard Shortcuts
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+            
+            
+
+
+ 
+  
+    
+      <li data-nav-id="/misc/regressiontestsystem/" title="Regression Test System" class="dd-item ">
+        <a href="/misc/regressiontestsystem/">
+        Regression Test System
+        
+        </a>
+    </li>
+     
+  
+ 
+
+            
+          
+        
+        </ul>
+              
+    </li>
+  
+ 
+
+          
+         
+    </ul>
+
+    
+    
+      <section id="shortcuts">
+        <h3></h3>
+        <ul>
+          
+              <li> 
+                  <a class="padding" href="https://resinsight.org/about"><i class='fas fa-info-circle'></i> About</a>
+              </li>
+          
+              <li> 
+                  <a class="padding" href="https://resinsight.org/support"><i class='far fa-question-circle'></i> Support</a>
+              </li>
+          
+              <li> 
+                  <a class="padding" href="https://resinsight.org/getting-started/download-and-install"><i class='fas fa-download'></i> Download and Install</a>
+              </li>
+          
+        </ul>
+      </section>
+    
+
+    
+    <section id="footer">
+      <a href="https://www.ceetronsolutions.com"><img src='https://resinsight.org//images/CeeSolLogoSmallForDarkBackground.png' style='width: 140px; '></a><br>
+
+ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetron Solutions</a>
+<p>in collaboration with</p>
+<a href="https://www.equinor.com">Equinor ASA</a>
+
+
+<script type="application/javascript">
+var doNotTrack = false;
+if (!doNotTrack) {
+	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+	(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+	m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+	})(window,document,'script','https://www.google-analytics.com/analytics.js','ga');
+	ga('create', 'UA-79509181-1', 'auto');
+	
+	ga('send', 'pageview');
+}
+</script>
+
+    </section>
+  </div>
+</nav>
+
+
+
+
+
+        <section id="body">
+        <div id="overlay"></div>
+        <div class="padding highlightable">
+              
+              <div>
+                <div id="top-bar">
+                
+                
+                <div id="breadcrumbs" itemscope="" itemtype="http://data-vocabulary.org/Breadcrumb">
+                    <span id="sidebar-toggle-span">
+                        <a href="#" id="sidebar-toggle" data-sidebar-toggle="">
+                          <i class="fas fa-bars"></i>
+                        </a>
+                    </span>
+                  
+                  <span id="toc-menu"><i class="fas fa-list-alt"></i></span>
+                  
+                  <span class="links">
+                 
+                 
+                    
+          
+          
+            
+            
+          
+          
+            
+            
+          
+          
+            <a href='/'>ResInsight</a> > <a href='/getting-started/'>Getting Started</a> > Other
+          
+         
+          
+         
+          
+        
+                 
+                  </span>
+                </div>
+                
+                    <div class="progress">
+    <div class="wrapper">
+<nav id="TableOfContents"></nav>
+    </div>
+</div>
+
+                
+              </div>
+            </div>
+            
+        <div id="head-tags">
+        
+        </div>
+        
+        <div id="body-inner">
+          
+            <h1>
+              
+              Other
+            </h1>
+          
+
+        
+
+
+
+
+	
+
+
+
+
+<footer class=" footline" >
+	
+</footer>
+
+        
+        </div> 
+        
+
+      </div>
+
+    <div id="navigation">
+        
+        
+        
+        
+            
+            
+                
+                    
+                    
+                
+                
+
+                    
+                    
+                        
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                    
+                
+                
+
+                    
+                    
+                        
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                        
+                        
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+        
+                    
+                        
+            
+            
+        
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                        
+                        
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+                        
+            
+            
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+            
+        
+                    
+            
+        
+                    
+            
+        
+        
+        
+
+
+	 
+	 
+		
+			<a class="nav nav-prev" href="/getting-started/modelnavigation/" title="Model Navigation"> <i class="fa fa-chevron-left"></i></a>
+		
+		
+			<a class="nav nav-next" href="/3d-main-window/" title="3D Main Window" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
+		
+	
+    </div>
+
+    </section>
+    
+    <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
+      <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
+    </div>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
+    <script>hljs.initHighlightingOnLoad();</script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
+
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
+    <script>
+        mermaid.initialize({ startOnLoad: true });
+    </script>
+    
+
+  </body>
+</html>
diff --git a/getting-started/other/index.xml b/getting-started/other/index.xml
new file mode 100644
index 0000000000..02e87b078b
--- /dev/null
+++ b/getting-started/other/index.xml
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Other on ResInsight</title>
+    <link>https://resinsight.org/getting-started/other/</link>
+    <description>Recent content in Other on ResInsight</description>
+    <generator>Hugo -- gohugo.io</generator>
+    <language>en-us</language>
+    
+	<atom:link href="https://resinsight.org/getting-started/other/index.xml" rel="self" type="application/rss+xml" />
+    
+    
+    <item>
+      <title>Release Notification Subscription</title>
+      <link>https://resinsight.org/getting-started/other/releasenotification/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://resinsight.org/getting-started/other/releasenotification/</guid>
+      <description>LinkedIn Feel free to join ResInsight on LinkedIn
+Newsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.</description>
+    </item>
+    
+    <item>
+      <title>Testimonials</title>
+      <link>https://resinsight.org/getting-started/other/testimonials/</link>
+      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+      
+      <guid>https://resinsight.org/getting-started/other/testimonials/</guid>
+      <description>“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”
+David BaxendaleSenior Petroleum Engineering Advisor, RPS Energy
+&amp;ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&amp;quot;
+Tor Harald SandveResearcher, International Research Institute of Stavanger (IRIS)</description>
+    </item>
+    
+  </channel>
+</rss>
\ No newline at end of file
diff --git a/getting-started/other/releasenotification/index.html b/getting-started/other/releasenotification/index.html
index 361d47e3a7..30d7dbdc61 100644
--- a/getting-started/other/releasenotification/index.html
+++ b/getting-started/other/releasenotification/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Release Notification Subscription :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        parent
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1754,7 +1788,13 @@ if (!doNotTrack) {
             
           
           
-            <a href='/'>ResInsight</a> > <a href='/getting-started/'>Getting Started</a> > Release Notification Subscription
+            
+            
+          
+          
+            <a href='/'>ResInsight</a> > <a href='/getting-started/'>Getting Started</a> > <a href='/getting-started/other/'>Other</a> > Release Notification Subscription
+          
+         
           
          
           
@@ -1768,16 +1808,14 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#linkedin">LinkedIn</a></li>
-<li><a href="#newsletter">Newsletter</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#linkedin">LinkedIn</a></li>
+        <li><a href="#newsletter">Newsletter</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1802,18 +1840,12 @@ if (!doNotTrack) {
 
 
 
-
-
 <h3 id="linkedin">LinkedIn</h3>
-
 <p>Feel free to join <a href="https://www.linkedin.com/groups/12167660/">ResInsight on LinkedIn</a></p>
-
 <h3 id="newsletter">Newsletter</h3>
-
-<p>By subscribing to the <strong>Release Notification</strong> you will get notified when new releases are available.
+<p>By subscribing to the <strong>Release Notification</strong> you will get notified when new releases are available. 
 Please use the button below to send a request for subscription mail.</p>
-
-<p><a href="mailto:info@ceetronsolutions.com?subject=ResInsight Release Notification subscription&body=Hi ResInsight administrator, I would like to subscribe to the ResInsight release notifications.">Subscribe</a></p>
+<p><!-- raw HTML omitted -->Subscribe<!-- raw HTML omitted --></p>
 
 
 <footer class=" footline" >
@@ -1990,6 +2022,20 @@ Please use the button below to send a request for subscription mail.</p>
                         
             
             
+                
+                    
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2000,11 +2046,17 @@ Please use the button below to send a request for subscription mail.</p>
             
         
                     
+            
+        
+                    
                         
             
             
                 
                     
+                        
+                        
+                    
                 
                 
 
@@ -3129,10 +3181,10 @@ Please use the button below to send a request for subscription mail.</p>
 	 
 	 
 		
-			<a class="nav nav-prev" href="/" title="ResInsight"> <i class="fa fa-chevron-left"></i></a>
+			<a class="nav nav-prev" href="/getting-started/modelnavigation/" title="Model Navigation"> <i class="fa fa-chevron-left"></i></a>
 		
 		
-			<a class="nav nav-next" href="/getting-started/overview/" title="Overview" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
+			<a class="nav nav-next" href="/3d-main-window/" title="3D Main Window" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
 		
 	
     </div>
@@ -3142,20 +3194,20 @@ Please use the button below to send a request for subscription mail.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/other/testimonials/index.html b/getting-started/other/testimonials/index.html
index 83c3bf1a4f..3a6d9f134b 100644
--- a/getting-started/other/testimonials/index.html
+++ b/getting-started/other/testimonials/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Testimonials :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        parent
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1754,7 +1788,13 @@ if (!doNotTrack) {
             
           
           
-            <a href='/'>ResInsight</a> > <a href='/getting-started/'>Getting Started</a> > Testimonials
+            
+            
+          
+          
+            <a href='/'>ResInsight</a> > <a href='/getting-started/'>Getting Started</a> > <a href='/getting-started/other/'>Other</a> > Testimonials
+          
+         
           
          
           
@@ -1767,7 +1807,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1792,16 +1832,12 @@ if (!doNotTrack) {
 
 
 <p><em>“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”</em></p>
-
-<p><strong>David Baxendale<br>
+<p><strong>David Baxendale<!-- raw HTML omitted -->
 Senior Petroleum Engineering Advisor, RPS Energy</strong></p>
-
-<p><em>&ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&rdquo;</em></p>
-
-<p><strong>Tor Harald Sandve<br>
+<p><em>&ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&quot;</em></p>
+<p><strong>Tor Harald Sandve<!-- raw HTML omitted -->
 Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
 
-
 <div class="notices note" ><p>Equinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.</p>
 </div>
 
@@ -1981,6 +2017,20 @@ Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
                         
             
             
+                
+                    
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1991,11 +2041,17 @@ Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
             
         
                     
+            
+        
+                    
                         
             
             
                 
                     
+                        
+                        
+                    
                 
                 
 
@@ -3120,10 +3176,10 @@ Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
 	 
 	 
 		
-			<a class="nav nav-prev" href="/" title="ResInsight"> <i class="fa fa-chevron-left"></i></a>
+			<a class="nav nav-prev" href="/getting-started/modelnavigation/" title="Model Navigation"> <i class="fa fa-chevron-left"></i></a>
 		
 		
-			<a class="nav nav-next" href="/getting-started/overview/" title="Overview" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
+			<a class="nav nav-next" href="/3d-main-window/" title="3D Main Window" style="margin-right: 0px;"><i class="fa fa-chevron-right"></i></a>
 		
 	
     </div>
@@ -3133,20 +3189,20 @@ Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/overview/index.html b/getting-started/overview/index.html
index fde8e629f7..3beac4289f 100644
--- a/getting-started/overview/index.html
+++ b/getting-started/overview/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Overview :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,33 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#user-interface">User Interface</a>
-<ul>
-<li><a href="#3d-main-window">3D Main Window</a></li>
-<li><a href="#plot-main-window">Plot Main Window</a></li>
-<li><a href="#switching-between-the-two-main-windows">Switching Between the Two Main Windows</a></li>
-<li><a href="#docking-windows">Docking Windows</a></li>
-</ul></li>
-<li><a href="#toolbars">Toolbars</a>
-<ul>
-<li><a href="#managing-3d-views-and-plot-windows">Managing 3D Views and Plot Windows</a></li>
-<li><a href="#editing-3d-views-and-plot-windows-content">Editing 3D Views and Plot Windows Content</a></li>
-</ul></li>
-<li><a href="#cases-and-their-types">Cases and Their Types</a>
-<ul>
-<li><a href="#eclipse-cases">Eclipse Cases</a></li>
-<li><a href="#geomechanical-cases">Geomechanical cases</a></li>
-<li><a href="#grid-case-groups">Grid Case Groups</a></li>
-</ul></li>
-<li><a href="#the-project-file-and-the-cache-directory">The Project File and the Cache Directory</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#user-interface">User Interface</a></li>
+        <li><a href="#toolbars">Toolbars</a></li>
+        <li><a href="#cases-and-their-types">Cases and Their Types</a></li>
+        <li><a href="#the-project-file-and-the-cache-directory">The Project File and the Cache Directory</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1819,33 +1836,20 @@ if (!doNotTrack) {
 
 
 
-
-
 <h3 id="user-interface">User Interface</h3>
-
 <p>ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.</p>
-
 <h4 id="3d-main-window">3D Main Window</h4>
-
-<p><img src="/images/getting-started/ResInsightUIMediumSize.png" alt="ResInsight User Interface" /></p>
-
+<p><img src="/images/getting-started/ResInsightUIMediumSize.png" alt="ResInsight User Interface"></p>
 <h4 id="plot-main-window">Plot Main Window</h4>
-
-<p><img src="/images/getting-started/ResInsightMainPlotMediumSize.png" alt="ResInsight User Interface" /></p>
-
+<p><img src="/images/getting-started/ResInsightMainPlotMediumSize.png" alt="ResInsight User Interface"></p>
 <h4 id="switching-between-the-two-main-windows">Switching Between the Two Main Windows</h4>
-
 <p>The two main windows has a toolbar button each, that directly opens and raises the other window. <img src="https://resinsight.org/images/getting-started/3DWindow24x24.png" style="display:inline; vertical-align:middle; margin:0">
 <img src="https://resinsight.org/images/getting-started/PlotWindow24x24.png" style="display:inline; vertical-align:middle; margin:0">
 </p>
-
 <p>Each of the windows can also be closed freely, but if both are closed, ResInsight exits.</p>
-
 <h4 id="docking-windows">Docking Windows</h4>
-
-<p>Each of the main windows has a central area and several docking windows surrounding it. The different docking
+<p>Each of the main windows has a central area and several docking windows surrounding it. The different docking 
 windows can be managed from the <strong>Windows</strong> menu or directly using the local menu bar of the docking window.</p>
-
 <ul>
 <li><strong>Project Tree</strong> &ndash; contains all application objects in a tree structure.</li>
 <li><strong>Property Editor</strong> &ndash; displays all properties for the selected object in the <strong>Project Tree</strong></li>
@@ -1854,111 +1858,74 @@ windows can be managed from the <strong>Windows</strong> menu or directly using
 <li><strong>Result Plot</strong> &ndash; displays curves based on result values for the selected cells in the 3D scene</li>
 <li><strong>Messages</strong> &ndash; displays occasional info and warnings related to operations executed.</li>
 </ul>
-
 <p>Result Info and Result Plot is described in detail in <a href="/3d-main-window/resultinspection/"> Result Inspection </a></p>
 
-
-<div class="notices note" ><p><b>Use several Project Trees and Property Editors: </b>
-If you want to pin the property editor for a certain object, you can add
-a new Project Tree and Property Editor by using the command <b>Windows-&gt;New Project and Property View</b>.</p>
+<div class="notices note" ><p><!-- raw HTML omitted -->Use several Project Trees and Property Editors: <!-- raw HTML omitted -->
+If you want to pin the property editor for a certain object, you can add 
+a new Project Tree and Property Editor by using the command <!-- raw HTML omitted -->Windows-&gt;New Project and Property View<!-- raw HTML omitted -->.</p>
 </div>
 
-
 <h3 id="toolbars">Toolbars</h3>
-
 <p>A selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.</p>
-
 <h4 id="managing-3d-views-and-plot-windows">Managing 3D Views and Plot Windows</h4>
-
 <p>In the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.</p>
-
 <p>Standard window management for applying minimized, normal and maximized state is available in the upper right corner.</p>
-
-<p><img src="/images/getting-started/RestoreDown.PNG" alt="Restore Down" /></p>
-
+<p><img src="/images/getting-started/RestoreDown.PNG" alt="Restore Down"></p>
 <p>Commands to arrange the windows in the standard ways are available from the <strong>Windows</strong> menu</p>
-
 <ul>
 <li><strong>Tile Windows</strong> &ndash; distribute all open view windows to fill available view widget space
-
 <ul>
 <li>The order of the tiled windows are determined by the window positions and the type of view at the time of running the tile command. The leftmost window are tiled first, then the next leftmost and so on. Master views are tiled before slave views.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Cascade Windows</strong> &ndash; organize all open view windows slightly offset on top of each other</li>
 <li><strong>Close All Windows</strong> &ndash; close all open view windows</li>
 </ul>
-
 <h4 id="editing-3d-views-and-plot-windows-content">Editing 3D Views and Plot Windows Content</h4>
-
 <p>Most of the settings and features of ResInsight is accessible through the <strong>Project Tree</strong> and the <strong>Property Editor</strong>. Selecting an item in the <strong>Project Tree</strong> activates the corresponding Window, and shows the item properties in the <strong>Property Editor</strong> available for editing.</p>
-
 <p>Toggling a checkbox next to an item in the <strong>Project Tree</strong> will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. <img src="https://resinsight.org/images/getting-started/TreeViewToggle.png" style="display:inline; vertical-align:middle; margin:0">
 </p>
-
 <p>right-click menu commands are also available to do special operations on a selected set of items.</p>
-
 <p>How to interact and manipulate the 3D model is described in <a href="/getting-started/modelnavigation/">Model Navigation</a></p>
-
 <h3 id="cases-and-their-types">Cases and Their Types</h3>
-
 <p>A <em>Case</em> in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.</p>
-
 <h4 id="eclipse-cases">Eclipse Cases</h4>
-
-<p>The following Eclipse cases can be imported into ResInsight via the <strong>File-&gt;Import-&gt;Eclipse Cases</strong> menu,
+<p>The following Eclipse cases can be imported into ResInsight via the <strong>File-&gt;Import-&gt;Eclipse Cases</strong> menu, 
 see <a href="/import/eclipsecases/">Import Eclipse Cases</a>:</p>
-
 <p><strong>Result Case <img src="https://resinsight.org/images/getting-started/Case24x24.png" style="display:inline; vertical-align:middle; margin:0">
 </strong></p>
-
 <p>This is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.</p>
-
 <p><strong>Input Case <img src="https://resinsight.org/images/getting-started/EclipseInput24x24.png" style="display:inline; vertical-align:middle; margin:0">
 </strong></p>
-
 <p>This Case type is based on a <em><code>*.GRDECL</code></em> file, or a part of an Eclipse <em>Input</em> file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.
 Each of the Eclipse properties are listed as separate entities in the <strong>Project Tree</strong>, and can be renamed and exported.
 See <a href="/import/eclipsecases/"> Grid Import and Property Export </a></p>
-
 <p><strong>Statistics Case <img src="https://resinsight.org/images/getting-started/Histogram24x24.png" style="display:inline; vertical-align:middle; margin:0">
 </strong></p>
-
 <p>This is a Case type that belongs to a <em>Grid Case Group</em> and makes statistical calculations based on the source cases in the Grid Case Group. See <a href="/3d-main-window/casegroupsandstatistics/"> Grid Case Groups and Statistics </a>.</p>
-
 <p><strong>Summary Case <img src="https://resinsight.org/images/getting-started/SummaryCase24x24.png" style="display:inline; vertical-align:middle; margin:0">
 </strong></p>
-
 <p>This is the case type listed in the Plot Main Window, and represents an <em><code>*.SMSPEC</code></em> file. These Cases are available for Summary Plotting. See <a href="/plot-window/summaryplots/"> Summary Plots </a>.</p>
-
 <h4 id="geomechanical-cases">Geomechanical cases</h4>
-
 <p>There are only one type of geomechanical <img src="https://resinsight.org/images/getting-started/GeoMechCase24x24.png" style="display:inline; vertical-align:middle; margin:0">
 
- cases, namely the ABAQUS-odb case type.
+cases, namely the ABAQUS-odb case type. 
 When ResInsight is compiled with ABAQUS-odb support, <em><code>*.odb</code></em> files can be imported by selecting the menu item:
 <strong>File-&gt;Import-&gt;Geo Mechanical Cases-&gt; <img src="https://resinsight.org/images/getting-started/GeoMechCase24x24.png" style="display:inline; vertical-align:middle; margin:0">
  Import Geo Mechanical Model</strong>.</p>
-
 <p>The geomechanical cases are sorted into its own folder in the project tree named <strong>Geomechanical Models</strong> <img src="https://resinsight.org/images/getting-started/GeoMechCases24x24.png" style="display:inline; vertical-align:middle; margin:0">
  as opposed to the <strong>Grid Models</strong> folder where the Eclipse cases and <strong>Grid Case Groups</strong> resides.</p>
-
 <p>See <a href="/getting-started/download-and-install/buildinstructions/">Build Instructions</a> on how to compile ResInsight with odb-support.</p>
-
 <h4 id="grid-case-groups">Grid Case Groups</h4>
-
 <p>A <strong>Grid Case Group</strong>  <img src="https://resinsight.org/images/getting-started/GridCaseGroup24x24.png" style="display:inline; vertical-align:middle; margin:0">
  is a group of Eclipse <strong>Result Cases</strong> with identical grids, but generally different active cells, initial values and results. These cases are called <em>Source Cases</em>. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See <a href="/3d-main-window/casegroupsandstatistics/"> Grid Case Groups and Statistics </a>.</p>
-
 <h3 id="the-project-file-and-the-cache-directory">The Project File and the Cache Directory</h3>
-
 <p>ResInsight stores all the views and settings in a Project File with the extension: <em><code>*.rsp</code></em>.
 This file only contains <em>references</em> to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.</p>
-
 <p>Statistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named <em><code>&lt;ProjectFileName&gt;_cache</code></em> in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.</p>
 
-
-<div class="notices note" ><p>The <code>*.rsp</code> file is an XML file, and can be edited by any text editor.<br />
-</div></p>
+<div class="notices note" ><p>The <!-- raw HTML omitted -->*.rsp<!-- raw HTML omitted --> file is an XML file, and can be edited by any text editor.</p>
+<!-- raw HTML omitted -->
 </div>
 
 
@@ -2138,6 +2105,19 @@ This file only contains <em>references</em> to the real data files, and does not
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2148,6 +2128,9 @@ This file only contains <em>references</em> to the real data files, and does not
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3290,20 +3273,20 @@ This file only contains <em>references</em> to the real data files, and does not
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2018_11/index.html b/getting-started/whats-new/releasenotes_2018_11/index.html
index 423eb6ceca..851512f88b 100644
--- a/getting-started/whats-new/releasenotes_2018_11/index.html
+++ b/getting-started/whats-new/releasenotes_2018_11/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2018.11 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,14 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#local-grid-refinement-lgr">Local Grid Refinement (LGR)</a></li>
-<li><a href="#well-path-creation">Well Path Creation</a></li>
-<li><a href="#contour-maps">Contour Maps</a></li>
-<li><a href="#summary-plotting">Summary Plotting</a></li>
-<li><a href="#well-bore-stability-plots-and-casing-design">Well Bore Stability Plots and Casing Design</a></li>
-<li><a href="#memory-management">Memory Management</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#local-grid-refinement-lgr">Local Grid Refinement (LGR)</a></li>
+    <li><a href="#well-path-creation">Well Path Creation</a></li>
+    <li><a href="#contour-maps">Contour Maps</a></li>
+    <li><a href="#summary-plotting">Summary Plotting</a></li>
+    <li><a href="#well-bore-stability-plots-and-casing-design">Well Bore Stability Plots and Casing Design</a></li>
+    <li><a href="#memory-management">Memory Management</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,52 +1834,28 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/introduction/TemporaryLGR.png" alt="Temporary LGR" /></p>
-
+<p><img src="/images/introduction/TemporaryLGR.png" alt="Temporary LGR"></p>
 <p>ResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.</p>
-
 <h2 id="local-grid-refinement-lgr">Local Grid Refinement (LGR)</h2>
-
-<p><img src="/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png" alt=""></p>
 <p>Local Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.</p>
-
 <p>See <a href="/wells-and-completions/completionslgr/">Completions LGR</a></p>
-
 <h2 id="well-path-creation">Well Path Creation</h2>
-
-<p><img src="/images/introduction/WellPathCreation.png" alt="Well Path Creation" /></p>
-
+<p><img src="/images/introduction/WellPathCreation.png" alt="Well Path Creation"></p>
 <p>ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.</p>
-
 <p>See <a href="/wells-and-completions/createnewwellpaths/">Create Well Paths</a></p>
-
 <h2 id="contour-maps">Contour Maps</h2>
-
-<p><img src="/images/introduction/ContourMaps1.png" alt="Contour Maps" /></p>
-
+<p><img src="/images/introduction/ContourMaps1.png" alt="Contour Maps"></p>
 <p>ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.</p>
-
 <p>See <a href="/3d-main-window/contourmaps/">Contour Maps</a></p>
-
 <h2 id="summary-plotting">Summary Plotting</h2>
-
 <h2 id="well-bore-stability-plots-and-casing-design">Well Bore Stability Plots and Casing Design</h2>
-
-<p><img src="/images/introduction/WellBoreStabilityPlots.png" alt="Well Bore Stability Plots" /></p>
-
+<p><img src="/images/introduction/WellBoreStabilityPlots.png" alt="Well Bore Stability Plots"></p>
 <p>ResInsight can create <strong>Well Bore Stability</strong> plots for Geomechanical cases. These plots are specialized <strong>Well Log Plots</strong> and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.</p>
-
 <p>See <a href="/plot-window/wellborestabilityplots/">Well Bore Stability Plots</a></p>
-
 <h2 id="memory-management">Memory Management</h2>
-
-<p><img src="/images/introduction/MemoryManagementBanner.png" alt="Memory Management" /></p>
-
+<p><img src="/images/introduction/MemoryManagementBanner.png" alt="Memory Management"></p>
 <p>ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.</p>
-
 <p>See <a href="/misc/memorymanagement/">Memory Management</a></p>
 
 
@@ -2026,6 +2033,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2036,6 +2056,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3178,20 +3201,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2019_04/index.html b/getting-started/whats-new/releasenotes_2019_04/index.html
index 9476d70fa9..21970ac625 100644
--- a/getting-started/whats-new/releasenotes_2019_04/index.html
+++ b/getting-started/whats-new/releasenotes_2019_04/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.04 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,18 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#grid-cross-plots">Grid Cross Plots</a></li>
-<li><a href="#saturation-pressure-plots">Saturation Pressure Plots</a></li>
-<li><a href="#sector-model-export">Sector Model Export</a></li>
-<li><a href="#well-model-for-icd-aicd-and-icv">Well model for ICD, AICD and ICV</a></li>
-<li><a href="#grid-model-annotations">Grid Model Annotations</a></li>
-<li><a href="#grid-measurements">Grid Measurements</a></li>
-<li><a href="#keyboard-shortcuts">Keyboard Shortcuts</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#grid-cross-plots">Grid Cross Plots</a></li>
+    <li><a href="#saturation-pressure-plots">Saturation Pressure Plots</a></li>
+    <li><a href="#sector-model-export">Sector Model Export</a></li>
+    <li><a href="#well-model-for-icd-aicd-and-icv">Well model for ICD, AICD and ICV</a></li>
+    <li><a href="#grid-model-annotations">Grid Model Annotations</a></li>
+    <li><a href="#grid-measurements">Grid Measurements</a></li>
+    <li><a href="#keyboard-shortcuts">Keyboard Shortcuts</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1804,67 +1835,36 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.</p>
-
 <h2 id="grid-cross-plots">Grid Cross Plots</h2>
-
-<p><img src="/images/introduction/GridCrossPlot.png" alt="" /></p>
-
+<p><img src="/images/introduction/GridCrossPlot.png" alt=""></p>
 <p>ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.</p>
-
 <p>See <a href="/plot-window/gridcrossplots/">Grid Cross Plots</a></p>
-
 <h2 id="saturation-pressure-plots">Saturation Pressure Plots</h2>
-
-<p><img src="/images/introduction/SaturationPressurePlot.png" alt="" /></p>
-
+<p><img src="/images/introduction/SaturationPressurePlot.png" alt=""></p>
 <p>ResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.</p>
-
 <p>See <a href="/plot-window/saturationpressureplots/">Saturation Pressure Plots</a></p>
-
 <h2 id="sector-model-export">Sector Model Export</h2>
-
-<p><img src="/images/introduction/ExportSectorModel_Grid.png" alt="" /></p>
-
+<p><img src="/images/introduction/ExportSectorModel_Grid.png" alt=""></p>
 <p>Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.</p>
-
 <p>See <a href="/export/sectormodel/">Export Sector Model</a></p>
-
 <h2 id="well-model-for-icd-aicd-and-icv">Well model for ICD, AICD and ICV</h2>
-
-<p><img src="/images/introduction/ValveVisualisation.png" alt="" /></p>
-
+<p><img src="/images/introduction/ValveVisualisation.png" alt=""></p>
 <p>ResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - <strong>MSW</strong>.</p>
-
 <p>See <a href="/wells-and-completions/completions/">Completions</a> and  <a href="/export/completionexport/">Completion Export</a></p>
-
 <h2 id="grid-model-annotations">Grid Model Annotations</h2>
-
-<p><img src="/images/introduction/Annotations.png" alt="" /></p>
-
+<p><img src="/images/introduction/Annotations.png" alt=""></p>
 <p>Annotation objects like text, lines and plolylines can easily be added to a view.</p>
-
 <p>See <a href="/3d-main-window/annotations/">Annotations</a></p>
-
 <h2 id="grid-measurements">Grid Measurements</h2>
-
-<p><img src="/images/introduction/Measurement.png" alt="" /></p>
-
+<p><img src="/images/introduction/Measurement.png" alt=""></p>
 <p>ResInsight now supports measuring distances and polyline lengths across a Grid.</p>
-
 <p>See <a href="/3d-main-window/measurement/">Measurements</a></p>
-
 <h2 id="keyboard-shortcuts">Keyboard Shortcuts</h2>
-
 <p>Several new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.</p>
-
-<p><img src="/images/introduction/KeyboardDel.png" alt="" />
-<img src="/images/introduction/KeyboardEast.png" alt="" /></p>
-
+<p><img src="/images/introduction/KeyboardDel.png" alt="">
+<img src="/images/introduction/KeyboardEast.png" alt=""></p>
 <p>For instance will the <strong>Delete</strong> key now delete any deletable item in the project tree and <strong>Ctrl-Alt-S/N/W/E/D/U</strong> will change the 3d Camera view to South, North, West East, Down and Up respectively.</p>
-
 <p>See <a href="/misc/keyboardshortcuts/">Keyboard Shortcuts</a></p>
 
 
@@ -2042,6 +2042,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2052,6 +2065,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3194,20 +3210,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2019_08/index.html b/getting-started/whats-new/releasenotes_2019_08/index.html
index ba83a54ebf..37e0617696 100644
--- a/getting-started/whats-new/releasenotes_2019_08/index.html
+++ b/getting-started/whats-new/releasenotes_2019_08/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.08 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,14 +1802,11 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#python-scripting">Python scripting</a></li>
-<li><a href="#launch-resinsight-without-user-interface">Launch ResInsight without user interface</a></li>
-<li><a href="#plotting-improvements">Plotting improvements</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#python-scripting">Python scripting</a></li>
+    <li><a href="#launch-resinsight-without-user-interface">Launch ResInsight without user interface</a></li>
+    <li><a href="#plotting-improvements">Plotting improvements</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1800,14 +1831,9 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.</p>
-
 <h2 id="python-scripting">Python scripting</h2>
-
 <p>Basic example on how to update views from Python</p>
-
 <pre><code>import rips
 # Connect to ResInsight instance
 resInsight = rips.Instance.find()
@@ -1825,27 +1851,18 @@ if resInsight is not None:
             view.setBackgroundColor(&quot;#3388AA&quot;)            
             # Update the view in ResInsight
             view.update()
-</code></pre>
-
-<p>See <a href="/scripting/pythonrips/">Python Scripting</a></p>
-
+</code></pre><p>See <a href="/scripting/pythonrips/">Python Scripting</a></p>
 <h2 id="launch-resinsight-without-user-interface">Launch ResInsight without user interface</h2>
-
 <p>It is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.</p>
-
 <p>See <a href="/scripting/commandlineinterface/">Command Line Interface</a></p>
-
 <h2 id="plotting-improvements">Plotting improvements</h2>
-
-<p><img src="/images/plot-window/SummaryCurveHighlight.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCurveHighlight.png" alt=""></p>
 <ul>
 <li>Date and time can now be customized to exactly the format you prefer</li>
 <li>To easily see the difference between history vectors and other vectors, the default style for history vector is symbols without lines</li>
 <li>Curves in a plot will be hightlighted when left-clicking the curve</li>
 </ul>
-
-<p>See <a href="/plot-window/summaryplots/#curve-hightlight">Summary Plotting</a></p>
+<p>See <a href="/plot-window/summaryplots/">Summary Plotting</a></p>
 
 
 <footer class=" footline" >
@@ -2022,6 +2039,19 @@ if resInsight is not None:
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2032,6 +2062,9 @@ if resInsight is not None:
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3174,20 +3207,20 @@ if resInsight is not None:
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2019_12/index.html b/getting-started/whats-new/releasenotes_2019_12/index.html
index f7d75e0bc1..900f7e3ac2 100644
--- a/getting-started/whats-new/releasenotes_2019_12/index.html
+++ b/getting-started/whats-new/releasenotes_2019_12/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.12 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,22 +1802,20 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#comparison-view">Comparison View</a></li>
-<li><a href="#support-for-summary-plot-templates">Support for Summary Plot Templates</a></li>
-<li><a href="#ensemble-rft-data-import-and-plotting">Ensemble RFT data import and plotting</a></li>
-<li><a href="#command-line-interface-for-summary-plotting">Command line interface for Summary plotting</a></li>
-<li><a href="#text-based-curve-creation-and-source-stepping">Text-Based Curve Creation and Source Stepping</a></li>
-<li><a href="#export-contour-plot-data">Export Contour plot data</a></li>
-<li><a href="#well-bore-stability-plots">Well Bore Stability plots</a></li>
-<li><a href="#changes-in-behavior-and-defaults">Changes in behavior and defaults</a>
-<ul>
-<li><a href="#info-box-change-of-defaults-for-statistics-options">Info Box: Change of defaults for Statistics Options</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#comparison-view">Comparison View</a></li>
+    <li><a href="#support-for-summary-plot-templates">Support for Summary Plot Templates</a></li>
+    <li><a href="#ensemble-rft-data-import-and-plotting">Ensemble RFT data import and plotting</a></li>
+    <li><a href="#command-line-interface-for-summary-plotting">Command line interface for Summary plotting</a></li>
+    <li><a href="#text-based-curve-creation-and-source-stepping">Text-Based Curve Creation and Source Stepping</a></li>
+    <li><a href="#export-contour-plot-data">Export Contour plot data</a></li>
+    <li><a href="#well-bore-stability-plots">Well Bore Stability plots</a></li>
+    <li><a href="#changes-in-behavior-and-defaults">Changes in behavior and defaults</a>
+      <ul>
+        <li><a href="#info-box-change-of-defaults-for-statistics-options">Info Box: Change of defaults for Statistics Options</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1808,70 +1840,42 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.
-Version 2019.12 is a major update bringing a range of significant new and enhanced features.
+Version 2019.12 is a major update bringing a range of significant new and enhanced features. 
 Some of the most important extensions are listed below.</p>
-
 <h2 id="comparison-view">Comparison View</h2>
-
 <p>ResInsight offers a <a href="/3d-main-window/comparisonview/">Comparison View</a> to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.</p>
-
-<p><img src="/images/3d-main-window/3DComparisonView.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3DComparisonView.png" alt=""></p>
 <h2 id="support-for-summary-plot-templates">Support for Summary Plot Templates</h2>
-
-<p>ResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for
-<a href="/plot-window/summaryplottemplate/">Summary Plot Templates</a> which are defined by a number of curves with preset appearance and vector names.
+<p>ResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for 
+<a href="/plot-window/summaryplottemplate/">Summary Plot Templates</a> which are defined by a number of curves with preset appearance and vector names. 
 Having tailored a plot setup, the user can save the setup as a template definition to file for later reuse.</p>
-
-<p><img src="/images/plot-window/SummaryPlotTemplate.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotTemplate.png" alt=""></p>
 <h2 id="ensemble-rft-data-import-and-plotting">Ensemble RFT data import and plotting</h2>
-
 <p>ResInsight allows the user to create a <a href="/plot-window/ensemblerftplot/">ensemble RFT plot</a> similar to summary ensemble plots. The functionality includes advanced color schemes for differentiation of curves, computation of statistics, and import of observed ensemble RFT data from FMU.</p>
-
-<p><img src="/images/plot-window/EnsembleRftPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/EnsembleRftPlot.png" alt=""></p>
 <h2 id="command-line-interface-for-summary-plotting">Command line interface for Summary plotting</h2>
-
 <p>ResInsight scripting has been extended with summary plotting commands that plot summary vectors based on textual specifications including the use of wildcards for selection and filtering. For more information and examples of use, see <a href="/scripting/commandlineinterface/#summary-plotting">Command line interface for Summary Plotting</a>.</p>
-
 <h2 id="text-based-curve-creation-and-source-stepping">Text-Based Curve Creation and Source Stepping</h2>
-
 <p><a href="/plot-window/summaryplots/#property-editor">Text-Based Curve Creation</a> allows specification of a list of vectors for plotting based on selected sources. The history of text-based curve specifications are recorded to allow for effective use.</p>
-
 <p>This is possible to combine with <a href="/scripting/commandlineinterface/">Summary Source Stepping</a> which has been extended to further support swift stepping through multiple vectors.</p>
-
-<p><img src="/images/plot-window/SummarySourceSteppingToolbar.png" alt="" />
-<img src="/images/plot-window/SummarySourceSteppingPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummarySourceSteppingToolbar.png" alt="">
+<img src="/images/plot-window/SummarySourceSteppingPropertyEditor.png" alt=""></p>
 <h2 id="export-contour-plot-data">Export Contour plot data</h2>
-
-<p>ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information,
+<p>ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information, 
 see <a href="/export/contourmapexport/">Contour Map Export</a>.</p>
-
-<p><img src="/images/export/ExportContourMap.png" alt="" /></p>
-
+<p><img src="/images/export/ExportContourMap.png" alt=""></p>
 <h2 id="well-bore-stability-plots">Well Bore Stability plots</h2>
-
 <p>Major extensions and enhancements have been added to Well Bore Stability plots for Geomechanical cases. Well Bore Stability plots are specialized <a href="/plot-window/welllogsandplots/">Well Log Plots</a> to visualize <a href="/3d-main-window/formations/">Formations</a>, <a href="/wells-and-completions/wellpaths/#well-path-attributes">Well Path Attributes</a> as well as a set of well path derived curves in different tracks.</p>
-
-<p><img src="/images/plot-window/WellBoreStability.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellBoreStability.png" alt=""></p>
 <h2 id="changes-in-behavior-and-defaults">Changes in behavior and defaults</h2>
-
 <h3 id="info-box-change-of-defaults-for-statistics-options">Info Box: Change of defaults for Statistics Options</h3>
-
 <p>Following multiple user requests, the defaults for <strong>Statistics Options</strong> in Info Box have been changed to:</p>
-
 <ul>
 <li>Statistics Time Range: <em>Current Time Step</em></li>
 <li>Statistics Cell Range: <em>Visible Cells</em></li>
 </ul>
-
-<p><img src="/images/3d-main-window/InfoBoxConfig.png" alt="" /></p>
+<p><img src="/images/3d-main-window/InfoBoxConfig.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2048,6 +2052,19 @@ see <a href="/export/contourmapexport/">Contour Map Export</a>.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2058,6 +2075,9 @@ see <a href="/export/contourmapexport/">Contour Map Export</a>.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3200,20 +3220,20 @@ see <a href="/export/contourmapexport/">Contour Map Export</a>.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2019_12_1/index.html b/getting-started/whats-new/releasenotes_2019_12_1/index.html
index 5497ee8791..35e68392b1 100644
--- a/getting-started/whats-new/releasenotes_2019_12_1/index.html
+++ b/getting-started/whats-new/releasenotes_2019_12_1/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.12.1 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#bugfixes">Bugfixes</a></li>
-<li><a href="#changes-in-behavior">Changes in behavior</a>
-<ul>
-<li><a href="#welsegs">WELSEGS</a></li>
-<li><a href="#multiple-completions-in-same-cell">Multiple completions in same cell</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#bugfixes">Bugfixes</a></li>
+    <li><a href="#changes-in-behavior">Changes in behavior</a>
+      <ul>
+        <li><a href="#welsegs">WELSEGS</a></li>
+        <li><a href="#multiple-completions-in-same-cell">Multiple completions in same cell</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,27 +1835,16 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight 2019.12.1 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.
 Version 2019.12.1 consists of a few critical issues and minor functionality changes.</p>
-
 <h2 id="bugfixes">Bugfixes</h2>
-
 <p><a href="https://github.com/OPM/ResInsight/releases/tag/v2019.12.1">Release info on GitHub</a></p>
-
 <h2 id="changes-in-behavior">Changes in behavior</h2>
-
 <h3 id="welsegs">WELSEGS</h3>
-
 <p>Output of segment depth is based on center of segment. Previously the segment end was reported.</p>
-
-<p><a href="/export/completionexport/#exported-msw-data"> Export of Completions and MSW </a></p>
-
+<p><a href="/export/completionexport/"> Export of Completions and MSW </a></p>
 <h3 id="multiple-completions-in-same-cell">Multiple completions in same cell</h3>
-
 <p>In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell. Now, when multiple fracture are detected, they are combined and reported similar to other completion types.</p>
-
 <p><a href="/export/completionexport/"> Export of Completions </a></p>
 
 
@@ -2001,6 +2022,19 @@ Version 2019.12.1 consists of a few critical issues and minor functionality chan
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2011,6 +2045,9 @@ Version 2019.12.1 consists of a few critical issues and minor functionality chan
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3153,20 +3190,20 @@ Version 2019.12.1 consists of a few critical issues and minor functionality chan
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/eclipsecases/index.html b/import/eclipsecases/index.html
index 23d58f0ebb..362ae326c2 100644
--- a/import/eclipsecases/index.html
+++ b/import/eclipsecases/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Eclipse Cases :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,21 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#eclipse-results">Eclipse Results</a>
-<ul>
-<li><a href="#result-index-file">Result Index File</a></li>
-</ul></li>
-<li><a href="#time-step-filtered-eclipse-result">Time Step Filtered Eclipse Result</a></li>
-<li><a href="#eclipse-ascii-input-data">Eclipse ASCII Input Data</a></li>
-<li><a href="#handling-missing-or-wrong-mapaxes">Handling Missing or Wrong MAPAXES</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#eclipse-results">Eclipse Results</a></li>
+        <li><a href="#time-step-filtered-eclipse-result">Time Step Filtered Eclipse Result</a></li>
+        <li><a href="#eclipse-ascii-input-data">Eclipse ASCII Input Data</a></li>
+        <li><a href="#handling-missing-or-wrong-mapaxes">Handling Missing or Wrong MAPAXES</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1807,24 +1836,17 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight supports the following type of Eclipse input data:</p>
-
 <ul>
 <li><em><code>*.GRID</code></em> and <em><code>*.EGRID</code></em> files along with their <em><code>*.INIT</code></em> and restart files <em><code>*.XNNN</code></em> and <em><code>*.UNRST</code></em>.</li>
 <li>Grid and Property data from  <em><code>*.GRDECL</code></em> files.</li>
 </ul>
 
-
 <div class="notices note" ><p>Release 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.</p>
 </div>
 
-
 <h3 id="eclipse-results">Eclipse Results</h3>
-
 <p>ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the <strong>File-&gt;Import-&gt;Eclipse Cases</strong> menu:</p>
-
 <ul>
 <li><strong>Import Eclipse Case</strong>: Brings up the standard file selection dialog. Select <em><code>*.EGRID</code></em> or <em><code>*.GRID</code></em> Eclipse files for import. Multiple selections are allowed.</li>
 <li><strong>Import Eclipse Cases Recursively</strong>: Brings up the recursive file selection dialog. This dialog is described in detail on the <a href="/plot-window/summaryplots/#recursive-summary-file-import">Summary Plots page</a>.</li>
@@ -1832,56 +1854,39 @@ if (!doNotTrack) {
 <li><strong>Import Input Eclipse Case</strong>: See <a href="#eclipse-ascii-input-data">description</a></li>
 <li><strong>Create Grid Case Group from Files</strong> and <strong>Create Grid Case Group from Files Recursively</strong>: These commands import a number of Eclipse files and places the cases in a <a href="/3d-main-window/casegroupsandstatistics/#creating-grid-case-groups">grid case group</a>. The only difference between the two commands, is the dialog used to select files. The recursive version is using the <a href="/plot-window/summaryplots/#recursive-summary-file-import">recursive file selection dialog</a> and is considered the new way of selecting files.</li>
 </ul>
-
 <p>The <strong>Reload Case</strong> command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.</p>
 
-
 <div class="notices note" ><p>You can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).</p>
 </div>
 
-
 <h4 id="result-index-file">Result Index File</h4>
-
 <p>If enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named <em><code>&lt;casename&gt;.RESINSIGHT_IDX</code></em>
 See <a href="/misc/preferences/#behavior-when-loading-data">Preferences: Behavior When Loading Data</a></p>
-
 <h3 id="time-step-filtered-eclipse-result">Time Step Filtered Eclipse Result</h3>
-
 <p>Some Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.</p>
-
 <p>Select <strong>File-&gt;Import-&gt;Eclipse Cases-&gt; <img src="https://resinsight.org/images/getting-started/Case24x24.png" style="display:inline; vertical-align:middle; margin:0">
  Import Eclipse Case (Time Step Filtered)</strong> and select an <em><code>*.EGRID</code></em> or <em><code>*.GRID</code></em> Eclipse file for import. A dialog will appear.</p>
-
-<p><img src="/images/getting-started/timeStepFilter.png" alt="" /></p>
-
-<p>Filtering can be done by adjusting the following parameters:
-* First and last time step
-* Step filter type and with step interval size</p>
-
+<p><img src="/images/getting-started/timeStepFilter.png" alt=""></p>
+<p>Filtering can be done by adjusting the following parameters:</p>
+<ul>
+<li>First and last time step</li>
+<li>Step filter type and with step interval size</li>
+</ul>
 <p>First and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.</p>
-
 <p><strong>Filter Type</strong> is set to <em>All</em> by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to <em>All</em> is to skip time steps in a number of <em>Days</em>, <em>Weeks</em>, <em>Months</em>, <em>Quarters</em> or <em>Years</em>. The skipping interval is set in the text field below. After editing the <strong>Interval</strong> field, press <em>tab</em> to update the <strong>Filtered Time Steps</strong> preview, or click anywhere in the dialog. Click <em>Ok</em> to import when the filter is ready.</p>
-
 <p>Filtering can also be done after import, in a case&rsquo;s <strong>Property Window</strong>.</p>
-
-<p><img src="/images/getting-started/timeStepFilterPropEditor.png" alt="" /></p>
-
+<p><img src="/images/getting-started/timeStepFilterPropEditor.png" alt=""></p>
 <p>After clicking <em>Reload Case</em>, the time steps in the toolbar will be updated.</p>
-
 <h3 id="eclipse-ascii-input-data">Eclipse ASCII Input Data</h3>
-
 <ol>
 <li>Select <strong>File-&gt;Import-&gt;Eclipse Cases-&gt; <img src="https://resinsight.org/images/getting-started/EclipseInput24x24.png" style="display:inline; vertical-align:middle; margin:0">
  Import Input Eclipse Case</strong> and select a <em><code>*.GRDECL</code></em> file.</li>
 <li>The case is imported, and a view of the case is created</li>
 <li>Right-click the <strong>Input Properties</strong> in the generated <strong>Input Case</strong> and use the right-click menu to import additional Eclipse Property data files.</li>
 </ol>
-
 <h3 id="handling-missing-or-wrong-mapaxes">Handling Missing or Wrong MAPAXES</h3>
-
 <p>The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the <strong>Property Editor</strong> for all Eclipse Case types as the toggle buttons <strong>Flip X Axis</strong> and <strong>Flip Y Axis</strong> as shown in the example below.</p>
-
-<p><img src="/images/getting-started/CaseProperties.png" alt="" /></p>
+<p><img src="/images/getting-started/CaseProperties.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2057,6 +2062,19 @@ See <a href="/misc/preferences/#behavior-when-loading-data">Preferences: Behavio
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2067,6 +2085,9 @@ See <a href="/misc/preferences/#behavior-when-loading-data">Preferences: Behavio
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3214,20 +3235,20 @@ See <a href="/misc/preferences/#behavior-when-loading-data">Preferences: Behavio
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/elementpropertytable/index.html b/import/elementpropertytable/index.html
index 3f96e8464a..8b397c2607 100644
--- a/import/elementpropertytable/index.html
+++ b/import/elementpropertytable/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Element Property Table :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#file-format">File Format</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#file-format">File Format</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,34 +1833,22 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>Element property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.</p>
-
-<p>To view the data as a <strong>Color Result</strong> select the <strong>Result Position</strong>: <strong><em>Element</em></strong> ( See <a href="/3d-main-window/cellresults/#geomechanical-results">Geomechanical Results</a> )</p>
-
+<p>To view the data as a <strong>Color Result</strong> select the <strong>Result Position</strong>: <em><strong>Element</strong></em> ( See <a href="/3d-main-window/cellresults/#geomechanical-results">Geomechanical Results</a> )</p>
 <p>A couple of property names are recognized and treated specially:</p>
-
 <ul>
 <li>MODULUS &ndash; Scaled by 1.0e-9 and shown as &ldquo;Yong&rsquo;s Modulus&rdquo; in the user interface</li>
 <li>RATIO &ndash; Shown as &ldquo;Poisson&rsquo;s Ratio&rdquo; in the user interface</li>
 </ul>
-
 <h3 id="file-format">File Format</h3>
-
 <p>A couple of examples on the file format are shown below.</p>
-
 <p>ResInsight searches for the first line containing <code>*Distribution Table</code>, then splits the following line by <code>,</code>. These entries describes the expected property values to be found in the file.</p>
-
 <p>ResInsight then searches for the data block by ignoring lines</p>
-
 <ul>
 <li>starting with <code>*</code> and <code>,</code></li>
 <li>does not have the expected column count when splitting the line by <code>,</code></li>
 </ul>
-
 <p>When the datablock is found, the part of the line before <code>.</code> is stripped away, and first column is expected to be element ID</p>
-
 <pre><code>** ELASTIC SETTING FOR EACH ELEMENT
 *Distribution Table, name=RSV_Res-1_Elastic_Table
 MODULUS, RATIO
@@ -1839,9 +1859,7 @@ Res-1.210, 11198814808.2538, 0.19041
 Res-1.209, 11207002032.1436, 0.19063
 Res-1.208, 11222989223.0933, 0.19104
 Res-1.207, 11202549454.349, 0.19051
-</code></pre>
-
-<pre><code>** DENSITY SETTING FOR EACH ELEMENT
+</code></pre><pre><code>** DENSITY SETTING FOR EACH ELEMENT
 *Distribution Table, name=RSV_Res-1_Density_Table
 Density
 *Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table
@@ -1853,7 +1871,6 @@ Res-1.208, 2500
 Res-1.207, 2500
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -2027,6 +2044,19 @@ Res-1.207, 2500
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2037,6 +2067,9 @@ Res-1.207, 2500
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3187,20 +3220,20 @@ Res-1.207, 2500
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/geomechanicaldata/index.html b/import/geomechanicaldata/index.html
index 2bb13d2a0c..dbd14ca154 100644
--- a/import/geomechanicaldata/index.html
+++ b/import/geomechanicaldata/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Geomechanical Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#geo-mechanical-data-support">Geo Mechanical Data Support</a></li>
-<li><a href="#resinsight-features">ResInsight Features</a></li>
-<li><a href="#time-step-filtered-import">Time Step Filtered Import</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#geo-mechanical-data-support">Geo Mechanical Data Support</a></li>
+        <li><a href="#resinsight-features">ResInsight Features</a></li>
+        <li><a href="#time-step-filtered-import">Time Step Filtered Import</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,40 +1835,22 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the <em><code>*.odb</code></em> format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.</p>
-
 <p>If you have, and would like to a use these features, please see <a href="/getting-started/download-and-install/buildinstructions/"> Build Instructions </a> for a description on how to build ResInsight and how to include the support for odb-files.</p>
-
 <h3 id="geo-mechanical-data-support">Geo Mechanical Data Support</h3>
-
 <p>Geo-mechanical data can be imported using the <strong>Import -&gt; Geo Mechanical Cases menu</strong>. Here three options are present: <strong>Import Geo Mechanical Model</strong>, <strong>Import Geo Mechanical Model (Time Step Filtered)</strong>  (both for odb files) and <strong>Import Element Property Table</strong>.</p>
-
-<p><img src="/images/import/GeoMechImport.png" alt="" /></p>
-
+<p><img src="/images/import/GeoMechImport.png" alt=""></p>
 <p>ResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are <em>no other element topologies</em> present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.</p>
-
 <p>ResInsight loads the second frame within each odb-step, and present those as the time series for each result.</p>
-
 <p>All the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.</p>
-
 <p>Pressure and stress are always displayed using the <em>Bar</em> unit.</p>
-
 <p>Other derived results are also calculated, and are described in <a href="/3d-main-window/derivedresults/"> Derived Results </a></p>
-
 <h3 id="resinsight-features">ResInsight Features</h3>
-
 <p>Most of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.</p>
-
 <p>The Octave interface, however, does not support the odb-data yet.</p>
-
 <h3 id="time-step-filtered-import">Time Step Filtered Import</h3>
-
 <p>By choosing the <strong>Import Geo Mechanical Model (Time Step Filtered)</strong> option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.</p>
-
-<p><img src="/images/import/GeoMechFilter.png" alt="" /></p>
-
+<p><img src="/images/import/GeoMechFilter.png" alt=""></p>
 <p>The data can be filtered by skipping Days, Weeks, Months or Years in the top <strong>Filter Type</strong> drop down list and the range of time steps can be picked in the <strong>First Time Step</strong> and <strong>Last Time Steps</strong> lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the <strong>Select From N Time Steps</strong> list. ResInsight will ignore any data that doesn&rsquo;t match these time steps and will thus reduce the amount of data imported.</p>
 
 
@@ -2013,6 +2027,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2023,6 +2050,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3173,20 +3203,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/index.html b/import/index.html
index 4ebc26a146..05e64288ba 100644
--- a/import/index.html
+++ b/import/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Import :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,21 +1820,16 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/import/GeoMechImport.png" alt="" /></p>
-
+	<p><img src="/images/import/GeoMechImport.png" alt=""></p>
 <p>ResInsight is able to import the following type of Eclipse files:</p>
-
 <ul>
 <li><em><code>*.GRID</code></em> and <em><code>*.EGRID</code></em> files along with their <em><code>*.INIT</code></em> and restart files <em><code>*.XNNN</code></em> and <em><code>*.UNRST</code></em>.</li>
 <li>Grid and Property data from  <em><code>*.GRDECL</code></em> files.</li>
 </ul>
-
 <p>For functionality and import of Eclipse data pertinent to summary vectors and well log data, see <a href="">Plot Window</a>.</p>
-
-<p>ResInsight can be built with support for geomechanical models from ABAQUS and is also able to import
+<p>ResInsight can be built with support for geomechanical models from ABAQUS and is also able to import 
 transient reservoir souring data from the SourSimRL simulation software.</p>
-
-<p>Furthermore, ResInsight supports import of property tables in ABQUS input file format,
+<p>Furthermore, ResInsight supports import of property tables in ABQUS input file format, 
 observed time history data, and pasting time history data into a summary plot
 as described in the subsequent subchapters.</p>
 
@@ -1980,6 +2009,19 @@ as described in the subsequent subchapters.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1990,6 +2032,9 @@ as described in the subsequent subchapters.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3136,20 +3181,20 @@ as described in the subsequent subchapters.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/index.xml b/import/index.xml
index 7c697319b1..a9dfe1438b 100644
--- a/import/index.xml
+++ b/import/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Import on ResInsight</title>
@@ -82,7 +82,7 @@ Import Observed Time History Data Importing observed time history data to ResIns
       
       <guid>https://resinsight.org/import/pasteexceltimedata/</guid>
       <description>When text have been copied to the operating system&amp;rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the Plot Main Window Project Tree and select Paste Excel Data to Summary Plot. Then a paste options dialog will appear.
-Paste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog.</description>
+Paste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog. Please see that section for documentation on those fields.</description>
     </item>
     
   </channel>
diff --git a/import/lasfile/index.html b/import/lasfile/index.html
index 8d20294a1c..e59d798b89 100644
--- a/import/lasfile/index.html
+++ b/import/lasfile/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Log ASCII Standard File :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#importing-a-las-file">Importing a LAS file</a>
-<ul>
-<li><a href="#moving-a-las-file">Moving a LAS file</a></li>
-<li><a href="#look-for-an-existing-well-path">Look for an Existing Well Path</a></li>
-</ul></li>
-<li><a href="#supported-date-formats">Supported Date Formats</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#importing-a-las-file">Importing a LAS file</a>
+      <ul>
+        <li><a href="#moving-a-las-file">Moving a LAS file</a></li>
+        <li><a href="#look-for-an-existing-well-path">Look for an Existing Well Path</a></li>
+      </ul>
+    </li>
+    <li><a href="#supported-date-formats">Supported Date Formats</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,44 +1835,27 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/3dWellLogCurves.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves.png" alt=""></p>
 <p>Log ASCII Standard (LAS) is a standard file format common in the oil-and-gas industry to store well log information.</p>
-
 <h2 id="importing-a-las-file">Importing a LAS file</h2>
-
 <p>Log ASCII Standard (LAS) files can be imported using the command: <strong>File-&gt;Import-&gt; Well Data-&gt;Import Well Logs from File</strong>.</p>
-
 <p>ResInsight will look for the the well name in the imported LAS-files among the existing <strong>Well Paths</strong>.
 If a match is found, the LAS-file is placed as a child of that well path. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.</p>
-
-<p><img src="/images/3d-main-window/LasFilesInTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/LasFilesInTree.png" alt=""></p>
 <p>If the LAS-file does not contain a well name, the file name is used instead.</p>
-
 <h3 id="moving-a-las-file">Moving a LAS file</h3>
-
 <p>If ResInsight&rsquo;s automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file right-click menu click <strong>Move LAS File to Well Path</strong> and select destination well path.</p>
-
-<p><img src="/images/3d-main-window/MoveLasFileMenu.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/MoveLasFileMenu.png" alt=""></p>
 <h3 id="look-for-an-existing-well-path">Look for an Existing Well Path</h3>
-
 <p>Well names may vary slightly among different files from the same well. When importing a well log file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:</p>
-
 <ul>
 <li>First remove any prefix (like <code>xxxxx1111/1111-</code> or <code>xxxxx1111/1111_</code>)</li>
 <li>Then try an exact name match</li>
 <li>If not found, try to match the names ignoring all spaces, dashes and underscores</li>
 <li>If still no match, no existing well was found and a new one is created</li>
 </ul>
-
 <h2 id="supported-date-formats">Supported Date Formats</h2>
-
 <p>During LAS import, ResInsight parses a date on file according to the following expressions. Supported separators between day, month, and year are <strong>space</strong>, <strong>underscore</strong>, <strong>hyphen</strong>, and <strong>dot</strong>.</p>
-
 <table>
 <thead>
 <tr>
@@ -1848,47 +1863,38 @@ If a match is found, the LAS-file is placed as a child of that well path. If not
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>d</td>
 <td>day as number without a leading zero (1 to 31), e.g. <em>7</em></td>
 </tr>
-
 <tr>
 <td>dd</td>
 <td>day as a two digit number (01 to 31), e.g. <em>07</em></td>
 </tr>
-
 <tr>
 <td>M</td>
 <td>month as number without a leading zero (1-12), e.g. <em>8</em></td>
 </tr>
-
 <tr>
 <td>MM</td>
 <td>month as a two digit number (01-12), e.g. <em>08</em></td>
 </tr>
-
 <tr>
 <td>MMM</td>
 <td>short month name in uppercase or lowercase (&lsquo;Jan&rsquo; to &lsquo;Dec&rsquo;), e.g. <em>AUG</em></td>
 </tr>
-
 <tr>
 <td>yy</td>
 <td>year as a two digit number (00-99), e.g. <em>19</em></td>
 </tr>
-
 <tr>
 <td>yyyy</td>
 <td>year as a four digit number, e.g. <em>2019</em></td>
 </tr>
 </tbody>
 </table>
-
 <p>Examples of supported date expressions are listed in the following table.</p>
-
 <table>
 <thead>
 <tr>
@@ -1896,38 +1902,31 @@ If a match is found, the LAS-file is placed as a child of that well path. If not
 <th>Example</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>yyyy MM dd</td>
 <td>2019 08 16</td>
 </tr>
-
 <tr>
 <td>yyyy-MM-dd</td>
 <td>2019-08-16</td>
 </tr>
-
 <tr>
 <td>yyyy MMM dd</td>
 <td>2019 Aug 16</td>
 </tr>
-
 <tr>
 <td>MMM dd yyyy</td>
 <td>Aug 16 2019</td>
 </tr>
-
 <tr>
 <td>d.M.yy</td>
 <td>1.8.89</td>
 </tr>
-
 <tr>
 <td>dd_MM_yyyy</td>
 <td>16_08_2019</td>
 </tr>
-
 <tr>
 <td>dd.MMM.yyyy</td>
 <td>16.Aug.2019</td>
@@ -2109,6 +2108,19 @@ If a match is found, the LAS-file is placed as a child of that well path. If not
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2119,6 +2131,9 @@ If a match is found, the LAS-file is placed as a child of that well path. If not
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3269,20 +3284,20 @@ If a match is found, the LAS-file is placed as a child of that well path. If not
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/observeddata/index.html b/import/observeddata/index.html
index d19f8e88a4..f14a4ff61d 100644
--- a/import/observeddata/index.html
+++ b/import/observeddata/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Observed Time History Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,37 +1802,17 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#import-observed-time-history-data">Import Observed Time History Data</a></li>
-<li><a href="#file-formats">File Formats</a>
-<ul>
-<li><a href="#import-csv-txt-observed-time-history-data">Import CSV/txt Observed Time History Data</a>
-<ul>
-<li><a href="#csv-txt-import-options-dialog">CSV/txt Import Options Dialog</a></li>
-<li><a href="#column-data">Column data</a>
-<ul>
-<li><a href="#eclipse-address-format">Eclipse address format</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#csv-line-based-format">CSV Line Based Format</a>
-<ul>
-<li><a href="#example">Example</a></li>
-</ul></li>
-<li><a href="#import-rsm-observed-time-history-data">Import RSM observed time history data</a>
-<ul>
-<li><a href="#column-based-file-format">Column Based File Format</a>
-<ul>
-<li><a href="#column-based-with-fixed-header-width">Column Based with Fixed Header Width</a></li>
-<li><a href="#column-based-with-random-header-width">Column Based with Random Header Width</a></li>
-</ul></li>
-<li><a href="#keyword-based-file-format">Keyword Based File Format</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#viewing-observed-time-history-data">Viewing Observed Time History Data</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#import-observed-time-history-data">Import Observed Time History Data</a></li>
+    <li><a href="#file-formats">File Formats</a>
+      <ul>
+        <li><a href="#import-csvtxt-observed-time-history-data">Import CSV/txt Observed Time History Data</a></li>
+        <li><a href="#csv-line-based-format">CSV Line Based Format</a></li>
+        <li><a href="#import-rsm-observed-time-history-data">Import RSM observed time history data</a></li>
+      </ul>
+    </li>
+    <li><a href="#viewing-observed-time-history-data">Viewing Observed Time History Data</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1823,21 +1837,14 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>Observed Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in <strong>Summary Plots</strong>.</p>
-
 <h2 id="import-observed-time-history-data">Import Observed Time History Data</h2>
-
 <p>Importing observed time history data to ResInsight may be performed in two different ways:</p>
-
 <ul>
 <li>By selecting the main menu item <strong>File -&gt; Import -&gt; Import Observed Time History Data</strong></li>
 <li>By using the context command <strong>Import Observed Time History Data</strong> on the <strong>Observed Time History Data</strong> item in the <strong>Plot Main Window Project Tree</strong></li>
 </ul>
-
 <p>The following file types are supported:</p>
-
 <ul>
 <li>RSM observed time history data file (<em>*.rsm</em>)</li>
 <li>Column based (Comma Separated Values, CSV) time history data file (<em>*.csv/*.txt</em>)
@@ -1845,23 +1852,14 @@ The imported <img src="https://resinsight.org/images/import/Default.png" style="
  Observed Time History Data files will be added to <img src="https://resinsight.org/images/import/Folder.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Observed Time History Data</strong>.</li>
 </ul>
-
 <p>Which summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data&rsquo;s <strong>Property Editor</strong>. In the image below, time and year info has been found together with the summary &ldquo;WBP9L&rdquo; for the well &ldquo;OP-1&rdquo;.</p>
-
-<p><img src="/images/import/observedDataProperty.png" alt="" /></p>
-
+<p><img src="/images/import/observedDataProperty.png" alt=""></p>
 <h2 id="file-formats">File Formats</h2>
-
-<h3 id="import-csv-txt-observed-time-history-data">Import CSV/txt Observed Time History Data</h3>
-
+<h3 id="import-csvtxt-observed-time-history-data">Import CSV/txt Observed Time History Data</h3>
 <p>CSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.</p>
-
-<h4 id="csv-txt-import-options-dialog">CSV/txt Import Options Dialog</h4>
-
-<p><img src="/images/import/ImportObservedTimeHistoryDataDialog.png" alt="" /></p>
-
+<h4 id="csvtxt-import-options-dialog">CSV/txt Import Options Dialog</h4>
+<p><img src="/images/import/ImportObservedTimeHistoryDataDialog.png" alt=""></p>
 <p>Dialog fields description:</p>
-
 <ul>
 <li><strong>Cell Separator</strong> &ndash; Select the correct cell separator character. ResInsight will try to set the correct value as default.</li>
 <li><strong>Decimal Separator</strong> &ndash; Select the correct decimal separator. ResInsight will try to set the correct value as default.</li>
@@ -1872,101 +1870,86 @@ The imported <img src="https://resinsight.org/images/import/Default.png" style="
 <li><strong>Time Format</strong> &ndash; Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight.</li>
 <li><strong>Preview</strong> &ndash; Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.</li>
 </ul>
-
 <h4 id="column-data">Column data</h4>
-
 <p>Each column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the <a href="/plot-window/summaryploteditor/">Summary Plot Editor</a>.</p>
-
 <h5 id="eclipse-address-format">Eclipse address format</h5>
-
 <p>An Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: &lsquo;RPR__WEL&rsquo;. Vector names having only the standard part are not padded.</p>
-
 <p>Categories:</p>
-
 <ul>
-<li><strong>Field</strong> - &lt;VECTOR &lsquo;F&hellip;.&rsquo;&gt;
-
+<li><strong>Field</strong> - &lt;VECTOR &lsquo;F&hellip;.&lsquo;&gt;
 <ul>
 <li>Example: &lsquo;FOPT&rsquo;</li>
-</ul></li>
-<li><strong>Aquifer</strong> - &lt;VECTOR &lsquo;A&hellip;.&rsquo;&gt;:&lt;AQUIFER NUMBER&gt;
-
+</ul>
+</li>
+<li><strong>Aquifer</strong> - &lt;VECTOR &lsquo;A&hellip;.&lsquo;&gt;:&lt;AQUIFER NUMBER&gt;
 <ul>
 <li>Example: &lsquo;AAQR:1&rsquo;</li>
-</ul></li>
-<li><strong>Network</strong> - &lt;VECTOR &lsquo;N&hellip;.&rsquo;&gt;</li>
-<li><strong>Misc</strong> - &lt;VECTOR &lsquo;&hellip;.&rsquo;&gt;</li>
-<li><strong>Region</strong> - &lt;VECTOR &lsquo;R&hellip;.&rsquo;&gt;:&lt;REGION NUMBER&gt;
-
+</ul>
+</li>
+<li><strong>Network</strong> - &lt;VECTOR &lsquo;N&hellip;.&lsquo;&gt;</li>
+<li><strong>Misc</strong> - &lt;VECTOR &lsquo;&hellip;.&lsquo;&gt;</li>
+<li><strong>Region</strong> - &lt;VECTOR &lsquo;R&hellip;.&lsquo;&gt;:&lt;REGION NUMBER&gt;
 <ul>
 <li>Example: &lsquo;RPR:1&rsquo;</li>
-</ul></li>
-<li><strong>Region to Region</strong> - &lt;VECTOR &lsquo;R.F..&rsquo;&gt;:&lt;REGION NUMBER&gt;-&lt;REGION NUMBER&gt;
-
+</ul>
+</li>
+<li><strong>Region to Region</strong> - &lt;VECTOR &lsquo;R.F..&lsquo;&gt;:&lt;REGION NUMBER&gt;-&lt;REGION NUMBER&gt;
 <ul>
 <li>Example: &lsquo;ROFR:1-2&rsquo;</li>
-</ul></li>
-<li><strong>Group</strong> - &lt;VECTOR &lsquo;G&hellip;.&rsquo;&gt;:&lt;GROUP NAME&gt;
-
+</ul>
+</li>
+<li><strong>Group</strong> - &lt;VECTOR &lsquo;G&hellip;.&lsquo;&gt;:&lt;GROUP NAME&gt;
 <ul>
 <li>Example: &lsquo;GOPR:MANI-B1&rsquo;</li>
-</ul></li>
-<li><strong>Well</strong> - &lt;VECTOR &lsquo;W&hellip;.&rsquo;&gt;:&lt;WELL NAME&gt;
-
+</ul>
+</li>
+<li><strong>Well</strong> - &lt;VECTOR &lsquo;W&hellip;.&lsquo;&gt;:&lt;WELL NAME&gt;
 <ul>
 <li>Example: &lsquo;WOPR:B-2H&rsquo;</li>
-</ul></li>
-<li><strong>Completion</strong> - &lt;VECTOR &lsquo;C&hellip;.&rsquo;&gt;:&lt;WELL NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
-
+</ul>
+</li>
+<li><strong>Completion</strong> - &lt;VECTOR &lsquo;C&hellip;.&lsquo;&gt;:&lt;WELL NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
 <ul>
 <li>Example: &lsquo;COFRL:C-1H:26,44,16&rsquo;</li>
-</ul></li>
-<li><strong>LGR Completion</strong> - &lt;VECTOR &lsquo;LC&hellip;&rsquo;&gt;:&lt;LGR NAME&gt;:&lt;WELL NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
-
+</ul>
+</li>
+<li><strong>LGR Completion</strong> - &lt;VECTOR &lsquo;LC&hellip;&lsquo;&gt;:&lt;LGR NAME&gt;:&lt;WELL NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
 <ul>
 <li>Example: &lsquo;LCWIT:WELLI1:I1:5,5,5&rsquo;</li>
-</ul></li>
-<li><strong>LGR Well</strong> - &lt;VECTOR &lsquo;LW&hellip;&rsquo;&gt;:&lt;LGR NAME&gt;:&lt;WELL NAME&gt;
-
+</ul>
+</li>
+<li><strong>LGR Well</strong> - &lt;VECTOR &lsquo;LW&hellip;&lsquo;&gt;:&lt;LGR NAME&gt;:&lt;WELL NAME&gt;
 <ul>
 <li>Example: &lsquo;LWWIR:WELLI1:I1&rsquo;</li>
-</ul></li>
-<li><strong>Segment</strong> - &lt;VECTOR &rsquo;S&hellip;.&lsquo;&gt;:&lt;WELL NAME&gt;:&lt;SEGMENT NUMBER&gt;
-
+</ul>
+</li>
+<li><strong>Segment</strong> - &lt;VECTOR &lsquo;S&hellip;.&lsquo;&gt;:&lt;WELL NAME&gt;:&lt;SEGMENT NUMBER&gt;
 <ul>
 <li>Example: &lsquo;SOFR:B-5H:32&rsquo;</li>
-</ul></li>
-<li><strong>Block</strong> - &lt;Vector &lsquo;B&hellip;.&rsquo;&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
-
+</ul>
+</li>
+<li><strong>Block</strong> - &lt;Vector &lsquo;B&hellip;.&lsquo;&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
 <ul>
 <li>Example: &lsquo;BPR:15,18,21&rsquo;</li>
-</ul></li>
-<li><strong>LGR Block</strong> - &lt;VECTOR &lsquo;LB&hellip;&rsquo;&gt;:&lt;LGR NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
-
+</ul>
+</li>
+<li><strong>LGR Block</strong> - &lt;VECTOR &lsquo;LB&hellip;&lsquo;&gt;:&lt;LGR NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
 <ul>
 <li>Example: &lsquo;LBOSAT:CENTER:5,5,5&rsquo;</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Imported</strong> - &lt;SOME NAME&gt;</li>
 </ul>
-
 <p>When ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the <strong>Imported</strong> category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.</p>
-
-<p><strong>Instantaneous vs Accumulated Data</strong><br />
-A valid Eclipse vector having a standard name ending with &rsquo;T&rsquo; or &lsquo;TH&rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.</p>
-
-<p><strong>Error data</strong><br />
-Any address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by &lsquo;ER:&lsquo;, &lsquo;ERR:&rsquo; or &lsquo;ERROR:&lsquo;. Example: &lsquo;ERR:FOPT&rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.</p>
-
+<p><strong>Instantaneous vs Accumulated Data</strong><br>
+A valid Eclipse vector having a standard name ending with &lsquo;T&rsquo; or &lsquo;TH&rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.</p>
+<p><strong>Error data</strong><br>
+Any address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by &lsquo;ER:', &lsquo;ERR:&rsquo; or &lsquo;ERROR:'. Example: &lsquo;ERR:FOPT&rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.</p>
 <p>Example:</p>
-
-<p><img src="/images/import/ErrorBars.png" alt="" /></p>
-
+<p><img src="/images/import/ErrorBars.png" alt=""></p>
 <h3 id="csv-line-based-format">CSV Line Based Format</h3>
-
 <p>ResInsight supports a &lsquo;line based&rsquo; CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.</p>
-
 <p>When importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:</p>
-
 <ul>
 <li>At least <strong>DATE</strong>, <strong>VECTOR</strong> and <strong>VALUE</strong> columns must be present. The order of columns may be changed.</li>
 <li>Optionally the columns <strong>ERROR</strong> and <strong>COMMENTS</strong> may be present</li>
@@ -1975,41 +1958,24 @@ Any address may have associated error data. Those type of data will have the sam
 <li>Point (.) must be used as decimal separator</li>
 <li>The comment must not contain any semicolons</li>
 </ul>
-
 <h4 id="example">Example</h4>
-
 <p>The two examples below are equvalent and result in identical data after importing to ResInsight</p>
-
 <p>Line based CSV:</p>
-
 <pre><code>DATE       ;VECTOR ;VALUE ;ERROR
 2018-04-16 ;FOPT   ;12.5  ;0.45
 2018-04-18 ;FOPT   ;8.6   ;0.31
-</code></pre>
-
-<p>Normal CSV:</p>
-
+</code></pre><p>Normal CSV:</p>
 <pre><code>DATE       ;FOPT ;ERR:FOPT
 2018-04-16 ;12.5 ;0.45
 2018-04-18 ;8.6  ;0.31
-</code></pre>
-
-<h3 id="import-rsm-observed-time-history-data">Import RSM observed time history data</h3>
-
+</code></pre><h3 id="import-rsm-observed-time-history-data">Import RSM observed time history data</h3>
 <p>To import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the <strong>Observed Time History Data</strong> node in the project tree. RSM files can be either <em>Column based</em> or <em>Keyword based</em>.</p>
-
 <h4 id="column-based-file-format">Column Based File Format</h4>
-
 <p>If a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.</p>
-
 <p>The first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, <em>FVPT</em> and <em>FWPT</em> are of type <em>Field</em>, as they both have an initial <em>F</em>. <em>WWCTH</em> and <em>WGORH</em> are well data types. See <em>Vector naming convention</em> in <strong>Eclipse: File Formats Reference Manual</strong> for a full overview of supported mnemonics.</p>
-
 <p>The next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with <em><em>&ndash;</em></em> will also be ignored.</p>
-
 <h5 id="column-based-with-fixed-header-width">Column Based with Fixed Header Width</h5>
-
 <p>When interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.</p>
-
 <pre><code>1                                                                                                      
  -------------------------------------------------------------------------
  SUMMARY
@@ -2026,12 +1992,8 @@ Any address may have associated error data. Those type of data will have the sam
   9-NOV-1997         0     19.38692     0.015243     14.76847     14.78372  
  10-NOV-1997         0     24.07161     0.018914     18.33751     18.35642
  11-NOV-1997         0     28.79427     0.022613     21.93558     21.95819
-</code></pre>
-
-<h5 id="column-based-with-random-header-width">Column Based with Random Header Width</h5>
-
+</code></pre><h5 id="column-based-with-random-header-width">Column Based with Random Header Width</h5>
 <p>Column Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 <em>probably</em> belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.</p>
-
 <pre><code>TIME      WWCTH      WGORH
 DAYS               SM3/SM3          
 
@@ -2039,12 +2001,8 @@ DAYS               SM3/SM3
      1     0.000   0.000
      2     0.000   0.000
      3     0.000   0.000
-</code></pre>
-
-<h4 id="keyword-based-file-format">Keyword Based File Format</h4>
-
+</code></pre><h4 id="keyword-based-file-format">Keyword Based File Format</h4>
 <p>If the non-comment line includes the word &ldquo;VECTOR&rdquo;, the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, <em>S-1AH-GOR</em> is associated with <em>YEARX</em>, since their origin is equal. ResInsight always interpret <em>ORIGIN</em> as well name, and look for a table with the line &ldquo;VECTOR YEARX&rdquo; to associate with it.</p>
-
 <pre><code>----------------------------------------------
 -- GOR data 
 ----------------------------------------------
@@ -2094,14 +2052,9 @@ UNITS YEAR
 2000.2367
 2000.4033
 2000.4966
-</code></pre>
-
-<p>Please seek &ldquo;User data file formats&rdquo; in <strong>Eclipse: File Formats Reference Manual</strong> for details.</p>
-
+</code></pre><p>Please seek &ldquo;User data file formats&rdquo; in <strong>Eclipse: File Formats Reference Manual</strong> for details.</p>
 <h2 id="viewing-observed-time-history-data">Viewing Observed Time History Data</h2>
-
-<p><img src="/images/import/observedDataCurveCreator.png" alt="" /></p>
-
+<p><img src="/images/import/observedDataCurveCreator.png" alt=""></p>
 <p>To plot Observed Time History Data, choose <strong>New Summary Plot</strong> in the right-click menu of <strong>Summary Plots</strong>, in <strong>Plot Object Project Tree</strong>. Observed time history data will appear in <strong>Sources</strong> together with summary cases. How to use the Plot Editor is covered in <a href="/plot-window/summaryploteditor/">Summary Plot Editor</a>. Observed time history data points are plotted without lines by default.</p>
 
 
@@ -2278,6 +2231,19 @@ UNITS YEAR
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2288,6 +2254,9 @@ UNITS YEAR
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3438,20 +3407,20 @@ UNITS YEAR
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/pasteexceltimedata/index.html b/import/pasteexceltimedata/index.html
index d4ac95ab66..2dd4893fdb 100644
--- a/import/pasteexceltimedata/index.html
+++ b/import/pasteexceltimedata/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Paste Excel Time History Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,12 +1802,9 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#paste-options-dialog">Paste Options Dialog</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#paste-options-dialog">Paste Options Dialog</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1798,16 +1829,10 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>When text have been copied to the operating system&rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the <strong>Plot Main Window Project Tree</strong> and select <strong>Paste Excel Data to Summary Plot</strong>. Then a paste options dialog will appear.</p>
-
 <h2 id="paste-options-dialog">Paste Options Dialog</h2>
-
-<p><img src="/images/import/PasteExcelData.png" alt="" /></p>
-
+<p><img src="/images/import/PasteExcelData.png" alt=""></p>
 <p>Most of the fields in this dialog are the same as in the <a href="/import/observeddata/#csv-txt-import-options-dialog">CSV/txt import options dialog</a>. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:</p>
-
 <ul>
 <li><strong>Curve Prefix</strong> &ndash; Curve name prefix for all curves created from the pasted data.</li>
 <li><strong>Line Style</strong> &ndash; Line style to use for the curves created from the pasted data.</li>
@@ -1989,6 +2014,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1999,6 +2037,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3149,20 +3190,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/soursimrlresults/index.html b/import/soursimrlresults/index.html
index e6ecfe0789..4eb6886abc 100644
--- a/import/soursimrlresults/index.html
+++ b/import/soursimrlresults/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>SourSimRL Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1791,12 +1825,10 @@ if (!doNotTrack) {
 
 
 
-<p>ResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization.
+<p>ResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization. 
 Results from SourSimRL in its <em>sourres</em> binary format can be imported using the <strong>SourSim File Name</strong> field as shown below:</p>
-
-<p><img src="/images/import/soursim_import.PNG" alt="" /></p>
-
-<p>Importing such a file will enable result type called <strong>SourSimRL</strong> as explained in <a href="/3d-main-window/cellresults/#eclipse-result-types">Eclipse Result Types</a></p>
+<p><img src="/images/import/soursim_import.PNG" alt=""></p>
+<p>Importing such a file will enable result type called <strong>SourSimRL</strong> as explained in <a href="/3d-main-window/cellresults/">Eclipse Result Types</a></p>
 
 
 <footer class=" footline" >
@@ -1972,6 +2004,19 @@ Results from SourSimRL in its <em>sourres</em> binary format can be imported usi
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1982,6 +2027,9 @@ Results from SourSimRL in its <em>sourres</em> binary format can be imported usi
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3132,20 +3180,20 @@ Results from SourSimRL in its <em>sourres</em> binary format can be imported usi
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/index.html b/index.html
index e0d3c50f10..ea7ea9e520 100644
--- a/index.html
+++ b/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>ResInsight :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1742,69 +1776,13 @@ if (!doNotTrack) {
 </span>
 
  
-
-
-<p><title>ResInsight • 3D viewer and post processing of reservoir models</title></p>
-
+<!-- raw HTML omitted -->
 <h1 id="post-processing-of-reservoir-simulations">Post Processing of Reservoir Simulations</h1>
-
-<p><img src="/images/FrontPageImage.png" alt="" /></p>
-
-<!--
-<section class="intro">
-  <div class="grid">
-    <div class="unit whole center-on-mobiles">
-      <p class="first">Post Processing of Reservoir Simulations</p>
-    </div>
-    <div class="post-content">
-      <img src="/images/FrontPageImage.png" alt="Reservoir" />
-    </div>
-  </div>
-</section> -->
-
-<section class="features">
-  <div class="grid">
-    <div class="unit one-third">
-      <h3>Fast and Free</h3>
-      <p>
-        &#x2713; Open source<br>
-        &#x2713; Efficient user interface<br>
-    &#x2713; Handles large Eclipse cases<br>
-        &#x2713; Plotting of summary vectors<br>
-    &#x2713; Embedded Flow Diagnostics<br>
-      </p>
-    </div>
-    <div class="unit one-third">
-      <h3>Unique Features</h3>
-      <p>
-        &#x2713; NNC visualization<br>
-        &#x2713; Cell Edge Coloring<br>
-        &#x2713; Detailed MSW visualization<br>
-        &#x2713; Seamless <a href="http://www.gnu.org/software/octave/"> Octave</a> integration<br>
-        &#x2713; Supports geomechanical ABAQUS simulations<br>
-      </p>
-    </div>
-    <div class="unit one-third">
-      <h3>Getting started</h3>
-      <p>
-        It's easy and free, both on Linux and Windows:
-      </p>
-      <a href="/getting-started/download-and-install/">Download and Install &rarr;</a><br>
-      <a href="/getting-started/">Getting Started &rarr;</a>
-      <p>Sign up to be notified of new releases:
-        <br>
-        <a href="/getting-started/other/releasenotification/">Release Notification &rarr;</a>
-      </p>
-      </div>
-    <div class="clear"></div>
-  </div>
-
-  <div class="grid">
-    <div class="unit whole center-on-mobiles">
-      <p>Here are some words from a few of the happy ResInsight users <a href="/getting-started/other/testimonials/">Testimonials &rarr;</a> </p>
-    </div>
-  </div>
-</section>
+<p><img src="/images/FrontPageImage.png" alt=""></p>
+<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
 	
   
         
@@ -1975,6 +1953,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1985,6 +1976,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3125,20 +3119,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/index.xml b/index.xml
index 3bb112cc62..3fc750c07d 100644
--- a/index.xml
+++ b/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>ResInsight</title>
@@ -51,7 +51,7 @@ Several views can be added to the same case by right-clicking the case or a view
       <guid>https://resinsight.org/getting-started/download-and-install/linux-installation/</guid>
       <description>Install ResInsight From Binary Packages on Linux Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.
 Red Hat Enterprise Linux 6 or 7 Login as root and do:
-yum-config-manager --add-repo https://opm-project.org/package/opm.repo yum install resinsight yum install resinsight-octave  Then you are good, and can start ResInsight by typing: ResInsight
+yum-config-manager --add-repo https://opm-project.org/package/opm.repoyum install resinsightyum install resinsight-octave Then you are good, and can start ResInsight by typing: ResInsight
 Ubuntu Linux 16.04-64bit On the command line do:</description>
     </item>
     
@@ -104,7 +104,7 @@ If you have many open plots, it can be useful to collapse all other plots by act
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_04/</guid>
       <description>ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.
-Grid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot.</description>
+Grid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.</description>
     </item>
     
     <item>
@@ -115,7 +115,7 @@ Grid Cross Plots ResInsight supports the creation of cross plots of two results
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_08/</guid>
       <description>ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.
 Python scripting Basic example on how to update views from Python
-import rips # Connect to ResInsight instance resInsight = rips.Instance.find() # Check if connection worked if resInsight is not None: # Get a list of all cases cases = resInsight.</description>
+import rips# Connect to ResInsight instanceresInsight = rips.Instance.find()# Check if connection workedif resInsight is not None:# Get a list of all casescases = resInsight.</description>
     </item>
     
     <item>
@@ -125,7 +125,7 @@ import rips # Connect to ResInsight instance resInsight = rips.Instance.find() #
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2019_12/</guid>
       <description>ResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12 is a major update bringing a range of significant new and enhanced features. Some of the most important extensions are listed below.
-Comparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more.</description>
+Comparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view.</description>
     </item>
     
     <item>
@@ -172,7 +172,7 @@ Cell Results are used in several operations and settings:
       <description>ResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.
 Command line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for Command Line Interfaces.
 Examples on how command line options are used are given below
-Command line options General    Parameter Description     &amp;#45;&amp;#45;help, &amp;#45;&amp;#45;?</description>
+Command line options General    Parameter Description     --help, --?</description>
     </item>
     
     <item>
@@ -272,7 +272,7 @@ Importing such a file will enable result type called SourSimRL as explained in E
 In a git enabled shell do: git clone https://github.com/OPM/ResInsight.git
 Dependencies and Prerequisites Windows Compiler Visual Studio 2015 and later is supported.
 GCC Compiler GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with
-source /opt/rh/devtoolset-3/enable  Qt5 Qt Qt5 version 5.6.0 or later is supported.
+source /opt/rh/devtoolset-3/enable Qt5 Qt Qt5 version 5.6.0 or later is supported.
 On some configurations you will be asked to specify the location of Qt5.</description>
     </item>
     
@@ -338,7 +338,7 @@ Other available keyboard shortcuts are
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/getting-started/modelnavigation/</guid>
-      <description>ResInsight comes with four navigation modes. The active mode can be selected in the Preferences dialog.
+      <description>ResInsight comes with four navigation modes. The active mode can be selected in the [Preferences dialog] (/misc/preferences/).
 Note that changing the navigation mode applies to the currently active view only, and views created after the change.
 These abbreviations are used in the tables below:
    Abbreviation Meaning     LMB Press the left mouse button   MMB Press the middle mouse button or scroll wheel button   RMB Press the right mouse button    The following applies to all navigation modes:</description>
@@ -373,7 +373,7 @@ Import Observed Time History Data Importing observed time history data to ResIns
       <guid>https://resinsight.org/plot-window/summaryploteditor/</guid>
       <description>The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.
 The upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the Summary Type currently highlighted.
-In this context highlighted means the marked item with a different background color, while selected means an item or items that have a ticked check box.</description>
+In this context highlightedmeans the marked item with a different background color, while selectedmeans an item or items that have a ticked check box.</description>
     </item>
     
     <item>
@@ -383,7 +383,7 @@ In this context highlighted means the marked item with a different background co
       
       <guid>https://resinsight.org/3d-main-window/comparisonview/</guid>
       <description>ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.
-The figure above exemplifies a Comparison View for comparison of two different simulations models and results.</description>
+The figure above exemplifies a Comparison View for comparison of two different simulations models and results. The left hand side is used to display grid and results of an Eclipse simulation while the right hand side displays an ABAQUS grid and simulation results from geomechanical analysis.</description>
     </item>
     
     <item>
@@ -421,7 +421,7 @@ Creating new 3D Well Log Curves Add a new 3D well log curve by selecting a Well
       
       <guid>https://resinsight.org/import/pasteexceltimedata/</guid>
       <description>When text have been copied to the operating system&amp;rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the Plot Main Window Project Tree and select Paste Excel Data to Summary Plot. Then a paste options dialog will appear.
-Paste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog.</description>
+Paste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog. Please see that section for documentation on those fields.</description>
     </item>
     
     <item>
@@ -431,7 +431,7 @@ Paste Options Dialog Most of the fields in this dialog are the same as in the CS
       
       <guid>https://resinsight.org/scripting/pythonexamples/</guid>
       <description>This pages is created based on the content in the PythonExamples folder located inside the rips module, made available online for convenience.
-AllCases ################################################################################### # This example will connect to ResInsight, retrieve a list of cases and print info # ################################################################################### # Import the ResInsight Processing Server Module import rips # Connect to ResInsight resinsight = rips.Instance.find() if resinsight is not None: # Get a list of all cases cases = resinsight.</description>
+AllCases #################################################################################### This example will connect to ResInsight, retrieve a list of cases and print info# #################################################################################### Import the ResInsight Processing Server Moduleimport rips# Connect to ResInsightresinsight = rips.Instance.find()if resinsight is not None:# Get a list of all casescases = resinsight.</description>
     </item>
     
     <item>
@@ -451,8 +451,7 @@ AllCases #######################################################################
       
       <guid>https://resinsight.org/getting-started/other/releasenotification/</guid>
       <description>LinkedIn Feel free to join ResInsight on LinkedIn
-Newsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.
-Subscribe</description>
+Newsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.</description>
     </item>
     
     <item>
@@ -473,10 +472,10 @@ Subscribe</description>
       <guid>https://resinsight.org/scripting/pythonrips/</guid>
       <description>Instance Module class rips.instance.Instance(port=50051, launched=False) The ResInsight Instance class. Use to launch or find existing ResInsight instances
 launched() Tells us whether the application was launched as a new process. If the application was launched we may need to close it when exiting the script.
- Type
+  Type
 bool
   commands() Command executor. Set when creating an instance.
- Type
+  Type
 Commands
   project() Current project in ResInsight. Set when creating an instance and updated when opening/closing projects.</description>
     </item>
@@ -530,9 +529,8 @@ Import There are several ways to import an ensemble:
       
       <guid>https://resinsight.org/scripting/octaveinterface/</guid>
       <description>ResInsight provides a flexible interface to Octave including:
- Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.
-  The Octave functions are documented in Octave Interface Reference.
-Note: The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.
+ Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.  The Octave functions are documented in Octave Interface Reference.
+Note:The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.
 Octave Script Management Octave scripts are available in the Scripts folder in the Project Tree.</description>
     </item>
     
@@ -587,7 +585,8 @@ Calculation Settings To make a new calculated curve, click on New Calculation. T
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/scripting/octaveinterfacereference/</guid>
-      <description>Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the &amp;ldquo;Current Case&amp;rdquo;), or the script is designed to access the selection and traverse the cases by itself.</description>
+      <description>Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the &amp;ldquo;Current Case&amp;rdquo;), or the script is designed to access the selection and traverse the cases by itself.
+Note:The Octave interface does not support Geomechanical cases and flow diagnostic results.</description>
     </item>
     
     <item>
@@ -597,7 +596,7 @@ Calculation Settings To make a new calculated curve, click on New Calculation. T
       
       <guid>https://resinsight.org/3d-main-window/resultinspection/</guid>
       <description>The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. The selected cells will be highlighted, text information displayed in the Result Info docking window, and the time-history values plotted in the Result Plot, if available.
-Visibility of the docking widows can be controlled from the Windows menu.
+Visibility of the docking widows can be controlled from the Windowsmenu.
 Result Info Clicking cells will display slightly different information text based on the case type as described in the following tables.</description>
     </item>
     
@@ -619,9 +618,9 @@ Exporting Grid and Faults Grid Export The Export dialog will allow the user to e
       
       <guid>https://resinsight.org/getting-started/other/testimonials/</guid>
       <description>“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”
-David Baxendale
-Senior Petroleum Engineering Advisor, RPS Energy
-&amp;ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&amp;rdquo;</description>
+David BaxendaleSenior Petroleum Engineering Advisor, RPS Energy
+&amp;ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.&amp;quot;
+Tor Harald SandveResearcher, International Research Institute of Stavanger (IRIS)</description>
     </item>
     
     <item>
@@ -631,8 +630,7 @@ Senior Petroleum Engineering Advisor, RPS Energy
       
       <guid>https://resinsight.org/3d-main-window/filters/</guid>
       <description>Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:
- Range Filter &amp;ndash; Extracts an IJK subset of the model. Property Filter &amp;ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from  Simulation Wells .
-(Not applicable for Geomechanical cases)</description>
+ Range Filter &amp;ndash; Extracts an IJK subset of the model. Property Filter &amp;ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from Simulation Wells.(Not applicable for Geomechanical cases)Common Properties for Range and Property Filters Both filter types can be turned on or off using the toggle in the Project Tree and controlled from their corresponding Property Editor.</description>
     </item>
     
     <item>
@@ -654,7 +652,7 @@ A new plot with a single Track and Curve is created matching active case and sel
       
       <guid>https://resinsight.org/3d-main-window/intersections/</guid>
       <description>Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.
-There are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line.</description>
+There are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate 2D Intersection View</description>
     </item>
     
     <item>
@@ -759,7 +757,7 @@ Grid Statistics Dialog Fields The dialog consist of three information parts.
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/3d-main-window/casegroupsandstatistics/</guid>
-      <description>Grid Case Group&amp;rsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).
+      <description>Grid Case Group&amp;lsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).
 If you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.</description>
     </item>
     
@@ -810,7 +808,7 @@ When ResInsight is in measurement mode, clicking on an surface in the 3D view wi
       
       <guid>https://resinsight.org/3d-main-window/annotations/</guid>
       <description>ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.
- Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file   Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree).</description>
+ Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file    Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree).</description>
     </item>
     
     <item>
@@ -830,7 +828,7 @@ Transmissibility Normalized by Area The transmissibility for cells and Non-Neigh
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/_footer/</guid>
-      <description> About Ceetron Solutions in collaboration with Equinor ASA Support </description>
+      <description>About Ceetron Solutions in collaboration with Equinor ASA Support </description>
     </item>
     
     <item>
@@ -859,7 +857,7 @@ Efficient User Interface The user interface is tailored for efficient interpreta
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/search/</guid>
-      <description>Search for: window.store = [];window.store[&#34;/getting-started/overview/&#34;] = {title: &#34;Overview&#34;,content: &#34; User Interface ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\n3D Main Window Plot Main Window Switching Between the Two Main Windows The two main windows has a toolbar button each, that directly opens and raises the other window. Each of the windows can also be closed freely, but if both are closed, ResInsight exits.</description>
+      <description>Search for: window.store = [];window.store[&#34;/getting-started/overview/&#34;] = {title: &#34;Overview&#34;,content: &#34;User Interface ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\n3D Main Window Plot Main Window Switching Between the Two Main Windows The two main windows has a toolbar button each, that directly opens and raises the other window. Each of the windows can also be closed freely, but if both are closed, ResInsight exits.</description>
     </item>
     
     <item>
@@ -871,8 +869,7 @@ Efficient User Interface The user interface is tailored for efficient interpreta
       <description>For inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.
 Phone : +47 73 60 43 00 e-mail : info@ceetronsolutions.com
 Bug reports and general feature requests can be filed directly on GitHub
-
-Ceetron Solutions AS - Digitalization and visualization for engineers</description>
+Ceetron Solutions AS - Digitalization and visualization for engineers </description>
     </item>
     
   </channel>
diff --git a/misc/index.html b/misc/index.html
index ef8933a158..5caaa8fc10 100644
--- a/misc/index.html
+++ b/misc/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Miscellaneous :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,17 +1820,14 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/3d-main-window/MemoryManagementBanner.png" alt="" /></p>
-
+	<p><img src="/images/3d-main-window/MemoryManagementBanner.png" alt=""></p>
 <p>This chapter of the ResInsight documentation describes the following:</p>
-
 <ul>
 <li>defining preferences to customize and adapt the behavior of ResInsight for your purposes and work flow</li>
 <li>memory management, i.e. how to determine consumption and clearing data from computer memory</li>
 <li>keyboard shortcuts for effective and convenient usage of ResInsight</li>
 <li>use of the built-in regression test system of ResInsight</li>
 </ul>
-
 <p>See the subsequent subchapters for more information on each topic.</p>
 
 
@@ -1975,6 +2006,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1985,6 +2029,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3131,20 +3178,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/index.xml b/misc/index.xml
index a1e22d8760..ccb24a5ed3 100644
--- a/misc/index.xml
+++ b/misc/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Miscellaneous on ResInsight</title>
diff --git a/misc/keyboardshortcuts/index.html b/misc/keyboardshortcuts/index.html
index b98f66a133..ff2163fbb7 100644
--- a/misc/keyboardshortcuts/index.html
+++ b/misc/keyboardshortcuts/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Keyboard Shortcuts :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1793,13 +1827,10 @@ if (!doNotTrack) {
 
 <p>ResInsight supports a selection of Keyboard Shortcuts for convenience. These include <strong>Delete</strong> for removing deletable items
 from the project tree, <strong>Ctrl-Alt-A</strong> for Zoom All and <strong>Ctrl-Alt-S/N/W/E/D/U</strong> for changing the camera view to South, North, West, East, Down and Up respectively.</p>
-
-<p><img src="/images/3d-main-window/KeyboardDel.png" alt="" />
-<img src="/images/3d-main-window/KeyboardEast.png" alt="" />
-<img src="/images/3d-main-window/KeyboardPlot.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/KeyboardDel.png" alt="">
+<img src="/images/3d-main-window/KeyboardEast.png" alt="">
+<img src="/images/3d-main-window/KeyboardPlot.png" alt=""></p>
 <p>Other available keyboard shortcuts are</p>
-
 <ul>
 <li><strong>Ctrl-Shift-P</strong> for opening up the plot window when you are in the 3d View</li>
 <li><strong>Ctrl-Shift-3</strong> for opening up the 3d View while you are in the Plot Window</li>
@@ -1985,6 +2016,19 @@ from the project tree, <strong>Ctrl-Alt-A</strong> for Zoom All and <strong>Ctrl
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1995,6 +2039,9 @@ from the project tree, <strong>Ctrl-Alt-A</strong> for Zoom All and <strong>Ctrl
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3145,20 +3192,20 @@ from the project tree, <strong>Ctrl-Alt-A</strong> for Zoom All and <strong>Ctrl
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/memorymanagement/index.html b/misc/memorymanagement/index.html
index 5c71390d4f..d2a5890957 100644
--- a/misc/memorymanagement/index.html
+++ b/misc/memorymanagement/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Memory Management :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,13 +1802,10 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#memory-indicator">Memory Indicator</a></li>
-<li><a href="#memory-management-tool">Memory Management Tool</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#memory-indicator">Memory Indicator</a></li>
+    <li><a href="#memory-management-tool">Memory Management Tool</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1799,27 +1830,16 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/MemoryManagementBanner.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/MemoryManagementBanner.png" alt=""></p>
 <p>ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. If the requirements starts approaching the available physical memory on the workstation, ResInsight may become unstable and crash, as the operating system starts freeing memory to avoid system failure. To help alleviate this, ResInsight has some built-in memory management tools.</p>
-
 <h2 id="memory-indicator">Memory Indicator</h2>
-
 <p>The tools are available from the memory indicator in the bottom right corner of the main 3D window.</p>
-
-<p><img src="/images/3d-main-window/MemoryIndicator.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/MemoryIndicator.png" alt=""></p>
 <p>If the available physical memory dips below 5% of the total physical memory on Windows, a warning will be displayed in the memory indicator. This threshold is 17.5% on Linux, as the memory manager on Linux is more likely to start stopping processes when memory is low. The amount of memory used will also be displayed in progress bars during operations in ResInsight if the available memory is less than 50% of total physical memory. In any case, ResInsight is likely to be stopped without warning by the operating system if the amount of used memory starts approaching the total physical memory on the computer.</p>
-
 <h2 id="memory-management-tool">Memory Management Tool</h2>
-
 <p>It is possible to click on the memory used indicator to open up a dialog allowing the user to clear results from memory when they are no longer required. Any tool that is not currently used in a view may be cleared by selecting the result and clicking the <strong>Clear Checked Data From Memory</strong>. Note that, dependending on your operating system, this may not result in a reduction in the memory reserved by the application. However, the actual use will have gone down and it may now be possible to run more operations without running out of memory.</p>
-
 <p>By default, results will be shown for the active case. However, a specific case may be selected in the top drop down list. The pictures below show the dialog for both Eclipse and Abaqus results.</p>
-
-<p><img src="/images/3d-main-window/MemoryTool.png" alt="" /> <img src="/images/3d-main-window/MemoryToolGeoMech.png" alt="" /></p>
+<p><img src="/images/3d-main-window/MemoryTool.png" alt=""> <img src="/images/3d-main-window/MemoryToolGeoMech.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -1995,6 +2015,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2005,6 +2038,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3155,20 +3191,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/preferences/index.html b/misc/preferences/index.html
index 369851e46a..a4c69b8455 100644
--- a/misc/preferences/index.html
+++ b/misc/preferences/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Preferences :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,31 +1802,31 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#general-tab">General - tab</a>
-<ul>
-<li><a href="#default-colors">Default Colors</a></li>
-<li><a href="#default-font-sizes">Default Font Sizes</a></li>
-<li><a href="#3d-views">3D Views</a></li>
-<li><a href="#other">Other</a></li>
-</ul></li>
-<li><a href="#eclipse-tab">Eclipse - tab</a>
-<ul>
-<li><a href="#behavior-when-loading-data">Behavior When Loading Data</a></li>
-<li><a href="#origin-files">Origin Files</a></li>
-</ul></li>
-<li><a href="#plotting-tab">Plotting - tab</a></li>
-<li><a href="#scripting-tab">Scripting - tab</a>
-<ul>
-<li><a href="#octave">Octave</a></li>
-<li><a href="#python">Python</a></li>
-<li><a href="#script-files">Script Files</a></li>
-</ul></li>
-<li><a href="#export-tab">Export - tab</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#general---tab">General - tab</a>
+      <ul>
+        <li><a href="#default-colors">Default Colors</a></li>
+        <li><a href="#default-font-sizes">Default Font Sizes</a></li>
+        <li><a href="#3d-views">3D Views</a></li>
+        <li><a href="#other">Other</a></li>
+      </ul>
+    </li>
+    <li><a href="#eclipse---tab">Eclipse - tab</a>
+      <ul>
+        <li><a href="#behavior-when-loading-data">Behavior When Loading Data</a></li>
+        <li><a href="#origin-files">Origin Files</a></li>
+      </ul>
+    </li>
+    <li><a href="#plotting---tab">Plotting - tab</a></li>
+    <li><a href="#scripting---tab">Scripting - tab</a>
+      <ul>
+        <li><a href="#octave">Octave</a></li>
+        <li><a href="#python">Python</a></li>
+        <li><a href="#script-files">Script Files</a></li>
+      </ul>
+    </li>
+    <li><a href="#export---tab">Export - tab</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1817,46 +1851,30 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>In this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the <strong>Preference</strong> dialog available from the <strong>Edit -&gt; Preferences</strong> menu.</p>
-
-<p><img src="/images/3d-main-window/Preferences.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Preferences.png" alt=""></p>
 <p>When changing the preferences, any default color, font or Z-scale Factor that has not been changed by the user in the various views, will be applied immediately. If the user has changed font sizes in specific plots or annotations from the default value, ResInsight will ask if the user wants the new defaults applied to all existing views and plots even where custom settings have been set.</p>
-
-<p><img src="/images/3d-main-window/Preferences_ApplyToAll.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Preferences_ApplyToAll.png" alt=""></p>
 <p>The preferences are not stored in the project files, but rather in a platform specific way for each user.</p>
-
-<h2 id="general-tab">General - tab</h2>
-
+<h2 id="general---tab">General - tab</h2>
 <h3 id="default-colors">Default Colors</h3>
-
 <p>This group contains the colors that will be applied to the 3D views.</p>
-
 <ul>
 <li><strong>Viewer Background</strong></li>
 <li><strong>Mesh Color</strong></li>
 <li><strong>Mesh Color Along Faults</strong></li>
 <li><strong>Well Label Color</strong></li>
 </ul>
-
 <h3 id="default-font-sizes">Default Font Sizes</h3>
-
 <p>This group contains the different fonts which are used through ResInsight.</p>
-
 <ul>
 <li><strong>Viewer Font Size</strong> &ndash; The fonts used for axes labels, legends and info boxes in the 3d View.</li>
 <li><strong>Annotation Font Size</strong> &ndash; The font used as default for Text Annotations.</li>
 <li><strong>Well Label Font Size</strong> &ndash; The font used for all Well Path labels.</li>
 <li><strong>Plot Font Size</strong> - The font used for legends, axes labels, values in Plots. This affects the docked plots in the main 3D window as well (Result Plot, Relative Permeability etc), although because of the reduces space available in these plots, the font size applied will be one less than the <strong>Plot Font Size</strong>.</li>
 </ul>
-
 <h3 id="3d-views">3D Views</h3>
-
 <p>This group of options controls visual settings that will be used when creating new views.</p>
-
 <ul>
 <li><strong>Show Grid Lines</strong> &ndash; Controls whether to show the grid lines by default for all cells or just along faults.</li>
 <li><strong>Navigation mode</strong> &ndash; Defines how to use the mouse to interact with with the 3D model. Please refer to <a href="/getting-started/modelnavigation/">Model Navigation</a> for details.</li>
@@ -1865,22 +1883,16 @@ if (!doNotTrack) {
 <li><strong>Use shaders</strong> &ndash; This option controls the use of OpenGL shaders. Should be left <strong>On</strong>. Available only for testing purposes.</li>
 <li><strong>Show 3D Information</strong> &ndash; Displays graphical resource usage as text in the 3D view.</li>
 </ul>
-
 <h3 id="other">Other</h3>
-
 <ul>
 <li><strong>Date Format</strong> &ndash; Defines the date format to be used in time legend plotting</li>
 <li><strong>Time Format</strong> &ndash; Defines the time format to be used in time legend plotting</li>
 <li><strong>SSIHUB Address</strong> &ndash; Optional URL to Equinor internal web service used to import well paths</li>
 <li><strong>Show LAS Curve Without TVD Warning</strong> - Turn off the warning displayed when showing LAS curves in TVD mode</li>
 </ul>
-
-<h2 id="eclipse-tab">Eclipse - tab</h2>
-
-<p><img src="/images/3d-main-window/EclipsePreferences.png" alt="" /></p>
-
+<h2 id="eclipse---tab">Eclipse - tab</h2>
+<p><img src="/images/3d-main-window/EclipsePreferences.png" alt=""></p>
 <h3 id="behavior-when-loading-data">Behavior When Loading Data</h3>
-
 <ul>
 <li><strong>Compute DEPTH Related Properties</strong> &ndash; If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases.</li>
 <li><strong>Load and Show SOIL</strong> &ndash; Control if SOIL is loaded and applied to grid.</li>
@@ -1889,15 +1901,10 @@ if (!doNotTrack) {
 <li><strong>Use Result Index File</strong> &ndash; If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the <em><code>*.EGRID</code></em> file with filename <em><code>&lt;casename&gt;.RESINSIGHT_IDX</code></em> If it exists, ResInsight will use this when loading the case, resulting in a significant speedup.</li>
 <li><strong>Skip Import of Simulation Well Data</strong> &ndash; Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).</li>
 </ul>
-
 <h3 id="origin-files">Origin Files</h3>
-
-<p>Please refer to <a href="/plot-window/summaryplots/#origin-files">Summary Origin</a> for details related to handling of <strong>Origin Files</strong>.</p>
-
-<h2 id="plotting-tab">Plotting - tab</h2>
-
-<p><img src="/images/misc/PreferencesPlotting.png" alt="" /></p>
-
+<p>Please refer to <a href="/plot-window/summaryplots/">Summary Origin</a> for details related to handling of <strong>Origin Files</strong>.</p>
+<h2 id="plotting---tab">Plotting - tab</h2>
+<p><img src="/images/misc/PreferencesPlotting.png" alt=""></p>
 <ul>
 <li><strong>Default Summary Curves</strong>: Defines default curves for import when creating a new summary plot, e.g. <code>FOPT WOPT*</code></li>
 <li><strong>Default Curve Style for History Vectors</strong>: allows specifying <em>symbols</em> and/or <em>lines</em> as preference.</li>
@@ -1905,47 +1912,34 @@ if (!doNotTrack) {
 <li><strong>Show resample time text</strong> preference</li>
 <li><strong>Use multiple threads</strong> preference which may improve performance when loading summary data</li>
 <li><strong>Plot Templates</strong> allows setting preferences for:
-
 <ul>
 <li><em>Plot Template Folder(s)</em>: Allows to enter and delete folder(s) that are searched for plot templates. Press <em>Append</em> to browse for folder to append.</li>
 <li>Checking <em>Search Plot Templates Recursively</em> instructs ResInsight to search subdirectories of specified folder(s) for templates.</li>
-</ul></li>
 </ul>
-
-<h2 id="scripting-tab">Scripting - tab</h2>
-
-<p><img src="/images/3d-main-window/Preferences_Scripting.png" alt="" /></p>
-
+</li>
+</ul>
+<h2 id="scripting---tab">Scripting - tab</h2>
+<p><img src="/images/3d-main-window/Preferences_Scripting.png" alt=""></p>
 <h3 id="octave">Octave</h3>
-
 <ul>
 <li><strong>Octave Executable Location</strong> &ndash; Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows.</li>
 <li><strong>Show text header when executing scripts</strong> &ndash; Enables the default output that octave outputs when started.</li>
 </ul>
-
 <p>Please refer to <a href="/scripting/octaveinterface/">Octave Interface</a> for more details.</p>
-
 <h3 id="python">Python</h3>
-
 <ul>
 <li><strong>Enable Python Script Server</strong></li>
 <li><strong>Default Python Script Server Port</strong> &ndash; Defines the port used for communication with Python scripts</li>
 <li><strong>Python Executable Location</strong></li>
 </ul>
-
 <p>Please refer to <a href="/scripting/pythonrips/">Python API</a> for more details.</p>
-
 <h3 id="script-files">Script Files</h3>
-
 <ul>
 <li><strong>Shared Script Folder(s)</strong> &ndash; Defines the search paths for octave scripts</li>
 <li><strong>Script Editor</strong> &ndash; The text editor to invoke when editing scripts</li>
 </ul>
-
-<h2 id="export-tab">Export - tab</h2>
-
-<p><img src="/images/3d-main-window/Preferences_Export.png" alt="" /></p>
-
+<h2 id="export---tab">Export - tab</h2>
+<p><img src="/images/3d-main-window/Preferences_Export.png" alt=""></p>
 <ul>
 <li><strong>CSV Text Export Field Separator</strong></li>
 </ul>
@@ -2124,6 +2118,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2134,6 +2141,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3281,20 +3291,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/regressiontestsystem/index.html b/misc/regressiontestsystem/index.html
index 8182137116..43f50e9d5b 100644
--- a/misc/regressiontestsystem/index.html
+++ b/misc/regressiontestsystem/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Regression Test System :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,13 +1802,10 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#how-to-run-regression-tests">How to Run Regression Tests</a></li>
-<li><a href="#creating-regression-tests">Creating Regression Tests</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#how-to-run-regression-tests">How to Run Regression Tests</a></li>
+    <li><a href="#creating-regression-tests">Creating Regression Tests</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1799,34 +1830,22 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>A regression tool for QA is build into ResInsight. This tool will do the following:</p>
-
 <ol>
 <li>Scan a directory for sub directories containing a <strong>RegressionTest.rsp</strong> files.</li>
 <li>Each found project file will be opened, and all views in this project will be exported as snapshot images to file.</li>
 <li>When snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed.</li>
 <li>Based on these three sets of images, an HTML report is created and automatically displayed.</li>
 </ol>
-
 <h2 id="how-to-run-regression-tests">How to Run Regression Tests</h2>
-
 <p>To be able to run regression tests you need the <strong>compare</strong> tool from the <a href="http://www.imagemagick.org/script/compare.php">ImageMagic suite</a>.</p>
-
 <p>You can start the tests either from the command line or from the ResInsight Gui.
 From the ResInsight Gui select : <strong>File-&gt;Testing-&gt;Regression Test Dialog</strong></p>
-
-<p><img src="/images/appendix/RegressionTestDialog.png" alt="" /></p>
-
+<p><img src="/images/appendix/RegressionTestDialog.png" alt=""></p>
 <p>Specify location of compare tool in <strong>Folder containing compare</strong>. The current working directory of ResInsight is temporarily changed to this path during execution.</p>
-
 <p>To execute a subset of tests, specify folder names separated by &ldquo;;&rdquo; in the <em>Test Filter</em>. If the test filter is empty, all tests are executed.</p>
-
 <h2 id="creating-regression-tests">Creating Regression Tests</h2>
-
 <p>An example of the folder structure is shown below:</p>
-
 <pre><code>RegressionTestFolder/
   TestCase1/
     RegressionTest.rip
@@ -1836,16 +1855,13 @@ From the ResInsight Gui select : <strong>File-&gt;Testing-&gt;Regression Test Di
   TestCase2/
     ...
 </code></pre>
-
 <p>To create regression tests you need to do the following:</p>
-
 <ol>
 <li>Create a root directory containing one directory for each test case.</li>
 <li>In each of the <strong>Test Case</strong> folders create a ResInsight project file called <strong>RegressionTest.rip</strong>.</li>
 <li>Run the regression test for the first time, and thereby creating images that can be used as Base images.</li>
 <li>Rename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/</li>
 </ol>
-
 <p>Now you are all set to test new releases of ResInsight towards your own Regression tests.</p>
 
 
@@ -2022,6 +2038,19 @@ From the ResInsight Gui select : <strong>File-&gt;Testing-&gt;Regression Test Di
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2032,6 +2061,9 @@ From the ResInsight Gui select : <strong>File-&gt;Testing-&gt;Regression Test Di
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3179,20 +3211,20 @@ From the ResInsight Gui select : <strong>File-&gt;Testing-&gt;Regression Test Di
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/curvecalculator/index.html b/plot-window/curvecalculator/index.html
index 2daea5081f..23705857a4 100644
--- a/plot-window/curvecalculator/index.html
+++ b/plot-window/curvecalculator/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Curve Calculator :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,25 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#calculation-settings">Calculation Settings</a>
-<ul>
-<li><a href="#operators-and-functions">Operators and Functions</a>
-<ul>
-<li><a href="#assignment-operators">Assignment Operators</a></li>
-<li><a href="#basic-operators">Basic Operators</a></li>
-<li><a href="#scalar-functions">Scalar Functions</a></li>
-<li><a href="#trigonometry-functions">Trigonometry Functions</a></li>
-<li><a href="#vector-functions">Vector Functions</a></li>
-</ul></li>
-<li><a href="#unit">Unit</a></li>
-</ul></li>
-<li><a href="#summary-address-selection">Summary Address Selection</a></li>
-<li><a href="#generating-curves">Generating Curves</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#calculation-settings">Calculation Settings</a>
+      <ul>
+        <li><a href="#operators-and-functions">Operators and Functions</a></li>
+        <li><a href="#unit">Unit</a></li>
+      </ul>
+    </li>
+    <li><a href="#summary-address-selection">Summary Address Selection</a></li>
+    <li><a href="#generating-curves">Generating Curves</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1811,25 +1836,15 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/SummaryCurveCalculator.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCurveCalculator.png" alt=""></p>
 <p>The summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.</p>
-
 <p>The calculator can be run by pressing the calculator icon <img src="https://resinsight.org/images/plot-window/calculator.png" style="display:inline; vertical-align:middle; margin:0">
  in the menu bar, or by right-clicking on either a summary case or the summary plot collection.</p>
-
 <h2 id="calculation-settings">Calculation Settings</h2>
-
 <p>To make a new calculated curve, click on <strong>New Calculation</strong>. This will add a new calculation to <strong>Calculated Summaries</strong>. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression <em>Calculation_1 := x + y</em> will do a vector addition on the curves which <em>x</em> and <em>y</em> are placeholders for, and assign it to the calculation <em>Calculation_1</em>. How to assign curves to assign to <em>x</em> and <em>y</em> will be covered in section <a href="#summary-address-selection">Summary Address Selection</a>.</p>
-
 <h3 id="operators-and-functions">Operators and Functions</h3>
-
 <p>Possible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.</p>
-
 <h4 id="assignment-operators">Assignment Operators</h4>
-
 <table>
 <thead>
 <tr>
@@ -1837,7 +1852,6 @@ if (!doNotTrack) {
 <th>DEFINITION</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>:=</td>
@@ -1845,9 +1859,7 @@ if (!doNotTrack) {
 </tr>
 </tbody>
 </table>
-
 <h4 id="basic-operators">Basic Operators</h4>
-
 <table>
 <thead>
 <tr>
@@ -1855,42 +1867,34 @@ if (!doNotTrack) {
 <th>DEFINITION</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>+</td>
 <td>Addition</td>
 </tr>
-
 <tr>
 <td>-</td>
 <td>Subtraction</td>
 </tr>
-
 <tr>
 <td>*</td>
 <td>Multiplication</td>
 </tr>
-
 <tr>
 <td>/</td>
 <td>Division</td>
 </tr>
-
 <tr>
 <td>%</td>
 <td>Modulus</td>
 </tr>
-
 <tr>
 <td>^</td>
 <td>Power</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="scalar-functions">Scalar Functions</h4>
-
 <table>
 <thead>
 <tr>
@@ -1898,32 +1902,26 @@ if (!doNotTrack) {
 <th>DEFINITION</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>avg</td>
 <td>Average</td>
 </tr>
-
 <tr>
 <td>max</td>
 <td>Maximum</td>
 </tr>
-
 <tr>
 <td>min</td>
 <td>Minimum</td>
 </tr>
-
 <tr>
 <td>sum</td>
 <td>Sum</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="trigonometry-functions">Trigonometry Functions</h4>
-
 <table>
 <thead>
 <tr>
@@ -1931,112 +1929,90 @@ if (!doNotTrack) {
 <th>DEFINITION</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>acos</td>
 <td>Arc cosine (in radians)</td>
 </tr>
-
 <tr>
 <td>acosh</td>
 <td>Inverse hyperbolic cosine (in radians)</td>
 </tr>
-
 <tr>
 <td>asin</td>
 <td>Arc sine (in radians)</td>
 </tr>
-
 <tr>
 <td>asinh</td>
 <td>Inverse hyperbolic sine (in radians)</td>
 </tr>
-
 <tr>
 <td>atan</td>
 <td>Arc tangent (in radians)</td>
 </tr>
-
 <tr>
 <td>atanh</td>
 <td>Inverse hyperbolic tangent (in radians)</td>
 </tr>
-
 <tr>
 <td>cos</td>
 <td>Cosine</td>
 </tr>
-
 <tr>
 <td>cosh</td>
 <td>Hyperbolic cosine</td>
 </tr>
-
 <tr>
 <td>cot</td>
 <td>Cotangent</td>
 </tr>
-
 <tr>
 <td>csc</td>
 <td>Cosecant</td>
 </tr>
-
 <tr>
 <td>deg2rad</td>
 <td>Convert x from degrees to radians</td>
 </tr>
-
 <tr>
 <td>deg2grad</td>
 <td>Convert x from degrees to radians</td>
 </tr>
-
 <tr>
 <td>rad2deg</td>
 <td>Convert x from radians to degrees</td>
 </tr>
-
 <tr>
 <td>grad2deg</td>
 <td>Convert x from radians to degrees</td>
 </tr>
-
 <tr>
 <td>sec</td>
 <td>Secant</td>
 </tr>
-
 <tr>
 <td>sin</td>
 <td>Sine</td>
 </tr>
-
 <tr>
 <td>sinc</td>
 <td>Sine cardinal</td>
 </tr>
-
 <tr>
 <td>sinh</td>
 <td>Hyperbolic sine</td>
 </tr>
-
 <tr>
 <td>tan</td>
 <td>Tangent</td>
 </tr>
-
 <tr>
 <td>tanh</td>
 <td>Hyperbolic tangent</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="vector-functions">Vector Functions</h4>
-
 <table>
 <thead>
 <tr>
@@ -2044,77 +2020,59 @@ if (!doNotTrack) {
 <th>DEFINITION</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>abs</td>
 <td>Absolute value</td>
 </tr>
-
 <tr>
 <td>ceil</td>
 <td>Rounding up</td>
 </tr>
-
 <tr>
 <td>floor</td>
 <td>Rounding down</td>
 </tr>
-
 <tr>
 <td>frac</td>
 <td>Fractional portion of input</td>
 </tr>
-
 <tr>
 <td>log</td>
 <td>Natural logarithm</td>
 </tr>
-
 <tr>
 <td>log10</td>
 <td>Base 10 logarithm</td>
 </tr>
-
 <tr>
 <td>pow</td>
 <td>Power</td>
 </tr>
-
 <tr>
 <td>round</td>
 <td>Round x to the nearest integer</td>
 </tr>
-
 <tr>
 <td>sgn</td>
 <td>Sign of x, -1 where x &lt; 0, +1 where x &gt; 0, else zero</td>
 </tr>
-
 <tr>
 <td>sqrt</td>
 <td>Square root</td>
 </tr>
-
 <tr>
 <td>trunc</td>
 <td>Integer portion of input</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="unit">Unit</h3>
-
 <p>It is possible to add a unit to the calculated curve, in the field <strong>Unit</strong> beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.</p>
-
 <h2 id="summary-address-selection">Summary Address Selection</h2>
-
 <p>An expression consists of placeholders (variables) for curves (summary address). By clicking <strong>Parse Expression</strong>, the variables will appear in the table below the settings. To assign a summary address to a variable, click <strong>Edit</strong>. This action will open a <strong>Summary Address Selection</strong> dialog. Use the dialog to select a summary address and press <strong>OK</strong>. Repeat the procedure for all the variables.</p>
-
 <h2 id="generating-curves">Generating Curves</h2>
-
 <p>After assigning summary addresses to all variables, click <strong>Calculate</strong> to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: <strong>Calculated</strong>.</p>
-
 <p>The curves can also be found in an existing curve&rsquo;s <strong>Property Editor</strong>. Choose the case <strong>Calculated</strong>, and the curves will appear in <strong>Vector Selection</strong>.</p>
 
 
@@ -2291,6 +2249,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2301,6 +2272,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3451,20 +3425,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/ensembleplotting/index.html b/plot-window/ensembleplotting/index.html
index 29b294fcda..9ef988435c 100644
--- a/plot-window/ensembleplotting/index.html
+++ b/plot-window/ensembleplotting/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble Plotting :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,17 +1802,15 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#import">Import</a></li>
-<li><a href="#plotting">Plotting</a>
-<ul>
-<li><a href="#statistics-curves">Statistics curves</a></li>
-</ul></li>
-<li><a href="#derived-ensembles">Derived Ensembles</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#import">Import</a></li>
+    <li><a href="#plotting">Plotting</a>
+      <ul>
+        <li><a href="#statistics-curves">Statistics curves</a></li>
+      </ul>
+    </li>
+    <li><a href="#derived-ensembles">Derived Ensembles</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1803,61 +1835,40 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>An ensemble is a group of cases that are tightly coupled, only a set of ensemble input parameters differ between cases. This makes it relevant to perform calculations and statistics analysis on ensembles.</p>
-
 <h2 id="import">Import</h2>
-
 <p>There are several ways to import an ensemble:</p>
-
 <ul>
 <li>Use menu option <strong>File-&gt;Import-&gt;Summary Cases-&gt;Import Ensemble</strong></li>
 <li>Use menu option <strong>File-&gt;Import-&gt;Summary Cases-&gt;Import Summary Case group</strong> and then convert the group to an ensemble</li>
 <li>Import a number of summary cases, move them into a group and then convert the group to an ensemble</li>
 </ul>
-
 <p>During import of a summary case, ResInsight tries to find an associated <strong>parameters.txt</strong> file or <strong>runspecification.xml</strong> file containing ensemble parameters. If found, the ensemble parameters are stored together with the summary case. When the user adds a summary case to an ensemble, then ResInsight will perform ensemble parameters validation. A warning dialog is displayed in the following cases:</p>
-
 <ul>
 <li>One or more of the cases in the ensemble have no ensemble parameters</li>
 <li>The list of ensemble parameters differ between cases in the ensemble</li>
 </ul>
-
 <h2 id="plotting">Plotting</h2>
-
 <p>Ensembles are plotted in the summary plot the same way as ordinary summary curves. Create a new summary plot using the <a href="/plot-window/summaryploteditor/">summary plot editor</a>. Imported ensembles will appear in a separate group in the list of summary cases. When an ensemble is selected, a new curve set is created and plotted as multiple summary curves. By default all curves in an ensemble curve set will have the same color. The coloring mode may be edited in the curve set&rsquo;s property editor in the project plot tree view. Two coloring modes are available:</p>
-
 <ul>
 <li><strong>Single color</strong> Use the same color for all curves in a curve set</li>
 <li><strong>By Ensemble Parameter</strong> One ensemble parameter is selected to control coloring. The ensemble parameter value for each case is used to pick a color in a color range. In this case a color legend appears.</li>
 </ul>
-
 <p>Stepping of data source for ensemble curves is described in <a href="/plot-window/summarysourcestepping/">Summary Plot Source Stepping</a></p>
-
 <h3 id="statistics-curves">Statistics curves</h3>
-
 <p>If the number of curves in a curve set is sufficient, ResInsight will calculate statistics for the curve set. The following statistics curves may be displayed:</p>
-
 <ul>
 <li><strong>P10</strong> &ndash; 10% of the curves in the curve set are above this curve</li>
 <li><strong>P50</strong> &ndash; 50% of the curves in the curve set are above this curve</li>
 <li><strong>Mean</strong> &ndash; Aritmetic mean for the curves in the curve set</li>
 <li><strong>P90</strong> &ndash; 90% of the curves in the curve set are above this curve</li>
 </ul>
-
 <p>Statistics curves may be toggled on or off in the curve set&rsquo;s property editor.</p>
-
 <p>Example:</p>
-
-<p><img src="/images/plot-window/Ensemble.png" alt="" /></p>
-
+<p><img src="/images/plot-window/Ensemble.png" alt=""></p>
 <h2 id="derived-ensembles">Derived Ensembles</h2>
-
 <p>New ensembles can be created based on calculations on two or more ensembles. Such ensembles are called &lsquo;derived ensembles&rsquo;. A derived ensemble will contain data which are either the sum or difference between two other ensembles. An existing derived ensemble may be input to a new derived ensemble, making it possible to for instance add more than two ensembles.</p>
-
 <p>To create a derived ensemble, select two existing ensembled in the project tree. Right click and select <strong>New Derived Ensenble</strong>. A new derived ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the new ensemble, both input ensembles and operator can be modified.</p>
-
 <p>If the two input ensembles differs in which cases they consist of, ResInsight will display a warning and let the user decide whether to create the derived ensemble or not.</p>
 
 
@@ -2034,6 +2045,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2044,6 +2068,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3194,20 +3221,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/ensemblerftplot/index.html b/plot-window/ensemblerftplot/index.html
index 3a0fb25baa..f2a96db94d 100644
--- a/plot-window/ensemblerftplot/index.html
+++ b/plot-window/ensemblerftplot/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble RFT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,30 +1802,23 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#create-new-ensemble-rft-plot">Create New Ensemble RFT Plot</a></li>
-<li><a href="#property-editor">Property Editor</a>
-<ul>
-<li><a href="#well-name">Well Name</a></li>
-<li><a href="#sources">Sources</a></li>
-<li><a href="#time-steps">Time Steps</a></li>
-<li><a href="#zonation-formation-names">Zonation/Formation Names</a></li>
-<li><a href="#legend-and-axis">Legend and Axis</a></li>
-</ul></li>
-<li><a href="#import-of-observed-ensemble-rft-data-from-fmu">Import of Observed Ensemble RFT data from FMU</a>
-<ul>
-<li>
-<ul>
-<li><a href="#correlation-of-grid-and-formations">Correlation of grid and formations</a></li>
-<li><a href="#observed-pressure-and-error">Observed pressure and error</a></li>
-<li><a href="#reservoir-zone-name">Reservoir zone name</a></li>
-<li><a href="#well-measurements">Well measurements</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#create-new-ensemble-rft-plot">Create New Ensemble RFT Plot</a></li>
+    <li><a href="#property-editor">Property Editor</a>
+      <ul>
+        <li><a href="#well-name">Well Name</a></li>
+        <li><a href="#sources">Sources</a></li>
+        <li><a href="#time-steps">Time Steps</a></li>
+        <li><a href="#zonationformation-names">Zonation/Formation Names</a></li>
+        <li><a href="#legend-and-axis">Legend and Axis</a></li>
+      </ul>
+    </li>
+    <li><a href="#import-of-observed-ensemble-rft-data-from-fmu">Import of Observed Ensemble RFT data from FMU</a>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1816,108 +1843,71 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/EnsembleRftPlot.png" alt="" /></p>
-
-<p>ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots.
+<p><img src="/images/plot-window/EnsembleRftPlot.png" alt=""></p>
+<p>ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. 
 The functionality also computes statistics, e.g. P10, P90, and mean.
 When possible, ResInsight avoids loading the grid when reading ensemble RFT data.</p>
-
 <h2 id="create-new-ensemble-rft-plot">Create New Ensemble RFT Plot</h2>
-
 <p>When a <a href="/plot-window/ensembleplotting/#import">summary ensemble has been imported</a>,
-observed FMU data can be imported via right-clicking <strong>Observed Data</strong> in the <strong>Plot Project Tree</strong>,
+observed FMU data can be imported via right-clicking <strong>Observed Data</strong> in the <strong>Plot Project Tree</strong>, 
 and selecting <strong>Import Observed FMU Data</strong>.</p>
-
-<p><img src="/images/plot-window/EnsembleRftImportObservedData.png" alt="" /></p>
-
+<p><img src="/images/plot-window/EnsembleRftImportObservedData.png" alt=""></p>
 <p>To create ensemble RFT plot, right-click <strong>RFT Plots</strong> and select <strong>New RFT Plot</strong>.</p>
-
-<p><img src="/images/plot-window/EnsembleRftNewRftPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/EnsembleRftNewRftPlot.png" alt=""></p>
 <h2 id="property-editor">Property Editor</h2>
-
 <p>The property editor lets the user select which curves to display in the RFT plot.</p>
-
-<p><img src="/images/plot-window/EnsembleRftPlotPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/EnsembleRftPlotPropertyEditor.png" alt=""></p>
 <h3 id="well-name">Well Name</h3>
-
-<p>Select the well to display in the plot. Wells postfixed by <em>&rsquo;(Well Path)&rsquo;</em> have an associated well trajectory loaded.</p>
-
+<p>Select the well to display in the plot. Wells postfixed by <em>'(Well Path)'</em> have an associated well trajectory loaded.</p>
 <h3 id="sources">Sources</h3>
-
 <p>Subsequent to selecting a well in the Well Name field, the relevant sources for that well will appear in the <strong>Sources</strong> field. The sources for this particular case are:</p>
-
 <ul>
 <li><strong>Ensembles with RFT Data</strong> &ndash; List of ensembles which contain RFT data with check-boxes to activate display.</li>
 <li><strong>Observed FMU data</strong> &ndash; Observed data imported from a FMU run.</li>
 </ul>
-
 <p>When the user selects one or more sources, a selection of their time steps appears in the <strong>Time Steps</strong> field.</p>
-
 <h3 id="time-steps">Time Steps</h3>
-
 <p>The <strong>Time Steps</strong> field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:</p>
-
 <ol>
 <li>If a single source or sources of the same type are selected, all available time steps in those sources are shown.</li>
-<li>If sources from two or tree types are selected, the time steps are filtered:
-
+<li>If sources from two or tree types are selected, the time steps are filtered:</li>
+</ol>
 <ul>
 <li>The time steps matching the observed case(s) time steps.</li>
 <li>If no time steps from a case match the observed time step, the two adjacent ones are shown.</li>
 <li>The first time step from any grid case(s) (as initial pressure reference).
 If the Observed data isn&rsquo;t selected, the RFT data serves as filter reference.</li>
-</ul></li>
-</ol>
-
+</ul>
 <p>Each time step is postfixed by letter(s) to indicate source type(s) of each time step. The source types are indicated in square brackets:</p>
-
 <ul>
 <li><strong>O</strong> &ndash; Time step has Observed data</li>
 <li><strong>E</strong> &ndash; Time step has Ensemble data</li>
 <li><strong>R</strong> &ndash; Time step has RFT data</li>
 <li><strong>G</strong> &ndash; Time step has Grid data</li>
 </ul>
-
 <p>More than one letter for one single time step, means that the time step comes from multiple case types.</p>
-
-<h3 id="zonation-formation-names">Zonation/Formation Names</h3>
-
+<h3 id="zonationformation-names">Zonation/Formation Names</h3>
 <p>The display of formations lines is controlled in the same manner as for <a href="/plot-window/rftplot/#zonation-formation-names">RFT plots</a>.
 Please see the <a href="/3d-main-window/formations/">full documentation</a> of the formations property editor for details about formations.</p>
-
 <h3 id="legend-and-axis">Legend and Axis</h3>
-
 <p>Visual properties of legend and axes is controlled in the same manner as for <a href="/plot-window/rftplot/#legend-and-axis">RFT plots</a>.</p>
-
 <h2 id="import-of-observed-ensemble-rft-data-from-fmu">Import of Observed Ensemble RFT data from FMU</h2>
-
 <p>Observed RFT data as part of a FMU run is presupposed to be located in a folder which contains the following four file types:</p>
-
 <ul>
 <li>layer_zone_table.txt</li>
 <li>&lt;<em>well_name</em>&gt;.obs</li>
 <li>&lt;<em>well_name</em>&gt;.txt</li>
 <li>well_date_rft.txt</li>
 </ul>
-
 <p>The purpose and format of the data files is explained below.</p>
 
-
 <div class="notices note" ><p>The data file <em>well_date_rft.txt</em> is required. If missing, no Observed FMU data will be imported.</p>
 </div>
 
-
 <h4 id="correlation-of-grid-and-formations">Correlation of grid and formations</h4>
-
-<p>The file <em>layer_zone_table.txt</em> can be used to correlate each grid k-layer with a formation name.
+<p>The file <em>layer_zone_table.txt</em> can be used to correlate each grid k-layer with a formation name. 
 This file is identical for all cases in the same ensemble.</p>
-
 <p>Example file <em>layer_zone_table.txt</em>:</p>
-
 <pre><code>1   UpperReek
 2   UpperReek
 3   UpperReek
@@ -1932,25 +1922,16 @@ This file is identical for all cases in the same ensemble.</p>
 12  LowerReek
 13  LowerReek
 14  LowerReek
-</code></pre>
-
-<h4 id="observed-pressure-and-error">Observed pressure and error</h4>
-
-<p>For a given well name, the file <em>&lt;well_name&gt;.obs</em> is a data file containing two columns to specify observed pressure and error.
+</code></pre><h4 id="observed-pressure-and-error">Observed pressure and error</h4>
+<p>For a given well name, the file <em>&lt;well_name&gt;.obs</em> is a data file containing two columns to specify observed pressure and error. 
 Column one contains observed pressure and column two contains error. The observation data is valid for one and only one layer/formation.</p>
-
 <p>Example file  for well <em>OP_1</em>, i.e. <em>OP_1.obs</em>:</p>
-
 <pre><code>303.000   3.000
 304.000   3.000
 305.000   3.000
-</code></pre>
-
-<h4 id="reservoir-zone-name">Reservoir zone name</h4>
-
-<p>For a given well name, the file <em>&lt;well_name&gt;.txt</em> is a data file containing five columns that specify its correlation with reservoir zones.
+</code></pre><h4 id="reservoir-zone-name">Reservoir zone name</h4>
+<p>For a given well name, the file <em>&lt;well_name&gt;.txt</em> is a data file containing five columns that specify its correlation with reservoir zones. 
 Each line of data must contain:</p>
-
 <ul>
 <li>Utmx: x-coordinate in UTM</li>
 <li>Utmy: y-coordinate in UTM</li>
@@ -1958,18 +1939,12 @@ Each line of data must contain:</p>
 <li>True Vertical Depth referenced to Mean Sea Level (TVDMSL)</li>
 <li>Reservoir zone name</li>
 </ul>
-
 <p>Example file for well <em>OP_1</em>, i.e. <em>OP_1.txt</em>:</p>
-
 <pre><code>461288.719   5933415.000   1816.200   1611.692   UpperReek
 461288.685   5933415.027   1824.560   1620.052   MidReek
 461288.683   5933415.029   1840.000   1635.492   LowerReek
-</code></pre>
-
-<h4 id="well-measurements">Well measurements</h4>
-
+</code></pre><h4 id="well-measurements">Well measurements</h4>
 <p>The data file <em>well_date_rft.txt</em> contains well measurements. The file contains four columns for each well measurement:</p>
-
 <ul>
 <li>Well Name</li>
 <li>Date in two digit form &lt;DD&gt;</li>
@@ -1977,11 +1952,8 @@ Each line of data must contain:</p>
 <li>Year in four digit form &lt;YYYY&gt;</li>
 <li>Measurement index</li>
 </ul>
-
 <p>There can be multiple measurement for each well.</p>
-
 <p>Example file <em>well_date_rft.txt</em>:</p>
-
 <pre><code>OP_1   01 02 2000   1
 OP_2   01 02 2000   1
 OP_4   01 01 2001   1
@@ -1989,7 +1961,6 @@ WI_1   01 02 2000   1
 WI_3   01 03 2001   1
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -2163,6 +2134,19 @@ WI_3   01 03 2001   1
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2173,6 +2157,9 @@ WI_3   01 03 2001   1
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3323,20 +3310,20 @@ WI_3   01 03 2001   1
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/flowdiagnosticsplots/index.html b/plot-window/flowdiagnosticsplots/index.html
index fb244125e9..58ee037c9b 100644
--- a/plot-window/flowdiagnosticsplots/index.html
+++ b/plot-window/flowdiagnosticsplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Flow Diagnostics Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,22 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#well-allocation-plots">Well Allocation Plots</a>
-<ul>
-<li><a href="#branches">Branches</a></li>
-<li><a href="#creating-well-allocation-plots">Creating Well Allocation Plots</a></li>
-<li><a href="#options">Options</a></li>
-<li><a href="#depth-settings">Depth Settings</a></li>
-<li><a href="#accessing-the-plot-data">Accessing the Plot Data</a></li>
-</ul></li>
-<li><a href="#flow-characteristics-plot">Flow Characteristics Plot</a>
-<ul>
-<li><a href="#settings">Settings</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#well-allocation-plots">Well Allocation Plots</a>
+      <ul>
+        <li><a href="#branches">Branches</a></li>
+        <li><a href="#creating-well-allocation-plots">Creating Well Allocation Plots</a></li>
+        <li><a href="#options">Options</a></li>
+        <li><a href="#depth-settings">Depth Settings</a></li>
+        <li><a href="#accessing-the-plot-data">Accessing the Plot Data</a></li>
+      </ul>
+    </li>
+    <li><a href="#flow-characteristics-plot">Flow Characteristics Plot</a>
+      <ul>
+        <li><a href="#settings">Settings</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,166 +1842,131 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/FlowDiagnosticsPlotsOverview.png" alt="" /></p>
-
+<p><img src="/images/plot-window/FlowDiagnosticsPlotsOverview.png" alt=""></p>
 <p>Flow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.</p>
-
 <p>They are managed from the folder <strong>Flow Diagnostics Plots</strong> located in <strong>Plot Project Tree</strong> in the <strong>Plot Main Window</strong>.</p>
-
-<p><img src="/images/plot-window/FlowDiagnosticsPlotsProjectTree.png" alt="" /></p>
-
+<p><img src="/images/plot-window/FlowDiagnosticsPlotsProjectTree.png" alt=""></p>
 <p>This folder contains a default <strong>Flow Characteristics Plot</strong> and <strong>Well Allocation Plot</strong>. In addition, two folders with stored  well allocation and flow characteristics plots will show up if there are any of those in the model.</p>
-
 <p>Please refer to <a href="/3d-main-window/cellresults/#flow-diagnostic-results">Cell Results-&gt; Flow Diagnostic Results</a> for a description of the results and references to more information about the methodology.</p>
-
 <h2 id="well-allocation-plots">Well Allocation Plots</h2>
-
 <p>Well allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.</p>
-
 <p>In addition a <strong>Cumulative Saturation by Time of Flight</strong> plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.</p>
-
 <h3 id="branches">Branches</h3>
-
 <p>Each branch of the well will be assigned a separate <strong>Track</strong>. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with <strong>Branch Detection</strong> <em>On</em> ( See <a href="/wells-and-completions/simulationwells/#well-pipe-geometry">Well Pipe Geometry</a> ).
 Multi Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See  <a href="/wells-and-completions/simulationwells/#dummy-branches">Dummy branches</a> ).</p>
-
 <h3 id="creating-well-allocation-plots">Creating Well Allocation Plots</h3>
-
 <p>To plot the Well allocation for a well, right-click the well in the <strong>Project Tree</strong> or in the <strong>3D View</strong> and invoke the command <strong>Plot Well Allocation</strong>.</p>
-
-<p><img src="/images/plot-window/SimulationWellContextMenu.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SimulationWellContextMenu.png" alt=""></p>
 <p>The command updates the default <strong>Well Allocation Plot</strong> with new values based on the selection and the settings in the active view. This plot can then be copied to the <strong>Stored Plots</strong> folder by the context command <strong>Add Stored Well Allocation Plot</strong>.</p>
-
 <h3 id="options">Options</h3>
-
 <p>The <strong>Legend</strong>, <strong>Total Allocation</strong> pie chart, <strong>Cumulative Saturation</strong>, and the <strong>Well Flow/Allocation</strong> can be turned on or off from the toggles in the <strong>Project Tree</strong>. The other options are controlled from the property panel of a Well Allocation Plot:</p>
-
-<p><img src="/images/plot-window/WellAllocationProperties.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellAllocationProperties.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; Auto generated name used as plot title</li>
 <li><strong>Show Plot Title</strong> &ndash; Toggles whether to show the title in the plot</li>
 <li><strong>Plot Data</strong> &ndash; Options controlling when and what the plot is based on
-
 <ul>
 <li><strong>Case</strong> &ndash; The case to plot data from</li>
 <li><strong>Time Step</strong> &ndash; The selected time step</li>
 <li><strong>Well</strong> &ndash; The simulation well to plot</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Options</strong>
-
 <ul>
 <li><strong>Plot Type</strong>
-
 <ul>
-<li><strong>Allocation</strong> &ndash; Plots <em>Reservoir well flow rates</em> along with how this well supports/are
+<li><strong>Allocation</strong> &ndash; Plots <em>Reservoir well flow rates</em> along with how this well supports/are 
 supported by other wells ( This option is only available for cases with Flux results available )</li>
 <li><strong>Well Flow</strong> &ndash; Plots <em>Surface Well Flow Rates</em> together with phase split between Oil, Gas, and Water</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Flow Type</strong>
-
 <ul>
 <li><strong>Accumulated</strong> &ndash; Plots an approximation of the accumulated flow along the well</li>
 <li><strong>Inflow Rates</strong> &ndash; Plots the rate of flow from the connection into the well</li>
-</ul></li>
-<li><strong>Group Small Contributions</strong> &ndash; Groups small well contributions into a group called <strong>Other</strong></li>
-<li><strong>Threshold</strong> &ndash; Threshold used by the <strong>Group Small Contributions</strong> option
-<br /></li>
-</ul></li>
 </ul>
-
+</li>
+<li><strong>Group Small Contributions</strong> &ndash; Groups small well contributions into a group called <strong>Other</strong></li>
+<li><strong>Threshold</strong> &ndash; Threshold used by the <strong>Group Small Contributions</strong> option</li>
+</ul>
+</li>
+</ul>
 <h3 id="depth-settings">Depth Settings</h3>
-
 <p>The depth value in the plot can be controlled by selecting the <strong>Accumulated Flow</strong>/<strong>Inflow Rates</strong> item in the <strong>Project Tree</strong>. This item represents the Well-Log-like part of the Well Allocation Plot and its properties are shown below:</p>
-
-<p><img src="/images/plot-window/WellAllocationWellLogProperties.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellAllocationWellLogProperties.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; The plot name, updated automatically based on the <strong>Flow Type</strong> and well.</li>
 <li><strong>Depth Type</strong>
-
 <ul>
-<li><strong>Pseudo Length</strong>  &ndash; Use the length along the visualized simulation well pipe as depth.
-In this mode the curves are extended somewhat above zero depth keeping the curve
-values constant. This is done to make it easier to see the final values of the curves relative to each other.<br />
-The depth are calculated with <strong>Branch detection</strong> <em>On</em> and using the <strong>Interpolated</strong> well pipe geometry.<br />
+<li><strong>Pseudo Length</strong>  &ndash; Use the length along the visualized simulation well pipe as depth. 
+In this mode the curves are extended somewhat above zero depth keeping the curve 
+values constant. This is done to make it easier to see the final values of the curves relative to each other.<br>
+The depth are calculated with <strong>Branch detection</strong> <em>On</em> and using the <strong>Interpolated</strong> well pipe geometry.<br>
 ( See <a href="/wells-and-completions/simulationwells/#well-pipe-geometry">Well Pipe Geometry</a> )</li>
 <li><strong>TVD</strong> &ndash; Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells.</li>
 <li><strong>Connection Number</strong> &ndash; Use the number of connections counted from the top on the depth-axis.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Visible Depth Range</strong> &ndash; These options control the depth zoom.
-
 <ul>
 <li><strong>Auto Scale</strong> &ndash; Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made.</li>
-<li><strong>Min</strong>, <strong>Max</strong> &ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.
-<br /></li>
-</ul></li>
+<li><strong>Min</strong>, <strong>Max</strong> &ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.</li>
+</ul>
+</li>
 </ul>
-
 <h3 id="accessing-the-plot-data">Accessing the Plot Data</h3>
-
 <p>The command context command <strong>Show Plot Data</strong> will show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.</p>
-
 <p>It is also possible to save the ascii data to a file directly by using the context command <strong>Export Plot Data to Text File</strong> on the <strong>Accumulated Flow</strong>/<strong>Inflow Rates</strong> item in the <strong>Project Tree</strong>.</p>
-
 <p>The total accumulation data can also be viewed in ascci format by the command <strong>Show Total Allocation Data</strong>.</p>
-
 <h2 id="flow-characteristics-plot">Flow Characteristics Plot</h2>
-
-<p><img src="/images/plot-window/FlowCharacteristicsPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/FlowCharacteristicsPlot.png" alt=""></p>
 <p>This window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.</p>
-
 <ul>
 <li><strong>Lorenz Coefficient</strong> &ndash; This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs.</li>
 <li><strong>Flow Capacity vs Storage Capacity</strong> &ndash; This plot displays one curve for each time step of the F-phi curve for the reservoir.</li>
 <li><strong>Sweep Efficiency</strong> &ndash; This plot displays one Sweep Efficiency curve for each selected time step.</li>
 </ul>
-
 <h3 id="settings">Settings</h3>
-
-<p><img src="/images/plot-window/FlowCharacteristicsPropertyPanel.png" alt="" /></p>
-
+<p><img src="/images/plot-window/FlowCharacteristicsPropertyPanel.png" alt=""></p>
 <ul>
 <li><strong>Case</strong> &ndash; Selects the source case for the plot.</li>
 <li><strong>Time Steps</strong> &ndash; These options selects the time steps to be used in the plot.
-
 <ul>
-<li><strong>All With Calculated FlowDiagnostics</strong> &ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using  <a href="/3d-main-window/cellresults/">Cell Results</a>, Well Allocation Plots, or <a href="/plot-window/welllogsandplots/#well-log-extraction-curves">Well Log Extraction Curves</a>.<br /></li>
+<li><strong>All With Calculated FlowDiagnostics</strong> &ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using  <a href="/3d-main-window/cellresults/">Cell Results</a>, Well Allocation Plots, or <a href="/plot-window/welllogsandplots/#well-log-extraction-curves">Well Log Extraction Curves</a>.</li>
 <li><strong>Selected</strong> &ndash; Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix <em><code>*</code></em>. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Region</strong> &ndash; These group of options controls the cell region of interest for the plot.
-
 <ul>
-<li><strong>Cell Filter</strong> &ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.</li>
+<li><strong>Cell Filter</strong> &ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.
+<ul>
 <li><strong>All Active Cells</strong> &ndash; Use all the active cells in the model (default)</li>
 <li><strong>Visible Cells</strong> &ndash; Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.
-
 <ul>
 <li><strong>View</strong> &ndash; The view to use as cell filter</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Injector Producer Communication</strong> &ndash; The region of communication between selected producers and injectors. See  <a href="/3d-main-window/cellresults/#Flow-Diagnostic-Results">Flow Diagnostic Results</a>
-
 <ul>
 <li><strong>Tracer Filter</strong> &ndash; Wild card based filter-text to filter the list of tracers</li>
 <li><strong>list</strong> &ndash; Producer and injector tracers to select</li>
 <li><strong>Show Region</strong> &ndash; Button to create (or edit) a 3D View showing the selected region of cells.</li>
 <li><strong>Min communication</strong> &ndash; A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Flooded by Injector</strong>/<strong>Drained by Producer</strong> &ndash; The region with a Time Of Flight from the selected tracers below the selected threshold.</li>
 <li><strong>Tracer Filter</strong>/<em>list</em>/<strong>Show Region</strong> &ndash; See above.</li>
 <li><strong>Max Time of Flight [days]</strong> &ndash; Only cells with a Time of Flight value less then this value are used.</li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li><strong>Options</strong>
-
 <ul>
 <li><strong>Legend</strong> &ndash; Toggles the legend on/off</li>
-<li><strong>Aquifer Cell Threshold</strong> &ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold <em><code>*</code></em> total pore volume.
-<br /></li>
-</ul></li>
+<li><strong>Aquifer Cell Threshold</strong> &ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold <em><code>*</code></em> total pore volume.</li>
+</ul>
+</li>
 </ul>
 
 
@@ -2145,6 +2143,19 @@ The depth are calculated with <strong>Branch detection</strong> <em>On</em> and
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2155,6 +2166,9 @@ The depth are calculated with <strong>Branch detection</strong> <em>On</em> and
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3305,20 +3319,20 @@ The depth are calculated with <strong>Branch detection</strong> <em>On</em> and
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/gridcrossplots/index.html b/plot-window/gridcrossplots/index.html
index 8281f122dd..4caa271be5 100644
--- a/plot-window/gridcrossplots/index.html
+++ b/plot-window/gridcrossplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Cross Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,12 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#creating-grid-cross-plots">Creating Grid Cross Plots</a></li>
-<li><a href="#grid-cross-plot-data-sets">Grid Cross Plot Data Sets</a></li>
-<li><a href="#show-plot-data">Show Plot Data</a></li>
-<li><a href="#swap-axes">Swap Axes</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#creating-grid-cross-plots">Creating Grid Cross Plots</a></li>
+    <li><a href="#grid-cross-plot-data-sets">Grid Cross Plot Data Sets</a></li>
+    <li><a href="#show-plot-data">Show Plot Data</a></li>
+    <li><a href="#swap-axes">Swap Axes</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,52 +1832,32 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/GridCrossPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlot.png" alt=""></p>
 <p>ResInsight supports the creation of scatter / cross plots of two Eclipse results against each  other, with each cell in the grid
 representing one data point in the plot. The data points can be grouped by a third result, by time step or by <strong>Formations</strong>.
 giving a separate color and label for each group. The above example shows a classic Porosity vs Permeability plot, grouped by
 formations, showing different trends for each formation.</p>
-
 <p>For continuous grouping parameters, the parameter will be divided into a set of equally sized intervals depending on the number of Color Legend intervals.</p>
-
 <p>Each cross plot can contain any number of <strong>Data Sets</strong>, representing a collection of cross plot points, where the <strong>Data Set</strong> can have a case source, time step and cell filter associated with it. This way, dynamic parameters for different time steps can be compared, or results from different case realizations.</p>
-
 <p>The Grid Cross plots may have a Symbol Legend below the plot, separating the Data Sets, and a Color Legend within the plot separating between the different Grouping categories or intervals. In addition, an Info Box will be added to the upper right corner of the plot, showing the different data sets in the plot and the parameters used. The Color Legends and Info Box can be moved to other parts of the plot and will snap to edges and corners when moved close to them.</p>
-
 <h2 id="creating-grid-cross-plots">Creating Grid Cross Plots</h2>
-
-<p><img src="/images/plot-window/GridCrossPlot_CreateFromView.png" alt="" />
-<img src="/images/plot-window/GridCrossPlot_Create.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlot_CreateFromView.png" alt="">
+<img src="/images/plot-window/GridCrossPlot_Create.png" alt=""></p>
 <p>Grid Cross Plots can be created in a couple of ways:</p>
-
 <ol>
 <li>Select a 3D view or Cell Result in the main ResInsight window, right-click and select <strong>Create Grid Cross Plot from 3d View</strong>. The resulting cross plot will display the current 3d Result x DEPTH and only contain data points for the visible cells.</li>
 <li>Right-click on the <strong>Grid Cross Plots</strong> entry under <strong>Plots</strong> in the <strong>Plot Window</strong>. By default the plot will contain the result values PORO x PERMX and will be grouped by formations (if any are loaded in the project). Data for all active cells will be displayed.</li>
 </ol>
-
 <p>Having created a Grid Cross Plot, the appearance of the Legends, the Info box and the Plot Title can be set in the Property Editor of the Grid Cross Plot.</p>
-
-<p><img src="/images/plot-window/GridCrossPlot_PropertyEditor.png" alt="" />
-<img src="/images/plot-window/GridCrossPlotAxis_PropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlot_PropertyEditor.png" alt="">
+<img src="/images/plot-window/GridCrossPlotAxis_PropertyEditor.png" alt=""></p>
 <p>The plot also have some available settings for the two plot axes (X and Y), where the title position and font size can be altered plus the axis range may be controlled and the axis may be set as logarithmic and inverted so the smallest value is first (default for DEPTH on the Y-axis).</p>
-
 <h2 id="grid-cross-plot-data-sets">Grid Cross Plot Data Sets</h2>
-
 <p>Further Grid Cross Plot data sets can be added to a Plot by right clicking on the plot in the Project Tree and selecting <strong>New Data Set</strong>.</p>
-
-<p><img src="/images/plot-window/GridCrossPlotDataSet_Create.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlotDataSet_Create.png" alt=""></p>
 <p>The Data Sets contain all the parameters controlling the data source and types of data being plotted.</p>
-
-<p><img src="/images/plot-window/GridCrossPlotDataSet_PropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlotDataSet_PropertyEditor.png" alt=""></p>
 <p>The available parameters are:</p>
-
 <table>
 <thead>
 <tr>
@@ -1854,66 +1865,50 @@ formations, showing different trends for each formation.</p>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Case</td>
 <td>The Eclipse Case containing the data</td>
 </tr>
-
 <tr>
 <td>Time Step</td>
 <td>Show data for All Time Steps or just a specific time step</td>
 </tr>
-
 <tr>
 <td>Filter by 3d View Visibility</td>
 <td>Pick a view to use only the cells visible in that view. Allows the use of range and property filters</td>
 </tr>
-
 <tr>
 <td>Group Data by</td>
 <td>Group and color data points by <strong>Time Step</strong>, <strong>Result Property</strong> or <strong>Formations</strong></td>
 </tr>
-
 <tr>
 <td>Data Grouping Property</td>
 <td>Available if grouping by <strong>Result Property</strong> and lets you pick any Eclipse result property and the number of intervals to divide the data into</td>
 </tr>
-
 <tr>
 <td>X-Axis Property</td>
 <td>The property representing the X-axis in the cross plot</td>
 </tr>
-
 <tr>
 <td>Y-Axis Property</td>
 <td>The property representing the Y-axis in the cross plot</td>
 </tr>
-
 <tr>
 <td>Name Configuration</td>
 <td>Add Case Name, Axis Variables, Time Step and/or Data Group to the name of the Data set</td>
 </tr>
 </tbody>
 </table>
-
 <h2 id="show-plot-data">Show Plot Data</h2>
-
 <p>The data used to create the Cross Plot can be exported by either right-clicking on the Cross Plot in the project tree or right clicking on the plot itself and selecting <strong>Show Plot Data</strong>.</p>
-
-<p><img src="/images/plot-window/GridCrossPlot_ShowData_ProjectTree.png" alt="" />
-<img src="/images/plot-window/GridCrossPlot_ShowData_PlotContext.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlot_ShowData_ProjectTree.png" alt="">
+<img src="/images/plot-window/GridCrossPlot_ShowData_PlotContext.png" alt=""></p>
 <p>Either method will bring up a dialog containing column-based text showing the X and Y result values, the Group index and Group Description (the latter two if Grouping is enabled). One tab in the dialog will be added for each Data Set. The data can be copied to the clipboard or exported to file by right-clicking on the text area.</p>
-
-<p><img src="/images/plot-window/GridCrossPlot_ShowData.png" alt="" /></p>
-
+<p><img src="/images/plot-window/GridCrossPlot_ShowData.png" alt=""></p>
 <h2 id="swap-axes">Swap Axes</h2>
-
 <p>The X- and Y-axes can be swapped, both for invididual data sets, by choosing <strong>Swap Axis Properties</strong> from the right-click menu of the Grid Cross Plot <strong>Data Set</strong>, or for all data sets by right clicking on either the Cross Plot in the Project Tree or on the plot itself and selecting <strong>Swap Axis Properties for all Data Sets in Plot</strong>. The X- and Y-axis will swap place retaining the properties, such as Logarithmic or inverted axes.</p>
-
-<p><img src="/images/plot-window/GridCrossPlot_SwapAxes.png" alt="" /></p>
+<p><img src="/images/plot-window/GridCrossPlot_SwapAxes.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2089,6 +2084,19 @@ formations, showing different trends for each formation.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2099,6 +2107,9 @@ formations, showing different trends for each formation.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3249,20 +3260,20 @@ formations, showing different trends for each formation.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/index.html b/plot-window/index.html
index 56e8578694..fbf2f4fadc 100644
--- a/plot-window/index.html
+++ b/plot-window/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Plot Main Window :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,17 +1820,14 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/getting-started/ResInsightMainPlotMediumSize.png" alt="ResInsight User Interface" /></p>
-
-<p>This is the main window of ResInsight for 2D graphing and plotting. As seen, the <strong>Plot Main Window</strong> has a central area
+	<p><img src="/images/getting-started/ResInsightMainPlotMediumSize.png" alt="ResInsight User Interface"></p>
+<p>This is the main window of ResInsight for 2D graphing and plotting. As seen, the <strong>Plot Main Window</strong> has a central area 
 and two docking windows surrounding it. The docking windows cover the following:</p>
-
 <ul>
 <li><strong>Plot Project Tree</strong> &ndash; contains all application objects in a tree structure.</li>
 <li><strong>Property Editor</strong> &ndash; displays all properties for the selected object in the <strong>Project Tree</strong></li>
 </ul>
-
-<p>A selected subset of actions are presented as controls in the toolbar.
+<p>A selected subset of actions are presented as controls in the toolbar. 
 The following subchapters describe the functionality, graphs, and plots of the <strong>Plot Main Window</strong>.</p>
 
 
@@ -1975,6 +2006,19 @@ The following subchapters describe the functionality, graphs, and plots of the <
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1985,6 +2029,9 @@ The following subchapters describe the functionality, graphs, and plots of the <
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3131,20 +3178,20 @@ The following subchapters describe the functionality, graphs, and plots of the <
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/index.xml b/plot-window/index.xml
index f85ceb1fef..c8c655fb2f 100644
--- a/plot-window/index.xml
+++ b/plot-window/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Plot Main Window on ResInsight</title>
@@ -40,7 +40,7 @@ The toolbar allows use of vector filters in addition to source stepping:</descri
       <guid>https://resinsight.org/plot-window/summaryploteditor/</guid>
       <description>The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.
 The upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the Summary Type currently highlighted.
-In this context highlighted means the marked item with a different background color, while selected means an item or items that have a ticked check box.</description>
+In this context highlightedmeans the marked item with a different background color, while selectedmeans an item or items that have a ticked check box.</description>
     </item>
     
     <item>
diff --git a/plot-window/pltplot/index.html b/plot-window/pltplot/index.html
index cf008035c2..879df686f5 100644
--- a/plot-window/pltplot/index.html
+++ b/plot-window/pltplot/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>PLT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,21 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#create-new-plt-plot">Create New PLT Plot</a></li>
-<li><a href="#plot-observed-data">Plot Observed Data</a></li>
-<li><a href="#property-editor">Property Editor</a>
-<ul>
-<li><a href="#well-name">Well Name</a></li>
-<li><a href="#sources">Sources</a></li>
-<li><a href="#time-steps">Time Steps</a></li>
-<li><a href="#curve-selection">Curve Selection</a></li>
-<li><a href="#zonation-formation-names">Zonation/Formation Names</a></li>
-<li><a href="#legend-and-axis">Legend and Axis</a></li>
-<li><a href="#plot">Plot</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#create-new-plt-plot">Create New PLT Plot</a></li>
+    <li><a href="#plot-observed-data">Plot Observed Data</a></li>
+    <li><a href="#property-editor">Property Editor</a>
+      <ul>
+        <li><a href="#well-name">Well Name</a></li>
+        <li><a href="#sources">Sources</a></li>
+        <li><a href="#time-steps">Time Steps</a></li>
+        <li><a href="#curve-selection">Curve Selection</a></li>
+        <li><a href="#zonationformation-names">Zonation/Formation Names</a></li>
+        <li><a href="#legend-and-axis">Legend and Axis</a></li>
+        <li><a href="#plot">Plot</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,38 +1841,24 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/PltPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/PltPlot.png" alt=""></p>
 <p>A PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated production data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed production data are loaded from well log files (*.las).</p>
-
 <h2 id="create-new-plt-plot">Create New PLT Plot</h2>
-
 <p>There are several ways to create new PLT Plots</p>
-
 <p><strong>From Project Tree in the Plot Main Window</strong></p>
-
 <ul>
 <li>Select context command <strong>New PLT Plot</strong> for the <em>PLT Plots</em> node.</li>
 </ul>
-
 <p><strong>From the Project Tree in the Main Window</strong></p>
-
 <ul>
 <li>Select context command <strong>New PLT Plot</strong> for a <em>Well Path</em> node or a <em>Simulation Well</em> node that has an associated well path.</li>
 </ul>
-
 <p><strong>From the 3D view</strong></p>
-
 <ul>
 <li>Right-click a well path, or a simulation well that has an associated well path, and select <strong>Well Plots -&gt; New PLT Plot</strong>.</li>
 </ul>
-
 <h2 id="plot-observed-data">Plot Observed Data</h2>
-
 <p>To be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:</p>
-
 <table>
 <thead>
 <tr>
@@ -1848,86 +1866,63 @@ if (!doNotTrack) {
 <th>Names</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Oil</td>
-<td><em>QOZT</em>, <em>QOIL</em>, _xxxx<em>QOIL</em></td>
+<td><em>QOZT</em>, <em>QOIL</em>, <em>xxxx_QOIL</em></td>
 </tr>
-
 <tr>
 <td>Gas</td>
-<td><em>QOZT</em>, <em>QGAS</em>, _xxxx<em>QGAS</em></td>
+<td><em>QOZT</em>, <em>QGAS</em>, <em>xxxx_QGAS</em></td>
 </tr>
-
 <tr>
 <td>Water</td>
-<td><em>QGZT</em>, <em>QWAT</em>, _xxxx<em>QWAT</em></td>
+<td><em>QGZT</em>, <em>QWAT</em>, <em>xxxx_QWAT</em></td>
 </tr>
-
 <tr>
 <td>Total</td>
-<td><em>QTZT</em>, <em>QTOT</em>, _xxxx<em>QTOT</em></td>
+<td><em>QTZT</em>, <em>QTOT</em>, <em>xxxx_QTOT</em></td>
 </tr>
 </tbody>
 </table>
-
 <p>To be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.</p>
-
-<p><img src="/images/plot-window/NoMdWarningDialog.png" alt="" /></p>
-
+<p><img src="/images/plot-window/NoMdWarningDialog.png" alt=""></p>
 <h2 id="property-editor">Property Editor</h2>
-
 <p>The property editor lets the user select which curves to display in the PLT plot.</p>
-
-<p><img src="/images/plot-window/PltPlotPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/PltPlotPropertyEditor.png" alt=""></p>
 <h3 id="well-name">Well Name</h3>
-
 <p>Select the well to display in the plot. Only observed well paths are displayed.</p>
-
 <h3 id="sources">Sources</h3>
-
 <p>After a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:</p>
-
 <ul>
 <li><strong>RFT File Cases</strong> &ndash; Simulation cases may have associated PLT data in <em>*.rft</em> file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword <code>WRFTPLT</code> in the Eclipse manual for information)</li>
 <li><strong>Grid Cases</strong> &ndash; Simulation cases</li>
 <li><strong>Observed Cases</strong> &ndash; Observed data imported from well log files and well path files</li>
 </ul>
-
 <p>When the user selects a source, time steps for that source appears in the <strong>Time Steps</strong> field.</p>
-
 <h3 id="time-steps">Time Steps</h3>
-
 <p>The <strong>Time Steps</strong> field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:</p>
-
 <ol>
 <li><strong>Exclusively grid cases selected</strong>. All available time steps for the selected grid cases are displayed.</li>
-<li><strong>Grid case(s) and observed data case selected</strong>. Time steps shown are:
-
+<li><strong>Grid case(s) and observed data case selected</strong>. Time steps shown are:</li>
+</ol>
 <ul>
 <li>The first time step from the merged time step list from all grid cases.</li>
 <li>If no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.</li>
-</ul></li>
+</ul>
+<ol start="3">
 <li><strong>Grid case(s) and RFT File case(s) selected</strong>. Same display logic as point 2.</li>
 <li><strong>All types of cases selected</strong>. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.</li>
 </ol>
-
 <p>Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: <strong>[ O ]</strong>, <strong>[ R G ]</strong>.</p>
-
 <ul>
 <li><strong>O</strong> &ndash; Time step belongs to observed data</li>
 <li><strong>R</strong> &ndash; Time step belongs to RFT data</li>
 <li><strong>G</strong> &ndash; Time step belongs to Grid data</li>
 </ul>
-
 <p>More than one letter for one single time step, means that the time step belongs to multiple case types.</p>
-
 <h3 id="curve-selection">Curve Selection</h3>
-
 <p>The curve selection group lets the user control which component(s) of the PLT data to display.</p>
-
 <ul>
 <li><strong>Standard Volume</strong> &ndash; Production data at standard conditions (normal air pressure)</li>
 <li><strong>Reservoir Volume</strong> &ndash; Production data at reservoir pressure (high air pressure)</li>
@@ -1936,56 +1931,44 @@ if (!doNotTrack) {
 <li><strong>Water</strong> &ndash; The water production component</li>
 <li><strong>Total</strong> &ndash; Total production</li>
 </ul>
-
-<h3 id="zonation-formation-names">Zonation/Formation Names</h3>
-
+<h3 id="zonationformation-names">Zonation/Formation Names</h3>
 <p>This property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.</p>
-
-<p><img src="/images/plot-window/RftPltFormationNames.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RftPltFormationNames.png" alt=""></p>
 <p>Please see the <a href="/3d-main-window/formations/">full documentation</a> on the formations property editor for details.</p>
 
-
-<div class="notices note" ><p>When the formation names property editor is used in the context of PLT plots, the fields <b>Trajectory</b> and <b>Simulation Well</b> are hidden because those values are given by the PLT plot definition.</p>
+<div class="notices note" ><p>When the formation names property editor is used in the context of PLT plots, the fields <!-- raw HTML omitted -->Trajectory<!-- raw HTML omitted --> and <!-- raw HTML omitted -->Simulation Well<!-- raw HTML omitted --> are hidden because those values are given by the PLT plot definition.</p>
 </div>
 
-
 <h3 id="legend-and-axis">Legend and Axis</h3>
-
-<p><img src="/images/plot-window/PltLegendAndAxis.png" alt="" /></p>
-
+<p><img src="/images/plot-window/PltLegendAndAxis.png" alt=""></p>
 <p>This property editor lets the user control visual properties for the legend and axis.</p>
-
 <ul>
 <li>Title and Legends
-
 <ul>
 <li><strong>Show Title</strong> &ndash; Toggle on/off title in plot</li>
 <li><strong>Show Legends</strong> &ndash; Toggle on/off legend in plot</li>
 <li><strong>Legend Orientation</strong> &ndash; Vertical or horizontal</li>
-</ul></li>
+</ul>
+</li>
 <li>X Axis Settings
-
 <ul>
 <li><strong>Logarithmic Scale</strong> &ndash; Toggle between linear and logarithmic</li>
 <li><strong>Min</strong> &ndash; Set X axis minimum value</li>
 <li><strong>Max</strong> &ndash; Set X axis maximum value</li>
 <li><strong>Show Grid Lines</strong> &ndash; Enable grid lines in background in plot</li>
-</ul></li>
+</ul>
+</li>
 <li>Depth Axis
-
 <ul>
 <li><strong>Type</strong> &ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)</li>
 <li><strong>Unit</strong> &ndash;</li>
 <li><strong>Min</strong> &ndash; Set depth axis minimum value</li>
 <li><strong>Max</strong> &ndash; Set depth axis maximum value</li>
-<li><strong>Show Grid Lines</strong> &ndash; Enable grid lines in background in plot
-<br /></li>
-</ul></li>
+<li><strong>Show Grid Lines</strong> &ndash; Enable grid lines in background in plot</li>
+</ul>
+</li>
 </ul>
-
 <h3 id="plot">Plot</h3>
-
 <p>The PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.</p>
 
 
@@ -2162,6 +2145,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2172,6 +2168,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3322,20 +3321,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/rftplot/index.html b/plot-window/rftplot/index.html
index 88416de3a5..d7832c688a 100644
--- a/plot-window/rftplot/index.html
+++ b/plot-window/rftplot/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>RFT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,21 +1802,19 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#create-new-rft-plot">Create New RFT Plot</a></li>
-<li><a href="#import-observed-rft-data">Import Observed RFT Data</a></li>
-<li><a href="#property-editor">Property Editor</a>
-<ul>
-<li><a href="#well-name">Well Name</a></li>
-<li><a href="#sources">Sources</a></li>
-<li><a href="#time-steps">Time Steps</a></li>
-<li><a href="#zonation-formation-names">Zonation/Formation Names</a></li>
-<li><a href="#legend-and-axis">Legend and Axis</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#create-new-rft-plot">Create New RFT Plot</a></li>
+    <li><a href="#import-observed-rft-data">Import Observed RFT Data</a></li>
+    <li><a href="#property-editor">Property Editor</a>
+      <ul>
+        <li><a href="#well-name">Well Name</a></li>
+        <li><a href="#sources">Sources</a></li>
+        <li><a href="#time-steps">Time Steps</a></li>
+        <li><a href="#zonationformation-names">Zonation/Formation Names</a></li>
+        <li><a href="#legend-and-axis">Legend and Axis</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1807,134 +1839,94 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/RftPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RftPlot.png" alt=""></p>
 <p>An RFT (<em>Repeated Formation Tester</em>) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD) or measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed pressure data are loaded from well log files (*.las).</p>
-
 <h2 id="create-new-rft-plot">Create New RFT Plot</h2>
-
 <p>There are several ways to create new RFT Plots.</p>
-
 <p><strong>From the Project Tree in the Plot Main Window</strong></p>
-
 <ul>
 <li>Select context command <strong>New RFT Plot</strong> for <em>Well Path</em> node or <em>RFT Plots</em> node.</li>
 </ul>
-
 <p><strong>From the Project Tree in the 3D Main Window</strong></p>
-
 <ul>
 <li>Select context command <strong>New RFT plot</strong> for a simulation well.</li>
 </ul>
-
 <p><strong>From a 3D view</strong></p>
-
 <ul>
 <li>Right-click a simulation well select <strong>Well Plots -&gt; New RFT Plot</strong>.</li>
 </ul>
-
 <h2 id="import-observed-rft-data">Import Observed RFT Data</h2>
-
-<p>To be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name <em>PRESSURE</em> or _PRES<em>FORM</em>. If the well log file itself does not contain a TVD column (named <em>TVDMSL</em>), a well path file (See <a href="/wells-and-completions/wellpaths/">Well Trajectories</a>) for the same well must also be imported to ResInsight.</p>
-
+<p>To be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name <em>PRESSURE</em> or <em>PRES_FORM</em>. If the well log file itself does not contain a TVD column (named <em>TVDMSL</em>), a well path file (See <a href="/wells-and-completions/wellpaths/">Well Trajectories</a>) for the same well must also be imported to ResInsight.</p>
 <p>If no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.</p>
-
-<p><img src="/images/plot-window/NoTvdWarningDialog.png" alt="" /></p>
-
+<p><img src="/images/plot-window/NoTvdWarningDialog.png" alt=""></p>
 <h2 id="property-editor">Property Editor</h2>
-
 <p>The property editor lets the user select which curves to display in the RFT plot.</p>
-
-<p><img src="/images/plot-window/RftPlotPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RftPlotPropertyEditor.png" alt=""></p>
 <h3 id="well-name">Well Name</h3>
-
-<p>Select the well to display in the plot. Wells postfixed by <em>&rsquo;(Well Path)&rsquo;</em> have an associated well trajectory loaded.</p>
-
+<p>Select the well to display in the plot. Wells postfixed by <em>'(Well Path)'</em> have an associated well trajectory loaded.</p>
 <h3 id="sources">Sources</h3>
-
 <p>After a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:</p>
-
 <ul>
 <li><strong>RFT File Cases</strong> &ndash; Simulation cases may have associated formation pressure data in <em>*.rft</em> file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword <code>WRFTPLT</code> in the Eclipse manual for information).</li>
 <li><strong>Grid Cases</strong> &ndash; The PRESSURE property in the 3D grid.</li>
 <li><strong>Observed Cases</strong> &ndash; Observed data imported from well log files.</li>
 </ul>
-
 <p>When the user selects one or more sources, a selection of their time steps appears in the <strong>Time Steps</strong> field.</p>
-
 <h3 id="time-steps">Time Steps</h3>
-
 <p>The <strong>Time Steps</strong> field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:</p>
-
 <ol>
 <li>If a single source or sources of the same type are selected, all available time steps in those sources are shown.</li>
-<li>If sources from two or tree types are selected, the time steps are filtered:
-
+<li>If sources from two or tree types are selected, the time steps are filtered:</li>
+</ol>
 <ul>
 <li>The time steps matching the observed case(s) time steps.</li>
 <li>If no time steps from a case match the observed time step, the two adjacent ones are shown.</li>
 <li>The first time step from any grid case(s) (as initial pressure reference).
 If the Observed data isn&rsquo;t selected, the RFT data serves as filter reference.</li>
-</ul></li>
-</ol>
-
+</ul>
 <p>Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: <strong>[ O ]</strong>, <strong>[ R G ]</strong>.</p>
-
 <ul>
 <li><strong>O</strong> &ndash; Time step has observed data</li>
 <li><strong>R</strong> &ndash; Time step has RFT data</li>
 <li><strong>G</strong> &ndash; Time step has Grid data</li>
 </ul>
-
 <p>More than one letter for one single time step, means that the time steps comes from multiple case types.</p>
-
-<h3 id="zonation-formation-names">Zonation/Formation Names</h3>
-
+<h3 id="zonationformation-names">Zonation/Formation Names</h3>
 <p>This property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.</p>
-
-<p><img src="/images/plot-window/RftPltFormationNames.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RftPltFormationNames.png" alt=""></p>
 <p>Please see the <a href="/3d-main-window/formations/">full documentation</a> on the formations property editor for details about formations.</p>
 
-
-<div class="notices note" ><p>When the formation names property editor is used in the context of RFT plots, the fields <b>Trajectory</b> and <b>Simulation Well</b> are hidden because those values are given by the RFT plot definition.</p>
+<div class="notices note" ><p>When the formation names property editor is used in the context of RFT plots, the fields <!-- raw HTML omitted -->Trajectory<!-- raw HTML omitted --> and <!-- raw HTML omitted -->Simulation Well<!-- raw HTML omitted --> are hidden because those values are given by the RFT plot definition.</p>
 </div>
 
-
 <h3 id="legend-and-axis">Legend and Axis</h3>
-
-<p><img src="/images/plot-window/RftLegendAndAxis.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RftLegendAndAxis.png" alt=""></p>
 <p>This property editor lets the user control visual properties for the legend and axis.</p>
-
 <ul>
 <li>Title and Legends
-
 <ul>
 <li><strong>Show Title</strong> &ndash; Toggle on/off title in plot</li>
 <li><strong>Show Legends</strong> &ndash; Toggle on/off legend in plot</li>
 <li><strong>Legend Orientation</strong> &ndash; Vertical or horizontal</li>
-</ul></li>
+</ul>
+</li>
 <li>X Axis Settings
-
 <ul>
 <li><strong>Logarithmic Scale</strong> &ndash; Toggle between linear and logarithmic</li>
 <li><strong>Min</strong> &ndash; Set X axis minimum value</li>
 <li><strong>Max</strong> &ndash; Set X axis maximum value</li>
 <li><strong>Show Grid Lines</strong> &ndash; Enable grid lines in background in plot</li>
-</ul></li>
+</ul>
+</li>
 <li>Depth Axis
-
 <ul>
 <li><strong>Type</strong> &ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)</li>
 <li><strong>Unit</strong> &ndash;</li>
 <li><strong>Min</strong> &ndash; Set depth axis minimum value</li>
 <li><strong>Max</strong> &ndash; Set depth axis maximum value</li>
 <li><strong>Show Grid Lines</strong> &ndash; Enable grid lines in background in plot</li>
-</ul></li>
+</ul>
+</li>
 </ul>
 
 
@@ -2111,6 +2103,19 @@ If the Observed data isn&rsquo;t selected, the RFT data serves as filter referen
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2121,6 +2126,9 @@ If the Observed data isn&rsquo;t selected, the RFT data serves as filter referen
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3271,20 +3279,20 @@ If the Observed data isn&rsquo;t selected, the RFT data serves as filter referen
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/saturationpressureplots/index.html b/plot-window/saturationpressureplots/index.html
index 37ac2c4cd9..52bb39b6e2 100644
--- a/plot-window/saturationpressureplots/index.html
+++ b/plot-window/saturationpressureplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Saturation Pressure Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1791,13 +1825,10 @@ if (!doNotTrack) {
 
 
 
-<p><img src="/images/plot-window/SaturationPressurePlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SaturationPressurePlot.png" alt=""></p>
 <p>A Saturation Pressure Plot a plot displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots. One Saturation Pressure Plot is created for each equilibrium region.</p>
-
 <p>To be able to create these plots, output of saturation pressures need to be specified in the <strong>SOLUTION</strong> section of the Eclipse &ldquo;.DATA&rdquo; file.</p>
-
-<p><img src="/images/plot-window/SaturationPressurePlotPropertyEditor.png" alt="" />
+<p><img src="/images/plot-window/SaturationPressurePlotPropertyEditor.png" alt="">
 To create these plots, right click on the view in the <strong>Property Editor</strong>, and select <strong>Create Saturation Pressure Plots</strong>. It is also possible to create these plots by right click on the item <strong>Saturation Pressure Plots</strong> in the <strong>Property Editor</strong> in the <strong>Plot Window</strong>.</p>
 
 
@@ -1974,6 +2005,19 @@ To create these plots, right click on the view in the <strong>Property Editor</s
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1984,6 +2028,9 @@ To create these plots, right click on the view in the <strong>Property Editor</s
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3134,20 +3181,20 @@ To create these plots, right click on the view in the <strong>Property Editor</s
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summarycrossplots/index.html b/plot-window/summarycrossplots/index.html
index fc86192aa3..de058e0182 100644
--- a/plot-window/summarycrossplots/index.html
+++ b/plot-window/summarycrossplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Cross Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#summary-cross-plot-curves">Summary Cross Plot Curves</a>
-<ul>
-<li><a href="#cross-plotting">Cross Plotting</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#summary-cross-plot-curves">Summary Cross Plot Curves</a>
+      <ul>
+        <li><a href="#cross-plotting">Cross Plotting</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,36 +1833,23 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/SummaryCrossPlot.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCrossPlot.png" alt=""></p>
 <p>A Summary Cross Plot is a window displaying a graph in the main area of the <strong>Plot Main Window</strong>. It is very similar to an ordinary <a href="/plot-window/summaryplots/">Summary Plot</a>, but there are some differences:</p>
-
 <ul>
 <li>Summary Cross Plot displays one vector against another vector, not one vector against time.</li>
 <li>Not possible to paste Excel/CSV data to a summary cross plot.</li>
 <li>Summary cross plots have no <a href="/plot-window/summaryploteditor/">Plot Editor</a>.</li>
 </ul>
-
 <p>The only way to create a new Summary Cross Plot, is to select the context command <img src="https://resinsight.org/images/plot-window/SummaryPlot16x16.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>New Summary Cross Plot</strong> on the <strong>Plot Main Window -&gt; Project Tree -&gt; Summary Cross Plots</strong> item.</p>
-
 <h2 id="summary-cross-plot-curves">Summary Cross Plot Curves</h2>
-
 <p>New Summary Cross Plot curves are created by using the context command <img src="https://resinsight.org/images/plot-window/SummaryCurve16x16.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>New Summary Cross Plot Curve</strong> on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the <strong>Summary Cross Plot Curve</strong> property editor.</p>
-
-<p><img src="/images/plot-window/SummaryCrossPlotCurvePropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCrossPlotCurvePropertyEditor.png" alt=""></p>
 <p>In this property editor, the editor group called <strong>Summary Vector</strong>, has been replaced by two vector selection groups <strong>Summary Vector Y</strong> and <strong>Summary Vector X</strong>, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The <strong>Summary Vector X</strong> group is missing the <strong>Axis</strong> field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the <a href="/plot-window/summaryplots/#summary-curves">detailed description</a>.</p>
-
 <h3 id="cross-plotting">Cross Plotting</h3>
-
 <p>Cross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.</p>
-
 <p>When a current time step <strong>T</strong> in input vector <strong>A</strong> is not found in input vector <strong>B</strong>, ResInsight interpolates between the time steps before and after <strong>T</strong> in vector <strong>B</strong>. In this way, ResInsight calculates an interpolated value for time step <strong>T</strong> from vector <strong>B</strong>. The same happens when a time step in vector <strong>B</strong> is not found in vector <strong>A</strong>.</p>
-
 <p>If either the value at the current time step or one of the values involved in interpolation are <strong>NULL</strong>, the resulting vector will have a <strong>NULL</strong> value at the current time step. This is displayed as a &lsquo;hole&rsquo; in the cross plot curve.</p>
 
 
@@ -2007,6 +2026,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2017,6 +2049,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3167,20 +3202,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryploteditor/index.html b/plot-window/summaryploteditor/index.html
index 625e13f293..6edd8f4aec 100644
--- a/plot-window/summaryploteditor/index.html
+++ b/plot-window/summaryploteditor/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Editor :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,24 +1802,23 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#selection-fields">Selection Fields</a>
-<ul>
-<li><a href="#sources">Sources</a></li>
-<li><a href="#summary-types-and-item-selection-fields">Summary Types and Item Selection Fields</a></li>
-<li><a href="#summaries">Summaries</a></li>
-</ul></li>
-<li><a href="#preview-plot">Preview Plot</a>
-<ul>
-<li><a href="#plot-and-curve-name-configuration">Plot and Curve Name Configuration</a></li>
-<li><a href="#curve-appearance-assignment">Curve Appearance Assignment</a></li>
-<li><a href="#curves">Curves</a></li>
-<li><a href="#target-plot">Target Plot</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#selection-fields">Selection Fields</a>
+      <ul>
+        <li><a href="#sources">Sources</a></li>
+        <li><a href="#summary-types-and-item-selection-fields">Summary Types and Item Selection Fields</a></li>
+        <li><a href="#summaries">Summaries</a></li>
+      </ul>
+    </li>
+    <li><a href="#preview-plot">Preview Plot</a>
+      <ul>
+        <li><a href="#plot-and-curve-name-configuration">Plot and Curve Name Configuration</a></li>
+        <li><a href="#curve-appearance-assignment">Curve Appearance Assignment</a></li>
+        <li><a href="#curves">Curves</a></li>
+        <li><a href="#target-plot">Target Plot</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1810,149 +1843,112 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/SummaryPlotEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotEditor.png" alt=""></p>
 <p>The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.</p>
-
 <p>The upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the <strong>Summary Type</strong> currently highlighted.</p>
 
-
-<div class="notices note" ><p>In this context <b>highlighted</b> means the marked item with a different background color, while <b>selected</b> means an item or items that have a ticked check box.</p>
+<div class="notices note" ><p>In this context <!-- raw HTML omitted -->highlighted<!-- raw HTML omitted --> means the marked item with a different background color, while <!-- raw HTML omitted -->selected<!-- raw HTML omitted --> means an item or items that have a ticked check box.</p>
 </div>
 
-
 <h2 id="selection-fields">Selection Fields</h2>
-
 <p>This section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.</p>
-
 <h3 id="sources">Sources</h3>
-
 <p>This field contains all imported cases and ensembles. Select the case(s) and/or ensemble(s) to display in the plot.</p>
-
 <h3 id="summary-types-and-item-selection-fields">Summary Types and Item Selection Fields</h3>
-
 <p>In the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.</p>
-
 <ul>
 <li><strong>Field</strong> &ndash; Select Field related vectors only</li>
 <li><strong>Aquifer</strong> &ndash; Select Aquifer category vectors only</li>
-<li><strong>Network</strong> &ndash; Select Network category vectors only<br /></li>
+<li><strong>Network</strong> &ndash; Select Network category vectors only</li>
 <li><strong>Misc</strong> &ndash; Select vectors in the Misc category only</li>
-<li><strong>Region</strong> &ndash; Select Region related vectors only<br />
-
+<li><strong>Region</strong> &ndash; Select Region related vectors only
 <ul>
 <li><strong>Region number</strong> &ndash; Select the Region number</li>
-</ul></li>
-<li><strong>Region-Region</strong> &ndash; Select Region to Region related vectors only<br />
-
+</ul>
+</li>
+<li><strong>Region-Region</strong> &ndash; Select Region to Region related vectors only
 <ul>
 <li><strong>Region numbers</strong> &ndash; Select the Region to Region numbers</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Group</strong> - Select Group related vectors only
-
 <ul>
 <li><strong>Group name</strong> &ndash;  Select Group name</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Well</strong> &ndash; Select Well related vectors only
-
 <ul>
 <li><strong>Well name</strong> &ndash;  Select Well name</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Completion</strong>   &ndash; Select Completion related vectors only
-
 <ul>
 <li><strong>Well name</strong> &ndash;  Select Well name</li>
 <li><strong>I, J, K</strong> &ndash; Select the I, J, K values of the completion</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Lgr-Completion</strong> &ndash; Select Completion in LGR related vectors only
-
 <ul>
 <li><strong>Well name</strong> &ndash;  Select Well name</li>
 <li><strong>Lgr name</strong> &ndash; Select Lgr name</li>
 <li><strong>I, J, K</strong> &ndash; Select the I, J, K values of the completion in the Lgr.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Lgr-Well</strong> &ndash; Select Well in LGR related vectors only
-
 <ul>
 <li><strong>Well name</strong> &ndash; Select Well name</li>
 <li><strong>Lgr name</strong> &ndash; Select Lgr name</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Segment</strong> &ndash; Select Segment related vectors only
-
 <ul>
 <li><strong>Well name</strong> &ndash; Select Well name</li>
 <li><strong>Segment number</strong> &ndash; Select the segment number</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Block</strong> &ndash; Select I, J, K &ndash; Block related vectors only
-
 <ul>
 <li><strong>I, J, K</strong> &ndash; Select the I, J, K values of the Block.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Lgr-Block</strong> &ndash; Select I, J, K - Block in LGR related vectors only
-
 <ul>
 <li><strong>Lgr name</strong> &ndash; Select Lgr name</li>
 <li><strong>I, J, K</strong> &ndash; Select the I, J, K values of the Block in the Lgr.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Calculated</strong> &ndash; Select calculated vectors created by the <a href="/plot-window/curvecalculator/">curve calculator</a>.</li>
 <li><strong>Imported</strong> &ndash; Select observed data vectors <a href="/import/observeddata/">imported from file</a> (e.g. CSV, RSM files)</li>
 </ul>
-
 <h3 id="summaries">Summaries</h3>
-
 <p>This field contains the summaries/vectors for the highlighted summary category.</p>
-
 <h2 id="preview-plot">Preview Plot</h2>
-
 <p>When a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the <em>Curve Name Configuration</em> and <em>Curve Appearance Assignment</em> fields.</p>
-
 <h3 id="plot-and-curve-name-configuration">Plot and Curve Name Configuration</h3>
-
-<p><img src="/images/plot-window/CurveNameConfig.png" alt="" /></p>
-
+<p><img src="/images/plot-window/CurveNameConfig.png" alt=""></p>
 <p>The checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.</p>
-
 <h3 id="curve-appearance-assignment">Curve Appearance Assignment</h3>
-
 <p>Curves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.</p>
-
 <p>These assignments can be controlled using the options in the <strong>Curve Appearance Assignment</strong> group.</p>
-
-<p><img src="/images/plot-window/CurveAppearanceAssignment.png" alt="" /></p>
-
+<p><img src="/images/plot-window/CurveAppearanceAssignment.png" alt=""></p>
 <p>When set to <strong>Auto</strong>, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.</p>
-
 <p>When disabling the <strong>Auto</strong> option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.</p>
-
 <p>The <strong>Apply</strong> button must be clicked to apply the new settings to all curves.</p>
-
 <p>The curve appearance settings apply to single summary curves only and do not affect ensemble curve sets. Curve sets receive their appearance automatically from a set of color ranges.</p>
 
-
 <div class="notices note" ><p>Assignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps.
-Press the <b>Apply</b> button to apply consistent appearance settings according to the current curve selection.</p>
+Press the <!-- raw HTML omitted -->Apply<!-- raw HTML omitted --> button to apply consistent appearance settings according to the current curve selection.</p>
 </div>
 
-
 <h3 id="curves">Curves</h3>
-
-<p><img src="/images/plot-window/SummaryPreviewCurves.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPreviewCurves.png" alt=""></p>
 <p>The curves field displays all summary curves and ensemble curve sets matching the settings in the selection fields. Those are separated in two groups, <strong>Summary Curves</strong> and <strong>Ensemble Curve Sets</strong>. The check box at each item controls which items are displayed in the preview plot.</p>
-
 <p>If the user make a selection that will result in a huge number of ensemble curves, ResInsight will display a drawing performance warning, and the newly created curve set(s) are toggled off by default.</p>
-
 <h3 id="target-plot">Target Plot</h3>
-
-<p><img src="/images/plot-window/TargetPlot_new.png" alt="" />
-<img src="/images/plot-window/TargetPlot_1.png" alt="" /></p>
-
+<p><img src="/images/plot-window/TargetPlot_new.png" alt="">
+<img src="/images/plot-window/TargetPlot_1.png" alt=""></p>
 <p>In the bottom of the dialog window <strong>Target Plot</strong> may be specified. The target plot is the summary plot that will receive the selected curves when the <strong>OK</strong> or <strong>Apply</strong> button is clicked.</p>
-
 <p>By default the target plot is set to <strong>(new plot)</strong> or to the plot selected for editing when invoking the command.</p>
-
 <p>Setting the target plot to a different plot will add the selected curves to that plot when pressing the the <strong>OK</strong> or <strong>Apply</strong> button.</p>
 
 
@@ -2129,6 +2125,19 @@ Press the <b>Apply</b> button to apply consistent appearance settings according
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2139,6 +2148,9 @@ Press the <b>Apply</b> button to apply consistent appearance settings according
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3289,20 +3301,20 @@ Press the <b>Apply</b> button to apply consistent appearance settings according
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplots/index.html b/plot-window/summaryplots/index.html
index c72ead2db0..ef16e8491e 100644
--- a/plot-window/summaryplots/index.html
+++ b/plot-window/summaryplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,38 +1802,39 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#plot-data">Plot Data</a>
-<ul>
-<li><a href="#summary-files">SUMMARY Files</a></li>
-<li><a href="#summary-case-groups">Summary Case Groups</a></li>
-<li><a href="#observed-data">Observed Data</a></li>
-<li><a href="#grid-cell-time-history-curve">Grid Cell Time History Curve</a></li>
-<li><a href="#pasted-ascii-curves">Pasted Ascii Curves</a></li>
-</ul></li>
-<li><a href="#summary-plots">Summary Plots</a>
-<ul>
-<li><a href="#property-editor">Property Editor</a></li>
-<li><a href="#time-axis-properties">Time Axis Properties</a></li>
-<li><a href="#y-axis-properties">Y-axis Properties</a></li>
-<li><a href="#plot-mouse-interaction">Plot Mouse Interaction</a></li>
-<li><a href="#curve-highlight">Curve Highlight</a></li>
-<li><a href="#accessing-the-plot-data">Accessing the Plot Data</a></li>
-</ul></li>
-<li><a href="#editing-properties-of-single-summary-curve">Editing properties of single Summary Curve</a>
-<ul>
-<li><a href="#summary-vector">Summary Vector</a></li>
-<li><a href="#curve-name">Curve Name</a></li>
-</ul></li>
-<li><a href="#copy-and-paste">Copy and Paste</a></li>
-<li><a href="#recursive-summary-file-import">Recursive summary file import</a>
-<ul>
-<li><a href="#origin-files">Origin Files</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#plot-data">Plot Data</a>
+      <ul>
+        <li><a href="#summary-files">SUMMARY Files</a></li>
+        <li><a href="#summary-case-groups">Summary Case Groups</a></li>
+        <li><a href="#observed-data">Observed Data</a></li>
+        <li><a href="#grid-cell-time-history-curve">Grid Cell Time History Curve</a></li>
+        <li><a href="#pasted-ascii-curves">Pasted Ascii Curves</a></li>
+      </ul>
+    </li>
+    <li><a href="#summary-plots">Summary Plots</a>
+      <ul>
+        <li><a href="#property-editor">Property Editor</a></li>
+        <li><a href="#time-axis-properties">Time Axis Properties</a></li>
+        <li><a href="#y-axis-properties">Y-axis Properties</a></li>
+        <li><a href="#plot-mouse-interaction">Plot Mouse Interaction</a></li>
+        <li><a href="#curve-highlight">Curve Highlight</a></li>
+        <li><a href="#accessing-the-plot-data">Accessing the Plot Data</a></li>
+      </ul>
+    </li>
+    <li><a href="#editing-properties-of-single-summary-curve">Editing properties of single Summary Curve</a>
+      <ul>
+        <li><a href="#summary-vector">Summary Vector</a></li>
+        <li><a href="#curve-name">Curve Name</a></li>
+      </ul>
+    </li>
+    <li><a href="#copy-and-paste">Copy and Paste</a></li>
+    <li><a href="#recursive-summary-file-import">Recursive summary file import</a>
+      <ul>
+        <li><a href="#origin-files">Origin Files</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1824,91 +1859,61 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/ResInsightMainPlotMediumSize.png" alt="" /></p>
-
+<p><img src="/images/plot-window/ResInsightMainPlotMediumSize.png" alt=""></p>
 <p>A Summary Plot is a window displaying a graph in the main area of the <strong>Plot Main Window</strong>. As described below, a Summary Plot can contain Summary Curves, Grid time history curves, and pasted ascii curves.</p>
-
-<p>A new Summary Plot can be created by using the right-click menu of <strong>Summary Plots</strong> in the <strong>Plot Project Tree</strong> and activate
+<p>A new Summary Plot can be created by using the right-click menu of <strong>Summary Plots</strong> in the <strong>Plot Project Tree</strong> and activate 
 <img src="https://resinsight.org/images/plot-window/SummaryPlot16x16.png" style="display:inline; vertical-align:middle; margin:0">
- <strong>Open Summary Plot Editor</strong> or
+ <strong>Open Summary Plot Editor</strong> or 
 <img src="https://resinsight.org/images/plot-window/SummaryPlot16x16.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>New Summary Plot</strong>.</p>
 
-
-<div class="notices info" ><p>If you have many open plots, it can be useful to collapse all other plots by activating <strong>Collapse Other Plots</strong> from right-click menu of a plot in the <b>Plot Project Tree</b>.</p>
+<div class="notices info" ><p>If you have many open plots, it can be useful to collapse all other plots by activating <strong>Collapse Other Plots</strong> from right-click menu of a plot in the <!-- raw HTML omitted -->Plot Project Tree<!-- raw HTML omitted -->.</p>
 </div>
 
-
 <h2 id="plot-data">Plot Data</h2>
-
 <p>ResInsight can create summary plots based on vectors from SUMMARY files ( <em><code>*.SMSPEC</code></em> ), imported Observed Time History Data, Grid Cell Time history Curve, and pasted ascii curves.</p>
-
 <h3 id="summary-files">SUMMARY Files</h3>
-
 <p>When opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a <strong>Summary Case</strong>.
 Summary files can also be imported directly using one of the following commands in the <strong>File-&gt;Import-&gt;Summary Cases</strong> menu:</p>
-
 <ul>
 <li><strong>Import Summary Case</strong>: Brings up the standard file selection dialog. Multiple selections are allowed.</li>
 <li><strong>Import Summary Cases Recursively</strong>: Brings up the recursive file selection dialog. This dialog is described in details <a href="#recursive-summary-file-import">below</a></li>
 <li><strong>Import Summary Case Group</strong>: Brings up the recursive file selection dialog. All files selected are automatically grouped in ResInsight.</li>
 <li><strong>Import Ensemble</strong>: Similar to the above, but in addition to just create a group, ResInsight performs some extra checking related to ensembles and converts the group to an ensemble. See <a href="/plot-window/ensembleplotting/">ensemble support description</a>.</li>
 </ul>
-
 <p>These commands can also be accessed in the right-click menu for the <strong>Summary Cases</strong> entry in the <strong>Plot Main Window Project Tree</strong> under which the imported cases will also be listed.</p>
-
 <p>During summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed. Origin file support is described <a href="#origin-files">below</a>.</p>
-
 <h3 id="summary-case-groups">Summary Case Groups</h3>
-
 <p>A selection of cases can be grouped by right-clicking  a selection of summary cases and selecting the command <strong>Group Summary Cases</strong>. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the <a href="/plot-window/summaryploteditor/">Summary Plot Editor</a>.</p>
-
 <h3 id="observed-data">Observed Data</h3>
-
 <p>See <a href="/import/observeddata/">Observed Time History Data</a></p>
-
 <h3 id="grid-cell-time-history-curve">Grid Cell Time History Curve</h3>
-
-<p>Time history curves from a grid cell property can also be added to a Summary Plot.
+<p>Time history curves from a grid cell property can also be added to a Summary Plot. 
 See <a href="/3d-main-window/resultinspection/#result-plot">Result Inspection</a>.</p>
-
 <h3 id="pasted-ascii-curves">Pasted Ascii Curves</h3>
-
 <p>You can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command <strong>Paste Excel Data to Summary Plot</strong>. See <a href="/import/pasteexceltimedata/">Paste Excel Time History Data</a>.</p>
-
 <h2 id="summary-plots">Summary Plots</h2>
-
-<p>Summary plots are created in the <strong>Plot Project Tree</strong> by right-clicking <strong>Summary Plots</strong> and selecting
+<p>Summary plots are created in the <strong>Plot Project Tree</strong> by right-clicking <strong>Summary Plots</strong> and selecting 
 <img src="https://resinsight.org/images/plot-window/SummaryPlot16x16.png" style="display:inline; vertical-align:middle; margin:0">
- <strong>Open Summary Plot Editor</strong> or
+ <strong>Open Summary Plot Editor</strong> or 
 <img src="https://resinsight.org/images/plot-window/SummaryPlot16x16.png" style="display:inline; vertical-align:middle; margin:0">
- <strong>New Summary Plot</strong>.
-Having created a Summary Plot, its entry is listed in the Plot Project Tree.
+ <strong>New Summary Plot</strong>. 
+Having created a Summary Plot, its entry is listed in the Plot Project Tree. 
 The settings of the Plot are controlled by its sub items in the <strong>Plot Project Tree</strong> and the <strong>Property Editor</strong> as described below.</p>
-
-<p><img src="/images/plot-window/SummaryPlotTree.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotTree.png" alt=""></p>
 <h3 id="property-editor">Property Editor</h3>
-
 <p>The Property Editor allows <strong>Text-Based Curve Creation</strong> based on selected sources and setting <strong>General Plot Options</strong>.</p>
-
-<p><img src="/images/plot-window/SummaryPlotPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotPropertyEditor.png" alt=""></p>
 <p><strong>Text-Based Curve Creation</strong> allows specification of a list of vectors for plotting based on selected sources.
 The vectors to plot are specified by the following syntax:
 <code>&lt;vectorshortname&gt;[:&lt;item&gt;[:&lt;subitem&gt;[:i,j,k]]]</code>.
 The specification of vectors allows use of wildcards and multiple entries separated by space:</p>
-
 <ul>
 <li><code>WOPT:*</code>: One total oil production curve for each well.</li>
 <li><code>FOPT FWPT</code>: Two curves with oil and water total production.</li>
 <li><code>BPR:15,28,*</code>: Oil phase pressure for all blocks along k as separate curves.</li>
 </ul>
-
 <p><strong>General Plot Options</strong> allows the following settings:</p>
-
 <ul>
 <li><strong>Show Title</strong> &ndash; Toggles whether to show the axis title</li>
 <li><strong>Auto Title</strong> &ndash; If enabled, the Plot title is derived automatically</li>
@@ -1917,215 +1922,175 @@ The specification of vectors allows use of wildcards and multiple entries separa
 <li><strong>Legend Font Size</strong> &ndash; Font size to be used in plot</li>
 <li><strong>Normalize all curves</strong> &ndash; Scales all curves into the range 0.0-1.0</li>
 </ul>
-
 <h3 id="time-axis-properties">Time Axis Properties</h3>
-
-<p><img src="/images/plot-window/SummaryTimeAxisProperties.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryTimeAxisProperties.png" alt=""></p>
 <ul>
 <li><strong>Axis Title</strong>
-
 <ul>
 <li><strong>Show Title</strong> &ndash; Toggles whether to show the axis title</li>
 <li><strong>Title</strong> &ndash; A user defined name for the axis</li>
 <li><strong>Title Position</strong> &ndash;  Either <em>Center</em> or <em>At End</em></li>
 <li><strong>Font Size</strong> &ndash; The font size used for the axis title</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Time Values</strong>
-
 <ul>
 <li><strong>Time Mode</strong> &ndash; Option to show the time from <em>Simulation Start</em>, or as real date-times.</li>
 <li><strong>Max</strong>/<strong>Min</strong> &ndash; The range of visible date/time in the Plot.</li>
 <li><strong>Automatic Date/Time labels</strong> &ndash; Option to invoke automatic date/time labels.</li>
 <li><strong>Font Size</strong> &ndash; The font size used for the date/time axis ticks, c.f. <a href="/misc/preferences/">Preferences</a> for default.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Date/Time Label Format</strong>
-
 <ul>
 <li><strong>Date Label Format</strong> &ndash; Date format for the time axis, c.f. <a href="/misc/preferences/">Preferences</a> for default.</li>
 <li><strong>Time Label Format</strong> &ndash; Time format for the time axis, c.f. <a href="/misc/preferences/">Preferences</a> for default.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <h3 id="y-axis-properties">Y-axis Properties</h3>
-
-<p><img src="/images/plot-window/summary_plot_yaxis_properties.png" alt="" /></p>
-
+<p><img src="/images/plot-window/summary_plot_yaxis_properties.png" alt=""></p>
 <ul>
 <li><strong>Title Text</strong>
-
 <ul>
 <li><strong>Auto Title</strong> &ndash; If enabled, the y-axis title is derived automatically with the following options:
-
 <ul>
 <li><strong>Names</strong> &ndash; Add quantity long name to y-axis title.</li>
 <li><strong>Acronyms</strong> &ndash; Add quantity acronym to y-axis title.</li>
 <li><strong>Units</strong> - Add unit of quantity to y-axis title.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Title</strong> &ndash; If <strong>Auto Title</strong> is disabled, the <strong>Title</strong> field emerges to facilitate manual setting of plot title.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Title Layout</strong>
-
 <ul>
 <li><strong>Title Position</strong> &ndash; Controls the position of the title; <em>Center</em> or <em>At End</em>.</li>
 <li><strong>Font Size</strong> &ndash;  Defines the font size used for the axis title.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Axis Values</strong>
-
 <ul>
 <li><strong>Logarithmic Scale</strong>  - Draw plot curves using a logarithmic scale.</li>
 <li><strong>Invert Axis</strong>  - Invert the axis, e.g. when depth is represented by the Y-axis.</li>
 <li><strong>Number Format</strong> &ndash; Defines how the legend numbers are formatted.
-
 <ul>
 <li><strong>Auto</strong> &ndash; Legend numbers are displayed by either scientific or decimal notation depending on actual value.</li>
 <li><strong>Decimal</strong> &ndash; Legend numbers are displayed using decimal notation.</li>
 <li><strong>Scientific</strong> &ndash; Legend numbers are displayed using scientific notation (e.g. 1.2e+6).</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Number of Decimals</strong> &ndash; Controls the number of digits after &ldquo;.&rdquo; for  <strong>Decimal</strong> and <strong>Scientific</strong>.</li>
 <li><strong>Scale Factor</strong> &ndash; Displays the y-axis values by multiplying with a specific scale factor for <strong>Decimal</strong> and <strong>Scientific</strong>.</li>
 <li><strong>Max and Min</strong> &ndash; Defines the visible y-range.</li>
-<li><strong>Font Size</strong> &ndash; The font size for showing values at the axis ticks.<br /></li>
-</ul></li>
+<li><strong>Font Size</strong> &ndash; The font size for showing values at the axis ticks.</li>
+</ul>
+</li>
 </ul>
-
 <h3 id="plot-mouse-interaction">Plot Mouse Interaction</h3>
-
 <ul>
 <li><strong>Value Tracking</strong> &ndash; When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip.</li>
 <li><strong>Selection</strong> &ndash; Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:
-
 <ul>
 <li>The closest curve.</li>
 <li>Each of the Plot Axes.</li>
 <li>The Plot itself if none of the above is hit and the Plot window is activated by the mouse click.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Window Zoom</strong> &ndash; Window zoom is available by dragging the mouse when the left mouse button is pressed. Use <img src="https://resinsight.org/images/plot-window/ZoomAll16x16.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Zoom All</strong> to restore default zoom level.</li>
 <li><strong>Wheel Zoom</strong> &ndash; The mouse wheel will zoom the plot in and out towards the current mouse cursor position.</li>
 </ul>
-
 <h3 id="curve-highlight">Curve Highlight</h3>
-
-<p><img src="/images/plot-window/SummaryCurveHighlight.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCurveHighlight.png" alt=""></p>
 <p>Summary curves will be highlighted when left-clicked in a plot. This allows for detailed investigation on curve values when many curves are plotted. All other curves can be hidden by activating the right-click menu of a plot, and select <strong>On - Others Off</strong></p>
-
 <h3 id="accessing-the-plot-data">Accessing the Plot Data</h3>
-
-<p>Right-clicking a plot and selecting <strong>Show Plot Data</strong> will open a window containing the plot data as text columns.
+<p>Right-clicking a plot and selecting <strong>Show Plot Data</strong> will open a window containing the plot data as text columns. 
 This dialog supports plot data displayed by day, week, month, quarter, half year and year.</p>
-
 <p>The text content of this window is easy to copy and paste into Excel or other tools for further processing.
 It is also possible to save the text data to a file directly by using the right-click command <strong>Export Plot Data to Text File</strong>.</p>
-
 <h2 id="editing-properties-of-single-summary-curve">Editing properties of single Summary Curve</h2>
-
 <p>Selecting a specific Summary Curve is possible via the <strong>Plot Project Tree</strong>.</p>
-
-<p><img src="/images/plot-window/SummaryCurveSelection.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCurveSelection.png" alt=""></p>
 <p>Having selected a Summary Curve, its properties are shown by the <strong>Property Editor</strong>.</p>
-
-<p><img src="/images/plot-window/summary_curve_properties.png" alt="" /></p>
-
+<p><img src="/images/plot-window/summary_curve_properties.png" alt=""></p>
 <p>As seen, the Property Editor organizes the available options into the following groups:</p>
-
 <ul>
 <li><strong>Summary Vector</strong> &ndash; Options to select case, vector to plot, axis specification, and error bars.</li>
 <li><strong>Appearance</strong> &ndash; Options to control curve color, symbols, line style etc.</li>
 <li><strong>Curve Name</strong> &ndash; Controls how the curve is labeled in the legend.</li>
 <li><strong>Advanced</strong> &ndash; Specification of additional options.</li>
 </ul>
-
 <h3 id="summary-vector">Summary Vector</h3>
-
 <p>This group of options is used to define summary vector data that the curve will display.</p>
-
 <ul>
 <li><strong>Case</strong> &ndash; Selects the imported Summary or Observed Data case to use as source.</li>
 <li><strong>Vector</strong> &ndash; Displays the acronym of the selected vector.</li>
 <li><strong>Axis</strong> &ndash; Controls whether the curve is to be associated with the left or right Y-Axis.</li>
 </ul>
-
-<p>Selection of vector is performed using a vector acronym or pressing the button to the right.
+<p>Selection of vector is performed using a vector acronym or pressing the button to the right. 
 Pressing the button opens a dialog similar to the <a href="/plot-window/summaryploteditor/">Summary Plot Editor</a>.</p>
 
-
-<div class="notices note" ><p>Switching the Y-Axis for several curves in one go can be done using the context command <b>Switch Plot Axis</b>.</p>
+<div class="notices note" ><p>Switching the Y-Axis for several curves in one go can be done using the context command <!-- raw HTML omitted -->Switch Plot Axis<!-- raw HTML omitted -->.</p>
 </div>
 
-
 <h3 id="curve-name">Curve Name</h3>
-
 <p>The user can control the curve name used in the plot legend by the following options:</p>
-
 <ul>
 <li><strong>Contribute To Legend</strong> &ndash; This option controls whether the curve will be visible in the plot legend. A curve with an empty name will be removed from legend.</li>
 <li><strong>Auto Name</strong> &ndash; If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group.</li>
 <li><strong>Curve Name</strong> &ndash; If <strong>Auto Name</strong> is off, you can enter a curve name here. If empty, the curve will be removed from the legend, but still visible in the plot.</li>
 <li><strong>Case Name, Vector name &hellip;</strong> etc. &ndash; These options controls what part of the summary vector information to use in the curve auto-name.</li>
 </ul>
-
 <h2 id="copy-and-paste">Copy and Paste</h2>
-
 <p>Copy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V).</p>
-
 <h2 id="recursive-summary-file-import">Recursive summary file import</h2>
-
 <p>When using the standard file selection dialog, the user is limited to select files in one directory only. If the interesting files are distributed over multiple directories, the dialog has to be opened once for each directory. The recursive file selection dialog is created to circumvent this limitation. This dialog is able to search a directory tree for files matching a specified pattern.</p>
-
-<p><img src="/images/plot-window/RecursiveImportDialog2.png" alt="" /></p>
-
+<p><img src="/images/plot-window/RecursiveImportDialog2.png" alt=""></p>
 <p>The dialog consists of the following fields:</p>
-
 <ul>
-<li><strong>Path Pattern</strong>: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single &ldquo;*<em>&rdquo; (eg. &ldquo;/home/</em>&rdquo;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by &ldquo;&hellip;&rdquo; in the <strong>Effective Filter</strong> label below.
-
+<li><strong>Path Pattern</strong>: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single &ldquo;**&rdquo; (eg. &ldquo;/home/*&quot;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by &ldquo;&hellip;&rdquo; in the <strong>Effective Filter</strong> label below.
 <ul>
 <li><strong>*</strong> Matches any number of any characters except the path separator</li>
 <li><strong>?</strong> Matches one character exception the directory separator</li>
 <li><strong>[abc]</strong> Matches one of the specified characters. Ex. a, b or c</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>File Pattern</strong>: The search pattern that applies to the file name.</li>
 <li><strong>Effective Filter</strong>: The effective filter displays the resulting full path search pattern. It is updated on the fly as the user edits the pattern fields. A text string of &ldquo;&hellip;&rdquo; indicates a complete recursive directory search.</li>
 </ul>
-
 <p>After pressing the <strong>Find</strong> button, a file search is performed in the root directory and the directories below matching the path pattern. The files found are presented in a list, where the user can check/uncheck each file individually.</p>
-
 <p>When the <strong>OK</strong> button is pressed, all checked files are imported.</p>
-
 <h3 id="origin-files">Origin Files</h3>
-
-<p><img src="/images/plot-window/OriginFileDialog.png" alt="" /></p>
-
+<p><img src="/images/plot-window/OriginFileDialog.png" alt=""></p>
 <p>During summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed.</p>
-
 <p>Depending on what triggered the summary file import, the dialog shows slightly different information. If the summary file import was triggered by a grid file import, the dialog displays information about grid files in addition to the summary origin file(s). If the summary file was imported directly, information about grid files are not relevant and thus not displayed.</p>
-
 <p>The dialog contents are organized in groups:</p>
-
 <ul>
 <li><strong>Current Grid and Summary Files</strong> or <strong>Current Summary Files</strong>: This group displays the name of the main summary file to import. If the import is triggered by a grid file import, the name of the grid file is also displayed.</li>
 <li><strong>Origin Summary Files</strong>: This group displays the names of the origin summary file(s) found. If there are more than one file listed, it means that the found origin file also has an origin file. ResInsight will search the &ldquo;chain&rdquo; of summary origin files until it reaches the end.
-
 <ul>
-<li><strong>Import Options</strong> There are three options to control how origin summary file are imported</li>
+<li><strong>Import Options</strong> There are three options to control how origin summary file are imported
+<ul>
 <li><strong>Unified</strong>: The main summary files and all origin files are imported into one single summary case</li>
 <li><strong>Separate Cases</strong>: The main files and all origin files are imported into separate summary cases</li>
 <li><strong>Skip</strong>: Only the main summary file is imported. The origin summary files are skipped.</li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li><strong>Origin Grid Files</strong>: If the summary file import was triggered by a grid file import, this group is visible. It contains a list of the grid files associated to the origin summary files
-
 <ul>
-<li><strong>Import Options</strong> There are two options to control how the grid files are imported</li>
+<li><strong>Import Options</strong> There are two options to control how the grid files are imported
+<ul>
 <li><strong>Separate Cases</strong>: All &ldquo;origin&rdquo; grid files are imported into separate grid cases</li>
 <li><strong>Skip</strong>: Only the main grid file is imported. The &ldquo;origin&rdquo; grid files are skipped.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
+</li>
+</ul>
 <p>By default the file names are displayed using relative path based on the common root folder for all files. In order to display the full path, check the <strong>Show full paths</strong> checkbox. Regardless of the checkbox state, there is always a tooltip showing the full path for every file. It is also possible to copy a full path file name to the clipboard. Right click on the file name and select <strong>Copy file name</strong>.</p>
-
 <p>If the user selected multiple summary files or grid files, this dialog will be displayed for every file that has an origin summary file. In this case the button <strong>OK to All</strong> appears. When this button is clicked, the rest of the files will be imported silently using the same options.</p>
 
 
@@ -2302,6 +2267,19 @@ Pressing the button opens a dialog similar to the <a href="/plot-window/summaryp
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2312,6 +2290,9 @@ Pressing the button opens a dialog similar to the <a href="/plot-window/summaryp
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3459,20 +3440,20 @@ Pressing the button opens a dialog similar to the <a href="/plot-window/summaryp
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplottemplate/index.html b/plot-window/summaryplottemplate/index.html
index 5df30921a9..8ef60fa94b 100644
--- a/plot-window/summaryplottemplate/index.html
+++ b/plot-window/summaryplottemplate/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Template :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,14 +1802,11 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#template-creation">Template creation</a></li>
-<li><a href="#template-usage">Template usage</a></li>
-<li><a href="#template-file-search-and-organization">Template file search and organization</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#template-creation">Template creation</a></li>
+    <li><a href="#template-usage">Template usage</a></li>
+    <li><a href="#template-file-search-and-organization">Template file search and organization</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1800,54 +1831,37 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/SummaryPlotTemplate.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotTemplate.png" alt=""></p>
 <h2 id="template-creation">Template creation</h2>
-
-<p>A summary plot template is defined by a number of curves with preset appearance and vector names.
+<p>A summary plot template is defined by a number of curves with preset appearance and vector names. 
 The parameters that are selected or varied by the user are:</p>
-
 <ul>
 <li>case(s)</li>
 <li>item(s), i.e. well(s), group(s), region(s)</li>
 </ul>
-
-<p>Having tailored a plot setup, the user can save the setup as a template via the context command <strong>Save As Plot Template</strong>, c.f. figure above. It is also possible to select a summary plot in the <strong>Plot Project Tree</strong> and use the context menu to save a template.
+<p>Having tailored a plot setup, the user can save the setup as a template via the context command <strong>Save As Plot Template</strong>, c.f. figure above. It is also possible to select a summary plot in the <strong>Plot Project Tree</strong> and use the context menu to save a template. 
 Both options save a template definition to file for later reuse.</p>
 
-
 <div class="notices note" ><p>Summary Plot Templates are created for all <em>Summary Plots</em> including ensemble plots by context menu option <strong>Save As Plot Template</strong> available in both the plot window and via their entries in the <strong>Plot Project Tree</strong>.</p>
 </div>
 
-
 <p>Given a new path, ResInsight will ask the user to confirm whether the path of the stored template is to be included in subsequent searches for templates.</p>
-
-<p><img src="/images/plot-window/SummaryPlotTemplatePath.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotTemplatePath.png" alt=""></p>
 <h2 id="template-usage">Template usage</h2>
-
 <p>Having selected items of interest in the <strong>Plot Project Tree</strong> (i.e. cases, wells, groups, and regions) a template plot can be created.</p>
-
-<p>Invoke the context menu shown below to select a specific summary plot template.
+<p>Invoke the context menu shown below to select a specific summary plot template. 
 Here two summary cases have been selected prior to invoking the context menu.
 As seen, available options for select a specific template are:</p>
-
 <ul>
 <li><strong>Create Plot from Last Used Summary Template</strong>  is a menu option to invoke the last used summary plot template.</li>
 <li><strong>Create Plot from Template</strong> shows all available templates in a separate dialog for search and selection.</li>
 </ul>
-
-<p><img src="/images/plot-window/SummaryPlotTemplateUsage.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryPlotTemplateUsage.png" alt=""></p>
 
 <div class="notices note" ><p><strong>Ctrl-T</strong> is a shortcut to swiftly create a plot based on the last used summary template.</p>
 </div>
 
-
 <h2 id="template-file-search-and-organization">Template file search and organization</h2>
-
 <p>Each summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files
 which can be managed by menu option <strong>Edit-&gt;Preferences</strong> and the <a href="/misc/preferences/#plotting-tab"><strong>Plotting tab</strong></a>.</p>
 
@@ -2025,6 +2039,19 @@ which can be managed by menu option <strong>Edit-&gt;Preferences</strong> and th
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2035,6 +2062,9 @@ which can be managed by menu option <strong>Edit-&gt;Preferences</strong> and th
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3185,20 +3215,20 @@ which can be managed by menu option <strong>Edit-&gt;Preferences</strong> and th
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summarysourcestepping/index.html b/plot-window/summarysourcestepping/index.html
index beee03d5d7..2d05df31a5 100644
--- a/plot-window/summarysourcestepping/index.html
+++ b/plot-window/summarysourcestepping/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Source Stepping :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,12 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#summary-plot-source-stepping">Summary Plot Source Stepping</a></li>
-<li><a href="#assign-source-stepping-curve">Assign source stepping curve</a></li>
-<li><a href="#handling-of-summary-curves-and-history-summary-curves">Handling of summary curves and history summary curves</a></li>
-<li><a href="#applying-data-source-change">Applying data source change</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#summary-plot-source-stepping">Summary Plot Source Stepping</a></li>
+    <li><a href="#assign-source-stepping-curve">Assign source stepping curve</a></li>
+    <li><a href="#handling-of-summary-curves-and-history-summary-curves">Handling of summary curves and history summary curves</a></li>
+    <li><a href="#applying-data-source-change">Applying data source change</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,27 +1832,16 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/SummarySourceSteppingBanner.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummarySourceSteppingBanner.png" alt=""></p>
 <h2 id="summary-plot-source-stepping">Summary Plot Source Stepping</h2>
-
-<p>Summary Source Stepping is a function which enables the user to swiftly step through multiple vectors.
+<p>Summary Source Stepping is a function which enables the user to swiftly step through multiple vectors. 
 The functionality applies both to single summary curves and ensemble curve sets.</p>
-
 <p>The functionality is available from both the toolbar and the <strong>Summary Curves</strong> property editor under a <strong>Summary Plot</strong> item in the <strong>Main Plot Window Project Tree</strong>.</p>
-
 <p>The toolbar allows use of <a href="/plot-window/summaryplots/#property-editor">vector filters</a> in addition to source stepping:</p>
-
-<p><img src="/images/plot-window/SummarySourceSteppingToolbar.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummarySourceSteppingToolbar.png" alt=""></p>
 <p>The corresponding property editor is:</p>
-
-<p><img src="/images/plot-window/SummarySourceSteppingPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummarySourceSteppingPropertyEditor.png" alt=""></p>
 <p>When ResInsight decides stepping dimensions to display, all visible curves in the current plot are taken into account. For instance, well stepping is enabled if all curves display data from the same well, c.f. figure above. This policy applies to the following source stepping dimensions:</p>
-
 <ul>
 <li>Cases</li>
 <li>Wells</li>
@@ -1832,22 +1852,14 @@ The functionality applies both to single summary curves and ensemble curve sets.
 <li>Block</li>
 <li>Summary Vectors</li>
 </ul>
-
 <h2 id="assign-source-stepping-curve">Assign source stepping curve</h2>
-
-<p>If the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available.
+<p>If the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available. 
 By right-clicking a summary curve or ensemble curve set, the menu item <strong>Set as Source Stepping Curve</strong> will use the selected curve as basis for source stepping. All source stepping dimensions for the selected curve will be displayed. When a curve or ensemble is marked for source stepping, a source stepping icon is displayed.</p>
-
-<p><img src="/images/plot-window/SummaryCurveSetSourceStepping.png" alt="" /></p>
-
+<p><img src="/images/plot-window/SummaryCurveSetSourceStepping.png" alt=""></p>
 <p>Right-clicking the summary curve or ensemble curve set, and select <strong>Clear Source Stepping Curve</strong> to leave this mode.</p>
-
 <h2 id="handling-of-summary-curves-and-history-summary-curves">Handling of summary curves and history summary curves</h2>
-
 <p>If a plot displays both a summary curve and the corresponding history summary curve, the source stepping can be applied to both curves at the same time. If you have a mix of several curves, it might be required to mark one of the curves using <strong>Set as Source Stepping Curve</strong>.</p>
-
 <h2 id="applying-data-source-change">Applying data source change</h2>
-
 <p>When one of the <strong>next buttons</strong> are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the <strong>next well button</strong>. Then the well source for all curves in the current plot are changed to display data for the next well.</p>
 
 
@@ -2024,6 +2036,19 @@ By right-clicking a summary curve or ensemble curve set, the menu item <strong>S
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2034,6 +2059,9 @@ By right-clicking a summary curve or ensemble curve set, the menu item <strong>S
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3184,20 +3212,20 @@ By right-clicking a summary curve or ensemble curve set, the menu item <strong>S
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/wellborestabilityplots/index.html b/plot-window/wellborestabilityplots/index.html
index 018acab2c4..129ca061ea 100644
--- a/plot-window/wellborestabilityplots/index.html
+++ b/plot-window/wellborestabilityplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Bore Stability Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,19 +1802,17 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#create-well-bore-stability-plots">Create Well Bore Stability plots</a></li>
-<li><a href="#input-requirements">Input requirements</a></li>
-<li><a href="#equations-and-calculations">Equations and calculations</a>
-<ul>
-<li><a href="#stresses-at-the-borehole-wall-kirsch-equations">Stresses at the borehole wall - Kirsch equations</a></li>
-<li><a href="#fracture-gradient-calculations-based-on-kirsch-in-sand">Fracture gradient calculations based on Kirsch in sand</a></li>
-<li><a href="#stassi-d-alia-failure-criterion-in-shale">Stassi-d&rsquo;Alia failure criterion in shale</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#create-well-bore-stability-plots">Create Well Bore Stability plots</a></li>
+    <li><a href="#input-requirements">Input requirements</a></li>
+    <li><a href="#equations-and-calculations">Equations and calculations</a>
+      <ul>
+        <li><a href="#stresses-at-the-borehole-wall---kirsch-equations">Stresses at the borehole wall - Kirsch equations</a></li>
+        <li><a href="#fracture-gradient-calculations-based-on-kirsch-in-sand">Fracture gradient calculations based on Kirsch in sand</a></li>
+        <li><a href="#stassi-dalia-failure-criterion-in-shale">Stassi-d&rsquo;Alia failure criterion in shale</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1805,16 +1837,11 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/WellBoreStability.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellBoreStability.png" alt=""></p>
 <p>ResInsight can create <strong>Well Bore Stability</strong> plots for Geomechanical cases. These plots are specialized <a href="/plot-window/welllogsandplots/">Well Log Plots</a> to visualize <a href="/3d-main-window/formations/">Formations</a>, <a href="/wells-and-completions/wellpaths/#well-path-attributes">Well Path Attributes</a> as well as a set of well path derived curves in different tracks.</p>
-
-<p>In the figure above, the first track contains <a href="/3d-main-window/formations/">Formations</a> while the second track contains well attributes of
+<p>In the figure above, the first track contains <a href="/3d-main-window/formations/">Formations</a> while the second track contains well attributes of 
 <a href="/wells-and-completions/wellpaths/#casing-design">Casing Design</a>.
 The third track shows the following stability gradients (all normalized by mud weight):</p>
-
 <ul>
 <li><strong>FG</strong>: Fracture Gradient for sands based on Kirsch.</li>
 <li><strong>OBG</strong>: Overburden stress gradient: Stress component S_33.</li>
@@ -1822,20 +1849,13 @@ The third track shows the following stability gradients (all normalized by mud w
 <li><strong>SFG</strong>: Shear Failure Gradient for shale based on Stassi-d&rsquo;Alia.</li>
 <li><strong>SH</strong>: Minimum horizontal stress.</li>
 </ul>
-
 <p>The fourth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.</p>
-
 <h2 id="create-well-bore-stability-plots">Create Well Bore Stability plots</h2>
-
 <p>Well Bore Stability plots can be created from the right-click menu for a well path in <strong>Project Tree</strong> or from the the right-click menu of the Well Log Plots entry in <strong>Plot Project Tree</strong>. In the former case, the well bore stability plot will be created for the selected <strong>Well Path</strong>. In the latter case, it will be created for the first well path in the well path list and the well path for the entire plot can be changed with the <a href="/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves">Change Data Source Feature</a>.</p>
-
-<p><img src="/images/plot-window/WellBoreStabilityCreation.png" alt="" />
-<img src="/images/plot-window/WellBoreStabilityCreation2.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellBoreStabilityCreation.png" alt=""> 
+<img src="/images/plot-window/WellBoreStabilityCreation2.png" alt=""></p>
 <h2 id="input-requirements">Input requirements</h2>
-
 <p>In order to calculate <strong>FG</strong>  and <strong>SFG</strong>, the following input parameters are required:</p>
-
 <table>
 <thead>
 <tr>
@@ -1843,26 +1863,20 @@ The third track shows the following stability gradients (all normalized by mud w
 <th>Required Parameters</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>FG</td>
 <td>Pore Pressure (PP), Poissons&rsquo; Ratio</td>
 </tr>
-
 <tr>
 <td>SFG</td>
 <td>Uniaxial Compressive Strength (UCS)</td>
 </tr>
 </tbody>
 </table>
-
 <p>These parameters may be read in in the following ways.</p>
-
 <p><a href="/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves">Change Data Source Feature</a></p>
-
 <p>The numbering for import is order of preference if multiple sources are found.</p>
-
 <table>
 <thead>
 <tr>
@@ -1871,20 +1885,17 @@ The third track shows the following stability gradients (all normalized by mud w
 <th>Import mechanisms</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>PP</td>
 <td>Hydrostatic PP (TVD x 9.81 / 100 bar)</td>
 <td>1. Grid (Grid units), 2. LAS-file as mud-weight (Variable: &ldquo;PP&rdquo;, Units: kg / m^3), 3. Element Property Table (Variable: &ldquo;POR&rdquo;, Units: Pascal)</td>
 </tr>
-
 <tr>
 <td>Poissons&rsquo; Ratio</td>
 <td>0.25</td>
 <td>1. LAS-file (Variable: &ldquo;POISSON_RATIO&rdquo;), 2. Element Property Table (Variable: &ldquo;POISSON_RATIO&rdquo;)</td>
 </tr>
-
 <tr>
 <td>UCS</td>
 <td>100 bar</td>
@@ -1892,45 +1903,31 @@ The third track shows the following stability gradients (all normalized by mud w
 </tr>
 </tbody>
 </table>
-
 <h2 id="equations-and-calculations">Equations and calculations</h2>
-
-<h3 id="stresses-at-the-borehole-wall-kirsch-equations">Stresses at the borehole wall - Kirsch equations</h3>
-
+<h3 id="stresses-at-the-borehole-wall---kirsch-equations">Stresses at the borehole wall - Kirsch equations</h3>
 <p>The basic input to wellbore stability models is the stresses at the borehole wall given by the Kirsch equations in cylindrical coordinates:</p>
-
-<p><img src="/images/plot-window/WellBoreStabilityKirschEquations.png" alt="" /></p>
-
-<p>The transformation of stresses from cartesian coordinate system to x&rsquo;, y&rsquo;, z&rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix <strong>M</strong>, i.e.
+<p><img src="/images/plot-window/WellBoreStabilityKirschEquations.png" alt=""></p>
+<p>The transformation of stresses from cartesian coordinate system to x&rsquo;, y&rsquo;, z&rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix <strong>M</strong>, i.e. 
 <img src="https://resinsight.org/images/plot-window/WellBoreStabilityStressTransformation.png" style="display:inline; vertical-align:middle; margin:0">
 .</p>
-
 <h3 id="fracture-gradient-calculations-based-on-kirsch-in-sand">Fracture gradient calculations based on Kirsch in sand</h3>
-
 <p>To estimate the fracture gradient <em>FG</em>, first step is to find the principle effective stresses at the borehole wall:</p>
-
-<p><img src="/images/plot-window/WellBoreStabilityKirschSandEquations.png" alt="" /></p>
-
-<p>Next step is to find the well pressure <em>Pw</em> that gives
+<p><img src="/images/plot-window/WellBoreStabilityKirschSandEquations.png" alt=""></p>
+<p>Next step is to find the well pressure <em>Pw</em> that gives 
 <img src="https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTminZero.png" style="display:inline; vertical-align:middle; margin:0">
- for
+ for 
 <img src="https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png" style="display:inline; vertical-align:middle; margin:0">
 .
-Then calculate <em>FG</em> in equivalent mud weight units as <em>FG</em> = <em>Pw</em> / (<em>TVDRKB</em> * <em>g</em> * 1000) where <em>TVDRKB = TVDMSL + RKB</em> and
+Then calculate <em>FG</em> in equivalent mud weight units as <em>FG</em> = <em>Pw</em> / (<em>TVDRKB</em> * <em>g</em> * 1000) where <em>TVDRKB = TVDMSL + RKB</em> and 
 <em>g = 9.81</em>.</p>
-
-<h3 id="stassi-d-alia-failure-criterion-in-shale">Stassi-d&rsquo;Alia failure criterion in shale</h3>
-
-<p>Stassi-d&rsquo;Alia failure criterion in shale is calculated by finding the well pressure <em>Pw</em> that satisfies the following equation
+<h3 id="stassi-dalia-failure-criterion-in-shale">Stassi-d&rsquo;Alia failure criterion in shale</h3>
+<p>Stassi-d&rsquo;Alia failure criterion in shale is calculated by finding the well pressure <em>Pw</em> that satisfies the following equation 
 for <img src="https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png" style="display:inline; vertical-align:middle; margin:0">
 .</p>
-
-<p><img src="/images/plot-window/WellBoreStabilityStassiEquations.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellBoreStabilityStassiEquations.png" alt=""></p>
 <p>where <img src="https://resinsight.org/images/plot-window/WellBoreStabilityPrincipalStresses.png" style="display:inline; vertical-align:middle; margin:0">
- are the effective principal stresses
+ are the effective principal stresses 
 and <em>UCS</em> is the <em>uniaxial compressive strength</em>.</p>
-
 <p>Shear Failure Gradient is then given as <em>SFG</em> = <em>Pw</em> / (<em>TVDRKB</em> * <em>g</em> * 1000) where <em>TVDRKB = TVDMSL + RKB</em> and <em>g = 9.81</em>.</p>
 
 
@@ -2107,6 +2104,19 @@ and <em>UCS</em> is the <em>uniaxial compressive strength</em>.</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2117,6 +2127,9 @@ and <em>UCS</em> is the <em>uniaxial compressive strength</em>.</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3267,20 +3280,20 @@ and <em>UCS</em> is the <em>uniaxial compressive strength</em>.</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/welllogsandplots/index.html b/plot-window/welllogsandplots/index.html
index 88c81a581e..fc0e527829 100644
--- a/plot-window/welllogsandplots/index.html
+++ b/plot-window/welllogsandplots/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Log Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,34 +1802,30 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#well-log-plots">Well Log Plots</a>
-<ul>
-<li><a href="#measured-depth-md-true-vertical-depth-tvd-and-pseudo-length-pl">Measured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)</a></li>
-<li><a href="#depth-unit">Depth Unit</a></li>
-<li><a href="#depth-zoom-and-pan">Depth Zoom and Pan</a></li>
-<li><a href="#accessing-plot-data">Accessing Plot Data</a></li>
-</ul></li>
-<li><a href="#tracks">Tracks</a></li>
-<li><a href="#curves">Curves</a>
-<ul>
-<li><a href="#well-log-extraction-curves">Well Log Extraction Curves</a>
-<ul>
-<li><a href="#curve-extraction-calculation">Curve Extraction Calculation</a></li>
-<li><a href="#change-data-source-for-plots-and-curves">Change Data Source for Plots and Curves</a></li>
-</ul></li>
-<li><a href="#well-log-rft-curves">Well Log RFT Curves</a></li>
-<li><a href="#well-log-las-curves">Well Log LAS Curves</a></li>
-</ul></li>
-<li><a href="#las-file-support">LAS-file Support</a>
-<ul>
-<li><a href="#importing-las-files">Importing LAS-files</a></li>
-<li><a href="#exporting-las-files">Exporting LAS-files</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#well-log-plots">Well Log Plots</a>
+      <ul>
+        <li><a href="#measured-depth-md-true-vertical-depth-tvd-and-pseudo-length-pl">Measured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)</a></li>
+        <li><a href="#depth-unit">Depth Unit</a></li>
+        <li><a href="#depth-zoom-and-pan">Depth Zoom and Pan</a></li>
+        <li><a href="#accessing-plot-data">Accessing Plot Data</a></li>
+      </ul>
+    </li>
+    <li><a href="#tracks">Tracks</a></li>
+    <li><a href="#curves">Curves</a>
+      <ul>
+        <li><a href="#well-log-extraction-curves">Well Log Extraction Curves</a></li>
+        <li><a href="#well-log-rft-curves">Well Log RFT Curves</a></li>
+        <li><a href="#well-log-las-curves">Well Log LAS Curves</a></li>
+      </ul>
+    </li>
+    <li><a href="#las-file-support">LAS-file Support</a>
+      <ul>
+        <li><a href="#importing-las-files">Importing LAS-files</a></li>
+        <li><a href="#exporting-las-files">Exporting LAS-files</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1820,157 +1850,94 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/plot-window/WellLogPlotOverview.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellLogPlotOverview.png" alt=""></p>
 <p>ResInsight can display well logs by extracting data from a simulation model along a well trajectory and from imported LAS-files. Extracted simulation data can be exported to LAS-files for further processing.</p>
-
 <h2 id="well-log-plots">Well Log Plots</h2>
-
 <p>Well log plots can be created in several ways:</p>
-
 <ol>
-<li>Right-click a well path or a simulation well in the 3D-view and select <strong>New Well Log Extraction Curve</strong>.<br />
+<li>Right-click a well path or a simulation well in the 3D-view and select <strong>New Well Log Extraction Curve</strong>.<br>
 A new plot with a single <strong>Track</strong> and <strong>Curve</strong> is created matching active case and selected Well trajectory.</li>
-<li>Right-click <strong>Well Log Plots</strong> in the <strong>Plot Project Tree</strong> and select <strong>New Well Log Plot</strong>.
+<li>Right-click <strong>Well Log Plots</strong> in the <strong>Plot Project Tree</strong> and select <strong>New Well Log Plot</strong>. 
 A plot is created with one <strong>Track</strong> and <strong>Curve</strong>.</li>
 <li>Right-click <img src="https://resinsight.org/images/3d-main-window/WellCollection.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Wells</strong>
 in the <strong>Project Tree</strong> and select <strong>Import-&gt;Import Well Logs from file</strong>.</li>
 </ol>
-
 <p>Each <strong>Well Log Plot</strong> can contain several <em>Tracks</em>, and each <strong>Track</strong> can contain several <strong>Curves</strong>.</p>
-
-<p><img src="/images/plot-window/WellLogPlotWindow.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellLogPlotWindow.png" alt=""></p>
 <p>Tracks and Curves can be organized using <strong>drag and drop</strong> of their entries in the <strong>Plot Project Tree</strong>. Tracks can be moved from one plot to another and you can alter the order of tracks within a Well Log Plot by drag and drop. In addition, <em>Curves</em> can be moved from one <em>Track</em> to another. Furthermore, <strong>copy and paste</strong> of a <em>Well Log Plot</em>, <em>Track</em>, and <em>Curve</em> is possible by right-clicking their entry.</p>
-
 <h3 id="measured-depth-md-true-vertical-depth-tvd-and-pseudo-length-pl">Measured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)</h3>
-
 <p>All <strong>Tracks</strong> in the same Well Log Plot always display the same depth range, and share the <em>True Vertical Depth (TVD)</em> or <em>Measured Depth (MD)</em> setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).</p>
-
 <p><strong>Simulation Wells</strong> however, is using a <em>Pseudo Length</em> instead of the real <em>Measured Depth</em> when the depth type is MD, as the MD information is not available in restart files. The <em>Pseudo Length</em> is a length along the coarsely interpolated visualization pipe, and serves only as a coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.</p>
-
 <h3 id="depth-unit">Depth Unit</h3>
-
 <p>The depth unit can be set using the <strong>Depth unit</strong> option. Currently ResInsight supports <em>Meter</em> and <em>Feet</em>. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.</p>
-
 <h3 id="depth-zoom-and-pan">Depth Zoom and Pan</h3>
-
 <p>The visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot.
 Pressing and holding <strong>CTRL</strong> while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.</p>
-
 <h3 id="accessing-plot-data">Accessing Plot Data</h3>
-
 <p>Right-click a Well Log Plot and select <strong>Show Plot Data</strong> to show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.</p>
-
 <p>It is also possible to save the ascii data to a file by selecting a Well Log Plot in the <strong>Plot Project Tree</strong> and use the context command <strong>Export Plot Data to Text File</strong>.</p>
-
 <h2 id="tracks">Tracks</h2>
-
 <p>Tracks can be created by right-clicking a <strong>Well Log Plot</strong> and select <strong>New Track</strong>.</p>
-
-<p>The settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by <a href="/3d-main-window/formations/">Formations</a> in <em>Category colors</em>.</p>
-
-<p><img src="/images/plot-window/TrackProperties.png" alt="" /></p>
-
+<p>The settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by [Formations] (/3d-main-window/formations/) in <em>Category colors</em>.</p>
+<p><img src="/images/plot-window/TrackProperties.png" alt=""></p>
 <p>A track controls the x-axis range of the display which is set in the property panel. In addition to the range, logarithmic display is controlled by checking <strong>Logarithmic Scale</strong>, grid lines are controlled by the <strong>Show Grid Lines</strong> option.</p>
-
 <p>It is also possible to visualize <a href="/wells-and-completions/wellpaths/#well-path-attributes">Well Attributes</a> such as casing and liners. The following images show some of the possibilities in which the first track shows cross sections of a well and the second track shows a radial view labeled with formations.</p>
-
-<p><img src="/images/plot-window/WellAttributeBothSides.png" alt="" /></p>
-
-<p><img src="/images/plot-window/WellLogTracksWidth.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellAttributeBothSides.png" alt=""></p>
+<p><img src="/images/plot-window/WellLogTracksWidth.png" alt=""></p>
 <h2 id="curves">Curves</h2>
-
 <p>Curves can be created by right-clicking a <strong>Track</strong> in the <strong>Plot Project Tree</strong> or by the commands mentioned above.
 The two types of curves are <em>Well Log Extraction Curves</em> and <em>Well Log LAS Curves</em>.</p>
-
 <h3 id="well-log-extraction-curves">Well Log Extraction Curves</h3>
-
 <p>Extraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.</p>
-
 <p>The property panel for an eclipse model is shown below:</p>
-
-<p><img src="/images/plot-window/WellLogExtractionCurveProperties.png" alt="" /></p>
-
-<p>The first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical
+<p><img src="/images/plot-window/WellLogExtractionCurveProperties.png" alt=""></p>
+<p>The first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical 
 cases and Eclipse cases. Time step can be specified for dynamic properties.</p>
-
-<p>Curve visual appearance and naming is controlled by the <strong>Appearance</strong> and <strong>Curve Name</strong> sections.
+<p>Curve visual appearance and naming is controlled by the <strong>Appearance</strong> and <strong>Curve Name</strong> sections. 
 The display name of a curve is normally generated automatically. Optionally, <strong>Auto Name</strong> can be switched off to use the options below to tailor curve name.</p>
 
-
-<div class="notices note" ><p>Placing keyboard focus in the <b>Time Step</b> drop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.</p>
+<div class="notices note" ><p>Placing keyboard focus in the <!-- raw HTML omitted -->Time Step<!-- raw HTML omitted --> drop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.</p>
 </div>
 
-
 <h4 id="curve-extraction-calculation">Curve Extraction Calculation</h4>
-
 <p>This section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.</p>
-
 <p>Extraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.</p>
-
 <p>For Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a <strong>Directional combined results</strong> is used ( See <a href="/3d-main-window/derivedresults/"> Derived Results </a> ), it will be that particular face&rsquo;s value.</p>
-
 <p>Abaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.</p>
-
 <h4 id="change-data-source-for-plots-and-curves">Change Data Source for Plots and Curves</h4>
-
 <p>It is possible to change some data source parameters in one go for either a full plot or several selected curves. To change the parameters for a whole plot use either the <strong>Data Source</strong> group in the Property Editor for the Well Log Plot or corresponding toolbar which is visible when a Well Log Plot or any of its children are selected. Changing parameters in the <strong>Data Source</strong> group for the plot will also change the source for Zonation/Formations and Well Path Attributes in addition to the data source for all <strong>Well Log Extraction Curves</strong> and <strong>Well Log LAS Curves</strong>.
 The source stepping icons <img src="https://resinsight.org/images/plot-window/SummarySourceSteppingIcons.png" style="display:inline; vertical-align:middle; margin:0">
- allows to quickly step through cases, wells, and timesteps c.f.
+ allows to quickly step through cases, wells, and timesteps c.f. 
 <a href="/plot-window/summarysourcestepping/">Summary Plot Source Stepping</a>.</p>
-
-<p><img src="/images/plot-window/WellLogPlotDataSource.png" alt="" /></p>
-
-<p>To change data source for curves, select the curves for which you wish to change source and select <strong>Change Data Source</strong> from the right-click menu.
+<p><img src="/images/plot-window/WellLogPlotDataSource.png" alt=""></p>
+<p>To change data source for curves, select the curves for which you wish to change source and select <strong>Change Data Source</strong> from the right-click menu. 
 The following dialog will appear:</p>
-
-<p><img src="/images/plot-window/WellLogExtractionChangeDataSource.png" alt="" /></p>
-
+<p><img src="/images/plot-window/WellLogExtractionChangeDataSource.png" alt=""></p>
 <p>In both cases, the following parameters are available to change:</p>
-
 <ul>
 <li><strong>Case</strong> &ndash; Applies the selected case to all the curves.</li>
 <li><strong>Trajectory Type</strong> &ndash; Sets whether to use Simulation Wells or Well Paths as a data source for all curves.</li>
 <li><strong>Well Name</strong> &ndash; Applies this well path to all the curves.</li>
 <li><strong>Time Step</strong> &ndash; Applies this time step to all the curves.</li>
 </ul>
-
 <p>Common for the different ways of changing data source is that if a parameter is not shared among all the curves, the drop down list will show &ldquo;Mixed Cases, &ldquo;Mixed Trajectory Types&rdquo;, &ldquo;Mixed Well Paths&rdquo; or &ldquo;Mixed Time Steps&rdquo; to indicate that the curves have different values for that parameter. It is still possible to select a common parameter for them which will then be applied across the curves.</p>
-
 <h3 id="well-log-rft-curves">Well Log RFT Curves</h3>
-
 <p>Well Log RFT Curves shows the values in a RFT file. See <a href="/plot-window/rftplot/">RFT Plot</a> for details about RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is <em>Point to Point</em>.</p>
-
 <h3 id="well-log-las-curves">Well Log LAS Curves</h3>
-
 <p>LAS-curves shows the values in a particular channel in a LAS-file.</p>
-
 <p>The property panel of a LAS-curve is shown below:</p>
+<p><img src="/images/plot-window/WellLogLasCurveProperties.png" alt=""></p>
 
-<p><img src="/images/plot-window/WellLogLasCurveProperties.png" alt="" /></p>
-
-
-<div class="notices note" ><p>You can also create a LAS-curve by a simple drag-drop operation in the <b>Project Tree</b>: Drag one of the LAS channels and drop it onto a <b>Track</b>. A new curve will be created with the correct setting.</p>
+<div class="notices note" ><p>You can also create a LAS-curve by a simple drag-drop operation in the <!-- raw HTML omitted -->Project Tree<!-- raw HTML omitted -->: Drag one of the LAS channels and drop it onto a <!-- raw HTML omitted -->Track<!-- raw HTML omitted -->. A new curve will be created with the correct setting.</p>
 </div>
 
-
 <h2 id="las-file-support">LAS-file Support</h2>
-
 <h3 id="importing-las-files">Importing LAS-files</h3>
-
 <p>See <a href="/wells-and-completions/wellpaths/#importing-well-log-files">Importing Well Log Files</a> for details on LAS file import.</p>
-
 <h3 id="exporting-las-files">Exporting LAS-files</h3>
-
 <p>A set of curves can be exported to LAS files by right-clicking the curves, well log track, or well log plots in <strong>Plot Project Tree</strong> and select <strong>Export To LAS Files &hellip;</strong>. An export dialog is displayed, allowing the user to configure how to export curve data.</p>
-
-<p><img src="/images/plot-window/export_to_las_files.png" alt="" /></p>
-
+<p><img src="/images/plot-window/export_to_las_files.png" alt=""></p>
 <ul>
 <li><strong>Export Folder</strong> &ndash; Location of the exported LAS files, one file per unique triplet of well path, case and time step.</li>
 <li><strong>Resampling</strong> &ndash; If enabled, all curves are resampled at the given resample interval before export.</li>
@@ -2151,6 +2118,19 @@ The following dialog will appear:</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2161,6 +2141,9 @@ The following dialog will appear:</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3311,20 +3294,20 @@ The following dialog will appear:</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/commandfile/index.html b/scripting/commandfile/index.html
index 1ee1e2ccd2..8eb529af25 100644
--- a/scripting/commandfile/index.html
+++ b/scripting/commandfile/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Command File :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,61 +1802,58 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#command-list">Command List</a>
-<ul>
-<li>
-<ul>
-<li><a href="#case-control-commands">Case Control Commands</a></li>
-<li><a href="#export-commands">Export Commands</a></li>
-<li><a href="#other-commands">Other Commands</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#syntax">Syntax</a>
-<ul>
-<li><a href="#types">Types</a></li>
-</ul></li>
-<li><a href="#case-control-commands-1">Case Control Commands</a>
-<ul>
-<li><a href="#openproject">openProject</a></li>
-<li><a href="#closeproject">closeProject</a></li>
-<li><a href="#setstartdir">setStartDir</a></li>
-<li><a href="#loadcase">loadCase</a></li>
-<li><a href="#creategridcasegroup">createGridCaseGroup</a></li>
-<li><a href="#createstatisticscase">createStatisticsCase</a></li>
-<li><a href="#replacecase">replaceCase</a></li>
-<li><a href="#replacesourcecases">replaceSourceCases</a></li>
-</ul></li>
-<li><a href="#export-commands-1">Export Commands</a>
-<ul>
-<li><a href="#exportmulticasesnapshots">exportMultiCaseSnapshots</a></li>
-<li><a href="#exportsnapshots">exportSnapshots</a></li>
-<li><a href="#exportproperty">exportProperty</a></li>
-<li><a href="#exportpropertyinviews">exportPropertyInViews</a></li>
-<li><a href="#exportwellpathcompletions">exportWellPathCompletions</a></li>
-<li><a href="#exportsimwellfracturecompletions">exportSimWellFractureCompletions</a></li>
-<li><a href="#exportmsw">exportMsw</a></li>
-<li><a href="#exportwellpaths">exportWellPaths</a></li>
-<li><a href="#exportvisiblecells">exportVisibleCells</a></li>
-<li><a href="#exportflowcharacteristics">exportFlowCharacteristics</a></li>
-<li><a href="#setexportfolder">setExportFolder</a></li>
-</ul></li>
-<li><a href="#other">Other</a>
-<ul>
-<li><a href="#runoctavescript">runOctaveScript</a></li>
-<li><a href="#setmainwindowsize">setMainWindowSize</a></li>
-<li><a href="#computecasegroupstatistics">computeCaseGroupStatistics</a></li>
-<li><a href="#settimestep">setTimeStep</a></li>
-<li><a href="#scalefracturetemplate">scaleFractureTemplate</a></li>
-<li><a href="#setfracturecontainment">setFractureContainment</a></li>
-<li><a href="#createmultiplefractures">createMultipleFractures</a></li>
-<li><a href="#createlgrforcompletions">createLgrForCompletions</a></li>
-<li><a href="#createsaturationpressureplots">createSaturationPressurePlots</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#command-list">Command List</a>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+    <li><a href="#syntax">Syntax</a>
+      <ul>
+        <li><a href="#types">Types</a></li>
+      </ul>
+    </li>
+    <li><a href="#case-control-commands-1">Case Control Commands</a>
+      <ul>
+        <li><a href="#openproject">openProject</a></li>
+        <li><a href="#closeproject">closeProject</a></li>
+        <li><a href="#setstartdir">setStartDir</a></li>
+        <li><a href="#loadcase">loadCase</a></li>
+        <li><a href="#creategridcasegroup">createGridCaseGroup</a></li>
+        <li><a href="#createstatisticscase">createStatisticsCase</a></li>
+        <li><a href="#replacecase">replaceCase</a></li>
+        <li><a href="#replacesourcecases">replaceSourceCases</a></li>
+      </ul>
+    </li>
+    <li><a href="#export-commands-1">Export Commands</a>
+      <ul>
+        <li><a href="#exportmulticasesnapshots">exportMultiCaseSnapshots</a></li>
+        <li><a href="#exportsnapshots">exportSnapshots</a></li>
+        <li><a href="#exportproperty">exportProperty</a></li>
+        <li><a href="#exportpropertyinviews">exportPropertyInViews</a></li>
+        <li><a href="#exportwellpathcompletions">exportWellPathCompletions</a></li>
+        <li><a href="#exportsimwellfracturecompletions">exportSimWellFractureCompletions</a></li>
+        <li><a href="#exportmsw">exportMsw</a></li>
+        <li><a href="#exportwellpaths">exportWellPaths</a></li>
+        <li><a href="#exportvisiblecells">exportVisibleCells</a></li>
+        <li><a href="#exportflowcharacteristics">exportFlowCharacteristics</a></li>
+        <li><a href="#setexportfolder">setExportFolder</a></li>
+      </ul>
+    </li>
+    <li><a href="#other">Other</a>
+      <ul>
+        <li><a href="#runoctavescript">runOctaveScript</a></li>
+        <li><a href="#setmainwindowsize">setMainWindowSize</a></li>
+        <li><a href="#computecasegroupstatistics">computeCaseGroupStatistics</a></li>
+        <li><a href="#settimestep">setTimeStep</a></li>
+        <li><a href="#scalefracturetemplate">scaleFractureTemplate</a></li>
+        <li><a href="#setfracturecontainment">setFractureContainment</a></li>
+        <li><a href="#createmultiplefractures">createMultipleFractures</a></li>
+        <li><a href="#createlgrforcompletions">createLgrForCompletions</a></li>
+        <li><a href="#createsaturationpressureplots">createSaturationPressurePlots</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1847,18 +1878,12 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>The command file interface allows a sequence of specified commands to be run in order from the command line.
 The interface is used by supplying the command file as a <a href="/scripting/commandlineinterface/">command line parameter</a>.
 Once the command file is finished executing, ResInsight will exit.</p>
-
-<p>It is possible to use these commands directly from a Python script. For further details see <a href="/scripting/pythonrips/#commands-module">Python Documentation</a></p>
-
+<p>It is possible to use these commands directly from a Python script. For further details see <a href="/scripting/pythonrips/">Python Documentation</a></p>
 <h2 id="command-list">Command List</h2>
-
 <h4 id="case-control-commands">Case Control Commands</h4>
-
 <ul>
 <li><a href="#openproject">openProject</a></li>
 <li><a href="#closeproject">closeProject</a></li>
@@ -1869,9 +1894,7 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <li><a href="#replacecase">replaceCase</a></li>
 <li><a href="#replacesourcecases">replaceSourceCases</a></li>
 </ul>
-
 <h4 id="export-commands">Export Commands</h4>
-
 <ul>
 <li><a href="#setexportfolder">setExportFolder</a></li>
 <li><a href="#exportmulticasesnapshots">exportMultiCaseSnapshots</a></li>
@@ -1885,9 +1908,7 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <li><a href="#exportvisiblecells">exportVisibleCells</a></li>
 <li><a href="#exportflowcharacteristics">exportFlowCharacteristics</a></li>
 </ul>
-
 <h4 id="other-commands">Other Commands</h4>
-
 <ul>
 <li><a href="#runoctavescript">runOctaveScript</a></li>
 <li><a href="#setmainwindowsize">setMainWindowSize</a></li>
@@ -1899,24 +1920,14 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <li><a href="#createlgrforcompletions">createLgrForCompletions</a></li>
 <li><a href="#createSaturationPressurePlots">createSaturationPressurePlots</a></li>
 </ul>
-
 <h2 id="syntax">Syntax</h2>
-
 <p>The command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.</p>
-
 <p>The line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.</p>
-
 <p>As an example; <code>openProject(path=&quot;/path/to/ResInsightProject.rsp&quot;)</code> will execute the command <code>openProject</code> with the parameter <code>path</code>. <code>path</code> is a string, see <a href="#types">Types</a> for a list of all types a parameter can have.</p>
-
 <p>Not all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.</p>
-
 <pre><code>Command file examples are displayed in sections like this.
-</code></pre>
-
-<h3 id="types">Types</h3>
-
+</code></pre><h3 id="types">Types</h3>
 <p>There are different types of parameters that can be supplied.</p>
-
 <table>
 <thead>
 <tr>
@@ -1925,38 +1936,32 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Example</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Integer</td>
 <td>Number</td>
 <td>5</td>
 </tr>
-
 <tr>
 <td>Double</td>
 <td>Decimal number</td>
 <td>3.14</td>
 </tr>
-
 <tr>
 <td>String</td>
-<td>Sequence of characters contained in quotes (<code>&quot;&quot;</code>)<sup>1</sup></td>
-<td>&rdquo;/path/to/file&rdquo;</td>
+<td>Sequence of characters contained in quotes (<code>&quot;&quot;</code>)<!-- raw HTML omitted -->1<!-- raw HTML omitted --></td>
+<td>&ldquo;/path/to/file&rdquo;</td>
 </tr>
-
 <tr>
 <td>Enum</td>
 <td>Choice of a set of given options</td>
 <td>ALL</td>
 </tr>
-
 <tr>
 <td>Boolean</td>
 <td><code>true</code> or <code>false</code></td>
 <td>true</td>
 </tr>
-
 <tr>
 <td>List</td>
 <td>Multiple choices of another type, written within square brackets (<code>[]</code>) separated by a comma (<code>,</code>)</td>
@@ -1964,15 +1969,10 @@ Once the command file is finished executing, ResInsight will exit.</p>
 </tr>
 </tbody>
 </table>
-
-<p><sup>1</sup> The backslash (<code>\</code>) character is used as an escape character within strings, so to use a quote within a string, use <code>&quot;escape \&quot; with \&quot;&quot;</code>. To input a literal backslash character, use <code>&quot;\\&quot;</code>.</p>
-
+<p><!-- raw HTML omitted -->1<!-- raw HTML omitted --> The backslash (<code>\</code>) character is used as an escape character within strings, so to use a quote within a string, use <code>&quot;escape \&quot; with \&quot;&quot;</code>. To input a literal backslash character, use <code>&quot;\\&quot;</code>.</p>
 <h2 id="case-control-commands-1">Case Control Commands</h2>
-
 <h3 id="openproject">openProject</h3>
-
 <p>Opens a ResInsight project file.</p>
-
 <table>
 <thead>
 <tr>
@@ -1982,31 +1982,21 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>path</td>
 <td>File path to the project file</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>openProject(path=&quot;/home/user/ResInsightProject.rsp&quot;)
-</code></pre>
-
-<h3 id="closeproject">closeProject</h3>
-
+</code></pre><h3 id="closeproject">closeProject</h3>
 <p>Closes the current open project.</p>
-
 <pre><code>closeProject()
-</code></pre>
-
-<h3 id="setstartdir">setStartDir</h3>
-
+</code></pre><h3 id="setstartdir">setStartDir</h3>
 <p>Set startup directory.</p>
-
 <table>
 <thead>
 <tr>
@@ -2016,24 +2006,18 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>path</td>
 <td>Path to directory to use as startup directory</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>setStartDir(path=&quot;/home/user&quot;)
-</code></pre>
-
-<h3 id="loadcase">loadCase</h3>
-
+</code></pre><h3 id="loadcase">loadCase</h3>
 <p>Import Eclipse case from file.</p>
-
 <table>
 <thead>
 <tr>
@@ -2043,24 +2027,18 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>path</td>
 <td>File path to the case to load</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>loadCase(path=&quot;/home/user/reservoir.EGRID&quot;)
-</code></pre>
-
-<h3 id="creategridcasegroup">createGridCaseGroup</h3>
-
+</code></pre><h3 id="creategridcasegroup">createGridCaseGroup</h3>
 <p>Create a Grid Case Group from a list of files.</p>
-
 <table>
 <thead>
 <tr>
@@ -2070,21 +2048,17 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>casePaths</td>
 <td>List of Paths to Case Files</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="createstatisticscase">createStatisticsCase</h3>
-
 <p>Create a Statistics Case in a Grid Case Group.</p>
-
 <table>
 <thead>
 <tr>
@@ -2094,27 +2068,20 @@ Once the command file is finished executing, ResInsight will exit.</p>
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseGroupId</td>
 <td>ID to the Case Group</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>createGridCaseGroup(path=[&quot;/home/user/reservoir.EGRID&quot;, &quot;/home/user/other_reservoir.EGRID&quot;])
 createStatisticsCase(caseGroupId=0)
-</code></pre>
-
-<h3 id="replacecase">replaceCase</h3>
-
+</code></pre><h3 id="replacecase">replaceCase</h3>
 <p>Replaces a case in the current project with the specified new case.</p>
-
 <p><code>openProject</code> must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use <code>replaceSourceCases</code>.</p>
-
 <table>
 <thead>
 <tr>
@@ -2124,15 +2091,13 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>newGridFile</td>
 <td>File path to the new grid file to replace with</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>caseId</td>
 <td>ID of the case to replace. Defaults to first case</td>
@@ -2141,16 +2106,10 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-
 <pre><code>replaceCase(newGridFile=&quot;/home/user/otherReservoir.EGRID&quot;, caseId=4)
-</code></pre>
-
-<h3 id="replacesourcecases">replaceSourceCases</h3>
-
+</code></pre><h3 id="replacesourcecases">replaceSourceCases</h3>
 <p>Replaces multiple source cases in the current project.</p>
-
 <p><code>openProject</code> must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.</p>
-
 <table>
 <thead>
 <tr>
@@ -2160,15 +2119,13 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>gridListFile</td>
 <td>File path to file containing list of cases to replace with</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>caseGroupId</td>
 <td>ID of group to replace cases in. Defaults to first group</td>
@@ -2177,20 +2134,12 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-
 <pre><code>replaceSourceCases(gridListFile=&quot;C:/resinsight/replacement_files.txt&quot;)
-</code></pre>
-
-<h2 id="export-commands-1">Export Commands</h2>
-
+</code></pre><h2 id="export-commands-1">Export Commands</h2>
 <h3 id="exportmulticasesnapshots">exportMultiCaseSnapshots</h3>
-
 <p>Replaces the first case in the current project with each case in the given file and saves snapshots of all views.</p>
-
 <p><code>openProject</code> must be called before this command to set which project file is to be used when replacing cases.</p>
-
 <p>Folder to output snapshots should be set using <code>setExportFolder</code> with <code>SNAPSHOTS</code> type.</p>
-
 <table>
 <thead>
 <tr>
@@ -2200,26 +2149,19 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>gridListFile</td>
 <td>File path to file containing list of cases to create snapshots of</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportMultiCaseSnapshots(gridListFile=&quot;C:\\resinsight\\replacement_files.txt&quot;)
-</code></pre>
-
-<h3 id="exportsnapshots">exportSnapshots</h3>
-
+</code></pre><h3 id="exportsnapshots">exportSnapshots</h3>
 <p>Export snapshots of specified type.</p>
-
 <p>Folder to output snapshots should be set using <code>setExportFolder</code> with <code>SNAPSHOTS</code> type.</p>
-
 <table>
 <thead>
 <tr>
@@ -2229,7 +2171,6 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>type</td>
@@ -2237,14 +2178,12 @@ createStatisticsCase(caseGroupId=0)
 <td>Enum</td>
 <td></td>
 </tr>
-
 <tr>
 <td>prefix</td>
 <td>Exported file name prefix. Defaults to no prefix</td>
 <td>String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>caseId</td>
 <td>ID of case for export, defaults to -1 meaning all cases</td>
@@ -2253,14 +2192,9 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportSnapshots(type=PLOTS)
-</code></pre>
-
-<h3 id="exportproperty">exportProperty</h3>
-
+</code></pre><h3 id="exportproperty">exportProperty</h3>
 <p>Exports property values for all cells in the grid to file in Eclipse format.</p>
-
 <table>
 <thead>
 <tr>
@@ -2270,43 +2204,37 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case for export</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeStep</td>
 <td>The time step index for export</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>property</td>
 <td>Name of property to export</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>eclipseKeyword</td>
 <td>Eclipse keyword used as text in export header. Defaults to the value of <code>property</code> parameter</td>
 <td>String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>undefinedValue</td>
 <td>Value to use for undefined values. Defaults to 0.0</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>exportFile</td>
 <td>Filename for export. Defaults to the value of <code>property</code> parameter</td>
@@ -2315,14 +2243,9 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportProperty(caseId=1, timeStep=4, property=&quot;SOIL&quot;)
-</code></pre>
-
-<h3 id="exportpropertyinviews">exportPropertyInViews</h3>
-
+</code></pre><h3 id="exportpropertyinviews">exportPropertyInViews</h3>
 <p>Exports property values for all cells in the grid to file in Eclipse format. Use specified cell result in view to define the export property. One file per view will be exported.</p>
-
 <table>
 <thead>
 <tr>
@@ -2332,22 +2255,19 @@ createStatisticsCase(caseGroupId=0)
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to export property from</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>viewNames</td>
 <td>Name of views to export from. If not specified, all views are exported</td>
 <td>List of String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>undefinedValue</td>
 <td>Value to use for undefined values. Defaults to 0.0</td>
@@ -2356,16 +2276,11 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportPropertyInViews(caseId=1)
 
 exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot;])
-</code></pre>
-
-<h3 id="exportwellpathcompletions">exportWellPathCompletions</h3>
-
+</code></pre><h3 id="exportwellpathcompletions">exportWellPathCompletions</h3>
 <p>Export well path completions.</p>
-
 <table>
 <thead>
 <tr>
@@ -2375,64 +2290,55 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to export well paths for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeStep</td>
 <td>The time step to export completions for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>wellPathNames</td>
 <td>Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked</td>
 <td>List of String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>fileSplit</td>
 <td>How the files are split. Choices: <code>UNIFIED_FILE</code>, <code>SPLIT_ON_WELL</code>, <code>SPLIT_ON_WELL_AND_COMPLETION_TYPE</code>. Defaults to <code>SPLIT_ON_WELL_AND_COMPLETION_TYPE</code></td>
 <td>Enum</td>
 <td></td>
 </tr>
-
 <tr>
 <td>compdatExport</td>
 <td>Chose whether transmissibilities are exported. Choices: <code>TRANSMISSIBILITIES</code>, <code>WPIMULT_AND_DEFAULT_CONNECTION_FACTORS</code>. Defaults to <code>TRANSMISSIBILITIES</code></td>
 <td>Enum</td>
 <td></td>
 </tr>
-
 <tr>
 <td>includePerforations</td>
 <td>Whether main bore perforations should be included. Defaults to <code>true</code></td>
 <td>Boolean</td>
 <td></td>
 </tr>
-
 <tr>
 <td>includeFishbones</td>
 <td>Whether fishbones should be included. Defaults to <code>true</code></td>
 <td>Boolean</td>
 <td></td>
 </tr>
-
 <tr>
 <td>excludeMainBoreForFishbones</td>
 <td>Whether main bore completions should be excluded for cells with fishbones. Defaults to <code>false</code></td>
 <td>Boolean</td>
 <td></td>
 </tr>
-
 <tr>
 <td>combinationMode</td>
 <td>Combination mode. Choices: <code>INDIVIDUALLY</code>, <code>COMBINED</code>. Defaults to <code>INDIVIDUALLY</code></td>
@@ -2441,14 +2347,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)
-</code></pre>
-
-<h3 id="exportsimwellfracturecompletions">exportSimWellFractureCompletions</h3>
-
+</code></pre><h3 id="exportsimwellfracturecompletions">exportSimWellFractureCompletions</h3>
 <p>Export fracture completions for simulation wells.</p>
-
 <table>
 <thead>
 <tr>
@@ -2458,43 +2359,37 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to export simulation well fracture completions for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>viewName</td>
 <td>The name of the view to export simulation well fracture completions for. Since view names are not unique, all views sharing the given name will be used</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeStep</td>
 <td>The time step to export completions for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>simulationWellNames</td>
 <td>Names of simulation wells to export for. Defaults to all checked wells. If a list of names are provided, those wells are included even if unchecked</td>
 <td>List of String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>fileSplit</td>
 <td>How the files are split. Choices: <code>UNIFIED_FILE</code>, <code>SPLIT_ON_WELL</code>, <code>SPLIT_ON_WELL_AND_COMPLETION_TYPE</code>. Defaults to <code>UNIFIED_FILE</code></td>
 <td>Enum</td>
 <td></td>
 </tr>
-
 <tr>
 <td>compdatExport</td>
 <td>Chose whether transmissibilities are exported. Choices: <code>TRANSMISSIBILITIES</code>, <code>WPIMULT_AND_DEFAULT_CONNECTION_FACTORS</code>. Defaults to <code>TRANSMISSIBILITIES</code></td>
@@ -2503,14 +2398,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportSimWellFractureCompletions(caseId=3, viewName=&quot;View 2&quot;, timeStep=5)
-</code></pre>
-
-<h3 id="exportmsw">exportMsw</h3>
-
+</code></pre><h3 id="exportmsw">exportMsw</h3>
 <p>Export multi-segment wells.</p>
-
 <table>
 <thead>
 <tr>
@@ -2520,31 +2410,24 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to export well paths for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>wellPath</td>
 <td>Name of well path to export well segments for</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportMsw(caseId=1, wellPath=&quot;MainWell&quot;)
-</code></pre>
-
-<h3 id="exportwellpaths">exportWellPaths</h3>
-
+</code></pre><h3 id="exportwellpaths">exportWellPaths</h3>
 <p>Export well paths.</p>
-
 <table>
 <thead>
 <tr>
@@ -2554,7 +2437,6 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>wellPathNames</td>
@@ -2562,7 +2444,6 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <td>List of String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>mdStepSize</td>
 <td>Spacing (measured depth) between each sample along the well path. Default to 5.0</td>
@@ -2571,14 +2452,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportWellPaths(wellPathNames=[&quot;B-1H&quot;, &quot;B-2H&quot;], mdStepSize=1.5)
-</code></pre>
-
-<h3 id="exportvisiblecells">exportVisibleCells</h3>
-
+</code></pre><h3 id="exportvisiblecells">exportVisibleCells</h3>
 <p>Export visible cells</p>
-
 <table>
 <thead>
 <tr>
@@ -2588,43 +2464,37 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to export cells for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>viewName</td>
 <td>Name of the view associated with the specified case</td>
 <td>Double</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>exportKeyword</td>
 <td>The keyword to export. Choices: <code>FLUXNUM</code> or <code>MULTNUM</code>. Default: <code>FLUXNUM</code></td>
 <td>Enum</td>
 <td></td>
 </tr>
-
 <tr>
 <td>visibleActiveCellsValue</td>
 <td>Value to use for visible active cells. Default: 1</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>hiddenActiveCellsValue</td>
 <td>Value to use for hidden active cells. Default: 0</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>inactiveCellsValue</td>
 <td>Value to use for inactive cells. Default: 0</td>
@@ -2633,14 +2503,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>exporVisibleCells(caseId=0, viewName=&quot;View 1&quot;, exportKeyword=MULTNUM)
-</code></pre>
-
-<h3 id="exportflowcharacteristics">exportFlowCharacteristics</h3>
-
+</code></pre><h3 id="exportflowcharacteristics">exportFlowCharacteristics</h3>
 <p>Export Flow Characteristics data to text file in CSV format</p>
-
 <table>
 <thead>
 <tr>
@@ -2650,50 +2515,43 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeSteps</td>
 <td>Time step indices</td>
 <td>List of Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>injectors</td>
 <td>Injector names</td>
 <td>List of Strings</td>
 <td></td>
 </tr>
-
 <tr>
 <td>producers</td>
 <td>Producer names</td>
 <td>List of Strings</td>
 <td></td>
 </tr>
-
 <tr>
 <td>fileName</td>
 <td>Export file name</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>minimumCommunication</td>
 <td>Minimum Communication, defaults to 0.0</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>aquiferCellThreshold</td>
 <td>Aquifer Cell Threshold, defaults to 0.1</td>
@@ -2702,14 +2560,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>exportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[&quot;INJA&quot;, &quot;INJB&quot;], producers=[&quot;PROD_F&quot;], fileName=&quot;myData.csv&quot;)
-</code></pre>
-
-<h3 id="setexportfolder">setExportFolder</h3>
-
+</code></pre><h3 id="setexportfolder">setExportFolder</h3>
 <p>Set the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.</p>
-
 <table>
 <thead>
 <tr>
@@ -2719,22 +2572,19 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>type</td>
 <td>Type of export folder to set. Choices: <code>COMPLETIONS</code>, <code>SNAPSHOTS</code>, <code>PROPERTIES</code>, <code>STATISTICS</code></td>
 <td>Enum</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>path</td>
 <td>Directory to export the given type to</td>
 <td>String</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>createFolder</td>
 <td>If true, create the folder when required. Default false.</td>
@@ -2743,16 +2593,10 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>setExportFolder(type=SNAPSHOTS, path=&quot;/home/user/snapshots&quot;)
-</code></pre>
-
-<h2 id="other">Other</h2>
-
+</code></pre><h2 id="other">Other</h2>
 <h3 id="runoctavescript">runOctaveScript</h3>
-
 <p>Execute an Octave script.</p>
-
 <table>
 <thead>
 <tr>
@@ -2762,15 +2606,13 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>path</td>
 <td>Path to the octave script to execute</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>caseIds</td>
 <td>The cases to run the octave script on. Defaults to running the script without a specified case</td>
@@ -2779,14 +2621,9 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>runOctaveScript(path=&quot;/home/user/octave/something.m&quot;, caseIds=[1,2,6])
-</code></pre>
-
-<h3 id="setmainwindowsize">setMainWindowSize</h3>
-
+</code></pre><h3 id="setmainwindowsize">setMainWindowSize</h3>
 <p>Resize the main window to the specified size.</p>
-
 <table>
 <thead>
 <tr>
@@ -2796,31 +2633,24 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>width</td>
 <td>The width to set for the main window</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>height</td>
 <td>The height to set for the main window</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>setMainWindowSize(width=1920, height=1200)
-</code></pre>
-
-<h3 id="computecasegroupstatistics">computeCaseGroupStatistics</h3>
-
+</code></pre><h3 id="computecasegroupstatistics">computeCaseGroupStatistics</h3>
 <p>Compute statistics for statistics cases.</p>
-
 <table>
 <thead>
 <tr>
@@ -2830,7 +2660,6 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseIds</td>
@@ -2840,16 +2669,11 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-
 <pre><code>computeCaseGroupStatistics(caseIds=[5])
 
 computeCaseGroupStatistics(caseIds=[2,4,8])
-</code></pre>
-
-<h3 id="settimestep">setTimeStep</h3>
-
+</code></pre><h3 id="settimestep">setTimeStep</h3>
 <p>Set the time step for a given case. The time step is used for all views on the case.</p>
-
 <table>
 <thead>
 <tr>
@@ -2859,31 +2683,24 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to set time step for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeStep</td>
 <td>Index of time step to switch to</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>setTimeStep(caseId=1, timeStep=8)
-</code></pre>
-
-<h3 id="scalefracturetemplate">scaleFractureTemplate</h3>
-
+</code></pre><h3 id="scalefracturetemplate">scaleFractureTemplate</h3>
 <p>Scale fracture template parameters.</p>
-
 <table>
 <thead>
 <tr>
@@ -2893,36 +2710,31 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>id</td>
 <td>ID of fracture template</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>halfLength</td>
 <td>Half Length scale factor</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>height</td>
 <td>Height scale factor</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>dFactor</td>
 <td>D-factor scale factor</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>conductivity</td>
 <td>Conductivity scale factor</td>
@@ -2931,14 +2743,9 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-
 <pre><code>scaleFractureTemplate(id=1, width=2, height=1.5)
-</code></pre>
-
-<h3 id="setfracturecontainment">setFractureContainment</h3>
-
+</code></pre><h3 id="setfracturecontainment">setFractureContainment</h3>
 <p>Set fracture template containment parameters.</p>
-
 <table>
 <thead>
 <tr>
@@ -2948,38 +2755,30 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>id</td>
 <td>ID of fracture template</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>topLayer</td>
 <td>Top layer containment</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>baseLayer</td>
 <td>Base layer containment</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>setFractureContainment(id=1, topLayer=2, baseLayer=7)
-</code></pre>
-
-<h3 id="createmultiplefractures">createMultipleFractures</h3>
-
+</code></pre><h3 id="createmultiplefractures">createMultipleFractures</h3>
 <p>Create multiple fractures on one or more well paths.</p>
-
 <table>
 <thead>
 <tr>
@@ -2989,64 +2788,55 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>Case ID</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>templateId</td>
 <td>Fracture template id</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>wellPathNames</td>
 <td>Well path names. Default: All well paths</td>
 <td>List of Strings</td>
 <td></td>
 </tr>
-
 <tr>
 <td>minDistFromWellTd</td>
 <td>Min distance from well path tip. Default: 100.0 m</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>maxFracturesPerWell</td>
 <td>Max fractures per well. Default: 100</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>topLayer</td>
 <td>Top K layer. Default: Top layer from current model</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>baseLayer</td>
 <td>Base K layer. Default: Bottom layer from current model</td>
 <td>Integer</td>
 <td></td>
 </tr>
-
 <tr>
 <td>spacing</td>
 <td>Distance between fractures. Default: 300.0 m</td>
 <td>Double</td>
 <td></td>
 </tr>
-
 <tr>
 <td>action</td>
 <td>How to handle existing fractures. Choices: <code>APPEND_FRACTURES</code>, <code>REPLACE_FRACTURES</code>. The replace option will delete all existing fractures before adding new ones. Default: <code>APPEND_FRACTURES</code></td>
@@ -3055,14 +2845,9 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-
 <pre><code>createMultipleFractures(caseId=0, templateId=1, wellPathNames=[&quot;B-1H&quot;, &quot;B-2H&quot;], action=REPLACE_FRACTURES)
-</code></pre>
-
-<h3 id="createlgrforcompletions">createLgrForCompletions</h3>
-
+</code></pre><h3 id="createlgrforcompletions">createLgrForCompletions</h3>
 <p>Create temporary LGRs for completions on the selected well paths. The splitType parameter controls which main grid cells to split into LGRs. The LGR_PER_CELL option splits only those main grid cells that intersect with a completion. The LGR_PER_COMPLETION option splits all main grid cells that are located within an IJK bounding box covering all intersected cells for each completion. The LGR_PER_WELL works like the previous option, but the bounding box covers intersected cells for all completions on a well path.</p>
-
 <table>
 <thead>
 <tr>
@@ -3072,50 +2857,43 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseId</td>
 <td>ID of case to create LGRs for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>timeStep</td>
 <td>The time step to create LGRs for</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>wellPathNames</td>
 <td>Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked</td>
 <td>List of String</td>
 <td></td>
 </tr>
-
 <tr>
 <td>refinementI</td>
 <td>Size of the LGR along the I axis, in each main grid cell.</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>refinementJ</td>
 <td>Size of the LGR along the J axis, in each main grid cell.</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>refinementK</td>
 <td>Size of the LGR along the K axis, in each main grid cell.</td>
 <td>Integer</td>
-<td>&#10004;</td>
+<td>✔</td>
 </tr>
-
 <tr>
 <td>splitType</td>
 <td>How to split the LGRs. Options: <code>LGR_PER_CELL</code>, <code>LGR_PER_COMPLETION</code>, <code>LGR_PER_WELL</code>. Default option is <code>LGR_PER_COMPLETION</code></td>
@@ -3124,14 +2902,9 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-
 <pre><code>createLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[&quot;B-1H&quot;, &quot;B-2H&quot;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)
-</code></pre>
-
-<h3 id="createsaturationpressureplots">createSaturationPressurePlots</h3>
-
+</code></pre><h3 id="createsaturationpressureplots">createSaturationPressurePlots</h3>
 <p>Create saturation pressure plots for the specified cases.</p>
-
 <table>
 <thead>
 <tr>
@@ -3141,7 +2914,6 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 <th>Required</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>caseIds</td>
@@ -3151,11 +2923,9 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-
 <pre><code>createSaturationPressurePlots(caseIds=[0])
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -3329,6 +3099,19 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -3339,6 +3122,9 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
             
         
                     
+            
+        
+                    
                         
             
             
@@ -4489,20 +4275,20 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/commandlineinterface/index.html b/scripting/commandlineinterface/index.html
index c40fb1c005..05a3cf2c38 100644
--- a/scripting/commandlineinterface/index.html
+++ b/scripting/commandlineinterface/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Command Line Interface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,28 +1802,27 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#command-line-options">Command line options</a>
-<ul>
-<li><a href="#general">General</a></li>
-<li><a href="#command-files">Command files</a></li>
-<li><a href="#snapshots">Snapshots</a></li>
-<li><a href="#case-handling">Case handling</a></li>
-<li><a href="#summary-plotting">Summary plotting</a></li>
-<li><a href="#testing">Testing</a></li>
-</ul></li>
-<li><a href="#examples">Examples</a>
-<ul>
-<li><a href="#create-snapshots-of-all-views-for-multiple-cases">Create snapshots of all views for multiple cases</a></li>
-<li><a href="#replace-a-single-case-and-take-snapshots-of-all-views">Replace a single case and take snapshots of all views</a></li>
-<li><a href="#replace-source-cases-in-a-case-group-and-create-snapshot">Replace source cases in a case group and create snapshot</a></li>
-<li><a href="#replace-source-cases-in-multiple-case-groups-and-create-snapshots">Replace source cases in multiple case groups and create snapshots</a></li>
-<li><a href="#summary-plotting-1">Summary plotting</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#command-line-options">Command line options</a>
+      <ul>
+        <li><a href="#general">General</a></li>
+        <li><a href="#command-files">Command files</a></li>
+        <li><a href="#snapshots">Snapshots</a></li>
+        <li><a href="#case-handling">Case handling</a></li>
+        <li><a href="#summary-plotting">Summary plotting</a></li>
+        <li><a href="#testing">Testing</a></li>
+      </ul>
+    </li>
+    <li><a href="#examples">Examples</a>
+      <ul>
+        <li><a href="#create-snapshots-of-all-views-for-multiple-cases">Create snapshots of all views for multiple cases</a></li>
+        <li><a href="#replace-a-single-case-and-take-snapshots-of-all-views">Replace a single case and take snapshots of all views</a></li>
+        <li><a href="#replace-source-cases-in-a-case-group-and-create-snapshot">Replace source cases in a case group and create snapshot</a></li>
+        <li><a href="#replace-source-cases-in-multiple-case-groups-and-create-snapshots">Replace source cases in multiple case groups and create snapshots</a></li>
+        <li><a href="#summary-plotting-1">Summary plotting</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1814,18 +1847,11 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.</p>
-
 <p>Command line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for <a href="http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html#Command_002dLine-Interfaces">Command Line Interfaces</a>.</p>
-
 <p>Examples on how command line options are used are given <a href="/scripting/commandlineinterface/#examples">below</a></p>
-
 <h2 id="command-line-options">Command line options</h2>
-
 <h3 id="general">General</h3>
-
 <table>
 <thead>
 <tr>
@@ -1833,47 +1859,38 @@ if (!doNotTrack) {
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;&#45;help, &#45;&#45;?</td>
+<td>--help, --?</td>
 <td>Displays help text and version info</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;project &lt;filename&gt;</td>
+<td>--project &lt;filename&gt;</td>
 <td>Open project file &lt;filename&gt;.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;last</td>
+<td>--last</td>
 <td>Open last used project.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;size &lt;width&gt; &lt;height&gt;</td>
+<td>--size &lt;width&gt; &lt;height&gt;</td>
 <td>Set size of the main application window.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;console</td>
+<td>--console</td>
 <td>Launch as a console application without graphics</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;server [&lt;portnumber&gt;]</td>
+<td>--server [&lt;portnumber&gt;]</td>
 <td>Launch as a GRPC server. Default port is 50051</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;startdir &lt;folder&gt;</td>
+<td>--startdir &lt;folder&gt;</td>
 <td>Set startup directory.</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="command-files">Command files</h3>
-
 <table>
 <thead>
 <tr>
@@ -1881,22 +1898,18 @@ if (!doNotTrack) {
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;&#45;commandFile &lt;commandFile&gt;</td>
+<td>--commandFile &lt;commandFile&gt;</td>
 <td>Execute a command file. See <a href="/scripting/commandfile/">command file documentation.</a></td>
 </tr>
-
 <tr>
-<td>&#45;&#45;commandFileProject &lt;filename&gt;</td>
+<td>--commandFileProject &lt;filename&gt;</td>
 <td>Project to use if performing case looping for command file. Used in conjunction with <code>commandFileReplaceCases</code>.</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="snapshots">Snapshots</h3>
-
 <table>
 <thead>
 <tr>
@@ -1904,22 +1917,18 @@ if (!doNotTrack) {
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;&#45;savesnapshots all&#124;views&#124;plots&#124;</td>
+<td>--savesnapshots all|views|plots|</td>
 <td>Save snapshot of all views or plots to project file location sub folder &lsquo;snapshots&rsquo;. Option &lsquo;all&rsquo; will include both views and plots. Application closes after snapshots have been written.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;multiCaseSnapshots &lt;gridListFile&gt;</td>
+<td>--multiCaseSnapshots &lt;gridListFile&gt;</td>
 <td>For each grid file listed in the &lt;gridListFile&gt; file, replace the first case in the project and save snapshot of all views.</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="case-handling">Case handling</h3>
-
 <table>
 <thead>
 <tr>
@@ -1927,76 +1936,62 @@ if (!doNotTrack) {
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;&#45;case &lt;casename&#124;filename&gt; [&lt;casename&#124;filename&gt;]</td>
+<td>--case &lt;casename|filename&gt; [&lt;casename|filename&gt;]</td>
 <td>Imports the Eclipse cases specified by case name with or without extension.If &lt;casename&gt;, import the corresponding grid file and summary file. If &lt;filename&gt; has extension .GRRID/.EGRID, import the grid file and corresponding summary file. If &lt;filename&gt; has extension .SMSPEC, import the summary file (does not open the grid file)</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;replaceCase [&lt;caseId&gt;] &lt;newGridFile&gt;</td>
+<td>--replaceCase [&lt;caseId&gt;] &lt;newGridFile&gt;</td>
 <td>Replace grid in &lt;caseId&gt; or first case with &lt;newGridFile&gt;. Repeat parameter for multiple replace operations.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;replaceSourceCases [&lt;caseGroupId&gt;] &lt;gridListFile&gt;</td>
+<td>--replaceSourceCases [&lt;caseGroupId&gt;] &lt;gridListFile&gt;</td>
 <td>Replace source cases in &lt;caseGroupId&gt; or first grid case group with the grid files listed in the &lt;gridListFile&gt; file. Repeat parameter for multiple replace operations.</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;commandFileReplaceCases [&lt;caseId&gt;] &lt;caseListFile&gt;</td>
+<td>--commandFileReplaceCases [&lt;caseId&gt;] &lt;caseListFile&gt;</td>
 <td>Supply list of cases to replace in project, performing command file for each case. Project to replace cases must be set with <code>commandFileProject</code>. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId.</td>
 </tr>
 </tbody>
 </table>
 
-
-<div class="notices note" ><p><b>Reduce project load time using <code>&ndash;replaceSourceCases</code></b>
- <br>
+<div class="notices note" ><p><!-- raw HTML omitted -->Reduce project load time using <!-- raw HTML omitted -->&ndash;replaceSourceCases<!-- raw HTML omitted --><!-- raw HTML omitted -->
+<!-- raw HTML omitted -->
 ResInsight stores data computed by statistics calculation in a cache file. When a project file is loaded, data from this cache is also imported. For large cases, the cached data can be large. When replacing source cases during batch, this data is never used and can be removed from the cache using the following workaround:
-<br>
-  - Open the project file used to produce statistics
-  <br>
-  - Select the statistics object in the project tree
-  <br>
-  - Click the button <b>Edit (Will DELETE current result)</b>
-  <br>
-  - Save the project file</p>
+<!-- raw HTML omitted --></p>
+<ul>
+<li>Open the project file used to produce statistics
+<!-- raw HTML omitted --></li>
+<li>Select the statistics object in the project tree
+<!-- raw HTML omitted --></li>
+<li>Click the button <!-- raw HTML omitted -->Edit (Will DELETE current result)<!-- raw HTML omitted -->
+<!-- raw HTML omitted --></li>
+<li>Save the project file</li>
+</ul>
 </div>
 
-
 <h3 id="summary-plotting">Summary plotting</h3>
-
 <p>The summary plotting command option follows the following syntax:</p>
-
 <pre><code>resinsight --summaryplot [&lt;plotOptions&gt;] &lt;eclipsesummaryvectorfilters&gt; &lt;eclipsedatafiles&gt;
 
 where:
 &lt;plotOptions&gt;                 denote summary plot options, see table below
 &lt;eclipsesummaryvectorfilters&gt; has the syntax &lt;vectorname&gt;[:&lt;item&gt;[:&lt;subitem&gt;[:i,j,k]]]
 &lt;eclipsedatafiles&gt;            lists a set of Eclipse data files with or without extension
-</code></pre>
-
-<p>The summary plotting command option creates one summary plot for each of the the summary vectors matched by<br />
+</code></pre><p>The summary plotting command option creates one summary plot for each of the the summary vectors matched by<br>
 <em>&lt;eclipsesummaryvectorfilters&gt;</em> using all listed Eclipse data files in each plot.</p>
-
-<p>Eclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above.
+<p>Eclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above. 
 Wildcards can be used in the specification. Brief examples are:</p>
-
 <ul>
 <li><code>WOPT:*</code>: One total oil production curve for each well.</li>
 <li><code>FOPT FWPT</code>: Two curves with oil and water total production.</li>
 <li><code>BPR:15,28,*</code>: Oil phase pressure for all blocks along k as separate curves. Please note no space in expression.</li>
 </ul>
-
 <p><a href="/scripting/commandlineinterface/#summary-plotting-1">Examples</a> are listed below.</p>
-
 <p>As long as only summary vectors are requested, only the corresponding SMSPEC file will be opened for each case.
 However, if a grid property is requested, the corresponding EGRID and restart data will be loaded as well.</p>
-
 <p>Specifying summary plot options is optional, c.f. table below.</p>
-
 <table>
 <thead>
 <tr>
@@ -2004,52 +1999,42 @@ However, if a grid property is requested, the corresponding EGRID and restart da
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;help</td>
+<td>-help</td>
 <td>Shows help text and ignores any other option.</td>
 </tr>
-
 <tr>
-<td>&#45;h</td>
+<td>-h</td>
 <td>Includes history vectors read from summary file if the vectors exist. Only history vectors from the first summary case in the project will be included.</td>
 </tr>
-
 <tr>
-<td>&#45;nl</td>
+<td>-nl</td>
 <td>Omits legend in plot.</td>
 </tr>
-
 <tr>
-<td>&#45;s</td>
+<td>-s</td>
 <td>Creates only one plot including all the defined vectors and cases.</td>
 </tr>
-
 <tr>
-<td>&#45;n</td>
+<td>-n</td>
 <td>Scales all curves into the range 0.0-1.0. Useful when using -s.</td>
 </tr>
-
 <tr>
-<td>&#45;e</td>
+<td>-e</td>
 <td>Imports all the cases as an ensemble, and create ensemble curves sets instead of single curves.</td>
 </tr>
-
 <tr>
-<td>&#45;c  &lt;parametername&gt;</td>
-<td>Same as <em>-e</em>, but colors the curves by the ensemble parameter <parametername> .</td>
+<td>-c  &lt;parametername&gt;</td>
+<td>Same as <em>-e</em>, but colors the curves by the ensemble parameter <!-- raw HTML omitted --> .</td>
 </tr>
-
 <tr>
-<td>&#45;cl &lt;parametername&gt;</td>
+<td>-cl &lt;parametername&gt;</td>
 <td>Same as <em>-c</em>, but uses logarithmic legend.</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="testing">Testing</h3>
-
 <table>
 <thead>
 <tr>
@@ -2057,110 +2042,65 @@ However, if a grid property is requested, the corresponding EGRID and restart da
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&#45;&#45;regressiontest &lt;folder&gt;</td>
+<td>--regressiontest &lt;folder&gt;</td>
 <td>System command</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;updateregressiontestbase &lt;folder&gt;</td>
+<td>--updateregressiontestbase &lt;folder&gt;</td>
 <td>System command</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;unittest</td>
+<td>--unittest</td>
 <td>Execute integration tests</td>
 </tr>
-
 <tr>
-<td>&#45;&#45;ignoreArgs</td>
+<td>--ignoreArgs</td>
 <td>System command</td>
 </tr>
 </tbody>
 </table>
-
 <p>See also the <a href="/misc/regressiontestsystem/">Regression Test System </a> for a more in-depth explanation.</p>
-
 <h2 id="examples">Examples</h2>
-
 <p>Most examples are also available from the <a href="https://github.com/OPM/ResInsight/tree/master/TestModels/Case_with_10_timesteps">test section</a>.</p>
-
 <h3 id="create-snapshots-of-all-views-for-multiple-cases">Create snapshots of all views for multiple cases</h3>
-
 <p>A list of cases is defined in <strong>CaseList.txt</strong>, containing the following</p>
-
 <pre><code>Real0/BRUGGE_0000.EGRID
 Real10/BRUGGE_0010.EGRID
 Real30/BRUGGE_0030.EGRID
 Real40/BRUGGE_0040.EGRID
-</code></pre>
-
-<p>The command line used to run this example is shown here:</p>
-
+</code></pre><p>The command line used to run this example is shown here:</p>
 <pre><code>ResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500
-</code></pre>
-
-<p>This will instruct ResInsight to read the project file <strong>BatchTest.rsp</strong>. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.</p>
-
+</code></pre><p>This will instruct ResInsight to read the project file <strong>BatchTest.rsp</strong>. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.</p>
 <h3 id="replace-a-single-case-and-take-snapshots-of-all-views">Replace a single case and take snapshots of all views</h3>
-
 <p>The command line used to run this example is shown here:</p>
-
 <pre><code>ResInsight --project BatchTest.rsp --replaceCase &quot;Real10\BRUGGE_0010.EGRID&quot; --savesnapshots
-</code></pre>
-
-<p>This will instruct ResInsight to read the project file <strong>BatchTest.rsp</strong>. The specified case <strong>Real10\BRUGGE_0010.EGRID</strong> will be imported into the project, and snapshots of all views will be written to file.</p>
-
+</code></pre><p>This will instruct ResInsight to read the project file <strong>BatchTest.rsp</strong>. The specified case <strong>Real10\BRUGGE_0010.EGRID</strong> will be imported into the project, and snapshots of all views will be written to file.</p>
 <h3 id="replace-source-cases-in-a-case-group-and-create-snapshot">Replace source cases in a case group and create snapshot</h3>
-
 <p>A list of cases is defined in <strong>CaseList2.txt</strong>, containing the following</p>
-
 <pre><code>Real0/BRUGGE_0000.EGRID
 Real10/BRUGGE_0010.EGRID
-</code></pre>
-
-<p>The command line used to run this example is shown here:</p>
-
+</code></pre><p>The command line used to run this example is shown here:</p>
 <pre><code>ResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots
-</code></pre>
-
-<p>This will instruct ResInsight to read the project file <strong>BatchStatistics.rsp</strong>. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.</p>
-
+</code></pre><p>This will instruct ResInsight to read the project file <strong>BatchStatistics.rsp</strong>. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.</p>
 <h3 id="replace-source-cases-in-multiple-case-groups-and-create-snapshots">Replace source cases in multiple case groups and create snapshots</h3>
-
 <p>Multiple source case groups can be updated by repeating the replaceSourceCases parameter.</p>
-
 <p>The command line used to run this example is shown here:</p>
-
 <pre><code>ResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots
-</code></pre>
-
-<p>This will instruct ResInsight to read the project file <strong>BatchStatistics.rsp</strong>. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.</p>
-
+</code></pre><p>This will instruct ResInsight to read the project file <strong>BatchStatistics.rsp</strong>. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.</p>
 <p>The possibility to replace multiple cases can also be applied for single case replace (parameter <em>replaceCase</em>).</p>
-
 <h3 id="summary-plotting-1">Summary plotting</h3>
-
 <p>The following command line performs a <a href="/plot-window/summaryplots/">summary plot</a> for <em>FOPT</em> based on Eclipse summary file <em>1_R001_REEK-0.SMSPEC</em>.</p>
-
 <pre><code>ResInsight --summaryplot 1_R001_REEK-0 FOPT
-</code></pre>
-
-<p>Based on file <em>1_R001_REEK-0.SMSPEC</em>, the following command line performs a <a href="/plot-window/summaryplots/">summary plot</a>
+</code></pre><p>Based on file <em>1_R001_REEK-0.SMSPEC</em>, the following command line performs a <a href="/plot-window/summaryplots/">summary plot</a> 
 for <em>FOPT</em> and any <em>WOPT</em>-vector for well <em>op_2</em>.
 The trailing option <em>-s</em> gathers the vectors into a single summary plot.</p>
-
 <pre><code>ResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 -s
-</code></pre>
-
-<p>Adding to previous example, the following command line also plots the 3D grid property <code>SOIL</code> for cell (20, 21, 1).</p>
-
+</code></pre><p>Adding to previous example, the following command line also plots the 3D grid property <code>SOIL</code> for cell (20, 21, 1).</p>
 <pre><code>ResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 SOIL:20,21,1
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -2334,6 +2274,19 @@ The trailing option <em>-s</em> gathers the vectors into a single summary plot.<
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2344,6 +2297,9 @@ The trailing option <em>-s</em> gathers the vectors into a single summary plot.<
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3491,20 +3447,20 @@ The trailing option <em>-s</em> gathers the vectors into a single summary plot.<
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/index.html b/scripting/index.html
index 20dca64b0b..469fe3218f 100644
--- a/scripting/index.html
+++ b/scripting/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Scripting :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1762,14 +1796,11 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#command-line-interface-and-command-files">Command Line Interface and Command files</a></li>
-<li><a href="#python-interface">Python Interface</a></li>
-<li><a href="#octave-interface">Octave Interface</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#command-line-interface-and-command-files">Command Line Interface and Command files</a></li>
+    <li><a href="#python-interface">Python Interface</a></li>
+    <li><a href="#octave-interface">Octave Interface</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1795,42 +1826,30 @@ if (!doNotTrack) {
 
 
 
-	
-
-<p><img src="/images/scripting/ExecuteOctaveScriptOnSelectedCases.png" alt="" /></p>
-
+	<p><img src="/images/scripting/ExecuteOctaveScriptOnSelectedCases.png" alt=""></p>
 <p>ResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:</p>
-
 <ul>
 <li>Command line interface and Command files</li>
 <li>Python interface</li>
 <li>Octave interface</li>
 </ul>
-
 <h2 id="command-line-interface-and-command-files">Command Line Interface and Command files</h2>
-
-<p>ResInsight supports several <a href="/scripting/commandlineinterface/">command line parameters</a>
-for automation via shell scripts.
+<p>ResInsight supports several [command line parameters] (/scripting/commandlineinterface/)
+for automation via shell scripts. 
 By gathering commands into a <a href="/scripting/commandfile/">Command file</a>,
-you may run a sequence of commands by supplying the command file as a
+you may run a sequence of commands by supplying the command file as a 
 <a href="/scripting/commandlineinterface/">command line parameter</a>.</p>
-
 <h2 id="python-interface">Python Interface</h2>
-
-<p>ResInsight offers a <a href="/scripting/pythonrips/">Python Interface</a>
-which allows you to interact with a running ResInsight instance from a Python script.
+<p>ResInsight offers a [Python Interface] (/scripting/pythonrips/)
+which allows you to interact with a running ResInsight instance from a Python script. 
 This allows using the powerful Python language, numerical libraries, and other support modules in conjunction with ResInsight. The Python client package is compatible with <strong>Python 3</strong>.</p>
-
 <p>For examples on how to use Python, see <a href="/scripting/pythonexamples/">Examples</a></p>
-
 <h2 id="octave-interface">Octave Interface</h2>
-
 <p>By the interface to <a href="http://www.gnu.org/software/octave/" title="Octave">Octave</a> you will find:</p>
-
 <ul>
 <li>Octave functions that communicates with a running ResInsight session</li>
 <li>Features to simplify management and editing of Octave scripts from ResInsight</li>
-<li>Commands to execute scripts using Octave.<br /></li>
+<li>Commands to execute scripts using Octave.</li>
 </ul>
 
 
@@ -2009,6 +2028,19 @@ This allows using the powerful Python language, numerical libraries, and other s
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2019,6 +2051,9 @@ This allows using the powerful Python language, numerical libraries, and other s
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3165,20 +3200,20 @@ This allows using the powerful Python language, numerical libraries, and other s
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/index.xml b/scripting/index.xml
index fa29c3c2af..24de880d4d 100644
--- a/scripting/index.xml
+++ b/scripting/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Scripting on ResInsight</title>
@@ -19,7 +19,7 @@
       <description>ResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.
 Command line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for Command Line Interfaces.
 Examples on how command line options are used are given below
-Command line options General    Parameter Description     &amp;#45;&amp;#45;help, &amp;#45;&amp;#45;?</description>
+Command line options General    Parameter Description     --help, --?</description>
     </item>
     
     <item>
@@ -40,7 +40,7 @@ Command List Case Control Commands  openProject closeProject setStartDir loadCas
       
       <guid>https://resinsight.org/scripting/pythonexamples/</guid>
       <description>This pages is created based on the content in the PythonExamples folder located inside the rips module, made available online for convenience.
-AllCases ################################################################################### # This example will connect to ResInsight, retrieve a list of cases and print info # ################################################################################### # Import the ResInsight Processing Server Module import rips # Connect to ResInsight resinsight = rips.Instance.find() if resinsight is not None: # Get a list of all cases cases = resinsight.</description>
+AllCases #################################################################################### This example will connect to ResInsight, retrieve a list of cases and print info# #################################################################################### Import the ResInsight Processing Server Moduleimport rips# Connect to ResInsightresinsight = rips.Instance.find()if resinsight is not None:# Get a list of all casescases = resinsight.</description>
     </item>
     
     <item>
@@ -51,10 +51,10 @@ AllCases #######################################################################
       <guid>https://resinsight.org/scripting/pythonrips/</guid>
       <description>Instance Module class rips.instance.Instance(port=50051, launched=False) The ResInsight Instance class. Use to launch or find existing ResInsight instances
 launched() Tells us whether the application was launched as a new process. If the application was launched we may need to close it when exiting the script.
- Type
+  Type
 bool
   commands() Command executor. Set when creating an instance.
- Type
+  Type
 Commands
   project() Current project in ResInsight. Set when creating an instance and updated when opening/closing projects.</description>
     </item>
@@ -77,9 +77,8 @@ On some systems the pip command may have to be replaced by python -m pip.</descr
       
       <guid>https://resinsight.org/scripting/octaveinterface/</guid>
       <description>ResInsight provides a flexible interface to Octave including:
- Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.
-  The Octave functions are documented in Octave Interface Reference.
-Note: The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.
+ Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.  The Octave functions are documented in Octave Interface Reference.
+Note:The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.
 Octave Script Management Octave scripts are available in the Scripts folder in the Project Tree.</description>
     </item>
     
@@ -89,7 +88,8 @@ Note: The Octave interface does not support Flow diagnostics and Injection flood
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/scripting/octaveinterfacereference/</guid>
-      <description>Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the &amp;ldquo;Current Case&amp;rdquo;), or the script is designed to access the selection and traverse the cases by itself.</description>
+      <description>Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the &amp;ldquo;Current Case&amp;rdquo;), or the script is designed to access the selection and traverse the cases by itself.
+Note:The Octave interface does not support Geomechanical cases and flow diagnostic results.</description>
     </item>
     
   </channel>
diff --git a/scripting/octaveinterface/index.html b/scripting/octaveinterface/index.html
index 9011c8a440..f84a71d6de 100644
--- a/scripting/octaveinterface/index.html
+++ b/scripting/octaveinterface/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Octave Interface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,32 +1802,26 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#octave-script-management">Octave Script Management</a>
-<ul>
-<li><a href="#adding-script-folders">Adding Script Folders</a></li>
-<li><a href="#editing-octave-scripts">Editing Octave Scripts</a></li>
-</ul></li>
-<li><a href="#executing-octave-scripts">Executing Octave Scripts</a>
-<ul>
-<li><a href="#executing-a-script-once">Executing a Script Once</a></li>
-<li><a href="#executing-a-script-for-each-selected-case">Executing a Script for Each Selected Case</a></li>
-<li><a href="#process-monitor">Process Monitor</a></li>
-</ul></li>
-<li><a href="#octave-script-examples">Octave Script Examples</a>
-<ul>
-<li>
-<ul>
-<li><a href="#example-1">Example 1</a></li>
-<li><a href="#example-2">Example 2</a></li>
-<li><a href="#example-3">Example 3</a></li>
-<li><a href="#example-4-might-be-slow-on-big-models">Example 4 ( Might be slow on big models)</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#octave-script-management">Octave Script Management</a>
+      <ul>
+        <li><a href="#adding-script-folders">Adding Script Folders</a></li>
+        <li><a href="#editing-octave-scripts">Editing Octave Scripts</a></li>
+      </ul>
+    </li>
+    <li><a href="#executing-octave-scripts">Executing Octave Scripts</a>
+      <ul>
+        <li><a href="#executing-a-script-once">Executing a Script Once</a></li>
+        <li><a href="#executing-a-script-for-each-selected-case">Executing a Script for Each Selected Case</a></li>
+        <li><a href="#process-monitor">Process Monitor</a></li>
+      </ul>
+    </li>
+    <li><a href="#octave-script-examples">Octave Script Examples</a>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1818,157 +1846,115 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>ResInsight provides a flexible interface to <a href="http://www.gnu.org/software/octave/" title="Octave">Octave</a> including:</p>
-
 <ul>
 <li>Octave functions that communicates with a running ResInsight session</li>
 <li>Features to simplify management and editing of Octave scripts from ResInsight</li>
-<li>Commands to execute scripts using Octave.<br /></li>
+<li>Commands to execute scripts using Octave.</li>
 </ul>
-
 <p>The Octave functions are documented in <a href="/scripting/octaveinterfacereference/">Octave Interface Reference</a>.</p>
 
-
-<div class="notices info" ><p><b>Note:</b> The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.</p>
+<div class="notices info" ><p><!-- raw HTML omitted -->Note:<!-- raw HTML omitted --> The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.</p>
 </div>
 
-
 <h2 id="octave-script-management">Octave Script Management</h2>
-
 <p>Octave scripts are available in the <strong>Scripts</strong> folder in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/scripting/OctaveScriptTree.png" alt="" /></p>
-
+<p><img src="/images/scripting/OctaveScriptTree.png" alt=""></p>
 <p>This folder contains an entry for each of the directories you have added as a <strong>Script Folder</strong>. Each of the folder lists available <em><code>*.m</code></em> files and sub directories.</p>
-
 <h3 id="adding-script-folders">Adding Script Folders</h3>
-
 <p>You can add directories by right-clicking the <strong>Scripts</strong> item to access the right-click menu.</p>
-
 <p>Multiple standard script folder locations can also be defined in the field <strong>Shared Script Folder(s)</strong> in the <strong>Preferences Dialog</strong> (<strong>Edit -&gt; Preferences</strong>).</p>
-
 <h3 id="editing-octave-scripts">Editing Octave Scripts</h3>
-
 <p>To enable script editing from ResInsight you need to set up the path to a text editor in the <strong>Script Editor</strong> field in the <strong>Preferences Dialog</strong> (<strong>Edit -&gt; Preferences</strong>)</p>
-
 <p>When done, scripts can be edited using the right-click menu command <strong>Edit</strong> on the script item in the tree.</p>
-
 <p>If you add a script file directly by creating a new file, the new script can be made visible in the user interface by activating <strong>Refresh</strong> in the right-click menu of a script folder.</p>
-
 <h2 id="executing-octave-scripts">Executing Octave Scripts</h2>
-
 <p>ResInsight can be instructed to execute an Octave script once as a one shot operation, or several times, one time for each selected case. The <a href="/scripting/octaveinterfacereference/">Octave Interface Reference</a> highlights in more depth how to design your Octave scripts to utilize these features.</p>
-
 <h3 id="executing-a-script-once">Executing a Script Once</h3>
-
 <p>A script can be started by navigating to the script in the <strong>Project Tree</strong>, and selecting <strong>Execute</strong> from the right-click menu. The currently active case (The one with the active 3D View) will then be set as ResInsight&rsquo;s <em>Current Case</em>, and the script is executed once.</p>
-
 <h3 id="executing-a-script-for-each-selected-case">Executing a Script for Each Selected Case</h3>
-
 <p>One script can be executed on many cases by first selecting a set of cases, and then activating <strong>Execute script</strong> from the right-click menu on the case selection. The script is then executed once per selected case setting the ResInsight&rsquo;s <em>Current Case</em> each time.</p>
-
-<p><img src="/images/scripting/ExecuteOctaveScriptOnSelectedCases.png" alt="" /></p>
-
+<p><img src="/images/scripting/ExecuteOctaveScriptOnSelectedCases.png" alt=""></p>
 <h3 id="process-monitor">Process Monitor</h3>
-
 <p>When an Octave script is executed, the <strong>Process Monitor</strong> pops up and displays the output from Octave during the script execution as displayed below:</p>
-
-<p><img src="/images/scripting/ProcessMonitor.png" alt="" /></p>
-
+<p><img src="/images/scripting/ProcessMonitor.png" alt=""></p>
 <p>In addition to the output from the script, it prints a start and stop time stamp. The <strong>Clear</strong>-button deletes all the text in the monitor, and the <strong>Stop</strong>-button tries to kill the running Octave process.</p>
-
 <h2 id="octave-script-examples">Octave Script Examples</h2>
-
 <p>Here are some example-scripts that illustrates the use of the octave interface.</p>
 
-
-<div class="notices info" ><p><b>Disclaimer:</b> The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.</p>
+<div class="notices info" ><p><!-- raw HTML omitted -->Disclaimer:<!-- raw HTML omitted --> The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.</p>
 </div>
 
-
 <h4 id="example-1">Example 1</h4>
-
-<pre><code class="language-matlab"># Calculate change of oil saturation from time step to time step
-SOIL = riGetActiveCellProperty(&quot;SOIL&quot;);
+<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-matlab" data-lang="matlab"># Calculate change of oil saturation from time step to time step
+SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
 SOILDIFF = SOIL;
 
-i = 0;
-for timestep = SOIL
-    if (i &gt; 0) 
-        SOILDIFF(:,i) = timestep - SOIL(:,i);
-    endif
-    i++;
+i = <span style="color:#ae81ff">0</span>;
+<span style="color:#66d9ef">for</span> timestep = SOIL
+	<span style="color:#66d9ef">if</span> (i <span style="color:#f92672">&gt;</span> <span style="color:#ae81ff">0</span>) 
+		SOILDIFF(:,i) = timestep <span style="color:#f92672">-</span> SOIL(:,i);
+	endif
+	i<span style="color:#f92672">++</span>;
 endfor
-SOILDIFF(:,i) = 0;
+SOILDIFF(:,i) = <span style="color:#ae81ff">0</span>;
 
-riSetActiveCellProperty(SOILDIFF, &quot;SOILDIFF&quot;);
-</code></pre>
-
-<h4 id="example-2">Example 2</h4>
-
-<pre><code class="language-matlab"># Set all values to &quot;Undefined&quot; exept k-layers from 17 to 20
+riSetActiveCellProperty(SOILDIFF, &#34;SOILDIFF&#34;);
+</code></pre></div><h4 id="example-2">Example 2</h4>
+<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-matlab" data-lang="matlab"># Set all values to &#34;Undefined&#34; exept k<span style="color:#f92672">-</span>layers from <span style="color:#ae81ff">17</span> to <span style="color:#ae81ff">20</span>
 CInfo = riGetActiveCellInfo();
-SOIL = riGetActiveCellProperty(&quot;SOIL&quot;);
+SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
 
-Mask = (CInfo(:,4) &lt; 17) | (CInfo(:,4) &gt; 20)
+Mask = (CInfo(:,<span style="color:#ae81ff">4</span>) <span style="color:#f92672">&lt;</span> <span style="color:#ae81ff">17</span>) <span style="color:#f92672">|</span> (CInfo(:,<span style="color:#ae81ff">4</span>) <span style="color:#f92672">&gt;</span> <span style="color:#ae81ff">20</span>)
 LGRSOIL = SOIL;
-i = 0;
-for i = (1:columns(LGRSOIL))
+i = <span style="color:#ae81ff">0</span>;
+<span style="color:#66d9ef">for</span> i = (<span style="color:#ae81ff">1</span>:columns(LGRSOIL))
     LGRSOIL(Mask,i) = nan;
 endfor
 
-riSetActiveCellProperty(LGRSOIL, &quot;KSlice&quot;);
-</code></pre>
-
-<h4 id="example-3">Example 3</h4>
-
-<pre><code class="language-matlab"># Keep the values in the first LGR only
+riSetActiveCellProperty(LGRSOIL, &#34;KSlice&#34;);
+</code></pre></div><h4 id="example-3">Example 3</h4>
+<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-matlab" data-lang="matlab"># Keep the values in the first LGR only
 
 CInfo = riGetActiveCellInfo();
-SOIL = riGetActiveCellProperty(&quot;SOIL&quot;);
+SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
 
-Mask = (CInfo(:,1) != 1);
+Mask = (CInfo(:,<span style="color:#ae81ff">1</span>) != <span style="color:#ae81ff">1</span>);
 
 LGRSOIL = SOIL;
-i = 0;
-for i = (1:columns(LGRSOIL))
+i = <span style="color:#ae81ff">0</span>;
+<span style="color:#66d9ef">for</span> i = (<span style="color:#ae81ff">1</span>:columns(LGRSOIL))
     LGRSOIL(Mask,i) = nan;
 endfor
 
-riSetActiveCellProperty(LGRSOIL, &quot;LGRSOIL&quot;);
-</code></pre>
-
-<h4 id="example-4-might-be-slow-on-big-models">Example 4 ( Might be slow on big models)</h4>
-
-<pre><code class="language-matlab"># Calculate the average SOIL value across K layers
+riSetActiveCellProperty(LGRSOIL, &#34;LGRSOIL&#34;);
+</code></pre></div><h4 id="example-4--might-be-slow-on-big-models">Example 4 ( Might be slow on big models)</h4>
+<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-matlab" data-lang="matlab"># Calculate the average SOIL value across K layers
 
 CInfo = riGetActiveCellInfo();
-SOIL = riGetActiveCellProperty(&quot;SOIL&quot;);
+SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
 
 SOIL_KAverage = SOIL;
 SOIL_KAverage(:) = nan;
 
-mini = min(CInfo(:,2))
-maxi = max(CInfo(:,2))
+mini = min(CInfo(:,<span style="color:#ae81ff">2</span>))
+maxi = max(CInfo(:,<span style="color:#ae81ff">2</span>))
 
-minj = min(CInfo(:,3))
-maxj = max(CInfo(:,3))
+minj = min(CInfo(:,<span style="color:#ae81ff">3</span>))
+maxj = max(CInfo(:,<span style="color:#ae81ff">3</span>))
 
-for i = mini:maxi
-  for j = minj:maxj 
-    Mask = (CInfo(:,1) == 0) &amp; (CInfo(:,2) == i) &amp; (CInfo(:,3) == j) ;
+<span style="color:#66d9ef">for</span> i = mini:maxi
+  <span style="color:#66d9ef">for</span> j = minj:maxj 
+    Mask = (CInfo(:,<span style="color:#ae81ff">1</span>) <span style="color:#f92672">==</span> <span style="color:#ae81ff">0</span>) <span style="color:#f92672">&amp;</span> (CInfo(:,<span style="color:#ae81ff">2</span>) <span style="color:#f92672">==</span> i) <span style="color:#f92672">&amp;</span> (CInfo(:,<span style="color:#ae81ff">3</span>) <span style="color:#f92672">==</span> j) ;
 
-    for ts = (1:columns(SOIL)) 
+    <span style="color:#66d9ef">for</span> ts = (<span style="color:#ae81ff">1</span>:columns(SOIL)) 
       SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));
     endfor
   endfor
 endfor
 
-riSetActiveCellProperty(SOIL_KAverage, &quot;SOIL_KAverage&quot;);
-</code></pre>
-
+riSetActiveCellProperty(SOIL_KAverage, &#34;SOIL_KAverage&#34;);
+</code></pre></div>
 
 <footer class=" footline" >
 	
@@ -2143,6 +2129,19 @@ riSetActiveCellProperty(SOIL_KAverage, &quot;SOIL_KAverage&quot;);
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2153,6 +2152,9 @@ riSetActiveCellProperty(SOIL_KAverage, &quot;SOIL_KAverage&quot;);
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3303,20 +3305,20 @@ riSetActiveCellProperty(SOIL_KAverage, &quot;SOIL_KAverage&quot;);
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/octaveinterfacereference/index.html b/scripting/octaveinterfacereference/index.html
index b1217c50fb..e14b21db00 100644
--- a/scripting/octaveinterfacereference/index.html
+++ b/scripting/octaveinterfacereference/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Octave Interface Reference :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,63 +1802,25 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#introduction">Introduction</a>
-<ul>
-<li><a href="#single-case-scripts">Single Case Scripts</a></li>
-<li><a href="#multi-case-scripts">Multi Case Scripts</a></li>
-<li><a href="#case-types">Case Types</a></li>
-<li><a href="#unresolved-issues">Unresolved Issues</a></li>
-</ul></li>
-<li><a href="#specification">Specification</a>
-<ul>
-<li><a href="#project-information">Project Information</a>
-<ul>
-<li><a href="#caseinfo-rigetcurrentcase">CaseInfo riGetCurrentCase()</a></li>
-<li><a href="#vector-caseinfo-rigetselectedcases">Vector[CaseInfo] riGetSelectedCases()</a></li>
-<li><a href="#vector-casegroupinfo-rigetcasegroups">Vector[CaseGroupInfo] riGetCaseGroups()</a></li>
-<li><a href="#vector-caseinfo-rigetcases-casegroupid">Vector[CaseInfo] riGetCases([CaseGroupId])</a></li>
-</ul></li>
-<li><a href="#retrieving-grid-metadata">Retrieving Grid Metadata</a>
-<ul>
-<li><a href="#matrix-numactivecells-9-rigetactivecellinfo-caseid-porositymodel-matrix-fracture">Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;] )</a></li>
-<li><a href="#matrix-numcoarsegroups-6-rigetcoarseninginfo-caseid">Matrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId])</a></li>
-<li><a href="#matrix-numgrids-3-rigetgriddimensions-caseid">Matrix[numGrids][3] riGetGridDimensions([CaseId])</a></li>
-<li><a href="#vector-timestepdate-rigettimestepdates-caseid">Vector[TimeStepDate] riGetTimeStepDates([CaseId])</a></li>
-<li><a href="#vector-decimalday-rigettimestepdays-caseid">Vector[DecimalDay] riGetTimeStepDays([CaseId])</a></li>
-</ul></li>
-<li><a href="#retrieving-property-data">Retrieving Property Data</a>
-<ul>
-<li><a href="#vector-propertyinfo-rigetpropertynames-caseid-porositymodel-matrix-fracture">Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-<li><a href="#matrix-numactivecells-numtimestepsrequested-rigetactivecellproperty-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-<li><a href="#matrix-numi-numj-numk-numtimestepsrequested-rigetgridproperty-caseid-gridindex-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-<li><a href="#risetactivecellproperty-matrix-numactivecells-numtimesteps-caseid-propertyname-timestepindices-porositymodel-matrix-fracture">riSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-<li><a href="#risetgridproperty-matrix-numi-numj-numk-numtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel-matrix-fracture">riSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-</ul></li>
-<li><a href="#cell-geometry-functions">Cell Geometry Functions</a>
-<ul>
-<li><a href="#matrix-numi-numj-numk-3-rigetcellcenters-caseid-gridindex">Matrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex)</a></li>
-<li><a href="#matrix-activecells-3-rigetactivecellcenters-caseid-porositymodel-matrix-fracture">Matrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-<li><a href="#matrix-numi-numj-numk-8-3-rigetcellcorners-caseid-gridindex">Matrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex)</a></li>
-<li><a href="#matrix-activecells-8-3-rigetactivecellcorners-caseid-porositymodel-matrix-fracture">Matrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</a></li>
-</ul></li>
-<li><a href="#well-data-functions">Well Data Functions</a>
-<ul>
-<li><a href="#vector-wellnames-rigetwellnames-caseid">Vector[WellNames] riGetWellNames([CaseId])</a></li>
-<li><a href="#vector-wellstatus-rigetwellstatus-caseid-wellname-requestedtimesteps">Vector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps])</a></li>
-<li><a href="#matrix-numselectedcells-5-rigetselectedcells-caseid">Matrix[numSelectedCells][5] riGetSelectedCells([CaseId])</a></li>
-<li><a href="#matrix-numselectedcells-numtimestepsrequested-rigetgridpropertyforselectedcells-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;] )</a></li>
-<li><a href="#vector-propertyinfo-rigetnncpropertynames-caseid">Vector[PropertyInfo] riGetNNCPropertyNames([CaseId])</a></li>
-<li><a href="#matrix-numnncconnections-2-rigetnncconnections-caseid">Matrix[numNNCConnections][2] riGetNNCConnections([CaseId])</a></li>
-<li><a href="#matrix-numconnections-numtimestepsrequested-rigetdynamicnncvalues-caseid-propertyname-requestedtimesteps">Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])</a></li>
-<li><a href="#vector-numconnections-rigetstaticnncvalues-caseid-propertyname">Vector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)</a></li>
-<li><a href="#risetnncproperty-matrix-numnncconnections-numtimesteps-caseid-propertyname-timestepindices">riSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#introduction">Introduction</a>
+      <ul>
+        <li><a href="#single-case-scripts">Single Case Scripts</a></li>
+        <li><a href="#multi-case-scripts">Multi Case Scripts</a></li>
+        <li><a href="#case-types">Case Types</a></li>
+        <li><a href="#unresolved-issues">Unresolved Issues</a></li>
+      </ul>
+    </li>
+    <li><a href="#specification">Specification</a>
+      <ul>
+        <li><a href="#project-information">Project Information</a></li>
+        <li><a href="#retrieving-grid-metadata">Retrieving Grid Metadata</a></li>
+        <li><a href="#retrieving-property-data">Retrieving Property Data</a></li>
+        <li><a href="#cell-geometry-functions">Cell Geometry Functions</a></li>
+        <li><a href="#well-data-functions">Well Data Functions</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1849,30 +1845,19 @@ if (!doNotTrack) {
 
 
 
-
-
 <h2 id="introduction">Introduction</h2>
-
 <p>To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the &ldquo;Current Case&rdquo;), or the script is designed to access the selection and traverse the cases by itself.</p>
 
-
-<div class="notices info" ><p><b>Note:</b> The Octave interface does not support Geomechanical cases and flow diagnostic results.</p>
+<div class="notices info" ><p><!-- raw HTML omitted -->Note:<!-- raw HTML omitted --> The Octave interface does not support Geomechanical cases and flow diagnostic results.</p>
 </div>
 
-
 <h3 id="single-case-scripts">Single Case Scripts</h3>
-
-<p>Single case scripts do not need to address cases explicitly, but works on what ResInsight considers being the &ldquo;Current Case&rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the &ldquo;Current Case&rdquo; from the script will then refer to the case currently being processed by ResInsight.
+<p>Single case scripts do not need to address cases explicitly, but works on what ResInsight considers being the &ldquo;Current Case&rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the &ldquo;Current Case&rdquo; from the script will then refer to the case currently being processed by ResInsight. 
 The Current Case can be accessed directly using <strong>riGetCurrentCase()</strong>, but the more direct way is to <em>omit the CaseId parameter</em> in the functions, the Current Case is then automatically used.</p>
-
 <h3 id="multi-case-scripts">Multi Case Scripts</h3>
-
 <p>Scripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.</p>
-
 <h3 id="case-types">Case Types</h3>
-
 <p>The case type (Labeled &ldquo;CaseType&rdquo; in the following specification) of a case is returned as a text string when retrieving lists of cases, and is one of the following:</p>
-
 <table>
 <thead>
 <tr>
@@ -1880,40 +1865,30 @@ The Current Case can be accessed directly using <strong>riGetCurrentCase()</stro
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>ResultCase</td>
 <td>A binary Eclipse case</td>
 </tr>
-
 <tr>
 <td>InputCase</td>
 <td>A case based on ASCII Eclipse input data</td>
 </tr>
-
 <tr>
 <td>StatisticsCase</td>
 <td>A statistics case based on many source cases in Grid Case Group</td>
 </tr>
-
 <tr>
 <td>SourceCase</td>
 <td>A binary Eclipse case in a Grid Case Group</td>
 </tr>
 </tbody>
 </table>
-
 <h3 id="unresolved-issues">Unresolved Issues</h3>
-
 <p>The issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.</p>
-
 <h2 id="specification">Specification</h2>
-
 <h3 id="project-information">Project Information</h3>
-
 <p>The case information is presented in an octave Structure called CaseInfo, and contains the following fields:</p>
-
 <pre><code>CaseInfo = {
   CaseId      = int    # A project-unique integer used to address this
                        # particular case 
@@ -1926,19 +1901,12 @@ The Current Case can be accessed directly using <strong>riGetCurrentCase()</stro
                        # Statistics-, and SourceCases
 }
 </code></pre>
-
 <h4 id="caseinfo-rigetcurrentcase">CaseInfo riGetCurrentCase()</h4>
-
 <p>This function returns a CaseInfo Structure for the Case considered being the &ldquo;Current Case&rdquo; by ResInsight. When ResInsight loops over a selection of cases and executes an Octave script for each of them, this function returns the CaseInfo for that particular Case.</p>
-
-<h4 id="vector-caseinfo-rigetselectedcases">Vector[CaseInfo] riGetSelectedCases()</h4>
-
+<h4 id="vectorcaseinfo-rigetselectedcases">Vector[CaseInfo] riGetSelectedCases()</h4>
 <p>This function returns a CaseInfo Structure for each of the cases selected in ResInsight at the time when the script launched.</p>
-
-<h4 id="vector-casegroupinfo-rigetcasegroups">Vector[CaseGroupInfo] riGetCaseGroups()</h4>
-
+<h4 id="vectorcasegroupinfo-rigetcasegroups">Vector[CaseGroupInfo] riGetCaseGroups()</h4>
 <p>This function returns a CaseGroupInfo Structure for each of the case groups in the current ResInsight project.</p>
-
 <pre><code>CaseGroupInfo = {
   CaseGroupId   = int    # A project-unique integer used to address
                          # this particular CaseGroup
@@ -1946,18 +1914,12 @@ The Current Case can be accessed directly using <strong>riGetCurrentCase()</stro
                          # in ResInsight
 }
 </code></pre>
-
-<h4 id="vector-caseinfo-rigetcases-casegroupid">Vector[CaseInfo] riGetCases([CaseGroupId])</h4>
-
-<p>This function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group.
+<h4 id="vectorcaseinfo-rigetcasescasegroupid">Vector[CaseInfo] riGetCases([CaseGroupId])</h4>
+<p>This function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group. 
 If a CaseGroupId is provided, only the cases in that Case Group will be returned.</p>
-
 <h3 id="retrieving-grid-metadata">Retrieving Grid Metadata</h3>
-
-<h4 id="matrix-numactivecells-9-rigetactivecellinfo-caseid-porositymodel-matrix-fracture">Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;] )</h4>
-
+<h4 id="matrixnumactivecells9-rigetactivecellinfocaseid-porositymodel--matrixfracture-">Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;] )</h4>
 <p>This function returns a two dimensional matrix containing grid and IJK information about each of the active cells in the requested case. The columns contain the following information:</p>
-
 <pre><code>[GridIdx, I, J, K, ParentGridIdx, PI, PJ, PK, CoarseBoxIdx]
   GridIdx       # The index of the grid the cell resides in.
                 # Main grid has index 0
@@ -1970,31 +1932,21 @@ If a CaseGroupId is provided, only the cases in that Case Group will be returned
                 # Coarsening box info can be retrieved using
                 # **riGetCoarseningInfo()**
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numcoarsegroups-6-rigetcoarseninginfo-caseid">Matrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId])</h4>
-
+<h4 id="matrixnumcoarsegroups6-rigetcoarseninginfocaseid">Matrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId])</h4>
 <p>This function returns all coarse box definitions used in the grid.
 The columns contain the following information:
 [I1, I2, J1, J2, K1, K2]: 1-based index addresses of the min and max corners of the coarsening box.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numgrids-3-rigetgriddimensions-caseid">Matrix[numGrids][3] riGetGridDimensions([CaseId])</h4>
-
+<h4 id="matrixnumgrids3-rigetgriddimensionscaseid">Matrix[numGrids][3] riGetGridDimensions([CaseId])</h4>
 <p>This function returns a two dimensional matrix: One row for each grid, starting with the main grid.</p>
-
 <p><em>NOTE</em>: This means that the &ldquo;normal&rdquo; GridIndices where 0 means Main Grid does not work directly with this matrix. You have to add 1.</p>
-
 <p>The columns contain the following information:
-[NI, NJ, NK]:  I, J, K dimensions of the grid.
+[NI, NJ, NK]:  I, J, K dimensions of the grid. 
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="vector-timestepdate-rigettimestepdates-caseid">Vector[TimeStepDate] riGetTimeStepDates([CaseId])</h4>
-
+<h4 id="vectortimestepdate-rigettimestepdatescaseid">Vector[TimeStepDate] riGetTimeStepDates([CaseId])</h4>
 <p>This function returns the date information for each of the time steps in the case as a Vector of Structures.
 The Structure is defined as:</p>
-
 <pre><code>TimeStepDate = {
   Year    = int # The year eg. 2013
   Month   = int # The month. Eg. 12
@@ -2004,21 +1956,14 @@ The Structure is defined as:</p>
   Second  = int # The second within the minute. Eg. 30
 }
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="vector-decimalday-rigettimestepdays-caseid">Vector[DecimalDay] riGetTimeStepDays([CaseId])</h4>
-
+<h4 id="vectordecimalday-rigettimestepdayscaseid">Vector[DecimalDay] riGetTimeStepDays([CaseId])</h4>
 <p>This function returns the time from the simulation start as decimal days for all the time steps as a Vector of doubles.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
 <h3 id="retrieving-property-data">Retrieving Property Data</h3>
-
-<h4 id="vector-propertyinfo-rigetpropertynames-caseid-porositymodel-matrix-fracture">Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
+<h4 id="vectorpropertyinfo-rigetpropertynamescaseid--porositymodel--matrixfracture">Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
 <p>This function returns the name and type of all the properties in the case as a Vector of Structures.
 The Structure is defined as:</p>
-
 <pre><code>PropertyInfo {
   PropName    = string # Name of the property as received from
                        # the analysis tool
@@ -2026,50 +1971,35 @@ The Structure is defined as:</p>
                        # &quot;DynamicNative&quot;, &quot;Input&quot;, &quot;Generated&quot;
 }
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numactivecells-numtimestepsrequested-rigetactivecellproperty-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
+<h4 id="matrixnumactivecellsnumtimestepsrequested-rigetactivecellpropertycaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture">Matrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
 <p>This function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId.
-If the case contains coarse-cells, the results are expanded onto the active cells.
-If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
+If the case contains coarse-cells, the results are expanded onto the active cells. 
+If the CaseId is not defined, ResInsight&rsquo;s Current Case is used. 
 The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.</p>
-
-<h4 id="matrix-numi-numj-numk-numtimestepsrequested-rigetgridproperty-caseid-gridindex-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
+<h4 id="matrixnuminumjnumknumtimestepsrequested-rigetgridpropertycaseid-gridindex--propertyname-requestedtimesteps-porositymodel--matrixfracture">Matrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
 <p>This function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step.
-Grids are indexed from 0 (main grid) to max number of LGR&rsquo;s
+Grids are indexed from 0 (main grid) to max number of LGR&rsquo;s 
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
 The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.
 Writing Back to ResInsight</p>
-
-<h4 id="risetactivecellproperty-matrix-numactivecells-numtimesteps-caseid-propertyname-timestepindices-porositymodel-matrix-fracture">riSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
-<p>Interprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a &ldquo;Generated&rdquo; property with the name &ldquo;PropertyName&rdquo;.
-The &ldquo;TimeStepIndices&rdquo; argument is used to &ldquo;label&rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.<br />
+<h4 id="risetactivecellproperty-matrixnumactivecellsnumtimesteps-caseid-propertyname-timestepindices-porositymodel--matrixfracture">riSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<p>Interprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a &ldquo;Generated&rdquo; property with the name &ldquo;PropertyName&rdquo;. 
+The &ldquo;TimeStepIndices&rdquo; argument is used to &ldquo;label&rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.<br>
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="risetgridproperty-matrix-numi-numj-numk-numtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel-matrix-fracture">riSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
-<p>Interprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a &ldquo;Generated&rdquo; property with the name &ldquo;PropertyName&rdquo;.
+<h4 id="risetgridproperty-matrixnuminumjnumknumtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel--matrixfracture">riSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<p>Interprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a &ldquo;Generated&rdquo; property with the name &ldquo;PropertyName&rdquo;. 
 The &ldquo;TimeStepIndices&rdquo; argument is used to &ldquo;label&rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
 <h3 id="cell-geometry-functions">Cell Geometry Functions</h3>
-
-<h4 id="matrix-numi-numj-numk-3-rigetcellcenters-caseid-gridindex">Matrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex)</h4>
-
+<h4 id="matrixnuminumjnumk3-rigetcellcenterscaseid-gridindex">Matrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex)</h4>
 <p>This function returns the UTM coordinates (X, Y, Z) of the center point of all the cells in the grid.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-activecells-3-rigetactivecellcenters-caseid-porositymodel-matrix-fracture">Matrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
+<h4 id="matrixactivecells3-rigetactivecellcenterscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
 <p>This function returns the UTM coordinates (X, Y, Z) of the center point of each of the active cells.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
 Cell Corner Index layout
 The corner indices follow the ECLIPSE standard:</p>
-
 <pre><code>      6-------------7             |k     
      /|            /|             | /j   
     / |           / |             |/     
@@ -2082,26 +2012,18 @@ The corner indices follow the ECLIPSE standard:</p>
   |/            |/
   0-------------1
 </code></pre>
-
-<h4 id="matrix-numi-numj-numk-8-3-rigetcellcorners-caseid-gridindex">Matrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex)</h4>
-
+<h4 id="matrixnuminumjnumk83-rigetcellcornerscaseid-gridindex">Matrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex)</h4>
 <p>This function returns the UTM coordinates(X, Y, Z) of the 8 corners of all the cells in the grid.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-activecells-8-3-rigetactivecellcorners-caseid-porositymodel-matrix-fracture">Matrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;])</h4>
-
+<h4 id="matrixactivecells83-rigetactivecellcornerscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
 <p>This function returns the UTM coordinates (X, Y, Z) of the 8 corners of each of the active cells.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
 <h3 id="well-data-functions">Well Data Functions</h3>
-
-<h4 id="vector-wellnames-rigetwellnames-caseid">Vector[WellNames] riGetWellNames([CaseId])</h4>
-
+<h4 id="vectorwellnames-rigetwellnamescaseid">Vector[WellNames] riGetWellNames([CaseId])</h4>
 <p>This function returns the names of all the wells in the case as a Vector of strings.
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
 Vector[WellCellInfo] riGetWellCells([CaseId], WellName, TimeStep)
 This function returns the cells defined in the specified well for the time step requested as a vector of Structures. The Structure is defined as:</p>
-
 <pre><code>WellCellInfo {
   I, J, K     = int # Index to the cell in the grid
   GridIndex   = int # the index of the grid. Main grid has index 0.
@@ -2111,13 +2033,9 @@ This function returns the cells defined in the specified well for the time step
   SegmentId   = int # Branch segment id of the branch intersecting the cell
 }
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="vector-wellstatus-rigetwellstatus-caseid-wellname-requestedtimesteps">Vector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps])</h4>
-
+<h4 id="vectorwellstatus-rigetwellstatus-caseid-wellname-requestedtimesteps">Vector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps])</h4>
 <p>This function returns the status information for a specified well for each requested time step as a vector of Structures. The Structure is defined as:</p>
-
 <pre><code>WellStatus {
   WellType    = string # &quot;Producer&quot;, &quot;OilInjector&quot;,
                        # &quot;WaterInjector&quot;, &quot;GasInjector&quot;, &quot;NotDefined&quot;
@@ -2125,36 +2043,24 @@ This function returns the cells defined in the specified well for the time step
                        # or open respectively
 }
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numselectedcells-5-rigetselectedcells-caseid">Matrix[numSelectedCells][5] riGetSelectedCells([CaseId])</h4>
-
+<h4 id="matrixnumselectedcells5-rigetselectedcellscaseid">Matrix[numSelectedCells][5] riGetSelectedCells([CaseId])</h4>
 <p>This function returns a two dimensional matrix containing the cell info for each selected cell in the case with <code>CaseId</code>.
 The columns contain the following information:</p>
-
 <pre><code>[CaseId, GridIdx, I, J, K]
   CaseId  # The ID of the case the cell resides in.
   GridIdx # The index of the grid the cell resides in.
           # Main grid has index 0
   I, J, K # 1-based index of the cell in the grid.
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numselectedcells-numtimestepsrequested-rigetgridpropertyforselectedcells-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture">Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;Fracture&rdquo;] )</h4>
-
+<h4 id="matrixnumselectedcellsnumtimestepsrequested-rigetgridpropertyforselectedcellscaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture-">Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;] )</h4>
 <p>This function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.</p>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
 The RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.</p>
-
-<h4 id="vector-propertyinfo-rigetnncpropertynames-caseid">Vector[PropertyInfo] riGetNNCPropertyNames([CaseId])</h4>
-
+<h4 id="vectorpropertyinfo-rigetnncpropertynamescaseid">Vector[PropertyInfo] riGetNNCPropertyNames([CaseId])</h4>
 <p>This function returns the name and type of all NNC properties in the case as a vector of structures.</p>
-
 <p>The structure is defined as:</p>
-
 <pre><code>PropertyInfo {
   PropName    = string # Name of the property as received from
                        # the analysis tool
@@ -2162,41 +2068,28 @@ The RequestedTimeSteps must contain a list of 1-based indices to the requested t
                        # &quot;DynamicNative&quot;, &quot;Generated&quot;
 }
 </code></pre>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="matrix-numnncconnections-2-rigetnncconnections-caseid">Matrix[numNNCConnections][2] riGetNNCConnections([CaseId])</h4>
-
+<h4 id="matrixnumnncconnections2-rigetnncconnectionscaseid">Matrix[numNNCConnections][2] riGetNNCConnections([CaseId])</h4>
 <p>This function returns a two dimensional matrix containing grid and IJK information about each NNC connection.
 Each row contains a from and to cell for the connection.
 The cells are specified in a structure defined as:</p>
-
 <pre><code>CellInfo = {
   GridIndex = int # Index of the grid the cell resides in.
                   # Main grid has index 0.
   I, J, K   = int # 1-based index address of the cell in the grid.
 }
 </code></pre>
-
-<h4 id="matrix-numconnections-numtimestepsrequested-rigetdynamicnncvalues-caseid-propertyname-requestedtimesteps">Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])</h4>
-
+<h4 id="matrixnumconnectionsnumtimestepsrequested-rigetdynamicnncvaluescaseid-propertyname-requestedtimesteps">Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])</h4>
 <p>This function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from <code>riGetNNCConnections</code>.</p>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.
 The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.</p>
-
-<h4 id="vector-numconnections-rigetstaticnncvalues-caseid-propertyname">Vector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)</h4>
-
+<h4 id="vectornumconnections-rigetstaticnncvaluescaseid-propertyname">Vector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)</h4>
 <p>This function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from <code>riGetNNCConnections</code>.</p>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-
-<h4 id="risetnncproperty-matrix-numnncconnections-numtimesteps-caseid-propertyname-timestepindices">riSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])</h4>
-
+<h4 id="risetnncpropertymatrixnumnncconnectionsnumtimesteps-caseid-propertyname-timestepindices">riSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])</h4>
 <p>Interprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a &ldquo;Generated&rdquo; property with the name &ldquo;PropertyName&rdquo;.
 The &ldquo;TimeStepIndices&rdquo; argument is used to &ldquo;label&rdquo; all the steps present in the supplied data matrix and must thus be complete.
 The time step data will then be put into ResInsight at the time steps requested.</p>
-
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
 
 
@@ -2373,6 +2266,19 @@ The time step data will then be put into ResInsight at the time steps requested.
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2383,6 +2289,9 @@ The time step data will then be put into ResInsight at the time steps requested.
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3533,20 +3442,20 @@ The time step data will then be put into ResInsight at the time steps requested.
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/pythonconfiguration/index.html b/scripting/pythonconfiguration/index.html
index 85f70e5112..dd88126c10 100644
--- a/scripting/pythonconfiguration/index.html
+++ b/scripting/pythonconfiguration/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Python Configuration :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,7 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1791,21 +1825,14 @@ if (!doNotTrack) {
 
 
 
-<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt="" /></p>
-
+<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt=""></p>
 <p>ResInsight has a <a href="https://www.grpc.io/">gRPC Remote Procedure Call</a> interface with a Python Client interface. This interface allows you to interact with a running ResInsight instance from a Python script. The Python client package is compatible with <strong>Python 3</strong>.</p>
-
 <p>The Python client package is available for install via the Python PIP package system with <code>pip install rips</code> as admin user, or <code>pip install --user rips</code> as a regular user.</p>
-
 <p>On some systems the <code>pip</code> command may have to be replaced by <code>python -m pip</code>.</p>
-
 <p>In order for gRPC to be available, ResInsight needs to be built with the <code>RESINSIGHT_ENABLE_GRPC</code> option set. A valid gRPC build will show a message in the About dialog confirming gRPC is available:</p>
-
-<p><img src="/images/scripting/AboutGrpc.png" alt="image" /></p>
-
+<p><img src="/images/scripting/AboutGrpc.png" alt="image"></p>
 <p>Furthermore, gRPC needs to be enabled in the Scripting tab of the Preference dialog:</p>
-
-<p><img src="/images/scripting/PrefGrpc.png" alt="image" /></p>
+<p><img src="/images/scripting/PrefGrpc.png" alt="image"></p>
 
 
 <footer class=" footline" >
@@ -1981,6 +2008,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1991,6 +2031,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3141,20 +3184,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/pythonexamples/index.html b/scripting/pythonexamples/index.html
index df099f7e20..a9e7ee266a 100644
--- a/scripting/pythonexamples/index.html
+++ b/scripting/pythonexamples/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Python Examples :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1767,34 +1801,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-<nav id="TableOfContents">
-<ul>
-<li><a href="#allcases">AllCases</a></li>
-<li><a href="#casegridgroup">CaseGridGroup</a></li>
-<li><a href="#caseinfostreamingexample">CaseInfoStreamingExample</a></li>
-<li><a href="#commandexample">CommandExample</a></li>
-<li><a href="#create-wbs-plot">Create WBS Plot</a></li>
-<li><a href="#errorhandling">ErrorHandling</a></li>
-<li><a href="#exportcontourmaps">ExportContourMaps</a></li>
-<li><a href="#exportplots">ExportPlots</a></li>
-<li><a href="#exportsnapshots">ExportSnapshots</a></li>
-<li><a href="#gridinformation">GridInformation</a></li>
-<li><a href="#import-well-paths">Import Well Paths</a></li>
-<li><a href="#inputproptestasync">InputPropTestAsync</a></li>
-<li><a href="#inputproptestsync">InputPropTestSync</a></li>
-<li><a href="#instanceexample">InstanceExample</a></li>
-<li><a href="#launchwithcommandlineoptions">LaunchWithCommandLineOptions</a></li>
-<li><a href="#selectedcases">SelectedCases</a></li>
-<li><a href="#setcellresult">SetCellResult</a></li>
-<li><a href="#setflowdiagnosticsresult">SetFlowDiagnosticsResult</a></li>
-<li><a href="#setgridproperties">SetGridProperties</a></li>
-<li><a href="#soilaverageasync">SoilAverageAsync</a></li>
-<li><a href="#soilaveragesync">SoilAverageSync</a></li>
-<li><a href="#soilporvasync">SoilPorvAsync</a></li>
-<li><a href="#soilporvsync">SoilPorvSync</a></li>
-<li><a href="#viewexample">ViewExample</a></li>
-</ul>
-</nav>
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1818,14 +1825,9 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt="" /></p>
-
+<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt=""></p>
 <p>This pages is created based on the content in the <strong>PythonExamples</strong> folder located inside the <strong>rips</strong> module, made available online for convenience.</p>
-
 <h1 id="allcases">AllCases</h1>
-
 <pre><code>###################################################################################
 # This example will connect to ResInsight, retrieve a list of cases and print info
 # 
@@ -1854,10 +1856,7 @@ if resinsight is not None:
         
     
 
-</code></pre>
-
-<h1 id="casegridgroup">CaseGridGroup</h1>
-
+</code></pre><h1 id="casegridgroup">CaseGridGroup</h1>
 <pre><code>import os
 import rips
 
@@ -1887,10 +1886,7 @@ cell_result = view.set_cell_result()
 cell_result.set_value(&quot;ResultVariable&quot;, &quot;PRESSURE_DEV&quot;)
 cell_result.update()
         
-</code></pre>
-
-<h1 id="caseinfostreamingexample">CaseInfoStreamingExample</h1>
-
+</code></pre><h1 id="caseinfostreamingexample">CaseInfoStreamingExample</h1>
 <pre><code>###############################################################################
 # This example will get the cell info for the active cells for the first case
 ###############################################################################
@@ -1918,10 +1914,7 @@ assert(cell_counts.active_cell_count == len(active_cell_infos))
 # Print information for the first active cell
 print(&quot;First active cell: &quot;)
 print(active_cell_infos[0])
-</code></pre>
-
-<h1 id="commandexample">CommandExample</h1>
-
+</code></pre><h1 id="commandexample">CommandExample</h1>
 <pre><code>###############################################################################
 # This example will show setting time step, window size and export snapshots and properties
 ###############################################################################
@@ -1979,10 +1972,7 @@ with tempfile.TemporaryDirectory(prefix=&quot;rips&quot;) as tmpdirname:
 
     assert(os.path.exists(full_path))
 
-</code></pre>
-
-<h1 id="create-wbs-plot">Create WBS Plot</h1>
-
+</code></pre><h1 id="create-wbs-plot">Create WBS Plot</h1>
 <pre><code>import os
 # Load ResInsight Processing Server Client Library
 import rips
@@ -2013,10 +2003,7 @@ for case in cases:
         for well_path in well_paths:
             wbsplot = case.create_well_bore_stability_plot(well_path=well_path, time_step=0)
             wbsplot.export_snapshot(export_folder=dirname)
-</code></pre>
-
-<h1 id="errorhandling">ErrorHandling</h1>
-
+</code></pre><h1 id="errorhandling">ErrorHandling</h1>
 <pre><code>###################################################################
 # This example demonstrates the use of ResInsight exceptions 
 # for proper error handling
@@ -2093,10 +2080,7 @@ if case is not None:
 
 
 
-</code></pre>
-
-<h1 id="exportcontourmaps">ExportContourMaps</h1>
-
+</code></pre><h1 id="exportcontourmaps">ExportContourMaps</h1>
 <pre><code># Load ResInsight Processing Server Client Library
 import rips
 import tempfile
@@ -2129,10 +2113,7 @@ for case in cases:
         filepath = tmpdir / filename
         print(&quot;Exporting to:&quot;, filepath)
         contour_map.export_to_text(str(filepath))
-</code></pre>
-
-<h1 id="exportplots">ExportPlots</h1>
-
+</code></pre><h1 id="exportplots">ExportPlots</h1>
 <pre><code># Import the tempfile module
 import tempfile
 # Load ResInsight Processing Server Client Library
@@ -2148,13 +2129,10 @@ export_folder = tempfile.mkdtemp()
 print(&quot;Exporting to: &quot; + export_folder)
 
 for plot in plots:
-    plot.export_snapshot(export_folder=export_folder)
-    plot.export_data_as_las(export_folder=export_folder)
-    plot.export_data_as_ascii(export_folder=export_folder)
-</code></pre>
-
-<h1 id="exportsnapshots">ExportSnapshots</h1>
-
+	plot.export_snapshot(export_folder=export_folder)
+	plot.export_data_as_las(export_folder=export_folder)
+	plot.export_data_as_ascii(export_folder=export_folder)
+</code></pre><h1 id="exportsnapshots">ExportSnapshots</h1>
 <pre><code>############################################################################
 # This script will export snapshots for two properties in every loaded case
 # And put them in a snapshots folder in the same folder as the case grid
@@ -2198,10 +2176,7 @@ for case in cases:
         for time_step in range(0, len(time_steps), 10):
             view.set_time_step(time_step = time_step)
             view.export_snapshot()
-</code></pre>
-
-<h1 id="gridinformation">GridInformation</h1>
-
+</code></pre><h1 id="gridinformation">GridInformation</h1>
 <pre><code>######################################################################################
 # This example prints information about the grids of all cases in the current project
 ######################################################################################
@@ -2221,10 +2196,7 @@ for case in cases:
 
 
 
-</code></pre>
-
-<h1 id="import-well-paths">Import Well Paths</h1>
-
+</code></pre><h1 id="import-well-paths">Import Well Paths</h1>
 <pre><code># Load ResInsight Processing Server Client Library
 import rips
 # Connect to ResInsight instance
@@ -2257,10 +2229,7 @@ if resInsight.project.has_warnings():
 
 for well_path_name in well_path_names:
     print(&quot;Imported well log file for: &quot; + well_path_name)
-</code></pre>
-
-<h1 id="inputproptestasync">InputPropTestAsync</h1>
-
+</code></pre><h1 id="inputproptestasync">InputPropTestAsync</h1>
 <pre><code>########################################################################################
 # This example generates a derived property in an asynchronous manner
 # Meaning it does not wait for all the data for each stage to be read before proceeding
@@ -2299,10 +2268,7 @@ end = time.time()
 print(&quot;Time elapsed: &quot;, end - start)
 print(&quot;Transferred all results back&quot;)
 view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')
-</code></pre>
-
-<h1 id="inputproptestsync">InputPropTestSync</h1>
-
+</code></pre><h1 id="inputproptestsync">InputPropTestSync</h1>
 <pre><code>########################################################################################
 # This example generates a derived property in an synchronous manner
 # Meaning it completes reading each result before calculating the derived result
@@ -2338,10 +2304,7 @@ print(&quot;Time elapsed: &quot;, end - start)
 print(&quot;Transferred all results back&quot;)
 
 view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')
-</code></pre>
-
-<h1 id="instanceexample">InstanceExample</h1>
-
+</code></pre><h1 id="instanceexample">InstanceExample</h1>
 <pre><code>#######################################
 # This example connects to ResInsight
 #######################################
@@ -2352,11 +2315,8 @@ resinsight  = rips.Instance.find()
 if resinsight is None:
     print('ERROR: could not find ResInsight')
 else:
-    print('Successfully connected to ResInsight')
-</code></pre>
-
-<h1 id="launchwithcommandlineoptions">LaunchWithCommandLineOptions</h1>
-
+	print('Successfully connected to ResInsight')
+</code></pre><h1 id="launchwithcommandlineoptions">LaunchWithCommandLineOptions</h1>
 <pre><code># Load ResInsight Processing Server Client Library
 import rips
 # Launch ResInsight with last project file and a Window size of 600x1000 pixels
@@ -2368,10 +2328,7 @@ print (&quot;Got &quot; + str(len(cases)) + &quot; cases: &quot;)
 for case in cases:
     print(&quot;Case name: &quot; + case.name)
     print(&quot;Case grid path: &quot; + case.grid_path())
-</code></pre>
-
-<h1 id="selectedcases">SelectedCases</h1>
-
+</code></pre><h1 id="selectedcases">SelectedCases</h1>
 <pre><code>############################################################################
 # This example returns the currently selected cases in ResInsight
 # Because running this script in the GUI takes away the selection
@@ -2392,10 +2349,7 @@ if resinsight is not None:
             print(property)
 
 
-</code></pre>
-
-<h1 id="setcellresult">SetCellResult</h1>
-
+</code></pre><h1 id="setcellresult">SetCellResult</h1>
 <pre><code>######################################################################
 # This script applies a cell result to the first view in the project
 ######################################################################
@@ -2405,10 +2359,7 @@ resinsight  = rips.Instance.find()
 
 view = resinsight.project.views()[0]
 view.apply_cell_result(result_type='STATIC_NATIVE', result_variable='DX')
-</code></pre>
-
-<h1 id="setflowdiagnosticsresult">SetFlowDiagnosticsResult</h1>
-
+</code></pre><h1 id="setflowdiagnosticsresult">SetFlowDiagnosticsResult</h1>
 <pre><code>######################################################################
 # This script applies a flow diagnostics cell result to the first view in the project
 ######################################################################
@@ -2427,10 +2378,7 @@ view.apply_flow_diagnostics_cell_result(result_variable='Fraction',
                                     selection_mode='FLOW_TR_BY_SELECTION',
                                     injectors = ['C-1H', 'C-2H', 'F-2H'],
                                     producers = ['B-1AH', 'B-3H', 'D-1H'])
-</code></pre>
-
-<h1 id="setgridproperties">SetGridProperties</h1>
-
+</code></pre><h1 id="setgridproperties">SetGridProperties</h1>
 <pre><code>######################################################################
 # This script sets values for SOIL for all grid cells in the first case in the project
 ######################################################################
@@ -2448,10 +2396,7 @@ for i in range(0, total_cell_count):
 print(&quot;Applying values to full grid&quot;)
 case.set_grid_property(values, 'DYNAMIC_NATIVE', 'SOIL', 0)
 
-</code></pre>
-
-<h1 id="soilaverageasync">SoilAverageAsync</h1>
-
+</code></pre><h1 id="soilaverageasync">SoilAverageAsync</h1>
 <pre><code>###########################################################################################
 # This example will asynchronously calculate the average value for SOIL for all time steps
 ###########################################################################################
@@ -2474,25 +2419,22 @@ averages = []
 for i in range(0, len(timeSteps)):
     # Get the results from time step i asynchronously
     # It actually returns a generator object almost immediately
-    result_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)
-    mysum = 0.0
-    count = 0
+	result_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)
+	mysum = 0.0
+	count = 0
     # Loop through and append the average. each time we loop resultChunks
     # We will trigger a read of the input data, meaning the script will start
     # Calculating averages before the whole resultValue for this time step has been received
-    for chunk in result_chunks:
-        mysum += sum(chunk.values)
-        count += len(chunk.values)
+	for chunk in result_chunks:
+		mysum += sum(chunk.values)
+		count += len(chunk.values)
 
-    averages.append(mysum/count)
+	averages.append(mysum/count)
 
 end = time.time()
 print(&quot;Time elapsed: &quot;, end - start)
 print(averages)
-</code></pre>
-
-<h1 id="soilaveragesync">SoilAverageSync</h1>
-
+</code></pre><h1 id="soilaveragesync">SoilAverageSync</h1>
 <pre><code>###########################################################################################
 # This example will synchronously calculate the average value for SOIL for all time steps
 ###########################################################################################
@@ -2513,17 +2455,14 @@ time_steps      = case.time_steps()
 averages = []
 for i in range(0, len(time_steps)):
     # Get a list of all the results for time step i
-    results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)
-    mysum = sum(results)
-    averages.append(mysum/len(results))
+	results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)
+	mysum = sum(results)
+	averages.append(mysum/len(results))
 
 end = time.time()
 print(&quot;Time elapsed: &quot;, end - start)
 print(averages)
-</code></pre>
-
-<h1 id="soilporvasync">SoilPorvAsync</h1>
-
+</code></pre><h1 id="soilporvasync">SoilPorvAsync</h1>
 <pre><code>##############################################################################
 # This example will create a derived result for each time step asynchronously
 ##############################################################################
@@ -2571,10 +2510,7 @@ print(&quot;Time elapsed: &quot;, end - start)
 print(&quot;Transferred all results back&quot;)
 
 view = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVAsync')
-</code></pre>
-
-<h1 id="soilporvsync">SoilPorvSync</h1>
-
+</code></pre><h1 id="soilporvsync">SoilPorvSync</h1>
 <pre><code>##############################################################################
 # This example will create a derived result for each time step synchronously
 ##############################################################################
@@ -2608,10 +2544,7 @@ print(&quot;Time elapsed: &quot;, end - start)
 print(&quot;Transferred all results back&quot;)
 
 view = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVSync')
-</code></pre>
-
-<h1 id="viewexample">ViewExample</h1>
-
+</code></pre><h1 id="viewexample">ViewExample</h1>
 <pre><code>#############################################################
 # This example will alter the views of all cases
 # By setting the background color and toggle the grid box
@@ -2641,7 +2574,6 @@ if resinsight is not None:
         new_view.update()
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -2815,6 +2747,19 @@ if resinsight is not None:
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2825,6 +2770,9 @@ if resinsight is not None:
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3975,20 +3923,20 @@ if resinsight is not None:
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/pythonrips/index.html b/scripting/pythonrips/index.html
index e9996301f8..2d3481c281 100644
--- a/scripting/pythonrips/index.html
+++ b/scripting/pythonrips/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Python API - rips :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,217 +1802,68 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li><a href="#instance-module">Instance Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-instance-instance-port-50051-launched-false">class rips.instance.Instance(port=50051, launched=False)</a></li>
-<li><a href="#launched">launched()</a></li>
-<li><a href="#commands">commands()</a></li>
-<li><a href="#project">project()</a></li>
-<li><a href="#client-version-string">client_version_string()</a></li>
-<li><a href="#exit">exit()</a></li>
-<li><a href="#static-find-start-port-50051-end-port-50071">static find(start_port=50051, end_port=50071)</a></li>
-<li><a href="#is-console">is_console()</a></li>
-<li><a href="#is-gui">is_gui()</a></li>
-<li><a href="#static-launch-resinsight-executable-console-false-launch-port-1-command-line-parameters-none">static launch(resinsight_executable=&ldquo;, console=False, launch_port=-1, command_line_parameters=None)</a></li>
-<li><a href="#major-version">major_version()</a></li>
-<li><a href="#minor-version">minor_version()</a></li>
-<li><a href="#patch-version">patch_version()</a></li>
-<li><a href="#set-export-folder-export-type-path-create-folder-false">set_export_folder(export_type, path, create_folder=False)</a>
-<ul>
-<li><a href="#enum-export-type">Enum export_type</a></li>
-</ul></li>
-<li><a href="#set-main-window-size-width-height">set_main_window_size(width, height)</a></li>
-<li><a href="#set-plot-window-size-width-height">set_plot_window_size(width, height)</a></li>
-<li><a href="#set-start-dir-path">set_start_dir(path)</a></li>
-<li><a href="#version-string">version_string()</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#example">Example</a></li>
-</ul></li>
-<li><a href="#case-module">Case Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-case-case-channel-case-id-project">class rips.case.Case(channel, case_id, project)</a></li>
-<li><a href="#id">id()</a></li>
-<li><a href="#name">name()</a></li>
-<li><a href="#group-id">group_id()</a></li>
-<li><a href="#chunksize">chunkSize()</a></li>
-<li><a href="#active-cell-property-property-type-property-name-time-step-porosity-model-matrix-model">active_cell_property(property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#active-cell-property-async-property-type-property-name-time-step-porosity-model-matrix-model">active_cell_property_async(property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#available-properties-property-type-porosity-model-matrix-model">available_properties(property_type, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#cell-count-porosity-model-matrix-model">cell_count(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#cell-info-for-active-cells-porosity-model-matrix-model">cell_info_for_active_cells(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-</ul></li>
-<li><a href="#cellinfo-class-description">CellInfo class description</a></li>
-<li><a href="#vec3i-class-description">Vec3i class description</a>
-<ul>
-<li><a href="#cell-info-for-active-cells-async-porosity-model-matrix-model">cell_info_for_active_cells_async(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#contour-maps-map-type-contourmaptype-eclipse-1">contour_maps(map_type=<ContourMapType.ECLIPSE: 1>)</a></li>
-<li><a href="#create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</a></li>
-<li><a href="#create-lgr-for-completion-time-step-well-path-names-refinement-i-refinement-j-refinement-k-split-type">create_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type)</a>
-<ul>
-<li><a href="#enum-split-type">Enum split_type</a></li>
-</ul></li>
-<li><a href="#create-view">create_view()</a></li>
-<li><a href="#create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action-1">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</a></li>
-<li><a href="#create-saturation-pressure-plots">create_saturation_pressure_plots()</a></li>
-<li><a href="#create-view-1">create_view()</a></li>
-<li><a href="#create-well-bore-stability-plot-well-path-time-step">create_well_bore_stability_plot(well_path, time_step)</a></li>
-<li><a href="#days-since-start">days_since_start()</a></li>
-<li><a href="#export-flow-characteristics-time-steps-injectors-producers-file-name-minimum-communication-0-0-aquifer-cell-threshold-0-1">export_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1)</a></li>
-<li><a href="#export-msw-well-path">export_msw(well_path)</a></li>
-<li><a href="#export-property-time-step-property-name-eclipse-keyword-class-property-undefined-value-0-0-export-file-class-property">export_property(time_step, property_name, eclipse_keyword=<class 'property'>, undefined_value=0.0, export_file=<class 'property'>)</a>
-<ul>
-<li><a href="#enum-file-split">Enum file_split</a></li>
-</ul></li>
-<li><a href="#grid-index">grid(index)</a></li>
-<li><a href="#export-snapshots-of-all-views-prefix-export-folder">export_snapshots_of_all_views(prefix=&ldquo;, export_folder=&ldquo;)</a></li>
-<li><a href="#export-well-path-completions-time-step-well-path-names-file-split-compdat-export-transmissibilities-include-perforations-true-include-fishbones-true-fishbones-exclude-main-bore-true-combination-mode-individually">export_well_path_completions(time_step, well_path_names, file_split, compdat_export=&lsquo;TRANSMISSIBILITIES&rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode=&lsquo;INDIVIDUALLY&rsquo;)</a>
-<ul>
-<li><a href="#enum-file-split-1">Enum file_split</a></li>
-<li><a href="#enum-compdat-export">Enum compdat_export</a></li>
-<li><a href="#enum-combination-mode">Enum combination_mode</a></li>
-</ul></li>
-<li><a href="#grid-index-1">grid(index)</a></li>
-<li><a href="#grid-path">grid_path()</a></li>
-<li><a href="#grid-property-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">grid_property(property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#grid-property-async-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">grid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#grids">grids()</a></li>
-<li><a href="#import-formation-names-formation-files-none">import_formation_names(formation_files=None)</a></li>
-<li><a href="#replace-new-grid-file">replace(new_grid_file)</a></li>
-<li><a href="#set-active-cell-property-values-property-type-property-name-time-step-porosity-model-matrix-model">set_active_cell_property(values, property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#set-active-cell-property-async-values-iterator-property-type-property-name-time-step-porosity-model-matrix-model">set_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#set-grid-property-values-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">set_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</a></li>
-<li><a href="#time-steps">time_steps()</a></li>
-<li><a href="#view-view-id">view(view_id)</a></li>
-<li><a href="#views">views()</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#example-1">Example</a></li>
-</ul></li>
-<li><a href="#contour-map-module">Contour Map Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-contour-map-contourmap-pdm-object-project-map-type">class rips.contour_map.ContourMap(pdm_object, project, map_type)</a></li>
-<li><a href="#view-id">view_id()</a></li>
-<li><a href="#export-to-text-export-file-name-export-local-coordinates-false-undefined-value-label-nan-exclude-undefined-values-false">export_to_text(export_file_name=&ldquo;, export_local_coordinates=False, undefined_value_label=&lsquo;NaN&rsquo;, exclude_undefined_values=False)</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-<li><a href="#grid-module">Grid Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-grid-grid-index-case-channel">class rips.grid.Grid(index, case, channel)</a></li>
-<li><a href="#dimensions">dimensions()</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#example-2">Example</a></li>
-</ul></li>
-<li><a href="#gridcasegroup-module">GridCaseGroup Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-gridcasegroup-gridcasegroup-pdm-object">class rips.gridcasegroup.GridCaseGroup(pdm_object)</a></li>
-<li><a href="#group-id-1">group_id()</a></li>
-<li><a href="#compute-statistics-case-ids-none">compute_statistics(case_ids=None)</a></li>
-<li><a href="#create-statistics-case">create_statistics_case()</a></li>
-<li><a href="#statistics-cases">statistics_cases()</a></li>
-<li><a href="#view-view-id-1">view(view_id)</a></li>
-<li><a href="#views-1">views()</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-<li><a href="#project-module">Project Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-project-project-channel">class rips.project.Project(channel)</a></li>
-<li><a href="#case-case-id">case(case_id)</a></li>
-<li><a href="#compute-statistics-case-ids-none-1">compute_statistics(case_ids=None)</a></li>
-<li><a href="#create-statistics-case-1">create_statistics_case()</a></li>
-<li><a href="#statistics-cases-1">statistics_cases()</a></li>
-<li><a href="#contour-maps-map-type-contourmaptype-eclipse-1-1">contour_maps(map_type=<ContourMapType.ECLIPSE: 1>)</a></li>
-<li><a href="#create-grid-case-group-case-paths">create_grid_case_group(case_paths)</a></li>
-<li><a href="#export-multi-case-snapshots-grid-list-file">export_multi_case_snapshots(grid_list_file)</a></li>
-<li><a href="#export-snapshots-snapshot-type-all-prefix">export_snapshots(snapshot_type=&lsquo;ALL&rsquo;, prefix=&ldquo;)</a></li>
-<li><a href="#export-well-paths-well-paths-none-md-step-size-5-0">export_well_paths(well_paths=None, md_step_size=5.0)</a></li>
-<li><a href="#grid-case-group-group-id">grid_case_group(group_id)</a></li>
-<li><a href="#create-grid-case-group-case-paths-1">create_grid_case_group(case_paths)</a></li>
-<li><a href="#grid-case-groups">grid_case_groups()</a></li>
-<li><a href="#import-formation-names-formation-files-none-1">import_formation_names(formation_files=None)</a></li>
-<li><a href="#export-multi-case-snapshots-grid-list-file-1">export_multi_case_snapshots(grid_list_file)</a></li>
-<li><a href="#import-well-log-files-well-log-files-none-well-log-folder">import_well_log_files(well_log_files=None, well_log_folder=&ldquo;)</a></li>
-<li><a href="#import-well-paths-well-path-files-none-well-path-folder">import_well_paths(well_path_files=None, well_path_folder=&ldquo;)</a></li>
-<li><a href="#load-case-path">load_case(path)</a></li>
-<li><a href="#grid-case-groups-1">grid_case_groups()</a></li>
-<li><a href="#open-path">open(path)</a></li>
-<li><a href="#plot-view-id">plot(view_id)</a></li>
-<li><a href="#plots">plots()</a></li>
-<li><a href="#replace-source-cases-grid-list-file-case-group-id-0">replace_source_cases(grid_list_file, case_group_id=0)</a></li>
-<li><a href="#save-path">save(path=&ldquo;)</a></li>
-<li><a href="#scale-fracture-template-template-id-half-length-height-d-factor-conductivity">scale_fracture_template(template_id, half_length, height, d_factor, conductivity)</a></li>
-<li><a href="#selected-cases">selected_cases()</a></li>
-<li><a href="#set-fracture-containment-template-id-top-layer-base-layer">set_fracture_containment(template_id, top_layer, base_layer)</a></li>
-<li><a href="#set-fracture-containment-template-id-top-layer-base-layer-1">set_fracture_containment(template_id, top_layer, base_layer)</a></li>
-<li><a href="#view-view-id-2">view(view_id)</a></li>
-<li><a href="#views-2">views()</a></li>
-<li><a href="#well-paths">well_paths()</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-<li><a href="#view-module">View Module</a>
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#class-rips-view-view-pdm-object-project">class rips.view.View(pdm_object, project)</a></li>
-<li><a href="#view-id-1">view_id()</a></li>
-<li><a href="#apply-cell-result-result-type-result-variable">apply_cell_result(result_type, result_variable)</a></li>
-<li><a href="#apply-flow-diagnostics-cell-result-result-variable-tof-selection-mode-flow-tr-by-selection-injectors-none-producers-none">apply_flow_diagnostics_cell_result(result_variable=&lsquo;TOF&rsquo;, selection_mode=&lsquo;FLOW_TR_BY_SELECTION&rsquo;, injectors=None, producers=None)</a>
-<ul>
-<li><a href="#enum-compdat-export-1">Enum compdat_export</a></li>
-</ul></li>
-<li><a href="#background-color">background_color()</a></li>
-<li><a href="#case">case()</a></li>
-<li><a href="#clone">clone()</a></li>
-<li><a href="#export-property-undefined-value-0-0">export_property(undefined_value=0.0)</a></li>
-<li><a href="#export-sim-well-fracture-completions-time-step-simulation-well-names-file-split-compdat-export">export_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export)</a>
-<ul>
-<li><a href="#enum-file-split-2">Enum file_split</a></li>
-<li><a href="#enum-compdat-export-2">Enum compdat_export</a></li>
-</ul></li>
-<li><a href="#export-snapshot-prefix-export-folder">export_snapshot(prefix=&ldquo;, export_folder=&ldquo;)</a></li>
-<li><a href="#export-visible-cells-export-keyword-fluxnum-visible-active-cells-value-1-hidden-active-cells-value-0-inactive-cells-value-0">export_visible_cells(export_keyword=&lsquo;FLUXNUM&rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0)</a></li>
-<li><a href="#set-background-color-bgcolor">set_background_color(bgcolor)</a></li>
-<li><a href="#set-cell-result">set_cell_result()</a></li>
-<li><a href="#set-show-grid-box-value">set_show_grid_box(value)</a></li>
-<li><a href="#set-time-step-time-step">set_time_step(time_step)</a></li>
-<li><a href="#show-grid-box">show_grid_box()</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#synchronous-example">Synchronous Example</a></li>
-<li><a href="#asynchronous-example">Asynchronous Example</a></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+    <li><a href="#example">Example</a></li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+        <li><a href="#cellinfo-class-description">CellInfo class description</a></li>
+        <li><a href="#vec3i-class-description">Vec3i class description</a></li>
+      </ul>
+    </li>
+    <li><a href="#example-1">Example</a></li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+    <li><a href="#example-2">Example</a></li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+  </ul>
+
+  <ul>
+    <li>
+      <ul>
+        <li></li>
+      </ul>
+    </li>
+    <li><a href="#synchronous-example">Synchronous Example</a></li>
+    <li><a href="#asynchronous-example">Asynchronous Example</a></li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -2003,129 +1888,104 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt="" /></p>
-
+<p><img src="/images/scripting/python-logo-master-v3-TM.png" alt=""></p>
 <h1 id="instance-module">Instance Module</h1>
-
-<h4 id="class-rips-instance-instance-port-50051-launched-false">class rips.instance.Instance(port=50051, launched=False)</h4>
-
+<h4 id="class-ripsinstanceinstanceport50051-launchedfalse">class rips.instance.Instance(port=50051, launched=False)</h4>
 <p>The ResInsight Instance class. Use to launch or find existing ResInsight instances</p>
-
 <h4 id="launched">launched()</h4>
-
 <p>Tells us whether the application was launched as a new process.
 If the application was launched we may need to close it when exiting the script.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>bool</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>bool</p>
+</li>
 </ul>
-
 <h4 id="commands">commands()</h4>
-
 <p>Command executor. Set when creating an instance.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>Commands</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>Commands</p>
+</li>
 </ul>
-
 <h4 id="project">project()</h4>
-
 <p>Current project in ResInsight.
 Set when creating an instance and updated when opening/closing projects.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>Project</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>Project</p>
+</li>
 </ul>
-
-<h4 id="client-version-string">client_version_string()</h4>
-
+<h4 id="client_version_string">client_version_string()</h4>
 <p>Get a full version string, i.e. 2019.04.01</p>
-
 <h4 id="exit">exit()</h4>
-
 <p>Tell ResInsight instance to quit</p>
-
-<h4 id="static-find-start-port-50051-end-port-50071">static find(start_port=50051, end_port=50071)</h4>
-
+<h4 id="static-findstart_port50051-end_port50071">static find(start_port=50051, end_port=50071)</h4>
 <p>Search for an existing Instance of ResInsight by testing ports.</p>
-
 <p>By default we search from port 50051 to 50071 or if the environment
 variable RESINSIGHT_GRPC_PORT is set we search
 RESINSIGHT_GRPC_PORT to RESINSIGHT_GRPC_PORT+20</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>start_port</strong> (<em>int</em>) &ndash; start searching from this port</p></li>
-
-<li><p><strong>end_port</strong> (<em>int</em>) &ndash; search up to but not including this port</p></li>
-</ul></li>
+<li>
+<p><strong>start_port</strong> (<em>int</em>) &ndash; start searching from this port</p>
+</li>
+<li>
+<p><strong>end_port</strong> (<em>int</em>) &ndash; search up to but not including this port</p>
+</li>
 </ul>
-
-<h4 id="is-console">is_console()</h4>
-
+</li>
+</ul>
+<h4 id="is_console">is_console()</h4>
 <p>Returns true if the connected ResInsight instance is a console app</p>
-
-<h4 id="is-gui">is_gui()</h4>
-
+<h4 id="is_gui">is_gui()</h4>
 <p>Returns true if the connected ResInsight instance is a GUI app</p>
-
-<h4 id="static-launch-resinsight-executable-console-false-launch-port-1-command-line-parameters-none">static launch(resinsight_executable=&ldquo;, console=False, launch_port=-1, command_line_parameters=None)</h4>
-
+<h4 id="static-launchresinsight_executable-consolefalse-launch_port-1-command_line_parametersnone">static launch(resinsight_executable=&rsquo;', console=False, launch_port=-1, command_line_parameters=None)</h4>
 <p>Launch a new Instance of ResInsight. This requires the environment variable
 RESINSIGHT_EXECUTABLE to be set or the parameter resinsight_executable to be provided.
 The RESINSIGHT_GRPC_PORT environment variable can be set to an alternative port number.</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>resinsight_executable</strong> (<em>str</em>) &ndash; Path to a valid ResInsight executable. If set
+<li>
+<p><strong>resinsight_executable</strong> (<em>str</em>) &ndash; Path to a valid ResInsight executable. If set
 will take precedence over what is provided in the RESINSIGHT_EXECUTABLE
-environment variable.</p></li>
-
-<li><p><strong>console</strong> (<em>bool</em>) &ndash; If True, launch as console application, without GUI.</p></li>
-
-<li><p><strong>launch_port</strong> (<em>int</em>) &ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT
-if anything else, ResInsight will try to launch with this port</p></li>
-
-<li><p><strong>command_line_parameters</strong> (<em>list</em>) &ndash; Additional parameters as string entries in the list.</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>an instance object if it worked. None if not.</p></li>
-
-<li><p><strong>Return type</strong></p>
-
-<p>Instance</p></li>
+environment variable.</p>
+</li>
+<li>
+<p><strong>console</strong> (<em>bool</em>) &ndash; If True, launch as console application, without GUI.</p>
+</li>
+<li>
+<p><strong>launch_port</strong> (<em>int</em>) &ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT
+if anything else, ResInsight will try to launch with this port</p>
+</li>
+<li>
+<p><strong>command_line_parameters</strong> (<em>list</em>) &ndash; Additional parameters as string entries in the list.</p>
+</li>
 </ul>
-
-<h4 id="major-version">major_version()</h4>
-
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>an instance object if it worked. None if not.</p>
+</li>
+<li>
+<p><strong>Return type</strong></p>
+<p>Instance</p>
+</li>
+</ul>
+<h4 id="major_version">major_version()</h4>
 <p>Get an integer with the major version number</p>
-
-<h4 id="minor-version">minor_version()</h4>
-
+<h4 id="minor_version">minor_version()</h4>
 <p>Get an integer with the minor version number</p>
-
-<h4 id="patch-version">patch_version()</h4>
-
+<h4 id="patch_version">patch_version()</h4>
 <p>Get an integer with the patch version number</p>
-
-<h4 id="set-export-folder-export-type-path-create-folder-false">set_export_folder(export_type, path, create_folder=False)</h4>
-
+<h4 id="set_export_folderexport_type-path-create_folderfalse">set_export_folder(export_type, path, create_folder=False)</h4>
 <p>Set the export folder used for all export functions</p>
-
 <table>
 <thead>
 <tr>
@@ -2134,20 +1994,17 @@ if anything else, ResInsight will try to launch with this port</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>export_type</td>
 <td>String specifying what to export</td>
 <td>String</td>
 </tr>
-
 <tr>
 <td>path</td>
 <td>Path to folder</td>
 <td>String</td>
 </tr>
-
 <tr>
 <td>create_folder</td>
 <td>Create folder if it doesn&rsquo;t exist?</td>
@@ -2155,9 +2012,7 @@ if anything else, ResInsight will try to launch with this port</p></li>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-export-type">Enum export_type</h5>
-
+<h5 id="enum-export_type">Enum export_type</h5>
 <table>
 <thead>
 <tr>
@@ -2165,34 +2020,27 @@ if anything else, ResInsight will try to launch with this port</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;COMPLETIONS&rdquo;</td>
 <td></td>
 </tr>
-
 <tr>
 <td>&ldquo;SNAPSHOTS&rdquo;</td>
 <td></td>
 </tr>
-
 <tr>
 <td>&ldquo;PROPERTIES&rdquo;</td>
 <td></td>
 </tr>
-
 <tr>
 <td>&ldquo;STATISTICS&rdquo;</td>
 <td></td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="set-main-window-size-width-height">set_main_window_size(width, height)</h4>
-
+<h4 id="set_main_window_sizewidth-height">set_main_window_size(width, height)</h4>
 <p>Set the main window size in pixels</p>
-
 <table>
 <thead>
 <tr>
@@ -2201,14 +2049,12 @@ if anything else, ResInsight will try to launch with this port</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>width</td>
 <td>Width in pixels</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>height</td>
 <td>Height in pixels</td>
@@ -2216,11 +2062,8 @@ if anything else, ResInsight will try to launch with this port</p></li>
 </tr>
 </tbody>
 </table>
-
-<h4 id="set-plot-window-size-width-height">set_plot_window_size(width, height)</h4>
-
+<h4 id="set_plot_window_sizewidth-height">set_plot_window_size(width, height)</h4>
 <p>Set the plot window size in pixels</p>
-
 <table>
 <thead>
 <tr>
@@ -2229,14 +2072,12 @@ if anything else, ResInsight will try to launch with this port</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>width</td>
 <td>Width in pixels</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>height</td>
 <td>Height in pixels</td>
@@ -2244,142 +2085,126 @@ if anything else, ResInsight will try to launch with this port</p></li>
 </tr>
 </tbody>
 </table>
-
-<h4 id="set-start-dir-path">set_start_dir(path)</h4>
-
+<h4 id="set_start_dirpath">set_start_dir(path)</h4>
 <p>Set current start directory</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>path</strong> (<em>str</em>) &ndash; path to directory</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>path</strong> (<em>str</em>) &ndash; path to directory</p>
+</li>
 </ul>
-
-<h4 id="version-string">version_string()</h4>
-
+<h4 id="version_string">version_string()</h4>
 <p>Get a full version string, i.e. 2019.04.01</p>
-
 <h2 id="example">Example</h2>
-
 <pre><code>
 resinsight  = rips.Instance.find()
 
 if resinsight is None:
     print('ERROR: could not find ResInsight')
 else:
-    print('Successfully connected to ResInsight')
-</code></pre>
-
-<h1 id="case-module">Case Module</h1>
-
-<h4 id="class-rips-case-case-channel-case-id-project">class rips.case.Case(channel, case_id, project)</h4>
-
+	print('Successfully connected to ResInsight')
+</code></pre><h1 id="case-module">Case Module</h1>
+<h4 id="class-ripscasecasechannel-case_id-project">class rips.case.Case(channel, case_id, project)</h4>
 <p>ResInsight case class</p>
-
 <p>Operate on a ResInsight case specified by a Case Id integer.
 Not meant to be constructed separately but created by one of the following
 methods in Project: loadCase, case, allCases, selectedCasesq</p>
-
 <h4 id="id">id()</h4>
-
 <p>Case Id corresponding to case Id in ResInsight project.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
 <h4 id="name">name()</h4>
-
 <p>Case name</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>str</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>str</p>
+</li>
 </ul>
-
-<h4 id="group-id">group_id()</h4>
-
+<h4 id="group_id">group_id()</h4>
 <p>Case Group id</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
 <h4 id="chunksize">chunkSize()</h4>
-
 <p>The size of each chunk during value streaming.
 A good chunk size is 64KiB = 65536B.
 Meaning the ideal number of doubles would be 8192.
 However we need overhead space, so the default is 8160.
 This leaves 256B for overhead.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
-<h4 id="active-cell-property-property-type-property-name-time-step-porosity-model-matrix-model">active_cell_property(property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+<h4 id="active_cell_propertyproperty_type-property_name-time_step-porosity_modelmatrix_model">active_cell_property(property_type, property_name, time_step, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a cell property for all active cells. Sync, so returns a list</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+</ul>
+</li>
+<li>
+<p><strong>Returns</strong></p>
 <p>A list containing double values
-Loop through the chunks and then the values within the chunk to get all values.</p></li>
+Loop through the chunks and then the values within the chunk to get all values.</p>
+</li>
 </ul>
-
-<h4 id="active-cell-property-async-property-type-property-name-time-step-porosity-model-matrix-model">active_cell_property_async(property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+<h4 id="active_cell_property_asyncproperty_type-property_name-time_step-porosity_modelmatrix_model">active_cell_property_async(property_type, property_name, time_step, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a cell property for all active cells. Async, so returns an iterator</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>An iterator to a chunk object containing an array of double values
-Loop through the chunks and then the values within the chunk to get all values.</p></li>
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
 </ul>
-
-<h4 id="available-properties-property-type-porosity-model-matrix-model">available_properties(property_type, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>An iterator to a chunk object containing an array of double values
+Loop through the chunks and then the values within the chunk to get all values.</p>
+</li>
+</ul>
+<h4 id="available_propertiesproperty_type-porosity_modelmatrix_model">available_properties(property_type, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a list of available properties</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string corresponding to property_type enum. Choices:</p>
-
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string corresponding to property_type enum. Choices:</p>
 <ul>
 <li>DYNAMIC_NATIVE</li>
 <li>STATIC_NATIVE</li>
@@ -2389,50 +2214,47 @@ Loop through the chunks and then the values within the chunk to get all values.<
 <li>FORMATION_NAMES</li>
 <li>FLOW_DIAGNOSTICS</li>
 <li>INJECTION_FLOODING</li>
-</ul></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
-</ul></li>
 </ul>
-
-<h4 id="cell-count-porosity-model-matrix-model">cell_count(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p>
+</li>
+</ul>
+</li>
+</ul>
+<h4 id="cell_countporosity_modelmatrix_model">cell_count(porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a cell count object containing number of active cells and
 total number of cells</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <p><strong>porosity_model</strong> (<em>str</em>) &ndash; String representing an enum.
-must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
-
-<li><p><strong>Returns</strong></p>
-
+must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p>
+</li>
+<li>
+<p><strong>Returns</strong></p>
 <p>active_cell_count: number of active cells
-reservoir_cell_count: total number of reservoir cells</p></li>
-
-<li><p><strong>Return type</strong></p>
-
-<p>Cell Count object with the following integer attributes</p></li>
+reservoir_cell_count: total number of reservoir cells</p>
+</li>
+<li>
+<p><strong>Return type</strong></p>
+<p>Cell Count object with the following integer attributes</p>
+</li>
 </ul>
-
-<h4 id="cell-info-for-active-cells-porosity-model-matrix-model">cell_info_for_active_cells(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+<h4 id="cell_info_for_active_cellsporosity_modelmatrix_model">cell_info_for_active_cells(porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get list of cell info objects for current case</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <p><strong>porosity_model</strong> (<em>str</em>) &ndash; String representing an enum.
-must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>List of <strong>CellInfo</strong> objects</p></li>
+must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p>
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>List of <strong>CellInfo</strong> objects</p>
+</li>
 </ul>
-
 <h3 id="cellinfo-class-description">CellInfo class description</h3>
-
 <table>
 <thead>
 <tr>
@@ -2441,32 +2263,27 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>grid_index</td>
 <td>Index to grid</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>parent_grid_index</td>
 <td>Index to parent grid</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>coarsening_box_index</td>
 <td>Index to coarsening box</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>local_ijk</td>
 <td>Cell index in IJK directions of local grid</td>
 <td>Vec3i</td>
 </tr>
-
 <tr>
 <td>parent_ijk</td>
 <td>Cell index in IJK directions of parent grid</td>
@@ -2474,9 +2291,7 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
 <h3 id="vec3i-class-description">Vec3i class description</h3>
-
 <table>
 <thead>
 <tr>
@@ -2485,20 +2300,17 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>i</td>
 <td>I grid index</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>j</td>
 <td>J grid index</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>k</td>
 <td>K grid index</td>
@@ -2506,28 +2318,22 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
-<h4 id="cell-info-for-active-cells-async-porosity-model-matrix-model">cell_info_for_active_cells_async(porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+<h4 id="cell_info_for_active_cells_asyncporosity_modelmatrix_model">cell_info_for_active_cells_async(porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get Stream of cell info objects for current case</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <p><strong>porosity_model</strong> (<em>str</em>) &ndash; String representing an enum.
-must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>Stream of <strong>CellInfo</strong> objects</p></li>
+must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p>
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>Stream of <strong>CellInfo</strong> objects</p>
+</li>
 </ul>
-
 <p>See cell_info_for_active_cells() for detalis on the <strong>CellInfo</strong> class.</p>
-
-<h4 id="contour-maps-map-type-contourmaptype-eclipse-1">contour_maps(map_type=<ContourMapType.ECLIPSE: 1>)</h4>
-
+<h4 id="contour_mapsmap_typecontourmaptypeeclipse-1">contour_maps(map_type=&lt;ContourMapType.ECLIPSE: 1&gt;)</h4>
 <p>Get a list of all contour maps belonging to a project</p>
-
 <table>
 <thead>
 <tr>
@@ -2536,38 +2342,32 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>time_steps</td>
 <td>Time step index</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>well_path_names</td>
 <td>List of well path names</td>
 <td>List of Strings</td>
 </tr>
-
 <tr>
 <td>refinement_i</td>
 <td>Refinment in x-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>refinement_j</td>
 <td>Refinment in y-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>refinement_k</td>
 <td>Refinment in z-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>split_type</td>
 <td>Defines how to split LGRS</td>
@@ -2575,21 +2375,16 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>map_type</strong> (<em>enum</em>) &ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>map_type</strong> (<em>enum</em>) &ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH</p>
+</li>
 </ul>
-
-<h4 id="create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</h4>
-
+<h4 id="create_multiple_fracturestemplate_id-well_path_names-min_dist_from_well_td-max_fractures_per_well-top_layer-base_layer-spacing-action">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</h4>
 <p>Create Multiple Fractures in one go</p>
-
-<h4 id="create-lgr-for-completion-time-step-well-path-names-refinement-i-refinement-j-refinement-k-split-type">create_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type)</h4>
-
+<h4 id="create_lgr_for_completiontime_step-well_path_names-refinement_i-refinement_j-refinement_k-split_type">create_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type)</h4>
 <p>Create a local grid refinement for the completions on the given well paths</p>
-
 <table>
 <thead>
 <tr>
@@ -2598,38 +2393,32 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>time_steps</td>
 <td>Time step index</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>well_path_names</td>
 <td>List of well path names</td>
 <td>List of Strings</td>
 </tr>
-
 <tr>
 <td>refinement_i</td>
 <td>Refinment in x-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>refinement_j</td>
 <td>Refinment in y-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>refinement_k</td>
 <td>Refinment in z-direction</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>split_type</td>
 <td>Defines how to split LGRS</td>
@@ -2637,9 +2426,7 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-split-type">Enum split_type</h5>
-
+<h5 id="enum-split_type">Enum split_type</h5>
 <table>
 <thead>
 <tr>
@@ -2647,33 +2434,25 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;LGR_PER_CELL&rdquo;</td>
 <td>One LGR for each completed cell</td>
 </tr>
-
 <tr>
 <td>&ldquo;LGR_PER_COMPLETION&rdquo;</td>
 <td>One LGR for each completion (fracture, perforation, &hellip;)</td>
 </tr>
-
 <tr>
 <td>&ldquo;LGR_PER_WELL&rdquo;</td>
 <td>One LGR for each well</td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="create-view">create_view()</h4>
-
+<h4 id="create_view">create_view()</h4>
 <p>Create a new view in the current case</p>
-
-<h4 id="create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action-1">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</h4>
-
+<h4 id="create_multiple_fracturestemplate_id-well_path_names-min_dist_from_well_td-max_fractures_per_well-top_layer-base_layer-spacing-action-1">create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)</h4>
 <p>Create Multiple Fractures in one go</p>
-
 <table>
 <thead>
 <tr>
@@ -2682,50 +2461,42 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>template_id</td>
 <td>Id of the template</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>well_path_names</td>
 <td>List of well path names</td>
 <td>List of Strings</td>
 </tr>
-
 <tr>
 <td>min_dist_from_well_td</td>
 <td>Minimum distance from well TD</td>
 <td>Double</td>
 </tr>
-
 <tr>
 <td>max_fractures_per_well</td>
 <td>Max number of fractures per well</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>top_layer</td>
 <td>Top grid k-level for fractures</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>base_layer</td>
 <td>Base grid k-level for fractures</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>spacing</td>
 <td>Spacing between fractures</td>
 <td>Double</td>
 </tr>
-
 <tr>
 <td>action</td>
 <td>&lsquo;APPEND_FRACTURES&rsquo; or &lsquo;REPLACE_FRACTURES&rsquo;</td>
@@ -2733,44 +2504,35 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
-<h4 id="create-saturation-pressure-plots">create_saturation_pressure_plots()</h4>
-
+<h4 id="create_saturation_pressure_plots">create_saturation_pressure_plots()</h4>
 <p>Create saturation pressure plots for the current case</p>
-
-<h4 id="create-view-1">create_view()</h4>
-
+<h4 id="create_view-1">create_view()</h4>
 <p>Create a new view in the current case</p>
-
-<h4 id="create-well-bore-stability-plot-well-path-time-step">create_well_bore_stability_plot(well_path, time_step)</h4>
-
+<h4 id="create_well_bore_stability_plotwell_path-time_step">create_well_bore_stability_plot(well_path, time_step)</h4>
 <p>Create a new well bore stability plot</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>well_path</strong> (<em>str</em>) &ndash; well path name</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; time step</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A new plot object</p></li>
+<li>
+<p><strong>well_path</strong> (<em>str</em>) &ndash; well path name</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; time step</p>
+</li>
 </ul>
-
-<h4 id="days-since-start">days_since_start()</h4>
-
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A new plot object</p>
+</li>
+</ul>
+<h4 id="days_since_start">days_since_start()</h4>
 <p>Get a list of decimal values representing days since the start of the simulation</p>
-
 <pre><code>* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter
 </code></pre>
-
-<h4 id="export-flow-characteristics-time-steps-injectors-producers-file-name-minimum-communication-0-0-aquifer-cell-threshold-0-1">export_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1)</h4>
-
+<h4 id="export_flow_characteristicstime_steps-injectors-producers-file_name-minimum_communication00-aquifer_cell_threshold01">export_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1)</h4>
 <p>Export Flow Characteristics data to text file in CSV format</p>
-
 <table>
 <thead>
 <tr>
@@ -2779,38 +2541,32 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>time_steps</td>
 <td>Time step indices</td>
 <td>List of Integer</td>
 </tr>
-
 <tr>
 <td>injectors</td>
 <td>Injector names</td>
 <td>List of Strings</td>
 </tr>
-
 <tr>
 <td>producers</td>
 <td>Producer names</td>
 <td>List of Strings</td>
 </tr>
-
 <tr>
 <td>file_name</td>
 <td>Export file name</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>minimum_communication</td>
 <td>Minimum Communication, defaults to 0.0</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>aquifer_cell_threshold</td>
 <td>Aquifer Cell Threshold, defaults to 0.1</td>
@@ -2818,25 +2574,20 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
-<h4 id="export-msw-well-path">export_msw(well_path)</h4>
-
+<h4 id="export_mswwell_path">export_msw(well_path)</h4>
 <p>Export Eclipse Multi-segment-well model to file</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p></li>
-
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>well_path</strong> (<em>str</em>) &ndash; Well path name</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+</li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>well_path</strong> (<em>str</em>) &ndash; Well path name</p>
+</li>
 </ul>
-
-<h4 id="export-property-time-step-property-name-eclipse-keyword-class-property-undefined-value-0-0-export-file-class-property">export_property(time_step, property_name, eclipse_keyword=<class 'property'>, undefined_value=0.0, export_file=<class 'property'>)</h4>
-
+<h4 id="export_propertytime_step-property_name-eclipse_keywordclass-property-undefined_value00-export_fileclass-property">export_property(time_step, property_name, eclipse_keyword=&lt;class &lsquo;property'&gt;, undefined_value=0.0, export_file=&lt;class &lsquo;property'&gt;)</h4>
 <p>Export an Eclipse property</p>
-
-<h5 id="enum-file-split">Enum file_split</h5>
-
+<h5 id="enum-file_split">Enum file_split</h5>
 <table>
 <thead>
 <tr>
@@ -2844,25 +2595,21 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;UNIFIED_FILE&rdquo;</td>
 <td>A single file with all combined transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL&rdquo;</td>
 <td>One file for each well with combined transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE&rdquo;</td>
 <td>One file for each completion type for each well</td>
 </tr>
 </tbody>
 </table>
-
 <pre><code>* **time_step** (*int*) -- time step index
 
 * **property_name** (*str*) -- property to export
@@ -2873,29 +2620,25 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 
 * **export_file** (*str*) -- File name for export. Defaults to the value of property parameter
 </code></pre>
-
-<h4 id="grid-index">grid(index)</h4>
-
+<h4 id="gridindex">grid(index)</h4>
 <p>Get Grid of a given index. Returns a rips Grid object</p>
-
-<h4 id="export-snapshots-of-all-views-prefix-export-folder">export_snapshots_of_all_views(prefix=&ldquo;, export_folder=&ldquo;)</h4>
-
+<h4 id="export_snapshots_of_all_viewsprefix-export_folder">export_snapshots_of_all_views(prefix=&rsquo;', export_folder=&rsquo;')</h4>
 <p>Export snapshots for all views in the case</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p></li>
-
-<li><p><strong>export_folder</strong> (<em>str</em>) &ndash; The path to export to. By default will use the global export folder</p></li>
-</ul></li>
+<li>
+<p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p>
+</li>
+<li>
+<p><strong>export_folder</strong> (<em>str</em>) &ndash; The path to export to. By default will use the global export folder</p>
+</li>
 </ul>
-
-<h4 id="export-well-path-completions-time-step-well-path-names-file-split-compdat-export-transmissibilities-include-perforations-true-include-fishbones-true-fishbones-exclude-main-bore-true-combination-mode-individually">export_well_path_completions(time_step, well_path_names, file_split, compdat_export=&lsquo;TRANSMISSIBILITIES&rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode=&lsquo;INDIVIDUALLY&rsquo;)</h4>
-
+</li>
+</ul>
+<h4 id="export_well_path_completionstime_step-well_path_names-file_split-compdat_exporttransmissibilities-include_perforationstrue-include_fishbonestrue-fishbones_exclude_main_boretrue-combination_modeindividually">export_well_path_completions(time_step, well_path_names, file_split, compdat_export='TRANSMISSIBILITIES&rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode='INDIVIDUALLY&rsquo;)</h4>
 <p>Export well path completions for the current case to file</p>
-
 <table>
 <thead>
 <tr>
@@ -2904,50 +2647,42 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>time_step</td>
 <td>Time step to export for</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>well_path_names</td>
 <td>List of well path names</td>
 <td>List</td>
 </tr>
-
 <tr>
 <td>file_split</td>
 <td>Controls how export data is split into files</td>
 <td>String enum</td>
 </tr>
-
 <tr>
 <td>compdat_export</td>
 <td>Compdat export type</td>
 <td>String enum</td>
 </tr>
-
 <tr>
 <td>include_perforations</td>
 <td>Export perforations?</td>
 <td>bool</td>
 </tr>
-
 <tr>
 <td>include_fishbones</td>
 <td>Export fishbones?</td>
 <td>bool</td>
 </tr>
-
 <tr>
 <td>fishbones_exclude_main_bore</td>
 <td>Exclude main bore when exporting fishbones?</td>
 <td>bool</td>
 </tr>
-
 <tr>
 <td>combination_mode</td>
 <td>Settings for multiple completions in same cell</td>
@@ -2955,9 +2690,7 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-file-split-1">Enum file_split</h5>
-
+<h5 id="enum-file_split-1">Enum file_split</h5>
 <table>
 <thead>
 <tr>
@@ -2965,27 +2698,22 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;UNIFIED_FILE&rdquo;</td>
 <td>A single file with all combined transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL&rdquo;</td>
 <td>One file for each well with combined transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE&rdquo;</td>
 <td>One file for each completion type for each well</td>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-compdat-export">Enum compdat_export</h5>
-
+<h5 id="enum-compdat_export">Enum compdat_export</h5>
 <table>
 <thead>
 <tr>
@@ -2993,22 +2721,18 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;TRANSMISSIBILITIES&rdquo;</td>
 <td>Direct export of transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS&rdquo;</td>
 <td>Include WPIMULT in addition to transmissibilities</td>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-combination-mode">Enum combination_mode</h5>
-
+<h5 id="enum-combination_mode">Enum combination_mode</h5>
 <table>
 <thead>
 <tr>
@@ -3016,187 +2740,188 @@ must be &lsquo;MATRIX_MODEL&rsquo; or &lsquo;FRACTURE_MODEL&rsquo;.</p></li>
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;INDIVIDUALLY&rdquo;</td>
 <td>Exports the different completion types into separate sections</td>
 </tr>
-
 <tr>
 <td>&ldquo;COMBINED&rdquo;</td>
 <td>Export one combined transmissibility for each cell</td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="grid-index-1">grid(index)</h4>
-
+<h4 id="gridindex-1">grid(index)</h4>
 <p>Get Grid of a given index. Returns a rips Grid object</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <p><strong>index</strong> (<em>int</em>) &ndash; The grid index</p>
-
 <ul>
 <li><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <p>Returns: Grid object</p>
-
-<h4 id="grid-path">grid_path()</h4>
-
+<h4 id="grid_path">grid_path()</h4>
 <p>Get path of the current grid case</p>
-
 <p>Returns: path string</p>
-
-<h4 id="grid-property-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">grid_property(property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+<h4 id="grid_propertyproperty_type-property_name-time_step-grid_index0-porosity_modelmatrix_model">grid_property(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a cell property for all grid cells. Synchronous, so returns a list</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>grid_index</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re getting values for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A list of double values</p></li>
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>grid_index</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re getting values for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
 </ul>
-
-<h4 id="grid-property-async-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">grid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A list of double values</p>
+</li>
+</ul>
+<h4 id="grid_property_asyncproperty_type-property_name-time_step-grid_index0-porosity_modelmatrix_model">grid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Get a cell property for all grid cells. Async, so returns an iterator</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>gridIndex</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re getting values for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>gridIndex</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re getting values for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+</ul>
+</li>
+<li>
+<p><strong>Returns</strong></p>
 <p>An iterator to a chunk object containing an array of double values
-Loop through the chunks and then the values within the chunk to get all values.</p></li>
+Loop through the chunks and then the values within the chunk to get all values.</p>
+</li>
 </ul>
-
 <h4 id="grids">grids()</h4>
-
 <p>Get a list of all rips Grid objects in the case</p>
-
-<h4 id="import-formation-names-formation-files-none">import_formation_names(formation_files=None)</h4>
-
+<h4 id="import_formation_namesformation_filesnone">import_formation_names(formation_files=None)</h4>
 <p>Import formation names into project and apply it to the current case</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>formation_files</strong> (<em>list</em>) &ndash; list of files to import</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>formation_files</strong> (<em>list</em>) &ndash; list of files to import</p>
+</li>
 </ul>
-
-<h4 id="replace-new-grid-file">replace(new_grid_file)</h4>
-
+<h4 id="replacenew_grid_file">replace(new_grid_file)</h4>
 <p>Replace the current case grid with a new grid loaded from file</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <p><strong>new_egrid_file</strong> (<em>str</em>) &ndash; path to EGRID file</p>
-
 <ul>
 <li><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</li>
-</ul></li>
 </ul>
-
-<h4 id="set-active-cell-property-values-property-type-property-name-time-step-porosity-model-matrix-model">set_active_cell_property(values, property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+</ul>
+<h4 id="set_active_cell_propertyvalues-property_type-property_name-time_step-porosity_modelmatrix_model">set_active_cell_property(values, property_type, property_name, time_step, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Set a cell property for all active cells.</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>values</strong> (<em>list</em>) &ndash; a list of double precision floating point numbers</p></li>
-
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
+<li>
+<p><strong>values</strong> (<em>list</em>) &ndash; a list of double precision floating point numbers</p>
+</li>
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
 </ul>
-
-<h4 id="set-active-cell-property-async-values-iterator-property-type-property-name-time-step-porosity-model-matrix-model">set_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+</ul>
+<h4 id="set_active_cell_property_asyncvalues_iterator-property_type-property_name-time_step-porosity_modelmatrix_model">set_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Set cell property for all active cells Async. Takes an iterator to the input values</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>values_iterator</strong> (<em>iterator</em>) &ndash; an iterator to the properties to be set</p></li>
-
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
+<li>
+<p><strong>values_iterator</strong> (<em>iterator</em>) &ndash; an iterator to the properties to be set</p>
+</li>
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
 </ul>
-
-<h4 id="set-grid-property-values-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model">set_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model=&lsquo;MATRIX_MODEL&rsquo;)</h4>
-
+</li>
+</ul>
+<h4 id="set_grid_propertyvalues-property_type-property_name-time_step-grid_index0-porosity_modelmatrix_model">set_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL&rsquo;)</h4>
 <p>Set a cell property for all grid cells.</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>values</strong> (<em>list</em>) &ndash; a list of double precision floating point numbers</p></li>
-
-<li><p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-
-<li><p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p></li>
-
-<li><p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p></li>
-
-<li><p><strong>grid_index</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re setting values for</p></li>
-
-<li><p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p></li>
-</ul></li>
+<li>
+<p><strong>values</strong> (<em>list</em>) &ndash; a list of double precision floating point numbers</p>
+</li>
+<li>
+<p><strong>property_type</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
+<li>
+<p><strong>property_name</strong> (<em>str</em>) &ndash; name of an Eclipse property</p>
+</li>
+<li>
+<p><strong>time_step</strong> (<em>int</em>) &ndash; the time step for which to get the property for</p>
+</li>
+<li>
+<p><strong>grid_index</strong> (<em>int</em>) &ndash; index to the grid we&rsquo;re setting values for</p>
+</li>
+<li>
+<p><strong>porosity_model</strong> (<em>str</em>) &ndash; string enum. See available()</p>
+</li>
 </ul>
-
-<h4 id="time-steps">time_steps()</h4>
-
+</li>
+</ul>
+<h4 id="time_steps">time_steps()</h4>
 <p>Get a list containing all time steps</p>
-
 <p>The time steps are defined by the class <strong>TimeStepDate</strong> :</p>
-
 <table>
 <thead>
 <tr>
@@ -3204,54 +2929,41 @@ Loop through the chunks and then the values within the chunk to get all values.<
 <th>Name</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>int</td>
 <td>year</td>
 </tr>
-
 <tr>
 <td>int</td>
 <td>month</td>
 </tr>
-
 <tr>
 <td>int</td>
 <td>day</td>
 </tr>
-
 <tr>
 <td>int</td>
 <td>hour</td>
 </tr>
-
 <tr>
 <td>int</td>
 <td>minute</td>
 </tr>
-
 <tr>
 <td>int</td>
 <td>second</td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="view-view-id">view(view_id)</h4>
-
+<h4 id="viewview_id">view(view_id)</h4>
 <p>Get a particular view belonging to a case by providing view id
 :param view_id: view id
 :type view_id: int</p>
-
 <p>Returns: a view object</p>
-
 <h4 id="views">views()</h4>
-
 <p>Get a list of views belonging to a case</p>
-
 <h2 id="example-1">Example</h2>
-
 <pre><code>
 # Import the ResInsight Processing Server Module
 import rips
@@ -3276,66 +2988,55 @@ if resinsight is not None:
         
     
 
-</code></pre>
-
-<h1 id="contour-map-module">Contour Map Module</h1>
-
-<h4 id="class-rips-contour-map-contourmap-pdm-object-project-map-type">class rips.contour_map.ContourMap(pdm_object, project, map_type)</h4>
-
+</code></pre><h1 id="contour-map-module">Contour Map Module</h1>
+<h4 id="class-ripscontour_mapcontourmappdm_object-project-map_type">class rips.contour_map.ContourMap(pdm_object, project, map_type)</h4>
 <p>ResInsight contour map class</p>
-
-<h4 id="view-id">view_id()</h4>
-
+<h4 id="view_id">view_id()</h4>
 <p>View Id corresponding to the View Id in ResInsight project.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
-<h4 id="export-to-text-export-file-name-export-local-coordinates-false-undefined-value-label-nan-exclude-undefined-values-false">export_to_text(export_file_name=&ldquo;, export_local_coordinates=False, undefined_value_label=&lsquo;NaN&rsquo;, exclude_undefined_values=False)</h4>
-
+<h4 id="export_to_textexport_file_name-export_local_coordinatesfalse-undefined_value_labelnan-exclude_undefined_valuesfalse">export_to_text(export_file_name=&rsquo;', export_local_coordinates=False, undefined_value_label='NaN&rsquo;, exclude_undefined_values=False)</h4>
 <p>Export snapshot for the current view</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>export_file_name</strong> (<em>str</em>) &ndash; The file location to store results in.</p></li>
-
-<li><p><strong>export_local_coordinates</strong> (<em>bool</em>) &ndash; Should we export local coordinates, or UTM.</p></li>
-
-<li><p><strong>undefined_value_label</strong> (<em>str</em>) &ndash; Replace undefined values with this label.</p></li>
-
-<li><p><strong>exclude_undefined_values</strong> (<em>bool</em>) &ndash; Skip undefined values.</p></li>
-</ul></li>
+<li>
+<p><strong>export_file_name</strong> (<em>str</em>) &ndash; The file location to store results in.</p>
+</li>
+<li>
+<p><strong>export_local_coordinates</strong> (<em>bool</em>) &ndash; Should we export local coordinates, or UTM.</p>
+</li>
+<li>
+<p><strong>undefined_value_label</strong> (<em>str</em>) &ndash; Replace undefined values with this label.</p>
+</li>
+<li>
+<p><strong>exclude_undefined_values</strong> (<em>bool</em>) &ndash; Skip undefined values.</p>
+</li>
+</ul>
+</li>
 </ul>
-
 <h1 id="grid-module">Grid Module</h1>
-
-<h4 id="class-rips-grid-grid-index-case-channel">class rips.grid.Grid(index, case, channel)</h4>
-
+<h4 id="class-ripsgridgridindex-case-channel">class rips.grid.Grid(index, case, channel)</h4>
 <p>Grid Information. Not meant to be constructed separately</p>
-
 <p>Create Grid objects using mathods on Case: Grid() and Grids()</p>
-
 <h4 id="dimensions">dimensions()</h4>
-
 <p>The dimensions in i, j, k direction</p>
-
 <ul>
-<li><p><strong>Returns</strong></p>
-
-<p>class with integer attributes i, j, k giving extent in all three dimensions.</p></li>
-
-<li><p><strong>Return type</strong></p>
-
-<p>Vec3i</p></li>
+<li>
+<p><strong>Returns</strong></p>
+<p>class with integer attributes i, j, k giving extent in all three dimensions.</p>
+</li>
+<li>
+<p><strong>Return type</strong></p>
+<p>Vec3i</p>
+</li>
 </ul>
-
 <h2 id="example-2">Example</h2>
-
 <pre><code>    case = rips_instance.project.loadCase(path=casePath)
 print (case.gridCount())
     if case.gridCount() &gt; 0:
@@ -3344,397 +3045,334 @@ print (case.gridCount())
             print(dimensions.i)
             print(dimensions.j)
             print(dimensions.k)
-</code></pre>
-
-<h1 id="gridcasegroup-module">GridCaseGroup Module</h1>
-
-<h4 id="class-rips-gridcasegroup-gridcasegroup-pdm-object">class rips.gridcasegroup.GridCaseGroup(pdm_object)</h4>
-
+</code></pre><h1 id="gridcasegroup-module">GridCaseGroup Module</h1>
+<h4 id="class-ripsgridcasegroupgridcasegrouppdm_object">class rips.gridcasegroup.GridCaseGroup(pdm_object)</h4>
 <p>ResInsight Grid Case Group class</p>
-
 <p>Operate on a ResInsight case group specified by a Case Group Id integer.</p>
-
-<h4 id="group-id-1">group_id()</h4>
-
+<h4 id="group_id-1">group_id()</h4>
 <p>Grid Case Group Id corresponding to case group Id in ResInsight project.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
-<h4 id="compute-statistics-case-ids-none">compute_statistics(case_ids=None)</h4>
-
+<h4 id="compute_statisticscase_idsnone">compute_statistics(case_ids=None)</h4>
 <p>Compute statistics for the given case ids</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>case_ids</strong> (<em>list of integers</em>) &ndash; list of case ids.</p></li>
-
-<li><p><strong>this is None all cases in group are included</strong> (<em>If</em>) &ndash;</p></li>
-</ul></li>
+<li>
+<p><strong>case_ids</strong> (<em>list of integers</em>) &ndash; list of case ids.</p>
+</li>
+<li>
+<p><strong>this is None all cases in group are included</strong> (<em>If</em>) &ndash;</p>
+</li>
 </ul>
-
-<h4 id="create-statistics-case">create_statistics_case()</h4>
-
+</li>
+</ul>
+<h4 id="create_statistics_case">create_statistics_case()</h4>
 <p>Create a Statistics case in the Grid Case Group</p>
-
 <ul>
-<li><p><strong>Returns</strong></p>
-
-<p>A new Case</p></li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A new Case</p>
+</li>
 </ul>
-
-<h4 id="statistics-cases">statistics_cases()</h4>
-
+<h4 id="statistics_cases">statistics_cases()</h4>
 <p>Get a list of all statistics cases in the Grid Case Group</p>
-
-<h4 id="view-view-id-1">view(view_id)</h4>
-
+<h4 id="viewview_id-1">view(view_id)</h4>
 <p>Get a particular view belonging to a case group by providing view id
 :param id: view id
 :type id: int</p>
-
 <p>Returns: a view object</p>
-
 <h4 id="views-1">views()</h4>
-
 <p>Get a list of views belonging to a grid case group</p>
-
 <h1 id="project-module">Project Module</h1>
-
-<h4 id="class-rips-project-project-channel">class rips.project.Project(channel)</h4>
-
+<h4 id="class-ripsprojectprojectchannel">class rips.project.Project(channel)</h4>
 <p>ResInsight project. Not intended to be created separately.</p>
-
 <ul>
 <li><strong>Type</strong></li>
 </ul>
-
-<h4 id="case-case-id">case(case_id)</h4>
-
+<h4 id="casecase_id">case(case_id)</h4>
 <p>Get a specific case from the provided case Id</p>
-
-<h4 id="compute-statistics-case-ids-none-1">compute_statistics(case_ids=None)</h4>
-
+<h4 id="compute_statisticscase_idsnone-1">compute_statistics(case_ids=None)</h4>
 <p>Compute statistics for the given case ids</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>case_ids</strong> (<em>list of integers</em>) &ndash; list of case ids.</p></li>
-
-<li><p><strong>this is None all cases in group are included</strong> (<em>If</em>) &ndash;</p></li>
-</ul></li>
+<li>
+<p><strong>case_ids</strong> (<em>list of integers</em>) &ndash; list of case ids.</p>
+</li>
+<li>
+<p><strong>this is None all cases in group are included</strong> (<em>If</em>) &ndash;</p>
+</li>
 </ul>
-
-<h4 id="create-statistics-case-1">create_statistics_case()</h4>
-
+</li>
+</ul>
+<h4 id="create_statistics_case-1">create_statistics_case()</h4>
 <p>Create a Statistics case in the Grid Case Group</p>
-
 <ul>
-<li><p><strong>Returns</strong></p>
-
-<p>A new Case</p></li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A new Case</p>
+</li>
 </ul>
-
-<h4 id="statistics-cases-1">statistics_cases()</h4>
-
+<h4 id="statistics_cases-1">statistics_cases()</h4>
 <p>Get a list of all statistics cases in the Grid Case Group</p>
-
-<h4 id="contour-maps-map-type-contourmaptype-eclipse-1-1">contour_maps(map_type=<ContourMapType.ECLIPSE: 1>)</h4>
-
+<h4 id="contour_mapsmap_typecontourmaptypeeclipse-1-1">contour_maps(map_type=&lt;ContourMapType.ECLIPSE: 1&gt;)</h4>
 <p>Get a list of all contour maps belonging to a project</p>
-
 <p>Returns: a view object</p>
-
-<h4 id="create-grid-case-group-case-paths">create_grid_case_group(case_paths)</h4>
-
+<h4 id="create_grid_case_groupcase_paths">create_grid_case_group(case_paths)</h4>
 <p>Create a Grid Case Group from a list of cases</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>case_paths</strong> (<em>list</em>) &ndash; list of file path strings</p></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A case group id and name</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>case_paths</strong> (<em>list</em>) &ndash; list of file path strings</p>
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A case group id and name</p>
+</li>
 </ul>
-
-<h4 id="export-multi-case-snapshots-grid-list-file">export_multi_case_snapshots(grid_list_file)</h4>
-
+<h4 id="export_multi_case_snapshotsgrid_list_file">export_multi_case_snapshots(grid_list_file)</h4>
 <p>Export snapshots for a set of cases</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>grid_list_file</strong> (<em>str</em>) &ndash; Path to a file containing a list of grids to export snapshot for</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>grid_list_file</strong> (<em>str</em>) &ndash; Path to a file containing a list of grids to export snapshot for</p>
+</li>
 </ul>
-
-<h4 id="export-snapshots-snapshot-type-all-prefix">export_snapshots(snapshot_type=&lsquo;ALL&rsquo;, prefix=&ldquo;)</h4>
-
+<h4 id="export_snapshotssnapshot_typeall-prefix">export_snapshots(snapshot_type='ALL&rsquo;, prefix=&rsquo;')</h4>
 <p>Export all snapshots of a given type</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>snapshot_type</strong> (<em>str</em>) &ndash; Enum string (&lsquo;ALL&rsquo;, &lsquo;VIEWS&rsquo; or &lsquo;PLOTS&rsquo;)</p></li>
-
-<li><p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p></li>
-</ul></li>
+<li>
+<p><strong>snapshot_type</strong> (<em>str</em>) &ndash; Enum string (&lsquo;ALL&rsquo;, &lsquo;VIEWS&rsquo; or &lsquo;PLOTS&rsquo;)</p>
+</li>
+<li>
+<p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p>
+</li>
 </ul>
-
-<h4 id="export-well-paths-well-paths-none-md-step-size-5-0">export_well_paths(well_paths=None, md_step_size=5.0)</h4>
-
+</li>
+</ul>
+<h4 id="export_well_pathswell_pathsnone-md_step_size50">export_well_paths(well_paths=None, md_step_size=5.0)</h4>
 <p>Export a set of well paths</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>well_paths</strong> (<em>list</em>) &ndash; List of strings of well paths. If none, export all.</p></li>
-
-<li><p><strong>md_step_size</strong> (<em>double</em>) &ndash; resolution of the exported well path</p></li>
-</ul></li>
+<li>
+<p><strong>well_paths</strong> (<em>list</em>) &ndash; List of strings of well paths. If none, export all.</p>
+</li>
+<li>
+<p><strong>md_step_size</strong> (<em>double</em>) &ndash; resolution of the exported well path</p>
+</li>
 </ul>
-
-<h4 id="grid-case-group-group-id">grid_case_group(group_id)</h4>
-
+</li>
+</ul>
+<h4 id="grid_case_groupgroup_id">grid_case_group(group_id)</h4>
 <p>Get a particular grid case group belonging to a project</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>groupId</strong> (<em>int</em>) &ndash; group id</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>groupId</strong> (<em>int</em>) &ndash; group id</p>
+</li>
 </ul>
-
-<h4 id="create-grid-case-group-case-paths-1">create_grid_case_group(case_paths)</h4>
-
+<h4 id="create_grid_case_groupcase_paths-1">create_grid_case_group(case_paths)</h4>
 <p>Create a Grid Case Group from a list of cases</p>
-
 <p>Returns: a grid case group object</p>
-
-<h4 id="grid-case-groups">grid_case_groups()</h4>
-
+<h4 id="grid_case_groups">grid_case_groups()</h4>
 <p>Get a list of all grid case groups in the project</p>
-
-<h4 id="import-formation-names-formation-files-none-1">import_formation_names(formation_files=None)</h4>
-
+<h4 id="import_formation_namesformation_filesnone-1">import_formation_names(formation_files=None)</h4>
 <p>Import formation names into project</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>formation_files</strong> (<em>list</em>) &ndash; list of files to import</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>formation_files</strong> (<em>list</em>) &ndash; list of files to import</p>
+</li>
 </ul>
-
-<h4 id="export-multi-case-snapshots-grid-list-file-1">export_multi_case_snapshots(grid_list_file)</h4>
-
+<h4 id="export_multi_case_snapshotsgrid_list_file-1">export_multi_case_snapshots(grid_list_file)</h4>
 <p>Export snapshots for a set of cases</p>
-
-<h4 id="import-well-log-files-well-log-files-none-well-log-folder">import_well_log_files(well_log_files=None, well_log_folder=&ldquo;)</h4>
-
+<h4 id="import_well_log_fileswell_log_filesnone-well_log_folder">import_well_log_files(well_log_files=None, well_log_folder=&rsquo;')</h4>
 <p>Import well log files into project</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>well_log_files</strong> (<em>list</em>) &ndash; List of file paths to import</p></li>
-
-<li><p><strong>well_log_folder</strong> (<em>str</em>) &ndash; A folder path containing files to import</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A list of well path names (strings) that had logs imported</p></li>
+<li>
+<p><strong>well_log_files</strong> (<em>list</em>) &ndash; List of file paths to import</p>
+</li>
+<li>
+<p><strong>well_log_folder</strong> (<em>str</em>) &ndash; A folder path containing files to import</p>
+</li>
 </ul>
-
-<h4 id="import-well-paths-well-path-files-none-well-path-folder">import_well_paths(well_path_files=None, well_path_folder=&ldquo;)</h4>
-
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A list of well path names (strings) that had logs imported</p>
+</li>
+</ul>
+<h4 id="import_well_pathswell_path_filesnone-well_path_folder">import_well_paths(well_path_files=None, well_path_folder=&rsquo;')</h4>
 <p>Import well paths into project</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>well_path_files</strong> (<em>list</em>) &ndash; List of file paths to import</p></li>
-
-<li><p><strong>well_path_folder</strong> (<em>str</em>) &ndash; A folder path containing files to import</p></li>
-</ul></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A list of well path names (strings)</p></li>
+<li>
+<p><strong>well_path_files</strong> (<em>list</em>) &ndash; List of file paths to import</p>
+</li>
+<li>
+<p><strong>well_path_folder</strong> (<em>str</em>) &ndash; A folder path containing files to import</p>
+</li>
+</ul>
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A list of well path names (strings)</p>
+</li>
 </ul>
-
 <p>Returns: a grid case group object</p>
-
-<h4 id="load-case-path">load_case(path)</h4>
-
+<h4 id="load_casepath">load_case(path)</h4>
 <p>Load a new case from the given file path</p>
-
-<h4 id="grid-case-groups-1">grid_case_groups()</h4>
-
+<h4 id="grid_case_groups-1">grid_case_groups()</h4>
 <p>Get a list of all grid case groups in the project</p>
-
 <pre><code>**path** (*str*) -- file path to case
 </code></pre>
-
 <ul>
-<li><p><strong>Parameters</strong></p></li>
-
-<li><p><strong>Returns</strong></p>
-
-<p>A rips Case object</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+</li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A rips Case object</p>
+</li>
 </ul>
-
-<h4 id="open-path">open(path)</h4>
-
+<h4 id="openpath">open(path)</h4>
 <p>Open a new project from the given path</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>path</strong> (<em>str</em>) &ndash; path to project file</p></li>
-
-<li><p><strong>Parameters</strong></p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>path</strong> (<em>str</em>) &ndash; path to project file</p>
+</li>
+<li>
+<p><strong>Parameters</strong></p>
+</li>
 </ul>
-
-<h4 id="plot-view-id">plot(view_id)</h4>
-
+<h4 id="plotview_id">plot(view_id)</h4>
 <p>Get a particular plot by providing view id
 :param view_id: view id
 :type view_id: int</p>
-
 <p>Returns: a plot object</p>
-
 <h4 id="plots">plots()</h4>
-
 <p>Get a list of all plots belonging to a project</p>
-
-<h4 id="replace-source-cases-grid-list-file-case-group-id-0">replace_source_cases(grid_list_file, case_group_id=0)</h4>
-
+<h4 id="replace_source_casesgrid_list_file-case_group_id0">replace_source_cases(grid_list_file, case_group_id=0)</h4>
 <p>Replace all source cases within a case group</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>grid_list_file</strong> (<em>str</em>) &ndash; path to file containing a list of cases</p></li>
-
-<li><p><strong>case_group_id</strong> (<em>int</em>) &ndash; id of the case group to replace</p></li>
-</ul></li>
+<li>
+<p><strong>grid_list_file</strong> (<em>str</em>) &ndash; path to file containing a list of cases</p>
+</li>
+<li>
+<p><strong>case_group_id</strong> (<em>int</em>) &ndash; id of the case group to replace</p>
+</li>
 </ul>
-
-<h4 id="save-path">save(path=&ldquo;)</h4>
-
+</li>
+</ul>
+<h4 id="savepath">save(path=&rsquo;')</h4>
 <p>Save the project to the existing project file, or to a new file
 :param path: File path to the file to save the project to. If empty, saves to the active project file
 :type path: str</p>
-
-<h4 id="scale-fracture-template-template-id-half-length-height-d-factor-conductivity">scale_fracture_template(template_id, half_length, height, d_factor, conductivity)</h4>
-
+<h4 id="scale_fracture_templatetemplate_id-half_length-height-d_factor-conductivity">scale_fracture_template(template_id, half_length, height, d_factor, conductivity)</h4>
 <p>Scale fracture template parameters</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>template_id</strong> (<em>int</em>) &ndash; ID of fracture template</p></li>
-
-<li><p><strong>half_length</strong> (<em>double</em>) &ndash; Half Length scale factor</p></li>
-
-<li><p><strong>height</strong> (<em>double</em>) &ndash; Height scale factor</p></li>
-
-<li><p><strong>d_factor</strong> (<em>double</em>) &ndash; D-factor scale factor</p></li>
-
-<li><p><strong>conductivity</strong> (<em>double</em>) &ndash; Conductivity scale factor</p></li>
-</ul></li>
+<li>
+<p><strong>template_id</strong> (<em>int</em>) &ndash; ID of fracture template</p>
+</li>
+<li>
+<p><strong>half_length</strong> (<em>double</em>) &ndash; Half Length scale factor</p>
+</li>
+<li>
+<p><strong>height</strong> (<em>double</em>) &ndash; Height scale factor</p>
+</li>
+<li>
+<p><strong>d_factor</strong> (<em>double</em>) &ndash; D-factor scale factor</p>
+</li>
+<li>
+<p><strong>conductivity</strong> (<em>double</em>) &ndash; Conductivity scale factor</p>
+</li>
 </ul>
-
-<h4 id="selected-cases">selected_cases()</h4>
-
+</li>
+</ul>
+<h4 id="selected_cases">selected_cases()</h4>
 <p>Get a list of all cases selected in the project tree</p>
-
 <ul>
-<li><p><strong>Returns</strong></p>
-
-<p>A list of rips Case objects</p></li>
+<li>
+<p><strong>Returns</strong></p>
+<p>A list of rips Case objects</p>
+</li>
 </ul>
-
-<h4 id="set-fracture-containment-template-id-top-layer-base-layer">set_fracture_containment(template_id, top_layer, base_layer)</h4>
-
+<h4 id="set_fracture_containmenttemplate_id-top_layer-base_layer">set_fracture_containment(template_id, top_layer, base_layer)</h4>
 <p>Set fracture template containment parameters</p>
-
-<h4 id="set-fracture-containment-template-id-top-layer-base-layer-1">set_fracture_containment(template_id, top_layer, base_layer)</h4>
-
+<h4 id="set_fracture_containmenttemplate_id-top_layer-base_layer-1">set_fracture_containment(template_id, top_layer, base_layer)</h4>
 <p>Set fracture template containment parameters</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>template_id</strong> (<em>int</em>) &ndash; ID of fracture template</p></li>
-
-<li><p><strong>top_layer</strong> (<em>int</em>) &ndash; Top layer containment</p></li>
-
-<li><p><strong>base_layer</strong> (<em>int</em>) &ndash; Base layer containment</p></li>
-</ul></li>
+<li>
+<p><strong>template_id</strong> (<em>int</em>) &ndash; ID of fracture template</p>
+</li>
+<li>
+<p><strong>top_layer</strong> (<em>int</em>) &ndash; Top layer containment</p>
+</li>
+<li>
+<p><strong>base_layer</strong> (<em>int</em>) &ndash; Base layer containment</p>
+</li>
 </ul>
-
-<h4 id="view-view-id-2">view(view_id)</h4>
-
+</li>
+</ul>
+<h4 id="viewview_id-2">view(view_id)</h4>
 <p>Get a particular view belonging to a case by providing view id</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>view_id</strong> (<em>int</em>) &ndash; view id</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>view_id</strong> (<em>int</em>) &ndash; view id</p>
+</li>
 </ul>
-
 <p>Returns: a view object</p>
-
 <h4 id="views-2">views()</h4>
-
 <p>Get a list of views belonging to a project</p>
-
-<h4 id="well-paths">well_paths()</h4>
-
+<h4 id="well_paths">well_paths()</h4>
 <p>Get a list of all the well path names in the project</p>
-
 <h1 id="view-module">View Module</h1>
-
-<h4 id="class-rips-view-view-pdm-object-project">class rips.view.View(pdm_object, project)</h4>
-
+<h4 id="class-ripsviewviewpdm_object-project">class rips.view.View(pdm_object, project)</h4>
 <p>ResInsight view class</p>
-
-<h4 id="view-id-1">view_id()</h4>
-
+<h4 id="view_id-1">view_id()</h4>
 <p>View Id corresponding to the View Id in ResInsight project.</p>
-
 <ul>
-<li><p><strong>Type</strong></p>
-
-<p>int</p></li>
+<li>
+<p><strong>Type</strong></p>
+<p>int</p>
+</li>
 </ul>
-
-<h4 id="apply-cell-result-result-type-result-variable">apply_cell_result(result_type, result_variable)</h4>
-
+<h4 id="apply_cell_resultresult_type-result_variable">apply_cell_result(result_type, result_variable)</h4>
 <p>Apply a regular cell result</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>result_type</strong> (<em>str</em>) &ndash; String representing the result category. The valid values are</p>
-
+<li>
+<p><strong>result_type</strong> (<em>str</em>) &ndash; String representing the result category. The valid values are</p>
 <ul>
 <li>DYNAMIC_NATIVE</li>
 <li>STATIC_NATIVE</li>
@@ -3744,16 +3382,16 @@ print (case.gridCount())
 <li>FORMATION_NAMES</li>
 <li>FLOW_DIAGNOSTICS</li>
 <li>INJECTION_FLOODING</li>
-</ul></li>
-
-<li><p><strong>result_variable</strong> (<em>str</em>) &ndash; String representing the result variable.</p></li>
-</ul></li>
 </ul>
-
-<h4 id="apply-flow-diagnostics-cell-result-result-variable-tof-selection-mode-flow-tr-by-selection-injectors-none-producers-none">apply_flow_diagnostics_cell_result(result_variable=&lsquo;TOF&rsquo;, selection_mode=&lsquo;FLOW_TR_BY_SELECTION&rsquo;, injectors=None, producers=None)</h4>
-
+</li>
+<li>
+<p><strong>result_variable</strong> (<em>str</em>) &ndash; String representing the result variable.</p>
+</li>
+</ul>
+</li>
+</ul>
+<h4 id="apply_flow_diagnostics_cell_resultresult_variabletof-selection_modeflow_tr_by_selection-injectorsnone-producersnone">apply_flow_diagnostics_cell_result(result_variable='TOF&rsquo;, selection_mode='FLOW_TR_BY_SELECTION&rsquo;, injectors=None, producers=None)</h4>
 <p>Apply a flow diagnostics cell result</p>
-
 <table>
 <thead>
 <tr>
@@ -3762,26 +3400,22 @@ print (case.gridCount())
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>result_variable</td>
 <td>String representing the result value</td>
 <td>String</td>
 </tr>
-
 <tr>
 <td>selection_mode</td>
 <td>String specifying which tracers to select</td>
 <td>String</td>
 </tr>
-
 <tr>
 <td>injectors</td>
 <td>List of injector names, used by &lsquo;FLOW_TR_BY_SELECTION&rsquo;</td>
 <td>String List</td>
 </tr>
-
 <tr>
 <td>producers</td>
 <td>List of injector names, used by &lsquo;FLOW_TR_BY_SELECTION&rsquo;</td>
@@ -3789,9 +3423,7 @@ print (case.gridCount())
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-compdat-export-1">Enum compdat_export</h5>
-
+<h5 id="enum-compdat_export-1">Enum compdat_export</h5>
 <table>
 <thead>
 <tr>
@@ -3799,56 +3431,41 @@ print (case.gridCount())
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>&ldquo;TOF&rdquo;</td>
 <td>Time of flight</td>
 </tr>
-
 <tr>
 <td>&ldquo;Fraction&rdquo;</td>
 <td>Fraction</td>
 </tr>
-
 <tr>
 <td>&ldquo;MaxFractionTracer&rdquo;</td>
 <td>Max Fraction Tracer</td>
 </tr>
-
 <tr>
 <td>&ldquo;Communication&rdquo;</td>
 <td>Communication</td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="background-color">background_color()</h4>
-
+<h4 id="background_color">background_color()</h4>
 <p>Get the current background color in the view</p>
-
 <h4 id="case">case()</h4>
-
 <p>Get the case the view belongs to</p>
-
 <h4 id="clone">clone()</h4>
-
 <p>Clone the current view</p>
-
-<h4 id="export-property-undefined-value-0-0">export_property(undefined_value=0.0)</h4>
-
+<h4 id="export_propertyundefined_value00">export_property(undefined_value=0.0)</h4>
 <p>Export the current Eclipse property from the view</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
-<p><strong>undefined_value</strong> (<em>double</em>) &ndash; Value to use for undefined values. Defaults to 0.0</p></li>
+<li>
+<p><strong>Parameters</strong></p>
+<p><strong>undefined_value</strong> (<em>double</em>) &ndash; Value to use for undefined values. Defaults to 0.0</p>
+</li>
 </ul>
-
-<h4 id="export-sim-well-fracture-completions-time-step-simulation-well-names-file-split-compdat-export">export_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export)</h4>
-
+<h4 id="export_sim_well_fracture_completionstime_step-simulation_well_names-file_split-compdat_export">export_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export)</h4>
 <p>Export fracture completions for simulation wells</p>
-
 <table>
 <thead>
 <tr>
@@ -3857,26 +3474,22 @@ print (case.gridCount())
 <th>Type</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>time_step</td>
 <td>Time step to export for</td>
 <td>Integer</td>
 </tr>
-
 <tr>
 <td>simulation_well_names</td>
 <td>List of simulation well names</td>
 <td>List</td>
 </tr>
-
 <tr>
 <td>file_split</td>
 <td>Controls how export data is split into files</td>
 <td>String enum</td>
 </tr>
-
 <tr>
 <td>compdat_export</td>
 <td>Compdat export type</td>
@@ -3884,9 +3497,7 @@ print (case.gridCount())
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-file-split-2">Enum file_split</h5>
-
+<h5 id="enum-file_split-2">Enum file_split</h5>
 <table>
 <thead>
 <tr>
@@ -3894,27 +3505,22 @@ print (case.gridCount())
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&ldquo;UNIFIED_FILE&rdquo; <b>Default Option</b></td>
+<td>&ldquo;UNIFIED_FILE&rdquo; <!-- raw HTML omitted -->Default Option<!-- raw HTML omitted --></td>
 <td>A single file with all transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL&rdquo;</td>
 <td>One file for each well transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE&rdquo;</td>
 <td>One file for each completion type for each well</td>
 </tr>
 </tbody>
 </table>
-
-<h5 id="enum-compdat-export-2">Enum compdat_export</h5>
-
+<h5 id="enum-compdat_export-2">Enum compdat_export</h5>
 <table>
 <thead>
 <tr>
@@ -3922,80 +3528,69 @@ print (case.gridCount())
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
-<td>&ldquo;TRANSMISSIBILITIES&rdquo;<b>Default Option</b></td>
+<td>&ldquo;TRANSMISSIBILITIES&quot;<!-- raw HTML omitted -->Default Option<!-- raw HTML omitted --></td>
 <td>Direct export of transmissibilities</td>
 </tr>
-
 <tr>
 <td>&ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS&rdquo;</td>
 <td>Include export of WPIMULT</td>
 </tr>
 </tbody>
 </table>
-
-<h4 id="export-snapshot-prefix-export-folder">export_snapshot(prefix=&ldquo;, export_folder=&ldquo;)</h4>
-
+<h4 id="export_snapshotprefix-export_folder">export_snapshot(prefix=&rsquo;', export_folder=&rsquo;')</h4>
 <p>Export snapshot for the current view</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p></li>
-
-<li><p><strong>export_folder</strong> (<em>str</em>) &ndash; The path to export to. By default will use the global export folder</p></li>
-</ul></li>
+<li>
+<p><strong>prefix</strong> (<em>str</em>) &ndash; Exported file name prefix</p>
+</li>
+<li>
+<p><strong>export_folder</strong> (<em>str</em>) &ndash; The path to export to. By default will use the global export folder</p>
+</li>
 </ul>
-
-<h4 id="export-visible-cells-export-keyword-fluxnum-visible-active-cells-value-1-hidden-active-cells-value-0-inactive-cells-value-0">export_visible_cells(export_keyword=&lsquo;FLUXNUM&rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0)</h4>
-
+</li>
+</ul>
+<h4 id="export_visible_cellsexport_keywordfluxnum-visible_active_cells_value1-hidden_active_cells_value0-inactive_cells_value0">export_visible_cells(export_keyword='FLUXNUM&rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0)</h4>
 <p>Export special properties for all visible cells.</p>
-
 <ul>
-<li><p><strong>Parameters</strong></p>
-
+<li>
+<p><strong>Parameters</strong></p>
 <ul>
-<li><p><strong>export_keyword</strong> (<em>string</em>) &ndash; The keyword to export.</p></li>
-
-<li><p><strong>Choices</strong> &ndash; &lsquo;FLUXNUM&rsquo; or &lsquo;MULTNUM&rsquo;. Default: &lsquo;FLUXNUM&rsquo;</p></li>
-
-<li><p><strong>visible_active_cells_value</strong> (<em>int</em>) &ndash; Value to export forvisible active cells. Default: 1</p></li>
-
-<li><p><strong>hidden_active_cells_value</strong> (<em>int</em>) &ndash; Value to export for hidden active cells. Default: 0</p></li>
-
-<li><p><strong>inactive_cells_value</strong> (<em>int</em>) &ndash; Value to export for inactive cells. Default: 0</p></li>
-</ul></li>
+<li>
+<p><strong>export_keyword</strong> (<em>string</em>) &ndash; The keyword to export.</p>
+</li>
+<li>
+<p><strong>Choices</strong> &ndash; &lsquo;FLUXNUM&rsquo; or &lsquo;MULTNUM&rsquo;. Default: &lsquo;FLUXNUM&rsquo;</p>
+</li>
+<li>
+<p><strong>visible_active_cells_value</strong> (<em>int</em>) &ndash; Value to export forvisible active cells. Default: 1</p>
+</li>
+<li>
+<p><strong>hidden_active_cells_value</strong> (<em>int</em>) &ndash; Value to export for hidden active cells. Default: 0</p>
+</li>
+<li>
+<p><strong>inactive_cells_value</strong> (<em>int</em>) &ndash; Value to export for inactive cells. Default: 0</p>
+</li>
 </ul>
-
-<h4 id="set-background-color-bgcolor">set_background_color(bgcolor)</h4>
-
+</li>
+</ul>
+<h4 id="set_background_colorbgcolor">set_background_color(bgcolor)</h4>
 <p>Set the background color in the view</p>
-
-<h4 id="set-cell-result">set_cell_result()</h4>
-
+<h4 id="set_cell_result">set_cell_result()</h4>
 <p>Retrieve the current cell results</p>
-
-<h4 id="set-show-grid-box-value">set_show_grid_box(value)</h4>
-
+<h4 id="set_show_grid_boxvalue">set_show_grid_box(value)</h4>
 <p>Set if the grid box is meant to be shown in the view</p>
-
-<h4 id="set-time-step-time-step">set_time_step(time_step)</h4>
-
+<h4 id="set_time_steptime_step">set_time_step(time_step)</h4>
 <p>Set the time step for current view</p>
-
-<h4 id="show-grid-box">show_grid_box()</h4>
-
+<h4 id="show_grid_box">show_grid_box()</h4>
 <p>Check if the grid box is meant to be shown in the view</p>
-
 <h2 id="synchronous-example">Synchronous Example</h2>
-
 <p>Read two properties, multiply them together and push the results back to ResInsight in a naïve way, by reading PORO into a list, then reading PERMX into a list, then multiplying them both in a resulting list and finally transferring back the list.</p>
-
 <p>This is slow and inefficient, but works.</p>
-
 <pre><code>import rips
 import time
 
@@ -4030,14 +3625,9 @@ end = time.time()
 print(&quot;Time elapsed: &quot;, end - start)
 print(&quot;Transferred all results back&quot;)
 view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')
-</code></pre>
-
-<h2 id="asynchronous-example">Asynchronous Example</h2>
-
+</code></pre><h2 id="asynchronous-example">Asynchronous Example</h2>
 <p>Read two properties at the same time chunk by chunk, multiply each chunk together and start transferring the result back to ResInsight as soon as the chunk is finished.</p>
-
 <p>This is far more efficient.</p>
-
 <pre><code>########################################################################################
 import rips
 import time
@@ -4071,7 +3661,6 @@ print(&quot;Transferred all results back&quot;)
 view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -4245,6 +3834,19 @@ view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -4255,6 +3857,9 @@ view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')
             
         
                     
+            
+        
+                    
                         
             
             
@@ -5405,20 +5010,20 @@ view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/search/index.html b/search/index.html
index 8697e9176c..0ce900e509 100644
--- a/search/index.html
+++ b/search/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Search :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1785,8 +1819,7 @@ if (!doNotTrack) {
 
 
 
-<!--- Uses html defined in /layouts/shortcodes/search.html--->
-
+<!-- raw HTML omitted -->
 <h2>Search for: <span id="search-title"></span></h2>
 <form action="/search/" method="GET" id="search-form">
     <input type="search" name="q" id="search-field" placeholder="Search">
@@ -1803,8 +1836,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/overview/"] = {
                 title:    "Overview",
-                content:  " User Interface ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\n3D Main Window Plot Main Window Switching Between the Two Main Windows The two main windows has a toolbar button each, that directly opens and raises the other window. Each of the windows can also be closed freely, but if both are closed, ResInsight exits.\nDocking Windows Each of the main windows has a central area and several docking windows surrounding it. The different docking windows can be managed from the Windows menu or directly using the local menu bar of the docking window.\n Project Tree \u0026ndash; contains all application objects in a tree structure. Property Editor \u0026ndash; displays all properties for the selected object in the Project Tree Process Monitor \u0026ndash; displays output from Octave when executing Octave scripts Result Info \u0026ndash; displays info for the selected object in the 3D scene Result Plot \u0026ndash; displays curves based on result values for the selected cells in the 3D scene Messages \u0026ndash; displays occasional info and warnings related to operations executed.  Result Info and Result Plot is described in detail in Result Inspection \nUse several Project Trees and Property Editors:  If you want to pin the property editor for a certain object, you can add a new Project Tree and Property Editor by using the command Windows-\u0026gt;New Project and Property View.\n\rToolbars A selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.\nManaging 3D Views and Plot Windows In the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.\nStandard window management for applying minimized, normal and maximized state is available in the upper right corner.\nCommands to arrange the windows in the standard ways are available from the Windows menu\n Tile Windows \u0026ndash; distribute all open view windows to fill available view widget space  The order of the tiled windows are determined by the window positions and the type of view at the time of running the tile command. The leftmost window are tiled first, then the next leftmost and so on. Master views are tiled before slave views.  Cascade Windows \u0026ndash; organize all open view windows slightly offset on top of each other Close All Windows \u0026ndash; close all open view windows  Editing 3D Views and Plot Windows Content Most of the settings and features of ResInsight is accessible through the Project Tree and the Property Editor. Selecting an item in the Project Tree activates the corresponding Window, and shows the item properties in the Property Editor available for editing.\nToggling a checkbox next to an item in the Project Tree will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. right-click menu commands are also available to do special operations on a selected set of items.\nHow to interact and manipulate the 3D model is described in Model Navigation\nCases and Their Types A Case in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.\nEclipse Cases The following Eclipse cases can be imported into ResInsight via the File-\u0026gt;Import-\u0026gt;Eclipse Cases menu, see Import Eclipse Cases:\nResult Case \nThis is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.\nInput Case \nThis Case type is based on a *.GRDECL file, or a part of an Eclipse Input file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files. Each of the Eclipse properties are listed as separate entities in the Project Tree, and can be renamed and exported. See Grid Import and Property Export \nStatistics Case \nThis is a Case type that belongs to a Grid Case Group and makes statistical calculations based on the source cases in the Grid Case Group. See Grid Case Groups and Statistics .\nSummary Case \nThis is the case type listed in the Plot Main Window, and represents an *.SMSPEC file. These Cases are available for Summary Plotting. See Summary Plots .\nGeomechanical cases There are only one type of geomechanical cases, namely the ABAQUS-odb case type. When ResInsight is compiled with ABAQUS-odb support, *.odb files can be imported by selecting the menu item: File-\u0026gt;Import-\u0026gt;Geo Mechanical Cases-\u0026gt; Import Geo Mechanical Model.\nThe geomechanical cases are sorted into its own folder in the project tree named Geomechanical Models as opposed to the Grid Models folder where the Eclipse cases and Grid Case Groups resides.\nSee Build Instructions on how to compile ResInsight with odb-support.\nGrid Case Groups A Grid Case Group is a group of Eclipse Result Cases with identical grids, but generally different active cells, initial values and results. These cases are called Source Cases. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See Grid Case Groups and Statistics .\nThe Project File and the Cache Directory ResInsight stores all the views and settings in a Project File with the extension: *.rsp. This file only contains references to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.\nStatistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named \u0026lt;ProjectFileName\u0026gt;_cache in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.\nThe *.rsp file is an XML file, and can be edited by any text editor.\n\n\r",
-                html:     "\n\n\u003ch3 id=\"user-interface\"\u003eUser Interface\u003c/h3\u003e\n\n\u003cp\u003eResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\u003c/p\u003e\n\n\u003ch4 id=\"3d-main-window\"\u003e3D Main Window\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightUIMediumSize.png\" alt=\"ResInsight User Interface\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"plot-main-window\"\u003ePlot Main Window\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightMainPlotMediumSize.png\" alt=\"ResInsight User Interface\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"switching-between-the-two-main-windows\"\u003eSwitching Between the Two Main Windows\u003c/h4\u003e\n\n\u003cp\u003eThe two main windows has a toolbar button each, that directly opens and raises the other window. \u003cimg src=\"https://resinsight.org/images/getting-started/3DWindow24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cimg src=\"https://resinsight.org/images/getting-started/PlotWindow24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\n\u003cp\u003eEach of the windows can also be closed freely, but if both are closed, ResInsight exits.\u003c/p\u003e\n\n\u003ch4 id=\"docking-windows\"\u003eDocking Windows\u003c/h4\u003e\n\n\u003cp\u003eEach of the main windows has a central area and several docking windows surrounding it. The different docking\nwindows can be managed from the \u003cstrong\u003eWindows\u003c/strong\u003e menu or directly using the local menu bar of the docking window.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eProject Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for the selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProcess Monitor\u003c/strong\u003e \u0026ndash; displays output from Octave when executing Octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Info\u003c/strong\u003e \u0026ndash; displays info for the selected object in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Plot\u003c/strong\u003e \u0026ndash; displays curves based on result values for the selected cells in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMessages\u003c/strong\u003e \u0026ndash; displays occasional info and warnings related to operations executed.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eResult Info and Result Plot is described in detail in \u003ca href=\"/3d-main-window/resultinspection/\"\u003e Result Inspection \u003c/a\u003e\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cb\u003eUse several Project Trees and Property Editors: \u003c/b\u003e\nIf you want to pin the property editor for a certain object, you can add\na new Project Tree and Property Editor by using the command \u003cb\u003eWindows-\u0026gt;New Project and Property View\u003c/b\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"toolbars\"\u003eToolbars\u003c/h3\u003e\n\n\u003cp\u003eA selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.\u003c/p\u003e\n\n\u003ch4 id=\"managing-3d-views-and-plot-windows\"\u003eManaging 3D Views and Plot Windows\u003c/h4\u003e\n\n\u003cp\u003eIn the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.\u003c/p\u003e\n\n\u003cp\u003eStandard window management for applying minimized, normal and maximized state is available in the upper right corner.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/RestoreDown.PNG\" alt=\"Restore Down\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eCommands to arrange the windows in the standard ways are available from the \u003cstrong\u003eWindows\u003c/strong\u003e menu\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTile Windows\u003c/strong\u003e \u0026ndash; distribute all open view windows to fill available view widget space\n\n\u003cul\u003e\n\u003cli\u003eThe order of the tiled windows are determined by the window positions and the type of view at the time of running the tile command. The leftmost window are tiled first, then the next leftmost and so on. Master views are tiled before slave views.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCascade Windows\u003c/strong\u003e \u0026ndash; organize all open view windows slightly offset on top of each other\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eClose All Windows\u003c/strong\u003e \u0026ndash; close all open view windows\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"editing-3d-views-and-plot-windows-content\"\u003eEditing 3D Views and Plot Windows Content\u003c/h4\u003e\n\n\u003cp\u003eMost of the settings and features of ResInsight is accessible through the \u003cstrong\u003eProject Tree\u003c/strong\u003e and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Selecting an item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e activates the corresponding Window, and shows the item properties in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e available for editing.\u003c/p\u003e\n\n\u003cp\u003eToggling a checkbox next to an item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. \u003cimg src=\"https://resinsight.org/images/getting-started/TreeViewToggle.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\n\u003cp\u003eright-click menu commands are also available to do special operations on a selected set of items.\u003c/p\u003e\n\n\u003cp\u003eHow to interact and manipulate the 3D model is described in \u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"cases-and-their-types\"\u003eCases and Their Types\u003c/h3\u003e\n\n\u003cp\u003eA \u003cem\u003eCase\u003c/em\u003e in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.\u003c/p\u003e\n\n\u003ch4 id=\"eclipse-cases\"\u003eEclipse Cases\u003c/h4\u003e\n\n\u003cp\u003eThe following Eclipse cases can be imported into ResInsight via the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases\u003c/strong\u003e menu,\nsee \u003ca href=\"/import/eclipsecases/\"\u003eImport Eclipse Cases\u003c/a\u003e:\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eResult Case \u003cimg src=\"https://resinsight.org/images/getting-started/Case24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eThis is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eInput Case \u003cimg src=\"https://resinsight.org/images/getting-started/EclipseInput24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eThis Case type is based on a \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e file, or a part of an Eclipse \u003cem\u003eInput\u003c/em\u003e file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.\nEach of the Eclipse properties are listed as separate entities in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and can be renamed and exported.\nSee \u003ca href=\"/import/eclipsecases/\"\u003e Grid Import and Property Export \u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eStatistics Case \u003cimg src=\"https://resinsight.org/images/getting-started/Histogram24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eThis is a Case type that belongs to a \u003cem\u003eGrid Case Group\u003c/em\u003e and makes statistical calculations based on the source cases in the Grid Case Group. See \u003ca href=\"/3d-main-window/casegroupsandstatistics/\"\u003e Grid Case Groups and Statistics \u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eSummary Case \u003cimg src=\"https://resinsight.org/images/getting-started/SummaryCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eThis is the case type listed in the Plot Main Window, and represents an \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e file. These Cases are available for Summary Plotting. See \u003ca href=\"/plot-window/summaryplots/\"\u003e Summary Plots \u003c/a\u003e.\u003c/p\u003e\n\n\u003ch4 id=\"geomechanical-cases\"\u003eGeomechanical cases\u003c/h4\u003e\n\n\u003cp\u003eThere are only one type of geomechanical \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\n cases, namely the ABAQUS-odb case type.\nWhen ResInsight is compiled with ABAQUS-odb support, \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e files can be imported by selecting the menu item:\n\u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Geo Mechanical Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Geo Mechanical Model\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe geomechanical cases are sorted into its own folder in the project tree named \u003cstrong\u003eGeomechanical Models\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCases24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n as opposed to the \u003cstrong\u003eGrid Models\u003c/strong\u003e folder where the Eclipse cases and \u003cstrong\u003eGrid Case Groups\u003c/strong\u003e resides.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e on how to compile ResInsight with odb-support.\u003c/p\u003e\n\n\u003ch4 id=\"grid-case-groups\"\u003eGrid Case Groups\u003c/h4\u003e\n\n\u003cp\u003eA \u003cstrong\u003eGrid Case Group\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/getting-started/GridCaseGroup24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n is a group of Eclipse \u003cstrong\u003eResult Cases\u003c/strong\u003e with identical grids, but generally different active cells, initial values and results. These cases are called \u003cem\u003eSource Cases\u003c/em\u003e. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See \u003ca href=\"/3d-main-window/casegroupsandstatistics/\"\u003e Grid Case Groups and Statistics \u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"the-project-file-and-the-cache-directory\"\u003eThe Project File and the Cache Directory\u003c/h3\u003e\n\n\u003cp\u003eResInsight stores all the views and settings in a Project File with the extension: \u003cem\u003e\u003ccode\u003e*.rsp\u003c/code\u003e\u003c/em\u003e.\nThis file only contains \u003cem\u003ereferences\u003c/em\u003e to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.\u003c/p\u003e\n\n\u003cp\u003eStatistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named \u003cem\u003e\u003ccode\u003e\u0026lt;ProjectFileName\u0026gt;_cache\u003c/code\u003e\u003c/em\u003e in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe \u003ccode\u003e*.rsp\u003c/code\u003e file is an XML file, and can be edited by any text editor.\u003cbr /\u003e\n\u003c/div\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
+                content:  "User Interface ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\n3D Main Window Plot Main Window Switching Between the Two Main Windows The two main windows has a toolbar button each, that directly opens and raises the other window. Each of the windows can also be closed freely, but if both are closed, ResInsight exits.\nDocking Windows Each of the main windows has a central area and several docking windows surrounding it. The different docking windows can be managed from the Windows menu or directly using the local menu bar of the docking window.\n Project Tree \u0026ndash; contains all application objects in a tree structure. Property Editor \u0026ndash; displays all properties for the selected object in the Project Tree Process Monitor \u0026ndash; displays output from Octave when executing Octave scripts Result Info \u0026ndash; displays info for the selected object in the 3D scene Result Plot \u0026ndash; displays curves based on result values for the selected cells in the 3D scene Messages \u0026ndash; displays occasional info and warnings related to operations executed.  Result Info and Result Plot is described in detail in Result Inspection \nUse several Project Trees and Property Editors: If you want to pin the property editor for a certain object, you can add a new Project Tree and Property Editor by using the command Windows-\u0026gt;New Project and Property View.\n\rToolbars A selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.\nManaging 3D Views and Plot Windows In the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.\nStandard window management for applying minimized, normal and maximized state is available in the upper right corner.\nCommands to arrange the windows in the standard ways are available from the Windows menu\n Tile Windows \u0026ndash; distribute all open view windows to fill available view widget space  The order of the tiled windows are determined by the window positions and the type of view at the time of running the tile command. The leftmost window are tiled first, then the next leftmost and so on. Master views are tiled before slave views.   Cascade Windows \u0026ndash; organize all open view windows slightly offset on top of each other Close All Windows \u0026ndash; close all open view windows  Editing 3D Views and Plot Windows Content Most of the settings and features of ResInsight is accessible through the Project Tree and the Property Editor. Selecting an item in the Project Tree activates the corresponding Window, and shows the item properties in the Property Editor available for editing.\nToggling a checkbox next to an item in the Project Tree will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. right-click menu commands are also available to do special operations on a selected set of items.\nHow to interact and manipulate the 3D model is described in Model Navigation\nCases and Their Types A Case in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.\nEclipse Cases The following Eclipse cases can be imported into ResInsight via the File-\u0026gt;Import-\u0026gt;Eclipse Cases menu, see Import Eclipse Cases:\nResult Case \nThis is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.\nInput Case \nThis Case type is based on a *.GRDECL file, or a part of an Eclipse Input file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files. Each of the Eclipse properties are listed as separate entities in the Project Tree, and can be renamed and exported. See Grid Import and Property Export \nStatistics Case \nThis is a Case type that belongs to a Grid Case Group and makes statistical calculations based on the source cases in the Grid Case Group. See Grid Case Groups and Statistics .\nSummary Case \nThis is the case type listed in the Plot Main Window, and represents an *.SMSPEC file. These Cases are available for Summary Plotting. See Summary Plots .\nGeomechanical cases There are only one type of geomechanical cases, namely the ABAQUS-odb case type. When ResInsight is compiled with ABAQUS-odb support, *.odb files can be imported by selecting the menu item: File-\u0026gt;Import-\u0026gt;Geo Mechanical Cases-\u0026gt; Import Geo Mechanical Model.\nThe geomechanical cases are sorted into its own folder in the project tree named Geomechanical Models as opposed to the Grid Models folder where the Eclipse cases and Grid Case Groups resides.\nSee Build Instructions on how to compile ResInsight with odb-support.\nGrid Case Groups A Grid Case Group is a group of Eclipse Result Cases with identical grids, but generally different active cells, initial values and results. These cases are called Source Cases. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See Grid Case Groups and Statistics .\nThe Project File and the Cache Directory ResInsight stores all the views and settings in a Project File with the extension: *.rsp. This file only contains references to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.\nStatistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named \u0026lt;ProjectFileName\u0026gt;_cache in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.\nThe *.rspfile is an XML file, and can be edited by any text editor.\n\r",
+                html:     "\u003ch3 id=\"user-interface\"\u003eUser Interface\u003c/h3\u003e\n\u003cp\u003eResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots.\u003c/p\u003e\n\u003ch4 id=\"3d-main-window\"\u003e3D Main Window\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightUIMediumSize.png\" alt=\"ResInsight User Interface\"\u003e\u003c/p\u003e\n\u003ch4 id=\"plot-main-window\"\u003ePlot Main Window\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightMainPlotMediumSize.png\" alt=\"ResInsight User Interface\"\u003e\u003c/p\u003e\n\u003ch4 id=\"switching-between-the-two-main-windows\"\u003eSwitching Between the Two Main Windows\u003c/h4\u003e\n\u003cp\u003eThe two main windows has a toolbar button each, that directly opens and raises the other window. \u003cimg src=\"https://resinsight.org/images/getting-started/3DWindow24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cimg src=\"https://resinsight.org/images/getting-started/PlotWindow24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003cp\u003eEach of the windows can also be closed freely, but if both are closed, ResInsight exits.\u003c/p\u003e\n\u003ch4 id=\"docking-windows\"\u003eDocking Windows\u003c/h4\u003e\n\u003cp\u003eEach of the main windows has a central area and several docking windows surrounding it. The different docking \nwindows can be managed from the \u003cstrong\u003eWindows\u003c/strong\u003e menu or directly using the local menu bar of the docking window.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eProject Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for the selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProcess Monitor\u003c/strong\u003e \u0026ndash; displays output from Octave when executing Octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Info\u003c/strong\u003e \u0026ndash; displays info for the selected object in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Plot\u003c/strong\u003e \u0026ndash; displays curves based on result values for the selected cells in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMessages\u003c/strong\u003e \u0026ndash; displays occasional info and warnings related to operations executed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eResult Info and Result Plot is described in detail in \u003ca href=\"/3d-main-window/resultinspection/\"\u003e Result Inspection \u003c/a\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eUse several Project Trees and Property Editors: \u003c!-- raw HTML omitted --\u003e\nIf you want to pin the property editor for a certain object, you can add \na new Project Tree and Property Editor by using the command \u003c!-- raw HTML omitted --\u003eWindows-\u0026gt;New Project and Property View\u003c!-- raw HTML omitted --\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"toolbars\"\u003eToolbars\u003c/h3\u003e\n\u003cp\u003eA selected subset of actions are presented as controls in the toolbar. The different sections in the toolbar can be dragged and positioned anywhere as small floating toolbars. Management of the toolbar is done by right-clicking on the toolbar and then manipulating the displayed menu.\u003c/p\u003e\n\u003ch4 id=\"managing-3d-views-and-plot-windows\"\u003eManaging 3D Views and Plot Windows\u003c/h4\u003e\n\u003cp\u003eIn the main area of the application, several 3D views or plot windows can be open at the same time. One of them will be active and the active view can be either maximized to use the whole main area, or restored so that you can see the open windows.\u003c/p\u003e\n\u003cp\u003eStandard window management for applying minimized, normal and maximized state is available in the upper right corner.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/RestoreDown.PNG\" alt=\"Restore Down\"\u003e\u003c/p\u003e\n\u003cp\u003eCommands to arrange the windows in the standard ways are available from the \u003cstrong\u003eWindows\u003c/strong\u003e menu\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTile Windows\u003c/strong\u003e \u0026ndash; distribute all open view windows to fill available view widget space\n\u003cul\u003e\n\u003cli\u003eThe order of the tiled windows are determined by the window positions and the type of view at the time of running the tile command. The leftmost window are tiled first, then the next leftmost and so on. Master views are tiled before slave views.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCascade Windows\u003c/strong\u003e \u0026ndash; organize all open view windows slightly offset on top of each other\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eClose All Windows\u003c/strong\u003e \u0026ndash; close all open view windows\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"editing-3d-views-and-plot-windows-content\"\u003eEditing 3D Views and Plot Windows Content\u003c/h4\u003e\n\u003cp\u003eMost of the settings and features of ResInsight is accessible through the \u003cstrong\u003eProject Tree\u003c/strong\u003e and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Selecting an item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e activates the corresponding Window, and shows the item properties in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e available for editing.\u003c/p\u003e\n\u003cp\u003eToggling a checkbox next to an item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e will toggle visibility in the window. Toggling a checkbox for a collection of items will affect the visibility for all items in the collection. \u003cimg src=\"https://resinsight.org/images/getting-started/TreeViewToggle.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003cp\u003eright-click menu commands are also available to do special operations on a selected set of items.\u003c/p\u003e\n\u003cp\u003eHow to interact and manipulate the 3D model is described in \u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"cases-and-their-types\"\u003eCases and Their Types\u003c/h3\u003e\n\u003cp\u003eA \u003cem\u003eCase\u003c/em\u003e in ResInsight means a Grid model with a particular set of results or property data. There are three different types of Eclipse cases and one type of Geomechanical cases.\u003c/p\u003e\n\u003ch4 id=\"eclipse-cases\"\u003eEclipse Cases\u003c/h4\u003e\n\u003cp\u003eThe following Eclipse cases can be imported into ResInsight via the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases\u003c/strong\u003e menu, \nsee \u003ca href=\"/import/eclipsecases/\"\u003eImport Eclipse Cases\u003c/a\u003e:\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResult Case \u003cimg src=\"https://resinsight.org/images/getting-started/Case24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis is a Case based on the results of an Eclipse simulation, read from a grid file together with static and restart data. Multiple Cases can be selected and read from a folder.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eInput Case \u003cimg src=\"https://resinsight.org/images/getting-started/EclipseInput24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis Case type is based on a \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e file, or a part of an Eclipse \u003cem\u003eInput\u003c/em\u003e file. This Case type supports loading single ASCII files defining Eclipse Cell Properties, and also to export modified property sets to ASCII files.\nEach of the Eclipse properties are listed as separate entities in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and can be renamed and exported.\nSee \u003ca href=\"/import/eclipsecases/\"\u003e Grid Import and Property Export \u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eStatistics Case \u003cimg src=\"https://resinsight.org/images/getting-started/Histogram24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis is a Case type that belongs to a \u003cem\u003eGrid Case Group\u003c/em\u003e and makes statistical calculations based on the source cases in the Grid Case Group. See \u003ca href=\"/3d-main-window/casegroupsandstatistics/\"\u003e Grid Case Groups and Statistics \u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSummary Case \u003cimg src=\"https://resinsight.org/images/getting-started/SummaryCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis is the case type listed in the Plot Main Window, and represents an \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e file. These Cases are available for Summary Plotting. See \u003ca href=\"/plot-window/summaryplots/\"\u003e Summary Plots \u003c/a\u003e.\u003c/p\u003e\n\u003ch4 id=\"geomechanical-cases\"\u003eGeomechanical cases\u003c/h4\u003e\n\u003cp\u003eThere are only one type of geomechanical \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\ncases, namely the ABAQUS-odb case type. \nWhen ResInsight is compiled with ABAQUS-odb support, \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e files can be imported by selecting the menu item:\n\u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Geo Mechanical Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCase24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Geo Mechanical Model\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe geomechanical cases are sorted into its own folder in the project tree named \u003cstrong\u003eGeomechanical Models\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/getting-started/GeoMechCases24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n as opposed to the \u003cstrong\u003eGrid Models\u003c/strong\u003e folder where the Eclipse cases and \u003cstrong\u003eGrid Case Groups\u003c/strong\u003e resides.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e on how to compile ResInsight with odb-support.\u003c/p\u003e\n\u003ch4 id=\"grid-case-groups\"\u003eGrid Case Groups\u003c/h4\u003e\n\u003cp\u003eA \u003cstrong\u003eGrid Case Group\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/getting-started/GridCaseGroup24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n is a group of Eclipse \u003cstrong\u003eResult Cases\u003c/strong\u003e with identical grids, but generally different active cells, initial values and results. These cases are called \u003cem\u003eSource Cases\u003c/em\u003e. The purpose of a Grid Case group is to make it easy to calculate statistics across the source cases both for static and dynamic Eclipse Properties. See \u003ca href=\"/3d-main-window/casegroupsandstatistics/\"\u003e Grid Case Groups and Statistics \u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"the-project-file-and-the-cache-directory\"\u003eThe Project File and the Cache Directory\u003c/h3\u003e\n\u003cp\u003eResInsight stores all the views and settings in a Project File with the extension: \u003cem\u003e\u003ccode\u003e*.rsp\u003c/code\u003e\u003c/em\u003e.\nThis file only contains \u003cem\u003ereferences\u003c/em\u003e to the real data files, and does not in any way copy the data itself. Data files generated by ResInsight are also referenced from the Project File.\u003c/p\u003e\n\u003cp\u003eStatistics calculations, octave generated property sets, and SSI-hub imported well paths are saved to a folder named \u003cem\u003e\u003ccode\u003e\u0026lt;ProjectFileName\u0026gt;_cache\u003c/code\u003e\u003c/em\u003e in the same directory as the project file. If you need to move your project, make sure you move this folder along. If you do not, the calculations or well path import needs to be done again.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe \u003c!-- raw HTML omitted --\u003e*.rsp\u003c!-- raw HTML omitted --\u003e file is an XML file, and can be edited by any text editor.\u003c/p\u003e\n\u003c!-- raw HTML omitted --\u003e\n\u003c/div\u003e\r\n\n",
                 url:      "/getting-started/overview/"
             };
         
@@ -1812,8 +1845,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/3dviews/"] = {
                 title:    "3D Views",
-                content:  " 3D Views are the windows displaying the Grid Models. The visualization is controlled by the Project Tree item representing the View and their sub items.\nEach item has a set of properties that can be edited in the Property Editor.\nSeveral views can be added to the same case by right-clicking the case or a view and select New View. You can also Copy and then Paste a view into a Case. All the settings are then copied to the new view.\nViews of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.\nCommon view features View properties Grid appearance can be controlled from the Property Editor when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.\nVisibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using Show Grid Box.\nCell Result The Cell Result item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the Cell Result item. The mapping between cell values and color is defined by the Legend Definitionalong with some appearance settings on the Legend itself. (Number format etc.)\nPlease refer to Result Color Legend for details.\nRange Filters and Property Filters In order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to Cell Filters to read more about them.\nInfo Box The Info Box controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.\nThe Animation Progress shows which time step you are viewing.\nThe Info Text shows general info about the case, the selected results, and some statistics. Mobile Volume Weighted Mean is the mean of the current Cell Property weighted by the Mobile pore volume. Mobile pore volume is defined in every cell as: MULTPV * PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.\nThe Histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\n The mean value ( a blue line ) P10 and P90 ( red lines )  Statistics Options  Statistics Time Range \u0026ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.\n Statistics Cell Range \u0026ndash; controls if visible cells or all active cells is included when statistics is computed.  The Info Box settings can be activated by clicking on the Info Text in the 3D view.\n\rGrids The Grids node contains child nodes for Main Grid, LGRs and Temporary LGRs where each grid\u0026rsquo;s visibilty can be controlled. The LGRs node contains all LGRs loaded from file, while Temporary LGRs contains all temporary LGRs (see Completions LGR). Toggling Grids off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called Hide grid cells.\nIntersections Intersections are used to cut the geometry and show result values mapped onto this geometry. Please refer to Intersections for details.\nActivate items by clicking Selected overlay items in the 3D view can activate a corresponding item in the Property Editor. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.\nEclipse features Cell Edge Results The Cell Edge Result visualization mode is one of ResInsight\u0026rsquo;s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values different from 1.0 along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.\nResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.\nWhen selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the Legend Definition item belonging to the Cell Edge Result item.\nSelect Custom Edge Result to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The Custom Edge Result can either be a static or dynamic result.\nSeparate Fault Result Default result mapping on faults is using the result specified in Cell Result. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the Property Editor. A second legend for the fault result is added to the view.\nSimulation Wells This item controls the visualization of the Eclipse simulation wells. Please refer to Simulation Wells to read more.\nWell Connection Factors This item controls the visualization of well connection factors. See Visualization and Inspection of Well Connection Factors for details.\nFractures This item controls the visualization of fractures. See Fractures for details.\nFaults Visualization of the faults in the model is controlled by this item. Please refer to Faults to read more.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DViewOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e3D Views are the windows displaying the Grid Models. The visualization is controlled by the \u003cstrong\u003eProject Tree\u003c/strong\u003e item representing the \u003cstrong\u003eView\u003c/strong\u003e and their sub items.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEach item has a set of properties that can be edited in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eSeveral views can be added to the same case by right-clicking the case or a view and select \u003cstrong\u003eNew View\u003c/strong\u003e. You can also \u003cstrong\u003eCopy\u003c/strong\u003e and then \u003cstrong\u003ePaste\u003c/strong\u003e a view into a Case. All the settings are then copied to the new view.\u003c/p\u003e\n\n\u003cp\u003eViews of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.\u003c/p\u003e\n\n\u003ch2 id=\"common-view-features\"\u003eCommon view features\u003c/h2\u003e\n\n\u003ch3 id=\"view-properties\"\u003eView properties\u003c/h3\u003e\n\n\u003cp\u003eGrid appearance can be controlled from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eVisibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using \u003cstrong\u003eShow Grid Box\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"cell-result\"\u003eCell Result\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eCell Result\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the \u003cstrong\u003eCell Result\u003c/strong\u003e item. The mapping between cell values and color is defined by the \u003cstrong\u003eLegend Definition\u003c/strong\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/Legend.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n along with some appearance settings on the Legend itself. (Number format etc.)\u003c/p\u003e\n\n\u003cp\u003ePlease refer to \u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e for details.\u003c/p\u003e\n\n\u003ch3 id=\"range-filters-and-property-filters\"\u003eRange Filters and Property Filters\u003c/h3\u003e\n\n\u003cp\u003eIn order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to \u003ca href=\"/3d-main-window/filters/\"\u003eCell Filters\u003c/a\u003e to read more about them.\u003c/p\u003e\n\n\u003ch3 id=\"info-box\"\u003eInfo Box\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eInfo Box\u003c/strong\u003e controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eAnimation Progress\u003c/strong\u003e shows which time step you are viewing.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AnimationProgress.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eInfo Text\u003c/strong\u003e shows general info about the case, the selected results, and some statistics. \u003cstrong\u003eMobile Volume Weighted Mean\u003c/strong\u003e is the mean of the current \u003cstrong\u003eCell Property\u003c/strong\u003e weighted by the \u003cstrong\u003eMobile pore volume\u003c/strong\u003e. Mobile pore volume is defined in every cell as: MULTPV \u003cem\u003e*\u003c/em\u003e PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/infoBox.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eHistogram\u003c/strong\u003e shows a histogram of the complete time series of the currently loaded \u003cstrong\u003eCell Result\u003c/strong\u003e together with:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe mean value ( a blue line )\u003c/li\u003e\n\u003cli\u003eP10 and P90 ( red lines )\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/HistogramExample.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"statistics-options\"\u003eStatistics Options\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Time Range\u003c/strong\u003e \u0026ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Cell Range\u003c/strong\u003e \u0026ndash; controls if visible cells or all active cells is included when statistics is computed.\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe \u003cb\u003eInfo Box\u003c/b\u003e settings can be activated by clicking on the Info Text in the 3D view.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"grids\"\u003eGrids\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewTreeGrids.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eGrids\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_meshlines_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n node contains child nodes for \u003cstrong\u003eMain Grid\u003c/strong\u003e, \u003cstrong\u003eLGRs\u003c/strong\u003e and \u003cstrong\u003eTemporary LGRs\u003c/strong\u003e where each grid\u0026rsquo;s visibilty can be controlled. The \u003cstrong\u003eLGRs\u003c/strong\u003e node contains all LGRs loaded from file, while \u003cstrong\u003eTemporary LGRs\u003c/strong\u003e contains all temporary LGRs (see \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e).\nToggling \u003cstrong\u003eGrids\u003c/strong\u003e off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called \u003cem\u003eHide grid cells\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"intersections\"\u003eIntersections\u003c/h3\u003e\n\n\u003cp\u003eIntersections \u003cimg src=\"https://resinsight.org/images/3d-main-window/CrossSections16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n are used to cut the geometry and show result values mapped onto this geometry.\nPlease refer to \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e for details.\u003c/p\u003e\n\n\u003ch3 id=\"activate-items-by-clicking\"\u003eActivate items by clicking\u003c/h3\u003e\n\n\u003cp\u003eSelected overlay items in the 3D view can activate a corresponding item in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.\u003c/p\u003e\n\n\u003ch2 id=\"eclipse-features\"\u003eEclipse features\u003c/h2\u003e\n\n\u003ch3 id=\"cell-edge-results\"\u003eCell Edge Results\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellEdgeExample.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eCell Edge Result\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/EdgeResult_1.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n visualization mode is one of ResInsight\u0026rsquo;s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values \u003cem\u003edifferent from 1.0\u003c/em\u003e along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.\u003c/p\u003e\n\n\u003cp\u003eResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.\u003c/p\u003e\n\n\u003cp\u003eWhen selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the \u003cstrong\u003eLegend Definition\u003c/strong\u003e item belonging to the \u003cstrong\u003eCell Edge Result\u003c/strong\u003e item.\u003c/p\u003e\n\n\u003cp\u003eSelect \u003cstrong\u003eCustom Edge Result\u003c/strong\u003e to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The \u003cstrong\u003eCustom Edge Result\u003c/strong\u003e can either be a static or dynamic result.\u003c/p\u003e\n\n\u003ch3 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h3\u003e\n\n\u003cp\u003eDefault result mapping on faults is using the result specified in \u003cstrong\u003eCell Result\u003c/strong\u003e. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. A second legend for the fault result is added to the view.\u003c/p\u003e\n\n\u003ch3 id=\"simulation-wells\"\u003eSimulation Wells\u003c/h3\u003e\n\n\u003cp\u003eThis item controls the visualization of the Eclipse simulation wells.\nPlease refer to \u003ca href=\"/wells-and-completions/simulationwells/\"\u003eSimulation Wells\u003c/a\u003e to read more.\u003c/p\u003e\n\n\u003ch3 id=\"well-connection-factors\"\u003eWell Connection Factors\u003c/h3\u003e\n\n\u003cp\u003eThis item controls the visualization of well connection factors.\nSee \u003ca href=\"/wells-and-completions/completions/#visualization-and-inspection-of-well-connection-factors\"\u003eVisualization and Inspection of Well Connection Factors\u003c/a\u003e for details.\u003c/p\u003e\n\n\u003ch3 id=\"fractures\"\u003eFractures\u003c/h3\u003e\n\n\u003cp\u003eThis item controls the visualization of fractures.\nSee \u003ca href=\"/wells-and-completions/completions/#fractures\"\u003eFractures\u003c/a\u003e for details.\u003c/p\u003e\n\n\u003ch3 id=\"faults\"\u003eFaults\u003c/h3\u003e\n\n\u003cp\u003eVisualization of the faults in the model is controlled by this item.\nPlease refer to \u003ca href=\"/3d-main-window/faults/\"\u003eFaults\u003c/a\u003e to read more.\u003c/p\u003e\n",
+                content:  "3D Views are the windows displaying the Grid Models. The visualization is controlled by the Project Tree item representing the View and their sub items.\nEach item has a set of properties that can be edited in the Property Editor.\nSeveral views can be added to the same case by right-clicking the case or a view and select New View. You can also Copy and then Paste a view into a Case. All the settings are then copied to the new view.\nViews of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.\nCommon view features View properties Grid appearance can be controlled from the Property Editor when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.\nVisibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using Show Grid Box.\nCell Result The Cell Result item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the Cell Result item. The mapping between cell values and color is defined by the Legend Definitionalong with some appearance settings on the Legend itself. (Number format etc.)\nPlease refer to Result Color Legend for details.\nRange Filters and Property Filters In order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to Cell Filters to read more about them.\nInfo Box The Info Box controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.\nThe Animation Progress shows which time step you are viewing.\nThe Info Text shows general info about the case, the selected results, and some statistics. Mobile Volume Weighted Mean is the mean of the current Cell Property weighted by the Mobile pore volume. Mobile pore volume is defined in every cell as: MULTPV * PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.\nThe Histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\n The mean value ( a blue line ) P10 and P90 ( red lines )  Statistics Options  Statistics Time Range \u0026ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option. Statistics Cell Range \u0026ndash; controls if visible cells or all active cells is included when statistics is computed.  The Info Boxsettings can be activated by clicking on the Info Text in the 3D view.\n\rGrids The Grids node contains child nodes for Main Grid, LGRs and Temporary LGRs where each grid\u0026rsquo;s visibilty can be controlled. The LGRs node contains all LGRs loaded from file, while Temporary LGRs contains all temporary LGRs (see Completions LGR). Toggling Grids off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called Hide grid cells.\nIntersections Intersections are used to cut the geometry and show result values mapped onto this geometry. Please refer to Intersections for details.\nActivate items by clicking Selected overlay items in the 3D view can activate a corresponding item in the Property Editor. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.\nEclipse features Cell Edge Results The Cell Edge Result visualization mode is one of ResInsight\u0026rsquo;s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values different from 1.0 along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.\nResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.\nWhen selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the Legend Definition item belonging to the Cell Edge Result item.\nSelect Custom Edge Result to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The Custom Edge Result can either be a static or dynamic result.\nSeparate Fault Result Default result mapping on faults is using the result specified in Cell Result. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the Property Editor. A second legend for the fault result is added to the view.\nSimulation Wells This item controls the visualization of the Eclipse simulation wells. Please refer to Simulation Wells to read more.\nWell Connection Factors This item controls the visualization of well connection factors. See Visualization and Inspection of Well Connection Factors for details.\nFractures This item controls the visualization of fractures. See Fractures for details.\nFaults Visualization of the faults in the model is controlled by this item. Please refer to Faults to read more.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DViewOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e3D Views are the windows displaying the Grid Models. The visualization is controlled by the \u003cstrong\u003eProject Tree\u003c/strong\u003e item representing the \u003cstrong\u003eView\u003c/strong\u003e and their sub items.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEach item has a set of properties that can be edited in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eSeveral views can be added to the same case by right-clicking the case or a view and select \u003cstrong\u003eNew View\u003c/strong\u003e. You can also \u003cstrong\u003eCopy\u003c/strong\u003e and then \u003cstrong\u003ePaste\u003c/strong\u003e a view into a Case. All the settings are then copied to the new view.\u003c/p\u003e\n\u003cp\u003eViews of Eclipse models and Geomechanical models has a lot in common, but Eclipse views has some features that applies to Eclipse simulations only.\u003c/p\u003e\n\u003ch2 id=\"common-view-features\"\u003eCommon view features\u003c/h2\u003e\n\u003ch3 id=\"view-properties\"\u003eView properties\u003c/h3\u003e\n\u003cp\u003eGrid appearance can be controlled from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e when a view is selected. This includes background color and z scaling. In addition, cell visibility controls of inactive and invalid cells.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eVisibility of the grid box with labels displaying the coordinates for the reservoir can also be controlled using \u003cstrong\u003eShow Grid Box\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"cell-result\"\u003eCell Result\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eCell Result\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n item defines which Eclipse or Geomechanical property the 3D View uses for the main cell color. The property can be chosen in the property panel of the \u003cstrong\u003eCell Result\u003c/strong\u003e item. The mapping between cell values and color is defined by the \u003cstrong\u003eLegend Definition\u003c/strong\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/Legend.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n along with some appearance settings on the Legend itself. (Number format etc.)\u003c/p\u003e\n\u003cp\u003ePlease refer to \u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e for details.\u003c/p\u003e\n\u003ch3 id=\"range-filters-and-property-filters\"\u003eRange Filters and Property Filters\u003c/h3\u003e\n\u003cp\u003eIn order to see different sets of cells, and cells inside the reservoir, Views use cell filters. Please refer to \u003ca href=\"/3d-main-window/filters/\"\u003eCell Filters\u003c/a\u003e to read more about them.\u003c/p\u003e\n\u003ch3 id=\"info-box\"\u003eInfo Box\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eInfo Box\u003c/strong\u003e controls the visibility of the animation progress, the Case description box, and the results histogram displayed in the top right corner of the view.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eAnimation Progress\u003c/strong\u003e shows which time step you are viewing.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AnimationProgress.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eInfo Text\u003c/strong\u003e shows general info about the case, the selected results, and some statistics. \u003cstrong\u003eMobile Volume Weighted Mean\u003c/strong\u003e is the mean of the current \u003cstrong\u003eCell Property\u003c/strong\u003e weighted by the \u003cstrong\u003eMobile pore volume\u003c/strong\u003e. Mobile pore volume is defined in every cell as: MULTPV \u003cem\u003e*\u003c/em\u003e PORV(1-SWCR). If MULTPV data is not present, it is ignored in the equation. The same applies to SWCR data.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/infoBox.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eHistogram\u003c/strong\u003e shows a histogram of the complete time series of the currently loaded \u003cstrong\u003eCell Result\u003c/strong\u003e together with:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe mean value ( a blue line )\u003c/li\u003e\n\u003cli\u003eP10 and P90 ( red lines )\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/HistogramExample.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"statistics-options\"\u003eStatistics Options\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Time Range\u003c/strong\u003e \u0026ndash; controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Cell Range\u003c/strong\u003e \u0026ndash; controls if visible cells or all active cells is included when statistics is computed.\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe \u003c!-- raw HTML omitted --\u003eInfo Box\u003c!-- raw HTML omitted --\u003e settings can be activated by clicking on the Info Text in the 3D view.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"grids\"\u003eGrids\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ViewTreeGrids.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eGrids\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_meshlines_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n node contains child nodes for \u003cstrong\u003eMain Grid\u003c/strong\u003e, \u003cstrong\u003eLGRs\u003c/strong\u003e and \u003cstrong\u003eTemporary LGRs\u003c/strong\u003e where each grid\u0026rsquo;s visibilty can be controlled. The \u003cstrong\u003eLGRs\u003c/strong\u003e node contains all LGRs loaded from file, while \u003cstrong\u003eTemporary LGRs\u003c/strong\u003e contains all temporary LGRs (see \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e).\nToggling \u003cstrong\u003eGrids\u003c/strong\u003e off will hide all grids cell geometry. This option is used to display geometry for faults and intersections. This feature is also available as a toolbutton called \u003cem\u003eHide grid cells\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"intersections\"\u003eIntersections\u003c/h3\u003e\n\u003cp\u003eIntersections \u003cimg src=\"https://resinsight.org/images/3d-main-window/CrossSections16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n are used to cut the geometry and show result values mapped onto this geometry.\nPlease refer to \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e for details.\u003c/p\u003e\n\u003ch3 id=\"activate-items-by-clicking\"\u003eActivate items by clicking\u003c/h3\u003e\n\u003cp\u003eSelected overlay items in the 3D view can activate a corresponding item in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. This is implemented for Info box and result color legends. Please note that this feature is activated by clicking inside the texture/colored part of the legend.\u003c/p\u003e\n\u003ch2 id=\"eclipse-features\"\u003eEclipse features\u003c/h2\u003e\n\u003ch3 id=\"cell-edge-results\"\u003eCell Edge Results\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellEdgeExample.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eCell Edge Result\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/3d-main-window/EdgeResult_1.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n visualization mode is one of ResInsight\u0026rsquo;s special features. Its main use is to show the MULT(X, Y, Z) properties at the same time. This will show the MULT property values \u003cem\u003edifferent from 1.0\u003c/em\u003e along the correct edges of the cells. In effect this highlights the faults and makes it easy to verify all the MULT values in one go.\u003c/p\u003e\n\u003cp\u003eResInsight supports all properties ending with X, Y, Z and X-, Y-, Z-. However, it is only the MULT property that ignores values of 1.0.\u003c/p\u003e\n\u003cp\u003eWhen selecting a result variable for cell edge, a second legend shows up in the 3D view showing the variation in values for this second property. Color legend management is available when selecting the \u003cstrong\u003eLegend Definition\u003c/strong\u003e item belonging to the \u003cstrong\u003eCell Edge Result\u003c/strong\u003e item.\u003c/p\u003e\n\u003cp\u003eSelect \u003cstrong\u003eCustom Edge Result\u003c/strong\u003e to specify one cell result to be mapped onto all cell edges. This way two cell results can easily be compared and visualized in the same view. The \u003cstrong\u003eCustom Edge Result\u003c/strong\u003e can either be a static or dynamic result.\u003c/p\u003e\n\u003ch3 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h3\u003e\n\u003cp\u003eDefault result mapping on faults is using the result specified in \u003cstrong\u003eCell Result\u003c/strong\u003e. If a different result mapping is wanted, enable the checkbox and select the result from the result selection dialog in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. A second legend for the fault result is added to the view.\u003c/p\u003e\n\u003ch3 id=\"simulation-wells\"\u003eSimulation Wells\u003c/h3\u003e\n\u003cp\u003eThis item controls the visualization of the Eclipse simulation wells.\nPlease refer to \u003ca href=\"/wells-and-completions/simulationwells/\"\u003eSimulation Wells\u003c/a\u003e to read more.\u003c/p\u003e\n\u003ch3 id=\"well-connection-factors\"\u003eWell Connection Factors\u003c/h3\u003e\n\u003cp\u003eThis item controls the visualization of well connection factors.\nSee \u003ca href=\"/wells-and-completions/completions/#visualization-and-inspection-of-well-connection-factors\"\u003eVisualization and Inspection of Well Connection Factors\u003c/a\u003e for details.\u003c/p\u003e\n\u003ch3 id=\"fractures\"\u003eFractures\u003c/h3\u003e\n\u003cp\u003eThis item controls the visualization of fractures.\nSee \u003ca href=\"/wells-and-completions/completions/#fractures\"\u003eFractures\u003c/a\u003e for details.\u003c/p\u003e\n\u003ch3 id=\"faults\"\u003eFaults\u003c/h3\u003e\n\u003cp\u003eVisualization of the faults in the model is controlled by this item. \nPlease refer to \u003ca href=\"/3d-main-window/faults/\"\u003eFaults\u003c/a\u003e to read more.\u003c/p\u003e\n",
                 url:      "/3d-main-window/3dviews/"
             };
         
@@ -1821,8 +1854,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/"] = {
                 title:    "Download and Install",
-                content:  " Installation See the following for common install procedures and options:\n Linux Installation \n Windows Installation \n  See Build Instructions  for the complete list of configuration options including support for Octave plugins, ABAQUS ODB API, and HDF5.\nWhat\u0026rsquo;s new ResInsight is under continuous development targeting two major releases per year. For an overview of some of its new and exciting features, see the following:\n ResInsight 2019.12.1 \n ResInsight 2019.12 \n ResInsight 2019.08 \n ResInsight 2019.04 \n ResInsight 2018.11 \n  Sign up to be notified of new releases \nFor the complete list of releases and updates, please visit ResInsight on Github.\n",
-                html:     "\n\n\u003ch2 id=\"installation\"\u003eInstallation\u003c/h2\u003e\n\n\u003cp\u003eSee the following for common install procedures and options:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/download-and-install/linux-installation/\"\u003e Linux Installation \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/download-and-install/windows-installation/\"\u003e Windows Installation \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSee \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003e Build Instructions \u003c/a\u003e for the complete list of configuration options including support for\nOctave plugins, ABAQUS ODB API, and HDF5.\u003c/p\u003e\n\n\u003ch2 id=\"what-s-new\"\u003eWhat\u0026rsquo;s new\u003c/h2\u003e\n\n\u003cp\u003eResInsight is under continuous development targeting two major releases per year.\nFor an overview of some of its new and exciting features, see the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_12_1/\"\u003e ResInsight 2019.12.1 \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_12/\"\u003e ResInsight 2019.12 \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_08/\"\u003e ResInsight 2019.08 \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_04/\"\u003e ResInsight 2019.04 \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2018_11/\"\u003e ResInsight 2018.11 \u003c/a\u003e\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003ca href=\"/getting-started/other/releasenotification/\"\u003e Sign up to be notified of new releases \u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003eFor the complete list of releases and updates, please visit \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eResInsight on Github\u003c/a\u003e.\u003c/p\u003e\n",
+                content:  "Installation See the following for common install procedures and options:\n  Linux Installation \n  Windows Installation \n  See Build Instructions  for the complete list of configuration options including support for Octave plugins, ABAQUS ODB API, and HDF5.\nWhat\u0026rsquo;s new ResInsight is under continuous development targeting two major releases per year. For an overview of some of its new and exciting features, see the following:\n  ResInsight 2019.12.1 \n  ResInsight 2019.12 \n  ResInsight 2019.08 \n  ResInsight 2019.04 \n  ResInsight 2018.11 \n  Sign up to be notified of new releases \nFor the complete list of releases and updates, please visit ResInsight on Github.\n",
+                html:     "\u003ch2 id=\"installation\"\u003eInstallation\u003c/h2\u003e\n\u003cp\u003eSee the following for common install procedures and options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/download-and-install/linux-installation/\"\u003e Linux Installation \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/download-and-install/windows-installation/\"\u003e Windows Installation \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003e Build Instructions \u003c/a\u003e for the complete list of configuration options including support for \nOctave plugins, ABAQUS ODB API, and HDF5.\u003c/p\u003e\n\u003ch2 id=\"whats-new\"\u003eWhat\u0026rsquo;s new\u003c/h2\u003e\n\u003cp\u003eResInsight is under continuous development targeting two major releases per year. \nFor an overview of some of its new and exciting features, see the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_12_1/\"\u003e ResInsight 2019.12.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_12/\"\u003e ResInsight 2019.12 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_08/\"\u003e ResInsight 2019.08 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2019_04/\"\u003e ResInsight 2019.04 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2018_11/\"\u003e ResInsight 2018.11 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/other/releasenotification/\"\u003e Sign up to be notified of new releases \u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor the complete list of releases and updates, please visit \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eResInsight on Github\u003c/a\u003e.\u003c/p\u003e\n",
                 url:      "/getting-started/download-and-install/"
             };
         
@@ -1830,8 +1863,8 @@ if (!doNotTrack) {
          
             window.store["/import/eclipsecases/"] = {
                 title:    "Eclipse Cases",
-                content:  " ResInsight supports the following type of Eclipse input data:\n *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. Grid and Property data from *.GRDECL files.  Release 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.\n\rEclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-\u0026gt;Import-\u0026gt;Eclipse Cases menu:\n Import Eclipse Case: Brings up the standard file selection dialog. Select *.EGRID or *.GRID Eclipse files for import. Multiple selections are allowed. Import Eclipse Cases Recursively: Brings up the recursive file selection dialog. This dialog is described in detail on the Summary Plots page. Import Eclipse Case (Time Step Filtered): See description Import Input Eclipse Case: See description Create Grid Case Group from Files and Create Grid Case Group from Files Recursively: These commands import a number of Eclipse files and places the cases in a grid case group. The only difference between the two commands, is the dialog used to select files. The recursive version is using the recursive file selection dialog and is considered the new way of selecting files.  The Reload Case command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.\nYou can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).\n\rResult Index File If enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named \u0026lt;casename\u0026gt;.RESINSIGHT_IDX See Preferences: Behavior When Loading Data\nTime Step Filtered Eclipse Result Some Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.\nSelect File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; Import Eclipse Case (Time Step Filtered) and select an *.EGRID or *.GRID Eclipse file for import. A dialog will appear.\nFiltering can be done by adjusting the following parameters: * First and last time step * Step filter type and with step interval size\nFirst and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.\nFilter Type is set to All by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to All is to skip time steps in a number of Days, Weeks, Months, Quarters or Years. The skipping interval is set in the text field below. After editing the Interval field, press tab to update the Filtered Time Steps preview, or click anywhere in the dialog. Click Ok to import when the filter is ready.\nFiltering can also be done after import, in a case\u0026rsquo;s Property Window.\nAfter clicking Reload Case, the time steps in the toolbar will be updated.\nEclipse ASCII Input Data  Select File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; Import Input Eclipse Case and select a *.GRDECL file. The case is imported, and a view of the case is created Right-click the Input Properties in the generated Input Case and use the right-click menu to import additional Eclipse Property data files.  Handling Missing or Wrong MAPAXES The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the Property Editor for all Eclipse Case types as the toggle buttons Flip X Axis and Flip Y Axis as shown in the example below.\n",
-                html:     "\n\n\u003cp\u003eResInsight supports the following type of Eclipse input data:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eGrid and Property data from  \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files.\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eRelease 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"eclipse-results\"\u003eEclipse Results\u003c/h3\u003e\n\n\u003cp\u003eResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases\u003c/strong\u003e menu:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Case\u003c/strong\u003e: Brings up the standard file selection dialog. Select \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e or \u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e Eclipse files for import. Multiple selections are allowed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Cases Recursively\u003c/strong\u003e: Brings up the recursive file selection dialog. This dialog is described in detail on the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Case (Time Step Filtered)\u003c/strong\u003e: See \u003ca href=\"#time-step-filtered-eclipse-result\"\u003edescription\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Input Eclipse Case\u003c/strong\u003e: See \u003ca href=\"#eclipse-ascii-input-data\"\u003edescription\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Grid Case Group from Files\u003c/strong\u003e and \u003cstrong\u003eCreate Grid Case Group from Files Recursively\u003c/strong\u003e: These commands import a number of Eclipse files and places the cases in a \u003ca href=\"/3d-main-window/casegroupsandstatistics/#creating-grid-case-groups\"\u003egrid case group\u003c/a\u003e. The only difference between the two commands, is the dialog used to select files. The recursive version is using the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003erecursive file selection dialog\u003c/a\u003e and is considered the new way of selecting files.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eReload Case\u003c/strong\u003e command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eYou can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"result-index-file\"\u003eResult Index File\u003c/h4\u003e\n\n\u003cp\u003eIf enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named \u003cem\u003e\u003ccode\u003e\u0026lt;casename\u0026gt;.RESINSIGHT_IDX\u003c/code\u003e\u003c/em\u003e\nSee \u003ca href=\"/misc/preferences/#behavior-when-loading-data\"\u003ePreferences: Behavior When Loading Data\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"time-step-filtered-eclipse-result\"\u003eTime Step Filtered Eclipse Result\u003c/h3\u003e\n\n\u003cp\u003eSome Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.\u003c/p\u003e\n\n\u003cp\u003eSelect \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/Case24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Eclipse Case (Time Step Filtered)\u003c/strong\u003e and select an \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e or \u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e Eclipse file for import. A dialog will appear.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/timeStepFilter.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFiltering can be done by adjusting the following parameters:\n* First and last time step\n* Step filter type and with step interval size\u003c/p\u003e\n\n\u003cp\u003eFirst and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eFilter Type\u003c/strong\u003e is set to \u003cem\u003eAll\u003c/em\u003e by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to \u003cem\u003eAll\u003c/em\u003e is to skip time steps in a number of \u003cem\u003eDays\u003c/em\u003e, \u003cem\u003eWeeks\u003c/em\u003e, \u003cem\u003eMonths\u003c/em\u003e, \u003cem\u003eQuarters\u003c/em\u003e or \u003cem\u003eYears\u003c/em\u003e. The skipping interval is set in the text field below. After editing the \u003cstrong\u003eInterval\u003c/strong\u003e field, press \u003cem\u003etab\u003c/em\u003e to update the \u003cstrong\u003eFiltered Time Steps\u003c/strong\u003e preview, or click anywhere in the dialog. Click \u003cem\u003eOk\u003c/em\u003e to import when the filter is ready.\u003c/p\u003e\n\n\u003cp\u003eFiltering can also be done after import, in a case\u0026rsquo;s \u003cstrong\u003eProperty Window\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/timeStepFilterPropEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAfter clicking \u003cem\u003eReload Case\u003c/em\u003e, the time steps in the toolbar will be updated.\u003c/p\u003e\n\n\u003ch3 id=\"eclipse-ascii-input-data\"\u003eEclipse ASCII Input Data\u003c/h3\u003e\n\n\u003col\u003e\n\u003cli\u003eSelect \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/EclipseInput24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Input Eclipse Case\u003c/strong\u003e and select a \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e file.\u003c/li\u003e\n\u003cli\u003eThe case is imported, and a view of the case is created\u003c/li\u003e\n\u003cli\u003eRight-click the \u003cstrong\u003eInput Properties\u003c/strong\u003e in the generated \u003cstrong\u003eInput Case\u003c/strong\u003e and use the right-click menu to import additional Eclipse Property data files.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003ch3 id=\"handling-missing-or-wrong-mapaxes\"\u003eHandling Missing or Wrong MAPAXES\u003c/h3\u003e\n\n\u003cp\u003eThe X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for all Eclipse Case types as the toggle buttons \u003cstrong\u003eFlip X Axis\u003c/strong\u003e and \u003cstrong\u003eFlip Y Axis\u003c/strong\u003e as shown in the example below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/getting-started/CaseProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "ResInsight supports the following type of Eclipse input data:\n *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. Grid and Property data from *.GRDECL files.  Release 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.\n\rEclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-\u0026gt;Import-\u0026gt;Eclipse Cases menu:\n Import Eclipse Case: Brings up the standard file selection dialog. Select *.EGRID or *.GRID Eclipse files for import. Multiple selections are allowed. Import Eclipse Cases Recursively: Brings up the recursive file selection dialog. This dialog is described in detail on the Summary Plots page. Import Eclipse Case (Time Step Filtered): See description Import Input Eclipse Case: See description Create Grid Case Group from Files and Create Grid Case Group from Files Recursively: These commands import a number of Eclipse files and places the cases in a grid case group. The only difference between the two commands, is the dialog used to select files. The recursive version is using the recursive file selection dialog and is considered the new way of selecting files.  The Reload Case command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.\nYou can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).\n\rResult Index File If enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named \u0026lt;casename\u0026gt;.RESINSIGHT_IDX See Preferences: Behavior When Loading Data\nTime Step Filtered Eclipse Result Some Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.\nSelect File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; Import Eclipse Case (Time Step Filtered) and select an *.EGRID or *.GRID Eclipse file for import. A dialog will appear.\nFiltering can be done by adjusting the following parameters:\n First and last time step Step filter type and with step interval size  First and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.\nFilter Type is set to All by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to All is to skip time steps in a number of Days, Weeks, Months, Quarters or Years. The skipping interval is set in the text field below. After editing the Interval field, press tab to update the Filtered Time Steps preview, or click anywhere in the dialog. Click Ok to import when the filter is ready.\nFiltering can also be done after import, in a case\u0026rsquo;s Property Window.\nAfter clicking Reload Case, the time steps in the toolbar will be updated.\nEclipse ASCII Input Data  Select File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; Import Input Eclipse Case and select a *.GRDECL file. The case is imported, and a view of the case is created Right-click the Input Properties in the generated Input Case and use the right-click menu to import additional Eclipse Property data files.  Handling Missing or Wrong MAPAXES The X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the Property Editor for all Eclipse Case types as the toggle buttons Flip X Axis and Flip Y Axis as shown in the example below.\n",
+                html:     "\u003cp\u003eResInsight supports the following type of Eclipse input data:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eGrid and Property data from  \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files.\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eRelease 2018.11 supports import of simulations from Intersect. To be able to import into ResInsight, the Intersect simulation must be exported into Eclipse file format.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"eclipse-results\"\u003eEclipse Results\u003c/h3\u003e\n\u003cp\u003eResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases\u003c/strong\u003e menu:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Case\u003c/strong\u003e: Brings up the standard file selection dialog. Select \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e or \u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e Eclipse files for import. Multiple selections are allowed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Cases Recursively\u003c/strong\u003e: Brings up the recursive file selection dialog. This dialog is described in detail on the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Eclipse Case (Time Step Filtered)\u003c/strong\u003e: See \u003ca href=\"#time-step-filtered-eclipse-result\"\u003edescription\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Input Eclipse Case\u003c/strong\u003e: See \u003ca href=\"#eclipse-ascii-input-data\"\u003edescription\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Grid Case Group from Files\u003c/strong\u003e and \u003cstrong\u003eCreate Grid Case Group from Files Recursively\u003c/strong\u003e: These commands import a number of Eclipse files and places the cases in a \u003ca href=\"/3d-main-window/casegroupsandstatistics/#creating-grid-case-groups\"\u003egrid case group\u003c/a\u003e. The only difference between the two commands, is the dialog used to select files. The recursive version is using the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003erecursive file selection dialog\u003c/a\u003e and is considered the new way of selecting files.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe \u003cstrong\u003eReload Case\u003c/strong\u003e command can be used to reload a previously imported case, to make sure it is up to date. This is useful if the grid or result files changes while a ResInsight session is active.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eYou can select several grid files in one go by multiple selection of files (Ctrl + left mouse button, Shift + left mouse button).\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"result-index-file\"\u003eResult Index File\u003c/h4\u003e\n\u003cp\u003eIf enabled, ResInsight will generate an index file when reading the eclipse result files for the first time. This file will significantly reduce the time used to open the case next time. The file is named \u003cem\u003e\u003ccode\u003e\u0026lt;casename\u0026gt;.RESINSIGHT_IDX\u003c/code\u003e\u003c/em\u003e\nSee \u003ca href=\"/misc/preferences/#behavior-when-loading-data\"\u003ePreferences: Behavior When Loading Data\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"time-step-filtered-eclipse-result\"\u003eTime Step Filtered Eclipse Result\u003c/h3\u003e\n\u003cp\u003eSome Eclipse files have an enormous amount of time steps. If only a selection of the time steps really are needed for the session, the time steps can be filtered before loading. This can possibly speed up the import a great deal. Filtering can be done in the following way.\u003c/p\u003e\n\u003cp\u003eSelect \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/Case24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Eclipse Case (Time Step Filtered)\u003c/strong\u003e and select an \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e or \u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e Eclipse file for import. A dialog will appear.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/timeStepFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFiltering can be done by adjusting the following parameters:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eFirst and last time step\u003c/li\u003e\n\u003cli\u003eStep filter type and with step interval size\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFirst and last time step to include in the import can be chosen in their respective drop down list. All time steps found in the file are included in both lists.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eFilter Type\u003c/strong\u003e is set to \u003cem\u003eAll\u003c/em\u003e by default. This means that all time steps between the first and last chosen time step will be imported. The alternative to \u003cem\u003eAll\u003c/em\u003e is to skip time steps in a number of \u003cem\u003eDays\u003c/em\u003e, \u003cem\u003eWeeks\u003c/em\u003e, \u003cem\u003eMonths\u003c/em\u003e, \u003cem\u003eQuarters\u003c/em\u003e or \u003cem\u003eYears\u003c/em\u003e. The skipping interval is set in the text field below. After editing the \u003cstrong\u003eInterval\u003c/strong\u003e field, press \u003cem\u003etab\u003c/em\u003e to update the \u003cstrong\u003eFiltered Time Steps\u003c/strong\u003e preview, or click anywhere in the dialog. Click \u003cem\u003eOk\u003c/em\u003e to import when the filter is ready.\u003c/p\u003e\n\u003cp\u003eFiltering can also be done after import, in a case\u0026rsquo;s \u003cstrong\u003eProperty Window\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/timeStepFilterPropEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAfter clicking \u003cem\u003eReload Case\u003c/em\u003e, the time steps in the toolbar will be updated.\u003c/p\u003e\n\u003ch3 id=\"eclipse-ascii-input-data\"\u003eEclipse ASCII Input Data\u003c/h3\u003e\n\u003col\u003e\n\u003cli\u003eSelect \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt; \u003cimg src=\"https://resinsight.org/images/getting-started/EclipseInput24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Import Input Eclipse Case\u003c/strong\u003e and select a \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e file.\u003c/li\u003e\n\u003cli\u003eThe case is imported, and a view of the case is created\u003c/li\u003e\n\u003cli\u003eRight-click the \u003cstrong\u003eInput Properties\u003c/strong\u003e in the generated \u003cstrong\u003eInput Case\u003c/strong\u003e and use the right-click menu to import additional Eclipse Property data files.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch3 id=\"handling-missing-or-wrong-mapaxes\"\u003eHandling Missing or Wrong MAPAXES\u003c/h3\u003e\n\u003cp\u003eThe X and Y grid data can be negated in order to make the Grid model appear correctly in ResInsight. This functionality is accessible in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for all Eclipse Case types as the toggle buttons \u003cstrong\u003eFlip X Axis\u003c/strong\u003e and \u003cstrong\u003eFlip Y Axis\u003c/strong\u003e as shown in the example below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/CaseProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/import/eclipsecases/"
             };
         
@@ -1839,8 +1872,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/"] = {
                 title:    "Getting Started",
-                content:  "ResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations. This chapter provides an overview of its functionality and installation.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/usingResinsight.png\" alt=\"Using ResInsight\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations.\nThis chapter provides an overview of its functionality and installation.\u003c/p\u003e\n",
+                content:  "ResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations. This chapter provides an overview of its functionality and installation.\nResInsight Documentation Overview  resinsight.org - Documentation for latest stable release api.resinsight.org - Documentation of Python API beta.resinsight.org - Latest documentation (not yet released)  ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/usingResinsight.png\" alt=\"Using ResInsight\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight is a powerful open source, cross-platform 3D visualization, curve plotting, and post processing tool for reservoir models and simulations. \nThis chapter provides an overview of its functionality and installation.\u003c/p\u003e\n\u003ch2 id=\"resinsight-documentation-overview\"\u003eResInsight Documentation Overview\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://resinsight.org/\"\u003eresinsight.org\u003c/a\u003e - Documentation for latest stable release\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://api.resinsight.org/\"\u003eapi.resinsight.org\u003c/a\u003e - Documentation of Python API\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"http://beta.resinsight.org\"\u003ebeta.resinsight.org\u003c/a\u003e - Latest documentation (not yet released)\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/getting-started/"
             };
         
@@ -1848,8 +1881,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/linux-installation/"] = {
                 title:    "Linux Installation",
-                content:  " Install ResInsight From Binary Packages on Linux Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.\n\rRed Hat Enterprise Linux 6 or 7 Login as root and do:\nyum-config-manager --add-repo https://opm-project.org/package/opm.repo yum install resinsight yum install resinsight-octave  Then you are good, and can start ResInsight by typing: ResInsight\nUbuntu Linux 16.04-64bit On the command line do:\nsudo apt-get update sudo apt-get install software-properties-common sudo apt-add-repository ppa:opm/ppa sudo apt-get update sudo apt-get install resinsight sudo apt-get install octave-resinsight  Start ResInsight by typing : ResInsight\nFor further installation details, see the ResInsight distribution on Opm Project Downloading and Installing.\n\rThe binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see Build Instructions.\n\rFrom downloaded tarball  Download TAR.GZ binary distribution from https://github.com/OPM/ResInsight/releases Extract content from TAR file Start ./ResInsight  Display Menu Icons in GNOME (Optional) By default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :\ngconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true  This fix was taken from reply number 11 in this thread\nSetup Octave Interface (optional)  Install Octave directly from the package manager in Linux. See the documentation for your particular distribution. Launch ResInsight, open Edit-\u0026gt;Preferences Enter the path to the Octave command line interpreter executable octave-cli (for older version of octave use octave)  The precompiled octave interface distributed in the tarball is only tested for RedHat 6. It is not expected to work for other configurations. (ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)\nIf you need the octave interface to work on a different OS, you need to build ResInsight yourself.\nSee Build Instructions\n\rWorkaround for crash using Virtual Box Uncheck Settings-\u0026gt;Display-\u0026gt;Enable 3D Acceleration. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.\nHere is a pointer addressing the issue with Virtual Box, this is not testes by us:\nhttps://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\n",
-                html:     "\n\n\u003ch2 id=\"install-resinsight\"\u003eInstall ResInsight\u003c/h2\u003e\n\n\u003ch3 id=\"from-binary-packages-on-linux\"\u003eFrom Binary Packages on Linux\u003c/h3\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003ePlease not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"red-hat-enterprise-linux-6-or-7\"\u003eRed Hat Enterprise Linux 6 or 7\u003c/h4\u003e\n\n\u003cp\u003eLogin as root and do:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eyum-config-manager --add-repo https://opm-project.org/package/opm.repo\nyum install resinsight\nyum install resinsight-octave\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThen you are good, and can start ResInsight by typing: ResInsight\u003c/p\u003e\n\n\u003ch4 id=\"ubuntu-linux-16-04-64bit\"\u003eUbuntu Linux 16.04-64bit\u003c/h4\u003e\n\n\u003cp\u003eOn the command line do:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003esudo apt-get update\nsudo apt-get install software-properties-common\nsudo apt-add-repository ppa:opm/ppa\nsudo apt-get update\nsudo apt-get install resinsight\nsudo apt-get install octave-resinsight\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eStart ResInsight by typing : \u003ccode\u003eResInsight\u003c/code\u003e\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eFor further installation details, see the ResInsight distribution on \u003ca href=\"http://opm-project.org/?page_id=36\"\u003eOpm Project Downloading and Installing\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see\n\u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"from-downloaded-tarball\"\u003eFrom downloaded tarball\u003c/h3\u003e\n\n\u003col\u003e\n\u003cli\u003eDownload TAR.GZ binary distribution from \u003ca href=\"https://github.com/OPM/ResInsight/releases\" title=\"release section on GitHub\"\u003ehttps://github.com/OPM/ResInsight/releases\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExtract content from TAR file\u003c/li\u003e\n\u003cli\u003eStart ./ResInsight\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003ch4 id=\"display-menu-icons-in-gnome-optional\"\u003eDisplay Menu Icons in GNOME (Optional)\u003c/h4\u003e\n\n\u003cp\u003eBy default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003egconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true\ngconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThis fix was taken from reply number 11 in this \u003ca href=\"https://bbs.archlinux.org/viewtopic.php?id=117414\"\u003ethread\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"setup-octave-interface-optional\"\u003eSetup Octave Interface (optional)\u003c/h2\u003e\n\n\u003col\u003e\n\u003cli\u003eInstall Octave directly from the package manager in Linux. See the documentation for your particular distribution.\u003c/li\u003e\n\u003cli\u003eLaunch ResInsight, open \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eEnter the path to the Octave command line interpreter executable \u003ccode\u003eoctave-cli\u003c/code\u003e (for older version of octave use \u003ccode\u003eoctave\u003c/code\u003e)\u003c/li\u003e\n\u003c/ol\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe precompiled octave interface distributed in the tarball is only tested for RedHat 6. \u003cbr\u003e\nIt is \u003cb\u003enot\u003c/b\u003e expected to work for other configurations.\n(ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)\u003cbr\u003e\n\u003cbr\u003e\nIf you need the octave interface to work on a different OS, you need to build ResInsight yourself.\u003cbr\u003e\nSee \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"workaround-for-crash-using-virtual-box\"\u003eWorkaround for crash using Virtual Box\u003c/h2\u003e\n\n\u003cp\u003eUncheck \u003cstrong\u003eSettings-\u0026gt;Display-\u0026gt;Enable 3D Acceleration\u003c/strong\u003e. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.\u003c/p\u003e\n\n\u003cp\u003eHere is a pointer addressing the issue with Virtual Box, this is not testes by us:\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"https://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\"\u003ehttps://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "Install ResInsight From Binary Packages on Linux Please not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.\n\rRed Hat Enterprise Linux 6 or 7 Login as root and do:\nyum-config-manager --add-repo https://opm-project.org/package/opm.repo\ryum install resinsight\ryum install resinsight-octave\r Then you are good, and can start ResInsight by typing: ResInsight\nUbuntu Linux 16.04-64bit On the command line do:\nsudo apt-get update\rsudo apt-get install software-properties-common\rsudo apt-add-repository ppa:opm/ppa\rsudo apt-get update\rsudo apt-get install resinsight\rsudo apt-get install octave-resinsight\r Start ResInsight by typing : ResInsight\nFor further installation details, see the ResInsight distribution on Opm Project Downloading and Installing.\n\rThe binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see Build Instructions.\n\rFrom downloaded tarball  Download TAR.GZ binary distribution from https://github.com/OPM/ResInsight/releases Extract content from TAR file Start ./ResInsight  Display Menu Icons in GNOME (Optional) By default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :\ngconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true\rgconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true\rThis fix was taken from reply number 11 in this thread\nSetup Octave Interface (optional)  Install Octave directly from the package manager in Linux. See the documentation for your particular distribution. Launch ResInsight, open Edit-\u0026gt;Preferences Enter the path to the Octave command line interpreter executable octave-cli (for older version of octave use octave)  The precompiled octave interface distributed in the tarball is only tested for RedHat 6. It is notexpected to work for other configurations. (ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)If you need the octave interface to work on a different OS, you need to build ResInsight yourself.See Build Instructions\rWorkaround for crash using Virtual Box Uncheck Settings-\u0026gt;Display-\u0026gt;Enable 3D Acceleration. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.\nHere is a pointer addressing the issue with Virtual Box, this is not testes by us:\nhttps://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\n",
+                html:     "\u003ch2 id=\"install-resinsight\"\u003eInstall ResInsight\u003c/h2\u003e\n\u003ch3 id=\"from-binary-packages-on-linux\"\u003eFrom Binary Packages on Linux\u003c/h3\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003ePlease not that the distribution by the OPM Project will updated some time after the release of a new version on GitHub.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"red-hat-enterprise-linux-6-or-7\"\u003eRed Hat Enterprise Linux 6 or 7\u003c/h4\u003e\n\u003cp\u003eLogin as root and do:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eyum-config-manager --add-repo https://opm-project.org/package/opm.repo\r\nyum install resinsight\r\nyum install resinsight-octave\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eThen you are good, and can start ResInsight by typing: ResInsight\u003c/p\u003e\n\u003ch4 id=\"ubuntu-linux-1604-64bit\"\u003eUbuntu Linux 16.04-64bit\u003c/h4\u003e\n\u003cp\u003eOn the command line do:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esudo apt-get update\r\nsudo apt-get install software-properties-common\r\nsudo apt-add-repository ppa:opm/ppa\r\nsudo apt-get update\r\nsudo apt-get install resinsight\r\nsudo apt-get install octave-resinsight\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eStart ResInsight by typing : \u003ccode\u003eResInsight\u003c/code\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eFor further installation details, see the ResInsight distribution on \u003ca href=\"http://opm-project.org/?page_id=36\"\u003eOpm Project Downloading and Installing\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see \n\u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"from-downloaded-tarball\"\u003eFrom downloaded tarball\u003c/h3\u003e\n\u003col\u003e\n\u003cli\u003eDownload TAR.GZ binary distribution from \u003ca href=\"https://github.com/OPM/ResInsight/releases\" title=\"release section on GitHub\"\u003ehttps://github.com/OPM/ResInsight/releases\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExtract content from TAR file\u003c/li\u003e\n\u003cli\u003eStart ./ResInsight\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch4 id=\"display-menu-icons-in-gnome-optional\"\u003eDisplay Menu Icons in GNOME (Optional)\u003c/h4\u003e\n\u003cp\u003eBy default, icons are not visible in menus in the GNOME desktop environment. ResInsight has icons for many menu items, and icons can be set visible by issuing the following commands (Tested on RHEL6) :\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003egconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true\r\ngconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThis fix was taken from reply number 11 in this \u003ca href=\"https://bbs.archlinux.org/viewtopic.php?id=117414\"\u003ethread\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"setup-octave-interface-optional\"\u003eSetup Octave Interface (optional)\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eInstall Octave directly from the package manager in Linux. See the documentation for your particular distribution.\u003c/li\u003e\n\u003cli\u003eLaunch ResInsight, open \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eEnter the path to the Octave command line interpreter executable \u003ccode\u003eoctave-cli\u003c/code\u003e (for older version of octave use \u003ccode\u003eoctave\u003c/code\u003e)\u003c/li\u003e\n\u003c/ol\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe precompiled octave interface distributed in the tarball is only tested for RedHat 6. \u003c!-- raw HTML omitted --\u003e\nIt is \u003c!-- raw HTML omitted --\u003enot\u003c!-- raw HTML omitted --\u003e expected to work for other configurations.\n(ResInsight 1.3.2-dev and earlier, was also tested on RedHat 5)\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\nIf you need the octave interface to work on a different OS, you need to build ResInsight yourself.\u003c!-- raw HTML omitted --\u003e \nSee \u003c!-- raw HTML omitted --\u003eBuild Instructions\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"workaround-for-crash-using-virtual-box\"\u003eWorkaround for crash using Virtual Box\u003c/h2\u003e\n\u003cp\u003eUncheck \u003cstrong\u003eSettings-\u0026gt;Display-\u0026gt;Enable 3D Acceleration\u003c/strong\u003e. Disabling this option will cause OpenGL operations to be executed in software, so the the performance of graphics operations in ResInsight will be slower, but will not crash.\u003c/p\u003e\n\u003cp\u003eHere is a pointer addressing the issue with Virtual Box, this is not testes by us:\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\"\u003ehttps://superuser.com/questions/541537/how-to-solve-issues-with-shader-model-in-virtualbox\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/download-and-install/linux-installation/"
             };
         
@@ -1857,8 +1890,8 @@ if (!doNotTrack) {
          
             window.store["/misc/preferences/"] = {
                 title:    "Preferences",
-                content:  " In this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the Preference dialog available from the Edit -\u0026gt; Preferences menu.\nWhen changing the preferences, any default color, font or Z-scale Factor that has not been changed by the user in the various views, will be applied immediately. If the user has changed font sizes in specific plots or annotations from the default value, ResInsight will ask if the user wants the new defaults applied to all existing views and plots even where custom settings have been set.\nThe preferences are not stored in the project files, but rather in a platform specific way for each user.\nGeneral - tab Default Colors This group contains the colors that will be applied to the 3D views.\n Viewer Background Mesh Color Mesh Color Along Faults Well Label Color  Default Font Sizes This group contains the different fonts which are used through ResInsight.\n Viewer Font Size \u0026ndash; The fonts used for axes labels, legends and info boxes in the 3d View. Annotation Font Size \u0026ndash; The font used as default for Text Annotations. Well Label Font Size \u0026ndash; The font used for all Well Path labels. Plot Font Size - The font used for legends, axes labels, values in Plots. This affects the docked plots in the main 3D window as well (Result Plot, Relative Permeability etc), although because of the reduces space available in these plots, the font size applied will be one less than the Plot Font Size.  3D Views This group of options controls visual settings that will be used when creating new views.\n Show Grid Lines \u0026ndash; Controls whether to show the grid lines by default for all cells or just along faults. Navigation mode \u0026ndash; Defines how to use the mouse to interact with with the 3D model. Please refer to Model Navigation for details. Default Z Scale Factor \u0026ndash; Default depth scale for grid models. Show Box around Legends \u0026ndash; Create a semi-transparent box containing each legend in the 3D Views. Use shaders \u0026ndash; This option controls the use of OpenGL shaders. Should be left On. Available only for testing purposes. Show 3D Information \u0026ndash; Displays graphical resource usage as text in the 3D view.  Other  Date Format \u0026ndash; Defines the date format to be used in time legend plotting Time Format \u0026ndash; Defines the time format to be used in time legend plotting SSIHUB Address \u0026ndash; Optional URL to Equinor internal web service used to import well paths Show LAS Curve Without TVD Warning - Turn off the warning displayed when showing LAS curves in TVD mode  Eclipse - tab Behavior When Loading Data  Compute DEPTH Related Properties \u0026ndash; If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases. Load and Show SOIL \u0026ndash; Control if SOIL is loaded and applied to grid. Import Faults/NNCs/Advanced MSW Data \u0026ndash; Disable import of data for a case to reduce case import time. Include File Absolute Path Prefix \u0026ndash; Prefix used on Windows if include files use absolute UNIX paths. Use Result Index File \u0026ndash; If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the *.EGRID file with filename \u0026lt;casename\u0026gt;.RESINSIGHT_IDX If it exists, ResInsight will use this when loading the case, resulting in a significant speedup. Skip Import of Simulation Well Data \u0026ndash; Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).  Origin Files Please refer to Summary Origin for details related to handling of Origin Files.\nPlotting - tab  Default Summary Curves: Defines default curves for import when creating a new summary plot, e.g. FOPT WOPT* Default Curve Style for History Vectors: allows specifying symbols and/or lines as preference. Date and Time format preferences. Show resample time text preference Use multiple threads preference which may improve performance when loading summary data Plot Templates allows setting preferences for:  Plot Template Folder(s): Allows to enter and delete folder(s) that are searched for plot templates. Press Append to browse for folder to append. Checking Search Plot Templates Recursively instructs ResInsight to search subdirectories of specified folder(s) for templates.   Scripting - tab Octave  Octave Executable Location \u0026ndash; Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows. Show text header when executing scripts \u0026ndash; Enables the default output that octave outputs when started.  Please refer to Octave Interface for more details.\nPython  Enable Python Script Server Default Python Script Server Port \u0026ndash; Defines the port used for communication with Python scripts Python Executable Location  Please refer to Python API for more details.\nScript Files  Shared Script Folder(s) \u0026ndash; Defines the search paths for octave scripts Script Editor \u0026ndash; The text editor to invoke when editing scripts  Export - tab  CSV Text Export Field Separator  ",
-                html:     "\n\n\u003cp\u003eIn this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the \u003cstrong\u003ePreference\u003c/strong\u003e dialog available from the \u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e menu.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen changing the preferences, any default color, font or Z-scale Factor that has not been changed by the user in the various views, will be applied immediately. If the user has changed font sizes in specific plots or annotations from the default value, ResInsight will ask if the user wants the new defaults applied to all existing views and plots even where custom settings have been set.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_ApplyToAll.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe preferences are not stored in the project files, but rather in a platform specific way for each user.\u003c/p\u003e\n\n\u003ch2 id=\"general-tab\"\u003eGeneral - tab\u003c/h2\u003e\n\n\u003ch3 id=\"default-colors\"\u003eDefault Colors\u003c/h3\u003e\n\n\u003cp\u003eThis group contains the colors that will be applied to the 3D views.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer Background\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Color\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Color Along Faults\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Label Color\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"default-font-sizes\"\u003eDefault Font Sizes\u003c/h3\u003e\n\n\u003cp\u003eThis group contains the different fonts which are used through ResInsight.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer Font Size\u003c/strong\u003e \u0026ndash; The fonts used for axes labels, legends and info boxes in the 3d View.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAnnotation Font Size\u003c/strong\u003e \u0026ndash; The font used as default for Text Annotations.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Label Font Size\u003c/strong\u003e \u0026ndash; The font used for all Well Path labels.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Font Size\u003c/strong\u003e - The font used for legends, axes labels, values in Plots. This affects the docked plots in the main 3D window as well (Result Plot, Relative Permeability etc), although because of the reduces space available in these plots, the font size applied will be one less than the \u003cstrong\u003ePlot Font Size\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"3d-views\"\u003e3D Views\u003c/h3\u003e\n\n\u003cp\u003eThis group of options controls visual settings that will be used when creating new views.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Controls whether to show the grid lines by default for all cells or just along faults.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNavigation mode\u003c/strong\u003e \u0026ndash; Defines how to use the mouse to interact with with the 3D model. Please refer to \u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Z Scale Factor\u003c/strong\u003e \u0026ndash; Default depth scale for grid models.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Box around Legends\u003c/strong\u003e \u0026ndash; Create a semi-transparent box containing each legend in the 3D Views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse shaders\u003c/strong\u003e \u0026ndash; This option controls the use of OpenGL shaders. Should be left \u003cstrong\u003eOn\u003c/strong\u003e. Available only for testing purposes.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow 3D Information\u003c/strong\u003e \u0026ndash; Displays graphical resource usage as text in the 3D view.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"other\"\u003eOther\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDate Format\u003c/strong\u003e \u0026ndash; Defines the date format to be used in time legend plotting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Format\u003c/strong\u003e \u0026ndash; Defines the time format to be used in time legend plotting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSSIHUB Address\u003c/strong\u003e \u0026ndash; Optional URL to Equinor internal web service used to import well paths\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow LAS Curve Without TVD Warning\u003c/strong\u003e - Turn off the warning displayed when showing LAS curves in TVD mode\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"eclipse-tab\"\u003eEclipse - tab\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/EclipsePreferences.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"behavior-when-loading-data\"\u003eBehavior When Loading Data\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCompute DEPTH Related Properties\u003c/strong\u003e \u0026ndash; If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLoad and Show SOIL\u003c/strong\u003e \u0026ndash; Control if SOIL is loaded and applied to grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Faults/NNCs/Advanced MSW Data\u003c/strong\u003e \u0026ndash; Disable import of data for a case to reduce case import time.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInclude File Absolute Path Prefix\u003c/strong\u003e \u0026ndash; Prefix used on Windows if include files use absolute UNIX paths.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Result Index File\u003c/strong\u003e \u0026ndash; If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e file with filename \u003cem\u003e\u003ccode\u003e\u0026lt;casename\u0026gt;.RESINSIGHT_IDX\u003c/code\u003e\u003c/em\u003e If it exists, ResInsight will use this when loading the case, resulting in a significant speedup.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip Import of Simulation Well Data\u003c/strong\u003e \u0026ndash; Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"origin-files\"\u003eOrigin Files\u003c/h3\u003e\n\n\u003cp\u003ePlease refer to \u003ca href=\"/plot-window/summaryplots/#origin-files\"\u003eSummary Origin\u003c/a\u003e for details related to handling of \u003cstrong\u003eOrigin Files\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"plotting-tab\"\u003ePlotting - tab\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesPlotting.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Summary Curves\u003c/strong\u003e: Defines default curves for import when creating a new summary plot, e.g. \u003ccode\u003eFOPT WOPT*\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Curve Style for History Vectors\u003c/strong\u003e: allows specifying \u003cem\u003esymbols\u003c/em\u003e and/or \u003cem\u003elines\u003c/em\u003e as preference.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate\u003c/strong\u003e and \u003cstrong\u003eTime\u003c/strong\u003e format preferences.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow resample time text\u003c/strong\u003e preference\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse multiple threads\u003c/strong\u003e preference which may improve performance when loading summary data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Templates\u003c/strong\u003e allows setting preferences for:\n\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003ePlot Template Folder(s)\u003c/em\u003e: Allows to enter and delete folder(s) that are searched for plot templates. Press \u003cem\u003eAppend\u003c/em\u003e to browse for folder to append.\u003c/li\u003e\n\u003cli\u003eChecking \u003cem\u003eSearch Plot Templates Recursively\u003c/em\u003e instructs ResInsight to search subdirectories of specified folder(s) for templates.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"scripting-tab\"\u003eScripting - tab\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_Scripting.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"octave\"\u003eOctave\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOctave Executable Location\u003c/strong\u003e \u0026ndash; Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow text header when executing scripts\u003c/strong\u003e \u0026ndash; Enables the default output that octave outputs when started.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003ePlease refer to \u003ca href=\"/scripting/octaveinterface/\"\u003eOctave Interface\u003c/a\u003e for more details.\u003c/p\u003e\n\n\u003ch3 id=\"python\"\u003ePython\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eEnable Python Script Server\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Python Script Server Port\u003c/strong\u003e \u0026ndash; Defines the port used for communication with Python scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePython Executable Location\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003ePlease refer to \u003ca href=\"/scripting/pythonrips/\"\u003ePython API\u003c/a\u003e for more details.\u003c/p\u003e\n\n\u003ch3 id=\"script-files\"\u003eScript Files\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShared Script Folder(s)\u003c/strong\u003e \u0026ndash; Defines the search paths for octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScript Editor\u003c/strong\u003e \u0026ndash; The text editor to invoke when editing scripts\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"export-tab\"\u003eExport - tab\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_Export.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCSV Text Export Field Separator\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "In this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the Preference dialog available from the Edit -\u0026gt; Preferences menu.\nWhen changing the preferences, any default color, font or Z-scale Factor that has not been changed by the user in the various views, will be applied immediately. If the user has changed font sizes in specific plots or annotations from the default value, ResInsight will ask if the user wants the new defaults applied to all existing views and plots even where custom settings have been set.\nThe preferences are not stored in the project files, but rather in a platform specific way for each user.\nGeneral - tab Default Colors This group contains the colors that will be applied to the 3D views.\n Viewer Background Mesh Color Mesh Color Along Faults Well Label Color  Default Font Sizes This group contains the different fonts which are used through ResInsight.\n Viewer Font Size \u0026ndash; The fonts used for axes labels, legends and info boxes in the 3d View. Annotation Font Size \u0026ndash; The font used as default for Text Annotations. Well Label Font Size \u0026ndash; The font used for all Well Path labels. Plot Font Size - The font used for legends, axes labels, values in Plots. This affects the docked plots in the main 3D window as well (Result Plot, Relative Permeability etc), although because of the reduces space available in these plots, the font size applied will be one less than the Plot Font Size.  3D Views This group of options controls visual settings that will be used when creating new views.\n Show Grid Lines \u0026ndash; Controls whether to show the grid lines by default for all cells or just along faults. Navigation mode \u0026ndash; Defines how to use the mouse to interact with with the 3D model. Please refer to Model Navigation for details. Default Z Scale Factor \u0026ndash; Default depth scale for grid models. Show Box around Legends \u0026ndash; Create a semi-transparent box containing each legend in the 3D Views. Use shaders \u0026ndash; This option controls the use of OpenGL shaders. Should be left On. Available only for testing purposes. Show 3D Information \u0026ndash; Displays graphical resource usage as text in the 3D view.  Other  Date Format \u0026ndash; Defines the date format to be used in time legend plotting Time Format \u0026ndash; Defines the time format to be used in time legend plotting SSIHUB Address \u0026ndash; Optional URL to Equinor internal web service used to import well paths Show LAS Curve Without TVD Warning - Turn off the warning displayed when showing LAS curves in TVD mode  Eclipse - tab Behavior When Loading Data  Compute DEPTH Related Properties \u0026ndash; If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases. Load and Show SOIL \u0026ndash; Control if SOIL is loaded and applied to grid. Import Faults/NNCs/Advanced MSW Data \u0026ndash; Disable import of data for a case to reduce case import time. Include File Absolute Path Prefix \u0026ndash; Prefix used on Windows if include files use absolute UNIX paths. Use Result Index File \u0026ndash; If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the *.EGRID file with filename \u0026lt;casename\u0026gt;.RESINSIGHT_IDX If it exists, ResInsight will use this when loading the case, resulting in a significant speedup. Skip Import of Simulation Well Data \u0026ndash; Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).  Origin Files Please refer to Summary Origin for details related to handling of Origin Files.\nPlotting - tab  Default Summary Curves: Defines default curves for import when creating a new summary plot, e.g. FOPT WOPT* Default Curve Style for History Vectors: allows specifying symbols and/or lines as preference. Date and Time format preferences. Show resample time text preference Use multiple threads preference which may improve performance when loading summary data Plot Templates allows setting preferences for:  Plot Template Folder(s): Allows to enter and delete folder(s) that are searched for plot templates. Press Append to browse for folder to append. Checking Search Plot Templates Recursively instructs ResInsight to search subdirectories of specified folder(s) for templates.    Scripting - tab Octave  Octave Executable Location \u0026ndash; Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows. Show text header when executing scripts \u0026ndash; Enables the default output that octave outputs when started.  Please refer to Octave Interface for more details.\nPython  Enable Python Script Server Default Python Script Server Port \u0026ndash; Defines the port used for communication with Python scripts Python Executable Location  Please refer to Python API for more details.\nScript Files  Shared Script Folder(s) \u0026ndash; Defines the search paths for octave scripts Script Editor \u0026ndash; The text editor to invoke when editing scripts  Export - tab  CSV Text Export Field Separator  ",
+                html:     "\u003cp\u003eIn this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the \u003cstrong\u003ePreference\u003c/strong\u003e dialog available from the \u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e menu.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen changing the preferences, any default color, font or Z-scale Factor that has not been changed by the user in the various views, will be applied immediately. If the user has changed font sizes in specific plots or annotations from the default value, ResInsight will ask if the user wants the new defaults applied to all existing views and plots even where custom settings have been set.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_ApplyToAll.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe preferences are not stored in the project files, but rather in a platform specific way for each user.\u003c/p\u003e\n\u003ch2 id=\"general---tab\"\u003eGeneral - tab\u003c/h2\u003e\n\u003ch3 id=\"default-colors\"\u003eDefault Colors\u003c/h3\u003e\n\u003cp\u003eThis group contains the colors that will be applied to the 3D views.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer Background\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Color\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Color Along Faults\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Label Color\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"default-font-sizes\"\u003eDefault Font Sizes\u003c/h3\u003e\n\u003cp\u003eThis group contains the different fonts which are used through ResInsight.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer Font Size\u003c/strong\u003e \u0026ndash; The fonts used for axes labels, legends and info boxes in the 3d View.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAnnotation Font Size\u003c/strong\u003e \u0026ndash; The font used as default for Text Annotations.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Label Font Size\u003c/strong\u003e \u0026ndash; The font used for all Well Path labels.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Font Size\u003c/strong\u003e - The font used for legends, axes labels, values in Plots. This affects the docked plots in the main 3D window as well (Result Plot, Relative Permeability etc), although because of the reduces space available in these plots, the font size applied will be one less than the \u003cstrong\u003ePlot Font Size\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"3d-views\"\u003e3D Views\u003c/h3\u003e\n\u003cp\u003eThis group of options controls visual settings that will be used when creating new views.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Controls whether to show the grid lines by default for all cells or just along faults.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNavigation mode\u003c/strong\u003e \u0026ndash; Defines how to use the mouse to interact with with the 3D model. Please refer to \u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Z Scale Factor\u003c/strong\u003e \u0026ndash; Default depth scale for grid models.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Box around Legends\u003c/strong\u003e \u0026ndash; Create a semi-transparent box containing each legend in the 3D Views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse shaders\u003c/strong\u003e \u0026ndash; This option controls the use of OpenGL shaders. Should be left \u003cstrong\u003eOn\u003c/strong\u003e. Available only for testing purposes.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow 3D Information\u003c/strong\u003e \u0026ndash; Displays graphical resource usage as text in the 3D view.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"other\"\u003eOther\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDate Format\u003c/strong\u003e \u0026ndash; Defines the date format to be used in time legend plotting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Format\u003c/strong\u003e \u0026ndash; Defines the time format to be used in time legend plotting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSSIHUB Address\u003c/strong\u003e \u0026ndash; Optional URL to Equinor internal web service used to import well paths\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow LAS Curve Without TVD Warning\u003c/strong\u003e - Turn off the warning displayed when showing LAS curves in TVD mode\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"eclipse---tab\"\u003eEclipse - tab\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/EclipsePreferences.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"behavior-when-loading-data\"\u003eBehavior When Loading Data\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCompute DEPTH Related Properties\u003c/strong\u003e \u0026ndash; If not present, compute DEPTH, DX, DY, DZ, TOP, BOTTOM when loading new cases.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLoad and Show SOIL\u003c/strong\u003e \u0026ndash; Control if SOIL is loaded and applied to grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Faults/NNCs/Advanced MSW Data\u003c/strong\u003e \u0026ndash; Disable import of data for a case to reduce case import time.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInclude File Absolute Path Prefix\u003c/strong\u003e \u0026ndash; Prefix used on Windows if include files use absolute UNIX paths.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Result Index File\u003c/strong\u003e \u0026ndash; If enabled ResInsight will try to save a result index file when opening a new case. The file is stored in the same directory as the \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e file with filename \u003cem\u003e\u003ccode\u003e\u0026lt;casename\u0026gt;.RESINSIGHT_IDX\u003c/code\u003e\u003c/em\u003e If it exists, ResInsight will use this when loading the case, resulting in a significant speedup.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip Import of Simulation Well Data\u003c/strong\u003e \u0026ndash; Disable import of simulation well data for a case to reduce case import time (opposite toggling than the other import commands).\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"origin-files\"\u003eOrigin Files\u003c/h3\u003e\n\u003cp\u003ePlease refer to \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Origin\u003c/a\u003e for details related to handling of \u003cstrong\u003eOrigin Files\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"plotting---tab\"\u003ePlotting - tab\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesPlotting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Summary Curves\u003c/strong\u003e: Defines default curves for import when creating a new summary plot, e.g. \u003ccode\u003eFOPT WOPT*\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Curve Style for History Vectors\u003c/strong\u003e: allows specifying \u003cem\u003esymbols\u003c/em\u003e and/or \u003cem\u003elines\u003c/em\u003e as preference.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate\u003c/strong\u003e and \u003cstrong\u003eTime\u003c/strong\u003e format preferences.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow resample time text\u003c/strong\u003e preference\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse multiple threads\u003c/strong\u003e preference which may improve performance when loading summary data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Templates\u003c/strong\u003e allows setting preferences for:\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003ePlot Template Folder(s)\u003c/em\u003e: Allows to enter and delete folder(s) that are searched for plot templates. Press \u003cem\u003eAppend\u003c/em\u003e to browse for folder to append.\u003c/li\u003e\n\u003cli\u003eChecking \u003cem\u003eSearch Plot Templates Recursively\u003c/em\u003e instructs ResInsight to search subdirectories of specified folder(s) for templates.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"scripting---tab\"\u003eScripting - tab\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_Scripting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"octave\"\u003eOctave\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOctave Executable Location\u003c/strong\u003e \u0026ndash; Defines the binary file location for Octave. Usually without path on Linux, and including path on Windows.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow text header when executing scripts\u003c/strong\u003e \u0026ndash; Enables the default output that octave outputs when started.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlease refer to \u003ca href=\"/scripting/octaveinterface/\"\u003eOctave Interface\u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch3 id=\"python\"\u003ePython\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eEnable Python Script Server\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Python Script Server Port\u003c/strong\u003e \u0026ndash; Defines the port used for communication with Python scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePython Executable Location\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlease refer to \u003ca href=\"/scripting/pythonrips/\"\u003ePython API\u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch3 id=\"script-files\"\u003eScript Files\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShared Script Folder(s)\u003c/strong\u003e \u0026ndash; Defines the search paths for octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScript Editor\u003c/strong\u003e \u0026ndash; The text editor to invoke when editing scripts\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"export---tab\"\u003eExport - tab\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Preferences_Export.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCSV Text Export Field Separator\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/misc/preferences/"
             };
         
@@ -1866,8 +1899,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/simulationwells/"] = {
                 title:    "Simulation Wells",
-                content:  " This section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.\nCommands Several commands are available as context commands on a simulation well. These commands are available either by right-clicking the well in the 3D View or in the Project Tree.\n New Well Log Extraction Curve \u0026ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property. ( See Well Log Plots ) New Well Log RFT Curve \u0026ndash; Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See Well Log Plots ) New RFT Plot \u0026ndash; See [Well Log Plots](/plot-window/rftplot/. Plot Production Rates \u0026ndash; Creates a summary plot of the selected wells production rates, along with the bottom hole pressure.\n( See Summary Plots ) Plot Well Allocation \u0026ndash; Creates or modifies the default Well Allocation Plot to show the well. allocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.\n( See Flow Diagnostics Plots  ) Show Contributing Wells \u0026ndash; This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:  Add a property filter of Time Of Flight to/from the selected well to show only the cells that contribute to/are influenced by the well. Sets the Cell Result to show Tracer With Max Fraction based on All Injectors or All Producers (the opposite of the selected well) Toggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.  New Fracture \u0026ndash; Creates a new fracture along the simulation well. (See Fracture instances) New Intersection \u0026ndash; creates a new intersection based on the selected simulation well.\n( See Well Log Plots )   Overall Settings for Simulation Wells The Property Panel of the Simulation Wells item in the Project Tree contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the Simulation Wells item.\nIf an option is overridden in any of the wells, this will be indicated in the corresponding top level toggle which will be partially checked. Toggling such a setting will overwrite the ones set on the individual level.\nIn the following are the different parts of the Simulation Wells property panel explained.\nVisibility These options controls the visibility of different aspects of the simulation wells.\n Wells Trough Visible Cells Only \u0026ndash; This option will only show wells with connections to cells deemed visible by the combined result of Range Filters and Property Filters. Label \u0026ndash; Controls visibility of well name labels in the 3D View Well head \u0026ndash; Controls visibility of the arrow displaying the production status of the well Pipe \u0026ndash; A symbolic pipe can be drawn between the well connection cells to illustrate the well. This option controls the visibility of the pipes. Spheres \u0026ndash; This option toggles the visibility of spheres drawn at the center of each well connection cell. Communication Lines \u0026ndash; Toggles the visibility of well communication lines. These arrows shows the communication between wells. Broader arrows indicate higher level of communication. These arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes. Arrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer \u0026ldquo;under\u0026rdquo; the other arrows, to make them easier to see.\n  Well Cells and Fence  Show Well Cells \u0026ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.\n Show Well Cell Fence \u0026ndash; This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set. Well Fence direction \u0026ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells   Size Scaling  Well Head Scale \u0026ndash; Scales the arrow displaying the production status of the well Pipe Radius Scale \u0026ndash; Scaling the pipe radius by the average i,j cell size. Sphere Radius Scale \u0026ndash; Scaling connection cell spheres radius by the average i,j cell size.  Open Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.\nColors  Color Pipe Connections \u0026ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.\n Label Color \u0026ndash; Sets the well label color in the 3D view. Individual Pipe Colors - Select how each pipe will be colored.  The Individual Pipe Color setting has two different options:\n Unique Colors \u0026ndash; Selecting this will apply unique colors from a pre-defined color palette to all the wells, overwriting the colors they had. Uniform Default Color \u0026ndash; Selecting this will apply the same color (made available in the Uniform Well Color option to all simulation wells.  Well Pipe Geometry  Type \u0026ndash; Controls whether the pipe will go from cell center to cell center or in a smoother trajectory. Branch Detection \u0026ndash; Enables splitting of wells into branches based on the positions of the connection cells. This option applies to ordinary wells only and has no effect on multi segment wells (MSW).  Advanced  Well Cell Transparency \u0026ndash; Controls the transparency level for the well cells. Well Head Position \u0026ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.\n  Individual Simulation Well options Each of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of Overall Settings for Simulation Wells.\nExcept for the Size Scaling, these options will override the corresponding setting on the global level, and will result in a partially checked state on the corresponding toggle in the Simulation Wells property panel. The Size Scaling options, however, works relative to the scaling level set on the top level.\nWell Pipes of Multi Segment Wells ResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the Preferences .\nGeometry Approximation The pipe geometry generated for MSW\u0026rsquo;s are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.\nDummy Branches Often MSW\u0026rsquo;s are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.\nPicking Reveals Segment/Branch Info Branch and segment info of a MSW-connected-Cell is shown in the Result Info window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWells.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.\u003c/p\u003e\n\n\u003ch2 id=\"commands\"\u003eCommands\u003c/h2\u003e\n\n\u003cp\u003eSeveral commands are available as context commands on a simulation well. These commands are available either by right-clicking  the well in the \u003cstrong\u003e3D View\u003c/strong\u003e or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNew Well Log Extraction Curve\u003c/strong\u003e \u0026ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.  ( See \u003ca href=\"/plot-window/welllogsandplots/#well-log-extraction-curves\"\u003eWell Log Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Well Log RFT Curve\u003c/strong\u003e \u0026ndash; Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See \u003ca href=\"/plot-window/welllogsandplots/#well-log-rft-curves\"\u003eWell Log Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew RFT Plot\u003c/strong\u003e \u0026ndash;  See [Well Log Plots](/plot-window/rftplot/.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Production Rates\u003c/strong\u003e \u0026ndash; Creates a summary plot of the selected wells production rates, along  with the bottom hole pressure.\u003cbr /\u003e\n( See \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Well Allocation\u003c/strong\u003e \u0026ndash; Creates or modifies the default Well Allocation Plot to show the well.\nallocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.\u003cbr /\u003e\n( See \u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003e Flow Diagnostics Plots \u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Contributing Wells\u003c/strong\u003e \u0026ndash; This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:\n\n\u003cul\u003e\n\u003cli\u003eAdd a property filter of \u003cstrong\u003eTime Of Flight\u003c/strong\u003e to/from the selected well to show only the cells that contribute to/are influenced by the well.\u003c/li\u003e\n\u003cli\u003eSets the \u003cstrong\u003eCell Result\u003c/strong\u003e to show \u003cstrong\u003eTracer With Max Fraction\u003c/strong\u003e based on \u003cstrong\u003eAll Injectors\u003c/strong\u003e or \u003cstrong\u003eAll Producers\u003c/strong\u003e (the opposite of the selected well)\u003c/li\u003e\n\u003cli\u003eToggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Fracture\u003c/strong\u003e \u0026ndash; Creates a new fracture along the simulation well. (See \u003ca href=\"/plot-window/welllogsandplots/#fracture-instances\"\u003eFracture instances\u003c/a\u003e)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Intersection\u003c/strong\u003e \u0026ndash; creates a new intersection based on the selected simulation well.\u003cbr /\u003e\n( See \u003ca href=\"/3d-main-window/intersections/\"\u003eWell Log Plots\u003c/a\u003e )\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"overall-settings-for-simulation-wells\"\u003eOverall Settings for Simulation Wells\u003c/h2\u003e\n\n\u003cp\u003eThe Property Panel of the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e item.\u003c/p\u003e\n\n\u003cp\u003eIf an option is overridden in any of the wells, this will be indicated in the corresponding top level toggle which will be partially checked. Toggling such a setting will overwrite the ones set on the individual level.\u003c/p\u003e\n\n\u003cp\u003eIn the following are the different parts of the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e property panel explained.\u003c/p\u003e\n\n\u003ch3 id=\"visibility\"\u003eVisibility\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsVisibilityProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThese options controls the visibility of different aspects of the simulation wells.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWells Trough Visible Cells Only\u003c/strong\u003e \u0026ndash; This option will only show wells with connections to cells deemed visible by the combined result of \u003cstrong\u003eRange Filters\u003c/strong\u003e and \u003cstrong\u003eProperty Filters\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel\u003c/strong\u003e \u0026ndash; Controls visibility of well name labels in the 3D View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell head\u003c/strong\u003e \u0026ndash; Controls visibility of the arrow displaying the production status of the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePipe\u003c/strong\u003e \u0026ndash; A symbolic pipe can be drawn between the well connection cells to illustrate the well. This option controls the visibility of the pipes.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpheres\u003c/strong\u003e \u0026ndash; This option toggles the visibility of spheres drawn at the center of each well connection cell.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCommunication Lines\u003c/strong\u003e \u0026ndash; Toggles the visibility of well communication lines.\nThese arrows shows the communication between wells. Broader arrows indicate higher level of communication.\nThese arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes.\nArrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer \u0026ldquo;under\u0026rdquo; the other arrows, to make them easier to see.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"well-cells-and-fence\"\u003eWell Cells and Fence\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsWellCellsProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Well Cells\u003c/strong\u003e \u0026ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Well Cell Fence\u003c/strong\u003e \u0026ndash; This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Fence direction\u003c/strong\u003e \u0026ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells\n\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"size-scaling\"\u003eSize Scaling\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsScalingProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Head Scale\u003c/strong\u003e \u0026ndash; Scales the arrow displaying the production status of the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePipe Radius Scale\u003c/strong\u003e \u0026ndash; Scaling the pipe radius by the average i,j cell size.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSphere Radius Scale\u003c/strong\u003e \u0026ndash; Scaling connection cell spheres radius by the average i,j cell size.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eOpen Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.\u003c/p\u003e\n\n\u003ch3 id=\"colors\"\u003eColors\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsColorsProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsColorsProperties_Uniform.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eColor Pipe Connections\u003c/strong\u003e \u0026ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel Color\u003c/strong\u003e \u0026ndash; Sets the well label color in the 3D view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIndividual Pipe Colors\u003c/strong\u003e - Select how each pipe will be colored.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eIndividual Pipe Color\u003c/strong\u003e setting has two different options:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUnique Colors\u003c/strong\u003e \u0026ndash; Selecting this will apply unique colors from a pre-defined color palette to all the wells, overwriting the colors they had.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUniform Default Color\u003c/strong\u003e \u0026ndash; Selecting this will apply the same color (made available in the \u003cstrong\u003eUniform Well Color\u003c/strong\u003e option to all simulation wells.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsPipeGeometryProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Controls whether the pipe will go from cell center to cell center or in a smoother trajectory.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch Detection\u003c/strong\u003e \u0026ndash; Enables splitting of wells into branches based on the positions of the connection cells.  This option applies to ordinary wells only and has no effect on multi segment wells (MSW).\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"advanced\"\u003eAdvanced\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsAdvancedProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Cell Transparency\u003c/strong\u003e \u0026ndash; Controls the transparency level for the well cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Head Position\u003c/strong\u003e \u0026ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"individual-simulation-well-options\"\u003eIndividual Simulation Well options\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEach of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of \u003ca href=\"#overall-settings-for-simulation-wells\"\u003eOverall Settings for Simulation Wells\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eExcept for the \u003cstrong\u003eSize Scaling\u003c/strong\u003e, these options will override the corresponding setting on the global level,\nand will result in a partially checked state on the corresponding toggle in the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e property panel.\nThe \u003cstrong\u003eSize Scaling\u003c/strong\u003e options, however, works relative to the scaling level set on the top level.\u003c/p\u003e\n\n\u003ch2 id=\"well-pipes-of-multi-segment-wells\"\u003eWell Pipes of Multi Segment Wells\u003c/h2\u003e\n\n\u003cp\u003eResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the \u003ca href=\"/misc/preferences/\"\u003e Preferences \u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"geometry-approximation\"\u003eGeometry Approximation\u003c/h3\u003e\n\n\u003cp\u003eThe pipe geometry generated for MSW\u0026rsquo;s are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.\u003c/p\u003e\n\n\u003ch3 id=\"dummy-branches\"\u003eDummy Branches\u003c/h3\u003e\n\n\u003cp\u003eOften MSW\u0026rsquo;s are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MSWDummyBranchExample.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"picking-reveals-segment-branch-info\"\u003ePicking Reveals Segment/Branch Info\u003c/h3\u003e\n\n\u003cp\u003eBranch and segment info of a MSW-connected-Cell is shown in the \u003cstrong\u003eResult Info\u003c/strong\u003e window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.\u003c/p\u003e\n",
+                content:  "This section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.\nCommands Several commands are available as context commands on a simulation well. These commands are available either by right-clicking the well in the 3D View or in the Project Tree.\n New Well Log Extraction Curve \u0026ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property. ( See Well Log Plots ) New Well Log RFT Curve \u0026ndash; Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See Well Log Plots ) New RFT Plot \u0026ndash; See [Well Log Plots](/plot-window/rftplot/. Plot Production Rates \u0026ndash; Creates a summary plot of the selected wells production rates, along with the bottom hole pressure.\n( See Summary Plots ) Plot Well Allocation \u0026ndash; Creates or modifies the default Well Allocation Plot to show the well. allocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.\n( See Flow Diagnostics Plots  ) Show Contributing Wells \u0026ndash; This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:  Add a property filter of Time Of Flight to/from the selected well to show only the cells that contribute to/are influenced by the well. Sets the Cell Result to show Tracer With Max Fraction based on All Injectors or All Producers (the opposite of the selected well) Toggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.   New Fracture \u0026ndash; Creates a new fracture along the simulation well. (See Fracture instances) New Intersection \u0026ndash; creates a new intersection based on the selected simulation well.\n( See Well Log Plots )  Overall Settings for Simulation Wells The Property Panel of the Simulation Wells item in the Project Tree contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the Simulation Wells item.\nIf an option is overridden in any of the wells, this will be indicated in the corresponding top level toggle which will be partially checked. Toggling such a setting will overwrite the ones set on the individual level.\nIn the following are the different parts of the Simulation Wells property panel explained.\nVisibility These options controls the visibility of different aspects of the simulation wells.\n Wells Trough Visible Cells Only \u0026ndash; This option will only show wells with connections to cells deemed visible by the combined result of Range Filters and Property Filters. Label \u0026ndash; Controls visibility of well name labels in the 3D View Well head \u0026ndash; Controls visibility of the arrow displaying the production status of the well Pipe \u0026ndash; A symbolic pipe can be drawn between the well connection cells to illustrate the well. This option controls the visibility of the pipes. Spheres \u0026ndash; This option toggles the visibility of spheres drawn at the center of each well connection cell. Communication Lines \u0026ndash; Toggles the visibility of well communication lines. These arrows shows the communication between wells. Broader arrows indicate higher level of communication. These arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes. Arrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer \u0026ldquo;under\u0026rdquo; the other arrows, to make them easier to see.  Well Cells and Fence  Show Well Cells \u0026ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells. Show Well Cell Fence \u0026ndash; This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set. Well Fence direction \u0026ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells  Size Scaling  Well Head Scale \u0026ndash; Scales the arrow displaying the production status of the well Pipe Radius Scale \u0026ndash; Scaling the pipe radius by the average i,j cell size. Sphere Radius Scale \u0026ndash; Scaling connection cell spheres radius by the average i,j cell size.  Open Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.\nColors  Color Pipe Connections \u0026ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively. Label Color \u0026ndash; Sets the well label color in the 3D view. Individual Pipe Colors - Select how each pipe will be colored.  The Individual Pipe Color setting has two different options:\n Unique Colors \u0026ndash; Selecting this will apply unique colors from a pre-defined color palette to all the wells, overwriting the colors they had. Uniform Default Color \u0026ndash; Selecting this will apply the same color (made available in the Uniform Well Color option to all simulation wells.  Well Pipe Geometry  Type \u0026ndash; Controls whether the pipe will go from cell center to cell center or in a smoother trajectory. Branch Detection \u0026ndash; Enables splitting of wells into branches based on the positions of the connection cells. This option applies to ordinary wells only and has no effect on multi segment wells (MSW).  Advanced  Well Cell Transparency \u0026ndash; Controls the transparency level for the well cells. Well Head Position \u0026ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.  Individual Simulation Well options Each of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of Overall Settings for Simulation Wells.\nExcept for the Size Scaling, these options will override the corresponding setting on the global level, and will result in a partially checked state on the corresponding toggle in the Simulation Wells property panel. The Size Scaling options, however, works relative to the scaling level set on the top level.\nWell Pipes of Multi Segment Wells ResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the Preferences .\nGeometry Approximation The pipe geometry generated for MSW\u0026rsquo;s are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.\nDummy Branches Often MSW\u0026rsquo;s are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.\nPicking Reveals Segment/Branch Info Branch and segment info of a MSW-connected-Cell is shown in the Result Info window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWells.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.\u003c/p\u003e\n\u003ch2 id=\"commands\"\u003eCommands\u003c/h2\u003e\n\u003cp\u003eSeveral commands are available as context commands on a simulation well. These commands are available either by right-clicking  the well in the \u003cstrong\u003e3D View\u003c/strong\u003e or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNew Well Log Extraction Curve\u003c/strong\u003e \u0026ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.  ( See \u003ca href=\"/plot-window/welllogsandplots/#well-log-extraction-curves\"\u003eWell Log Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Well Log RFT Curve\u003c/strong\u003e \u0026ndash; Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See \u003ca href=\"/plot-window/welllogsandplots/#well-log-rft-curves\"\u003eWell Log Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew RFT Plot\u003c/strong\u003e \u0026ndash;  See [Well Log Plots](/plot-window/rftplot/.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Production Rates\u003c/strong\u003e \u0026ndash; Creates a summary plot of the selected wells production rates, along  with the bottom hole pressure.\u003cbr\u003e\n( See \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plots\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Well Allocation\u003c/strong\u003e \u0026ndash; Creates or modifies the default Well Allocation Plot to show the well.\nallocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.\u003cbr\u003e\n( See \u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003e Flow Diagnostics Plots \u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Contributing Wells\u003c/strong\u003e \u0026ndash; This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:\n\u003cul\u003e\n\u003cli\u003eAdd a property filter of \u003cstrong\u003eTime Of Flight\u003c/strong\u003e to/from the selected well to show only the cells that contribute to/are influenced by the well.\u003c/li\u003e\n\u003cli\u003eSets the \u003cstrong\u003eCell Result\u003c/strong\u003e to show \u003cstrong\u003eTracer With Max Fraction\u003c/strong\u003e based on \u003cstrong\u003eAll Injectors\u003c/strong\u003e or \u003cstrong\u003eAll Producers\u003c/strong\u003e (the opposite of the selected well)\u003c/li\u003e\n\u003cli\u003eToggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Fracture\u003c/strong\u003e \u0026ndash; Creates a new fracture along the simulation well. (See \u003ca href=\"/plot-window/welllogsandplots/#fracture-instances\"\u003eFracture instances\u003c/a\u003e)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNew Intersection\u003c/strong\u003e \u0026ndash; creates a new intersection based on the selected simulation well.\u003cbr\u003e\n( See \u003ca href=\"/3d-main-window/intersections/\"\u003eWell Log Plots\u003c/a\u003e )\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"overall-settings-for-simulation-wells\"\u003eOverall Settings for Simulation Wells\u003c/h2\u003e\n\u003cp\u003eThe Property Panel of the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e item.\u003c/p\u003e\n\u003cp\u003eIf an option is overridden in any of the wells, this will be indicated in the corresponding top level toggle which will be partially checked. Toggling such a setting will overwrite the ones set on the individual level.\u003c/p\u003e\n\u003cp\u003eIn the following are the different parts of the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e property panel explained.\u003c/p\u003e\n\u003ch3 id=\"visibility\"\u003eVisibility\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsVisibilityProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThese options controls the visibility of different aspects of the simulation wells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWells Trough Visible Cells Only\u003c/strong\u003e \u0026ndash; This option will only show wells with connections to cells deemed visible by the combined result of \u003cstrong\u003eRange Filters\u003c/strong\u003e and \u003cstrong\u003eProperty Filters\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel\u003c/strong\u003e \u0026ndash; Controls visibility of well name labels in the 3D View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell head\u003c/strong\u003e \u0026ndash; Controls visibility of the arrow displaying the production status of the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePipe\u003c/strong\u003e \u0026ndash; A symbolic pipe can be drawn between the well connection cells to illustrate the well. This option controls the visibility of the pipes.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpheres\u003c/strong\u003e \u0026ndash; This option toggles the visibility of spheres drawn at the center of each well connection cell.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCommunication Lines\u003c/strong\u003e \u0026ndash; Toggles the visibility of well communication lines. \nThese arrows shows the communication between wells. Broader arrows indicate higher level of communication. \nThese arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes. \nArrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer \u0026ldquo;under\u0026rdquo; the other arrows, to make them easier to see.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"well-cells-and-fence\"\u003eWell Cells and Fence\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsWellCellsProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Well Cells\u003c/strong\u003e \u0026ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Well Cell Fence\u003c/strong\u003e \u0026ndash; This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Fence direction\u003c/strong\u003e \u0026ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"size-scaling\"\u003eSize Scaling\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsScalingProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Head Scale\u003c/strong\u003e \u0026ndash; Scales the arrow displaying the production status of the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePipe Radius Scale\u003c/strong\u003e \u0026ndash; Scaling the pipe radius by the average i,j cell size.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSphere Radius Scale\u003c/strong\u003e \u0026ndash; Scaling connection cell spheres radius by the average i,j cell size.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eOpen Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.\u003c/p\u003e\n\u003ch3 id=\"colors\"\u003eColors\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsColorsProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsColorsProperties_Uniform.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eColor Pipe Connections\u003c/strong\u003e \u0026ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel Color\u003c/strong\u003e \u0026ndash; Sets the well label color in the 3D view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIndividual Pipe Colors\u003c/strong\u003e - Select how each pipe will be colored.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe \u003cstrong\u003eIndividual Pipe Color\u003c/strong\u003e setting has two different options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUnique Colors\u003c/strong\u003e \u0026ndash; Selecting this will apply unique colors from a pre-defined color palette to all the wells, overwriting the colors they had.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUniform Default Color\u003c/strong\u003e \u0026ndash; Selecting this will apply the same color (made available in the \u003cstrong\u003eUniform Well Color\u003c/strong\u003e option to all simulation wells.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsPipeGeometryProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Controls whether the pipe will go from cell center to cell center or in a smoother trajectory.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch Detection\u003c/strong\u003e \u0026ndash; Enables splitting of wells into branches based on the positions of the connection cells.  This option applies to ordinary wells only and has no effect on multi segment wells (MSW).\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"advanced\"\u003eAdvanced\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SimulationWellsAdvancedProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Cell Transparency\u003c/strong\u003e \u0026ndash; Controls the transparency level for the well cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Head Position\u003c/strong\u003e \u0026ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"individual-simulation-well-options\"\u003eIndividual Simulation Well options\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEach of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of \u003ca href=\"#overall-settings-for-simulation-wells\"\u003eOverall Settings for Simulation Wells\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eExcept for the \u003cstrong\u003eSize Scaling\u003c/strong\u003e, these options will override the corresponding setting on the global level, \nand will result in a partially checked state on the corresponding toggle in the \u003cstrong\u003eSimulation Wells\u003c/strong\u003e property panel. \nThe \u003cstrong\u003eSize Scaling\u003c/strong\u003e options, however, works relative to the scaling level set on the top level.\u003c/p\u003e\n\u003ch2 id=\"well-pipes-of-multi-segment-wells\"\u003eWell Pipes of Multi Segment Wells\u003c/h2\u003e\n\u003cp\u003eResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the \u003ca href=\"/misc/preferences/\"\u003e Preferences \u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"geometry-approximation\"\u003eGeometry Approximation\u003c/h3\u003e\n\u003cp\u003eThe pipe geometry generated for MSW\u0026rsquo;s are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.\u003c/p\u003e\n\u003ch3 id=\"dummy-branches\"\u003eDummy Branches\u003c/h3\u003e\n\u003cp\u003eOften MSW\u0026rsquo;s are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MSWDummyBranchExample.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"picking-reveals-segmentbranch-info\"\u003ePicking Reveals Segment/Branch Info\u003c/h3\u003e\n\u003cp\u003eBranch and segment info of a MSW-connected-Cell is shown in the \u003cstrong\u003eResult Info\u003c/strong\u003e window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.\u003c/p\u003e\n",
                 url:      "/wells-and-completions/simulationwells/"
             };
         
@@ -1875,8 +1908,8 @@ if (!doNotTrack) {
          
             window.store["/export/snapshots/"] = {
                 title:    "Snapshots",
-                content:  " ResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.\nSnapshots of Existing Views The commands to snapshot existing views and plots are available from the toolbar and the Edit and File-\u0026gt;Export menus in the main windows Snapshot to Clipboard A snapshot of the active view is copied to the clipboard using Edit -\u0026gt; Copy Snapshot To Clipboard .\nSnapshot to File Image export of the currently active 3D View or Plot Window can be launched from File -\u0026gt; Export -\u0026gt; Snapshot To File .\nSnapshot All Views/Plots to File If a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using File -\u0026gt; Export -\u0026gt; Snapshot All Views To File . This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.\nThe files generated are stored in a folder named snapshots within the folder where the Project File resides.\nSnapshots of existing views can also be created and saved from the command line ( See Command Line Interface ).\n\rAdvanced Snapshot Export The Advanced Snapshot Export command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.\nThe Advanced Snapshot Export is available from the File-\u0026gt;Export menu in the 3D Main Window Invoking the command will display the following dialog:\nThis table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.\nTo edit a row, the row must be activated by toggling it on in the Active column, then double click on the cell to edit.\nOptions represented by columns:\n View \u0026ndash; Selects the view to modify. Result Type, Properties \u0026ndash; Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row. Start Time, End Time \u0026ndash; Defines the time step range to cycle through when creating snapshots. Range Filter Slice, Range Start, Range End \u0026ndash; Defines a range filter slice that will be added to the view, and then cycled from Range Start to Range End when creating snapshots. Cases \u0026ndash; Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.  The number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.\nRows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.\nThe snapshots will be generated and saved to the folder displayed in the Export Folder field, when pressing the Export button. This might take quite some time, depending on you settings.\n",
-                html:     "\n\n\u003cp\u003eResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.\u003c/p\u003e\n\n\u003ch2 id=\"snapshots-of-existing-views\"\u003eSnapshots of Existing Views\u003c/h2\u003e\n\n\u003cp\u003eThe commands to snapshot existing views and plots are available from the toolbar and the \u003cstrong\u003eEdit\u003c/strong\u003e and \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eExport\u003c/strong\u003e menus in the main windows \u003cimg src=\"https://resinsight.org/images/export/SnapShotToolBar.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\n\u003ch3 id=\"snapshot-to-clipboard\"\u003eSnapshot to Clipboard\u003c/h3\u003e\n\n\u003cp\u003eA snapshot of the active view is copied to the clipboard using \u003cstrong\u003eEdit -\u0026gt; Copy Snapshot To Clipboard\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\n\u003ch3 id=\"snapshot-to-file\"\u003eSnapshot to File\u003c/h3\u003e\n\n\u003cp\u003eImage export of the currently active 3D View or Plot Window can be launched from \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Snapshot To File\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/export/SnapShotSave.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\n\u003ch3 id=\"snapshot-all-views-plots-to-file\"\u003eSnapshot All Views/Plots to File\u003c/h3\u003e\n\n\u003cp\u003eIf a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Snapshot All Views To File\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShotSaveViews.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n. This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.\u003c/p\u003e\n\n\u003cp\u003eThe files generated are stored in a folder named \u003cem\u003e\u003ccode\u003esnapshots\u003c/code\u003e\u003c/em\u003e within the folder where the Project File resides.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSnapshots of existing views can also be created and saved from the command line\n ( See \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand Line Interface\u003c/a\u003e ).\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"advanced-snapshot-export\"\u003eAdvanced Snapshot Export\u003c/h2\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eAdvanced Snapshot Export\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShotSaveViews.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eAdvanced Snapshot Export\u003c/strong\u003e is available from the \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eExport\u003c/strong\u003e menu in the \u003cstrong\u003e3D Main Window\u003c/strong\u003e\nInvoking the command will display the following dialog:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/SnapshotAdvancedExport.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.\u003c/p\u003e\n\n\u003cp\u003eTo edit a row, the row must be activated by toggling it on in the \u003cstrong\u003eActive\u003c/strong\u003e column, then double click on the cell to edit.\u003c/p\u003e\n\n\u003cp\u003eOptions represented by columns:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e \u0026ndash; Selects the view to modify.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Type\u003c/strong\u003e, \u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Time\u003c/strong\u003e, \u003cstrong\u003eEnd Time\u003c/strong\u003e \u0026ndash; Defines the time step range to cycle through when creating snapshots.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filter Slice\u003c/strong\u003e, \u003cstrong\u003eRange Start\u003c/strong\u003e, \u003cstrong\u003eRange End\u003c/strong\u003e \u0026ndash; Defines a range filter slice that will be added to the view, and then cycled from \u003cem\u003eRange Start\u003c/em\u003e to \u003cem\u003eRange End\u003c/em\u003e when creating snapshots.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCases\u003c/strong\u003e \u0026ndash; Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.\u003c/p\u003e\n\n\u003cp\u003eRows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.\u003c/p\u003e\n\n\u003cp\u003eThe snapshots will be generated and saved to the folder displayed in the \u003cstrong\u003eExport Folder\u003c/strong\u003e field, when pressing the \u003cstrong\u003eExport\u003c/strong\u003e button. This might take quite some time, depending on you settings.\u003c/p\u003e\n",
+                content:  "ResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.\nSnapshots of Existing Views The commands to snapshot existing views and plots are available from the toolbar and the Edit and File-\u0026gt;Export menus in the main windows Snapshot to Clipboard A snapshot of the active view is copied to the clipboard using Edit -\u0026gt; Copy Snapshot To Clipboard .\nSnapshot to File Image export of the currently active 3D View or Plot Window can be launched from File -\u0026gt; Export -\u0026gt; Snapshot To File .\nSnapshot All Views/Plots to File If a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using File -\u0026gt; Export -\u0026gt; Snapshot All Views To File . This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.\nThe files generated are stored in a folder named snapshots within the folder where the Project File resides.\nSnapshots of existing views can also be created and saved from the command line ( See Command Line Interface).\n\rAdvanced Snapshot Export The Advanced Snapshot Export command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.\nThe Advanced Snapshot Export is available from the File-\u0026gt;Export menu in the 3D Main Window Invoking the command will display the following dialog:\nThis table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.\nTo edit a row, the row must be activated by toggling it on in the Active column, then double click on the cell to edit.\nOptions represented by columns:\n View \u0026ndash; Selects the view to modify. Result Type, Properties \u0026ndash; Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row. Start Time, End Time \u0026ndash; Defines the time step range to cycle through when creating snapshots. Range Filter Slice, Range Start, Range End \u0026ndash; Defines a range filter slice that will be added to the view, and then cycled from Range Start to Range End when creating snapshots. Cases \u0026ndash; Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.  The number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.\nRows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.\nThe snapshots will be generated and saved to the folder displayed in the Export Folder field, when pressing the Export button. This might take quite some time, depending on you settings.\n",
+                html:     "\u003cp\u003eResInsight has several commands to create snapshots conveniently. 3 commands to take snapshots of existing Plot and 3D Views directly, and a more advanced export command that can automatically modify Eclipse 3D Views before snapshotting them.\u003c/p\u003e\n\u003ch2 id=\"snapshots-of-existing-views\"\u003eSnapshots of Existing Views\u003c/h2\u003e\n\u003cp\u003eThe commands to snapshot existing views and plots are available from the toolbar and the \u003cstrong\u003eEdit\u003c/strong\u003e and \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eExport\u003c/strong\u003e menus in the main windows \u003cimg src=\"https://resinsight.org/images/export/SnapShotToolBar.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003ch3 id=\"snapshot-to-clipboard\"\u003eSnapshot to Clipboard\u003c/h3\u003e\n\u003cp\u003eA snapshot of the active view is copied to the clipboard using \u003cstrong\u003eEdit -\u0026gt; Copy Snapshot To Clipboard\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003ch3 id=\"snapshot-to-file\"\u003eSnapshot to File\u003c/h3\u003e\n\u003cp\u003eImage export of the currently active 3D View or Plot Window can be launched from \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Snapshot To File\u003c/strong\u003e \u003cimg src=\"https://resinsight.org/images/export/SnapShotSave.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003ch3 id=\"snapshot-all-viewsplots-to-file\"\u003eSnapshot All Views/Plots to File\u003c/h3\u003e\n\u003cp\u003eIf a project contains multiple 3D Views or Plot Windows, all of them can be exported in one go using \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Snapshot All Views To File\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShotSaveViews.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n. This will either export all the 3D Views or all the Plot Windows, depending on whether you invoke the command in the 3D Main Window or the Plot Main Window.\u003c/p\u003e\n\u003cp\u003eThe files generated are stored in a folder named \u003cem\u003e\u003ccode\u003esnapshots\u003c/code\u003e\u003c/em\u003e within the folder where the Project File resides.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSnapshots of existing views can also be created and saved from the command line \n( See \u003c!-- raw HTML omitted --\u003eCommand Line Interface\u003c!-- raw HTML omitted --\u003e ).\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"advanced-snapshot-export\"\u003eAdvanced Snapshot Export\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eAdvanced Snapshot Export\u003c/strong\u003e  \u003cimg src=\"https://resinsight.org/images/export/SnapShotSaveViews.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n command is useful for exporting several images of a specified set of views while simultaneously changing some of their settings. By using this command it is easy to document all layers of a specific model, or generate images with identical setup across several different cases. It is also easy to export an image for each of the time steps in a case, or even a combination of all these parameters.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eAdvanced Snapshot Export\u003c/strong\u003e is available from the \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eExport\u003c/strong\u003e menu in the \u003cstrong\u003e3D Main Window\u003c/strong\u003e \nInvoking the command will display the following dialog:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/SnapshotAdvancedExport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis table defines which 3D Views to modify, and how to modify them. Each row defines the modifications of a specific view, and for all the combinations a row specifies, a snapshot is generated.\u003c/p\u003e\n\u003cp\u003eTo edit a row, the row must be activated by toggling it on in the \u003cstrong\u003eActive\u003c/strong\u003e column, then double click on the cell to edit.\u003c/p\u003e\n\u003cp\u003eOptions represented by columns:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e \u0026ndash; Selects the view to modify.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Type\u003c/strong\u003e, \u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; Defines a list of eclipse result properties to cycle through when creating snapshots. If properties from both the dynamic and static list is needed, you must create a new row.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Time\u003c/strong\u003e, \u003cstrong\u003eEnd Time\u003c/strong\u003e \u0026ndash; Defines the time step range to cycle through when creating snapshots.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filter Slice\u003c/strong\u003e, \u003cstrong\u003eRange Start\u003c/strong\u003e, \u003cstrong\u003eRange End\u003c/strong\u003e \u0026ndash; Defines a range filter slice that will be added to the view, and then cycled from \u003cem\u003eRange Start\u003c/em\u003e to \u003cem\u003eRange End\u003c/em\u003e when creating snapshots.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCases\u003c/strong\u003e \u0026ndash; Defines the cases to cycle while creating snapshots. Normally you can not change which case a view is displaying, but this option does temporarily.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe number of exported snapshots from a row can easily end up being huge, so it is wise to use some caution. The total number will be Properties * Time Steps * Range Steps * Cases.\u003c/p\u003e\n\u003cp\u003eRows can be deleted and created by right-clicking in the table. 5 rows are created for convenience by default.\u003c/p\u003e\n\u003cp\u003eThe snapshots will be generated and saved to the folder displayed in the \u003cstrong\u003eExport Folder\u003c/strong\u003e field, when pressing the \u003cstrong\u003eExport\u003c/strong\u003e button. This might take quite some time, depending on you settings.\u003c/p\u003e\n",
                 url:      "/export/snapshots/"
             };
         
@@ -1884,8 +1917,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryplots/"] = {
                 title:    "Summary Plots",
-                content:  " A Summary Plot is a window displaying a graph in the main area of the Plot Main Window. As described below, a Summary Plot can contain Summary Curves, Grid time history curves, and pasted ascii curves.\nA new Summary Plot can be created by using the right-click menu of Summary Plots in the Plot Project Tree and activate Open Summary Plot Editor or New Summary Plot.\nIf you have many open plots, it can be useful to collapse all other plots by activating Collapse Other Plots from right-click menu of a plot in the Plot Project Tree.\n\rPlot Data ResInsight can create summary plots based on vectors from SUMMARY files ( *.SMSPEC ), imported Observed Time History Data, Grid Cell Time history Curve, and pasted ascii curves.\nSUMMARY Files When opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a Summary Case. Summary files can also be imported directly using one of the following commands in the File-\u0026gt;Import-\u0026gt;Summary Cases menu:\n Import Summary Case: Brings up the standard file selection dialog. Multiple selections are allowed. Import Summary Cases Recursively: Brings up the recursive file selection dialog. This dialog is described in details below Import Summary Case Group: Brings up the recursive file selection dialog. All files selected are automatically grouped in ResInsight. Import Ensemble: Similar to the above, but in addition to just create a group, ResInsight performs some extra checking related to ensembles and converts the group to an ensemble. See ensemble support description.  These commands can also be accessed in the right-click menu for the Summary Cases entry in the Plot Main Window Project Tree under which the imported cases will also be listed.\nDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed. Origin file support is described below.\nSummary Case Groups A selection of cases can be grouped by right-clicking a selection of summary cases and selecting the command Group Summary Cases. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the Summary Plot Editor.\nObserved Data See Observed Time History Data\nGrid Cell Time History Curve Time history curves from a grid cell property can also be added to a Summary Plot. See Result Inspection.\nPasted Ascii Curves You can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command Paste Excel Data to Summary Plot. See Paste Excel Time History Data.\nSummary Plots Summary plots are created in the Plot Project Tree by right-clicking Summary Plots and selecting Open Summary Plot Editor or New Summary Plot. Having created a Summary Plot, its entry is listed in the Plot Project Tree. The settings of the Plot are controlled by its sub items in the Plot Project Tree and the Property Editor as described below.\nProperty Editor The Property Editor allows Text-Based Curve Creation based on selected sources and setting General Plot Options.\nText-Based Curve Creation allows specification of a list of vectors for plotting based on selected sources. The vectors to plot are specified by the following syntax: \u0026lt;vectorshortname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]. The specification of vectors allows use of wildcards and multiple entries separated by space:\n WOPT:*: One total oil production curve for each well. FOPT FWPT: Two curves with oil and water total production. BPR:15,28,*: Oil phase pressure for all blocks along k as separate curves.  General Plot Options allows the following settings:\n Show Title \u0026ndash; Toggles whether to show the axis title Auto Title \u0026ndash; If enabled, the Plot title is derived automatically Name \u0026ndash; Allows manual setting of plot title if Auto Title is disabled Show Legends \u0026ndash; Toggles whether to legends Legend Font Size \u0026ndash; Font size to be used in plot Normalize all curves \u0026ndash; Scales all curves into the range 0.0-1.0  Time Axis Properties  Axis Title  Show Title \u0026ndash; Toggles whether to show the axis title Title \u0026ndash; A user defined name for the axis Title Position \u0026ndash; Either Center or At End Font Size \u0026ndash; The font size used for the axis title  Time Values  Time Mode \u0026ndash; Option to show the time from Simulation Start, or as real date-times. Max/Min \u0026ndash; The range of visible date/time in the Plot. Automatic Date/Time labels \u0026ndash; Option to invoke automatic date/time labels. Font Size \u0026ndash; The font size used for the date/time axis ticks, c.f. Preferences for default.  Date/Time Label Format  Date Label Format \u0026ndash; Date format for the time axis, c.f. Preferences for default. Time Label Format \u0026ndash; Time format for the time axis, c.f. Preferences for default.   Y-axis Properties  Title Text  Auto Title \u0026ndash; If enabled, the y-axis title is derived automatically with the following options:  Names \u0026ndash; Add quantity long name to y-axis title. Acronyms \u0026ndash; Add quantity acronym to y-axis title. Units - Add unit of quantity to y-axis title.  Title \u0026ndash; If Auto Title is disabled, the Title field emerges to facilitate manual setting of plot title.  Title Layout  Title Position \u0026ndash; Controls the position of the title; Center or At End. Font Size \u0026ndash; Defines the font size used for the axis title.  Axis Values  Logarithmic Scale - Draw plot curves using a logarithmic scale. Invert Axis - Invert the axis, e.g. when depth is represented by the Y-axis. Number Format \u0026ndash; Defines how the legend numbers are formatted.  Auto \u0026ndash; Legend numbers are displayed by either scientific or decimal notation depending on actual value. Decimal \u0026ndash; Legend numbers are displayed using decimal notation. Scientific \u0026ndash; Legend numbers are displayed using scientific notation (e.g. 1.2e+6).  Number of Decimals \u0026ndash; Controls the number of digits after \u0026ldquo;.\u0026rdquo; for Decimal and Scientific. Scale Factor \u0026ndash; Displays the y-axis values by multiplying with a specific scale factor for Decimal and Scientific. Max and Min \u0026ndash; Defines the visible y-range. Font Size \u0026ndash; The font size for showing values at the axis ticks.\n   Plot Mouse Interaction  Value Tracking \u0026ndash; When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip. Selection \u0026ndash; Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:  The closest curve. Each of the Plot Axes. The Plot itself if none of the above is hit and the Plot window is activated by the mouse click.  Window Zoom \u0026ndash; Window zoom is available by dragging the mouse when the left mouse button is pressed. Use Zoom All to restore default zoom level. Wheel Zoom \u0026ndash; The mouse wheel will zoom the plot in and out towards the current mouse cursor position.  Curve Highlight Summary curves will be highlighted when left-clicked in a plot. This allows for detailed investigation on curve values when many curves are plotted. All other curves can be hidden by activating the right-click menu of a plot, and select On - Others Off\nAccessing the Plot Data Right-clicking a plot and selecting Show Plot Data will open a window containing the plot data as text columns. This dialog supports plot data displayed by day, week, month, quarter, half year and year.\nThe text content of this window is easy to copy and paste into Excel or other tools for further processing. It is also possible to save the text data to a file directly by using the right-click command Export Plot Data to Text File.\nEditing properties of single Summary Curve Selecting a specific Summary Curve is possible via the Plot Project Tree.\nHaving selected a Summary Curve, its properties are shown by the Property Editor.\nAs seen, the Property Editor organizes the available options into the following groups:\n Summary Vector \u0026ndash; Options to select case, vector to plot, axis specification, and error bars. Appearance \u0026ndash; Options to control curve color, symbols, line style etc. Curve Name \u0026ndash; Controls how the curve is labeled in the legend. Advanced \u0026ndash; Specification of additional options.  Summary Vector This group of options is used to define summary vector data that the curve will display.\n Case \u0026ndash; Selects the imported Summary or Observed Data case to use as source. Vector \u0026ndash; Displays the acronym of the selected vector. Axis \u0026ndash; Controls whether the curve is to be associated with the left or right Y-Axis.  Selection of vector is performed using a vector acronym or pressing the button to the right. Pressing the button opens a dialog similar to the Summary Plot Editor.\nSwitching the Y-Axis for several curves in one go can be done using the context command Switch Plot Axis.\n\rCurve Name The user can control the curve name used in the plot legend by the following options:\n Contribute To Legend \u0026ndash; This option controls whether the curve will be visible in the plot legend. A curve with an empty name will be removed from legend. Auto Name \u0026ndash; If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group. Curve Name \u0026ndash; If Auto Name is off, you can enter a curve name here. If empty, the curve will be removed from the legend, but still visible in the plot. Case Name, Vector name \u0026hellip; etc. \u0026ndash; These options controls what part of the summary vector information to use in the curve auto-name.  Copy and Paste Copy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V).\nRecursive summary file import When using the standard file selection dialog, the user is limited to select files in one directory only. If the interesting files are distributed over multiple directories, the dialog has to be opened once for each directory. The recursive file selection dialog is created to circumvent this limitation. This dialog is able to search a directory tree for files matching a specified pattern.\nThe dialog consists of the following fields:\n Path Pattern: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single \u0026ldquo;*\u0026rdquo; (eg. \u0026ldquo;/home/\u0026rdquo;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by \u0026ldquo;\u0026hellip;\u0026rdquo; in the Effective Filter label below.  * Matches any number of any characters except the path separator ? Matches one character exception the directory separator [abc] Matches one of the specified characters. Ex. a, b or c  File Pattern: The search pattern that applies to the file name. Effective Filter: The effective filter displays the resulting full path search pattern. It is updated on the fly as the user edits the pattern fields. A text string of \u0026ldquo;\u0026hellip;\u0026rdquo; indicates a complete recursive directory search.  After pressing the Find button, a file search is performed in the root directory and the directories below matching the path pattern. The files found are presented in a list, where the user can check/uncheck each file individually.\nWhen the OK button is pressed, all checked files are imported.\nOrigin Files During summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed.\nDepending on what triggered the summary file import, the dialog shows slightly different information. If the summary file import was triggered by a grid file import, the dialog displays information about grid files in addition to the summary origin file(s). If the summary file was imported directly, information about grid files are not relevant and thus not displayed.\nThe dialog contents are organized in groups:\n Current Grid and Summary Files or Current Summary Files: This group displays the name of the main summary file to import. If the import is triggered by a grid file import, the name of the grid file is also displayed. Origin Summary Files: This group displays the names of the origin summary file(s) found. If there are more than one file listed, it means that the found origin file also has an origin file. ResInsight will search the \u0026ldquo;chain\u0026rdquo; of summary origin files until it reaches the end.  Import Options There are three options to control how origin summary file are imported Unified: The main summary files and all origin files are imported into one single summary case Separate Cases: The main files and all origin files are imported into separate summary cases Skip: Only the main summary file is imported. The origin summary files are skipped.  Origin Grid Files: If the summary file import was triggered by a grid file import, this group is visible. It contains a list of the grid files associated to the origin summary files  Import Options There are two options to control how the grid files are imported Separate Cases: All \u0026ldquo;origin\u0026rdquo; grid files are imported into separate grid cases Skip: Only the main grid file is imported. The \u0026ldquo;origin\u0026rdquo; grid files are skipped.   By default the file names are displayed using relative path based on the common root folder for all files. In order to display the full path, check the Show full paths checkbox. Regardless of the checkbox state, there is always a tooltip showing the full path for every file. It is also possible to copy a full path file name to the clipboard. Right click on the file name and select Copy file name.\nIf the user selected multiple summary files or grid files, this dialog will be displayed for every file that has an origin summary file. In this case the button OK to All appears. When this button is clicked, the rest of the files will be imported silently using the same options.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ResInsightMainPlotMediumSize.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA Summary Plot is a window displaying a graph in the main area of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e. As described below, a Summary Plot can contain Summary Curves, Grid time history curves, and pasted ascii curves.\u003c/p\u003e\n\n\u003cp\u003eA new Summary Plot can be created by using the right-click menu of \u003cstrong\u003eSummary Plots\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and activate\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eOpen Summary Plot Editor\u003c/strong\u003e or\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIf you have many open plots, it can be useful to collapse all other plots by activating \u003cstrong\u003eCollapse Other Plots\u003c/strong\u003e from right-click menu of a plot in the \u003cb\u003ePlot Project Tree\u003c/b\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"plot-data\"\u003ePlot Data\u003c/h2\u003e\n\n\u003cp\u003eResInsight can create summary plots based on vectors from SUMMARY files ( \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e ), imported Observed Time History Data, Grid Cell Time history Curve, and pasted ascii curves.\u003c/p\u003e\n\n\u003ch3 id=\"summary-files\"\u003eSUMMARY Files\u003c/h3\u003e\n\n\u003cp\u003eWhen opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a \u003cstrong\u003eSummary Case\u003c/strong\u003e.\nSummary files can also be imported directly using one of the following commands in the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases\u003c/strong\u003e menu:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Case\u003c/strong\u003e: Brings up the standard file selection dialog. Multiple selections are allowed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Cases Recursively\u003c/strong\u003e: Brings up the recursive file selection dialog. This dialog is described in details \u003ca href=\"#recursive-summary-file-import\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Case Group\u003c/strong\u003e: Brings up the recursive file selection dialog. All files selected are automatically grouped in ResInsight.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Ensemble\u003c/strong\u003e: Similar to the above, but in addition to just create a group, ResInsight performs some extra checking related to ensembles and converts the group to an ensemble. See \u003ca href=\"/plot-window/ensembleplotting/\"\u003eensemble support description\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThese commands can also be accessed in the right-click menu for the \u003cstrong\u003eSummary Cases\u003c/strong\u003e entry in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e under which the imported cases will also be listed.\u003c/p\u003e\n\n\u003cp\u003eDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed. Origin file support is described \u003ca href=\"#origin-files\"\u003ebelow\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"summary-case-groups\"\u003eSummary Case Groups\u003c/h3\u003e\n\n\u003cp\u003eA selection of cases can be grouped by right-clicking  a selection of summary cases and selecting the command \u003cstrong\u003eGroup Summary Cases\u003c/strong\u003e. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"observed-data\"\u003eObserved Data\u003c/h3\u003e\n\n\u003cp\u003eSee \u003ca href=\"/import/observeddata/\"\u003eObserved Time History Data\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"grid-cell-time-history-curve\"\u003eGrid Cell Time History Curve\u003c/h3\u003e\n\n\u003cp\u003eTime history curves from a grid cell property can also be added to a Summary Plot.\nSee \u003ca href=\"/3d-main-window/resultinspection/#result-plot\"\u003eResult Inspection\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"pasted-ascii-curves\"\u003ePasted Ascii Curves\u003c/h3\u003e\n\n\u003cp\u003eYou can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command \u003cstrong\u003ePaste Excel Data to Summary Plot\u003c/strong\u003e. See \u003ca href=\"/import/pasteexceltimedata/\"\u003ePaste Excel Time History Data\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"summary-plots\"\u003eSummary Plots\u003c/h2\u003e\n\n\u003cp\u003eSummary plots are created in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e by right-clicking \u003cstrong\u003eSummary Plots\u003c/strong\u003e and selecting\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eOpen Summary Plot Editor\u003c/strong\u003e or\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e.\nHaving created a Summary Plot, its entry is listed in the Plot Project Tree.\nThe settings of the Plot are controlled by its sub items in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e as described below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"property-editor\"\u003eProperty Editor\u003c/h3\u003e\n\n\u003cp\u003eThe Property Editor allows \u003cstrong\u003eText-Based Curve Creation\u003c/strong\u003e based on selected sources and setting \u003cstrong\u003eGeneral Plot Options\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eText-Based Curve Creation\u003c/strong\u003e allows specification of a list of vectors for plotting based on selected sources.\nThe vectors to plot are specified by the following syntax:\n\u003ccode\u003e\u0026lt;vectorshortname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\u003c/code\u003e.\nThe specification of vectors allows use of wildcards and multiple entries separated by space:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ccode\u003eWOPT:*\u003c/code\u003e: One total oil production curve for each well.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eFOPT FWPT\u003c/code\u003e: Two curves with oil and water total production.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eBPR:15,28,*\u003c/code\u003e: Oil phase pressure for all blocks along k as separate curves.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eGeneral Plot Options\u003c/strong\u003e allows the following settings:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the axis title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Title\u003c/strong\u003e \u0026ndash; If enabled, the Plot title is derived automatically\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Allows manual setting of plot title if \u003cstrong\u003eAuto Title\u003c/strong\u003e is disabled\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggles whether to legends\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Font Size\u003c/strong\u003e \u0026ndash; Font size to be used in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNormalize all curves\u003c/strong\u003e \u0026ndash; Scales all curves into the range 0.0-1.0\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"time-axis-properties\"\u003eTime Axis Properties\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryTimeAxisProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Title\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the axis title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle\u003c/strong\u003e \u0026ndash; A user defined name for the axis\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Position\u003c/strong\u003e \u0026ndash;  Either \u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size used for the axis title\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Values\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTime Mode\u003c/strong\u003e \u0026ndash; Option to show the time from \u003cem\u003eSimulation Start\u003c/em\u003e, or as real date-times.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e/\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; The range of visible date/time in the Plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAutomatic Date/Time labels\u003c/strong\u003e \u0026ndash; Option to invoke automatic date/time labels.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size used for the date/time axis ticks, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate/Time Label Format\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDate Label Format\u003c/strong\u003e \u0026ndash; Date format for the time axis, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Label Format\u003c/strong\u003e \u0026ndash; Time format for the time axis, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"y-axis-properties\"\u003eY-axis Properties\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_plot_yaxis_properties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Text\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Title\u003c/strong\u003e \u0026ndash; If enabled, the y-axis title is derived automatically with the following options:\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNames\u003c/strong\u003e \u0026ndash; Add quantity long name to y-axis title.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAcronyms\u003c/strong\u003e \u0026ndash; Add quantity acronym to y-axis title.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnits\u003c/strong\u003e - Add unit of quantity to y-axis title.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle\u003c/strong\u003e \u0026ndash; If \u003cstrong\u003eAuto Title\u003c/strong\u003e is disabled, the \u003cstrong\u003eTitle\u003c/strong\u003e field emerges to facilitate manual setting of plot title.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Layout\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Position\u003c/strong\u003e \u0026ndash; Controls the position of the title; \u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash;  Defines the font size used for the axis title.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Values\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e  - Draw plot curves using a logarithmic scale.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInvert Axis\u003c/strong\u003e  - Invert the axis, e.g. when depth is represented by the Y-axis.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber Format\u003c/strong\u003e \u0026ndash; Defines how the legend numbers are formatted.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto\u003c/strong\u003e \u0026ndash; Legend numbers are displayed by either scientific or decimal notation depending on actual value.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDecimal\u003c/strong\u003e \u0026ndash; Legend numbers are displayed using decimal notation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScientific\u003c/strong\u003e \u0026ndash; Legend numbers are displayed using scientific notation (e.g. 1.2e+6).\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Decimals\u003c/strong\u003e \u0026ndash; Controls the number of digits after \u0026ldquo;.\u0026rdquo; for  \u003cstrong\u003eDecimal\u003c/strong\u003e and \u003cstrong\u003eScientific\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScale Factor\u003c/strong\u003e \u0026ndash; Displays the y-axis values by multiplying with a specific scale factor for \u003cstrong\u003eDecimal\u003c/strong\u003e and \u003cstrong\u003eScientific\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax and Min\u003c/strong\u003e \u0026ndash; Defines the visible y-range.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size for showing values at the axis ticks.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"plot-mouse-interaction\"\u003ePlot Mouse Interaction\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Tracking\u003c/strong\u003e \u0026ndash; When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelection\u003c/strong\u003e \u0026ndash; Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:\n\n\u003cul\u003e\n\u003cli\u003eThe closest curve.\u003c/li\u003e\n\u003cli\u003eEach of the Plot Axes.\u003c/li\u003e\n\u003cli\u003eThe Plot itself if none of the above is hit and the Plot window is activated by the mouse click.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWindow Zoom\u003c/strong\u003e \u0026ndash; Window zoom is available by dragging the mouse when the left mouse button is pressed. Use \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomAll16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eZoom All\u003c/strong\u003e to restore default zoom level.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWheel Zoom\u003c/strong\u003e \u0026ndash; The mouse wheel will zoom the plot in and out towards the current mouse cursor position.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"curve-highlight\"\u003eCurve Highlight\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eSummary curves will be highlighted when left-clicked in a plot. This allows for detailed investigation on curve values when many curves are plotted. All other curves can be hidden by activating the right-click menu of a plot, and select \u003cstrong\u003eOn - Others Off\u003c/strong\u003e\u003c/p\u003e\n\n\u003ch3 id=\"accessing-the-plot-data\"\u003eAccessing the Plot Data\u003c/h3\u003e\n\n\u003cp\u003eRight-clicking a plot and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will open a window containing the plot data as text columns.\nThis dialog supports plot data displayed by day, week, month, quarter, half year and year.\u003c/p\u003e\n\n\u003cp\u003eThe text content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the text data to a file directly by using the right-click command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"editing-properties-of-single-summary-curve\"\u003eEditing properties of single Summary Curve\u003c/h2\u003e\n\n\u003cp\u003eSelecting a specific Summary Curve is possible via the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveSelection.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eHaving selected a Summary Curve, its properties are shown by the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_curve_properties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAs seen, the Property Editor organizes the available options into the following groups:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSummary Vector\u003c/strong\u003e \u0026ndash; Options to select case, vector to plot, axis specification, and error bars.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e \u0026ndash; Options to control curve color, symbols, line style etc.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Name\u003c/strong\u003e \u0026ndash; Controls how the curve is labeled in the legend.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAdvanced\u003c/strong\u003e \u0026ndash; Specification of additional options.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"summary-vector\"\u003eSummary Vector\u003c/h3\u003e\n\n\u003cp\u003eThis group of options is used to define summary vector data that the curve will display.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Selects the imported Summary or Observed Data case to use as source.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVector\u003c/strong\u003e \u0026ndash; Displays the acronym of the selected vector.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis\u003c/strong\u003e \u0026ndash; Controls whether the curve is to be associated with the left or right Y-Axis.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSelection of vector is performed using a vector acronym or pressing the button to the right.\nPressing the button opens a dialog similar to the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSwitching the Y-Axis for several curves in one go can be done using the context command \u003cb\u003eSwitch Plot Axis\u003c/b\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"curve-name\"\u003eCurve Name\u003c/h3\u003e\n\n\u003cp\u003eThe user can control the curve name used in the plot legend by the following options:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eContribute To Legend\u003c/strong\u003e \u0026ndash; This option controls whether the curve will be visible in the plot legend. A curve with an empty name will be removed from legend.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Name\u003c/strong\u003e \u0026ndash; If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Name\u003c/strong\u003e \u0026ndash; If \u003cstrong\u003eAuto Name\u003c/strong\u003e is off, you can enter a curve name here. If empty, the curve will be removed from the legend, but still visible in the plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCase Name, Vector name \u0026hellip;\u003c/strong\u003e etc. \u0026ndash; These options controls what part of the summary vector information to use in the curve auto-name.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"copy-and-paste\"\u003eCopy and Paste\u003c/h2\u003e\n\n\u003cp\u003eCopy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V).\u003c/p\u003e\n\n\u003ch2 id=\"recursive-summary-file-import\"\u003eRecursive summary file import\u003c/h2\u003e\n\n\u003cp\u003eWhen using the standard file selection dialog, the user is limited to select files in one directory only. If the interesting files are distributed over multiple directories, the dialog has to be opened once for each directory. The recursive file selection dialog is created to circumvent this limitation. This dialog is able to search a directory tree for files matching a specified pattern.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RecursiveImportDialog2.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe dialog consists of the following fields:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePath Pattern\u003c/strong\u003e: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single \u0026ldquo;*\u003cem\u003e\u0026rdquo; (eg. \u0026ldquo;/home/\u003c/em\u003e\u0026rdquo;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by \u0026ldquo;\u0026hellip;\u0026rdquo; in the \u003cstrong\u003eEffective Filter\u003c/strong\u003e label below.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003e*\u003c/strong\u003e Matches any number of any characters except the path separator\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e?\u003c/strong\u003e Matches one character exception the directory separator\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e[abc]\u003c/strong\u003e Matches one of the specified characters. Ex. a, b or c\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Pattern\u003c/strong\u003e: The search pattern that applies to the file name.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEffective Filter\u003c/strong\u003e: The effective filter displays the resulting full path search pattern. It is updated on the fly as the user edits the pattern fields. A text string of \u0026ldquo;\u0026hellip;\u0026rdquo; indicates a complete recursive directory search.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eAfter pressing the \u003cstrong\u003eFind\u003c/strong\u003e button, a file search is performed in the root directory and the directories below matching the path pattern. The files found are presented in a list, where the user can check/uncheck each file individually.\u003c/p\u003e\n\n\u003cp\u003eWhen the \u003cstrong\u003eOK\u003c/strong\u003e button is pressed, all checked files are imported.\u003c/p\u003e\n\n\u003ch3 id=\"origin-files\"\u003eOrigin Files\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/OriginFileDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed.\u003c/p\u003e\n\n\u003cp\u003eDepending on what triggered the summary file import, the dialog shows slightly different information. If the summary file import was triggered by a grid file import, the dialog displays information about grid files in addition to the summary origin file(s). If the summary file was imported directly, information about grid files are not relevant and thus not displayed.\u003c/p\u003e\n\n\u003cp\u003eThe dialog contents are organized in groups:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Grid and Summary Files\u003c/strong\u003e or \u003cstrong\u003eCurrent Summary Files\u003c/strong\u003e: This group displays the name of the main summary file to import. If the import is triggered by a grid file import, the name of the grid file is also displayed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrigin Summary Files\u003c/strong\u003e: This group displays the names of the origin summary file(s) found. If there are more than one file listed, it means that the found origin file also has an origin file. ResInsight will search the \u0026ldquo;chain\u0026rdquo; of summary origin files until it reaches the end.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Options\u003c/strong\u003e There are three options to control how origin summary file are imported\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnified\u003c/strong\u003e: The main summary files and all origin files are imported into one single summary case\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Cases\u003c/strong\u003e: The main files and all origin files are imported into separate summary cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip\u003c/strong\u003e: Only the main summary file is imported. The origin summary files are skipped.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrigin Grid Files\u003c/strong\u003e: If the summary file import was triggered by a grid file import, this group is visible. It contains a list of the grid files associated to the origin summary files\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Options\u003c/strong\u003e There are two options to control how the grid files are imported\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Cases\u003c/strong\u003e: All \u0026ldquo;origin\u0026rdquo; grid files are imported into separate grid cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip\u003c/strong\u003e: Only the main grid file is imported. The \u0026ldquo;origin\u0026rdquo; grid files are skipped.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eBy default the file names are displayed using relative path based on the common root folder for all files. In order to display the full path, check the \u003cstrong\u003eShow full paths\u003c/strong\u003e checkbox. Regardless of the checkbox state, there is always a tooltip showing the full path for every file. It is also possible to copy a full path file name to the clipboard. Right click on the file name and select \u003cstrong\u003eCopy file name\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf the user selected multiple summary files or grid files, this dialog will be displayed for every file that has an origin summary file. In this case the button \u003cstrong\u003eOK to All\u003c/strong\u003e appears. When this button is clicked, the rest of the files will be imported silently using the same options.\u003c/p\u003e\n",
+                content:  "A Summary Plot is a window displaying a graph in the main area of the Plot Main Window. As described below, a Summary Plot can contain Summary Curves, Grid time history curves, and pasted ascii curves.\nA new Summary Plot can be created by using the right-click menu of Summary Plots in the Plot Project Tree and activate Open Summary Plot Editor or New Summary Plot.\nIf you have many open plots, it can be useful to collapse all other plots by activating Collapse Other Plots from right-click menu of a plot in the Plot Project Tree.\n\rPlot Data ResInsight can create summary plots based on vectors from SUMMARY files ( *.SMSPEC ), imported Observed Time History Data, Grid Cell Time history Curve, and pasted ascii curves.\nSUMMARY Files When opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a Summary Case. Summary files can also be imported directly using one of the following commands in the File-\u0026gt;Import-\u0026gt;Summary Cases menu:\n Import Summary Case: Brings up the standard file selection dialog. Multiple selections are allowed. Import Summary Cases Recursively: Brings up the recursive file selection dialog. This dialog is described in details below Import Summary Case Group: Brings up the recursive file selection dialog. All files selected are automatically grouped in ResInsight. Import Ensemble: Similar to the above, but in addition to just create a group, ResInsight performs some extra checking related to ensembles and converts the group to an ensemble. See ensemble support description.  These commands can also be accessed in the right-click menu for the Summary Cases entry in the Plot Main Window Project Tree under which the imported cases will also be listed.\nDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed. Origin file support is described below.\nSummary Case Groups A selection of cases can be grouped by right-clicking a selection of summary cases and selecting the command Group Summary Cases. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the Summary Plot Editor.\nObserved Data See Observed Time History Data\nGrid Cell Time History Curve Time history curves from a grid cell property can also be added to a Summary Plot. See Result Inspection.\nPasted Ascii Curves You can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command Paste Excel Data to Summary Plot. See Paste Excel Time History Data.\nSummary Plots Summary plots are created in the Plot Project Tree by right-clicking Summary Plots and selecting Open Summary Plot Editor or New Summary Plot. Having created a Summary Plot, its entry is listed in the Plot Project Tree. The settings of the Plot are controlled by its sub items in the Plot Project Tree and the Property Editor as described below.\nProperty Editor The Property Editor allows Text-Based Curve Creation based on selected sources and setting General Plot Options.\nText-Based Curve Creation allows specification of a list of vectors for plotting based on selected sources. The vectors to plot are specified by the following syntax: \u0026lt;vectorshortname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]. The specification of vectors allows use of wildcards and multiple entries separated by space:\n WOPT:*: One total oil production curve for each well. FOPT FWPT: Two curves with oil and water total production. BPR:15,28,*: Oil phase pressure for all blocks along k as separate curves.  General Plot Options allows the following settings:\n Show Title \u0026ndash; Toggles whether to show the axis title Auto Title \u0026ndash; If enabled, the Plot title is derived automatically Name \u0026ndash; Allows manual setting of plot title if Auto Title is disabled Show Legends \u0026ndash; Toggles whether to legends Legend Font Size \u0026ndash; Font size to be used in plot Normalize all curves \u0026ndash; Scales all curves into the range 0.0-1.0  Time Axis Properties  Axis Title  Show Title \u0026ndash; Toggles whether to show the axis title Title \u0026ndash; A user defined name for the axis Title Position \u0026ndash; Either Center or At End Font Size \u0026ndash; The font size used for the axis title   Time Values  Time Mode \u0026ndash; Option to show the time from Simulation Start, or as real date-times. Max/Min \u0026ndash; The range of visible date/time in the Plot. Automatic Date/Time labels \u0026ndash; Option to invoke automatic date/time labels. Font Size \u0026ndash; The font size used for the date/time axis ticks, c.f. Preferences for default.   Date/Time Label Format  Date Label Format \u0026ndash; Date format for the time axis, c.f. Preferences for default. Time Label Format \u0026ndash; Time format for the time axis, c.f. Preferences for default.    Y-axis Properties  Title Text  Auto Title \u0026ndash; If enabled, the y-axis title is derived automatically with the following options:  Names \u0026ndash; Add quantity long name to y-axis title. Acronyms \u0026ndash; Add quantity acronym to y-axis title. Units - Add unit of quantity to y-axis title.   Title \u0026ndash; If Auto Title is disabled, the Title field emerges to facilitate manual setting of plot title.   Title Layout  Title Position \u0026ndash; Controls the position of the title; Center or At End. Font Size \u0026ndash; Defines the font size used for the axis title.   Axis Values  Logarithmic Scale - Draw plot curves using a logarithmic scale. Invert Axis - Invert the axis, e.g. when depth is represented by the Y-axis. Number Format \u0026ndash; Defines how the legend numbers are formatted.  Auto \u0026ndash; Legend numbers are displayed by either scientific or decimal notation depending on actual value. Decimal \u0026ndash; Legend numbers are displayed using decimal notation. Scientific \u0026ndash; Legend numbers are displayed using scientific notation (e.g. 1.2e+6).   Number of Decimals \u0026ndash; Controls the number of digits after \u0026ldquo;.\u0026rdquo; for Decimal and Scientific. Scale Factor \u0026ndash; Displays the y-axis values by multiplying with a specific scale factor for Decimal and Scientific. Max and Min \u0026ndash; Defines the visible y-range. Font Size \u0026ndash; The font size for showing values at the axis ticks.    Plot Mouse Interaction  Value Tracking \u0026ndash; When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip. Selection \u0026ndash; Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:  The closest curve. Each of the Plot Axes. The Plot itself if none of the above is hit and the Plot window is activated by the mouse click.   Window Zoom \u0026ndash; Window zoom is available by dragging the mouse when the left mouse button is pressed. Use Zoom All to restore default zoom level. Wheel Zoom \u0026ndash; The mouse wheel will zoom the plot in and out towards the current mouse cursor position.  Curve Highlight Summary curves will be highlighted when left-clicked in a plot. This allows for detailed investigation on curve values when many curves are plotted. All other curves can be hidden by activating the right-click menu of a plot, and select On - Others Off\nAccessing the Plot Data Right-clicking a plot and selecting Show Plot Data will open a window containing the plot data as text columns. This dialog supports plot data displayed by day, week, month, quarter, half year and year.\nThe text content of this window is easy to copy and paste into Excel or other tools for further processing. It is also possible to save the text data to a file directly by using the right-click command Export Plot Data to Text File.\nEditing properties of single Summary Curve Selecting a specific Summary Curve is possible via the Plot Project Tree.\nHaving selected a Summary Curve, its properties are shown by the Property Editor.\nAs seen, the Property Editor organizes the available options into the following groups:\n Summary Vector \u0026ndash; Options to select case, vector to plot, axis specification, and error bars. Appearance \u0026ndash; Options to control curve color, symbols, line style etc. Curve Name \u0026ndash; Controls how the curve is labeled in the legend. Advanced \u0026ndash; Specification of additional options.  Summary Vector This group of options is used to define summary vector data that the curve will display.\n Case \u0026ndash; Selects the imported Summary or Observed Data case to use as source. Vector \u0026ndash; Displays the acronym of the selected vector. Axis \u0026ndash; Controls whether the curve is to be associated with the left or right Y-Axis.  Selection of vector is performed using a vector acronym or pressing the button to the right. Pressing the button opens a dialog similar to the Summary Plot Editor.\nSwitching the Y-Axis for several curves in one go can be done using the context command Switch Plot Axis.\n\rCurve Name The user can control the curve name used in the plot legend by the following options:\n Contribute To Legend \u0026ndash; This option controls whether the curve will be visible in the plot legend. A curve with an empty name will be removed from legend. Auto Name \u0026ndash; If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group. Curve Name \u0026ndash; If Auto Name is off, you can enter a curve name here. If empty, the curve will be removed from the legend, but still visible in the plot. Case Name, Vector name \u0026hellip; etc. \u0026ndash; These options controls what part of the summary vector information to use in the curve auto-name.  Copy and Paste Copy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V).\nRecursive summary file import When using the standard file selection dialog, the user is limited to select files in one directory only. If the interesting files are distributed over multiple directories, the dialog has to be opened once for each directory. The recursive file selection dialog is created to circumvent this limitation. This dialog is able to search a directory tree for files matching a specified pattern.\nThe dialog consists of the following fields:\n Path Pattern: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single \u0026ldquo;**\u0026rdquo; (eg. \u0026ldquo;/home/*\u0026quot;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by \u0026ldquo;\u0026hellip;\u0026rdquo; in the Effective Filter label below.  * Matches any number of any characters except the path separator ? Matches one character exception the directory separator [abc] Matches one of the specified characters. Ex. a, b or c   File Pattern: The search pattern that applies to the file name. Effective Filter: The effective filter displays the resulting full path search pattern. It is updated on the fly as the user edits the pattern fields. A text string of \u0026ldquo;\u0026hellip;\u0026rdquo; indicates a complete recursive directory search.  After pressing the Find button, a file search is performed in the root directory and the directories below matching the path pattern. The files found are presented in a list, where the user can check/uncheck each file individually.\nWhen the OK button is pressed, all checked files are imported.\nOrigin Files During summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed.\nDepending on what triggered the summary file import, the dialog shows slightly different information. If the summary file import was triggered by a grid file import, the dialog displays information about grid files in addition to the summary origin file(s). If the summary file was imported directly, information about grid files are not relevant and thus not displayed.\nThe dialog contents are organized in groups:\n Current Grid and Summary Files or Current Summary Files: This group displays the name of the main summary file to import. If the import is triggered by a grid file import, the name of the grid file is also displayed. Origin Summary Files: This group displays the names of the origin summary file(s) found. If there are more than one file listed, it means that the found origin file also has an origin file. ResInsight will search the \u0026ldquo;chain\u0026rdquo; of summary origin files until it reaches the end.  Import Options There are three options to control how origin summary file are imported  Unified: The main summary files and all origin files are imported into one single summary case Separate Cases: The main files and all origin files are imported into separate summary cases Skip: Only the main summary file is imported. The origin summary files are skipped.     Origin Grid Files: If the summary file import was triggered by a grid file import, this group is visible. It contains a list of the grid files associated to the origin summary files  Import Options There are two options to control how the grid files are imported  Separate Cases: All \u0026ldquo;origin\u0026rdquo; grid files are imported into separate grid cases Skip: Only the main grid file is imported. The \u0026ldquo;origin\u0026rdquo; grid files are skipped.      By default the file names are displayed using relative path based on the common root folder for all files. In order to display the full path, check the Show full paths checkbox. Regardless of the checkbox state, there is always a tooltip showing the full path for every file. It is also possible to copy a full path file name to the clipboard. Right click on the file name and select Copy file name.\nIf the user selected multiple summary files or grid files, this dialog will be displayed for every file that has an origin summary file. In this case the button OK to All appears. When this button is clicked, the rest of the files will be imported silently using the same options.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/ResInsightMainPlotMediumSize.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Summary Plot is a window displaying a graph in the main area of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e. As described below, a Summary Plot can contain Summary Curves, Grid time history curves, and pasted ascii curves.\u003c/p\u003e\n\u003cp\u003eA new Summary Plot can be created by using the right-click menu of \u003cstrong\u003eSummary Plots\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and activate \n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eOpen Summary Plot Editor\u003c/strong\u003e or \n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIf you have many open plots, it can be useful to collapse all other plots by activating \u003cstrong\u003eCollapse Other Plots\u003c/strong\u003e from right-click menu of a plot in the \u003c!-- raw HTML omitted --\u003ePlot Project Tree\u003c!-- raw HTML omitted --\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"plot-data\"\u003ePlot Data\u003c/h2\u003e\n\u003cp\u003eResInsight can create summary plots based on vectors from SUMMARY files ( \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e ), imported Observed Time History Data, Grid Cell Time history Curve, and pasted ascii curves.\u003c/p\u003e\n\u003ch3 id=\"summary-files\"\u003eSUMMARY Files\u003c/h3\u003e\n\u003cp\u003eWhen opening an Eclipse case in the 3D view, the associated summary file is opened automatically by default, and made available as a \u003cstrong\u003eSummary Case\u003c/strong\u003e.\nSummary files can also be imported directly using one of the following commands in the \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases\u003c/strong\u003e menu:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Case\u003c/strong\u003e: Brings up the standard file selection dialog. Multiple selections are allowed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Cases Recursively\u003c/strong\u003e: Brings up the recursive file selection dialog. This dialog is described in details \u003ca href=\"#recursive-summary-file-import\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Summary Case Group\u003c/strong\u003e: Brings up the recursive file selection dialog. All files selected are automatically grouped in ResInsight.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Ensemble\u003c/strong\u003e: Similar to the above, but in addition to just create a group, ResInsight performs some extra checking related to ensembles and converts the group to an ensemble. See \u003ca href=\"/plot-window/ensembleplotting/\"\u003eensemble support description\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThese commands can also be accessed in the right-click menu for the \u003cstrong\u003eSummary Cases\u003c/strong\u003e entry in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e under which the imported cases will also be listed.\u003c/p\u003e\n\u003cp\u003eDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed. Origin file support is described \u003ca href=\"#origin-files\"\u003ebelow\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"summary-case-groups\"\u003eSummary Case Groups\u003c/h3\u003e\n\u003cp\u003eA selection of cases can be grouped by right-clicking  a selection of summary cases and selecting the command \u003cstrong\u003eGroup Summary Cases\u003c/strong\u003e. Summary cases can also be drag-dropped between summary groups. The groups will be used when listing the cases in the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"observed-data\"\u003eObserved Data\u003c/h3\u003e\n\u003cp\u003eSee \u003ca href=\"/import/observeddata/\"\u003eObserved Time History Data\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"grid-cell-time-history-curve\"\u003eGrid Cell Time History Curve\u003c/h3\u003e\n\u003cp\u003eTime history curves from a grid cell property can also be added to a Summary Plot. \nSee \u003ca href=\"/3d-main-window/resultinspection/#result-plot\"\u003eResult Inspection\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"pasted-ascii-curves\"\u003ePasted Ascii Curves\u003c/h3\u003e\n\u003cp\u003eYou can copy an ascii table directly from Excel or any text source and paste it directly into a Summary Plot using the command \u003cstrong\u003ePaste Excel Data to Summary Plot\u003c/strong\u003e. See \u003ca href=\"/import/pasteexceltimedata/\"\u003ePaste Excel Time History Data\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"summary-plots\"\u003eSummary Plots\u003c/h2\u003e\n\u003cp\u003eSummary plots are created in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e by right-clicking \u003cstrong\u003eSummary Plots\u003c/strong\u003e and selecting \n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eOpen Summary Plot Editor\u003c/strong\u003e or \n\u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e. \nHaving created a Summary Plot, its entry is listed in the Plot Project Tree. \nThe settings of the Plot are controlled by its sub items in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e as described below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"property-editor\"\u003eProperty Editor\u003c/h3\u003e\n\u003cp\u003eThe Property Editor allows \u003cstrong\u003eText-Based Curve Creation\u003c/strong\u003e based on selected sources and setting \u003cstrong\u003eGeneral Plot Options\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eText-Based Curve Creation\u003c/strong\u003e allows specification of a list of vectors for plotting based on selected sources.\nThe vectors to plot are specified by the following syntax:\n\u003ccode\u003e\u0026lt;vectorshortname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\u003c/code\u003e.\nThe specification of vectors allows use of wildcards and multiple entries separated by space:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ccode\u003eWOPT:*\u003c/code\u003e: One total oil production curve for each well.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eFOPT FWPT\u003c/code\u003e: Two curves with oil and water total production.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eBPR:15,28,*\u003c/code\u003e: Oil phase pressure for all blocks along k as separate curves.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eGeneral Plot Options\u003c/strong\u003e allows the following settings:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the axis title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Title\u003c/strong\u003e \u0026ndash; If enabled, the Plot title is derived automatically\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Allows manual setting of plot title if \u003cstrong\u003eAuto Title\u003c/strong\u003e is disabled\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggles whether to legends\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Font Size\u003c/strong\u003e \u0026ndash; Font size to be used in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNormalize all curves\u003c/strong\u003e \u0026ndash; Scales all curves into the range 0.0-1.0\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"time-axis-properties\"\u003eTime Axis Properties\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryTimeAxisProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Title\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the axis title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle\u003c/strong\u003e \u0026ndash; A user defined name for the axis\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Position\u003c/strong\u003e \u0026ndash;  Either \u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size used for the axis title\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Values\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTime Mode\u003c/strong\u003e \u0026ndash; Option to show the time from \u003cem\u003eSimulation Start\u003c/em\u003e, or as real date-times.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e/\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; The range of visible date/time in the Plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAutomatic Date/Time labels\u003c/strong\u003e \u0026ndash; Option to invoke automatic date/time labels.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size used for the date/time axis ticks, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate/Time Label Format\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDate Label Format\u003c/strong\u003e \u0026ndash; Date format for the time axis, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Label Format\u003c/strong\u003e \u0026ndash; Time format for the time axis, c.f. \u003ca href=\"/misc/preferences/\"\u003ePreferences\u003c/a\u003e for default.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"y-axis-properties\"\u003eY-axis Properties\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_plot_yaxis_properties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Text\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Title\u003c/strong\u003e \u0026ndash; If enabled, the y-axis title is derived automatically with the following options:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNames\u003c/strong\u003e \u0026ndash; Add quantity long name to y-axis title.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAcronyms\u003c/strong\u003e \u0026ndash; Add quantity acronym to y-axis title.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnits\u003c/strong\u003e - Add unit of quantity to y-axis title.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle\u003c/strong\u003e \u0026ndash; If \u003cstrong\u003eAuto Title\u003c/strong\u003e is disabled, the \u003cstrong\u003eTitle\u003c/strong\u003e field emerges to facilitate manual setting of plot title.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Layout\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Position\u003c/strong\u003e \u0026ndash; Controls the position of the title; \u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash;  Defines the font size used for the axis title.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Values\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e  - Draw plot curves using a logarithmic scale.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInvert Axis\u003c/strong\u003e  - Invert the axis, e.g. when depth is represented by the Y-axis.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber Format\u003c/strong\u003e \u0026ndash; Defines how the legend numbers are formatted.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto\u003c/strong\u003e \u0026ndash; Legend numbers are displayed by either scientific or decimal notation depending on actual value.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDecimal\u003c/strong\u003e \u0026ndash; Legend numbers are displayed using decimal notation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScientific\u003c/strong\u003e \u0026ndash; Legend numbers are displayed using scientific notation (e.g. 1.2e+6).\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Decimals\u003c/strong\u003e \u0026ndash; Controls the number of digits after \u0026ldquo;.\u0026rdquo; for  \u003cstrong\u003eDecimal\u003c/strong\u003e and \u003cstrong\u003eScientific\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eScale Factor\u003c/strong\u003e \u0026ndash; Displays the y-axis values by multiplying with a specific scale factor for \u003cstrong\u003eDecimal\u003c/strong\u003e and \u003cstrong\u003eScientific\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax and Min\u003c/strong\u003e \u0026ndash; Defines the visible y-range.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFont Size\u003c/strong\u003e \u0026ndash; The font size for showing values at the axis ticks.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"plot-mouse-interaction\"\u003ePlot Mouse Interaction\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Tracking\u003c/strong\u003e \u0026ndash; When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value at this location is displayed in a tooltip.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelection\u003c/strong\u003e \u0026ndash; Left mouse button click can be used to select several of the parts in the plot, and display them in the Property Editor:\n\u003cul\u003e\n\u003cli\u003eThe closest curve.\u003c/li\u003e\n\u003cli\u003eEach of the Plot Axes.\u003c/li\u003e\n\u003cli\u003eThe Plot itself if none of the above is hit and the Plot window is activated by the mouse click.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWindow Zoom\u003c/strong\u003e \u0026ndash; Window zoom is available by dragging the mouse when the left mouse button is pressed. Use \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomAll16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eZoom All\u003c/strong\u003e to restore default zoom level.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWheel Zoom\u003c/strong\u003e \u0026ndash; The mouse wheel will zoom the plot in and out towards the current mouse cursor position.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"curve-highlight\"\u003eCurve Highlight\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary curves will be highlighted when left-clicked in a plot. This allows for detailed investigation on curve values when many curves are plotted. All other curves can be hidden by activating the right-click menu of a plot, and select \u003cstrong\u003eOn - Others Off\u003c/strong\u003e\u003c/p\u003e\n\u003ch3 id=\"accessing-the-plot-data\"\u003eAccessing the Plot Data\u003c/h3\u003e\n\u003cp\u003eRight-clicking a plot and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will open a window containing the plot data as text columns. \nThis dialog supports plot data displayed by day, week, month, quarter, half year and year.\u003c/p\u003e\n\u003cp\u003eThe text content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the text data to a file directly by using the right-click command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"editing-properties-of-single-summary-curve\"\u003eEditing properties of single Summary Curve\u003c/h2\u003e\n\u003cp\u003eSelecting a specific Summary Curve is possible via the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveSelection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHaving selected a Summary Curve, its properties are shown by the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_curve_properties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs seen, the Property Editor organizes the available options into the following groups:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSummary Vector\u003c/strong\u003e \u0026ndash; Options to select case, vector to plot, axis specification, and error bars.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e \u0026ndash; Options to control curve color, symbols, line style etc.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Name\u003c/strong\u003e \u0026ndash; Controls how the curve is labeled in the legend.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAdvanced\u003c/strong\u003e \u0026ndash; Specification of additional options.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"summary-vector\"\u003eSummary Vector\u003c/h3\u003e\n\u003cp\u003eThis group of options is used to define summary vector data that the curve will display.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Selects the imported Summary or Observed Data case to use as source.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVector\u003c/strong\u003e \u0026ndash; Displays the acronym of the selected vector.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis\u003c/strong\u003e \u0026ndash; Controls whether the curve is to be associated with the left or right Y-Axis.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSelection of vector is performed using a vector acronym or pressing the button to the right. \nPressing the button opens a dialog similar to the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSwitching the Y-Axis for several curves in one go can be done using the context command \u003c!-- raw HTML omitted --\u003eSwitch Plot Axis\u003c!-- raw HTML omitted --\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"curve-name\"\u003eCurve Name\u003c/h3\u003e\n\u003cp\u003eThe user can control the curve name used in the plot legend by the following options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eContribute To Legend\u003c/strong\u003e \u0026ndash; This option controls whether the curve will be visible in the plot legend. A curve with an empty name will be removed from legend.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Name\u003c/strong\u003e \u0026ndash; If enabled, ResInsight will create a name for the curve automatically based on the settings in this option group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Name\u003c/strong\u003e \u0026ndash; If \u003cstrong\u003eAuto Name\u003c/strong\u003e is off, you can enter a curve name here. If empty, the curve will be removed from the legend, but still visible in the plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCase Name, Vector name \u0026hellip;\u003c/strong\u003e etc. \u0026ndash; These options controls what part of the summary vector information to use in the curve auto-name.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"copy-and-paste\"\u003eCopy and Paste\u003c/h2\u003e\n\u003cp\u003eCopy and Paste of selections of Summary Plots and Curves, is possible using the Project Tree right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V).\u003c/p\u003e\n\u003ch2 id=\"recursive-summary-file-import\"\u003eRecursive summary file import\u003c/h2\u003e\n\u003cp\u003eWhen using the standard file selection dialog, the user is limited to select files in one directory only. If the interesting files are distributed over multiple directories, the dialog has to be opened once for each directory. The recursive file selection dialog is created to circumvent this limitation. This dialog is able to search a directory tree for files matching a specified pattern.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RecursiveImportDialog2.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe dialog consists of the following fields:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePath Pattern\u003c/strong\u003e: The path filter uses normal wildcard file globbing, like in any unix shell. When the filter ends with a single \u0026ldquo;**\u0026rdquo; (eg. \u0026ldquo;/home/*\u0026quot;), however, ResInsight will search recursively in all subdirectories from that point. This is indicated by \u0026ldquo;\u0026hellip;\u0026rdquo; in the \u003cstrong\u003eEffective Filter\u003c/strong\u003e label below.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003e*\u003c/strong\u003e Matches any number of any characters except the path separator\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e?\u003c/strong\u003e Matches one character exception the directory separator\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e[abc]\u003c/strong\u003e Matches one of the specified characters. Ex. a, b or c\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Pattern\u003c/strong\u003e: The search pattern that applies to the file name.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEffective Filter\u003c/strong\u003e: The effective filter displays the resulting full path search pattern. It is updated on the fly as the user edits the pattern fields. A text string of \u0026ldquo;\u0026hellip;\u0026rdquo; indicates a complete recursive directory search.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eAfter pressing the \u003cstrong\u003eFind\u003c/strong\u003e button, a file search is performed in the root directory and the directories below matching the path pattern. The files found are presented in a list, where the user can check/uncheck each file individually.\u003c/p\u003e\n\u003cp\u003eWhen the \u003cstrong\u003eOK\u003c/strong\u003e button is pressed, all checked files are imported.\u003c/p\u003e\n\u003ch3 id=\"origin-files\"\u003eOrigin Files\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/OriginFileDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eDuring summary file import, ResInsight checks whether the summary file is restarted, i.e. has an origin file. If an origin file is found, the Origin Files dialog is displayed.\u003c/p\u003e\n\u003cp\u003eDepending on what triggered the summary file import, the dialog shows slightly different information. If the summary file import was triggered by a grid file import, the dialog displays information about grid files in addition to the summary origin file(s). If the summary file was imported directly, information about grid files are not relevant and thus not displayed.\u003c/p\u003e\n\u003cp\u003eThe dialog contents are organized in groups:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Grid and Summary Files\u003c/strong\u003e or \u003cstrong\u003eCurrent Summary Files\u003c/strong\u003e: This group displays the name of the main summary file to import. If the import is triggered by a grid file import, the name of the grid file is also displayed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrigin Summary Files\u003c/strong\u003e: This group displays the names of the origin summary file(s) found. If there are more than one file listed, it means that the found origin file also has an origin file. ResInsight will search the \u0026ldquo;chain\u0026rdquo; of summary origin files until it reaches the end.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Options\u003c/strong\u003e There are three options to control how origin summary file are imported\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUnified\u003c/strong\u003e: The main summary files and all origin files are imported into one single summary case\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Cases\u003c/strong\u003e: The main files and all origin files are imported into separate summary cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip\u003c/strong\u003e: Only the main summary file is imported. The origin summary files are skipped.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrigin Grid Files\u003c/strong\u003e: If the summary file import was triggered by a grid file import, this group is visible. It contains a list of the grid files associated to the origin summary files\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eImport Options\u003c/strong\u003e There are two options to control how the grid files are imported\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Cases\u003c/strong\u003e: All \u0026ldquo;origin\u0026rdquo; grid files are imported into separate grid cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkip\u003c/strong\u003e: Only the main grid file is imported. The \u0026ldquo;origin\u0026rdquo; grid files are skipped.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eBy default the file names are displayed using relative path based on the common root folder for all files. In order to display the full path, check the \u003cstrong\u003eShow full paths\u003c/strong\u003e checkbox. Regardless of the checkbox state, there is always a tooltip showing the full path for every file. It is also possible to copy a full path file name to the clipboard. Right click on the file name and select \u003cstrong\u003eCopy file name\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eIf the user selected multiple summary files or grid files, this dialog will be displayed for every file that has an origin summary file. In this case the button \u003cstrong\u003eOK to All\u003c/strong\u003e appears. When this button is clicked, the rest of the files will be imported silently using the same options.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryplots/"
             };
         
@@ -1893,8 +1926,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2019_04/"] = {
                 title:    "What's New in 2019.04",
-                content:  " ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.\nGrid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.\nSee Grid Cross Plots\nSaturation Pressure Plots ResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.\nSee Saturation Pressure Plots\nSector Model Export Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.\nSee Export Sector Model\nWell model for ICD, AICD and ICV ResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - MSW.\nSee Completions and Completion Export\nGrid Model Annotations Annotation objects like text, lines and plolylines can easily be added to a view.\nSee Annotations\nGrid Measurements ResInsight now supports measuring distances and polyline lengths across a Grid.\nSee Measurements\nKeyboard Shortcuts Several new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.\nFor instance will the Delete key now delete any deletable item in the project tree and Ctrl-Alt-S/N/W/E/D/U will change the 3d Camera view to South, North, West East, Down and Up respectively.\nSee Keyboard Shortcuts\n",
-                html:     "\n\n\u003cp\u003eResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.\u003c/p\u003e\n\n\u003ch2 id=\"grid-cross-plots\"\u003eGrid Cross Plots\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/GridCrossPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/plot-window/gridcrossplots/\"\u003eGrid Cross Plots\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"saturation-pressure-plots\"\u003eSaturation Pressure Plots\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/SaturationPressurePlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/plot-window/saturationpressureplots/\"\u003eSaturation Pressure Plots\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"sector-model-export\"\u003eSector Model Export\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/ExportSectorModel_Grid.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eSub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/export/sectormodel/\"\u003eExport Sector Model\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"well-model-for-icd-aicd-and-icv\"\u003eWell model for ICD, AICD and ICV\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/ValveVisualisation.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - \u003cstrong\u003eMSW\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e and  \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"grid-model-annotations\"\u003eGrid Model Annotations\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/Annotations.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAnnotation objects like text, lines and plolylines can easily be added to a view.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/annotations/\"\u003eAnnotations\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"grid-measurements\"\u003eGrid Measurements\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/Measurement.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight now supports measuring distances and polyline lengths across a Grid.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/measurement/\"\u003eMeasurements\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"keyboard-shortcuts\"\u003eKeyboard Shortcuts\u003c/h2\u003e\n\n\u003cp\u003eSeveral new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/KeyboardDel.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/introduction/KeyboardEast.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor instance will the \u003cstrong\u003eDelete\u003c/strong\u003e key now delete any deletable item in the project tree and \u003cstrong\u003eCtrl-Alt-S/N/W/E/D/U\u003c/strong\u003e will change the 3d Camera view to South, North, West East, Down and Up respectively.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/misc/keyboardshortcuts/\"\u003eKeyboard Shortcuts\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "ResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.\nGrid Cross Plots ResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.\nSee Grid Cross Plots\nSaturation Pressure Plots ResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.\nSee Saturation Pressure Plots\nSector Model Export Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.\nSee Export Sector Model\nWell model for ICD, AICD and ICV ResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - MSW.\nSee Completions and Completion Export\nGrid Model Annotations Annotation objects like text, lines and plolylines can easily be added to a view.\nSee Annotations\nGrid Measurements ResInsight now supports measuring distances and polyline lengths across a Grid.\nSee Measurements\nKeyboard Shortcuts Several new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.\nFor instance will the Delete key now delete any deletable item in the project tree and Ctrl-Alt-S/N/W/E/D/U will change the 3d Camera view to South, North, West East, Down and Up respectively.\nSee Keyboard Shortcuts\n",
+                html:     "\u003cp\u003eResInsight 2019.04 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.04 contains a larger number of new and exciting features, some of which are listed below.\u003c/p\u003e\n\u003ch2 id=\"grid-cross-plots\"\u003eGrid Cross Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/GridCrossPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports the creation of cross plots of two results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations, giving a separate color and label for each group.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/plot-window/gridcrossplots/\"\u003eGrid Cross Plots\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"saturation-pressure-plots\"\u003eSaturation Pressure Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/SaturationPressurePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create plots displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/plot-window/saturationpressureplots/\"\u003eSaturation Pressure Plots\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"sector-model-export\"\u003eSector Model Export\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/ExportSectorModel_Grid.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section. These sub-sections can also be refined to a higher resolution.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/export/sectormodel/\"\u003eExport Sector Model\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"well-model-for-icd-aicd-and-icv\"\u003eWell model for ICD, AICD and ICV\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/ValveVisualisation.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports interactive modeling of ICD, AICD and ICV. It is possible to export completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well - \u003cstrong\u003eMSW\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e and  \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"grid-model-annotations\"\u003eGrid Model Annotations\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/Annotations.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAnnotation objects like text, lines and plolylines can easily be added to a view.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/annotations/\"\u003eAnnotations\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"grid-measurements\"\u003eGrid Measurements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/Measurement.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight now supports measuring distances and polyline lengths across a Grid.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/measurement/\"\u003eMeasurements\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"keyboard-shortcuts\"\u003eKeyboard Shortcuts\u003c/h2\u003e\n\u003cp\u003eSeveral new keyboard shortcuts have been added to ResInsight for convenience. The shortcut can be seen by hovering over tool bar icons to show the tooltip for the given action, or seen in the right-click menu for project tree items.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/KeyboardDel.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/introduction/KeyboardEast.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor instance will the \u003cstrong\u003eDelete\u003c/strong\u003e key now delete any deletable item in the project tree and \u003cstrong\u003eCtrl-Alt-S/N/W/E/D/U\u003c/strong\u003e will change the 3d Camera view to South, North, West East, Down and Up respectively.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/misc/keyboardshortcuts/\"\u003eKeyboard Shortcuts\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2019_04/"
             };
         
@@ -1902,8 +1935,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2019_08/"] = {
                 title:    "What's New in 2019.08",
-                content:  " ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.\nPython scripting Basic example on how to update views from Python\nimport rips # Connect to ResInsight instance resInsight = rips.Instance.find() # Check if connection worked if resInsight is not None: # Get a list of all cases cases = resInsight.project.cases() for case in cases: # Get a list of all views views = case.views() for view in views: # Set some parameters for the view view.setShowGridBox(not view.showGridBox()) view.setBackgroundColor(\u0026quot;#3388AA\u0026quot;) # Update the view in ResInsight view.update()  See Python Scripting\nLaunch ResInsight without user interface It is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.\nSee Command Line Interface\nPlotting improvements  Date and time can now be customized to exactly the format you prefer To easily see the difference between history vectors and other vectors, the default style for history vector is symbols without lines Curves in a plot will be hightlighted when left-clicking the curve  See Summary Plotting\n",
-                html:     "\n\n\u003cp\u003eResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.\u003c/p\u003e\n\n\u003ch2 id=\"python-scripting\"\u003ePython scripting\u003c/h2\u003e\n\n\u003cp\u003eBasic example on how to update views from Python\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eimport rips\n# Connect to ResInsight instance\nresInsight = rips.Instance.find()\n\n# Check if connection worked\nif resInsight is not None:\n    # Get a list of all cases\n    cases = resInsight.project.cases()\n    for case in cases:\n        # Get a list of all views\n        views = case.views()\n        for view in views:\n            # Set some parameters for the view\n            view.setShowGridBox(not view.showGridBox())\n            view.setBackgroundColor(\u0026quot;#3388AA\u0026quot;)            \n            # Update the view in ResInsight\n            view.update()\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eSee \u003ca href=\"/scripting/pythonrips/\"\u003ePython Scripting\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"launch-resinsight-without-user-interface\"\u003eLaunch ResInsight without user interface\u003c/h2\u003e\n\n\u003cp\u003eIt is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand Line Interface\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"plotting-improvements\"\u003ePlotting improvements\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDate and time can now be customized to exactly the format you prefer\u003c/li\u003e\n\u003cli\u003eTo easily see the difference between history vectors and other vectors, the default style for history vector is symbols without lines\u003c/li\u003e\n\u003cli\u003eCurves in a plot will be hightlighted when left-clicking the curve\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSee \u003ca href=\"/plot-window/summaryplots/#curve-hightlight\"\u003eSummary Plotting\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "ResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.\nPython scripting Basic example on how to update views from Python\nimport rips\r# Connect to ResInsight instance\rresInsight = rips.Instance.find()\r# Check if connection worked\rif resInsight is not None:\r# Get a list of all cases\rcases = resInsight.project.cases()\rfor case in cases:\r# Get a list of all views\rviews = case.views()\rfor view in views:\r# Set some parameters for the view\rview.setShowGridBox(not view.showGridBox())\rview.setBackgroundColor(\u0026quot;#3388AA\u0026quot;) # Update the view in ResInsight\rview.update()\rSee Python Scripting\nLaunch ResInsight without user interface It is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.\nSee Command Line Interface\nPlotting improvements  Date and time can now be customized to exactly the format you prefer To easily see the difference between history vectors and other vectors, the default style for history vector is symbols without lines Curves in a plot will be hightlighted when left-clicking the curve  See Summary Plotting\n",
+                html:     "\u003cp\u003eResInsight 2019.08 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2019.08 opens up a range of new and efficient workflows by adding Python script support in ResInsight.\u003c/p\u003e\n\u003ch2 id=\"python-scripting\"\u003ePython scripting\u003c/h2\u003e\n\u003cp\u003eBasic example on how to update views from Python\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eimport rips\r\n# Connect to ResInsight instance\r\nresInsight = rips.Instance.find()\r\n\r\n# Check if connection worked\r\nif resInsight is not None:\r\n    # Get a list of all cases\r\n    cases = resInsight.project.cases()\r\n    for case in cases:\r\n        # Get a list of all views\r\n        views = case.views()\r\n        for view in views:\r\n            # Set some parameters for the view\r\n            view.setShowGridBox(not view.showGridBox())\r\n            view.setBackgroundColor(\u0026quot;#3388AA\u0026quot;)            \r\n            # Update the view in ResInsight\r\n            view.update()\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eSee \u003ca href=\"/scripting/pythonrips/\"\u003ePython Scripting\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"launch-resinsight-without-user-interface\"\u003eLaunch ResInsight without user interface\u003c/h2\u003e\n\u003cp\u003eIt is now possible to launch ResInsight as a console application with no user interface. Some workflows might include servers with no graphics card, and the console mode enables use of ResInsight in this context.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand Line Interface\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"plotting-improvements\"\u003ePlotting improvements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eDate and time can now be customized to exactly the format you prefer\u003c/li\u003e\n\u003cli\u003eTo easily see the difference between history vectors and other vectors, the default style for history vector is symbols without lines\u003c/li\u003e\n\u003cli\u003eCurves in a plot will be hightlighted when left-clicking the curve\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plotting\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2019_08/"
             };
         
@@ -1911,8 +1944,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2019_12/"] = {
                 title:    "What's New in 2019.12",
-                content:  " ResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12 is a major update bringing a range of significant new and enhanced features. Some of the most important extensions are listed below.\nComparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\nSupport for Summary Plot Templates ResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for Summary Plot Templates which are defined by a number of curves with preset appearance and vector names. Having tailored a plot setup, the user can save the setup as a template definition to file for later reuse.\nEnsemble RFT data import and plotting ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. The functionality includes advanced color schemes for differentiation of curves, computation of statistics, and import of observed ensemble RFT data from FMU.\nCommand line interface for Summary plotting ResInsight scripting has been extended with summary plotting commands that plot summary vectors based on textual specifications including the use of wildcards for selection and filtering. For more information and examples of use, see Command line interface for Summary Plotting.\nText-Based Curve Creation and Source Stepping Text-Based Curve Creation allows specification of a list of vectors for plotting based on selected sources. The history of text-based curve specifications are recorded to allow for effective use.\nThis is possible to combine with Summary Source Stepping which has been extended to further support swift stepping through multiple vectors.\nExport Contour plot data ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information, see Contour Map Export.\nWell Bore Stability plots Major extensions and enhancements have been added to Well Bore Stability plots for Geomechanical cases. Well Bore Stability plots are specialized Well Log Plots to visualize Formations, Well Path Attributes as well as a set of well path derived curves in different tracks.\nChanges in behavior and defaults Info Box: Change of defaults for Statistics Options Following multiple user requests, the defaults for Statistics Options in Info Box have been changed to:\n Statistics Time Range: Current Time Step Statistics Cell Range: Visible Cells  ",
-                html:     "\n\n\u003cp\u003eResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.\nVersion 2019.12 is a major update bringing a range of significant new and enhanced features.\nSome of the most important extensions are listed below.\u003c/p\u003e\n\n\u003ch2 id=\"comparison-view\"\u003eComparison View\u003c/h2\u003e\n\n\u003cp\u003eResInsight offers a \u003ca href=\"/3d-main-window/comparisonview/\"\u003eComparison View\u003c/a\u003e to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonView.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"support-for-summary-plot-templates\"\u003eSupport for Summary Plot Templates\u003c/h2\u003e\n\n\u003cp\u003eResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for\n\u003ca href=\"/plot-window/summaryplottemplate/\"\u003eSummary Plot Templates\u003c/a\u003e which are defined by a number of curves with preset appearance and vector names.\nHaving tailored a plot setup, the user can save the setup as a template definition to file for later reuse.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"ensemble-rft-data-import-and-plotting\"\u003eEnsemble RFT data import and plotting\u003c/h2\u003e\n\n\u003cp\u003eResInsight allows the user to create a \u003ca href=\"/plot-window/ensemblerftplot/\"\u003eensemble RFT plot\u003c/a\u003e similar to summary ensemble plots. The functionality includes advanced color schemes for differentiation of curves, computation of statistics, and import of observed ensemble RFT data from FMU.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"command-line-interface-for-summary-plotting\"\u003eCommand line interface for Summary plotting\u003c/h2\u003e\n\n\u003cp\u003eResInsight scripting has been extended with summary plotting commands that plot summary vectors based on textual specifications including the use of wildcards for selection and filtering. For more information and examples of use, see \u003ca href=\"/scripting/commandlineinterface/#summary-plotting\"\u003eCommand line interface for Summary Plotting\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"text-based-curve-creation-and-source-stepping\"\u003eText-Based Curve Creation and Source Stepping\u003c/h2\u003e\n\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/#property-editor\"\u003eText-Based Curve Creation\u003c/a\u003e allows specification of a list of vectors for plotting based on selected sources. The history of text-based curve specifications are recorded to allow for effective use.\u003c/p\u003e\n\n\u003cp\u003eThis is possible to combine with \u003ca href=\"/scripting/commandlineinterface/\"\u003eSummary Source Stepping\u003c/a\u003e which has been extended to further support swift stepping through multiple vectors.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"export-contour-plot-data\"\u003eExport Contour plot data\u003c/h2\u003e\n\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information,\nsee \u003ca href=\"/export/contourmapexport/\"\u003eContour Map Export\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMap.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"well-bore-stability-plots\"\u003eWell Bore Stability plots\u003c/h2\u003e\n\n\u003cp\u003eMajor extensions and enhancements have been added to Well Bore Stability plots for Geomechanical cases. Well Bore Stability plots are specialized \u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e to visualize \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e, \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Path Attributes\u003c/a\u003e as well as a set of well path derived curves in different tracks.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStability.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"changes-in-behavior-and-defaults\"\u003eChanges in behavior and defaults\u003c/h2\u003e\n\n\u003ch3 id=\"info-box-change-of-defaults-for-statistics-options\"\u003eInfo Box: Change of defaults for Statistics Options\u003c/h3\u003e\n\n\u003cp\u003eFollowing multiple user requests, the defaults for \u003cstrong\u003eStatistics Options\u003c/strong\u003e in Info Box have been changed to:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eStatistics Time Range: \u003cem\u003eCurrent Time Step\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003eStatistics Cell Range: \u003cem\u003eVisible Cells\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InfoBoxConfig.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "ResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12 is a major update bringing a range of significant new and enhanced features. Some of the most important extensions are listed below.\nComparison View ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\nSupport for Summary Plot Templates ResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for Summary Plot Templates which are defined by a number of curves with preset appearance and vector names. Having tailored a plot setup, the user can save the setup as a template definition to file for later reuse.\nEnsemble RFT data import and plotting ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. The functionality includes advanced color schemes for differentiation of curves, computation of statistics, and import of observed ensemble RFT data from FMU.\nCommand line interface for Summary plotting ResInsight scripting has been extended with summary plotting commands that plot summary vectors based on textual specifications including the use of wildcards for selection and filtering. For more information and examples of use, see Command line interface for Summary Plotting.\nText-Based Curve Creation and Source Stepping Text-Based Curve Creation allows specification of a list of vectors for plotting based on selected sources. The history of text-based curve specifications are recorded to allow for effective use.\nThis is possible to combine with Summary Source Stepping which has been extended to further support swift stepping through multiple vectors.\nExport Contour plot data ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information, see Contour Map Export.\nWell Bore Stability plots Major extensions and enhancements have been added to Well Bore Stability plots for Geomechanical cases. Well Bore Stability plots are specialized Well Log Plots to visualize Formations, Well Path Attributes as well as a set of well path derived curves in different tracks.\nChanges in behavior and defaults Info Box: Change of defaults for Statistics Options Following multiple user requests, the defaults for Statistics Options in Info Box have been changed to:\n Statistics Time Range: Current Time Step Statistics Cell Range: Visible Cells  ",
+                html:     "\u003cp\u003eResInsight 2019.12 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.\nVersion 2019.12 is a major update bringing a range of significant new and enhanced features. \nSome of the most important extensions are listed below.\u003c/p\u003e\n\u003ch2 id=\"comparison-view\"\u003eComparison View\u003c/h2\u003e\n\u003cp\u003eResInsight offers a \u003ca href=\"/3d-main-window/comparisonview/\"\u003eComparison View\u003c/a\u003e to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"support-for-summary-plot-templates\"\u003eSupport for Summary Plot Templates\u003c/h2\u003e\n\u003cp\u003eResInsight 2019.12 includes numerous enhancements to Summary Plots and notably support for \n\u003ca href=\"/plot-window/summaryplottemplate/\"\u003eSummary Plot Templates\u003c/a\u003e which are defined by a number of curves with preset appearance and vector names. \nHaving tailored a plot setup, the user can save the setup as a template definition to file for later reuse.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"ensemble-rft-data-import-and-plotting\"\u003eEnsemble RFT data import and plotting\u003c/h2\u003e\n\u003cp\u003eResInsight allows the user to create a \u003ca href=\"/plot-window/ensemblerftplot/\"\u003eensemble RFT plot\u003c/a\u003e similar to summary ensemble plots. The functionality includes advanced color schemes for differentiation of curves, computation of statistics, and import of observed ensemble RFT data from FMU.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"command-line-interface-for-summary-plotting\"\u003eCommand line interface for Summary plotting\u003c/h2\u003e\n\u003cp\u003eResInsight scripting has been extended with summary plotting commands that plot summary vectors based on textual specifications including the use of wildcards for selection and filtering. For more information and examples of use, see \u003ca href=\"/scripting/commandlineinterface/#summary-plotting\"\u003eCommand line interface for Summary Plotting\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"text-based-curve-creation-and-source-stepping\"\u003eText-Based Curve Creation and Source Stepping\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/#property-editor\"\u003eText-Based Curve Creation\u003c/a\u003e allows specification of a list of vectors for plotting based on selected sources. The history of text-based curve specifications are recorded to allow for effective use.\u003c/p\u003e\n\u003cp\u003eThis is possible to combine with \u003ca href=\"/scripting/commandlineinterface/\"\u003eSummary Source Stepping\u003c/a\u003e which has been extended to further support swift stepping through multiple vectors.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"export-contour-plot-data\"\u003eExport Contour plot data\u003c/h2\u003e\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. For more information, \nsee \u003ca href=\"/export/contourmapexport/\"\u003eContour Map Export\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMap.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"well-bore-stability-plots\"\u003eWell Bore Stability plots\u003c/h2\u003e\n\u003cp\u003eMajor extensions and enhancements have been added to Well Bore Stability plots for Geomechanical cases. Well Bore Stability plots are specialized \u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e to visualize \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e, \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Path Attributes\u003c/a\u003e as well as a set of well path derived curves in different tracks.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStability.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"changes-in-behavior-and-defaults\"\u003eChanges in behavior and defaults\u003c/h2\u003e\n\u003ch3 id=\"info-box-change-of-defaults-for-statistics-options\"\u003eInfo Box: Change of defaults for Statistics Options\u003c/h3\u003e\n\u003cp\u003eFollowing multiple user requests, the defaults for \u003cstrong\u003eStatistics Options\u003c/strong\u003e in Info Box have been changed to:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eStatistics Time Range: \u003cem\u003eCurrent Time Step\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003eStatistics Cell Range: \u003cem\u003eVisible Cells\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InfoBoxConfig.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2019_12/"
             };
         
@@ -1920,8 +1953,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2019_12_1/"] = {
                 title:    "What's New in 2019.12.1",
-                content:  " ResInsight 2019.12.1 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12.1 consists of a few critical issues and minor functionality changes.\nBugfixes Release info on GitHub\nChanges in behavior WELSEGS Output of segment depth is based on center of segment. Previously the segment end was reported.\nExport of Completions and MSW \nMultiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell. Now, when multiple fracture are detected, they are combined and reported similar to other completion types.\nExport of Completions \n",
-                html:     "\n\n\u003cp\u003eResInsight 2019.12.1 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.\nVersion 2019.12.1 consists of a few critical issues and minor functionality changes.\u003c/p\u003e\n\n\u003ch2 id=\"bugfixes\"\u003eBugfixes\u003c/h2\u003e\n\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/tag/v2019.12.1\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"changes-in-behavior\"\u003eChanges in behavior\u003c/h2\u003e\n\n\u003ch3 id=\"welsegs\"\u003eWELSEGS\u003c/h3\u003e\n\n\u003cp\u003eOutput of segment depth is based on center of segment. Previously the segment end was reported.\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"/export/completionexport/#exported-msw-data\"\u003e Export of Completions and MSW \u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"multiple-completions-in-same-cell\"\u003eMultiple completions in same cell\u003c/h3\u003e\n\n\u003cp\u003eIn previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell. Now, when multiple fracture are detected, they are combined and reported similar to other completion types.\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"/export/completionexport/\"\u003e Export of Completions \u003c/a\u003e\u003c/p\u003e\n",
+                content:  "ResInsight 2019.12.1 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations. Version 2019.12.1 consists of a few critical issues and minor functionality changes.\nBugfixes Release info on GitHub\nChanges in behavior WELSEGS Output of segment depth is based on center of segment. Previously the segment end was reported.\nExport of Completions and MSW \nMultiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell. Now, when multiple fracture are detected, they are combined and reported similar to other completion types.\nExport of Completions \n",
+                html:     "\u003cp\u003eResInsight 2019.12.1 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for reservoir models and simulations.\nVersion 2019.12.1 consists of a few critical issues and minor functionality changes.\u003c/p\u003e\n\u003ch2 id=\"bugfixes\"\u003eBugfixes\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/tag/v2019.12.1\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"changes-in-behavior\"\u003eChanges in behavior\u003c/h2\u003e\n\u003ch3 id=\"welsegs\"\u003eWELSEGS\u003c/h3\u003e\n\u003cp\u003eOutput of segment depth is based on center of segment. Previously the segment end was reported.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/export/completionexport/\"\u003e Export of Completions and MSW \u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"multiple-completions-in-same-cell\"\u003eMultiple completions in same cell\u003c/h3\u003e\n\u003cp\u003eIn previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell. Now, when multiple fracture are detected, they are combined and reported similar to other completion types.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/export/completionexport/\"\u003e Export of Completions \u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2019_12_1/"
             };
         
@@ -1929,8 +1962,8 @@ if (!doNotTrack) {
          
             window.store["/import/lasfile/"] = {
                 title:    "Log ASCII Standard File",
-                content:  " Log ASCII Standard (LAS) is a standard file format common in the oil-and-gas industry to store well log information.\nImporting a LAS file Log ASCII Standard (LAS) files can be imported using the command: File-\u0026gt;Import-\u0026gt; Well Data-\u0026gt;Import Well Logs from File.\nResInsight will look for the the well name in the imported LAS-files among the existing Well Paths. If a match is found, the LAS-file is placed as a child of that well path. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.\nIf the LAS-file does not contain a well name, the file name is used instead.\nMoving a LAS file If ResInsight\u0026rsquo;s automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file right-click menu click Move LAS File to Well Path and select destination well path.\nLook for an Existing Well Path Well names may vary slightly among different files from the same well. When importing a well log file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:\n First remove any prefix (like xxxxx1111/1111- or xxxxx1111/1111_) Then try an exact name match If not found, try to match the names ignoring all spaces, dashes and underscores If still no match, no existing well was found and a new one is created  Supported Date Formats During LAS import, ResInsight parses a date on file according to the following expressions. Supported separators between day, month, and year are space, underscore, hyphen, and dot.\n   Expression Description     d day as number without a leading zero (1 to 31), e.g. 7   dd day as a two digit number (01 to 31), e.g. 07   M month as number without a leading zero (1-12), e.g. 8   MM month as a two digit number (01-12), e.g. 08   MMM short month name in uppercase or lowercase (\u0026lsquo;Jan\u0026rsquo; to \u0026lsquo;Dec\u0026rsquo;), e.g. AUG   yy year as a two digit number (00-99), e.g. 19   yyyy year as a four digit number, e.g. 2019    Examples of supported date expressions are listed in the following table.\n   Expression Example     yyyy MM dd 2019 08 16   yyyy-MM-dd 2019-08-16   yyyy MMM dd 2019 Aug 16   MMM dd yyyy Aug 16 2019   d.M.yy 1.8.89   dd_MM_yyyy 16_08_2019   dd.MMM.yyyy 16.Aug.2019    ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eLog ASCII Standard (LAS) is a standard file format common in the oil-and-gas industry to store well log information.\u003c/p\u003e\n\n\u003ch2 id=\"importing-a-las-file\"\u003eImporting a LAS file\u003c/h2\u003e\n\n\u003cp\u003eLog ASCII Standard (LAS) files can be imported using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt; Well Data-\u0026gt;Import Well Logs from File\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eResInsight will look for the the well name in the imported LAS-files among the existing \u003cstrong\u003eWell Paths\u003c/strong\u003e.\nIf a match is found, the LAS-file is placed as a child of that well path. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LasFilesInTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIf the LAS-file does not contain a well name, the file name is used instead.\u003c/p\u003e\n\n\u003ch3 id=\"moving-a-las-file\"\u003eMoving a LAS file\u003c/h3\u003e\n\n\u003cp\u003eIf ResInsight\u0026rsquo;s automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file right-click menu click \u003cstrong\u003eMove LAS File to Well Path\u003c/strong\u003e and select destination well path.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MoveLasFileMenu.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"look-for-an-existing-well-path\"\u003eLook for an Existing Well Path\u003c/h3\u003e\n\n\u003cp\u003eWell names may vary slightly among different files from the same well. When importing a well log file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eFirst remove any prefix (like \u003ccode\u003exxxxx1111/1111-\u003c/code\u003e or \u003ccode\u003exxxxx1111/1111_\u003c/code\u003e)\u003c/li\u003e\n\u003cli\u003eThen try an exact name match\u003c/li\u003e\n\u003cli\u003eIf not found, try to match the names ignoring all spaces, dashes and underscores\u003c/li\u003e\n\u003cli\u003eIf still no match, no existing well was found and a new one is created\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"supported-date-formats\"\u003eSupported Date Formats\u003c/h2\u003e\n\n\u003cp\u003eDuring LAS import, ResInsight parses a date on file according to the following expressions. Supported separators between day, month, and year are \u003cstrong\u003espace\u003c/strong\u003e, \u003cstrong\u003eunderscore\u003c/strong\u003e, \u003cstrong\u003ehyphen\u003c/strong\u003e, and \u003cstrong\u003edot\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eExpression\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ed\u003c/td\u003e\n\u003ctd\u003eday as number without a leading zero (1 to 31), e.g. \u003cem\u003e7\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edd\u003c/td\u003e\n\u003ctd\u003eday as a two digit number (01 to 31), e.g. \u003cem\u003e07\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eM\u003c/td\u003e\n\u003ctd\u003emonth as number without a leading zero (1-12), e.g. \u003cem\u003e8\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMM\u003c/td\u003e\n\u003ctd\u003emonth as a two digit number (01-12), e.g. \u003cem\u003e08\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMM\u003c/td\u003e\n\u003ctd\u003eshort month name in uppercase or lowercase (\u0026lsquo;Jan\u0026rsquo; to \u0026lsquo;Dec\u0026rsquo;), e.g. \u003cem\u003eAUG\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eyy\u003c/td\u003e\n\u003ctd\u003eyear as a two digit number (00-99), e.g. \u003cem\u003e19\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eyyyy\u003c/td\u003e\n\u003ctd\u003eyear as a four digit number, e.g. \u003cem\u003e2019\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eExamples of supported date expressions are listed in the following table.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eExpression\u003c/th\u003e\n\u003cth\u003eExample\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eyyyy MM dd\u003c/td\u003e\n\u003ctd\u003e2019 08 16\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eyyyy-MM-dd\u003c/td\u003e\n\u003ctd\u003e2019-08-16\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eyyyy MMM dd\u003c/td\u003e\n\u003ctd\u003e2019 Aug 16\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMM dd yyyy\u003c/td\u003e\n\u003ctd\u003eAug 16 2019\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ed.M.yy\u003c/td\u003e\n\u003ctd\u003e1.8.89\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edd_MM_yyyy\u003c/td\u003e\n\u003ctd\u003e16_08_2019\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edd.MMM.yyyy\u003c/td\u003e\n\u003ctd\u003e16.Aug.2019\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
+                content:  "Log ASCII Standard (LAS) is a standard file format common in the oil-and-gas industry to store well log information.\nImporting a LAS file Log ASCII Standard (LAS) files can be imported using the command: File-\u0026gt;Import-\u0026gt; Well Data-\u0026gt;Import Well Logs from File.\nResInsight will look for the the well name in the imported LAS-files among the existing Well Paths. If a match is found, the LAS-file is placed as a child of that well path. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.\nIf the LAS-file does not contain a well name, the file name is used instead.\nMoving a LAS file If ResInsight\u0026rsquo;s automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file right-click menu click Move LAS File to Well Path and select destination well path.\nLook for an Existing Well Path Well names may vary slightly among different files from the same well. When importing a well log file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:\n First remove any prefix (like xxxxx1111/1111- or xxxxx1111/1111_) Then try an exact name match If not found, try to match the names ignoring all spaces, dashes and underscores If still no match, no existing well was found and a new one is created  Supported Date Formats During LAS import, ResInsight parses a date on file according to the following expressions. Supported separators between day, month, and year are space, underscore, hyphen, and dot.\n   Expression Description     d day as number without a leading zero (1 to 31), e.g. 7   dd day as a two digit number (01 to 31), e.g. 07   M month as number without a leading zero (1-12), e.g. 8   MM month as a two digit number (01-12), e.g. 08   MMM short month name in uppercase or lowercase (\u0026lsquo;Jan\u0026rsquo; to \u0026lsquo;Dec\u0026rsquo;), e.g. AUG   yy year as a two digit number (00-99), e.g. 19   yyyy year as a four digit number, e.g. 2019    Examples of supported date expressions are listed in the following table.\n   Expression Example     yyyy MM dd 2019 08 16   yyyy-MM-dd 2019-08-16   yyyy MMM dd 2019 Aug 16   MMM dd yyyy Aug 16 2019   d.M.yy 1.8.89   dd_MM_yyyy 16_08_2019   dd.MMM.yyyy 16.Aug.2019    ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eLog ASCII Standard (LAS) is a standard file format common in the oil-and-gas industry to store well log information.\u003c/p\u003e\n\u003ch2 id=\"importing-a-las-file\"\u003eImporting a LAS file\u003c/h2\u003e\n\u003cp\u003eLog ASCII Standard (LAS) files can be imported using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt; Well Data-\u0026gt;Import Well Logs from File\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eResInsight will look for the the well name in the imported LAS-files among the existing \u003cstrong\u003eWell Paths\u003c/strong\u003e.\nIf a match is found, the LAS-file is placed as a child of that well path. If not, a new empty well path entry is created with the imported LAS-file under it. A well path may have more than one LAS-files as children.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LasFilesInTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf the LAS-file does not contain a well name, the file name is used instead.\u003c/p\u003e\n\u003ch3 id=\"moving-a-las-file\"\u003eMoving a LAS file\u003c/h3\u003e\n\u003cp\u003eIf ResInsight\u0026rsquo;s automatic well matching fails and a LAS-file is matched with the wrong well path, it is possible to move the LAS-file to the correct well path. Select the LAS-file right-click menu click \u003cstrong\u003eMove LAS File to Well Path\u003c/strong\u003e and select destination well path.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MoveLasFileMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"look-for-an-existing-well-path\"\u003eLook for an Existing Well Path\u003c/h3\u003e\n\u003cp\u003eWell names may vary slightly among different files from the same well. When importing a well log file, ResInsight have to look for an existing well path item to ensure that the well log data and well path are imported to the correct well path item. The lookup is based on name comparison this way:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eFirst remove any prefix (like \u003ccode\u003exxxxx1111/1111-\u003c/code\u003e or \u003ccode\u003exxxxx1111/1111_\u003c/code\u003e)\u003c/li\u003e\n\u003cli\u003eThen try an exact name match\u003c/li\u003e\n\u003cli\u003eIf not found, try to match the names ignoring all spaces, dashes and underscores\u003c/li\u003e\n\u003cli\u003eIf still no match, no existing well was found and a new one is created\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"supported-date-formats\"\u003eSupported Date Formats\u003c/h2\u003e\n\u003cp\u003eDuring LAS import, ResInsight parses a date on file according to the following expressions. Supported separators between day, month, and year are \u003cstrong\u003espace\u003c/strong\u003e, \u003cstrong\u003eunderscore\u003c/strong\u003e, \u003cstrong\u003ehyphen\u003c/strong\u003e, and \u003cstrong\u003edot\u003c/strong\u003e.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eExpression\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ed\u003c/td\u003e\n\u003ctd\u003eday as number without a leading zero (1 to 31), e.g. \u003cem\u003e7\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edd\u003c/td\u003e\n\u003ctd\u003eday as a two digit number (01 to 31), e.g. \u003cem\u003e07\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eM\u003c/td\u003e\n\u003ctd\u003emonth as number without a leading zero (1-12), e.g. \u003cem\u003e8\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMM\u003c/td\u003e\n\u003ctd\u003emonth as a two digit number (01-12), e.g. \u003cem\u003e08\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMM\u003c/td\u003e\n\u003ctd\u003eshort month name in uppercase or lowercase (\u0026lsquo;Jan\u0026rsquo; to \u0026lsquo;Dec\u0026rsquo;), e.g. \u003cem\u003eAUG\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eyy\u003c/td\u003e\n\u003ctd\u003eyear as a two digit number (00-99), e.g. \u003cem\u003e19\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eyyyy\u003c/td\u003e\n\u003ctd\u003eyear as a four digit number, e.g. \u003cem\u003e2019\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eExamples of supported date expressions are listed in the following table.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eExpression\u003c/th\u003e\n\u003cth\u003eExample\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eyyyy MM dd\u003c/td\u003e\n\u003ctd\u003e2019 08 16\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eyyyy-MM-dd\u003c/td\u003e\n\u003ctd\u003e2019-08-16\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eyyyy MMM dd\u003c/td\u003e\n\u003ctd\u003e2019 Aug 16\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMM dd yyyy\u003c/td\u003e\n\u003ctd\u003eAug 16 2019\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ed.M.yy\u003c/td\u003e\n\u003ctd\u003e1.8.89\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edd_MM_yyyy\u003c/td\u003e\n\u003ctd\u003e16_08_2019\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edd.MMM.yyyy\u003c/td\u003e\n\u003ctd\u003e16.Aug.2019\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
                 url:      "/import/lasfile/"
             };
         
@@ -1939,7 +1972,7 @@ if (!doNotTrack) {
             window.store["/3d-main-window/"] = {
                 title:    "3D Main Window",
                 content:  "This is the main window of ResInsight for all 3D related functionality and visualization. As seen, the 3D Main Window has a central area and several docking windows surrounding it. The different docking windows cover the following:\n Project Tree \u0026ndash; contains all application objects in a tree structure. Property Editor \u0026ndash; displays all properties for selected object in the Project Tree Process Monitor \u0026ndash; displays output from Octave when executing Octave scripts Result Info \u0026ndash; displays info for the selected object in the 3D scene Result Plot \u0026ndash; displays curves based on result values for the selected cells in the 3D scene Messages \u0026ndash; displays occasional info and warnings related to operations executed.  In addition, a selected subset of actions are presented as controls in the toolbar. The following subchapters describe the functionality and visualization pertinent to the 3D Main Window.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightUIMediumSize.png\" alt=\"ResInsight User Interface\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis is the main window of ResInsight for all 3D related functionality and visualization.\nAs seen, the \u003cstrong\u003e3D Main Window\u003c/strong\u003e has a central area and several docking windows surrounding it.\nThe different docking windows cover the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eProject Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProcess Monitor\u003c/strong\u003e \u0026ndash; displays output from Octave when executing Octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Info\u003c/strong\u003e \u0026ndash; displays info for the selected object in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Plot\u003c/strong\u003e \u0026ndash; displays curves based on result values for the selected cells in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMessages\u003c/strong\u003e \u0026ndash; displays occasional info and warnings related to operations executed.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eIn addition, a selected subset of actions are presented as controls in the toolbar.\nThe following subchapters describe the functionality and visualization pertinent to the \u003cstrong\u003e3D Main Window\u003c/strong\u003e.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightUIMediumSize.png\" alt=\"ResInsight User Interface\"\u003e\u003c/p\u003e\n\u003cp\u003eThis is the main window of ResInsight for all 3D related functionality and visualization. \nAs seen, the \u003cstrong\u003e3D Main Window\u003c/strong\u003e has a central area and several docking windows surrounding it. \nThe different docking windows cover the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eProject Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProcess Monitor\u003c/strong\u003e \u0026ndash; displays output from Octave when executing Octave scripts\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Info\u003c/strong\u003e \u0026ndash; displays info for the selected object in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Plot\u003c/strong\u003e \u0026ndash; displays curves based on result values for the selected cells in the 3D scene\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMessages\u003c/strong\u003e \u0026ndash; displays occasional info and warnings related to operations executed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIn addition, a selected subset of actions are presented as controls in the toolbar.\nThe following subchapters describe the functionality and visualization pertinent to the \u003cstrong\u003e3D Main Window\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/3d-main-window/"
             };
         
@@ -1947,8 +1980,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/cellresults/"] = {
                 title:    "Cell Results",
-                content:  " The main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per cell over a region of the grid. A Cell Result is also referred to as a Property.\nCell Results are used in several operations and settings:\n Cell Colors Cell Edge Result (Eclipse Only) Separate Fault Result (Eclipse Only) Property Filters Well Log Extraction Curves Cell Result Time History Curves  In the property panel of all those, the same options are used to define the Cell Result of interest.\nIn the following we will describe these options.\nEclipse Result Types Results and difference options are displayed by the Property Editor.\nThe different result types are:\n Dynamic \u0026ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f. Derived Results Static \u0026ndash; Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. Derived Results SourSimRL \u0026ndash; Available if SourSimRL results have been imported, c.f. SourSimRL Import Generated \u0026ndash; Results generated by an Octave Script Input Property \u0026ndash; Directly imported Eclipse properties from ascii files Formation Names \u0026ndash; Lists only the Active Formation Names selected on the case, c.f. Formations Flow Diagnostics \u0026ndash; Flow diagnostic results derived from a flux field, c.f. below Injection Flooding \u0026ndash; Calculation of derived property based on one or more selected simulation tracers, c.f. below  Difference options are:\n Difference Case \u0026ndash; Base case for calculation of difference Base Time Step \u0026ndash; Base time step for calculation of difference  The difference option is not applicable for TERNARY result display.\n\rFlow Diagnostic Results ResInsight has embedded Flow Diagnostics calculations made available using the Flow Diagnostics result type. These results make it easier to see how and where wells interact with the reservoir and each other. It is possible to select exactly what wells to investigate, and even the possible opposite flow part of the well.\nSee also Flow Diagnostics Plots and Flow Characteristics Plot\nMethod The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital.\nThis method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.\nA more elaborate description of the technique and how it can be utilized, can be found at Sintef\u0026rsquo;s web site. The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.\nThe methodology is also described in: The application of flow diagnostics for reservoir management SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: 10.2118\u0026frasl;171557-PA\nCross Flow and Opposite Flow The opposite flow of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections. Each well is assigned an opposite flow name by adding \u0026ldquo;-XF\u0026rdquo; to the end of the name. \u0026ldquo;-XF\u0026rdquo; was chosen as a reference to Cross Flow.\nIn this way, a producer will have two tracer names: The \u0026ldquo;well name\u0026rdquo; as a producer tracer, and \u0026ldquo;well name-XF\u0026rdquo; as an injector tracer.\nDefining Results There are several options available to define the particular result you want to target, as shown below:\nThere are two main selections you need to make: The tracers and the result property\n Tracers \u0026ndash; Option to select how/what tracers to use. Available options are:  All Injectors and Producers \u0026ndash; Selects all the wells, including the opposite flow tracers All Producers \u0026ndash; Selects all producer tracers, including the opposite flow tracers of injectors. All Injectors \u0026ndash; Selects all injector tracers, including the opposite flow tracers of producers. By Selection \u0026ndash; Displays lists of all the injector tracers and producer tracers side-by-side allowing any to be selected freely.  Both lists of selectable tracers can be filtered by typing in parts of the name. The tracers will have a suffix of [I/P] if they are both injector and producer, thus appearing in both lists. All producers communicating with the selected injectors (and vice-versa) can be selected with the \u0026ldquo;Add Communicator\u0026rdquo; buttons.   Phases \u0026ndash; Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the Time Of Flight result property will be available in the list below. Result property \u0026ndash; Displays a list of the available results:  Residence Time \u0026ndash; The time for some fluid in the cell to reach a producer, or the time it takes to reach the cell from an injector. The option changes name depending on the selection of injectors and producers and will be Forward Time of Flight if only injectors are selected and Reverse Time of Flight if only producers are selected. When selecting several tracers, the time of flight values from each of the tracers are weighted by their cell fraction before they are averaged. The suffix (Average) will then be added to the option label. Tracer Cell Fraction (Sum) \u0026ndash; The volume fraction of a cell occupied by the selected tracers. The injector and producer tracers counts as independent in this regard, so the sum of fractions for all the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers are selected, the total sum will normally reach 2.0. Drainage/Flooding Regions \u0026ndash; Shows which of the selected tracers that has the largest fraction in each cell. This is shown as a category result displaying a color for each tracer, and the names in the legend. If only injectors are selected, this option will be labelled Drainage Regions and if only producers are selected, it is called Flooding Regions. Injector Producer Communication \u0026ndash; The communication in a cell between a set of producers and a set of injectors is calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell. This produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers have a high influence.   On-Demand Calculation The flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.\nInjection Flooding This result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is Water Flooded PV. Please refer to Derived Results for more information.\n Tracers \u0026ndash; Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter \u0026ldquo;F\u0026rdquo;. Select the tracers you want to investigate. Result Property \u0026ndash; Select the variable you want to calculate. (Number Of Flooded PV is currently the only one)  Geomechanical Results Geomechanical results are sorted in different Result Positions:\n Nodal \u0026ndash; Results given a value per node in the grid Element Nodal \u0026ndash; Results with values per element node Integration Point \u0026ndash; Results with values per integration point. These are displayed in the same way as element nodal results. Element Nodal on Face \u0026ndash; Results with values transformed to element faces or intersections. See Element Nodal on Face for more information Formation Names \u0026ndash; Lists the Active Formation Names selected on the case. ( See Formations ) Element \u0026ndash; Imported element property table results. One value pr element. See Element Property Table Import  Several derived cell properties are calculated. Please refer to Derived Results for more information.\nRelative Result Options This group of options controls time-lapse results to be calculated. ( See Relative Results for more information )\nSelect Color Result In the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing Select Color Result. The corresponding result property will be shown in the Property Editor.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultsOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per\ncell over a region of the grid. A Cell Result is also referred to as a \u003cem\u003eProperty\u003c/em\u003e.\u003c/p\u003e\n\n\u003cp\u003eCell Results are used in several operations and settings:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Colors\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Edge Result\u003c/strong\u003e (Eclipse Only)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e (Eclipse Only)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Log Extraction Curves\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Result Time History Curves\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eIn the property panel of all those, the same options are used to define the Cell Result of interest.\u003cbr /\u003e\nIn the following we will describe these options.\u003c/p\u003e\n\n\u003ch2 id=\"eclipse-result-types\"\u003eEclipse Result Types\u003c/h2\u003e\n\n\u003cp\u003eResults and difference options are displayed by the Property Editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultTypes.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe different result types are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDynamic\u003c/strong\u003e \u0026ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f.\n\u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatic\u003c/strong\u003e \u0026ndash; Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSourSimRL\u003c/strong\u003e \u0026ndash; Available if SourSimRL results have been imported, c.f. \u003ca href=\"/import/soursimrlresults/\"\u003eSourSimRL Import\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e \u0026ndash; Results generated by an Octave Script\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInput Property\u003c/strong\u003e \u0026ndash; Directly imported Eclipse properties from ascii files\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Names\u003c/strong\u003e \u0026ndash; Lists only the Active Formation Names selected on the case, c.f. \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Diagnostics\u003c/strong\u003e \u0026ndash; Flow diagnostic results derived from a flux field,\nc.f. \u003ca href=\"/3d-main-window/cellresults/#flow-diagnostic-results\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjection Flooding\u003c/strong\u003e \u0026ndash; Calculation of derived property based on one or more selected simulation tracers,\nc.f. \u003ca href=\"/3d-main-window/cellresults/#injection-flooding\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eDifference options are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDifference Case\u003c/strong\u003e \u0026ndash; Base case for calculation of difference\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase Time Step\u003c/strong\u003e \u0026ndash; Base time step for calculation of difference\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe difference option is not applicable for TERNARY result display.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"flow-diagnostic-results\"\u003eFlow Diagnostic Results\u003c/h3\u003e\n\n\u003cp\u003eResInsight has embedded Flow Diagnostics calculations made available using the \u003cstrong\u003eFlow Diagnostics\u003c/strong\u003e result type.\nThese results make it easier to see how and where wells interact with the reservoir and each other.\nIt is possible to select exactly what wells to investigate, and even the possible \u003cem\u003eopposite flow\u003c/em\u003e part of the well.\u003c/p\u003e\n\n\u003cp\u003eSee also \u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003e Flow Diagnostics Plots\u003c/a\u003e and \u003ca href=\"/plot-window/flowdiagnosticsplots/#flow-characteristics-plot\"\u003e Flow Characteristics Plot\u003c/a\u003e\u003c/p\u003e\n\n\u003ch4 id=\"method\"\u003eMethod\u003c/h4\u003e\n\n\u003cp\u003eThe calculations are performed by a library called \u003ca href=\"https://github.com/OPM/opm-flowdiagnostics\"\u003eopm-flowdiagnostics\u003c/a\u003e developed by \u003ca href=\"http://www.sintef.no/sintef-ikt/#/\"\u003eSINTEF Digital\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eThis method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.\u003c/p\u003e\n\n\u003cp\u003eA more elaborate description of the technique and how it can be  utilized, can be found at Sintef\u0026rsquo;s \u003ca href=\"http://www.sintef.no/projectweb/mrst/modules/diagnostics/\"\u003eweb site\u003c/a\u003e. The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.\u003c/p\u003e\n\n\u003cp\u003eThe methodology is also described in:\n\u003ca href=\"http://folk.ntnu.no/andreas/papers/diagnostics.pdf\"\u003eThe application of flow diagnostics for reservoir management\u003c/a\u003e SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: \u003ca href=\"https://dx.doi.org/10.2118/171557-PA\"\u003e10.\u003csup\u003e2118\u003c/sup\u003e\u0026frasl;\u003csub\u003e171557\u003c/sub\u003e-PA\u003c/a\u003e\u003c/p\u003e\n\n\u003ch4 id=\"cross-flow-and-opposite-flow\"\u003eCross Flow and Opposite Flow\u003c/h4\u003e\n\n\u003cp\u003eThe \u003cem\u003eopposite flow\u003c/em\u003e of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections.\nEach well is assigned an opposite flow name by adding \u0026ldquo;-XF\u0026rdquo; to the end of the name. \u0026ldquo;-XF\u0026rdquo; was chosen as a reference to Cross Flow.\u003c/p\u003e\n\n\u003cp\u003eIn this way, a producer will have two tracer names: The \u0026ldquo;well name\u0026rdquo; as a producer tracer, and \u0026ldquo;well name-XF\u0026rdquo; as an injector tracer.\u003c/p\u003e\n\n\u003ch4 id=\"defining-results\"\u003eDefining Results\u003c/h4\u003e\n\n\u003cp\u003eThere are several options available to define the particular result you want to target, as shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultFlowDiagnostics.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThere are two main selections you need to make: The tracers and the result property\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracers\u003c/strong\u003e \u0026ndash; Option to select how/what tracers to use. Available options are:\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Injectors and Producers\u003c/strong\u003e \u0026ndash;  Selects all the wells, including the opposite flow tracers\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Producers\u003c/strong\u003e \u0026ndash; Selects all producer tracers, including the opposite flow tracers of injectors.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Injectors\u003c/strong\u003e \u0026ndash; Selects all injector tracers, including the opposite flow tracers of producers.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Selection\u003c/strong\u003e \u0026ndash; Displays lists of all the injector tracers and producer tracers side-by-side allowing any to be selected freely.\n\n\u003cul\u003e\n\u003cli\u003eBoth lists of selectable tracers can be filtered by typing in parts of the name.\u003c/li\u003e\n\u003cli\u003eThe tracers will have a suffix of [I/P] if they are both injector and producer, thus appearing in both lists.\u003c/li\u003e\n\u003cli\u003eAll producers communicating with the selected injectors (and vice-versa) can be selected with the \u0026ldquo;Add Communicator\u0026rdquo; buttons.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePhases\u003c/strong\u003e \u0026ndash; Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the \u003cem\u003eTime Of Flight\u003c/em\u003e result property will be available in the list below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult property\u003c/strong\u003e \u0026ndash; Displays a list of the available results:\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eResidence Time\u003c/strong\u003e \u0026ndash; The time for some fluid in the cell to reach a producer,\nor the time it takes to reach the cell from an injector. The option changes name depending on the selection of injectors and producers and will be Forward Time of Flight if only injectors are selected and Reverse Time of Flight if only producers are selected.\nWhen selecting several tracers, the time of flight values from each of the tracers are weighted\nby their cell fraction before they are averaged. The suffix (Average) will then be added to the option label.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Cell Fraction (Sum)\u003c/strong\u003e \u0026ndash; The volume fraction of a cell occupied by the selected tracers.\nThe injector and producer tracers counts as independent in this regard, so the sum of fractions for\nall the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers\nare selected, the total sum will normally reach 2.0.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDrainage/Flooding Regions\u003c/strong\u003e \u0026ndash; Shows which of the selected tracers that has the largest fraction in each cell.\nThis is shown as a category result displaying a color for each tracer, and the names in the legend. If only injectors are selected, this option will be labelled \u003cstrong\u003eDrainage Regions\u003c/strong\u003e and if only producers are selected, it is called \u003cstrong\u003eFlooding Regions\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjector Producer Communication\u003c/strong\u003e \u0026ndash; The communication in a cell between a set of producers and a set of injectors\nis calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell.\nThis produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers\nhave a high influence.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"on-demand-calculation\"\u003eOn-Demand Calculation\u003c/h4\u003e\n\n\u003cp\u003eThe flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.\u003c/p\u003e\n\n\u003ch3 id=\"injection-flooding\"\u003eInjection Flooding\u003c/h3\u003e\n\n\u003cp\u003eThis result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is \u003cstrong\u003eWater Flooded PV\u003c/strong\u003e. Please refer to \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e for more information.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InjectionFloodingPropertyPanel.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracers\u003c/strong\u003e \u0026ndash; Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter \u0026ldquo;F\u0026rdquo;. Select the tracers you want to investigate.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Property\u003c/strong\u003e \u0026ndash; Select the variable you want to calculate. (\u003cem\u003eNumber Of Flooded PV\u003c/em\u003e is currently the only one)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"geomechanical-results\"\u003eGeomechanical Results\u003c/h2\u003e\n\n\u003cp\u003eGeomechanical results are sorted in different \u003cstrong\u003eResult Position\u003c/strong\u003es:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNodal\u003c/strong\u003e \u0026ndash; Results given a value per node in the grid\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement Nodal\u003c/strong\u003e \u0026ndash; Results with values per element node\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntegration Point\u003c/strong\u003e \u0026ndash; Results with values per integration point. These are displayed in the same way as element nodal results.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement Nodal on Face\u003c/strong\u003e \u0026ndash; Results with values transformed to element faces or intersections.\nSee \u003ca href=\"/3d-main-window/derivedresults/#element-nodal-on-face\"\u003eElement Nodal on Face\u003c/a\u003e for more information\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Names\u003c/strong\u003e \u0026ndash; Lists the \u003cstrong\u003eActive Formation Names\u003c/strong\u003e selected on the case. ( See \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement\u003c/strong\u003e \u0026ndash; Imported element property table results. One value pr element. See \u003ca href=\"/import/elementpropertytable/\"\u003eElement Property Table Import\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSeveral derived cell properties are calculated. Please refer to \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e for more information.\u003c/p\u003e\n\n\u003ch3 id=\"relative-result-options\"\u003eRelative Result Options\u003c/h3\u003e\n\n\u003cp\u003eThis group of options controls time-lapse results to be calculated. ( See \u003ca href=\"/3d-main-window/derivedresults/#relative-results-time-lapse-results\"\u003eRelative Results\u003c/a\u003e for more information )\u003c/p\u003e\n\n\u003ch2 id=\"select-color-result\"\u003eSelect Color Result\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SelectColorResult.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing \u003cstrong\u003eSelect Color Result\u003c/strong\u003e. The corresponding result property will be shown in the Property Editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SelectColorResultPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "The main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per cell over a region of the grid. A Cell Result is also referred to as a Property.\nCell Results are used in several operations and settings:\n Cell Colors Cell Edge Result (Eclipse Only) Separate Fault Result (Eclipse Only) Property Filters Well Log Extraction Curves Cell Result Time History Curves  In the property panel of all those, the same options are used to define the Cell Result of interest.\nIn the following we will describe these options.\nEclipse Result Types Results and difference options are displayed by the Property Editor.\nThe different result types are:\n Dynamic \u0026ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f. Derived Results Static \u0026ndash; Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. Derived Results SourSimRL \u0026ndash; Available if SourSimRL results have been imported, c.f. SourSimRL Import Generated \u0026ndash; Results generated by an Octave Script Input Property \u0026ndash; Directly imported Eclipse properties from ascii files Formation Names \u0026ndash; Lists only the Active Formation Names selected on the case, c.f. Formations Flow Diagnostics \u0026ndash; Flow diagnostic results derived from a flux field, c.f. below Injection Flooding \u0026ndash; Calculation of derived property based on one or more selected simulation tracers, c.f. below  Difference options are:\n Difference Case \u0026ndash; Base case for calculation of difference Base Time Step \u0026ndash; Base time step for calculation of difference  The difference option is not applicable for TERNARY result display.\n\rFlow Diagnostic Results ResInsight has embedded Flow Diagnostics calculations made available using the Flow Diagnostics result type. These results make it easier to see how and where wells interact with the reservoir and each other. It is possible to select exactly what wells to investigate, and even the possible opposite flow part of the well.\nSee also Flow Diagnostics Plots and Flow Characteristics Plot\nMethod The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital.\nThis method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.\nA more elaborate description of the technique and how it can be utilized, can be found at Sintef\u0026rsquo;s web site. The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.\nThe methodology is also described in: The application of flow diagnostics for reservoir management SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: 10.2118/171557-PA\nCross Flow and Opposite Flow The opposite flow of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections. Each well is assigned an opposite flow name by adding \u0026ldquo;-XF\u0026rdquo; to the end of the name. \u0026ldquo;-XF\u0026rdquo; was chosen as a reference to Cross Flow.\nIn this way, a producer will have two tracer names: The \u0026ldquo;well name\u0026rdquo; as a producer tracer, and \u0026ldquo;well name-XF\u0026rdquo; as an injector tracer.\nDefining Results There are several options available to define the particular result you want to target, as shown below:\nThere are two main selections you need to make: The tracers and the result property\n Tracers \u0026ndash; Option to select how/what tracers to use. Available options are:  All Injectors and Producers \u0026ndash; Selects all the wells, including the opposite flow tracers All Producers \u0026ndash; Selects all producer tracers, including the opposite flow tracers of injectors. All Injectors \u0026ndash; Selects all injector tracers, including the opposite flow tracers of producers. By Selection \u0026ndash; Displays lists of all the injector tracers and producer tracers side-by-side allowing any to be selected freely.  Both lists of selectable tracers can be filtered by typing in parts of the name. The tracers will have a suffix of [I/P] if they are both injector and producer, thus appearing in both lists. All producers communicating with the selected injectors (and vice-versa) can be selected with the \u0026ldquo;Add Communicator\u0026rdquo; buttons.     Phases \u0026ndash; Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the Time Of Flight result property will be available in the list below. Result property \u0026ndash; Displays a list of the available results:  Residence Time \u0026ndash; The time for some fluid in the cell to reach a producer, or the time it takes to reach the cell from an injector. The option changes name depending on the selection of injectors and producers and will be Forward Time of Flight if only injectors are selected and Reverse Time of Flight if only producers are selected. When selecting several tracers, the time of flight values from each of the tracers are weighted by their cell fraction before they are averaged. The suffix (Average) will then be added to the option label. Tracer Cell Fraction (Sum) \u0026ndash; The volume fraction of a cell occupied by the selected tracers. The injector and producer tracers counts as independent in this regard, so the sum of fractions for all the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers are selected, the total sum will normally reach 2.0. Drainage/Flooding Regions \u0026ndash; Shows which of the selected tracers that has the largest fraction in each cell. This is shown as a category result displaying a color for each tracer, and the names in the legend. If only injectors are selected, this option will be labelled Drainage Regions and if only producers are selected, it is called Flooding Regions. Injector Producer Communication \u0026ndash; The communication in a cell between a set of producers and a set of injectors is calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell. This produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers have a high influence.    On-Demand Calculation The flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.\nInjection Flooding This result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is Water Flooded PV. Please refer to Derived Results for more information.\n Tracers \u0026ndash; Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter \u0026ldquo;F\u0026rdquo;. Select the tracers you want to investigate. Result Property \u0026ndash; Select the variable you want to calculate. (Number Of Flooded PV is currently the only one)  Geomechanical Results Geomechanical results are sorted in different Result Positions:\n Nodal \u0026ndash; Results given a value per node in the grid Element Nodal \u0026ndash; Results with values per element node Integration Point \u0026ndash; Results with values per integration point. These are displayed in the same way as element nodal results. Element Nodal on Face \u0026ndash; Results with values transformed to element faces or intersections. See Element Nodal on Face for more information Formation Names \u0026ndash; Lists the Active Formation Names selected on the case. ( See Formations ) Element \u0026ndash; Imported element property table results. One value pr element. See Element Property Table Import  Several derived cell properties are calculated. Please refer to Derived Results for more information.\nRelative Result Options This group of options controls time-lapse results to be calculated. ( See Relative Results for more information )\nSelect Color Result In the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing Select Color Result. The corresponding result property will be shown in the Property Editor.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultsOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe main results to post process in ResInsight are Cell Results. A Cell Result is one value, or a small set of values per \ncell over a region of the grid. A Cell Result is also referred to as a \u003cem\u003eProperty\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eCell Results are used in several operations and settings:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Colors\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Edge Result\u003c/strong\u003e (Eclipse Only)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e (Eclipse Only)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Log Extraction Curves\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Result Time History Curves\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIn the property panel of all those, the same options are used to define the Cell Result of interest.\u003cbr\u003e\nIn the following we will describe these options.\u003c/p\u003e\n\u003ch2 id=\"eclipse-result-types\"\u003eEclipse Result Types\u003c/h2\u003e\n\u003cp\u003eResults and difference options are displayed by the Property Editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultTypes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe different result types are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDynamic\u003c/strong\u003e \u0026ndash; Time varying properties of an Eclipse simulation and derived properties calculated by ResInsight, c.f. \n\u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatic\u003c/strong\u003e \u0026ndash; Eclipse properties that does not vary with time and derived properties calculated by ResInsight, c.f. \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSourSimRL\u003c/strong\u003e \u0026ndash; Available if SourSimRL results have been imported, c.f. \u003ca href=\"/import/soursimrlresults/\"\u003eSourSimRL Import\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e \u0026ndash; Results generated by an Octave Script\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInput Property\u003c/strong\u003e \u0026ndash; Directly imported Eclipse properties from ascii files\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Names\u003c/strong\u003e \u0026ndash; Lists only the Active Formation Names selected on the case, c.f. \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Diagnostics\u003c/strong\u003e \u0026ndash; Flow diagnostic results derived from a flux field, \nc.f. \u003ca href=\"/3d-main-window/cellresults/#flow-diagnostic-results\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjection Flooding\u003c/strong\u003e \u0026ndash; Calculation of derived property based on one or more selected simulation tracers, \nc.f. \u003ca href=\"/3d-main-window/cellresults/#injection-flooding\"\u003ebelow\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eDifference options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDifference Case\u003c/strong\u003e \u0026ndash; Base case for calculation of difference\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase Time Step\u003c/strong\u003e \u0026ndash; Base time step for calculation of difference\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe difference option is not applicable for TERNARY result display.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"flow-diagnostic-results\"\u003eFlow Diagnostic Results\u003c/h3\u003e\n\u003cp\u003eResInsight has embedded Flow Diagnostics calculations made available using the \u003cstrong\u003eFlow Diagnostics\u003c/strong\u003e result type. \nThese results make it easier to see how and where wells interact with the reservoir and each other. \nIt is possible to select exactly what wells to investigate, and even the possible \u003cem\u003eopposite flow\u003c/em\u003e part of the well.\u003c/p\u003e\n\u003cp\u003eSee also \u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003e Flow Diagnostics Plots\u003c/a\u003e and \u003ca href=\"/plot-window/flowdiagnosticsplots/#flow-characteristics-plot\"\u003e Flow Characteristics Plot\u003c/a\u003e\u003c/p\u003e\n\u003ch4 id=\"method\"\u003eMethod\u003c/h4\u003e\n\u003cp\u003eThe calculations are performed by a library called \u003ca href=\"https://github.com/OPM/opm-flowdiagnostics\"\u003eopm-flowdiagnostics\u003c/a\u003e developed by \u003ca href=\"http://www.sintef.no/sintef-ikt/#/\"\u003eSINTEF Digital\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eThis method is based on the presence of a flux field, and will use the flux field written to the Eclipse result data file (Cell Properties: FLRGAS, FLRWAT, FLROIL) if available. If these are not available, the flux field is estimated by algorithms in the opm-flowdiagnostics-applications library based on pressure differences, relative and absolute permeability and viscosity. Other effects are not included.\u003c/p\u003e\n\u003cp\u003eA more elaborate description of the technique and how it can be  utilized, can be found at Sintef\u0026rsquo;s \u003ca href=\"http://www.sintef.no/projectweb/mrst/modules/diagnostics/\"\u003eweb site\u003c/a\u003e. The MRST tool described is a Matlab predecessor of the flow diagnostics calculations developed for ResInsight.\u003c/p\u003e\n\u003cp\u003eThe methodology is also described in: \n\u003ca href=\"http://folk.ntnu.no/andreas/papers/diagnostics.pdf\"\u003eThe application of flow diagnostics for reservoir management\u003c/a\u003e SPE J., Vol. 20, No. 2, pp. 306-323, 2015. DOI: \u003ca href=\"https://dx.doi.org/10.2118/171557-PA\"\u003e10.2118/171557-PA\u003c/a\u003e\u003c/p\u003e\n\u003ch4 id=\"cross-flow-and-opposite-flow\"\u003eCross Flow and Opposite Flow\u003c/h4\u003e\n\u003cp\u003eThe \u003cem\u003eopposite flow\u003c/em\u003e of a well denotes the flow that is opposite to the expected normal state of the well. E.g. parts of a producer might actually be injecting due to cross flow, and an injector could be producing in some sections.\nEach well is assigned an opposite flow name by adding \u0026ldquo;-XF\u0026rdquo; to the end of the name. \u0026ldquo;-XF\u0026rdquo; was chosen as a reference to Cross Flow.\u003c/p\u003e\n\u003cp\u003eIn this way, a producer will have two tracer names: The \u0026ldquo;well name\u0026rdquo; as a producer tracer, and \u0026ldquo;well name-XF\u0026rdquo; as an injector tracer.\u003c/p\u003e\n\u003ch4 id=\"defining-results\"\u003eDefining Results\u003c/h4\u003e\n\u003cp\u003eThere are several options available to define the particular result you want to target, as shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellResultFlowDiagnostics.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThere are two main selections you need to make: The tracers and the result property\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracers\u003c/strong\u003e \u0026ndash; Option to select how/what tracers to use. Available options are:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Injectors and Producers\u003c/strong\u003e \u0026ndash;  Selects all the wells, including the opposite flow tracers\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Producers\u003c/strong\u003e \u0026ndash; Selects all producer tracers, including the opposite flow tracers of injectors.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Injectors\u003c/strong\u003e \u0026ndash; Selects all injector tracers, including the opposite flow tracers of producers.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Selection\u003c/strong\u003e \u0026ndash; Displays lists of all the injector tracers and producer tracers side-by-side allowing any to be selected freely.\n\u003cul\u003e\n\u003cli\u003eBoth lists of selectable tracers can be filtered by typing in parts of the name.\u003c/li\u003e\n\u003cli\u003eThe tracers will have a suffix of [I/P] if they are both injector and producer, thus appearing in both lists.\u003c/li\u003e\n\u003cli\u003eAll producers communicating with the selected injectors (and vice-versa) can be selected with the \u0026ldquo;Add Communicator\u0026rdquo; buttons.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePhases\u003c/strong\u003e \u0026ndash; Select the fluid phase you are interested in: All, Oil, Gas or Water. If one of the separate phases are selected, only the \u003cem\u003eTime Of Flight\u003c/em\u003e result property will be available in the list below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult property\u003c/strong\u003e \u0026ndash; Displays a list of the available results:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eResidence Time\u003c/strong\u003e \u0026ndash; The time for some fluid in the cell to reach a producer, \nor the time it takes to reach the cell from an injector. The option changes name depending on the selection of injectors and producers and will be Forward Time of Flight if only injectors are selected and Reverse Time of Flight if only producers are selected.\nWhen selecting several tracers, the time of flight values from each of the tracers are weighted \nby their cell fraction before they are averaged. The suffix (Average) will then be added to the option label.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Cell Fraction (Sum)\u003c/strong\u003e \u0026ndash; The volume fraction of a cell occupied by the selected tracers. \nThe injector and producer tracers counts as independent in this regard, so the sum of fractions for \nall the producer tracers will be 1.0 and the same for the injector tracers. If both types of tracers \nare selected, the total sum will normally reach 2.0.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDrainage/Flooding Regions\u003c/strong\u003e \u0026ndash; Shows which of the selected tracers that has the largest fraction in each cell. \nThis is shown as a category result displaying a color for each tracer, and the names in the legend. If only injectors are selected, this option will be labelled \u003cstrong\u003eDrainage Regions\u003c/strong\u003e and if only producers are selected, it is called \u003cstrong\u003eFlooding Regions\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjector Producer Communication\u003c/strong\u003e \u0026ndash; The communication in a cell between a set of producers and a set of injectors \nis calculated as the sum of producer fractions multiplied by the sum of injector fractions in the cell. \nThis produces values between 0.0 and 1.0 where high values indicate that both the injectors and the producers \nhave a high influence.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"on-demand-calculation\"\u003eOn-Demand Calculation\u003c/h4\u003e\n\u003cp\u003eThe flow diagnostics results are only calculated when asked for, and only for requested time steps. This means that statistics based on all time steps are not available for these results.\u003c/p\u003e\n\u003ch3 id=\"injection-flooding\"\u003eInjection Flooding\u003c/h3\u003e\n\u003cp\u003eThis result type is used to plot derived results based on a selection of simulated tracers, typically seawater injection. Currently the only derived property available is \u003cstrong\u003eWater Flooded PV\u003c/strong\u003e. Please refer to \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e for more information.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InjectionFloodingPropertyPanel.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracers\u003c/strong\u003e \u0026ndash; Lists the available simulation tracers from the Eclipse Case. The list is produced by showing only the properties with names ending with the letter \u0026ldquo;F\u0026rdquo;. Select the tracers you want to investigate.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResult Property\u003c/strong\u003e \u0026ndash; Select the variable you want to calculate. (\u003cem\u003eNumber Of Flooded PV\u003c/em\u003e is currently the only one)\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"geomechanical-results\"\u003eGeomechanical Results\u003c/h2\u003e\n\u003cp\u003eGeomechanical results are sorted in different \u003cstrong\u003eResult Position\u003c/strong\u003es:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNodal\u003c/strong\u003e \u0026ndash; Results given a value per node in the grid\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement Nodal\u003c/strong\u003e \u0026ndash; Results with values per element node\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntegration Point\u003c/strong\u003e \u0026ndash; Results with values per integration point. These are displayed in the same way as element nodal results.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement Nodal on Face\u003c/strong\u003e \u0026ndash; Results with values transformed to element faces or intersections. \nSee \u003ca href=\"/3d-main-window/derivedresults/\"\u003eElement Nodal on Face\u003c/a\u003e for more information\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Names\u003c/strong\u003e \u0026ndash; Lists the \u003cstrong\u003eActive Formation Names\u003c/strong\u003e selected on the case. ( See \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eElement\u003c/strong\u003e \u0026ndash; Imported element property table results. One value pr element. See \u003ca href=\"/import/elementpropertytable/\"\u003eElement Property Table Import\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSeveral derived cell properties are calculated. Please refer to \u003ca href=\"/3d-main-window/derivedresults/\"\u003eDerived Results\u003c/a\u003e for more information.\u003c/p\u003e\n\u003ch3 id=\"relative-result-options\"\u003eRelative Result Options\u003c/h3\u003e\n\u003cp\u003eThis group of options controls time-lapse results to be calculated. ( See \u003ca href=\"/3d-main-window/derivedresults/\"\u003eRelative Results\u003c/a\u003e for more information )\u003c/p\u003e\n\u003ch2 id=\"select-color-result\"\u003eSelect Color Result\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SelectColorResult.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the 3D view, the result property for a selected cell can be found by right-clicking on the 3D view and choosing \u003cstrong\u003eSelect Color Result\u003c/strong\u003e. The corresponding result property will be shown in the Property Editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SelectColorResultPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/cellresults/"
             };
         
@@ -1956,8 +1989,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/commandlineinterface/"] = {
                 title:    "Command Line Interface",
-                content:  " ResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.\nCommand line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for Command Line Interfaces.\nExamples on how command line options are used are given below\nCommand line options General    Parameter Description     \u0026#45;\u0026#45;help, \u0026#45;\u0026#45;? Displays help text and version info   \u0026#45;\u0026#45;project \u0026lt;filename\u0026gt; Open project file \u0026lt;filename\u0026gt;.   \u0026#45;\u0026#45;last Open last used project.   \u0026#45;\u0026#45;size \u0026lt;width\u0026gt; \u0026lt;height\u0026gt; Set size of the main application window.   \u0026#45;\u0026#45;console Launch as a console application without graphics   \u0026#45;\u0026#45;server [\u0026lt;portnumber\u0026gt;] Launch as a GRPC server. Default port is 50051   \u0026#45;\u0026#45;startdir \u0026lt;folder\u0026gt; Set startup directory.    Command files    Parameter Description     \u0026#45;\u0026#45;commandFile \u0026lt;commandFile\u0026gt; Execute a command file. See command file documentation.   \u0026#45;\u0026#45;commandFileProject \u0026lt;filename\u0026gt; Project to use if performing case looping for command file. Used in conjunction with commandFileReplaceCases.    Snapshots    Parameter Description     \u0026#45;\u0026#45;savesnapshots all\u0026#124;views\u0026#124;plots\u0026#124; Save snapshot of all views or plots to project file location sub folder \u0026lsquo;snapshots\u0026rsquo;. Option \u0026lsquo;all\u0026rsquo; will include both views and plots. Application closes after snapshots have been written.   \u0026#45;\u0026#45;multiCaseSnapshots \u0026lt;gridListFile\u0026gt; For each grid file listed in the \u0026lt;gridListFile\u0026gt; file, replace the first case in the project and save snapshot of all views.    Case handling    Parameter Description     \u0026#45;\u0026#45;case \u0026lt;casename\u0026#124;filename\u0026gt; [\u0026lt;casename\u0026#124;filename\u0026gt;] Imports the Eclipse cases specified by case name with or without extension.If \u0026lt;casename\u0026gt;, import the corresponding grid file and summary file. If \u0026lt;filename\u0026gt; has extension .GRRID/.EGRID, import the grid file and corresponding summary file. If \u0026lt;filename\u0026gt; has extension .SMSPEC, import the summary file (does not open the grid file)   \u0026#45;\u0026#45;replaceCase [\u0026lt;caseId\u0026gt;] \u0026lt;newGridFile\u0026gt; Replace grid in \u0026lt;caseId\u0026gt; or first case with \u0026lt;newGridFile\u0026gt;. Repeat parameter for multiple replace operations.   \u0026#45;\u0026#45;replaceSourceCases [\u0026lt;caseGroupId\u0026gt;] \u0026lt;gridListFile\u0026gt; Replace source cases in \u0026lt;caseGroupId\u0026gt; or first grid case group with the grid files listed in the \u0026lt;gridListFile\u0026gt; file. Repeat parameter for multiple replace operations.   \u0026#45;\u0026#45;commandFileReplaceCases [\u0026lt;caseId\u0026gt;] \u0026lt;caseListFile\u0026gt; Supply list of cases to replace in project, performing command file for each case. Project to replace cases must be set with commandFileProject. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId.    Reduce project load time using \u0026ndash;replaceSourceCases ResInsight stores data computed by statistics calculation in a cache file. When a project file is loaded, data from this cache is also imported. For large cases, the cached data can be large. When replacing source cases during batch, this data is never used and can be removed from the cache using the following workaround: - Open the project file used to produce statistics - Select the statistics object in the project tree - Click the button Edit (Will DELETE current result) - Save the project file\n\rSummary plotting The summary plotting command option follows the following syntax:\nresinsight --summaryplot [\u0026lt;plotOptions\u0026gt;] \u0026lt;eclipsesummaryvectorfilters\u0026gt; \u0026lt;eclipsedatafiles\u0026gt; where: \u0026lt;plotOptions\u0026gt; denote summary plot options, see table below \u0026lt;eclipsesummaryvectorfilters\u0026gt; has the syntax \u0026lt;vectorname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]] \u0026lt;eclipsedatafiles\u0026gt; lists a set of Eclipse data files with or without extension  The summary plotting command option creates one summary plot for each of the the summary vectors matched by\n\u0026lt;eclipsesummaryvectorfilters\u0026gt; using all listed Eclipse data files in each plot.\nEclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above. Wildcards can be used in the specification. Brief examples are:\n WOPT:*: One total oil production curve for each well. FOPT FWPT: Two curves with oil and water total production. BPR:15,28,*: Oil phase pressure for all blocks along k as separate curves. Please note no space in expression.  Examples are listed below.\nAs long as only summary vectors are requested, only the corresponding SMSPEC file will be opened for each case. However, if a grid property is requested, the corresponding EGRID and restart data will be loaded as well.\nSpecifying summary plot options is optional, c.f. table below.\n   Option Description     \u0026#45;help Shows help text and ignores any other option.   \u0026#45;h Includes history vectors read from summary file if the vectors exist. Only history vectors from the first summary case in the project will be included.   \u0026#45;nl Omits legend in plot.   \u0026#45;s Creates only one plot including all the defined vectors and cases.   \u0026#45;n Scales all curves into the range 0.0-1.0. Useful when using -s.   \u0026#45;e Imports all the cases as an ensemble, and create ensemble curves sets instead of single curves.   \u0026#45;c \u0026lt;parametername\u0026gt; Same as -e, but colors the curves by the ensemble parameter  .   \u0026#45;cl \u0026lt;parametername\u0026gt; Same as -c, but uses logarithmic legend.    Testing    Parameter Description     \u0026#45;\u0026#45;regressiontest \u0026lt;folder\u0026gt; System command   \u0026#45;\u0026#45;updateregressiontestbase \u0026lt;folder\u0026gt; System command   \u0026#45;\u0026#45;unittest Execute integration tests   \u0026#45;\u0026#45;ignoreArgs System command    See also the Regression Test System  for a more in-depth explanation.\nExamples Most examples are also available from the test section.\nCreate snapshots of all views for multiple cases A list of cases is defined in CaseList.txt, containing the following\nReal0/BRUGGE_0000.EGRID Real10/BRUGGE_0010.EGRID Real30/BRUGGE_0030.EGRID Real40/BRUGGE_0040.EGRID  The command line used to run this example is shown here:\nResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500  This will instruct ResInsight to read the project file BatchTest.rsp. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.\nReplace a single case and take snapshots of all views The command line used to run this example is shown here:\nResInsight --project BatchTest.rsp --replaceCase \u0026quot;Real10\\BRUGGE_0010.EGRID\u0026quot; --savesnapshots  This will instruct ResInsight to read the project file BatchTest.rsp. The specified case Real10\\BRUGGE_0010.EGRID will be imported into the project, and snapshots of all views will be written to file.\nReplace source cases in a case group and create snapshot A list of cases is defined in CaseList2.txt, containing the following\nReal0/BRUGGE_0000.EGRID Real10/BRUGGE_0010.EGRID  The command line used to run this example is shown here:\nResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots  This will instruct ResInsight to read the project file BatchStatistics.rsp. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.\nReplace source cases in multiple case groups and create snapshots Multiple source case groups can be updated by repeating the replaceSourceCases parameter.\nThe command line used to run this example is shown here:\nResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots  This will instruct ResInsight to read the project file BatchStatistics.rsp. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.\nThe possibility to replace multiple cases can also be applied for single case replace (parameter replaceCase).\nSummary plotting The following command line performs a summary plot for FOPT based on Eclipse summary file 1_R001_REEK-0.SMSPEC.\nResInsight --summaryplot 1_R001_REEK-0 FOPT  Based on file 1_R001_REEK-0.SMSPEC, the following command line performs a summary plot for FOPT and any WOPT-vector for well op_2. The trailing option -s gathers the vectors into a single summary plot.\nResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 -s  Adding to previous example, the following command line also plots the 3D grid property SOIL for cell (20, 21, 1).\nResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 SOIL:20,21,1  ",
-                html:     "\n\n\u003cp\u003eResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.\u003c/p\u003e\n\n\u003cp\u003eCommand line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for \u003ca href=\"http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html#Command_002dLine-Interfaces\"\u003eCommand Line Interfaces\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eExamples on how command line options are used are given \u003ca href=\"/scripting/commandlineinterface/#examples\"\u003ebelow\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"command-line-options\"\u003eCommand line options\u003c/h2\u003e\n\n\u003ch3 id=\"general\"\u003eGeneral\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;help, \u0026#45;\u0026#45;?\u003c/td\u003e\n\u003ctd\u003eDisplays help text and version info\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;project \u0026lt;filename\u0026gt;\u003c/td\u003e\n\u003ctd\u003eOpen project file \u0026lt;filename\u0026gt;.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;last\u003c/td\u003e\n\u003ctd\u003eOpen last used project.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;size \u0026lt;width\u0026gt; \u0026lt;height\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSet size of the main application window.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;console\u003c/td\u003e\n\u003ctd\u003eLaunch as a console application without graphics\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;server [\u0026lt;portnumber\u0026gt;]\u003c/td\u003e\n\u003ctd\u003eLaunch as a GRPC server. Default port is 50051\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;startdir \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSet startup directory.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"command-files\"\u003eCommand files\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;commandFile \u0026lt;commandFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eExecute a command file. See \u003ca href=\"/scripting/commandfile/\"\u003ecommand file documentation.\u003c/a\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;commandFileProject \u0026lt;filename\u0026gt;\u003c/td\u003e\n\u003ctd\u003eProject to use if performing case looping for command file. Used in conjunction with \u003ccode\u003ecommandFileReplaceCases\u003c/code\u003e.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"snapshots\"\u003eSnapshots\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;savesnapshots all\u0026#124;views\u0026#124;plots\u0026#124;\u003c/td\u003e\n\u003ctd\u003eSave snapshot of all views or plots to project file location sub folder \u0026lsquo;snapshots\u0026rsquo;. Option \u0026lsquo;all\u0026rsquo; will include both views and plots. Application closes after snapshots have been written.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;multiCaseSnapshots \u0026lt;gridListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eFor each grid file listed in the \u0026lt;gridListFile\u0026gt; file, replace the first case in the project and save snapshot of all views.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"case-handling\"\u003eCase handling\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;case \u0026lt;casename\u0026#124;filename\u0026gt; [\u0026lt;casename\u0026#124;filename\u0026gt;]\u003c/td\u003e\n\u003ctd\u003eImports the Eclipse cases specified by case name with or without extension.If \u0026lt;casename\u0026gt;, import the corresponding grid file and summary file. If \u0026lt;filename\u0026gt; has extension .GRRID/.EGRID, import the grid file and corresponding summary file. If \u0026lt;filename\u0026gt; has extension .SMSPEC, import the summary file (does not open the grid file)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;replaceCase [\u0026lt;caseId\u0026gt;] \u0026lt;newGridFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eReplace grid in \u0026lt;caseId\u0026gt; or first case with \u0026lt;newGridFile\u0026gt;. Repeat parameter for multiple replace operations.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;replaceSourceCases [\u0026lt;caseGroupId\u0026gt;] \u0026lt;gridListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eReplace source cases in \u0026lt;caseGroupId\u0026gt; or first grid case group with the grid files listed in the \u0026lt;gridListFile\u0026gt; file. Repeat parameter for multiple replace operations.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;commandFileReplaceCases [\u0026lt;caseId\u0026gt;] \u0026lt;caseListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSupply list of cases to replace in project, performing command file for each case. Project to replace cases must be set with \u003ccode\u003ecommandFileProject\u003c/code\u003e. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cb\u003eReduce project load time using \u003ccode\u003e\u0026ndash;replaceSourceCases\u003c/code\u003e\u003c/b\u003e\n \u003cbr\u003e\nResInsight stores data computed by statistics calculation in a cache file. When a project file is loaded, data from this cache is also imported. For large cases, the cached data can be large. When replacing source cases during batch, this data is never used and can be removed from the cache using the following workaround:\n\u003cbr\u003e\n  - Open the project file used to produce statistics\n  \u003cbr\u003e\n  - Select the statistics object in the project tree\n  \u003cbr\u003e\n  - Click the button \u003cb\u003eEdit (Will DELETE current result)\u003c/b\u003e\n  \u003cbr\u003e\n  - Save the project file\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"summary-plotting\"\u003eSummary plotting\u003c/h3\u003e\n\n\u003cp\u003eThe summary plotting command option follows the following syntax:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eresinsight --summaryplot [\u0026lt;plotOptions\u0026gt;] \u0026lt;eclipsesummaryvectorfilters\u0026gt; \u0026lt;eclipsedatafiles\u0026gt;\n\nwhere:\n\u0026lt;plotOptions\u0026gt;                 denote summary plot options, see table below\n\u0026lt;eclipsesummaryvectorfilters\u0026gt; has the syntax \u0026lt;vectorname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\n\u0026lt;eclipsedatafiles\u0026gt;            lists a set of Eclipse data files with or without extension\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe summary plotting command option creates one summary plot for each of the the summary vectors matched by\u003cbr /\u003e\n\u003cem\u003e\u0026lt;eclipsesummaryvectorfilters\u0026gt;\u003c/em\u003e using all listed Eclipse data files in each plot.\u003c/p\u003e\n\n\u003cp\u003eEclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above.\nWildcards can be used in the specification. Brief examples are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ccode\u003eWOPT:*\u003c/code\u003e: One total oil production curve for each well.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eFOPT FWPT\u003c/code\u003e: Two curves with oil and water total production.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eBPR:15,28,*\u003c/code\u003e: Oil phase pressure for all blocks along k as separate curves. Please note no space in expression.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003ca href=\"/scripting/commandlineinterface/#summary-plotting-1\"\u003eExamples\u003c/a\u003e are listed below.\u003c/p\u003e\n\n\u003cp\u003eAs long as only summary vectors are requested, only the corresponding SMSPEC file will be opened for each case.\nHowever, if a grid property is requested, the corresponding EGRID and restart data will be loaded as well.\u003c/p\u003e\n\n\u003cp\u003eSpecifying summary plot options is optional, c.f. table below.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;help\u003c/td\u003e\n\u003ctd\u003eShows help text and ignores any other option.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;h\u003c/td\u003e\n\u003ctd\u003eIncludes history vectors read from summary file if the vectors exist. Only history vectors from the first summary case in the project will be included.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;nl\u003c/td\u003e\n\u003ctd\u003eOmits legend in plot.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;s\u003c/td\u003e\n\u003ctd\u003eCreates only one plot including all the defined vectors and cases.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;n\u003c/td\u003e\n\u003ctd\u003eScales all curves into the range 0.0-1.0. Useful when using -s.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;e\u003c/td\u003e\n\u003ctd\u003eImports all the cases as an ensemble, and create ensemble curves sets instead of single curves.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;c  \u0026lt;parametername\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSame as \u003cem\u003e-e\u003c/em\u003e, but colors the curves by the ensemble parameter \u003cparametername\u003e .\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;cl \u0026lt;parametername\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSame as \u003cem\u003e-c\u003c/em\u003e, but uses logarithmic legend.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"testing\"\u003eTesting\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;regressiontest \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;updateregressiontestbase \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;unittest\u003c/td\u003e\n\u003ctd\u003eExecute integration tests\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026#45;\u0026#45;ignoreArgs\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eSee also the \u003ca href=\"/misc/regressiontestsystem/\"\u003eRegression Test System \u003c/a\u003e for a more in-depth explanation.\u003c/p\u003e\n\n\u003ch2 id=\"examples\"\u003eExamples\u003c/h2\u003e\n\n\u003cp\u003eMost examples are also available from the \u003ca href=\"https://github.com/OPM/ResInsight/tree/master/TestModels/Case_with_10_timesteps\"\u003etest section\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"create-snapshots-of-all-views-for-multiple-cases\"\u003eCreate snapshots of all views for multiple cases\u003c/h3\u003e\n\n\u003cp\u003eA list of cases is defined in \u003cstrong\u003eCaseList.txt\u003c/strong\u003e, containing the following\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eReal0/BRUGGE_0000.EGRID\nReal10/BRUGGE_0010.EGRID\nReal30/BRUGGE_0030.EGRID\nReal40/BRUGGE_0040.EGRID\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchTest.rsp\u003c/strong\u003e. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.\u003c/p\u003e\n\n\u003ch3 id=\"replace-a-single-case-and-take-snapshots-of-all-views\"\u003eReplace a single case and take snapshots of all views\u003c/h3\u003e\n\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchTest.rsp --replaceCase \u0026quot;Real10\\BRUGGE_0010.EGRID\u0026quot; --savesnapshots\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchTest.rsp\u003c/strong\u003e. The specified case \u003cstrong\u003eReal10\\BRUGGE_0010.EGRID\u003c/strong\u003e will be imported into the project, and snapshots of all views will be written to file.\u003c/p\u003e\n\n\u003ch3 id=\"replace-source-cases-in-a-case-group-and-create-snapshot\"\u003eReplace source cases in a case group and create snapshot\u003c/h3\u003e\n\n\u003cp\u003eA list of cases is defined in \u003cstrong\u003eCaseList2.txt\u003c/strong\u003e, containing the following\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eReal0/BRUGGE_0000.EGRID\nReal10/BRUGGE_0010.EGRID\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchStatistics.rsp\u003c/strong\u003e. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.\u003c/p\u003e\n\n\u003ch3 id=\"replace-source-cases-in-multiple-case-groups-and-create-snapshots\"\u003eReplace source cases in multiple case groups and create snapshots\u003c/h3\u003e\n\n\u003cp\u003eMultiple source case groups can be updated by repeating the replaceSourceCases parameter.\u003c/p\u003e\n\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchStatistics.rsp\u003c/strong\u003e. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.\u003c/p\u003e\n\n\u003cp\u003eThe possibility to replace multiple cases can also be applied for single case replace (parameter \u003cem\u003ereplaceCase\u003c/em\u003e).\u003c/p\u003e\n\n\u003ch3 id=\"summary-plotting-1\"\u003eSummary plotting\u003c/h3\u003e\n\n\u003cp\u003eThe following command line performs a \u003ca href=\"/plot-window/summaryplots/\"\u003esummary plot\u003c/a\u003e for \u003cem\u003eFOPT\u003c/em\u003e based on Eclipse summary file \u003cem\u003e1_R001_REEK-0.SMSPEC\u003c/em\u003e.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eBased on file \u003cem\u003e1_R001_REEK-0.SMSPEC\u003c/em\u003e, the following command line performs a \u003ca href=\"/plot-window/summaryplots/\"\u003esummary plot\u003c/a\u003e\nfor \u003cem\u003eFOPT\u003c/em\u003e and any \u003cem\u003eWOPT\u003c/em\u003e-vector for well \u003cem\u003eop_2\u003c/em\u003e.\nThe trailing option \u003cem\u003e-s\u003c/em\u003e gathers the vectors into a single summary plot.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 -s\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eAdding to previous example, the following command line also plots the 3D grid property \u003ccode\u003eSOIL\u003c/code\u003e for cell (20, 21, 1).\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 SOIL:20,21,1\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "ResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.\nCommand line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for Command Line Interfaces.\nExamples on how command line options are used are given below\nCommand line options General    Parameter Description     --help, --? Displays help text and version info   --project \u0026lt;filename\u0026gt; Open project file \u0026lt;filename\u0026gt;.   --last Open last used project.   --size \u0026lt;width\u0026gt; \u0026lt;height\u0026gt; Set size of the main application window.   --console Launch as a console application without graphics   --server [\u0026lt;portnumber\u0026gt;] Launch as a GRPC server. Default port is 50051   --startdir \u0026lt;folder\u0026gt; Set startup directory.    Command files    Parameter Description     --commandFile \u0026lt;commandFile\u0026gt; Execute a command file. See command file documentation.   --commandFileProject \u0026lt;filename\u0026gt; Project to use if performing case looping for command file. Used in conjunction with commandFileReplaceCases.    Snapshots    Parameter Description     --savesnapshots all|views|plots| Save snapshot of all views or plots to project file location sub folder \u0026lsquo;snapshots\u0026rsquo;. Option \u0026lsquo;all\u0026rsquo; will include both views and plots. Application closes after snapshots have been written.   --multiCaseSnapshots \u0026lt;gridListFile\u0026gt; For each grid file listed in the \u0026lt;gridListFile\u0026gt; file, replace the first case in the project and save snapshot of all views.    Case handling    Parameter Description     --case \u0026lt;casename|filename\u0026gt; [\u0026lt;casename|filename\u0026gt;] Imports the Eclipse cases specified by case name with or without extension.If \u0026lt;casename\u0026gt;, import the corresponding grid file and summary file. If \u0026lt;filename\u0026gt; has extension .GRRID/.EGRID, import the grid file and corresponding summary file. If \u0026lt;filename\u0026gt; has extension .SMSPEC, import the summary file (does not open the grid file)   --replaceCase [\u0026lt;caseId\u0026gt;] \u0026lt;newGridFile\u0026gt; Replace grid in \u0026lt;caseId\u0026gt; or first case with \u0026lt;newGridFile\u0026gt;. Repeat parameter for multiple replace operations.   --replaceSourceCases [\u0026lt;caseGroupId\u0026gt;] \u0026lt;gridListFile\u0026gt; Replace source cases in \u0026lt;caseGroupId\u0026gt; or first grid case group with the grid files listed in the \u0026lt;gridListFile\u0026gt; file. Repeat parameter for multiple replace operations.   --commandFileReplaceCases [\u0026lt;caseId\u0026gt;] \u0026lt;caseListFile\u0026gt; Supply list of cases to replace in project, performing command file for each case. Project to replace cases must be set with commandFileProject. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId.    Reduce project load time using \u0026ndash;replaceSourceCasesResInsight stores data computed by statistics calculation in a cache file. When a project file is loaded, data from this cache is also imported. For large cases, the cached data can be large. When replacing source cases during batch, this data is never used and can be removed from the cache using the following workaround:  Open the project file used to produce statistics  Select the statistics object in the project tree  Click the button Edit (Will DELETE current result) Save the project file  \rSummary plotting The summary plotting command option follows the following syntax:\nresinsight --summaryplot [\u0026lt;plotOptions\u0026gt;] \u0026lt;eclipsesummaryvectorfilters\u0026gt; \u0026lt;eclipsedatafiles\u0026gt;\rwhere:\r\u0026lt;plotOptions\u0026gt; denote summary plot options, see table below\r\u0026lt;eclipsesummaryvectorfilters\u0026gt; has the syntax \u0026lt;vectorname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\r\u0026lt;eclipsedatafiles\u0026gt; lists a set of Eclipse data files with or without extension\rThe summary plotting command option creates one summary plot for each of the the summary vectors matched by\n\u0026lt;eclipsesummaryvectorfilters\u0026gt; using all listed Eclipse data files in each plot.\nEclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above. Wildcards can be used in the specification. Brief examples are:\n WOPT:*: One total oil production curve for each well. FOPT FWPT: Two curves with oil and water total production. BPR:15,28,*: Oil phase pressure for all blocks along k as separate curves. Please note no space in expression.  Examples are listed below.\nAs long as only summary vectors are requested, only the corresponding SMSPEC file will be opened for each case. However, if a grid property is requested, the corresponding EGRID and restart data will be loaded as well.\nSpecifying summary plot options is optional, c.f. table below.\n   Option Description     -help Shows help text and ignores any other option.   -h Includes history vectors read from summary file if the vectors exist. Only history vectors from the first summary case in the project will be included.   -nl Omits legend in plot.   -s Creates only one plot including all the defined vectors and cases.   -n Scales all curves into the range 0.0-1.0. Useful when using -s.   -e Imports all the cases as an ensemble, and create ensemble curves sets instead of single curves.   -c \u0026lt;parametername\u0026gt; Same as -e, but colors the curves by the ensemble parameter .   -cl \u0026lt;parametername\u0026gt; Same as -c, but uses logarithmic legend.    Testing    Parameter Description     --regressiontest \u0026lt;folder\u0026gt; System command   --updateregressiontestbase \u0026lt;folder\u0026gt; System command   --unittest Execute integration tests   --ignoreArgs System command    See also the Regression Test System  for a more in-depth explanation.\nExamples Most examples are also available from the test section.\nCreate snapshots of all views for multiple cases A list of cases is defined in CaseList.txt, containing the following\nReal0/BRUGGE_0000.EGRID\rReal10/BRUGGE_0010.EGRID\rReal30/BRUGGE_0030.EGRID\rReal40/BRUGGE_0040.EGRID\rThe command line used to run this example is shown here:\nResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500\rThis will instruct ResInsight to read the project file BatchTest.rsp. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.\nReplace a single case and take snapshots of all views The command line used to run this example is shown here:\nResInsight --project BatchTest.rsp --replaceCase \u0026quot;Real10\\BRUGGE_0010.EGRID\u0026quot; --savesnapshots\rThis will instruct ResInsight to read the project file BatchTest.rsp. The specified case Real10\\BRUGGE_0010.EGRID will be imported into the project, and snapshots of all views will be written to file.\nReplace source cases in a case group and create snapshot A list of cases is defined in CaseList2.txt, containing the following\nReal0/BRUGGE_0000.EGRID\rReal10/BRUGGE_0010.EGRID\rThe command line used to run this example is shown here:\nResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots\rThis will instruct ResInsight to read the project file BatchStatistics.rsp. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.\nReplace source cases in multiple case groups and create snapshots Multiple source case groups can be updated by repeating the replaceSourceCases parameter.\nThe command line used to run this example is shown here:\nResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots\rThis will instruct ResInsight to read the project file BatchStatistics.rsp. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.\nThe possibility to replace multiple cases can also be applied for single case replace (parameter replaceCase).\nSummary plotting The following command line performs a summary plot for FOPT based on Eclipse summary file 1_R001_REEK-0.SMSPEC.\nResInsight --summaryplot 1_R001_REEK-0 FOPT\rBased on file 1_R001_REEK-0.SMSPEC, the following command line performs a summary plot for FOPT and any WOPT-vector for well op_2. The trailing option -s gathers the vectors into a single summary plot.\nResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 -s\rAdding to previous example, the following command line also plots the 3D grid property SOIL for cell (20, 21, 1).\nResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 SOIL:20,21,1\r",
+                html:     "\u003cp\u003eResInsight supports several command line parameters that can be used to automate some tasks using shell scripts.\u003c/p\u003e\n\u003cp\u003eCommand line parameters are prefixed using a double dash. This convention is used on all platforms to make it possible to reuse scripts across different platforms. See GNU Standards for \u003ca href=\"http://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html#Command_002dLine-Interfaces\"\u003eCommand Line Interfaces\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eExamples on how command line options are used are given \u003ca href=\"/scripting/commandlineinterface/#examples\"\u003ebelow\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"command-line-options\"\u003eCommand line options\u003c/h2\u003e\n\u003ch3 id=\"general\"\u003eGeneral\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e--help, --?\u003c/td\u003e\n\u003ctd\u003eDisplays help text and version info\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--project \u0026lt;filename\u0026gt;\u003c/td\u003e\n\u003ctd\u003eOpen project file \u0026lt;filename\u0026gt;.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--last\u003c/td\u003e\n\u003ctd\u003eOpen last used project.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--size \u0026lt;width\u0026gt; \u0026lt;height\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSet size of the main application window.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--console\u003c/td\u003e\n\u003ctd\u003eLaunch as a console application without graphics\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--server [\u0026lt;portnumber\u0026gt;]\u003c/td\u003e\n\u003ctd\u003eLaunch as a GRPC server. Default port is 50051\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--startdir \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSet startup directory.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"command-files\"\u003eCommand files\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e--commandFile \u0026lt;commandFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eExecute a command file. See \u003ca href=\"/scripting/commandfile/\"\u003ecommand file documentation.\u003c/a\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--commandFileProject \u0026lt;filename\u0026gt;\u003c/td\u003e\n\u003ctd\u003eProject to use if performing case looping for command file. Used in conjunction with \u003ccode\u003ecommandFileReplaceCases\u003c/code\u003e.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"snapshots\"\u003eSnapshots\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e--savesnapshots all|views|plots|\u003c/td\u003e\n\u003ctd\u003eSave snapshot of all views or plots to project file location sub folder \u0026lsquo;snapshots\u0026rsquo;. Option \u0026lsquo;all\u0026rsquo; will include both views and plots. Application closes after snapshots have been written.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--multiCaseSnapshots \u0026lt;gridListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eFor each grid file listed in the \u0026lt;gridListFile\u0026gt; file, replace the first case in the project and save snapshot of all views.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"case-handling\"\u003eCase handling\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e--case \u0026lt;casename|filename\u0026gt; [\u0026lt;casename|filename\u0026gt;]\u003c/td\u003e\n\u003ctd\u003eImports the Eclipse cases specified by case name with or without extension.If \u0026lt;casename\u0026gt;, import the corresponding grid file and summary file. If \u0026lt;filename\u0026gt; has extension .GRRID/.EGRID, import the grid file and corresponding summary file. If \u0026lt;filename\u0026gt; has extension .SMSPEC, import the summary file (does not open the grid file)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--replaceCase [\u0026lt;caseId\u0026gt;] \u0026lt;newGridFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eReplace grid in \u0026lt;caseId\u0026gt; or first case with \u0026lt;newGridFile\u0026gt;. Repeat parameter for multiple replace operations.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--replaceSourceCases [\u0026lt;caseGroupId\u0026gt;] \u0026lt;gridListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eReplace source cases in \u0026lt;caseGroupId\u0026gt; or first grid case group with the grid files listed in the \u0026lt;gridListFile\u0026gt; file. Repeat parameter for multiple replace operations.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--commandFileReplaceCases [\u0026lt;caseId\u0026gt;] \u0026lt;caseListFile\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSupply list of cases to replace in project, performing command file for each case. Project to replace cases must be set with \u003ccode\u003ecommandFileProject\u003c/code\u003e. If caseId is not supplied, first case is replaced. When supplying caseId, multiple cases may be replaced at once, by supplying several caseIds and a file containing a list of grid-files to replace with for each caseId.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eReduce project load time using \u003c!-- raw HTML omitted --\u003e\u0026ndash;replaceSourceCases\u003c!-- raw HTML omitted --\u003e\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\nResInsight stores data computed by statistics calculation in a cache file. When a project file is loaded, data from this cache is also imported. For large cases, the cached data can be large. When replacing source cases during batch, this data is never used and can be removed from the cache using the following workaround:\n\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOpen the project file used to produce statistics\n\u003c!-- raw HTML omitted --\u003e\u003c/li\u003e\n\u003cli\u003eSelect the statistics object in the project tree\n\u003c!-- raw HTML omitted --\u003e\u003c/li\u003e\n\u003cli\u003eClick the button \u003c!-- raw HTML omitted --\u003eEdit (Will DELETE current result)\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\u003c/li\u003e\n\u003cli\u003eSave the project file\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"summary-plotting\"\u003eSummary plotting\u003c/h3\u003e\n\u003cp\u003eThe summary plotting command option follows the following syntax:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eresinsight --summaryplot [\u0026lt;plotOptions\u0026gt;] \u0026lt;eclipsesummaryvectorfilters\u0026gt; \u0026lt;eclipsedatafiles\u0026gt;\r\n\r\nwhere:\r\n\u0026lt;plotOptions\u0026gt;                 denote summary plot options, see table below\r\n\u0026lt;eclipsesummaryvectorfilters\u0026gt; has the syntax \u0026lt;vectorname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\r\n\u0026lt;eclipsedatafiles\u0026gt;            lists a set of Eclipse data files with or without extension\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThe summary plotting command option creates one summary plot for each of the the summary vectors matched by\u003cbr\u003e\n\u003cem\u003e\u0026lt;eclipsesummaryvectorfilters\u0026gt;\u003c/em\u003e using all listed Eclipse data files in each plot.\u003c/p\u003e\n\u003cp\u003eEclipse summary vector filters specify a list of vectors separated by spaces following the syntax noted above. \nWildcards can be used in the specification. Brief examples are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ccode\u003eWOPT:*\u003c/code\u003e: One total oil production curve for each well.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eFOPT FWPT\u003c/code\u003e: Two curves with oil and water total production.\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eBPR:15,28,*\u003c/code\u003e: Oil phase pressure for all blocks along k as separate curves. Please note no space in expression.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"/scripting/commandlineinterface/#summary-plotting-1\"\u003eExamples\u003c/a\u003e are listed below.\u003c/p\u003e\n\u003cp\u003eAs long as only summary vectors are requested, only the corresponding SMSPEC file will be opened for each case.\nHowever, if a grid property is requested, the corresponding EGRID and restart data will be loaded as well.\u003c/p\u003e\n\u003cp\u003eSpecifying summary plot options is optional, c.f. table below.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e-help\u003c/td\u003e\n\u003ctd\u003eShows help text and ignores any other option.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-h\u003c/td\u003e\n\u003ctd\u003eIncludes history vectors read from summary file if the vectors exist. Only history vectors from the first summary case in the project will be included.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-nl\u003c/td\u003e\n\u003ctd\u003eOmits legend in plot.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-s\u003c/td\u003e\n\u003ctd\u003eCreates only one plot including all the defined vectors and cases.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-n\u003c/td\u003e\n\u003ctd\u003eScales all curves into the range 0.0-1.0. Useful when using -s.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-e\u003c/td\u003e\n\u003ctd\u003eImports all the cases as an ensemble, and create ensemble curves sets instead of single curves.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-c  \u0026lt;parametername\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSame as \u003cem\u003e-e\u003c/em\u003e, but colors the curves by the ensemble parameter \u003c!-- raw HTML omitted --\u003e .\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-cl \u0026lt;parametername\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSame as \u003cem\u003e-c\u003c/em\u003e, but uses logarithmic legend.\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"testing\"\u003eTesting\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e--regressiontest \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--updateregressiontestbase \u0026lt;folder\u0026gt;\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--unittest\u003c/td\u003e\n\u003ctd\u003eExecute integration tests\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e--ignoreArgs\u003c/td\u003e\n\u003ctd\u003eSystem command\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eSee also the \u003ca href=\"/misc/regressiontestsystem/\"\u003eRegression Test System \u003c/a\u003e for a more in-depth explanation.\u003c/p\u003e\n\u003ch2 id=\"examples\"\u003eExamples\u003c/h2\u003e\n\u003cp\u003eMost examples are also available from the \u003ca href=\"https://github.com/OPM/ResInsight/tree/master/TestModels/Case_with_10_timesteps\"\u003etest section\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"create-snapshots-of-all-views-for-multiple-cases\"\u003eCreate snapshots of all views for multiple cases\u003c/h3\u003e\n\u003cp\u003eA list of cases is defined in \u003cstrong\u003eCaseList.txt\u003c/strong\u003e, containing the following\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eReal0/BRUGGE_0000.EGRID\r\nReal10/BRUGGE_0010.EGRID\r\nReal30/BRUGGE_0030.EGRID\r\nReal40/BRUGGE_0040.EGRID\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchTest.rsp\u003c/strong\u003e. All cases will be replaced one by one in ResInsight, and snapshots of all views will be written to file.\u003c/p\u003e\n\u003ch3 id=\"replace-a-single-case-and-take-snapshots-of-all-views\"\u003eReplace a single case and take snapshots of all views\u003c/h3\u003e\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchTest.rsp --replaceCase \u0026quot;Real10\\BRUGGE_0010.EGRID\u0026quot; --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchTest.rsp\u003c/strong\u003e. The specified case \u003cstrong\u003eReal10\\BRUGGE_0010.EGRID\u003c/strong\u003e will be imported into the project, and snapshots of all views will be written to file.\u003c/p\u003e\n\u003ch3 id=\"replace-source-cases-in-a-case-group-and-create-snapshot\"\u003eReplace source cases in a case group and create snapshot\u003c/h3\u003e\n\u003cp\u003eA list of cases is defined in \u003cstrong\u003eCaseList2.txt\u003c/strong\u003e, containing the following\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eReal0/BRUGGE_0000.EGRID\r\nReal10/BRUGGE_0010.EGRID\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchStatistics.rsp\u003c/strong\u003e. All cases specified will be imported in the case group specified in the project file. Statistics will be computed, and snapshots for all views will be written to file.\u003c/p\u003e\n\u003ch3 id=\"replace-source-cases-in-multiple-case-groups-and-create-snapshots\"\u003eReplace source cases in multiple case groups and create snapshots\u003c/h3\u003e\n\u003cp\u003eMultiple source case groups can be updated by repeating the replaceSourceCases parameter.\u003c/p\u003e\n\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThis will instruct ResInsight to read the project file \u003cstrong\u003eBatchStatistics.rsp\u003c/strong\u003e. Source cases for case group 0 is given in CaseList2.txt, and source cases for case group 1 is given in CaseList3.txt. Statistics will be computed, and snapshots for all views will be written to file.\u003c/p\u003e\n\u003cp\u003eThe possibility to replace multiple cases can also be applied for single case replace (parameter \u003cem\u003ereplaceCase\u003c/em\u003e).\u003c/p\u003e\n\u003ch3 id=\"summary-plotting-1\"\u003eSummary plotting\u003c/h3\u003e\n\u003cp\u003eThe following command line performs a \u003ca href=\"/plot-window/summaryplots/\"\u003esummary plot\u003c/a\u003e for \u003cem\u003eFOPT\u003c/em\u003e based on Eclipse summary file \u003cem\u003e1_R001_REEK-0.SMSPEC\u003c/em\u003e.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eBased on file \u003cem\u003e1_R001_REEK-0.SMSPEC\u003c/em\u003e, the following command line performs a \u003ca href=\"/plot-window/summaryplots/\"\u003esummary plot\u003c/a\u003e \nfor \u003cem\u003eFOPT\u003c/em\u003e and any \u003cem\u003eWOPT\u003c/em\u003e-vector for well \u003cem\u003eop_2\u003c/em\u003e.\nThe trailing option \u003cem\u003e-s\u003c/em\u003e gathers the vectors into a single summary plot.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 -s\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eAdding to previous example, the following command line also plots the 3D grid property \u003ccode\u003eSOIL\u003c/code\u003e for cell (20, 21, 1).\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eResInsight --summaryplot 1_R001_REEK-0 FOPT WOPT*:op_2 SOIL:20,21,1\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/scripting/commandlineinterface/"
             };
         
@@ -1965,8 +1998,8 @@ if (!doNotTrack) {
          
             window.store["/export/eclipseproperties/"] = {
                 title:    "Eclipse Properties",
-                content:  " Eclipse Properties can be exported to Eclipse ASCII files. This is particularly useful when a new property is generated using Octave. The generated property can be exported for further use in the simulator.\nExport Command To export the property currently active in the 3D View, activate the right-click menu on a Cell Result item in the Project Tree.\nThe following dialog will appear:\n Export File Name \u0026ndash; The path to exported file Eclipse Keyword \u0026ndash; The keyword to use for the property in the eclipse file Undefined Value \u0026ndash; This value is written to the file for all values that are flagged as undefined in ResInsight  File Format The exported file has the following format, that matches the Eclipse input format:\n-- Exported from ResInsight \u0026lt;keyword\u0026gt; \u0026lt;One number per cell separated by spaces\u0026gt; /  ",
-                html:     "\n\n\u003cp\u003eEclipse Properties can be exported to Eclipse ASCII files.\nThis is particularly useful when a new property is generated using Octave.\nThe generated property can be exported for further use in the simulator.\u003c/p\u003e\n\n\u003ch3 id=\"export-command\"\u003eExport Command\u003c/h3\u003e\n\n\u003cp\u003eTo export the property currently active in the 3D View, activate the right-click menu on a \u003cstrong\u003eCell Result\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportProperty.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe following dialog will appear:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportPropertyDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport File Name\u003c/strong\u003e \u0026ndash; The path to exported file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEclipse Keyword\u003c/strong\u003e \u0026ndash; The keyword to use for the property in the eclipse file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined Value\u003c/strong\u003e \u0026ndash; This value is written to the file for all values that are flagged as undefined in ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"file-format\"\u003eFile Format\u003c/h3\u003e\n\n\u003cp\u003eThe exported file has the following format, that matches the Eclipse input format:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e-- Exported from ResInsight\n\u0026lt;keyword\u0026gt;\n\u0026lt;One number per cell separated by spaces\u0026gt;\n/\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "Eclipse Properties can be exported to Eclipse ASCII files. This is particularly useful when a new property is generated using Octave. The generated property can be exported for further use in the simulator.\nExport Command To export the property currently active in the 3D View, activate the right-click menu on a Cell Result item in the Project Tree.\nThe following dialog will appear:\n Export File Name \u0026ndash; The path to exported file Eclipse Keyword \u0026ndash; The keyword to use for the property in the eclipse file Undefined Value \u0026ndash; This value is written to the file for all values that are flagged as undefined in ResInsight  File Format The exported file has the following format, that matches the Eclipse input format:\n-- Exported from ResInsight\r\u0026lt;keyword\u0026gt;\r\u0026lt;One number per cell separated by spaces\u0026gt;\r/\r ",
+                html:     "\u003cp\u003eEclipse Properties can be exported to Eclipse ASCII files. \nThis is particularly useful when a new property is generated using Octave. \nThe generated property can be exported for further use in the simulator.\u003c/p\u003e\n\u003ch3 id=\"export-command\"\u003eExport Command\u003c/h3\u003e\n\u003cp\u003eTo export the property currently active in the 3D View, activate the right-click menu on a \u003cstrong\u003eCell Result\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportProperty.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe following dialog will appear:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportPropertyDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport File Name\u003c/strong\u003e \u0026ndash; The path to exported file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEclipse Keyword\u003c/strong\u003e \u0026ndash; The keyword to use for the property in the eclipse file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined Value\u003c/strong\u003e \u0026ndash; This value is written to the file for all values that are flagged as undefined in ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"file-format\"\u003eFile Format\u003c/h3\u003e\n\u003cp\u003eThe exported file has the following format, that matches the Eclipse input format:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e-- Exported from ResInsight\r\n\u0026lt;keyword\u0026gt;\r\n\u0026lt;One number per cell separated by spaces\u0026gt;\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n",
                 url:      "/export/eclipseproperties/"
             };
         
@@ -1974,8 +2007,8 @@ if (!doNotTrack) {
          
             window.store["/import/geomechanicaldata/"] = {
                 title:    "Geomechanical Data",
-                content:  " ResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the *.odb format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.\nIf you have, and would like to a use these features, please see Build Instructions  for a description on how to build ResInsight and how to include the support for odb-files.\nGeo Mechanical Data Support Geo-mechanical data can be imported using the Import -\u0026gt; Geo Mechanical Cases menu. Here three options are present: Import Geo Mechanical Model, Import Geo Mechanical Model (Time Step Filtered) (both for odb files) and Import Element Property Table.\nResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are no other element topologies present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.\nResInsight loads the second frame within each odb-step, and present those as the time series for each result.\nAll the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.\nPressure and stress are always displayed using the Bar unit.\nOther derived results are also calculated, and are described in Derived Results \nResInsight Features Most of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.\nThe Octave interface, however, does not support the odb-data yet.\nTime Step Filtered Import By choosing the Import Geo Mechanical Model (Time Step Filtered) option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.\nThe data can be filtered by skipping Days, Weeks, Months or Years in the top Filter Type drop down list and the range of time steps can be picked in the First Time Step and Last Time Steps lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the Select From N Time Steps list. ResInsight will ignore any data that doesn\u0026rsquo;t match these time steps and will thus reduce the amount of data imported.\n",
-                html:     "\n\n\u003cp\u003eResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.\u003c/p\u003e\n\n\u003cp\u003eIf you have, and would like to a use these features, please see \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003e Build Instructions \u003c/a\u003e for a description on how to build ResInsight and how to include the support for odb-files.\u003c/p\u003e\n\n\u003ch3 id=\"geo-mechanical-data-support\"\u003eGeo Mechanical Data Support\u003c/h3\u003e\n\n\u003cp\u003eGeo-mechanical data can be imported using the \u003cstrong\u003eImport -\u0026gt; Geo Mechanical Cases menu\u003c/strong\u003e. Here three options are present: \u003cstrong\u003eImport Geo Mechanical Model\u003c/strong\u003e, \u003cstrong\u003eImport Geo Mechanical Model (Time Step Filtered)\u003c/strong\u003e  (both for odb files) and \u003cstrong\u003eImport Element Property Table\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/GeoMechImport.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are \u003cem\u003eno other element topologies\u003c/em\u003e present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.\u003c/p\u003e\n\n\u003cp\u003eResInsight loads the second frame within each odb-step, and present those as the time series for each result.\u003c/p\u003e\n\n\u003cp\u003eAll the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.\u003c/p\u003e\n\n\u003cp\u003ePressure and stress are always displayed using the \u003cem\u003eBar\u003c/em\u003e unit.\u003c/p\u003e\n\n\u003cp\u003eOther derived results are also calculated, and are described in \u003ca href=\"/3d-main-window/derivedresults/\"\u003e Derived Results \u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"resinsight-features\"\u003eResInsight Features\u003c/h3\u003e\n\n\u003cp\u003eMost of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.\u003c/p\u003e\n\n\u003cp\u003eThe Octave interface, however, does not support the odb-data yet.\u003c/p\u003e\n\n\u003ch3 id=\"time-step-filtered-import\"\u003eTime Step Filtered Import\u003c/h3\u003e\n\n\u003cp\u003eBy choosing the \u003cstrong\u003eImport Geo Mechanical Model (Time Step Filtered)\u003c/strong\u003e option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/GeoMechFilter.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe data can be filtered by skipping Days, Weeks, Months or Years in the top \u003cstrong\u003eFilter Type\u003c/strong\u003e drop down list and the range of time steps can be picked in the \u003cstrong\u003eFirst Time Step\u003c/strong\u003e and \u003cstrong\u003eLast Time Steps\u003c/strong\u003e lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the \u003cstrong\u003eSelect From N Time Steps\u003c/strong\u003e list. ResInsight will ignore any data that doesn\u0026rsquo;t match these time steps and will thus reduce the amount of data imported.\u003c/p\u003e\n",
+                content:  "ResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the *.odb format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.\nIf you have, and would like to a use these features, please see Build Instructions  for a description on how to build ResInsight and how to include the support for odb-files.\nGeo Mechanical Data Support Geo-mechanical data can be imported using the Import -\u0026gt; Geo Mechanical Cases menu. Here three options are present: Import Geo Mechanical Model, Import Geo Mechanical Model (Time Step Filtered) (both for odb files) and Import Element Property Table.\nResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are no other element topologies present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.\nResInsight loads the second frame within each odb-step, and present those as the time series for each result.\nAll the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.\nPressure and stress are always displayed using the Bar unit.\nOther derived results are also calculated, and are described in Derived Results \nResInsight Features Most of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.\nThe Octave interface, however, does not support the odb-data yet.\nTime Step Filtered Import By choosing the Import Geo Mechanical Model (Time Step Filtered) option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.\nThe data can be filtered by skipping Days, Weeks, Months or Years in the top Filter Type drop down list and the range of time steps can be picked in the First Time Step and Last Time Steps lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the Select From N Time Steps list. ResInsight will ignore any data that doesn\u0026rsquo;t match these time steps and will thus reduce the amount of data imported.\n",
+                html:     "\u003cp\u003eResInsight can be built with support for reading and displaying geomechanical analysis models produced by ABAQUS in the \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e format. This is only possible if you or your organization has a copy of the ODB-Api from Simulia, and a valid license to use it.\u003c/p\u003e\n\u003cp\u003eIf you have, and would like to a use these features, please see \u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003e Build Instructions \u003c/a\u003e for a description on how to build ResInsight and how to include the support for odb-files.\u003c/p\u003e\n\u003ch3 id=\"geo-mechanical-data-support\"\u003eGeo Mechanical Data Support\u003c/h3\u003e\n\u003cp\u003eGeo-mechanical data can be imported using the \u003cstrong\u003eImport -\u0026gt; Geo Mechanical Cases menu\u003c/strong\u003e. Here three options are present: \u003cstrong\u003eImport Geo Mechanical Model\u003c/strong\u003e, \u003cstrong\u003eImport Geo Mechanical Model (Time Step Filtered)\u003c/strong\u003e  (both for odb files) and \u003cstrong\u003eImport Element Property Table\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/GeoMechImport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports the elements C3D8R, C3D8 and C3D8P which are all HEX8 cells. It is also assumed that there are \u003cem\u003eno other element topologies\u003c/em\u003e present in the odb file, and that there are only one part. For IJK-based range filters to work, it is also assumed that the elements in the part is topologically arranged as a complete box.\u003c/p\u003e\n\u003cp\u003eResInsight loads the second frame within each odb-step, and present those as the time series for each result.\u003c/p\u003e\n\u003cp\u003eAll the result fields in the odb-file is then available for post processing in ResInsight, but stresses and strains are converted to pressure-positive tensors as normally used in geomechanics, instead of the normal tension-positive tensors that ABAQUS stores.\u003c/p\u003e\n\u003cp\u003ePressure and stress are always displayed using the \u003cem\u003eBar\u003c/em\u003e unit.\u003c/p\u003e\n\u003cp\u003eOther derived results are also calculated, and are described in \u003ca href=\"/3d-main-window/derivedresults/\"\u003e Derived Results \u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"resinsight-features\"\u003eResInsight Features\u003c/h3\u003e\n\u003cp\u003eMost of the central features of ResInsight visualization setup also applies to ABAQUS Odb models, like range filters and property filters. Well Paths will also show up along with the odb models.\u003c/p\u003e\n\u003cp\u003eThe Octave interface, however, does not support the odb-data yet.\u003c/p\u003e\n\u003ch3 id=\"time-step-filtered-import\"\u003eTime Step Filtered Import\u003c/h3\u003e\n\u003cp\u003eBy choosing the \u003cstrong\u003eImport Geo Mechanical Model (Time Step Filtered)\u003c/strong\u003e option, it is possible to limit the amount of time steps that are imported to improve the speed and reduce the memory use. If this option is chosen a tile step filter dialog is shown after selecting the file to import.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/GeoMechFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe data can be filtered by skipping Days, Weeks, Months or Years in the top \u003cstrong\u003eFilter Type\u003c/strong\u003e drop down list and the range of time steps can be picked in the \u003cstrong\u003eFirst Time Step\u003c/strong\u003e and \u003cstrong\u003eLast Time Steps\u003c/strong\u003e lists. Furthermore, the final selection can be fine tuned by selecting or deselecting individual time steps in the \u003cstrong\u003eSelect From N Time Steps\u003c/strong\u003e list. ResInsight will ignore any data that doesn\u0026rsquo;t match these time steps and will thus reduce the amount of data imported.\u003c/p\u003e\n",
                 url:      "/import/geomechanicaldata/"
             };
         
@@ -1983,8 +2016,8 @@ if (!doNotTrack) {
          
             window.store["/misc/memorymanagement/"] = {
                 title:    "Memory Management",
-                content:  " ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. If the requirements starts approaching the available physical memory on the workstation, ResInsight may become unstable and crash, as the operating system starts freeing memory to avoid system failure. To help alleviate this, ResInsight has some built-in memory management tools.\nMemory Indicator The tools are available from the memory indicator in the bottom right corner of the main 3D window.\nIf the available physical memory dips below 5% of the total physical memory on Windows, a warning will be displayed in the memory indicator. This threshold is 17.5% on Linux, as the memory manager on Linux is more likely to start stopping processes when memory is low. The amount of memory used will also be displayed in progress bars during operations in ResInsight if the available memory is less than 50% of total physical memory. In any case, ResInsight is likely to be stopped without warning by the operating system if the amount of used memory starts approaching the total physical memory on the computer.\nMemory Management Tool It is possible to click on the memory used indicator to open up a dialog allowing the user to clear results from memory when they are no longer required. Any tool that is not currently used in a view may be cleared by selecting the result and clicking the Clear Checked Data From Memory. Note that, dependending on your operating system, this may not result in a reduction in the memory reserved by the application. However, the actual use will have gone down and it may now be possible to run more operations without running out of memory.\nBy default, results will be shown for the active case. However, a specific case may be selected in the top drop down list. The pictures below show the dialog for both Eclipse and Abaqus results.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryManagementBanner.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. If the requirements starts approaching the available physical memory on the workstation, ResInsight may become unstable and crash, as the operating system starts freeing memory to avoid system failure. To help alleviate this, ResInsight has some built-in memory management tools.\u003c/p\u003e\n\n\u003ch2 id=\"memory-indicator\"\u003eMemory Indicator\u003c/h2\u003e\n\n\u003cp\u003eThe tools are available from the memory indicator in the bottom right corner of the main 3D window.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryIndicator.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIf the available physical memory dips below 5% of the total physical memory on Windows, a warning will be displayed in the memory indicator. This threshold is 17.5% on Linux, as the memory manager on Linux is more likely to start stopping processes when memory is low. The amount of memory used will also be displayed in progress bars during operations in ResInsight if the available memory is less than 50% of total physical memory. In any case, ResInsight is likely to be stopped without warning by the operating system if the amount of used memory starts approaching the total physical memory on the computer.\u003c/p\u003e\n\n\u003ch2 id=\"memory-management-tool\"\u003eMemory Management Tool\u003c/h2\u003e\n\n\u003cp\u003eIt is possible to click on the memory used indicator to open up a dialog allowing the user to clear results from memory when they are no longer required. Any tool that is not currently used in a view may be cleared by selecting the result and clicking the \u003cstrong\u003eClear Checked Data From Memory\u003c/strong\u003e. Note that, dependending on your operating system, this may not result in a reduction in the memory reserved by the application. However, the actual use will have gone down and it may now be possible to run more operations without running out of memory.\u003c/p\u003e\n\n\u003cp\u003eBy default, results will be shown for the active case. However, a specific case may be selected in the top drop down list. The pictures below show the dialog for both Eclipse and Abaqus results.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryTool.png\" alt=\"\" /\u003e \u003cimg src=\"/images/3d-main-window/MemoryToolGeoMech.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. If the requirements starts approaching the available physical memory on the workstation, ResInsight may become unstable and crash, as the operating system starts freeing memory to avoid system failure. To help alleviate this, ResInsight has some built-in memory management tools.\nMemory Indicator The tools are available from the memory indicator in the bottom right corner of the main 3D window.\nIf the available physical memory dips below 5% of the total physical memory on Windows, a warning will be displayed in the memory indicator. This threshold is 17.5% on Linux, as the memory manager on Linux is more likely to start stopping processes when memory is low. The amount of memory used will also be displayed in progress bars during operations in ResInsight if the available memory is less than 50% of total physical memory. In any case, ResInsight is likely to be stopped without warning by the operating system if the amount of used memory starts approaching the total physical memory on the computer.\nMemory Management Tool It is possible to click on the memory used indicator to open up a dialog allowing the user to clear results from memory when they are no longer required. Any tool that is not currently used in a view may be cleared by selecting the result and clicking the Clear Checked Data From Memory. Note that, dependending on your operating system, this may not result in a reduction in the memory reserved by the application. However, the actual use will have gone down and it may now be possible to run more operations without running out of memory.\nBy default, results will be shown for the active case. However, a specific case may be selected in the top drop down list. The pictures below show the dialog for both Eclipse and Abaqus results.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryManagementBanner.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. If the requirements starts approaching the available physical memory on the workstation, ResInsight may become unstable and crash, as the operating system starts freeing memory to avoid system failure. To help alleviate this, ResInsight has some built-in memory management tools.\u003c/p\u003e\n\u003ch2 id=\"memory-indicator\"\u003eMemory Indicator\u003c/h2\u003e\n\u003cp\u003eThe tools are available from the memory indicator in the bottom right corner of the main 3D window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryIndicator.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf the available physical memory dips below 5% of the total physical memory on Windows, a warning will be displayed in the memory indicator. This threshold is 17.5% on Linux, as the memory manager on Linux is more likely to start stopping processes when memory is low. The amount of memory used will also be displayed in progress bars during operations in ResInsight if the available memory is less than 50% of total physical memory. In any case, ResInsight is likely to be stopped without warning by the operating system if the amount of used memory starts approaching the total physical memory on the computer.\u003c/p\u003e\n\u003ch2 id=\"memory-management-tool\"\u003eMemory Management Tool\u003c/h2\u003e\n\u003cp\u003eIt is possible to click on the memory used indicator to open up a dialog allowing the user to clear results from memory when they are no longer required. Any tool that is not currently used in a view may be cleared by selecting the result and clicking the \u003cstrong\u003eClear Checked Data From Memory\u003c/strong\u003e. Note that, dependending on your operating system, this may not result in a reduction in the memory reserved by the application. However, the actual use will have gone down and it may now be possible to run more operations without running out of memory.\u003c/p\u003e\n\u003cp\u003eBy default, results will be shown for the active case. However, a specific case may be selected in the top drop down list. The pictures below show the dialog for both Eclipse and Abaqus results.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryTool.png\" alt=\"\"\u003e \u003cimg src=\"/images/3d-main-window/MemoryToolGeoMech.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/misc/memorymanagement/"
             };
         
@@ -1992,8 +2025,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summarysourcestepping/"] = {
                 title:    "Summary Plot Source Stepping",
-                content:  " Summary Plot Source Stepping Summary Source Stepping is a function which enables the user to swiftly step through multiple vectors. The functionality applies both to single summary curves and ensemble curve sets.\nThe functionality is available from both the toolbar and the Summary Curves property editor under a Summary Plot item in the Main Plot Window Project Tree.\nThe toolbar allows use of vector filters in addition to source stepping:\nThe corresponding property editor is:\nWhen ResInsight decides stepping dimensions to display, all visible curves in the current plot are taken into account. For instance, well stepping is enabled if all curves display data from the same well, c.f. figure above. This policy applies to the following source stepping dimensions:\n Cases Wells Well groups Regions Completions Segments Block Summary Vectors  Assign source stepping curve If the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available. By right-clicking a summary curve or ensemble curve set, the menu item Set as Source Stepping Curve will use the selected curve as basis for source stepping. All source stepping dimensions for the selected curve will be displayed. When a curve or ensemble is marked for source stepping, a source stepping icon is displayed.\nRight-clicking the summary curve or ensemble curve set, and select Clear Source Stepping Curve to leave this mode.\nHandling of summary curves and history summary curves If a plot displays both a summary curve and the corresponding history summary curve, the source stepping can be applied to both curves at the same time. If you have a mix of several curves, it might be required to mark one of the curves using Set as Source Stepping Curve.\nApplying data source change When one of the next buttons are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the next well button. Then the well source for all curves in the current plot are changed to display data for the next well.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingBanner.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"summary-plot-source-stepping\"\u003eSummary Plot Source Stepping\u003c/h2\u003e\n\n\u003cp\u003eSummary Source Stepping is a function which enables the user to swiftly step through multiple vectors.\nThe functionality applies both to single summary curves and ensemble curve sets.\u003c/p\u003e\n\n\u003cp\u003eThe functionality is available from both the toolbar and the \u003cstrong\u003eSummary Curves\u003c/strong\u003e property editor under a \u003cstrong\u003eSummary Plot\u003c/strong\u003e item in the \u003cstrong\u003eMain Plot Window Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe toolbar allows use of \u003ca href=\"/plot-window/summaryplots/#property-editor\"\u003evector filters\u003c/a\u003e in addition to source stepping:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe corresponding property editor is:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen ResInsight decides stepping dimensions to display, all visible curves in the current plot are taken into account. For instance, well stepping is enabled if all curves display data from the same well, c.f. figure above. This policy applies to the following source stepping dimensions:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eCases\u003c/li\u003e\n\u003cli\u003eWells\u003c/li\u003e\n\u003cli\u003eWell groups\u003c/li\u003e\n\u003cli\u003eRegions\u003c/li\u003e\n\u003cli\u003eCompletions\u003c/li\u003e\n\u003cli\u003eSegments\u003c/li\u003e\n\u003cli\u003eBlock\u003c/li\u003e\n\u003cli\u003eSummary Vectors\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"assign-source-stepping-curve\"\u003eAssign source stepping curve\u003c/h2\u003e\n\n\u003cp\u003eIf the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available.\nBy right-clicking a summary curve or ensemble curve set, the menu item \u003cstrong\u003eSet as Source Stepping Curve\u003c/strong\u003e will use the selected curve as basis for source stepping. All source stepping dimensions for the selected curve will be displayed. When a curve or ensemble is marked for source stepping, a source stepping icon is displayed.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveSetSourceStepping.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eRight-clicking the summary curve or ensemble curve set, and select \u003cstrong\u003eClear Source Stepping Curve\u003c/strong\u003e to leave this mode.\u003c/p\u003e\n\n\u003ch2 id=\"handling-of-summary-curves-and-history-summary-curves\"\u003eHandling of summary curves and history summary curves\u003c/h2\u003e\n\n\u003cp\u003eIf a plot displays both a summary curve and the corresponding history summary curve, the source stepping can be applied to both curves at the same time. If you have a mix of several curves, it might be required to mark one of the curves using \u003cstrong\u003eSet as Source Stepping Curve\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"applying-data-source-change\"\u003eApplying data source change\u003c/h2\u003e\n\n\u003cp\u003eWhen one of the \u003cstrong\u003enext buttons\u003c/strong\u003e are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the \u003cstrong\u003enext well button\u003c/strong\u003e. Then the well source for all curves in the current plot are changed to display data for the next well.\u003c/p\u003e\n",
+                content:  "Summary Plot Source Stepping Summary Source Stepping is a function which enables the user to swiftly step through multiple vectors. The functionality applies both to single summary curves and ensemble curve sets.\nThe functionality is available from both the toolbar and the Summary Curves property editor under a Summary Plot item in the Main Plot Window Project Tree.\nThe toolbar allows use of vector filters in addition to source stepping:\nThe corresponding property editor is:\nWhen ResInsight decides stepping dimensions to display, all visible curves in the current plot are taken into account. For instance, well stepping is enabled if all curves display data from the same well, c.f. figure above. This policy applies to the following source stepping dimensions:\n Cases Wells Well groups Regions Completions Segments Block Summary Vectors  Assign source stepping curve If the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available. By right-clicking a summary curve or ensemble curve set, the menu item Set as Source Stepping Curve will use the selected curve as basis for source stepping. All source stepping dimensions for the selected curve will be displayed. When a curve or ensemble is marked for source stepping, a source stepping icon is displayed.\nRight-clicking the summary curve or ensemble curve set, and select Clear Source Stepping Curve to leave this mode.\nHandling of summary curves and history summary curves If a plot displays both a summary curve and the corresponding history summary curve, the source stepping can be applied to both curves at the same time. If you have a mix of several curves, it might be required to mark one of the curves using Set as Source Stepping Curve.\nApplying data source change When one of the next buttons are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the next well button. Then the well source for all curves in the current plot are changed to display data for the next well.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingBanner.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"summary-plot-source-stepping\"\u003eSummary Plot Source Stepping\u003c/h2\u003e\n\u003cp\u003eSummary Source Stepping is a function which enables the user to swiftly step through multiple vectors. \nThe functionality applies both to single summary curves and ensemble curve sets.\u003c/p\u003e\n\u003cp\u003eThe functionality is available from both the toolbar and the \u003cstrong\u003eSummary Curves\u003c/strong\u003e property editor under a \u003cstrong\u003eSummary Plot\u003c/strong\u003e item in the \u003cstrong\u003eMain Plot Window Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe toolbar allows use of \u003ca href=\"/plot-window/summaryplots/#property-editor\"\u003evector filters\u003c/a\u003e in addition to source stepping:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe corresponding property editor is:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen ResInsight decides stepping dimensions to display, all visible curves in the current plot are taken into account. For instance, well stepping is enabled if all curves display data from the same well, c.f. figure above. This policy applies to the following source stepping dimensions:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCases\u003c/li\u003e\n\u003cli\u003eWells\u003c/li\u003e\n\u003cli\u003eWell groups\u003c/li\u003e\n\u003cli\u003eRegions\u003c/li\u003e\n\u003cli\u003eCompletions\u003c/li\u003e\n\u003cli\u003eSegments\u003c/li\u003e\n\u003cli\u003eBlock\u003c/li\u003e\n\u003cli\u003eSummary Vectors\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"assign-source-stepping-curve\"\u003eAssign source stepping curve\u003c/h2\u003e\n\u003cp\u003eIf the plot contains a mix of different curves, ResInsight might end up with no common stepping dimensions available. \nBy right-clicking a summary curve or ensemble curve set, the menu item \u003cstrong\u003eSet as Source Stepping Curve\u003c/strong\u003e will use the selected curve as basis for source stepping. All source stepping dimensions for the selected curve will be displayed. When a curve or ensemble is marked for source stepping, a source stepping icon is displayed.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveSetSourceStepping.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eRight-clicking the summary curve or ensemble curve set, and select \u003cstrong\u003eClear Source Stepping Curve\u003c/strong\u003e to leave this mode.\u003c/p\u003e\n\u003ch2 id=\"handling-of-summary-curves-and-history-summary-curves\"\u003eHandling of summary curves and history summary curves\u003c/h2\u003e\n\u003cp\u003eIf a plot displays both a summary curve and the corresponding history summary curve, the source stepping can be applied to both curves at the same time. If you have a mix of several curves, it might be required to mark one of the curves using \u003cstrong\u003eSet as Source Stepping Curve\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"applying-data-source-change\"\u003eApplying data source change\u003c/h2\u003e\n\u003cp\u003eWhen one of the \u003cstrong\u003enext buttons\u003c/strong\u003e are clicked, all curves are changed to display data for the next item for the clicked source dimension. Example: The user clicks the \u003cstrong\u003enext well button\u003c/strong\u003e. Then the well source for all curves in the current plot are changed to display data for the next well.\u003c/p\u003e\n",
                 url:      "/plot-window/summarysourcestepping/"
             };
         
@@ -2001,8 +2034,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/wellpaths/"] = {
                 title:    "Well Paths",
-                content:  " ResInsight can import well paths from simple Ascii files. In addition, ResInsight is able to retrieve well paths from an Equinor internal web service.\nResInsight also supports creation of your own user-defined well paths. See Create Well Paths\nAscii Well Paths The command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From File will read the well paths in the selected file, and create one entry for each well path under the Wells item in the Project Tree.\nThe supported ASCII format is quite flexible but the main requirements are:\n Each data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space. Lines starting with \u0026quot;--\u0026quot; or \u0026quot;#\u0026quot; is considered to be comment lines A line starting with none-number-characters are used as a well name after the following rules:  If the line contains a pair of : \u0026quot;'\u0026quot;, \u0026quot;`\u0026quot;, \u0026quot;´\u0026quot;, \u0026quot;’\u0026quot; or \u0026quot;‘\u0026quot; the text between the quotation marks is used as a well name. If the line contains the case insensitive string \u0026ldquo;name\u0026rdquo; with an optional \u0026ldquo;:\u0026rdquo; after then the rest of the line is used as a well name. If there are no quotes or \u0026ldquo;name\u0026rdquo;\u0026rsquo;s, the complete line is used as a well name. If there are several consecutive name-like lines, only the last one will be used  If a well name is found, a new well is created and the following data points are added to it.  Example 1: WELLNAME: WELL1 6507.1 725 2542 2590 6523.5 757 2549 2626.6 6523.5 760 2559 2637.1 -999 WELLNAME: WELL2 550.7 1020.2 2410 2410 551 1004.1 2422.2 2430.2 555.2 993.9 2425 2441.6 -999  Example 2: X Y TVD(MSL) MD(RKB) Name Well_1 6507.1 725 2542 2542 6523.5 757 2549 2578.6 6523.5 760 2559 2589.1 -- A Comment new well This is not its name Name Well_2 550.7 1020.2 2410 2520 551 1004.1 2422.2 2540.2 # a comment inside the data 555.2 993.9 2425 2551.6 3Q AHB-J 5507.0 4638.5 0.0 0.0 5507 4638.5 1628.6 1628.6  Well Path Files are Referenced The well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.\nIf the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.\n\rImporting well paths from SSI-Hub SSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.\nThe command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From SSI-hub launches a wizard to guide you through the process of selecting the well paths you need. Having completed the wizard, the imported wells are accessible as Items under the Wells item in the Project Tree.\nThe well path data is not copied into the ResInsight project as such, but is stored in files in a directory called ProjectFileName_wellpaths in the same directory as your project file.\nAccess to web service:  If you are an Equinor employee, make sure you have access to \u0026ldquo;EDM Landmark\u0026rdquo; and \u0026ldquo;EDM Compass\u0026rdquo;.\n\rWell Path Visualization All the imported well paths are available below the Wells item in the Project Tree.\nThe visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Paths. The Property Editor of the Wells item is shown below\n Global well path visibility \u0026ndash; This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual. Clip Well Paths \u0026ndash; This option hides the top of the Well Paths to avoid displaying the very long lines from the reservoir to the sea surface. Well Path clipping depth distance \u0026ndash; This number is the distance from the top of the reservoir to the clipping depth.  Individual Well Path A well path will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.\nImporting Well Log Files Well log data is imported from LAS-files.\nWell Path Property Editor The well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.\n Appearance group \u0026ndash; Settings in this group affect the well path appearance in the 3D view File group \u0026ndash; Information about the well path file Simulation Well group \u0026ndash; Associated simulation well. ResInsight will try to associate each well path with a simulation well. This is done in the exact same way as looking up an existing well path. If the auto-association fails, the user can set the correct simulation well here. Well Info group \u0026ndash; Metadata for the well path Well Picks group \u0026ndash; Information about imported well picks file containing data for the current well path  Casing Design Some Casing Design elements can be assigned to the well path by selecting Create Casign Design from the right-click menu of the well path.\nThis will create a new child object for the Well Path, named Casing Design. In the Casign Design Property editor well path containment properties such as Casing (with Casing Shoe) and Liner can be added to the well path along with a start and end depth and a diameter.\nThese can be visualised in the 3D View and Well Log Plots on a Well Log Track.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResInsight_WellPathWithSimulationWell.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can import well paths from simple Ascii files.\nIn addition, ResInsight is able to retrieve well paths from an Equinor internal web service.\u003c/p\u003e\n\n\u003cp\u003eResInsight also supports creation of your own user-defined well paths. See \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate Well Paths\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"ascii-well-paths\"\u003eAscii Well Paths\u003c/h2\u003e\n\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From File\u003c/strong\u003e will read the well paths in the selected file, and create one entry for each well path under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe supported ASCII format is quite flexible but the main requirements are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eEach data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space.\u003c/li\u003e\n\u003cli\u003eLines starting with \u003ccode\u003e\u0026quot;--\u0026quot; or \u0026quot;#\u0026quot;\u003c/code\u003e is considered to be comment lines\u003c/li\u003e\n\u003cli\u003eA line starting with none-number-characters are used as a well name after the following rules:\n\n\u003cul\u003e\n\u003cli\u003eIf the line contains a pair of : \u003ccode\u003e\u0026quot;'\u0026quot;, \u0026quot;`\u0026quot;, \u0026quot;´\u0026quot;, \u0026quot;’\u0026quot; or \u0026quot;‘\u0026quot;\u003c/code\u003e the text between the quotation marks is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf the line contains the case insensitive string \u0026ldquo;name\u0026rdquo; with an optional \u0026ldquo;:\u0026rdquo; after then the rest of the line is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf there are no quotes or \u0026ldquo;name\u0026rdquo;\u0026rsquo;s, the complete line is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf there are several consecutive name-like lines, only the last one will be used\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eIf a well name is found, a new well is created and the following data points are added to it.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"example-1\"\u003eExample 1:\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELLNAME: WELL1\n6507.1  725 2542    2590\n6523.5  757 2549    2626.6\n6523.5  760 2559    2637.1\n-999\nWELLNAME: WELL2\n550.7 1020.2  2410   2410\n551   1004.1  2422.2 2430.2\n555.2  993.9  2425   2441.6\n-999\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"example-2\"\u003eExample 2:\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode\u003eX Y TVD(MSL) MD(RKB)\nName Well_1\n6507.1  725 2542    2542\n6523.5  757 2549    2578.6\n6523.5  760 2559    2589.1\n\n-- A Comment new well\nThis is not its name\nName Well_2\n550.7   1020.2  2410    2520\n551 1004.1  2422.2  2540.2\n# a comment inside the data \n555.2   993.9   2425    2551.6\n\n3Q AHB-J\n5507.0  4638.5  0.0 0.0\n5507    4638.5  1628.6  1628.6\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"well-path-files-are-referenced\"\u003eWell Path Files are Referenced\u003c/h3\u003e\n\n\u003cp\u003eThe well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIf the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"importing-well-paths-from-ssi-hub\"\u003eImporting well paths from SSI-Hub\u003c/h2\u003e\n\n\u003cp\u003eSSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.\u003c/p\u003e\n\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From SSI-hub\u003c/strong\u003e launches a wizard to guide you through the process of selecting the well paths you need.\nHaving completed the wizard, the imported wells are accessible as Items under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe well path data is not copied into the ResInsight project as such, but is stored in files in a directory called \u003cem\u003eProjectFileName_wellpaths\u003c/em\u003e in the same directory as your project file.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003cstrong\u003eAccess to web service: \u003c/strong\u003e\nIf you are an Equinor employee, make sure you have access to \u0026ldquo;EDM Landmark\u0026rdquo; and \u0026ldquo;EDM Compass\u0026rdquo;.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"well-path-visualization\"\u003eWell Path Visualization\u003c/h2\u003e\n\n\u003cp\u003eAll the imported well paths are available below the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellsInTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Paths. The \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eWells\u003c/strong\u003e item is shown below\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathCollectionProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGlobal well path visibility\u003c/strong\u003e \u0026ndash; This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eClip Well Paths\u003c/strong\u003e \u0026ndash; This option hides the top of the Well Paths to avoid displaying the very long lines from the reservoir to the sea surface.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Path clipping depth distance\u003c/strong\u003e \u0026ndash; This number is the distance from the top of the reservoir to the clipping depth.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"individual-well-path\"\u003eIndividual Well Path\u003c/h2\u003e\n\n\u003cp\u003eA well path will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.\u003c/p\u003e\n\n\u003ch3 id=\"importing-well-log-files\"\u003eImporting Well Log Files\u003c/h3\u003e\n\n\u003cp\u003eWell log data is \u003ca href=\"/import/lasfile/#importing-a-las-file\"\u003eimported from LAS-files\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"well-path-property-editor\"\u003eWell Path Property Editor\u003c/h3\u003e\n\n\u003cp\u003eThe well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance group\u003c/strong\u003e \u0026ndash; Settings in this group affect the well path appearance in the 3D view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile group\u003c/strong\u003e \u0026ndash; Information about the well path file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSimulation Well group\u003c/strong\u003e \u0026ndash; Associated simulation well. ResInsight will try to associate each well path with a simulation well. This is done in the exact same way as looking up an existing well path. If the auto-association fails, the user can set the correct simulation well here.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Info group\u003c/strong\u003e \u0026ndash; Metadata for the well path\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Picks group\u003c/strong\u003e \u0026ndash; Information about imported \u003ca href=\"/3d-main-window/formations/#well-picks\"\u003ewell picks\u003c/a\u003e file containing data for the current well path\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"casing-design\"\u003eCasing Design\u003c/h3\u003e\n\n\u003cp\u003eSome Casing Design elements can be assigned to the well path by selecting \u003cstrong\u003eCreate Casign Design\u003c/strong\u003e from the right-click menu of the well path.\u003c/p\u003e\n\n\u003cp\u003eThis will create a new child object for the Well Path, named \u003cstrong\u003eCasing Design\u003c/strong\u003e. In the \u003cstrong\u003eCasign Design\u003c/strong\u003e Property editor\nwell path containment properties such as Casing (with Casing Shoe) and Liner can be added to the well path along with a start and end depth and a diameter.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesign.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThese can be visualised in the 3D View and Well Log Plots on a \u003ca href=\"/plot-window/welllogsandplots/#tracks\"\u003eWell Log Track\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesign3D.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesignPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "ResInsight can import well paths from simple Ascii files. In addition, ResInsight is able to retrieve well paths from an Equinor internal web service.\nResInsight also supports creation of your own user-defined well paths. See Create Well Paths\nAscii Well Paths The command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From File will read the well paths in the selected file, and create one entry for each well path under the Wells item in the Project Tree.\nThe supported ASCII format is quite flexible but the main requirements are:\n Each data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space. Lines starting with \u0026quot;--\u0026quot; or \u0026quot;#\u0026quot; is considered to be comment lines A line starting with none-number-characters are used as a well name after the following rules:  If the line contains a pair of :  \u0026quot;'\u0026quot;, \u0026quot;`\u0026quot;, \u0026quot;´\u0026quot;, \u0026quot;’\u0026quot; or \u0026quot;‘\u0026quot; the text between the quotation marks is used as a well name. If the line contains the case insensitive string \u0026ldquo;name\u0026rdquo; with an optional \u0026ldquo;:\u0026rdquo; after then the rest of the line is used as a well name. If there are no quotes or \u0026ldquo;name\u0026rdquo;\u0026lsquo;s, the complete line is used as a well name. If there are several consecutive name-like lines, only the last one will be used   If a well name is found, a new well is created and the following data points are added to it.  Example 1: WELLNAME: WELL1\r6507.1\t725\t2542\t2590\r6523.5\t757\t2549\t2626.6\r6523.5\t760\t2559\t2637.1\r-999\rWELLNAME: WELL2\r550.7 1020.2 2410 2410\r551 1004.1 2422.2 2430.2\r555.2 993.9 2425 2441.6\r-999\r Example 2: X Y TVD(MSL) MD(RKB)\rName Well_1\r6507.1\t725\t2542\t2542\r6523.5\t757\t2549\t2578.6\r6523.5\t760\t2559\t2589.1\r-- A Comment new well\rThis is not its name\rName Well_2\r550.7\t1020.2\t2410\t2520\r551\t1004.1\t2422.2\t2540.2\r# a comment inside the data 555.2\t993.9\t2425\t2551.6\r3Q AHB-J\r5507.0\t4638.5\t0.0\t0.0\r5507\t4638.5\t1628.6\t1628.6\r Well Path Files are Referenced The well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.\nIf the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.\n\rImporting well paths from SSI-Hub SSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.\nThe command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From SSI-hub launches a wizard to guide you through the process of selecting the well paths you need. Having completed the wizard, the imported wells are accessible as Items under the Wells item in the Project Tree.\nThe well path data is not copied into the ResInsight project as such, but is stored in files in a directory called ProjectFileName_wellpaths in the same directory as your project file.\nAccess to web service: If you are an Equinor employee, make sure you have access to \u0026ldquo;EDM Landmark\u0026rdquo; and \u0026ldquo;EDM Compass\u0026rdquo;.\n\rWell Path Visualization All the imported well paths are available below the Wells item in the Project Tree.\nThe visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Paths. The Property Editor of the Wells item is shown below\n Global well path visibility \u0026ndash; This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual. Clip Well Paths \u0026ndash; This option hides the top of the Well Paths to avoid displaying the very long lines from the reservoir to the sea surface. Well Path clipping depth distance \u0026ndash; This number is the distance from the top of the reservoir to the clipping depth.  Individual Well Path A well path will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.\nImporting Well Log Files Well log data is imported from LAS-files.\nWell Path Property Editor The well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.\n Appearance group \u0026ndash; Settings in this group affect the well path appearance in the 3D view File group \u0026ndash; Information about the well path file Simulation Well group \u0026ndash; Associated simulation well. ResInsight will try to associate each well path with a simulation well. This is done in the exact same way as looking up an existing well path. If the auto-association fails, the user can set the correct simulation well here. Well Info group \u0026ndash; Metadata for the well path Well Picks group \u0026ndash; Information about imported well picks file containing data for the current well path  Casing Design Some Casing Design elements can be assigned to the well path by selecting Create Casign Design from the right-click menu of the well path.\nThis will create a new child object for the Well Path, named Casing Design. In the Casign Design Property editor well path containment properties such as Casing (with Casing Shoe) and Liner can be added to the well path along with a start and end depth and a diameter.\nThese can be visualised in the 3D View and Well Log Plots on a Well Log Track.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResInsight_WellPathWithSimulationWell.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can import well paths from simple Ascii files. \nIn addition, ResInsight is able to retrieve well paths from an Equinor internal web service.\u003c/p\u003e\n\u003cp\u003eResInsight also supports creation of your own user-defined well paths. See \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate Well Paths\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"ascii-well-paths\"\u003eAscii Well Paths\u003c/h2\u003e\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From File\u003c/strong\u003e will read the well paths in the selected file, and create one entry for each well path under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe supported ASCII format is quite flexible but the main requirements are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEach data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space.\u003c/li\u003e\n\u003cli\u003eLines starting with \u003ccode\u003e\u0026quot;--\u0026quot; or \u0026quot;#\u0026quot;\u003c/code\u003e is considered to be comment lines\u003c/li\u003e\n\u003cli\u003eA line starting with none-number-characters are used as a well name after the following rules:\n\u003cul\u003e\n\u003cli\u003eIf the line contains a pair of : \u003ccode\u003e \u0026quot;'\u0026quot;, \u0026quot;`\u0026quot;, \u0026quot;´\u0026quot;, \u0026quot;’\u0026quot; or \u0026quot;‘\u0026quot;\u003c/code\u003e the text between the quotation marks is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf the line contains the case insensitive string \u0026ldquo;name\u0026rdquo; with an optional \u0026ldquo;:\u0026rdquo; after then the rest of the line is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf there are no quotes or \u0026ldquo;name\u0026rdquo;\u0026lsquo;s, the complete line is used as a well name.\u003c/li\u003e\n\u003cli\u003eIf there are several consecutive name-like lines, only the last one will be used\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eIf a well name is found, a new well is created and the following data points are added to it.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"example-1\"\u003eExample 1:\u003c/h4\u003e\n\u003cpre\u003e\u003ccode\u003eWELLNAME: WELL1\r\n6507.1\t725\t2542\t2590\r\n6523.5\t757\t2549\t2626.6\r\n6523.5\t760\t2559\t2637.1\r\n-999\r\nWELLNAME: WELL2\r\n550.7 1020.2  2410   2410\r\n551   1004.1  2422.2 2430.2\r\n555.2  993.9  2425   2441.6\r\n-999\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"example-2\"\u003eExample 2:\u003c/h4\u003e\n\u003cpre\u003e\u003ccode\u003eX Y TVD(MSL) MD(RKB)\r\nName Well_1\r\n6507.1\t725\t2542\t2542\r\n6523.5\t757\t2549\t2578.6\r\n6523.5\t760\t2559\t2589.1\r\n\r\n-- A Comment new well\r\nThis is not its name\r\nName Well_2\r\n550.7\t1020.2\t2410\t2520\r\n551\t1004.1\t2422.2\t2540.2\r\n# a comment inside the data \r\n555.2\t993.9\t2425\t2551.6\r\n\r\n3Q AHB-J\r\n5507.0\t4638.5\t0.0\t0.0\r\n5507\t4638.5\t1628.6\t1628.6\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"well-path-files-are-referenced\"\u003eWell Path Files are Referenced\u003c/h3\u003e\n\u003cp\u003eThe well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIf the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"importing-well-paths-from-ssi-hub\"\u003eImporting well paths from SSI-Hub\u003c/h2\u003e\n\u003cp\u003eSSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.\u003c/p\u003e\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Well Paths From SSI-hub\u003c/strong\u003e launches a wizard to guide you through the process of selecting the well paths you need.\nHaving completed the wizard, the imported wells are accessible as Items under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe well path data is not copied into the ResInsight project as such, but is stored in files in a directory called \u003cem\u003eProjectFileName_wellpaths\u003c/em\u003e in the same directory as your project file.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eAccess to web service: \u003c!-- raw HTML omitted --\u003e\nIf you are an Equinor employee, make sure you have access to \u0026ldquo;EDM Landmark\u0026rdquo; and \u0026ldquo;EDM Compass\u0026rdquo;.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"well-path-visualization\"\u003eWell Path Visualization\u003c/h2\u003e\n\u003cp\u003eAll the imported well paths are available below the \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellsInTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Paths. The \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eWells\u003c/strong\u003e item is shown below\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathCollectionProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGlobal well path visibility\u003c/strong\u003e \u0026ndash; This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eClip Well Paths\u003c/strong\u003e \u0026ndash; This option hides the top of the Well Paths to avoid displaying the very long lines from the reservoir to the sea surface.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Path clipping depth distance\u003c/strong\u003e \u0026ndash; This number is the distance from the top of the reservoir to the clipping depth.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"individual-well-path\"\u003eIndividual Well Path\u003c/h2\u003e\n\u003cp\u003eA well path will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.\u003c/p\u003e\n\u003ch3 id=\"importing-well-log-files\"\u003eImporting Well Log Files\u003c/h3\u003e\n\u003cp\u003eWell log data is \u003ca href=\"/import/lasfile/#importing-a-las-file\"\u003eimported from LAS-files\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"well-path-property-editor\"\u003eWell Path Property Editor\u003c/h3\u003e\n\u003cp\u003eThe well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance group\u003c/strong\u003e \u0026ndash; Settings in this group affect the well path appearance in the 3D view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile group\u003c/strong\u003e \u0026ndash; Information about the well path file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSimulation Well group\u003c/strong\u003e \u0026ndash; Associated simulation well. ResInsight will try to associate each well path with a simulation well. This is done in the exact same way as looking up an existing well path. If the auto-association fails, the user can set the correct simulation well here.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Info group\u003c/strong\u003e \u0026ndash; Metadata for the well path\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Picks group\u003c/strong\u003e \u0026ndash; Information about imported \u003ca href=\"/3d-main-window/formations/#well-picks\"\u003ewell picks\u003c/a\u003e file containing data for the current well path\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"casing-design\"\u003eCasing Design\u003c/h3\u003e\n\u003cp\u003eSome Casing Design elements can be assigned to the well path by selecting \u003cstrong\u003eCreate Casign Design\u003c/strong\u003e from the right-click menu of the well path.\u003c/p\u003e\n\u003cp\u003eThis will create a new child object for the Well Path, named \u003cstrong\u003eCasing Design\u003c/strong\u003e. In the \u003cstrong\u003eCasign Design\u003c/strong\u003e Property editor \nwell path containment properties such as Casing (with Casing Shoe) and Liner can be added to the well path along with a start and end depth and a diameter.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesign.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThese can be visualised in the 3D View and Well Log Plots on a \u003ca href=\"/plot-window/welllogsandplots/#tracks\"\u003eWell Log Track\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesign3D.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CasignDesignPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/wells-and-completions/wellpaths/"
             };
         
@@ -2010,8 +2043,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2018_11/"] = {
                 title:    "What's New in 2018.11",
-                content:  " ResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.\nLocal Grid Refinement (LGR) Local Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.\nSee Completions LGR\nWell Path Creation ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.\nSee Create Well Paths\nContour Maps ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.\nSee Contour Maps\nSummary Plotting Well Bore Stability Plots and Casing Design ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.\nSee Well Bore Stability Plots\nMemory Management ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.\nSee Memory Management\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/TemporaryLGR.png\" alt=\"Temporary LGR\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.\u003c/p\u003e\n\n\u003ch2 id=\"local-grid-refinement-lgr\"\u003eLocal Grid Refinement (LGR)\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eLocal Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"well-path-creation\"\u003eWell Path Creation\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/WellPathCreation.png\" alt=\"Well Path Creation\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate Well Paths\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"contour-maps\"\u003eContour Maps\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/ContourMaps1.png\" alt=\"Contour Maps\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/contourmaps/\"\u003eContour Maps\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"summary-plotting\"\u003eSummary Plotting\u003c/h2\u003e\n\n\u003ch2 id=\"well-bore-stability-plots-and-casing-design\"\u003eWell Bore Stability Plots and Casing Design\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/WellBoreStabilityPlots.png\" alt=\"Well Bore Stability Plots\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create \u003cstrong\u003eWell Bore Stability\u003c/strong\u003e plots for Geomechanical cases. These plots are specialized \u003cstrong\u003eWell Log Plots\u003c/strong\u003e and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/plot-window/wellborestabilityplots/\"\u003eWell Bore Stability Plots\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"memory-management\"\u003eMemory Management\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/introduction/MemoryManagementBanner.png\" alt=\"Memory Management\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/misc/memorymanagement/\"\u003eMemory Management\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "ResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.\nLocal Grid Refinement (LGR) Local Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.\nSee Completions LGR\nWell Path Creation ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.\nSee Create Well Paths\nContour Maps ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.\nSee Contour Maps\nSummary Plotting Well Bore Stability Plots and Casing Design ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.\nSee Well Bore Stability Plots\nMemory Management ResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.\nSee Memory Management\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/introduction/TemporaryLGR.png\" alt=\"Temporary LGR\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight 2018.11 is the latest version of ResInsight, the professional quality, open source 3D visualization, curve plotting and post-processing tool for Eclipse reservoir models. Version 2018.11 contains a larger number of new and exciting features, some of which are listed below.\u003c/p\u003e\n\u003ch2 id=\"local-grid-refinement-lgr\"\u003eLocal Grid Refinement (LGR)\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eLocal Grid Refinement (LGR) can be created based on Eclipse simulations. The refined grids can also be visualised in 3D.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"well-path-creation\"\u003eWell Path Creation\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/WellPathCreation.png\" alt=\"Well Path Creation\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight lets the user create new/custom well paths by clicking in the 3D view. A self-established well path will behave in the same way as a regular imported well path.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate Well Paths\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"contour-maps\"\u003eContour Maps\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/ContourMaps1.png\" alt=\"Contour Maps\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D map.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/contourmaps/\"\u003eContour Maps\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"summary-plotting\"\u003eSummary Plotting\u003c/h2\u003e\n\u003ch2 id=\"well-bore-stability-plots-and-casing-design\"\u003eWell Bore Stability Plots and Casing Design\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/WellBoreStabilityPlots.png\" alt=\"Well Bore Stability Plots\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create \u003cstrong\u003eWell Bore Stability\u003c/strong\u003e plots for Geomechanical cases. These plots are specialized \u003cstrong\u003eWell Log Plots\u003c/strong\u003e and contain a visualization of Formations, Well Path Attributes as well as a set of well path derived curves in two different tracks.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/plot-window/wellborestabilityplots/\"\u003eWell Bore Stability Plots\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"memory-management\"\u003eMemory Management\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/introduction/MemoryManagementBanner.png\" alt=\"Memory Management\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can require a considerable amount of memory to hold all the grids and necessary result variables. A Memory Management system is now in place to help the user if available memory is low.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/misc/memorymanagement/\"\u003eMemory Management\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2018_11/"
             };
         
@@ -2019,8 +2052,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/windows-installation/"] = {
                 title:    "Windows Installation",
-                content:  " ResInsight Installation  Download ZIP binary distribution from https://github.com/OPM/ResInsight/releases Extract content from ZIP file Start ResInsight.exe  The binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see Build Instructions.\n\rOctave Installation (optional)  Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-\u0026gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.\n( Usually C:\\Your\\Path\\To\\Octave-x.x.x\\bin\\octave-cli.exe )  A binary package of ResInsight will normally not work with other Octave versions than the one it is compiled with.\n\rYou have to point to the cli binary in the windows octave installation. The octave.exe will not work as it is launching the octave GUI.\n\r",
-                html:     "\n\n\u003ch3 id=\"resinsight-installation\"\u003eResInsight Installation\u003c/h3\u003e\n\n\u003col\u003e\n\u003cli\u003eDownload ZIP binary distribution from \u003ca href=\"https://github.com/OPM/ResInsight/releases\" title=\"release section on GitHub\"\u003ehttps://github.com/OPM/ResInsight/releases\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExtract content from ZIP file\u003c/li\u003e\n\u003cli\u003eStart ResInsight.exe\u003c/li\u003e\n\u003c/ol\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see\n\u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"octave-installation-optional\"\u003eOctave Installation (optional)\u003c/h3\u003e\n\n\u003col\u003e\n\u003cli\u003eDownload \u003ca href=\"ftp://ftp.gnu.org/gnu/octave/windows\"\u003eOctave-4.0.0\u003c/a\u003e and install it. (Newer versions will not work)\u003c/li\u003e\n\u003cli\u003eLaunch ResInsight.exe, open \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eOn the \u003cstrong\u003eOctave\u003c/strong\u003e tab, enter the path to the Octave command line interpreter executable.\u003cbr /\u003e\n( Usually \u003cem\u003e\u003ccode\u003eC:\\Your\\Path\\To\\Octave-x.x.x\\bin\\octave-cli.exe\u003c/code\u003e\u003c/em\u003e )\u003c/li\u003e\n\u003c/ol\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eA binary package of ResInsight will normally \u003cb\u003enot\u003c/b\u003e work with other Octave versions than the one it is compiled with.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eYou \u003cb\u003ehave\u003c/b\u003e to point to the \u003cb\u003ecli\u003c/b\u003e binary in the windows octave installation. The \u003ccode\u003eoctave.exe\u003c/code\u003e will not work as it is launching the octave GUI.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
+                content:  "ResInsight Installation  Download ZIP binary distribution from https://github.com/OPM/ResInsight/releases Extract content from ZIP file Start ResInsight.exe  The binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see Build Instructions.\n\rOctave Installation (optional)  Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-\u0026gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.\n( Usually C:\\Your\\Path\\To\\Octave-x.x.x\\bin\\octave-cli.exe )  A binary package of ResInsight will normally notwork with other Octave versions than the one it is compiled with.\n\rYou haveto point to the clibinary in the windows octave installation. The octave.exewill not work as it is launching the octave GUI.\n\r",
+                html:     "\u003ch3 id=\"resinsight-installation\"\u003eResInsight Installation\u003c/h3\u003e\n\u003col\u003e\n\u003cli\u003eDownload ZIP binary distribution from \u003ca href=\"https://github.com/OPM/ResInsight/releases\" title=\"release section on GitHub\"\u003ehttps://github.com/OPM/ResInsight/releases\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExtract content from ZIP file\u003c/li\u003e\n\u003cli\u003eStart ResInsight.exe\u003c/li\u003e\n\u003c/ol\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe binary distribution does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see \n\u003ca href=\"/getting-started/download-and-install/buildinstructions/\"\u003eBuild Instructions\u003c/a\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"octave-installation-optional\"\u003eOctave Installation (optional)\u003c/h3\u003e\n\u003col\u003e\n\u003cli\u003eDownload \u003ca href=\"ftp://ftp.gnu.org/gnu/octave/windows\"\u003eOctave-4.0.0\u003c/a\u003e and install it. (Newer versions will not work)\u003c/li\u003e\n\u003cli\u003eLaunch ResInsight.exe, open \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eOn the \u003cstrong\u003eOctave\u003c/strong\u003e tab, enter the path to the Octave command line interpreter executable.\u003cbr\u003e\n( Usually \u003cem\u003e\u003ccode\u003eC:\\Your\\Path\\To\\Octave-x.x.x\\bin\\octave-cli.exe\u003c/code\u003e\u003c/em\u003e )\u003c/li\u003e\n\u003c/ol\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eA binary package of ResInsight will normally \u003c!-- raw HTML omitted --\u003enot\u003c!-- raw HTML omitted --\u003e work with other Octave versions than the one it is compiled with.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eYou \u003c!-- raw HTML omitted --\u003ehave\u003c!-- raw HTML omitted --\u003e to point to the \u003c!-- raw HTML omitted --\u003ecli\u003c!-- raw HTML omitted --\u003e binary in the windows octave installation. The \u003c!-- raw HTML omitted --\u003eoctave.exe\u003c!-- raw HTML omitted --\u003e will not work as it is launching the octave GUI.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
                 url:      "/getting-started/download-and-install/windows-installation/"
             };
         
@@ -2029,7 +2062,7 @@ if (!doNotTrack) {
             window.store["/import/soursimrlresults/"] = {
                 title:    "SourSimRL Results",
                 content:  "ResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization. Results from SourSimRL in its sourres binary format can be imported using the SourSim File Name field as shown below:\nImporting such a file will enable result type called SourSimRL as explained in Eclipse Result Types\n",
-                html:     "\u003cp\u003eResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization.\nResults from SourSimRL in its \u003cem\u003esourres\u003c/em\u003e binary format can be imported using the \u003cstrong\u003eSourSim File Name\u003c/strong\u003e field as shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/soursim_import.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eImporting such a file will enable result type called \u003cstrong\u003eSourSimRL\u003c/strong\u003e as explained in \u003ca href=\"/3d-main-window/cellresults/#eclipse-result-types\"\u003eEclipse Result Types\u003c/a\u003e\u003c/p\u003e\n",
+                html:     "\u003cp\u003eResInsight is able to import transient results from the simulation software SourSimRL to combine reservoir souring simulation data with an Eclipse case for analysis and visualization. \nResults from SourSimRL in its \u003cem\u003esourres\u003c/em\u003e binary format can be imported using the \u003cstrong\u003eSourSim File Name\u003c/strong\u003e field as shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/soursim_import.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eImporting such a file will enable result type called \u003cstrong\u003eSourSimRL\u003c/strong\u003e as explained in \u003ca href=\"/3d-main-window/cellresults/\"\u003eEclipse Result Types\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/import/soursimrlresults/"
             };
         
@@ -2037,8 +2070,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/buildinstructions/"] = {
                 title:    "Build Instructions",
-                content:  " Source code The source code is hosted at GitHub\nIn a git enabled shell do: git clone https://github.com/OPM/ResInsight.git\nDependencies and Prerequisites Windows Compiler Visual Studio 2015 and later is supported.\nGCC Compiler GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with\nsource /opt/rh/devtoolset-3/enable  Qt5 Qt Qt5 version 5.6.0 or later is supported.\nOn some configurations you will be asked to specify the location of Qt5. Example for Windows : Qt5_DIR=d:\\Qt\\5.11.3\\msvc2017_64\\lib\\cmake\\Qt5\nQt4 (Deprecated) Qt4 is marked as deprecated and support for using Qt4 will soon be removed.\n\rQt Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.\nRESINSIGHT_BUILD_WITH_QT5=FALSE\nYou will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this : Qt-patch\nCMake CMake version 2.8 or later is supported.\nBuild Instructions The ResInsight build may be configured in different ways, with optional support for Octave plugins, ABAQUS ODB API, HDF5, Pyton, and OpenMP. This is configured using options in CMake.\nIf you check the button \u0026lsquo;Grouped\u0026rsquo; in the CMake GUI, the CMake variables are grouped by prefix. This makes it easier to see all of the options for ResInsight.\n Open the CMake GUI Set the path to the source code Set the path to the build directory Click Configure and select your preferred compiler Set the build options and click \u0026ldquo;Configure\u0026rdquo; again (see ResInsight specific options below) Click Generate to generate the makefiles or solution file and project files in the build directory Run the compiler using the generated makefiles or solution file/project files to build ResInsight  Windows ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015\u0026frasl;2017. Typical usage on Windows is to follow the build instructions above, and then open the generated solution file in Visual Studio to build the application.\nLinux Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:\n make make install  To build from the command line without using the CMake GUI:\n mkdir ResInsight_build cd ResInsight_build \u0026hellip; (set CMake options) \u0026hellip; cmake \u0026lt; path to ResInsight source folder \u0026gt; make make install  You will find the ResInsight binary under the Install directory in your build directory.\nCMake Options for ResInsight    CMake Name Default Description     RESINSIGHT_BUILD_DOCUMENTATION OFF Use Doxygen to create the HTML based API documentation. Doxygen must be properly installed.   RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python   RESINSIGHT_HDF5_DIR Blank Windows Only: Optional path to HDF5 libraries on Windows   RESINSIGHT_ODB_API_DIR Blank Optional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models   RESINSIGHT_USE_OPENMP ON Enable OpenMP parallellization in the code    Advanced Options To be able to modify Advanced Options from the CMake User Interface, tick the checkbox Advanced\n   CMake Name Default Description     RESINSIGHT_BUILD_WITH_QT5 ON If ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed)   RESINSIGHT_QT5_BUNDLE_LIBRARIES OFF Linux only: Include Qt5 libraries in the installation package   RESINSIGHT_BUNDLE_OPENSSL OFF Bundle the OpenSSL library DLLs in the Windows installer package   RESINSIGHT_ENABLE_COTIRE OFF Experimental speedup of compilation using cotire   RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING ON Enable Souring features   RESINSIGHT_INCLUDE_APPFWK_TESTS OFF Include unit tests from thirdparty libraries AppFwk and VizFwk   RESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS OFF Include Application Code Unit Tests   RESINSIGHT_PRIVATE_INSTALL ON Linux only: Include libecl libraries in the installation package   RESINSIGHT_HDF5_BUNDLE_LIBRARIES OFF Linux only: Include HDF5 libraries in the installation package    Configuration parameters for Python (beta) These parameters are considered beta, and might change.\n   CMake Name Default Description     RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python   RESINSIGHT_GRPC_PYTHON_EXECUTABLE Blank Location of Python3 executable   RESINSIGHT_GRPC_INSTALL_PREFIX Blank Linux only : Installation prefix for gRPC    Optional Libraries and features Python (Beta) Scripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.\nThe current build instructions are specified in text files in the ResInsight repository.\n Grpc install instructions Helper script for Linux  See Python API  for how to use the Python library.\nOctave Octave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:\nOCTAVE_CONFIG_EXECUTABLE : d:\\octave\\Octave-4.0.0\\bin\\octave-config.exe\nIt is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like \u0026lsquo;Failed to find mkoctfile\u0026rsquo;. This will not break the build or compilation of ResInsight.\nResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.\nOctave Dependencies for Debian Based Distributions The following command line can be used as a starting point to install required libraries sudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev\nODB support ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library files must be specified. Leaving this option blank gives a build without ODB support. ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.\nHDF5 HDF5 is used to read SourSimRL result files. On Windows this is optional, while on Linux the installed HDF5 library will be used if present.\nUse an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.\nTested with 1.8.18 on windows, and default installation on RedHat 6.\n",
-                html:     "\n\n\u003ch2 id=\"source-code\"\u003eSource code\u003c/h2\u003e\n\n\u003cp\u003eThe source code is hosted at \u003ca href=\"https://github.com/opm/resinsight\"\u003eGitHub\u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003eIn a git enabled shell do: \u003ccode\u003egit clone https://github.com/OPM/ResInsight.git\u003c/code\u003e\u003c/p\u003e\n\n\u003ch2 id=\"dependencies-and-prerequisites\"\u003eDependencies and Prerequisites\u003c/h2\u003e\n\n\u003ch3 id=\"windows-compiler\"\u003eWindows Compiler\u003c/h3\u003e\n\n\u003cp\u003eVisual Studio 2015 and later is supported.\u003c/p\u003e\n\n\u003ch3 id=\"gcc-compiler\"\u003eGCC Compiler\u003c/h3\u003e\n\n\u003cp\u003eGCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003esource /opt/rh/devtoolset-3/enable\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"qt5\"\u003eQt5\u003c/h3\u003e\n\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt\u003c/a\u003e Qt5 version 5.6.0 or later is supported.\u003c/p\u003e\n\n\u003cp\u003eOn some configurations you will be asked to specify the location of Qt5. Example for Windows :\n\u003ccode\u003eQt5_DIR=d:\\Qt\\5.11.3\\msvc2017_64\\lib\\cmake\\Qt5\u003c/code\u003e\u003c/p\u003e\n\n\u003ch4 id=\"qt4-deprecated\"\u003eQt4 (Deprecated)\u003c/h4\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eQt4 is marked as deprecated and support for using Qt4 will soon be removed.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt\u003c/a\u003e Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.\u003c/p\u003e\n\n\u003cp\u003e\u003ccode\u003eRESINSIGHT_BUILD_WITH_QT5=FALSE\u003c/code\u003e\u003c/p\u003e\n\n\u003cp\u003eYou will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this :\n\u003ca href=\"https://github.com/appleseedhq/appleseed/wiki/Making-Qt-4.8.7-compile-with-Visual-Studio-2015\"\u003eQt-patch\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"cmake\"\u003eCMake\u003c/h3\u003e\n\n\u003cp\u003e\u003ca href=\"https://cmake.org/download/\"\u003eCMake\u003c/a\u003e version 2.8 or later is supported.\u003c/p\u003e\n\n\u003ch2 id=\"build-instructions\"\u003eBuild Instructions\u003c/h2\u003e\n\n\u003cp\u003eThe ResInsight build may be configured in different ways, with optional support for Octave plugins,\nABAQUS ODB API, HDF5, Pyton, and OpenMP. This is configured using options in CMake.\u003c/p\u003e\n\n\u003cp\u003eIf you check the button \u0026lsquo;Grouped\u0026rsquo; in the CMake GUI, the CMake variables are grouped by prefix.\nThis makes it easier to see all of the options for ResInsight.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eOpen the CMake GUI\u003c/li\u003e\n\u003cli\u003eSet the path to the source code\u003c/li\u003e\n\u003cli\u003eSet the path to the build directory\u003c/li\u003e\n\u003cli\u003eClick \u003cstrong\u003eConfigure\u003c/strong\u003e and select your preferred compiler\u003c/li\u003e\n\u003cli\u003eSet the build options and click \u0026ldquo;Configure\u0026rdquo; again (see ResInsight specific options below)\u003c/li\u003e\n\u003cli\u003eClick \u003cstrong\u003eGenerate\u003c/strong\u003e to generate the makefiles or solution file and project files in the build directory\u003c/li\u003e\n\u003cli\u003eRun the compiler using the generated makefiles or solution file/project files to build ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"windows\"\u003eWindows\u003c/h3\u003e\n\n\u003cp\u003eResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio \u003csup\u003e2015\u003c/sup\u003e\u0026frasl;\u003csub\u003e2017\u003c/sub\u003e.\nTypical usage on Windows is to follow the build instructions above, and then open the generated\nsolution file in Visual Studio to build the application.\u003c/p\u003e\n\n\u003ch3 id=\"linux\"\u003eLinux\u003c/h3\u003e\n\n\u003cp\u003eTypical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003emake\u003c/li\u003e\n\u003cli\u003emake install\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eTo build from the command line without using the CMake GUI:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003emkdir ResInsight_build\u003c/li\u003e\n\u003cli\u003ecd ResInsight_build\u003c/li\u003e\n\u003cli\u003e\u0026hellip;\u003c/li\u003e\n\u003cli\u003e(set CMake options)\u003c/li\u003e\n\u003cli\u003e\u0026hellip;\u003c/li\u003e\n\u003cli\u003ecmake \u0026lt; path to ResInsight source folder \u0026gt;\u003c/li\u003e\n\u003cli\u003emake\u003c/li\u003e\n\u003cli\u003emake install\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eYou will find the ResInsight binary under the Install directory in your build directory.\u003c/p\u003e\n\n\u003ch3 id=\"cmake-options-for-resinsight\"\u003eCMake Options for ResInsight\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUILD_DOCUMENTATION\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eUse Doxygen to create the HTML based API documentation. Doxygen must be properly installed.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable gRPC scripting server. Required to be able to use ResInsight from Python\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_HDF5_DIR\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eWindows Only: Optional path to HDF5 libraries on Windows\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ODB_API_DIR\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eOptional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_USE_OPENMP\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eEnable OpenMP parallellization in the code\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"advanced-options\"\u003eAdvanced Options\u003c/h4\u003e\n\n\u003cp\u003eTo be able to modify \u003cstrong\u003eAdvanced Options\u003c/strong\u003e from the CMake User Interface, tick the checkbox \u003cstrong\u003eAdvanced\u003c/strong\u003e\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUILD_WITH_QT5\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eIf ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_QT5_BUNDLE_LIBRARIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eLinux only: Include Qt5 libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUNDLE_OPENSSL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eBundle the OpenSSL library DLLs in the Windows installer package\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_COTIRE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eExperimental speedup of compilation using cotire\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eEnable Souring features\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_INCLUDE_APPFWK_TESTS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eInclude unit tests from thirdparty libraries AppFwk and VizFwk\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eInclude Application Code Unit Tests\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_PRIVATE_INSTALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eLinux only: Include libecl libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_HDF5_BUNDLE_LIBRARIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eLinux only: Include HDF5 libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"configuration-parameters-for-python-beta\"\u003eConfiguration parameters for Python (beta)\u003c/h4\u003e\n\n\u003cp\u003eThese parameters are considered beta, and might change.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable gRPC scripting server. Required to be able to use ResInsight from Python\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_PYTHON_EXECUTABLE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eLocation of Python3 executable\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_INSTALL_PREFIX\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eLinux only : Installation prefix for gRPC\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"optional-libraries-and-features\"\u003eOptional Libraries and features\u003c/h3\u003e\n\n\u003ch4 id=\"python-beta\"\u003ePython (Beta)\u003c/h4\u003e\n\n\u003cp\u003eScripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.\u003c/p\u003e\n\n\u003cp\u003eThe current build instructions are specified in text files in the ResInsight repository.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/OPM/ResInsight/blob/dev/GRPC_install_instructions.txt\"\u003eGrpc install instructions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/OPM/ResInsight/blob/dev/build_grpc_linux.sh\"\u003eHelper script for Linux\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSee \u003ca href=\"/scripting/pythonrips/\"\u003e Python API \u003c/a\u003e for how to use the Python library.\u003c/p\u003e\n\n\u003ch4 id=\"octave\"\u003eOctave\u003c/h4\u003e\n\n\u003cp\u003eOctave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:\u003c/p\u003e\n\n\u003cp\u003e\u003ccode\u003eOCTAVE_CONFIG_EXECUTABLE : d:\\octave\\Octave-4.0.0\\bin\\octave-config.exe\u003c/code\u003e\u003c/p\u003e\n\n\u003cp\u003eIt is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for\nthe Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like \u0026lsquo;Failed to find mkoctfile\u0026rsquo;.\nThis will not break the build or compilation of ResInsight.\u003c/p\u003e\n\n\u003cp\u003eResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.\u003c/p\u003e\n\n\u003ch5 id=\"octave-dependencies-for-debian-based-distributions\"\u003eOctave Dependencies for Debian Based Distributions\u003c/h5\u003e\n\n\u003cp\u003eThe following command line can be used as a starting point to install required libraries\n\u003ccode\u003esudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev\u003c/code\u003e\u003c/p\u003e\n\n\u003ch4 id=\"odb-support\"\u003eODB support\u003c/h4\u003e\n\n\u003cp\u003eResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API\nfrom Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library\nfiles must be specified. Leaving this option blank gives a build without ODB support.\nResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.\u003c/p\u003e\n\n\u003ch4 id=\"hdf5\"\u003eHDF5\u003c/h4\u003e\n\n\u003cp\u003eHDF5 is used to read SourSimRL result files. On Windows this is optional, while on Linux the installed HDF5 library will be used if present.\u003c/p\u003e\n\n\u003cp\u003eUse an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.\u003c/p\u003e\n\n\u003cp\u003eTested with 1.8.18 on windows, and default installation on RedHat 6.\u003c/p\u003e\n",
+                content:  "Source code The source code is hosted at GitHub\nIn a git enabled shell do: git clone https://github.com/OPM/ResInsight.git\nDependencies and Prerequisites Windows Compiler Visual Studio 2015 and later is supported.\nGCC Compiler GCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with\nsource /opt/rh/devtoolset-3/enable\r Qt5 Qt Qt5 version 5.6.0 or later is supported.\nOn some configurations you will be asked to specify the location of Qt5. Example for Windows : Qt5_DIR=d:\\Qt\\5.11.3\\msvc2017_64\\lib\\cmake\\Qt5\nQt4 (Deprecated) Qt4 is marked as deprecated and support for using Qt4 will soon be removed.\n\rQt Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.\nRESINSIGHT_BUILD_WITH_QT5=FALSE\nYou will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this : Qt-patch\nCMake CMake version 2.8 or later is supported.\nBuild Instructions The ResInsight build may be configured in different ways, with optional support for Octave plugins, ABAQUS ODB API, HDF5, Pyton, and OpenMP. This is configured using options in CMake.\nIf you check the button \u0026lsquo;Grouped\u0026rsquo; in the CMake GUI, the CMake variables are grouped by prefix. This makes it easier to see all of the options for ResInsight.\n Open the CMake GUI Set the path to the source code Set the path to the build directory Click Configure and select your preferred compiler Set the build options and click \u0026ldquo;Configure\u0026rdquo; again (see ResInsight specific options below) Click Generate to generate the makefiles or solution file and project files in the build directory Run the compiler using the generated makefiles or solution file/project files to build ResInsight  Windows ResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015/2017. Typical usage on Windows is to follow the build instructions above, and then open the generated solution file in Visual Studio to build the application.\nLinux Typical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:\n make make install  To build from the command line without using the CMake GUI:\n mkdir ResInsight_build cd ResInsight_build \u0026hellip; (set CMake options) \u0026hellip; cmake \u0026lt; path to ResInsight source folder \u0026gt; make make install  You will find the ResInsight binary under the Install directory in your build directory.\nCMake Options for ResInsight    CMake Name Default Description     RESINSIGHT_BUILD_DOCUMENTATION OFF Use Doxygen to create the HTML based API documentation. Doxygen must be properly installed.   RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python   RESINSIGHT_HDF5_DIR Blank Windows Only: Optional path to HDF5 libraries on Windows   RESINSIGHT_ODB_API_DIR Blank Optional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models   RESINSIGHT_USE_OPENMP ON Enable OpenMP parallellization in the code    Advanced Options To be able to modify Advanced Options from the CMake User Interface, tick the checkbox Advanced\n   CMake Name Default Description     RESINSIGHT_BUILD_WITH_QT5 ON If ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed)   RESINSIGHT_QT5_BUNDLE_LIBRARIES OFF Linux only: Include Qt5 libraries in the installation package   RESINSIGHT_BUNDLE_OPENSSL OFF Bundle the OpenSSL library DLLs in the Windows installer package   RESINSIGHT_ENABLE_COTIRE OFF Experimental speedup of compilation using cotire   RESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING ON Enable Souring features   RESINSIGHT_INCLUDE_APPFWK_TESTS OFF Include unit tests from thirdparty libraries AppFwk and VizFwk   RESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS OFF Include Application Code Unit Tests   RESINSIGHT_PRIVATE_INSTALL ON Linux only: Include libecl libraries in the installation package   RESINSIGHT_HDF5_BUNDLE_LIBRARIES OFF Linux only: Include HDF5 libraries in the installation package    Configuration parameters for Python (beta) These parameters are considered beta, and might change.\n   CMake Name Default Description     RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python   RESINSIGHT_GRPC_PYTHON_EXECUTABLE Blank Location of Python3 executable   RESINSIGHT_GRPC_INSTALL_PREFIX Blank Linux only : Installation prefix for gRPC    Optional Libraries and features Python (Beta) Scripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.\nThe current build instructions are specified in text files in the ResInsight repository.\n Grpc install instructions Helper script for Linux  See Python API  for how to use the Python library.\nOctave Octave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:\nOCTAVE_CONFIG_EXECUTABLE : d:\\octave\\Octave-4.0.0\\bin\\octave-config.exe\nIt is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for the Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like \u0026lsquo;Failed to find mkoctfile\u0026rsquo;. This will not break the build or compilation of ResInsight.\nResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.\nOctave Dependencies for Debian Based Distributions The following command line can be used as a starting point to install required libraries sudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev\nODB support ResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API from Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library files must be specified. Leaving this option blank gives a build without ODB support. ResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.\nHDF5 HDF5 is used to read SourSimRL result files. On Windows this is optional, while on Linux the installed HDF5 library will be used if present.\nUse an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.\nTested with 1.8.18 on windows, and default installation on RedHat 6.\n",
+                html:     "\u003ch2 id=\"source-code\"\u003eSource code\u003c/h2\u003e\n\u003cp\u003eThe source code is hosted at \u003ca href=\"https://github.com/opm/resinsight\"\u003eGitHub\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn a git enabled shell do: \u003ccode\u003egit clone https://github.com/OPM/ResInsight.git\u003c/code\u003e\u003c/p\u003e\n\u003ch2 id=\"dependencies-and-prerequisites\"\u003eDependencies and Prerequisites\u003c/h2\u003e\n\u003ch3 id=\"windows-compiler\"\u003eWindows Compiler\u003c/h3\u003e\n\u003cp\u003eVisual Studio 2015 and later is supported.\u003c/p\u003e\n\u003ch3 id=\"gcc-compiler\"\u003eGCC Compiler\u003c/h3\u003e\n\u003cp\u003eGCC version 4.9 or later is supported. On RedHat Linux 6 you need to install devtoolset-3, and enable it with\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esource /opt/rh/devtoolset-3/enable\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"qt5\"\u003eQt5\u003c/h3\u003e\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt\u003c/a\u003e Qt5 version 5.6.0 or later is supported.\u003c/p\u003e\n\u003cp\u003eOn some configurations you will be asked to specify the location of Qt5. Example for Windows :\n\u003ccode\u003eQt5_DIR=d:\\Qt\\5.11.3\\msvc2017_64\\lib\\cmake\\Qt5\u003c/code\u003e\u003c/p\u003e\n\u003ch4 id=\"qt4-deprecated\"\u003eQt4 (Deprecated)\u003c/h4\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eQt4 is marked as deprecated and support for using Qt4 will soon be removed.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt\u003c/a\u003e Qt4 version 4.6.2 or later is supported. On Windows we recommend Qt-4.8.7, while the default installation will do under Linux.\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eRESINSIGHT_BUILD_WITH_QT5=FALSE\u003c/code\u003e\u003c/p\u003e\n\u003cp\u003eYou will need to patch the Qt sources in order to make them build using Visual Studio 2015 using this : \n\u003ca href=\"https://github.com/appleseedhq/appleseed/wiki/Making-Qt-4.8.7-compile-with-Visual-Studio-2015\"\u003eQt-patch\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"cmake\"\u003eCMake\u003c/h3\u003e\n\u003cp\u003e\u003ca href=\"https://cmake.org/download/\"\u003eCMake\u003c/a\u003e version 2.8 or later is supported.\u003c/p\u003e\n\u003ch2 id=\"build-instructions\"\u003eBuild Instructions\u003c/h2\u003e\n\u003cp\u003eThe ResInsight build may be configured in different ways, with optional support for Octave plugins, \nABAQUS ODB API, HDF5, Pyton, and OpenMP. This is configured using options in CMake.\u003c/p\u003e\n\u003cp\u003eIf you check the button \u0026lsquo;Grouped\u0026rsquo; in the CMake GUI, the CMake variables are grouped by prefix. \nThis makes it easier to see all of the options for ResInsight.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOpen the CMake GUI\u003c/li\u003e\n\u003cli\u003eSet the path to the source code\u003c/li\u003e\n\u003cli\u003eSet the path to the build directory\u003c/li\u003e\n\u003cli\u003eClick \u003cstrong\u003eConfigure\u003c/strong\u003e and select your preferred compiler\u003c/li\u003e\n\u003cli\u003eSet the build options and click \u0026ldquo;Configure\u0026rdquo; again (see ResInsight specific options below)\u003c/li\u003e\n\u003cli\u003eClick \u003cstrong\u003eGenerate\u003c/strong\u003e to generate the makefiles or solution file and project files in the build directory\u003c/li\u003e\n\u003cli\u003eRun the compiler using the generated makefiles or solution file/project files to build ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"windows\"\u003eWindows\u003c/h3\u003e\n\u003cp\u003eResInsight has been verified to build and run on Windows 7/8/10 using Microsoft Visual Studio 2015/2017. \nTypical usage on Windows is to follow the build instructions above, and then open the generated \nsolution file in Visual Studio to build the application.\u003c/p\u003e\n\u003ch3 id=\"linux\"\u003eLinux\u003c/h3\u003e\n\u003cp\u003eTypical usage is to follow the build instructions above to build the makefiles. Then go to the build directory, and run:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003emake\u003c/li\u003e\n\u003cli\u003emake install\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eTo build from the command line without using the CMake GUI:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003emkdir ResInsight_build\u003c/li\u003e\n\u003cli\u003ecd ResInsight_build\u003c/li\u003e\n\u003cli\u003e\u0026hellip;\u003c/li\u003e\n\u003cli\u003e(set CMake options)\u003c/li\u003e\n\u003cli\u003e\u0026hellip;\u003c/li\u003e\n\u003cli\u003ecmake \u0026lt; path to ResInsight source folder \u0026gt;\u003c/li\u003e\n\u003cli\u003emake\u003c/li\u003e\n\u003cli\u003emake install\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eYou will find the ResInsight binary under the Install directory in your build directory.\u003c/p\u003e\n\u003ch3 id=\"cmake-options-for-resinsight\"\u003eCMake Options for ResInsight\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUILD_DOCUMENTATION\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eUse Doxygen to create the HTML based API documentation. Doxygen must be properly installed.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable gRPC scripting server. Required to be able to use ResInsight from Python\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_HDF5_DIR\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eWindows Only: Optional path to HDF5 libraries on Windows\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ODB_API_DIR\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eOptional path to the ABAQUS ODB API from Simulia. Needed for support of geomechanical models\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_USE_OPENMP\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eEnable OpenMP parallellization in the code\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"advanced-options\"\u003eAdvanced Options\u003c/h4\u003e\n\u003cp\u003eTo be able to modify \u003cstrong\u003eAdvanced Options\u003c/strong\u003e from the CMake User Interface, tick the checkbox \u003cstrong\u003eAdvanced\u003c/strong\u003e\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUILD_WITH_QT5\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eIf ON, use Qt5. If OFF, use Qt4 (Support for Qt4 is deprecated and will be removed)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_QT5_BUNDLE_LIBRARIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eLinux only: Include Qt5 libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_BUNDLE_OPENSSL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eBundle the OpenSSL library DLLs in the Windows installer package\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_COTIRE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eExperimental speedup of compilation using cotire\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_PROTOTYPE_FEATURE_SOURING\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eEnable Souring features\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_INCLUDE_APPFWK_TESTS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eInclude unit tests from thirdparty libraries AppFwk and VizFwk\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_INCLUDE_APPLICATION_UNIT_TESTS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eInclude Application Code Unit Tests\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_PRIVATE_INSTALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eLinux only: Include libecl libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_HDF5_BUNDLE_LIBRARIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eLinux only: Include HDF5 libraries in the installation package\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"configuration-parameters-for-python-beta\"\u003eConfiguration parameters for Python (beta)\u003c/h4\u003e\n\u003cp\u003eThese parameters are considered beta, and might change.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCMake Name\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable gRPC scripting server. Required to be able to use ResInsight from Python\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_PYTHON_EXECUTABLE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eLocation of Python3 executable\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_INSTALL_PREFIX\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBlank\u003c/td\u003e\n\u003ctd\u003eLinux only : Installation prefix for gRPC\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"optional-libraries-and-features\"\u003eOptional Libraries and features\u003c/h3\u003e\n\u003ch4 id=\"python-beta\"\u003ePython (Beta)\u003c/h4\u003e\n\u003cp\u003eScripting of ResInsight is possible from a Python library. The build configuration is a bit involved and is under review.\u003c/p\u003e\n\u003cp\u003eThe current build instructions are specified in text files in the ResInsight repository.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/OPM/ResInsight/blob/dev/GRPC_install_instructions.txt\"\u003eGrpc install instructions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/OPM/ResInsight/blob/dev/build_grpc_linux.sh\"\u003eHelper script for Linux\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"/scripting/pythonrips/\"\u003e Python API \u003c/a\u003e for how to use the Python library.\u003c/p\u003e\n\u003ch4 id=\"octave\"\u003eOctave\u003c/h4\u003e\n\u003cp\u003eOctave is now detected searching the file system. If Octave is not detected, the following file path variable must be defined:\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eOCTAVE_CONFIG_EXECUTABLE : d:\\octave\\Octave-4.0.0\\bin\\octave-config.exe\u003c/code\u003e\u003c/p\u003e\n\u003cp\u003eIt is possible to build ResInsight without compiling the Octave plugins. This can be done by specifying blank for \nthe Octave CMake options. The Octave plugin module will not be built, and CMake will show warnings like \u0026lsquo;Failed to find mkoctfile\u0026rsquo;. \nThis will not break the build or compilation of ResInsight.\u003c/p\u003e\n\u003cp\u003eResInsight has been verified to build and run with Octave versions 3.4.3, 3.8.1, and 4.0.0 on RedHat linux, and 4.0.0 on Windows.\u003c/p\u003e\n\u003ch5 id=\"octave-dependencies-for-debian-based-distributions\"\u003eOctave Dependencies for Debian Based Distributions\u003c/h5\u003e\n\u003cp\u003eThe following command line can be used as a starting point to install required libraries\n\u003ccode\u003esudo apt-get install git cmake build-essential octave liboctave-dev qtbase5-dev qtscript5-dev\u003c/code\u003e\u003c/p\u003e\n\u003ch4 id=\"odb-support\"\u003eODB support\u003c/h4\u003e\n\u003cp\u003eResInsight can be built with support for ABAQUS ODB files. This requires an installation of the ABAQUS ODB API \nfrom Simulia on the build computer. The path to the ABAQUS ODB API folder containing header files and library \nfiles must be specified. Leaving this option blank gives a build without ODB support. \nResInsight has been built and tested with ABAQUS ODB API version 6.14-3 on Windows 7/8/10 and RedHat Linux 6.\u003c/p\u003e\n\u003ch4 id=\"hdf5\"\u003eHDF5\u003c/h4\u003e\n\u003cp\u003eHDF5 is used to read SourSimRL result files. On Windows this is optional, while on Linux the installed HDF5 library will be used if present.\u003c/p\u003e\n\u003cp\u003eUse an advanced flag RESINSIGHT_HDF5_BUNDLE_LIBRARIES to include HDF5 libraries in the installation package.\u003c/p\u003e\n\u003cp\u003eTested with 1.8.18 on windows, and default installation on RedHat 6.\u003c/p\u003e\n",
                 url:      "/getting-started/download-and-install/buildinstructions/"
             };
         
@@ -2046,8 +2079,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/commandfile/"] = {
                 title:    "Command File",
-                content:  " The command file interface allows a sequence of specified commands to be run in order from the command line. The interface is used by supplying the command file as a command line parameter. Once the command file is finished executing, ResInsight will exit.\nIt is possible to use these commands directly from a Python script. For further details see Python Documentation\nCommand List Case Control Commands  openProject closeProject setStartDir loadCase createGridCaseGroup createStatisticsCase replaceCase replaceSourceCases  Export Commands  setExportFolder exportMultiCaseSnapshots exportSnapshots exportProperty exportPropertyInViews exportWellPathCompletions exportSimWellFractureCompletions exportMsw exportWellPaths exportVisibleCells exportFlowCharacteristics  Other Commands  runOctaveScript setMainWindowSize computeCaseGroupStatistics setTimeStep scaleFractureTemplate setFractureContainment createMultipleFractures createLgrForCompletions createSaturationPressurePlots  Syntax The command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.\nThe line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.\nAs an example; openProject(path=\u0026quot;/path/to/ResInsightProject.rsp\u0026quot;) will execute the command openProject with the parameter path. path is a string, see Types for a list of all types a parameter can have.\nNot all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.\nCommand file examples are displayed in sections like this.  Types There are different types of parameters that can be supplied.\n   Type Input Example     Integer Number 5   Double Decimal number 3.14   String Sequence of characters contained in quotes (\u0026quot;\u0026quot;)1 \u0026rdquo;/path/to/file\u0026rdquo;   Enum Choice of a set of given options ALL   Boolean true or false true   List Multiple choices of another type, written within square brackets ([]) separated by a comma (,) [1, 2, 3]    1 The backslash (\\) character is used as an escape character within strings, so to use a quote within a string, use \u0026quot;escape \\\u0026quot; with \\\u0026quot;\u0026quot;. To input a literal backslash character, use \u0026quot;\\\\\u0026quot;.\nCase Control Commands openProject Opens a ResInsight project file.\n   Parameter Description Type Required     path File path to the project file String \u0026#10004;    openProject(path=\u0026quot;/home/user/ResInsightProject.rsp\u0026quot;)  closeProject Closes the current open project.\ncloseProject()  setStartDir Set startup directory.\n   Parameter Description Type Required     path Path to directory to use as startup directory String \u0026#10004;    setStartDir(path=\u0026quot;/home/user\u0026quot;)  loadCase Import Eclipse case from file.\n   Parameter Description Type Required     path File path to the case to load String \u0026#10004;    loadCase(path=\u0026quot;/home/user/reservoir.EGRID\u0026quot;)  createGridCaseGroup Create a Grid Case Group from a list of files.\n   Parameter Description Type Required     casePaths List of Paths to Case Files String \u0026#10004;    createStatisticsCase Create a Statistics Case in a Grid Case Group.\n   Parameter Description Type Required     caseGroupId ID to the Case Group Integer \u0026#10004;    createGridCaseGroup(path=[\u0026quot;/home/user/reservoir.EGRID\u0026quot;, \u0026quot;/home/user/other_reservoir.EGRID\u0026quot;]) createStatisticsCase(caseGroupId=0)  replaceCase Replaces a case in the current project with the specified new case.\nopenProject must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use replaceSourceCases.\n   Parameter Description Type Required     newGridFile File path to the new grid file to replace with String \u0026#10004;   caseId ID of the case to replace. Defaults to first case Integer     replaceCase(newGridFile=\u0026quot;/home/user/otherReservoir.EGRID\u0026quot;, caseId=4)  replaceSourceCases Replaces multiple source cases in the current project.\nopenProject must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.\n   Parameter Description Type Required     gridListFile File path to file containing list of cases to replace with String \u0026#10004;   caseGroupId ID of group to replace cases in. Defaults to first group Integer     replaceSourceCases(gridListFile=\u0026quot;C:/resinsight/replacement_files.txt\u0026quot;)  Export Commands exportMultiCaseSnapshots Replaces the first case in the current project with each case in the given file and saves snapshots of all views.\nopenProject must be called before this command to set which project file is to be used when replacing cases.\nFolder to output snapshots should be set using setExportFolder with SNAPSHOTS type.\n   Parameter Description Type Required     gridListFile File path to file containing list of cases to create snapshots of String \u0026#10004;    exportMultiCaseSnapshots(gridListFile=\u0026quot;C:\\\\resinsight\\\\replacement_files.txt\u0026quot;)  exportSnapshots Export snapshots of specified type.\nFolder to output snapshots should be set using setExportFolder with SNAPSHOTS type.\n   Parameter Description Type Required     type Type of snapshots to export. Choices: ALL, VIEWS, PLOTS. Defaults to ALL Enum    prefix Exported file name prefix. Defaults to no prefix String    caseId ID of case for export, defaults to -1 meaning all cases Integer     exportSnapshots(type=PLOTS)  exportProperty Exports property values for all cells in the grid to file in Eclipse format.\n   Parameter Description Type Required     caseId ID of case for export Integer \u0026#10004;   timeStep The time step index for export Integer \u0026#10004;   property Name of property to export String \u0026#10004;   eclipseKeyword Eclipse keyword used as text in export header. Defaults to the value of property parameter String    undefinedValue Value to use for undefined values. Defaults to 0.0 Double    exportFile Filename for export. Defaults to the value of property parameter String     exportProperty(caseId=1, timeStep=4, property=\u0026quot;SOIL\u0026quot;)  exportPropertyInViews Exports property values for all cells in the grid to file in Eclipse format. Use specified cell result in view to define the export property. One file per view will be exported.\n   Parameter Description Type Required     caseId ID of case to export property from Integer \u0026#10004;   viewNames Name of views to export from. If not specified, all views are exported List of String    undefinedValue Value to use for undefined values. Defaults to 0.0 Double     exportPropertyInViews(caseId=1) exportPropertyInViews(caseId=1, viewNames=[\u0026quot;view A\u0026quot;, \u0026quot;view 4\u0026quot;])  exportWellPathCompletions Export well path completions.\n   Parameter Description Type Required     caseId ID of case to export well paths for Integer \u0026#10004;   timeStep The time step to export completions for Integer \u0026#10004;   wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    fileSplit How the files are split. Choices: UNIFIED_FILE, SPLIT_ON_WELL, SPLIT_ON_WELL_AND_COMPLETION_TYPE. Defaults to SPLIT_ON_WELL_AND_COMPLETION_TYPE Enum    compdatExport Chose whether transmissibilities are exported. Choices: TRANSMISSIBILITIES, WPIMULT_AND_DEFAULT_CONNECTION_FACTORS. Defaults to TRANSMISSIBILITIES Enum    includePerforations Whether main bore perforations should be included. Defaults to true Boolean    includeFishbones Whether fishbones should be included. Defaults to true Boolean    excludeMainBoreForFishbones Whether main bore completions should be excluded for cells with fishbones. Defaults to false Boolean    combinationMode Combination mode. Choices: INDIVIDUALLY, COMBINED. Defaults to INDIVIDUALLY Enum     exportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)  exportSimWellFractureCompletions Export fracture completions for simulation wells.\n   Parameter Description Type Required     caseId ID of case to export simulation well fracture completions for Integer \u0026#10004;   viewName The name of the view to export simulation well fracture completions for. Since view names are not unique, all views sharing the given name will be used String \u0026#10004;   timeStep The time step to export completions for Integer \u0026#10004;   simulationWellNames Names of simulation wells to export for. Defaults to all checked wells. If a list of names are provided, those wells are included even if unchecked List of String    fileSplit How the files are split. Choices: UNIFIED_FILE, SPLIT_ON_WELL, SPLIT_ON_WELL_AND_COMPLETION_TYPE. Defaults to UNIFIED_FILE Enum    compdatExport Chose whether transmissibilities are exported. Choices: TRANSMISSIBILITIES, WPIMULT_AND_DEFAULT_CONNECTION_FACTORS. Defaults to TRANSMISSIBILITIES Enum     exportSimWellFractureCompletions(caseId=3, viewName=\u0026quot;View 2\u0026quot;, timeStep=5)  exportMsw Export multi-segment wells.\n   Parameter Description Type Required     caseId ID of case to export well paths for Integer \u0026#10004;   wellPath Name of well path to export well segments for String \u0026#10004;    exportMsw(caseId=1, wellPath=\u0026quot;MainWell\u0026quot;)  exportWellPaths Export well paths.\n   Parameter Description Type Required     wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    mdStepSize Spacing (measured depth) between each sample along the well path. Default to 5.0 Double     exportWellPaths(wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], mdStepSize=1.5)  exportVisibleCells Export visible cells\n   Parameter Description Type Required     caseId ID of case to export cells for Integer \u0026#10004;   viewName Name of the view associated with the specified case Double \u0026#10004;   exportKeyword The keyword to export. Choices: FLUXNUM or MULTNUM. Default: FLUXNUM Enum    visibleActiveCellsValue Value to use for visible active cells. Default: 1 Integer    hiddenActiveCellsValue Value to use for hidden active cells. Default: 0 Integer    inactiveCellsValue Value to use for inactive cells. Default: 0 Integer     exporVisibleCells(caseId=0, viewName=\u0026quot;View 1\u0026quot;, exportKeyword=MULTNUM)  exportFlowCharacteristics Export Flow Characteristics data to text file in CSV format\n   Parameter Description Type Required     caseId ID of case Integer \u0026#10004;   timeSteps Time step indices List of Integer \u0026#10004;   injectors Injector names List of Strings    producers Producer names List of Strings    fileName Export file name Integer    minimumCommunication Minimum Communication, defaults to 0.0 Integer    aquiferCellThreshold Aquifer Cell Threshold, defaults to 0.1 Integer     exportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[\u0026quot;INJA\u0026quot;, \u0026quot;INJB\u0026quot;], producers=[\u0026quot;PROD_F\u0026quot;], fileName=\u0026quot;myData.csv\u0026quot;)  setExportFolder Set the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.\n   Parameter Description Type Required     type Type of export folder to set. Choices: COMPLETIONS, SNAPSHOTS, PROPERTIES, STATISTICS Enum \u0026#10004;   path Directory to export the given type to String \u0026#10004;   createFolder If true, create the folder when required. Default false. Boolean     setExportFolder(type=SNAPSHOTS, path=\u0026quot;/home/user/snapshots\u0026quot;)  Other runOctaveScript Execute an Octave script.\n   Parameter Description Type Required     path Path to the octave script to execute Integer \u0026#10004;   caseIds The cases to run the octave script on. Defaults to running the script without a specified case List of Integer     runOctaveScript(path=\u0026quot;/home/user/octave/something.m\u0026quot;, caseIds=[1,2,6])  setMainWindowSize Resize the main window to the specified size.\n   Parameter Description Type Required     width The width to set for the main window Integer \u0026#10004;   height The height to set for the main window Integer \u0026#10004;    setMainWindowSize(width=1920, height=1200)  computeCaseGroupStatistics Compute statistics for statistics cases.\n   Parameter Description Type Required     caseIds IDs of statistics cases to compute. Default is all statistics cases List of Integer     computeCaseGroupStatistics(caseIds=[5]) computeCaseGroupStatistics(caseIds=[2,4,8])  setTimeStep Set the time step for a given case. The time step is used for all views on the case.\n   Parameter Description Type Required     caseId ID of case to set time step for Integer \u0026#10004;   timeStep Index of time step to switch to Integer \u0026#10004;    setTimeStep(caseId=1, timeStep=8)  scaleFractureTemplate Scale fracture template parameters.\n   Parameter Description Type Required     id ID of fracture template Integer \u0026#10004;   halfLength Half Length scale factor Double    height Height scale factor Double    dFactor D-factor scale factor Double    conductivity Conductivity scale factor Double     scaleFractureTemplate(id=1, width=2, height=1.5)  setFractureContainment Set fracture template containment parameters.\n   Parameter Description Type Required     id ID of fracture template Integer \u0026#10004;   topLayer Top layer containment Integer \u0026#10004;   baseLayer Base layer containment Integer \u0026#10004;    setFractureContainment(id=1, topLayer=2, baseLayer=7)  createMultipleFractures Create multiple fractures on one or more well paths.\n   Parameter Description Type Required     caseId Case ID Integer \u0026#10004;   templateId Fracture template id Integer \u0026#10004;   wellPathNames Well path names. Default: All well paths List of Strings    minDistFromWellTd Min distance from well path tip. Default: 100.0 m Double    maxFracturesPerWell Max fractures per well. Default: 100 Integer    topLayer Top K layer. Default: Top layer from current model Integer    baseLayer Base K layer. Default: Bottom layer from current model Integer    spacing Distance between fractures. Default: 300.0 m Double    action How to handle existing fractures. Choices: APPEND_FRACTURES, REPLACE_FRACTURES. The replace option will delete all existing fractures before adding new ones. Default: APPEND_FRACTURES Enum     createMultipleFractures(caseId=0, templateId=1, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], action=REPLACE_FRACTURES)  createLgrForCompletions Create temporary LGRs for completions on the selected well paths. The splitType parameter controls which main grid cells to split into LGRs. The LGR_PER_CELL option splits only those main grid cells that intersect with a completion. The LGR_PER_COMPLETION option splits all main grid cells that are located within an IJK bounding box covering all intersected cells for each completion. The LGR_PER_WELL works like the previous option, but the bounding box covers intersected cells for all completions on a well path.\n   Parameter Description Type Required     caseId ID of case to create LGRs for Integer \u0026#10004;   timeStep The time step to create LGRs for Integer \u0026#10004;   wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    refinementI Size of the LGR along the I axis, in each main grid cell. Integer \u0026#10004;   refinementJ Size of the LGR along the J axis, in each main grid cell. Integer \u0026#10004;   refinementK Size of the LGR along the K axis, in each main grid cell. Integer \u0026#10004;   splitType How to split the LGRs. Options: LGR_PER_CELL, LGR_PER_COMPLETION, LGR_PER_WELL. Default option is LGR_PER_COMPLETION Enum     createLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)  createSaturationPressurePlots Create saturation pressure plots for the specified cases.\n   Parameter Description Type Required     caseIds IDs of cases to create plots for. Default is all cases List of Integer     createSaturationPressurePlots(caseIds=[0])  ",
-                html:     "\n\n\u003cp\u003eThe command file interface allows a sequence of specified commands to be run in order from the command line.\nThe interface is used by supplying the command file as a \u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\u003c/a\u003e.\nOnce the command file is finished executing, ResInsight will exit.\u003c/p\u003e\n\n\u003cp\u003eIt is possible to use these commands directly from a Python script. For further details see \u003ca href=\"/scripting/pythonrips/#commands-module\"\u003ePython Documentation\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"command-list\"\u003eCommand List\u003c/h2\u003e\n\n\u003ch4 id=\"case-control-commands\"\u003eCase Control Commands\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#openproject\"\u003eopenProject\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#closeproject\"\u003ecloseProject\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setstartdir\"\u003esetStartDir\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#loadcase\"\u003eloadCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#creategridcasegroup\"\u003ecreateGridCaseGroup\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createstatisticscase\"\u003ecreateStatisticsCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#replacecase\"\u003ereplaceCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#replacesourcecases\"\u003ereplaceSourceCases\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-commands\"\u003eExport Commands\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#setexportfolder\"\u003esetExportFolder\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportmulticasesnapshots\"\u003eexportMultiCaseSnapshots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportsnapshots\"\u003eexportSnapshots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportproperty\"\u003eexportProperty\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportpropertyinviews\"\u003eexportPropertyInViews\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportwellpathcompletions\"\u003eexportWellPathCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportsimwellfracturecompletions\"\u003eexportSimWellFractureCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportmsw\"\u003eexportMsw\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportwellpaths\"\u003eexportWellPaths\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportvisiblecells\"\u003eexportVisibleCells\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportflowcharacteristics\"\u003eexportFlowCharacteristics\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"other-commands\"\u003eOther Commands\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#runoctavescript\"\u003erunOctaveScript\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setmainwindowsize\"\u003esetMainWindowSize\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#computecasegroupstatistics\"\u003ecomputeCaseGroupStatistics\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#settimestep\"\u003esetTimeStep\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#scalefracturetemplate\"\u003escaleFractureTemplate\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setfracturecontainment\"\u003esetFractureContainment\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createmultiplefractures\"\u003ecreateMultipleFractures\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createlgrforcompletions\"\u003ecreateLgrForCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createSaturationPressurePlots\"\u003ecreateSaturationPressurePlots\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"syntax\"\u003eSyntax\u003c/h2\u003e\n\n\u003cp\u003eThe command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.\u003c/p\u003e\n\n\u003cp\u003eThe line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.\u003c/p\u003e\n\n\u003cp\u003eAs an example; \u003ccode\u003eopenProject(path=\u0026quot;/path/to/ResInsightProject.rsp\u0026quot;)\u003c/code\u003e will execute the command \u003ccode\u003eopenProject\u003c/code\u003e with the parameter \u003ccode\u003epath\u003c/code\u003e. \u003ccode\u003epath\u003c/code\u003e is a string, see \u003ca href=\"#types\"\u003eTypes\u003c/a\u003e for a list of all types a parameter can have.\u003c/p\u003e\n\n\u003cp\u003eNot all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eCommand file examples are displayed in sections like this.\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"types\"\u003eTypes\u003c/h3\u003e\n\n\u003cp\u003eThere are different types of parameters that can be supplied.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eInput\u003c/th\u003e\n\u003cth\u003eExample\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003eNumber\u003c/td\u003e\n\u003ctd\u003e5\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003eDecimal number\u003c/td\u003e\n\u003ctd\u003e3.14\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003eSequence of characters contained in quotes (\u003ccode\u003e\u0026quot;\u0026quot;\u003c/code\u003e)\u003csup\u003e1\u003c/sup\u003e\u003c/td\u003e\n\u003ctd\u003e\u0026rdquo;/path/to/file\u0026rdquo;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003eChoice of a set of given options\u003c/td\u003e\n\u003ctd\u003eALL\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003ccode\u003etrue\u003c/code\u003e or \u003ccode\u003efalse\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003etrue\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003ctd\u003eMultiple choices of another type, written within square brackets (\u003ccode\u003e[]\u003c/code\u003e) separated by a comma (\u003ccode\u003e,\u003c/code\u003e)\u003c/td\u003e\n\u003ctd\u003e[1, 2, 3]\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003e\u003csup\u003e1\u003c/sup\u003e The backslash (\u003ccode\u003e\\\u003c/code\u003e) character is used as an escape character within strings, so to use a quote within a string, use \u003ccode\u003e\u0026quot;escape \\\u0026quot; with \\\u0026quot;\u0026quot;\u003c/code\u003e. To input a literal backslash character, use \u003ccode\u003e\u0026quot;\\\\\u0026quot;\u003c/code\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"case-control-commands-1\"\u003eCase Control Commands\u003c/h2\u003e\n\n\u003ch3 id=\"openproject\"\u003eopenProject\u003c/h3\u003e\n\n\u003cp\u003eOpens a ResInsight project file.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eFile path to the project file\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eopenProject(path=\u0026quot;/home/user/ResInsightProject.rsp\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"closeproject\"\u003ecloseProject\u003c/h3\u003e\n\n\u003cp\u003eCloses the current open project.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003ecloseProject()\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"setstartdir\"\u003esetStartDir\u003c/h3\u003e\n\n\u003cp\u003eSet startup directory.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to directory to use as startup directory\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003esetStartDir(path=\u0026quot;/home/user\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"loadcase\"\u003eloadCase\u003c/h3\u003e\n\n\u003cp\u003eImport Eclipse case from file.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eFile path to the case to load\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eloadCase(path=\u0026quot;/home/user/reservoir.EGRID\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"creategridcasegroup\"\u003ecreateGridCaseGroup\u003c/h3\u003e\n\n\u003cp\u003eCreate a Grid Case Group from a list of files.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecasePaths\u003c/td\u003e\n\u003ctd\u003eList of Paths to Case Files\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"createstatisticscase\"\u003ecreateStatisticsCase\u003c/h3\u003e\n\n\u003cp\u003eCreate a Statistics Case in a Grid Case Group.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseGroupId\u003c/td\u003e\n\u003ctd\u003eID to the Case Group\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ecreateGridCaseGroup(path=[\u0026quot;/home/user/reservoir.EGRID\u0026quot;, \u0026quot;/home/user/other_reservoir.EGRID\u0026quot;])\ncreateStatisticsCase(caseGroupId=0)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"replacecase\"\u003ereplaceCase\u003c/h3\u003e\n\n\u003cp\u003eReplaces a case in the current project with the specified new case.\u003c/p\u003e\n\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use \u003ccode\u003ereplaceSourceCases\u003c/code\u003e.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003enewGridFile\u003c/td\u003e\n\u003ctd\u003eFile path to the new grid file to replace with\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of the case to replace. Defaults to first case\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ereplaceCase(newGridFile=\u0026quot;/home/user/otherReservoir.EGRID\u0026quot;, caseId=4)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"replacesourcecases\"\u003ereplaceSourceCases\u003c/h3\u003e\n\n\u003cp\u003eReplaces multiple source cases in the current project.\u003c/p\u003e\n\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egridListFile\u003c/td\u003e\n\u003ctd\u003eFile path to file containing list of cases to replace with\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecaseGroupId\u003c/td\u003e\n\u003ctd\u003eID of group to replace cases in. Defaults to first group\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ereplaceSourceCases(gridListFile=\u0026quot;C:/resinsight/replacement_files.txt\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch2 id=\"export-commands-1\"\u003eExport Commands\u003c/h2\u003e\n\n\u003ch3 id=\"exportmulticasesnapshots\"\u003eexportMultiCaseSnapshots\u003c/h3\u003e\n\n\u003cp\u003eReplaces the first case in the current project with each case in the given file and saves snapshots of all views.\u003c/p\u003e\n\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases.\u003c/p\u003e\n\n\u003cp\u003eFolder to output snapshots should be set using \u003ccode\u003esetExportFolder\u003c/code\u003e with \u003ccode\u003eSNAPSHOTS\u003c/code\u003e type.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egridListFile\u003c/td\u003e\n\u003ctd\u003eFile path to file containing list of cases to create snapshots of\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportMultiCaseSnapshots(gridListFile=\u0026quot;C:\\\\resinsight\\\\replacement_files.txt\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportsnapshots\"\u003eexportSnapshots\u003c/h3\u003e\n\n\u003cp\u003eExport snapshots of specified type.\u003c/p\u003e\n\n\u003cp\u003eFolder to output snapshots should be set using \u003ccode\u003esetExportFolder\u003c/code\u003e with \u003ccode\u003eSNAPSHOTS\u003c/code\u003e type.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etype\u003c/td\u003e\n\u003ctd\u003eType of snapshots to export. Choices: \u003ccode\u003eALL\u003c/code\u003e, \u003ccode\u003eVIEWS\u003c/code\u003e, \u003ccode\u003ePLOTS\u003c/code\u003e. Defaults to \u003ccode\u003eALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eprefix\u003c/td\u003e\n\u003ctd\u003eExported file name prefix. Defaults to no prefix\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case for export, defaults to -1 meaning all cases\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportSnapshots(type=PLOTS)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportproperty\"\u003eexportProperty\u003c/h3\u003e\n\n\u003cp\u003eExports property values for all cells in the grid to file in Eclipse format.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case for export\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step index for export\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eproperty\u003c/td\u003e\n\u003ctd\u003eName of property to export\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eeclipseKeyword\u003c/td\u003e\n\u003ctd\u003eEclipse keyword used as text in export header. Defaults to the value of \u003ccode\u003eproperty\u003c/code\u003e parameter\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eundefinedValue\u003c/td\u003e\n\u003ctd\u003eValue to use for undefined values. Defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eexportFile\u003c/td\u003e\n\u003ctd\u003eFilename for export. Defaults to the value of \u003ccode\u003eproperty\u003c/code\u003e parameter\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportProperty(caseId=1, timeStep=4, property=\u0026quot;SOIL\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportpropertyinviews\"\u003eexportPropertyInViews\u003c/h3\u003e\n\n\u003cp\u003eExports property values for all cells in the grid to file in Eclipse format. Use specified cell result in view to define the export property. One file per view will be exported.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export property from\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eviewNames\u003c/td\u003e\n\u003ctd\u003eName of views to export from. If not specified, all views are exported\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eundefinedValue\u003c/td\u003e\n\u003ctd\u003eValue to use for undefined values. Defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportPropertyInViews(caseId=1)\n\nexportPropertyInViews(caseId=1, viewNames=[\u0026quot;view A\u0026quot;, \u0026quot;view 4\u0026quot;])\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportwellpathcompletions\"\u003eexportWellPathCompletions\u003c/h3\u003e\n\n\u003cp\u003eExport well path completions.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export well paths for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to export completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efileSplit\u003c/td\u003e\n\u003ctd\u003eHow the files are split. Choices: \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e. Defaults to \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecompdatExport\u003c/td\u003e\n\u003ctd\u003eChose whether transmissibilities are exported. Choices: \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e, \u003ccode\u003eWPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u003c/code\u003e. Defaults to \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eincludePerforations\u003c/td\u003e\n\u003ctd\u003eWhether main bore perforations should be included. Defaults to \u003ccode\u003etrue\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eincludeFishbones\u003c/td\u003e\n\u003ctd\u003eWhether fishbones should be included. Defaults to \u003ccode\u003etrue\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eexcludeMainBoreForFishbones\u003c/td\u003e\n\u003ctd\u003eWhether main bore completions should be excluded for cells with fishbones. Defaults to \u003ccode\u003efalse\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecombinationMode\u003c/td\u003e\n\u003ctd\u003eCombination mode. Choices: \u003ccode\u003eINDIVIDUALLY\u003c/code\u003e, \u003ccode\u003eCOMBINED\u003c/code\u003e. Defaults to \u003ccode\u003eINDIVIDUALLY\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportsimwellfracturecompletions\"\u003eexportSimWellFractureCompletions\u003c/h3\u003e\n\n\u003cp\u003eExport fracture completions for simulation wells.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export simulation well fracture completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eviewName\u003c/td\u003e\n\u003ctd\u003eThe name of the view to export simulation well fracture completions for. Since view names are not unique, all views sharing the given name will be used\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to export completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esimulationWellNames\u003c/td\u003e\n\u003ctd\u003eNames of simulation wells to export for. Defaults to all checked wells. If a list of names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efileSplit\u003c/td\u003e\n\u003ctd\u003eHow the files are split. Choices: \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e. Defaults to \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecompdatExport\u003c/td\u003e\n\u003ctd\u003eChose whether transmissibilities are exported. Choices: \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e, \u003ccode\u003eWPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u003c/code\u003e. Defaults to \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportSimWellFractureCompletions(caseId=3, viewName=\u0026quot;View 2\u0026quot;, timeStep=5)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportmsw\"\u003eexportMsw\u003c/h3\u003e\n\n\u003cp\u003eExport multi-segment wells.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export well paths for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewellPath\u003c/td\u003e\n\u003ctd\u003eName of well path to export well segments for\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportMsw(caseId=1, wellPath=\u0026quot;MainWell\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportwellpaths\"\u003eexportWellPaths\u003c/h3\u003e\n\n\u003cp\u003eExport well paths.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emdStepSize\u003c/td\u003e\n\u003ctd\u003eSpacing (measured depth) between each sample along the well path. Default to 5.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportWellPaths(wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], mdStepSize=1.5)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportvisiblecells\"\u003eexportVisibleCells\u003c/h3\u003e\n\n\u003cp\u003eExport visible cells\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export cells for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eviewName\u003c/td\u003e\n\u003ctd\u003eName of the view associated with the specified case\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eexportKeyword\u003c/td\u003e\n\u003ctd\u003eThe keyword to export. Choices: \u003ccode\u003eFLUXNUM\u003c/code\u003e or \u003ccode\u003eMULTNUM\u003c/code\u003e. Default: \u003ccode\u003eFLUXNUM\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003evisibleActiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for visible active cells. Default: 1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ehiddenActiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for hidden active cells. Default: 0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einactiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for inactive cells. Default: 0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexporVisibleCells(caseId=0, viewName=\u0026quot;View 1\u0026quot;, exportKeyword=MULTNUM)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"exportflowcharacteristics\"\u003eexportFlowCharacteristics\u003c/h3\u003e\n\n\u003cp\u003eExport Flow Characteristics data to text file in CSV format\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeSteps\u003c/td\u003e\n\u003ctd\u003eTime step indices\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eInjector names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eProducer names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efileName\u003c/td\u003e\n\u003ctd\u003eExport file name\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eminimumCommunication\u003c/td\u003e\n\u003ctd\u003eMinimum Communication, defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eaquiferCellThreshold\u003c/td\u003e\n\u003ctd\u003eAquifer Cell Threshold, defaults to 0.1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003eexportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[\u0026quot;INJA\u0026quot;, \u0026quot;INJB\u0026quot;], producers=[\u0026quot;PROD_F\u0026quot;], fileName=\u0026quot;myData.csv\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"setexportfolder\"\u003esetExportFolder\u003c/h3\u003e\n\n\u003cp\u003eSet the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etype\u003c/td\u003e\n\u003ctd\u003eType of export folder to set. Choices: \u003ccode\u003eCOMPLETIONS\u003c/code\u003e, \u003ccode\u003eSNAPSHOTS\u003c/code\u003e, \u003ccode\u003ePROPERTIES\u003c/code\u003e, \u003ccode\u003eSTATISTICS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eDirectory to export the given type to\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecreateFolder\u003c/td\u003e\n\u003ctd\u003eIf true, create the folder when required. Default false.\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003esetExportFolder(type=SNAPSHOTS, path=\u0026quot;/home/user/snapshots\u0026quot;)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch2 id=\"other\"\u003eOther\u003c/h2\u003e\n\n\u003ch3 id=\"runoctavescript\"\u003erunOctaveScript\u003c/h3\u003e\n\n\u003cp\u003eExecute an Octave script.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to the octave script to execute\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eThe cases to run the octave script on. Defaults to running the script without a specified case\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003erunOctaveScript(path=\u0026quot;/home/user/octave/something.m\u0026quot;, caseIds=[1,2,6])\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"setmainwindowsize\"\u003esetMainWindowSize\u003c/h3\u003e\n\n\u003cp\u003eResize the main window to the specified size.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eThe width to set for the main window\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eThe height to set for the main window\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003esetMainWindowSize(width=1920, height=1200)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"computecasegroupstatistics\"\u003ecomputeCaseGroupStatistics\u003c/h3\u003e\n\n\u003cp\u003eCompute statistics for statistics cases.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eIDs of statistics cases to compute. Default is all statistics cases\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ecomputeCaseGroupStatistics(caseIds=[5])\n\ncomputeCaseGroupStatistics(caseIds=[2,4,8])\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"settimestep\"\u003esetTimeStep\u003c/h3\u003e\n\n\u003cp\u003eSet the time step for a given case. The time step is used for all views on the case.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to set time step for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eIndex of time step to switch to\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003esetTimeStep(caseId=1, timeStep=8)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"scalefracturetemplate\"\u003escaleFractureTemplate\u003c/h3\u003e\n\n\u003cp\u003eScale fracture template parameters.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eid\u003c/td\u003e\n\u003ctd\u003eID of fracture template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ehalfLength\u003c/td\u003e\n\u003ctd\u003eHalf Length scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edFactor\u003c/td\u003e\n\u003ctd\u003eD-factor scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003econductivity\u003c/td\u003e\n\u003ctd\u003eConductivity scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003escaleFractureTemplate(id=1, width=2, height=1.5)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"setfracturecontainment\"\u003esetFractureContainment\u003c/h3\u003e\n\n\u003cp\u003eSet fracture template containment parameters.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eid\u003c/td\u003e\n\u003ctd\u003eID of fracture template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etopLayer\u003c/td\u003e\n\u003ctd\u003eTop layer containment\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ebaseLayer\u003c/td\u003e\n\u003ctd\u003eBase layer containment\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003esetFractureContainment(id=1, topLayer=2, baseLayer=7)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"createmultiplefractures\"\u003ecreateMultipleFractures\u003c/h3\u003e\n\n\u003cp\u003eCreate multiple fractures on one or more well paths.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eCase ID\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etemplateId\u003c/td\u003e\n\u003ctd\u003eFracture template id\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eWell path names. Default: All well paths\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eminDistFromWellTd\u003c/td\u003e\n\u003ctd\u003eMin distance from well path tip. Default: 100.0 m\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emaxFracturesPerWell\u003c/td\u003e\n\u003ctd\u003eMax fractures per well. Default: 100\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etopLayer\u003c/td\u003e\n\u003ctd\u003eTop K layer. Default: Top layer from current model\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ebaseLayer\u003c/td\u003e\n\u003ctd\u003eBase K layer. Default: Bottom layer from current model\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003espacing\u003c/td\u003e\n\u003ctd\u003eDistance between fractures. Default: 300.0 m\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eaction\u003c/td\u003e\n\u003ctd\u003eHow to handle existing fractures. Choices: \u003ccode\u003eAPPEND_FRACTURES\u003c/code\u003e, \u003ccode\u003eREPLACE_FRACTURES\u003c/code\u003e. The replace option will delete all existing fractures before adding new ones. Default: \u003ccode\u003eAPPEND_FRACTURES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ecreateMultipleFractures(caseId=0, templateId=1, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], action=REPLACE_FRACTURES)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"createlgrforcompletions\"\u003ecreateLgrForCompletions\u003c/h3\u003e\n\n\u003cp\u003eCreate temporary LGRs for completions on the selected well paths. The splitType parameter controls which main grid cells to split into LGRs. The LGR_PER_CELL option splits only those main grid cells that intersect with a completion. The LGR_PER_COMPLETION option splits all main grid cells that are located within an IJK bounding box covering all intersected cells for each completion. The LGR_PER_WELL works like the previous option, but the bounding box covers intersected cells for all completions on a well path.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to create LGRs for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to create LGRs for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinementI\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the I axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinementJ\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the J axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinementK\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the K axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u0026#10004;\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esplitType\u003c/td\u003e\n\u003ctd\u003eHow to split the LGRs. Options: \u003ccode\u003eLGR_PER_CELL\u003c/code\u003e, \u003ccode\u003eLGR_PER_COMPLETION\u003c/code\u003e, \u003ccode\u003eLGR_PER_WELL\u003c/code\u003e. Default option is \u003ccode\u003eLGR_PER_COMPLETION\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ecreateLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"createsaturationpressureplots\"\u003ecreateSaturationPressurePlots\u003c/h3\u003e\n\n\u003cp\u003eCreate saturation pressure plots for the specified cases.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eIDs of cases to create plots for. Default is all cases\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003ecreateSaturationPressurePlots(caseIds=[0])\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "The command file interface allows a sequence of specified commands to be run in order from the command line. The interface is used by supplying the command file as a command line parameter. Once the command file is finished executing, ResInsight will exit.\nIt is possible to use these commands directly from a Python script. For further details see Python Documentation\nCommand List Case Control Commands  openProject closeProject setStartDir loadCase createGridCaseGroup createStatisticsCase replaceCase replaceSourceCases  Export Commands  setExportFolder exportMultiCaseSnapshots exportSnapshots exportProperty exportPropertyInViews exportWellPathCompletions exportSimWellFractureCompletions exportMsw exportWellPaths exportVisibleCells exportFlowCharacteristics  Other Commands  runOctaveScript setMainWindowSize computeCaseGroupStatistics setTimeStep scaleFractureTemplate setFractureContainment createMultipleFractures createLgrForCompletions createSaturationPressurePlots  Syntax The command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.\nThe line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.\nAs an example; openProject(path=\u0026quot;/path/to/ResInsightProject.rsp\u0026quot;) will execute the command openProject with the parameter path. path is a string, see Types for a list of all types a parameter can have.\nNot all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.\nCommand file examples are displayed in sections like this.\rTypes There are different types of parameters that can be supplied.\n   Type Input Example     Integer Number 5   Double Decimal number 3.14   String Sequence of characters contained in quotes (\u0026quot;\u0026quot;)1 \u0026ldquo;/path/to/file\u0026rdquo;   Enum Choice of a set of given options ALL   Boolean true or false true   List Multiple choices of another type, written within square brackets ([]) separated by a comma (,) [1, 2, 3]    1The backslash (\\) character is used as an escape character within strings, so to use a quote within a string, use \u0026quot;escape \\\u0026quot; with \\\u0026quot;\u0026quot;. To input a literal backslash character, use \u0026quot;\\\\\u0026quot;.\nCase Control Commands openProject Opens a ResInsight project file.\n   Parameter Description Type Required     path File path to the project file String ✔    openProject(path=\u0026quot;/home/user/ResInsightProject.rsp\u0026quot;)\rcloseProject Closes the current open project.\ncloseProject()\rsetStartDir Set startup directory.\n   Parameter Description Type Required     path Path to directory to use as startup directory String ✔    setStartDir(path=\u0026quot;/home/user\u0026quot;)\rloadCase Import Eclipse case from file.\n   Parameter Description Type Required     path File path to the case to load String ✔    loadCase(path=\u0026quot;/home/user/reservoir.EGRID\u0026quot;)\rcreateGridCaseGroup Create a Grid Case Group from a list of files.\n   Parameter Description Type Required     casePaths List of Paths to Case Files String ✔    createStatisticsCase Create a Statistics Case in a Grid Case Group.\n   Parameter Description Type Required     caseGroupId ID to the Case Group Integer ✔    createGridCaseGroup(path=[\u0026quot;/home/user/reservoir.EGRID\u0026quot;, \u0026quot;/home/user/other_reservoir.EGRID\u0026quot;])\rcreateStatisticsCase(caseGroupId=0)\rreplaceCase Replaces a case in the current project with the specified new case.\nopenProject must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use replaceSourceCases.\n   Parameter Description Type Required     newGridFile File path to the new grid file to replace with String ✔   caseId ID of the case to replace. Defaults to first case Integer     replaceCase(newGridFile=\u0026quot;/home/user/otherReservoir.EGRID\u0026quot;, caseId=4)\rreplaceSourceCases Replaces multiple source cases in the current project.\nopenProject must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.\n   Parameter Description Type Required     gridListFile File path to file containing list of cases to replace with String ✔   caseGroupId ID of group to replace cases in. Defaults to first group Integer     replaceSourceCases(gridListFile=\u0026quot;C:/resinsight/replacement_files.txt\u0026quot;)\rExport Commands exportMultiCaseSnapshots Replaces the first case in the current project with each case in the given file and saves snapshots of all views.\nopenProject must be called before this command to set which project file is to be used when replacing cases.\nFolder to output snapshots should be set using setExportFolder with SNAPSHOTS type.\n   Parameter Description Type Required     gridListFile File path to file containing list of cases to create snapshots of String ✔    exportMultiCaseSnapshots(gridListFile=\u0026quot;C:\\\\resinsight\\\\replacement_files.txt\u0026quot;)\rexportSnapshots Export snapshots of specified type.\nFolder to output snapshots should be set using setExportFolder with SNAPSHOTS type.\n   Parameter Description Type Required     type Type of snapshots to export. Choices: ALL, VIEWS, PLOTS. Defaults to ALL Enum    prefix Exported file name prefix. Defaults to no prefix String    caseId ID of case for export, defaults to -1 meaning all cases Integer     exportSnapshots(type=PLOTS)\rexportProperty Exports property values for all cells in the grid to file in Eclipse format.\n   Parameter Description Type Required     caseId ID of case for export Integer ✔   timeStep The time step index for export Integer ✔   property Name of property to export String ✔   eclipseKeyword Eclipse keyword used as text in export header. Defaults to the value of property parameter String    undefinedValue Value to use for undefined values. Defaults to 0.0 Double    exportFile Filename for export. Defaults to the value of property parameter String     exportProperty(caseId=1, timeStep=4, property=\u0026quot;SOIL\u0026quot;)\rexportPropertyInViews Exports property values for all cells in the grid to file in Eclipse format. Use specified cell result in view to define the export property. One file per view will be exported.\n   Parameter Description Type Required     caseId ID of case to export property from Integer ✔   viewNames Name of views to export from. If not specified, all views are exported List of String    undefinedValue Value to use for undefined values. Defaults to 0.0 Double     exportPropertyInViews(caseId=1)\rexportPropertyInViews(caseId=1, viewNames=[\u0026quot;view A\u0026quot;, \u0026quot;view 4\u0026quot;])\rexportWellPathCompletions Export well path completions.\n   Parameter Description Type Required     caseId ID of case to export well paths for Integer ✔   timeStep The time step to export completions for Integer ✔   wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    fileSplit How the files are split. Choices: UNIFIED_FILE, SPLIT_ON_WELL, SPLIT_ON_WELL_AND_COMPLETION_TYPE. Defaults to SPLIT_ON_WELL_AND_COMPLETION_TYPE Enum    compdatExport Chose whether transmissibilities are exported. Choices: TRANSMISSIBILITIES, WPIMULT_AND_DEFAULT_CONNECTION_FACTORS. Defaults to TRANSMISSIBILITIES Enum    includePerforations Whether main bore perforations should be included. Defaults to true Boolean    includeFishbones Whether fishbones should be included. Defaults to true Boolean    excludeMainBoreForFishbones Whether main bore completions should be excluded for cells with fishbones. Defaults to false Boolean    combinationMode Combination mode. Choices: INDIVIDUALLY, COMBINED. Defaults to INDIVIDUALLY Enum     exportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)\rexportSimWellFractureCompletions Export fracture completions for simulation wells.\n   Parameter Description Type Required     caseId ID of case to export simulation well fracture completions for Integer ✔   viewName The name of the view to export simulation well fracture completions for. Since view names are not unique, all views sharing the given name will be used String ✔   timeStep The time step to export completions for Integer ✔   simulationWellNames Names of simulation wells to export for. Defaults to all checked wells. If a list of names are provided, those wells are included even if unchecked List of String    fileSplit How the files are split. Choices: UNIFIED_FILE, SPLIT_ON_WELL, SPLIT_ON_WELL_AND_COMPLETION_TYPE. Defaults to UNIFIED_FILE Enum    compdatExport Chose whether transmissibilities are exported. Choices: TRANSMISSIBILITIES, WPIMULT_AND_DEFAULT_CONNECTION_FACTORS. Defaults to TRANSMISSIBILITIES Enum     exportSimWellFractureCompletions(caseId=3, viewName=\u0026quot;View 2\u0026quot;, timeStep=5)\rexportMsw Export multi-segment wells.\n   Parameter Description Type Required     caseId ID of case to export well paths for Integer ✔   wellPath Name of well path to export well segments for String ✔    exportMsw(caseId=1, wellPath=\u0026quot;MainWell\u0026quot;)\rexportWellPaths Export well paths.\n   Parameter Description Type Required     wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    mdStepSize Spacing (measured depth) between each sample along the well path. Default to 5.0 Double     exportWellPaths(wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], mdStepSize=1.5)\rexportVisibleCells Export visible cells\n   Parameter Description Type Required     caseId ID of case to export cells for Integer ✔   viewName Name of the view associated with the specified case Double ✔   exportKeyword The keyword to export. Choices: FLUXNUM or MULTNUM. Default: FLUXNUM Enum    visibleActiveCellsValue Value to use for visible active cells. Default: 1 Integer    hiddenActiveCellsValue Value to use for hidden active cells. Default: 0 Integer    inactiveCellsValue Value to use for inactive cells. Default: 0 Integer     exporVisibleCells(caseId=0, viewName=\u0026quot;View 1\u0026quot;, exportKeyword=MULTNUM)\rexportFlowCharacteristics Export Flow Characteristics data to text file in CSV format\n   Parameter Description Type Required     caseId ID of case Integer ✔   timeSteps Time step indices List of Integer ✔   injectors Injector names List of Strings    producers Producer names List of Strings    fileName Export file name Integer    minimumCommunication Minimum Communication, defaults to 0.0 Integer    aquiferCellThreshold Aquifer Cell Threshold, defaults to 0.1 Integer     exportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[\u0026quot;INJA\u0026quot;, \u0026quot;INJB\u0026quot;], producers=[\u0026quot;PROD_F\u0026quot;], fileName=\u0026quot;myData.csv\u0026quot;)\rsetExportFolder Set the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.\n   Parameter Description Type Required     type Type of export folder to set. Choices: COMPLETIONS, SNAPSHOTS, PROPERTIES, STATISTICS Enum ✔   path Directory to export the given type to String ✔   createFolder If true, create the folder when required. Default false. Boolean     setExportFolder(type=SNAPSHOTS, path=\u0026quot;/home/user/snapshots\u0026quot;)\rOther runOctaveScript Execute an Octave script.\n   Parameter Description Type Required     path Path to the octave script to execute Integer ✔   caseIds The cases to run the octave script on. Defaults to running the script without a specified case List of Integer     runOctaveScript(path=\u0026quot;/home/user/octave/something.m\u0026quot;, caseIds=[1,2,6])\rsetMainWindowSize Resize the main window to the specified size.\n   Parameter Description Type Required     width The width to set for the main window Integer ✔   height The height to set for the main window Integer ✔    setMainWindowSize(width=1920, height=1200)\rcomputeCaseGroupStatistics Compute statistics for statistics cases.\n   Parameter Description Type Required     caseIds IDs of statistics cases to compute. Default is all statistics cases List of Integer     computeCaseGroupStatistics(caseIds=[5])\rcomputeCaseGroupStatistics(caseIds=[2,4,8])\rsetTimeStep Set the time step for a given case. The time step is used for all views on the case.\n   Parameter Description Type Required     caseId ID of case to set time step for Integer ✔   timeStep Index of time step to switch to Integer ✔    setTimeStep(caseId=1, timeStep=8)\rscaleFractureTemplate Scale fracture template parameters.\n   Parameter Description Type Required     id ID of fracture template Integer ✔   halfLength Half Length scale factor Double    height Height scale factor Double    dFactor D-factor scale factor Double    conductivity Conductivity scale factor Double     scaleFractureTemplate(id=1, width=2, height=1.5)\rsetFractureContainment Set fracture template containment parameters.\n   Parameter Description Type Required     id ID of fracture template Integer ✔   topLayer Top layer containment Integer ✔   baseLayer Base layer containment Integer ✔    setFractureContainment(id=1, topLayer=2, baseLayer=7)\rcreateMultipleFractures Create multiple fractures on one or more well paths.\n   Parameter Description Type Required     caseId Case ID Integer ✔   templateId Fracture template id Integer ✔   wellPathNames Well path names. Default: All well paths List of Strings    minDistFromWellTd Min distance from well path tip. Default: 100.0 m Double    maxFracturesPerWell Max fractures per well. Default: 100 Integer    topLayer Top K layer. Default: Top layer from current model Integer    baseLayer Base K layer. Default: Bottom layer from current model Integer    spacing Distance between fractures. Default: 300.0 m Double    action How to handle existing fractures. Choices: APPEND_FRACTURES, REPLACE_FRACTURES. The replace option will delete all existing fractures before adding new ones. Default: APPEND_FRACTURES Enum     createMultipleFractures(caseId=0, templateId=1, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], action=REPLACE_FRACTURES)\rcreateLgrForCompletions Create temporary LGRs for completions on the selected well paths. The splitType parameter controls which main grid cells to split into LGRs. The LGR_PER_CELL option splits only those main grid cells that intersect with a completion. The LGR_PER_COMPLETION option splits all main grid cells that are located within an IJK bounding box covering all intersected cells for each completion. The LGR_PER_WELL works like the previous option, but the bounding box covers intersected cells for all completions on a well path.\n   Parameter Description Type Required     caseId ID of case to create LGRs for Integer ✔   timeStep The time step to create LGRs for Integer ✔   wellPathNames Names of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked List of String    refinementI Size of the LGR along the I axis, in each main grid cell. Integer ✔   refinementJ Size of the LGR along the J axis, in each main grid cell. Integer ✔   refinementK Size of the LGR along the K axis, in each main grid cell. Integer ✔   splitType How to split the LGRs. Options: LGR_PER_CELL, LGR_PER_COMPLETION, LGR_PER_WELL. Default option is LGR_PER_COMPLETION Enum     createLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)\rcreateSaturationPressurePlots Create saturation pressure plots for the specified cases.\n   Parameter Description Type Required     caseIds IDs of cases to create plots for. Default is all cases List of Integer     createSaturationPressurePlots(caseIds=[0])\r",
+                html:     "\u003cp\u003eThe command file interface allows a sequence of specified commands to be run in order from the command line.\nThe interface is used by supplying the command file as a \u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\u003c/a\u003e.\nOnce the command file is finished executing, ResInsight will exit.\u003c/p\u003e\n\u003cp\u003eIt is possible to use these commands directly from a Python script. For further details see \u003ca href=\"/scripting/pythonrips/\"\u003ePython Documentation\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"command-list\"\u003eCommand List\u003c/h2\u003e\n\u003ch4 id=\"case-control-commands\"\u003eCase Control Commands\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#openproject\"\u003eopenProject\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#closeproject\"\u003ecloseProject\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setstartdir\"\u003esetStartDir\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#loadcase\"\u003eloadCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#creategridcasegroup\"\u003ecreateGridCaseGroup\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createstatisticscase\"\u003ecreateStatisticsCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#replacecase\"\u003ereplaceCase\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#replacesourcecases\"\u003ereplaceSourceCases\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export-commands\"\u003eExport Commands\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#setexportfolder\"\u003esetExportFolder\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportmulticasesnapshots\"\u003eexportMultiCaseSnapshots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportsnapshots\"\u003eexportSnapshots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportproperty\"\u003eexportProperty\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportpropertyinviews\"\u003eexportPropertyInViews\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportwellpathcompletions\"\u003eexportWellPathCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportsimwellfracturecompletions\"\u003eexportSimWellFractureCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportmsw\"\u003eexportMsw\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportwellpaths\"\u003eexportWellPaths\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportvisiblecells\"\u003eexportVisibleCells\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#exportflowcharacteristics\"\u003eexportFlowCharacteristics\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"other-commands\"\u003eOther Commands\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"#runoctavescript\"\u003erunOctaveScript\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setmainwindowsize\"\u003esetMainWindowSize\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#computecasegroupstatistics\"\u003ecomputeCaseGroupStatistics\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#settimestep\"\u003esetTimeStep\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#scalefracturetemplate\"\u003escaleFractureTemplate\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#setfracturecontainment\"\u003esetFractureContainment\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createmultiplefractures\"\u003ecreateMultipleFractures\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createlgrforcompletions\"\u003ecreateLgrForCompletions\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"#createSaturationPressurePlots\"\u003ecreateSaturationPressurePlots\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"syntax\"\u003eSyntax\u003c/h2\u003e\n\u003cp\u003eThe command file is comprised of a set of commands to be executed in order. Each command must begin on a separate line, i.e. there cannot be two commands on the same line.\u003c/p\u003e\n\u003cp\u003eThe line starts with the command name, followed by parenthesis. Within the parenthesis, parameters can be supplied. Each parameter must be named, followed by an equals sign and its value.\u003c/p\u003e\n\u003cp\u003eAs an example; \u003ccode\u003eopenProject(path=\u0026quot;/path/to/ResInsightProject.rsp\u0026quot;)\u003c/code\u003e will execute the command \u003ccode\u003eopenProject\u003c/code\u003e with the parameter \u003ccode\u003epath\u003c/code\u003e. \u003ccode\u003epath\u003c/code\u003e is a string, see \u003ca href=\"#types\"\u003eTypes\u003c/a\u003e for a list of all types a parameter can have.\u003c/p\u003e\n\u003cp\u003eNot all parameters are required, in which case they can be omitted and their value will be defaulted. The order of parameters does not matter.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eCommand file examples are displayed in sections like this.\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"types\"\u003eTypes\u003c/h3\u003e\n\u003cp\u003eThere are different types of parameters that can be supplied.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eInput\u003c/th\u003e\n\u003cth\u003eExample\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003eNumber\u003c/td\u003e\n\u003ctd\u003e5\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003eDecimal number\u003c/td\u003e\n\u003ctd\u003e3.14\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003eSequence of characters contained in quotes (\u003ccode\u003e\u0026quot;\u0026quot;\u003c/code\u003e)\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e\u003c/td\u003e\n\u003ctd\u003e\u0026ldquo;/path/to/file\u0026rdquo;\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003eChoice of a set of given options\u003c/td\u003e\n\u003ctd\u003eALL\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003ccode\u003etrue\u003c/code\u003e or \u003ccode\u003efalse\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003etrue\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003ctd\u003eMultiple choices of another type, written within square brackets (\u003ccode\u003e[]\u003c/code\u003e) separated by a comma (\u003ccode\u003e,\u003c/code\u003e)\u003c/td\u003e\n\u003ctd\u003e[1, 2, 3]\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003e\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e The backslash (\u003ccode\u003e\\\u003c/code\u003e) character is used as an escape character within strings, so to use a quote within a string, use \u003ccode\u003e\u0026quot;escape \\\u0026quot; with \\\u0026quot;\u0026quot;\u003c/code\u003e. To input a literal backslash character, use \u003ccode\u003e\u0026quot;\\\\\u0026quot;\u003c/code\u003e.\u003c/p\u003e\n\u003ch2 id=\"case-control-commands-1\"\u003eCase Control Commands\u003c/h2\u003e\n\u003ch3 id=\"openproject\"\u003eopenProject\u003c/h3\u003e\n\u003cp\u003eOpens a ResInsight project file.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eFile path to the project file\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eopenProject(path=\u0026quot;/home/user/ResInsightProject.rsp\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"closeproject\"\u003ecloseProject\u003c/h3\u003e\n\u003cp\u003eCloses the current open project.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ecloseProject()\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"setstartdir\"\u003esetStartDir\u003c/h3\u003e\n\u003cp\u003eSet startup directory.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to directory to use as startup directory\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003esetStartDir(path=\u0026quot;/home/user\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"loadcase\"\u003eloadCase\u003c/h3\u003e\n\u003cp\u003eImport Eclipse case from file.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eFile path to the case to load\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eloadCase(path=\u0026quot;/home/user/reservoir.EGRID\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"creategridcasegroup\"\u003ecreateGridCaseGroup\u003c/h3\u003e\n\u003cp\u003eCreate a Grid Case Group from a list of files.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecasePaths\u003c/td\u003e\n\u003ctd\u003eList of Paths to Case Files\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"createstatisticscase\"\u003ecreateStatisticsCase\u003c/h3\u003e\n\u003cp\u003eCreate a Statistics Case in a Grid Case Group.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseGroupId\u003c/td\u003e\n\u003ctd\u003eID to the Case Group\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ecreateGridCaseGroup(path=[\u0026quot;/home/user/reservoir.EGRID\u0026quot;, \u0026quot;/home/user/other_reservoir.EGRID\u0026quot;])\r\ncreateStatisticsCase(caseGroupId=0)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"replacecase\"\u003ereplaceCase\u003c/h3\u003e\n\u003cp\u003eReplaces a case in the current project with the specified new case.\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases. This command re-opens the project with the new case replaced. To replace more than one case at the same time, use \u003ccode\u003ereplaceSourceCases\u003c/code\u003e.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003enewGridFile\u003c/td\u003e\n\u003ctd\u003eFile path to the new grid file to replace with\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of the case to replace. Defaults to first case\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ereplaceCase(newGridFile=\u0026quot;/home/user/otherReservoir.EGRID\u0026quot;, caseId=4)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"replacesourcecases\"\u003ereplaceSourceCases\u003c/h3\u003e\n\u003cp\u003eReplaces multiple source cases in the current project.\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases. This command re-opens tje project with the cases replaced.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egridListFile\u003c/td\u003e\n\u003ctd\u003eFile path to file containing list of cases to replace with\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseGroupId\u003c/td\u003e\n\u003ctd\u003eID of group to replace cases in. Defaults to first group\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ereplaceSourceCases(gridListFile=\u0026quot;C:/resinsight/replacement_files.txt\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch2 id=\"export-commands-1\"\u003eExport Commands\u003c/h2\u003e\n\u003ch3 id=\"exportmulticasesnapshots\"\u003eexportMultiCaseSnapshots\u003c/h3\u003e\n\u003cp\u003eReplaces the first case in the current project with each case in the given file and saves snapshots of all views.\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eopenProject\u003c/code\u003e must be called before this command to set which project file is to be used when replacing cases.\u003c/p\u003e\n\u003cp\u003eFolder to output snapshots should be set using \u003ccode\u003esetExportFolder\u003c/code\u003e with \u003ccode\u003eSNAPSHOTS\u003c/code\u003e type.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egridListFile\u003c/td\u003e\n\u003ctd\u003eFile path to file containing list of cases to create snapshots of\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportMultiCaseSnapshots(gridListFile=\u0026quot;C:\\\\resinsight\\\\replacement_files.txt\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportsnapshots\"\u003eexportSnapshots\u003c/h3\u003e\n\u003cp\u003eExport snapshots of specified type.\u003c/p\u003e\n\u003cp\u003eFolder to output snapshots should be set using \u003ccode\u003esetExportFolder\u003c/code\u003e with \u003ccode\u003eSNAPSHOTS\u003c/code\u003e type.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etype\u003c/td\u003e\n\u003ctd\u003eType of snapshots to export. Choices: \u003ccode\u003eALL\u003c/code\u003e, \u003ccode\u003eVIEWS\u003c/code\u003e, \u003ccode\u003ePLOTS\u003c/code\u003e. Defaults to \u003ccode\u003eALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eprefix\u003c/td\u003e\n\u003ctd\u003eExported file name prefix. Defaults to no prefix\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case for export, defaults to -1 meaning all cases\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportSnapshots(type=PLOTS)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportproperty\"\u003eexportProperty\u003c/h3\u003e\n\u003cp\u003eExports property values for all cells in the grid to file in Eclipse format.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case for export\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step index for export\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eproperty\u003c/td\u003e\n\u003ctd\u003eName of property to export\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eeclipseKeyword\u003c/td\u003e\n\u003ctd\u003eEclipse keyword used as text in export header. Defaults to the value of \u003ccode\u003eproperty\u003c/code\u003e parameter\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eundefinedValue\u003c/td\u003e\n\u003ctd\u003eValue to use for undefined values. Defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eexportFile\u003c/td\u003e\n\u003ctd\u003eFilename for export. Defaults to the value of \u003ccode\u003eproperty\u003c/code\u003e parameter\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportProperty(caseId=1, timeStep=4, property=\u0026quot;SOIL\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportpropertyinviews\"\u003eexportPropertyInViews\u003c/h3\u003e\n\u003cp\u003eExports property values for all cells in the grid to file in Eclipse format. Use specified cell result in view to define the export property. One file per view will be exported.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export property from\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eviewNames\u003c/td\u003e\n\u003ctd\u003eName of views to export from. If not specified, all views are exported\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eundefinedValue\u003c/td\u003e\n\u003ctd\u003eValue to use for undefined values. Defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportPropertyInViews(caseId=1)\r\n\r\nexportPropertyInViews(caseId=1, viewNames=[\u0026quot;view A\u0026quot;, \u0026quot;view 4\u0026quot;])\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportwellpathcompletions\"\u003eexportWellPathCompletions\u003c/h3\u003e\n\u003cp\u003eExport well path completions.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export well paths for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to export completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efileSplit\u003c/td\u003e\n\u003ctd\u003eHow the files are split. Choices: \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e. Defaults to \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecompdatExport\u003c/td\u003e\n\u003ctd\u003eChose whether transmissibilities are exported. Choices: \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e, \u003ccode\u003eWPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u003c/code\u003e. Defaults to \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eincludePerforations\u003c/td\u003e\n\u003ctd\u003eWhether main bore perforations should be included. Defaults to \u003ccode\u003etrue\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eincludeFishbones\u003c/td\u003e\n\u003ctd\u003eWhether fishbones should be included. Defaults to \u003ccode\u003etrue\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eexcludeMainBoreForFishbones\u003c/td\u003e\n\u003ctd\u003eWhether main bore completions should be excluded for cells with fishbones. Defaults to \u003ccode\u003efalse\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecombinationMode\u003c/td\u003e\n\u003ctd\u003eCombination mode. Choices: \u003ccode\u003eINDIVIDUALLY\u003c/code\u003e, \u003ccode\u003eCOMBINED\u003c/code\u003e. Defaults to \u003ccode\u003eINDIVIDUALLY\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportsimwellfracturecompletions\"\u003eexportSimWellFractureCompletions\u003c/h3\u003e\n\u003cp\u003eExport fracture completions for simulation wells.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export simulation well fracture completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eviewName\u003c/td\u003e\n\u003ctd\u003eThe name of the view to export simulation well fracture completions for. Since view names are not unique, all views sharing the given name will be used\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to export completions for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esimulationWellNames\u003c/td\u003e\n\u003ctd\u003eNames of simulation wells to export for. Defaults to all checked wells. If a list of names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efileSplit\u003c/td\u003e\n\u003ctd\u003eHow the files are split. Choices: \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL\u003c/code\u003e, \u003ccode\u003eSPLIT_ON_WELL_AND_COMPLETION_TYPE\u003c/code\u003e. Defaults to \u003ccode\u003eUNIFIED_FILE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecompdatExport\u003c/td\u003e\n\u003ctd\u003eChose whether transmissibilities are exported. Choices: \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e, \u003ccode\u003eWPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u003c/code\u003e. Defaults to \u003ccode\u003eTRANSMISSIBILITIES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportSimWellFractureCompletions(caseId=3, viewName=\u0026quot;View 2\u0026quot;, timeStep=5)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportmsw\"\u003eexportMsw\u003c/h3\u003e\n\u003cp\u003eExport multi-segment wells.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export well paths for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPath\u003c/td\u003e\n\u003ctd\u003eName of well path to export well segments for\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportMsw(caseId=1, wellPath=\u0026quot;MainWell\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportwellpaths\"\u003eexportWellPaths\u003c/h3\u003e\n\u003cp\u003eExport well paths.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emdStepSize\u003c/td\u003e\n\u003ctd\u003eSpacing (measured depth) between each sample along the well path. Default to 5.0\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportWellPaths(wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], mdStepSize=1.5)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportvisiblecells\"\u003eexportVisibleCells\u003c/h3\u003e\n\u003cp\u003eExport visible cells\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to export cells for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eviewName\u003c/td\u003e\n\u003ctd\u003eName of the view associated with the specified case\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eexportKeyword\u003c/td\u003e\n\u003ctd\u003eThe keyword to export. Choices: \u003ccode\u003eFLUXNUM\u003c/code\u003e or \u003ccode\u003eMULTNUM\u003c/code\u003e. Default: \u003ccode\u003eFLUXNUM\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003evisibleActiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for visible active cells. Default: 1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ehiddenActiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for hidden active cells. Default: 0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einactiveCellsValue\u003c/td\u003e\n\u003ctd\u003eValue to use for inactive cells. Default: 0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexporVisibleCells(caseId=0, viewName=\u0026quot;View 1\u0026quot;, exportKeyword=MULTNUM)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"exportflowcharacteristics\"\u003eexportFlowCharacteristics\u003c/h3\u003e\n\u003cp\u003eExport Flow Characteristics data to text file in CSV format\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeSteps\u003c/td\u003e\n\u003ctd\u003eTime step indices\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eInjector names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eProducer names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efileName\u003c/td\u003e\n\u003ctd\u003eExport file name\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eminimumCommunication\u003c/td\u003e\n\u003ctd\u003eMinimum Communication, defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eaquiferCellThreshold\u003c/td\u003e\n\u003ctd\u003eAquifer Cell Threshold, defaults to 0.1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003eexportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[\u0026quot;INJA\u0026quot;, \u0026quot;INJB\u0026quot;], producers=[\u0026quot;PROD_F\u0026quot;], fileName=\u0026quot;myData.csv\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"setexportfolder\"\u003esetExportFolder\u003c/h3\u003e\n\u003cp\u003eSet the folder to export different types of data to. Set this before attempting to export data to ensure it is exported to desired location.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etype\u003c/td\u003e\n\u003ctd\u003eType of export folder to set. Choices: \u003ccode\u003eCOMPLETIONS\u003c/code\u003e, \u003ccode\u003eSNAPSHOTS\u003c/code\u003e, \u003ccode\u003ePROPERTIES\u003c/code\u003e, \u003ccode\u003eSTATISTICS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003eDirectory to export the given type to\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecreateFolder\u003c/td\u003e\n\u003ctd\u003eIf true, create the folder when required. Default false.\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003esetExportFolder(type=SNAPSHOTS, path=\u0026quot;/home/user/snapshots\u0026quot;)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch2 id=\"other\"\u003eOther\u003c/h2\u003e\n\u003ch3 id=\"runoctavescript\"\u003erunOctaveScript\u003c/h3\u003e\n\u003cp\u003eExecute an Octave script.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to the octave script to execute\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eThe cases to run the octave script on. Defaults to running the script without a specified case\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003erunOctaveScript(path=\u0026quot;/home/user/octave/something.m\u0026quot;, caseIds=[1,2,6])\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"setmainwindowsize\"\u003esetMainWindowSize\u003c/h3\u003e\n\u003cp\u003eResize the main window to the specified size.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eThe width to set for the main window\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eThe height to set for the main window\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003esetMainWindowSize(width=1920, height=1200)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"computecasegroupstatistics\"\u003ecomputeCaseGroupStatistics\u003c/h3\u003e\n\u003cp\u003eCompute statistics for statistics cases.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eIDs of statistics cases to compute. Default is all statistics cases\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ecomputeCaseGroupStatistics(caseIds=[5])\r\n\r\ncomputeCaseGroupStatistics(caseIds=[2,4,8])\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"settimestep\"\u003esetTimeStep\u003c/h3\u003e\n\u003cp\u003eSet the time step for a given case. The time step is used for all views on the case.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to set time step for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eIndex of time step to switch to\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003esetTimeStep(caseId=1, timeStep=8)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"scalefracturetemplate\"\u003escaleFractureTemplate\u003c/h3\u003e\n\u003cp\u003eScale fracture template parameters.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eid\u003c/td\u003e\n\u003ctd\u003eID of fracture template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ehalfLength\u003c/td\u003e\n\u003ctd\u003eHalf Length scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edFactor\u003c/td\u003e\n\u003ctd\u003eD-factor scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003econductivity\u003c/td\u003e\n\u003ctd\u003eConductivity scale factor\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003escaleFractureTemplate(id=1, width=2, height=1.5)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"setfracturecontainment\"\u003esetFractureContainment\u003c/h3\u003e\n\u003cp\u003eSet fracture template containment parameters.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eid\u003c/td\u003e\n\u003ctd\u003eID of fracture template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etopLayer\u003c/td\u003e\n\u003ctd\u003eTop layer containment\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ebaseLayer\u003c/td\u003e\n\u003ctd\u003eBase layer containment\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003esetFractureContainment(id=1, topLayer=2, baseLayer=7)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"createmultiplefractures\"\u003ecreateMultipleFractures\u003c/h3\u003e\n\u003cp\u003eCreate multiple fractures on one or more well paths.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eCase ID\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etemplateId\u003c/td\u003e\n\u003ctd\u003eFracture template id\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eWell path names. Default: All well paths\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eminDistFromWellTd\u003c/td\u003e\n\u003ctd\u003eMin distance from well path tip. Default: 100.0 m\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emaxFracturesPerWell\u003c/td\u003e\n\u003ctd\u003eMax fractures per well. Default: 100\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etopLayer\u003c/td\u003e\n\u003ctd\u003eTop K layer. Default: Top layer from current model\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ebaseLayer\u003c/td\u003e\n\u003ctd\u003eBase K layer. Default: Bottom layer from current model\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003espacing\u003c/td\u003e\n\u003ctd\u003eDistance between fractures. Default: 300.0 m\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eaction\u003c/td\u003e\n\u003ctd\u003eHow to handle existing fractures. Choices: \u003ccode\u003eAPPEND_FRACTURES\u003c/code\u003e, \u003ccode\u003eREPLACE_FRACTURES\u003c/code\u003e. The replace option will delete all existing fractures before adding new ones. Default: \u003ccode\u003eAPPEND_FRACTURES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ecreateMultipleFractures(caseId=0, templateId=1, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], action=REPLACE_FRACTURES)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"createlgrforcompletions\"\u003ecreateLgrForCompletions\u003c/h3\u003e\n\u003cp\u003eCreate temporary LGRs for completions on the selected well paths. The splitType parameter controls which main grid cells to split into LGRs. The LGR_PER_CELL option splits only those main grid cells that intersect with a completion. The LGR_PER_COMPLETION option splits all main grid cells that are located within an IJK bounding box covering all intersected cells for each completion. The LGR_PER_WELL works like the previous option, but the bounding box covers intersected cells for all completions on a well path.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseId\u003c/td\u003e\n\u003ctd\u003eID of case to create LGRs for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etimeStep\u003c/td\u003e\n\u003ctd\u003eThe time step to create LGRs for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewellPathNames\u003c/td\u003e\n\u003ctd\u003eNames of well paths to export for. Defaults to all checked wells. If a list of well names are provided, those wells are included even if unchecked\u003c/td\u003e\n\u003ctd\u003eList of String\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinementI\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the I axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinementJ\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the J axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinementK\u003c/td\u003e\n\u003ctd\u003eSize of the LGR along the K axis, in each main grid cell.\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003ctd\u003e✔\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esplitType\u003c/td\u003e\n\u003ctd\u003eHow to split the LGRs. Options: \u003ccode\u003eLGR_PER_CELL\u003c/code\u003e, \u003ccode\u003eLGR_PER_COMPLETION\u003c/code\u003e, \u003ccode\u003eLGR_PER_WELL\u003c/code\u003e. Default option is \u003ccode\u003eLGR_PER_COMPLETION\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eEnum\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ecreateLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[\u0026quot;B-1H\u0026quot;, \u0026quot;B-2H\u0026quot;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"createsaturationpressureplots\"\u003ecreateSaturationPressurePlots\u003c/h3\u003e\n\u003cp\u003eCreate saturation pressure plots for the specified cases.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eRequired\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ecaseIds\u003c/td\u003e\n\u003ctd\u003eIDs of cases to create plots for. Default is all cases\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003ecreateSaturationPressurePlots(caseIds=[0])\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/scripting/commandfile/"
             };
         
@@ -2055,8 +2088,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/createnewwellpaths/"] = {
                 title:    "Create Well Paths",
-                content:  " ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self created well path will behave the same way as an ordinary imported well path.\nTo create a well path:\n Right click Wells in the project tree Select Create Well Path in the right-click menu. A new well node and a well targets node are created. Click in the 3D view on locations where the well path will pass (targets). Note. A 3D object must be hit when clicking. Clicking in thin air will not work. When finished placing targets, click on \u0026ldquo;Stop Picking Targets\u0026rdquo; in the property editor  Well targets property editor fields\n UTM Reference Point - Reference point. Defaults to the first target point clicked MDRKB at First Target - Define MD (referenced to Rotary Kelly Bushing) at first target point. Applies to well path export only. Well Targets: List of targets. Will have pink background when in picking state.  Point - Target position relative to reference point DL in - Dog leg inwards. Unit: Degrees/30m DL out - Dog leg outwards. Unit: Degrees/30m Dir - Check box for overriding well path auto calculated directions Azi (deg) - Azimuth. Y axis is 0 degrees Inc (deg) - Inclination. Z axis is 0 degrees   A self created well path may be edited by either editing coordinates in the property editor or clicking and dragging targets in the 3D view.\nClicking and dragging the blue part of a target, it can be moved along the Z axis only. Clicking and dragging the magenta part of a target, it can be moved freely around.\nWell Plan A well plan can be displayed by selecting Show Well Plan from the right-click menu of a generated well path.\n-- MDRKB CL Inc Azi TVDMSL NS EW Dogleg Build Turn 0.00000 0.00000 91.23218 67.46458 2560.64104 7320830.60875 456093.37763 0.00000 0.00000 0.00000 109.69761 109.69761 91.23218 67.46458 2558.28210 7320872.64113 456194.67560 0.00000 0.00000 0.00000 383.74602 274.04841 90.01335 94.84447 2555.24550 7320914.37090 456462.87518 3.00000 -0.13343 2.99727 518.95310 135.20708 88.73259 106.92696 2556.73062 7320888.88803 456595.39303 2.69569 -0.28418 2.68089 597.83872 78.88561 88.73259 106.92696 2558.47547 7320865.92593 456670.84259 0.00000 0.00000 0.00000 730.04479 132.20607 90.46303 138.71821 2559.42803 7320795.18191 456780.51358 7.22424 0.39267 7.21402 1087.97847 357.93368 92.23380 -164.19586 2550.23230 7320460.45997 456856.25443 4.78528 0.14842 -25.38856  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathCreation.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight lets the user create new/custom well paths by clicking in the 3D view. A self created well path will behave the same way as an ordinary imported well path.\u003c/p\u003e\n\n\u003cp\u003eTo create a well path:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eRight click \u003cstrong\u003eWells\u003c/strong\u003e in the project tree\u003c/li\u003e\n\u003cli\u003eSelect \u003cstrong\u003eCreate Well Path\u003c/strong\u003e in the right-click menu. A new well node and a well targets node are created.\u003c/li\u003e\n\u003cli\u003eClick in the 3D view on locations where the well path will pass (targets). Note. A 3D object must be hit when clicking. Clicking in thin air will not work.\u003c/li\u003e\n\u003cli\u003eWhen finished placing targets, click on \u0026ldquo;Stop Picking Targets\u0026rdquo; in the property editor\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargetsTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargetsPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWell targets property editor fields\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUTM Reference Point\u003c/strong\u003e - Reference point. Defaults to the first target point clicked\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMDRKB at First Target\u003c/strong\u003e - Define MD (referenced to Rotary Kelly Bushing) at first target point. Applies to well path export only.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Targets:\u003c/strong\u003e List of targets. Will have pink background when in picking state.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePoint\u003c/strong\u003e - Target position relative to reference point\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL in\u003c/strong\u003e - Dog leg inwards. Unit: Degrees/30m\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL out\u003c/strong\u003e - Dog leg outwards. Unit: Degrees/30m\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDir\u003c/strong\u003e - Check box for overriding well path auto calculated directions\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzi (deg)\u003c/strong\u003e - Azimuth. Y axis is 0 degrees\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInc (deg)\u003c/strong\u003e - Inclination. Z axis is 0 degrees\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eA self created well path may be edited by either editing coordinates in the property editor or clicking and dragging targets in the 3D view.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargets.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eClicking and dragging the blue part of a target, it can be moved along the Z axis only. Clicking and dragging the magenta part of a target, it can be moved freely around.\u003c/p\u003e\n\n\u003ch3 id=\"well-plan\"\u003eWell Plan\u003c/h3\u003e\n\n\u003cp\u003eA well plan can be displayed by selecting \u003cstrong\u003eShow Well Plan\u003c/strong\u003e from the right-click menu of a generated well path.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e-- MDRKB          CL            Inc          Azi            TVDMSL         NS                EW               Dogleg      Build        Turn          \n0.00000        0.00000       91.23218     67.46458       2560.64104     7320830.60875     456093.37763     0.00000     0.00000      0.00000       \n109.69761      109.69761     91.23218     67.46458       2558.28210     7320872.64113     456194.67560     0.00000     0.00000      0.00000       \n383.74602      274.04841     90.01335     94.84447       2555.24550     7320914.37090     456462.87518     3.00000     -0.13343     2.99727       \n518.95310      135.20708     88.73259     106.92696      2556.73062     7320888.88803     456595.39303     2.69569     -0.28418     2.68089       \n597.83872      78.88561      88.73259     106.92696      2558.47547     7320865.92593     456670.84259     0.00000     0.00000      0.00000       \n730.04479      132.20607     90.46303     138.71821      2559.42803     7320795.18191     456780.51358     7.22424     0.39267      7.21402       \n1087.97847     357.93368     92.23380     -164.19586     2550.23230     7320460.45997     456856.25443     4.78528     0.14842      -25.38856     \n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self created well path will behave the same way as an ordinary imported well path.\nTo create a well path:\n Right click Wells in the project tree Select Create Well Path in the right-click menu. A new well node and a well targets node are created. Click in the 3D view on locations where the well path will pass (targets). Note. A 3D object must be hit when clicking. Clicking in thin air will not work. When finished placing targets, click on \u0026ldquo;Stop Picking Targets\u0026rdquo; in the property editor  Well targets property editor fields\n UTM Reference Point - Reference point. Defaults to the first target point clicked MDRKB at First Target - Define MD (referenced to Rotary Kelly Bushing) at first target point. Applies to well path export only. Well Targets: List of targets. Will have pink background when in picking state.  Point - Target position relative to reference point DL in - Dog leg inwards. Unit: Degrees/30m DL out - Dog leg outwards. Unit: Degrees/30m Dir - Check box for overriding well path auto calculated directions Azi (deg) - Azimuth. Y axis is 0 degrees Inc (deg) - Inclination. Z axis is 0 degrees    A self created well path may be edited by either editing coordinates in the property editor or clicking and dragging targets in the 3D view.\nClicking and dragging the blue part of a target, it can be moved along the Z axis only. Clicking and dragging the magenta part of a target, it can be moved freely around.\nWell Plan A well plan can be displayed by selecting Show Well Plan from the right-click menu of a generated well path.\n-- MDRKB CL Inc Azi TVDMSL NS EW Dogleg Build Turn 0.00000 0.00000 91.23218 67.46458 2560.64104 7320830.60875 456093.37763 0.00000 0.00000 0.00000 109.69761 109.69761 91.23218 67.46458 2558.28210 7320872.64113 456194.67560 0.00000 0.00000 0.00000 383.74602 274.04841 90.01335 94.84447 2555.24550 7320914.37090 456462.87518 3.00000 -0.13343 2.99727 518.95310 135.20708 88.73259 106.92696 2556.73062 7320888.88803 456595.39303 2.69569 -0.28418 2.68089 597.83872 78.88561 88.73259 106.92696 2558.47547 7320865.92593 456670.84259 0.00000 0.00000 0.00000 730.04479 132.20607 90.46303 138.71821 2559.42803 7320795.18191 456780.51358 7.22424 0.39267 7.21402 1087.97847 357.93368 92.23380 -164.19586 2550.23230 7320460.45997 456856.25443 4.78528 0.14842 -25.38856 ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPathCreation.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight lets the user create new/custom well paths by clicking in the 3D view. A self created well path will behave the same way as an ordinary imported well path.\u003c/p\u003e\n\u003cp\u003eTo create a well path:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eRight click \u003cstrong\u003eWells\u003c/strong\u003e in the project tree\u003c/li\u003e\n\u003cli\u003eSelect \u003cstrong\u003eCreate Well Path\u003c/strong\u003e in the right-click menu. A new well node and a well targets node are created.\u003c/li\u003e\n\u003cli\u003eClick in the 3D view on locations where the well path will pass (targets). Note. A 3D object must be hit when clicking. Clicking in thin air will not work.\u003c/li\u003e\n\u003cli\u003eWhen finished placing targets, click on \u0026ldquo;Stop Picking Targets\u0026rdquo; in the property editor\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargetsTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargetsPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWell targets property editor fields\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUTM Reference Point\u003c/strong\u003e - Reference point. Defaults to the first target point clicked\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMDRKB at First Target\u003c/strong\u003e - Define MD (referenced to Rotary Kelly Bushing) at first target point. Applies to well path export only.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Targets:\u003c/strong\u003e List of targets. Will have pink background when in picking state.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePoint\u003c/strong\u003e - Target position relative to reference point\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL in\u003c/strong\u003e - Dog leg inwards. Unit: Degrees/30m\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL out\u003c/strong\u003e - Dog leg outwards. Unit: Degrees/30m\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDir\u003c/strong\u003e - Check box for overriding well path auto calculated directions\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzi (deg)\u003c/strong\u003e - Azimuth. Y axis is 0 degrees\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInc (deg)\u003c/strong\u003e - Inclination. Z axis is 0 degrees\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eA self created well path may be edited by either editing coordinates in the property editor or clicking and dragging targets in the 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellTargets.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eClicking and dragging the blue part of a target, it can be moved along the Z axis only. Clicking and dragging the magenta part of a target, it can be moved freely around.\u003c/p\u003e\n\u003ch3 id=\"well-plan\"\u003eWell Plan\u003c/h3\u003e\n\u003cp\u003eA well plan can be displayed by selecting \u003cstrong\u003eShow Well Plan\u003c/strong\u003e from the right-click menu of a generated well path.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e-- MDRKB          CL            Inc          Azi            TVDMSL         NS                EW               Dogleg      Build        Turn          \r\n0.00000        0.00000       91.23218     67.46458       2560.64104     7320830.60875     456093.37763     0.00000     0.00000      0.00000       \r\n109.69761      109.69761     91.23218     67.46458       2558.28210     7320872.64113     456194.67560     0.00000     0.00000      0.00000       \r\n383.74602      274.04841     90.01335     94.84447       2555.24550     7320914.37090     456462.87518     3.00000     -0.13343     2.99727       \r\n518.95310      135.20708     88.73259     106.92696      2556.73062     7320888.88803     456595.39303     2.69569     -0.28418     2.68089       \r\n597.83872      78.88561      88.73259     106.92696      2558.47547     7320865.92593     456670.84259     0.00000     0.00000      0.00000       \r\n730.04479      132.20607     90.46303     138.71821      2559.42803     7320795.18191     456780.51358     7.22424     0.39267      7.21402       \r\n1087.97847     357.93368     92.23380     -164.19586     2550.23230     7320460.45997     456856.25443     4.78528     0.14842      -25.38856     \r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/wells-and-completions/createnewwellpaths/"
             };
         
@@ -2064,8 +2097,8 @@ if (!doNotTrack) {
          
             window.store["/import/elementpropertytable/"] = {
                 title:    "Element Property Table",
-                content:  " Element property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.\nTo view the data as a Color Result select the Result Position: Element ( See Geomechanical Results )\nA couple of property names are recognized and treated specially:\n MODULUS \u0026ndash; Scaled by 1.0e-9 and shown as \u0026ldquo;Yong\u0026rsquo;s Modulus\u0026rdquo; in the user interface RATIO \u0026ndash; Shown as \u0026ldquo;Poisson\u0026rsquo;s Ratio\u0026rdquo; in the user interface  File Format A couple of examples on the file format are shown below.\nResInsight searches for the first line containing *Distribution Table, then splits the following line by ,. These entries describes the expected property values to be found in the file.\nResInsight then searches for the data block by ignoring lines\n starting with * and , does not have the expected column count when splitting the line by ,  When the datablock is found, the part of the line before . is stripped away, and first column is expected to be element ID\n** ELASTIC SETTING FOR EACH ELEMENT *Distribution Table, name=RSV_Res-1_Elastic_Table MODULUS, RATIO *Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table ** Description: Element-by-Element Elastic properties , 2. Res-1.210, 11198814808.2538, 0.19041 Res-1.209, 11207002032.1436, 0.19063 Res-1.208, 11222989223.0933, 0.19104 Res-1.207, 11202549454.349, 0.19051  ** DENSITY SETTING FOR EACH ELEMENT *Distribution Table, name=RSV_Res-1_Density_Table Density *Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table ** Description: Element-by-Element Densities , 1. Res-1.210, 2500 Res-1.209, 2500 Res-1.208, 2500 Res-1.207, 2500  ",
-                html:     "\n\n\u003cp\u003eElement property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.\u003c/p\u003e\n\n\u003cp\u003eTo view the data as a \u003cstrong\u003eColor Result\u003c/strong\u003e select the \u003cstrong\u003eResult Position\u003c/strong\u003e: \u003cstrong\u003e\u003cem\u003eElement\u003c/em\u003e\u003c/strong\u003e ( See \u003ca href=\"/3d-main-window/cellresults/#geomechanical-results\"\u003eGeomechanical Results\u003c/a\u003e )\u003c/p\u003e\n\n\u003cp\u003eA couple of property names are recognized and treated specially:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eMODULUS \u0026ndash; Scaled by 1.0e-9 and shown as \u0026ldquo;Yong\u0026rsquo;s Modulus\u0026rdquo; in the user interface\u003c/li\u003e\n\u003cli\u003eRATIO \u0026ndash; Shown as \u0026ldquo;Poisson\u0026rsquo;s Ratio\u0026rdquo; in the user interface\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"file-format\"\u003eFile Format\u003c/h3\u003e\n\n\u003cp\u003eA couple of examples on the file format are shown below.\u003c/p\u003e\n\n\u003cp\u003eResInsight searches for the first line containing \u003ccode\u003e*Distribution Table\u003c/code\u003e, then splits the following line by \u003ccode\u003e,\u003c/code\u003e. These entries describes the expected property values to be found in the file.\u003c/p\u003e\n\n\u003cp\u003eResInsight then searches for the data block by ignoring lines\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003estarting with \u003ccode\u003e*\u003c/code\u003e and \u003ccode\u003e,\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003edoes not have the expected column count when splitting the line by \u003ccode\u003e,\u003c/code\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen the datablock is found, the part of the line before \u003ccode\u003e.\u003c/code\u003e is stripped away, and first column is expected to be element ID\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e** ELASTIC SETTING FOR EACH ELEMENT\n*Distribution Table, name=RSV_Res-1_Elastic_Table\nMODULUS, RATIO\n*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table\n** Description: Element-by-Element Elastic properties\n,     2.\nRes-1.210, 11198814808.2538, 0.19041\nRes-1.209, 11207002032.1436, 0.19063\nRes-1.208, 11222989223.0933, 0.19104\nRes-1.207, 11202549454.349, 0.19051\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cpre\u003e\u003ccode\u003e** DENSITY SETTING FOR EACH ELEMENT\n*Distribution Table, name=RSV_Res-1_Density_Table\nDensity\n*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table\n** Description: Element-by-Element Densities\n,     1.\nRes-1.210, 2500\nRes-1.209, 2500\nRes-1.208, 2500\nRes-1.207, 2500\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "Element property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.\nTo view the data as a Color Result select the Result Position: Element ( See Geomechanical Results )\nA couple of property names are recognized and treated specially:\n MODULUS \u0026ndash; Scaled by 1.0e-9 and shown as \u0026ldquo;Yong\u0026rsquo;s Modulus\u0026rdquo; in the user interface RATIO \u0026ndash; Shown as \u0026ldquo;Poisson\u0026rsquo;s Ratio\u0026rdquo; in the user interface  File Format A couple of examples on the file format are shown below.\nResInsight searches for the first line containing *Distribution Table, then splits the following line by ,. These entries describes the expected property values to be found in the file.\nResInsight then searches for the data block by ignoring lines\n starting with * and , does not have the expected column count when splitting the line by ,  When the datablock is found, the part of the line before . is stripped away, and first column is expected to be element ID\n** ELASTIC SETTING FOR EACH ELEMENT\r*Distribution Table, name=RSV_Res-1_Elastic_Table\rMODULUS, RATIO\r*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table\r** Description: Element-by-Element Elastic properties\r, 2.\rRes-1.210, 11198814808.2538, 0.19041\rRes-1.209, 11207002032.1436, 0.19063\rRes-1.208, 11222989223.0933, 0.19104\rRes-1.207, 11202549454.349, 0.19051\r** DENSITY SETTING FOR EACH ELEMENT\r*Distribution Table, name=RSV_Res-1_Density_Table\rDensity\r*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table\r** Description: Element-by-Element Densities\r, 1.\rRes-1.210, 2500\rRes-1.209, 2500\rRes-1.208, 2500\rRes-1.207, 2500\r",
+                html:     "\u003cp\u003eElement property tables in ABQUS input file format can be imported into ResInsight and displayed as Element Results. This can be used to display material properties, or any scalar value on each element.\u003c/p\u003e\n\u003cp\u003eTo view the data as a \u003cstrong\u003eColor Result\u003c/strong\u003e select the \u003cstrong\u003eResult Position\u003c/strong\u003e: \u003cem\u003e\u003cstrong\u003eElement\u003c/strong\u003e\u003c/em\u003e ( See \u003ca href=\"/3d-main-window/cellresults/#geomechanical-results\"\u003eGeomechanical Results\u003c/a\u003e )\u003c/p\u003e\n\u003cp\u003eA couple of property names are recognized and treated specially:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eMODULUS \u0026ndash; Scaled by 1.0e-9 and shown as \u0026ldquo;Yong\u0026rsquo;s Modulus\u0026rdquo; in the user interface\u003c/li\u003e\n\u003cli\u003eRATIO \u0026ndash; Shown as \u0026ldquo;Poisson\u0026rsquo;s Ratio\u0026rdquo; in the user interface\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"file-format\"\u003eFile Format\u003c/h3\u003e\n\u003cp\u003eA couple of examples on the file format are shown below.\u003c/p\u003e\n\u003cp\u003eResInsight searches for the first line containing \u003ccode\u003e*Distribution Table\u003c/code\u003e, then splits the following line by \u003ccode\u003e,\u003c/code\u003e. These entries describes the expected property values to be found in the file.\u003c/p\u003e\n\u003cp\u003eResInsight then searches for the data block by ignoring lines\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003estarting with \u003ccode\u003e*\u003c/code\u003e and \u003ccode\u003e,\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003edoes not have the expected column count when splitting the line by \u003ccode\u003e,\u003c/code\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen the datablock is found, the part of the line before \u003ccode\u003e.\u003c/code\u003e is stripped away, and first column is expected to be element ID\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e** ELASTIC SETTING FOR EACH ELEMENT\r\n*Distribution Table, name=RSV_Res-1_Elastic_Table\r\nMODULUS, RATIO\r\n*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table\r\n** Description: Element-by-Element Elastic properties\r\n,     2.\r\nRes-1.210, 11198814808.2538, 0.19041\r\nRes-1.209, 11207002032.1436, 0.19063\r\nRes-1.208, 11222989223.0933, 0.19104\r\nRes-1.207, 11202549454.349, 0.19051\r\n\u003c/code\u003e\u003c/pre\u003e\u003cpre\u003e\u003ccode\u003e** DENSITY SETTING FOR EACH ELEMENT\r\n*Distribution Table, name=RSV_Res-1_Density_Table\r\nDensity\r\n*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table\r\n** Description: Element-by-Element Densities\r\n,     1.\r\nRes-1.210, 2500\r\nRes-1.209, 2500\r\nRes-1.208, 2500\r\nRes-1.207, 2500\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/import/elementpropertytable/"
             };
         
@@ -2074,7 +2107,7 @@ if (!doNotTrack) {
             window.store["/export/fluxnummultnum/"] = {
                 title:    "FLUXNUM/MULTNUM",
                 content:  "The visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.\nYou can do this by using the command Export Visible Cells as FLUXNUM/MULTNUM found by right clicking:\n View in the Project Tree. Cell Result in the Project Tree. In any Eclipse 3D View.  The command can also be found in File -\u0026gt; Export. If the command is used in the project tree, the visible cells from the selected view are used for calculation. In the 3D view and from File -\u0026gt; Export, the visible cells from the currently active 3D view are used.\n Export Filename \u0026ndash; Name of the file to export to. Export Keyword \u0026ndash; Selects the Eclipse keyword to export. Visible Active Cells Value \u0026ndash; This value is used for all the active cells that passes the filters(Range Filter, Property Filter etc) in the 3D View, and thus is visible. Hidden Active Cells Value \u0026ndash; All the active cells that are not visible in the 3D view. Inactive Cells Value \u0026ndash; This value is used for all inactive cells, regardless of whether they are visible or not.  ",
-                html:     "\u003cp\u003eThe visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.\u003c/p\u003e\n\n\u003cp\u003eYou can do this by using the command \u003cstrong\u003eExport Visible Cells as FLUXNUM/MULTNUM\u003c/strong\u003e found by right clicking:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e in the Project Tree.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Result\u003c/strong\u003e in the Project Tree.\u003c/li\u003e\n\u003cli\u003eIn any Eclipse \u003cstrong\u003e3D View\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe command can also be found in \u003cstrong\u003eFile -\u0026gt; Export\u003c/strong\u003e. If the command is used in the project tree, the visible cells from the selected view are used for calculation. In the 3D view and from File -\u0026gt; Export, the visible cells from the currently active 3D view are used.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/fluxnumMultnum.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Filename\u003c/strong\u003e \u0026ndash; Name of the file to export to.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Keyword\u003c/strong\u003e \u0026ndash; Selects the Eclipse keyword to export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Active Cells Value\u003c/strong\u003e \u0026ndash; This value is used for all the active cells that passes the filters(Range Filter, Property Filter etc) in the 3D View, and thus is visible.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHidden Active Cells Value\u003c/strong\u003e \u0026ndash; All the active cells that are not visible in the 3D view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInactive Cells Value\u003c/strong\u003e \u0026ndash; This value is used for all inactive cells, regardless of whether they are visible or not.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                html:     "\u003cp\u003eThe visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.\u003c/p\u003e\n\u003cp\u003eYou can do this by using the command \u003cstrong\u003eExport Visible Cells as FLUXNUM/MULTNUM\u003c/strong\u003e found by right clicking:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e in the Project Tree.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Result\u003c/strong\u003e in the Project Tree.\u003c/li\u003e\n\u003cli\u003eIn any Eclipse \u003cstrong\u003e3D View\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe command can also be found in \u003cstrong\u003eFile -\u0026gt; Export\u003c/strong\u003e. If the command is used in the project tree, the visible cells from the selected view are used for calculation. In the 3D view and from File -\u0026gt; Export, the visible cells from the currently active 3D view are used.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/fluxnumMultnum.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Filename\u003c/strong\u003e \u0026ndash; Name of the file to export to.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Keyword\u003c/strong\u003e \u0026ndash; Selects the Eclipse keyword to export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Active Cells Value\u003c/strong\u003e \u0026ndash; This value is used for all the active cells that passes the filters(Range Filter, Property Filter etc) in the 3D View, and thus is visible.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHidden Active Cells Value\u003c/strong\u003e \u0026ndash; All the active cells that are not visible in the 3D view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInactive Cells Value\u003c/strong\u003e \u0026ndash; This value is used for all inactive cells, regardless of whether they are visible or not.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/export/fluxnummultnum/"
             };
         
@@ -2083,7 +2116,7 @@ if (!doNotTrack) {
             window.store["/misc/keyboardshortcuts/"] = {
                 title:    "Keyboard Shortcuts",
                 content:  "ResInsight supports a selection of Keyboard Shortcuts for convenience. These include Delete for removing deletable items from the project tree, Ctrl-Alt-A for Zoom All and Ctrl-Alt-S/N/W/E/D/U for changing the camera view to South, North, West, East, Down and Up respectively.\nOther available keyboard shortcuts are\n Ctrl-Shift-P for opening up the plot window when you are in the 3d View Ctrl-Shift-3 for opening up the 3d View while you are in the Plot Window Ctrl-X for Cut and Ctrl-V for Paste of project tree items where this functionality is available. Ctrl-O for opening a project Ctrl-S for saving the project F1 for opening the online User Guide Ctrl-M for single line measurement Ctrl-Shift-M for poly line measurement  ",
-                html:     "\u003cp\u003eResInsight supports a selection of Keyboard Shortcuts for convenience. These include \u003cstrong\u003eDelete\u003c/strong\u003e for removing deletable items\nfrom the project tree, \u003cstrong\u003eCtrl-Alt-A\u003c/strong\u003e for Zoom All and \u003cstrong\u003eCtrl-Alt-S/N/W/E/D/U\u003c/strong\u003e for changing the camera view to South, North, West, East, Down and Up respectively.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/KeyboardDel.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/3d-main-window/KeyboardEast.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/3d-main-window/KeyboardPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eOther available keyboard shortcuts are\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-P\u003c/strong\u003e for opening up the plot window when you are in the 3d View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-3\u003c/strong\u003e for opening up the 3d View while you are in the Plot Window\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-X\u003c/strong\u003e for Cut and \u003cstrong\u003eCtrl-V\u003c/strong\u003e for Paste of project tree items where this functionality is available.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-O\u003c/strong\u003e for opening a project\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-S\u003c/strong\u003e for saving the project\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eF1\u003c/strong\u003e for opening the online User Guide\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-M\u003c/strong\u003e for single line measurement\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-M\u003c/strong\u003e for poly line measurement\u003c/li\u003e\n\u003c/ul\u003e\n",
+                html:     "\u003cp\u003eResInsight supports a selection of Keyboard Shortcuts for convenience. These include \u003cstrong\u003eDelete\u003c/strong\u003e for removing deletable items\nfrom the project tree, \u003cstrong\u003eCtrl-Alt-A\u003c/strong\u003e for Zoom All and \u003cstrong\u003eCtrl-Alt-S/N/W/E/D/U\u003c/strong\u003e for changing the camera view to South, North, West, East, Down and Up respectively.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/KeyboardDel.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/3d-main-window/KeyboardEast.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/3d-main-window/KeyboardPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eOther available keyboard shortcuts are\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-P\u003c/strong\u003e for opening up the plot window when you are in the 3d View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-3\u003c/strong\u003e for opening up the 3d View while you are in the Plot Window\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-X\u003c/strong\u003e for Cut and \u003cstrong\u003eCtrl-V\u003c/strong\u003e for Paste of project tree items where this functionality is available.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-O\u003c/strong\u003e for opening a project\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-S\u003c/strong\u003e for saving the project\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eF1\u003c/strong\u003e for opening the online User Guide\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-M\u003c/strong\u003e for single line measurement\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl-Shift-M\u003c/strong\u003e for poly line measurement\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/misc/keyboardshortcuts/"
             };
         
@@ -2091,8 +2124,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/modelnavigation/"] = {
                 title:    "Model Navigation",
-                content:  " ResInsight comes with four navigation modes. The active mode can be selected in the Preferences dialog.\nNote that changing the navigation mode applies to the currently active view only, and views created after the change.\nThese abbreviations are used in the tables below:\n   Abbreviation Meaning     LMB Press the left mouse button   MMB Press the middle mouse button or scroll wheel button   RMB Press the right mouse button    The following applies to all navigation modes:\n   Mouse interaction Action     RMB single click Right-click menu (context menu)   LMB single click Update status bar and Result Info    RMS navigation mode    Mouse interaction Action     LMB + drag Zoom model   MMB + drag Rotate model   Scroll wheel Zoom to mouse pointer location   RMB + drag Pan model    CAD navigation mode    Mouse interaction Action     LMB + drag Pan model   MMB + drag Rotate model   MMB + Shift Pan model   Scroll wheel Zoom to mouse pointer location    GeoQuest navigation mode    Mouse interaction Action     LMB + drag Rotate model   MMB + drag Pan model   Scroll wheel Zoom to mouse pointer location    Ceetron navigation mode    Mouse interaction Action     LMB + drag Pan model   MMB + drag Zoom to mouse pointer location   Scroll wheel Zoom to mouse pointer location   RMB + drag Rotate model    ",
-                html:     "\n\n\u003cp\u003eResInsight comes with four navigation modes. The active mode can be selected in the \u003ca href=\"/misc/preferences/\"\u003ePreferences dialog\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eNote that changing the navigation mode applies to the currently active view only, and views created after the change.\u003c/p\u003e\n\n\u003cp\u003eThese abbreviations are used in the tables below:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eAbbreviation\u003c/th\u003e\n\u003cth\u003eMeaning\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB\u003c/td\u003e\n\u003ctd\u003ePress the left mouse button\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB\u003c/td\u003e\n\u003ctd\u003ePress the middle mouse button or scroll wheel button\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eRMB\u003c/td\u003e\n\u003ctd\u003ePress the right mouse button\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eThe following applies to all navigation modes:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eRMB single click\u003c/td\u003e\n\u003ctd\u003eRight-click menu (context menu)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eLMB single click\u003c/td\u003e\n\u003ctd\u003eUpdate status bar and \u003cstrong\u003eResult Info\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"rms-navigation-mode\"\u003eRMS navigation mode\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003eZoom model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eRMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"cad-navigation-mode\"\u003eCAD navigation mode\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB + Shift\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"geoquest-navigation-mode\"\u003eGeoQuest navigation mode\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"ceetron-navigation-mode\"\u003eCeetron navigation mode\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eRMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
+                content:  "ResInsight comes with four navigation modes. The active mode can be selected in the [Preferences dialog] (/misc/preferences/).\nNote that changing the navigation mode applies to the currently active view only, and views created after the change.\nThese abbreviations are used in the tables below:\n   Abbreviation Meaning     LMB Press the left mouse button   MMB Press the middle mouse button or scroll wheel button   RMB Press the right mouse button    The following applies to all navigation modes:\n   Mouse interaction Action     RMB single click Right-click menu (context menu)   LMB single click Update status bar and Result Info    RMS navigation mode    Mouse interaction Action     LMB + drag Zoom model   MMB + drag Rotate model   Scroll wheel Zoom to mouse pointer location   RMB + drag Pan model    CAD navigation mode    Mouse interaction Action     LMB + drag Pan model   MMB + drag Rotate model   MMB + Shift Pan model   Scroll wheel Zoom to mouse pointer location    GeoQuest navigation mode    Mouse interaction Action     LMB + drag Rotate model   MMB + drag Pan model   Scroll wheel Zoom to mouse pointer location    Ceetron navigation mode    Mouse interaction Action     LMB + drag Pan model   MMB + drag Zoom to mouse pointer location   Scroll wheel Zoom to mouse pointer location   RMB + drag Rotate model    ",
+                html:     "\u003cp\u003eResInsight comes with four navigation modes. The active mode can be selected in the [Preferences dialog] (/misc/preferences/).\u003c/p\u003e\n\u003cp\u003eNote that changing the navigation mode applies to the currently active view only, and views created after the change.\u003c/p\u003e\n\u003cp\u003eThese abbreviations are used in the tables below:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eAbbreviation\u003c/th\u003e\n\u003cth\u003eMeaning\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB\u003c/td\u003e\n\u003ctd\u003ePress the left mouse button\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB\u003c/td\u003e\n\u003ctd\u003ePress the middle mouse button or scroll wheel button\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRMB\u003c/td\u003e\n\u003ctd\u003ePress the right mouse button\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eThe following applies to all navigation modes:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eRMB single click\u003c/td\u003e\n\u003ctd\u003eRight-click menu (context menu)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB single click\u003c/td\u003e\n\u003ctd\u003eUpdate status bar and \u003cstrong\u003eResult Info\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"rms-navigation-mode\"\u003eRMS navigation mode\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003eZoom model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"cad-navigation-mode\"\u003eCAD navigation mode\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB + Shift\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"geoquest-navigation-mode\"\u003eGeoQuest navigation mode\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"ceetron-navigation-mode\"\u003eCeetron navigation mode\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eMouse interaction\u003c/th\u003e\n\u003cth\u003eAction\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLMB + drag\u003c/td\u003e\n\u003ctd\u003ePan model\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMMB + drag\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eScroll wheel\u003c/td\u003e\n\u003ctd\u003eZoom to mouse pointer location\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eRMB + drag\u003c/td\u003e\n\u003ctd\u003eRotate model\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
                 url:      "/getting-started/modelnavigation/"
             };
         
@@ -2100,8 +2133,8 @@ if (!doNotTrack) {
          
             window.store["/import/observeddata/"] = {
                 title:    "Observed Time History Data",
-                content:  " Observed Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in Summary Plots.\nImport Observed Time History Data Importing observed time history data to ResInsight may be performed in two different ways:\n By selecting the main menu item File -\u0026gt; Import -\u0026gt; Import Observed Time History Data By using the context command Import Observed Time History Data on the Observed Time History Data item in the Plot Main Window Project Tree  The following file types are supported:\n RSM observed time history data file (*.rsm) Column based (Comma Separated Values, CSV) time history data file (*.csv/*.txt) The imported Observed Time History Data files will be added to Observed Time History Data.  Which summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data\u0026rsquo;s Property Editor. In the image below, time and year info has been found together with the summary \u0026ldquo;WBP9L\u0026rdquo; for the well \u0026ldquo;OP-1\u0026rdquo;.\nFile Formats Import CSV/txt Observed Time History Data CSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.\nCSV/txt Import Options Dialog Dialog fields description:\n Cell Separator \u0026ndash; Select the correct cell separator character. ResInsight will try to set the correct value as default. Decimal Separator \u0026ndash; Select the correct decimal separator. ResInsight will try to set the correct value as default. Selected Time Column \u0026ndash; Select the column that contains the time/date information. The first column is default. Use Custom Date Time Format \u0026ndash; Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats. Custom Date Time Format \u0026ndash; Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information. Date Format \u0026ndash; Select the date format matching the date information in the file. Time Format \u0026ndash; Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight. Preview \u0026ndash; Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.  Column data Each column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the Summary Plot Editor.\nEclipse address format An Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: \u0026lsquo;RPR__WEL\u0026rsquo;. Vector names having only the standard part are not padded.\nCategories:\n Field - \u0026lt;VECTOR \u0026lsquo;F\u0026hellip;.\u0026rsquo;\u0026gt;  Example: \u0026lsquo;FOPT\u0026rsquo;  Aquifer - \u0026lt;VECTOR \u0026lsquo;A\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;AQUIFER NUMBER\u0026gt;  Example: \u0026lsquo;AAQR:1\u0026rsquo;  Network - \u0026lt;VECTOR \u0026lsquo;N\u0026hellip;.\u0026rsquo;\u0026gt; Misc - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.\u0026rsquo;\u0026gt; Region - \u0026lt;VECTOR \u0026lsquo;R\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;  Example: \u0026lsquo;RPR:1\u0026rsquo;  Region to Region - \u0026lt;VECTOR \u0026lsquo;R.F..\u0026rsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;-\u0026lt;REGION NUMBER\u0026gt;  Example: \u0026lsquo;ROFR:1-2\u0026rsquo;  Group - \u0026lt;VECTOR \u0026lsquo;G\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;GROUP NAME\u0026gt;  Example: \u0026lsquo;GOPR:MANI-B1\u0026rsquo;  Well - \u0026lt;VECTOR \u0026lsquo;W\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;  Example: \u0026lsquo;WOPR:B-2H\u0026rsquo;  Completion - \u0026lt;VECTOR \u0026lsquo;C\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;COFRL:C-1H:26,44,16\u0026rsquo;  LGR Completion - \u0026lt;VECTOR \u0026lsquo;LC\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;LCWIT:WELLI1:I1:5,5,5\u0026rsquo;  LGR Well - \u0026lt;VECTOR \u0026lsquo;LW\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;  Example: \u0026lsquo;LWWIR:WELLI1:I1\u0026rsquo;  Segment - \u0026lt;VECTOR \u0026rsquo;S\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;SEGMENT NUMBER\u0026gt;  Example: \u0026lsquo;SOFR:B-5H:32\u0026rsquo;  Block - \u0026lt;Vector \u0026lsquo;B\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;BPR:15,18,21\u0026rsquo;  LGR Block - \u0026lt;VECTOR \u0026lsquo;LB\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;LBOSAT:CENTER:5,5,5\u0026rsquo;  Imported - \u0026lt;SOME NAME\u0026gt;  When ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the Imported category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.\nInstantaneous vs Accumulated Data\nA valid Eclipse vector having a standard name ending with \u0026rsquo;T\u0026rsquo; or \u0026lsquo;TH\u0026rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.\nError data\nAny address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by \u0026lsquo;ER:\u0026lsquo;, \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:\u0026lsquo;. Example: \u0026lsquo;ERR:FOPT\u0026rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.\nExample:\nCSV Line Based Format ResInsight supports a \u0026lsquo;line based\u0026rsquo; CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.\nWhen importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:\n At least DATE, VECTOR and VALUE columns must be present. The order of columns may be changed. Optionally the columns ERROR and COMMENTS may be present ISO date format must be used: \u0026lsquo;yyyy-mm-dd\u0026rsquo; or \u0026lsquo;yyyy-mm-dd hh:mm\u0026rsquo; Semicolon (;) must be used as column separator Point (.) must be used as decimal separator The comment must not contain any semicolons  Example The two examples below are equvalent and result in identical data after importing to ResInsight\nLine based CSV:\nDATE ;VECTOR ;VALUE ;ERROR 2018-04-16 ;FOPT ;12.5 ;0.45 2018-04-18 ;FOPT ;8.6 ;0.31  Normal CSV:\nDATE ;FOPT ;ERR:FOPT 2018-04-16 ;12.5 ;0.45 2018-04-18 ;8.6 ;0.31  Import RSM observed time history data To import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the Observed Time History Data node in the project tree. RSM files can be either Column based or Keyword based.\nColumn Based File Format If a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.\nThe first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, FVPT and FWPT are of type Field, as they both have an initial F. WWCTH and WGORH are well data types. See Vector naming convention in Eclipse: File Formats Reference Manual for a full overview of supported mnemonics.\nThe next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with \u0026ndash; will also be ignored.\nColumn Based with Fixed Header Width When interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.\n1 ------------------------------------------------------------------------- SUMMARY ------------------------------------------------------------------------- DATE FGIRH FVPT FWPT FOPT FLPT SM3/DAY RM3 SM3 SM3 SM3 *10**3 *10**3 *10**3 *10**3 ------------------------------------------------------------------------- 6-NOV-1997 0 0 0 0 0 7-NOV-1997 0 5.749954 0.004548 4.379801 4.384350 8-NOV-1997 0 13.76883 0.010841 10.48852 10.49936 9-NOV-1997 0 19.38692 0.015243 14.76847 14.78372 10-NOV-1997 0 24.07161 0.018914 18.33751 18.35642 11-NOV-1997 0 28.79427 0.022613 21.93558 21.95819  Column Based with Random Header Width Column Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 probably belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.\nTIME WWCTH WGORH DAYS SM3/SM3 A-5HP A-5HP 1 0.000 0.000 2 0.000 0.000 3 0.000 0.000  Keyword Based File Format If the non-comment line includes the word \u0026ldquo;VECTOR\u0026rdquo;, the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, S-1AH-GOR is associated with YEARX, since their origin is equal. ResInsight always interpret ORIGIN as well name, and look for a table with the line \u0026ldquo;VECTOR YEARX\u0026rdquo; to associate with it.\n---------------------------------------------- -- GOR data ---------------------------------------------- VECTOR S-122AH-GOR UNITS SM3/SM3 ORIGIN GORS-122AH 330.6601 257.7500 335.9894 301.4388 260.4193 306.0298 280.2883 VECTOR YEARX ORIGIN GORS-112AH UNITS YEAR 1999.7902 1999.8446 1999.9285 2000.0391 2000.0800 2000.0862 2000.1285 ---comment ---------------------------------------------- -- GOR data ---------------------------------------------- VECTOR S-211H-GOR UNITS SM3/SM3 ORIGIN GORS-211H 293.8103 293.1634 304.0000 334.5932 306.4610 293.7571 VECTOR YEARX ORIGIN GORS-22H UNITS YEAR 1999.8255 2000.1274 2000.2075 2000.2367 2000.4033 2000.4966  Please seek \u0026ldquo;User data file formats\u0026rdquo; in Eclipse: File Formats Reference Manual for details.\nViewing Observed Time History Data To plot Observed Time History Data, choose New Summary Plot in the right-click menu of Summary Plots, in Plot Object Project Tree. Observed time history data will appear in Sources together with summary cases. How to use the Plot Editor is covered in Summary Plot Editor. Observed time history data points are plotted without lines by default.\n",
-                html:     "\n\n\u003cp\u003eObserved Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in \u003cstrong\u003eSummary Plots\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"import-observed-time-history-data\"\u003eImport Observed Time History Data\u003c/h2\u003e\n\n\u003cp\u003eImporting observed time history data to ResInsight may be performed in two different ways:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eBy selecting the main menu item \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Import Observed Time History Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the context command \u003cstrong\u003eImport Observed Time History Data\u003c/strong\u003e on the \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e item in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe following file types are supported:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eRSM observed time history data file (\u003cem\u003e*.rsm\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003eColumn based (Comma Separated Values, CSV) time history data file (\u003cem\u003e*.csv/*.txt\u003c/em\u003e)\nThe imported \u003cimg src=\"https://resinsight.org/images/import/Default.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Observed Time History Data files will be added to \u003cimg src=\"https://resinsight.org/images/import/Folder.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhich summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. In the image below, time and year info has been found together with the summary \u0026ldquo;WBP9L\u0026rdquo; for the well \u0026ldquo;OP-1\u0026rdquo;.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/observedDataProperty.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"file-formats\"\u003eFile Formats\u003c/h2\u003e\n\n\u003ch3 id=\"import-csv-txt-observed-time-history-data\"\u003eImport CSV/txt Observed Time History Data\u003c/h3\u003e\n\n\u003cp\u003eCSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.\u003c/p\u003e\n\n\u003ch4 id=\"csv-txt-import-options-dialog\"\u003eCSV/txt Import Options Dialog\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/ImportObservedTimeHistoryDataDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eDialog fields description:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Separator\u003c/strong\u003e \u0026ndash; Select the correct cell separator character. ResInsight will try to set the correct value as default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDecimal Separator\u003c/strong\u003e \u0026ndash; Select the correct decimal separator. ResInsight will try to set the correct value as default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelected Time Column\u003c/strong\u003e \u0026ndash; Select the column that contains the time/date information. The first column is default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Custom Date Time Format\u003c/strong\u003e \u0026ndash; Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCustom Date Time Format\u003c/strong\u003e \u0026ndash; Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate Format\u003c/strong\u003e \u0026ndash; Select the date format matching the date information in the file.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Format\u003c/strong\u003e \u0026ndash; Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePreview\u003c/strong\u003e \u0026ndash; Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"column-data\"\u003eColumn data\u003c/h4\u003e\n\n\u003cp\u003eEach column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch5 id=\"eclipse-address-format\"\u003eEclipse address format\u003c/h5\u003e\n\n\u003cp\u003eAn Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: \u0026lsquo;RPR__WEL\u0026rsquo;. Vector names having only the standard part are not padded.\u003c/p\u003e\n\n\u003cp\u003eCategories:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eField\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;F\u0026hellip;.\u0026rsquo;\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;FOPT\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;A\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;AQUIFER NUMBER\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;AAQR:1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNetwork\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;N\u0026hellip;.\u0026rsquo;\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMisc\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.\u0026rsquo;\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;R\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;RPR:1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion to Region\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;R.F..\u0026rsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;-\u0026lt;REGION NUMBER\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;ROFR:1-2\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;G\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;GROUP NAME\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;GOPR:MANI-B1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;W\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;WOPR:B-2H\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;C\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;COFRL:C-1H:26,44,16\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Completion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LC\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LCWIT:WELLI1:I1:5,5,5\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Well\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LW\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LWWIR:WELLI1:I1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment\u003c/strong\u003e - \u0026lt;VECTOR \u0026rsquo;S\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;SEGMENT NUMBER\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;SOFR:B-5H:32\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBlock\u003c/strong\u003e - \u0026lt;Vector \u0026lsquo;B\u0026hellip;.\u0026rsquo;\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;BPR:15,18,21\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Block\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LB\u0026hellip;\u0026rsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LBOSAT:CENTER:5,5,5\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImported\u003c/strong\u003e - \u0026lt;SOME NAME\u0026gt;\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the \u003cstrong\u003eImported\u003c/strong\u003e category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eInstantaneous vs Accumulated Data\u003c/strong\u003e\u003cbr /\u003e\nA valid Eclipse vector having a standard name ending with \u0026rsquo;T\u0026rsquo; or \u0026lsquo;TH\u0026rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eError data\u003c/strong\u003e\u003cbr /\u003e\nAny address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by \u0026lsquo;ER:\u0026lsquo;, \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:\u0026lsquo;. Example: \u0026lsquo;ERR:FOPT\u0026rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.\u003c/p\u003e\n\n\u003cp\u003eExample:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/ErrorBars.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"csv-line-based-format\"\u003eCSV Line Based Format\u003c/h3\u003e\n\n\u003cp\u003eResInsight supports a \u0026lsquo;line based\u0026rsquo; CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.\u003c/p\u003e\n\n\u003cp\u003eWhen importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eAt least \u003cstrong\u003eDATE\u003c/strong\u003e, \u003cstrong\u003eVECTOR\u003c/strong\u003e and \u003cstrong\u003eVALUE\u003c/strong\u003e columns must be present. The order of columns may be changed.\u003c/li\u003e\n\u003cli\u003eOptionally the columns \u003cstrong\u003eERROR\u003c/strong\u003e and \u003cstrong\u003eCOMMENTS\u003c/strong\u003e may be present\u003c/li\u003e\n\u003cli\u003eISO date format must be used: \u0026lsquo;yyyy-mm-dd\u0026rsquo; or \u0026lsquo;yyyy-mm-dd hh:mm\u0026rsquo;\u003c/li\u003e\n\u003cli\u003eSemicolon (;) must be used as column separator\u003c/li\u003e\n\u003cli\u003ePoint (.) must be used as decimal separator\u003c/li\u003e\n\u003cli\u003eThe comment must not contain any semicolons\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"example\"\u003eExample\u003c/h4\u003e\n\n\u003cp\u003eThe two examples below are equvalent and result in identical data after importing to ResInsight\u003c/p\u003e\n\n\u003cp\u003eLine based CSV:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eDATE       ;VECTOR ;VALUE ;ERROR\n2018-04-16 ;FOPT   ;12.5  ;0.45\n2018-04-18 ;FOPT   ;8.6   ;0.31\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eNormal CSV:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eDATE       ;FOPT ;ERR:FOPT\n2018-04-16 ;12.5 ;0.45\n2018-04-18 ;8.6  ;0.31\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"import-rsm-observed-time-history-data\"\u003eImport RSM observed time history data\u003c/h3\u003e\n\n\u003cp\u003eTo import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e node in the project tree. RSM files can be either \u003cem\u003eColumn based\u003c/em\u003e or \u003cem\u003eKeyword based\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch4 id=\"column-based-file-format\"\u003eColumn Based File Format\u003c/h4\u003e\n\n\u003cp\u003eIf a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.\u003c/p\u003e\n\n\u003cp\u003eThe first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, \u003cem\u003eFVPT\u003c/em\u003e and \u003cem\u003eFWPT\u003c/em\u003e are of type \u003cem\u003eField\u003c/em\u003e, as they both have an initial \u003cem\u003eF\u003c/em\u003e. \u003cem\u003eWWCTH\u003c/em\u003e and \u003cem\u003eWGORH\u003c/em\u003e are well data types. See \u003cem\u003eVector naming convention\u003c/em\u003e in \u003cstrong\u003eEclipse: File Formats Reference Manual\u003c/strong\u003e for a full overview of supported mnemonics.\u003c/p\u003e\n\n\u003cp\u003eThe next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with \u003cem\u003e\u003cem\u003e\u0026ndash;\u003c/em\u003e\u003c/em\u003e will also be ignored.\u003c/p\u003e\n\n\u003ch5 id=\"column-based-with-fixed-header-width\"\u003eColumn Based with Fixed Header Width\u003c/h5\u003e\n\n\u003cp\u003eWhen interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e1                                                                                                      \n -------------------------------------------------------------------------\n SUMMARY\n -------------------------------------------------------------------------\n DATE         FGIRH        FVPT         FWPT         FOPT         FLPT  \n              SM3/DAY      RM3          SM3          SM3          SM3    \n                           *10**3       *10**3       *10**3       *10**3 \n                                                                         \n                                                                         \n -------------------------------------------------------------------------\n  6-NOV-1997         0            0            0            0            0 \n  7-NOV-1997         0     5.749954     0.004548     4.379801     4.384350  \n  8-NOV-1997         0     13.76883     0.010841     10.48852     10.49936\n  9-NOV-1997         0     19.38692     0.015243     14.76847     14.78372  \n 10-NOV-1997         0     24.07161     0.018914     18.33751     18.35642\n 11-NOV-1997         0     28.79427     0.022613     21.93558     21.95819\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch5 id=\"column-based-with-random-header-width\"\u003eColumn Based with Random Header Width\u003c/h5\u003e\n\n\u003cp\u003eColumn Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 \u003cem\u003eprobably\u003c/em\u003e belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eTIME      WWCTH      WGORH\nDAYS               SM3/SM3          \n\n          A-5HP          A-5HP\n     1     0.000   0.000\n     2     0.000   0.000\n     3     0.000   0.000\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"keyword-based-file-format\"\u003eKeyword Based File Format\u003c/h4\u003e\n\n\u003cp\u003eIf the non-comment line includes the word \u0026ldquo;VECTOR\u0026rdquo;, the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, \u003cem\u003eS-1AH-GOR\u003c/em\u003e is associated with \u003cem\u003eYEARX\u003c/em\u003e, since their origin is equal. ResInsight always interpret \u003cem\u003eORIGIN\u003c/em\u003e as well name, and look for a table with the line \u0026ldquo;VECTOR YEARX\u0026rdquo; to associate with it.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e----------------------------------------------\n-- GOR data \n----------------------------------------------\nVECTOR S-122AH-GOR\nUNITS SM3/SM3\nORIGIN GORS-122AH\n330.6601\n257.7500\n335.9894\n301.4388\n260.4193\n306.0298\n280.2883\n\nVECTOR YEARX\nORIGIN GORS-112AH\nUNITS YEAR\n1999.7902\n1999.8446\n1999.9285\n2000.0391\n2000.0800\n2000.0862\n2000.1285\n---comment\n\n\n----------------------------------------------\n-- GOR data\n----------------------------------------------\nVECTOR S-211H-GOR\nUNITS SM3/SM3\nORIGIN GORS-211H\n293.8103\n293.1634\n304.0000\n334.5932\n306.4610\n293.7571\n\nVECTOR YEARX\nORIGIN GORS-22H\nUNITS YEAR\n1999.8255\n2000.1274\n2000.2075\n2000.2367\n2000.4033\n2000.4966\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003ePlease seek \u0026ldquo;User data file formats\u0026rdquo; in \u003cstrong\u003eEclipse: File Formats Reference Manual\u003c/strong\u003e for details.\u003c/p\u003e\n\n\u003ch2 id=\"viewing-observed-time-history-data\"\u003eViewing Observed Time History Data\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/observedDataCurveCreator.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTo plot Observed Time History Data, choose \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e in the right-click menu of \u003cstrong\u003eSummary Plots\u003c/strong\u003e, in \u003cstrong\u003ePlot Object Project Tree\u003c/strong\u003e. Observed time history data will appear in \u003cstrong\u003eSources\u003c/strong\u003e together with summary cases. How to use the Plot Editor is covered in \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e. Observed time history data points are plotted without lines by default.\u003c/p\u003e\n",
+                content:  "Observed Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in Summary Plots.\nImport Observed Time History Data Importing observed time history data to ResInsight may be performed in two different ways:\n By selecting the main menu item File -\u0026gt; Import -\u0026gt; Import Observed Time History Data By using the context command Import Observed Time History Data on the Observed Time History Data item in the Plot Main Window Project Tree  The following file types are supported:\n RSM observed time history data file (*.rsm) Column based (Comma Separated Values, CSV) time history data file (*.csv/*.txt) The imported Observed Time History Data files will be added to Observed Time History Data.  Which summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data\u0026rsquo;s Property Editor. In the image below, time and year info has been found together with the summary \u0026ldquo;WBP9L\u0026rdquo; for the well \u0026ldquo;OP-1\u0026rdquo;.\nFile Formats Import CSV/txt Observed Time History Data CSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.\nCSV/txt Import Options Dialog Dialog fields description:\n Cell Separator \u0026ndash; Select the correct cell separator character. ResInsight will try to set the correct value as default. Decimal Separator \u0026ndash; Select the correct decimal separator. ResInsight will try to set the correct value as default. Selected Time Column \u0026ndash; Select the column that contains the time/date information. The first column is default. Use Custom Date Time Format \u0026ndash; Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats. Custom Date Time Format \u0026ndash; Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information. Date Format \u0026ndash; Select the date format matching the date information in the file. Time Format \u0026ndash; Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight. Preview \u0026ndash; Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.  Column data Each column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the Summary Plot Editor.\nEclipse address format An Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: \u0026lsquo;RPR__WEL\u0026rsquo;. Vector names having only the standard part are not padded.\nCategories:\n Field - \u0026lt;VECTOR \u0026lsquo;F\u0026hellip;.\u0026lsquo;\u0026gt;  Example: \u0026lsquo;FOPT\u0026rsquo;   Aquifer - \u0026lt;VECTOR \u0026lsquo;A\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;AQUIFER NUMBER\u0026gt;  Example: \u0026lsquo;AAQR:1\u0026rsquo;   Network - \u0026lt;VECTOR \u0026lsquo;N\u0026hellip;.\u0026lsquo;\u0026gt; Misc - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.\u0026lsquo;\u0026gt; Region - \u0026lt;VECTOR \u0026lsquo;R\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;  Example: \u0026lsquo;RPR:1\u0026rsquo;   Region to Region - \u0026lt;VECTOR \u0026lsquo;R.F..\u0026lsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;-\u0026lt;REGION NUMBER\u0026gt;  Example: \u0026lsquo;ROFR:1-2\u0026rsquo;   Group - \u0026lt;VECTOR \u0026lsquo;G\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;GROUP NAME\u0026gt;  Example: \u0026lsquo;GOPR:MANI-B1\u0026rsquo;   Well - \u0026lt;VECTOR \u0026lsquo;W\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;  Example: \u0026lsquo;WOPR:B-2H\u0026rsquo;   Completion - \u0026lt;VECTOR \u0026lsquo;C\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;COFRL:C-1H:26,44,16\u0026rsquo;   LGR Completion - \u0026lt;VECTOR \u0026lsquo;LC\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;LCWIT:WELLI1:I1:5,5,5\u0026rsquo;   LGR Well - \u0026lt;VECTOR \u0026lsquo;LW\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;  Example: \u0026lsquo;LWWIR:WELLI1:I1\u0026rsquo;   Segment - \u0026lt;VECTOR \u0026lsquo;S\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;SEGMENT NUMBER\u0026gt;  Example: \u0026lsquo;SOFR:B-5H:32\u0026rsquo;   Block - \u0026lt;Vector \u0026lsquo;B\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;BPR:15,18,21\u0026rsquo;   LGR Block - \u0026lt;VECTOR \u0026lsquo;LB\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;  Example: \u0026lsquo;LBOSAT:CENTER:5,5,5\u0026rsquo;   Imported - \u0026lt;SOME NAME\u0026gt;  When ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the Imported category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.\nInstantaneous vs Accumulated Data\nA valid Eclipse vector having a standard name ending with \u0026lsquo;T\u0026rsquo; or \u0026lsquo;TH\u0026rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.\nError data\nAny address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by \u0026lsquo;ER:', \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:'. Example: \u0026lsquo;ERR:FOPT\u0026rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.\nExample:\nCSV Line Based Format ResInsight supports a \u0026lsquo;line based\u0026rsquo; CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.\nWhen importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:\n At least DATE, VECTOR and VALUE columns must be present. The order of columns may be changed. Optionally the columns ERROR and COMMENTS may be present ISO date format must be used: \u0026lsquo;yyyy-mm-dd\u0026rsquo; or \u0026lsquo;yyyy-mm-dd hh:mm\u0026rsquo; Semicolon (;) must be used as column separator Point (.) must be used as decimal separator The comment must not contain any semicolons  Example The two examples below are equvalent and result in identical data after importing to ResInsight\nLine based CSV:\nDATE ;VECTOR ;VALUE ;ERROR\r2018-04-16 ;FOPT ;12.5 ;0.45\r2018-04-18 ;FOPT ;8.6 ;0.31\rNormal CSV:\nDATE ;FOPT ;ERR:FOPT\r2018-04-16 ;12.5 ;0.45\r2018-04-18 ;8.6 ;0.31\rImport RSM observed time history data To import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the Observed Time History Data node in the project tree. RSM files can be either Column based or Keyword based.\nColumn Based File Format If a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.\nThe first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, FVPT and FWPT are of type Field, as they both have an initial F. WWCTH and WGORH are well data types. See Vector naming convention in Eclipse: File Formats Reference Manual for a full overview of supported mnemonics.\nThe next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with \u0026ndash; will also be ignored.\nColumn Based with Fixed Header Width When interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.\n1 -------------------------------------------------------------------------\rSUMMARY\r-------------------------------------------------------------------------\rDATE FGIRH FVPT FWPT FOPT FLPT SM3/DAY RM3 SM3 SM3 SM3 *10**3 *10**3 *10**3 *10**3 -------------------------------------------------------------------------\r6-NOV-1997 0 0 0 0 0 7-NOV-1997 0 5.749954 0.004548 4.379801 4.384350 8-NOV-1997 0 13.76883 0.010841 10.48852 10.49936\r9-NOV-1997 0 19.38692 0.015243 14.76847 14.78372 10-NOV-1997 0 24.07161 0.018914 18.33751 18.35642\r11-NOV-1997 0 28.79427 0.022613 21.93558 21.95819\rColumn Based with Random Header Width Column Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 probably belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.\nTIME WWCTH WGORH\rDAYS SM3/SM3 A-5HP A-5HP\r1 0.000 0.000\r2 0.000 0.000\r3 0.000 0.000\rKeyword Based File Format If the non-comment line includes the word \u0026ldquo;VECTOR\u0026rdquo;, the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, S-1AH-GOR is associated with YEARX, since their origin is equal. ResInsight always interpret ORIGIN as well name, and look for a table with the line \u0026ldquo;VECTOR YEARX\u0026rdquo; to associate with it.\n----------------------------------------------\r-- GOR data ----------------------------------------------\rVECTOR S-122AH-GOR\rUNITS SM3/SM3\rORIGIN GORS-122AH\r330.6601\r257.7500\r335.9894\r301.4388\r260.4193\r306.0298\r280.2883\rVECTOR YEARX\rORIGIN GORS-112AH\rUNITS YEAR\r1999.7902\r1999.8446\r1999.9285\r2000.0391\r2000.0800\r2000.0862\r2000.1285\r---comment\r----------------------------------------------\r-- GOR data\r----------------------------------------------\rVECTOR S-211H-GOR\rUNITS SM3/SM3\rORIGIN GORS-211H\r293.8103\r293.1634\r304.0000\r334.5932\r306.4610\r293.7571\rVECTOR YEARX\rORIGIN GORS-22H\rUNITS YEAR\r1999.8255\r2000.1274\r2000.2075\r2000.2367\r2000.4033\r2000.4966\rPlease seek \u0026ldquo;User data file formats\u0026rdquo; in Eclipse: File Formats Reference Manual for details.\nViewing Observed Time History Data To plot Observed Time History Data, choose New Summary Plot in the right-click menu of Summary Plots, in Plot Object Project Tree. Observed time history data will appear in Sources together with summary cases. How to use the Plot Editor is covered in Summary Plot Editor. Observed time history data points are plotted without lines by default.\n",
+                html:     "\u003cp\u003eObserved Time History Data, is data measured in time. On import of observed time history data, ResInsight translates the data to make it similar to summary data. Observed time history data can be plotted along with summary data in \u003cstrong\u003eSummary Plots\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"import-observed-time-history-data\"\u003eImport Observed Time History Data\u003c/h2\u003e\n\u003cp\u003eImporting observed time history data to ResInsight may be performed in two different ways:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eBy selecting the main menu item \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Import Observed Time History Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the context command \u003cstrong\u003eImport Observed Time History Data\u003c/strong\u003e on the \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e item in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe following file types are supported:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eRSM observed time history data file (\u003cem\u003e*.rsm\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003eColumn based (Comma Separated Values, CSV) time history data file (\u003cem\u003e*.csv/*.txt\u003c/em\u003e)\nThe imported \u003cimg src=\"https://resinsight.org/images/import/Default.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Observed Time History Data files will be added to \u003cimg src=\"https://resinsight.org/images/import/Folder.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhich summaries that has been detected in a Observed Time History Data file can be read in an Observed Time History Data\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. In the image below, time and year info has been found together with the summary \u0026ldquo;WBP9L\u0026rdquo; for the well \u0026ldquo;OP-1\u0026rdquo;.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/observedDataProperty.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"file-formats\"\u003eFile Formats\u003c/h2\u003e\n\u003ch3 id=\"import-csvtxt-observed-time-history-data\"\u003eImport CSV/txt Observed Time History Data\u003c/h3\u003e\n\u003cp\u003eCSV/txt files are generic ascii files where data is arranged in columns. Some variations in formatting is supported, for instance deifferent cell separators, date and time format, decimal separator etc. When importing these types of files the user is presented a dialog, where the user may tell ResInsight how to import the selected file(s). If more than one file is selected, the dialog appears once for each file.\u003c/p\u003e\n\u003ch4 id=\"csvtxt-import-options-dialog\"\u003eCSV/txt Import Options Dialog\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/ImportObservedTimeHistoryDataDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eDialog fields description:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Separator\u003c/strong\u003e \u0026ndash; Select the correct cell separator character. ResInsight will try to set the correct value as default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDecimal Separator\u003c/strong\u003e \u0026ndash; Select the correct decimal separator. ResInsight will try to set the correct value as default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelected Time Column\u003c/strong\u003e \u0026ndash; Select the column that contains the time/date information. The first column is default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Custom Date Time Format\u003c/strong\u003e \u0026ndash; Check this box if the Date Format and/or Time Format in the file do not match any of the most common formats.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCustom Date Time Format\u003c/strong\u003e \u0026ndash; Enter date time format to match the time information in the file. This field is visible only when the above check box checked. A tooltip will tell the user how to enter the correct information.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate Format\u003c/strong\u003e \u0026ndash; Select the date format matching the date information in the file.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Format\u003c/strong\u003e \u0026ndash; Select the time format matching the time information in the file. If the file contains dates only, this field is ignored by ResInsight.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePreview\u003c/strong\u003e \u0026ndash; Preview the first 30 lines of the file contents. The view will reflect the currently selected Cell Separator and the selected time column is marked in yellow.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"column-data\"\u003eColumn data\u003c/h4\u003e\n\u003cp\u003eEach column must have a header text, which may be a name/description for the data in the column. By formatting the header text to a valid Eclipse address, ResInsight recognizes the column data and will be able to categorize the data in the same way as grid data. So when plotting these data later, the user will find the data in the correct category in the \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e.\u003c/p\u003e\n\u003ch5 id=\"eclipse-address-format\"\u003eEclipse address format\u003c/h5\u003e\n\u003cp\u003eAn Eclipse address consists of a vector name and zero or more parameters. The number of parameters are defined by the category of the vector. The category is determined by looking up the category in an internal vector table. A valid standard vector name has 3 to 5 characters. Optionally it may be postfixed by a user defined name of 3 characters. A vector name having both a standard part and a user part must have 8 characters (5+3). In this case, if the standard part has less than 5 characters, it must be padded with underscores up to 5 characters. Example: \u0026lsquo;RPR__WEL\u0026rsquo;. Vector names having only the standard part are not padded.\u003c/p\u003e\n\u003cp\u003eCategories:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eField\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;F\u0026hellip;.\u0026lsquo;\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;FOPT\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;A\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;AQUIFER NUMBER\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;AAQR:1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNetwork\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;N\u0026hellip;.\u0026lsquo;\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMisc\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.\u0026lsquo;\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;R\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;RPR:1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion to Region\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;R.F..\u0026lsquo;\u0026gt;:\u0026lt;REGION NUMBER\u0026gt;-\u0026lt;REGION NUMBER\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;ROFR:1-2\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;G\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;GROUP NAME\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;GOPR:MANI-B1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;W\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;WOPR:B-2H\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;C\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;COFRL:C-1H:26,44,16\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Completion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LC\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LCWIT:WELLI1:I1:5,5,5\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Well\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LW\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;WELL NAME\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LWWIR:WELLI1:I1\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;S\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;WELL NAME\u0026gt;:\u0026lt;SEGMENT NUMBER\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;SOFR:B-5H:32\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBlock\u003c/strong\u003e - \u0026lt;Vector \u0026lsquo;B\u0026hellip;.\u0026lsquo;\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;BPR:15,18,21\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Block\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;LB\u0026hellip;\u0026lsquo;\u0026gt;:\u0026lt;LGR NAME\u0026gt;:\u0026lt;I\u0026gt;,\u0026lt;J\u0026gt;,\u0026lt;K\u0026gt;\n\u003cul\u003e\n\u003cli\u003eExample: \u0026lsquo;LBOSAT:CENTER:5,5,5\u0026rsquo;\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImported\u003c/strong\u003e - \u0026lt;SOME NAME\u0026gt;\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen ResInsight parses an eclipse address, it first tries to identify an address category by analyzing the vector name, as described above. If no category could be found, the \u003cstrong\u003eImported\u003c/strong\u003e category is used. This category is also used if the address format is wrong (for instance missing parameters) even though the vector name identifies a different category.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eInstantaneous vs Accumulated Data\u003c/strong\u003e\u003cbr\u003e\nA valid Eclipse vector having a standard name ending with \u0026lsquo;T\u0026rsquo; or \u0026lsquo;TH\u0026rsquo; are considered accumulated data. In the summary plot, these types of data are plotted slightly different. Instantaneous data are plotted using a stepped curve, while accumulated data are plotted using straight lines between the samples.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eError data\u003c/strong\u003e\u003cbr\u003e\nAny address may have associated error data. Those type of data will have the same address as their associated data, but are prefixed by \u0026lsquo;ER:', \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:'. Example: \u0026lsquo;ERR:FOPT\u0026rsquo;. It is not possible to select error data explicitly in the plot editor selection fields, but when selecting a vector having associated error data, the error data is plotted as error bars in the summary plot.\u003c/p\u003e\n\u003cp\u003eExample:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/ErrorBars.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"csv-line-based-format\"\u003eCSV Line Based Format\u003c/h3\u003e\n\u003cp\u003eResInsight supports a \u0026lsquo;line based\u0026rsquo; CSV file format variant as well. As opposed to the normal CSV format, data values are organized in lines. Each line must contain at least a date (and time), a vector address and a sample value. Optionally it may also contain an error value and a comment. The information carried by this format is equivalent to the normal CSV format, it is only a different file layout.\u003c/p\u003e\n\u003cp\u003eWhen importing a line based CSV file, no dialog appears. Instead a more stict set of rules apply to this type of files:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAt least \u003cstrong\u003eDATE\u003c/strong\u003e, \u003cstrong\u003eVECTOR\u003c/strong\u003e and \u003cstrong\u003eVALUE\u003c/strong\u003e columns must be present. The order of columns may be changed.\u003c/li\u003e\n\u003cli\u003eOptionally the columns \u003cstrong\u003eERROR\u003c/strong\u003e and \u003cstrong\u003eCOMMENTS\u003c/strong\u003e may be present\u003c/li\u003e\n\u003cli\u003eISO date format must be used: \u0026lsquo;yyyy-mm-dd\u0026rsquo; or \u0026lsquo;yyyy-mm-dd hh:mm\u0026rsquo;\u003c/li\u003e\n\u003cli\u003eSemicolon (;) must be used as column separator\u003c/li\u003e\n\u003cli\u003ePoint (.) must be used as decimal separator\u003c/li\u003e\n\u003cli\u003eThe comment must not contain any semicolons\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"example\"\u003eExample\u003c/h4\u003e\n\u003cp\u003eThe two examples below are equvalent and result in identical data after importing to ResInsight\u003c/p\u003e\n\u003cp\u003eLine based CSV:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eDATE       ;VECTOR ;VALUE ;ERROR\r\n2018-04-16 ;FOPT   ;12.5  ;0.45\r\n2018-04-18 ;FOPT   ;8.6   ;0.31\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eNormal CSV:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eDATE       ;FOPT ;ERR:FOPT\r\n2018-04-16 ;12.5 ;0.45\r\n2018-04-18 ;8.6  ;0.31\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"import-rsm-observed-time-history-data\"\u003eImport RSM observed time history data\u003c/h3\u003e\n\u003cp\u003eTo import RSM files, the only action needed from the user is to select one or more RSM files. When the import is finished, one tree node for each file will appear under the \u003cstrong\u003eObserved Time History Data\u003c/strong\u003e node in the project tree. RSM files can be either \u003cem\u003eColumn based\u003c/em\u003e or \u003cem\u003eKeyword based\u003c/em\u003e.\u003c/p\u003e\n\u003ch4 id=\"column-based-file-format\"\u003eColumn Based File Format\u003c/h4\u003e\n\u003cp\u003eIf a column based file is presented, ResInsight first tries to identify if its header has fixed width or not. Further, the header is interpreted by looking for specific lines.\u003c/p\u003e\n\u003cp\u003eThe first line must have one or more vector mnemonics. The initial letter(s) in a mnemonic specify which summary data type the column represents. For instance, \u003cem\u003eFVPT\u003c/em\u003e and \u003cem\u003eFWPT\u003c/em\u003e are of type \u003cem\u003eField\u003c/em\u003e, as they both have an initial \u003cem\u003eF\u003c/em\u003e. \u003cem\u003eWWCTH\u003c/em\u003e and \u003cem\u003eWGORH\u003c/em\u003e are well data types. See \u003cem\u003eVector naming convention\u003c/em\u003e in \u003cstrong\u003eEclipse: File Formats Reference Manual\u003c/strong\u003e for a full overview of supported mnemonics.\u003c/p\u003e\n\u003cp\u003eThe next lines can define units, well/group names, region names, LGR names and block numbers and the local cell number. They do not have to appear in any particular order. Scale factors can also be included, but will be ignored by ResInsight. All lines starting with \u003cem\u003e\u003cem\u003e\u0026ndash;\u003c/em\u003e\u003c/em\u003e will also be ignored.\u003c/p\u003e\n\u003ch5 id=\"column-based-with-fixed-header-width\"\u003eColumn Based with Fixed Header Width\u003c/h5\u003e\n\u003cp\u003eWhen interpreting column based files with fixed header width, ResInsight looks for left aligned column entries. These type of files are interpreted as we naturally read them. More than one table can be present in each file.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e1                                                                                                      \r\n -------------------------------------------------------------------------\r\n SUMMARY\r\n -------------------------------------------------------------------------\r\n DATE         FGIRH        FVPT         FWPT         FOPT         FLPT  \r\n              SM3/DAY      RM3          SM3          SM3          SM3    \r\n                           *10**3       *10**3       *10**3       *10**3 \r\n                                                                         \r\n                                                                         \r\n -------------------------------------------------------------------------\r\n  6-NOV-1997         0            0            0            0            0 \r\n  7-NOV-1997         0     5.749954     0.004548     4.379801     4.384350  \r\n  8-NOV-1997         0     13.76883     0.010841     10.48852     10.49936\r\n  9-NOV-1997         0     19.38692     0.015243     14.76847     14.78372  \r\n 10-NOV-1997         0     24.07161     0.018914     18.33751     18.35642\r\n 11-NOV-1997         0     28.79427     0.022613     21.93558     21.95819\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch5 id=\"column-based-with-random-header-width\"\u003eColumn Based with Random Header Width\u003c/h5\u003e\n\u003cp\u003eColumn Based with Random Header Width will try to be parsed in the same way as fixed width, but it might fail in situations like the one below. We can see that SM3/SM3 \u003cem\u003eprobably\u003c/em\u003e belongs to WGORH, but it is parsed to WWCTH, as it is the second entry on that line.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eTIME      WWCTH      WGORH\r\nDAYS               SM3/SM3          \r\n\r\n          A-5HP          A-5HP\r\n     1     0.000   0.000\r\n     2     0.000   0.000\r\n     3     0.000   0.000\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch4 id=\"keyword-based-file-format\"\u003eKeyword Based File Format\u003c/h4\u003e\n\u003cp\u003eIf the non-comment line includes the word \u0026ldquo;VECTOR\u0026rdquo;, the file is interpreted as a keyword based file. In keyword based files, the content of the one-column tables is described in each header. Tables should be associated with a table containing time stamps. In the example below, \u003cem\u003eS-1AH-GOR\u003c/em\u003e is associated with \u003cem\u003eYEARX\u003c/em\u003e, since their origin is equal. ResInsight always interpret \u003cem\u003eORIGIN\u003c/em\u003e as well name, and look for a table with the line \u0026ldquo;VECTOR YEARX\u0026rdquo; to associate with it.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e----------------------------------------------\r\n-- GOR data \r\n----------------------------------------------\r\nVECTOR S-122AH-GOR\r\nUNITS SM3/SM3\r\nORIGIN GORS-122AH\r\n330.6601\r\n257.7500\r\n335.9894\r\n301.4388\r\n260.4193\r\n306.0298\r\n280.2883\r\n\r\nVECTOR YEARX\r\nORIGIN GORS-112AH\r\nUNITS YEAR\r\n1999.7902\r\n1999.8446\r\n1999.9285\r\n2000.0391\r\n2000.0800\r\n2000.0862\r\n2000.1285\r\n---comment\r\n\r\n\r\n----------------------------------------------\r\n-- GOR data\r\n----------------------------------------------\r\nVECTOR S-211H-GOR\r\nUNITS SM3/SM3\r\nORIGIN GORS-211H\r\n293.8103\r\n293.1634\r\n304.0000\r\n334.5932\r\n306.4610\r\n293.7571\r\n\r\nVECTOR YEARX\r\nORIGIN GORS-22H\r\nUNITS YEAR\r\n1999.8255\r\n2000.1274\r\n2000.2075\r\n2000.2367\r\n2000.4033\r\n2000.4966\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003ePlease seek \u0026ldquo;User data file formats\u0026rdquo; in \u003cstrong\u003eEclipse: File Formats Reference Manual\u003c/strong\u003e for details.\u003c/p\u003e\n\u003ch2 id=\"viewing-observed-time-history-data\"\u003eViewing Observed Time History Data\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/observedDataCurveCreator.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo plot Observed Time History Data, choose \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e in the right-click menu of \u003cstrong\u003eSummary Plots\u003c/strong\u003e, in \u003cstrong\u003ePlot Object Project Tree\u003c/strong\u003e. Observed time history data will appear in \u003cstrong\u003eSources\u003c/strong\u003e together with summary cases. How to use the Plot Editor is covered in \u003ca href=\"/plot-window/summaryploteditor/\"\u003eSummary Plot Editor\u003c/a\u003e. Observed time history data points are plotted without lines by default.\u003c/p\u003e\n",
                 url:      "/import/observeddata/"
             };
         
@@ -2110,7 +2143,7 @@ if (!doNotTrack) {
             window.store["/plot-window/"] = {
                 title:    "Plot Main Window",
                 content:  "This is the main window of ResInsight for 2D graphing and plotting. As seen, the Plot Main Window has a central area and two docking windows surrounding it. The docking windows cover the following:\n Plot Project Tree \u0026ndash; contains all application objects in a tree structure. Property Editor \u0026ndash; displays all properties for the selected object in the Project Tree  A selected subset of actions are presented as controls in the toolbar. The following subchapters describe the functionality, graphs, and plots of the Plot Main Window.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightMainPlotMediumSize.png\" alt=\"ResInsight User Interface\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis is the main window of ResInsight for 2D graphing and plotting. As seen, the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e has a central area\nand two docking windows surrounding it. The docking windows cover the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Project Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for the selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eA selected subset of actions are presented as controls in the toolbar.\nThe following subchapters describe the functionality, graphs, and plots of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightMainPlotMediumSize.png\" alt=\"ResInsight User Interface\"\u003e\u003c/p\u003e\n\u003cp\u003eThis is the main window of ResInsight for 2D graphing and plotting. As seen, the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e has a central area \nand two docking windows surrounding it. The docking windows cover the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Project Tree\u003c/strong\u003e \u0026ndash; contains all application objects in a tree structure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e \u0026ndash; displays all properties for the selected object in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eA selected subset of actions are presented as controls in the toolbar. \nThe following subchapters describe the functionality, graphs, and plots of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/"
             };
         
@@ -2118,8 +2151,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/resultcolorlegend/"] = {
                 title:    "Result Color Legend",
-                content:  "The color mapping of the displayed cell result is controlled by the Color Legend located below a result node in the Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.\n Number of levels \u0026ndash; Defines the number of tick marks displayed next to the color legend Significant digits \u0026ndash; Defines the number of significant digits in the number formatting Number format \u0026ndash; Defines how the numbers are formatted Colors \u0026ndash; Defines the color palette Mapping \u0026ndash; This option defines how the values are mapped onto the color distribution  Discrete Linear \u0026ndash; Legend divided into linear levels defined by Number of levels Continuous Linear \u0026ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic \u0026ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic \u0026ndash; Logarithmic legend divided into levels defined by Number of levels Category \u0026ndash; Special legend with one level for each category, either integer values or formation names.\nOnly available for result names ending with NUM or formation names.  Range type  All Timesteps \u0026ndash; values for all time steps are used to find min and max value of the result values represented by the color legend.\n(Not available for Flow Diagnostics results) Current Timestep \u0026ndash; use current (one) time step to find min and max values\n User Defined Range \u0026ndash; user specifies numeric values for min and max\n   Furthermore the legend can have a semi-transparent background applied to it by selecting the *Show Box around Legends option in the Preferences dialog.\n",
-                html:     "\u003cp\u003eThe color mapping of the displayed cell result is controlled by the \u003cstrong\u003eColor Legend\u003c/strong\u003e located below a result node in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_configuration.PNG\" alt=\"Legend Configuration\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of levels\u003c/strong\u003e \u0026ndash; Defines the number of tick marks displayed next to the color legend\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSignificant digits\u003c/strong\u003e \u0026ndash; Defines the number of significant digits in the number formatting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber format\u003c/strong\u003e \u0026ndash; Defines how the numbers are formatted\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e \u0026ndash; Defines the color palette\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMapping\u003c/strong\u003e \u0026ndash; This option defines how the values are mapped onto the color distribution\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDiscrete Linear\u003c/strong\u003e \u0026ndash; Legend divided into linear levels defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eContinuous Linear\u003c/strong\u003e \u0026ndash; Continuous linear legend with tick mark count defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eContinuous Logarithmic\u003c/strong\u003e \u0026ndash; Continuous logarithmic legend with tick mark count defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiscrete Logarithmic\u003c/strong\u003e \u0026ndash; Logarithmic legend divided into levels defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCategory\u003c/strong\u003e \u0026ndash; Special legend with one level for each category, either integer values or formation names.\u003cbr /\u003e\nOnly available for result names ending with \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e or formation names.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRange type\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Timesteps\u003c/strong\u003e \u0026ndash; values for all time steps are used to find min and max value of\nthe result values represented by the color legend.\u003cbr /\u003e\n(Not available for Flow Diagnostics results)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Timestep\u003c/strong\u003e \u0026ndash; use current (one) time step to find min and max values\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Range\u003c/strong\u003e \u0026ndash; user specifies numeric values for min and max\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eFurthermore the legend can have a semi-transparent background applied to it by selecting the *\u003cem\u003eShow Box around Legends\u003c/em\u003e option in the Preferences dialog.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_background.png\" alt=\"Legend Background\" /\u003e \u003cimg src=\"/images/3d-main-window/legend_with_background.png\" alt=\"Show Box around legends\" /\u003e\u003c/p\u003e\n",
+                content:  "The color mapping of the displayed cell result is controlled by the Color Legend located below a result node in the Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.\n Number of levels \u0026ndash; Defines the number of tick marks displayed next to the color legend Significant digits \u0026ndash; Defines the number of significant digits in the number formatting Number format \u0026ndash; Defines how the numbers are formatted Colors \u0026ndash; Defines the color palette Mapping \u0026ndash; This option defines how the values are mapped onto the color distribution  Discrete Linear \u0026ndash; Legend divided into linear levels defined by Number of levels Continuous Linear \u0026ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic \u0026ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic \u0026ndash; Logarithmic legend divided into levels defined by Number of levels Category \u0026ndash; Special legend with one level for each category, either integer values or formation names.\nOnly available for result names ending with NUM or formation names.   Range type  All Timesteps \u0026ndash; values for all time steps are used to find min and max value of the result values represented by the color legend.\n(Not available for Flow Diagnostics results) Current Timestep \u0026ndash; use current (one) time step to find min and max values User Defined Range \u0026ndash; user specifies numeric values for min and max    Furthermore the legend can have a semi-transparent background applied to it by selecting the *Show Box around Legends option in the Preferences dialog.\n",
+                html:     "\u003cp\u003eThe color mapping of the displayed cell result is controlled by the \u003cstrong\u003eColor Legend\u003c/strong\u003e located below a result node in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The legend can be shown or hidden by checking or unchecking the box in front of the Legend Definition.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_configuration.PNG\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of levels\u003c/strong\u003e \u0026ndash; Defines the number of tick marks displayed next to the color legend\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSignificant digits\u003c/strong\u003e \u0026ndash; Defines the number of significant digits in the number formatting\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber format\u003c/strong\u003e \u0026ndash; Defines how the numbers are formatted\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e \u0026ndash; Defines the color palette\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMapping\u003c/strong\u003e \u0026ndash; This option defines how the values are mapped onto the color distribution\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDiscrete Linear\u003c/strong\u003e \u0026ndash; Legend divided into linear levels defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eContinuous Linear\u003c/strong\u003e \u0026ndash; Continuous linear legend with tick mark count defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eContinuous Logarithmic\u003c/strong\u003e \u0026ndash; Continuous logarithmic legend with tick mark count defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiscrete Logarithmic\u003c/strong\u003e \u0026ndash; Logarithmic legend divided into levels defined by \u003cstrong\u003eNumber of levels\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCategory\u003c/strong\u003e \u0026ndash; Special legend with one level for each category, either integer values or formation names.\u003cbr\u003e\nOnly available for result names ending with \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e or formation names.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRange type\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Timesteps\u003c/strong\u003e \u0026ndash; values for all time steps are used to find min and max value of \nthe result values represented by the color legend.\u003cbr\u003e\n(Not available for Flow Diagnostics results)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Timestep\u003c/strong\u003e \u0026ndash; use current (one) time step to find min and max values\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Range\u003c/strong\u003e \u0026ndash; user specifies numeric values for min and max\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFurthermore the legend can have a semi-transparent background applied to it by selecting the *\u003cem\u003eShow Box around Legends\u003c/em\u003e option in the Preferences dialog.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_background.png\" alt=\"Legend Background\"\u003e \u003cimg src=\"/images/3d-main-window/legend_with_background.png\" alt=\"Show Box around legends\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/resultcolorlegend/"
             };
         
@@ -2127,8 +2160,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryploteditor/"] = {
                 title:    "Summary Plot Editor",
-                content:  " The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.\nThe upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the Summary Type currently highlighted.\nIn this context highlighted means the marked item with a different background color, while selected means an item or items that have a ticked check box.\n\rSelection Fields This section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.\nSources This field contains all imported cases and ensembles. Select the case(s) and/or ensemble(s) to display in the plot.\nSummary Types and Item Selection Fields In the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.\n Field \u0026ndash; Select Field related vectors only Aquifer \u0026ndash; Select Aquifer category vectors only Network \u0026ndash; Select Network category vectors only\n Misc \u0026ndash; Select vectors in the Misc category only Region \u0026ndash; Select Region related vectors only\n Region number \u0026ndash; Select the Region number  Region-Region \u0026ndash; Select Region to Region related vectors only\n Region numbers \u0026ndash; Select the Region to Region numbers  Group - Select Group related vectors only  Group name \u0026ndash; Select Group name  Well \u0026ndash; Select Well related vectors only  Well name \u0026ndash; Select Well name  Completion \u0026ndash; Select Completion related vectors only  Well name \u0026ndash; Select Well name I, J, K \u0026ndash; Select the I, J, K values of the completion  Lgr-Completion \u0026ndash; Select Completion in LGR related vectors only  Well name \u0026ndash; Select Well name Lgr name \u0026ndash; Select Lgr name I, J, K \u0026ndash; Select the I, J, K values of the completion in the Lgr.  Lgr-Well \u0026ndash; Select Well in LGR related vectors only  Well name \u0026ndash; Select Well name Lgr name \u0026ndash; Select Lgr name  Segment \u0026ndash; Select Segment related vectors only  Well name \u0026ndash; Select Well name Segment number \u0026ndash; Select the segment number  Block \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only  I, J, K \u0026ndash; Select the I, J, K values of the Block.  Lgr-Block \u0026ndash; Select I, J, K - Block in LGR related vectors only  Lgr name \u0026ndash; Select Lgr name I, J, K \u0026ndash; Select the I, J, K values of the Block in the Lgr.  Calculated \u0026ndash; Select calculated vectors created by the curve calculator. Imported \u0026ndash; Select observed data vectors imported from file (e.g. CSV, RSM files)  Summaries This field contains the summaries/vectors for the highlighted summary category.\nPreview Plot When a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the Curve Name Configuration and Curve Appearance Assignment fields.\nPlot and Curve Name Configuration The checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.\nCurve Appearance Assignment Curves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.\nThese assignments can be controlled using the options in the Curve Appearance Assignment group.\nWhen set to Auto, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.\nWhen disabling the Auto option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.\nThe Apply button must be clicked to apply the new settings to all curves.\nThe curve appearance settings apply to single summary curves only and do not affect ensemble curve sets. Curve sets receive their appearance automatically from a set of color ranges.\nAssignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps. Press the Apply button to apply consistent appearance settings according to the current curve selection.\n\rCurves The curves field displays all summary curves and ensemble curve sets matching the settings in the selection fields. Those are separated in two groups, Summary Curves and Ensemble Curve Sets. The check box at each item controls which items are displayed in the preview plot.\nIf the user make a selection that will result in a huge number of ensemble curves, ResInsight will display a drawing performance warning, and the newly created curve set(s) are toggled off by default.\nTarget Plot In the bottom of the dialog window Target Plot may be specified. The target plot is the summary plot that will receive the selected curves when the OK or Apply button is clicked.\nBy default the target plot is set to (new plot) or to the plot selected for editing when invoking the command.\nSetting the target plot to a different plot will add the selected curves to that plot when pressing the the OK or Apply button.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.\u003c/p\u003e\n\n\u003cp\u003eThe upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the \u003cstrong\u003eSummary Type\u003c/strong\u003e currently highlighted.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eIn this context \u003cb\u003ehighlighted\u003c/b\u003e means the marked item with a different background color, while \u003cb\u003eselected\u003c/b\u003e means an item or items that have a ticked check box.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"selection-fields\"\u003eSelection Fields\u003c/h2\u003e\n\n\u003cp\u003eThis section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.\u003c/p\u003e\n\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\n\u003cp\u003eThis field contains all imported cases and ensembles. Select the case(s) and/or ensemble(s) to display in the plot.\u003c/p\u003e\n\n\u003ch3 id=\"summary-types-and-item-selection-fields\"\u003eSummary Types and Item Selection Fields\u003c/h3\u003e\n\n\u003cp\u003eIn the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eField\u003c/strong\u003e \u0026ndash; Select Field related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer\u003c/strong\u003e \u0026ndash; Select Aquifer category vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNetwork\u003c/strong\u003e \u0026ndash; Select Network category vectors only\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMisc\u003c/strong\u003e \u0026ndash; Select vectors in the Misc category only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e \u0026ndash; Select Region related vectors only\u003cbr /\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRegion number\u003c/strong\u003e \u0026ndash; Select the Region number\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion-Region\u003c/strong\u003e \u0026ndash; Select Region to Region related vectors only\u003cbr /\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRegion numbers\u003c/strong\u003e \u0026ndash; Select the Region to Region numbers\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup\u003c/strong\u003e - Select Group related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGroup name\u003c/strong\u003e \u0026ndash;  Select Group name\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e \u0026ndash; Select Well related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletion\u003c/strong\u003e   \u0026ndash; Select Completion related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the completion\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Completion\u003c/strong\u003e \u0026ndash; Select Completion in LGR related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the completion in the Lgr.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Well\u003c/strong\u003e \u0026ndash; Select Well in LGR related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash; Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment\u003c/strong\u003e \u0026ndash; Select Segment related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash; Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment number\u003c/strong\u003e \u0026ndash; Select the segment number\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBlock\u003c/strong\u003e \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the Block.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Block\u003c/strong\u003e \u0026ndash; Select I, J, K - Block in LGR related vectors only\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the Block in the Lgr.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCalculated\u003c/strong\u003e \u0026ndash; Select calculated vectors created by the \u003ca href=\"/plot-window/curvecalculator/\"\u003ecurve calculator\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImported\u003c/strong\u003e \u0026ndash; Select observed data vectors \u003ca href=\"/import/observeddata/\"\u003eimported from file\u003c/a\u003e (e.g. CSV, RSM files)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"summaries\"\u003eSummaries\u003c/h3\u003e\n\n\u003cp\u003eThis field contains the summaries/vectors for the highlighted summary category.\u003c/p\u003e\n\n\u003ch2 id=\"preview-plot\"\u003ePreview Plot\u003c/h2\u003e\n\n\u003cp\u003eWhen a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the \u003cem\u003eCurve Name Configuration\u003c/em\u003e and \u003cem\u003eCurve Appearance Assignment\u003c/em\u003e fields.\u003c/p\u003e\n\n\u003ch3 id=\"plot-and-curve-name-configuration\"\u003ePlot and Curve Name Configuration\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CurveNameConfig.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.\u003c/p\u003e\n\n\u003ch3 id=\"curve-appearance-assignment\"\u003eCurve Appearance Assignment\u003c/h3\u003e\n\n\u003cp\u003eCurves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.\u003c/p\u003e\n\n\u003cp\u003eThese assignments can be controlled using the options in the \u003cstrong\u003eCurve Appearance Assignment\u003c/strong\u003e group.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CurveAppearanceAssignment.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen set to \u003cstrong\u003eAuto\u003c/strong\u003e, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.\u003c/p\u003e\n\n\u003cp\u003eWhen disabling the \u003cstrong\u003eAuto\u003c/strong\u003e option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eApply\u003c/strong\u003e button must be clicked to apply the new settings to all curves.\u003c/p\u003e\n\n\u003cp\u003eThe curve appearance settings apply to single summary curves only and do not affect ensemble curve sets. Curve sets receive their appearance automatically from a set of color ranges.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eAssignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps.\nPress the \u003cb\u003eApply\u003c/b\u003e button to apply consistent appearance settings according to the current curve selection.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"curves\"\u003eCurves\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPreviewCurves.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe curves field displays all summary curves and ensemble curve sets matching the settings in the selection fields. Those are separated in two groups, \u003cstrong\u003eSummary Curves\u003c/strong\u003e and \u003cstrong\u003eEnsemble Curve Sets\u003c/strong\u003e. The check box at each item controls which items are displayed in the preview plot.\u003c/p\u003e\n\n\u003cp\u003eIf the user make a selection that will result in a huge number of ensemble curves, ResInsight will display a drawing performance warning, and the newly created curve set(s) are toggled off by default.\u003c/p\u003e\n\n\u003ch3 id=\"target-plot\"\u003eTarget Plot\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/TargetPlot_new.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/TargetPlot_1.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn the bottom of the dialog window \u003cstrong\u003eTarget Plot\u003c/strong\u003e may be specified. The target plot is the summary plot that will receive the selected curves when the \u003cstrong\u003eOK\u003c/strong\u003e or \u003cstrong\u003eApply\u003c/strong\u003e button is clicked.\u003c/p\u003e\n\n\u003cp\u003eBy default the target plot is set to \u003cstrong\u003e(new plot)\u003c/strong\u003e or to the plot selected for editing when invoking the command.\u003c/p\u003e\n\n\u003cp\u003eSetting the target plot to a different plot will add the selected curves to that plot when pressing the the \u003cstrong\u003eOK\u003c/strong\u003e or \u003cstrong\u003eApply\u003c/strong\u003e button.\u003c/p\u003e\n",
+                content:  "The plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.\nThe upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the Summary Type currently highlighted.\nIn this context highlightedmeans the marked item with a different background color, while selectedmeans an item or items that have a ticked check box.\n\rSelection Fields This section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.\nSources This field contains all imported cases and ensembles. Select the case(s) and/or ensemble(s) to display in the plot.\nSummary Types and Item Selection Fields In the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.\n Field \u0026ndash; Select Field related vectors only Aquifer \u0026ndash; Select Aquifer category vectors only Network \u0026ndash; Select Network category vectors only Misc \u0026ndash; Select vectors in the Misc category only Region \u0026ndash; Select Region related vectors only  Region number \u0026ndash; Select the Region number   Region-Region \u0026ndash; Select Region to Region related vectors only  Region numbers \u0026ndash; Select the Region to Region numbers   Group - Select Group related vectors only  Group name \u0026ndash; Select Group name   Well \u0026ndash; Select Well related vectors only  Well name \u0026ndash; Select Well name   Completion \u0026ndash; Select Completion related vectors only  Well name \u0026ndash; Select Well name I, J, K \u0026ndash; Select the I, J, K values of the completion   Lgr-Completion \u0026ndash; Select Completion in LGR related vectors only  Well name \u0026ndash; Select Well name Lgr name \u0026ndash; Select Lgr name I, J, K \u0026ndash; Select the I, J, K values of the completion in the Lgr.   Lgr-Well \u0026ndash; Select Well in LGR related vectors only  Well name \u0026ndash; Select Well name Lgr name \u0026ndash; Select Lgr name   Segment \u0026ndash; Select Segment related vectors only  Well name \u0026ndash; Select Well name Segment number \u0026ndash; Select the segment number   Block \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only  I, J, K \u0026ndash; Select the I, J, K values of the Block.   Lgr-Block \u0026ndash; Select I, J, K - Block in LGR related vectors only  Lgr name \u0026ndash; Select Lgr name I, J, K \u0026ndash; Select the I, J, K values of the Block in the Lgr.   Calculated \u0026ndash; Select calculated vectors created by the curve calculator. Imported \u0026ndash; Select observed data vectors imported from file (e.g. CSV, RSM files)  Summaries This field contains the summaries/vectors for the highlighted summary category.\nPreview Plot When a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the Curve Name Configuration and Curve Appearance Assignment fields.\nPlot and Curve Name Configuration The checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.\nCurve Appearance Assignment Curves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.\nThese assignments can be controlled using the options in the Curve Appearance Assignment group.\nWhen set to Auto, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.\nWhen disabling the Auto option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.\nThe Apply button must be clicked to apply the new settings to all curves.\nThe curve appearance settings apply to single summary curves only and do not affect ensemble curve sets. Curve sets receive their appearance automatically from a set of color ranges.\nAssignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps. Press the Applybutton to apply consistent appearance settings according to the current curve selection.\n\rCurves The curves field displays all summary curves and ensemble curve sets matching the settings in the selection fields. Those are separated in two groups, Summary Curves and Ensemble Curve Sets. The check box at each item controls which items are displayed in the preview plot.\nIf the user make a selection that will result in a huge number of ensemble curves, ResInsight will display a drawing performance warning, and the newly created curve set(s) are toggled off by default.\nTarget Plot In the bottom of the dialog window Target Plot may be specified. The target plot is the summary plot that will receive the selected curves when the OK or Apply button is clicked.\nBy default the target plot is set to (new plot) or to the plot selected for editing when invoking the command.\nSetting the target plot to a different plot will add the selected curves to that plot when pressing the the OK or Apply button.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe plot editor is a separate ResInsight dialog window where the user can select which vectors to display in a summary plot. It is also possible to edit an existing plot in this editor.\u003c/p\u003e\n\u003cp\u003eThe upper part of the editor contains editors for selecting which vectors/summaries to display in the plot. The number of fields vary from 3 to 6 depending on the \u003cstrong\u003eSummary Type\u003c/strong\u003e currently highlighted.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eIn this context \u003c!-- raw HTML omitted --\u003ehighlighted\u003c!-- raw HTML omitted --\u003e means the marked item with a different background color, while \u003c!-- raw HTML omitted --\u003eselected\u003c!-- raw HTML omitted --\u003e means an item or items that have a ticked check box.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"selection-fields\"\u003eSelection Fields\u003c/h2\u003e\n\u003cp\u003eThis section describes the different selection fields in the selection part of the plot editor. A complete/valid vector selection consists of a selected source, a selected summary category, a selected item in each dynamic field (if any) and a selected vector among the Summaries.\u003c/p\u003e\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\u003cp\u003eThis field contains all imported cases and ensembles. Select the case(s) and/or ensemble(s) to display in the plot.\u003c/p\u003e\n\u003ch3 id=\"summary-types-and-item-selection-fields\"\u003eSummary Types and Item Selection Fields\u003c/h3\u003e\n\u003cp\u003eIn the mid-section of the dialog, the Summary Type and the corresponding Items can be selected.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eField\u003c/strong\u003e \u0026ndash; Select Field related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer\u003c/strong\u003e \u0026ndash; Select Aquifer category vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNetwork\u003c/strong\u003e \u0026ndash; Select Network category vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMisc\u003c/strong\u003e \u0026ndash; Select vectors in the Misc category only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e \u0026ndash; Select Region related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRegion number\u003c/strong\u003e \u0026ndash; Select the Region number\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion-Region\u003c/strong\u003e \u0026ndash; Select Region to Region related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRegion numbers\u003c/strong\u003e \u0026ndash; Select the Region to Region numbers\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup\u003c/strong\u003e - Select Group related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGroup name\u003c/strong\u003e \u0026ndash;  Select Group name\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e \u0026ndash; Select Well related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletion\u003c/strong\u003e   \u0026ndash; Select Completion related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the completion\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Completion\u003c/strong\u003e \u0026ndash; Select Completion in LGR related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash;  Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the completion in the Lgr.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Well\u003c/strong\u003e \u0026ndash; Select Well in LGR related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash; Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment\u003c/strong\u003e \u0026ndash; Select Segment related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell name\u003c/strong\u003e \u0026ndash; Select Well name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment number\u003c/strong\u003e \u0026ndash; Select the segment number\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBlock\u003c/strong\u003e \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the Block.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Block\u003c/strong\u003e \u0026ndash; Select I, J, K - Block in LGR related vectors only\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLgr name\u003c/strong\u003e \u0026ndash; Select Lgr name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eI, J, K\u003c/strong\u003e \u0026ndash; Select the I, J, K values of the Block in the Lgr.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCalculated\u003c/strong\u003e \u0026ndash; Select calculated vectors created by the \u003ca href=\"/plot-window/curvecalculator/\"\u003ecurve calculator\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImported\u003c/strong\u003e \u0026ndash; Select observed data vectors \u003ca href=\"/import/observeddata/\"\u003eimported from file\u003c/a\u003e (e.g. CSV, RSM files)\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"summaries\"\u003eSummaries\u003c/h3\u003e\n\u003cp\u003eThis field contains the summaries/vectors for the highlighted summary category.\u003c/p\u003e\n\u003ch2 id=\"preview-plot\"\u003ePreview Plot\u003c/h2\u003e\n\u003cp\u003eWhen a complete/valid vector exists, one or more curves will appear in the preview plot. Each curve will also have a corresponding item in the curves field in the lower left corner. Visibility for the curves may be controlled by the checkboxes. Each curve is automatically assigned a name and appearance. However the user may modify these settings in the \u003cem\u003eCurve Name Configuration\u003c/em\u003e and \u003cem\u003eCurve Appearance Assignment\u003c/em\u003e fields.\u003c/p\u003e\n\u003ch3 id=\"plot-and-curve-name-configuration\"\u003ePlot and Curve Name Configuration\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CurveNameConfig.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe checkboxes in this field control which information elements to include in the curve name. Toggling some of the checkboxes will have no effect on some curves depending on which information elements are relevant for each curve.\u003c/p\u003e\n\u003ch3 id=\"curve-appearance-assignment\"\u003eCurve Appearance Assignment\u003c/h3\u003e\n\u003cp\u003eCurves created are assigned individual visual properties like colors and symbols in a systematic manner to make the plots easy to read. Different aspects of the vectors are assigned to different curve appearances. E.g. using symbols to distinguish cases, while using colors to distinguish quantity.\u003c/p\u003e\n\u003cp\u003eThese assignments can be controlled using the options in the \u003cstrong\u003eCurve Appearance Assignment\u003c/strong\u003e group.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CurveAppearanceAssignment.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen set to \u003cstrong\u003eAuto\u003c/strong\u003e, ResInsight assigns visual properties based on the present vector categories and the number of different values in each category.\u003c/p\u003e\n\u003cp\u003eWhen disabling the \u003cstrong\u003eAuto\u003c/strong\u003e option, you can select which of the visual curve properties to use for which summary category. The summary category that currently can be used is Case, Vector, Well, Group and Region. The visual properties supported types are Color, Symbols, Line Style, Gradient and Line Thickness.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eApply\u003c/strong\u003e button must be clicked to apply the new settings to all curves.\u003c/p\u003e\n\u003cp\u003eThe curve appearance settings apply to single summary curves only and do not affect ensemble curve sets. Curve sets receive their appearance automatically from a set of color ranges.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eAssignment of curve appearance are incremental, and can end up as sub optimal if adding curves in several steps.\nPress the \u003c!-- raw HTML omitted --\u003eApply\u003c!-- raw HTML omitted --\u003e button to apply consistent appearance settings according to the current curve selection.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"curves\"\u003eCurves\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPreviewCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe curves field displays all summary curves and ensemble curve sets matching the settings in the selection fields. Those are separated in two groups, \u003cstrong\u003eSummary Curves\u003c/strong\u003e and \u003cstrong\u003eEnsemble Curve Sets\u003c/strong\u003e. The check box at each item controls which items are displayed in the preview plot.\u003c/p\u003e\n\u003cp\u003eIf the user make a selection that will result in a huge number of ensemble curves, ResInsight will display a drawing performance warning, and the newly created curve set(s) are toggled off by default.\u003c/p\u003e\n\u003ch3 id=\"target-plot\"\u003eTarget Plot\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/TargetPlot_new.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/TargetPlot_1.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the bottom of the dialog window \u003cstrong\u003eTarget Plot\u003c/strong\u003e may be specified. The target plot is the summary plot that will receive the selected curves when the \u003cstrong\u003eOK\u003c/strong\u003e or \u003cstrong\u003eApply\u003c/strong\u003e button is clicked.\u003c/p\u003e\n\u003cp\u003eBy default the target plot is set to \u003cstrong\u003e(new plot)\u003c/strong\u003e or to the plot selected for editing when invoking the command.\u003c/p\u003e\n\u003cp\u003eSetting the target plot to a different plot will add the selected curves to that plot when pressing the the \u003cstrong\u003eOK\u003c/strong\u003e or \u003cstrong\u003eApply\u003c/strong\u003e button.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryploteditor/"
             };
         
@@ -2136,8 +2169,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/comparisonview/"] = {
                 title:    "Comparison View",
-                content:  " ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\nThe figure above exemplifies a Comparison View for comparison of two different simulations models and results. The left hand side is used to display grid and results of an Eclipse simulation while the right hand side displays an ABAQUS grid and simulation results from geomechanical analysis.\nA different way to use the Comparison View is to compare the same geometrical grid with different Cell Results. Thus two cell results can easily be seen together in the same view.\nCreating a Comparison View A Comparison View can be created as follows:\n In Project Tree, select a view and specify Comparison View in the Viewer section of Property Editor Right-click a 3D View, and select Compare To\u0026hellip;  Comparison View Divider In the figure below, the Comparison View is used to compare two different grids in the same view, one to the left and the other to the right of the divider between them. The screen aligned divider is possible to drag right and left by clicking the handle marked by a green circle.\nView Properties and Settings Properties of an individual view included in a Comparison View are controlled by their respective settings, notably 3D Views, Cell Results, Result Color Legend, Cell Filters, and Intersections.\nSetting up Linked Views may also be relevant, e.g. to syncronize cell results and cell filters.\nPolyline Intersections does not facilitate picking points across the Comparison View divider. However, an intersection can be copied betweens views, see Intersections for details.\n\r",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonView.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight offers a \u003cstrong\u003eComparison View\u003c/strong\u003e to compare two existing views in terms of grid geometry, results, intersections and more.\nThe Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view.\nThis improves efficiency and simplifies the workflow when working with related but different models.\u003c/p\u003e\n\n\u003cp\u003eThe figure above exemplifies a Comparison View for comparison of two different simulations models and results.\nThe left hand side is used to display grid and results of an \u003ca href=\"/import/eclipsecases/\"\u003eEclipse simulation\u003c/a\u003e\nwhile the right hand side displays an ABAQUS grid and simulation results from \u003ca href=\"/import/geomechanicaldata/\"\u003egeomechanical analysis\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eA different way to use the Comparison View is to compare the same geometrical grid with different \u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e.\nThus two cell results can easily be seen together in the same view.\u003c/p\u003e\n\n\u003ch2 id=\"creating-a-comparison-view\"\u003eCreating a Comparison View\u003c/h2\u003e\n\n\u003cp\u003eA Comparison View can be created as follows:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eIn \u003cstrong\u003eProject Tree\u003c/strong\u003e, select a view and specify \u003cstrong\u003eComparison View\u003c/strong\u003e in the \u003cstrong\u003eViewer\u003c/strong\u003e section of \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eRight-click a 3D View, and select \u003cstrong\u003eCompare To\u0026hellip;\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonViewCreate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"comparison-view-divider\"\u003eComparison View Divider\u003c/h2\u003e\n\n\u003cp\u003eIn the figure below, the Comparison View is used to compare two different grids in the same view, one to the left and the other to the right of the  divider between them.  The screen aligned divider is  possible to drag right and left by clicking the handle marked by a green circle.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonViewDividerHandle.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"view-properties-and-settings\"\u003eView Properties and Settings\u003c/h2\u003e\n\n\u003cp\u003eProperties of an individual view included in a Comparison View are controlled by their respective settings, notably\n\u003ca href=\"/3d-main-window/3dviews/\"\u003e3D Views\u003c/a\u003e,\n\u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e,\n\u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e,\n\u003ca href=\"/3d-main-window/filters/\"\u003eCell Filters\u003c/a\u003e,\nand \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eSetting up \u003ca href=\"/3d-main-window/linkedviews/\"\u003eLinked Views\u003c/a\u003e may also be relevant, e.g. to syncronize \u003ca href=\"/3d-main-window/cellresults/\"\u003ecell results\u003c/a\u003e\nand \u003ca href=\"/3d-main-window/filters/\"\u003ecell filters\u003c/a\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003ca href=\"/3d-main-window/intersections/#polyline-intersection\"\u003ePolyline Intersections\u003c/a\u003e does not facilitate picking points across the Comparison View divider. However, an intersection can be copied betweens views, see \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e for details.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
+                content:  "ResInsight offers a Comparison View to compare two existing views in terms of grid geometry, results, intersections and more. The Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view. This improves efficiency and simplifies the workflow when working with related but different models.\nThe figure above exemplifies a Comparison View for comparison of two different simulations models and results. The left hand side is used to display grid and results of an Eclipse simulation while the right hand side displays an ABAQUS grid and simulation results from geomechanical analysis.\nA different way to use the Comparison View is to compare the same geometrical grid with different Cell Results. Thus two cell results can easily be seen together in the same view.\nCreating a Comparison View A Comparison View can be created as follows:\n In Project Tree, select a view and specify Comparison View in the Viewer section of Property Editor Right-click a 3D View, and select Compare To\u0026hellip;  Comparison View Divider In the figure below, the Comparison View is used to compare two different grids in the same view, one to the left and the other to the right of the divider between them. The screen aligned divider is possible to drag right and left by clicking the handle marked by a green circle.\nView Properties and Settings Properties of an individual view included in a Comparison View are controlled by their respective settings, notably 3D Views, Cell Results, Result Color Legend, Cell Filters, and Intersections.\nSetting up Linked Views may also be relevant, e.g. to syncronize cell results and cell filters.\nPolyline Intersections does not facilitate picking points across the Comparison View divider. However, an intersection can be copied betweens views, see Intersections for details.\n\r",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers a \u003cstrong\u003eComparison View\u003c/strong\u003e to compare two existing views in terms of grid geometry, results, intersections and more. \nThe Comparison View allows comparison of information of different grids and different solutions on the same grid in a single view.\nThis improves efficiency and simplifies the workflow when working with related but different models.\u003c/p\u003e\n\u003cp\u003eThe figure above exemplifies a Comparison View for comparison of two different simulations models and results. \nThe left hand side is used to display grid and results of an \u003ca href=\"/import/eclipsecases/\"\u003eEclipse simulation\u003c/a\u003e\nwhile the right hand side displays an ABAQUS grid and simulation results from \u003ca href=\"/import/geomechanicaldata/\"\u003egeomechanical analysis\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eA different way to use the Comparison View is to compare the same geometrical grid with different \u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e. \nThus two cell results can easily be seen together in the same view.\u003c/p\u003e\n\u003ch2 id=\"creating-a-comparison-view\"\u003eCreating a Comparison View\u003c/h2\u003e\n\u003cp\u003eA Comparison View can be created as follows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eIn \u003cstrong\u003eProject Tree\u003c/strong\u003e, select a view and specify \u003cstrong\u003eComparison View\u003c/strong\u003e in the \u003cstrong\u003eViewer\u003c/strong\u003e section of \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eRight-click a 3D View, and select \u003cstrong\u003eCompare To\u0026hellip;\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonViewCreate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"comparison-view-divider\"\u003eComparison View Divider\u003c/h2\u003e\n\u003cp\u003eIn the figure below, the Comparison View is used to compare two different grids in the same view, one to the left and the other to the right of the  divider between them.  The screen aligned divider is  possible to drag right and left by clicking the handle marked by a green circle.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3DComparisonViewDividerHandle.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"view-properties-and-settings\"\u003eView Properties and Settings\u003c/h2\u003e\n\u003cp\u003eProperties of an individual view included in a Comparison View are controlled by their respective settings, notably \n\u003ca href=\"/3d-main-window/3dviews/\"\u003e3D Views\u003c/a\u003e, \n\u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e, \n\u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e, \n\u003ca href=\"/3d-main-window/filters/\"\u003eCell Filters\u003c/a\u003e,\nand \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eSetting up \u003ca href=\"/3d-main-window/linkedviews/\"\u003eLinked Views\u003c/a\u003e may also be relevant, e.g. to syncronize \u003ca href=\"/3d-main-window/cellresults/\"\u003ecell results\u003c/a\u003e\nand \u003ca href=\"/3d-main-window/filters/\"\u003ecell filters\u003c/a\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003ca href=\"/3d-main-window/intersections/#polyline-intersection\"\u003ePolyline Intersections\u003c/a\u003e does not facilitate picking points across the Comparison View divider. However, an intersection can be copied betweens views, see \u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e for details.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
                 url:      "/3d-main-window/comparisonview/"
             };
         
@@ -2145,8 +2178,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/3dwelllogcurves/"] = {
                 title:    "3D Well Log Plots",
-                content:  " ResInsight can display well logs curves directly in the 3D view with a subset of the functionality of the full 2D Well Log Plot Editor. The curves will be drawn in a plane next to or centered on the well trajectory they belong to and can display well log data from a simulation model and from imported LAS-files.\nCreating new 3D Well Log Curves Add a new 3D well log curve by selecting a Well Path in the Project Tree, right-clicking and selecting 3D Well Log Curves and Add 3D Well Log Curve.\nDeleting 3D Well Log Curves Delete one or more 3D well log curves by selecting them in the project tree, right-clicking on one of the selected items and choosing Delete 3D Well Log Curve(s). The curves will be deleted with no further confirmation.\nConfigurating the 3D Well Log Curves 3D Track and Draw Plane Appearance Each 3D well log curve belongs to a 3D Track which in turn is attached to a well path. The 3D track itself contains some settings related to the display of the curves.\n   Parameter Description Range     Show Grid Show axis markers for the value-axis of the curves along the draw surface True/False   Show Background Draw a white background on the drawing surfaces of the curves True/False   Width Scaling A scaling factor applied to the width of the draw surfaces [0.25, 2.5]    Curve Configuration In addition to the 3D track configuration, each 3D well log curve may be configured in its Property Editor. Here settings are grouped into three categories: Data Selection, Appearance and Name Generation.\nData Selection The Curve Data configuration allows you to select a case, result type, property and time step to plot.\n   Parameter Description     Case The eclipse or geomechanical case to retrieve the data from   Result Type Dynamic, static, generated, input property, formation names, flow diagnostics or injection flooding   Result Property The parameter to plot   Time Step Which time step to show    Appearance In the Curve Appearance box, the curve can be assigned to a draw plane, the color can be changed and a range of curve values applied. The range of the result property can be set with the minimum and maximum curve value settings. The curve range is by default set to the minimum and maximum values found in the data set and these values are retained in the label if different values have been chosen.\nThe draw plane can be vertical (above well path, centered and below well path) and horizontal (left, centered and right). If multiple curves are added and assigned to the same draw plane, they will appear in the same curve plot.\nName Generation Finally the name of the curve is created automatically from a set of parameters such as case, view, etc. The parameters that should make up the curve name can be selected in the Curve Name box. Only extraction log curves have multiple settings here. The automatic name generation will be automatically switched off if the curve has been renamed manually and can be switched back on by checking the Generate Name Automatically tick box.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can display well logs curves directly in the 3D view with a subset of the functionality of the full \u003ca href=\"/plot-window/welllogsandplots/\"\u003e2D Well Log Plot Editor\u003c/a\u003e. The curves will be drawn in a plane next to or centered on the well trajectory they belong to and can display well log data from a simulation model and from imported LAS-files.\u003c/p\u003e\n\n\u003ch2 id=\"creating-new-3d-well-log-curves\"\u003eCreating new 3D Well Log Curves\u003c/h2\u003e\n\n\u003cp\u003eAdd a new 3D well log curve by selecting a Well Path in the Project Tree, right-clicking and selecting \u003cstrong\u003e3D Well Log Curves\u003c/strong\u003e and \u003cstrong\u003eAdd 3D Well Log Curve\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurvesCreate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"deleting-3d-well-log-curves\"\u003eDeleting 3D Well Log Curves\u003c/h2\u003e\n\n\u003cp\u003eDelete one or more 3D well log curves by selecting them in the project tree, right-clicking on one of the selected items and choosing \u003cstrong\u003eDelete 3D Well Log Curve(s)\u003c/strong\u003e. The curves will be deleted with no further confirmation.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurvesDelete.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"configurating-the-3d-well-log-curves\"\u003eConfigurating the 3D Well Log Curves\u003c/h2\u003e\n\n\u003ch3 id=\"3d-track-and-draw-plane-appearance\"\u003e3D Track and Draw Plane Appearance\u003c/h3\u003e\n\n\u003cp\u003eEach 3D well log curve belongs to a 3D Track which in turn is attached to a well path. The 3D track itself contains some settings related to the display of the curves.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_DrawPlaneAppearance.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eRange\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eShow Grid\u003c/td\u003e\n\u003ctd\u003eShow axis markers for the value-axis of the curves along the draw surface\u003c/td\u003e\n\u003ctd\u003eTrue/False\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eShow Background\u003c/td\u003e\n\u003ctd\u003eDraw a white background on the drawing surfaces of the curves\u003c/td\u003e\n\u003ctd\u003eTrue/False\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eWidth Scaling\u003c/td\u003e\n\u003ctd\u003eA scaling factor applied to the width of the draw surfaces\u003c/td\u003e\n\u003ctd\u003e[0.25, 2.5]\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"curve-configuration\"\u003eCurve Configuration\u003c/h3\u003e\n\n\u003cp\u003eIn addition to the 3D track configuration, each 3D well log curve may be configured in its Property Editor. Here settings are grouped into three categories: Data Selection, Appearance and Name Generation.\u003c/p\u003e\n\n\u003ch4 id=\"data-selection\"\u003eData Selection\u003c/h4\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eCurve Data\u003c/strong\u003e configuration allows you to select a case, result type, property and time step to plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_CurveData.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eCase\u003c/td\u003e\n\u003ctd\u003eThe eclipse or geomechanical case to retrieve the data from\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eResult Type\u003c/td\u003e\n\u003ctd\u003eDynamic, static, generated, input property, formation names, flow diagnostics or injection flooding\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eResult Property\u003c/td\u003e\n\u003ctd\u003eThe parameter to plot\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eTime Step\u003c/td\u003e\n\u003ctd\u003eWhich time step to show\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"appearance\"\u003eAppearance\u003c/h4\u003e\n\n\u003cp\u003eIn the \u003cstrong\u003eCurve Appearance\u003c/strong\u003e box, the curve can be assigned to a draw plane, the color can be changed and a range of curve values applied. The range of the result property can be set with the minimum and maximum curve value settings. The curve range is by default set to the minimum and maximum values found in the data set and these values are retained in the label if different values have been chosen.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_CurveConfiguration.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe draw plane can be vertical (above well path, centered and below well path) and horizontal (left, centered and right). If multiple curves are added and assigned to the same draw plane, they will appear in the same curve plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_DrawPlaneSelection.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"name-generation\"\u003eName Generation\u003c/h4\u003e\n\n\u003cp\u003eFinally the name of the curve is created automatically from a set of parameters such as case, view, etc. The parameters that should make up the curve name can be selected in the \u003cstrong\u003eCurve Name\u003c/strong\u003e box. Only extraction log curves have multiple settings here. The automatic name generation will be automatically switched off if the curve has been renamed manually and can be switched back on by checking the \u003cstrong\u003eGenerate Name Automatically\u003c/strong\u003e tick box.\u003c/p\u003e\n",
+                content:  "ResInsight can display well logs curves directly in the 3D view with a subset of the functionality of the full 2D Well Log Plot Editor. The curves will be drawn in a plane next to or centered on the well trajectory they belong to and can display well log data from a simulation model and from imported LAS-files.\nCreating new 3D Well Log Curves Add a new 3D well log curve by selecting a Well Path in the Project Tree, right-clicking and selecting 3D Well Log Curves and Add 3D Well Log Curve.\nDeleting 3D Well Log Curves Delete one or more 3D well log curves by selecting them in the project tree, right-clicking on one of the selected items and choosing Delete 3D Well Log Curve(s). The curves will be deleted with no further confirmation.\nConfigurating the 3D Well Log Curves 3D Track and Draw Plane Appearance Each 3D well log curve belongs to a 3D Track which in turn is attached to a well path. The 3D track itself contains some settings related to the display of the curves.\n   Parameter Description Range     Show Grid Show axis markers for the value-axis of the curves along the draw surface True/False   Show Background Draw a white background on the drawing surfaces of the curves True/False   Width Scaling A scaling factor applied to the width of the draw surfaces [0.25, 2.5]    Curve Configuration In addition to the 3D track configuration, each 3D well log curve may be configured in its Property Editor. Here settings are grouped into three categories: Data Selection, Appearance and Name Generation.\nData Selection The Curve Data configuration allows you to select a case, result type, property and time step to plot.\n   Parameter Description     Case The eclipse or geomechanical case to retrieve the data from   Result Type Dynamic, static, generated, input property, formation names, flow diagnostics or injection flooding   Result Property The parameter to plot   Time Step Which time step to show    Appearance In the Curve Appearance box, the curve can be assigned to a draw plane, the color can be changed and a range of curve values applied. The range of the result property can be set with the minimum and maximum curve value settings. The curve range is by default set to the minimum and maximum values found in the data set and these values are retained in the label if different values have been chosen.\nThe draw plane can be vertical (above well path, centered and below well path) and horizontal (left, centered and right). If multiple curves are added and assigned to the same draw plane, they will appear in the same curve plot.\nName Generation Finally the name of the curve is created automatically from a set of parameters such as case, view, etc. The parameters that should make up the curve name can be selected in the Curve Name box. Only extraction log curves have multiple settings here. The automatic name generation will be automatically switched off if the curve has been renamed manually and can be switched back on by checking the Generate Name Automatically tick box.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can display well logs curves directly in the 3D view with a subset of the functionality of the full \u003ca href=\"/plot-window/welllogsandplots/\"\u003e2D Well Log Plot Editor\u003c/a\u003e. The curves will be drawn in a plane next to or centered on the well trajectory they belong to and can display well log data from a simulation model and from imported LAS-files.\u003c/p\u003e\n\u003ch2 id=\"creating-new-3d-well-log-curves\"\u003eCreating new 3D Well Log Curves\u003c/h2\u003e\n\u003cp\u003eAdd a new 3D well log curve by selecting a Well Path in the Project Tree, right-clicking and selecting \u003cstrong\u003e3D Well Log Curves\u003c/strong\u003e and \u003cstrong\u003eAdd 3D Well Log Curve\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurvesCreate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"deleting-3d-well-log-curves\"\u003eDeleting 3D Well Log Curves\u003c/h2\u003e\n\u003cp\u003eDelete one or more 3D well log curves by selecting them in the project tree, right-clicking on one of the selected items and choosing \u003cstrong\u003eDelete 3D Well Log Curve(s)\u003c/strong\u003e. The curves will be deleted with no further confirmation.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurvesDelete.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"configurating-the-3d-well-log-curves\"\u003eConfigurating the 3D Well Log Curves\u003c/h2\u003e\n\u003ch3 id=\"3d-track-and-draw-plane-appearance\"\u003e3D Track and Draw Plane Appearance\u003c/h3\u003e\n\u003cp\u003eEach 3D well log curve belongs to a 3D Track which in turn is attached to a well path. The 3D track itself contains some settings related to the display of the curves.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_DrawPlaneAppearance.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eRange\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eShow Grid\u003c/td\u003e\n\u003ctd\u003eShow axis markers for the value-axis of the curves along the draw surface\u003c/td\u003e\n\u003ctd\u003eTrue/False\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eShow Background\u003c/td\u003e\n\u003ctd\u003eDraw a white background on the drawing surfaces of the curves\u003c/td\u003e\n\u003ctd\u003eTrue/False\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWidth Scaling\u003c/td\u003e\n\u003ctd\u003eA scaling factor applied to the width of the draw surfaces\u003c/td\u003e\n\u003ctd\u003e[0.25, 2.5]\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"curve-configuration\"\u003eCurve Configuration\u003c/h3\u003e\n\u003cp\u003eIn addition to the 3D track configuration, each 3D well log curve may be configured in its Property Editor. Here settings are grouped into three categories: Data Selection, Appearance and Name Generation.\u003c/p\u003e\n\u003ch4 id=\"data-selection\"\u003eData Selection\u003c/h4\u003e\n\u003cp\u003eThe \u003cstrong\u003eCurve Data\u003c/strong\u003e configuration allows you to select a case, result type, property and time step to plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_CurveData.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eCase\u003c/td\u003e\n\u003ctd\u003eThe eclipse or geomechanical case to retrieve the data from\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eResult Type\u003c/td\u003e\n\u003ctd\u003eDynamic, static, generated, input property, formation names, flow diagnostics or injection flooding\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eResult Property\u003c/td\u003e\n\u003ctd\u003eThe parameter to plot\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTime Step\u003c/td\u003e\n\u003ctd\u003eWhich time step to show\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"appearance\"\u003eAppearance\u003c/h4\u003e\n\u003cp\u003eIn the \u003cstrong\u003eCurve Appearance\u003c/strong\u003e box, the curve can be assigned to a draw plane, the color can be changed and a range of curve values applied. The range of the result property can be set with the minimum and maximum curve value settings. The curve range is by default set to the minimum and maximum values found in the data set and these values are retained in the label if different values have been chosen.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_CurveConfiguration.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe draw plane can be vertical (above well path, centered and below well path) and horizontal (left, centered and right). If multiple curves are added and assigned to the same draw plane, they will appear in the same curve plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3dWellLogCurves_DrawPlaneSelection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"name-generation\"\u003eName Generation\u003c/h4\u003e\n\u003cp\u003eFinally the name of the curve is created automatically from a set of parameters such as case, view, etc. The parameters that should make up the curve name can be selected in the \u003cstrong\u003eCurve Name\u003c/strong\u003e box. Only extraction log curves have multiple settings here. The automatic name generation will be automatically switched off if the curve has been renamed manually and can be switched back on by checking the \u003cstrong\u003eGenerate Name Automatically\u003c/strong\u003e tick box.\u003c/p\u003e\n",
                 url:      "/wells-and-completions/3dwelllogcurves/"
             };
         
@@ -2154,8 +2187,8 @@ if (!doNotTrack) {
          
             window.store["/export/completionexport/"] = {
                 title:    "Completions",
-                content:  " The completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands Export Completion Data For Visible Wells, Export Completion Data For Visible Simulation Wells and Export Completion Data For Selected Wells can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the Project Tree. The first command is available from the File-\u0026gt;Import menu as well.\n Export Settings  Calculated Transmissibilities \u0026ndash; The transmissibilities calculated based on the case and completion data are exported directly Default Connection Factors and WPIMULT \u0026ndash; The information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT/COMPDATL keywords. In addition, the same transmissibility calculation is performed by ResInsight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword. Case to Apply \u0026ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case.\n Use NTG Horizontally \u0026ndash; Toggles whether NTG in I and J directions is included in the calculation Include Multi Segment Well Model \u0026ndash; Toggles whether to also export the completions as Multi Segment Wells.  File Settings  File Split \u0026ndash; Controls how ResInsight splits the export in different files Unified File \u0026ndash; One file with all the completions. Split on Well \u0026ndash; One file for each well Split on Well and Completion Type \u0026ndash; One file for each well and completion type (Perforation Interval, Fishbone, \u0026hellip;) Export Completion Types \u0026ndash; Control how several completions of different type in the same cell are handled Individually \u0026ndash; Completions of each type are exported to separate sections in the file and not combined in any way.\n Combined \u0026ndash; Connection factors from different completion types are added together producing one number for each cell. Export Folder \u0026ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.  Completions Export Selection  Perforations \u0026ndash; Option to include or exclude perforation intervals in the export. Time step \u0026ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps. Fractures \u0026ndash; Option to include or exclude fracture completions from the export. Pressure Differential Depletion Scaling \u0026ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion. Fishbones \u0026ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to. Exclude Main Bore Transmissibility \u0026ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.   Transmissibility Calculations The transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.\nTaking the X direction as an example, we first calculate the relevant permeability K from the Eclipse properties PERMY (Ky) and PERMZ (Kz):\nThe Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (Dy and Dz):\nThe x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (lx), the well radius (rw) and skin factor (S):\nThe y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:\nIf the Export Calculated Transmissibilities is chosen in the export setting (see Exporting Completion Data to Eclipse), this value is exported in the COMPDAT/COMPDATL keywords directly. If the Export Default Connection Factors and WPIMULT the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT/COMPDATL keywords (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.\nFor an example of COMPDAT files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.\nFracture Export Pressure Differential Depletion Scaling For cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a Well Bore Hole Pressure (WBHP) larger than zero in the Summary Case information.\nHaving chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If WBHP From Summary Case is picked, the WBHP value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in WBHP Before Production Start is used.\nIf, however, a Fixed User Defined WBHP is chosen, the provided WBHP value is used for all wells.\nFracture Report Header At the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.\nDescription of Derived Data One of the tables displays derived data, see the example here:\n Tr #con Fcd Area KfWf Kf Wf Xf H Km [cP.rm3/day/bars] [] [m2] [mDm] [mD] [m] [m] [m] [mD] ---------------------------------------------------------------------------------------------------- 110.834 24 276.168 9315.748 54.889 3805.029 0.014 61.628 75.580 13.778   Tr \u0026ndash; Accumulated computed transmissibilies for all reservoir cells intersected by the fracture #con \u0026ndash; Number of reservoir cells intersected by the fracture Fcd \u0026ndash; Area weighted fracture conductivity divided by area weighted matrix transmissibility (Kf/Km) Area \u0026ndash; Area of reservoir cells(both active and inactive) intersected by the fracture KfWf \u0026ndash; Multiplication of Kf by Wf (Kf * Wf) Kf \u0026ndash; Area weighted average of permeability of fracture cells intersecting reservoir grid cells (using Area defined above) Wf \u0026ndash; Area weighted average of width of fracture cells intersecting reservoir grid cells (using Area defined above) Xf \u0026ndash; Half-length, defined as fracture area divided by half-height (Area/(H/2)) H \u0026ndash; Longest continuous distance with fracture cells open for flow along a fracture grid column Km \u0026ndash; Area weighted average of matrix transmissibility (using Area defined above)  Differential Depletion Fracture Output In addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (WBHP From Summary Case or Fixed User Defined WBHP). For WBHP From Summary Case the User WBHP column will describe the well pressure used for all time steps before the production starts according to the summary case information and the Actual WBHP will describe the well pressure used in the scaling, which will be different from the User WBHP if the scaling is performed for a time step following the well productions start. Finally the columns Min Pressure Drop and Max Pressure Drop describes the minimum and maximum well drawdown for this particular fracture.\n-- -- Pressure Depletion Time step: 01.Feb 2001 -- WBHP Source: WBHP From Summary Case -- User Defined WBHP: 200 -- Well Fracture Actual WBHP Min Pressure Drop Max Pressure Drop ------------------------------------------------------------------------------ -- B-1H Fracture_01 221.68147 0.04077 45.10402 -- B-1H Fracture_02 221.68147 0.00624 36.02608 -- B-4DH Fracture_07 200.00000 28.21733 97.34970 --  Export of Fishbone Completion Data The transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.\nAn example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.\nWELSPECS -- Well Grp I J RefDepth WellType Well Path B GR 26 45 1230 Oil \\ \\ COMPDAT -- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0 -- Well Path B main bore : 0.0569986 Well Path B 26 45 29 29 OPEN 1* 5.699858E-02 / -- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382 -- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575 -- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269 -- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929 -- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964 -- Well Path B main bore : 0.230572 Well Path B 27 41 15 15 OPEN 1* 2.645858E-01 / /  For export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.\nThe WPIMULT parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the WPIMUT keyword.\nWELSPEC -- Well Grp I J RefDepth WellType Well Path B GR 26 45 1230 Oil \\ \\ COMPDAT -- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0 -- Well Path B main bore : 0.0569986 Well Path B 26 45 29 29 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' / -- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382 -- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575 -- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269 -- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929 -- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964 -- Well Path B main bore : 0.230572 Well Path B 27 41 15 15 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' / / WPIMULT -- Well Mult I J K Well Path B 0.70133 25 45 29 / Well Path B 25.11396 27 41 15 / /  Completions for LGR (WELSPECL and COMPDATL) Completion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by \u0026ldquo;_LGR\u0026rdquo;. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns LGR and LgrName, respectively. The extra columns contains the name of the LGR grid.\nWELSPECL -- Well Grp LGR I J RefDepth WellType UWell-1 1* WELLI1 2 9 1* OIL / / COMPDATL -- Well LgrName I J K1 K2 Status SAT TR DIAM KH S Df DIR -- ---- Completions for completion type Perforation ---- -- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676 UWell-1 WELLI1 2 9 6 6 OPEN 1* 6.106763E+00 0.21600 1* 0.00000 1* 'Y' / -- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679 UWell-1 WELLI1 2 8 6 6 OPEN 1* 6.106791E+00 0.21600 1* 0.00000 1* 'Y' /  LGR for completions (Temporary LGRs) The previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs. To accomplish this, do the following:\n Create LGRs for completions on selected well paths. See Completions LGR Export completions the usual way. See Completion Export  In addition to the completion data, the geometrical definition of all temporary LGRs is also exported into \u0026ldquo;*.dat\u0026rdquo; files.\n\rMulti Segment Well Model It is possible to export all the completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well. This is done by checking the Include Multi Segment Well Model. All completions are supported and are exported in somewhat different ways.\nExported MSW Data In the output file there are data for three Eclipse keyword specified.\nWELSEGS WELSEGS defines multi-segment wells. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for. Example:\nWELSEGS -- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop Well Path A 4137.09154 87.00000 1* ABS H-- / -- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Main stem -- Segment for sub 0 2 2 1 1 13.00000 0.53667 0.15200 0.00001 / -- Laterals -- Diam: MSW - Tubing Radius -- Rough: MSW - Open Hole Roughness Factor -- ICD 3 3 2 2 0.10000 0 0.15200 0.00001 / -- Fishbone 0 : Sub index 0 - Lateral 0 52 52 27 3 1.70326 -0.57276 0.00960 0.00100 / 53 53 27 52 2.34748 -0.81635 0.00960 0.00100 / /   The first WELSEGS entry contains information about the well:\n Name - Name of well Dep 1 - TVD of start MD point, as given by the user in the Fishbones Start MD field.\n Tlen 1 - Point given by the user in the Fishbones Start MD field.\n Len\u0026amp;Dep - incremental or absolute, as specified by the user in the Fishbones property editor. PresDrop - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.  The following WELSEGS entries contains information about each segment:\n First Seg, Last Seg \u0026ndash; Values are being exported pr segment, so both first and last segment number is the number of the segment being exported. Branch Num \u0026ndash; Branch number for segment being exported. Outlet Seg \u0026ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.\n Length \u0026ndash; Length of segment (if incremental Len\u0026amp;Dep above) or length of segments including this along well (if absolute Len\u0026amp;Dep above). For ICDs length is set to 0.1. Depth Change \u0026ndash; Depth of segment, incremental or absolute as for Length. For ICDs depth is set to 0. Diam \u0026ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.\n Rough \u0026ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.\n   COMPSEGS An example of the COMPSEGS keyword as exported is shown below.\nCOMPSEGS -- Name Well Path A / -- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 28 40 6 27 0.00000 1.70326 / 28 40 7 27 1.70326 2.34748 / 28 40 8 27 2.34748 2.96577 / /  The first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and containing the following field:\n I, J and K \u0026ndash; The Eclipse cell index Branch no \u0026ndash; Branch number for the segment Start Length, End Length \u0026ndash; Start and end length along the well for the relevant segment.  WSEGVALV An example of the WSEGVALV keyword as exported is shown below.\nWSEGVALV -- Well Name Seg No Cv Ac Well Path A 3 1.50000 0.00008 / Well Path A 5 1.50000 0.00008 / Well Path A 7 1.50000 0.00008 / /  The parameters exported in the WEGVALV keyword are\n Well Name \u0026ndash; The name of the well. Seg No \u0026ndash; Segment number along the well. Cv \u0026ndash; The ICD Flow Coefficient, as entered by the user. Ac \u0026ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.\n  Export of Fractures and Perforations as Multi-Segment Wells Fractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the Diam and Rough parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.\nWELSEGS -- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop C-1 H 2575.39553 2919.53029 1* INC H-- / -- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Fracture Segments -- Diam: MSW - Default Dummy -- Rough: MSW - Default Dummy -- Traversal Fracture 02 connected to Main stem segment 11 25 25 2 11 0.01000 0.00000 0.15000 0.00005 / / COMPSEGS -- Fractures -- Name C-1 H / -- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 27 43 1 2 11.27214 11.28214 / 26 44 1 2 11.27214 11.28214 /  The entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.\nWELSEGS -- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop B-1 AH 2530.38706 3137.28258 1* INC H-- / -- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Main Stem Segments 2 2 1 1 16.33624 6.96924 0.15200 0.00001 / 3 3 1 2 11.77390 4.75668 0.15200 0.00001 / 4 4 1 3 9.49721 3.63598 0.15200 0.00001 / 5 5 1 4 6.77104 2.59228 0.15200 0.00001 / 6 6 1 5 29.44930 10.10431 0.15200 0.00001 / 7 7 1 6 27.93603 7.96718 0.15200 0.00001 / 8 8 1 7 13.95369 3.66086 0.15200 0.00001 / / COMPSEGS -- Name B-1 AH / -- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 10 24 1 1 3137.28258 3153.61882 / 10 24 2 1 3153.61882 3165.39273 / 9 24 2 1 3165.39273 3174.88994 / 9 25 2 1 3174.88994 3181.66098 / 9 25 3 1 3181.66098 3211.11028 / 9 25 5 1 3239.04631 3253.00000 / /  ",
-                html:     "\n\n\u003cp\u003eThe completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands \u003cstrong\u003eExport Completion Data For Visible Wells\u003c/strong\u003e, \u003cstrong\u003eExport Completion Data For Visible Simulation Wells\u003c/strong\u003e and \u003cstrong\u003eExport Completion Data For Selected Wells\u003c/strong\u003e can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The first command is available from the \u003cstrong\u003eFile-\u0026gt;Import\u003c/strong\u003e menu as well.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_ExportCompletionData.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Settings\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCalculated Transmissibilities\u003c/strong\u003e \u0026ndash; The transmissibilities calculated based on the case and completion data are exported directly\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Connection Factors and WPIMULT\u003c/strong\u003e \u0026ndash; The information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT/COMPDATL keywords. In addition, the same transmissibility calculation is performed by ResInsight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCase to Apply\u003c/strong\u003e \u0026ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse NTG Horizontally\u003c/strong\u003e \u0026ndash; Toggles whether NTG in I and J directions is included in the calculation\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInclude Multi Segment Well Model\u003c/strong\u003e \u0026ndash; Toggles whether to also export the completions as Multi Segment Wells.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Settings\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile Split\u003c/strong\u003e \u0026ndash; Controls how ResInsight splits the export in different files\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnified File\u003c/strong\u003e \u0026ndash; One file with all the completions.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit on Well\u003c/strong\u003e \u0026ndash; One file for each well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit on Well and Completion Type\u003c/strong\u003e \u0026ndash; One file for each well and completion type (Perforation Interval, Fishbone, \u0026hellip;)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Completion Types\u003c/strong\u003e \u0026ndash; Control how several completions of different type in the same cell are handled\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIndividually\u003c/strong\u003e \u0026ndash; Completions of each type are exported to separate sections in the file and not combined in any way.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCombined\u003c/strong\u003e \u0026ndash; Connection factors from different completion types are added together producing one number for each cell.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e \u0026ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletions Export Selection\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePerforations\u003c/strong\u003e \u0026ndash; Option to include or exclude perforation intervals in the export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime step\u003c/strong\u003e \u0026ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFractures\u003c/strong\u003e \u0026ndash; Option to include or exclude fracture completions from the export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Differential Depletion Scaling\u003c/strong\u003e \u0026ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFishbones\u003c/strong\u003e \u0026ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Main Bore Transmissibility\u003c/strong\u003e \u0026ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"transmissibility-calculations\"\u003eTransmissibility Calculations\u003c/h3\u003e\n\n\u003cp\u003eThe transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.\u003c/p\u003e\n\n\u003cp\u003eTaking the X direction as an example, we first calculate the relevant permeability \u003cem\u003eK\u003c/em\u003e from the Eclipse properties \u003cem\u003ePERMY\u003c/em\u003e (K\u003csub\u003ey\u003c/sub\u003e) and PERMZ (K\u003csub\u003ez\u003c/sub\u003e):\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_K.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (D\u003csub\u003ey\u003c/sub\u003e and D\u003csub\u003ez\u003c/sub\u003e):\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_Peaceman.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (l\u003csub\u003ex\u003c/sub\u003e), the well radius (r\u003csub\u003ew\u003c/sub\u003e) and skin factor (S):\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_Trans.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_TotalT.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIf the \u003cem\u003eExport Calculated Transmissibilities\u003c/em\u003e is chosen in the export setting (see \u003ca href=\"#exporting-completion-data-to-eclipse\"\u003eExporting Completion Data to Eclipse\u003c/a\u003e), this value is exported in the COMPDAT/COMPDATL keywords directly. If the \u003cem\u003eExport Default Connection Factors and WPIMULT\u003c/em\u003e the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT/COMPDATL keywords (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.\u003c/p\u003e\n\n\u003cp\u003eFor an example of \u003cem\u003eCOMPDAT\u003c/em\u003e files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.\u003c/p\u003e\n\n\u003ch3 id=\"fracture-export\"\u003eFracture Export\u003c/h3\u003e\n\n\u003ch4 id=\"pressure-differential-depletion-scaling\"\u003ePressure Differential Depletion Scaling\u003c/h4\u003e\n\n\u003cp\u003eFor cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a \u003cstrong\u003eWell Bore Hole Pressure\u003c/strong\u003e (\u003cstrong\u003eWBHP\u003c/strong\u003e) larger than zero in the Summary Case information.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_TimeStep.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eHaving chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If \u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e is picked, the \u003cstrong\u003eWBHP\u003c/strong\u003e value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in \u003cstrong\u003eWBHP Before Production Start\u003c/strong\u003e is used.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_WBHP.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIf, however, a \u003cstrong\u003eFixed User Defined WBHP\u003c/strong\u003e is chosen, the provided \u003cstrong\u003eWBHP\u003c/strong\u003e value is used for all wells.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_User_WBHP.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"fracture-report-header\"\u003eFracture Report Header\u003c/h4\u003e\n\n\u003cp\u003eAt the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.\u003c/p\u003e\n\n\u003ch5 id=\"description-of-derived-data\"\u003eDescription of Derived Data\u003c/h5\u003e\n\n\u003cp\u003eOne of the tables displays derived data, see the example here:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e               Tr   #con       Fcd       Area     KfWf         Kf      Wf       Xf        H       Km\n[cP.rm3/day/bars]               []       [m2]    [mDm]       [mD]     [m]      [m]      [m]     [mD]\n----------------------------------------------------------------------------------------------------\n          110.834     24   276.168   9315.748   54.889   3805.029   0.014   61.628   75.580   13.778\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTr\u003c/strong\u003e \u0026ndash; Accumulated computed transmissibilies for all reservoir cells intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e#con\u003c/strong\u003e \u0026ndash; Number of reservoir cells intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFcd\u003c/strong\u003e \u0026ndash; Area weighted fracture conductivity divided by area weighted matrix transmissibility (Kf/Km)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArea\u003c/strong\u003e \u0026ndash; Area of reservoir cells(both active and inactive) intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKfWf\u003c/strong\u003e \u0026ndash; Multiplication of Kf by Wf (Kf * Wf)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKf\u003c/strong\u003e \u0026ndash; Area weighted average of permeability of fracture cells intersecting reservoir grid cells (using Area defined above)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWf\u003c/strong\u003e \u0026ndash; Area weighted average of width of fracture cells intersecting reservoir grid cells (using Area defined above)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXf\u003c/strong\u003e \u0026ndash; Half-length, defined as fracture area divided by half-height (Area/(H/2))\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eH\u003c/strong\u003e \u0026ndash; Longest continuous distance with fracture cells open for flow along a fracture grid column\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKm\u003c/strong\u003e \u0026ndash; Area weighted average of matrix transmissibility (using Area defined above)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"differential-depletion-fracture-output\"\u003eDifferential Depletion Fracture Output\u003c/h4\u003e\n\n\u003cp\u003eIn addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (\u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e or \u003cstrong\u003eFixed User Defined WBHP\u003c/strong\u003e). For \u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e the \u003cstrong\u003eUser WBHP\u003c/strong\u003e column will describe the well pressure used for all time steps before the production starts according to the summary case information and the \u003cstrong\u003eActual WBHP\u003c/strong\u003e will describe the well pressure used in the scaling, which will be different from the \u003cstrong\u003eUser WBHP\u003c/strong\u003e if the scaling is performed for a time step following the well productions start. Finally the columns \u003cstrong\u003eMin Pressure Drop\u003c/strong\u003e and \u003cstrong\u003eMax Pressure Drop\u003c/strong\u003e describes the minimum and maximum well drawdown for this particular fracture.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e--\n-- Pressure Depletion Time step: 01.Feb 2001\n-- WBHP Source: WBHP From Summary Case\n-- User Defined WBHP: 200\n-- Well    Fracture      Actual WBHP   Min Pressure Drop   Max Pressure Drop   \n------------------------------------------------------------------------------\n-- B-1H    Fracture_01   221.68147     0.04077             45.10402            \n-- B-1H    Fracture_02   221.68147     0.00624             36.02608            \n-- B-4DH   Fracture_07   200.00000     28.21733            97.34970            \n-- \n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"export-of-fishbone-completion-data\"\u003eExport of Fishbone Completion Data\u003c/h3\u003e\n\n\u003cp\u003eThe transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.\u003c/p\u003e\n\n\u003cp\u003eAn example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSPECS\n-- Well          Grp   I   J    RefDepth   WellType   \n   Well Path B   GR    26  45   1230       Oil        \\\n\\\nCOMPDAT\n-- Well            I      J      K1     K2     Status     SAT     TR               DIAM     KH     S     Df     DIR     r0     \n-- Well Path B main bore : 0.0569986\n   Well Path B     26     45     29     29     OPEN       1*      5.699858E-02      /\n-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\n-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\n-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\n-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\n-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\n-- Well Path B main bore : 0.230572\n   Well Path B     27     41     15     15     OPEN       1*      2.645858E-01      /\n/\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eFor export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cem\u003eWPIMULT\u003c/em\u003e parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the \u003cem\u003eWPIMUT\u003c/em\u003e keyword.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSPEC\n-- Well          Grp   I   J    RefDepth   WellType   \n   Well Path B   GR    26  45   1230       Oil        \\\n\\\nCOMPDAT\n-- Well            I      J      K1     K2     Status     SAT     TR     DIAM        KH     S           Df     DIR     r0     \n-- Well Path B main bore : 0.0569986\n   Well Path B     26     45     29     29     OPEN       1*      1*     0.21600     1*     0.00000     1*     'Z'      /\n-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\n-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\n-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\n-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\n-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\n-- Well Path B main bore : 0.230572\n   Well Path B     27     41     15     15     OPEN       1*      1*     0.21600     1*     0.00000     1*     'Z'      /\n/\nWPIMULT\n-- Well            Mult         I      J      K      \n   Well Path B     0.70133      25     45     29      /\n   Well Path B     25.11396     27     41     15      /\n/\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"completions-for-lgr-welspecl-and-compdatl\"\u003eCompletions for LGR (WELSPECL and COMPDATL)\u003c/h3\u003e\n\n\u003cp\u003eCompletion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by \u0026ldquo;_LGR\u0026rdquo;. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns \u003cstrong\u003eLGR\u003c/strong\u003e and \u003cstrong\u003eLgrName\u003c/strong\u003e, respectively. The extra columns contains the name of the LGR grid.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSPECL\n-- Well      Grp   LGR      I   J   RefDepth   WellType   \n   UWell-1   1*    WELLI1   2   9   1*         OIL         /\n    /\nCOMPDATL\n-- Well      LgrName   I   J   K1   K2   Status   SAT   TR             DIAM      KH   S         Df   DIR   \n-- ---- Completions for completion type Perforation ----\n-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676\n   UWell-1   WELLI1    2   9   6    6    OPEN     1*    6.106763E+00   0.21600   1*   0.00000   1*   'Y'    /\n-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679\n   UWell-1   WELLI1    2   8   6    6    OPEN     1*    6.106791E+00   0.21600   1*   0.00000   1*   'Y'    /\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"lgr-for-completions-temporary-lgrs\"\u003eLGR for completions (Temporary LGRs)\u003c/h3\u003e\n\n\u003cp\u003eThe previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs.\nTo accomplish this, do the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eCreate LGRs for completions on selected well paths. See \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExport completions the usual way. See \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIn addition to the completion data, the geometrical definition of all temporary LGRs is also exported into \u0026ldquo;*.dat\u0026rdquo; files.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"multi-segment-well-model\"\u003eMulti Segment Well Model\u003c/h2\u003e\n\n\u003cp\u003eIt is possible to export all the completions to a text file containing the Eclipse input data\nkeywords needed to represent the completions as a Multi Segment Well. This is done by checking the \u003cstrong\u003eInclude Multi Segment Well Model\u003c/strong\u003e. All completions are supported and are exported in somewhat different ways.\u003c/p\u003e\n\n\u003ch3 id=\"exported-msw-data\"\u003eExported MSW Data\u003c/h3\u003e\n\n\u003cp\u003eIn the output file there are data for three Eclipse keyword specified.\u003c/p\u003e\n\n\u003ch5 id=\"welsegs\"\u003eWELSEGS\u003c/h5\u003e\n\n\u003cp\u003eWELSEGS defines multi-segment wells. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for.  Example:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSEGS\n-- Name            Dep 1          Tlen 1       Vol 1     Len\u0026amp;Dep     PresDrop     \n   Well Path A     4137.09154     87.00000     1*        ABS         H--           /\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length        Depth Change     Diam        Rough       \n-- Main stem\n-- Segment for sub 0\n   2             2            1              1              13.00000      0.53667          0.15200     0.00001      /\n-- Laterals\n-- Diam: MSW - Tubing Radius\n-- Rough: MSW - Open Hole Roughness Factor\n-- ICD\n   3             3            2              2              0.10000       0                0.15200     0.00001      /\n-- Fishbone 0 : Sub index 0 - Lateral 0\n   52            52           27             3              1.70326       -0.57276         0.00960     0.00100      /\n   53            53           27             52             2.34748       -0.81635         0.00960     0.00100      /\n/\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003eThe first \u003cem\u003eWELSEGS\u003c/em\u003e entry contains information about the well:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e - Name of well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDep 1\u003c/strong\u003e - TVD of start MD point, as given by the user in the Fishbones \u003cstrong\u003eStart MD\u003c/strong\u003e field.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTlen 1\u003c/strong\u003e - Point given by the user in the Fishbones \u003cstrong\u003eStart MD\u003c/strong\u003e field.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLen\u0026amp;Dep\u003c/strong\u003e - incremental or absolute, as specified by the user in the Fishbones property editor.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePresDrop\u003c/strong\u003e - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003eThe following \u003cem\u003eWELSEGS\u003c/em\u003e entries contains information about each segment:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFirst Seg\u003c/strong\u003e, \u003cstrong\u003eLast Seg\u003c/strong\u003e \u0026ndash; Values are being exported pr segment, so both first and last segment number is the number of the segment being exported.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch Num\u003c/strong\u003e \u0026ndash; Branch number for segment being exported.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOutlet Seg\u003c/strong\u003e \u0026ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength\u003c/strong\u003e \u0026ndash; Length of segment (if incremental Len\u0026amp;Dep above) or length of segments including this along well (if absolute Len\u0026amp;Dep above). For ICDs length is set to 0.1.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Change\u003c/strong\u003e \u0026ndash; Depth of segment, incremental or absolute as for Length. For ICDs depth is set to 0.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiam\u003c/strong\u003e \u0026ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRough\u003c/strong\u003e \u0026ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.\u003cbr /\u003e\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"compsegs\"\u003eCOMPSEGS\u003c/h5\u003e\n\n\u003cp\u003eAn example of the COMPSEGS keyword as exported is shown below.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eCOMPSEGS\n-- Name            \n   Well Path A      /\n-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n   28     40     6      27            0.00000          1.70326         /\n   28     40     7      27            1.70326          2.34748         /\n   28     40     8      27            2.34748          2.96577         /\n/\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and containing the following field:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eI\u003c/strong\u003e, \u003cstrong\u003eJ\u003c/strong\u003e and \u003cstrong\u003eK\u003c/strong\u003e \u0026ndash; The Eclipse cell index\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch no\u003c/strong\u003e \u0026ndash; Branch number for the segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Length\u003c/strong\u003e, \u003cstrong\u003eEnd Length\u003c/strong\u003e \u0026ndash; Start and end length along the well for the relevant segment.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"wsegvalv\"\u003eWSEGVALV\u003c/h5\u003e\n\n\u003cp\u003eAn example of the WSEGVALV keyword as exported is shown below.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWSEGVALV\n-- Well Name       Seg No     Cv          Ac          \n   Well Path A     3          1.50000     0.00008      /\n   Well Path A     5          1.50000     0.00008      /\n   Well Path A     7          1.50000     0.00008      /\n/\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe parameters exported in the WEGVALV keyword are\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; The name of the well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeg No\u003c/strong\u003e \u0026ndash; Segment number along the well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCv\u003c/strong\u003e \u0026ndash; The ICD Flow Coefficient, as entered by the user.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAc\u003c/strong\u003e \u0026ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.\u003cbr /\u003e\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"export-of-fractures-and-perforations-as-multi-segment-wells\"\u003eExport of Fractures and Perforations as Multi-Segment Wells\u003c/h3\u003e\n\n\u003cp\u003eFractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the \u003cstrong\u003eDiam\u003c/strong\u003e and \u003cstrong\u003eRough\u003c/strong\u003e parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSEGS\n-- Name      Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \n   C-1 H     2575.39553     2919.53029     1*        INC         H--           /\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \n-- Fracture Segments\n-- Diam: MSW - Default Dummy\n-- Rough: MSW - Default Dummy\n-- Traversal Fracture 02 connected to Main stem segment 11\n   25            25           2              11             0.01000      0.00000          0.15000     0.00005      /\n    /\nCOMPSEGS\n-- Fractures\n-- Name      \n   C-1 H      /\n-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n   27     43     1      2             11.27214         11.28214        /\n   26     44     1      2             11.27214         11.28214        /\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELSEGS\n-- Name       Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \n   B-1 AH     2530.38706     3137.28258     1*        INC         H--           /\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \n-- Main Stem Segments\n   2             2            1              1              16.33624     6.96924          0.15200     0.00001      /\n   3             3            1              2              11.77390     4.75668          0.15200     0.00001      /\n   4             4            1              3              9.49721      3.63598          0.15200     0.00001      /\n   5             5            1              4              6.77104      2.59228          0.15200     0.00001      /\n   6             6            1              5              29.44930     10.10431         0.15200     0.00001      /\n   7             7            1              6              27.93603     7.96718          0.15200     0.00001      /\n   8             8            1              7              13.95369     3.66086          0.15200     0.00001      /\n   /\nCOMPSEGS\n-- Name       \n   B-1 AH      /\n-- I      J      K     Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n   10     24     1     1             3137.28258       3153.61882      /\n   10     24     2     1             3153.61882       3165.39273      /\n   9      24     2     1             3165.39273       3174.88994      /\n   9      25     2     1             3174.88994       3181.66098      /\n   9      25     3     1             3181.66098       3211.11028      /\n   9      25     5     1             3239.04631       3253.00000      /\n   /\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "The completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands Export Completion Data For Visible Wells, Export Completion Data For Visible Simulation Wells and Export Completion Data For Selected Wells can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the Project Tree. The first command is available from the File-\u0026gt;Import menu as well.\n Export Settings  Calculated Transmissibilities \u0026ndash; The transmissibilities calculated based on the case and completion data are exported directly Default Connection Factors and WPIMULT \u0026ndash; The information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT/COMPDATL keywords. In addition, the same transmissibility calculation is performed by ResInsight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword. Case to Apply \u0026ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case. Use NTG Horizontally \u0026ndash; Toggles whether NTG in I and J directions is included in the calculation Include Multi Segment Well Model \u0026ndash; Toggles whether to also export the completions as Multi Segment Wells.   File Settings  File Split \u0026ndash; Controls how ResInsight splits the export in different files  Unified File \u0026ndash; One file with all the completions. Split on Well \u0026ndash; One file for each well Split on Well and Completion Type \u0026ndash; One file for each well and completion type (Perforation Interval, Fishbone, \u0026hellip;)   Export Completion Types \u0026ndash; Control how several completions of different type in the same cell are handled  Individually \u0026ndash; Completions of each type are exported to separate sections in the file and not combined in any way. Combined \u0026ndash; Connection factors from different completion types are added together producing one number for each cell.   Export Folder \u0026ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.   Completions Export Selection  Perforations \u0026ndash; Option to include or exclude perforation intervals in the export.  Time step \u0026ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.   Fractures \u0026ndash; Option to include or exclude fracture completions from the export.  Pressure Differential Depletion Scaling \u0026ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion.   Fishbones \u0026ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to.  Exclude Main Bore Transmissibility \u0026ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.      Transmissibility Calculations The transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.\nTaking the X direction as an example, we first calculate the relevant permeability K from the Eclipse properties PERMY (Ky) and PERMZ (Kz):\nThe Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (Dyand Dz):\nThe x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (lx), the well radius (rw) and skin factor (S):\nThe y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:\nIf the Export Calculated Transmissibilities is chosen in the export setting (see Exporting Completion Data to Eclipse), this value is exported in the COMPDAT/COMPDATL keywords directly. If the Export Default Connection Factors and WPIMULT the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT/COMPDATL keywords (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.\nFor an example of COMPDAT files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.\nFracture Export Pressure Differential Depletion Scaling For cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a Well Bore Hole Pressure (WBHP) larger than zero in the Summary Case information.\nHaving chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If WBHP From Summary Case is picked, the WBHP value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in WBHP Before Production Start is used.\nIf, however, a Fixed User Defined WBHP is chosen, the provided WBHP value is used for all wells.\nFracture Report Header At the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.\nDescription of Derived Data One of the tables displays derived data, see the example here:\n Tr #con Fcd Area KfWf Kf Wf Xf H Km\r[cP.rm3/day/bars] [] [m2] [mDm] [mD] [m] [m] [m] [mD]\r----------------------------------------------------------------------------------------------------\r110.834 24 276.168 9315.748 54.889 3805.029 0.014 61.628 75.580 13.778\r  Tr \u0026ndash; Accumulated computed transmissibilies for all reservoir cells intersected by the fracture #con \u0026ndash; Number of reservoir cells intersected by the fracture Fcd \u0026ndash; Area weighted fracture conductivity divided by area weighted matrix transmissibility (Kf/Km) Area \u0026ndash; Area of reservoir cells(both active and inactive) intersected by the fracture KfWf \u0026ndash; Multiplication of Kf by Wf (Kf * Wf) Kf \u0026ndash; Area weighted average of permeability of fracture cells intersecting reservoir grid cells (using Area defined above) Wf \u0026ndash; Area weighted average of width of fracture cells intersecting reservoir grid cells (using Area defined above) Xf \u0026ndash; Half-length, defined as fracture area divided by half-height (Area/(H/2)) H \u0026ndash; Longest continuous distance with fracture cells open for flow along a fracture grid column Km \u0026ndash; Area weighted average of matrix transmissibility (using Area defined above)  Differential Depletion Fracture Output In addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (WBHP From Summary Case or Fixed User Defined WBHP). For WBHP From Summary Case the User WBHP column will describe the well pressure used for all time steps before the production starts according to the summary case information and the Actual WBHP will describe the well pressure used in the scaling, which will be different from the User WBHP if the scaling is performed for a time step following the well productions start. Finally the columns Min Pressure Drop and Max Pressure Drop describes the minimum and maximum well drawdown for this particular fracture.\n--\r-- Pressure Depletion Time step: 01.Feb 2001\r-- WBHP Source: WBHP From Summary Case\r-- User Defined WBHP: 200\r-- Well Fracture Actual WBHP Min Pressure Drop Max Pressure Drop ------------------------------------------------------------------------------\r-- B-1H Fracture_01 221.68147 0.04077 45.10402 -- B-1H Fracture_02 221.68147 0.00624 36.02608 -- B-4DH Fracture_07 200.00000 28.21733 97.34970 --  Export of Fishbone Completion Data The transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.\nAn example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.\nWELSPECS\r-- Well Grp I J RefDepth WellType Well Path B GR 26 45 1230 Oil \\\r\\\rCOMPDAT\r-- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0 -- Well Path B main bore : 0.0569986\rWell Path B 26 45 29 29 OPEN 1* 5.699858E-02 /\r-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\r-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\r-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\r-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\r-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\r-- Well Path B main bore : 0.230572\rWell Path B 27 41 15 15 OPEN 1* 2.645858E-01 /\r/\r For export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.\nThe WPIMULT parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the WPIMUT keyword.\nWELSPEC\r-- Well Grp I J RefDepth WellType Well Path B GR 26 45 1230 Oil \\\r\\\rCOMPDAT\r-- Well I J K1 K2 Status SAT TR DIAM KH S Df DIR r0 -- Well Path B main bore : 0.0569986\rWell Path B 26 45 29 29 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' /\r-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\r-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\r-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\r-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\r-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\r-- Well Path B main bore : 0.230572\rWell Path B 27 41 15 15 OPEN 1* 1* 0.21600 1* 0.00000 1* 'Z' /\r/\rWPIMULT\r-- Well Mult I J K Well Path B 0.70133 25 45 29 /\rWell Path B 25.11396 27 41 15 /\r/\r Completions for LGR (WELSPECL and COMPDATL) Completion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by \u0026ldquo;_LGR\u0026rdquo;. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns LGR and LgrName, respectively. The extra columns contains the name of the LGR grid.\nWELSPECL\r-- Well Grp LGR I J RefDepth WellType UWell-1 1* WELLI1 2 9 1* OIL /\r/\rCOMPDATL\r-- Well LgrName I J K1 K2 Status SAT TR DIAM KH S Df DIR -- ---- Completions for completion type Perforation ----\r-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676\rUWell-1 WELLI1 2 9 6 6 OPEN 1* 6.106763E+00 0.21600 1* 0.00000 1* 'Y' /\r-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679\rUWell-1 WELLI1 2 8 6 6 OPEN 1* 6.106791E+00 0.21600 1* 0.00000 1* 'Y' /\r LGR for completions (Temporary LGRs) The previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs. To accomplish this, do the following:\n Create LGRs for completions on selected well paths. See Completions LGR Export completions the usual way. See Completion Export  In addition to the completion data, the geometrical definition of all temporary LGRs is also exported into \u0026ldquo;*.dat\u0026rdquo; files.\n\rMulti Segment Well Model It is possible to export all the completions to a text file containing the Eclipse input data keywords needed to represent the completions as a Multi Segment Well. This is done by checking the Include Multi Segment Well Model. All completions are supported and are exported in somewhat different ways.\nExported MSW Data In the output file there are data for three Eclipse keyword specified.\nWELSEGS WELSEGS defines multi-segment wells. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for. Example:\nWELSEGS\r-- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop Well Path A 4137.09154 87.00000 1* ABS H-- /\r-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Main stem\r-- Segment for sub 0\r2 2 1 1 13.00000 0.53667 0.15200 0.00001 /\r-- Laterals\r-- Diam: MSW - Tubing Radius\r-- Rough: MSW - Open Hole Roughness Factor\r-- ICD\r3 3 2 2 0.10000 0 0.15200 0.00001 /\r-- Fishbone 0 : Sub index 0 - Lateral 0\r52 52 27 3 1.70326 -0.57276 0.00960 0.00100 /\r53 53 27 52 2.34748 -0.81635 0.00960 0.00100 /\r/\r   The first WELSEGS entry contains information about the well:\n Name - Name of well Dep 1 - TVD of start MD point, as given by the user in the Fishbones Start MD field. Tlen 1 - Point given by the user in the Fishbones Start MD field. Len\u0026amp;Dep - incremental or absolute, as specified by the user in the Fishbones property editor. PresDrop - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.    The following WELSEGS entries contains information about each segment:\n First Seg, Last Seg \u0026ndash; Values are being exported pr segment, so both first and last segment number is the number of the segment being exported. Branch Num \u0026ndash; Branch number for segment being exported. Outlet Seg \u0026ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected. Length \u0026ndash; Length of segment (if incremental Len\u0026amp;Dep above) or length of segments including this along well (if absolute Len\u0026amp;Dep above). For ICDs length is set to 0.1. Depth Change \u0026ndash; Depth of segment, incremental or absolute as for Length. For ICDs depth is set to 0. Diam \u0026ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter. Rough \u0026ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.    COMPSEGS An example of the COMPSEGS keyword as exported is shown below.\nCOMPSEGS\r-- Name Well Path A /\r-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 28 40 6 27 0.00000 1.70326 /\r28 40 7 27 1.70326 2.34748 /\r28 40 8 27 2.34748 2.96577 /\r/\r The first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and containing the following field:\n I, J and K \u0026ndash; The Eclipse cell index Branch no \u0026ndash; Branch number for the segment Start Length, End Length \u0026ndash; Start and end length along the well for the relevant segment.  WSEGVALV An example of the WSEGVALV keyword as exported is shown below.\nWSEGVALV\r-- Well Name Seg No Cv Ac Well Path A 3 1.50000 0.00008 /\rWell Path A 5 1.50000 0.00008 /\rWell Path A 7 1.50000 0.00008 /\r/\r The parameters exported in the WEGVALV keyword are\n Well Name \u0026ndash; The name of the well. Seg No \u0026ndash; Segment number along the well. Cv \u0026ndash; The ICD Flow Coefficient, as entered by the user. Ac \u0026ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.  Export of Fractures and Perforations as Multi-Segment Wells Fractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the Diam and Rough parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.\nWELSEGS\r-- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop C-1 H 2575.39553 2919.53029 1* INC H-- /\r-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Fracture Segments\r-- Diam: MSW - Default Dummy\r-- Rough: MSW - Default Dummy\r-- Traversal Fracture 02 connected to Main stem segment 11\r25 25 2 11 0.01000 0.00000 0.15000 0.00005 /\r/\rCOMPSEGS\r-- Fractures\r-- Name C-1 H /\r-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 27 43 1 2 11.27214 11.28214 /\r26 44 1 2 11.27214 11.28214 /\r The entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.\nWELSEGS\r-- Name Dep 1 Tlen 1 Vol 1 Len\u0026amp;Dep PresDrop B-1 AH 2530.38706 3137.28258 1* INC H-- /\r-- First Seg Last Seg Branch Num Outlet Seg Length Depth Change Diam Rough -- Main Stem Segments\r2 2 1 1 16.33624 6.96924 0.15200 0.00001 /\r3 3 1 2 11.77390 4.75668 0.15200 0.00001 /\r4 4 1 3 9.49721 3.63598 0.15200 0.00001 /\r5 5 1 4 6.77104 2.59228 0.15200 0.00001 /\r6 6 1 5 29.44930 10.10431 0.15200 0.00001 /\r7 7 1 6 27.93603 7.96718 0.15200 0.00001 /\r8 8 1 7 13.95369 3.66086 0.15200 0.00001 /\r/\rCOMPSEGS\r-- Name B-1 AH /\r-- I J K Branch no Start Length End Length Dir Pen End Range Connection Depth 10 24 1 1 3137.28258 3153.61882 /\r10 24 2 1 3153.61882 3165.39273 /\r9 24 2 1 3165.39273 3174.88994 /\r9 25 2 1 3174.88994 3181.66098 /\r9 25 3 1 3181.66098 3211.11028 /\r9 25 5 1 3239.04631 3253.00000 /\r/\r ",
+                html:     "\u003cp\u003eThe completions defined in ResInsight can be exported to Eclipse for use in new simulation runs. The commands \u003cstrong\u003eExport Completion Data For Visible Wells\u003c/strong\u003e, \u003cstrong\u003eExport Completion Data For Visible Simulation Wells\u003c/strong\u003e and \u003cstrong\u003eExport Completion Data For Selected Wells\u003c/strong\u003e can be used to invoke the export. The commands are available by right clicking Well Paths or Simulation Wells in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The first command is available from the \u003cstrong\u003eFile-\u0026gt;Import\u003c/strong\u003e menu as well.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_ExportCompletionData.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Settings\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCalculated Transmissibilities\u003c/strong\u003e \u0026ndash; The transmissibilities calculated based on the case and completion data are exported directly\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Connection Factors and WPIMULT\u003c/strong\u003e \u0026ndash; The information about the connections for Eclipse to be able to make the transmissibility calculaton is exported for the COMPDAT/COMPDATL keywords. In addition, the same transmissibility calculation is performed by ResInsight, and the factor between the actual transmissibility for the connection and the Eclipse calculation is exported in the WPIMULT keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCase to Apply\u003c/strong\u003e \u0026ndash; Select which case to use for the export. Matrix transmissibilities will be read from this case.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse NTG Horizontally\u003c/strong\u003e \u0026ndash; Toggles whether NTG in I and J directions is included in the calculation\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInclude Multi Segment Well Model\u003c/strong\u003e \u0026ndash; Toggles whether to also export the completions as Multi Segment Wells.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Settings\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile Split\u003c/strong\u003e \u0026ndash; Controls how ResInsight splits the export in different files\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUnified File\u003c/strong\u003e \u0026ndash; One file with all the completions.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit on Well\u003c/strong\u003e \u0026ndash; One file for each well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit on Well and Completion Type\u003c/strong\u003e \u0026ndash; One file for each well and completion type (Perforation Interval, Fishbone, \u0026hellip;)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Completion Types\u003c/strong\u003e \u0026ndash; Control how several completions of different type in the same cell are handled\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eIndividually\u003c/strong\u003e \u0026ndash; Completions of each type are exported to separate sections in the file and not combined in any way.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCombined\u003c/strong\u003e \u0026ndash; Connection factors from different completion types are added together producing one number for each cell.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e \u0026ndash; Folder for the exported COMPDAT file(s). The folder will be created when performing the export and the names of the exported file(s) will be auto generated.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletions Export Selection\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePerforations\u003c/strong\u003e \u0026ndash; Option to include or exclude perforation intervals in the export.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTime step\u003c/strong\u003e \u0026ndash; Which timestep to export. This option is included since perforation intervals have a start time, and thus not all perforations need be present at all time steps.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFractures\u003c/strong\u003e \u0026ndash; Option to include or exclude fracture completions from the export.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Differential Depletion Scaling\u003c/strong\u003e \u0026ndash; Options to scale transmissibilities based on the well drawdown. This allows the Eclipse simulation to more accurately model cases with high differential depletion.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFishbones\u003c/strong\u003e \u0026ndash; Option to include or exclude fishbone completions from the export. The direction reported in the COMPDAT/COMPDATL keywords is computed based on the orientation of the main bore cell the fishbone is connected to.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Main Bore Transmissibility\u003c/strong\u003e \u0026ndash; If this options is checked on, only the transmissibilities for the fishbone laterals will be included in the export, and transmissibility along the main bore will not contribute.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"transmissibility-calculations\"\u003eTransmissibility Calculations\u003c/h3\u003e\n\u003cp\u003eThe transmissibility calculation is performed for each direction, X, Y and Z, in an orthogonal coordinate system local to the cell.\u003c/p\u003e\n\u003cp\u003eTaking the X direction as an example, we first calculate the relevant permeability \u003cem\u003eK\u003c/em\u003e from the Eclipse properties \u003cem\u003ePERMY\u003c/em\u003e (K\u003c!-- raw HTML omitted --\u003ey\u003c!-- raw HTML omitted --\u003e) and PERMZ (K\u003c!-- raw HTML omitted --\u003ez\u003c!-- raw HTML omitted --\u003e):\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_K.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Peacman radius (pressure equivalent radius) for the cell is then calculated, using permeabilities and cell sizes (D\u003c!-- raw HTML omitted --\u003ey\u003c!-- raw HTML omitted --\u003e and D\u003c!-- raw HTML omitted --\u003ez\u003c!-- raw HTML omitted --\u003e):\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_Peaceman.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe x-component of the transmissibility vector is calculated, using the length of the perforation in the x direction (l\u003c!-- raw HTML omitted --\u003ex\u003c!-- raw HTML omitted --\u003e), the well radius (r\u003c!-- raw HTML omitted --\u003ew\u003c!-- raw HTML omitted --\u003e) and skin factor (S):\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_Trans.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe y and z component of the transmissibility are calculated in the same manner, and the total transmissibility is then calculated as:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Equation_PerfInterval_TotalT.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf the \u003cem\u003eExport Calculated Transmissibilities\u003c/em\u003e is chosen in the export setting (see \u003ca href=\"#exporting-completion-data-to-eclipse\"\u003eExporting Completion Data to Eclipse\u003c/a\u003e), this value is exported in the COMPDAT/COMPDATL keywords directly. If the \u003cem\u003eExport Default Connection Factors and WPIMULT\u003c/em\u003e the transmissibility is chosen, the transmissibility is calculated as above, and in addition the transmissibility is calculated as Eclipse would do it using values other than transmissibility in the COMPDAT/COMPDATL keywords (perforation length, well radius etc). The ratio between these transmissibilities is then exported as the WPIMULT value.\u003c/p\u003e\n\u003cp\u003eFor an example of \u003cem\u003eCOMPDAT\u003c/em\u003e files exported with calculated transmissibilities and with defaults and WPIMULT values, see export of fishbones completion data below.\u003c/p\u003e\n\u003ch3 id=\"fracture-export\"\u003eFracture Export\u003c/h3\u003e\n\u003ch4 id=\"pressure-differential-depletion-scaling\"\u003ePressure Differential Depletion Scaling\u003c/h4\u003e\n\u003cp\u003eFor cases with high differential depletion, it is possible to scale the transmissibilities from the grid cells into the well (via the fracture) by the well drawdown. This enables the simulation to take into account that the flow will take different paths into the well as the pressure differential between the surrounding grid cells increases. If enabled, a time step for the grid pressures have to be selected. The list of time steps will also show the time step in which the wells first show a \u003cstrong\u003eWell Bore Hole Pressure\u003c/strong\u003e (\u003cstrong\u003eWBHP\u003c/strong\u003e) larger than zero in the Summary Case information.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_TimeStep.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHaving chosen a time step for differential depletion scaling a source for the well pressures can be chosen. If \u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e is picked, the \u003cstrong\u003eWBHP\u003c/strong\u003e value in the summary case for the chosen time step is used. However, if the chosen time step precedes the production start of a well, the value set in \u003cstrong\u003eWBHP Before Production Start\u003c/strong\u003e is used.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_WBHP.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf, however, a \u003cstrong\u003eFixed User Defined WBHP\u003c/strong\u003e is chosen, the provided \u003cstrong\u003eWBHP\u003c/strong\u003e value is used for all wells.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/Completions_Export_PDD_User_WBHP.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"fracture-report-header\"\u003eFracture Report Header\u003c/h4\u003e\n\u003cp\u003eAt the top of the exported transmissibilities for fractures, a fracture report summary is displayed. This section displays the different properties for the fractures used to compute the transmissibility values.\u003c/p\u003e\n\u003ch5 id=\"description-of-derived-data\"\u003eDescription of Derived Data\u003c/h5\u003e\n\u003cp\u003eOne of the tables displays derived data, see the example here:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e               Tr   #con       Fcd       Area     KfWf         Kf      Wf       Xf        H       Km\r\n[cP.rm3/day/bars]               []       [m2]    [mDm]       [mD]     [m]      [m]      [m]     [mD]\r\n----------------------------------------------------------------------------------------------------\r\n          110.834     24   276.168   9315.748   54.889   3805.029   0.014   61.628   75.580   13.778\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTr\u003c/strong\u003e \u0026ndash; Accumulated computed transmissibilies for all reservoir cells intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003e#con\u003c/strong\u003e \u0026ndash; Number of reservoir cells intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFcd\u003c/strong\u003e \u0026ndash; Area weighted fracture conductivity divided by area weighted matrix transmissibility (Kf/Km)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArea\u003c/strong\u003e \u0026ndash; Area of reservoir cells(both active and inactive) intersected by the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKfWf\u003c/strong\u003e \u0026ndash; Multiplication of Kf by Wf (Kf * Wf)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKf\u003c/strong\u003e \u0026ndash; Area weighted average of permeability of fracture cells intersecting reservoir grid cells (using Area defined above)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWf\u003c/strong\u003e \u0026ndash; Area weighted average of width of fracture cells intersecting reservoir grid cells (using Area defined above)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXf\u003c/strong\u003e \u0026ndash; Half-length, defined as fracture area divided by half-height (Area/(H/2))\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eH\u003c/strong\u003e \u0026ndash; Longest continuous distance with fracture cells open for flow along a fracture grid column\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKm\u003c/strong\u003e \u0026ndash; Area weighted average of matrix transmissibility (using Area defined above)\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"differential-depletion-fracture-output\"\u003eDifferential Depletion Fracture Output\u003c/h4\u003e\n\u003cp\u003eIn addition to scaling the transmissibilities in the fracture output, using pressure differential depletion scaling will also provide a table with information regarding the scaling performed for each well. This table will show the well name, fracture name and the source of the Well Bore Hole Pressure (\u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e or \u003cstrong\u003eFixed User Defined WBHP\u003c/strong\u003e). For \u003cstrong\u003eWBHP From Summary Case\u003c/strong\u003e the \u003cstrong\u003eUser WBHP\u003c/strong\u003e column will describe the well pressure used for all time steps before the production starts according to the summary case information and the \u003cstrong\u003eActual WBHP\u003c/strong\u003e will describe the well pressure used in the scaling, which will be different from the \u003cstrong\u003eUser WBHP\u003c/strong\u003e if the scaling is performed for a time step following the well productions start. Finally the columns \u003cstrong\u003eMin Pressure Drop\u003c/strong\u003e and \u003cstrong\u003eMax Pressure Drop\u003c/strong\u003e describes the minimum and maximum well drawdown for this particular fracture.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e--\r\n-- Pressure Depletion Time step: 01.Feb 2001\r\n-- WBHP Source: WBHP From Summary Case\r\n-- User Defined WBHP: 200\r\n-- Well    Fracture      Actual WBHP   Min Pressure Drop   Max Pressure Drop   \r\n------------------------------------------------------------------------------\r\n-- B-1H    Fracture_01   221.68147     0.04077             45.10402            \r\n-- B-1H    Fracture_02   221.68147     0.00624             36.02608            \r\n-- B-4DH   Fracture_07   200.00000     28.21733            97.34970            \r\n-- \r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"export-of-fishbone-completion-data\"\u003eExport of Fishbone Completion Data\u003c/h3\u003e\n\u003cp\u003eThe transmissibility calculation for the fishbones is done following the above description except that when calculating the transmissibility for the laterals, the full cell volume is split among the laterals for calculation of the transmissibility. This is done by finding the direction of the main bore, and then dividing the cell size in this direction by the number of laterals in the cell when calculating the Peaceman radius.\u003c/p\u003e\n\u003cp\u003eAn example of the exported COMPDAT file is shown below. The calculated transmissibility contribution to the cell connection factor from each lateral or main bore part is included as a comment.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSPECS\r\n-- Well          Grp   I   J    RefDepth   WellType   \r\n   Well Path B   GR    26  45   1230       Oil        \\\r\n\\\r\nCOMPDAT\r\n-- Well            I      J      K1     K2     Status     SAT     TR               DIAM     KH     S     Df     DIR     r0     \r\n-- Well Path B main bore : 0.0569986\r\n   Well Path B     26     45     29     29     OPEN       1*      5.699858E-02      /\r\n-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\r\n-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\r\n-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\r\n-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\r\n-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\r\n-- Well Path B main bore : 0.230572\r\n   Well Path B     27     41     15     15     OPEN       1*      2.645858E-01      /\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eFor export with WPIMULT factors, the main bore diameter and direction are given in the export for cells which have both main bore and lateral contributions, while diameter and main direction of the first lateral is used for cells with no main bore contribution. Other parameters exported as part of COMPDAT are set to default.\u003c/p\u003e\n\u003cp\u003eThe \u003cem\u003eWPIMULT\u003c/em\u003e parameters are calculated, as for the perforation intervals, by ResInsight calculating both the transmissibility of the completion as described above, and in addition calculating the transmissibility based on the information exported in the COMPDAT keyword. The ratio between these two numbers is then exported as the \u003cem\u003eWPIMUT\u003c/em\u003e keyword.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSPEC\r\n-- Well          Grp   I   J    RefDepth   WellType   \r\n   Well Path B   GR    26  45   1230       Oil        \\\r\n\\\r\nCOMPDAT\r\n-- Well            I      J      K1     K2     Status     SAT     TR     DIAM        KH     S           Df     DIR     r0     \r\n-- Well Path B main bore : 0.0569986\r\n   Well Path B     26     45     29     29     OPEN       1*      1*     0.21600     1*     0.00000     1*     'Z'      /\r\n-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\r\n-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\r\n-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\r\n-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\r\n-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\r\n-- Well Path B main bore : 0.230572\r\n   Well Path B     27     41     15     15     OPEN       1*      1*     0.21600     1*     0.00000     1*     'Z'      /\r\n/\r\nWPIMULT\r\n-- Well            Mult         I      J      K      \r\n   Well Path B     0.70133      25     45     29      /\r\n   Well Path B     25.11396     27     41     15      /\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"completions-for-lgr-welspecl-and-compdatl\"\u003eCompletions for LGR (WELSPECL and COMPDATL)\u003c/h3\u003e\n\u003cp\u003eCompletion data for LGR grids are exported to a separate file having the same name as the main grid completions file postfixed by \u0026ldquo;_LGR\u0026rdquo;. Instead of using the WELSPECS and COMPDAT keywords, the WELSPECL and COMPDATL keywords are used. Those tables are simlar to the WELSPECS and COMPDAT tables, except from including the columns \u003cstrong\u003eLGR\u003c/strong\u003e and \u003cstrong\u003eLgrName\u003c/strong\u003e, respectively. The extra columns contains the name of the LGR grid.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSPECL\r\n-- Well      Grp   LGR      I   J   RefDepth   WellType   \r\n   UWell-1   1*    WELLI1   2   9   1*         OIL         /\r\n    /\r\nCOMPDATL\r\n-- Well      LgrName   I   J   K1   K2   Status   SAT   TR             DIAM      KH   S         Df   DIR   \r\n-- ---- Completions for completion type Perforation ----\r\n-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676\r\n   UWell-1   WELLI1    2   9   6    6    OPEN     1*    6.106763E+00   0.21600   1*   0.00000   1*   'Y'    /\r\n-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679\r\n   UWell-1   WELLI1    2   8   6    6    OPEN     1*    6.106791E+00   0.21600   1*   0.00000   1*   'Y'    /\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"lgr-for-completions-temporary-lgrs\"\u003eLGR for completions (Temporary LGRs)\u003c/h3\u003e\n\u003cp\u003eThe previous section describes the export of COMPDATL for completions intersecting existing LGRs, loaded from file. This section will describe how to have ResInsight create temporary LGRs around completions, and then export COMPDATL for those LGRs.\nTo accomplish this, do the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCreate LGRs for completions on selected well paths. See \u003ca href=\"/wells-and-completions/completionslgr/\"\u003eCompletions LGR\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eExport completions the usual way. See \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eIn addition to the completion data, the geometrical definition of all temporary LGRs is also exported into \u0026ldquo;*.dat\u0026rdquo; files.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"multi-segment-well-model\"\u003eMulti Segment Well Model\u003c/h2\u003e\n\u003cp\u003eIt is possible to export all the completions to a text file containing the Eclipse input data \nkeywords needed to represent the completions as a Multi Segment Well. This is done by checking the \u003cstrong\u003eInclude Multi Segment Well Model\u003c/strong\u003e. All completions are supported and are exported in somewhat different ways.\u003c/p\u003e\n\u003ch3 id=\"exported-msw-data\"\u003eExported MSW Data\u003c/h3\u003e\n\u003cp\u003eIn the output file there are data for three Eclipse keyword specified.\u003c/p\u003e\n\u003ch5 id=\"welsegs\"\u003eWELSEGS\u003c/h5\u003e\n\u003cp\u003eWELSEGS defines multi-segment wells. The list of entries contains information on the main stem, the ICDs at the fishbone subs and the fishbone laterals. A comment above each entry details which element (main bore / ICD / lateral) the entry is for.  Example:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSEGS\r\n-- Name            Dep 1          Tlen 1       Vol 1     Len\u0026amp;Dep     PresDrop     \r\n   Well Path A     4137.09154     87.00000     1*        ABS         H--           /\r\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length        Depth Change     Diam        Rough       \r\n-- Main stem\r\n-- Segment for sub 0\r\n   2             2            1              1              13.00000      0.53667          0.15200     0.00001      /\r\n-- Laterals\r\n-- Diam: MSW - Tubing Radius\r\n-- Rough: MSW - Open Hole Roughness Factor\r\n-- ICD\r\n   3             3            2              2              0.10000       0                0.15200     0.00001      /\r\n-- Fishbone 0 : Sub index 0 - Lateral 0\r\n   52            52           27             3              1.70326       -0.57276         0.00960     0.00100      /\r\n   53            53           27             52             2.34748       -0.81635         0.00960     0.00100      /\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eThe first \u003cem\u003eWELSEGS\u003c/em\u003e entry contains information about the well:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e - Name of well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDep 1\u003c/strong\u003e - TVD of start MD point, as given by the user in the Fishbones \u003cstrong\u003eStart MD\u003c/strong\u003e field.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTlen 1\u003c/strong\u003e - Point given by the user in the Fishbones \u003cstrong\u003eStart MD\u003c/strong\u003e field.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLen\u0026amp;Dep\u003c/strong\u003e - incremental or absolute, as specified by the user in the Fishbones property editor.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePresDrop\u003c/strong\u003e - specifies what is included in the pressure drop calculation, hydrostatic, friction or acceleration. Specified by user in the Fishbones property editor.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eThe following \u003cem\u003eWELSEGS\u003c/em\u003e entries contains information about each segment:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFirst Seg\u003c/strong\u003e, \u003cstrong\u003eLast Seg\u003c/strong\u003e \u0026ndash; Values are being exported pr segment, so both first and last segment number is the number of the segment being exported.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch Num\u003c/strong\u003e \u0026ndash; Branch number for segment being exported.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOutlet Seg\u003c/strong\u003e \u0026ndash; The segment the exported segment is connected to. For the main bore segments, this is the segment before them, for ICDs the segment number being exported and for fishbone laterals the segment on the main broe where the laterals are connected.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength\u003c/strong\u003e \u0026ndash; Length of segment (if incremental Len\u0026amp;Dep above) or length of segments including this along well (if absolute Len\u0026amp;Dep above). For ICDs length is set to 0.1.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Change\u003c/strong\u003e \u0026ndash; Depth of segment, incremental or absolute as for Length. For ICDs depth is set to 0.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiam\u003c/strong\u003e \u0026ndash; Diameter of segment. For main bore and ICD entries, the liner inner diameter for the Fishbones collection is used. For laterals, an effective diameter is calculated so that the diameter exported is the diameter which, assuming a circle, would give the same area as the area between the hole diameter and the tubing diameter.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRough\u003c/strong\u003e \u0026ndash; The roughness factor as entered by the user. Notice that a different value can be specified for the main bore and the laterals, as described above.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"compsegs\"\u003eCOMPSEGS\u003c/h5\u003e\n\u003cp\u003eAn example of the COMPSEGS keyword as exported is shown below.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eCOMPSEGS\r\n-- Name            \r\n   Well Path A      /\r\n-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \r\n   28     40     6      27            0.00000          1.70326         /\r\n   28     40     7      27            1.70326          2.34748         /\r\n   28     40     8      27            2.34748          2.96577         /\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eThe first COMPSEGS entry is a line with the well path name. Each following entry is for the segments in the well, and containing the following field:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eI\u003c/strong\u003e, \u003cstrong\u003eJ\u003c/strong\u003e and \u003cstrong\u003eK\u003c/strong\u003e \u0026ndash; The Eclipse cell index\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBranch no\u003c/strong\u003e \u0026ndash; Branch number for the segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Length\u003c/strong\u003e, \u003cstrong\u003eEnd Length\u003c/strong\u003e \u0026ndash; Start and end length along the well for the relevant segment.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"wsegvalv\"\u003eWSEGVALV\u003c/h5\u003e\n\u003cp\u003eAn example of the WSEGVALV keyword as exported is shown below.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWSEGVALV\r\n-- Well Name       Seg No     Cv          Ac          \r\n   Well Path A     3          1.50000     0.00008      /\r\n   Well Path A     5          1.50000     0.00008      /\r\n   Well Path A     7          1.50000     0.00008      /\r\n/\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eThe parameters exported in the WEGVALV keyword are\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; The name of the well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSeg No\u003c/strong\u003e \u0026ndash; Segment number along the well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCv\u003c/strong\u003e \u0026ndash; The ICD Flow Coefficient, as entered by the user.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAc\u003c/strong\u003e \u0026ndash; the total ICD area per sub, calculated as the area per ICD (given by the orifice radius) multiplied with the number of icd per Sub.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"export-of-fractures-and-perforations-as-multi-segment-wells\"\u003eExport of Fractures and Perforations as Multi-Segment Wells\u003c/h3\u003e\n\u003cp\u003eFractures and Perforations may also be exported as Multi-Segment Wells. In the case of Fractures, ResInsight will create one segment for the entire fracture, with a number of COMPSEGS-entries corresponding to the cells intersecting the fracture. In this case, the \u003cstrong\u003eDiam\u003c/strong\u003e and \u003cstrong\u003eRough\u003c/strong\u003e parameters are not used for anything and the length of the fracture segment is nominal. An example of a Fracture entry is shown below.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSEGS\r\n-- Name      Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \r\n   C-1 H     2575.39553     2919.53029     1*        INC         H--           /\r\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \r\n-- Fracture Segments\r\n-- Diam: MSW - Default Dummy\r\n-- Rough: MSW - Default Dummy\r\n-- Traversal Fracture 02 connected to Main stem segment 11\r\n   25            25           2              11             0.01000      0.00000          0.15000     0.00005      /\r\n    /\r\nCOMPSEGS\r\n-- Fractures\r\n-- Name      \r\n   C-1 H      /\r\n-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \r\n   27     43     1      2             11.27214         11.28214        /\r\n   26     44     1      2             11.27214         11.28214        /\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eThe entries for Perforations are simpler. No additional branches are created as the perforation intervals are all on the main bore and all perforated cells are listed as COMPSEG entries very similar to normal COMPDAT export of perforation intervals.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELSEGS\r\n-- Name       Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \r\n   B-1 AH     2530.38706     3137.28258     1*        INC         H--           /\r\n-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \r\n-- Main Stem Segments\r\n   2             2            1              1              16.33624     6.96924          0.15200     0.00001      /\r\n   3             3            1              2              11.77390     4.75668          0.15200     0.00001      /\r\n   4             4            1              3              9.49721      3.63598          0.15200     0.00001      /\r\n   5             5            1              4              6.77104      2.59228          0.15200     0.00001      /\r\n   6             6            1              5              29.44930     10.10431         0.15200     0.00001      /\r\n   7             7            1              6              27.93603     7.96718          0.15200     0.00001      /\r\n   8             8            1              7              13.95369     3.66086          0.15200     0.00001      /\r\n   /\r\nCOMPSEGS\r\n-- Name       \r\n   B-1 AH      /\r\n-- I      J      K     Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \r\n   10     24     1     1             3137.28258       3153.61882      /\r\n   10     24     2     1             3153.61882       3165.39273      /\r\n   9      24     2     1             3165.39273       3174.88994      /\r\n   9      25     2     1             3174.88994       3181.66098      /\r\n   9      25     3     1             3181.66098       3211.11028      /\r\n   9      25     5     1             3239.04631       3253.00000      /\r\n   /\r\n\u003c/code\u003e\u003c/pre\u003e\n",
                 url:      "/export/completionexport/"
             };
         
@@ -2163,8 +2196,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/contourmaps/"] = {
                 title:    "Contour Maps",
-                content:  " ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. ResInsight is able to export a contour map to a text file.\nCreating New Contour Maps Contour Maps can be created in many different ways:\n New Contour Map from the right-click menu of case or the Contour Maps project tree item underneath the case. These will create contour maps with default values. New Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result. Duplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.  Properties of the Contour Maps A contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the 2d Intersection Views with optional Axis Lines controlled with the Show Axis Lines toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See Map Projection Properties for the two latter).\nMap Projection Properties The Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.\nA set of parameters governs this projection:\n The first option Sample Spacing Factor controls how many 2D Grid Cells are used in the map. The factor is multiplied by the characteristic cell length/width of the 3D grid to get the 2D Cell Size. A smaller factor will thus create a finer Contour Map. The second option Show Contour Lines toggles on/off the contour lines in the view. The final control in the Projection Settings box is the Result Aggregation. Here the following options are available:     Aggregation Type Description     Oil Column A sum of SOIL * NTG * PORO * dZ   Gas Column A sum of SGAS * NTG * PORO * dZ   Hydrocarbon Column A sum of (SOIL + SGAS)* NTG * PORO * dZ   Arithmetic Mean A volume weighted arithmetic mean of the specified cell result   Harmonic Mean A volume weighted harmonic mean of the specified cell result   Geometric Mean A volume weighted geometric mean of the specified cell result   Volume Weighted Sum A volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO   Sum A sum of the specified cell result. Suitable for absolute quantities.   Top Value The first value encountered downwards vertically   Min Value The minimum cell result value in the volume underneath the 2D Element   Max Value The maximum cell result value in the volume underneath the 2D Element    For the Column options, no Cell Result is available in the property tree under the Contour Map.\nWeighting Means by Cell Result For the Arithmetic Mean, Geometric Mean and Harmonic Mean it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.\nDifference options Creating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the Cell Result item underneath the actual Contour Map in the project tree. This will display the Cell Result Property Editor to specify base case and/or base time step.\nContour Map Export ResInsight is able to export a contour map to a text file.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMaps.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.\nResInsight is able to \u003ca href=\"/export/contourmapexport/\"\u003eexport a contour map\u003c/a\u003e to a text file.\u003c/p\u003e\n\n\u003ch2 id=\"creating-new-contour-maps\"\u003eCreating New Contour Maps\u003c/h2\u003e\n\n\u003cp\u003eContour Maps can be created in many different ways:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eNew Contour Map from the right-click menu of case or the \u003cstrong\u003eContour Maps\u003c/strong\u003e project tree item underneath the case. These will create contour maps with default values.\u003c/li\u003e\n\u003cli\u003eNew Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result.\u003c/li\u003e\n\u003cli\u003eDuplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewContourMapFromCase.png\" alt=\"\" /\u003e \u003cimg src=\"/images/3d-main-window/NewContourMapFromFolder.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewContourMapFromView.png\" alt=\"\" /\u003e \u003cimg src=\"/images/3d-main-window/NewContourMapFromExisting.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"properties-of-the-contour-maps\"\u003eProperties of the Contour Maps\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapViewProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the \u003cstrong\u003e2d Intersection Views\u003c/strong\u003e with optional Axis Lines controlled with the \u003cstrong\u003eShow Axis Lines\u003c/strong\u003e toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See \u003cstrong\u003eMap Projection Properties\u003c/strong\u003e for the two latter).\u003c/p\u003e\n\n\u003ch2 id=\"map-projection-properties\"\u003eMap Projection Properties\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapProjectionProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.\u003c/p\u003e\n\n\u003cp\u003eA set of parameters governs this projection:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe first option \u003cstrong\u003eSample Spacing Factor\u003c/strong\u003e controls how many 2D Grid Cells are used in the map. The factor is multiplied by the characteristic cell length/width of the 3D grid to get the 2D Cell Size. A smaller factor will thus create a finer Contour Map.\u003c/li\u003e\n\u003cli\u003eThe second option \u003cstrong\u003eShow Contour Lines\u003c/strong\u003e toggles on/off the contour lines in the view.\u003c/li\u003e\n\u003cli\u003eThe final control in the \u003cstrong\u003eProjection Settings\u003c/strong\u003e box is the \u003cstrong\u003eResult Aggregation\u003c/strong\u003e. Here the following options are available:\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eAggregation Type\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eOil Column\u003c/td\u003e\n\u003ctd\u003eA sum of SOIL * NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eGas Column\u003c/td\u003e\n\u003ctd\u003eA sum of SGAS * NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eHydrocarbon Column\u003c/td\u003e\n\u003ctd\u003eA sum of (SOIL + SGAS)* NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eArithmetic Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted arithmetic mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eHarmonic Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted harmonic mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eGeometric Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted geometric mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eVolume Weighted Sum\u003c/td\u003e\n\u003ctd\u003eA volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eSum\u003c/td\u003e\n\u003ctd\u003eA sum of the specified cell result. Suitable for absolute quantities.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eTop Value\u003c/td\u003e\n\u003ctd\u003eThe first value encountered downwards vertically\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMin Value\u003c/td\u003e\n\u003ctd\u003eThe minimum cell result value in the volume underneath the 2D Element\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eMax Value\u003c/td\u003e\n\u003ctd\u003eThe maximum cell result value in the volume underneath the 2D Element\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eFor the Column options, no \u003cstrong\u003eCell Result\u003c/strong\u003e is available in the property tree under the Contour Map.\u003c/p\u003e\n\n\u003ch3 id=\"weighting-means-by-cell-result\"\u003eWeighting Means by Cell Result\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapProjectionWeights.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor the \u003cstrong\u003eArithmetic Mean\u003c/strong\u003e, \u003cstrong\u003eGeometric Mean\u003c/strong\u003e and \u003cstrong\u003eHarmonic Mean\u003c/strong\u003e it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.\u003c/p\u003e\n\n\u003ch2 id=\"difference-options\"\u003eDifference options\u003c/h2\u003e\n\n\u003cp\u003eCreating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the\n\u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eCell Result\u003c/strong\u003e item\nunderneath the actual \u003cstrong\u003eContour Map\u003c/strong\u003e in the project tree. This will display the \u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eCell Result\u003c/strong\u003e \u003ca href=\"/3d-main-window/cellresults/#eclipse-result-types\"\u003eProperty Editor\u003c/a\u003e to specify base case and/or base time step.\u003c/p\u003e\n\n\u003ch2 id=\"contour-map-export\"\u003eContour Map Export\u003c/h2\u003e\n\n\u003cp\u003eResInsight is able to \u003ca href=\"/export/contourmapexport/\"\u003eexport a contour map\u003c/a\u003e to a text file.\u003c/p\u003e\n",
+                content:  "ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. ResInsight is able to export a contour map to a text file.\nCreating New Contour Maps Contour Maps can be created in many different ways:\n New Contour Map from the right-click menu of case or the Contour Maps project tree item underneath the case. These will create contour maps with default values. New Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result. Duplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.  Properties of the Contour Maps A contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the 2d Intersection Views with optional Axis Lines controlled with the Show Axis Lines toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See Map Projection Properties for the two latter).\nMap Projection Properties The Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.\nA set of parameters governs this projection:\n The first option Sample Spacing Factor controls how many 2D Grid Cells are used in the map. The factor is multiplied by the characteristic cell length/width of the 3D grid to get the 2D Cell Size. A smaller factor will thus create a finer Contour Map. The second option Show Contour Lines toggles on/off the contour lines in the view. The final control in the Projection Settings box is the Result Aggregation. Here the following options are available:     Aggregation Type Description     Oil Column A sum of SOIL * NTG * PORO * dZ   Gas Column A sum of SGAS * NTG * PORO * dZ   Hydrocarbon Column A sum of (SOIL + SGAS)* NTG * PORO * dZ   Arithmetic Mean A volume weighted arithmetic mean of the specified cell result   Harmonic Mean A volume weighted harmonic mean of the specified cell result   Geometric Mean A volume weighted geometric mean of the specified cell result   Volume Weighted Sum A volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO   Sum A sum of the specified cell result. Suitable for absolute quantities.   Top Value The first value encountered downwards vertically   Min Value The minimum cell result value in the volume underneath the 2D Element   Max Value The maximum cell result value in the volume underneath the 2D Element    For the Column options, no Cell Result is available in the property tree under the Contour Map.\nWeighting Means by Cell Result For the Arithmetic Mean, Geometric Mean and Harmonic Mean it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.\nDifference options Creating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the Cell Result item underneath the actual Contour Map in the project tree. This will display the Cell Result [Property Editor] (/3d-main-window/cellresults/#eclipse-result-types) to specify base case and/or base time step.\nContour Map Export ResInsight is able to export a contour map to a text file.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMaps.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as Oil, Gas and Hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells. \nResInsight is able to \u003ca href=\"/export/contourmapexport/\"\u003eexport a contour map\u003c/a\u003e to a text file.\u003c/p\u003e\n\u003ch2 id=\"creating-new-contour-maps\"\u003eCreating New Contour Maps\u003c/h2\u003e\n\u003cp\u003eContour Maps can be created in many different ways:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eNew Contour Map from the right-click menu of case or the \u003cstrong\u003eContour Maps\u003c/strong\u003e project tree item underneath the case. These will create contour maps with default values.\u003c/li\u003e\n\u003cli\u003eNew Contour Map from 3D View in the Eclipse View right-click menu. This will create a contour map based on the existing 3D View with matching filters and result.\u003c/li\u003e\n\u003cli\u003eDuplicate Contour Map from the right-click menu of an existing Contour Map. This will copy the existing map.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewContourMapFromCase.png\" alt=\"\"\u003e \u003cimg src=\"/images/3d-main-window/NewContourMapFromFolder.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewContourMapFromView.png\" alt=\"\"\u003e \u003cimg src=\"/images/3d-main-window/NewContourMapFromExisting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"properties-of-the-contour-maps\"\u003eProperties of the Contour Maps\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapViewProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA contour Map has many of the same options available as a 3D View, but is always orthographic/parallel projection with no perspective projection or lighting available. Instead of the 3D Grid Box, the Contour Maps uses a 2D Grid simular to the \u003cstrong\u003e2d Intersection Views\u003c/strong\u003e with optional Axis Lines controlled with the \u003cstrong\u003eShow Axis Lines\u003c/strong\u003e toggle. The name of the map can be automatically generated from the Case Name, Property Type, Aggregation Type and Sample Spacing (See \u003cstrong\u003eMap Projection Properties\u003c/strong\u003e for the two latter).\u003c/p\u003e\n\u003ch2 id=\"map-projection-properties\"\u003eMap Projection Properties\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapProjectionProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Map Projection settings control how the 3D Data is aggregated onto the 2D plane. In all cases the results are calculated for a square 2D Cell lying in an arbitrary z-plane of the 3D Grid. For each 2D cell a cuboid extrusion in the full bounding extent of the 3D grid is created and this cuboid extrusion is used to calculate the volume of intersection with the 3D Grid cells for all volume weighted sums and averages. For the regular sums, a vertical ray through the center of the 2D cell is used instead. Since the ray may travel through multiple cells in the same K-layer, all the values from within one K-layer are averaged before being added to the sum.\u003c/p\u003e\n\u003cp\u003eA set of parameters governs this projection:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe first option \u003cstrong\u003eSample Spacing Factor\u003c/strong\u003e controls how many 2D Grid Cells are used in the map. The factor is multiplied by the characteristic cell length/width of the 3D grid to get the 2D Cell Size. A smaller factor will thus create a finer Contour Map.\u003c/li\u003e\n\u003cli\u003eThe second option \u003cstrong\u003eShow Contour Lines\u003c/strong\u003e toggles on/off the contour lines in the view.\u003c/li\u003e\n\u003cli\u003eThe final control in the \u003cstrong\u003eProjection Settings\u003c/strong\u003e box is the \u003cstrong\u003eResult Aggregation\u003c/strong\u003e. Here the following options are available:\u003c/li\u003e\n\u003c/ul\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eAggregation Type\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eOil Column\u003c/td\u003e\n\u003ctd\u003eA sum of SOIL * NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGas Column\u003c/td\u003e\n\u003ctd\u003eA sum of SGAS * NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHydrocarbon Column\u003c/td\u003e\n\u003ctd\u003eA sum of (SOIL + SGAS)* NTG * PORO * dZ\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eArithmetic Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted arithmetic mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eHarmonic Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted harmonic mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGeometric Mean\u003c/td\u003e\n\u003ctd\u003eA volume weighted geometric mean of the specified cell result\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eVolume Weighted Sum\u003c/td\u003e\n\u003ctd\u003eA volume weighted sum of the specified cell result. Suitable for volume fractions such as SOIL or PORO\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSum\u003c/td\u003e\n\u003ctd\u003eA sum of the specified cell result. Suitable for absolute quantities.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTop Value\u003c/td\u003e\n\u003ctd\u003eThe first value encountered downwards vertically\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMin Value\u003c/td\u003e\n\u003ctd\u003eThe minimum cell result value in the volume underneath the 2D Element\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMax Value\u003c/td\u003e\n\u003ctd\u003eThe maximum cell result value in the volume underneath the 2D Element\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eFor the Column options, no \u003cstrong\u003eCell Result\u003c/strong\u003e is available in the property tree under the Contour Map.\u003c/p\u003e\n\u003ch3 id=\"weighting-means-by-cell-result\"\u003eWeighting Means by Cell Result\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ContourMapProjectionWeights.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor the \u003cstrong\u003eArithmetic Mean\u003c/strong\u003e, \u003cstrong\u003eGeometric Mean\u003c/strong\u003e and \u003cstrong\u003eHarmonic Mean\u003c/strong\u003e it is also possible to specify a cell result as a weighting parameter in addition to the regular weighting by volume of intersection. The total weight will then be the volume of intersection multiplied by the specified cell result. The full range of regular cell results is available for this use.\u003c/p\u003e\n\u003ch2 id=\"difference-options\"\u003eDifference options\u003c/h2\u003e\n\u003cp\u003eCreating a Contour Map as a difference with a specific base case and/or base time step is performed by clicking the \n\u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eCell Result\u003c/strong\u003e item\nunderneath the actual \u003cstrong\u003eContour Map\u003c/strong\u003e in the project tree. This will display the \u003cimg src=\"https://resinsight.org/images/3d-main-window/CellResult.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eCell Result\u003c/strong\u003e [Property Editor]\n(/3d-main-window/cellresults/#eclipse-result-types) to specify base case and/or base time step.\u003c/p\u003e\n\u003ch2 id=\"contour-map-export\"\u003eContour Map Export\u003c/h2\u003e\n\u003cp\u003eResInsight is able to \u003ca href=\"/export/contourmapexport/\"\u003eexport a contour map\u003c/a\u003e to a text file.\u003c/p\u003e\n",
                 url:      "/3d-main-window/contourmaps/"
             };
         
@@ -2172,8 +2205,8 @@ if (!doNotTrack) {
          
             window.store["/import/pasteexceltimedata/"] = {
                 title:    "Paste Excel Time History Data",
-                content:  " When text have been copied to the operating system\u0026rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the Plot Main Window Project Tree and select Paste Excel Data to Summary Plot. Then a paste options dialog will appear.\nPaste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:\n Curve Prefix \u0026ndash; Curve name prefix for all curves created from the pasted data. Line Style \u0026ndash; Line style to use for the curves created from the pasted data. Symbol \u0026ndash; Line symbol to use for each data point on the curves created from the pasted data. Symbol Skip Distance \u0026ndash; Minimum distance between two adjacent symbols on the curves. If two data points on a curve is closer than the specified distance, a symbol is not drawn for one of the data points. Default value is 0, which will draw a symbol at all data points on the curves regardless of the distance between data points.  ",
-                html:     "\n\n\u003cp\u003eWhen text have been copied to the operating system\u0026rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e and select \u003cstrong\u003ePaste Excel Data to Summary Plot\u003c/strong\u003e. Then a paste options dialog will appear.\u003c/p\u003e\n\n\u003ch2 id=\"paste-options-dialog\"\u003ePaste Options Dialog\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/import/PasteExcelData.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eMost of the fields in this dialog are the same as in the \u003ca href=\"/import/observeddata/#csv-txt-import-options-dialog\"\u003eCSV/txt import options dialog\u003c/a\u003e. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Prefix\u003c/strong\u003e \u0026ndash; Curve name prefix for all curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Style\u003c/strong\u003e \u0026ndash; Line style to use for the curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSymbol\u003c/strong\u003e \u0026ndash; Line symbol to use for each data point on the curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSymbol Skip Distance\u003c/strong\u003e \u0026ndash; Minimum distance between two adjacent symbols on the curves. If two data points on a curve is closer than the specified distance, a symbol is not drawn for one of the data points. Default value is 0, which will draw a symbol at all data points on the curves regardless of the distance between data points.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "When text have been copied to the operating system\u0026rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the Plot Main Window Project Tree and select Paste Excel Data to Summary Plot. Then a paste options dialog will appear.\nPaste Options Dialog Most of the fields in this dialog are the same as in the CSV/txt import options dialog. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:\n Curve Prefix \u0026ndash; Curve name prefix for all curves created from the pasted data. Line Style \u0026ndash; Line style to use for the curves created from the pasted data. Symbol \u0026ndash; Line symbol to use for each data point on the curves created from the pasted data. Symbol Skip Distance \u0026ndash; Minimum distance between two adjacent symbols on the curves. If two data points on a curve is closer than the specified distance, a symbol is not drawn for one of the data points. Default value is 0, which will draw a symbol at all data points on the curves regardless of the distance between data points.  ",
+                html:     "\u003cp\u003eWhen text have been copied to the operating system\u0026rsquo;s clipboard, it will be possible to paste that text into a summary plot. Right click on a summary plot in the \u003cstrong\u003ePlot Main Window Project Tree\u003c/strong\u003e and select \u003cstrong\u003ePaste Excel Data to Summary Plot\u003c/strong\u003e. Then a paste options dialog will appear.\u003c/p\u003e\n\u003ch2 id=\"paste-options-dialog\"\u003ePaste Options Dialog\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/PasteExcelData.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eMost of the fields in this dialog are the same as in the \u003ca href=\"/import/observeddata/#csv-txt-import-options-dialog\"\u003eCSV/txt import options dialog\u003c/a\u003e. Please see that section for documentation on those fields. The fields specific to the paste options dialog are as follows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Prefix\u003c/strong\u003e \u0026ndash; Curve name prefix for all curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Style\u003c/strong\u003e \u0026ndash; Line style to use for the curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSymbol\u003c/strong\u003e \u0026ndash; Line symbol to use for each data point on the curves created from the pasted data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSymbol Skip Distance\u003c/strong\u003e \u0026ndash; Minimum distance between two adjacent symbols on the curves. If two data points on a curve is closer than the specified distance, a symbol is not drawn for one of the data points. Default value is 0, which will draw a symbol at all data points on the curves regardless of the distance between data points.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/import/pasteexceltimedata/"
             };
         
@@ -2181,8 +2214,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/pythonexamples/"] = {
                 title:    "Python Examples",
-                content:  " This pages is created based on the content in the PythonExamples folder located inside the rips module, made available online for convenience.\nAllCases ################################################################################### # This example will connect to ResInsight, retrieve a list of cases and print info # ################################################################################### # Import the ResInsight Processing Server Module import rips # Connect to ResInsight resinsight = rips.Instance.find() if resinsight is not None: # Get a list of all cases cases = resinsight.project.cases() print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;) for case in cases: print(\u0026quot;Case id: \u0026quot; + str(case.case_id)) print(\u0026quot;Case name: \u0026quot; + case.name) print(\u0026quot;Case type: \u0026quot; + case.type) print(\u0026quot;Case grid path: \u0026quot; + case.grid_path()) timesteps = case.time_steps() for t in timesteps: print(\u0026quot;Year: \u0026quot; + str(t.year)) print(\u0026quot;Month: \u0026quot; + str(t.month))  CaseGridGroup import os import rips resinsight = rips.Instance.find() case_paths = [] case_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real0/BRUGGE_0000.EGRID\u0026quot;) case_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real10/BRUGGE_0010.EGRID\u0026quot;) for case_path in case_paths: assert os.path.exists(case_path), \u0026quot;You need to set valid case paths for this script to work\u0026quot; case_group = resinsight.project.create_grid_case_group(case_paths=case_paths) case_group.print_object_info() #stat_cases = caseGroup.statistics_cases() #case_ids = [] #for stat_case in stat_cases: # stat_case.set_value(\u0026quot;DynamicPropertiesToCalculate\u0026quot;, [\u0026quot;SWAT\u0026quot;]) # stat_case.update() # case_ids.append(stat_case.get_value(\u0026quot;CaseId\u0026quot;)) case_group.compute_statistics() view = case_group.views()[0] cell_result = view.set_cell_result() cell_result.set_value(\u0026quot;ResultVariable\u0026quot;, \u0026quot;PRESSURE_DEV\u0026quot;) cell_result.update()  CaseInfoStreamingExample ############################################################################### # This example will get the cell info for the active cells for the first case ############################################################################### # Import the ResInsight Processing Server Module import rips # Connect to ResInsight resinsight = rips.Instance.find() # Get the first case. This will fail if you haven't loaded any cases case = resinsight.project.cases()[0] # Get the cell count object cell_counts = case.cell_count() print(\u0026quot;Number of active cells: \u0026quot; + str(cell_counts.active_cell_count)) print(\u0026quot;Total number of reservoir cells: \u0026quot; + str(cell_counts.reservoir_cell_count)) # Get information for all active cells active_cell_infos = case.cell_info_for_active_cells() # A simple check on the size of the cell info assert(cell_counts.active_cell_count == len(active_cell_infos)) # Print information for the first active cell print(\u0026quot;First active cell: \u0026quot;) print(active_cell_infos[0])  CommandExample ############################################################################### # This example will show setting time step, window size and export snapshots and properties ############################################################################### import os import tempfile import rips # Load instance resinsight = rips.Instance.find() # Set window sizes resinsight.set_main_window_size(width=800, height=500) resinsight.set_plot_window_size(width=1000, height=1000) # Retrieve first case case = resinsight.project.cases()[0] # Get a view view1 = case.views()[0] # Clone the view view2 = view1.clone() # Set the time step for view1 only view1.set_time_step(time_step=2) # Set cell result to SOIL view1.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable='SOIL') # Create a temporary directory which will disappear at the end of this script # If you want to keep the files, provide a good path name instead of tmpdirname with tempfile.TemporaryDirectory(prefix=\u0026quot;rips\u0026quot;) as tmpdirname: print(\u0026quot;Temporary folder: \u0026quot;, tmpdirname) # Set export folder for snapshots and properties resinsight.set_export_folder(export_type='SNAPSHOTS', path=tmpdirname) resinsight.set_export_folder(export_type='PROPERTIES', path=tmpdirname) # Export all snapshots resinsight.project.export_snapshots() assert(len(os.listdir(tmpdirname)) \u0026gt; 0) # Export properties in the view view1.export_property() # Check that the exported file exists expected_file_name = case.name + \u0026quot;-\u0026quot; + str(\u0026quot;3D_View\u0026quot;) + \u0026quot;-\u0026quot; + \u0026quot;T2\u0026quot; + \u0026quot;-SOIL\u0026quot; full_path = tmpdirname + \u0026quot;/\u0026quot; + expected_file_name # Print contents of temporary folder print(os.listdir(tmpdirname)) assert(os.path.exists(full_path))  Create WBS Plot import os # Load ResInsight Processing Server Client Library import rips # Connect to ResInsight instance resInsight = rips.Instance.find() cases = resInsight.project.cases() well_paths = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_LessWellPaths') well_log_files = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS') if len(well_paths) \u0026lt; 1: print(\u0026quot;No well paths in project\u0026quot;) exit(1) print(well_paths) for case in cases: if case.type == \u0026quot;GeoMechCase\u0026quot;: print (case.case_id) case_path = case.grid_path() folder_name = os.path.dirname(case_path) case.import_formation_names(formation_files=['D:/Projects/ResInsight-regression-test/ModelData/norne/Norne_ATW2013.lyr']) # create a folder to hold the snapshots dirname = os.path.join(folder_name, 'snapshots') print(\u0026quot;Exporting to: \u0026quot; + dirname) for well_path in well_paths: wbsplot = case.create_well_bore_stability_plot(well_path=well_path, time_step=0) wbsplot.export_snapshot(export_folder=dirname)  ErrorHandling ################################################################### # This example demonstrates the use of ResInsight exceptions # for proper error handling ################################################################### import rips import grpc import tempfile resinsight = rips.Instance.find() case = None # Try loading a non-existing case. We should get a grpc.RpcError exception from the server try: case = resinsight.project.load_case(\u0026quot;Nonsense\u0026quot;) except grpc.RpcError as e: print(\u0026quot;Expected Server Exception Received while loading case: \u0026quot;, e) # Try loading well paths from a non-existing folder. We should get a grpc.RpcError exception from the server try: well_path_files = resinsight.project.import_well_paths(well_path_folder=\u0026quot;NONSENSE/NONSENSE\u0026quot;) except grpc.RpcError as e: print(\u0026quot;Expected Server Exception Received while loading wellpaths: \u0026quot;, e) # Try loading well paths from an existing but empty folder. We should get a warning. try: with tempfile.TemporaryDirectory() as tmpdirname: well_path_files = resinsight.project.import_well_paths(well_path_folder=tmpdirname) assert(len(well_path_files) == 0) assert(resinsight.project.has_warnings()) print(\u0026quot;Should get warnings below\u0026quot;) for warning in resinsight.project.warnings(): print (warning) except grpc.RpcError as e: print(\u0026quot;Unexpected Server Exception caught!!!\u0026quot;, e) case = resinsight.project.case(case_id=0) if case is not None: results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0) active_cell_count = len(results) # Send the results back to ResInsight inside try / except construct try: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0) print(\u0026quot;Everything went well as expected\u0026quot;) except: # Match any exception, but it should not happen print(\u0026quot;Ooops!\u0026quot;) # Add another value, so this is outside the bounds of the active cell result storage results.append(1.0) # This time we should get a grpc.RpcError exception, which is a server side error. try: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0) print(\u0026quot;Everything went well??\u0026quot;) except grpc.RpcError as e: print(\u0026quot;Expected Server Exception Received: \u0026quot;, e) except IndexError: print (\u0026quot;Got index out of bounds error. This shouldn't happen here\u0026quot;) # With a chunk size exactly matching the active cell count the server will not # be able to see any error as it will successfully close the stream after receiving # the correct number of values, even if the python client has more chunks to send case.chunk_size = active_cell_count try: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0) print(\u0026quot;Everything went well??\u0026quot;) except grpc.RpcError as e: print(\u0026quot;Got unexpected server exception\u0026quot;, e, \u0026quot;This should not happen now\u0026quot;) except IndexError: print (\u0026quot;Got expected index out of bounds error on client side\u0026quot;)  ExportContourMaps # Load ResInsight Processing Server Client Library import rips import tempfile import pathlib # Connect to ResInsight instance resInsight = rips.Instance.find() # Data will be written to temp tmpdir = pathlib.Path(tempfile.gettempdir()) # Find all eclipse contour maps of the project contour_maps = resInsight.project.contour_maps(rips.ContourMapType.ECLIPSE) print(\u0026quot;Number of eclipse contour maps:\u0026quot;, len(contour_maps)) # Export the contour maps to a text file for (index, contour_map) in enumerate(contour_maps): filename = \u0026quot;eclipse_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot; filepath = tmpdir / filename print(\u0026quot;Exporting to:\u0026quot;, filepath) contour_map.export_to_text(str(filepath)) # The contour maps is also available for a Case cases = resInsight.project.cases() for case in cases: contour_maps = case.contour_maps(rips.ContourMapType.GEO_MECH) # Export the contour maps to a text file for (index, contour_map) in enumerate(contour_maps): filename = \u0026quot;geomech_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot; filepath = tmpdir / filename print(\u0026quot;Exporting to:\u0026quot;, filepath) contour_map.export_to_text(str(filepath))  ExportPlots # Import the tempfile module import tempfile # Load ResInsight Processing Server Client Library import rips # Connect to ResInsight instance resInsight = rips.Instance.find() # Get a list of all plots plots = resInsight.project.plots() export_folder = tempfile.mkdtemp() print(\u0026quot;Exporting to: \u0026quot; + export_folder) for plot in plots: plot.export_snapshot(export_folder=export_folder) plot.export_data_as_las(export_folder=export_folder) plot.export_data_as_ascii(export_folder=export_folder)  ExportSnapshots ############################################################################ # This script will export snapshots for two properties in every loaded case # And put them in a snapshots folder in the same folder as the case grid ############################################################################ import os import rips # Load instance resinsight = rips.Instance.find() cases = resinsight.project.cases() # Set main window size resinsight.set_main_window_size(width=800, height=500) n = 5 # every n-th time_step for snapshot property_list = ['SOIL', 'PRESSURE'] # list of parameter for snapshot print (\u0026quot;Looping through cases\u0026quot;) for case in cases: print(\u0026quot;Case name: \u0026quot;, case.name) print(\u0026quot;Case id: \u0026quot;, case.case_id) # Get grid path and its folder name case_path = case.grid_path() folder_name = os.path.dirname(case_path) # create a folder to hold the snapshots dirname = os.path.join(folder_name, 'snapshots') if os.path.exists(dirname) is False: os.mkdir(dirname) print (\u0026quot;Exporting to folder: \u0026quot; + dirname) resinsight.set_export_folder(export_type='SNAPSHOTS', path=dirname) time_steps = case.time_steps() print('Number of time_steps: ' + str(len(time_steps))) view = case.views()[0] for property in property_list: view.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable=property) for time_step in range(0, len(time_steps), 10): view.set_time_step(time_step = time_step) view.export_snapshot()  GridInformation ###################################################################################### # This example prints information about the grids of all cases in the current project ###################################################################################### import rips resinsight = rips.Instance.find() cases = resinsight.project.cases() print(\u0026quot;Number of cases found: \u0026quot;, len(cases)) for case in cases: print(case.name) grids = case.grids() print(\u0026quot;Number of grids: \u0026quot;, len(grids)) for grid in grids: print(\u0026quot;Grid dimensions: \u0026quot;, grid.dimensions())  Import Well Paths # Load ResInsight Processing Server Client Library import rips # Connect to ResInsight instance resInsight = rips.Instance.find() well_path_names = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/norne/wellpaths') if resInsight.project.has_warnings(): for warning in resInsight.project.warnings(): print(warning) for well_path_name in well_path_names: print(\u0026quot;Imported from folder: \u0026quot; + well_path_name) well_path_names = resInsight.project.import_well_paths(well_path_files=['D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/E-3H.json', 'D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/C-1H.json']) if resInsight.project.has_warnings(): for warning in resInsight.project.warnings(): print(warning) for well_path_name in well_path_names: print(\u0026quot;Imported from indivdual files: \u0026quot; + well_path_name) well_path_names = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS') if resInsight.project.has_warnings(): for warning in resInsight.project.warnings(): print(warning) for well_path_name in well_path_names: print(\u0026quot;Imported well log file for: \u0026quot; + well_path_name)  InputPropTestAsync ######################################################################################## # This example generates a derived property in an asynchronous manner # Meaning it does not wait for all the data for each stage to be read before proceeding ######################################################################################## import rips import time # Internal function for creating a result from a small chunk of poro and permx results # The return value of the function is a generator for the results rather than the result itself. def create_result(poro_chunks, permx_chunks): # Loop through all the chunks of poro and permx in order for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks): resultChunk = [] # Loop through all the values inside the chunks, in order for (poro, permx) in zip(poroChunk.values, permxChunk.values): resultChunk.append(poro * permx) # Return a generator object that behaves like a Python iterator yield resultChunk resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] # Get a generator for the poro results. The generator will provide a chunk each time it is iterated poro_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0) # Get a generator for the permx results. The generator will provide a chunk each time it is iterated permx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0) # Send back the result with the result provided by a generator object. # Iterating the result generator will cause the script to read from the poro and permx generators # And return the result of each iteration case.set_active_cell_property_async(create_result(poro_chunks, permx_chunks), 'GENERATED', 'POROPERMXAS', 0) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')  InputPropTestSync ######################################################################################## # This example generates a derived property in an synchronous manner # Meaning it completes reading each result before calculating the derived result # See InputPropTestAsync for how to do this asynchronously instead. ######################################################################################## import rips import time import grpc resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] # Read poro result into list poro_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0) # Read permx result into list permx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0) # Generate output result results = [] for (poro, permx) in zip(poro_results, permx_results): results.append(poro * permx) try: # Send back output result case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0) except grpc.RpcError as e: print(\u0026quot;Exception Received: \u0026quot;, e) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')  InstanceExample ####################################### # This example connects to ResInsight ####################################### import rips resinsight = rips.Instance.find() if resinsight is None: print('ERROR: could not find ResInsight') else: print('Successfully connected to ResInsight')  LaunchWithCommandLineOptions # Load ResInsight Processing Server Client Library import rips # Launch ResInsight with last project file and a Window size of 600x1000 pixels resinsight = rips.Instance.launch(command_line_parameters=['--last', '--size', 600, 1000]) # Get a list of all cases cases = resinsight.project.cases() print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;) for case in cases: print(\u0026quot;Case name: \u0026quot; + case.name) print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())  SelectedCases ############################################################################ # This example returns the currently selected cases in ResInsight # Because running this script in the GUI takes away the selection # This script does not run successfully from within the ResInsight GUI # And will need to be run from the command line separately from ResInsight ############################################################################ import rips resinsight = rips.Instance.find() if resinsight is not None: cases = resinsight.project.selected_cases() print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;) for case in cases: print(case.name) for property in case.available_properties('DYNAMIC_NATIVE'): print(property)  SetCellResult ###################################################################### # This script applies a cell result to the first view in the project ###################################################################### import rips resinsight = rips.Instance.find() view = resinsight.project.views()[0] view.apply_cell_result(result_type='STATIC_NATIVE', result_variable='DX')  SetFlowDiagnosticsResult ###################################################################### # This script applies a flow diagnostics cell result to the first view in the project ###################################################################### # Load ResInsight Processing Server Client Library import rips # Connect to ResInsight instance resinsight = rips.Instance.find() view = resinsight.project.view(view_id=1) #view.apply_flow_diagnostics_cell_result(result_variable='Fraction', # selection_mode='FLOW_TR_INJ_AND_PROD') # Example of setting individual wells. Commented out because well names are case specific. view.apply_flow_diagnostics_cell_result(result_variable='Fraction', selection_mode='FLOW_TR_BY_SELECTION', injectors = ['C-1H', 'C-2H', 'F-2H'], producers = ['B-1AH', 'B-3H', 'D-1H'])  SetGridProperties ###################################################################### # This script sets values for SOIL for all grid cells in the first case in the project ###################################################################### import rips resinsight = rips.Instance.find() case = resinsight.project.case(case_id=0) total_cell_count = case.cell_count().reservoir_cell_count values = [] for i in range(0, total_cell_count): values.append(i % 2 * 0.75); print(\u0026quot;Applying values to full grid\u0026quot;) case.set_grid_property(values, 'DYNAMIC_NATIVE', 'SOIL', 0)  SoilAverageAsync ########################################################################################### # This example will asynchronously calculate the average value for SOIL for all time steps ########################################################################################### import rips import itertools import time resinsight = rips.Instance.find() start = time.time() # Get the case with case id 0 case = resinsight.project.case(case_id=0) # Get a list of all time steps timeSteps = case.time_steps() averages = [] for i in range(0, len(timeSteps)): # Get the results from time step i asynchronously # It actually returns a generator object almost immediately result_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i) mysum = 0.0 count = 0 # Loop through and append the average. each time we loop resultChunks # We will trigger a read of the input data, meaning the script will start # Calculating averages before the whole resultValue for this time step has been received for chunk in result_chunks: mysum += sum(chunk.values) count += len(chunk.values) averages.append(mysum/count) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(averages)  SoilAverageSync ########################################################################################### # This example will synchronously calculate the average value for SOIL for all time steps ########################################################################################### import rips import itertools import time resinsight = rips.Instance.find() start = time.time() # Get the case with case id 0 case = resinsight.project.case(case_id=0) # Get a list of all time steps time_steps = case.time_steps() averages = [] for i in range(0, len(time_steps)): # Get a list of all the results for time step i results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i) mysum = sum(results) averages.append(mysum/len(results)) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(averages)  SoilPorvAsync ############################################################################## # This example will create a derived result for each time step asynchronously ############################################################################## import rips import time # Internal function for creating a result from a small chunk of soil and porv results # The return value of the function is a generator for the results rather than the result itself. def create_result(soil_chunks, porv_chunks): for (soil_chunk, porv_chunk) in zip(soil_chunks, porv_chunks): resultChunk = [] number = 0 for (soil_value, porv_value) in zip(soil_chunk.values, porv_chunk.values): resultChunk.append(soil_value * porv_value) # Return a Python generator yield resultChunk resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] timeStepInfo = case.time_steps() # Get a generator for the porv results. The generator will provide a chunk each time it is iterated porv_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORV', 0) # Read the static result into an array, so we don't have to transfer it for each iteration # Note we use the async method even if we synchronise here, because we need the values chunked # ... to match the soil chunks porv_array = [] for porv_chunk in porv_chunks: porv_array.append(porv_chunk) for i in range (0, len(timeStepInfo)): # Get a generator object for the SOIL property for time step i soil_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i) # Create the generator object for the SOIL * PORV derived result result_generator = create_result(soil_chunks, iter(porv_array)) # Send back the result asynchronously with a generator object case.set_active_cell_property_async(result_generator, 'GENERATED', 'SOILPORVAsync', i) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVAsync')  SoilPorvSync ############################################################################## # This example will create a derived result for each time step synchronously ############################################################################## import rips import time resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] # Read the full porv result porv_results = case.active_cell_property('STATIC_NATIVE', 'PORV', 0) time_step_info = case.time_steps() for i in range (0, len(time_step_info)): # Read the full SOIl result for time step i soil_results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i) # Generate the result by looping through both lists in order results = [] for (soil, porv) in zip(soil_results, porv_results): results.append(soil * porv) # Send back result case.set_active_cell_property(results, 'GENERATED', 'SOILPORVSync', i) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVSync')  ViewExample ############################################################# # This example will alter the views of all cases # By setting the background color and toggle the grid box # Also clones the first view ############################################################# import rips # Connect to ResInsight instance resinsight = rips.Instance.find() # Check if connection worked if resinsight is not None: # Get a list of all cases cases = resinsight.project.cases() for case in cases: # Get a list of all views views = case.views() for view in views: # Set some parameters for the view view.set_show_grid_box(not view.show_grid_box()) view.set_background_color(\u0026quot;#3388AA\u0026quot;) # Update the view in ResInsight view.update() # Clone the first view new_view = views[0].clone() view.set_show_grid_box(False) new_view.set_background_color(\u0026quot;#FFAA33\u0026quot;) new_view.update()  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis pages is created based on the content in the \u003cstrong\u003ePythonExamples\u003c/strong\u003e folder located inside the \u003cstrong\u003erips\u003c/strong\u003e module, made available online for convenience.\u003c/p\u003e\n\n\u003ch1 id=\"allcases\"\u003eAllCases\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###################################################################################\n# This example will connect to ResInsight, retrieve a list of cases and print info\n# \n###################################################################################\n\n# Import the ResInsight Processing Server Module\nimport rips\n\n# Connect to ResInsight\nresinsight  = rips.Instance.find()\nif resinsight is not None:\n    # Get a list of all cases\n    cases = resinsight.project.cases()\n\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\n    for case in cases:\n        print(\u0026quot;Case id: \u0026quot; + str(case.case_id))\n        print(\u0026quot;Case name: \u0026quot; + case.name)\n        print(\u0026quot;Case type: \u0026quot; + case.type)\n        print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\n        \n        timesteps = case.time_steps()\n        for t in timesteps:\n            print(\u0026quot;Year: \u0026quot; + str(t.year))\n            print(\u0026quot;Month: \u0026quot; + str(t.month))\n        \n    \n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"casegridgroup\"\u003eCaseGridGroup\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003eimport os\nimport rips\n\nresinsight  = rips.Instance.find()\n\ncase_paths = []\ncase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real0/BRUGGE_0000.EGRID\u0026quot;)\ncase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real10/BRUGGE_0010.EGRID\u0026quot;)\nfor case_path in case_paths:\n    assert os.path.exists(case_path), \u0026quot;You need to set valid case paths for this script to work\u0026quot;\n\ncase_group = resinsight.project.create_grid_case_group(case_paths=case_paths)\n\ncase_group.print_object_info()\n    \n#stat_cases = caseGroup.statistics_cases()\n#case_ids = []\n#for stat_case in stat_cases:\n#    stat_case.set_value(\u0026quot;DynamicPropertiesToCalculate\u0026quot;, [\u0026quot;SWAT\u0026quot;])\n#    stat_case.update()\n#    case_ids.append(stat_case.get_value(\u0026quot;CaseId\u0026quot;))\n\ncase_group.compute_statistics()\n\nview = case_group.views()[0]\ncell_result = view.set_cell_result()\ncell_result.set_value(\u0026quot;ResultVariable\u0026quot;, \u0026quot;PRESSURE_DEV\u0026quot;)\ncell_result.update()\n        \n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"caseinfostreamingexample\"\u003eCaseInfoStreamingExample\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###############################################################################\n# This example will get the cell info for the active cells for the first case\n###############################################################################\n\n# Import the ResInsight Processing Server Module\nimport rips\n\n# Connect to ResInsight\nresinsight  = rips.Instance.find()\n\n# Get the first case. This will fail if you haven't loaded any cases\ncase = resinsight.project.cases()[0]\n\n# Get the cell count object\ncell_counts = case.cell_count()\nprint(\u0026quot;Number of active cells: \u0026quot; + str(cell_counts.active_cell_count))\nprint(\u0026quot;Total number of reservoir cells: \u0026quot; + str(cell_counts.reservoir_cell_count))\n\n# Get information for all active cells\nactive_cell_infos = case.cell_info_for_active_cells()\n\n# A simple check on the size of the cell info\nassert(cell_counts.active_cell_count == len(active_cell_infos))\n\n# Print information for the first active cell\nprint(\u0026quot;First active cell: \u0026quot;)\nprint(active_cell_infos[0])\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"commandexample\"\u003eCommandExample\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###############################################################################\n# This example will show setting time step, window size and export snapshots and properties\n###############################################################################\nimport os\nimport tempfile\nimport rips\n\n# Load instance\nresinsight = rips.Instance.find()\n\n# Set window sizes\nresinsight.set_main_window_size(width=800, height=500)\nresinsight.set_plot_window_size(width=1000, height=1000)\n\n\n# Retrieve first case\ncase = resinsight.project.cases()[0]\n\n# Get a view\nview1 = case.views()[0]\n\n# Clone the view\nview2 = view1.clone()\n\n# Set the time step for view1 only\nview1.set_time_step(time_step=2)\n\n# Set cell result to SOIL\nview1.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable='SOIL')\n\n\n# Create a temporary directory which will disappear at the end of this script\n# If you want to keep the files, provide a good path name instead of tmpdirname\nwith tempfile.TemporaryDirectory(prefix=\u0026quot;rips\u0026quot;) as tmpdirname:\n    print(\u0026quot;Temporary folder: \u0026quot;, tmpdirname)\n    \n    # Set export folder for snapshots and properties\n    resinsight.set_export_folder(export_type='SNAPSHOTS', path=tmpdirname)\n    resinsight.set_export_folder(export_type='PROPERTIES', path=tmpdirname)\n    \n    # Export all snapshots\n    resinsight.project.export_snapshots()\n        \n    assert(len(os.listdir(tmpdirname)) \u0026gt; 0)\n    \n    # Export properties in the view\n    view1.export_property()\n\n    # Check that the exported file exists\n    expected_file_name = case.name + \u0026quot;-\u0026quot; + str(\u0026quot;3D_View\u0026quot;) + \u0026quot;-\u0026quot; + \u0026quot;T2\u0026quot; + \u0026quot;-SOIL\u0026quot;\n    full_path = tmpdirname + \u0026quot;/\u0026quot; + expected_file_name\n\n    # Print contents of temporary folder\n    print(os.listdir(tmpdirname))\n\n    assert(os.path.exists(full_path))\n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"create-wbs-plot\"\u003eCreate WBS Plot\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003eimport os\n# Load ResInsight Processing Server Client Library\nimport rips\n# Connect to ResInsight instance\nresInsight = rips.Instance.find()\n\ncases = resInsight.project.cases()\n\nwell_paths = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_LessWellPaths')\nwell_log_files = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\n\nif len(well_paths) \u0026lt; 1:\n    print(\u0026quot;No well paths in project\u0026quot;)\n    exit(1)\nprint(well_paths)\n\nfor case in cases:\n    if case.type == \u0026quot;GeoMechCase\u0026quot;:\n        print (case.case_id)\n        case_path = case.grid_path()\n        folder_name = os.path.dirname(case_path)\n        case.import_formation_names(formation_files=['D:/Projects/ResInsight-regression-test/ModelData/norne/Norne_ATW2013.lyr'])\n\n        # create a folder to hold the snapshots\n        dirname = os.path.join(folder_name, 'snapshots')\n        print(\u0026quot;Exporting to: \u0026quot; + dirname)\n\n        for well_path in well_paths:\n            wbsplot = case.create_well_bore_stability_plot(well_path=well_path, time_step=0)\n            wbsplot.export_snapshot(export_folder=dirname)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"errorhandling\"\u003eErrorHandling\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###################################################################\n# This example demonstrates the use of ResInsight exceptions \n# for proper error handling\n###################################################################\n\nimport rips\nimport grpc\nimport tempfile\n\nresinsight     = rips.Instance.find()\n\ncase = None\n\n# Try loading a non-existing case. We should get a grpc.RpcError exception from the server\ntry:\n    case = resinsight.project.load_case(\u0026quot;Nonsense\u0026quot;)\nexcept grpc.RpcError as e:\n    print(\u0026quot;Expected Server Exception Received while loading case: \u0026quot;, e)\n\n# Try loading well paths from a non-existing folder.  We should get a grpc.RpcError exception from the server\ntry:\n    well_path_files = resinsight.project.import_well_paths(well_path_folder=\u0026quot;NONSENSE/NONSENSE\u0026quot;)\nexcept grpc.RpcError as e:\n    print(\u0026quot;Expected Server Exception Received while loading wellpaths: \u0026quot;, e)\n\n# Try loading well paths from an existing but empty folder. We should get a warning.\ntry:\n    with tempfile.TemporaryDirectory() as tmpdirname:\n        well_path_files = resinsight.project.import_well_paths(well_path_folder=tmpdirname)\n        assert(len(well_path_files) == 0)\n        assert(resinsight.project.has_warnings())\n        print(\u0026quot;Should get warnings below\u0026quot;)\n        for warning in resinsight.project.warnings():\n            print (warning)\nexcept grpc.RpcError as e:\n    print(\u0026quot;Unexpected Server Exception caught!!!\u0026quot;, e)\n\ncase = resinsight.project.case(case_id=0)\nif case is not None:\n    results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\n    active_cell_count = len(results)\n\n    # Send the results back to ResInsight inside try / except construct\n    try:        \n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\n        print(\u0026quot;Everything went well as expected\u0026quot;)\n    except: # Match any exception, but it should not happen\n        print(\u0026quot;Ooops!\u0026quot;)\n\n    # Add another value, so this is outside the bounds of the active cell result storage\n    results.append(1.0)\n\n    # This time we should get a grpc.RpcError exception, which is a server side error.\n    try:        \n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\n        print(\u0026quot;Everything went well??\u0026quot;)\n    except grpc.RpcError as e:\n        print(\u0026quot;Expected Server Exception Received: \u0026quot;, e)\n    except IndexError:\n        print (\u0026quot;Got index out of bounds error. This shouldn't happen here\u0026quot;)\n\n    # With a chunk size exactly matching the active cell count the server will not\n    # be able to see any error as it will successfully close the stream after receiving\n    # the correct number of values, even if the python client has more chunks to send\n    case.chunk_size = active_cell_count\n\n    try:        \n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\n        print(\u0026quot;Everything went well??\u0026quot;)\n    except grpc.RpcError as e:\n        print(\u0026quot;Got unexpected server exception\u0026quot;, e, \u0026quot;This should not happen now\u0026quot;)\n    except IndexError:\n        print (\u0026quot;Got expected index out of bounds error on client side\u0026quot;)\n\n\n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"exportcontourmaps\"\u003eExportContourMaps\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\nimport rips\nimport tempfile\nimport pathlib\n\n# Connect to ResInsight instance\nresInsight = rips.Instance.find()\n\n# Data will be written to temp\ntmpdir = pathlib.Path(tempfile.gettempdir())\n\n# Find all eclipse contour maps of the project\ncontour_maps = resInsight.project.contour_maps(rips.ContourMapType.ECLIPSE)\nprint(\u0026quot;Number of eclipse contour maps:\u0026quot;, len(contour_maps))\n\n# Export the contour maps to a text file\nfor (index, contour_map) in enumerate(contour_maps):\n    filename = \u0026quot;eclipse_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\n    filepath = tmpdir / filename\n    print(\u0026quot;Exporting to:\u0026quot;, filepath)\n    contour_map.export_to_text(str(filepath))\n\n# The contour maps is also available for a Case\ncases = resInsight.project.cases()\nfor case in cases:\n    contour_maps = case.contour_maps(rips.ContourMapType.GEO_MECH)\n    # Export the contour maps to a text file\n    for (index, contour_map) in enumerate(contour_maps):\n        filename = \u0026quot;geomech_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\n        filepath = tmpdir / filename\n        print(\u0026quot;Exporting to:\u0026quot;, filepath)\n        contour_map.export_to_text(str(filepath))\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"exportplots\"\u003eExportPlots\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e# Import the tempfile module\nimport tempfile\n# Load ResInsight Processing Server Client Library\nimport rips\n# Connect to ResInsight instance\nresInsight = rips.Instance.find()\n\n# Get a list of all plots\nplots = resInsight.project.plots()\n\nexport_folder = tempfile.mkdtemp()\n\nprint(\u0026quot;Exporting to: \u0026quot; + export_folder)\n\nfor plot in plots:\n    plot.export_snapshot(export_folder=export_folder)\n    plot.export_data_as_las(export_folder=export_folder)\n    plot.export_data_as_ascii(export_folder=export_folder)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"exportsnapshots\"\u003eExportSnapshots\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e############################################################################\n# This script will export snapshots for two properties in every loaded case\n# And put them in a snapshots folder in the same folder as the case grid\n############################################################################\nimport os\nimport rips\n\n# Load instance\nresinsight = rips.Instance.find()\ncases = resinsight.project.cases()\n\n# Set main window size\nresinsight.set_main_window_size(width=800, height=500)\n\nn = 5                            # every n-th time_step for snapshot\nproperty_list = ['SOIL', 'PRESSURE'] # list of parameter for snapshot\n\nprint (\u0026quot;Looping through cases\u0026quot;)\nfor case in cases:\n    print(\u0026quot;Case name: \u0026quot;, case.name)\n    print(\u0026quot;Case id: \u0026quot;, case.case_id)\n    # Get grid path and its folder name\n    case_path = case.grid_path()\n    folder_name = os.path.dirname(case_path)\n    \n    # create a folder to hold the snapshots\n    dirname = os.path.join(folder_name, 'snapshots')\n        \n    if os.path.exists(dirname) is False:\n        os.mkdir(dirname)\n    \n    print (\u0026quot;Exporting to folder: \u0026quot; + dirname)\n    resinsight.set_export_folder(export_type='SNAPSHOTS', path=dirname)\n   \n    time_steps = case.time_steps()\n    print('Number of time_steps: ' + str(len(time_steps)))\n        \n    view = case.views()[0]\n    for property in property_list:\n        view.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable=property)\n        for time_step in range(0, len(time_steps), 10):\n            view.set_time_step(time_step = time_step)\n            view.export_snapshot()\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"gridinformation\"\u003eGridInformation\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e######################################################################################\n# This example prints information about the grids of all cases in the current project\n######################################################################################\n\nimport rips\n\nresinsight  = rips.Instance.find()\n\ncases = resinsight.project.cases()\nprint(\u0026quot;Number of cases found: \u0026quot;, len(cases))\nfor case in cases:\n    print(case.name)\n    grids = case.grids()\n    print(\u0026quot;Number of grids: \u0026quot;, len(grids))\n    for grid in grids:\n        print(\u0026quot;Grid dimensions: \u0026quot;, grid.dimensions())\n\n\n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"import-well-paths\"\u003eImport Well Paths\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\nimport rips\n# Connect to ResInsight instance\nresInsight = rips.Instance.find()\n\nwell_path_names = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/norne/wellpaths')\nif resInsight.project.has_warnings():\n    for warning in resInsight.project.warnings():\n        print(warning)\n\n\nfor well_path_name in well_path_names:\n    print(\u0026quot;Imported from folder: \u0026quot; + well_path_name)\n\nwell_path_names = resInsight.project.import_well_paths(well_path_files=['D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/E-3H.json',\n                                                                        'D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/C-1H.json'])\nif resInsight.project.has_warnings():\n    for warning in resInsight.project.warnings():\n        print(warning)\n\n\nfor well_path_name in well_path_names:\n    print(\u0026quot;Imported from indivdual files: \u0026quot; + well_path_name)\n\n\nwell_path_names = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\nif resInsight.project.has_warnings():\n    for warning in resInsight.project.warnings():\n        print(warning)\n\nfor well_path_name in well_path_names:\n    print(\u0026quot;Imported well log file for: \u0026quot; + well_path_name)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"inputproptestasync\"\u003eInputPropTestAsync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e########################################################################################\n# This example generates a derived property in an asynchronous manner\n# Meaning it does not wait for all the data for each stage to be read before proceeding\n########################################################################################\nimport rips\nimport time\n\n# Internal function for creating a result from a small chunk of poro and permx results\n# The return value of the function is a generator for the results rather than the result itself.\ndef create_result(poro_chunks, permx_chunks):\n    # Loop through all the chunks of poro and permx in order\n    for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\n        resultChunk = []\n        # Loop through all the values inside the chunks, in order\n        for (poro, permx) in zip(poroChunk.values, permxChunk.values):\n            resultChunk.append(poro * permx)\n        # Return a generator object that behaves like a Python iterator\n        yield resultChunk\n\nresinsight     = rips.Instance.find()\nstart = time.time()\ncase = resinsight.project.cases()[0]\n\n# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\nporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\n# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\npermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\n\n# Send back the result with the result provided by a generator object.\n# Iterating the result generator will cause the script to read from the poro and permx generators\n# And return the result of each iteration\ncase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\n                                           'GENERATED', 'POROPERMXAS', 0)\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(\u0026quot;Transferred all results back\u0026quot;)\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"inputproptestsync\"\u003eInputPropTestSync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e########################################################################################\n# This example generates a derived property in an synchronous manner\n# Meaning it completes reading each result before calculating the derived result\n# See InputPropTestAsync for how to do this asynchronously instead.\n########################################################################################\nimport rips\nimport time\nimport grpc\n\nresinsight     = rips.Instance.find()\nstart = time.time()\ncase = resinsight.project.cases()[0]\n\n# Read poro result into list\nporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\n# Read permx result into list\npermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\n\n# Generate output result\nresults = []\nfor (poro, permx) in zip(poro_results, permx_results):\n    results.append(poro * permx)\n\ntry:\n    # Send back output result\n    case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\nexcept grpc.RpcError as e:\n    print(\u0026quot;Exception Received: \u0026quot;, e)\n\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(\u0026quot;Transferred all results back\u0026quot;)\n\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"instanceexample\"\u003eInstanceExample\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e#######################################\n# This example connects to ResInsight\n#######################################\nimport rips\n\nresinsight  = rips.Instance.find()\n\nif resinsight is None:\n    print('ERROR: could not find ResInsight')\nelse:\n    print('Successfully connected to ResInsight')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"launchwithcommandlineoptions\"\u003eLaunchWithCommandLineOptions\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\nimport rips\n# Launch ResInsight with last project file and a Window size of 600x1000 pixels\nresinsight = rips.Instance.launch(command_line_parameters=['--last', '--size', 600, 1000])\n# Get a list of all cases\ncases = resinsight.project.cases()\n\nprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\nfor case in cases:\n    print(\u0026quot;Case name: \u0026quot; + case.name)\n    print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"selectedcases\"\u003eSelectedCases\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e############################################################################\n# This example returns the currently selected cases in ResInsight\n# Because running this script in the GUI takes away the selection\n# This script does not run successfully from within the ResInsight GUI\n# And will need to be run from the command line separately from ResInsight\n############################################################################\n\nimport rips\n\nresinsight  = rips.Instance.find()\nif resinsight is not None:\n    cases = resinsight.project.selected_cases()\n\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\n    for case in cases:\n        print(case.name)\n        for property in case.available_properties('DYNAMIC_NATIVE'):\n            print(property)\n\n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"setcellresult\"\u003eSetCellResult\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e######################################################################\n# This script applies a cell result to the first view in the project\n######################################################################\nimport rips\n\nresinsight  = rips.Instance.find()\n\nview = resinsight.project.views()[0]\nview.apply_cell_result(result_type='STATIC_NATIVE', result_variable='DX')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"setflowdiagnosticsresult\"\u003eSetFlowDiagnosticsResult\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e######################################################################\n# This script applies a flow diagnostics cell result to the first view in the project\n######################################################################\n\n# Load ResInsight Processing Server Client Library\nimport rips\n# Connect to ResInsight instance\nresinsight = rips.Instance.find()\n\nview = resinsight.project.view(view_id=1)\n#view.apply_flow_diagnostics_cell_result(result_variable='Fraction',\n#                                    selection_mode='FLOW_TR_INJ_AND_PROD')\n                                    \n# Example of setting individual wells. Commented out because well names are case specific.\nview.apply_flow_diagnostics_cell_result(result_variable='Fraction',\n                                    selection_mode='FLOW_TR_BY_SELECTION',\n                                    injectors = ['C-1H', 'C-2H', 'F-2H'],\n                                    producers = ['B-1AH', 'B-3H', 'D-1H'])\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"setgridproperties\"\u003eSetGridProperties\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e######################################################################\n# This script sets values for SOIL for all grid cells in the first case in the project\n######################################################################\nimport rips\n\nresinsight     = rips.Instance.find()\n\ncase = resinsight.project.case(case_id=0)\ntotal_cell_count = case.cell_count().reservoir_cell_count\n\nvalues = []\nfor i in range(0, total_cell_count):\n    values.append(i % 2 * 0.75);\n\nprint(\u0026quot;Applying values to full grid\u0026quot;)\ncase.set_grid_property(values, 'DYNAMIC_NATIVE', 'SOIL', 0)\n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"soilaverageasync\"\u003eSoilAverageAsync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###########################################################################################\n# This example will asynchronously calculate the average value for SOIL for all time steps\n###########################################################################################\n\nimport rips\nimport itertools\nimport time\n\nresinsight     = rips.Instance.find()\n\nstart          = time.time()\n\n# Get the case with case id 0\ncase           = resinsight.project.case(case_id=0)\n\n# Get a list of all time steps\ntimeSteps      = case.time_steps()\n\naverages = []\nfor i in range(0, len(timeSteps)):\n    # Get the results from time step i asynchronously\n    # It actually returns a generator object almost immediately\n    result_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\n    mysum = 0.0\n    count = 0\n    # Loop through and append the average. each time we loop resultChunks\n    # We will trigger a read of the input data, meaning the script will start\n    # Calculating averages before the whole resultValue for this time step has been received\n    for chunk in result_chunks:\n        mysum += sum(chunk.values)\n        count += len(chunk.values)\n\n    averages.append(mysum/count)\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(averages)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"soilaveragesync\"\u003eSoilAverageSync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e###########################################################################################\n# This example will synchronously calculate the average value for SOIL for all time steps\n###########################################################################################\nimport rips\nimport itertools\nimport time\n\nresinsight     = rips.Instance.find()\n\nstart          = time.time()\n\n# Get the case with case id 0\ncase           = resinsight.project.case(case_id=0)\n\n# Get a list of all time steps\ntime_steps      = case.time_steps()\n\naverages = []\nfor i in range(0, len(time_steps)):\n    # Get a list of all the results for time step i\n    results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\n    mysum = sum(results)\n    averages.append(mysum/len(results))\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(averages)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"soilporvasync\"\u003eSoilPorvAsync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e##############################################################################\n# This example will create a derived result for each time step asynchronously\n##############################################################################\n\nimport rips\nimport time\n\n# Internal function for creating a result from a small chunk of soil and porv results\n# The return value of the function is a generator for the results rather than the result itself.\ndef create_result(soil_chunks, porv_chunks):\n    for (soil_chunk, porv_chunk) in zip(soil_chunks, porv_chunks):\n        resultChunk = []\n        number = 0\n        for (soil_value, porv_value) in zip(soil_chunk.values, porv_chunk.values):\n            resultChunk.append(soil_value * porv_value)\n        # Return a Python generator\n        yield resultChunk\n\nresinsight   = rips.Instance.find()\nstart        = time.time()\ncase         = resinsight.project.cases()[0]\ntimeStepInfo = case.time_steps()\n\n# Get a generator for the porv results. The generator will provide a chunk each time it is iterated\nporv_chunks   = case.active_cell_property_async('STATIC_NATIVE', 'PORV', 0)\n\n# Read the static result into an array, so we don't have to transfer it for each iteration\n# Note we use the async method even if we synchronise here, because we need the values chunked\n# ... to match the soil chunks\nporv_array = []\nfor porv_chunk in porv_chunks:\n    porv_array.append(porv_chunk)\n\nfor i in range (0, len(timeStepInfo)):\n    # Get a generator object for the SOIL property for time step i\n    soil_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\n    # Create the generator object for the SOIL * PORV derived result\n    result_generator = create_result(soil_chunks, iter(porv_array))\n    # Send back the result asynchronously with a generator object\n    case.set_active_cell_property_async(result_generator, 'GENERATED', 'SOILPORVAsync', i)\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\n        \nprint(\u0026quot;Transferred all results back\u0026quot;)\n\nview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVAsync')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"soilporvsync\"\u003eSoilPorvSync\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e##############################################################################\n# This example will create a derived result for each time step synchronously\n##############################################################################\n\nimport rips\nimport time\n\nresinsight = rips.Instance.find()\nstart = time.time()\ncase       = resinsight.project.cases()[0]\n\n# Read the full porv result\nporv_results = case.active_cell_property('STATIC_NATIVE', 'PORV', 0)\ntime_step_info = case.time_steps()\n\nfor i in range (0, len(time_step_info)):\n    # Read the full SOIl result for time step i\n    soil_results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\n    \n    # Generate the result by looping through both lists in order\n    results = []\n    for (soil, porv) in zip(soil_results, porv_results):\n        results.append(soil * porv)\n\n    # Send back result\n    case.set_active_cell_property(results, 'GENERATED', 'SOILPORVSync', i)\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\n\nprint(\u0026quot;Transferred all results back\u0026quot;)\n\nview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVSync')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"viewexample\"\u003eViewExample\u003c/h1\u003e\n\n\u003cpre\u003e\u003ccode\u003e#############################################################\n# This example will alter the views of all cases\n# By setting the background color and toggle the grid box\n# Also clones the first view\n#############################################################\nimport rips\n# Connect to ResInsight instance\nresinsight = rips.Instance.find()\n\n# Check if connection worked\nif resinsight is not None:\n    # Get a list of all cases\n    cases = resinsight.project.cases()\n    for case in cases:\n        # Get a list of all views\n        views = case.views()\n        for view in views:\n            # Set some parameters for the view\n            view.set_show_grid_box(not view.show_grid_box())\n            view.set_background_color(\u0026quot;#3388AA\u0026quot;)            \n            # Update the view in ResInsight\n            view.update()\n        # Clone the first view\n        new_view = views[0].clone()\n        view.set_show_grid_box(False)\n        new_view.set_background_color(\u0026quot;#FFAA33\u0026quot;)\n        new_view.update()\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "This pages is created based on the content in the PythonExamples folder located inside the rips module, made available online for convenience.\nAllCases ###################################################################################\r# This example will connect to ResInsight, retrieve a list of cases and print info\r# ###################################################################################\r# Import the ResInsight Processing Server Module\rimport rips\r# Connect to ResInsight\rresinsight = rips.Instance.find()\rif resinsight is not None:\r# Get a list of all cases\rcases = resinsight.project.cases()\rprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\rfor case in cases:\rprint(\u0026quot;Case id: \u0026quot; + str(case.case_id))\rprint(\u0026quot;Case name: \u0026quot; + case.name)\rprint(\u0026quot;Case type: \u0026quot; + case.type)\rprint(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\rtimesteps = case.time_steps()\rfor t in timesteps:\rprint(\u0026quot;Year: \u0026quot; + str(t.year))\rprint(\u0026quot;Month: \u0026quot; + str(t.month))\rCaseGridGroup import os\rimport rips\rresinsight = rips.Instance.find()\rcase_paths = []\rcase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real0/BRUGGE_0000.EGRID\u0026quot;)\rcase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real10/BRUGGE_0010.EGRID\u0026quot;)\rfor case_path in case_paths:\rassert os.path.exists(case_path), \u0026quot;You need to set valid case paths for this script to work\u0026quot;\rcase_group = resinsight.project.create_grid_case_group(case_paths=case_paths)\rcase_group.print_object_info()\r#stat_cases = caseGroup.statistics_cases()\r#case_ids = []\r#for stat_case in stat_cases:\r# stat_case.set_value(\u0026quot;DynamicPropertiesToCalculate\u0026quot;, [\u0026quot;SWAT\u0026quot;])\r# stat_case.update()\r# case_ids.append(stat_case.get_value(\u0026quot;CaseId\u0026quot;))\rcase_group.compute_statistics()\rview = case_group.views()[0]\rcell_result = view.set_cell_result()\rcell_result.set_value(\u0026quot;ResultVariable\u0026quot;, \u0026quot;PRESSURE_DEV\u0026quot;)\rcell_result.update()\rCaseInfoStreamingExample ###############################################################################\r# This example will get the cell info for the active cells for the first case\r###############################################################################\r# Import the ResInsight Processing Server Module\rimport rips\r# Connect to ResInsight\rresinsight = rips.Instance.find()\r# Get the first case. This will fail if you haven't loaded any cases\rcase = resinsight.project.cases()[0]\r# Get the cell count object\rcell_counts = case.cell_count()\rprint(\u0026quot;Number of active cells: \u0026quot; + str(cell_counts.active_cell_count))\rprint(\u0026quot;Total number of reservoir cells: \u0026quot; + str(cell_counts.reservoir_cell_count))\r# Get information for all active cells\ractive_cell_infos = case.cell_info_for_active_cells()\r# A simple check on the size of the cell info\rassert(cell_counts.active_cell_count == len(active_cell_infos))\r# Print information for the first active cell\rprint(\u0026quot;First active cell: \u0026quot;)\rprint(active_cell_infos[0])\rCommandExample ###############################################################################\r# This example will show setting time step, window size and export snapshots and properties\r###############################################################################\rimport os\rimport tempfile\rimport rips\r# Load instance\rresinsight = rips.Instance.find()\r# Set window sizes\rresinsight.set_main_window_size(width=800, height=500)\rresinsight.set_plot_window_size(width=1000, height=1000)\r# Retrieve first case\rcase = resinsight.project.cases()[0]\r# Get a view\rview1 = case.views()[0]\r# Clone the view\rview2 = view1.clone()\r# Set the time step for view1 only\rview1.set_time_step(time_step=2)\r# Set cell result to SOIL\rview1.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable='SOIL')\r# Create a temporary directory which will disappear at the end of this script\r# If you want to keep the files, provide a good path name instead of tmpdirname\rwith tempfile.TemporaryDirectory(prefix=\u0026quot;rips\u0026quot;) as tmpdirname:\rprint(\u0026quot;Temporary folder: \u0026quot;, tmpdirname)\r# Set export folder for snapshots and properties\rresinsight.set_export_folder(export_type='SNAPSHOTS', path=tmpdirname)\rresinsight.set_export_folder(export_type='PROPERTIES', path=tmpdirname)\r# Export all snapshots\rresinsight.project.export_snapshots()\rassert(len(os.listdir(tmpdirname)) \u0026gt; 0)\r# Export properties in the view\rview1.export_property()\r# Check that the exported file exists\rexpected_file_name = case.name + \u0026quot;-\u0026quot; + str(\u0026quot;3D_View\u0026quot;) + \u0026quot;-\u0026quot; + \u0026quot;T2\u0026quot; + \u0026quot;-SOIL\u0026quot;\rfull_path = tmpdirname + \u0026quot;/\u0026quot; + expected_file_name\r# Print contents of temporary folder\rprint(os.listdir(tmpdirname))\rassert(os.path.exists(full_path))\rCreate WBS Plot import os\r# Load ResInsight Processing Server Client Library\rimport rips\r# Connect to ResInsight instance\rresInsight = rips.Instance.find()\rcases = resInsight.project.cases()\rwell_paths = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_LessWellPaths')\rwell_log_files = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\rif len(well_paths) \u0026lt; 1:\rprint(\u0026quot;No well paths in project\u0026quot;)\rexit(1)\rprint(well_paths)\rfor case in cases:\rif case.type == \u0026quot;GeoMechCase\u0026quot;:\rprint (case.case_id)\rcase_path = case.grid_path()\rfolder_name = os.path.dirname(case_path)\rcase.import_formation_names(formation_files=['D:/Projects/ResInsight-regression-test/ModelData/norne/Norne_ATW2013.lyr'])\r# create a folder to hold the snapshots\rdirname = os.path.join(folder_name, 'snapshots')\rprint(\u0026quot;Exporting to: \u0026quot; + dirname)\rfor well_path in well_paths:\rwbsplot = case.create_well_bore_stability_plot(well_path=well_path, time_step=0)\rwbsplot.export_snapshot(export_folder=dirname)\rErrorHandling ###################################################################\r# This example demonstrates the use of ResInsight exceptions # for proper error handling\r###################################################################\rimport rips\rimport grpc\rimport tempfile\rresinsight = rips.Instance.find()\rcase = None\r# Try loading a non-existing case. We should get a grpc.RpcError exception from the server\rtry:\rcase = resinsight.project.load_case(\u0026quot;Nonsense\u0026quot;)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Expected Server Exception Received while loading case: \u0026quot;, e)\r# Try loading well paths from a non-existing folder. We should get a grpc.RpcError exception from the server\rtry:\rwell_path_files = resinsight.project.import_well_paths(well_path_folder=\u0026quot;NONSENSE/NONSENSE\u0026quot;)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Expected Server Exception Received while loading wellpaths: \u0026quot;, e)\r# Try loading well paths from an existing but empty folder. We should get a warning.\rtry:\rwith tempfile.TemporaryDirectory() as tmpdirname:\rwell_path_files = resinsight.project.import_well_paths(well_path_folder=tmpdirname)\rassert(len(well_path_files) == 0)\rassert(resinsight.project.has_warnings())\rprint(\u0026quot;Should get warnings below\u0026quot;)\rfor warning in resinsight.project.warnings():\rprint (warning)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Unexpected Server Exception caught!!!\u0026quot;, e)\rcase = resinsight.project.case(case_id=0)\rif case is not None:\rresults = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\ractive_cell_count = len(results)\r# Send the results back to ResInsight inside try / except construct\rtry: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\rprint(\u0026quot;Everything went well as expected\u0026quot;)\rexcept: # Match any exception, but it should not happen\rprint(\u0026quot;Ooops!\u0026quot;)\r# Add another value, so this is outside the bounds of the active cell result storage\rresults.append(1.0)\r# This time we should get a grpc.RpcError exception, which is a server side error.\rtry: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\rprint(\u0026quot;Everything went well??\u0026quot;)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Expected Server Exception Received: \u0026quot;, e)\rexcept IndexError:\rprint (\u0026quot;Got index out of bounds error. This shouldn't happen here\u0026quot;)\r# With a chunk size exactly matching the active cell count the server will not\r# be able to see any error as it will successfully close the stream after receiving\r# the correct number of values, even if the python client has more chunks to send\rcase.chunk_size = active_cell_count\rtry: case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\rprint(\u0026quot;Everything went well??\u0026quot;)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Got unexpected server exception\u0026quot;, e, \u0026quot;This should not happen now\u0026quot;)\rexcept IndexError:\rprint (\u0026quot;Got expected index out of bounds error on client side\u0026quot;)\rExportContourMaps # Load ResInsight Processing Server Client Library\rimport rips\rimport tempfile\rimport pathlib\r# Connect to ResInsight instance\rresInsight = rips.Instance.find()\r# Data will be written to temp\rtmpdir = pathlib.Path(tempfile.gettempdir())\r# Find all eclipse contour maps of the project\rcontour_maps = resInsight.project.contour_maps(rips.ContourMapType.ECLIPSE)\rprint(\u0026quot;Number of eclipse contour maps:\u0026quot;, len(contour_maps))\r# Export the contour maps to a text file\rfor (index, contour_map) in enumerate(contour_maps):\rfilename = \u0026quot;eclipse_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\rfilepath = tmpdir / filename\rprint(\u0026quot;Exporting to:\u0026quot;, filepath)\rcontour_map.export_to_text(str(filepath))\r# The contour maps is also available for a Case\rcases = resInsight.project.cases()\rfor case in cases:\rcontour_maps = case.contour_maps(rips.ContourMapType.GEO_MECH)\r# Export the contour maps to a text file\rfor (index, contour_map) in enumerate(contour_maps):\rfilename = \u0026quot;geomech_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\rfilepath = tmpdir / filename\rprint(\u0026quot;Exporting to:\u0026quot;, filepath)\rcontour_map.export_to_text(str(filepath))\rExportPlots # Import the tempfile module\rimport tempfile\r# Load ResInsight Processing Server Client Library\rimport rips\r# Connect to ResInsight instance\rresInsight = rips.Instance.find()\r# Get a list of all plots\rplots = resInsight.project.plots()\rexport_folder = tempfile.mkdtemp()\rprint(\u0026quot;Exporting to: \u0026quot; + export_folder)\rfor plot in plots:\rplot.export_snapshot(export_folder=export_folder)\rplot.export_data_as_las(export_folder=export_folder)\rplot.export_data_as_ascii(export_folder=export_folder)\rExportSnapshots ############################################################################\r# This script will export snapshots for two properties in every loaded case\r# And put them in a snapshots folder in the same folder as the case grid\r############################################################################\rimport os\rimport rips\r# Load instance\rresinsight = rips.Instance.find()\rcases = resinsight.project.cases()\r# Set main window size\rresinsight.set_main_window_size(width=800, height=500)\rn = 5 # every n-th time_step for snapshot\rproperty_list = ['SOIL', 'PRESSURE'] # list of parameter for snapshot\rprint (\u0026quot;Looping through cases\u0026quot;)\rfor case in cases:\rprint(\u0026quot;Case name: \u0026quot;, case.name)\rprint(\u0026quot;Case id: \u0026quot;, case.case_id)\r# Get grid path and its folder name\rcase_path = case.grid_path()\rfolder_name = os.path.dirname(case_path)\r# create a folder to hold the snapshots\rdirname = os.path.join(folder_name, 'snapshots')\rif os.path.exists(dirname) is False:\ros.mkdir(dirname)\rprint (\u0026quot;Exporting to folder: \u0026quot; + dirname)\rresinsight.set_export_folder(export_type='SNAPSHOTS', path=dirname)\rtime_steps = case.time_steps()\rprint('Number of time_steps: ' + str(len(time_steps)))\rview = case.views()[0]\rfor property in property_list:\rview.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable=property)\rfor time_step in range(0, len(time_steps), 10):\rview.set_time_step(time_step = time_step)\rview.export_snapshot()\rGridInformation ######################################################################################\r# This example prints information about the grids of all cases in the current project\r######################################################################################\rimport rips\rresinsight = rips.Instance.find()\rcases = resinsight.project.cases()\rprint(\u0026quot;Number of cases found: \u0026quot;, len(cases))\rfor case in cases:\rprint(case.name)\rgrids = case.grids()\rprint(\u0026quot;Number of grids: \u0026quot;, len(grids))\rfor grid in grids:\rprint(\u0026quot;Grid dimensions: \u0026quot;, grid.dimensions())\rImport Well Paths # Load ResInsight Processing Server Client Library\rimport rips\r# Connect to ResInsight instance\rresInsight = rips.Instance.find()\rwell_path_names = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/norne/wellpaths')\rif resInsight.project.has_warnings():\rfor warning in resInsight.project.warnings():\rprint(warning)\rfor well_path_name in well_path_names:\rprint(\u0026quot;Imported from folder: \u0026quot; + well_path_name)\rwell_path_names = resInsight.project.import_well_paths(well_path_files=['D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/E-3H.json',\r'D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/C-1H.json'])\rif resInsight.project.has_warnings():\rfor warning in resInsight.project.warnings():\rprint(warning)\rfor well_path_name in well_path_names:\rprint(\u0026quot;Imported from indivdual files: \u0026quot; + well_path_name)\rwell_path_names = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\rif resInsight.project.has_warnings():\rfor warning in resInsight.project.warnings():\rprint(warning)\rfor well_path_name in well_path_names:\rprint(\u0026quot;Imported well log file for: \u0026quot; + well_path_name)\rInputPropTestAsync ########################################################################################\r# This example generates a derived property in an asynchronous manner\r# Meaning it does not wait for all the data for each stage to be read before proceeding\r########################################################################################\rimport rips\rimport time\r# Internal function for creating a result from a small chunk of poro and permx results\r# The return value of the function is a generator for the results rather than the result itself.\rdef create_result(poro_chunks, permx_chunks):\r# Loop through all the chunks of poro and permx in order\rfor (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\rresultChunk = []\r# Loop through all the values inside the chunks, in order\rfor (poro, permx) in zip(poroChunk.values, permxChunk.values):\rresultChunk.append(poro * permx)\r# Return a generator object that behaves like a Python iterator\ryield resultChunk\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\r# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\rporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\r# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\rpermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\r# Send back the result with the result provided by a generator object.\r# Iterating the result generator will cause the script to read from the poro and permx generators\r# And return the result of each iteration\rcase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\r'GENERATED', 'POROPERMXAS', 0)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\rInputPropTestSync ########################################################################################\r# This example generates a derived property in an synchronous manner\r# Meaning it completes reading each result before calculating the derived result\r# See InputPropTestAsync for how to do this asynchronously instead.\r########################################################################################\rimport rips\rimport time\rimport grpc\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\r# Read poro result into list\rporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\r# Read permx result into list\rpermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\r# Generate output result\rresults = []\rfor (poro, permx) in zip(poro_results, permx_results):\rresults.append(poro * permx)\rtry:\r# Send back output result\rcase.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Exception Received: \u0026quot;, e)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\rInstanceExample #######################################\r# This example connects to ResInsight\r#######################################\rimport rips\rresinsight = rips.Instance.find()\rif resinsight is None:\rprint('ERROR: could not find ResInsight')\relse:\rprint('Successfully connected to ResInsight')\rLaunchWithCommandLineOptions # Load ResInsight Processing Server Client Library\rimport rips\r# Launch ResInsight with last project file and a Window size of 600x1000 pixels\rresinsight = rips.Instance.launch(command_line_parameters=['--last', '--size', 600, 1000])\r# Get a list of all cases\rcases = resinsight.project.cases()\rprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\rfor case in cases:\rprint(\u0026quot;Case name: \u0026quot; + case.name)\rprint(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\rSelectedCases ############################################################################\r# This example returns the currently selected cases in ResInsight\r# Because running this script in the GUI takes away the selection\r# This script does not run successfully from within the ResInsight GUI\r# And will need to be run from the command line separately from ResInsight\r############################################################################\rimport rips\rresinsight = rips.Instance.find()\rif resinsight is not None:\rcases = resinsight.project.selected_cases()\rprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\rfor case in cases:\rprint(case.name)\rfor property in case.available_properties('DYNAMIC_NATIVE'):\rprint(property)\rSetCellResult ######################################################################\r# This script applies a cell result to the first view in the project\r######################################################################\rimport rips\rresinsight = rips.Instance.find()\rview = resinsight.project.views()[0]\rview.apply_cell_result(result_type='STATIC_NATIVE', result_variable='DX')\rSetFlowDiagnosticsResult ######################################################################\r# This script applies a flow diagnostics cell result to the first view in the project\r######################################################################\r# Load ResInsight Processing Server Client Library\rimport rips\r# Connect to ResInsight instance\rresinsight = rips.Instance.find()\rview = resinsight.project.view(view_id=1)\r#view.apply_flow_diagnostics_cell_result(result_variable='Fraction',\r# selection_mode='FLOW_TR_INJ_AND_PROD')\r# Example of setting individual wells. Commented out because well names are case specific.\rview.apply_flow_diagnostics_cell_result(result_variable='Fraction',\rselection_mode='FLOW_TR_BY_SELECTION',\rinjectors = ['C-1H', 'C-2H', 'F-2H'],\rproducers = ['B-1AH', 'B-3H', 'D-1H'])\rSetGridProperties ######################################################################\r# This script sets values for SOIL for all grid cells in the first case in the project\r######################################################################\rimport rips\rresinsight = rips.Instance.find()\rcase = resinsight.project.case(case_id=0)\rtotal_cell_count = case.cell_count().reservoir_cell_count\rvalues = []\rfor i in range(0, total_cell_count):\rvalues.append(i % 2 * 0.75);\rprint(\u0026quot;Applying values to full grid\u0026quot;)\rcase.set_grid_property(values, 'DYNAMIC_NATIVE', 'SOIL', 0)\rSoilAverageAsync ###########################################################################################\r# This example will asynchronously calculate the average value for SOIL for all time steps\r###########################################################################################\rimport rips\rimport itertools\rimport time\rresinsight = rips.Instance.find()\rstart = time.time()\r# Get the case with case id 0\rcase = resinsight.project.case(case_id=0)\r# Get a list of all time steps\rtimeSteps = case.time_steps()\raverages = []\rfor i in range(0, len(timeSteps)):\r# Get the results from time step i asynchronously\r# It actually returns a generator object almost immediately\rresult_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\rmysum = 0.0\rcount = 0\r# Loop through and append the average. each time we loop resultChunks\r# We will trigger a read of the input data, meaning the script will start\r# Calculating averages before the whole resultValue for this time step has been received\rfor chunk in result_chunks:\rmysum += sum(chunk.values)\rcount += len(chunk.values)\raverages.append(mysum/count)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(averages)\rSoilAverageSync ###########################################################################################\r# This example will synchronously calculate the average value for SOIL for all time steps\r###########################################################################################\rimport rips\rimport itertools\rimport time\rresinsight = rips.Instance.find()\rstart = time.time()\r# Get the case with case id 0\rcase = resinsight.project.case(case_id=0)\r# Get a list of all time steps\rtime_steps = case.time_steps()\raverages = []\rfor i in range(0, len(time_steps)):\r# Get a list of all the results for time step i\rresults = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\rmysum = sum(results)\raverages.append(mysum/len(results))\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(averages)\rSoilPorvAsync ##############################################################################\r# This example will create a derived result for each time step asynchronously\r##############################################################################\rimport rips\rimport time\r# Internal function for creating a result from a small chunk of soil and porv results\r# The return value of the function is a generator for the results rather than the result itself.\rdef create_result(soil_chunks, porv_chunks):\rfor (soil_chunk, porv_chunk) in zip(soil_chunks, porv_chunks):\rresultChunk = []\rnumber = 0\rfor (soil_value, porv_value) in zip(soil_chunk.values, porv_chunk.values):\rresultChunk.append(soil_value * porv_value)\r# Return a Python generator\ryield resultChunk\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\rtimeStepInfo = case.time_steps()\r# Get a generator for the porv results. The generator will provide a chunk each time it is iterated\rporv_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORV', 0)\r# Read the static result into an array, so we don't have to transfer it for each iteration\r# Note we use the async method even if we synchronise here, because we need the values chunked\r# ... to match the soil chunks\rporv_array = []\rfor porv_chunk in porv_chunks:\rporv_array.append(porv_chunk)\rfor i in range (0, len(timeStepInfo)):\r# Get a generator object for the SOIL property for time step i\rsoil_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\r# Create the generator object for the SOIL * PORV derived result\rresult_generator = create_result(soil_chunks, iter(porv_array))\r# Send back the result asynchronously with a generator object\rcase.set_active_cell_property_async(result_generator, 'GENERATED', 'SOILPORVAsync', i)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVAsync')\rSoilPorvSync ##############################################################################\r# This example will create a derived result for each time step synchronously\r##############################################################################\rimport rips\rimport time\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\r# Read the full porv result\rporv_results = case.active_cell_property('STATIC_NATIVE', 'PORV', 0)\rtime_step_info = case.time_steps()\rfor i in range (0, len(time_step_info)):\r# Read the full SOIl result for time step i\rsoil_results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\r# Generate the result by looping through both lists in order\rresults = []\rfor (soil, porv) in zip(soil_results, porv_results):\rresults.append(soil * porv)\r# Send back result\rcase.set_active_cell_property(results, 'GENERATED', 'SOILPORVSync', i)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVSync')\rViewExample #############################################################\r# This example will alter the views of all cases\r# By setting the background color and toggle the grid box\r# Also clones the first view\r#############################################################\rimport rips\r# Connect to ResInsight instance\rresinsight = rips.Instance.find()\r# Check if connection worked\rif resinsight is not None:\r# Get a list of all cases\rcases = resinsight.project.cases()\rfor case in cases:\r# Get a list of all views\rviews = case.views()\rfor view in views:\r# Set some parameters for the view\rview.set_show_grid_box(not view.show_grid_box())\rview.set_background_color(\u0026quot;#3388AA\u0026quot;) # Update the view in ResInsight\rview.update()\r# Clone the first view\rnew_view = views[0].clone()\rview.set_show_grid_box(False)\rnew_view.set_background_color(\u0026quot;#FFAA33\u0026quot;)\rnew_view.update()\r",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis pages is created based on the content in the \u003cstrong\u003ePythonExamples\u003c/strong\u003e folder located inside the \u003cstrong\u003erips\u003c/strong\u003e module, made available online for convenience.\u003c/p\u003e\n\u003ch1 id=\"allcases\"\u003eAllCases\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###################################################################################\r\n# This example will connect to ResInsight, retrieve a list of cases and print info\r\n# \r\n###################################################################################\r\n\r\n# Import the ResInsight Processing Server Module\r\nimport rips\r\n\r\n# Connect to ResInsight\r\nresinsight  = rips.Instance.find()\r\nif resinsight is not None:\r\n    # Get a list of all cases\r\n    cases = resinsight.project.cases()\r\n\r\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\r\n    for case in cases:\r\n        print(\u0026quot;Case id: \u0026quot; + str(case.case_id))\r\n        print(\u0026quot;Case name: \u0026quot; + case.name)\r\n        print(\u0026quot;Case type: \u0026quot; + case.type)\r\n        print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\r\n        \r\n        timesteps = case.time_steps()\r\n        for t in timesteps:\r\n            print(\u0026quot;Year: \u0026quot; + str(t.year))\r\n            print(\u0026quot;Month: \u0026quot; + str(t.month))\r\n        \r\n    \r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"casegridgroup\"\u003eCaseGridGroup\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003eimport os\r\nimport rips\r\n\r\nresinsight  = rips.Instance.find()\r\n\r\ncase_paths = []\r\ncase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real0/BRUGGE_0000.EGRID\u0026quot;)\r\ncase_paths.append(\u0026quot;C:/Users/lindk/source/repos/ResInsight/TestModels/Case_with_10_timesteps/Real10/BRUGGE_0010.EGRID\u0026quot;)\r\nfor case_path in case_paths:\r\n    assert os.path.exists(case_path), \u0026quot;You need to set valid case paths for this script to work\u0026quot;\r\n\r\ncase_group = resinsight.project.create_grid_case_group(case_paths=case_paths)\r\n\r\ncase_group.print_object_info()\r\n    \r\n#stat_cases = caseGroup.statistics_cases()\r\n#case_ids = []\r\n#for stat_case in stat_cases:\r\n#    stat_case.set_value(\u0026quot;DynamicPropertiesToCalculate\u0026quot;, [\u0026quot;SWAT\u0026quot;])\r\n#    stat_case.update()\r\n#    case_ids.append(stat_case.get_value(\u0026quot;CaseId\u0026quot;))\r\n\r\ncase_group.compute_statistics()\r\n\r\nview = case_group.views()[0]\r\ncell_result = view.set_cell_result()\r\ncell_result.set_value(\u0026quot;ResultVariable\u0026quot;, \u0026quot;PRESSURE_DEV\u0026quot;)\r\ncell_result.update()\r\n        \r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"caseinfostreamingexample\"\u003eCaseInfoStreamingExample\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###############################################################################\r\n# This example will get the cell info for the active cells for the first case\r\n###############################################################################\r\n\r\n# Import the ResInsight Processing Server Module\r\nimport rips\r\n\r\n# Connect to ResInsight\r\nresinsight  = rips.Instance.find()\r\n\r\n# Get the first case. This will fail if you haven't loaded any cases\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Get the cell count object\r\ncell_counts = case.cell_count()\r\nprint(\u0026quot;Number of active cells: \u0026quot; + str(cell_counts.active_cell_count))\r\nprint(\u0026quot;Total number of reservoir cells: \u0026quot; + str(cell_counts.reservoir_cell_count))\r\n\r\n# Get information for all active cells\r\nactive_cell_infos = case.cell_info_for_active_cells()\r\n\r\n# A simple check on the size of the cell info\r\nassert(cell_counts.active_cell_count == len(active_cell_infos))\r\n\r\n# Print information for the first active cell\r\nprint(\u0026quot;First active cell: \u0026quot;)\r\nprint(active_cell_infos[0])\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"commandexample\"\u003eCommandExample\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###############################################################################\r\n# This example will show setting time step, window size and export snapshots and properties\r\n###############################################################################\r\nimport os\r\nimport tempfile\r\nimport rips\r\n\r\n# Load instance\r\nresinsight = rips.Instance.find()\r\n\r\n# Set window sizes\r\nresinsight.set_main_window_size(width=800, height=500)\r\nresinsight.set_plot_window_size(width=1000, height=1000)\r\n\r\n\r\n# Retrieve first case\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Get a view\r\nview1 = case.views()[0]\r\n\r\n# Clone the view\r\nview2 = view1.clone()\r\n\r\n# Set the time step for view1 only\r\nview1.set_time_step(time_step=2)\r\n\r\n# Set cell result to SOIL\r\nview1.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable='SOIL')\r\n\r\n\r\n# Create a temporary directory which will disappear at the end of this script\r\n# If you want to keep the files, provide a good path name instead of tmpdirname\r\nwith tempfile.TemporaryDirectory(prefix=\u0026quot;rips\u0026quot;) as tmpdirname:\r\n    print(\u0026quot;Temporary folder: \u0026quot;, tmpdirname)\r\n    \r\n    # Set export folder for snapshots and properties\r\n    resinsight.set_export_folder(export_type='SNAPSHOTS', path=tmpdirname)\r\n    resinsight.set_export_folder(export_type='PROPERTIES', path=tmpdirname)\r\n    \r\n    # Export all snapshots\r\n    resinsight.project.export_snapshots()\r\n        \r\n    assert(len(os.listdir(tmpdirname)) \u0026gt; 0)\r\n    \r\n    # Export properties in the view\r\n    view1.export_property()\r\n\r\n    # Check that the exported file exists\r\n    expected_file_name = case.name + \u0026quot;-\u0026quot; + str(\u0026quot;3D_View\u0026quot;) + \u0026quot;-\u0026quot; + \u0026quot;T2\u0026quot; + \u0026quot;-SOIL\u0026quot;\r\n    full_path = tmpdirname + \u0026quot;/\u0026quot; + expected_file_name\r\n\r\n    # Print contents of temporary folder\r\n    print(os.listdir(tmpdirname))\r\n\r\n    assert(os.path.exists(full_path))\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"create-wbs-plot\"\u003eCreate WBS Plot\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003eimport os\r\n# Load ResInsight Processing Server Client Library\r\nimport rips\r\n# Connect to ResInsight instance\r\nresInsight = rips.Instance.find()\r\n\r\ncases = resInsight.project.cases()\r\n\r\nwell_paths = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_LessWellPaths')\r\nwell_log_files = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\r\n\r\nif len(well_paths) \u0026lt; 1:\r\n    print(\u0026quot;No well paths in project\u0026quot;)\r\n    exit(1)\r\nprint(well_paths)\r\n\r\nfor case in cases:\r\n    if case.type == \u0026quot;GeoMechCase\u0026quot;:\r\n        print (case.case_id)\r\n        case_path = case.grid_path()\r\n        folder_name = os.path.dirname(case_path)\r\n        case.import_formation_names(formation_files=['D:/Projects/ResInsight-regression-test/ModelData/norne/Norne_ATW2013.lyr'])\r\n\r\n        # create a folder to hold the snapshots\r\n        dirname = os.path.join(folder_name, 'snapshots')\r\n        print(\u0026quot;Exporting to: \u0026quot; + dirname)\r\n\r\n        for well_path in well_paths:\r\n            wbsplot = case.create_well_bore_stability_plot(well_path=well_path, time_step=0)\r\n            wbsplot.export_snapshot(export_folder=dirname)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"errorhandling\"\u003eErrorHandling\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###################################################################\r\n# This example demonstrates the use of ResInsight exceptions \r\n# for proper error handling\r\n###################################################################\r\n\r\nimport rips\r\nimport grpc\r\nimport tempfile\r\n\r\nresinsight     = rips.Instance.find()\r\n\r\ncase = None\r\n\r\n# Try loading a non-existing case. We should get a grpc.RpcError exception from the server\r\ntry:\r\n    case = resinsight.project.load_case(\u0026quot;Nonsense\u0026quot;)\r\nexcept grpc.RpcError as e:\r\n    print(\u0026quot;Expected Server Exception Received while loading case: \u0026quot;, e)\r\n\r\n# Try loading well paths from a non-existing folder.  We should get a grpc.RpcError exception from the server\r\ntry:\r\n    well_path_files = resinsight.project.import_well_paths(well_path_folder=\u0026quot;NONSENSE/NONSENSE\u0026quot;)\r\nexcept grpc.RpcError as e:\r\n    print(\u0026quot;Expected Server Exception Received while loading wellpaths: \u0026quot;, e)\r\n\r\n# Try loading well paths from an existing but empty folder. We should get a warning.\r\ntry:\r\n    with tempfile.TemporaryDirectory() as tmpdirname:\r\n        well_path_files = resinsight.project.import_well_paths(well_path_folder=tmpdirname)\r\n        assert(len(well_path_files) == 0)\r\n        assert(resinsight.project.has_warnings())\r\n        print(\u0026quot;Should get warnings below\u0026quot;)\r\n        for warning in resinsight.project.warnings():\r\n            print (warning)\r\nexcept grpc.RpcError as e:\r\n    print(\u0026quot;Unexpected Server Exception caught!!!\u0026quot;, e)\r\n\r\ncase = resinsight.project.case(case_id=0)\r\nif case is not None:\r\n    results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\r\n    active_cell_count = len(results)\r\n\r\n    # Send the results back to ResInsight inside try / except construct\r\n    try:        \r\n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\r\n        print(\u0026quot;Everything went well as expected\u0026quot;)\r\n    except: # Match any exception, but it should not happen\r\n        print(\u0026quot;Ooops!\u0026quot;)\r\n\r\n    # Add another value, so this is outside the bounds of the active cell result storage\r\n    results.append(1.0)\r\n\r\n    # This time we should get a grpc.RpcError exception, which is a server side error.\r\n    try:        \r\n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\r\n        print(\u0026quot;Everything went well??\u0026quot;)\r\n    except grpc.RpcError as e:\r\n        print(\u0026quot;Expected Server Exception Received: \u0026quot;, e)\r\n    except IndexError:\r\n        print (\u0026quot;Got index out of bounds error. This shouldn't happen here\u0026quot;)\r\n\r\n    # With a chunk size exactly matching the active cell count the server will not\r\n    # be able to see any error as it will successfully close the stream after receiving\r\n    # the correct number of values, even if the python client has more chunks to send\r\n    case.chunk_size = active_cell_count\r\n\r\n    try:        \r\n        case.set_active_cell_property(results, 'GENERATED', 'POROAPPENDED', 0)\r\n        print(\u0026quot;Everything went well??\u0026quot;)\r\n    except grpc.RpcError as e:\r\n        print(\u0026quot;Got unexpected server exception\u0026quot;, e, \u0026quot;This should not happen now\u0026quot;)\r\n    except IndexError:\r\n        print (\u0026quot;Got expected index out of bounds error on client side\u0026quot;)\r\n\r\n\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"exportcontourmaps\"\u003eExportContourMaps\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\r\nimport rips\r\nimport tempfile\r\nimport pathlib\r\n\r\n# Connect to ResInsight instance\r\nresInsight = rips.Instance.find()\r\n\r\n# Data will be written to temp\r\ntmpdir = pathlib.Path(tempfile.gettempdir())\r\n\r\n# Find all eclipse contour maps of the project\r\ncontour_maps = resInsight.project.contour_maps(rips.ContourMapType.ECLIPSE)\r\nprint(\u0026quot;Number of eclipse contour maps:\u0026quot;, len(contour_maps))\r\n\r\n# Export the contour maps to a text file\r\nfor (index, contour_map) in enumerate(contour_maps):\r\n    filename = \u0026quot;eclipse_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\r\n    filepath = tmpdir / filename\r\n    print(\u0026quot;Exporting to:\u0026quot;, filepath)\r\n    contour_map.export_to_text(str(filepath))\r\n\r\n# The contour maps is also available for a Case\r\ncases = resInsight.project.cases()\r\nfor case in cases:\r\n    contour_maps = case.contour_maps(rips.ContourMapType.GEO_MECH)\r\n    # Export the contour maps to a text file\r\n    for (index, contour_map) in enumerate(contour_maps):\r\n        filename = \u0026quot;geomech_contour_map\u0026quot; + str(index) + \u0026quot;.txt\u0026quot;\r\n        filepath = tmpdir / filename\r\n        print(\u0026quot;Exporting to:\u0026quot;, filepath)\r\n        contour_map.export_to_text(str(filepath))\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"exportplots\"\u003eExportPlots\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e# Import the tempfile module\r\nimport tempfile\r\n# Load ResInsight Processing Server Client Library\r\nimport rips\r\n# Connect to ResInsight instance\r\nresInsight = rips.Instance.find()\r\n\r\n# Get a list of all plots\r\nplots = resInsight.project.plots()\r\n\r\nexport_folder = tempfile.mkdtemp()\r\n\r\nprint(\u0026quot;Exporting to: \u0026quot; + export_folder)\r\n\r\nfor plot in plots:\r\n\tplot.export_snapshot(export_folder=export_folder)\r\n\tplot.export_data_as_las(export_folder=export_folder)\r\n\tplot.export_data_as_ascii(export_folder=export_folder)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"exportsnapshots\"\u003eExportSnapshots\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e############################################################################\r\n# This script will export snapshots for two properties in every loaded case\r\n# And put them in a snapshots folder in the same folder as the case grid\r\n############################################################################\r\nimport os\r\nimport rips\r\n\r\n# Load instance\r\nresinsight = rips.Instance.find()\r\ncases = resinsight.project.cases()\r\n\r\n# Set main window size\r\nresinsight.set_main_window_size(width=800, height=500)\r\n\r\nn = 5                            # every n-th time_step for snapshot\r\nproperty_list = ['SOIL', 'PRESSURE'] # list of parameter for snapshot\r\n\r\nprint (\u0026quot;Looping through cases\u0026quot;)\r\nfor case in cases:\r\n    print(\u0026quot;Case name: \u0026quot;, case.name)\r\n    print(\u0026quot;Case id: \u0026quot;, case.case_id)\r\n    # Get grid path and its folder name\r\n    case_path = case.grid_path()\r\n    folder_name = os.path.dirname(case_path)\r\n    \r\n    # create a folder to hold the snapshots\r\n    dirname = os.path.join(folder_name, 'snapshots')\r\n        \r\n    if os.path.exists(dirname) is False:\r\n        os.mkdir(dirname)\r\n    \r\n    print (\u0026quot;Exporting to folder: \u0026quot; + dirname)\r\n    resinsight.set_export_folder(export_type='SNAPSHOTS', path=dirname)\r\n   \r\n    time_steps = case.time_steps()\r\n    print('Number of time_steps: ' + str(len(time_steps)))\r\n        \r\n    view = case.views()[0]\r\n    for property in property_list:\r\n        view.apply_cell_result(result_type='DYNAMIC_NATIVE', result_variable=property)\r\n        for time_step in range(0, len(time_steps), 10):\r\n            view.set_time_step(time_step = time_step)\r\n            view.export_snapshot()\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"gridinformation\"\u003eGridInformation\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e######################################################################################\r\n# This example prints information about the grids of all cases in the current project\r\n######################################################################################\r\n\r\nimport rips\r\n\r\nresinsight  = rips.Instance.find()\r\n\r\ncases = resinsight.project.cases()\r\nprint(\u0026quot;Number of cases found: \u0026quot;, len(cases))\r\nfor case in cases:\r\n    print(case.name)\r\n    grids = case.grids()\r\n    print(\u0026quot;Number of grids: \u0026quot;, len(grids))\r\n    for grid in grids:\r\n        print(\u0026quot;Grid dimensions: \u0026quot;, grid.dimensions())\r\n\r\n\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"import-well-paths\"\u003eImport Well Paths\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\r\nimport rips\r\n# Connect to ResInsight instance\r\nresInsight = rips.Instance.find()\r\n\r\nwell_path_names = resInsight.project.import_well_paths(well_path_folder='D:/Projects/ResInsight-regression-test/ModelData/norne/wellpaths')\r\nif resInsight.project.has_warnings():\r\n    for warning in resInsight.project.warnings():\r\n        print(warning)\r\n\r\n\r\nfor well_path_name in well_path_names:\r\n    print(\u0026quot;Imported from folder: \u0026quot; + well_path_name)\r\n\r\nwell_path_names = resInsight.project.import_well_paths(well_path_files=['D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/E-3H.json',\r\n                                                                        'D:/Projects/ResInsight-regression-test/ModelData/Norne_WellPaths/C-1H.json'])\r\nif resInsight.project.has_warnings():\r\n    for warning in resInsight.project.warnings():\r\n        print(warning)\r\n\r\n\r\nfor well_path_name in well_path_names:\r\n    print(\u0026quot;Imported from indivdual files: \u0026quot; + well_path_name)\r\n\r\n\r\nwell_path_names = resInsight.project.import_well_log_files(well_log_folder='D:/Projects/ResInsight-regression-test/ModelData/Norne_PLT_LAS')\r\nif resInsight.project.has_warnings():\r\n    for warning in resInsight.project.warnings():\r\n        print(warning)\r\n\r\nfor well_path_name in well_path_names:\r\n    print(\u0026quot;Imported well log file for: \u0026quot; + well_path_name)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"inputproptestasync\"\u003eInputPropTestAsync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e########################################################################################\r\n# This example generates a derived property in an asynchronous manner\r\n# Meaning it does not wait for all the data for each stage to be read before proceeding\r\n########################################################################################\r\nimport rips\r\nimport time\r\n\r\n# Internal function for creating a result from a small chunk of poro and permx results\r\n# The return value of the function is a generator for the results rather than the result itself.\r\ndef create_result(poro_chunks, permx_chunks):\r\n    # Loop through all the chunks of poro and permx in order\r\n    for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\r\n        resultChunk = []\r\n        # Loop through all the values inside the chunks, in order\r\n        for (poro, permx) in zip(poroChunk.values, permxChunk.values):\r\n            resultChunk.append(poro * permx)\r\n        # Return a generator object that behaves like a Python iterator\r\n        yield resultChunk\r\n\r\nresinsight     = rips.Instance.find()\r\nstart = time.time()\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\r\nporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\r\n# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\r\npermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\r\n\r\n# Send back the result with the result provided by a generator object.\r\n# Iterating the result generator will cause the script to read from the poro and permx generators\r\n# And return the result of each iteration\r\ncase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\r\n                                           'GENERATED', 'POROPERMXAS', 0)\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"inputproptestsync\"\u003eInputPropTestSync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e########################################################################################\r\n# This example generates a derived property in an synchronous manner\r\n# Meaning it completes reading each result before calculating the derived result\r\n# See InputPropTestAsync for how to do this asynchronously instead.\r\n########################################################################################\r\nimport rips\r\nimport time\r\nimport grpc\r\n\r\nresinsight     = rips.Instance.find()\r\nstart = time.time()\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Read poro result into list\r\nporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\r\n# Read permx result into list\r\npermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\r\n\r\n# Generate output result\r\nresults = []\r\nfor (poro, permx) in zip(poro_results, permx_results):\r\n    results.append(poro * permx)\r\n\r\ntry:\r\n    # Send back output result\r\n    case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\r\nexcept grpc.RpcError as e:\r\n    print(\u0026quot;Exception Received: \u0026quot;, e)\r\n\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\n\r\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"instanceexample\"\u003eInstanceExample\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e#######################################\r\n# This example connects to ResInsight\r\n#######################################\r\nimport rips\r\n\r\nresinsight  = rips.Instance.find()\r\n\r\nif resinsight is None:\r\n    print('ERROR: could not find ResInsight')\r\nelse:\r\n\tprint('Successfully connected to ResInsight')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"launchwithcommandlineoptions\"\u003eLaunchWithCommandLineOptions\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e# Load ResInsight Processing Server Client Library\r\nimport rips\r\n# Launch ResInsight with last project file and a Window size of 600x1000 pixels\r\nresinsight = rips.Instance.launch(command_line_parameters=['--last', '--size', 600, 1000])\r\n# Get a list of all cases\r\ncases = resinsight.project.cases()\r\n\r\nprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\r\nfor case in cases:\r\n    print(\u0026quot;Case name: \u0026quot; + case.name)\r\n    print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"selectedcases\"\u003eSelectedCases\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e############################################################################\r\n# This example returns the currently selected cases in ResInsight\r\n# Because running this script in the GUI takes away the selection\r\n# This script does not run successfully from within the ResInsight GUI\r\n# And will need to be run from the command line separately from ResInsight\r\n############################################################################\r\n\r\nimport rips\r\n\r\nresinsight  = rips.Instance.find()\r\nif resinsight is not None:\r\n    cases = resinsight.project.selected_cases()\r\n\r\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\r\n    for case in cases:\r\n        print(case.name)\r\n        for property in case.available_properties('DYNAMIC_NATIVE'):\r\n            print(property)\r\n\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"setcellresult\"\u003eSetCellResult\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e######################################################################\r\n# This script applies a cell result to the first view in the project\r\n######################################################################\r\nimport rips\r\n\r\nresinsight  = rips.Instance.find()\r\n\r\nview = resinsight.project.views()[0]\r\nview.apply_cell_result(result_type='STATIC_NATIVE', result_variable='DX')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"setflowdiagnosticsresult\"\u003eSetFlowDiagnosticsResult\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e######################################################################\r\n# This script applies a flow diagnostics cell result to the first view in the project\r\n######################################################################\r\n\r\n# Load ResInsight Processing Server Client Library\r\nimport rips\r\n# Connect to ResInsight instance\r\nresinsight = rips.Instance.find()\r\n\r\nview = resinsight.project.view(view_id=1)\r\n#view.apply_flow_diagnostics_cell_result(result_variable='Fraction',\r\n#                                    selection_mode='FLOW_TR_INJ_AND_PROD')\r\n                                    \r\n# Example of setting individual wells. Commented out because well names are case specific.\r\nview.apply_flow_diagnostics_cell_result(result_variable='Fraction',\r\n                                    selection_mode='FLOW_TR_BY_SELECTION',\r\n                                    injectors = ['C-1H', 'C-2H', 'F-2H'],\r\n                                    producers = ['B-1AH', 'B-3H', 'D-1H'])\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"setgridproperties\"\u003eSetGridProperties\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e######################################################################\r\n# This script sets values for SOIL for all grid cells in the first case in the project\r\n######################################################################\r\nimport rips\r\n\r\nresinsight     = rips.Instance.find()\r\n\r\ncase = resinsight.project.case(case_id=0)\r\ntotal_cell_count = case.cell_count().reservoir_cell_count\r\n\r\nvalues = []\r\nfor i in range(0, total_cell_count):\r\n    values.append(i % 2 * 0.75);\r\n\r\nprint(\u0026quot;Applying values to full grid\u0026quot;)\r\ncase.set_grid_property(values, 'DYNAMIC_NATIVE', 'SOIL', 0)\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"soilaverageasync\"\u003eSoilAverageAsync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###########################################################################################\r\n# This example will asynchronously calculate the average value for SOIL for all time steps\r\n###########################################################################################\r\n\r\nimport rips\r\nimport itertools\r\nimport time\r\n\r\nresinsight     = rips.Instance.find()\r\n\r\nstart          = time.time()\r\n\r\n# Get the case with case id 0\r\ncase           = resinsight.project.case(case_id=0)\r\n\r\n# Get a list of all time steps\r\ntimeSteps      = case.time_steps()\r\n\r\naverages = []\r\nfor i in range(0, len(timeSteps)):\r\n    # Get the results from time step i asynchronously\r\n    # It actually returns a generator object almost immediately\r\n\tresult_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\r\n\tmysum = 0.0\r\n\tcount = 0\r\n    # Loop through and append the average. each time we loop resultChunks\r\n    # We will trigger a read of the input data, meaning the script will start\r\n    # Calculating averages before the whole resultValue for this time step has been received\r\n\tfor chunk in result_chunks:\r\n\t\tmysum += sum(chunk.values)\r\n\t\tcount += len(chunk.values)\r\n\r\n\taverages.append(mysum/count)\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(averages)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"soilaveragesync\"\u003eSoilAverageSync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e###########################################################################################\r\n# This example will synchronously calculate the average value for SOIL for all time steps\r\n###########################################################################################\r\nimport rips\r\nimport itertools\r\nimport time\r\n\r\nresinsight     = rips.Instance.find()\r\n\r\nstart          = time.time()\r\n\r\n# Get the case with case id 0\r\ncase           = resinsight.project.case(case_id=0)\r\n\r\n# Get a list of all time steps\r\ntime_steps      = case.time_steps()\r\n\r\naverages = []\r\nfor i in range(0, len(time_steps)):\r\n    # Get a list of all the results for time step i\r\n\tresults = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\r\n\tmysum = sum(results)\r\n\taverages.append(mysum/len(results))\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(averages)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"soilporvasync\"\u003eSoilPorvAsync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e##############################################################################\r\n# This example will create a derived result for each time step asynchronously\r\n##############################################################################\r\n\r\nimport rips\r\nimport time\r\n\r\n# Internal function for creating a result from a small chunk of soil and porv results\r\n# The return value of the function is a generator for the results rather than the result itself.\r\ndef create_result(soil_chunks, porv_chunks):\r\n    for (soil_chunk, porv_chunk) in zip(soil_chunks, porv_chunks):\r\n        resultChunk = []\r\n        number = 0\r\n        for (soil_value, porv_value) in zip(soil_chunk.values, porv_chunk.values):\r\n            resultChunk.append(soil_value * porv_value)\r\n        # Return a Python generator\r\n        yield resultChunk\r\n\r\nresinsight   = rips.Instance.find()\r\nstart        = time.time()\r\ncase         = resinsight.project.cases()[0]\r\ntimeStepInfo = case.time_steps()\r\n\r\n# Get a generator for the porv results. The generator will provide a chunk each time it is iterated\r\nporv_chunks   = case.active_cell_property_async('STATIC_NATIVE', 'PORV', 0)\r\n\r\n# Read the static result into an array, so we don't have to transfer it for each iteration\r\n# Note we use the async method even if we synchronise here, because we need the values chunked\r\n# ... to match the soil chunks\r\nporv_array = []\r\nfor porv_chunk in porv_chunks:\r\n    porv_array.append(porv_chunk)\r\n\r\nfor i in range (0, len(timeStepInfo)):\r\n    # Get a generator object for the SOIL property for time step i\r\n    soil_chunks = case.active_cell_property_async('DYNAMIC_NATIVE', 'SOIL', i)\r\n    # Create the generator object for the SOIL * PORV derived result\r\n    result_generator = create_result(soil_chunks, iter(porv_array))\r\n    # Send back the result asynchronously with a generator object\r\n    case.set_active_cell_property_async(result_generator, 'GENERATED', 'SOILPORVAsync', i)\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\n        \r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\n\r\nview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVAsync')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"soilporvsync\"\u003eSoilPorvSync\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e##############################################################################\r\n# This example will create a derived result for each time step synchronously\r\n##############################################################################\r\n\r\nimport rips\r\nimport time\r\n\r\nresinsight = rips.Instance.find()\r\nstart = time.time()\r\ncase       = resinsight.project.cases()[0]\r\n\r\n# Read the full porv result\r\nporv_results = case.active_cell_property('STATIC_NATIVE', 'PORV', 0)\r\ntime_step_info = case.time_steps()\r\n\r\nfor i in range (0, len(time_step_info)):\r\n    # Read the full SOIl result for time step i\r\n    soil_results = case.active_cell_property('DYNAMIC_NATIVE', 'SOIL', i)\r\n    \r\n    # Generate the result by looping through both lists in order\r\n    results = []\r\n    for (soil, porv) in zip(soil_results, porv_results):\r\n        results.append(soil * porv)\r\n\r\n    # Send back result\r\n    case.set_active_cell_property(results, 'GENERATED', 'SOILPORVSync', i)\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\n\r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\n\r\nview = case.views()[0].apply_cell_result('GENERATED', 'SOILPORVSync')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"viewexample\"\u003eViewExample\u003c/h1\u003e\n\u003cpre\u003e\u003ccode\u003e#############################################################\r\n# This example will alter the views of all cases\r\n# By setting the background color and toggle the grid box\r\n# Also clones the first view\r\n#############################################################\r\nimport rips\r\n# Connect to ResInsight instance\r\nresinsight = rips.Instance.find()\r\n\r\n# Check if connection worked\r\nif resinsight is not None:\r\n    # Get a list of all cases\r\n    cases = resinsight.project.cases()\r\n    for case in cases:\r\n        # Get a list of all views\r\n        views = case.views()\r\n        for view in views:\r\n            # Set some parameters for the view\r\n            view.set_show_grid_box(not view.show_grid_box())\r\n            view.set_background_color(\u0026quot;#3388AA\u0026quot;)            \r\n            # Update the view in ResInsight\r\n            view.update()\r\n        # Clone the first view\r\n        new_view = views[0].clone()\r\n        view.set_show_grid_box(False)\r\n        new_view.set_background_color(\u0026quot;#FFAA33\u0026quot;)\r\n        new_view.update()\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/scripting/pythonexamples/"
             };
         
@@ -2190,8 +2223,8 @@ if (!doNotTrack) {
          
             window.store["/misc/regressiontestsystem/"] = {
                 title:    "Regression Test System",
-                content:  " A regression tool for QA is build into ResInsight. This tool will do the following:\n Scan a directory for sub directories containing a RegressionTest.rsp files. Each found project file will be opened, and all views in this project will be exported as snapshot images to file. When snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed. Based on these three sets of images, an HTML report is created and automatically displayed.  How to Run Regression Tests To be able to run regression tests you need the compare tool from the ImageMagic suite.\nYou can start the tests either from the command line or from the ResInsight Gui. From the ResInsight Gui select : File-\u0026gt;Testing-\u0026gt;Regression Test Dialog\nSpecify location of compare tool in Folder containing compare. The current working directory of ResInsight is temporarily changed to this path during execution.\nTo execute a subset of tests, specify folder names separated by \u0026ldquo;;\u0026rdquo; in the Test Filter. If the test filter is empty, all tests are executed.\nCreating Regression Tests An example of the folder structure is shown below:\nRegressionTestFolder/ TestCase1/ RegressionTest.rip RegTestBaseImages/ RegTestDiffImages/ RegTestGeneratedImages/ TestCase2/ ...  To create regression tests you need to do the following:\n Create a root directory containing one directory for each test case. In each of the Test Case folders create a ResInsight project file called RegressionTest.rip. Run the regression test for the first time, and thereby creating images that can be used as Base images. Rename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/  Now you are all set to test new releases of ResInsight towards your own Regression tests.\n",
-                html:     "\n\n\u003cp\u003eA regression tool for QA is build into ResInsight. This tool will do the following:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eScan a directory for sub directories containing a \u003cstrong\u003eRegressionTest.rsp\u003c/strong\u003e files.\u003c/li\u003e\n\u003cli\u003eEach found project file will be opened, and all views in this project will be exported as snapshot images to file.\u003c/li\u003e\n\u003cli\u003eWhen snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed.\u003c/li\u003e\n\u003cli\u003eBased on these three sets of images, an HTML report is created and automatically displayed.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003ch2 id=\"how-to-run-regression-tests\"\u003eHow to Run Regression Tests\u003c/h2\u003e\n\n\u003cp\u003eTo be able to run regression tests you need the \u003cstrong\u003ecompare\u003c/strong\u003e tool from the \u003ca href=\"http://www.imagemagick.org/script/compare.php\"\u003eImageMagic suite\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eYou can start the tests either from the command line or from the ResInsight Gui.\nFrom the ResInsight Gui select : \u003cstrong\u003eFile-\u0026gt;Testing-\u0026gt;Regression Test Dialog\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/RegressionTestDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eSpecify location of compare tool in \u003cstrong\u003eFolder containing compare\u003c/strong\u003e. The current working directory of ResInsight is temporarily changed to this path during execution.\u003c/p\u003e\n\n\u003cp\u003eTo execute a subset of tests, specify folder names separated by \u0026ldquo;;\u0026rdquo; in the \u003cem\u003eTest Filter\u003c/em\u003e. If the test filter is empty, all tests are executed.\u003c/p\u003e\n\n\u003ch2 id=\"creating-regression-tests\"\u003eCreating Regression Tests\u003c/h2\u003e\n\n\u003cp\u003eAn example of the folder structure is shown below:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eRegressionTestFolder/\n  TestCase1/\n    RegressionTest.rip\n    RegTestBaseImages/\n    RegTestDiffImages/\n    RegTestGeneratedImages/\n  TestCase2/\n    ...\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eTo create regression tests you need to do the following:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eCreate a root directory containing one directory for each test case.\u003c/li\u003e\n\u003cli\u003eIn each of the \u003cstrong\u003eTest Case\u003c/strong\u003e folders create a ResInsight project file called \u003cstrong\u003eRegressionTest.rip\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eRun the regression test for the first time, and thereby creating images that can be used as Base images.\u003c/li\u003e\n\u003cli\u003eRename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eNow you are all set to test new releases of ResInsight towards your own Regression tests.\u003c/p\u003e\n",
+                content:  "A regression tool for QA is build into ResInsight. This tool will do the following:\n Scan a directory for sub directories containing a RegressionTest.rsp files. Each found project file will be opened, and all views in this project will be exported as snapshot images to file. When snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed. Based on these three sets of images, an HTML report is created and automatically displayed.  How to Run Regression Tests To be able to run regression tests you need the compare tool from the ImageMagic suite.\nYou can start the tests either from the command line or from the ResInsight Gui. From the ResInsight Gui select : File-\u0026gt;Testing-\u0026gt;Regression Test Dialog\nSpecify location of compare tool in Folder containing compare. The current working directory of ResInsight is temporarily changed to this path during execution.\nTo execute a subset of tests, specify folder names separated by \u0026ldquo;;\u0026rdquo; in the Test Filter. If the test filter is empty, all tests are executed.\nCreating Regression Tests An example of the folder structure is shown below:\nRegressionTestFolder/\rTestCase1/\rRegressionTest.rip\rRegTestBaseImages/\rRegTestDiffImages/\rRegTestGeneratedImages/\rTestCase2/\r...\r To create regression tests you need to do the following:\n Create a root directory containing one directory for each test case. In each of the Test Case folders create a ResInsight project file called RegressionTest.rip. Run the regression test for the first time, and thereby creating images that can be used as Base images. Rename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/  Now you are all set to test new releases of ResInsight towards your own Regression tests.\n",
+                html:     "\u003cp\u003eA regression tool for QA is build into ResInsight. This tool will do the following:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eScan a directory for sub directories containing a \u003cstrong\u003eRegressionTest.rsp\u003c/strong\u003e files.\u003c/li\u003e\n\u003cli\u003eEach found project file will be opened, and all views in this project will be exported as snapshot images to file.\u003c/li\u003e\n\u003cli\u003eWhen snapshot images from all projects are completed, difference images based on generated and QA-approved images are computed.\u003c/li\u003e\n\u003cli\u003eBased on these three sets of images, an HTML report is created and automatically displayed.\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"how-to-run-regression-tests\"\u003eHow to Run Regression Tests\u003c/h2\u003e\n\u003cp\u003eTo be able to run regression tests you need the \u003cstrong\u003ecompare\u003c/strong\u003e tool from the \u003ca href=\"http://www.imagemagick.org/script/compare.php\"\u003eImageMagic suite\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eYou can start the tests either from the command line or from the ResInsight Gui.\nFrom the ResInsight Gui select : \u003cstrong\u003eFile-\u0026gt;Testing-\u0026gt;Regression Test Dialog\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/RegressionTestDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSpecify location of compare tool in \u003cstrong\u003eFolder containing compare\u003c/strong\u003e. The current working directory of ResInsight is temporarily changed to this path during execution.\u003c/p\u003e\n\u003cp\u003eTo execute a subset of tests, specify folder names separated by \u0026ldquo;;\u0026rdquo; in the \u003cem\u003eTest Filter\u003c/em\u003e. If the test filter is empty, all tests are executed.\u003c/p\u003e\n\u003ch2 id=\"creating-regression-tests\"\u003eCreating Regression Tests\u003c/h2\u003e\n\u003cp\u003eAn example of the folder structure is shown below:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eRegressionTestFolder/\r\n  TestCase1/\r\n    RegressionTest.rip\r\n    RegTestBaseImages/\r\n    RegTestDiffImages/\r\n    RegTestGeneratedImages/\r\n  TestCase2/\r\n    ...\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eTo create regression tests you need to do the following:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eCreate a root directory containing one directory for each test case.\u003c/li\u003e\n\u003cli\u003eIn each of the \u003cstrong\u003eTest Case\u003c/strong\u003e folders create a ResInsight project file called \u003cstrong\u003eRegressionTest.rip\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eRun the regression test for the first time, and thereby creating images that can be used as Base images.\u003c/li\u003e\n\u003cli\u003eRename the generated RegTestGeneratedImages/ folder to RegTestBaseImages/\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eNow you are all set to test new releases of ResInsight towards your own Regression tests.\u003c/p\u003e\n",
                 url:      "/misc/regressiontestsystem/"
             };
         
@@ -2199,8 +2232,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/other/releasenotification/"] = {
                 title:    "Release Notification Subscription",
-                content:  " LinkedIn Feel free to join ResInsight on LinkedIn\nNewsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.\nSubscribe\n",
-                html:     "\n\n\u003ch3 id=\"linkedin\"\u003eLinkedIn\u003c/h3\u003e\n\n\u003cp\u003eFeel free to join \u003ca href=\"https://www.linkedin.com/groups/12167660/\"\u003eResInsight on LinkedIn\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"newsletter\"\u003eNewsletter\u003c/h3\u003e\n\n\u003cp\u003eBy subscribing to the \u003cstrong\u003eRelease Notification\u003c/strong\u003e you will get notified when new releases are available.\nPlease use the button below to send a request for subscription mail.\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"mailto:info@ceetronsolutions.com?subject=ResInsight Release Notification subscription\u0026body=Hi ResInsight administrator, I would like to subscribe to the ResInsight release notifications.\"\u003eSubscribe\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "LinkedIn Feel free to join ResInsight on LinkedIn\nNewsletter By subscribing to the Release Notification you will get notified when new releases are available. Please use the button below to send a request for subscription mail.\nSubscribe",
+                html:     "\u003ch3 id=\"linkedin\"\u003eLinkedIn\u003c/h3\u003e\n\u003cp\u003eFeel free to join \u003ca href=\"https://www.linkedin.com/groups/12167660/\"\u003eResInsight on LinkedIn\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"newsletter\"\u003eNewsletter\u003c/h3\u003e\n\u003cp\u003eBy subscribing to the \u003cstrong\u003eRelease Notification\u003c/strong\u003e you will get notified when new releases are available. \nPlease use the button below to send a request for subscription mail.\u003c/p\u003e\n\u003cp\u003e\u003c!-- raw HTML omitted --\u003eSubscribe\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/other/releasenotification/"
             };
         
@@ -2208,8 +2241,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summarycrossplots/"] = {
                 title:    "Summary Cross Plot",
-                content:  " A Summary Cross Plot is a window displaying a graph in the main area of the Plot Main Window. It is very similar to an ordinary Summary Plot, but there are some differences:\n Summary Cross Plot displays one vector against another vector, not one vector against time. Not possible to paste Excel/CSV data to a summary cross plot. Summary cross plots have no Plot Editor.  The only way to create a new Summary Cross Plot, is to select the context command New Summary Cross Plot on the Plot Main Window -\u0026gt; Project Tree -\u0026gt; Summary Cross Plots item.\nSummary Cross Plot Curves New Summary Cross Plot curves are created by using the context command New Summary Cross Plot Curve on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the Summary Cross Plot Curve property editor.\nIn this property editor, the editor group called Summary Vector, has been replaced by two vector selection groups Summary Vector Y and Summary Vector X, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The Summary Vector X group is missing the Axis field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the detailed description.\nCross Plotting Cross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.\nWhen a current time step T in input vector A is not found in input vector B, ResInsight interpolates between the time steps before and after T in vector B. In this way, ResInsight calculates an interpolated value for time step T from vector B. The same happens when a time step in vector B is not found in vector A.\nIf either the value at the current time step or one of the values involved in interpolation are NULL, the resulting vector will have a NULL value at the current time step. This is displayed as a \u0026lsquo;hole\u0026rsquo; in the cross plot curve.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCrossPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA Summary Cross Plot is a window displaying a graph in the main area of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e. It is very similar to an ordinary \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plot\u003c/a\u003e, but there are some differences:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSummary Cross Plot displays one vector against another vector, not one vector against time.\u003c/li\u003e\n\u003cli\u003eNot possible to paste Excel/CSV data to a summary cross plot.\u003c/li\u003e\n\u003cli\u003eSummary cross plots have no \u003ca href=\"/plot-window/summaryploteditor/\"\u003ePlot Editor\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe only way to create a new Summary Cross Plot, is to select the context command \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Cross Plot\u003c/strong\u003e on the \u003cstrong\u003ePlot Main Window -\u0026gt; Project Tree -\u0026gt; Summary Cross Plots\u003c/strong\u003e item.\u003c/p\u003e\n\n\u003ch2 id=\"summary-cross-plot-curves\"\u003eSummary Cross Plot Curves\u003c/h2\u003e\n\n\u003cp\u003eNew Summary Cross Plot curves are created by using the context command \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryCurve16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Cross Plot Curve\u003c/strong\u003e on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the \u003cstrong\u003eSummary Cross Plot Curve\u003c/strong\u003e property editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCrossPlotCurvePropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn this property editor, the editor group called \u003cstrong\u003eSummary Vector\u003c/strong\u003e, has been replaced by two vector selection groups \u003cstrong\u003eSummary Vector Y\u003c/strong\u003e and \u003cstrong\u003eSummary Vector X\u003c/strong\u003e, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The \u003cstrong\u003eSummary Vector X\u003c/strong\u003e group is missing the \u003cstrong\u003eAxis\u003c/strong\u003e field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the \u003ca href=\"/plot-window/summaryplots/#summary-curves\"\u003edetailed description\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"cross-plotting\"\u003eCross Plotting\u003c/h3\u003e\n\n\u003cp\u003eCross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.\u003c/p\u003e\n\n\u003cp\u003eWhen a current time step \u003cstrong\u003eT\u003c/strong\u003e in input vector \u003cstrong\u003eA\u003c/strong\u003e is not found in input vector \u003cstrong\u003eB\u003c/strong\u003e, ResInsight interpolates between the time steps before and after \u003cstrong\u003eT\u003c/strong\u003e in vector \u003cstrong\u003eB\u003c/strong\u003e. In this way, ResInsight calculates an interpolated value for time step \u003cstrong\u003eT\u003c/strong\u003e from vector \u003cstrong\u003eB\u003c/strong\u003e. The same happens when a time step in vector \u003cstrong\u003eB\u003c/strong\u003e is not found in vector \u003cstrong\u003eA\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf either the value at the current time step or one of the values involved in interpolation are \u003cstrong\u003eNULL\u003c/strong\u003e, the resulting vector will have a \u003cstrong\u003eNULL\u003c/strong\u003e value at the current time step. This is displayed as a \u0026lsquo;hole\u0026rsquo; in the cross plot curve.\u003c/p\u003e\n",
+                content:  "A Summary Cross Plot is a window displaying a graph in the main area of the Plot Main Window. It is very similar to an ordinary Summary Plot, but there are some differences:\n Summary Cross Plot displays one vector against another vector, not one vector against time. Not possible to paste Excel/CSV data to a summary cross plot. Summary cross plots have no Plot Editor.  The only way to create a new Summary Cross Plot, is to select the context command New Summary Cross Plot on the Plot Main Window -\u0026gt; Project Tree -\u0026gt; Summary Cross Plots item.\nSummary Cross Plot Curves New Summary Cross Plot curves are created by using the context command New Summary Cross Plot Curve on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the Summary Cross Plot Curve property editor.\nIn this property editor, the editor group called Summary Vector, has been replaced by two vector selection groups Summary Vector Y and Summary Vector X, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The Summary Vector X group is missing the Axis field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the detailed description.\nCross Plotting Cross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.\nWhen a current time step T in input vector A is not found in input vector B, ResInsight interpolates between the time steps before and after T in vector B. In this way, ResInsight calculates an interpolated value for time step T from vector B. The same happens when a time step in vector B is not found in vector A.\nIf either the value at the current time step or one of the values involved in interpolation are NULL, the resulting vector will have a NULL value at the current time step. This is displayed as a \u0026lsquo;hole\u0026rsquo; in the cross plot curve.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCrossPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Summary Cross Plot is a window displaying a graph in the main area of the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e. It is very similar to an ordinary \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plot\u003c/a\u003e, but there are some differences:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSummary Cross Plot displays one vector against another vector, not one vector against time.\u003c/li\u003e\n\u003cli\u003eNot possible to paste Excel/CSV data to a summary cross plot.\u003c/li\u003e\n\u003cli\u003eSummary cross plots have no \u003ca href=\"/plot-window/summaryploteditor/\"\u003ePlot Editor\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe only way to create a new Summary Cross Plot, is to select the context command \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlot16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Cross Plot\u003c/strong\u003e on the \u003cstrong\u003ePlot Main Window -\u0026gt; Project Tree -\u0026gt; Summary Cross Plots\u003c/strong\u003e item.\u003c/p\u003e\n\u003ch2 id=\"summary-cross-plot-curves\"\u003eSummary Cross Plot Curves\u003c/h2\u003e\n\u003cp\u003eNew Summary Cross Plot curves are created by using the context command \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryCurve16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Summary Cross Plot Curve\u003c/strong\u003e on a summary cross plot. To be able to display a Summary Cross Plot curve, ResInsight needs two data vectors, which are selected using the \u003cstrong\u003eSummary Cross Plot Curve\u003c/strong\u003e property editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCrossPlotCurvePropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn this property editor, the editor group called \u003cstrong\u003eSummary Vector\u003c/strong\u003e, has been replaced by two vector selection groups \u003cstrong\u003eSummary Vector Y\u003c/strong\u003e and \u003cstrong\u003eSummary Vector X\u003c/strong\u003e, compared to an ordinary summary plot. Like the other property editor groups, the vector selection groups works the same way as in the ordinary summary plot. However, there is one exception. The \u003cstrong\u003eSummary Vector X\u003c/strong\u003e group is missing the \u003cstrong\u003eAxis\u003c/strong\u003e field. This is because the X values have one axis only, below the plot, as opposed to the Y values, which have the left and right axis. See the \u003ca href=\"/plot-window/summaryplots/#summary-curves\"\u003edetailed description\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"cross-plotting\"\u003eCross Plotting\u003c/h3\u003e\n\u003cp\u003eCross plotting creates a new vector from two input vectors. Each vector entry in the resulting vector consists of one vector item value from each of the two input vectors, having equal time steps. However, in most cases the two input vectors do not share the same time steps. To be able to create a resulting cross plot vector in such cases, linear interpolation between adjacent input vector items is being used.\u003c/p\u003e\n\u003cp\u003eWhen a current time step \u003cstrong\u003eT\u003c/strong\u003e in input vector \u003cstrong\u003eA\u003c/strong\u003e is not found in input vector \u003cstrong\u003eB\u003c/strong\u003e, ResInsight interpolates between the time steps before and after \u003cstrong\u003eT\u003c/strong\u003e in vector \u003cstrong\u003eB\u003c/strong\u003e. In this way, ResInsight calculates an interpolated value for time step \u003cstrong\u003eT\u003c/strong\u003e from vector \u003cstrong\u003eB\u003c/strong\u003e. The same happens when a time step in vector \u003cstrong\u003eB\u003c/strong\u003e is not found in vector \u003cstrong\u003eA\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eIf either the value at the current time step or one of the values involved in interpolation are \u003cstrong\u003eNULL\u003c/strong\u003e, the resulting vector will have a \u003cstrong\u003eNULL\u003c/strong\u003e value at the current time step. This is displayed as a \u0026lsquo;hole\u0026rsquo; in the cross plot curve.\u003c/p\u003e\n",
                 url:      "/plot-window/summarycrossplots/"
             };
         
@@ -2218,7 +2251,7 @@ if (!doNotTrack) {
             window.store["/wells-and-completions/"] = {
                 title:    "Wells and Completions",
                 content:  "This chaper describes the following aspects of wells and completions:\n how wells defined in the simulation are displayed and how to control the different aspects of their visualization retrieval of well trajectories from file and an internal Equinor web service the creation of user-defined well paths display of well log curves directly in a 3D view based on well log data from a simulation model or imported LAS-files modeling and export of completions including perforation intervals, fishbone wells and fractures in order to perform refined simulations creating and exporting local grid refinement (LGRs) in main grid cells intersected by completions  The following subchapters details the functionality and capabilites.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveVisualisation.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis chaper describes the following aspects of wells and completions:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003ehow wells defined in the simulation are displayed and how to control the different aspects of their visualization\u003c/li\u003e\n\u003cli\u003eretrieval of well trajectories from file and an internal Equinor web service\u003c/li\u003e\n\u003cli\u003ethe creation of user-defined well paths\u003c/li\u003e\n\u003cli\u003edisplay of well log curves directly in a 3D view based on well log data from a simulation model or imported LAS-files\u003c/li\u003e\n\u003cli\u003emodeling and export of completions including perforation intervals, fishbone wells and fractures in order to perform refined simulations\u003c/li\u003e\n\u003cli\u003ecreating and exporting local grid refinement (LGRs) in main grid cells intersected by completions\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe following subchapters details the functionality and capabilites.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveVisualisation.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis chaper describes the following aspects of wells and completions:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ehow wells defined in the simulation are displayed and how to control the different aspects of their visualization\u003c/li\u003e\n\u003cli\u003eretrieval of well trajectories from file and an internal Equinor web service\u003c/li\u003e\n\u003cli\u003ethe creation of user-defined well paths\u003c/li\u003e\n\u003cli\u003edisplay of well log curves directly in a 3D view based on well log data from a simulation model or imported LAS-files\u003c/li\u003e\n\u003cli\u003emodeling and export of completions including perforation intervals, fishbone wells and fractures in order to perform refined simulations\u003c/li\u003e\n\u003cli\u003ecreating and exporting local grid refinement (LGRs) in main grid cells intersected by completions\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe following subchapters details the functionality and capabilites.\u003c/p\u003e\n",
                 url:      "/wells-and-completions/"
             };
         
@@ -2226,8 +2259,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/pythonrips/"] = {
                 title:    "Python API - rips",
-                content:  " Instance Module class rips.instance.Instance(port=50051, launched=False) The ResInsight Instance class. Use to launch or find existing ResInsight instances\nlaunched() Tells us whether the application was launched as a new process. If the application was launched we may need to close it when exiting the script.\n Type\nbool\n  commands() Command executor. Set when creating an instance.\n Type\nCommands\n  project() Current project in ResInsight. Set when creating an instance and updated when opening/closing projects.\n Type\nProject\n  client_version_string() Get a full version string, i.e. 2019.04.01\nexit() Tell ResInsight instance to quit\nstatic find(start_port=50051, end_port=50071) Search for an existing Instance of ResInsight by testing ports.\nBy default we search from port 50051 to 50071 or if the environment variable RESINSIGHT_GRPC_PORT is set we search RESINSIGHT_GRPC_PORT to RESINSIGHT_GRPC_PORT+20\n Parameters\n start_port (int) \u0026ndash; start searching from this port\n end_port (int) \u0026ndash; search up to but not including this port\n   is_console() Returns true if the connected ResInsight instance is a console app\nis_gui() Returns true if the connected ResInsight instance is a GUI app\nstatic launch(resinsight_executable=\u0026ldquo;, console=False, launch_port=-1, command_line_parameters=None) Launch a new Instance of ResInsight. This requires the environment variable RESINSIGHT_EXECUTABLE to be set or the parameter resinsight_executable to be provided. The RESINSIGHT_GRPC_PORT environment variable can be set to an alternative port number.\n Parameters\n resinsight_executable (str) \u0026ndash; Path to a valid ResInsight executable. If set will take precedence over what is provided in the RESINSIGHT_EXECUTABLE environment variable.\n console (bool) \u0026ndash; If True, launch as console application, without GUI.\n launch_port (int) \u0026ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT if anything else, ResInsight will try to launch with this port\n command_line_parameters (list) \u0026ndash; Additional parameters as string entries in the list.\n  Returns\nan instance object if it worked. None if not.\n Return type\nInstance\n  major_version() Get an integer with the major version number\nminor_version() Get an integer with the minor version number\npatch_version() Get an integer with the patch version number\nset_export_folder(export_type, path, create_folder=False) Set the export folder used for all export functions\n   Parameter Description Type     export_type String specifying what to export String   path Path to folder String   create_folder Create folder if it doesn\u0026rsquo;t exist? Boolean    Enum export_type    Option Description     \u0026ldquo;COMPLETIONS\u0026rdquo;    \u0026ldquo;SNAPSHOTS\u0026rdquo;    \u0026ldquo;PROPERTIES\u0026rdquo;    \u0026ldquo;STATISTICS\u0026rdquo;     set_main_window_size(width, height) Set the main window size in pixels\n   Parameter Description Type     width Width in pixels Integer   height Height in pixels Integer    set_plot_window_size(width, height) Set the plot window size in pixels\n   Parameter Description Type     width Width in pixels Integer   height Height in pixels Integer    set_start_dir(path) Set current start directory\n Parameters\npath (str) \u0026ndash; path to directory\n  version_string() Get a full version string, i.e. 2019.04.01\nExample  resinsight = rips.Instance.find() if resinsight is None: print('ERROR: could not find ResInsight') else: print('Successfully connected to ResInsight')  Case Module class rips.case.Case(channel, case_id, project) ResInsight case class\nOperate on a ResInsight case specified by a Case Id integer. Not meant to be constructed separately but created by one of the following methods in Project: loadCase, case, allCases, selectedCasesq\nid() Case Id corresponding to case Id in ResInsight project.\n Type\nint\n  name() Case name\n Type\nstr\n  group_id() Case Group id\n Type\nint\n  chunkSize() The size of each chunk during value streaming. A good chunk size is 64KiB = 65536B. Meaning the ideal number of doubles would be 8192. However we need overhead space, so the default is 8160. This leaves 256B for overhead.\n Type\nint\n  active_cell_property(property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a cell property for all active cells. Sync, so returns a list\n Parameters\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n porosity_model (str) \u0026ndash; string enum. See available()\n  Returns\nA list containing double values Loop through the chunks and then the values within the chunk to get all values.\n  active_cell_property_async(property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a cell property for all active cells. Async, so returns an iterator\n Parameters\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n porosity_model (str) \u0026ndash; string enum. See available()\n  Returns\nAn iterator to a chunk object containing an array of double values Loop through the chunks and then the values within the chunk to get all values.\n  available_properties(property_type, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a list of available properties\n Parameters\n property_type (str) \u0026ndash; string corresponding to property_type enum. Choices:\n DYNAMIC_NATIVE STATIC_NATIVE SOURSIMRL GENERATED INPUT_PROPERTY FORMATION_NAMES FLOW_DIAGNOSTICS INJECTION_FLOODING  porosity_model (str) \u0026ndash; \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n   cell_count(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a cell count object containing number of active cells and total number of cells\n Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n Returns\nactive_cell_count: number of active cells reservoir_cell_count: total number of reservoir cells\n Return type\nCell Count object with the following integer attributes\n  cell_info_for_active_cells(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get list of cell info objects for current case\n Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n Returns\nList of CellInfo objects\n  CellInfo class description    Parameter Description Type     grid_index Index to grid Integer   parent_grid_index Index to parent grid Integer   coarsening_box_index Index to coarsening box Integer   local_ijk Cell index in IJK directions of local grid Vec3i   parent_ijk Cell index in IJK directions of parent grid Vec3i    Vec3i class description    Parameter Description Type     i I grid index Integer   j J grid index Integer   k K grid index Integer    cell_info_for_active_cells_async(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get Stream of cell info objects for current case\n Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n Returns\nStream of CellInfo objects\n  See cell_info_for_active_cells() for detalis on the CellInfo class.\ncontour_maps(map_type=) Get a list of all contour maps belonging to a project\n   Parameter Description Type     time_steps Time step index Integer   well_path_names List of well path names List of Strings   refinement_i Refinment in x-direction Integer   refinement_j Refinment in y-direction Integer   refinement_k Refinment in z-direction Integer   split_type Defines how to split LGRS String enum     Parameters\nmap_type (enum) \u0026ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH\n  create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action) Create Multiple Fractures in one go\ncreate_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type) Create a local grid refinement for the completions on the given well paths\n   Parameter Description Type     time_steps Time step index Integer   well_path_names List of well path names List of Strings   refinement_i Refinment in x-direction Integer   refinement_j Refinment in y-direction Integer   refinement_k Refinment in z-direction Integer   split_type Defines how to split LGRS String enum    Enum split_type    Option Description     \u0026ldquo;LGR_PER_CELL\u0026rdquo; One LGR for each completed cell   \u0026ldquo;LGR_PER_COMPLETION\u0026rdquo; One LGR for each completion (fracture, perforation, \u0026hellip;)   \u0026ldquo;LGR_PER_WELL\u0026rdquo; One LGR for each well    create_view() Create a new view in the current case\ncreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action) Create Multiple Fractures in one go\n   Parameter Description Type     template_id Id of the template Integer   well_path_names List of well path names List of Strings   min_dist_from_well_td Minimum distance from well TD Double   max_fractures_per_well Max number of fractures per well Integer   top_layer Top grid k-level for fractures Integer   base_layer Base grid k-level for fractures Integer   spacing Spacing between fractures Double   action \u0026lsquo;APPEND_FRACTURES\u0026rsquo; or \u0026lsquo;REPLACE_FRACTURES\u0026rsquo; String enum    create_saturation_pressure_plots() Create saturation pressure plots for the current case\ncreate_view() Create a new view in the current case\ncreate_well_bore_stability_plot(well_path, time_step) Create a new well bore stability plot\n Parameters\n well_path (str) \u0026ndash; well path name\n time_step (int) \u0026ndash; time step\n  Returns\nA new plot object\n  days_since_start() Get a list of decimal values representing days since the start of the simulation\n* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter  export_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1) Export Flow Characteristics data to text file in CSV format\n   Parameter Description Type     time_steps Time step indices List of Integer   injectors Injector names List of Strings   producers Producer names List of Strings   file_name Export file name Integer   minimum_communication Minimum Communication, defaults to 0.0 Integer   aquifer_cell_threshold Aquifer Cell Threshold, defaults to 0.1 Integer    export_msw(well_path) Export Eclipse Multi-segment-well model to file\n Parameters\n Parameters\nwell_path (str) \u0026ndash; Well path name\n  export_property(time_step, property_name, eclipse_keyword=, undefined_value=0.0, export_file=) Export an Eclipse property\nEnum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; A single file with all combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well with combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    * **time_step** (*int*) -- time step index * **property_name** (*str*) -- property to export * **eclipse_keyword** (*str*) -- Keyword used in export header. Defaults: value of property * **undefined_value** (*double*) -- Value to use for undefined values. Defaults to 0.0 * **export_file** (*str*) -- File name for export. Defaults to the value of property parameter  grid(index) Get Grid of a given index. Returns a rips Grid object\nexport_snapshots_of_all_views(prefix=\u0026ldquo;, export_folder=\u0026ldquo;) Export snapshots for all views in the case\n Parameters\n prefix (str) \u0026ndash; Exported file name prefix\n export_folder (str) \u0026ndash; The path to export to. By default will use the global export folder\n   export_well_path_completions(time_step, well_path_names, file_split, compdat_export=\u0026lsquo;TRANSMISSIBILITIES\u0026rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode=\u0026lsquo;INDIVIDUALLY\u0026rsquo;) Export well path completions for the current case to file\n   Parameter Description Type     time_step Time step to export for Integer   well_path_names List of well path names List   file_split Controls how export data is split into files String enum   compdat_export Compdat export type String enum   include_perforations Export perforations? bool   include_fishbones Export fishbones? bool   fishbones_exclude_main_bore Exclude main bore when exporting fishbones? bool   combination_mode Settings for multiple completions in same cell String Enum    Enum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; A single file with all combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well with combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    Enum compdat_export    Option Description     \u0026ldquo;TRANSMISSIBILITIES\u0026rdquo; Direct export of transmissibilities   \u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo; Include WPIMULT in addition to transmissibilities    Enum combination_mode    Option Description     \u0026ldquo;INDIVIDUALLY\u0026rdquo; Exports the different completion types into separate sections   \u0026ldquo;COMBINED\u0026rdquo; Export one combined transmissibility for each cell    grid(index) Get Grid of a given index. Returns a rips Grid object\n Parameters\nindex (int) \u0026ndash; The grid index\n property_name (str) \u0026ndash; name of an Eclipse property   Returns: Grid object\ngrid_path() Get path of the current grid case\nReturns: path string\ngrid_property(property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a cell property for all grid cells. Synchronous, so returns a list\n Parameters\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n grid_index (int) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\n porosity_model (str) \u0026ndash; string enum. See available()\n  Returns\nA list of double values\n  grid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Get a cell property for all grid cells. Async, so returns an iterator\n Parameters\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n gridIndex (int) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\n porosity_model (str) \u0026ndash; string enum. See available()\n  Returns\nAn iterator to a chunk object containing an array of double values Loop through the chunks and then the values within the chunk to get all values.\n  grids() Get a list of all rips Grid objects in the case\nimport_formation_names(formation_files=None) Import formation names into project and apply it to the current case\n Parameters\nformation_files (list) \u0026ndash; list of files to import\n  replace(new_grid_file) Replace the current case grid with a new grid loaded from file\n Parameters\nnew_egrid_file (str) \u0026ndash; path to EGRID file\n property_name (str) \u0026ndash; name of an Eclipse property   set_active_cell_property(values, property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Set a cell property for all active cells.\n Parameters\n values (list) \u0026ndash; a list of double precision floating point numbers\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n porosity_model (str) \u0026ndash; string enum. See available()\n   set_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Set cell property for all active cells Async. Takes an iterator to the input values\n Parameters\n values_iterator (iterator) \u0026ndash; an iterator to the properties to be set\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n porosity_model (str) \u0026ndash; string enum. See available()\n   set_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;) Set a cell property for all grid cells.\n Parameters\n values (list) \u0026ndash; a list of double precision floating point numbers\n property_type (str) \u0026ndash; string enum. See available()\n property_name (str) \u0026ndash; name of an Eclipse property\n time_step (int) \u0026ndash; the time step for which to get the property for\n grid_index (int) \u0026ndash; index to the grid we\u0026rsquo;re setting values for\n porosity_model (str) \u0026ndash; string enum. See available()\n   time_steps() Get a list containing all time steps\nThe time steps are defined by the class TimeStepDate :\n   Type Name     int year   int month   int day   int hour   int minute   int second    view(view_id) Get a particular view belonging to a case by providing view id :param view_id: view id :type view_id: int\nReturns: a view object\nviews() Get a list of views belonging to a case\nExample  # Import the ResInsight Processing Server Module import rips # Connect to ResInsight resinsight = rips.Instance.find() if resinsight is not None: # Get a list of all cases cases = resinsight.project.cases() print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;) for case in cases: print(\u0026quot;Case id: \u0026quot; + str(case.case_id)) print(\u0026quot;Case name: \u0026quot; + case.name) print(\u0026quot;Case type: \u0026quot; + case.type) print(\u0026quot;Case grid path: \u0026quot; + case.grid_path()) timesteps = case.time_steps() for t in timesteps: print(\u0026quot;Year: \u0026quot; + str(t.year)) print(\u0026quot;Month: \u0026quot; + str(t.month))  Contour Map Module class rips.contour_map.ContourMap(pdm_object, project, map_type) ResInsight contour map class\nview_id() View Id corresponding to the View Id in ResInsight project.\n Type\nint\n  export_to_text(export_file_name=\u0026ldquo;, export_local_coordinates=False, undefined_value_label=\u0026lsquo;NaN\u0026rsquo;, exclude_undefined_values=False) Export snapshot for the current view\n Parameters\n export_file_name (str) \u0026ndash; The file location to store results in.\n export_local_coordinates (bool) \u0026ndash; Should we export local coordinates, or UTM.\n undefined_value_label (str) \u0026ndash; Replace undefined values with this label.\n exclude_undefined_values (bool) \u0026ndash; Skip undefined values.\n   Grid Module class rips.grid.Grid(index, case, channel) Grid Information. Not meant to be constructed separately\nCreate Grid objects using mathods on Case: Grid() and Grids()\ndimensions() The dimensions in i, j, k direction\n Returns\nclass with integer attributes i, j, k giving extent in all three dimensions.\n Return type\nVec3i\n  Example  case = rips_instance.project.loadCase(path=casePath) print (case.gridCount()) if case.gridCount() \u0026gt; 0: grid = case.grid(index=0) dimensions = grid.dimensions() print(dimensions.i) print(dimensions.j) print(dimensions.k)  GridCaseGroup Module class rips.gridcasegroup.GridCaseGroup(pdm_object) ResInsight Grid Case Group class\nOperate on a ResInsight case group specified by a Case Group Id integer.\ngroup_id() Grid Case Group Id corresponding to case group Id in ResInsight project.\n Type\nint\n  compute_statistics(case_ids=None) Compute statistics for the given case ids\n Parameters\n case_ids (list of integers) \u0026ndash; list of case ids.\n this is None all cases in group are included (If) \u0026ndash;\n   create_statistics_case() Create a Statistics case in the Grid Case Group\n Returns\nA new Case\n  statistics_cases() Get a list of all statistics cases in the Grid Case Group\nview(view_id) Get a particular view belonging to a case group by providing view id :param id: view id :type id: int\nReturns: a view object\nviews() Get a list of views belonging to a grid case group\nProject Module class rips.project.Project(channel) ResInsight project. Not intended to be created separately.\n Type  case(case_id) Get a specific case from the provided case Id\ncompute_statistics(case_ids=None) Compute statistics for the given case ids\n Parameters\n case_ids (list of integers) \u0026ndash; list of case ids.\n this is None all cases in group are included (If) \u0026ndash;\n   create_statistics_case() Create a Statistics case in the Grid Case Group\n Returns\nA new Case\n  statistics_cases() Get a list of all statistics cases in the Grid Case Group\ncontour_maps(map_type=) Get a list of all contour maps belonging to a project\nReturns: a view object\ncreate_grid_case_group(case_paths) Create a Grid Case Group from a list of cases\n Parameters\ncase_paths (list) \u0026ndash; list of file path strings\n Returns\nA case group id and name\n  export_multi_case_snapshots(grid_list_file) Export snapshots for a set of cases\n Parameters\ngrid_list_file (str) \u0026ndash; Path to a file containing a list of grids to export snapshot for\n  export_snapshots(snapshot_type=\u0026lsquo;ALL\u0026rsquo;, prefix=\u0026ldquo;) Export all snapshots of a given type\n Parameters\n snapshot_type (str) \u0026ndash; Enum string (\u0026lsquo;ALL\u0026rsquo;, \u0026lsquo;VIEWS\u0026rsquo; or \u0026lsquo;PLOTS\u0026rsquo;)\n prefix (str) \u0026ndash; Exported file name prefix\n   export_well_paths(well_paths=None, md_step_size=5.0) Export a set of well paths\n Parameters\n well_paths (list) \u0026ndash; List of strings of well paths. If none, export all.\n md_step_size (double) \u0026ndash; resolution of the exported well path\n   grid_case_group(group_id) Get a particular grid case group belonging to a project\n Parameters\ngroupId (int) \u0026ndash; group id\n  create_grid_case_group(case_paths) Create a Grid Case Group from a list of cases\nReturns: a grid case group object\ngrid_case_groups() Get a list of all grid case groups in the project\nimport_formation_names(formation_files=None) Import formation names into project\n Parameters\nformation_files (list) \u0026ndash; list of files to import\n  export_multi_case_snapshots(grid_list_file) Export snapshots for a set of cases\nimport_well_log_files(well_log_files=None, well_log_folder=\u0026ldquo;) Import well log files into project\n Parameters\n well_log_files (list) \u0026ndash; List of file paths to import\n well_log_folder (str) \u0026ndash; A folder path containing files to import\n  Returns\nA list of well path names (strings) that had logs imported\n  import_well_paths(well_path_files=None, well_path_folder=\u0026ldquo;) Import well paths into project\n Parameters\n well_path_files (list) \u0026ndash; List of file paths to import\n well_path_folder (str) \u0026ndash; A folder path containing files to import\n  Returns\nA list of well path names (strings)\n  Returns: a grid case group object\nload_case(path) Load a new case from the given file path\ngrid_case_groups() Get a list of all grid case groups in the project\n**path** (*str*) -- file path to case   Parameters\n Returns\nA rips Case object\n  open(path) Open a new project from the given path\n Parameters\npath (str) \u0026ndash; path to project file\n Parameters\n  plot(view_id) Get a particular plot by providing view id :param view_id: view id :type view_id: int\nReturns: a plot object\nplots() Get a list of all plots belonging to a project\nreplace_source_cases(grid_list_file, case_group_id=0) Replace all source cases within a case group\n Parameters\n grid_list_file (str) \u0026ndash; path to file containing a list of cases\n case_group_id (int) \u0026ndash; id of the case group to replace\n   save(path=\u0026ldquo;) Save the project to the existing project file, or to a new file :param path: File path to the file to save the project to. If empty, saves to the active project file :type path: str\nscale_fracture_template(template_id, half_length, height, d_factor, conductivity) Scale fracture template parameters\n Parameters\n template_id (int) \u0026ndash; ID of fracture template\n half_length (double) \u0026ndash; Half Length scale factor\n height (double) \u0026ndash; Height scale factor\n d_factor (double) \u0026ndash; D-factor scale factor\n conductivity (double) \u0026ndash; Conductivity scale factor\n   selected_cases() Get a list of all cases selected in the project tree\n Returns\nA list of rips Case objects\n  set_fracture_containment(template_id, top_layer, base_layer) Set fracture template containment parameters\nset_fracture_containment(template_id, top_layer, base_layer) Set fracture template containment parameters\n Parameters\n template_id (int) \u0026ndash; ID of fracture template\n top_layer (int) \u0026ndash; Top layer containment\n base_layer (int) \u0026ndash; Base layer containment\n   view(view_id) Get a particular view belonging to a case by providing view id\n Parameters\nview_id (int) \u0026ndash; view id\n  Returns: a view object\nviews() Get a list of views belonging to a project\nwell_paths() Get a list of all the well path names in the project\nView Module class rips.view.View(pdm_object, project) ResInsight view class\nview_id() View Id corresponding to the View Id in ResInsight project.\n Type\nint\n  apply_cell_result(result_type, result_variable) Apply a regular cell result\n Parameters\n result_type (str) \u0026ndash; String representing the result category. The valid values are\n DYNAMIC_NATIVE STATIC_NATIVE SOURSIMRL GENERATED INPUT_PROPERTY FORMATION_NAMES FLOW_DIAGNOSTICS INJECTION_FLOODING  result_variable (str) \u0026ndash; String representing the result variable.\n   apply_flow_diagnostics_cell_result(result_variable=\u0026lsquo;TOF\u0026rsquo;, selection_mode=\u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;, injectors=None, producers=None) Apply a flow diagnostics cell result\n   Parameter Description Type     result_variable String representing the result value String   selection_mode String specifying which tracers to select String   injectors List of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo; String List   producers List of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo; String List    Enum compdat_export    Option Description     \u0026ldquo;TOF\u0026rdquo; Time of flight   \u0026ldquo;Fraction\u0026rdquo; Fraction   \u0026ldquo;MaxFractionTracer\u0026rdquo; Max Fraction Tracer   \u0026ldquo;Communication\u0026rdquo; Communication    background_color() Get the current background color in the view\ncase() Get the case the view belongs to\nclone() Clone the current view\nexport_property(undefined_value=0.0) Export the current Eclipse property from the view\n Parameters\nundefined_value (double) \u0026ndash; Value to use for undefined values. Defaults to 0.0\n  export_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export) Export fracture completions for simulation wells\n   Parameter Description Type     time_step Time step to export for Integer   simulation_well_names List of simulation well names List   file_split Controls how export data is split into files String enum   compdat_export Compdat export type String enum    Enum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; Default Option A single file with all transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    Enum compdat_export    Option Description     \u0026ldquo;TRANSMISSIBILITIES\u0026rdquo;Default Option Direct export of transmissibilities   \u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo; Include export of WPIMULT    export_snapshot(prefix=\u0026ldquo;, export_folder=\u0026ldquo;) Export snapshot for the current view\n Parameters\n prefix (str) \u0026ndash; Exported file name prefix\n export_folder (str) \u0026ndash; The path to export to. By default will use the global export folder\n   export_visible_cells(export_keyword=\u0026lsquo;FLUXNUM\u0026rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0) Export special properties for all visible cells.\n Parameters\n export_keyword (string) \u0026ndash; The keyword to export.\n Choices \u0026ndash; \u0026lsquo;FLUXNUM\u0026rsquo; or \u0026lsquo;MULTNUM\u0026rsquo;. Default: \u0026lsquo;FLUXNUM\u0026rsquo;\n visible_active_cells_value (int) \u0026ndash; Value to export forvisible active cells. Default: 1\n hidden_active_cells_value (int) \u0026ndash; Value to export for hidden active cells. Default: 0\n inactive_cells_value (int) \u0026ndash; Value to export for inactive cells. Default: 0\n   set_background_color(bgcolor) Set the background color in the view\nset_cell_result() Retrieve the current cell results\nset_show_grid_box(value) Set if the grid box is meant to be shown in the view\nset_time_step(time_step) Set the time step for current view\nshow_grid_box() Check if the grid box is meant to be shown in the view\nSynchronous Example Read two properties, multiply them together and push the results back to ResInsight in a naïve way, by reading PORO into a list, then reading PERMX into a list, then multiplying them both in a resulting list and finally transferring back the list.\nThis is slow and inefficient, but works.\nimport rips import time # Internal function for creating a result from a small chunk of poro and permx results # The return value of the function is a generator for the results rather than the result itself. def create_result(poro_chunks, permx_chunks): # Loop through all the chunks of poro and permx in order for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks): resultChunk = [] # Loop through all the values inside the chunks, in order for (poro, permx) in zip(poroChunk.values, permxChunk.values): resultChunk.append(poro * permx) # Return a generator object that behaves like a Python iterator yield resultChunk resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] # Get a generator for the poro results. The generator will provide a chunk each time it is iterated poro_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0) # Get a generator for the permx results. The generator will provide a chunk each time it is iterated permx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0) # Send back the result with the result provided by a generator object. # Iterating the result generator will cause the script to read from the poro and permx generators # And return the result of each iteration case.set_active_cell_property_async(create_result(poro_chunks, permx_chunks), 'GENERATED', 'POROPERMXAS', 0) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')  Asynchronous Example Read two properties at the same time chunk by chunk, multiply each chunk together and start transferring the result back to ResInsight as soon as the chunk is finished.\nThis is far more efficient.\n######################################################################################## import rips import time import grpc resinsight = rips.Instance.find() start = time.time() case = resinsight.project.cases()[0] # Read poro result into list poro_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0) # Read permx result into list permx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0) # Generate output result results = [] for (poro, permx) in zip(poro_results, permx_results): results.append(poro * permx) try: # Send back output result case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0) except grpc.RpcError as e: print(\u0026quot;Exception Received: \u0026quot;, e) end = time.time() print(\u0026quot;Time elapsed: \u0026quot;, end - start) print(\u0026quot;Transferred all results back\u0026quot;) view = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch1 id=\"instance-module\"\u003eInstance Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-instance-instance-port-50051-launched-false\"\u003eclass rips.instance.Instance(port=50051, launched=False)\u003c/h4\u003e\n\n\u003cp\u003eThe ResInsight Instance class. Use to launch or find existing ResInsight instances\u003c/p\u003e\n\n\u003ch4 id=\"launched\"\u003elaunched()\u003c/h4\u003e\n\n\u003cp\u003eTells us whether the application was launched as a new process.\nIf the application was launched we may need to close it when exiting the script.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003ebool\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"commands\"\u003ecommands()\u003c/h4\u003e\n\n\u003cp\u003eCommand executor. Set when creating an instance.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eCommands\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"project\"\u003eproject()\u003c/h4\u003e\n\n\u003cp\u003eCurrent project in ResInsight.\nSet when creating an instance and updated when opening/closing projects.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eProject\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"client-version-string\"\u003eclient_version_string()\u003c/h4\u003e\n\n\u003cp\u003eGet a full version string, i.e. 2019.04.01\u003c/p\u003e\n\n\u003ch4 id=\"exit\"\u003eexit()\u003c/h4\u003e\n\n\u003cp\u003eTell ResInsight instance to quit\u003c/p\u003e\n\n\u003ch4 id=\"static-find-start-port-50051-end-port-50071\"\u003estatic find(start_port=50051, end_port=50071)\u003c/h4\u003e\n\n\u003cp\u003eSearch for an existing Instance of ResInsight by testing ports.\u003c/p\u003e\n\n\u003cp\u003eBy default we search from port 50051 to 50071 or if the environment\nvariable RESINSIGHT_GRPC_PORT is set we search\nRESINSIGHT_GRPC_PORT to RESINSIGHT_GRPC_PORT+20\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003estart_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; start searching from this port\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eend_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; search up to but not including this port\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"is-console\"\u003eis_console()\u003c/h4\u003e\n\n\u003cp\u003eReturns true if the connected ResInsight instance is a console app\u003c/p\u003e\n\n\u003ch4 id=\"is-gui\"\u003eis_gui()\u003c/h4\u003e\n\n\u003cp\u003eReturns true if the connected ResInsight instance is a GUI app\u003c/p\u003e\n\n\u003ch4 id=\"static-launch-resinsight-executable-console-false-launch-port-1-command-line-parameters-none\"\u003estatic launch(resinsight_executable=\u0026ldquo;, console=False, launch_port=-1, command_line_parameters=None)\u003c/h4\u003e\n\n\u003cp\u003eLaunch a new Instance of ResInsight. This requires the environment variable\nRESINSIGHT_EXECUTABLE to be set or the parameter resinsight_executable to be provided.\nThe RESINSIGHT_GRPC_PORT environment variable can be set to an alternative port number.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eresinsight_executable\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Path to a valid ResInsight executable. If set\nwill take precedence over what is provided in the RESINSIGHT_EXECUTABLE\nenvironment variable.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003econsole\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; If True, launch as console application, without GUI.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003elaunch_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT\nif anything else, ResInsight will try to launch with this port\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ecommand_line_parameters\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; Additional parameters as string entries in the list.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003ean instance object if it worked. None if not.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eInstance\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"major-version\"\u003emajor_version()\u003c/h4\u003e\n\n\u003cp\u003eGet an integer with the major version number\u003c/p\u003e\n\n\u003ch4 id=\"minor-version\"\u003eminor_version()\u003c/h4\u003e\n\n\u003cp\u003eGet an integer with the minor version number\u003c/p\u003e\n\n\u003ch4 id=\"patch-version\"\u003epatch_version()\u003c/h4\u003e\n\n\u003cp\u003eGet an integer with the patch version number\u003c/p\u003e\n\n\u003ch4 id=\"set-export-folder-export-type-path-create-folder-false\"\u003eset_export_folder(export_type, path, create_folder=False)\u003c/h4\u003e\n\n\u003cp\u003eSet the export folder used for all export functions\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eexport_type\u003c/td\u003e\n\u003ctd\u003eString specifying what to export\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to folder\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecreate_folder\u003c/td\u003e\n\u003ctd\u003eCreate folder if it doesn\u0026rsquo;t exist?\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-export-type\"\u003eEnum export_type\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;COMPLETIONS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SNAPSHOTS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;PROPERTIES\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;STATISTICS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"set-main-window-size-width-height\"\u003eset_main_window_size(width, height)\u003c/h4\u003e\n\n\u003cp\u003eSet the main window size in pixels\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eWidth in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"set-plot-window-size-width-height\"\u003eset_plot_window_size(width, height)\u003c/h4\u003e\n\n\u003cp\u003eSet the plot window size in pixels\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eWidth in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"set-start-dir-path\"\u003eset_start_dir(path)\u003c/h4\u003e\n\n\u003cp\u003eSet current start directory\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003epath\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to directory\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"version-string\"\u003eversion_string()\u003c/h4\u003e\n\n\u003cp\u003eGet a full version string, i.e. 2019.04.01\u003c/p\u003e\n\n\u003ch2 id=\"example\"\u003eExample\u003c/h2\u003e\n\n\u003cpre\u003e\u003ccode\u003e\nresinsight  = rips.Instance.find()\n\nif resinsight is None:\n    print('ERROR: could not find ResInsight')\nelse:\n    print('Successfully connected to ResInsight')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"case-module\"\u003eCase Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-case-case-channel-case-id-project\"\u003eclass rips.case.Case(channel, case_id, project)\u003c/h4\u003e\n\n\u003cp\u003eResInsight case class\u003c/p\u003e\n\n\u003cp\u003eOperate on a ResInsight case specified by a Case Id integer.\nNot meant to be constructed separately but created by one of the following\nmethods in Project: loadCase, case, allCases, selectedCasesq\u003c/p\u003e\n\n\u003ch4 id=\"id\"\u003eid()\u003c/h4\u003e\n\n\u003cp\u003eCase Id corresponding to case Id in ResInsight project.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"name\"\u003ename()\u003c/h4\u003e\n\n\u003cp\u003eCase name\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003estr\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"group-id\"\u003egroup_id()\u003c/h4\u003e\n\n\u003cp\u003eCase Group id\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"chunksize\"\u003echunkSize()\u003c/h4\u003e\n\n\u003cp\u003eThe size of each chunk during value streaming.\nA good chunk size is 64KiB = 65536B.\nMeaning the ideal number of doubles would be 8192.\nHowever we need overhead space, so the default is 8160.\nThis leaves 256B for overhead.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"active-cell-property-property-type-property-name-time-step-porosity-model-matrix-model\"\u003eactive_cell_property(property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a cell property for all active cells. Sync, so returns a list\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA list containing double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"active-cell-property-async-property-type-property-name-time-step-porosity-model-matrix-model\"\u003eactive_cell_property_async(property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a cell property for all active cells. Async, so returns an iterator\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eAn iterator to a chunk object containing an array of double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"available-properties-property-type-porosity-model-matrix-model\"\u003eavailable_properties(property_type, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a list of available properties\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string corresponding to property_type enum. Choices:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDYNAMIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSTATIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSOURSIMRL\u003c/li\u003e\n\u003cli\u003eGENERATED\u003c/li\u003e\n\u003cli\u003eINPUT_PROPERTY\u003c/li\u003e\n\u003cli\u003eFORMATION_NAMES\u003c/li\u003e\n\u003cli\u003eFLOW_DIAGNOSTICS\u003c/li\u003e\n\u003cli\u003eINJECTION_FLOODING\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"cell-count-porosity-model-matrix-model\"\u003ecell_count(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a cell count object containing number of active cells and\ntotal number of cells\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eactive_cell_count: number of active cells\nreservoir_cell_count: total number of reservoir cells\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eCell Count object with the following integer attributes\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"cell-info-for-active-cells-porosity-model-matrix-model\"\u003ecell_info_for_active_cells(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet list of cell info objects for current case\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eList of \u003cstrong\u003eCellInfo\u003c/strong\u003e objects\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"cellinfo-class-description\"\u003eCellInfo class description\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egrid_index\u003c/td\u003e\n\u003ctd\u003eIndex to grid\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eparent_grid_index\u003c/td\u003e\n\u003ctd\u003eIndex to parent grid\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecoarsening_box_index\u003c/td\u003e\n\u003ctd\u003eIndex to coarsening box\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003elocal_ijk\u003c/td\u003e\n\u003ctd\u003eCell index in IJK directions of local grid\u003c/td\u003e\n\u003ctd\u003eVec3i\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eparent_ijk\u003c/td\u003e\n\u003ctd\u003eCell index in IJK directions of parent grid\u003c/td\u003e\n\u003ctd\u003eVec3i\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"vec3i-class-description\"\u003eVec3i class description\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ei\u003c/td\u003e\n\u003ctd\u003eI grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ej\u003c/td\u003e\n\u003ctd\u003eJ grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ek\u003c/td\u003e\n\u003ctd\u003eK grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"cell-info-for-active-cells-async-porosity-model-matrix-model\"\u003ecell_info_for_active_cells_async(porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet Stream of cell info objects for current case\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eStream of \u003cstrong\u003eCellInfo\u003c/strong\u003e objects\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSee cell_info_for_active_cells() for detalis on the \u003cstrong\u003eCellInfo\u003c/strong\u003e class.\u003c/p\u003e\n\n\u003ch4 id=\"contour-maps-map-type-contourmaptype-eclipse-1\"\u003econtour_maps(map_type=\u003cContourMapType.ECLIPSE: 1\u003e)\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all contour maps belonging to a project\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_i\u003c/td\u003e\n\u003ctd\u003eRefinment in x-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_j\u003c/td\u003e\n\u003ctd\u003eRefinment in y-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_k\u003c/td\u003e\n\u003ctd\u003eRefinment in z-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esplit_type\u003c/td\u003e\n\u003ctd\u003eDefines how to split LGRS\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003emap_type\u003c/strong\u003e (\u003cem\u003eenum\u003c/em\u003e) \u0026ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action\"\u003ecreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)\u003c/h4\u003e\n\n\u003cp\u003eCreate Multiple Fractures in one go\u003c/p\u003e\n\n\u003ch4 id=\"create-lgr-for-completion-time-step-well-path-names-refinement-i-refinement-j-refinement-k-split-type\"\u003ecreate_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type)\u003c/h4\u003e\n\n\u003cp\u003eCreate a local grid refinement for the completions on the given well paths\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_i\u003c/td\u003e\n\u003ctd\u003eRefinment in x-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_j\u003c/td\u003e\n\u003ctd\u003eRefinment in y-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erefinement_k\u003c/td\u003e\n\u003ctd\u003eRefinment in z-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esplit_type\u003c/td\u003e\n\u003ctd\u003eDefines how to split LGRS\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-split-type\"\u003eEnum split_type\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_CELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each completed cell\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_COMPLETION\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each completion (fracture, perforation, \u0026hellip;)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"create-view\"\u003ecreate_view()\u003c/h4\u003e\n\n\u003cp\u003eCreate a new view in the current case\u003c/p\u003e\n\n\u003ch4 id=\"create-multiple-fractures-template-id-well-path-names-min-dist-from-well-td-max-fractures-per-well-top-layer-base-layer-spacing-action-1\"\u003ecreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)\u003c/h4\u003e\n\n\u003cp\u003eCreate Multiple Fractures in one go\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etemplate_id\u003c/td\u003e\n\u003ctd\u003eId of the template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emin_dist_from_well_td\u003c/td\u003e\n\u003ctd\u003eMinimum distance from well TD\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emax_fractures_per_well\u003c/td\u003e\n\u003ctd\u003eMax number of fractures per well\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etop_layer\u003c/td\u003e\n\u003ctd\u003eTop grid k-level for fractures\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ebase_layer\u003c/td\u003e\n\u003ctd\u003eBase grid k-level for fractures\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003espacing\u003c/td\u003e\n\u003ctd\u003eSpacing between fractures\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eaction\u003c/td\u003e\n\u003ctd\u003e\u0026lsquo;APPEND_FRACTURES\u0026rsquo; or \u0026lsquo;REPLACE_FRACTURES\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"create-saturation-pressure-plots\"\u003ecreate_saturation_pressure_plots()\u003c/h4\u003e\n\n\u003cp\u003eCreate saturation pressure plots for the current case\u003c/p\u003e\n\n\u003ch4 id=\"create-view-1\"\u003ecreate_view()\u003c/h4\u003e\n\n\u003cp\u003eCreate a new view in the current case\u003c/p\u003e\n\n\u003ch4 id=\"create-well-bore-stability-plot-well-path-time-step\"\u003ecreate_well_bore_stability_plot(well_path, time_step)\u003c/h4\u003e\n\n\u003cp\u003eCreate a new well bore stability plot\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_path\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; well path name\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; time step\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA new plot object\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"days-since-start\"\u003edays_since_start()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of decimal values representing days since the start of the simulation\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"export-flow-characteristics-time-steps-injectors-producers-file-name-minimum-communication-0-0-aquifer-cell-threshold-0-1\"\u003eexport_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1)\u003c/h4\u003e\n\n\u003cp\u003eExport Flow Characteristics data to text file in CSV format\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step indices\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eInjector names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eProducer names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efile_name\u003c/td\u003e\n\u003ctd\u003eExport file name\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eminimum_communication\u003c/td\u003e\n\u003ctd\u003eMinimum Communication, defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eaquifer_cell_threshold\u003c/td\u003e\n\u003ctd\u003eAquifer Cell Threshold, defaults to 0.1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"export-msw-well-path\"\u003eexport_msw(well_path)\u003c/h4\u003e\n\n\u003cp\u003eExport Eclipse Multi-segment-well model to file\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003ewell_path\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Well path name\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-property-time-step-property-name-eclipse-keyword-class-property-undefined-value-0-0-export-file-class-property\"\u003eexport_property(time_step, property_name, eclipse_keyword=\u003cclass 'property'\u003e, undefined_value=0.0, export_file=\u003cclass 'property'\u003e)\u003c/h4\u003e\n\n\u003cp\u003eExport an Eclipse property\u003c/p\u003e\n\n\u003ch5 id=\"enum-file-split\"\u003eEnum file_split\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eA single file with all combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well with combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cpre\u003e\u003ccode\u003e* **time_step** (*int*) -- time step index\n\n* **property_name** (*str*) -- property to export\n\n* **eclipse_keyword** (*str*) -- Keyword used in export header. Defaults: value of property\n\n* **undefined_value** (*double*) -- Value to use for undefined values. Defaults to 0.0\n\n* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"grid-index\"\u003egrid(index)\u003c/h4\u003e\n\n\u003cp\u003eGet Grid of a given index. Returns a rips Grid object\u003c/p\u003e\n\n\u003ch4 id=\"export-snapshots-of-all-views-prefix-export-folder\"\u003eexport_snapshots_of_all_views(prefix=\u0026ldquo;, export_folder=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eExport snapshots for all views in the case\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexport_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The path to export to. By default will use the global export folder\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-well-path-completions-time-step-well-path-names-file-split-compdat-export-transmissibilities-include-perforations-true-include-fishbones-true-fishbones-exclude-main-bore-true-combination-mode-individually\"\u003eexport_well_path_completions(time_step, well_path_names, file_split, compdat_export=\u0026lsquo;TRANSMISSIBILITIES\u0026rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode=\u0026lsquo;INDIVIDUALLY\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eExport well path completions for the current case to file\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_step\u003c/td\u003e\n\u003ctd\u003eTime step to export for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efile_split\u003c/td\u003e\n\u003ctd\u003eControls how export data is split into files\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecompdat_export\u003c/td\u003e\n\u003ctd\u003eCompdat export type\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einclude_perforations\u003c/td\u003e\n\u003ctd\u003eExport perforations?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einclude_fishbones\u003c/td\u003e\n\u003ctd\u003eExport fishbones?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efishbones_exclude_main_bore\u003c/td\u003e\n\u003ctd\u003eExclude main bore when exporting fishbones?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecombination_mode\u003c/td\u003e\n\u003ctd\u003eSettings for multiple completions in same cell\u003c/td\u003e\n\u003ctd\u003eString Enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-file-split-1\"\u003eEnum file_split\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eA single file with all combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well with combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-compdat-export\"\u003eEnum compdat_export\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TRANSMISSIBILITIES\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eDirect export of transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eInclude WPIMULT in addition to transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-combination-mode\"\u003eEnum combination_mode\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;INDIVIDUALLY\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eExports the different completion types into separate sections\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;COMBINED\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eExport one combined transmissibility for each cell\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"grid-index-1\"\u003egrid(index)\u003c/h4\u003e\n\n\u003cp\u003eGet Grid of a given index. Returns a rips Grid object\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eindex\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; The grid index\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eReturns: Grid object\u003c/p\u003e\n\n\u003ch4 id=\"grid-path\"\u003egrid_path()\u003c/h4\u003e\n\n\u003cp\u003eGet path of the current grid case\u003c/p\u003e\n\n\u003cp\u003eReturns: path string\u003c/p\u003e\n\n\u003ch4 id=\"grid-property-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model\"\u003egrid_property(property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a cell property for all grid cells. Synchronous, so returns a list\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003egrid_index\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA list of double values\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"grid-property-async-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model\"\u003egrid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eGet a cell property for all grid cells. Async, so returns an iterator\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003egridIndex\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eAn iterator to a chunk object containing an array of double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"grids\"\u003egrids()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all rips Grid objects in the case\u003c/p\u003e\n\n\u003ch4 id=\"import-formation-names-formation-files-none\"\u003eimport_formation_names(formation_files=None)\u003c/h4\u003e\n\n\u003cp\u003eImport formation names into project and apply it to the current case\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eformation_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of files to import\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"replace-new-grid-file\"\u003ereplace(new_grid_file)\u003c/h4\u003e\n\n\u003cp\u003eReplace the current case grid with a new grid loaded from file\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003enew_egrid_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to EGRID file\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"set-active-cell-property-values-property-type-property-name-time-step-porosity-model-matrix-model\"\u003eset_active_cell_property(values, property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eSet a cell property for all active cells.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003evalues\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; a list of double precision floating point numbers\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"set-active-cell-property-async-values-iterator-property-type-property-name-time-step-porosity-model-matrix-model\"\u003eset_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eSet cell property for all active cells Async. Takes an iterator to the input values\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003evalues_iterator\u003c/strong\u003e (\u003cem\u003eiterator\u003c/em\u003e) \u0026ndash; an iterator to the properties to be set\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"set-grid-property-values-property-type-property-name-time-step-grid-index-0-porosity-model-matrix-model\"\u003eset_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model=\u0026lsquo;MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\n\u003cp\u003eSet a cell property for all grid cells.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003evalues\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; a list of double precision floating point numbers\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003egrid_index\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re setting values for\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"time-steps\"\u003etime_steps()\u003c/h4\u003e\n\n\u003cp\u003eGet a list containing all time steps\u003c/p\u003e\n\n\u003cp\u003eThe time steps are defined by the class \u003cstrong\u003eTimeStepDate\u003c/strong\u003e :\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eyear\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003emonth\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eday\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003ehour\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eminute\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003esecond\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"view-view-id\"\u003eview(view_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a particular view belonging to a case by providing view id\n:param view_id: view id\n:type view_id: int\u003c/p\u003e\n\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\n\u003ch4 id=\"views\"\u003eviews()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of views belonging to a case\u003c/p\u003e\n\n\u003ch2 id=\"example-1\"\u003eExample\u003c/h2\u003e\n\n\u003cpre\u003e\u003ccode\u003e\n# Import the ResInsight Processing Server Module\nimport rips\n\n# Connect to ResInsight\nresinsight  = rips.Instance.find()\nif resinsight is not None:\n    # Get a list of all cases\n    cases = resinsight.project.cases()\n\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\n    for case in cases:\n        print(\u0026quot;Case id: \u0026quot; + str(case.case_id))\n        print(\u0026quot;Case name: \u0026quot; + case.name)\n        print(\u0026quot;Case type: \u0026quot; + case.type)\n        print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\n        \n        timesteps = case.time_steps()\n        for t in timesteps:\n            print(\u0026quot;Year: \u0026quot; + str(t.year))\n            print(\u0026quot;Month: \u0026quot; + str(t.month))\n        \n    \n\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"contour-map-module\"\u003eContour Map Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-contour-map-contourmap-pdm-object-project-map-type\"\u003eclass rips.contour_map.ContourMap(pdm_object, project, map_type)\u003c/h4\u003e\n\n\u003cp\u003eResInsight contour map class\u003c/p\u003e\n\n\u003ch4 id=\"view-id\"\u003eview_id()\u003c/h4\u003e\n\n\u003cp\u003eView Id corresponding to the View Id in ResInsight project.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-to-text-export-file-name-export-local-coordinates-false-undefined-value-label-nan-exclude-undefined-values-false\"\u003eexport_to_text(export_file_name=\u0026ldquo;, export_local_coordinates=False, undefined_value_label=\u0026lsquo;NaN\u0026rsquo;, exclude_undefined_values=False)\u003c/h4\u003e\n\n\u003cp\u003eExport snapshot for the current view\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexport_file_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The file location to store results in.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexport_local_coordinates\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; Should we export local coordinates, or UTM.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eundefined_value_label\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Replace undefined values with this label.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexclude_undefined_values\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; Skip undefined values.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch1 id=\"grid-module\"\u003eGrid Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-grid-grid-index-case-channel\"\u003eclass rips.grid.Grid(index, case, channel)\u003c/h4\u003e\n\n\u003cp\u003eGrid Information. Not meant to be constructed separately\u003c/p\u003e\n\n\u003cp\u003eCreate Grid objects using mathods on Case: Grid() and Grids()\u003c/p\u003e\n\n\u003ch4 id=\"dimensions\"\u003edimensions()\u003c/h4\u003e\n\n\u003cp\u003eThe dimensions in i, j, k direction\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eclass with integer attributes i, j, k giving extent in all three dimensions.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eVec3i\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"example-2\"\u003eExample\u003c/h2\u003e\n\n\u003cpre\u003e\u003ccode\u003e    case = rips_instance.project.loadCase(path=casePath)\nprint (case.gridCount())\n    if case.gridCount() \u0026gt; 0:\n            grid = case.grid(index=0)\n            dimensions = grid.dimensions()\n            print(dimensions.i)\n            print(dimensions.j)\n            print(dimensions.k)\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch1 id=\"gridcasegroup-module\"\u003eGridCaseGroup Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-gridcasegroup-gridcasegroup-pdm-object\"\u003eclass rips.gridcasegroup.GridCaseGroup(pdm_object)\u003c/h4\u003e\n\n\u003cp\u003eResInsight Grid Case Group class\u003c/p\u003e\n\n\u003cp\u003eOperate on a ResInsight case group specified by a Case Group Id integer.\u003c/p\u003e\n\n\u003ch4 id=\"group-id-1\"\u003egroup_id()\u003c/h4\u003e\n\n\u003cp\u003eGrid Case Group Id corresponding to case group Id in ResInsight project.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"compute-statistics-case-ids-none\"\u003ecompute_statistics(case_ids=None)\u003c/h4\u003e\n\n\u003cp\u003eCompute statistics for the given case ids\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ecase_ids\u003c/strong\u003e (\u003cem\u003elist of integers\u003c/em\u003e) \u0026ndash; list of case ids.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ethis is None all cases in group are included\u003c/strong\u003e (\u003cem\u003eIf\u003c/em\u003e) \u0026ndash;\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"create-statistics-case\"\u003ecreate_statistics_case()\u003c/h4\u003e\n\n\u003cp\u003eCreate a Statistics case in the Grid Case Group\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA new Case\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"statistics-cases\"\u003estatistics_cases()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all statistics cases in the Grid Case Group\u003c/p\u003e\n\n\u003ch4 id=\"view-view-id-1\"\u003eview(view_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a particular view belonging to a case group by providing view id\n:param id: view id\n:type id: int\u003c/p\u003e\n\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\n\u003ch4 id=\"views-1\"\u003eviews()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of views belonging to a grid case group\u003c/p\u003e\n\n\u003ch1 id=\"project-module\"\u003eProject Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-project-project-channel\"\u003eclass rips.project.Project(channel)\u003c/h4\u003e\n\n\u003cp\u003eResInsight project. Not intended to be created separately.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"case-case-id\"\u003ecase(case_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a specific case from the provided case Id\u003c/p\u003e\n\n\u003ch4 id=\"compute-statistics-case-ids-none-1\"\u003ecompute_statistics(case_ids=None)\u003c/h4\u003e\n\n\u003cp\u003eCompute statistics for the given case ids\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ecase_ids\u003c/strong\u003e (\u003cem\u003elist of integers\u003c/em\u003e) \u0026ndash; list of case ids.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ethis is None all cases in group are included\u003c/strong\u003e (\u003cem\u003eIf\u003c/em\u003e) \u0026ndash;\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"create-statistics-case-1\"\u003ecreate_statistics_case()\u003c/h4\u003e\n\n\u003cp\u003eCreate a Statistics case in the Grid Case Group\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA new Case\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"statistics-cases-1\"\u003estatistics_cases()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all statistics cases in the Grid Case Group\u003c/p\u003e\n\n\u003ch4 id=\"contour-maps-map-type-contourmaptype-eclipse-1-1\"\u003econtour_maps(map_type=\u003cContourMapType.ECLIPSE: 1\u003e)\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all contour maps belonging to a project\u003c/p\u003e\n\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\n\u003ch4 id=\"create-grid-case-group-case-paths\"\u003ecreate_grid_case_group(case_paths)\u003c/h4\u003e\n\n\u003cp\u003eCreate a Grid Case Group from a list of cases\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003ecase_paths\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of file path strings\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA case group id and name\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-multi-case-snapshots-grid-list-file\"\u003eexport_multi_case_snapshots(grid_list_file)\u003c/h4\u003e\n\n\u003cp\u003eExport snapshots for a set of cases\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003egrid_list_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Path to a file containing a list of grids to export snapshot for\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-snapshots-snapshot-type-all-prefix\"\u003eexport_snapshots(snapshot_type=\u0026lsquo;ALL\u0026rsquo;, prefix=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eExport all snapshots of a given type\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003esnapshot_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Enum string (\u0026lsquo;ALL\u0026rsquo;, \u0026lsquo;VIEWS\u0026rsquo; or \u0026lsquo;PLOTS\u0026rsquo;)\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-well-paths-well-paths-none-md-step-size-5-0\"\u003eexport_well_paths(well_paths=None, md_step_size=5.0)\u003c/h4\u003e\n\n\u003cp\u003eExport a set of well paths\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_paths\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of strings of well paths. If none, export all.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003emd_step_size\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; resolution of the exported well path\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"grid-case-group-group-id\"\u003egrid_case_group(group_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a particular grid case group belonging to a project\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003egroupId\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; group id\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"create-grid-case-group-case-paths-1\"\u003ecreate_grid_case_group(case_paths)\u003c/h4\u003e\n\n\u003cp\u003eCreate a Grid Case Group from a list of cases\u003c/p\u003e\n\n\u003cp\u003eReturns: a grid case group object\u003c/p\u003e\n\n\u003ch4 id=\"grid-case-groups\"\u003egrid_case_groups()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all grid case groups in the project\u003c/p\u003e\n\n\u003ch4 id=\"import-formation-names-formation-files-none-1\"\u003eimport_formation_names(formation_files=None)\u003c/h4\u003e\n\n\u003cp\u003eImport formation names into project\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eformation_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of files to import\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-multi-case-snapshots-grid-list-file-1\"\u003eexport_multi_case_snapshots(grid_list_file)\u003c/h4\u003e\n\n\u003cp\u003eExport snapshots for a set of cases\u003c/p\u003e\n\n\u003ch4 id=\"import-well-log-files-well-log-files-none-well-log-folder\"\u003eimport_well_log_files(well_log_files=None, well_log_folder=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eImport well log files into project\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_log_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of file paths to import\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_log_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; A folder path containing files to import\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA list of well path names (strings) that had logs imported\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"import-well-paths-well-path-files-none-well-path-folder\"\u003eimport_well_paths(well_path_files=None, well_path_folder=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eImport well paths into project\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_path_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of file paths to import\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ewell_path_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; A folder path containing files to import\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA list of well path names (strings)\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eReturns: a grid case group object\u003c/p\u003e\n\n\u003ch4 id=\"load-case-path\"\u003eload_case(path)\u003c/h4\u003e\n\n\u003cp\u003eLoad a new case from the given file path\u003c/p\u003e\n\n\u003ch4 id=\"grid-case-groups-1\"\u003egrid_case_groups()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all grid case groups in the project\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e**path** (*str*) -- file path to case\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA rips Case object\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"open-path\"\u003eopen(path)\u003c/h4\u003e\n\n\u003cp\u003eOpen a new project from the given path\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003epath\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to project file\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"plot-view-id\"\u003eplot(view_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a particular plot by providing view id\n:param view_id: view id\n:type view_id: int\u003c/p\u003e\n\n\u003cp\u003eReturns: a plot object\u003c/p\u003e\n\n\u003ch4 id=\"plots\"\u003eplots()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all plots belonging to a project\u003c/p\u003e\n\n\u003ch4 id=\"replace-source-cases-grid-list-file-case-group-id-0\"\u003ereplace_source_cases(grid_list_file, case_group_id=0)\u003c/h4\u003e\n\n\u003cp\u003eReplace all source cases within a case group\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003egrid_list_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to file containing a list of cases\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ecase_group_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; id of the case group to replace\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"save-path\"\u003esave(path=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eSave the project to the existing project file, or to a new file\n:param path: File path to the file to save the project to. If empty, saves to the active project file\n:type path: str\u003c/p\u003e\n\n\u003ch4 id=\"scale-fracture-template-template-id-half-length-height-d-factor-conductivity\"\u003escale_fracture_template(template_id, half_length, height, d_factor, conductivity)\u003c/h4\u003e\n\n\u003cp\u003eScale fracture template parameters\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etemplate_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; ID of fracture template\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ehalf_length\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Half Length scale factor\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eheight\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Height scale factor\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ed_factor\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; D-factor scale factor\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003econductivity\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Conductivity scale factor\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"selected-cases\"\u003eselected_cases()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all cases selected in the project tree\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eA list of rips Case objects\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"set-fracture-containment-template-id-top-layer-base-layer\"\u003eset_fracture_containment(template_id, top_layer, base_layer)\u003c/h4\u003e\n\n\u003cp\u003eSet fracture template containment parameters\u003c/p\u003e\n\n\u003ch4 id=\"set-fracture-containment-template-id-top-layer-base-layer-1\"\u003eset_fracture_containment(template_id, top_layer, base_layer)\u003c/h4\u003e\n\n\u003cp\u003eSet fracture template containment parameters\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etemplate_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; ID of fracture template\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003etop_layer\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Top layer containment\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ebase_layer\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Base layer containment\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"view-view-id-2\"\u003eview(view_id)\u003c/h4\u003e\n\n\u003cp\u003eGet a particular view belonging to a case by providing view id\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eview_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; view id\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\n\u003ch4 id=\"views-2\"\u003eviews()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of views belonging to a project\u003c/p\u003e\n\n\u003ch4 id=\"well-paths\"\u003ewell_paths()\u003c/h4\u003e\n\n\u003cp\u003eGet a list of all the well path names in the project\u003c/p\u003e\n\n\u003ch1 id=\"view-module\"\u003eView Module\u003c/h1\u003e\n\n\u003ch4 id=\"class-rips-view-view-pdm-object-project\"\u003eclass rips.view.View(pdm_object, project)\u003c/h4\u003e\n\n\u003cp\u003eResInsight view class\u003c/p\u003e\n\n\u003ch4 id=\"view-id-1\"\u003eview_id()\u003c/h4\u003e\n\n\u003cp\u003eView Id corresponding to the View Id in ResInsight project.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eint\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"apply-cell-result-result-type-result-variable\"\u003eapply_cell_result(result_type, result_variable)\u003c/h4\u003e\n\n\u003cp\u003eApply a regular cell result\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eresult_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing the result category. The valid values are\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eDYNAMIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSTATIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSOURSIMRL\u003c/li\u003e\n\u003cli\u003eGENERATED\u003c/li\u003e\n\u003cli\u003eINPUT_PROPERTY\u003c/li\u003e\n\u003cli\u003eFORMATION_NAMES\u003c/li\u003e\n\u003cli\u003eFLOW_DIAGNOSTICS\u003c/li\u003e\n\u003cli\u003eINJECTION_FLOODING\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eresult_variable\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing the result variable.\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"apply-flow-diagnostics-cell-result-result-variable-tof-selection-mode-flow-tr-by-selection-injectors-none-producers-none\"\u003eapply_flow_diagnostics_cell_result(result_variable=\u0026lsquo;TOF\u0026rsquo;, selection_mode=\u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;, injectors=None, producers=None)\u003c/h4\u003e\n\n\u003cp\u003eApply a flow diagnostics cell result\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eresult_variable\u003c/td\u003e\n\u003ctd\u003eString representing the result value\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eselection_mode\u003c/td\u003e\n\u003ctd\u003eString specifying which tracers to select\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eList of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString List\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eList of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString List\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-compdat-export-1\"\u003eEnum compdat_export\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TOF\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eTime of flight\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;Fraction\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eFraction\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;MaxFractionTracer\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eMax Fraction Tracer\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;Communication\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eCommunication\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"background-color\"\u003ebackground_color()\u003c/h4\u003e\n\n\u003cp\u003eGet the current background color in the view\u003c/p\u003e\n\n\u003ch4 id=\"case\"\u003ecase()\u003c/h4\u003e\n\n\u003cp\u003eGet the case the view belongs to\u003c/p\u003e\n\n\u003ch4 id=\"clone\"\u003eclone()\u003c/h4\u003e\n\n\u003cp\u003eClone the current view\u003c/p\u003e\n\n\u003ch4 id=\"export-property-undefined-value-0-0\"\u003eexport_property(undefined_value=0.0)\u003c/h4\u003e\n\n\u003cp\u003eExport the current Eclipse property from the view\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eundefined_value\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Value to use for undefined values. Defaults to 0.0\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-sim-well-fracture-completions-time-step-simulation-well-names-file-split-compdat-export\"\u003eexport_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export)\u003c/h4\u003e\n\n\u003cp\u003eExport fracture completions for simulation wells\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_step\u003c/td\u003e\n\u003ctd\u003eTime step to export for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esimulation_well_names\u003c/td\u003e\n\u003ctd\u003eList of simulation well names\u003c/td\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efile_split\u003c/td\u003e\n\u003ctd\u003eControls how export data is split into files\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecompdat_export\u003c/td\u003e\n\u003ctd\u003eCompdat export type\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-file-split-2\"\u003eEnum file_split\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo; \u003cb\u003eDefault Option\u003c/b\u003e\u003c/td\u003e\n\u003ctd\u003eA single file with all transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch5 id=\"enum-compdat-export-2\"\u003eEnum compdat_export\u003c/h5\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TRANSMISSIBILITIES\u0026rdquo;\u003cb\u003eDefault Option\u003c/b\u003e\u003c/td\u003e\n\u003ctd\u003eDirect export of transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eInclude export of WPIMULT\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"export-snapshot-prefix-export-folder\"\u003eexport_snapshot(prefix=\u0026ldquo;, export_folder=\u0026ldquo;)\u003c/h4\u003e\n\n\u003cp\u003eExport snapshot for the current view\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexport_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The path to export to. By default will use the global export folder\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"export-visible-cells-export-keyword-fluxnum-visible-active-cells-value-1-hidden-active-cells-value-0-inactive-cells-value-0\"\u003eexport_visible_cells(export_keyword=\u0026lsquo;FLUXNUM\u0026rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0)\u003c/h4\u003e\n\n\u003cp\u003eExport special properties for all visible cells.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eexport_keyword\u003c/strong\u003e (\u003cem\u003estring\u003c/em\u003e) \u0026ndash; The keyword to export.\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003eChoices\u003c/strong\u003e \u0026ndash; \u0026lsquo;FLUXNUM\u0026rsquo; or \u0026lsquo;MULTNUM\u0026rsquo;. Default: \u0026lsquo;FLUXNUM\u0026rsquo;\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003evisible_active_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export forvisible active cells. Default: 1\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003ehidden_active_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export for hidden active cells. Default: 0\u003c/p\u003e\u003c/li\u003e\n\n\u003cli\u003e\u003cp\u003e\u003cstrong\u003einactive_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export for inactive cells. Default: 0\u003c/p\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"set-background-color-bgcolor\"\u003eset_background_color(bgcolor)\u003c/h4\u003e\n\n\u003cp\u003eSet the background color in the view\u003c/p\u003e\n\n\u003ch4 id=\"set-cell-result\"\u003eset_cell_result()\u003c/h4\u003e\n\n\u003cp\u003eRetrieve the current cell results\u003c/p\u003e\n\n\u003ch4 id=\"set-show-grid-box-value\"\u003eset_show_grid_box(value)\u003c/h4\u003e\n\n\u003cp\u003eSet if the grid box is meant to be shown in the view\u003c/p\u003e\n\n\u003ch4 id=\"set-time-step-time-step\"\u003eset_time_step(time_step)\u003c/h4\u003e\n\n\u003cp\u003eSet the time step for current view\u003c/p\u003e\n\n\u003ch4 id=\"show-grid-box\"\u003eshow_grid_box()\u003c/h4\u003e\n\n\u003cp\u003eCheck if the grid box is meant to be shown in the view\u003c/p\u003e\n\n\u003ch2 id=\"synchronous-example\"\u003eSynchronous Example\u003c/h2\u003e\n\n\u003cp\u003eRead two properties, multiply them together and push the results back to ResInsight in a naïve way, by reading PORO into a list, then reading PERMX into a list, then multiplying them both in a resulting list and finally transferring back the list.\u003c/p\u003e\n\n\u003cp\u003eThis is slow and inefficient, but works.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eimport rips\nimport time\n\n# Internal function for creating a result from a small chunk of poro and permx results\n# The return value of the function is a generator for the results rather than the result itself.\ndef create_result(poro_chunks, permx_chunks):\n    # Loop through all the chunks of poro and permx in order\n    for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\n        resultChunk = []\n        # Loop through all the values inside the chunks, in order\n        for (poro, permx) in zip(poroChunk.values, permxChunk.values):\n            resultChunk.append(poro * permx)\n        # Return a generator object that behaves like a Python iterator\n        yield resultChunk\n\nresinsight     = rips.Instance.find()\nstart = time.time()\ncase = resinsight.project.cases()[0]\n\n# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\nporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\n# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\npermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\n\n# Send back the result with the result provided by a generator object.\n# Iterating the result generator will cause the script to read from the poro and permx generators\n# And return the result of each iteration\ncase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\n                                           'GENERATED', 'POROPERMXAS', 0)\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(\u0026quot;Transferred all results back\u0026quot;)\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch2 id=\"asynchronous-example\"\u003eAsynchronous Example\u003c/h2\u003e\n\n\u003cp\u003eRead two properties at the same time chunk by chunk, multiply each chunk together and start transferring the result back to ResInsight as soon as the chunk is finished.\u003c/p\u003e\n\n\u003cp\u003eThis is far more efficient.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e########################################################################################\nimport rips\nimport time\nimport grpc\n\nresinsight     = rips.Instance.find()\nstart = time.time()\ncase = resinsight.project.cases()[0]\n\n# Read poro result into list\nporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\n# Read permx result into list\npermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\n\n# Generate output result\nresults = []\nfor (poro, permx) in zip(poro_results, permx_results):\n    results.append(poro * permx)\n\ntry:\n    # Send back output result\n    case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\nexcept grpc.RpcError as e:\n    print(\u0026quot;Exception Received: \u0026quot;, e)\n\n\nend = time.time()\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\nprint(\u0026quot;Transferred all results back\u0026quot;)\n\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "Instance Module class rips.instance.Instance(port=50051, launched=False) The ResInsight Instance class. Use to launch or find existing ResInsight instances\nlaunched() Tells us whether the application was launched as a new process. If the application was launched we may need to close it when exiting the script.\n  Type\nbool\n  commands() Command executor. Set when creating an instance.\n  Type\nCommands\n  project() Current project in ResInsight. Set when creating an instance and updated when opening/closing projects.\n  Type\nProject\n  client_version_string() Get a full version string, i.e. 2019.04.01\nexit() Tell ResInsight instance to quit\nstatic find(start_port=50051, end_port=50071) Search for an existing Instance of ResInsight by testing ports.\nBy default we search from port 50051 to 50071 or if the environment variable RESINSIGHT_GRPC_PORT is set we search RESINSIGHT_GRPC_PORT to RESINSIGHT_GRPC_PORT+20\n  Parameters\n  start_port (int) \u0026ndash; start searching from this port\n  end_port (int) \u0026ndash; search up to but not including this port\n    is_console() Returns true if the connected ResInsight instance is a console app\nis_gui() Returns true if the connected ResInsight instance is a GUI app\nstatic launch(resinsight_executable=\u0026rsquo;', console=False, launch_port=-1, command_line_parameters=None) Launch a new Instance of ResInsight. This requires the environment variable RESINSIGHT_EXECUTABLE to be set or the parameter resinsight_executable to be provided. The RESINSIGHT_GRPC_PORT environment variable can be set to an alternative port number.\n  Parameters\n  resinsight_executable (str) \u0026ndash; Path to a valid ResInsight executable. If set will take precedence over what is provided in the RESINSIGHT_EXECUTABLE environment variable.\n  console (bool) \u0026ndash; If True, launch as console application, without GUI.\n  launch_port (int) \u0026ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT if anything else, ResInsight will try to launch with this port\n  command_line_parameters (list) \u0026ndash; Additional parameters as string entries in the list.\n    Returns\nan instance object if it worked. None if not.\n  Return type\nInstance\n  major_version() Get an integer with the major version number\nminor_version() Get an integer with the minor version number\npatch_version() Get an integer with the patch version number\nset_export_folder(export_type, path, create_folder=False) Set the export folder used for all export functions\n   Parameter Description Type     export_type String specifying what to export String   path Path to folder String   create_folder Create folder if it doesn\u0026rsquo;t exist? Boolean    Enum export_type    Option Description     \u0026ldquo;COMPLETIONS\u0026rdquo;    \u0026ldquo;SNAPSHOTS\u0026rdquo;    \u0026ldquo;PROPERTIES\u0026rdquo;    \u0026ldquo;STATISTICS\u0026rdquo;     set_main_window_size(width, height) Set the main window size in pixels\n   Parameter Description Type     width Width in pixels Integer   height Height in pixels Integer    set_plot_window_size(width, height) Set the plot window size in pixels\n   Parameter Description Type     width Width in pixels Integer   height Height in pixels Integer    set_start_dir(path) Set current start directory\n  Parameters\npath (str) \u0026ndash; path to directory\n  version_string() Get a full version string, i.e. 2019.04.01\nExample \rresinsight = rips.Instance.find()\rif resinsight is None:\rprint('ERROR: could not find ResInsight')\relse:\rprint('Successfully connected to ResInsight')\rCase Module class rips.case.Case(channel, case_id, project) ResInsight case class\nOperate on a ResInsight case specified by a Case Id integer. Not meant to be constructed separately but created by one of the following methods in Project: loadCase, case, allCases, selectedCasesq\nid() Case Id corresponding to case Id in ResInsight project.\n  Type\nint\n  name() Case name\n  Type\nstr\n  group_id() Case Group id\n  Type\nint\n  chunkSize() The size of each chunk during value streaming. A good chunk size is 64KiB = 65536B. Meaning the ideal number of doubles would be 8192. However we need overhead space, so the default is 8160. This leaves 256B for overhead.\n  Type\nint\n  active_cell_property(property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;) Get a cell property for all active cells. Sync, so returns a list\n  Parameters\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    Returns\nA list containing double values Loop through the chunks and then the values within the chunk to get all values.\n  active_cell_property_async(property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;) Get a cell property for all active cells. Async, so returns an iterator\n  Parameters\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    Returns\nAn iterator to a chunk object containing an array of double values Loop through the chunks and then the values within the chunk to get all values.\n  available_properties(property_type, porosity_model='MATRIX_MODEL\u0026rsquo;) Get a list of available properties\n  Parameters\n  property_type (str) \u0026ndash; string corresponding to property_type enum. Choices:\n DYNAMIC_NATIVE STATIC_NATIVE SOURSIMRL GENERATED INPUT_PROPERTY FORMATION_NAMES FLOW_DIAGNOSTICS INJECTION_FLOODING    porosity_model (str) \u0026ndash; \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n    cell_count(porosity_model='MATRIX_MODEL\u0026rsquo;) Get a cell count object containing number of active cells and total number of cells\n  Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n  Returns\nactive_cell_count: number of active cells reservoir_cell_count: total number of reservoir cells\n  Return type\nCell Count object with the following integer attributes\n  cell_info_for_active_cells(porosity_model='MATRIX_MODEL\u0026rsquo;) Get list of cell info objects for current case\n  Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n  Returns\nList of CellInfo objects\n  CellInfo class description    Parameter Description Type     grid_index Index to grid Integer   parent_grid_index Index to parent grid Integer   coarsening_box_index Index to coarsening box Integer   local_ijk Cell index in IJK directions of local grid Vec3i   parent_ijk Cell index in IJK directions of parent grid Vec3i    Vec3i class description    Parameter Description Type     i I grid index Integer   j J grid index Integer   k K grid index Integer    cell_info_for_active_cells_async(porosity_model='MATRIX_MODEL\u0026rsquo;) Get Stream of cell info objects for current case\n  Parameters\nporosity_model (str) \u0026ndash; String representing an enum. must be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\n  Returns\nStream of CellInfo objects\n  See cell_info_for_active_cells() for detalis on the CellInfo class.\ncontour_maps(map_type=\u0026lt;ContourMapType.ECLIPSE: 1\u0026gt;) Get a list of all contour maps belonging to a project\n   Parameter Description Type     time_steps Time step index Integer   well_path_names List of well path names List of Strings   refinement_i Refinment in x-direction Integer   refinement_j Refinment in y-direction Integer   refinement_k Refinment in z-direction Integer   split_type Defines how to split LGRS String enum      Parameters\nmap_type (enum) \u0026ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH\n  create_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action) Create Multiple Fractures in one go\ncreate_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type) Create a local grid refinement for the completions on the given well paths\n   Parameter Description Type     time_steps Time step index Integer   well_path_names List of well path names List of Strings   refinement_i Refinment in x-direction Integer   refinement_j Refinment in y-direction Integer   refinement_k Refinment in z-direction Integer   split_type Defines how to split LGRS String enum    Enum split_type    Option Description     \u0026ldquo;LGR_PER_CELL\u0026rdquo; One LGR for each completed cell   \u0026ldquo;LGR_PER_COMPLETION\u0026rdquo; One LGR for each completion (fracture, perforation, \u0026hellip;)   \u0026ldquo;LGR_PER_WELL\u0026rdquo; One LGR for each well    create_view() Create a new view in the current case\ncreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action) Create Multiple Fractures in one go\n   Parameter Description Type     template_id Id of the template Integer   well_path_names List of well path names List of Strings   min_dist_from_well_td Minimum distance from well TD Double   max_fractures_per_well Max number of fractures per well Integer   top_layer Top grid k-level for fractures Integer   base_layer Base grid k-level for fractures Integer   spacing Spacing between fractures Double   action \u0026lsquo;APPEND_FRACTURES\u0026rsquo; or \u0026lsquo;REPLACE_FRACTURES\u0026rsquo; String enum    create_saturation_pressure_plots() Create saturation pressure plots for the current case\ncreate_view() Create a new view in the current case\ncreate_well_bore_stability_plot(well_path, time_step) Create a new well bore stability plot\n  Parameters\n  well_path (str) \u0026ndash; well path name\n  time_step (int) \u0026ndash; time step\n    Returns\nA new plot object\n  days_since_start() Get a list of decimal values representing days since the start of the simulation\n* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\r export_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1) Export Flow Characteristics data to text file in CSV format\n   Parameter Description Type     time_steps Time step indices List of Integer   injectors Injector names List of Strings   producers Producer names List of Strings   file_name Export file name Integer   minimum_communication Minimum Communication, defaults to 0.0 Integer   aquifer_cell_threshold Aquifer Cell Threshold, defaults to 0.1 Integer    export_msw(well_path) Export Eclipse Multi-segment-well model to file\n  Parameters\n  Parameters\nwell_path (str) \u0026ndash; Well path name\n  export_property(time_step, property_name, eclipse_keyword=\u0026lt;class \u0026lsquo;property'\u0026gt;, undefined_value=0.0, export_file=\u0026lt;class \u0026lsquo;property'\u0026gt;) Export an Eclipse property\nEnum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; A single file with all combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well with combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    * **time_step** (*int*) -- time step index\r* **property_name** (*str*) -- property to export\r* **eclipse_keyword** (*str*) -- Keyword used in export header. Defaults: value of property\r* **undefined_value** (*double*) -- Value to use for undefined values. Defaults to 0.0\r* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\r grid(index) Get Grid of a given index. Returns a rips Grid object\nexport_snapshots_of_all_views(prefix=\u0026rsquo;', export_folder=\u0026rsquo;') Export snapshots for all views in the case\n  Parameters\n  prefix (str) \u0026ndash; Exported file name prefix\n  export_folder (str) \u0026ndash; The path to export to. By default will use the global export folder\n    export_well_path_completions(time_step, well_path_names, file_split, compdat_export='TRANSMISSIBILITIES\u0026rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode='INDIVIDUALLY\u0026rsquo;) Export well path completions for the current case to file\n   Parameter Description Type     time_step Time step to export for Integer   well_path_names List of well path names List   file_split Controls how export data is split into files String enum   compdat_export Compdat export type String enum   include_perforations Export perforations? bool   include_fishbones Export fishbones? bool   fishbones_exclude_main_bore Exclude main bore when exporting fishbones? bool   combination_mode Settings for multiple completions in same cell String Enum    Enum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; A single file with all combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well with combined transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    Enum compdat_export    Option Description     \u0026ldquo;TRANSMISSIBILITIES\u0026rdquo; Direct export of transmissibilities   \u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo; Include WPIMULT in addition to transmissibilities    Enum combination_mode    Option Description     \u0026ldquo;INDIVIDUALLY\u0026rdquo; Exports the different completion types into separate sections   \u0026ldquo;COMBINED\u0026rdquo; Export one combined transmissibility for each cell    grid(index) Get Grid of a given index. Returns a rips Grid object\n  Parameters\nindex (int) \u0026ndash; The grid index\n property_name (str) \u0026ndash; name of an Eclipse property    Returns: Grid object\ngrid_path() Get path of the current grid case\nReturns: path string\ngrid_property(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;) Get a cell property for all grid cells. Synchronous, so returns a list\n  Parameters\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  grid_index (int) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    Returns\nA list of double values\n  grid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;) Get a cell property for all grid cells. Async, so returns an iterator\n  Parameters\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  gridIndex (int) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    Returns\nAn iterator to a chunk object containing an array of double values Loop through the chunks and then the values within the chunk to get all values.\n  grids() Get a list of all rips Grid objects in the case\nimport_formation_names(formation_files=None) Import formation names into project and apply it to the current case\n  Parameters\nformation_files (list) \u0026ndash; list of files to import\n  replace(new_grid_file) Replace the current case grid with a new grid loaded from file\n  Parameters\nnew_egrid_file (str) \u0026ndash; path to EGRID file\n property_name (str) \u0026ndash; name of an Eclipse property    set_active_cell_property(values, property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;) Set a cell property for all active cells.\n  Parameters\n  values (list) \u0026ndash; a list of double precision floating point numbers\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    set_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;) Set cell property for all active cells Async. Takes an iterator to the input values\n  Parameters\n  values_iterator (iterator) \u0026ndash; an iterator to the properties to be set\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    set_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;) Set a cell property for all grid cells.\n  Parameters\n  values (list) \u0026ndash; a list of double precision floating point numbers\n  property_type (str) \u0026ndash; string enum. See available()\n  property_name (str) \u0026ndash; name of an Eclipse property\n  time_step (int) \u0026ndash; the time step for which to get the property for\n  grid_index (int) \u0026ndash; index to the grid we\u0026rsquo;re setting values for\n  porosity_model (str) \u0026ndash; string enum. See available()\n    time_steps() Get a list containing all time steps\nThe time steps are defined by the class TimeStepDate :\n   Type Name     int year   int month   int day   int hour   int minute   int second    view(view_id) Get a particular view belonging to a case by providing view id :param view_id: view id :type view_id: int\nReturns: a view object\nviews() Get a list of views belonging to a case\nExample \r# Import the ResInsight Processing Server Module\rimport rips\r# Connect to ResInsight\rresinsight = rips.Instance.find()\rif resinsight is not None:\r# Get a list of all cases\rcases = resinsight.project.cases()\rprint (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\rfor case in cases:\rprint(\u0026quot;Case id: \u0026quot; + str(case.case_id))\rprint(\u0026quot;Case name: \u0026quot; + case.name)\rprint(\u0026quot;Case type: \u0026quot; + case.type)\rprint(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\rtimesteps = case.time_steps()\rfor t in timesteps:\rprint(\u0026quot;Year: \u0026quot; + str(t.year))\rprint(\u0026quot;Month: \u0026quot; + str(t.month))\rContour Map Module class rips.contour_map.ContourMap(pdm_object, project, map_type) ResInsight contour map class\nview_id() View Id corresponding to the View Id in ResInsight project.\n  Type\nint\n  export_to_text(export_file_name=\u0026rsquo;', export_local_coordinates=False, undefined_value_label='NaN\u0026rsquo;, exclude_undefined_values=False) Export snapshot for the current view\n  Parameters\n  export_file_name (str) \u0026ndash; The file location to store results in.\n  export_local_coordinates (bool) \u0026ndash; Should we export local coordinates, or UTM.\n  undefined_value_label (str) \u0026ndash; Replace undefined values with this label.\n  exclude_undefined_values (bool) \u0026ndash; Skip undefined values.\n    Grid Module class rips.grid.Grid(index, case, channel) Grid Information. Not meant to be constructed separately\nCreate Grid objects using mathods on Case: Grid() and Grids()\ndimensions() The dimensions in i, j, k direction\n  Returns\nclass with integer attributes i, j, k giving extent in all three dimensions.\n  Return type\nVec3i\n  Example  case = rips_instance.project.loadCase(path=casePath)\rprint (case.gridCount())\rif case.gridCount() \u0026gt; 0:\rgrid = case.grid(index=0)\rdimensions = grid.dimensions()\rprint(dimensions.i)\rprint(dimensions.j)\rprint(dimensions.k)\rGridCaseGroup Module class rips.gridcasegroup.GridCaseGroup(pdm_object) ResInsight Grid Case Group class\nOperate on a ResInsight case group specified by a Case Group Id integer.\ngroup_id() Grid Case Group Id corresponding to case group Id in ResInsight project.\n  Type\nint\n  compute_statistics(case_ids=None) Compute statistics for the given case ids\n  Parameters\n  case_ids (list of integers) \u0026ndash; list of case ids.\n  this is None all cases in group are included (If) \u0026ndash;\n    create_statistics_case() Create a Statistics case in the Grid Case Group\n  Returns\nA new Case\n  statistics_cases() Get a list of all statistics cases in the Grid Case Group\nview(view_id) Get a particular view belonging to a case group by providing view id :param id: view id :type id: int\nReturns: a view object\nviews() Get a list of views belonging to a grid case group\nProject Module class rips.project.Project(channel) ResInsight project. Not intended to be created separately.\n Type  case(case_id) Get a specific case from the provided case Id\ncompute_statistics(case_ids=None) Compute statistics for the given case ids\n  Parameters\n  case_ids (list of integers) \u0026ndash; list of case ids.\n  this is None all cases in group are included (If) \u0026ndash;\n    create_statistics_case() Create a Statistics case in the Grid Case Group\n  Returns\nA new Case\n  statistics_cases() Get a list of all statistics cases in the Grid Case Group\ncontour_maps(map_type=\u0026lt;ContourMapType.ECLIPSE: 1\u0026gt;) Get a list of all contour maps belonging to a project\nReturns: a view object\ncreate_grid_case_group(case_paths) Create a Grid Case Group from a list of cases\n  Parameters\ncase_paths (list) \u0026ndash; list of file path strings\n  Returns\nA case group id and name\n  export_multi_case_snapshots(grid_list_file) Export snapshots for a set of cases\n  Parameters\ngrid_list_file (str) \u0026ndash; Path to a file containing a list of grids to export snapshot for\n  export_snapshots(snapshot_type='ALL\u0026rsquo;, prefix=\u0026rsquo;') Export all snapshots of a given type\n  Parameters\n  snapshot_type (str) \u0026ndash; Enum string (\u0026lsquo;ALL\u0026rsquo;, \u0026lsquo;VIEWS\u0026rsquo; or \u0026lsquo;PLOTS\u0026rsquo;)\n  prefix (str) \u0026ndash; Exported file name prefix\n    export_well_paths(well_paths=None, md_step_size=5.0) Export a set of well paths\n  Parameters\n  well_paths (list) \u0026ndash; List of strings of well paths. If none, export all.\n  md_step_size (double) \u0026ndash; resolution of the exported well path\n    grid_case_group(group_id) Get a particular grid case group belonging to a project\n  Parameters\ngroupId (int) \u0026ndash; group id\n  create_grid_case_group(case_paths) Create a Grid Case Group from a list of cases\nReturns: a grid case group object\ngrid_case_groups() Get a list of all grid case groups in the project\nimport_formation_names(formation_files=None) Import formation names into project\n  Parameters\nformation_files (list) \u0026ndash; list of files to import\n  export_multi_case_snapshots(grid_list_file) Export snapshots for a set of cases\nimport_well_log_files(well_log_files=None, well_log_folder=\u0026rsquo;') Import well log files into project\n  Parameters\n  well_log_files (list) \u0026ndash; List of file paths to import\n  well_log_folder (str) \u0026ndash; A folder path containing files to import\n    Returns\nA list of well path names (strings) that had logs imported\n  import_well_paths(well_path_files=None, well_path_folder=\u0026rsquo;') Import well paths into project\n  Parameters\n  well_path_files (list) \u0026ndash; List of file paths to import\n  well_path_folder (str) \u0026ndash; A folder path containing files to import\n    Returns\nA list of well path names (strings)\n  Returns: a grid case group object\nload_case(path) Load a new case from the given file path\ngrid_case_groups() Get a list of all grid case groups in the project\n**path** (*str*) -- file path to case\r   Parameters\n  Returns\nA rips Case object\n  open(path) Open a new project from the given path\n  Parameters\npath (str) \u0026ndash; path to project file\n  Parameters\n  plot(view_id) Get a particular plot by providing view id :param view_id: view id :type view_id: int\nReturns: a plot object\nplots() Get a list of all plots belonging to a project\nreplace_source_cases(grid_list_file, case_group_id=0) Replace all source cases within a case group\n  Parameters\n  grid_list_file (str) \u0026ndash; path to file containing a list of cases\n  case_group_id (int) \u0026ndash; id of the case group to replace\n    save(path=\u0026rsquo;') Save the project to the existing project file, or to a new file :param path: File path to the file to save the project to. If empty, saves to the active project file :type path: str\nscale_fracture_template(template_id, half_length, height, d_factor, conductivity) Scale fracture template parameters\n  Parameters\n  template_id (int) \u0026ndash; ID of fracture template\n  half_length (double) \u0026ndash; Half Length scale factor\n  height (double) \u0026ndash; Height scale factor\n  d_factor (double) \u0026ndash; D-factor scale factor\n  conductivity (double) \u0026ndash; Conductivity scale factor\n    selected_cases() Get a list of all cases selected in the project tree\n  Returns\nA list of rips Case objects\n  set_fracture_containment(template_id, top_layer, base_layer) Set fracture template containment parameters\nset_fracture_containment(template_id, top_layer, base_layer) Set fracture template containment parameters\n  Parameters\n  template_id (int) \u0026ndash; ID of fracture template\n  top_layer (int) \u0026ndash; Top layer containment\n  base_layer (int) \u0026ndash; Base layer containment\n    view(view_id) Get a particular view belonging to a case by providing view id\n  Parameters\nview_id (int) \u0026ndash; view id\n  Returns: a view object\nviews() Get a list of views belonging to a project\nwell_paths() Get a list of all the well path names in the project\nView Module class rips.view.View(pdm_object, project) ResInsight view class\nview_id() View Id corresponding to the View Id in ResInsight project.\n  Type\nint\n  apply_cell_result(result_type, result_variable) Apply a regular cell result\n  Parameters\n  result_type (str) \u0026ndash; String representing the result category. The valid values are\n DYNAMIC_NATIVE STATIC_NATIVE SOURSIMRL GENERATED INPUT_PROPERTY FORMATION_NAMES FLOW_DIAGNOSTICS INJECTION_FLOODING    result_variable (str) \u0026ndash; String representing the result variable.\n    apply_flow_diagnostics_cell_result(result_variable='TOF\u0026rsquo;, selection_mode='FLOW_TR_BY_SELECTION\u0026rsquo;, injectors=None, producers=None) Apply a flow diagnostics cell result\n   Parameter Description Type     result_variable String representing the result value String   selection_mode String specifying which tracers to select String   injectors List of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo; String List   producers List of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo; String List    Enum compdat_export    Option Description     \u0026ldquo;TOF\u0026rdquo; Time of flight   \u0026ldquo;Fraction\u0026rdquo; Fraction   \u0026ldquo;MaxFractionTracer\u0026rdquo; Max Fraction Tracer   \u0026ldquo;Communication\u0026rdquo; Communication    background_color() Get the current background color in the view\ncase() Get the case the view belongs to\nclone() Clone the current view\nexport_property(undefined_value=0.0) Export the current Eclipse property from the view\n  Parameters\nundefined_value (double) \u0026ndash; Value to use for undefined values. Defaults to 0.0\n  export_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export) Export fracture completions for simulation wells\n   Parameter Description Type     time_step Time step to export for Integer   simulation_well_names List of simulation well names List   file_split Controls how export data is split into files String enum   compdat_export Compdat export type String enum    Enum file_split    Option Description     \u0026ldquo;UNIFIED_FILE\u0026rdquo; Default Option A single file with all transmissibilities   \u0026ldquo;SPLIT_ON_WELL\u0026rdquo; One file for each well transmissibilities   \u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo; One file for each completion type for each well    Enum compdat_export    Option Description     \u0026ldquo;TRANSMISSIBILITIES\u0026quot;Default Option Direct export of transmissibilities   \u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo; Include export of WPIMULT    export_snapshot(prefix=\u0026rsquo;', export_folder=\u0026rsquo;') Export snapshot for the current view\n  Parameters\n  prefix (str) \u0026ndash; Exported file name prefix\n  export_folder (str) \u0026ndash; The path to export to. By default will use the global export folder\n    export_visible_cells(export_keyword='FLUXNUM\u0026rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0) Export special properties for all visible cells.\n  Parameters\n  export_keyword (string) \u0026ndash; The keyword to export.\n  Choices \u0026ndash; \u0026lsquo;FLUXNUM\u0026rsquo; or \u0026lsquo;MULTNUM\u0026rsquo;. Default: \u0026lsquo;FLUXNUM\u0026rsquo;\n  visible_active_cells_value (int) \u0026ndash; Value to export forvisible active cells. Default: 1\n  hidden_active_cells_value (int) \u0026ndash; Value to export for hidden active cells. Default: 0\n  inactive_cells_value (int) \u0026ndash; Value to export for inactive cells. Default: 0\n    set_background_color(bgcolor) Set the background color in the view\nset_cell_result() Retrieve the current cell results\nset_show_grid_box(value) Set if the grid box is meant to be shown in the view\nset_time_step(time_step) Set the time step for current view\nshow_grid_box() Check if the grid box is meant to be shown in the view\nSynchronous Example Read two properties, multiply them together and push the results back to ResInsight in a naïve way, by reading PORO into a list, then reading PERMX into a list, then multiplying them both in a resulting list and finally transferring back the list.\nThis is slow and inefficient, but works.\nimport rips\rimport time\r# Internal function for creating a result from a small chunk of poro and permx results\r# The return value of the function is a generator for the results rather than the result itself.\rdef create_result(poro_chunks, permx_chunks):\r# Loop through all the chunks of poro and permx in order\rfor (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\rresultChunk = []\r# Loop through all the values inside the chunks, in order\rfor (poro, permx) in zip(poroChunk.values, permxChunk.values):\rresultChunk.append(poro * permx)\r# Return a generator object that behaves like a Python iterator\ryield resultChunk\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\r# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\rporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\r# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\rpermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\r# Send back the result with the result provided by a generator object.\r# Iterating the result generator will cause the script to read from the poro and permx generators\r# And return the result of each iteration\rcase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\r'GENERATED', 'POROPERMXAS', 0)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\rAsynchronous Example Read two properties at the same time chunk by chunk, multiply each chunk together and start transferring the result back to ResInsight as soon as the chunk is finished.\nThis is far more efficient.\n########################################################################################\rimport rips\rimport time\rimport grpc\rresinsight = rips.Instance.find()\rstart = time.time()\rcase = resinsight.project.cases()[0]\r# Read poro result into list\rporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\r# Read permx result into list\rpermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\r# Generate output result\rresults = []\rfor (poro, permx) in zip(poro_results, permx_results):\rresults.append(poro * permx)\rtry:\r# Send back output result\rcase.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\rexcept grpc.RpcError as e:\rprint(\u0026quot;Exception Received: \u0026quot;, e)\rend = time.time()\rprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\rprint(\u0026quot;Transferred all results back\u0026quot;)\rview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\r",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch1 id=\"instance-module\"\u003eInstance Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripsinstanceinstanceport50051-launchedfalse\"\u003eclass rips.instance.Instance(port=50051, launched=False)\u003c/h4\u003e\n\u003cp\u003eThe ResInsight Instance class. Use to launch or find existing ResInsight instances\u003c/p\u003e\n\u003ch4 id=\"launched\"\u003elaunched()\u003c/h4\u003e\n\u003cp\u003eTells us whether the application was launched as a new process.\nIf the application was launched we may need to close it when exiting the script.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003ebool\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"commands\"\u003ecommands()\u003c/h4\u003e\n\u003cp\u003eCommand executor. Set when creating an instance.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eCommands\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"project\"\u003eproject()\u003c/h4\u003e\n\u003cp\u003eCurrent project in ResInsight.\nSet when creating an instance and updated when opening/closing projects.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eProject\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"client_version_string\"\u003eclient_version_string()\u003c/h4\u003e\n\u003cp\u003eGet a full version string, i.e. 2019.04.01\u003c/p\u003e\n\u003ch4 id=\"exit\"\u003eexit()\u003c/h4\u003e\n\u003cp\u003eTell ResInsight instance to quit\u003c/p\u003e\n\u003ch4 id=\"static-findstart_port50051-end_port50071\"\u003estatic find(start_port=50051, end_port=50071)\u003c/h4\u003e\n\u003cp\u003eSearch for an existing Instance of ResInsight by testing ports.\u003c/p\u003e\n\u003cp\u003eBy default we search from port 50051 to 50071 or if the environment\nvariable RESINSIGHT_GRPC_PORT is set we search\nRESINSIGHT_GRPC_PORT to RESINSIGHT_GRPC_PORT+20\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003estart_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; start searching from this port\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eend_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; search up to but not including this port\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"is_console\"\u003eis_console()\u003c/h4\u003e\n\u003cp\u003eReturns true if the connected ResInsight instance is a console app\u003c/p\u003e\n\u003ch4 id=\"is_gui\"\u003eis_gui()\u003c/h4\u003e\n\u003cp\u003eReturns true if the connected ResInsight instance is a GUI app\u003c/p\u003e\n\u003ch4 id=\"static-launchresinsight_executable-consolefalse-launch_port-1-command_line_parametersnone\"\u003estatic launch(resinsight_executable=\u0026rsquo;', console=False, launch_port=-1, command_line_parameters=None)\u003c/h4\u003e\n\u003cp\u003eLaunch a new Instance of ResInsight. This requires the environment variable\nRESINSIGHT_EXECUTABLE to be set or the parameter resinsight_executable to be provided.\nThe RESINSIGHT_GRPC_PORT environment variable can be set to an alternative port number.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eresinsight_executable\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Path to a valid ResInsight executable. If set\nwill take precedence over what is provided in the RESINSIGHT_EXECUTABLE\nenvironment variable.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003econsole\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; If True, launch as console application, without GUI.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003elaunch_port\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; If -1 will use the default port 50051 or RESINSIGHT_GRPC_PORT\nif anything else, ResInsight will try to launch with this port\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ecommand_line_parameters\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; Additional parameters as string entries in the list.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003ean instance object if it worked. None if not.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eInstance\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"major_version\"\u003emajor_version()\u003c/h4\u003e\n\u003cp\u003eGet an integer with the major version number\u003c/p\u003e\n\u003ch4 id=\"minor_version\"\u003eminor_version()\u003c/h4\u003e\n\u003cp\u003eGet an integer with the minor version number\u003c/p\u003e\n\u003ch4 id=\"patch_version\"\u003epatch_version()\u003c/h4\u003e\n\u003cp\u003eGet an integer with the patch version number\u003c/p\u003e\n\u003ch4 id=\"set_export_folderexport_type-path-create_folderfalse\"\u003eset_export_folder(export_type, path, create_folder=False)\u003c/h4\u003e\n\u003cp\u003eSet the export folder used for all export functions\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eexport_type\u003c/td\u003e\n\u003ctd\u003eString specifying what to export\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003epath\u003c/td\u003e\n\u003ctd\u003ePath to folder\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecreate_folder\u003c/td\u003e\n\u003ctd\u003eCreate folder if it doesn\u0026rsquo;t exist?\u003c/td\u003e\n\u003ctd\u003eBoolean\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-export_type\"\u003eEnum export_type\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;COMPLETIONS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SNAPSHOTS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;PROPERTIES\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;STATISTICS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"set_main_window_sizewidth-height\"\u003eset_main_window_size(width, height)\u003c/h4\u003e\n\u003cp\u003eSet the main window size in pixels\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eWidth in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"set_plot_window_sizewidth-height\"\u003eset_plot_window_size(width, height)\u003c/h4\u003e\n\u003cp\u003eSet the plot window size in pixels\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ewidth\u003c/td\u003e\n\u003ctd\u003eWidth in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eheight\u003c/td\u003e\n\u003ctd\u003eHeight in pixels\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"set_start_dirpath\"\u003eset_start_dir(path)\u003c/h4\u003e\n\u003cp\u003eSet current start directory\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003epath\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to directory\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"version_string\"\u003eversion_string()\u003c/h4\u003e\n\u003cp\u003eGet a full version string, i.e. 2019.04.01\u003c/p\u003e\n\u003ch2 id=\"example\"\u003eExample\u003c/h2\u003e\n\u003cpre\u003e\u003ccode\u003e\r\nresinsight  = rips.Instance.find()\r\n\r\nif resinsight is None:\r\n    print('ERROR: could not find ResInsight')\r\nelse:\r\n\tprint('Successfully connected to ResInsight')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"case-module\"\u003eCase Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripscasecasechannel-case_id-project\"\u003eclass rips.case.Case(channel, case_id, project)\u003c/h4\u003e\n\u003cp\u003eResInsight case class\u003c/p\u003e\n\u003cp\u003eOperate on a ResInsight case specified by a Case Id integer.\nNot meant to be constructed separately but created by one of the following\nmethods in Project: loadCase, case, allCases, selectedCasesq\u003c/p\u003e\n\u003ch4 id=\"id\"\u003eid()\u003c/h4\u003e\n\u003cp\u003eCase Id corresponding to case Id in ResInsight project.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"name\"\u003ename()\u003c/h4\u003e\n\u003cp\u003eCase name\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003estr\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"group_id\"\u003egroup_id()\u003c/h4\u003e\n\u003cp\u003eCase Group id\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"chunksize\"\u003echunkSize()\u003c/h4\u003e\n\u003cp\u003eThe size of each chunk during value streaming.\nA good chunk size is 64KiB = 65536B.\nMeaning the ideal number of doubles would be 8192.\nHowever we need overhead space, so the default is 8160.\nThis leaves 256B for overhead.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"active_cell_propertyproperty_type-property_name-time_step-porosity_modelmatrix_model\"\u003eactive_cell_property(property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a cell property for all active cells. Sync, so returns a list\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA list containing double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"active_cell_property_asyncproperty_type-property_name-time_step-porosity_modelmatrix_model\"\u003eactive_cell_property_async(property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a cell property for all active cells. Async, so returns an iterator\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eAn iterator to a chunk object containing an array of double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"available_propertiesproperty_type-porosity_modelmatrix_model\"\u003eavailable_properties(property_type, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a list of available properties\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string corresponding to property_type enum. Choices:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eDYNAMIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSTATIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSOURSIMRL\u003c/li\u003e\n\u003cli\u003eGENERATED\u003c/li\u003e\n\u003cli\u003eINPUT_PROPERTY\u003c/li\u003e\n\u003cli\u003eFORMATION_NAMES\u003c/li\u003e\n\u003cli\u003eFLOW_DIAGNOSTICS\u003c/li\u003e\n\u003cli\u003eINJECTION_FLOODING\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"cell_countporosity_modelmatrix_model\"\u003ecell_count(porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a cell count object containing number of active cells and\ntotal number of cells\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eactive_cell_count: number of active cells\nreservoir_cell_count: total number of reservoir cells\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eCell Count object with the following integer attributes\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"cell_info_for_active_cellsporosity_modelmatrix_model\"\u003ecell_info_for_active_cells(porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet list of cell info objects for current case\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eList of \u003cstrong\u003eCellInfo\u003c/strong\u003e objects\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"cellinfo-class-description\"\u003eCellInfo class description\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egrid_index\u003c/td\u003e\n\u003ctd\u003eIndex to grid\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eparent_grid_index\u003c/td\u003e\n\u003ctd\u003eIndex to parent grid\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecoarsening_box_index\u003c/td\u003e\n\u003ctd\u003eIndex to coarsening box\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003elocal_ijk\u003c/td\u003e\n\u003ctd\u003eCell index in IJK directions of local grid\u003c/td\u003e\n\u003ctd\u003eVec3i\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eparent_ijk\u003c/td\u003e\n\u003ctd\u003eCell index in IJK directions of parent grid\u003c/td\u003e\n\u003ctd\u003eVec3i\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"vec3i-class-description\"\u003eVec3i class description\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ei\u003c/td\u003e\n\u003ctd\u003eI grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ej\u003c/td\u003e\n\u003ctd\u003eJ grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ek\u003c/td\u003e\n\u003ctd\u003eK grid index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"cell_info_for_active_cells_asyncporosity_modelmatrix_model\"\u003ecell_info_for_active_cells_async(porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet Stream of cell info objects for current case\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing an enum.\nmust be \u0026lsquo;MATRIX_MODEL\u0026rsquo; or \u0026lsquo;FRACTURE_MODEL\u0026rsquo;.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eStream of \u003cstrong\u003eCellInfo\u003c/strong\u003e objects\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee cell_info_for_active_cells() for detalis on the \u003cstrong\u003eCellInfo\u003c/strong\u003e class.\u003c/p\u003e\n\u003ch4 id=\"contour_mapsmap_typecontourmaptypeeclipse-1\"\u003econtour_maps(map_type=\u0026lt;ContourMapType.ECLIPSE: 1\u0026gt;)\u003c/h4\u003e\n\u003cp\u003eGet a list of all contour maps belonging to a project\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_i\u003c/td\u003e\n\u003ctd\u003eRefinment in x-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_j\u003c/td\u003e\n\u003ctd\u003eRefinment in y-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_k\u003c/td\u003e\n\u003ctd\u003eRefinment in z-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esplit_type\u003c/td\u003e\n\u003ctd\u003eDefines how to split LGRS\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003emap_type\u003c/strong\u003e (\u003cem\u003eenum\u003c/em\u003e) \u0026ndash; ContourMapType.ECLIPSE or ContourMapType.GEO_MECH\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"create_multiple_fracturestemplate_id-well_path_names-min_dist_from_well_td-max_fractures_per_well-top_layer-base_layer-spacing-action\"\u003ecreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)\u003c/h4\u003e\n\u003cp\u003eCreate Multiple Fractures in one go\u003c/p\u003e\n\u003ch4 id=\"create_lgr_for_completiontime_step-well_path_names-refinement_i-refinement_j-refinement_k-split_type\"\u003ecreate_lgr_for_completion(time_step, well_path_names, refinement_i, refinement_j, refinement_k, split_type)\u003c/h4\u003e\n\u003cp\u003eCreate a local grid refinement for the completions on the given well paths\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step index\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_i\u003c/td\u003e\n\u003ctd\u003eRefinment in x-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_j\u003c/td\u003e\n\u003ctd\u003eRefinment in y-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erefinement_k\u003c/td\u003e\n\u003ctd\u003eRefinment in z-direction\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esplit_type\u003c/td\u003e\n\u003ctd\u003eDefines how to split LGRS\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-split_type\"\u003eEnum split_type\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_CELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each completed cell\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_COMPLETION\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each completion (fracture, perforation, \u0026hellip;)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;LGR_PER_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne LGR for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"create_view\"\u003ecreate_view()\u003c/h4\u003e\n\u003cp\u003eCreate a new view in the current case\u003c/p\u003e\n\u003ch4 id=\"create_multiple_fracturestemplate_id-well_path_names-min_dist_from_well_td-max_fractures_per_well-top_layer-base_layer-spacing-action-1\"\u003ecreate_multiple_fractures(template_id, well_path_names, min_dist_from_well_td, max_fractures_per_well, top_layer, base_layer, spacing, action)\u003c/h4\u003e\n\u003cp\u003eCreate Multiple Fractures in one go\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etemplate_id\u003c/td\u003e\n\u003ctd\u003eId of the template\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emin_dist_from_well_td\u003c/td\u003e\n\u003ctd\u003eMinimum distance from well TD\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emax_fractures_per_well\u003c/td\u003e\n\u003ctd\u003eMax number of fractures per well\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etop_layer\u003c/td\u003e\n\u003ctd\u003eTop grid k-level for fractures\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ebase_layer\u003c/td\u003e\n\u003ctd\u003eBase grid k-level for fractures\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003espacing\u003c/td\u003e\n\u003ctd\u003eSpacing between fractures\u003c/td\u003e\n\u003ctd\u003eDouble\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eaction\u003c/td\u003e\n\u003ctd\u003e\u0026lsquo;APPEND_FRACTURES\u0026rsquo; or \u0026lsquo;REPLACE_FRACTURES\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"create_saturation_pressure_plots\"\u003ecreate_saturation_pressure_plots()\u003c/h4\u003e\n\u003cp\u003eCreate saturation pressure plots for the current case\u003c/p\u003e\n\u003ch4 id=\"create_view-1\"\u003ecreate_view()\u003c/h4\u003e\n\u003cp\u003eCreate a new view in the current case\u003c/p\u003e\n\u003ch4 id=\"create_well_bore_stability_plotwell_path-time_step\"\u003ecreate_well_bore_stability_plot(well_path, time_step)\u003c/h4\u003e\n\u003cp\u003eCreate a new well bore stability plot\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_path\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; well path name\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; time step\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA new plot object\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"days_since_start\"\u003edays_since_start()\u003c/h4\u003e\n\u003cp\u003eGet a list of decimal values representing days since the start of the simulation\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"export_flow_characteristicstime_steps-injectors-producers-file_name-minimum_communication00-aquifer_cell_threshold01\"\u003eexport_flow_characteristics(time_steps, injectors, producers, file_name, minimum_communication=0.0, aquifer_cell_threshold=0.1)\u003c/h4\u003e\n\u003cp\u003eExport Flow Characteristics data to text file in CSV format\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_steps\u003c/td\u003e\n\u003ctd\u003eTime step indices\u003c/td\u003e\n\u003ctd\u003eList of Integer\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eInjector names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eProducer names\u003c/td\u003e\n\u003ctd\u003eList of Strings\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efile_name\u003c/td\u003e\n\u003ctd\u003eExport file name\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eminimum_communication\u003c/td\u003e\n\u003ctd\u003eMinimum Communication, defaults to 0.0\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eaquifer_cell_threshold\u003c/td\u003e\n\u003ctd\u003eAquifer Cell Threshold, defaults to 0.1\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"export_mswwell_path\"\u003eexport_msw(well_path)\u003c/h4\u003e\n\u003cp\u003eExport Eclipse Multi-segment-well model to file\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003ewell_path\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Well path name\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_propertytime_step-property_name-eclipse_keywordclass-property-undefined_value00-export_fileclass-property\"\u003eexport_property(time_step, property_name, eclipse_keyword=\u0026lt;class \u0026lsquo;property'\u0026gt;, undefined_value=0.0, export_file=\u0026lt;class \u0026lsquo;property'\u0026gt;)\u003c/h4\u003e\n\u003cp\u003eExport an Eclipse property\u003c/p\u003e\n\u003ch5 id=\"enum-file_split\"\u003eEnum file_split\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eA single file with all combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well with combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003e* **time_step** (*int*) -- time step index\r\n\r\n* **property_name** (*str*) -- property to export\r\n\r\n* **eclipse_keyword** (*str*) -- Keyword used in export header. Defaults: value of property\r\n\r\n* **undefined_value** (*double*) -- Value to use for undefined values. Defaults to 0.0\r\n\r\n* **export_file** (*str*) -- File name for export. Defaults to the value of property parameter\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"gridindex\"\u003egrid(index)\u003c/h4\u003e\n\u003cp\u003eGet Grid of a given index. Returns a rips Grid object\u003c/p\u003e\n\u003ch4 id=\"export_snapshots_of_all_viewsprefix-export_folder\"\u003eexport_snapshots_of_all_views(prefix=\u0026rsquo;', export_folder=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eExport snapshots for all views in the case\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexport_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The path to export to. By default will use the global export folder\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_well_path_completionstime_step-well_path_names-file_split-compdat_exporttransmissibilities-include_perforationstrue-include_fishbonestrue-fishbones_exclude_main_boretrue-combination_modeindividually\"\u003eexport_well_path_completions(time_step, well_path_names, file_split, compdat_export='TRANSMISSIBILITIES\u0026rsquo;, include_perforations=True, include_fishbones=True, fishbones_exclude_main_bore=True, combination_mode='INDIVIDUALLY\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eExport well path completions for the current case to file\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_step\u003c/td\u003e\n\u003ctd\u003eTime step to export for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewell_path_names\u003c/td\u003e\n\u003ctd\u003eList of well path names\u003c/td\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efile_split\u003c/td\u003e\n\u003ctd\u003eControls how export data is split into files\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecompdat_export\u003c/td\u003e\n\u003ctd\u003eCompdat export type\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einclude_perforations\u003c/td\u003e\n\u003ctd\u003eExport perforations?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einclude_fishbones\u003c/td\u003e\n\u003ctd\u003eExport fishbones?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efishbones_exclude_main_bore\u003c/td\u003e\n\u003ctd\u003eExclude main bore when exporting fishbones?\u003c/td\u003e\n\u003ctd\u003ebool\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecombination_mode\u003c/td\u003e\n\u003ctd\u003eSettings for multiple completions in same cell\u003c/td\u003e\n\u003ctd\u003eString Enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-file_split-1\"\u003eEnum file_split\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eA single file with all combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well with combined transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-compdat_export\"\u003eEnum compdat_export\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TRANSMISSIBILITIES\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eDirect export of transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eInclude WPIMULT in addition to transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-combination_mode\"\u003eEnum combination_mode\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;INDIVIDUALLY\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eExports the different completion types into separate sections\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;COMBINED\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eExport one combined transmissibility for each cell\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"gridindex-1\"\u003egrid(index)\u003c/h4\u003e\n\u003cp\u003eGet Grid of a given index. Returns a rips Grid object\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eindex\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; The grid index\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eReturns: Grid object\u003c/p\u003e\n\u003ch4 id=\"grid_path\"\u003egrid_path()\u003c/h4\u003e\n\u003cp\u003eGet path of the current grid case\u003c/p\u003e\n\u003cp\u003eReturns: path string\u003c/p\u003e\n\u003ch4 id=\"grid_propertyproperty_type-property_name-time_step-grid_index0-porosity_modelmatrix_model\"\u003egrid_property(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a cell property for all grid cells. Synchronous, so returns a list\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003egrid_index\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA list of double values\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"grid_property_asyncproperty_type-property_name-time_step-grid_index0-porosity_modelmatrix_model\"\u003egrid_property_async(property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eGet a cell property for all grid cells. Async, so returns an iterator\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003egridIndex\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re getting values for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eAn iterator to a chunk object containing an array of double values\nLoop through the chunks and then the values within the chunk to get all values.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"grids\"\u003egrids()\u003c/h4\u003e\n\u003cp\u003eGet a list of all rips Grid objects in the case\u003c/p\u003e\n\u003ch4 id=\"import_formation_namesformation_filesnone\"\u003eimport_formation_names(formation_files=None)\u003c/h4\u003e\n\u003cp\u003eImport formation names into project and apply it to the current case\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eformation_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of files to import\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"replacenew_grid_file\"\u003ereplace(new_grid_file)\u003c/h4\u003e\n\u003cp\u003eReplace the current case grid with a new grid loaded from file\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003enew_egrid_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to EGRID file\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"set_active_cell_propertyvalues-property_type-property_name-time_step-porosity_modelmatrix_model\"\u003eset_active_cell_property(values, property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eSet a cell property for all active cells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003evalues\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; a list of double precision floating point numbers\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"set_active_cell_property_asyncvalues_iterator-property_type-property_name-time_step-porosity_modelmatrix_model\"\u003eset_active_cell_property_async(values_iterator, property_type, property_name, time_step, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eSet cell property for all active cells Async. Takes an iterator to the input values\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003evalues_iterator\u003c/strong\u003e (\u003cem\u003eiterator\u003c/em\u003e) \u0026ndash; an iterator to the properties to be set\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"set_grid_propertyvalues-property_type-property_name-time_step-grid_index0-porosity_modelmatrix_model\"\u003eset_grid_property(values, property_type, property_name, time_step, grid_index=0, porosity_model='MATRIX_MODEL\u0026rsquo;)\u003c/h4\u003e\n\u003cp\u003eSet a cell property for all grid cells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003evalues\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; a list of double precision floating point numbers\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eproperty_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; name of an Eclipse property\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etime_step\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; the time step for which to get the property for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003egrid_index\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; index to the grid we\u0026rsquo;re setting values for\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eporosity_model\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; string enum. See available()\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"time_steps\"\u003etime_steps()\u003c/h4\u003e\n\u003cp\u003eGet a list containing all time steps\u003c/p\u003e\n\u003cp\u003eThe time steps are defined by the class \u003cstrong\u003eTimeStepDate\u003c/strong\u003e :\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eyear\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003emonth\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eday\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003ehour\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003eminute\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eint\u003c/td\u003e\n\u003ctd\u003esecond\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"viewview_id\"\u003eview(view_id)\u003c/h4\u003e\n\u003cp\u003eGet a particular view belonging to a case by providing view id\n:param view_id: view id\n:type view_id: int\u003c/p\u003e\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\u003ch4 id=\"views\"\u003eviews()\u003c/h4\u003e\n\u003cp\u003eGet a list of views belonging to a case\u003c/p\u003e\n\u003ch2 id=\"example-1\"\u003eExample\u003c/h2\u003e\n\u003cpre\u003e\u003ccode\u003e\r\n# Import the ResInsight Processing Server Module\r\nimport rips\r\n\r\n# Connect to ResInsight\r\nresinsight  = rips.Instance.find()\r\nif resinsight is not None:\r\n    # Get a list of all cases\r\n    cases = resinsight.project.cases()\r\n\r\n    print (\u0026quot;Got \u0026quot; + str(len(cases)) + \u0026quot; cases: \u0026quot;)\r\n    for case in cases:\r\n        print(\u0026quot;Case id: \u0026quot; + str(case.case_id))\r\n        print(\u0026quot;Case name: \u0026quot; + case.name)\r\n        print(\u0026quot;Case type: \u0026quot; + case.type)\r\n        print(\u0026quot;Case grid path: \u0026quot; + case.grid_path())\r\n        \r\n        timesteps = case.time_steps()\r\n        for t in timesteps:\r\n            print(\u0026quot;Year: \u0026quot; + str(t.year))\r\n            print(\u0026quot;Month: \u0026quot; + str(t.month))\r\n        \r\n    \r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"contour-map-module\"\u003eContour Map Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripscontour_mapcontourmappdm_object-project-map_type\"\u003eclass rips.contour_map.ContourMap(pdm_object, project, map_type)\u003c/h4\u003e\n\u003cp\u003eResInsight contour map class\u003c/p\u003e\n\u003ch4 id=\"view_id\"\u003eview_id()\u003c/h4\u003e\n\u003cp\u003eView Id corresponding to the View Id in ResInsight project.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_to_textexport_file_name-export_local_coordinatesfalse-undefined_value_labelnan-exclude_undefined_valuesfalse\"\u003eexport_to_text(export_file_name=\u0026rsquo;', export_local_coordinates=False, undefined_value_label='NaN\u0026rsquo;, exclude_undefined_values=False)\u003c/h4\u003e\n\u003cp\u003eExport snapshot for the current view\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexport_file_name\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The file location to store results in.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexport_local_coordinates\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; Should we export local coordinates, or UTM.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eundefined_value_label\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Replace undefined values with this label.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexclude_undefined_values\u003c/strong\u003e (\u003cem\u003ebool\u003c/em\u003e) \u0026ndash; Skip undefined values.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch1 id=\"grid-module\"\u003eGrid Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripsgridgridindex-case-channel\"\u003eclass rips.grid.Grid(index, case, channel)\u003c/h4\u003e\n\u003cp\u003eGrid Information. Not meant to be constructed separately\u003c/p\u003e\n\u003cp\u003eCreate Grid objects using mathods on Case: Grid() and Grids()\u003c/p\u003e\n\u003ch4 id=\"dimensions\"\u003edimensions()\u003c/h4\u003e\n\u003cp\u003eThe dimensions in i, j, k direction\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eclass with integer attributes i, j, k giving extent in all three dimensions.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturn type\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eVec3i\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"example-2\"\u003eExample\u003c/h2\u003e\n\u003cpre\u003e\u003ccode\u003e    case = rips_instance.project.loadCase(path=casePath)\r\nprint (case.gridCount())\r\n    if case.gridCount() \u0026gt; 0:\r\n            grid = case.grid(index=0)\r\n            dimensions = grid.dimensions()\r\n            print(dimensions.i)\r\n            print(dimensions.j)\r\n            print(dimensions.k)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch1 id=\"gridcasegroup-module\"\u003eGridCaseGroup Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripsgridcasegroupgridcasegrouppdm_object\"\u003eclass rips.gridcasegroup.GridCaseGroup(pdm_object)\u003c/h4\u003e\n\u003cp\u003eResInsight Grid Case Group class\u003c/p\u003e\n\u003cp\u003eOperate on a ResInsight case group specified by a Case Group Id integer.\u003c/p\u003e\n\u003ch4 id=\"group_id-1\"\u003egroup_id()\u003c/h4\u003e\n\u003cp\u003eGrid Case Group Id corresponding to case group Id in ResInsight project.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"compute_statisticscase_idsnone\"\u003ecompute_statistics(case_ids=None)\u003c/h4\u003e\n\u003cp\u003eCompute statistics for the given case ids\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ecase_ids\u003c/strong\u003e (\u003cem\u003elist of integers\u003c/em\u003e) \u0026ndash; list of case ids.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ethis is None all cases in group are included\u003c/strong\u003e (\u003cem\u003eIf\u003c/em\u003e) \u0026ndash;\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"create_statistics_case\"\u003ecreate_statistics_case()\u003c/h4\u003e\n\u003cp\u003eCreate a Statistics case in the Grid Case Group\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA new Case\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"statistics_cases\"\u003estatistics_cases()\u003c/h4\u003e\n\u003cp\u003eGet a list of all statistics cases in the Grid Case Group\u003c/p\u003e\n\u003ch4 id=\"viewview_id-1\"\u003eview(view_id)\u003c/h4\u003e\n\u003cp\u003eGet a particular view belonging to a case group by providing view id\n:param id: view id\n:type id: int\u003c/p\u003e\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\u003ch4 id=\"views-1\"\u003eviews()\u003c/h4\u003e\n\u003cp\u003eGet a list of views belonging to a grid case group\u003c/p\u003e\n\u003ch1 id=\"project-module\"\u003eProject Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripsprojectprojectchannel\"\u003eclass rips.project.Project(channel)\u003c/h4\u003e\n\u003cp\u003eResInsight project. Not intended to be created separately.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"casecase_id\"\u003ecase(case_id)\u003c/h4\u003e\n\u003cp\u003eGet a specific case from the provided case Id\u003c/p\u003e\n\u003ch4 id=\"compute_statisticscase_idsnone-1\"\u003ecompute_statistics(case_ids=None)\u003c/h4\u003e\n\u003cp\u003eCompute statistics for the given case ids\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ecase_ids\u003c/strong\u003e (\u003cem\u003elist of integers\u003c/em\u003e) \u0026ndash; list of case ids.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ethis is None all cases in group are included\u003c/strong\u003e (\u003cem\u003eIf\u003c/em\u003e) \u0026ndash;\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"create_statistics_case-1\"\u003ecreate_statistics_case()\u003c/h4\u003e\n\u003cp\u003eCreate a Statistics case in the Grid Case Group\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA new Case\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"statistics_cases-1\"\u003estatistics_cases()\u003c/h4\u003e\n\u003cp\u003eGet a list of all statistics cases in the Grid Case Group\u003c/p\u003e\n\u003ch4 id=\"contour_mapsmap_typecontourmaptypeeclipse-1-1\"\u003econtour_maps(map_type=\u0026lt;ContourMapType.ECLIPSE: 1\u0026gt;)\u003c/h4\u003e\n\u003cp\u003eGet a list of all contour maps belonging to a project\u003c/p\u003e\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\u003ch4 id=\"create_grid_case_groupcase_paths\"\u003ecreate_grid_case_group(case_paths)\u003c/h4\u003e\n\u003cp\u003eCreate a Grid Case Group from a list of cases\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003ecase_paths\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of file path strings\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA case group id and name\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_multi_case_snapshotsgrid_list_file\"\u003eexport_multi_case_snapshots(grid_list_file)\u003c/h4\u003e\n\u003cp\u003eExport snapshots for a set of cases\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003egrid_list_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Path to a file containing a list of grids to export snapshot for\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_snapshotssnapshot_typeall-prefix\"\u003eexport_snapshots(snapshot_type='ALL\u0026rsquo;, prefix=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eExport all snapshots of a given type\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003esnapshot_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Enum string (\u0026lsquo;ALL\u0026rsquo;, \u0026lsquo;VIEWS\u0026rsquo; or \u0026lsquo;PLOTS\u0026rsquo;)\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_well_pathswell_pathsnone-md_step_size50\"\u003eexport_well_paths(well_paths=None, md_step_size=5.0)\u003c/h4\u003e\n\u003cp\u003eExport a set of well paths\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_paths\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of strings of well paths. If none, export all.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003emd_step_size\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; resolution of the exported well path\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"grid_case_groupgroup_id\"\u003egrid_case_group(group_id)\u003c/h4\u003e\n\u003cp\u003eGet a particular grid case group belonging to a project\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003egroupId\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; group id\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"create_grid_case_groupcase_paths-1\"\u003ecreate_grid_case_group(case_paths)\u003c/h4\u003e\n\u003cp\u003eCreate a Grid Case Group from a list of cases\u003c/p\u003e\n\u003cp\u003eReturns: a grid case group object\u003c/p\u003e\n\u003ch4 id=\"grid_case_groups\"\u003egrid_case_groups()\u003c/h4\u003e\n\u003cp\u003eGet a list of all grid case groups in the project\u003c/p\u003e\n\u003ch4 id=\"import_formation_namesformation_filesnone-1\"\u003eimport_formation_names(formation_files=None)\u003c/h4\u003e\n\u003cp\u003eImport formation names into project\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eformation_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; list of files to import\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_multi_case_snapshotsgrid_list_file-1\"\u003eexport_multi_case_snapshots(grid_list_file)\u003c/h4\u003e\n\u003cp\u003eExport snapshots for a set of cases\u003c/p\u003e\n\u003ch4 id=\"import_well_log_fileswell_log_filesnone-well_log_folder\"\u003eimport_well_log_files(well_log_files=None, well_log_folder=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eImport well log files into project\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_log_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of file paths to import\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_log_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; A folder path containing files to import\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA list of well path names (strings) that had logs imported\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"import_well_pathswell_path_filesnone-well_path_folder\"\u003eimport_well_paths(well_path_files=None, well_path_folder=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eImport well paths into project\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_path_files\u003c/strong\u003e (\u003cem\u003elist\u003c/em\u003e) \u0026ndash; List of file paths to import\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ewell_path_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; A folder path containing files to import\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA list of well path names (strings)\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eReturns: a grid case group object\u003c/p\u003e\n\u003ch4 id=\"load_casepath\"\u003eload_case(path)\u003c/h4\u003e\n\u003cp\u003eLoad a new case from the given file path\u003c/p\u003e\n\u003ch4 id=\"grid_case_groups-1\"\u003egrid_case_groups()\u003c/h4\u003e\n\u003cp\u003eGet a list of all grid case groups in the project\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e**path** (*str*) -- file path to case\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA rips Case object\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"openpath\"\u003eopen(path)\u003c/h4\u003e\n\u003cp\u003eOpen a new project from the given path\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003epath\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to project file\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"plotview_id\"\u003eplot(view_id)\u003c/h4\u003e\n\u003cp\u003eGet a particular plot by providing view id\n:param view_id: view id\n:type view_id: int\u003c/p\u003e\n\u003cp\u003eReturns: a plot object\u003c/p\u003e\n\u003ch4 id=\"plots\"\u003eplots()\u003c/h4\u003e\n\u003cp\u003eGet a list of all plots belonging to a project\u003c/p\u003e\n\u003ch4 id=\"replace_source_casesgrid_list_file-case_group_id0\"\u003ereplace_source_cases(grid_list_file, case_group_id=0)\u003c/h4\u003e\n\u003cp\u003eReplace all source cases within a case group\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003egrid_list_file\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; path to file containing a list of cases\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ecase_group_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; id of the case group to replace\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"savepath\"\u003esave(path=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eSave the project to the existing project file, or to a new file\n:param path: File path to the file to save the project to. If empty, saves to the active project file\n:type path: str\u003c/p\u003e\n\u003ch4 id=\"scale_fracture_templatetemplate_id-half_length-height-d_factor-conductivity\"\u003escale_fracture_template(template_id, half_length, height, d_factor, conductivity)\u003c/h4\u003e\n\u003cp\u003eScale fracture template parameters\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etemplate_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; ID of fracture template\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ehalf_length\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Half Length scale factor\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eheight\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Height scale factor\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ed_factor\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; D-factor scale factor\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003econductivity\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Conductivity scale factor\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"selected_cases\"\u003eselected_cases()\u003c/h4\u003e\n\u003cp\u003eGet a list of all cases selected in the project tree\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReturns\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA list of rips Case objects\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"set_fracture_containmenttemplate_id-top_layer-base_layer\"\u003eset_fracture_containment(template_id, top_layer, base_layer)\u003c/h4\u003e\n\u003cp\u003eSet fracture template containment parameters\u003c/p\u003e\n\u003ch4 id=\"set_fracture_containmenttemplate_id-top_layer-base_layer-1\"\u003eset_fracture_containment(template_id, top_layer, base_layer)\u003c/h4\u003e\n\u003cp\u003eSet fracture template containment parameters\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etemplate_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; ID of fracture template\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003etop_layer\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Top layer containment\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ebase_layer\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Base layer containment\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"viewview_id-2\"\u003eview(view_id)\u003c/h4\u003e\n\u003cp\u003eGet a particular view belonging to a case by providing view id\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eview_id\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; view id\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eReturns: a view object\u003c/p\u003e\n\u003ch4 id=\"views-2\"\u003eviews()\u003c/h4\u003e\n\u003cp\u003eGet a list of views belonging to a project\u003c/p\u003e\n\u003ch4 id=\"well_paths\"\u003ewell_paths()\u003c/h4\u003e\n\u003cp\u003eGet a list of all the well path names in the project\u003c/p\u003e\n\u003ch1 id=\"view-module\"\u003eView Module\u003c/h1\u003e\n\u003ch4 id=\"class-ripsviewviewpdm_object-project\"\u003eclass rips.view.View(pdm_object, project)\u003c/h4\u003e\n\u003cp\u003eResInsight view class\u003c/p\u003e\n\u003ch4 id=\"view_id-1\"\u003eview_id()\u003c/h4\u003e\n\u003cp\u003eView Id corresponding to the View Id in ResInsight project.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eType\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eint\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"apply_cell_resultresult_type-result_variable\"\u003eapply_cell_result(result_type, result_variable)\u003c/h4\u003e\n\u003cp\u003eApply a regular cell result\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eresult_type\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing the result category. The valid values are\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eDYNAMIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSTATIC_NATIVE\u003c/li\u003e\n\u003cli\u003eSOURSIMRL\u003c/li\u003e\n\u003cli\u003eGENERATED\u003c/li\u003e\n\u003cli\u003eINPUT_PROPERTY\u003c/li\u003e\n\u003cli\u003eFORMATION_NAMES\u003c/li\u003e\n\u003cli\u003eFLOW_DIAGNOSTICS\u003c/li\u003e\n\u003cli\u003eINJECTION_FLOODING\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eresult_variable\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; String representing the result variable.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"apply_flow_diagnostics_cell_resultresult_variabletof-selection_modeflow_tr_by_selection-injectorsnone-producersnone\"\u003eapply_flow_diagnostics_cell_result(result_variable='TOF\u0026rsquo;, selection_mode='FLOW_TR_BY_SELECTION\u0026rsquo;, injectors=None, producers=None)\u003c/h4\u003e\n\u003cp\u003eApply a flow diagnostics cell result\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eresult_variable\u003c/td\u003e\n\u003ctd\u003eString representing the result value\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eselection_mode\u003c/td\u003e\n\u003ctd\u003eString specifying which tracers to select\u003c/td\u003e\n\u003ctd\u003eString\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003einjectors\u003c/td\u003e\n\u003ctd\u003eList of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString List\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eproducers\u003c/td\u003e\n\u003ctd\u003eList of injector names, used by \u0026lsquo;FLOW_TR_BY_SELECTION\u0026rsquo;\u003c/td\u003e\n\u003ctd\u003eString List\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-compdat_export-1\"\u003eEnum compdat_export\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TOF\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eTime of flight\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;Fraction\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eFraction\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;MaxFractionTracer\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eMax Fraction Tracer\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;Communication\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eCommunication\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"background_color\"\u003ebackground_color()\u003c/h4\u003e\n\u003cp\u003eGet the current background color in the view\u003c/p\u003e\n\u003ch4 id=\"case\"\u003ecase()\u003c/h4\u003e\n\u003cp\u003eGet the case the view belongs to\u003c/p\u003e\n\u003ch4 id=\"clone\"\u003eclone()\u003c/h4\u003e\n\u003cp\u003eClone the current view\u003c/p\u003e\n\u003ch4 id=\"export_propertyundefined_value00\"\u003eexport_property(undefined_value=0.0)\u003c/h4\u003e\n\u003cp\u003eExport the current Eclipse property from the view\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eundefined_value\u003c/strong\u003e (\u003cem\u003edouble\u003c/em\u003e) \u0026ndash; Value to use for undefined values. Defaults to 0.0\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_sim_well_fracture_completionstime_step-simulation_well_names-file_split-compdat_export\"\u003eexport_sim_well_fracture_completions(time_step, simulation_well_names, file_split, compdat_export)\u003c/h4\u003e\n\u003cp\u003eExport fracture completions for simulation wells\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eType\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003etime_step\u003c/td\u003e\n\u003ctd\u003eTime step to export for\u003c/td\u003e\n\u003ctd\u003eInteger\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esimulation_well_names\u003c/td\u003e\n\u003ctd\u003eList of simulation well names\u003c/td\u003e\n\u003ctd\u003eList\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efile_split\u003c/td\u003e\n\u003ctd\u003eControls how export data is split into files\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecompdat_export\u003c/td\u003e\n\u003ctd\u003eCompdat export type\u003c/td\u003e\n\u003ctd\u003eString enum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-file_split-2\"\u003eEnum file_split\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;UNIFIED_FILE\u0026rdquo; \u003c!-- raw HTML omitted --\u003eDefault Option\u003c!-- raw HTML omitted --\u003e\u003c/td\u003e\n\u003ctd\u003eA single file with all transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each well transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;SPLIT_ON_WELL_AND_COMPLETION_TYPE\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eOne file for each completion type for each well\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch5 id=\"enum-compdat_export-2\"\u003eEnum compdat_export\u003c/h5\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;TRANSMISSIBILITIES\u0026quot;\u003c!-- raw HTML omitted --\u003eDefault Option\u003c!-- raw HTML omitted --\u003e\u003c/td\u003e\n\u003ctd\u003eDirect export of transmissibilities\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u0026ldquo;WPIMULT_AND_DEFAULT_CONNECTION_FACTORS\u0026rdquo;\u003c/td\u003e\n\u003ctd\u003eInclude export of WPIMULT\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"export_snapshotprefix-export_folder\"\u003eexport_snapshot(prefix=\u0026rsquo;', export_folder=\u0026rsquo;')\u003c/h4\u003e\n\u003cp\u003eExport snapshot for the current view\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eprefix\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; Exported file name prefix\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexport_folder\u003c/strong\u003e (\u003cem\u003estr\u003c/em\u003e) \u0026ndash; The path to export to. By default will use the global export folder\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"export_visible_cellsexport_keywordfluxnum-visible_active_cells_value1-hidden_active_cells_value0-inactive_cells_value0\"\u003eexport_visible_cells(export_keyword='FLUXNUM\u0026rsquo;, visible_active_cells_value=1, hidden_active_cells_value=0, inactive_cells_value=0)\u003c/h4\u003e\n\u003cp\u003eExport special properties for all visible cells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eParameters\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eexport_keyword\u003c/strong\u003e (\u003cem\u003estring\u003c/em\u003e) \u0026ndash; The keyword to export.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eChoices\u003c/strong\u003e \u0026ndash; \u0026lsquo;FLUXNUM\u0026rsquo; or \u0026lsquo;MULTNUM\u0026rsquo;. Default: \u0026lsquo;FLUXNUM\u0026rsquo;\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003evisible_active_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export forvisible active cells. Default: 1\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ehidden_active_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export for hidden active cells. Default: 0\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003einactive_cells_value\u003c/strong\u003e (\u003cem\u003eint\u003c/em\u003e) \u0026ndash; Value to export for inactive cells. Default: 0\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"set_background_colorbgcolor\"\u003eset_background_color(bgcolor)\u003c/h4\u003e\n\u003cp\u003eSet the background color in the view\u003c/p\u003e\n\u003ch4 id=\"set_cell_result\"\u003eset_cell_result()\u003c/h4\u003e\n\u003cp\u003eRetrieve the current cell results\u003c/p\u003e\n\u003ch4 id=\"set_show_grid_boxvalue\"\u003eset_show_grid_box(value)\u003c/h4\u003e\n\u003cp\u003eSet if the grid box is meant to be shown in the view\u003c/p\u003e\n\u003ch4 id=\"set_time_steptime_step\"\u003eset_time_step(time_step)\u003c/h4\u003e\n\u003cp\u003eSet the time step for current view\u003c/p\u003e\n\u003ch4 id=\"show_grid_box\"\u003eshow_grid_box()\u003c/h4\u003e\n\u003cp\u003eCheck if the grid box is meant to be shown in the view\u003c/p\u003e\n\u003ch2 id=\"synchronous-example\"\u003eSynchronous Example\u003c/h2\u003e\n\u003cp\u003eRead two properties, multiply them together and push the results back to ResInsight in a naïve way, by reading PORO into a list, then reading PERMX into a list, then multiplying them both in a resulting list and finally transferring back the list.\u003c/p\u003e\n\u003cp\u003eThis is slow and inefficient, but works.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eimport rips\r\nimport time\r\n\r\n# Internal function for creating a result from a small chunk of poro and permx results\r\n# The return value of the function is a generator for the results rather than the result itself.\r\ndef create_result(poro_chunks, permx_chunks):\r\n    # Loop through all the chunks of poro and permx in order\r\n    for (poroChunk, permxChunk) in zip(poro_chunks, permx_chunks):\r\n        resultChunk = []\r\n        # Loop through all the values inside the chunks, in order\r\n        for (poro, permx) in zip(poroChunk.values, permxChunk.values):\r\n            resultChunk.append(poro * permx)\r\n        # Return a generator object that behaves like a Python iterator\r\n        yield resultChunk\r\n\r\nresinsight     = rips.Instance.find()\r\nstart = time.time()\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Get a generator for the poro results. The generator will provide a chunk each time it is iterated\r\nporo_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PORO', 0)\r\n# Get a generator for the permx results. The generator will provide a chunk each time it is iterated\r\npermx_chunks = case.active_cell_property_async('STATIC_NATIVE', 'PERMX', 0)\r\n\r\n# Send back the result with the result provided by a generator object.\r\n# Iterating the result generator will cause the script to read from the poro and permx generators\r\n# And return the result of each iteration\r\ncase.set_active_cell_property_async(create_result(poro_chunks, permx_chunks),\r\n                                           'GENERATED', 'POROPERMXAS', 0)\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXAS')\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch2 id=\"asynchronous-example\"\u003eAsynchronous Example\u003c/h2\u003e\n\u003cp\u003eRead two properties at the same time chunk by chunk, multiply each chunk together and start transferring the result back to ResInsight as soon as the chunk is finished.\u003c/p\u003e\n\u003cp\u003eThis is far more efficient.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e########################################################################################\r\nimport rips\r\nimport time\r\nimport grpc\r\n\r\nresinsight     = rips.Instance.find()\r\nstart = time.time()\r\ncase = resinsight.project.cases()[0]\r\n\r\n# Read poro result into list\r\nporo_results = case.active_cell_property('STATIC_NATIVE', 'PORO', 0)\r\n# Read permx result into list\r\npermx_results = case.active_cell_property('STATIC_NATIVE', 'PERMX', 0)\r\n\r\n# Generate output result\r\nresults = []\r\nfor (poro, permx) in zip(poro_results, permx_results):\r\n    results.append(poro * permx)\r\n\r\ntry:\r\n    # Send back output result\r\n    case.set_active_cell_property(results, 'GENERATED', 'POROPERMXSY', 0)\r\nexcept grpc.RpcError as e:\r\n    print(\u0026quot;Exception Received: \u0026quot;, e)\r\n\r\n\r\nend = time.time()\r\nprint(\u0026quot;Time elapsed: \u0026quot;, end - start)\r\nprint(\u0026quot;Transferred all results back\u0026quot;)\r\n\r\nview = case.views()[0].apply_cell_result('GENERATED', 'POROPERMXSY')\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/scripting/pythonrips/"
             };
         
@@ -2236,7 +2269,7 @@ if (!doNotTrack) {
             window.store["/scripting/pythonconfiguration/"] = {
                 title:    "Python Configuration",
                 content:  "ResInsight has a gRPC Remote Procedure Call interface with a Python Client interface. This interface allows you to interact with a running ResInsight instance from a Python script. The Python client package is compatible with Python 3.\nThe Python client package is available for install via the Python PIP package system with pip install rips as admin user, or pip install --user rips as a regular user.\nOn some systems the pip command may have to be replaced by python -m pip.\nIn order for gRPC to be available, ResInsight needs to be built with the RESINSIGHT_ENABLE_GRPC option set. A valid gRPC build will show a message in the About dialog confirming gRPC is available:\nFurthermore, gRPC needs to be enabled in the Scripting tab of the Preference dialog:\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight has a \u003ca href=\"https://www.grpc.io/\"\u003egRPC Remote Procedure Call\u003c/a\u003e interface with a Python Client interface. This interface allows you to interact with a running ResInsight instance from a Python script. The Python client package is compatible with \u003cstrong\u003ePython 3\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe Python client package is available for install via the Python PIP package system with \u003ccode\u003epip install rips\u003c/code\u003e as admin user, or \u003ccode\u003epip install --user rips\u003c/code\u003e as a regular user.\u003c/p\u003e\n\n\u003cp\u003eOn some systems the \u003ccode\u003epip\u003c/code\u003e command may have to be replaced by \u003ccode\u003epython -m pip\u003c/code\u003e.\u003c/p\u003e\n\n\u003cp\u003eIn order for gRPC to be available, ResInsight needs to be built with the \u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e option set. A valid gRPC build will show a message in the About dialog confirming gRPC is available:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/AboutGrpc.png\" alt=\"image\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFurthermore, gRPC needs to be enabled in the Scripting tab of the Preference dialog:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/PrefGrpc.png\" alt=\"image\" /\u003e\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight has a \u003ca href=\"https://www.grpc.io/\"\u003egRPC Remote Procedure Call\u003c/a\u003e interface with a Python Client interface. This interface allows you to interact with a running ResInsight instance from a Python script. The Python client package is compatible with \u003cstrong\u003ePython 3\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe Python client package is available for install via the Python PIP package system with \u003ccode\u003epip install rips\u003c/code\u003e as admin user, or \u003ccode\u003epip install --user rips\u003c/code\u003e as a regular user.\u003c/p\u003e\n\u003cp\u003eOn some systems the \u003ccode\u003epip\u003c/code\u003e command may have to be replaced by \u003ccode\u003epython -m pip\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eIn order for gRPC to be available, ResInsight needs to be built with the \u003ccode\u003eRESINSIGHT_ENABLE_GRPC\u003c/code\u003e option set. A valid gRPC build will show a message in the About dialog confirming gRPC is available:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/AboutGrpc.png\" alt=\"image\"\u003e\u003c/p\u003e\n\u003cp\u003eFurthermore, gRPC needs to be enabled in the Scripting tab of the Preference dialog:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/PrefGrpc.png\" alt=\"image\"\u003e\u003c/p\u003e\n",
                 url:      "/scripting/pythonconfiguration/"
             };
         
@@ -2244,8 +2277,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryplottemplate/"] = {
                 title:    "Summary Plot Template",
-                content:  " Template creation A summary plot template is defined by a number of curves with preset appearance and vector names. The parameters that are selected or varied by the user are:\n case(s) item(s), i.e. well(s), group(s), region(s)  Having tailored a plot setup, the user can save the setup as a template via the context command Save As Plot Template, c.f. figure above. It is also possible to select a summary plot in the Plot Project Tree and use the context menu to save a template. Both options save a template definition to file for later reuse.\nSummary Plot Templates are created for all Summary Plots including ensemble plots by context menu option Save As Plot Template available in both the plot window and via their entries in the Plot Project Tree.\n\rGiven a new path, ResInsight will ask the user to confirm whether the path of the stored template is to be included in subsequent searches for templates.\nTemplate usage Having selected items of interest in the Plot Project Tree (i.e. cases, wells, groups, and regions) a template plot can be created.\nInvoke the context menu shown below to select a specific summary plot template. Here two summary cases have been selected prior to invoking the context menu. As seen, available options for select a specific template are:\n Create Plot from Last Used Summary Template is a menu option to invoke the last used summary plot template. Create Plot from Template shows all available templates in a separate dialog for search and selection.  Ctrl-T is a shortcut to swiftly create a plot based on the last used summary template.\n\rTemplate file search and organization Each summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which can be managed by menu option Edit-\u0026gt;Preferences and the Plotting tab.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"template-creation\"\u003eTemplate creation\u003c/h2\u003e\n\n\u003cp\u003eA summary plot template is defined by a number of curves with preset appearance and vector names.\nThe parameters that are selected or varied by the user are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003ecase(s)\u003c/li\u003e\n\u003cli\u003eitem(s), i.e. well(s), group(s), region(s)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eHaving tailored a plot setup, the user can save the setup as a template via the context command \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e, c.f. figure above. It is also possible to select a summary plot in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and use the context menu to save a template.\nBoth options save a template definition to file for later reuse.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSummary Plot Templates are created for all \u003cem\u003eSummary Plots\u003c/em\u003e including ensemble plots by context menu option \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e available in both the plot window and via their entries in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003cp\u003eGiven a new path, ResInsight will ask the user to confirm whether the path of the stored template is to be included in subsequent searches for templates.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplatePath.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"template-usage\"\u003eTemplate usage\u003c/h2\u003e\n\n\u003cp\u003eHaving selected items of interest in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e (i.e. cases, wells, groups, and regions) a template plot can be created.\u003c/p\u003e\n\n\u003cp\u003eInvoke the context menu shown below to select a specific summary plot template.\nHere two summary cases have been selected prior to invoking the context menu.\nAs seen, available options for select a specific template are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Plot from Last Used Summary Template\u003c/strong\u003e  is a menu option to invoke the last used summary plot template.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Plot from Template\u003c/strong\u003e shows all available templates in a separate dialog for search and selection.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateUsage.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cstrong\u003eCtrl-T\u003c/strong\u003e is a shortcut to swiftly create a plot based on the last used summary template.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"template-file-search-and-organization\"\u003eTemplate file search and organization\u003c/h2\u003e\n\n\u003cp\u003eEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files\nwhich can be managed by menu option \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e and the \u003ca href=\"/misc/preferences/#plotting-tab\"\u003e\u003cstrong\u003ePlotting tab\u003c/strong\u003e\u003c/a\u003e.\u003c/p\u003e\n",
+                content:  "Template creation A summary plot template is defined by a number of curves with preset appearance and vector names. The parameters that are selected or varied by the user are:\n case(s) item(s), i.e. well(s), group(s), region(s)  Having tailored a plot setup, the user can save the setup as a template via the context command Save As Plot Template, c.f. figure above. It is also possible to select a summary plot in the Plot Project Tree and use the context menu to save a template. Both options save a template definition to file for later reuse.\nSummary Plot Templates are created for all Summary Plots including ensemble plots by context menu option Save As Plot Template available in both the plot window and via their entries in the Plot Project Tree.\n\rGiven a new path, ResInsight will ask the user to confirm whether the path of the stored template is to be included in subsequent searches for templates.\nTemplate usage Having selected items of interest in the Plot Project Tree (i.e. cases, wells, groups, and regions) a template plot can be created.\nInvoke the context menu shown below to select a specific summary plot template. Here two summary cases have been selected prior to invoking the context menu. As seen, available options for select a specific template are:\n Create Plot from Last Used Summary Template is a menu option to invoke the last used summary plot template. Create Plot from Template shows all available templates in a separate dialog for search and selection.  Ctrl-T is a shortcut to swiftly create a plot based on the last used summary template.\n\rTemplate file search and organization Each summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which can be managed by menu option Edit-\u0026gt;Preferences and the Plotting tab.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"template-creation\"\u003eTemplate creation\u003c/h2\u003e\n\u003cp\u003eA summary plot template is defined by a number of curves with preset appearance and vector names. \nThe parameters that are selected or varied by the user are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecase(s)\u003c/li\u003e\n\u003cli\u003eitem(s), i.e. well(s), group(s), region(s)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eHaving tailored a plot setup, the user can save the setup as a template via the context command \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e, c.f. figure above. It is also possible to select a summary plot in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and use the context menu to save a template. \nBoth options save a template definition to file for later reuse.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eSummary Plot Templates are created for all \u003cem\u003eSummary Plots\u003c/em\u003e including ensemble plots by context menu option \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e available in both the plot window and via their entries in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eGiven a new path, ResInsight will ask the user to confirm whether the path of the stored template is to be included in subsequent searches for templates.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplatePath.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"template-usage\"\u003eTemplate usage\u003c/h2\u003e\n\u003cp\u003eHaving selected items of interest in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e (i.e. cases, wells, groups, and regions) a template plot can be created.\u003c/p\u003e\n\u003cp\u003eInvoke the context menu shown below to select a specific summary plot template. \nHere two summary cases have been selected prior to invoking the context menu.\nAs seen, available options for select a specific template are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Plot from Last Used Summary Template\u003c/strong\u003e  is a menu option to invoke the last used summary plot template.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Plot from Template\u003c/strong\u003e shows all available templates in a separate dialog for search and selection.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateUsage.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cstrong\u003eCtrl-T\u003c/strong\u003e is a shortcut to swiftly create a plot based on the last used summary template.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"template-file-search-and-organization\"\u003eTemplate file search and organization\u003c/h2\u003e\n\u003cp\u003eEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files\nwhich can be managed by menu option \u003cstrong\u003eEdit-\u0026gt;Preferences\u003c/strong\u003e and the \u003ca href=\"/misc/preferences/#plotting-tab\"\u003e\u003cstrong\u003ePlotting tab\u003c/strong\u003e\u003c/a\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryplottemplate/"
             };
         
@@ -2253,8 +2286,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/completions/"] = {
                 title:    "Completions",
-                content:  " Three types of completions are available for modeling and export: Perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.\nCompletions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword. See Export Completions\nFor fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV, c.f. Export Well Segments.\nThe derived cell property Completion Type displays wich cells are intersected by the completions.\n\rVisualization and Inspection of Well Connection Factors Connection factors both from the Simulation Wells and the ones calculated from the modeled completions can be visualized in the 3D view by enabling Well Connection Factors in the Project Tree. The connection factors are displayed with a symbol as in the example shown above. The color of the symbol displays the magnitude of the connection factor and can be controlled by the legend settings. Additional details of the connection factor are displayed in the Result Info window when clicking on the connection factor symbol.\nThe Property Panel of the Well Connection Factors item has a few options:\n Geometry Scale Factor \u0026ndash; Scales the connection factor symbols relative to the displayed well path radius Show on Closed Connections \u0026ndash; Show the connection factors calculated for closed simulation well cells in addition to the ones at open cells.  A combined view of well connection factors and the derived result Completion Type enables the user to see the completion type contributing to connection factor in a cell.\nPerforation Intervals A new perforation interval on a well can be set up by right-clicking on the well in the 3D View or in the Project Tree, and choosing the command Create Perforation interval in the Create Completions sub-menu. In the 3D View the completion will be created at the specific depth the right-click occured at.\nAfter creating the perforation interval, the following properties of the perforation can be set in the property editor:\n Start MD, End MD \u0026ndash; Measured depth along the well path for the perforation to start/stop. Diameter \u0026ndash; Well bore diameter for the perforation interval, used in calculation of transmissibility ( For details on the transmissibility calculation, see Transmissibility Calculations). Skin Factor \u0026ndash; Skin factor for the perforation, used in calculation of transmissibility. All Timesteps \u0026ndash; If on, the perforation interval will be present for all time steps Start Date \u0026ndash; The perforation will be included in the model for all time steps after this date. If \u0026ldquo;All TimeSteps\u0026rdquo; is turned on, this option is not available and the perforation is included for all time steps.  The perforation intervals will be indicated by different color along the well path.\nFor each well path there is a top level folder in the Project Tree containing all the perforation intervals definitions containing settings that applies to all the perforation intervals for this well path.\nFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\n Multi Segment Well Options - Options used by the Well Segments Export  Liner Inner Diameter \u0026ndash; The liner inner diameter for the completion intervals. Roughness Factor \u0026ndash; The roughness factor used in export of main bore segments. Pressure Drop \u0026ndash; can be either Hydrostatic, Hydrostatic + Friction or Hydrostatic + Friction + Acceleration. Length and Depth \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment Incremental \u0026ndash; length / depth of given segment Absolute \u0026ndash; the length down the tube or depth of the last nodal point Enforce Max Segment Length \u0026ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.    There are three options for Non-Darcy Flow. None, User defined D-factor and Compute D-factor. The second option displays an input field where the user defined D-factor can be entered. The last options calculates D-factor for gas given Dake´s (1976) radiel inflow model and correlation for calculating matrix beta factor depending on permeability and porosity.\n Non-Darcy Flow - Non-Darcy settings for D factor computation  Grid Permeability Kr Scaling Factor \u0026ndash; Rel.perm. scaling factor to calculate effective permeability. Well Radius \u0026ndash; Well bore radius. Relative Gas Density Gas Viscosity \u0026ndash; Gas viscosity at flowing bottom hole pressure. Inertial Coefficient \u0026ndash; Coefficient to calculate beta factor. Permeability Scaling Exponent \u0026ndash; For beta factor calculation. Porosity Scaling Exponent \u0026ndash; For beta factor calculation.    Perforation Interval Valves Perforation Intervals can have valves (ICDs/AICDs/ICVs) associated with them.\nThese valves can be created by right-clicking on the Perforation Interval and selecting Create Valve.\nEach Valve require a Valve Template containing properties which can be shared among multiple Valves. If you have no Valve Template, a new one can be created by clicking the New button next to the Valve Template selection list.\nThis will create a new Valve Template which can be of three different types:\n ICD - In-flow Control Device, allowing the setting of Orifice Diameter and Flow Coefficient. ICDs are displayed in Orange. AICD - Autonomous In-flow Control Device, providing several more parameters associated with the Eclipse simulation and seen in the picture below. AICDs are displayed in Dark Purple. ICV - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.   An example of the ICD parameters can be seen below: An example of the AICD parameters: New templates can also be added by selecting the New Valve Template option from the right-click menu of the Valve Templates entry in the Completion Templates Project Tree item.\nFor ICDs and AICDs, multiple valves can be added in the same go by specifying the number of valves, spacing of valves or specific positions of valves as chosen in the Location Defined By drop down list.\nFor ICVs only one valve is added at a time so only the measured depth of that valve can be chosen.\nWhen you have a valid valve template selected, there is an Edit button next to the valve template selection. Clicking this will take you straight to modify the valve template.\nImport Perforation Intervals Perforation intervals can be imported into ResInsight from *.ev files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.\nPerforation Interval File Format \u0026rdquo;\u0026ndash;\u0026rdquo; is interpreted as the start of a comment. The comment ends at the end of the line. The files can start with a unit definition line:\nUNITS \u0026lt;unitname\u0026gt;  This line is ignored for now. The numbers are interpreted to be in the units present in the case.\n\rIn the following any number of :\nWELLNAME \u0026lt;well-name\u0026gt; \u0026lt;date\u0026gt; \u0026lt;well completion\u0026gt; \u0026lt;top mMD\u0026gt; \u0026lt;base mMD\u0026gt; \u0026lt;bore hole diameter\u0026gt; \u0026lt;skin factor\u0026gt; \u0026lt;date\u0026gt; \u0026lt;well completion\u0026gt; \u0026lt;top mMD\u0026gt; \u0026lt;base mMD\u0026gt; \u0026lt;bore hole diameter\u0026gt; \u0026lt;skin factor\u0026gt;   date \u0026ndash; Start date of the completion in the format \u0026ldquo;dd mmm yyyy\u0026rdquo;. Eg 01 SEP 2006. A special \u0026quot;SOH\u0026quot;date is also allowed meaning Start Of History. well completion \u0026ndash; For now, only \u0026quot;perforation\u0026quot; is supported  Here is an example:\nUNITS METRIC -- R-2 AH sidetrack into Ile/Tilje WELLNAME R-2AH \u0026quot;SOH\u0026quot; perforation 6200 6350 0.212 0 -- taget Ile 2 and Ile 3 \u0026quot;SOH\u0026quot; perforation 7050 7133 0.212 0 -- target Tilje 3, 83 m prodint -- S-2 AH WELLNAME S-2AH \u0026quot;SOH\u0026quot; perforation 4340 4369 0.212 0 -- target Garn 2, 29 m prodint (update 290915) 01 SEP 2006 perforation 5060 6185 0.212 0 -- target Tilje 3, 1125 m prodint  Fishbones Fishbones are completions created by drilling or by jetting a set of small lateral holes with a high deviation from the main bore. Each set of holes created at the same location along the main bore, is referred to as a sub while each individual hole is called a lateral.\nFor each well path there is a top level folder in the Project Tree containing all the Fishbones definitions containing settings that applies to all the fishbones for this well path. To make use of the Multi Segment Well option for pressure loss along laterals, the grid resolution needs to be fine enough to allow a grid cell to be connected to only one lateral.\n Fishbone Well Properties \u0026ndash; Settings used when exporting well connection factors  StartMD \u0026ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.\n Main Bore Diameter \u0026ndash; The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore. Main Bore Skin Factor \u0026ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore. For multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.  Multi Segment Wells - Options used by the Well Segments Export  Liner Inner eter \u0026ndash; The liner inner diameter for the fishbones. Roughness Factor \u0026ndash; The roughness factor used in export of main bore segments. Pressure Drop \u0026ndash; can be either Hydrostatic, Hydrostatic + Friction or Hydrostatic + Friction + Acceleration. Length and Depth \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment Incremental \u0026ndash; length / depth of given segment Absolute \u0026ndash; the length down the tube or depth of the last nodal point   Fishbones Subs Definition To add new fishbones completions, select the New Fishbones Subs Definition command. This menu item is available by right clicking on Wells in the Project Tree or right clicking on the well trajectory in the 3D View.\nThe new Fishbones Subs Definition (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 1\u0026frasl;2\u0026rdquo; main bore.\n Appearance  Fishbones Color \u0026ndash; The 3D View color of the fishbones created by this definition  Location \u0026ndash; Options to control the position and number of fishbone subs created by this definition  Location Defined By \u0026ndash; This setting will select how to define the location of the subs in this group. Start MD \u0026ndash; Position, in Measured depth along the well, of the first fishbone Sub. End MD \u0026ndash; Position of the last fishbone Sub. Number of Subs \u0026ndash; Defines the number of subs to create in the defined interval Spacing \u0026ndash; Spacing between the subs within the interval Measured Depths \u0026ndash; The measured depth of each of the fishbone subs. If the Location Defined By is set to the User Specified this will be directly editable by the user.  Laterals Configuration \u0026ndash; Configures the laterals at each sub position.\n Laterals Per Sub \u0026ndash; Number of laterals for each sub position Lenght(s) \u0026ndash; Length of each lateral, in m or ft. Exit Angle \u0026ndash; Exit angle for fishbone lateral, in degree. Build Angle \u0026ndash; Build angle for fishbone lateral, in degree pr meter. Orientation Fixed Angle \u0026ndash; The user can specify the angle for the first lateral Random angle \u0026ndash; Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced. Install Success Rate \u0026ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.\n  Well Properties \u0026ndash; Settings to control the connection factor calculation used in Completion Export)  Hole Diameter \u0026ndash; The hole diameter of the lateral Skin Factor \u0026ndash; The skin factor used in the transmissibility calculation for the lateral.  Multi Segment Wells \u0026ndash; Settings used for Well Segment Export  Tubing Diameter \u0026ndash; The diameter used in the WELSEGS export of the laterals. Open Hole Roughness Factor \u0026ndash; Exported directly to the WELSEGS keyword. Tubing Roughness Factor \u0026ndash; Exported directly to the WELSEGS keyword. ICDs per Sub \u0026ndash; The number of ICD (valves) per Sub, used for calculation of total ICD area for WSEGVALV export. ICD Orifice Diameter \u0026ndash; The Diameter of the ICD, used for calculation of ICD area for WSEGVALV export. ICD Flow Coefficient \u0026ndash; The flow coefficient, exported directly as a part of WSEGVALV.   Import Well Trajectories as Fishbones Laterals The command Import Completions From File can be used to import well trajectories in the *.dev format as fishbone laterals. The imported laterals are listed under the folder Imported Laterals in the Project Tree. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the Imported Laterals folder.\nExport Fishbones as Well Trajectories The Export Laterals command will export the fishbone laterals as a well trajectory into a *.dev* -file.\nNotice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to .dev files.\n\rFractures Hydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formation. A substance is then injected into the crack to keep it open when relaxing the pressure.\nFractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Elliptical fractures and StimPlan fractures.\nVisualization control The Fractures item in the Project Tree controls whether to show the modeled fractures or not. For fractures along the well path the Perforation Length is shown as an olive green cylinder around the well path as shown in the image below.\n Colors \u0026ndash; Control the color settings for the fractures in the View  Result Variable \u0026ndash; Selects the fracture result to use for coloring the fracture. This is most interesting when you have imported a StimPlan fracture with varying width, conductivity and other parameters. The legend item in the Project Tree controls how the legend is set up. Default Color \u0026ndash; The color to use if the requested result is not available for some fracture.  StimPlan  Show Mesh \u0026ndash; Toggles the visualization of the StimPlan mesh lines, showing the StimPlan cell borders Color Interpolation \u0026ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.    Fracture Templates To create a functioning fracture you first need a Fracture Template. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.\nFracture Templates are listed in a folder with the same name in the Project Tree.\nTo create a new fracture template, right-click the Fracture Template item in the tree, and select either New Ellipse Fracture Template or New StimPlan Fracture Template. If you have no existing fracture templates, you will be given the opportunity to create such templates through two buttons in the Fracture Property Editor as seen below.\nCommon Fracture Template Options  Name \u0026ndash; User defined name for the template. Used when selecting which template to use in the Fracture ID \u0026ndash; Assigned ID to be used when addressing this template form a Command file script Geometry  Fracture Orientation \u0026ndash; The fractures orientation Transverse(normal) to Well Path \u0026ndash; The fracture plane is vertical and normal to the well path at the intersection point. Along Well Path \u0026ndash; Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below. Azimuth \u0026ndash; The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.  Fracture Truncation  Use Containment \u0026ndash; Enable this option to activate layer containment. Top Layer \u0026ndash; Topmost K-layer that the fracture will drain. Base Layer \u0026ndash; Lowest K-layer that the fracture will drain. Truncate At Faults \u0026ndash; Enable this option to activate fault truncation. Minimum Fault Throw \u0026ndash; Fault throw threshold to activate fault truncation.  Properties \u0026ndash; The availability of these options depend on the Fracture Orientation and the Conductivity in Fracture setting.  Conductivity in Fracture Finite Conductivity \u0026ndash; Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures. Infinite Conductivity \u0026ndash; Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the StimPlan data. Skin Factor \u0026ndash; Used when exporting to Eclipse. Perforation Length \u0026ndash; The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures Along Well Path only ). Perforation Efficiency \u0026ndash; The efficiency of the wellbore-fracture perforation ( Fractures Along Well Path only ). Well Diameter \u0026ndash; Used when exporting to Eclipse.  Sensitivity Scale Factors \u0026ndash; Each of the properties are scaled by the scaling factor. When used interactively, the Apply button must be pressed to apply the scaling factors. These scaling factors are also available from command file scripting  Height, Width \u0026ndash; Scales the height or the Halflength of the fracture template D-factor \u0026ndash; Scales the none-darcy flow factor Conductivity \u0026ndash; Scales the conductivity in the fracture directly   Non-Darcy Flow Non-Darcy Flow is used to improve the computation of connection factors for cells penetrated by well pipes. A pre-computed D-factor can be set using User Defined D-factor. Selecting the option Compute D-factor displays the following set of properties:\n Inertial Coefficient  User Defined \u0026ndash; Beta-factor in Forcheimer units Use Fracture Beta Factor \u0026ndash; Extract beta factor from the fracture template at the well intersection location. For transversal fractures, the conductivity is computed from the geometric average of fracture cells intersected by the fracture perforation length.  Effective Permeability  User Defined \u0026ndash; Defines the permeability Ke in milliDarcy in the property Effective Permeability Use Fracture Conductivity \u0026ndash; Extract conductivity from the fracture template at the well intersection location and scale with Relative Permeability. For transversal fractures, the conductivity is computed from the weighted average of fracture cells intersected by the fracture perforation length.  Width  User Defined \u0026ndash; Defines the width of the fracture Use Fracture Width \u0026ndash; Extract width from the fracture template at the well intersection location. For transversal fractures, the width is based on the weighted average of fracture cells intersected by the fracture perforation length.  Relative Gas Density Gas Viscosity D Factor \u0026ndash; Displays the computed value of the D factor. NOTE : For transversal fractures, the computed D factor is scaled by 1.2 to compensate for a different flow model D Factor Details \u0026ndash; Displays the value of variables used to compute the D factor  Ellipse Fracture Template  Name \u0026ndash; User name of this particular fracture template Geometry  Halflength Xr \u0026ndash; Half the width of the ellipse Height \u0026ndash; The height of the elliptical fracture Fracture Orientation \u0026ndash; See above  Fracture Truncation \u0026ndash; See above Properties \u0026ndash; The availability of these options depend on the Fracture Orientation and the Conductivity in Fracture setting  Permeability \u0026ndash; A constant permeability inside the fracture (Used to calculate conductivity in the fracture) Width \u0026ndash; Crack width (Used to calculate conductivity in the fracture)  Sensivity Scale Factors \u0026ndash; See above Non-Darcy Flow \u0026ndash; See above  Stimplan Fracture Template StimPlan fracture templates imports XML output from the StimPlan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting conductivity etc. as time varying quantities. Both symmetric and asymmetric StimPlan fracture templates are supported.\n Name \u0026ndash; User name of this particular fracture template Show StimPlan Mesh \u0026ndash; Show or hide the mesh lines on the fracture in the 3D View Input  File Name \u0026ndash; Path to the imported StimPlan XML-file Active Time step Index \u0026ndash; Time step in the StimPlan simulation to use for transmissibility calculations and visualization Well/fracture Intersection Depth \u0026ndash; The position of the fracture along the well path as MD.  Geometry  Fracture Orientation \u0026ndash; See above  Fracture Truncation \u0026ndash; See above Properties  Conductivity Scaling Factor \u0026ndash; Scale the overall conductivity to do sensitivity studies.  Sensitivity Scale Factors \u0026ndash; See above Non-Darcy Flow \u0026ndash; See above  Fracture Instances Instances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the Project Tree.\n Name \u0026ndash; User editable name Fracture Template \u0026ndash; Select the fracture template to use for this fracture. Click the Edit shortcut next to the template selection list to go directly to modify the selected template. Location/Orientation  Measured depth Location \u0026ndash; The measured depth Azimuth \u0026ndash; Azimuth orientation of fracture. Dip \u0026ndash; Dip of fracture plane Tilt \u0026ndash; Rotation of fracture about its plane normal  Properties  Fracture Unit System \u0026ndash; Read only display of the units used for the current template StimPlan Time Step \u0026ndash; Displays the time step used by the template Perforation Length / Perforation Efficiency / Well Diameter \u0026ndash; These values are copied from the new template when selecting a different one. See Common Fracture Template Options\n  Fracture Center Info \u0026ndash; This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.  Multiple Fracture Creation In some cases the user wants to create a number of fractures on one or more well paths. Doing this by creating one by one fracture can be very error prone and time consuming. To ease this task, ResInsight has support for creating several fractures in one operation.\nSelect one or more well paths in the project tree, right click and select Create Multiple Fractures from the right-click menu. Then the Create Multiple Fractures dialog appears. In this dialog, the user defines where fractures will be created on the selected well paths. Different fracture templates and spacing can be used for different K layer ranges in the grid, by adding new options lines to the table. To edit an option line, double click the field to edit. Adding and deleting option lines are done by right clicking the table.\n Case \u0026ndash; Current grid case Min Distance From Well TD \u0026ndash; Minimum distance from well tip for created fractures Max Fractures Per Well \u0026ndash; Maximum number of fractures to create per well Options  Top K Layer \u0026ndash; The topmost K layer to add fractures to Base K Layer \u0026ndash; The bottommost K layer to add fractures to Template \u0026ndash; The fracture template used in the specified K layer range Spacing \u0026ndash; The distance between each fracture in the K layer range  Generated Fractures \u0026ndash; Output information to the user. Shows number of fractures that will be created on each selected well path Replace Fractures \u0026ndash; Press this button to delete all existing fractures on the selected wells before creating new fractures Add Fractures \u0026ndash; Press this button to add the new fractures to all selected wells (not deleting existing fractures)  The Create Multiple Fractures function is also available as a CommandFile command. See the CommandFile section\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CompletionsIllustration.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThree types of completions are available for modeling and export: Perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.\u003c/p\u003e\n\n\u003cp\u003eCompletions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword. See \u003ca href=\"/export/completionexport/\"\u003e Export Completions\u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003eFor fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV,\nc.f. \u003ca href=\"/export/completionexport/\"\u003eExport Well Segments\u003c/a\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe derived cell property \u003ca href=\"/3d-main-window/derivedresults/#completion-type\"\u003eCompletion Type\u003c/a\u003e displays wich cells are intersected by the completions.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"visualization-and-inspection-of-well-connection-factors\"\u003eVisualization and Inspection of Well Connection Factors\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Completions_WellConnectionFactors.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eConnection factors both from the Simulation Wells and the ones calculated from the modeled completions can be visualized in the 3D view by enabling \u003cstrong\u003eWell Connection Factors\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The connection factors are displayed with a symbol as in the example shown above. The color of the symbol displays the magnitude of the connection factor and can be controlled by the legend settings.  Additional details of the connection factor are displayed in the \u003cstrong\u003eResult Info\u003c/strong\u003e window when clicking on the connection factor symbol.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eProperty Panel\u003c/strong\u003e of the \u003cstrong\u003eWell Connection Factors\u003c/strong\u003e item has a few options:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry Scale Factor\u003c/strong\u003e \u0026ndash; Scales the connection factor symbols relative to the displayed well path radius\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow on Closed Connections\u003c/strong\u003e \u0026ndash; Show the connection factors calculated for closed simulation well cells in addition to the ones at open cells.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eA combined view of well connection factors and the derived result \u003ca href=\"/3d-main-window/derivedresults/#completion-type\"\u003eCompletion Type\u003c/a\u003e\nenables the user to see the completion type contributing to connection factor in a cell.\u003c/p\u003e\n\n\u003ch2 id=\"perforation-intervals\"\u003ePerforation Intervals\u003c/h2\u003e\n\n\u003cp\u003eA new perforation interval on a well can be set up by right-clicking on the well in the \u003cstrong\u003e3D View\u003c/strong\u003e or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and choosing the command \u003cstrong\u003eCreate Perforation interval\u003c/strong\u003e in the \u003cstrong\u003eCreate Completions\u003c/strong\u003e sub-menu. In the 3D View the completion will be created at the specific depth the right-click occured at.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateCompletionOnWellPath.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerforationIntervals_propEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAfter creating the perforation interval, the following properties of the perforation can be set in the property editor:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStart MD\u003c/strong\u003e, \u003cstrong\u003eEnd MD\u003c/strong\u003e \u0026ndash; Measured depth along the well path for the perforation to start/stop.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiameter\u003c/strong\u003e \u0026ndash; Well bore diameter for the perforation interval, used in calculation of transmissibility ( For details on the transmissibility calculation, see \u003ca href=\"/export/completionexport/#transmissibility-calculations\"\u003eTransmissibility Calculations\u003c/a\u003e).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; Skin factor for the perforation, used in calculation of transmissibility.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Timesteps\u003c/strong\u003e \u0026ndash; If on, the perforation interval will be present for all time steps\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Date\u003c/strong\u003e \u0026ndash; The perforation will be included in the model for all time steps after this date. If \u0026ldquo;All TimeSteps\u0026rdquo; is turned on, this option is not available and the perforation is included for all time steps.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe perforation intervals will be indicated by different color along the well path.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPerforationIntervalColor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor each well path there is a top level folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e containing all the perforation intervals definitions containing settings that applies to all the perforation intervals for this well path.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Perforations_PropEdit.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerfIntervalMsw.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Well Options\u003c/strong\u003e - Options used by the Well Segments Export\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLiner Inner Diameter\u003c/strong\u003e \u0026ndash; The liner inner diameter for the completion intervals.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRoughness Factor\u003c/strong\u003e \u0026ndash; The roughness factor used in export of main bore segments.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Drop\u003c/strong\u003e \u0026ndash; can be either \u003cem\u003eHydrostatic\u003c/em\u003e, \u003cem\u003eHydrostatic + Friction\u003c/em\u003e or \u003cem\u003eHydrostatic + Friction + Acceleration\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength and Depth\u003c/strong\u003e \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIncremental\u003c/strong\u003e \u0026ndash; length / depth of given segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbsolute\u003c/strong\u003e \u0026ndash; the length down the tube or depth of the last nodal point\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEnforce Max Segment Length\u003c/strong\u003e \u0026ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThere are three options for Non-Darcy Flow. \u003cstrong\u003eNone\u003c/strong\u003e, \u003cstrong\u003eUser defined D-factor\u003c/strong\u003e and \u003cstrong\u003eCompute D-factor\u003c/strong\u003e. The second option displays an input field where the user defined D-factor can be entered. The last options calculates D-factor for gas given Dake´s (1976) radiel inflow model and correlation for calculating matrix beta factor depending on permeability and porosity.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerfIntervalNonDarcy.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e - Non-Darcy settings for D factor computation\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Permeability Kr Scaling Factor\u003c/strong\u003e \u0026ndash; Rel.perm. scaling factor to calculate effective permeability.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Radius\u003c/strong\u003e \u0026ndash; Well bore radius.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Gas Density\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas Viscosity\u003c/strong\u003e \u0026ndash; Gas viscosity at flowing bottom hole pressure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInertial Coefficient\u003c/strong\u003e \u0026ndash; Coefficient to calculate beta factor.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability Scaling Exponent\u003c/strong\u003e \u0026ndash; For beta factor calculation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePorosity Scaling Exponent\u003c/strong\u003e \u0026ndash; For beta factor calculation.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"perforation-interval-valves\"\u003ePerforation Interval Valves\u003c/h3\u003e\n\n\u003cp\u003ePerforation Intervals can have valves (ICDs/AICDs/ICVs) associated with them.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveVisualisation.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThese valves can be created by right-clicking on the Perforation Interval and selecting \u003cstrong\u003eCreate Valve\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValve.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEach Valve require a \u003cstrong\u003eValve Template\u003c/strong\u003e containing properties which can be shared among multiple Valves. If you have no Valve Template, a new one can be created by clicking the \u003cstrong\u003eNew\u003c/strong\u003e button next to the Valve Template selection list.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValveWithoutTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis will create a new \u003cstrong\u003eValve Template\u003c/strong\u003e which can be of three different types:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eICD\u003c/strong\u003e - In-flow Control Device, allowing the setting of \u003cstrong\u003eOrifice Diameter\u003c/strong\u003e and \u003cstrong\u003eFlow Coefficient\u003c/strong\u003e. ICDs are displayed in Orange.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAICD\u003c/strong\u003e - Autonomous In-flow Control Device, providing several more parameters associated with the Eclipse simulation and seen in the picture below. AICDs are displayed in Dark Purple.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICV\u003c/strong\u003e - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eAn example of the ICD parameters can be seen below:\n\u003cimg src=\"/images/3d-main-window/ValveTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAn example of the AICD parameters:\n\u003cimg src=\"/images/3d-main-window/ValveTemplate_AICD.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eNew templates can also be added by selecting the \u003cstrong\u003eNew Valve Template\u003c/strong\u003e option from the right-click menu of the \u003cstrong\u003eValve Templates\u003c/strong\u003e entry in the \u003cstrong\u003eCompletion Templates\u003c/strong\u003e Project Tree item.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValveTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor ICDs and AICDs, multiple valves can be added in the same go by specifying the number of valves, spacing of valves or specific positions of valves as chosen in the \u003cstrong\u003eLocation Defined By\u003c/strong\u003e drop down list.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveProperties_ICD.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFor ICVs only one valve is added at a time so only the measured depth of that valve can be chosen.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveProperties_ICV.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen you have a valid valve template selected, there is an \u003cstrong\u003eEdit\u003c/strong\u003e button next to the valve template selection. Clicking this will take you straight to modify the valve template.\u003c/p\u003e\n\n\u003ch3 id=\"import-perforation-intervals\"\u003eImport Perforation Intervals\u003c/h3\u003e\n\n\u003cp\u003ePerforation intervals can be imported into ResInsight from \u003cem\u003e\u003ccode\u003e*.ev\u003c/code\u003e\u003c/em\u003e files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.\u003c/p\u003e\n\n\u003ch4 id=\"perforation-interval-file-format\"\u003ePerforation Interval File Format\u003c/h4\u003e\n\n\u003cp\u003e\u0026rdquo;\u0026ndash;\u0026rdquo; is interpreted as the start of a comment. The comment ends at the end of the line.\nThe files can start with a unit definition line:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eUNITS \u0026lt;unitname\u0026gt;\n\u003c/code\u003e\u003c/pre\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThis line is ignored for now. The numbers are interpreted to be in the units present in the case.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003cp\u003eIn the following any number of :\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWELLNAME \u0026lt;well-name\u0026gt;\n\u0026lt;date\u0026gt;  \u0026lt;well completion\u0026gt;  \u0026lt;top mMD\u0026gt;  \u0026lt;base mMD\u0026gt;   \u0026lt;bore hole diameter\u0026gt;  \u0026lt;skin factor\u0026gt;\n\u0026lt;date\u0026gt;  \u0026lt;well completion\u0026gt;  \u0026lt;top mMD\u0026gt;  \u0026lt;base mMD\u0026gt;   \u0026lt;bore hole diameter\u0026gt;  \u0026lt;skin factor\u0026gt;\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003edate\u003c/em\u003e \u0026ndash; Start date of the completion in the format \u0026ldquo;dd mmm yyyy\u0026rdquo;. Eg \u003ccode\u003e01 SEP 2006\u003c/code\u003e. A special \u003ccode\u003e\u0026quot;SOH\u0026quot;\u003c/code\u003edate is also allowed meaning Start Of History.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003ewell completion\u003c/em\u003e \u0026ndash; For now, only \u003ccode\u003e\u0026quot;perforation\u0026quot;\u003c/code\u003e is supported\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eHere is an example:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eUNITS METRIC\n\n-- R-2 AH sidetrack into Ile/Tilje\nWELLNAME R-2AH\n\u0026quot;SOH\u0026quot;   perforation 6200 6350 0.212 0   -- taget Ile 2 and Ile 3\n\u0026quot;SOH\u0026quot;   perforation 7050 7133 0.212 0   -- target Tilje 3, 83 m prodint\n\n-- S-2 AH\nWELLNAME S-2AH\n\u0026quot;SOH\u0026quot;   perforation 4340 4369 0.212 0   -- target Garn 2, 29 m prodint (update 290915)\n01 SEP 2006   perforation 5060 6185 0.212 0   -- target Tilje 3, 1125 m prodint\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch2 id=\"fishbones\"\u003eFishbones\u003c/h2\u003e\n\n\u003cp\u003eFishbones are completions created by drilling or by jetting a set of small lateral holes with a high deviation from the main bore.\nEach set of holes created at the same location along the main bore, is referred to as a \u003cem\u003esub\u003c/em\u003e while each individual hole is called a \u003cem\u003elateral\u003c/em\u003e.\u003c/p\u003e\n\n\u003cp\u003eFor each well path there is a top level folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e containing all the Fishbones definitions containing settings that applies to all the fishbones for this well path. To make use of the Multi Segment Well option for pressure loss along laterals, the grid resolution needs to be fine enough to allow a grid cell to be connected to only one lateral.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_PropEdit.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFishbone Well Properties\u003c/strong\u003e \u0026ndash; Settings used when exporting well connection factors\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStartMD\u003c/strong\u003e \u0026ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMain Bore Diameter\u003c/strong\u003e \u0026ndash; The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMain Bore Skin Factor\u003c/strong\u003e \u0026ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore.\nFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Wells\u003c/strong\u003e - Options used by the Well Segments Export\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLiner Inner  eter\u003c/strong\u003e \u0026ndash; The liner inner diameter for the fishbones.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRoughness Factor\u003c/strong\u003e \u0026ndash; The roughness factor used in export of main bore segments.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Drop\u003c/strong\u003e \u0026ndash; can be either \u003cem\u003eHydrostatic\u003c/em\u003e, \u003cem\u003eHydrostatic + Friction\u003c/em\u003e or \u003cem\u003eHydrostatic + Friction + Acceleration\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength and Depth\u003c/strong\u003e \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIncremental\u003c/strong\u003e \u0026ndash; length / depth of given segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbsolute\u003c/strong\u003e \u0026ndash; the length down the tube or depth of the last nodal point\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"fishbones-subs-definition\"\u003eFishbones Subs Definition\u003c/h3\u003e\n\n\u003cp\u003eTo add new fishbones completions, select the \u003cstrong\u003eNew Fishbones Subs Definition\u003c/strong\u003e command. This menu item is available by right clicking on \u003cstrong\u003eWells\u003c/strong\u003e in the Project Tree or right clicking on the well trajectory in the 3D View.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateCompletionOnWellPath.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe new \u003cstrong\u003eFishbones Subs Definition\u003c/strong\u003e (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 \u003csup\u003e1\u003c/sup\u003e\u0026frasl;\u003csub\u003e2\u003c/sub\u003e\u0026rdquo; main bore.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_SubDefPropEdit.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFishbones Color\u003c/strong\u003e \u0026ndash; The 3D View color of the fishbones created by this definition\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLocation\u003c/strong\u003e \u0026ndash; Options to control the position and number of fishbone subs created by this definition\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLocation Defined By\u003c/strong\u003e \u0026ndash; This setting will select how to define the location of the subs in this group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart MD\u003c/strong\u003e \u0026ndash; Position, in Measured depth along the well, of the first fishbone Sub.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEnd MD\u003c/strong\u003e \u0026ndash; Position of the last fishbone Sub.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Subs\u003c/strong\u003e \u0026ndash; Defines the number of subs to create in the defined interval\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpacing\u003c/strong\u003e \u0026ndash; Spacing between the subs within the interval\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMeasured Depths\u003c/strong\u003e \u0026ndash; The measured depth of each of the fishbone subs. If the \u003cstrong\u003eLocation Defined By\u003c/strong\u003e is set to the \u003cstrong\u003eUser Specified\u003c/strong\u003e this will be directly editable by the user.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLaterals Configuration\u003c/strong\u003e \u0026ndash; Configures the laterals at each sub position.\u003cbr /\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLaterals Per Sub\u003c/strong\u003e \u0026ndash; Number of laterals for each sub position\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLenght(s)\u003c/strong\u003e \u0026ndash; Length of each lateral, in m or ft.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExit Angle\u003c/strong\u003e \u0026ndash; Exit angle for fishbone lateral, in degree.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBuild Angle\u003c/strong\u003e \u0026ndash; Build angle for fishbone lateral, in degree pr meter.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrientation\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFixed Angle\u003c/strong\u003e \u0026ndash; The user can specify the angle for the first lateral\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRandom angle\u003c/strong\u003e \u0026ndash; Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInstall Success Rate\u003c/strong\u003e \u0026ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Properties\u003c/strong\u003e \u0026ndash; Settings to control the connection factor calculation used in \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e)\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHole Diameter\u003c/strong\u003e \u0026ndash; The hole diameter of the lateral\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; The skin factor used in the transmissibility calculation for the lateral.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Wells\u003c/strong\u003e \u0026ndash; Settings used for Well Segment Export\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTubing Diameter\u003c/strong\u003e \u0026ndash; The diameter used in the \u003cem\u003eWELSEGS\u003c/em\u003e export of the laterals.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOpen Hole Roughness Factor\u003c/strong\u003e \u0026ndash; Exported directly to the \u003cem\u003eWELSEGS\u003c/em\u003e keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTubing Roughness Factor\u003c/strong\u003e \u0026ndash; Exported directly to the \u003cem\u003eWELSEGS\u003c/em\u003e keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICDs per Sub\u003c/strong\u003e \u0026ndash; The number of ICD (valves) per Sub, used for calculation of total ICD area for \u003cem\u003eWSEGVALV\u003c/em\u003e export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICD Orifice Diameter\u003c/strong\u003e \u0026ndash; The Diameter of the ICD, used for calculation of ICD area for \u003cem\u003eWSEGVALV\u003c/em\u003e export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICD Flow Coefficient\u003c/strong\u003e \u0026ndash; The flow coefficient, exported directly as a part of \u003cem\u003eWSEGVALV\u003c/em\u003e.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"import-well-trajectories-as-fishbones-laterals\"\u003eImport Well Trajectories as Fishbones Laterals\u003c/h3\u003e\n\n\u003cp\u003eThe command \u003cstrong\u003eImport Completions From File\u003c/strong\u003e can be used to import well trajectories in the \u003cem\u003e\u003ccode\u003e*.dev\u003c/code\u003e\u003c/em\u003e format as fishbone laterals.  The imported laterals are listed under the folder \u003cstrong\u003eImported Laterals\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the \u003cstrong\u003eImported Laterals\u003c/strong\u003e folder.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_LateralsMSWprop.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"export-fishbones-as-well-trajectories\"\u003eExport Fishbones as Well Trajectories\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eExport Laterals\u003c/strong\u003e command will export the fishbone laterals as a well trajectory into a  \u003cem\u003e\u003ccode\u003e*.dev*\u003c/code\u003e\u003c/em\u003e -file.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eNotice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to \u003ccode\u003e\u003cem\u003e.dev\u003c/em\u003e\u003c/code\u003e files.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"fractures\"\u003eFractures\u003c/h2\u003e\n\n\u003cp\u003eHydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formation. A substance is then injected into the crack to keep it open when relaxing the pressure.\u003c/p\u003e\n\n\u003cp\u003eFractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Elliptical fractures and StimPlan fractures.\u003c/p\u003e\n\n\u003ch3 id=\"visualization-control\"\u003eVisualization control\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eFractures\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e controls whether to show the modeled fractures or not. For fractures along the well path the \u003cstrong\u003ePerforation Length\u003c/strong\u003e is shown as an olive green cylinder around the well path as shown in the image below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureVizControl.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e \u0026ndash; Control the color settings for the fractures in the View\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eResult Variable\u003c/strong\u003e \u0026ndash; Selects the fracture result to use for coloring the fracture. This is most interesting when you have imported a StimPlan fracture with varying width, conductivity and other parameters. The legend item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e controls how the legend is set up.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Color\u003c/strong\u003e \u0026ndash; The color to use if the requested result is not available for some fracture.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStimPlan\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Mesh\u003c/strong\u003e \u0026ndash; Toggles the visualization of the StimPlan mesh lines, showing the StimPlan cell borders\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColor Interpolation\u003c/strong\u003e \u0026ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"fracture-templates\"\u003eFracture Templates\u003c/h3\u003e\n\n\u003cp\u003eTo create a functioning fracture you first need a \u003cstrong\u003eFracture Template\u003c/strong\u003e. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.\u003c/p\u003e\n\n\u003cp\u003eFracture Templates are listed in a folder with the same name in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureTemplates.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTo create a new fracture template, right-click the \u003cstrong\u003eFracture Template\u003c/strong\u003e item in the tree, and select either \u003cstrong\u003eNew Ellipse Fracture Template\u003c/strong\u003e or \u003cstrong\u003eNew StimPlan Fracture Template\u003c/strong\u003e. If you have no existing fracture templates, you will be given the opportunity to create such templates through two buttons in the Fracture Property Editor as seen below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateFractureTemplate.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"common-fracture-template-options\"\u003eCommon Fracture Template Options\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CommonFractureTemplateProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User defined name for the template. Used when selecting which template to use in the Fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eID\u003c/strong\u003e \u0026ndash; Assigned ID to be used when addressing this template form a Command file script\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; The fractures orientation\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTransverse(normal) to Well Path\u003c/strong\u003e \u0026ndash; The fracture plane is vertical and normal to the well path at the intersection point.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAlong Well Path\u003c/strong\u003e \u0026ndash; Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e \u0026ndash; The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUse Containment\u003c/strong\u003e \u0026ndash; Enable this option to activate layer containment.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTop Layer\u003c/strong\u003e \u0026ndash; Topmost K-layer that the fracture will drain.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase Layer\u003c/strong\u003e \u0026ndash; Lowest K-layer that the fracture will drain.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTruncate At Faults\u003c/strong\u003e \u0026ndash; Enable this option to activate fault truncation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum Fault Throw\u003c/strong\u003e \u0026ndash; Fault throw threshold to activate fault truncation.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; The availability of these options depend on the \u003cstrong\u003eFracture Orientation\u003c/strong\u003e and the \u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e setting.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFinite Conductivity\u003c/strong\u003e \u0026ndash; Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInfinite Conductivity\u003c/strong\u003e \u0026ndash; Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the StimPlan data.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; Used when exporting to Eclipse.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Length\u003c/strong\u003e \u0026ndash; The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures \u003cstrong\u003eAlong Well Path\u003c/strong\u003e only ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Efficiency\u003c/strong\u003e \u0026ndash; The efficiency of the wellbore-fracture perforation ( Fractures \u003cstrong\u003eAlong Well Path\u003c/strong\u003e only ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Diameter\u003c/strong\u003e \u0026ndash; Used when exporting to Eclipse.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensitivity Scale Factors\u003c/strong\u003e \u0026ndash; Each of the properties are scaled by the scaling factor. When used interactively, the \u003cstrong\u003eApply\u003c/strong\u003e button must be pressed to apply the scaling factors. These scaling factors are also available from command file scripting\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHeight, Width\u003c/strong\u003e \u0026ndash; Scales the height or the \u003cem\u003e\u003cem\u003eHalflength\u003c/em\u003e\u003c/em\u003e of the fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD-factor\u003c/strong\u003e \u0026ndash; Scales the none-darcy flow factor\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity\u003c/strong\u003e \u0026ndash; Scales the conductivity in the fracture directly\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"non-darcy-flow\"\u003eNon-Darcy Flow\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureNonDarcyFlow.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eNon-Darcy Flow is used to improve the computation of connection factors for cells penetrated by well pipes. A pre-computed D-factor can be set using \u003cstrong\u003eUser Defined D-factor\u003c/strong\u003e. Selecting the option \u003cstrong\u003eCompute D-factor\u003c/strong\u003e displays the following set of properties:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInertial Coefficient\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Beta-factor in Forcheimer units\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Beta Factor\u003c/strong\u003e \u0026ndash; Extract beta factor from the fracture template at the well intersection location. For transversal fractures, the conductivity is computed from the geometric average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEffective Permeability\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Defines the permeability \u003cem\u003eKe\u003c/em\u003e in milliDarcy in the property \u003cstrong\u003eEffective Permeability\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Conductivity\u003c/strong\u003e \u0026ndash; Extract conductivity from the fracture template at the well intersection location and scale with \u003cstrong\u003eRelative Permeability\u003c/strong\u003e. For transversal fractures, the conductivity is computed from the weighted average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Defines the width of the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Width\u003c/strong\u003e \u0026ndash; Extract width from the fracture template at the well intersection location. For transversal fractures, the width is based on the weighted average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Gas Density\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas Viscosity\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD Factor\u003c/strong\u003e \u0026ndash; Displays the computed value of the D factor. NOTE : For \u003cem\u003etransversal fractures\u003c/em\u003e, the computed D factor is scaled by 1.2 to compensate for a different flow model\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD Factor Details\u003c/strong\u003e \u0026ndash; Displays the value of variables used to compute the D factor\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"ellipse-fracture-template\"\u003eEllipse Fracture Template\u003c/h4\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/EllipseFractureTemplateProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User name of this particular fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHalflength X\u003csub\u003er\u003c/sub\u003e\u003c/strong\u003e \u0026ndash; Half the width of the ellipse\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHeight\u003c/strong\u003e \u0026ndash; The height of the elliptical fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; The availability of these options depend on the \u003cstrong\u003eFracture Orientation\u003c/strong\u003e and the \u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e setting\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability\u003c/strong\u003e \u0026ndash; A constant permeability inside the fracture (Used to calculate conductivity in the fracture)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e \u0026ndash; Crack width (Used to calculate conductivity in the fracture)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensivity Scale Factors\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"stimplan-fracture-template\"\u003eStimplan Fracture Template\u003c/h4\u003e\n\n\u003cp\u003eStimPlan fracture templates imports XML output from the StimPlan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting conductivity etc. as time varying quantities. Both symmetric and asymmetric StimPlan fracture templates are supported.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StimplanFractureTemplateProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User name of this particular fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow StimPlan Mesh\u003c/strong\u003e \u0026ndash; Show or hide the mesh lines on the fracture in the 3D View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInput\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile Name\u003c/strong\u003e \u0026ndash; Path to the imported StimPlan XML-file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eActive Time step Index\u003c/strong\u003e \u0026ndash; Time step in the StimPlan simulation to use for transmissibility calculations and visualization\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell/fracture Intersection Depth\u003c/strong\u003e \u0026ndash; The position of the fracture along the well path as MD.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity Scaling Factor\u003c/strong\u003e \u0026ndash; Scale the overall conductivity to do sensitivity studies.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensitivity Scale Factors\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"fracture-instances\"\u003eFracture Instances\u003c/h3\u003e\n\n\u003cp\u003eInstances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureInstancePropertyPanel.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User editable name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Template\u003c/strong\u003e \u0026ndash; Select the fracture template to use for this fracture. Click the \u003cstrong\u003eEdit\u003c/strong\u003e shortcut next to the template selection list to go directly to modify the selected template.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLocation/Orientation\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMeasured depth Location\u003c/strong\u003e \u0026ndash; The measured depth\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e \u0026ndash; Azimuth orientation of fracture.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e \u0026ndash; Dip of fracture plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTilt\u003c/strong\u003e \u0026ndash; Rotation of fracture about its plane normal\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Unit System\u003c/strong\u003e \u0026ndash; Read only display of the units used for the current template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStimPlan Time Step\u003c/strong\u003e \u0026ndash; Displays the time step used by the template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Length\u003c/strong\u003e / \u003cstrong\u003ePerforation Efficiency\u003c/strong\u003e / \u003cstrong\u003eWell Diameter\u003c/strong\u003e \u0026ndash; These values are copied from the new template when selecting a different one. See \u003ca href=\"/wells-and-completions/completions/#common-fracture-template-options\"\u003eCommon Fracture Template Options\u003c/a\u003e\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Center Info\u003c/strong\u003e \u0026ndash; This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"multiple-fracture-creation\"\u003eMultiple Fracture Creation\u003c/h3\u003e\n\n\u003cp\u003eIn some cases the user wants to create a number of fractures on one or more well paths. Doing this by creating one by one fracture can be very error prone and time consuming. To ease this task, ResInsight has support for creating several fractures in one operation.\u003c/p\u003e\n\n\u003cp\u003eSelect one or more well paths in the project tree, right click and select \u003cstrong\u003eCreate Multiple Fractures\u003c/strong\u003e from the right-click menu. Then the \u003cstrong\u003eCreate Multiple Fractures\u003c/strong\u003e dialog appears. In this dialog, the user defines where fractures will be created on the selected well paths. Different fracture templates and spacing can be used for different K layer ranges in the grid, by adding new options lines to the table. To edit an option line, double click the field to edit. Adding and deleting option lines are done by right clicking the table.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateMultipleFracturesDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Current grid case\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin Distance From Well TD\u003c/strong\u003e \u0026ndash; Minimum distance from well tip for created fractures\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax Fractures Per Well\u003c/strong\u003e \u0026ndash; Maximum number of fractures to create per well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTop K Layer\u003c/strong\u003e \u0026ndash; The topmost K layer to add fractures to\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase K Layer\u003c/strong\u003e \u0026ndash; The bottommost K layer to add fractures to\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTemplate\u003c/strong\u003e \u0026ndash; The fracture template used in the specified K layer range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpacing\u003c/strong\u003e \u0026ndash; The distance between each fracture in the K layer range\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerated Fractures\u003c/strong\u003e \u0026ndash; Output information to the user. Shows number of fractures that will be created on each selected well path\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eReplace Fractures\u003c/strong\u003e \u0026ndash; Press this button to delete all existing fractures on the selected wells before creating new fractures\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAdd Fractures\u003c/strong\u003e \u0026ndash; Press this button to add the new fractures to all selected wells (not deleting existing fractures)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe Create Multiple Fractures function is also available as a CommandFile command. See the \u003ca href=\"/scripting/commandfile/\"\u003eCommandFile section\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "Three types of completions are available for modeling and export: Perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.\nCompletions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword. See Export Completions\nFor fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV, c.f. Export Well Segments.\nThe derived cell property Completion Type displays wich cells are intersected by the completions.\n\rVisualization and Inspection of Well Connection Factors Connection factors both from the Simulation Wells and the ones calculated from the modeled completions can be visualized in the 3D view by enabling Well Connection Factors in the Project Tree. The connection factors are displayed with a symbol as in the example shown above. The color of the symbol displays the magnitude of the connection factor and can be controlled by the legend settings. Additional details of the connection factor are displayed in the Result Info window when clicking on the connection factor symbol.\nThe Property Panel of the Well Connection Factors item has a few options:\n Geometry Scale Factor \u0026ndash; Scales the connection factor symbols relative to the displayed well path radius Show on Closed Connections \u0026ndash; Show the connection factors calculated for closed simulation well cells in addition to the ones at open cells.  A combined view of well connection factors and the derived result Completion Type enables the user to see the completion type contributing to connection factor in a cell.\nPerforation Intervals A new perforation interval on a well can be set up by right-clicking on the well in the 3D View or in the Project Tree, and choosing the command Create Perforation interval in the Create Completions sub-menu. In the 3D View the completion will be created at the specific depth the right-click occured at.\nAfter creating the perforation interval, the following properties of the perforation can be set in the property editor:\n Start MD, End MD \u0026ndash; Measured depth along the well path for the perforation to start/stop. Diameter \u0026ndash; Well bore diameter for the perforation interval, used in calculation of transmissibility ( For details on the transmissibility calculation, see Transmissibility Calculations). Skin Factor \u0026ndash; Skin factor for the perforation, used in calculation of transmissibility. All Timesteps \u0026ndash; If on, the perforation interval will be present for all time steps Start Date \u0026ndash; The perforation will be included in the model for all time steps after this date. If \u0026ldquo;All TimeSteps\u0026rdquo; is turned on, this option is not available and the perforation is included for all time steps.  The perforation intervals will be indicated by different color along the well path.\nFor each well path there is a top level folder in the Project Tree containing all the perforation intervals definitions containing settings that applies to all the perforation intervals for this well path.\nFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\n Multi Segment Well Options - Options used by the Well Segments Export  Liner Inner Diameter \u0026ndash; The liner inner diameter for the completion intervals. Roughness Factor \u0026ndash; The roughness factor used in export of main bore segments. Pressure Drop \u0026ndash; can be either Hydrostatic, Hydrostatic + Friction or Hydrostatic + Friction + Acceleration. Length and Depth \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment  Incremental \u0026ndash; length / depth of given segment Absolute \u0026ndash; the length down the tube or depth of the last nodal point   Enforce Max Segment Length \u0026ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.    There are three options for Non-Darcy Flow. None, User defined D-factor and Compute D-factor. The second option displays an input field where the user defined D-factor can be entered. The last options calculates D-factor for gas given Dake´s (1976) radiel inflow model and correlation for calculating matrix beta factor depending on permeability and porosity.\n Non-Darcy Flow - Non-Darcy settings for D factor computation  Grid Permeability Kr Scaling Factor \u0026ndash; Rel.perm. scaling factor to calculate effective permeability. Well Radius \u0026ndash; Well bore radius. Relative Gas Density Gas Viscosity \u0026ndash; Gas viscosity at flowing bottom hole pressure. Inertial Coefficient \u0026ndash; Coefficient to calculate beta factor. Permeability Scaling Exponent \u0026ndash; For beta factor calculation. Porosity Scaling Exponent \u0026ndash; For beta factor calculation.    Perforation Interval Valves Perforation Intervals can have valves (ICDs/AICDs/ICVs) associated with them.\nThese valves can be created by right-clicking on the Perforation Interval and selecting Create Valve.\nEach Valve require a Valve Template containing properties which can be shared among multiple Valves. If you have no Valve Template, a new one can be created by clicking the New button next to the Valve Template selection list.\nThis will create a new Valve Template which can be of three different types:\n ICD - In-flow Control Device, allowing the setting of Orifice Diameter and Flow Coefficient. ICDs are displayed in Orange. AICD - Autonomous In-flow Control Device, providing several more parameters associated with the Eclipse simulation and seen in the picture below. AICDs are displayed in Dark Purple. ICV - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.  An example of the ICD parameters can be seen below: An example of the AICD parameters: New templates can also be added by selecting the New Valve Template option from the right-click menu of the Valve Templates entry in the Completion Templates Project Tree item.\nFor ICDs and AICDs, multiple valves can be added in the same go by specifying the number of valves, spacing of valves or specific positions of valves as chosen in the Location Defined By drop down list.\nFor ICVs only one valve is added at a time so only the measured depth of that valve can be chosen.\nWhen you have a valid valve template selected, there is an Edit button next to the valve template selection. Clicking this will take you straight to modify the valve template.\nImport Perforation Intervals Perforation intervals can be imported into ResInsight from *.ev files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.\nPerforation Interval File Format \u0026ldquo;\u0026ndash;\u0026rdquo; is interpreted as the start of a comment. The comment ends at the end of the line. The files can start with a unit definition line:\nUNITS \u0026lt;unitname\u0026gt;\r This line is ignored for now. The numbers are interpreted to be in the units present in the case.\n\rIn the following any number of :\nWELLNAME \u0026lt;well-name\u0026gt;\r\u0026lt;date\u0026gt; \u0026lt;well completion\u0026gt; \u0026lt;top mMD\u0026gt; \u0026lt;base mMD\u0026gt; \u0026lt;bore hole diameter\u0026gt; \u0026lt;skin factor\u0026gt;\r\u0026lt;date\u0026gt; \u0026lt;well completion\u0026gt; \u0026lt;top mMD\u0026gt; \u0026lt;base mMD\u0026gt; \u0026lt;bore hole diameter\u0026gt; \u0026lt;skin factor\u0026gt;\r  date \u0026ndash; Start date of the completion in the format \u0026ldquo;dd mmm yyyy\u0026rdquo;. Eg 01 SEP 2006. A special \u0026quot;SOH\u0026quot;date is also allowed meaning Start Of History. well completion \u0026ndash; For now, only \u0026quot;perforation\u0026quot; is supported  Here is an example:\nUNITS METRIC\r-- R-2 AH sidetrack into Ile/Tilje\rWELLNAME R-2AH\r\u0026quot;SOH\u0026quot; perforation 6200 6350 0.212 0 -- taget Ile 2 and Ile 3\r\u0026quot;SOH\u0026quot; perforation 7050 7133 0.212 0 -- target Tilje 3, 83 m prodint\r-- S-2 AH\rWELLNAME S-2AH\r\u0026quot;SOH\u0026quot; perforation 4340 4369 0.212 0 -- target Garn 2, 29 m prodint (update 290915)\r01 SEP 2006 perforation 5060 6185 0.212 0 -- target Tilje 3, 1125 m prodint\r Fishbones Fishbones are completions created by drilling or by jetting a set of small lateral holes with a high deviation from the main bore. Each set of holes created at the same location along the main bore, is referred to as a sub while each individual hole is called a lateral.\nFor each well path there is a top level folder in the Project Tree containing all the Fishbones definitions containing settings that applies to all the fishbones for this well path. To make use of the Multi Segment Well option for pressure loss along laterals, the grid resolution needs to be fine enough to allow a grid cell to be connected to only one lateral.\n Fishbone Well Properties \u0026ndash; Settings used when exporting well connection factors  StartMD \u0026ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated. Main Bore Diameter \u0026ndash; The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore. Main Bore Skin Factor \u0026ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore. For multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.   Multi Segment Wells - Options used by the Well Segments Export  Liner Inner eter \u0026ndash; The liner inner diameter for the fishbones. Roughness Factor \u0026ndash; The roughness factor used in export of main bore segments. Pressure Drop \u0026ndash; can be either Hydrostatic, Hydrostatic + Friction or Hydrostatic + Friction + Acceleration. Length and Depth \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment  Incremental \u0026ndash; length / depth of given segment Absolute \u0026ndash; the length down the tube or depth of the last nodal point      Fishbones Subs Definition To add new fishbones completions, select the New Fishbones Subs Definition command. This menu item is available by right clicking on Wells in the Project Tree or right clicking on the well trajectory in the 3D View.\nThe new Fishbones Subs Definition (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 1/2\u0026rdquo; main bore.\n Appearance  Fishbones Color \u0026ndash; The 3D View color of the fishbones created by this definition   Location \u0026ndash; Options to control the position and number of fishbone subs created by this definition  Location Defined By \u0026ndash; This setting will select how to define the location of the subs in this group. Start MD \u0026ndash; Position, in Measured depth along the well, of the first fishbone Sub. End MD \u0026ndash; Position of the last fishbone Sub. Number of Subs \u0026ndash; Defines the number of subs to create in the defined interval Spacing \u0026ndash; Spacing between the subs within the interval Measured Depths \u0026ndash; The measured depth of each of the fishbone subs. If the Location Defined By is set to the User Specified this will be directly editable by the user.   Laterals Configuration \u0026ndash; Configures the laterals at each sub position.  Laterals Per Sub \u0026ndash; Number of laterals for each sub position Lenght(s) \u0026ndash; Length of each lateral, in m or ft. Exit Angle \u0026ndash; Exit angle for fishbone lateral, in degree. Build Angle \u0026ndash; Build angle for fishbone lateral, in degree pr meter. Orientation  Fixed Angle \u0026ndash; The user can specify the angle for the first lateral Random angle \u0026ndash; Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced.   Install Success Rate \u0026ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.   Well Properties \u0026ndash; Settings to control the connection factor calculation used in Completion Export)  Hole Diameter \u0026ndash; The hole diameter of the lateral Skin Factor \u0026ndash; The skin factor used in the transmissibility calculation for the lateral.   Multi Segment Wells \u0026ndash; Settings used for Well Segment Export  Tubing Diameter \u0026ndash; The diameter used in the WELSEGS export of the laterals. Open Hole Roughness Factor \u0026ndash; Exported directly to the WELSEGS keyword. Tubing Roughness Factor \u0026ndash; Exported directly to the WELSEGS keyword. ICDs per Sub \u0026ndash; The number of ICD (valves) per Sub, used for calculation of total ICD area for WSEGVALV export. ICD Orifice Diameter \u0026ndash; The Diameter of the ICD, used for calculation of ICD area for WSEGVALV export. ICD Flow Coefficient \u0026ndash; The flow coefficient, exported directly as a part of WSEGVALV.    Import Well Trajectories as Fishbones Laterals The command Import Completions From File can be used to import well trajectories in the *.dev format as fishbone laterals. The imported laterals are listed under the folder Imported Laterals in the Project Tree. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the Imported Laterals folder.\nExport Fishbones as Well Trajectories The Export Laterals command will export the fishbone laterals as a well trajectory into a *.dev* -file.\nNotice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to *.dev*files.\n\rFractures Hydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formation. A substance is then injected into the crack to keep it open when relaxing the pressure.\nFractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Elliptical fractures and StimPlan fractures.\nVisualization control The Fractures item in the Project Tree controls whether to show the modeled fractures or not. For fractures along the well path the Perforation Length is shown as an olive green cylinder around the well path as shown in the image below.\n Colors \u0026ndash; Control the color settings for the fractures in the View  Result Variable \u0026ndash; Selects the fracture result to use for coloring the fracture. This is most interesting when you have imported a StimPlan fracture with varying width, conductivity and other parameters. The legend item in the Project Tree controls how the legend is set up. Default Color \u0026ndash; The color to use if the requested result is not available for some fracture.   StimPlan  Show Mesh \u0026ndash; Toggles the visualization of the StimPlan mesh lines, showing the StimPlan cell borders Color Interpolation \u0026ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.    Fracture Templates To create a functioning fracture you first need a Fracture Template. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.\nFracture Templates are listed in a folder with the same name in the Project Tree.\nTo create a new fracture template, right-click the Fracture Template item in the tree, and select either New Ellipse Fracture Template or New StimPlan Fracture Template. If you have no existing fracture templates, you will be given the opportunity to create such templates through two buttons in the Fracture Property Editor as seen below.\nCommon Fracture Template Options  Name \u0026ndash; User defined name for the template. Used when selecting which template to use in the Fracture ID \u0026ndash; Assigned ID to be used when addressing this template form a Command file script Geometry  Fracture Orientation \u0026ndash; The fractures orientation  Transverse(normal) to Well Path \u0026ndash; The fracture plane is vertical and normal to the well path at the intersection point. Along Well Path \u0026ndash; Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below. Azimuth \u0026ndash; The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.     Fracture Truncation  Use Containment \u0026ndash; Enable this option to activate layer containment.  Top Layer \u0026ndash; Topmost K-layer that the fracture will drain. Base Layer \u0026ndash; Lowest K-layer that the fracture will drain.   Truncate At Faults \u0026ndash; Enable this option to activate fault truncation.  Minimum Fault Throw \u0026ndash; Fault throw threshold to activate fault truncation.     Properties \u0026ndash; The availability of these options depend on the Fracture Orientation and the Conductivity in Fracture setting.  Conductivity in Fracture  Finite Conductivity \u0026ndash; Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures. Infinite Conductivity \u0026ndash; Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the StimPlan data.   Skin Factor \u0026ndash; Used when exporting to Eclipse. Perforation Length \u0026ndash; The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures Along Well Path only ). Perforation Efficiency \u0026ndash; The efficiency of the wellbore-fracture perforation ( Fractures Along Well Path only ). Well Diameter \u0026ndash; Used when exporting to Eclipse.   Sensitivity Scale Factors \u0026ndash; Each of the properties are scaled by the scaling factor. When used interactively, the Apply button must be pressed to apply the scaling factors. These scaling factors are also available from command file scripting  Height, Width \u0026ndash; Scales the height or the Halflength of the fracture template D-factor \u0026ndash; Scales the none-darcy flow factor Conductivity \u0026ndash; Scales the conductivity in the fracture directly    Non-Darcy Flow Non-Darcy Flow is used to improve the computation of connection factors for cells penetrated by well pipes. A pre-computed D-factor can be set using User Defined D-factor. Selecting the option Compute D-factor displays the following set of properties:\n Inertial Coefficient  User Defined \u0026ndash; Beta-factor in Forcheimer units Use Fracture Beta Factor \u0026ndash; Extract beta factor from the fracture template at the well intersection location. For transversal fractures, the conductivity is computed from the geometric average of fracture cells intersected by the fracture perforation length.   Effective Permeability  User Defined \u0026ndash; Defines the permeability Ke in milliDarcy in the property Effective Permeability Use Fracture Conductivity \u0026ndash; Extract conductivity from the fracture template at the well intersection location and scale with Relative Permeability. For transversal fractures, the conductivity is computed from the weighted average of fracture cells intersected by the fracture perforation length.   Width  User Defined \u0026ndash; Defines the width of the fracture Use Fracture Width \u0026ndash; Extract width from the fracture template at the well intersection location. For transversal fractures, the width is based on the weighted average of fracture cells intersected by the fracture perforation length.   Relative Gas Density Gas Viscosity D Factor \u0026ndash; Displays the computed value of the D factor. NOTE : For transversal fractures, the computed D factor is scaled by 1.2 to compensate for a different flow model D Factor Details \u0026ndash; Displays the value of variables used to compute the D factor  Ellipse Fracture Template  Name \u0026ndash; User name of this particular fracture template Geometry  Halflength Xr \u0026ndash; Half the width of the ellipse Height \u0026ndash; The height of the elliptical fracture Fracture Orientation \u0026ndash; See above   Fracture Truncation \u0026ndash; See above Properties \u0026ndash; The availability of these options depend on the Fracture Orientation and the Conductivity in Fracture setting  Permeability \u0026ndash; A constant permeability inside the fracture (Used to calculate conductivity in the fracture) Width \u0026ndash; Crack width (Used to calculate conductivity in the fracture)   Sensivity Scale Factors \u0026ndash; See above Non-Darcy Flow \u0026ndash; See above  Stimplan Fracture Template StimPlan fracture templates imports XML output from the StimPlan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting conductivity etc. as time varying quantities. Both symmetric and asymmetric StimPlan fracture templates are supported.\n Name \u0026ndash; User name of this particular fracture template Show StimPlan Mesh \u0026ndash; Show or hide the mesh lines on the fracture in the 3D View Input  File Name \u0026ndash; Path to the imported StimPlan XML-file Active Time step Index \u0026ndash; Time step in the StimPlan simulation to use for transmissibility calculations and visualization Well/fracture Intersection Depth \u0026ndash; The position of the fracture along the well path as MD.   Geometry  Fracture Orientation \u0026ndash; See above   Fracture Truncation \u0026ndash; See above Properties  Conductivity Scaling Factor \u0026ndash; Scale the overall conductivity to do sensitivity studies.   Sensitivity Scale Factors \u0026ndash; See above Non-Darcy Flow \u0026ndash; See above  Fracture Instances Instances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the Project Tree.\n Name \u0026ndash; User editable name Fracture Template \u0026ndash; Select the fracture template to use for this fracture. Click the Edit shortcut next to the template selection list to go directly to modify the selected template. Location/Orientation  Measured depth Location \u0026ndash; The measured depth Azimuth \u0026ndash; Azimuth orientation of fracture. Dip \u0026ndash; Dip of fracture plane Tilt \u0026ndash; Rotation of fracture about its plane normal   Properties  Fracture Unit System \u0026ndash; Read only display of the units used for the current template StimPlan Time Step \u0026ndash; Displays the time step used by the template Perforation Length / Perforation Efficiency / Well Diameter \u0026ndash; These values are copied from the new template when selecting a different one. See Common Fracture Template Options   Fracture Center Info \u0026ndash; This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.  Multiple Fracture Creation In some cases the user wants to create a number of fractures on one or more well paths. Doing this by creating one by one fracture can be very error prone and time consuming. To ease this task, ResInsight has support for creating several fractures in one operation.\nSelect one or more well paths in the project tree, right click and select Create Multiple Fractures from the right-click menu. Then the Create Multiple Fractures dialog appears. In this dialog, the user defines where fractures will be created on the selected well paths. Different fracture templates and spacing can be used for different K layer ranges in the grid, by adding new options lines to the table. To edit an option line, double click the field to edit. Adding and deleting option lines are done by right clicking the table.\n Case \u0026ndash; Current grid case Min Distance From Well TD \u0026ndash; Minimum distance from well tip for created fractures Max Fractures Per Well \u0026ndash; Maximum number of fractures to create per well Options  Top K Layer \u0026ndash; The topmost K layer to add fractures to Base K Layer \u0026ndash; The bottommost K layer to add fractures to Template \u0026ndash; The fracture template used in the specified K layer range Spacing \u0026ndash; The distance between each fracture in the K layer range   Generated Fractures \u0026ndash; Output information to the user. Shows number of fractures that will be created on each selected well path Replace Fractures \u0026ndash; Press this button to delete all existing fractures on the selected wells before creating new fractures Add Fractures \u0026ndash; Press this button to add the new fractures to all selected wells (not deleting existing fractures)  The Create Multiple Fractures function is also available as a CommandFile command. See the CommandFile section\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CompletionsIllustration.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThree types of completions are available for modeling and export: Perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.\u003c/p\u003e\n\u003cp\u003eCompletions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword. See \u003ca href=\"/export/completionexport/\"\u003e Export Completions\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV,\nc.f. \u003ca href=\"/export/completionexport/\"\u003eExport Well Segments\u003c/a\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe derived cell property \u003ca href=\"/3d-main-window/derivedresults/#completion-type\"\u003eCompletion Type\u003c/a\u003e displays wich cells are intersected by the completions.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"visualization-and-inspection-of-well-connection-factors\"\u003eVisualization and Inspection of Well Connection Factors\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Completions_WellConnectionFactors.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eConnection factors both from the Simulation Wells and the ones calculated from the modeled completions can be visualized in the 3D view by enabling \u003cstrong\u003eWell Connection Factors\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The connection factors are displayed with a symbol as in the example shown above. The color of the symbol displays the magnitude of the connection factor and can be controlled by the legend settings.  Additional details of the connection factor are displayed in the \u003cstrong\u003eResult Info\u003c/strong\u003e window when clicking on the connection factor symbol.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eProperty Panel\u003c/strong\u003e of the \u003cstrong\u003eWell Connection Factors\u003c/strong\u003e item has a few options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry Scale Factor\u003c/strong\u003e \u0026ndash; Scales the connection factor symbols relative to the displayed well path radius\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow on Closed Connections\u003c/strong\u003e \u0026ndash; Show the connection factors calculated for closed simulation well cells in addition to the ones at open cells.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eA combined view of well connection factors and the derived result \u003ca href=\"/3d-main-window/derivedresults/#completion-type\"\u003eCompletion Type\u003c/a\u003e \nenables the user to see the completion type contributing to connection factor in a cell.\u003c/p\u003e\n\u003ch2 id=\"perforation-intervals\"\u003ePerforation Intervals\u003c/h2\u003e\n\u003cp\u003eA new perforation interval on a well can be set up by right-clicking on the well in the \u003cstrong\u003e3D View\u003c/strong\u003e or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and choosing the command \u003cstrong\u003eCreate Perforation interval\u003c/strong\u003e in the \u003cstrong\u003eCreate Completions\u003c/strong\u003e sub-menu. In the 3D View the completion will be created at the specific depth the right-click occured at.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateCompletionOnWellPath.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerforationIntervals_propEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAfter creating the perforation interval, the following properties of the perforation can be set in the property editor:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStart MD\u003c/strong\u003e, \u003cstrong\u003eEnd MD\u003c/strong\u003e \u0026ndash; Measured depth along the well path for the perforation to start/stop.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDiameter\u003c/strong\u003e \u0026ndash; Well bore diameter for the perforation interval, used in calculation of transmissibility ( For details on the transmissibility calculation, see \u003ca href=\"/export/completionexport/#transmissibility-calculations\"\u003eTransmissibility Calculations\u003c/a\u003e).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; Skin factor for the perforation, used in calculation of transmissibility.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Timesteps\u003c/strong\u003e \u0026ndash; If on, the perforation interval will be present for all time steps\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Date\u003c/strong\u003e \u0026ndash; The perforation will be included in the model for all time steps after this date. If \u0026ldquo;All TimeSteps\u0026rdquo; is turned on, this option is not available and the perforation is included for all time steps.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe perforation intervals will be indicated by different color along the well path.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellPerforationIntervalColor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor each well path there is a top level folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e containing all the perforation intervals definitions containing settings that applies to all the perforation intervals for this well path.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Perforations_PropEdit.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerfIntervalMsw.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Well Options\u003c/strong\u003e - Options used by the Well Segments Export\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLiner Inner Diameter\u003c/strong\u003e \u0026ndash; The liner inner diameter for the completion intervals.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRoughness Factor\u003c/strong\u003e \u0026ndash; The roughness factor used in export of main bore segments.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Drop\u003c/strong\u003e \u0026ndash; can be either \u003cem\u003eHydrostatic\u003c/em\u003e, \u003cem\u003eHydrostatic + Friction\u003c/em\u003e or \u003cem\u003eHydrostatic + Friction + Acceleration\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength and Depth\u003c/strong\u003e \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eIncremental\u003c/strong\u003e \u0026ndash; length / depth of given segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbsolute\u003c/strong\u003e \u0026ndash; the length down the tube or depth of the last nodal point\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEnforce Max Segment Length\u003c/strong\u003e \u0026ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThere are three options for Non-Darcy Flow. \u003cstrong\u003eNone\u003c/strong\u003e, \u003cstrong\u003eUser defined D-factor\u003c/strong\u003e and \u003cstrong\u003eCompute D-factor\u003c/strong\u003e. The second option displays an input field where the user defined D-factor can be entered. The last options calculates D-factor for gas given Dake´s (1976) radiel inflow model and correlation for calculating matrix beta factor depending on permeability and porosity.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PerfIntervalNonDarcy.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e - Non-Darcy settings for D factor computation\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Permeability Kr Scaling Factor\u003c/strong\u003e \u0026ndash; Rel.perm. scaling factor to calculate effective permeability.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Radius\u003c/strong\u003e \u0026ndash; Well bore radius.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Gas Density\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas Viscosity\u003c/strong\u003e \u0026ndash; Gas viscosity at flowing bottom hole pressure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInertial Coefficient\u003c/strong\u003e \u0026ndash; Coefficient to calculate beta factor.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability Scaling Exponent\u003c/strong\u003e \u0026ndash; For beta factor calculation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePorosity Scaling Exponent\u003c/strong\u003e \u0026ndash; For beta factor calculation.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"perforation-interval-valves\"\u003ePerforation Interval Valves\u003c/h3\u003e\n\u003cp\u003ePerforation Intervals can have valves (ICDs/AICDs/ICVs) associated with them.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveVisualisation.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThese valves can be created by right-clicking on the Perforation Interval and selecting \u003cstrong\u003eCreate Valve\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValve.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEach Valve require a \u003cstrong\u003eValve Template\u003c/strong\u003e containing properties which can be shared among multiple Valves. If you have no Valve Template, a new one can be created by clicking the \u003cstrong\u003eNew\u003c/strong\u003e button next to the Valve Template selection list.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValveWithoutTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis will create a new \u003cstrong\u003eValve Template\u003c/strong\u003e which can be of three different types:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eICD\u003c/strong\u003e - In-flow Control Device, allowing the setting of \u003cstrong\u003eOrifice Diameter\u003c/strong\u003e and \u003cstrong\u003eFlow Coefficient\u003c/strong\u003e. ICDs are displayed in Orange.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAICD\u003c/strong\u003e - Autonomous In-flow Control Device, providing several more parameters associated with the Eclipse simulation and seen in the picture below. AICDs are displayed in Dark Purple.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICV\u003c/strong\u003e - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eAn example of the ICD parameters can be seen below:\n\u003cimg src=\"/images/3d-main-window/ValveTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn example of the AICD parameters:\n\u003cimg src=\"/images/3d-main-window/ValveTemplate_AICD.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNew templates can also be added by selecting the \u003cstrong\u003eNew Valve Template\u003c/strong\u003e option from the right-click menu of the \u003cstrong\u003eValve Templates\u003c/strong\u003e entry in the \u003cstrong\u003eCompletion Templates\u003c/strong\u003e Project Tree item.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/NewValveTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor ICDs and AICDs, multiple valves can be added in the same go by specifying the number of valves, spacing of valves or specific positions of valves as chosen in the \u003cstrong\u003eLocation Defined By\u003c/strong\u003e drop down list.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveProperties_ICD.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFor ICVs only one valve is added at a time so only the measured depth of that valve can be chosen.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ValveProperties_ICV.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen you have a valid valve template selected, there is an \u003cstrong\u003eEdit\u003c/strong\u003e button next to the valve template selection. Clicking this will take you straight to modify the valve template.\u003c/p\u003e\n\u003ch3 id=\"import-perforation-intervals\"\u003eImport Perforation Intervals\u003c/h3\u003e\n\u003cp\u003ePerforation intervals can be imported into ResInsight from \u003cem\u003e\u003ccode\u003e*.ev\u003c/code\u003e\u003c/em\u003e files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.\u003c/p\u003e\n\u003ch4 id=\"perforation-interval-file-format\"\u003ePerforation Interval File Format\u003c/h4\u003e\n\u003cp\u003e\u0026ldquo;\u0026ndash;\u0026rdquo; is interpreted as the start of a comment. The comment ends at the end of the line. \nThe files can start with a unit definition line:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eUNITS \u0026lt;unitname\u0026gt;\r\n\u003c/code\u003e\u003c/pre\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThis line is ignored for now. The numbers are interpreted to be in the units present in the case.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eIn the following any number of :\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWELLNAME \u0026lt;well-name\u0026gt;\r\n\u0026lt;date\u0026gt;  \u0026lt;well completion\u0026gt;  \u0026lt;top mMD\u0026gt;  \u0026lt;base mMD\u0026gt;   \u0026lt;bore hole diameter\u0026gt;  \u0026lt;skin factor\u0026gt;\r\n\u0026lt;date\u0026gt;  \u0026lt;well completion\u0026gt;  \u0026lt;top mMD\u0026gt;  \u0026lt;base mMD\u0026gt;   \u0026lt;bore hole diameter\u0026gt;  \u0026lt;skin factor\u0026gt;\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003edate\u003c/em\u003e \u0026ndash; Start date of the completion in the format \u0026ldquo;dd mmm yyyy\u0026rdquo;. Eg \u003ccode\u003e01 SEP 2006\u003c/code\u003e. A special \u003ccode\u003e\u0026quot;SOH\u0026quot;\u003c/code\u003edate is also allowed meaning Start Of History.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003ewell completion\u003c/em\u003e \u0026ndash; For now, only \u003ccode\u003e\u0026quot;perforation\u0026quot;\u003c/code\u003e is supported\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eHere is an example:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eUNITS METRIC\r\n\r\n-- R-2 AH sidetrack into Ile/Tilje\r\nWELLNAME R-2AH\r\n\u0026quot;SOH\u0026quot;   perforation 6200 6350 0.212 0   -- taget Ile 2 and Ile 3\r\n\u0026quot;SOH\u0026quot;   perforation 7050 7133 0.212 0   -- target Tilje 3, 83 m prodint\r\n\r\n-- S-2 AH\r\nWELLNAME S-2AH\r\n\u0026quot;SOH\u0026quot;   perforation 4340 4369 0.212 0   -- target Garn 2, 29 m prodint (update 290915)\r\n01 SEP 2006   perforation 5060 6185 0.212 0   -- target Tilje 3, 1125 m prodint\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch2 id=\"fishbones\"\u003eFishbones\u003c/h2\u003e\n\u003cp\u003eFishbones are completions created by drilling or by jetting a set of small lateral holes with a high deviation from the main bore.\nEach set of holes created at the same location along the main bore, is referred to as a \u003cem\u003esub\u003c/em\u003e while each individual hole is called a \u003cem\u003elateral\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eFor each well path there is a top level folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e containing all the Fishbones definitions containing settings that applies to all the fishbones for this well path. To make use of the Multi Segment Well option for pressure loss along laterals, the grid resolution needs to be fine enough to allow a grid cell to be connected to only one lateral.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_PropEdit.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFishbone Well Properties\u003c/strong\u003e \u0026ndash; Settings used when exporting well connection factors\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStartMD\u003c/strong\u003e \u0026ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMain Bore Diameter\u003c/strong\u003e \u0026ndash; The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMain Bore Skin Factor\u003c/strong\u003e \u0026ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore. \nFor multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Wells\u003c/strong\u003e - Options used by the Well Segments Export\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLiner Inner  eter\u003c/strong\u003e \u0026ndash; The liner inner diameter for the fishbones.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRoughness Factor\u003c/strong\u003e \u0026ndash; The roughness factor used in export of main bore segments.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePressure Drop\u003c/strong\u003e \u0026ndash; can be either \u003cem\u003eHydrostatic\u003c/em\u003e, \u003cem\u003eHydrostatic + Friction\u003c/em\u003e or \u003cem\u003eHydrostatic + Friction + Acceleration\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength and Depth\u003c/strong\u003e \u0026ndash; Used in WELSEGS export - when specifying the length and depth change for each segment\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eIncremental\u003c/strong\u003e \u0026ndash; length / depth of given segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbsolute\u003c/strong\u003e \u0026ndash; the length down the tube or depth of the last nodal point\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"fishbones-subs-definition\"\u003eFishbones Subs Definition\u003c/h3\u003e\n\u003cp\u003eTo add new fishbones completions, select the \u003cstrong\u003eNew Fishbones Subs Definition\u003c/strong\u003e command. This menu item is available by right clicking on \u003cstrong\u003eWells\u003c/strong\u003e in the Project Tree or right clicking on the well trajectory in the 3D View.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateCompletionOnWellPath.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003cstrong\u003eFishbones Subs Definition\u003c/strong\u003e (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 1/2\u0026rdquo; main bore.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_SubDefPropEdit.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFishbones Color\u003c/strong\u003e \u0026ndash; The 3D View color of the fishbones created by this definition\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLocation\u003c/strong\u003e \u0026ndash; Options to control the position and number of fishbone subs created by this definition\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLocation Defined By\u003c/strong\u003e \u0026ndash; This setting will select how to define the location of the subs in this group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart MD\u003c/strong\u003e \u0026ndash; Position, in Measured depth along the well, of the first fishbone Sub.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEnd MD\u003c/strong\u003e \u0026ndash; Position of the last fishbone Sub.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Subs\u003c/strong\u003e \u0026ndash; Defines the number of subs to create in the defined interval\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpacing\u003c/strong\u003e \u0026ndash; Spacing between the subs within the interval\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMeasured Depths\u003c/strong\u003e \u0026ndash; The measured depth of each of the fishbone subs. If the \u003cstrong\u003eLocation Defined By\u003c/strong\u003e is set to the \u003cstrong\u003eUser Specified\u003c/strong\u003e this will be directly editable by the user.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLaterals Configuration\u003c/strong\u003e \u0026ndash; Configures the laterals at each sub position.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLaterals Per Sub\u003c/strong\u003e \u0026ndash; Number of laterals for each sub position\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLenght(s)\u003c/strong\u003e \u0026ndash; Length of each lateral, in m or ft.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExit Angle\u003c/strong\u003e \u0026ndash; Exit angle for fishbone lateral, in degree.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBuild Angle\u003c/strong\u003e \u0026ndash; Build angle for fishbone lateral, in degree pr meter.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOrientation\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFixed Angle\u003c/strong\u003e \u0026ndash; The user can specify the angle for the first lateral\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRandom angle\u003c/strong\u003e \u0026ndash; Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInstall Success Rate\u003c/strong\u003e \u0026ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Properties\u003c/strong\u003e \u0026ndash; Settings to control the connection factor calculation used in \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e)\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHole Diameter\u003c/strong\u003e \u0026ndash; The hole diameter of the lateral\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; The skin factor used in the transmissibility calculation for the lateral.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMulti Segment Wells\u003c/strong\u003e \u0026ndash; Settings used for Well Segment Export\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTubing Diameter\u003c/strong\u003e \u0026ndash; The diameter used in the \u003cem\u003eWELSEGS\u003c/em\u003e export of the laterals.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOpen Hole Roughness Factor\u003c/strong\u003e \u0026ndash; Exported directly to the \u003cem\u003eWELSEGS\u003c/em\u003e keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTubing Roughness Factor\u003c/strong\u003e \u0026ndash; Exported directly to the \u003cem\u003eWELSEGS\u003c/em\u003e keyword.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICDs per Sub\u003c/strong\u003e \u0026ndash; The number of ICD (valves) per Sub, used for calculation of total ICD area for \u003cem\u003eWSEGVALV\u003c/em\u003e export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICD Orifice Diameter\u003c/strong\u003e \u0026ndash; The Diameter of the ICD, used for calculation of ICD area for \u003cem\u003eWSEGVALV\u003c/em\u003e export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eICD Flow Coefficient\u003c/strong\u003e \u0026ndash; The flow coefficient, exported directly as a part of \u003cem\u003eWSEGVALV\u003c/em\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"import-well-trajectories-as-fishbones-laterals\"\u003eImport Well Trajectories as Fishbones Laterals\u003c/h3\u003e\n\u003cp\u003eThe command \u003cstrong\u003eImport Completions From File\u003c/strong\u003e can be used to import well trajectories in the \u003cem\u003e\u003ccode\u003e*.dev\u003c/code\u003e\u003c/em\u003e format as fishbone laterals.  The imported laterals are listed under the folder \u003cstrong\u003eImported Laterals\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the \u003cstrong\u003eImported Laterals\u003c/strong\u003e folder.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Fishbones_LateralsMSWprop.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"export-fishbones-as-well-trajectories\"\u003eExport Fishbones as Well Trajectories\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eExport Laterals\u003c/strong\u003e command will export the fishbone laterals as a well trajectory into a  \u003cem\u003e\u003ccode\u003e*.dev*\u003c/code\u003e\u003c/em\u003e -file.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eNotice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to \u003c!-- raw HTML omitted --\u003e*.dev*\u003c!-- raw HTML omitted --\u003e files.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"fractures\"\u003eFractures\u003c/h2\u003e\n\u003cp\u003eHydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formation. A substance is then injected into the crack to keep it open when relaxing the pressure.\u003c/p\u003e\n\u003cp\u003eFractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Elliptical fractures and StimPlan fractures.\u003c/p\u003e\n\u003ch3 id=\"visualization-control\"\u003eVisualization control\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eFractures\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e controls whether to show the modeled fractures or not. For fractures along the well path the \u003cstrong\u003ePerforation Length\u003c/strong\u003e is shown as an olive green cylinder around the well path as shown in the image below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureVizControl.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e \u0026ndash; Control the color settings for the fractures in the View\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eResult Variable\u003c/strong\u003e \u0026ndash; Selects the fracture result to use for coloring the fracture. This is most interesting when you have imported a StimPlan fracture with varying width, conductivity and other parameters. The legend item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e controls how the legend is set up.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Color\u003c/strong\u003e \u0026ndash; The color to use if the requested result is not available for some fracture.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStimPlan\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Mesh\u003c/strong\u003e \u0026ndash; Toggles the visualization of the StimPlan mesh lines, showing the StimPlan cell borders\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColor Interpolation\u003c/strong\u003e \u0026ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"fracture-templates\"\u003eFracture Templates\u003c/h3\u003e\n\u003cp\u003eTo create a functioning fracture you first need a \u003cstrong\u003eFracture Template\u003c/strong\u003e. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.\u003c/p\u003e\n\u003cp\u003eFracture Templates are listed in a folder with the same name in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureTemplates.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo create a new fracture template, right-click the \u003cstrong\u003eFracture Template\u003c/strong\u003e item in the tree, and select either \u003cstrong\u003eNew Ellipse Fracture Template\u003c/strong\u003e or \u003cstrong\u003eNew StimPlan Fracture Template\u003c/strong\u003e. If you have no existing fracture templates, you will be given the opportunity to create such templates through two buttons in the Fracture Property Editor as seen below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateFractureTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"common-fracture-template-options\"\u003eCommon Fracture Template Options\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CommonFractureTemplateProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User defined name for the template. Used when selecting which template to use in the Fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eID\u003c/strong\u003e \u0026ndash; Assigned ID to be used when addressing this template form a Command file script\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; The fractures orientation\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTransverse(normal) to Well Path\u003c/strong\u003e \u0026ndash; The fracture plane is vertical and normal to the well path at the intersection point.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAlong Well Path\u003c/strong\u003e \u0026ndash; Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e \u0026ndash; The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUse Containment\u003c/strong\u003e \u0026ndash; Enable this option to activate layer containment.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTop Layer\u003c/strong\u003e \u0026ndash; Topmost K-layer that the fracture will drain.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase Layer\u003c/strong\u003e \u0026ndash; Lowest K-layer that the fracture will drain.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTruncate At Faults\u003c/strong\u003e \u0026ndash; Enable this option to activate fault truncation.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum Fault Throw\u003c/strong\u003e \u0026ndash; Fault throw threshold to activate fault truncation.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; The availability of these options depend on the \u003cstrong\u003eFracture Orientation\u003c/strong\u003e and the \u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e setting.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFinite Conductivity\u003c/strong\u003e \u0026ndash; Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInfinite Conductivity\u003c/strong\u003e \u0026ndash; Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the StimPlan data.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSkin Factor\u003c/strong\u003e \u0026ndash; Used when exporting to Eclipse.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Length\u003c/strong\u003e \u0026ndash; The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures \u003cstrong\u003eAlong Well Path\u003c/strong\u003e only ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Efficiency\u003c/strong\u003e \u0026ndash; The efficiency of the wellbore-fracture perforation ( Fractures \u003cstrong\u003eAlong Well Path\u003c/strong\u003e only ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Diameter\u003c/strong\u003e \u0026ndash; Used when exporting to Eclipse.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensitivity Scale Factors\u003c/strong\u003e \u0026ndash; Each of the properties are scaled by the scaling factor. When used interactively, the \u003cstrong\u003eApply\u003c/strong\u003e button must be pressed to apply the scaling factors. These scaling factors are also available from command file scripting\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHeight, Width\u003c/strong\u003e \u0026ndash; Scales the height or the \u003cem\u003e\u003cem\u003eHalflength\u003c/em\u003e\u003c/em\u003e of the fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD-factor\u003c/strong\u003e \u0026ndash; Scales the none-darcy flow factor\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity\u003c/strong\u003e \u0026ndash; Scales the conductivity in the fracture directly\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"non-darcy-flow\"\u003eNon-Darcy Flow\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureNonDarcyFlow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNon-Darcy Flow is used to improve the computation of connection factors for cells penetrated by well pipes. A pre-computed D-factor can be set using \u003cstrong\u003eUser Defined D-factor\u003c/strong\u003e. Selecting the option \u003cstrong\u003eCompute D-factor\u003c/strong\u003e displays the following set of properties:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInertial Coefficient\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Beta-factor in Forcheimer units\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Beta Factor\u003c/strong\u003e \u0026ndash; Extract beta factor from the fracture template at the well intersection location. For transversal fractures, the conductivity is computed from the geometric average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEffective Permeability\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Defines the permeability \u003cem\u003eKe\u003c/em\u003e in milliDarcy in the property \u003cstrong\u003eEffective Permeability\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Conductivity\u003c/strong\u003e \u0026ndash; Extract conductivity from the fracture template at the well intersection location and scale with \u003cstrong\u003eRelative Permeability\u003c/strong\u003e. For transversal fractures, the conductivity is computed from the weighted average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined\u003c/strong\u003e \u0026ndash; Defines the width of the fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUse Fracture Width\u003c/strong\u003e \u0026ndash; Extract width from the fracture template at the well intersection location. For transversal fractures, the width is based on the weighted average of fracture cells intersected by the fracture perforation length.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Gas Density\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas Viscosity\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD Factor\u003c/strong\u003e \u0026ndash; Displays the computed value of the D factor. NOTE : For \u003cem\u003etransversal fractures\u003c/em\u003e, the computed D factor is scaled by 1.2 to compensate for a different flow model\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eD Factor Details\u003c/strong\u003e \u0026ndash; Displays the value of variables used to compute the D factor\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"ellipse-fracture-template\"\u003eEllipse Fracture Template\u003c/h4\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/EllipseFractureTemplateProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User name of this particular fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHalflength X\u003c!-- raw HTML omitted --\u003er\u003c!-- raw HTML omitted --\u003e\u003c/strong\u003e \u0026ndash; Half the width of the ellipse\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHeight\u003c/strong\u003e \u0026ndash; The height of the elliptical fracture\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e \u0026ndash; The availability of these options depend on the \u003cstrong\u003eFracture Orientation\u003c/strong\u003e and the \u003cstrong\u003eConductivity in Fracture\u003c/strong\u003e setting\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability\u003c/strong\u003e \u0026ndash; A constant permeability inside the fracture (Used to calculate conductivity in the fracture)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e \u0026ndash; Crack width (Used to calculate conductivity in the fracture)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensivity Scale Factors\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"stimplan-fracture-template\"\u003eStimplan Fracture Template\u003c/h4\u003e\n\u003cp\u003eStimPlan fracture templates imports XML output from the StimPlan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting conductivity etc. as time varying quantities. Both symmetric and asymmetric StimPlan fracture templates are supported.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StimplanFractureTemplateProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User name of this particular fracture template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow StimPlan Mesh\u003c/strong\u003e \u0026ndash; Show or hide the mesh lines on the fracture in the 3D View\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInput\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile Name\u003c/strong\u003e \u0026ndash; Path to the imported StimPlan XML-file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eActive Time step Index\u003c/strong\u003e \u0026ndash; Time step in the StimPlan simulation to use for transmissibility calculations and visualization\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell/fracture Intersection Depth\u003c/strong\u003e \u0026ndash; The position of the fracture along the well path as MD.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometry\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Orientation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Truncation\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity Scaling Factor\u003c/strong\u003e \u0026ndash; Scale the overall conductivity to do sensitivity studies.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSensitivity Scale Factors\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNon-Darcy Flow\u003c/strong\u003e \u0026ndash; See above\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"fracture-instances\"\u003eFracture Instances\u003c/h3\u003e\n\u003cp\u003eInstances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FractureInstancePropertyPanel.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User editable name\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Template\u003c/strong\u003e \u0026ndash; Select the fracture template to use for this fracture. Click the \u003cstrong\u003eEdit\u003c/strong\u003e shortcut next to the template selection list to go directly to modify the selected template.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLocation/Orientation\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMeasured depth Location\u003c/strong\u003e \u0026ndash; The measured depth\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e \u0026ndash; Azimuth orientation of fracture.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e \u0026ndash; Dip of fracture plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTilt\u003c/strong\u003e \u0026ndash; Rotation of fracture about its plane normal\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Unit System\u003c/strong\u003e \u0026ndash; Read only display of the units used for the current template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStimPlan Time Step\u003c/strong\u003e \u0026ndash; Displays the time step used by the template\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Length\u003c/strong\u003e / \u003cstrong\u003ePerforation Efficiency\u003c/strong\u003e / \u003cstrong\u003eWell Diameter\u003c/strong\u003e \u0026ndash; These values are copied from the new template when selecting a different one. See \u003ca href=\"/wells-and-completions/completions/#common-fracture-template-options\"\u003eCommon Fracture Template Options\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFracture Center Info\u003c/strong\u003e \u0026ndash; This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"multiple-fracture-creation\"\u003eMultiple Fracture Creation\u003c/h3\u003e\n\u003cp\u003eIn some cases the user wants to create a number of fractures on one or more well paths. Doing this by creating one by one fracture can be very error prone and time consuming. To ease this task, ResInsight has support for creating several fractures in one operation.\u003c/p\u003e\n\u003cp\u003eSelect one or more well paths in the project tree, right click and select \u003cstrong\u003eCreate Multiple Fractures\u003c/strong\u003e from the right-click menu. Then the \u003cstrong\u003eCreate Multiple Fractures\u003c/strong\u003e dialog appears. In this dialog, the user defines where fractures will be created on the selected well paths. Different fracture templates and spacing can be used for different K layer ranges in the grid, by adding new options lines to the table. To edit an option line, double click the field to edit. Adding and deleting option lines are done by right clicking the table.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CreateMultipleFracturesDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Current grid case\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin Distance From Well TD\u003c/strong\u003e \u0026ndash; Minimum distance from well tip for created fractures\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax Fractures Per Well\u003c/strong\u003e \u0026ndash; Maximum number of fractures to create per well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTop K Layer\u003c/strong\u003e \u0026ndash; The topmost K layer to add fractures to\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBase K Layer\u003c/strong\u003e \u0026ndash; The bottommost K layer to add fractures to\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTemplate\u003c/strong\u003e \u0026ndash; The fracture template used in the specified K layer range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSpacing\u003c/strong\u003e \u0026ndash; The distance between each fracture in the K layer range\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerated Fractures\u003c/strong\u003e \u0026ndash; Output information to the user. Shows number of fractures that will be created on each selected well path\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eReplace Fractures\u003c/strong\u003e \u0026ndash; Press this button to delete all existing fractures on the selected wells before creating new fractures\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAdd Fractures\u003c/strong\u003e \u0026ndash; Press this button to add the new fractures to all selected wells (not deleting existing fractures)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe Create Multiple Fractures function is also available as a CommandFile command. See the \u003ca href=\"/scripting/commandfile/\"\u003eCommandFile section\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/wells-and-completions/completions/"
             };
         
@@ -2262,8 +2295,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/ensembleplotting/"] = {
                 title:    "Ensemble Plotting",
-                content:  " An ensemble is a group of cases that are tightly coupled, only a set of ensemble input parameters differ between cases. This makes it relevant to perform calculations and statistics analysis on ensembles.\nImport There are several ways to import an ensemble:\n Use menu option File-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Ensemble Use menu option File-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Summary Case group and then convert the group to an ensemble Import a number of summary cases, move them into a group and then convert the group to an ensemble  During import of a summary case, ResInsight tries to find an associated parameters.txt file or runspecification.xml file containing ensemble parameters. If found, the ensemble parameters are stored together with the summary case. When the user adds a summary case to an ensemble, then ResInsight will perform ensemble parameters validation. A warning dialog is displayed in the following cases:\n One or more of the cases in the ensemble have no ensemble parameters The list of ensemble parameters differ between cases in the ensemble  Plotting Ensembles are plotted in the summary plot the same way as ordinary summary curves. Create a new summary plot using the summary plot editor. Imported ensembles will appear in a separate group in the list of summary cases. When an ensemble is selected, a new curve set is created and plotted as multiple summary curves. By default all curves in an ensemble curve set will have the same color. The coloring mode may be edited in the curve set\u0026rsquo;s property editor in the project plot tree view. Two coloring modes are available:\n Single color Use the same color for all curves in a curve set By Ensemble Parameter One ensemble parameter is selected to control coloring. The ensemble parameter value for each case is used to pick a color in a color range. In this case a color legend appears.  Stepping of data source for ensemble curves is described in Summary Plot Source Stepping\nStatistics curves If the number of curves in a curve set is sufficient, ResInsight will calculate statistics for the curve set. The following statistics curves may be displayed:\n P10 \u0026ndash; 10% of the curves in the curve set are above this curve P50 \u0026ndash; 50% of the curves in the curve set are above this curve Mean \u0026ndash; Aritmetic mean for the curves in the curve set P90 \u0026ndash; 90% of the curves in the curve set are above this curve  Statistics curves may be toggled on or off in the curve set\u0026rsquo;s property editor.\nExample:\nDerived Ensembles New ensembles can be created based on calculations on two or more ensembles. Such ensembles are called \u0026lsquo;derived ensembles\u0026rsquo;. A derived ensemble will contain data which are either the sum or difference between two other ensembles. An existing derived ensemble may be input to a new derived ensemble, making it possible to for instance add more than two ensembles.\nTo create a derived ensemble, select two existing ensembled in the project tree. Right click and select New Derived Ensenble. A new derived ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the new ensemble, both input ensembles and operator can be modified.\nIf the two input ensembles differs in which cases they consist of, ResInsight will display a warning and let the user decide whether to create the derived ensemble or not.\n",
-                html:     "\n\n\u003cp\u003eAn ensemble is a group of cases that are tightly coupled, only a set of ensemble input parameters differ between cases. This makes it relevant to perform calculations and statistics analysis on ensembles.\u003c/p\u003e\n\n\u003ch2 id=\"import\"\u003eImport\u003c/h2\u003e\n\n\u003cp\u003eThere are several ways to import an ensemble:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eUse menu option \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Ensemble\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eUse menu option \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Summary Case group\u003c/strong\u003e and then convert the group to an ensemble\u003c/li\u003e\n\u003cli\u003eImport a number of summary cases, move them into a group and then convert the group to an ensemble\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eDuring import of a summary case, ResInsight tries to find an associated \u003cstrong\u003eparameters.txt\u003c/strong\u003e file or \u003cstrong\u003erunspecification.xml\u003c/strong\u003e file containing ensemble parameters. If found, the ensemble parameters are stored together with the summary case. When the user adds a summary case to an ensemble, then ResInsight will perform ensemble parameters validation. A warning dialog is displayed in the following cases:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eOne or more of the cases in the ensemble have no ensemble parameters\u003c/li\u003e\n\u003cli\u003eThe list of ensemble parameters differ between cases in the ensemble\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"plotting\"\u003ePlotting\u003c/h2\u003e\n\n\u003cp\u003eEnsembles are plotted in the summary plot the same way as ordinary summary curves. Create a new summary plot using the \u003ca href=\"/plot-window/summaryploteditor/\"\u003esummary plot editor\u003c/a\u003e. Imported ensembles will appear in a separate group in the list of summary cases. When an ensemble is selected, a new curve set is created and plotted as multiple summary curves. By default all curves in an ensemble curve set will have the same color. The coloring mode may be edited in the curve set\u0026rsquo;s property editor in the project plot tree view. Two coloring modes are available:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSingle color\u003c/strong\u003e Use the same color for all curves in a curve set\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Ensemble Parameter\u003c/strong\u003e One ensemble parameter is selected to control coloring. The ensemble parameter value for each case is used to pick a color in a color range. In this case a color legend appears.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eStepping of data source for ensemble curves is described in \u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"statistics-curves\"\u003eStatistics curves\u003c/h3\u003e\n\n\u003cp\u003eIf the number of curves in a curve set is sufficient, ResInsight will calculate statistics for the curve set. The following statistics curves may be displayed:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eP10\u003c/strong\u003e \u0026ndash; 10% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eP50\u003c/strong\u003e \u0026ndash; 50% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMean\u003c/strong\u003e \u0026ndash; Aritmetic mean for the curves in the curve set\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eP90\u003c/strong\u003e \u0026ndash; 90% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eStatistics curves may be toggled on or off in the curve set\u0026rsquo;s property editor.\u003c/p\u003e\n\n\u003cp\u003eExample:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Ensemble.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"derived-ensembles\"\u003eDerived Ensembles\u003c/h2\u003e\n\n\u003cp\u003eNew ensembles can be created based on calculations on two or more ensembles. Such ensembles are called \u0026lsquo;derived ensembles\u0026rsquo;. A derived ensemble will contain data which are either the sum or difference between two other ensembles. An existing derived ensemble may be input to a new derived ensemble, making it possible to for instance add more than two ensembles.\u003c/p\u003e\n\n\u003cp\u003eTo create a derived ensemble, select two existing ensembled in the project tree. Right click and select \u003cstrong\u003eNew Derived Ensenble\u003c/strong\u003e. A new derived ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the new ensemble, both input ensembles and operator can be modified.\u003c/p\u003e\n\n\u003cp\u003eIf the two input ensembles differs in which cases they consist of, ResInsight will display a warning and let the user decide whether to create the derived ensemble or not.\u003c/p\u003e\n",
+                content:  "An ensemble is a group of cases that are tightly coupled, only a set of ensemble input parameters differ between cases. This makes it relevant to perform calculations and statistics analysis on ensembles.\nImport There are several ways to import an ensemble:\n Use menu option File-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Ensemble Use menu option File-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Summary Case group and then convert the group to an ensemble Import a number of summary cases, move them into a group and then convert the group to an ensemble  During import of a summary case, ResInsight tries to find an associated parameters.txt file or runspecification.xml file containing ensemble parameters. If found, the ensemble parameters are stored together with the summary case. When the user adds a summary case to an ensemble, then ResInsight will perform ensemble parameters validation. A warning dialog is displayed in the following cases:\n One or more of the cases in the ensemble have no ensemble parameters The list of ensemble parameters differ between cases in the ensemble  Plotting Ensembles are plotted in the summary plot the same way as ordinary summary curves. Create a new summary plot using the summary plot editor. Imported ensembles will appear in a separate group in the list of summary cases. When an ensemble is selected, a new curve set is created and plotted as multiple summary curves. By default all curves in an ensemble curve set will have the same color. The coloring mode may be edited in the curve set\u0026rsquo;s property editor in the project plot tree view. Two coloring modes are available:\n Single color Use the same color for all curves in a curve set By Ensemble Parameter One ensemble parameter is selected to control coloring. The ensemble parameter value for each case is used to pick a color in a color range. In this case a color legend appears.  Stepping of data source for ensemble curves is described in Summary Plot Source Stepping\nStatistics curves If the number of curves in a curve set is sufficient, ResInsight will calculate statistics for the curve set. The following statistics curves may be displayed:\n P10 \u0026ndash; 10% of the curves in the curve set are above this curve P50 \u0026ndash; 50% of the curves in the curve set are above this curve Mean \u0026ndash; Aritmetic mean for the curves in the curve set P90 \u0026ndash; 90% of the curves in the curve set are above this curve  Statistics curves may be toggled on or off in the curve set\u0026rsquo;s property editor.\nExample:\nDerived Ensembles New ensembles can be created based on calculations on two or more ensembles. Such ensembles are called \u0026lsquo;derived ensembles\u0026rsquo;. A derived ensemble will contain data which are either the sum or difference between two other ensembles. An existing derived ensemble may be input to a new derived ensemble, making it possible to for instance add more than two ensembles.\nTo create a derived ensemble, select two existing ensembled in the project tree. Right click and select New Derived Ensenble. A new derived ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the new ensemble, both input ensembles and operator can be modified.\nIf the two input ensembles differs in which cases they consist of, ResInsight will display a warning and let the user decide whether to create the derived ensemble or not.\n",
+                html:     "\u003cp\u003eAn ensemble is a group of cases that are tightly coupled, only a set of ensemble input parameters differ between cases. This makes it relevant to perform calculations and statistics analysis on ensembles.\u003c/p\u003e\n\u003ch2 id=\"import\"\u003eImport\u003c/h2\u003e\n\u003cp\u003eThere are several ways to import an ensemble:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUse menu option \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Ensemble\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eUse menu option \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Summary Cases-\u0026gt;Import Summary Case group\u003c/strong\u003e and then convert the group to an ensemble\u003c/li\u003e\n\u003cli\u003eImport a number of summary cases, move them into a group and then convert the group to an ensemble\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eDuring import of a summary case, ResInsight tries to find an associated \u003cstrong\u003eparameters.txt\u003c/strong\u003e file or \u003cstrong\u003erunspecification.xml\u003c/strong\u003e file containing ensemble parameters. If found, the ensemble parameters are stored together with the summary case. When the user adds a summary case to an ensemble, then ResInsight will perform ensemble parameters validation. A warning dialog is displayed in the following cases:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOne or more of the cases in the ensemble have no ensemble parameters\u003c/li\u003e\n\u003cli\u003eThe list of ensemble parameters differ between cases in the ensemble\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"plotting\"\u003ePlotting\u003c/h2\u003e\n\u003cp\u003eEnsembles are plotted in the summary plot the same way as ordinary summary curves. Create a new summary plot using the \u003ca href=\"/plot-window/summaryploteditor/\"\u003esummary plot editor\u003c/a\u003e. Imported ensembles will appear in a separate group in the list of summary cases. When an ensemble is selected, a new curve set is created and plotted as multiple summary curves. By default all curves in an ensemble curve set will have the same color. The coloring mode may be edited in the curve set\u0026rsquo;s property editor in the project plot tree view. Two coloring modes are available:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSingle color\u003c/strong\u003e Use the same color for all curves in a curve set\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Ensemble Parameter\u003c/strong\u003e One ensemble parameter is selected to control coloring. The ensemble parameter value for each case is used to pick a color in a color range. In this case a color legend appears.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eStepping of data source for ensemble curves is described in \u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"statistics-curves\"\u003eStatistics curves\u003c/h3\u003e\n\u003cp\u003eIf the number of curves in a curve set is sufficient, ResInsight will calculate statistics for the curve set. The following statistics curves may be displayed:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eP10\u003c/strong\u003e \u0026ndash; 10% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eP50\u003c/strong\u003e \u0026ndash; 50% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMean\u003c/strong\u003e \u0026ndash; Aritmetic mean for the curves in the curve set\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eP90\u003c/strong\u003e \u0026ndash; 90% of the curves in the curve set are above this curve\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eStatistics curves may be toggled on or off in the curve set\u0026rsquo;s property editor.\u003c/p\u003e\n\u003cp\u003eExample:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"derived-ensembles\"\u003eDerived Ensembles\u003c/h2\u003e\n\u003cp\u003eNew ensembles can be created based on calculations on two or more ensembles. Such ensembles are called \u0026lsquo;derived ensembles\u0026rsquo;. A derived ensemble will contain data which are either the sum or difference between two other ensembles. An existing derived ensemble may be input to a new derived ensemble, making it possible to for instance add more than two ensembles.\u003c/p\u003e\n\u003cp\u003eTo create a derived ensemble, select two existing ensembled in the project tree. Right click and select \u003cstrong\u003eNew Derived Ensenble\u003c/strong\u003e. A new derived ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the new ensemble, both input ensembles and operator can be modified.\u003c/p\u003e\n\u003cp\u003eIf the two input ensembles differs in which cases they consist of, ResInsight will display a warning and let the user decide whether to create the derived ensemble or not.\u003c/p\u003e\n",
                 url:      "/plot-window/ensembleplotting/"
             };
         
@@ -2272,7 +2305,7 @@ if (!doNotTrack) {
             window.store["/import/"] = {
                 title:    "Import",
                 content:  "ResInsight is able to import the following type of Eclipse files:\n *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. Grid and Property data from *.GRDECL files.  For functionality and import of Eclipse data pertinent to summary vectors and well log data, see Plot Window.\nResInsight can be built with support for geomechanical models from ABAQUS and is also able to import transient reservoir souring data from the SourSimRL simulation software.\nFurthermore, ResInsight supports import of property tables in ABQUS input file format, observed time history data, and pasting time history data into a summary plot as described in the subsequent subchapters.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/import/GeoMechImport.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight is able to import the following type of Eclipse files:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eGrid and Property data from  \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eFor functionality and import of Eclipse data pertinent to summary vectors and well log data, see \u003ca href=\"\"\u003ePlot Window\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eResInsight can be built with support for geomechanical models from ABAQUS and is also able to import\ntransient reservoir souring data from the SourSimRL simulation software.\u003c/p\u003e\n\n\u003cp\u003eFurthermore, ResInsight supports import of property tables in ABQUS input file format,\nobserved time history data, and pasting time history data into a summary plot\nas described in the subsequent subchapters.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/import/GeoMechImport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight is able to import the following type of Eclipse files:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eGrid and Property data from  \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFor functionality and import of Eclipse data pertinent to summary vectors and well log data, see \u003ca href=\"\"\u003ePlot Window\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eResInsight can be built with support for geomechanical models from ABAQUS and is also able to import \ntransient reservoir souring data from the SourSimRL simulation software.\u003c/p\u003e\n\u003cp\u003eFurthermore, ResInsight supports import of property tables in ABQUS input file format, \nobserved time history data, and pasting time history data into a summary plot\nas described in the subsequent subchapters.\u003c/p\u003e\n",
                 url:      "/import/"
             };
         
@@ -2280,8 +2313,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/octaveinterface/"] = {
                 title:    "Octave Interface",
-                content:  " ResInsight provides a flexible interface to Octave including:\n Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.\n  The Octave functions are documented in Octave Interface Reference.\nNote: The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.\n\rOctave Script Management Octave scripts are available in the Scripts folder in the Project Tree.\nThis folder contains an entry for each of the directories you have added as a Script Folder. Each of the folder lists available *.m files and sub directories.\nAdding Script Folders You can add directories by right-clicking the Scripts item to access the right-click menu.\nMultiple standard script folder locations can also be defined in the field Shared Script Folder(s) in the Preferences Dialog (Edit -\u0026gt; Preferences).\nEditing Octave Scripts To enable script editing from ResInsight you need to set up the path to a text editor in the Script Editor field in the Preferences Dialog (Edit -\u0026gt; Preferences)\nWhen done, scripts can be edited using the right-click menu command Edit on the script item in the tree.\nIf you add a script file directly by creating a new file, the new script can be made visible in the user interface by activating Refresh in the right-click menu of a script folder.\nExecuting Octave Scripts ResInsight can be instructed to execute an Octave script once as a one shot operation, or several times, one time for each selected case. The Octave Interface Reference highlights in more depth how to design your Octave scripts to utilize these features.\nExecuting a Script Once A script can be started by navigating to the script in the Project Tree, and selecting Execute from the right-click menu. The currently active case (The one with the active 3D View) will then be set as ResInsight\u0026rsquo;s Current Case, and the script is executed once.\nExecuting a Script for Each Selected Case One script can be executed on many cases by first selecting a set of cases, and then activating Execute script from the right-click menu on the case selection. The script is then executed once per selected case setting the ResInsight\u0026rsquo;s Current Case each time.\nProcess Monitor When an Octave script is executed, the Process Monitor pops up and displays the output from Octave during the script execution as displayed below:\nIn addition to the output from the script, it prints a start and stop time stamp. The Clear-button deletes all the text in the monitor, and the Stop-button tries to kill the running Octave process.\nOctave Script Examples Here are some example-scripts that illustrates the use of the octave interface.\nDisclaimer: The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.\n\rExample 1 # Calculate change of oil saturation from time step to time step SOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;); SOILDIFF = SOIL; i = 0; for timestep = SOIL if (i \u0026gt; 0) SOILDIFF(:,i) = timestep - SOIL(:,i); endif i++; endfor SOILDIFF(:,i) = 0; riSetActiveCellProperty(SOILDIFF, \u0026quot;SOILDIFF\u0026quot;);  Example 2 # Set all values to \u0026quot;Undefined\u0026quot; exept k-layers from 17 to 20 CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;); Mask = (CInfo(:,4) \u0026lt; 17) | (CInfo(:,4) \u0026gt; 20) LGRSOIL = SOIL; i = 0; for i = (1:columns(LGRSOIL)) LGRSOIL(Mask,i) = nan; endfor riSetActiveCellProperty(LGRSOIL, \u0026quot;KSlice\u0026quot;);  Example 3 # Keep the values in the first LGR only CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;); Mask = (CInfo(:,1) != 1); LGRSOIL = SOIL; i = 0; for i = (1:columns(LGRSOIL)) LGRSOIL(Mask,i) = nan; endfor riSetActiveCellProperty(LGRSOIL, \u0026quot;LGRSOIL\u0026quot;);  Example 4 ( Might be slow on big models) # Calculate the average SOIL value across K layers CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;); SOIL_KAverage = SOIL; SOIL_KAverage(:) = nan; mini = min(CInfo(:,2)) maxi = max(CInfo(:,2)) minj = min(CInfo(:,3)) maxj = max(CInfo(:,3)) for i = mini:maxi for j = minj:maxj Mask = (CInfo(:,1) == 0) \u0026amp; (CInfo(:,2) == i) \u0026amp; (CInfo(:,3) == j) ; for ts = (1:columns(SOIL)) SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts)); endfor endfor endfor riSetActiveCellProperty(SOIL_KAverage, \u0026quot;SOIL_KAverage\u0026quot;);  ",
-                html:     "\n\n\u003cp\u003eResInsight provides a flexible interface to \u003ca href=\"http://www.gnu.org/software/octave/\" title=\"Octave\"\u003eOctave\u003c/a\u003e including:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eOctave functions that communicates with a running ResInsight session\u003c/li\u003e\n\u003cli\u003eFeatures to simplify management and editing of Octave scripts from ResInsight\u003c/li\u003e\n\u003cli\u003eCommands to execute scripts using Octave.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe Octave functions are documented in \u003ca href=\"/scripting/octaveinterfacereference/\"\u003eOctave Interface Reference\u003c/a\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003cb\u003eNote:\u003c/b\u003e The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"octave-script-management\"\u003eOctave Script Management\u003c/h2\u003e\n\n\u003cp\u003eOctave scripts are available in the \u003cstrong\u003eScripts\u003c/strong\u003e folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/OctaveScriptTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis folder contains an entry for each of the directories you have added as a \u003cstrong\u003eScript Folder\u003c/strong\u003e. Each of the folder lists available \u003cem\u003e\u003ccode\u003e*.m\u003c/code\u003e\u003c/em\u003e files and sub directories.\u003c/p\u003e\n\n\u003ch3 id=\"adding-script-folders\"\u003eAdding Script Folders\u003c/h3\u003e\n\n\u003cp\u003eYou can add directories by right-clicking the \u003cstrong\u003eScripts\u003c/strong\u003e item to access the right-click menu.\u003c/p\u003e\n\n\u003cp\u003eMultiple standard script folder locations can also be defined in the field \u003cstrong\u003eShared Script Folder(s)\u003c/strong\u003e in the \u003cstrong\u003ePreferences Dialog\u003c/strong\u003e (\u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e).\u003c/p\u003e\n\n\u003ch3 id=\"editing-octave-scripts\"\u003eEditing Octave Scripts\u003c/h3\u003e\n\n\u003cp\u003eTo enable script editing from ResInsight you need to set up the path to a text editor in the \u003cstrong\u003eScript Editor\u003c/strong\u003e field in the \u003cstrong\u003ePreferences Dialog\u003c/strong\u003e (\u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e)\u003c/p\u003e\n\n\u003cp\u003eWhen done, scripts can be edited using the right-click menu command \u003cstrong\u003eEdit\u003c/strong\u003e on the script item in the tree.\u003c/p\u003e\n\n\u003cp\u003eIf you add a script file directly by creating a new file, the new script can be made visible in the user interface by activating \u003cstrong\u003eRefresh\u003c/strong\u003e in the right-click menu of a script folder.\u003c/p\u003e\n\n\u003ch2 id=\"executing-octave-scripts\"\u003eExecuting Octave Scripts\u003c/h2\u003e\n\n\u003cp\u003eResInsight can be instructed to execute an Octave script once as a one shot operation, or several times, one time for each selected case. The \u003ca href=\"/scripting/octaveinterfacereference/\"\u003eOctave Interface Reference\u003c/a\u003e highlights in more depth how to design your Octave scripts to utilize these features.\u003c/p\u003e\n\n\u003ch3 id=\"executing-a-script-once\"\u003eExecuting a Script Once\u003c/h3\u003e\n\n\u003cp\u003eA script can be started by navigating to the script in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and selecting \u003cstrong\u003eExecute\u003c/strong\u003e from the right-click menu. The currently active case (The one with the active 3D View) will then be set as ResInsight\u0026rsquo;s \u003cem\u003eCurrent Case\u003c/em\u003e, and the script is executed once.\u003c/p\u003e\n\n\u003ch3 id=\"executing-a-script-for-each-selected-case\"\u003eExecuting a Script for Each Selected Case\u003c/h3\u003e\n\n\u003cp\u003eOne script can be executed on many cases by first selecting a set of cases, and then activating \u003cstrong\u003eExecute script\u003c/strong\u003e from the right-click menu on the case selection. The script is then executed once per selected case setting the ResInsight\u0026rsquo;s \u003cem\u003eCurrent Case\u003c/em\u003e each time.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/ExecuteOctaveScriptOnSelectedCases.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"process-monitor\"\u003eProcess Monitor\u003c/h3\u003e\n\n\u003cp\u003eWhen an Octave script is executed, the \u003cstrong\u003eProcess Monitor\u003c/strong\u003e pops up and displays the output from Octave during the script execution as displayed below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/ProcessMonitor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn addition to the output from the script, it prints a start and stop time stamp. The \u003cstrong\u003eClear\u003c/strong\u003e-button deletes all the text in the monitor, and the \u003cstrong\u003eStop\u003c/strong\u003e-button tries to kill the running Octave process.\u003c/p\u003e\n\n\u003ch2 id=\"octave-script-examples\"\u003eOctave Script Examples\u003c/h2\u003e\n\n\u003cp\u003eHere are some example-scripts that illustrates the use of the octave interface.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003cb\u003eDisclaimer:\u003c/b\u003e The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"example-1\"\u003eExample 1\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode class=\"language-matlab\"\u003e# Calculate change of oil saturation from time step to time step\nSOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;);\nSOILDIFF = SOIL;\n\ni = 0;\nfor timestep = SOIL\n    if (i \u0026gt; 0) \n        SOILDIFF(:,i) = timestep - SOIL(:,i);\n    endif\n    i++;\nendfor\nSOILDIFF(:,i) = 0;\n\nriSetActiveCellProperty(SOILDIFF, \u0026quot;SOILDIFF\u0026quot;);\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"example-2\"\u003eExample 2\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode class=\"language-matlab\"\u003e# Set all values to \u0026quot;Undefined\u0026quot; exept k-layers from 17 to 20\nCInfo = riGetActiveCellInfo();\nSOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;);\n\nMask = (CInfo(:,4) \u0026lt; 17) | (CInfo(:,4) \u0026gt; 20)\nLGRSOIL = SOIL;\ni = 0;\nfor i = (1:columns(LGRSOIL))\n    LGRSOIL(Mask,i) = nan;\nendfor\n\nriSetActiveCellProperty(LGRSOIL, \u0026quot;KSlice\u0026quot;);\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"example-3\"\u003eExample 3\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode class=\"language-matlab\"\u003e# Keep the values in the first LGR only\n\nCInfo = riGetActiveCellInfo();\nSOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;);\n\nMask = (CInfo(:,1) != 1);\n\nLGRSOIL = SOIL;\ni = 0;\nfor i = (1:columns(LGRSOIL))\n    LGRSOIL(Mask,i) = nan;\nendfor\n\nriSetActiveCellProperty(LGRSOIL, \u0026quot;LGRSOIL\u0026quot;);\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"example-4-might-be-slow-on-big-models\"\u003eExample 4 ( Might be slow on big models)\u003c/h4\u003e\n\n\u003cpre\u003e\u003ccode class=\"language-matlab\"\u003e# Calculate the average SOIL value across K layers\n\nCInfo = riGetActiveCellInfo();\nSOIL = riGetActiveCellProperty(\u0026quot;SOIL\u0026quot;);\n\nSOIL_KAverage = SOIL;\nSOIL_KAverage(:) = nan;\n\nmini = min(CInfo(:,2))\nmaxi = max(CInfo(:,2))\n\nminj = min(CInfo(:,3))\nmaxj = max(CInfo(:,3))\n\nfor i = mini:maxi\n  for j = minj:maxj \n    Mask = (CInfo(:,1) == 0) \u0026amp; (CInfo(:,2) == i) \u0026amp; (CInfo(:,3) == j) ;\n\n    for ts = (1:columns(SOIL)) \n      SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));\n    endfor\n  endfor\nendfor\n\nriSetActiveCellProperty(SOIL_KAverage, \u0026quot;SOIL_KAverage\u0026quot;);\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "ResInsight provides a flexible interface to Octave including:\n Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.  The Octave functions are documented in Octave Interface Reference.\nNote:The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.\n\rOctave Script Management Octave scripts are available in the Scripts folder in the Project Tree.\nThis folder contains an entry for each of the directories you have added as a Script Folder. Each of the folder lists available *.m files and sub directories.\nAdding Script Folders You can add directories by right-clicking the Scripts item to access the right-click menu.\nMultiple standard script folder locations can also be defined in the field Shared Script Folder(s) in the Preferences Dialog (Edit -\u0026gt; Preferences).\nEditing Octave Scripts To enable script editing from ResInsight you need to set up the path to a text editor in the Script Editor field in the Preferences Dialog (Edit -\u0026gt; Preferences)\nWhen done, scripts can be edited using the right-click menu command Edit on the script item in the tree.\nIf you add a script file directly by creating a new file, the new script can be made visible in the user interface by activating Refresh in the right-click menu of a script folder.\nExecuting Octave Scripts ResInsight can be instructed to execute an Octave script once as a one shot operation, or several times, one time for each selected case. The Octave Interface Reference highlights in more depth how to design your Octave scripts to utilize these features.\nExecuting a Script Once A script can be started by navigating to the script in the Project Tree, and selecting Execute from the right-click menu. The currently active case (The one with the active 3D View) will then be set as ResInsight\u0026rsquo;s Current Case, and the script is executed once.\nExecuting a Script for Each Selected Case One script can be executed on many cases by first selecting a set of cases, and then activating Execute script from the right-click menu on the case selection. The script is then executed once per selected case setting the ResInsight\u0026rsquo;s Current Case each time.\nProcess Monitor When an Octave script is executed, the Process Monitor pops up and displays the output from Octave during the script execution as displayed below:\nIn addition to the output from the script, it prints a start and stop time stamp. The Clear-button deletes all the text in the monitor, and the Stop-button tries to kill the running Octave process.\nOctave Script Examples Here are some example-scripts that illustrates the use of the octave interface.\nDisclaimer:The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.\n\rExample 1 # Calculate change of oil saturation from time step to time step\rSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\rSOILDIFF = SOIL;\ri = 0;\rfor timestep = SOIL\rif (i \u0026gt; 0) SOILDIFF(:,i) = timestep - SOIL(:,i);\rendif\ri++;\rendfor\rSOILDIFF(:,i) = 0;\rriSetActiveCellProperty(SOILDIFF, \u0026#34;SOILDIFF\u0026#34;);\rExample 2 # Set all values to \u0026#34;Undefined\u0026#34; exept k-layers from 17 to 20\rCInfo = riGetActiveCellInfo();\rSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\rMask = (CInfo(:,4) \u0026lt; 17) | (CInfo(:,4) \u0026gt; 20)\rLGRSOIL = SOIL;\ri = 0;\rfor i = (1:columns(LGRSOIL))\rLGRSOIL(Mask,i) = nan;\rendfor\rriSetActiveCellProperty(LGRSOIL, \u0026#34;KSlice\u0026#34;);\rExample 3 # Keep the values in the first LGR only\rCInfo = riGetActiveCellInfo();\rSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\rMask = (CInfo(:,1) != 1);\rLGRSOIL = SOIL;\ri = 0;\rfor i = (1:columns(LGRSOIL))\rLGRSOIL(Mask,i) = nan;\rendfor\rriSetActiveCellProperty(LGRSOIL, \u0026#34;LGRSOIL\u0026#34;);\rExample 4 ( Might be slow on big models) # Calculate the average SOIL value across K layers\rCInfo = riGetActiveCellInfo();\rSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\rSOIL_KAverage = SOIL;\rSOIL_KAverage(:) = nan;\rmini = min(CInfo(:,2))\rmaxi = max(CInfo(:,2))\rminj = min(CInfo(:,3))\rmaxj = max(CInfo(:,3))\rfor i = mini:maxi\rfor j = minj:maxj Mask = (CInfo(:,1) == 0) \u0026amp; (CInfo(:,2) == i) \u0026amp; (CInfo(:,3) == j) ;\rfor ts = (1:columns(SOIL)) SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));\rendfor\rendfor\rendfor\rriSetActiveCellProperty(SOIL_KAverage, \u0026#34;SOIL_KAverage\u0026#34;);\r",
+                html:     "\u003cp\u003eResInsight provides a flexible interface to \u003ca href=\"http://www.gnu.org/software/octave/\" title=\"Octave\"\u003eOctave\u003c/a\u003e including:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOctave functions that communicates with a running ResInsight session\u003c/li\u003e\n\u003cli\u003eFeatures to simplify management and editing of Octave scripts from ResInsight\u003c/li\u003e\n\u003cli\u003eCommands to execute scripts using Octave.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe Octave functions are documented in \u003ca href=\"/scripting/octaveinterfacereference/\"\u003eOctave Interface Reference\u003c/a\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eNote:\u003c!-- raw HTML omitted --\u003e The Octave interface does not support Flow diagnostics and Injection flooding results in addition to Geomechanical cases.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"octave-script-management\"\u003eOctave Script Management\u003c/h2\u003e\n\u003cp\u003eOctave scripts are available in the \u003cstrong\u003eScripts\u003c/strong\u003e folder in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/OctaveScriptTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis folder contains an entry for each of the directories you have added as a \u003cstrong\u003eScript Folder\u003c/strong\u003e. Each of the folder lists available \u003cem\u003e\u003ccode\u003e*.m\u003c/code\u003e\u003c/em\u003e files and sub directories.\u003c/p\u003e\n\u003ch3 id=\"adding-script-folders\"\u003eAdding Script Folders\u003c/h3\u003e\n\u003cp\u003eYou can add directories by right-clicking the \u003cstrong\u003eScripts\u003c/strong\u003e item to access the right-click menu.\u003c/p\u003e\n\u003cp\u003eMultiple standard script folder locations can also be defined in the field \u003cstrong\u003eShared Script Folder(s)\u003c/strong\u003e in the \u003cstrong\u003ePreferences Dialog\u003c/strong\u003e (\u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e).\u003c/p\u003e\n\u003ch3 id=\"editing-octave-scripts\"\u003eEditing Octave Scripts\u003c/h3\u003e\n\u003cp\u003eTo enable script editing from ResInsight you need to set up the path to a text editor in the \u003cstrong\u003eScript Editor\u003c/strong\u003e field in the \u003cstrong\u003ePreferences Dialog\u003c/strong\u003e (\u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e)\u003c/p\u003e\n\u003cp\u003eWhen done, scripts can be edited using the right-click menu command \u003cstrong\u003eEdit\u003c/strong\u003e on the script item in the tree.\u003c/p\u003e\n\u003cp\u003eIf you add a script file directly by creating a new file, the new script can be made visible in the user interface by activating \u003cstrong\u003eRefresh\u003c/strong\u003e in the right-click menu of a script folder.\u003c/p\u003e\n\u003ch2 id=\"executing-octave-scripts\"\u003eExecuting Octave Scripts\u003c/h2\u003e\n\u003cp\u003eResInsight can be instructed to execute an Octave script once as a one shot operation, or several times, one time for each selected case. The \u003ca href=\"/scripting/octaveinterfacereference/\"\u003eOctave Interface Reference\u003c/a\u003e highlights in more depth how to design your Octave scripts to utilize these features.\u003c/p\u003e\n\u003ch3 id=\"executing-a-script-once\"\u003eExecuting a Script Once\u003c/h3\u003e\n\u003cp\u003eA script can be started by navigating to the script in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and selecting \u003cstrong\u003eExecute\u003c/strong\u003e from the right-click menu. The currently active case (The one with the active 3D View) will then be set as ResInsight\u0026rsquo;s \u003cem\u003eCurrent Case\u003c/em\u003e, and the script is executed once.\u003c/p\u003e\n\u003ch3 id=\"executing-a-script-for-each-selected-case\"\u003eExecuting a Script for Each Selected Case\u003c/h3\u003e\n\u003cp\u003eOne script can be executed on many cases by first selecting a set of cases, and then activating \u003cstrong\u003eExecute script\u003c/strong\u003e from the right-click menu on the case selection. The script is then executed once per selected case setting the ResInsight\u0026rsquo;s \u003cem\u003eCurrent Case\u003c/em\u003e each time.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/ExecuteOctaveScriptOnSelectedCases.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"process-monitor\"\u003eProcess Monitor\u003c/h3\u003e\n\u003cp\u003eWhen an Octave script is executed, the \u003cstrong\u003eProcess Monitor\u003c/strong\u003e pops up and displays the output from Octave during the script execution as displayed below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/ProcessMonitor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn addition to the output from the script, it prints a start and stop time stamp. The \u003cstrong\u003eClear\u003c/strong\u003e-button deletes all the text in the monitor, and the \u003cstrong\u003eStop\u003c/strong\u003e-button tries to kill the running Octave process.\u003c/p\u003e\n\u003ch2 id=\"octave-script-examples\"\u003eOctave Script Examples\u003c/h2\u003e\n\u003cp\u003eHere are some example-scripts that illustrates the use of the octave interface.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eDisclaimer:\u003c!-- raw HTML omitted --\u003e The scripts are provided as illustration only. They are probably not the best way of using the octave script language, and could potentially be incorrect.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"example-1\"\u003eExample 1\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"\u003e\u003ccode class=\"language-matlab\" data-lang=\"matlab\"\u003e# Calculate change of oil saturation from time step to time step\r\nSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\r\nSOILDIFF = SOIL;\r\n\r\ni = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\r\n\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e timestep = SOIL\r\n\t\u003cspan style=\"color:#66d9ef\"\u003eif\u003c/span\u003e (i \u003cspan style=\"color:#f92672\"\u003e\u0026gt;\u003c/span\u003e \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e) \r\n\t\tSOILDIFF(:,i) = timestep \u003cspan style=\"color:#f92672\"\u003e-\u003c/span\u003e SOIL(:,i);\r\n\tendif\r\n\ti\u003cspan style=\"color:#f92672\"\u003e++\u003c/span\u003e;\r\nendfor\r\nSOILDIFF(:,i) = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\r\n\r\nriSetActiveCellProperty(SOILDIFF, \u0026#34;SOILDIFF\u0026#34;);\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-2\"\u003eExample 2\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"\u003e\u003ccode class=\"language-matlab\" data-lang=\"matlab\"\u003e# Set all values to \u0026#34;Undefined\u0026#34; exept k\u003cspan style=\"color:#f92672\"\u003e-\u003c/span\u003elayers from \u003cspan style=\"color:#ae81ff\"\u003e17\u003c/span\u003e to \u003cspan style=\"color:#ae81ff\"\u003e20\u003c/span\u003e\r\nCInfo = riGetActiveCellInfo();\r\nSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\r\n\r\nMask = (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e4\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e\u0026lt;\u003c/span\u003e \u003cspan style=\"color:#ae81ff\"\u003e17\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e|\u003c/span\u003e (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e4\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e\u0026gt;\u003c/span\u003e \u003cspan style=\"color:#ae81ff\"\u003e20\u003c/span\u003e)\r\nLGRSOIL = SOIL;\r\ni = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\r\n\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(LGRSOIL))\r\n    LGRSOIL(Mask,i) = nan;\r\nendfor\r\n\r\nriSetActiveCellProperty(LGRSOIL, \u0026#34;KSlice\u0026#34;);\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-3\"\u003eExample 3\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"\u003e\u003ccode class=\"language-matlab\" data-lang=\"matlab\"\u003e# Keep the values in the first LGR only\r\n\r\nCInfo = riGetActiveCellInfo();\r\nSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\r\n\r\nMask = (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e) != \u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e);\r\n\r\nLGRSOIL = SOIL;\r\ni = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\r\n\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(LGRSOIL))\r\n    LGRSOIL(Mask,i) = nan;\r\nendfor\r\n\r\nriSetActiveCellProperty(LGRSOIL, \u0026#34;LGRSOIL\u0026#34;);\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-4--might-be-slow-on-big-models\"\u003eExample 4 ( Might be slow on big models)\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4\"\u003e\u003ccode class=\"language-matlab\" data-lang=\"matlab\"\u003e# Calculate the average SOIL value across K layers\r\n\r\nCInfo = riGetActiveCellInfo();\r\nSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\r\n\r\nSOIL_KAverage = SOIL;\r\nSOIL_KAverage(:) = nan;\r\n\r\nmini = min(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e2\u003c/span\u003e))\r\nmaxi = max(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e2\u003c/span\u003e))\r\n\r\nminj = min(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e3\u003c/span\u003e))\r\nmaxj = max(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e3\u003c/span\u003e))\r\n\r\n\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = mini:maxi\r\n  \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e j = minj:maxj \r\n    Mask = (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e==\u003c/span\u003e \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e\u0026amp;\u003c/span\u003e (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e2\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e==\u003c/span\u003e i) \u003cspan style=\"color:#f92672\"\u003e\u0026amp;\u003c/span\u003e (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e3\u003c/span\u003e) \u003cspan style=\"color:#f92672\"\u003e==\u003c/span\u003e j) ;\r\n\r\n    \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e ts = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(SOIL)) \r\n      SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));\r\n    endfor\r\n  endfor\r\nendfor\r\n\r\nriSetActiveCellProperty(SOIL_KAverage, \u0026#34;SOIL_KAverage\u0026#34;);\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/scripting/octaveinterface/"
             };
         
@@ -2289,8 +2322,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/tensors/"] = {
                 title:    "Tensor Results",
-                content:  " Tensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.\nThe tensor results editor is found in a geo mechanical model\u0026rsquo;s View in the project tree as seen below.\nVisualization The tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal. In the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.\nProperties Value Tensor Results of an element can be calculated from one of the three result values SE, ST and E.\nVisibility Choose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.\nVector Colors Choose which color palette to use for the three arrows. The colors appear in \u0026ldquo;correct\u0026rdquo; order (first color = principal 1).\nThe vector color Result Colors is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.\nVector Size Scale method Result scales the arrows relative to the maximum result value of all components in the model. With scale method Constant, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the Size Scale.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorArrows.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.\u003c/p\u003e\n\n\u003cp\u003eThe tensor results editor is found in a geo mechanical model\u0026rsquo;s \u003cstrong\u003eView\u003c/strong\u003e in the project tree as seen below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorProjectTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"visualization\"\u003eVisualization\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorPressureTension.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal.\nIn the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.\u003c/p\u003e\n\n\u003ch2 id=\"properties\"\u003eProperties\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorPropEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"value\"\u003eValue\u003c/h3\u003e\n\n\u003cp\u003eTensor Results of an element can be calculated from one of the three result values \u003cem\u003eSE, ST\u003c/em\u003e and \u003cem\u003eE\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"visibility\"\u003eVisibility\u003c/h3\u003e\n\n\u003cp\u003eChoose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.\u003c/p\u003e\n\n\u003ch3 id=\"vector-colors\"\u003eVector Colors\u003c/h3\u003e\n\n\u003cp\u003eChoose which color palette to use for the three arrows. The colors appear in \u0026ldquo;correct\u0026rdquo; order (first color = principal 1).\u003c/p\u003e\n\n\u003cp\u003eThe vector color \u003cstrong\u003eResult Colors\u003c/strong\u003e is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorsResultColor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"vector-size\"\u003eVector Size\u003c/h3\u003e\n\n\u003cp\u003eScale method \u003cstrong\u003eResult\u003c/strong\u003e scales the arrows relative to the maximum result value of all components in the model. With scale method \u003cstrong\u003eConstant\u003c/strong\u003e, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the \u003cstrong\u003eSize Scale\u003c/strong\u003e.\u003c/p\u003e\n",
+                content:  "Tensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.\nThe tensor results editor is found in a geo mechanical model\u0026rsquo;s View in the project tree as seen below.\nVisualization The tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal. In the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.\nProperties Value Tensor Results of an element can be calculated from one of the three result values SE, ST and E.\nVisibility Choose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.\nVector Colors Choose which color palette to use for the three arrows. The colors appear in \u0026ldquo;correct\u0026rdquo; order (first color = principal 1).\nThe vector color Result Colors is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.\nVector Size Scale method Result scales the arrows relative to the maximum result value of all components in the model. With scale method Constant, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the Size Scale.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorArrows.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTensors are arrows showing the average principal vectors in an element, shown on every visible face of the element.\u003c/p\u003e\n\u003cp\u003eThe tensor results editor is found in a geo mechanical model\u0026rsquo;s \u003cstrong\u003eView\u003c/strong\u003e in the project tree as seen below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorProjectTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"visualization\"\u003eVisualization\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorPressureTension.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe tensor arrows visualize the principal vectors in three directions. Each colored pair of arrows represents a principal.\nIn the example above, the orange and blue arrows represent pressures and the white arrows represent a tension.\u003c/p\u003e\n\u003ch2 id=\"properties\"\u003eProperties\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorPropEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"value\"\u003eValue\u003c/h3\u003e\n\u003cp\u003eTensor Results of an element can be calculated from one of the three result values \u003cem\u003eSE, ST\u003c/em\u003e and \u003cem\u003eE\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"visibility\"\u003eVisibility\u003c/h3\u003e\n\u003cp\u003eChoose which of the three principals to be shown. The threshold removes all principals with an absolute value less than or equal to the threshold value.\u003c/p\u003e\n\u003ch3 id=\"vector-colors\"\u003eVector Colors\u003c/h3\u003e\n\u003cp\u003eChoose which color palette to use for the three arrows. The colors appear in \u0026ldquo;correct\u0026rdquo; order (first color = principal 1).\u003c/p\u003e\n\u003cp\u003eThe vector color \u003cstrong\u003eResult Colors\u003c/strong\u003e is special. By choosing this color type, a new legend will appear. This legend is defined by the values in the Legend definition of the Element Tensor Results. The extreme values of the color mapper are the extremes of the three principals combined. In the example below, the color result is SE-S1. The largest arrow (principal 1) is quite similar to the cell color, as expected.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/tensorsResultColor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"vector-size\"\u003eVector Size\u003c/h3\u003e\n\u003cp\u003eScale method \u003cstrong\u003eResult\u003c/strong\u003e scales the arrows relative to the maximum result value of all components in the model. With scale method \u003cstrong\u003eConstant\u003c/strong\u003e, all the arrows are set to an equal constant size. The overall arrow size can be adjusted by using the \u003cstrong\u003eSize Scale\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/3d-main-window/tensors/"
             };
         
@@ -2299,7 +2332,7 @@ if (!doNotTrack) {
             window.store["/export/exportwellpaths/"] = {
                 title:    "Well Paths",
                 content:  "In order to export well paths to dev files, select the menu item File -\u0026gt; Export -\u0026gt; Export Visible Well Paths or select one or more well paths and then select one of the items in the context sub menu Export Well Paths.\nA dialog appears after selecting an export well path command.\n Export Folder - Folder for the exported well path file(s). The folder will be created when performing the export and the names of the exported file(s) will be on the format \u0026lt;well name\u0026gt;.dev MD Step Size - Spacing (measured depth) between samples along the well path in the exported file  ",
-                html:     "\u003cp\u003eIn order to export well paths to dev files, select the menu item \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Export Visible Well Paths\u003c/strong\u003e or select one or more well paths and then select one of the items in the context sub menu \u003cstrong\u003eExport Well Paths\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eA dialog appears after selecting an export well path command.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportWellPathsDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e - Folder for the exported well path file(s). The folder will be created when performing the export and the names of the exported file(s) will be on the format \u0026lt;well name\u0026gt;.dev\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD Step Size\u003c/strong\u003e - Spacing (measured depth) between samples along the well path in the exported file\u003c/li\u003e\n\u003c/ul\u003e\n",
+                html:     "\u003cp\u003eIn order to export well paths to dev files, select the menu item \u003cstrong\u003eFile -\u0026gt; Export -\u0026gt; Export Visible Well Paths\u003c/strong\u003e or select one or more well paths and then select one of the items in the context sub menu \u003cstrong\u003eExport Well Paths\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eA dialog appears after selecting an export well path command.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportWellPathsDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e - Folder for the exported well path file(s). The folder will be created when performing the export and the names of the exported file(s) will be on the format \u0026lt;well name\u0026gt;.dev\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD Step Size\u003c/strong\u003e - Spacing (measured depth) between samples along the well path in the exported file\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/export/exportwellpaths/"
             };
         
@@ -2307,8 +2340,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/completionslgr/"] = {
                 title:    "Completions LGR",
-                content:  " ResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.\nCreate Temporary LGRs To create temporary LGR(s), first select one or more well paths in the project tree, right click and select \u0026lsquo;Create Temporary LGR\u0026rsquo;. This command brings up the following dialog.\nThe dialog contains several input fields\n Source Case \u0026ndash; The source case/grid Time Step \u0026ndash; The time step to use Fractures, Fishbones, Perforations \u0026ndash; Check boxes to control which completion types to create LGRs for Split Type \u0026ndash; Three options controlling how the LGRs will be created  LGR Per Cell \u0026ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion \u0026ndash; One LGR is created for each completion of the selected types. Each LGR span all main grid cells that are located within an IJK bounding box containing all intersected cells. LGR Per Well \u0026ndash; One LGR is created for each of the selected well paths. The LGR spans all main grid cells that are located within an IJK bounding box containing all intersected cells for all selected completions on that well path.  Cell Count I,J,K \u0026ndash; The size of the LGR, in each main grid cell, in the I, J and K direction  After pressing the OK button, LGR(s) are created and will be visible in the grid view. Temporary LGRs are stored in memory, and are thus not saved to file. After restarting ResInsight those LGRs have to be recreated.\nIndividual visibility of generated LGRs can be controlled from the Grids section in a view.\nDelete temporary LGRs It is possible to explicitly delete all temporary LGRs. Right click on the View -\u0026gt; Grids -\u0026gt; Temporary LGRs project tree node and select Delete Temporary LGRs. This command deletes all temporary LGRs.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.\u003c/p\u003e\n\n\u003ch2 id=\"create-temporary-lgrs\"\u003eCreate Temporary LGRs\u003c/h2\u003e\n\n\u003cp\u003eTo create temporary LGR(s), first select one or more well paths in the project tree, right click and select \u0026lsquo;Create Temporary LGR\u0026rsquo;. This command brings up the following dialog.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLgrDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe dialog contains several input fields\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSource Case\u003c/strong\u003e \u0026ndash; The source case/grid\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; The time step to use\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFractures, Fishbones, Perforations\u003c/strong\u003e \u0026ndash; Check boxes to control which completion types to create LGRs for\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit Type\u003c/strong\u003e \u0026ndash; Three options controlling how the LGRs will be created\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Cell\u003c/strong\u003e \u0026ndash; One LGR is created for each main grid cell intersected by completions of the selected type\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Completion\u003c/strong\u003e \u0026ndash; One LGR is created for each completion of the selected types. Each LGR span all main grid cells that are located within an IJK bounding box containing all intersected cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Well\u003c/strong\u003e \u0026ndash; One LGR is created for each of the selected well paths. The LGR spans all main grid cells that are located within an IJK bounding box containing all intersected cells for all selected completions on that well path.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Count I,J,K\u003c/strong\u003e \u0026ndash; The size of the LGR, in each main grid cell, in the I, J and K direction\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eAfter pressing the OK button, LGR(s) are created and will be visible in the grid view.\nTemporary LGRs are stored in memory, and are thus not saved to file. After restarting ResInsight those LGRs have to be recreated.\u003c/p\u003e\n\n\u003cp\u003eIndividual visibility of generated LGRs can be controlled from the \u003ca href=\"/3d-main-window/3dviews/#grids\"\u003eGrids\u003c/a\u003e section in a view.\u003c/p\u003e\n\n\u003ch3 id=\"delete-temporary-lgrs\"\u003eDelete temporary LGRs\u003c/h3\u003e\n\n\u003cp\u003eIt is possible to explicitly delete all temporary LGRs. Right click on the \u003cstrong\u003eView -\u0026gt; Grids -\u0026gt; Temporary LGRs\u003c/strong\u003e project tree node and select \u003cstrong\u003eDelete Temporary LGRs\u003c/strong\u003e. This command deletes all temporary LGRs.\u003c/p\u003e\n",
+                content:  "ResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.\nCreate Temporary LGRs To create temporary LGR(s), first select one or more well paths in the project tree, right click and select \u0026lsquo;Create Temporary LGR\u0026rsquo;. This command brings up the following dialog.\nThe dialog contains several input fields\n Source Case \u0026ndash; The source case/grid Time Step \u0026ndash; The time step to use Fractures, Fishbones, Perforations \u0026ndash; Check boxes to control which completion types to create LGRs for Split Type \u0026ndash; Three options controlling how the LGRs will be created  LGR Per Cell \u0026ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion \u0026ndash; One LGR is created for each completion of the selected types. Each LGR span all main grid cells that are located within an IJK bounding box containing all intersected cells. LGR Per Well \u0026ndash; One LGR is created for each of the selected well paths. The LGR spans all main grid cells that are located within an IJK bounding box containing all intersected cells for all selected completions on that well path.   Cell Count I,J,K \u0026ndash; The size of the LGR, in each main grid cell, in the I, J and K direction  After pressing the OK button, LGR(s) are created and will be visible in the grid view. Temporary LGRs are stored in memory, and are thus not saved to file. After restarting ResInsight those LGRs have to be recreated.\nIndividual visibility of generated LGRs can be controlled from the Grids section in a view.\nDelete temporary LGRs It is possible to explicitly delete all temporary LGRs. Right click on the View -\u0026gt; Grids -\u0026gt; Temporary LGRs project tree node and select Delete Temporary LGRs. This command deletes all temporary LGRs.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.\u003c/p\u003e\n\u003ch2 id=\"create-temporary-lgrs\"\u003eCreate Temporary LGRs\u003c/h2\u003e\n\u003cp\u003eTo create temporary LGR(s), first select one or more well paths in the project tree, right click and select \u0026lsquo;Create Temporary LGR\u0026rsquo;. This command brings up the following dialog.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TemporaryLgrDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe dialog contains several input fields\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSource Case\u003c/strong\u003e \u0026ndash; The source case/grid\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; The time step to use\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFractures, Fishbones, Perforations\u003c/strong\u003e \u0026ndash; Check boxes to control which completion types to create LGRs for\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSplit Type\u003c/strong\u003e \u0026ndash; Three options controlling how the LGRs will be created\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Cell\u003c/strong\u003e \u0026ndash; One LGR is created for each main grid cell intersected by completions of the selected type\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Completion\u003c/strong\u003e \u0026ndash; One LGR is created for each completion of the selected types. Each LGR span all main grid cells that are located within an IJK bounding box containing all intersected cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLGR Per Well\u003c/strong\u003e \u0026ndash; One LGR is created for each of the selected well paths. The LGR spans all main grid cells that are located within an IJK bounding box containing all intersected cells for all selected completions on that well path.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Count I,J,K\u003c/strong\u003e \u0026ndash; The size of the LGR, in each main grid cell, in the I, J and K direction\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eAfter pressing the OK button, LGR(s) are created and will be visible in the grid view.\nTemporary LGRs are stored in memory, and are thus not saved to file. After restarting ResInsight those LGRs have to be recreated.\u003c/p\u003e\n\u003cp\u003eIndividual visibility of generated LGRs can be controlled from the \u003ca href=\"/3d-main-window/3dviews/#grids\"\u003eGrids\u003c/a\u003e section in a view.\u003c/p\u003e\n\u003ch3 id=\"delete-temporary-lgrs\"\u003eDelete temporary LGRs\u003c/h3\u003e\n\u003cp\u003eIt is possible to explicitly delete all temporary LGRs. Right click on the \u003cstrong\u003eView -\u0026gt; Grids -\u0026gt; Temporary LGRs\u003c/strong\u003e project tree node and select \u003cstrong\u003eDelete Temporary LGRs\u003c/strong\u003e. This command deletes all temporary LGRs.\u003c/p\u003e\n",
                 url:      "/wells-and-completions/completionslgr/"
             };
         
@@ -2316,8 +2349,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/curvecalculator/"] = {
                 title:    "Curve Calculator",
-                content:  " The summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.\nThe calculator can be run by pressing the calculator icon in the menu bar, or by right-clicking on either a summary case or the summary plot collection.\nCalculation Settings To make a new calculated curve, click on New Calculation. This will add a new calculation to Calculated Summaries. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression Calculation_1 := x + y will do a vector addition on the curves which x and y are placeholders for, and assign it to the calculation Calculation_1. How to assign curves to assign to x and y will be covered in section Summary Address Selection.\nOperators and Functions Possible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.\nAssignment Operators    OPERATOR DEFINITION     := Assign    Basic Operators    OPERATOR DEFINITION     + Addition   - Subtraction   * Multiplication   / Division   % Modulus   ^ Power    Scalar Functions    FUNCTION DEFINITION     avg Average   max Maximum   min Minimum   sum Sum    Trigonometry Functions    FUNCTION DEFINITION     acos Arc cosine (in radians)   acosh Inverse hyperbolic cosine (in radians)   asin Arc sine (in radians)   asinh Inverse hyperbolic sine (in radians)   atan Arc tangent (in radians)   atanh Inverse hyperbolic tangent (in radians)   cos Cosine   cosh Hyperbolic cosine   cot Cotangent   csc Cosecant   deg2rad Convert x from degrees to radians   deg2grad Convert x from degrees to radians   rad2deg Convert x from radians to degrees   grad2deg Convert x from radians to degrees   sec Secant   sin Sine   sinc Sine cardinal   sinh Hyperbolic sine   tan Tangent   tanh Hyperbolic tangent    Vector Functions    FUNCTION DEFINITION     abs Absolute value   ceil Rounding up   floor Rounding down   frac Fractional portion of input   log Natural logarithm   log10 Base 10 logarithm   pow Power   round Round x to the nearest integer   sgn Sign of x, -1 where x \u0026lt; 0, +1 where x \u0026gt; 0, else zero   sqrt Square root   trunc Integer portion of input    Unit It is possible to add a unit to the calculated curve, in the field Unit beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.\nSummary Address Selection An expression consists of placeholders (variables) for curves (summary address). By clicking Parse Expression, the variables will appear in the table below the settings. To assign a summary address to a variable, click Edit. This action will open a Summary Address Selection dialog. Use the dialog to select a summary address and press OK. Repeat the procedure for all the variables.\nGenerating Curves After assigning summary addresses to all variables, click Calculate to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: Calculated.\nThe curves can also be found in an existing curve\u0026rsquo;s Property Editor. Choose the case Calculated, and the curves will appear in Vector Selection.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveCalculator.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.\u003c/p\u003e\n\n\u003cp\u003eThe calculator can be run by pressing the calculator icon \u003cimg src=\"https://resinsight.org/images/plot-window/calculator.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n in the menu bar, or by right-clicking on either a summary case or the summary plot collection.\u003c/p\u003e\n\n\u003ch2 id=\"calculation-settings\"\u003eCalculation Settings\u003c/h2\u003e\n\n\u003cp\u003eTo make a new calculated curve, click on \u003cstrong\u003eNew Calculation\u003c/strong\u003e. This will add a new calculation to \u003cstrong\u003eCalculated Summaries\u003c/strong\u003e. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression \u003cem\u003eCalculation_1 := x + y\u003c/em\u003e will do a vector addition on the curves which \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e are placeholders for, and assign it to the calculation \u003cem\u003eCalculation_1\u003c/em\u003e. How to assign curves to assign to \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e will be covered in section \u003ca href=\"#summary-address-selection\"\u003eSummary Address Selection\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"operators-and-functions\"\u003eOperators and Functions\u003c/h3\u003e\n\n\u003cp\u003ePossible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.\u003c/p\u003e\n\n\u003ch4 id=\"assignment-operators\"\u003eAssignment Operators\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOPERATOR\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e:=\u003c/td\u003e\n\u003ctd\u003eAssign\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"basic-operators\"\u003eBasic Operators\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOPERATOR\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e+\u003c/td\u003e\n\u003ctd\u003eAddition\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e-\u003c/td\u003e\n\u003ctd\u003eSubtraction\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e*\u003c/td\u003e\n\u003ctd\u003eMultiplication\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e/\u003c/td\u003e\n\u003ctd\u003eDivision\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e%\u003c/td\u003e\n\u003ctd\u003eModulus\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003e^\u003c/td\u003e\n\u003ctd\u003ePower\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"scalar-functions\"\u003eScalar Functions\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eavg\u003c/td\u003e\n\u003ctd\u003eAverage\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emax\u003c/td\u003e\n\u003ctd\u003eMaximum\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003emin\u003c/td\u003e\n\u003ctd\u003eMinimum\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esum\u003c/td\u003e\n\u003ctd\u003eSum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"trigonometry-functions\"\u003eTrigonometry Functions\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eacos\u003c/td\u003e\n\u003ctd\u003eArc cosine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eacosh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic cosine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003easin\u003c/td\u003e\n\u003ctd\u003eArc sine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003easinh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic sine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eatan\u003c/td\u003e\n\u003ctd\u003eArc tangent (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eatanh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic tangent (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecos\u003c/td\u003e\n\u003ctd\u003eCosine\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecosh\u003c/td\u003e\n\u003ctd\u003eHyperbolic cosine\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecot\u003c/td\u003e\n\u003ctd\u003eCotangent\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ecsc\u003c/td\u003e\n\u003ctd\u003eCosecant\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edeg2rad\u003c/td\u003e\n\u003ctd\u003eConvert x from degrees to radians\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003edeg2grad\u003c/td\u003e\n\u003ctd\u003eConvert x from degrees to radians\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003erad2deg\u003c/td\u003e\n\u003ctd\u003eConvert x from radians to degrees\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003egrad2deg\u003c/td\u003e\n\u003ctd\u003eConvert x from radians to degrees\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esec\u003c/td\u003e\n\u003ctd\u003eSecant\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esin\u003c/td\u003e\n\u003ctd\u003eSine\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esinc\u003c/td\u003e\n\u003ctd\u003eSine cardinal\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esinh\u003c/td\u003e\n\u003ctd\u003eHyperbolic sine\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etan\u003c/td\u003e\n\u003ctd\u003eTangent\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etanh\u003c/td\u003e\n\u003ctd\u003eHyperbolic tangent\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch4 id=\"vector-functions\"\u003eVector Functions\u003c/h4\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eabs\u003c/td\u003e\n\u003ctd\u003eAbsolute value\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eceil\u003c/td\u003e\n\u003ctd\u003eRounding up\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efloor\u003c/td\u003e\n\u003ctd\u003eRounding down\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003efrac\u003c/td\u003e\n\u003ctd\u003eFractional portion of input\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003elog\u003c/td\u003e\n\u003ctd\u003eNatural logarithm\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003elog10\u003c/td\u003e\n\u003ctd\u003eBase 10 logarithm\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003epow\u003c/td\u003e\n\u003ctd\u003ePower\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eround\u003c/td\u003e\n\u003ctd\u003eRound x to the nearest integer\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esgn\u003c/td\u003e\n\u003ctd\u003eSign of x, -1 where x \u0026lt; 0, +1 where x \u0026gt; 0, else zero\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003esqrt\u003c/td\u003e\n\u003ctd\u003eSquare root\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003etrunc\u003c/td\u003e\n\u003ctd\u003eInteger portion of input\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"unit\"\u003eUnit\u003c/h3\u003e\n\n\u003cp\u003eIt is possible to add a unit to the calculated curve, in the field \u003cstrong\u003eUnit\u003c/strong\u003e beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.\u003c/p\u003e\n\n\u003ch2 id=\"summary-address-selection\"\u003eSummary Address Selection\u003c/h2\u003e\n\n\u003cp\u003eAn expression consists of placeholders (variables) for curves (summary address). By clicking \u003cstrong\u003eParse Expression\u003c/strong\u003e, the variables will appear in the table below the settings. To assign a summary address to a variable, click \u003cstrong\u003eEdit\u003c/strong\u003e. This action will open a \u003cstrong\u003eSummary Address Selection\u003c/strong\u003e dialog. Use the dialog to select a summary address and press \u003cstrong\u003eOK\u003c/strong\u003e. Repeat the procedure for all the variables.\u003c/p\u003e\n\n\u003ch2 id=\"generating-curves\"\u003eGenerating Curves\u003c/h2\u003e\n\n\u003cp\u003eAfter assigning summary addresses to all variables, click \u003cstrong\u003eCalculate\u003c/strong\u003e to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: \u003cstrong\u003eCalculated\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe curves can also be found in an existing curve\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Choose the case \u003cstrong\u003eCalculated\u003c/strong\u003e, and the curves will appear in \u003cstrong\u003eVector Selection\u003c/strong\u003e.\u003c/p\u003e\n",
+                content:  "The summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.\nThe calculator can be run by pressing the calculator icon in the menu bar, or by right-clicking on either a summary case or the summary plot collection.\nCalculation Settings To make a new calculated curve, click on New Calculation. This will add a new calculation to Calculated Summaries. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression Calculation_1 := x + y will do a vector addition on the curves which x and y are placeholders for, and assign it to the calculation Calculation_1. How to assign curves to assign to x and y will be covered in section Summary Address Selection.\nOperators and Functions Possible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.\nAssignment Operators    OPERATOR DEFINITION     := Assign    Basic Operators    OPERATOR DEFINITION     + Addition   - Subtraction   * Multiplication   / Division   % Modulus   ^ Power    Scalar Functions    FUNCTION DEFINITION     avg Average   max Maximum   min Minimum   sum Sum    Trigonometry Functions    FUNCTION DEFINITION     acos Arc cosine (in radians)   acosh Inverse hyperbolic cosine (in radians)   asin Arc sine (in radians)   asinh Inverse hyperbolic sine (in radians)   atan Arc tangent (in radians)   atanh Inverse hyperbolic tangent (in radians)   cos Cosine   cosh Hyperbolic cosine   cot Cotangent   csc Cosecant   deg2rad Convert x from degrees to radians   deg2grad Convert x from degrees to radians   rad2deg Convert x from radians to degrees   grad2deg Convert x from radians to degrees   sec Secant   sin Sine   sinc Sine cardinal   sinh Hyperbolic sine   tan Tangent   tanh Hyperbolic tangent    Vector Functions    FUNCTION DEFINITION     abs Absolute value   ceil Rounding up   floor Rounding down   frac Fractional portion of input   log Natural logarithm   log10 Base 10 logarithm   pow Power   round Round x to the nearest integer   sgn Sign of x, -1 where x \u0026lt; 0, +1 where x \u0026gt; 0, else zero   sqrt Square root   trunc Integer portion of input    Unit It is possible to add a unit to the calculated curve, in the field Unit beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.\nSummary Address Selection An expression consists of placeholders (variables) for curves (summary address). By clicking Parse Expression, the variables will appear in the table below the settings. To assign a summary address to a variable, click Edit. This action will open a Summary Address Selection dialog. Use the dialog to select a summary address and press OK. Repeat the procedure for all the variables.\nGenerating Curves After assigning summary addresses to all variables, click Calculate to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: Calculated.\nThe curves can also be found in an existing curve\u0026rsquo;s Property Editor. Choose the case Calculated, and the curves will appear in Vector Selection.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveCalculator.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe summary curve calculator is a tool to do relative simple vector calculations on a set of curves. The created curves can be stored for later use in the project.\u003c/p\u003e\n\u003cp\u003eThe calculator can be run by pressing the calculator icon \u003cimg src=\"https://resinsight.org/images/plot-window/calculator.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n in the menu bar, or by right-clicking on either a summary case or the summary plot collection.\u003c/p\u003e\n\u003ch2 id=\"calculation-settings\"\u003eCalculation Settings\u003c/h2\u003e\n\u003cp\u003eTo make a new calculated curve, click on \u003cstrong\u003eNew Calculation\u003c/strong\u003e. This will add a new calculation to \u003cstrong\u003eCalculated Summaries\u003c/strong\u003e. Before choosing which curves to do calculations on, a calculation expression must be made. The default expression \u003cem\u003eCalculation_1 := x + y\u003c/em\u003e will do a vector addition on the curves which \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e are placeholders for, and assign it to the calculation \u003cem\u003eCalculation_1\u003c/em\u003e. How to assign curves to assign to \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e will be covered in section \u003ca href=\"#summary-address-selection\"\u003eSummary Address Selection\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"operators-and-functions\"\u003eOperators and Functions\u003c/h3\u003e\n\u003cp\u003ePossible operations and functions are found by right-clicking in the expression window. The following tables show all the options available.\u003c/p\u003e\n\u003ch4 id=\"assignment-operators\"\u003eAssignment Operators\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOPERATOR\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e:=\u003c/td\u003e\n\u003ctd\u003eAssign\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"basic-operators\"\u003eBasic Operators\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOPERATOR\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e+\u003c/td\u003e\n\u003ctd\u003eAddition\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e-\u003c/td\u003e\n\u003ctd\u003eSubtraction\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e*\u003c/td\u003e\n\u003ctd\u003eMultiplication\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e/\u003c/td\u003e\n\u003ctd\u003eDivision\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e%\u003c/td\u003e\n\u003ctd\u003eModulus\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e^\u003c/td\u003e\n\u003ctd\u003ePower\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"scalar-functions\"\u003eScalar Functions\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eavg\u003c/td\u003e\n\u003ctd\u003eAverage\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emax\u003c/td\u003e\n\u003ctd\u003eMaximum\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003emin\u003c/td\u003e\n\u003ctd\u003eMinimum\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esum\u003c/td\u003e\n\u003ctd\u003eSum\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"trigonometry-functions\"\u003eTrigonometry Functions\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eacos\u003c/td\u003e\n\u003ctd\u003eArc cosine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eacosh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic cosine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003easin\u003c/td\u003e\n\u003ctd\u003eArc sine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003easinh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic sine (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eatan\u003c/td\u003e\n\u003ctd\u003eArc tangent (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eatanh\u003c/td\u003e\n\u003ctd\u003eInverse hyperbolic tangent (in radians)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecos\u003c/td\u003e\n\u003ctd\u003eCosine\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecosh\u003c/td\u003e\n\u003ctd\u003eHyperbolic cosine\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecot\u003c/td\u003e\n\u003ctd\u003eCotangent\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ecsc\u003c/td\u003e\n\u003ctd\u003eCosecant\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edeg2rad\u003c/td\u003e\n\u003ctd\u003eConvert x from degrees to radians\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003edeg2grad\u003c/td\u003e\n\u003ctd\u003eConvert x from degrees to radians\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003erad2deg\u003c/td\u003e\n\u003ctd\u003eConvert x from radians to degrees\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003egrad2deg\u003c/td\u003e\n\u003ctd\u003eConvert x from radians to degrees\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esec\u003c/td\u003e\n\u003ctd\u003eSecant\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esin\u003c/td\u003e\n\u003ctd\u003eSine\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esinc\u003c/td\u003e\n\u003ctd\u003eSine cardinal\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esinh\u003c/td\u003e\n\u003ctd\u003eHyperbolic sine\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etan\u003c/td\u003e\n\u003ctd\u003eTangent\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etanh\u003c/td\u003e\n\u003ctd\u003eHyperbolic tangent\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"vector-functions\"\u003eVector Functions\u003c/h4\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFUNCTION\u003c/th\u003e\n\u003cth\u003eDEFINITION\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eabs\u003c/td\u003e\n\u003ctd\u003eAbsolute value\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eceil\u003c/td\u003e\n\u003ctd\u003eRounding up\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efloor\u003c/td\u003e\n\u003ctd\u003eRounding down\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003efrac\u003c/td\u003e\n\u003ctd\u003eFractional portion of input\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003elog\u003c/td\u003e\n\u003ctd\u003eNatural logarithm\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003elog10\u003c/td\u003e\n\u003ctd\u003eBase 10 logarithm\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003epow\u003c/td\u003e\n\u003ctd\u003ePower\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eround\u003c/td\u003e\n\u003ctd\u003eRound x to the nearest integer\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esgn\u003c/td\u003e\n\u003ctd\u003eSign of x, -1 where x \u0026lt; 0, +1 where x \u0026gt; 0, else zero\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003esqrt\u003c/td\u003e\n\u003ctd\u003eSquare root\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003etrunc\u003c/td\u003e\n\u003ctd\u003eInteger portion of input\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"unit\"\u003eUnit\u003c/h3\u003e\n\u003cp\u003eIt is possible to add a unit to the calculated curve, in the field \u003cstrong\u003eUnit\u003c/strong\u003e beneath the expression field. This will be used as the label on the y-axis when the curve is used in a plot.\u003c/p\u003e\n\u003ch2 id=\"summary-address-selection\"\u003eSummary Address Selection\u003c/h2\u003e\n\u003cp\u003eAn expression consists of placeholders (variables) for curves (summary address). By clicking \u003cstrong\u003eParse Expression\u003c/strong\u003e, the variables will appear in the table below the settings. To assign a summary address to a variable, click \u003cstrong\u003eEdit\u003c/strong\u003e. This action will open a \u003cstrong\u003eSummary Address Selection\u003c/strong\u003e dialog. Use the dialog to select a summary address and press \u003cstrong\u003eOK\u003c/strong\u003e. Repeat the procedure for all the variables.\u003c/p\u003e\n\u003ch2 id=\"generating-curves\"\u003eGenerating Curves\u003c/h2\u003e\n\u003cp\u003eAfter assigning summary addresses to all variables, click \u003cstrong\u003eCalculate\u003c/strong\u003e to evaluate the expression. The curve is saved and can be accessed in the Plot Editor selecting the Summary Type: \u003cstrong\u003eCalculated\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe curves can also be found in an existing curve\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Choose the case \u003cstrong\u003eCalculated\u003c/strong\u003e, and the curves will appear in \u003cstrong\u003eVector Selection\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/curvecalculator/"
             };
         
@@ -2326,7 +2359,7 @@ if (!doNotTrack) {
             window.store["/export/"] = {
                 title:    "Export",
                 content:  "ResInsight features the following capabilities for export of data to reporting or further analysis:\n convenient export of snapshots of 3D views and plots, either by direct export or automated modification of Eclipse 3D Views export of Eclipse properties, either direct or subsequent to post-processing by ResInsight, for input to further simulations visible cells in ResInsight can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck completions defined in ResInsight can be exported to Eclipse for use in new simulation runs file export of well paths export of sub-sections of an Eclipse Grid with Parameters and Faults to Eclipse ASCII files to perform additional simulations export of a contour map to text file  The following subchapters details the functionality and capabilites.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_RightClick.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight features the following capabilities for export of data to reporting or further analysis:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003econvenient export of snapshots of 3D views and plots, either by direct export or automated modification of Eclipse 3D Views\u003c/li\u003e\n\u003cli\u003eexport of Eclipse properties, either direct or subsequent to post-processing by ResInsight, for input to further simulations\u003c/li\u003e\n\u003cli\u003evisible cells in ResInsight can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck\u003c/li\u003e\n\u003cli\u003ecompletions defined in ResInsight can be exported to Eclipse for use in new simulation runs\u003c/li\u003e\n\u003cli\u003efile export of well paths\u003c/li\u003e\n\u003cli\u003eexport of sub-sections of an Eclipse Grid with Parameters and Faults to Eclipse ASCII files to perform additional simulations\u003c/li\u003e\n\u003cli\u003eexport of a contour map to text file\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe following subchapters details the functionality and capabilites.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_RightClick.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight features the following capabilities for export of data to reporting or further analysis:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003econvenient export of snapshots of 3D views and plots, either by direct export or automated modification of Eclipse 3D Views\u003c/li\u003e\n\u003cli\u003eexport of Eclipse properties, either direct or subsequent to post-processing by ResInsight, for input to further simulations\u003c/li\u003e\n\u003cli\u003evisible cells in ResInsight can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck\u003c/li\u003e\n\u003cli\u003ecompletions defined in ResInsight can be exported to Eclipse for use in new simulation runs\u003c/li\u003e\n\u003cli\u003efile export of well paths\u003c/li\u003e\n\u003cli\u003eexport of sub-sections of an Eclipse Grid with Parameters and Faults to Eclipse ASCII files to perform additional simulations\u003c/li\u003e\n\u003cli\u003eexport of a contour map to text file\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe following subchapters details the functionality and capabilites.\u003c/p\u003e\n",
                 url:      "/export/"
             };
         
@@ -2334,8 +2367,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/octaveinterfacereference/"] = {
                 title:    "Octave Interface Reference",
-                content:  " Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the \u0026ldquo;Current Case\u0026rdquo;), or the script is designed to access the selection and traverse the cases by itself.\nNote: The Octave interface does not support Geomechanical cases and flow diagnostic results.\n\rSingle Case Scripts Single case scripts do not need to address cases explicitly, but works on what ResInsight considers being the \u0026ldquo;Current Case\u0026rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the \u0026ldquo;Current Case\u0026rdquo; from the script will then refer to the case currently being processed by ResInsight. The Current Case can be accessed directly using riGetCurrentCase(), but the more direct way is to omit the CaseId parameter in the functions, the Current Case is then automatically used.\nMulti Case Scripts Scripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.\nCase Types The case type (Labeled \u0026ldquo;CaseType\u0026rdquo; in the following specification) of a case is returned as a text string when retrieving lists of cases, and is one of the following:\n   Case Type Description     ResultCase A binary Eclipse case   InputCase A case based on ASCII Eclipse input data   StatisticsCase A statistics case based on many source cases in Grid Case Group   SourceCase A binary Eclipse case in a Grid Case Group    Unresolved Issues The issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.\nSpecification Project Information The case information is presented in an octave Structure called CaseInfo, and contains the following fields:\nCaseInfo = { CaseId = int # A project-unique integer used to address this # particular case CaseName = string # The name that has been assigned to the case # in ResInsight. CaseType = string # See the description above CaseGroupId = int # A project-unique integer identifying the # CaseGroup this case is a member of. # -1 if not in a CaseGroup. Valid only for # Statistics-, and SourceCases }  CaseInfo riGetCurrentCase() This function returns a CaseInfo Structure for the Case considered being the \u0026ldquo;Current Case\u0026rdquo; by ResInsight. When ResInsight loops over a selection of cases and executes an Octave script for each of them, this function returns the CaseInfo for that particular Case.\nVector[CaseInfo] riGetSelectedCases() This function returns a CaseInfo Structure for each of the cases selected in ResInsight at the time when the script launched.\nVector[CaseGroupInfo] riGetCaseGroups() This function returns a CaseGroupInfo Structure for each of the case groups in the current ResInsight project.\nCaseGroupInfo = { CaseGroupId = int # A project-unique integer used to address # this particular CaseGroup CaseGroupName = string # The name assigned to the CaseGroup # in ResInsight }  Vector[CaseInfo] riGetCases([CaseGroupId]) This function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group. If a CaseGroupId is provided, only the cases in that Case Group will be returned.\nRetrieving Grid Metadata Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;] ) This function returns a two dimensional matrix containing grid and IJK information about each of the active cells in the requested case. The columns contain the following information:\n[GridIdx, I, J, K, ParentGridIdx, PI, PJ, PK, CoarseBoxIdx] GridIdx # The index of the grid the cell resides in. # Main grid has index 0 I, J, K # 1-based index address of the cell in the grid. ParentGridIdx # The index to the grid that this cell's grid # is residing in. PI, PJ, PK # 1-based address of the parent grid cell that # this cell is a part of. CoarseBoxIdx # 1-based coarsening box index, -1 if none. # Coarsening box info can be retrieved using # **riGetCoarseningInfo()**  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId]) This function returns all coarse box definitions used in the grid. The columns contain the following information: [I1, I2, J1, J2, K1, K2]: 1-based index addresses of the min and max corners of the coarsening box. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numGrids][3] riGetGridDimensions([CaseId]) This function returns a two dimensional matrix: One row for each grid, starting with the main grid.\nNOTE: This means that the \u0026ldquo;normal\u0026rdquo; GridIndices where 0 means Main Grid does not work directly with this matrix. You have to add 1.\nThe columns contain the following information: [NI, NJ, NK]: I, J, K dimensions of the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[TimeStepDate] riGetTimeStepDates([CaseId]) This function returns the date information for each of the time steps in the case as a Vector of Structures. The Structure is defined as:\nTimeStepDate = { Year = int # The year eg. 2013 Month = int # The month. Eg. 12 Day = int # The day in the month. Eg. 24 Hour = int # The hour of the day. Eg. 17 Minute = int # The minute in the hour. Eg. 55 Second = int # The second within the minute. Eg. 30 }  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[DecimalDay] riGetTimeStepDays([CaseId]) This function returns the time from the simulation start as decimal days for all the time steps as a Vector of doubles. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nRetrieving Property Data Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) This function returns the name and type of all the properties in the case as a Vector of Structures. The Structure is defined as:\nPropertyInfo { PropName = string # Name of the property as received from # the analysis tool PropType = string # The type of the property: \u0026quot;StaticNative\u0026quot;, # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Input\u0026quot;, \u0026quot;Generated\u0026quot; }  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) This function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId. If the case contains coarse-cells, the results are expanded onto the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nMatrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) This function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step. Grids are indexed from 0 (main grid) to max number of LGR\u0026rsquo;s If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned. Writing Back to ResInsight\nriSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) Interprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nriSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) Interprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nCell Geometry Functions Matrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex) This function returns the UTM coordinates (X, Y, Z) of the center point of all the cells in the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) This function returns the UTM coordinates (X, Y, Z) of the center point of each of the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. Cell Corner Index layout The corner indices follow the ECLIPSE standard:\n 6-------------7 |k /| /| | /j / | / | |/ / | / | *---i 4-------------5 | | | | | | 2---------|---3 | / | / | / | / |/ |/ 0-------------1  Matrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex) This function returns the UTM coordinates(X, Y, Z) of the 8 corners of all the cells in the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;]) This function returns the UTM coordinates (X, Y, Z) of the 8 corners of each of the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nWell Data Functions Vector[WellNames] riGetWellNames([CaseId]) This function returns the names of all the wells in the case as a Vector of strings. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. Vector[WellCellInfo] riGetWellCells([CaseId], WellName, TimeStep) This function returns the cells defined in the specified well for the time step requested as a vector of Structures. The Structure is defined as:\nWellCellInfo { I, J, K = int # Index to the cell in the grid GridIndex = int # the index of the grid. Main grid has index 0. CellStatus = int # is either 0 or 1, meaning the cell is closed # or open respectively BranchId = int # Branch id of the branch intersecting the cell SegmentId = int # Branch segment id of the branch intersecting the cell }  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps]) This function returns the status information for a specified well for each requested time step as a vector of Structures. The Structure is defined as:\nWellStatus { WellType = string # \u0026quot;Producer\u0026quot;, \u0026quot;OilInjector\u0026quot;, # \u0026quot;WaterInjector\u0026quot;, \u0026quot;GasInjector\u0026quot;, \u0026quot;NotDefined\u0026quot; WellStatus = int # is either 0 or 1, meaning the well is shut # or open respectively }  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numSelectedCells][5] riGetSelectedCells([CaseId]) This function returns a two dimensional matrix containing the cell info for each selected cell in the case with CaseId. The columns contain the following information:\n[CaseId, GridIdx, I, J, K] CaseId # The ID of the case the cell resides in. GridIdx # The index of the grid the cell resides in. # Main grid has index 0 I, J, K # 1-based index of the cell in the grid.  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;] ) This function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.\nVector[PropertyInfo] riGetNNCPropertyNames([CaseId]) This function returns the name and type of all NNC properties in the case as a vector of structures.\nThe structure is defined as:\nPropertyInfo { PropName = string # Name of the property as received from # the analysis tool PropType = string # The type of the property: \u0026quot;StaticNative\u0026quot;, # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Generated\u0026quot; }  If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numNNCConnections][2] riGetNNCConnections([CaseId]) This function returns a two dimensional matrix containing grid and IJK information about each NNC connection. Each row contains a from and to cell for the connection. The cells are specified in a structure defined as:\nCellInfo = { GridIndex = int # Index of the grid the cell resides in. # Main grid has index 0. I, J, K = int # 1-based index address of the cell in the grid. }  Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps]) This function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from riGetNNCConnections.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nVector[numConnections] riGetStaticNNCValues([CaseId], PropertyName) This function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from riGetNNCConnections.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nriSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices]) Interprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the steps present in the supplied data matrix and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\n",
-                html:     "\n\n\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\n\u003cp\u003eTo identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the \u0026ldquo;Current Case\u0026rdquo;), or the script is designed to access the selection and traverse the cases by itself.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003cb\u003eNote:\u003c/b\u003e The Octave interface does not support Geomechanical cases and flow diagnostic results.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"single-case-scripts\"\u003eSingle Case Scripts\u003c/h3\u003e\n\n\u003cp\u003eSingle case scripts do not need to address cases explicitly, but works on what ResInsight considers being the \u0026ldquo;Current Case\u0026rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the \u0026ldquo;Current Case\u0026rdquo; from the script will then refer to the case currently being processed by ResInsight.\nThe Current Case can be accessed directly using \u003cstrong\u003eriGetCurrentCase()\u003c/strong\u003e, but the more direct way is to \u003cem\u003eomit the CaseId parameter\u003c/em\u003e in the functions, the Current Case is then automatically used.\u003c/p\u003e\n\n\u003ch3 id=\"multi-case-scripts\"\u003eMulti Case Scripts\u003c/h3\u003e\n\n\u003cp\u003eScripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.\u003c/p\u003e\n\n\u003ch3 id=\"case-types\"\u003eCase Types\u003c/h3\u003e\n\n\u003cp\u003eThe case type (Labeled \u0026ldquo;CaseType\u0026rdquo; in the following specification) of a case is returned as a text string when retrieving lists of cases, and is one of the following:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCase Type\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eResultCase\u003c/td\u003e\n\u003ctd\u003eA binary Eclipse case\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eInputCase\u003c/td\u003e\n\u003ctd\u003eA case based on ASCII Eclipse input data\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eStatisticsCase\u003c/td\u003e\n\u003ctd\u003eA statistics case based on many source cases in Grid Case Group\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eSourceCase\u003c/td\u003e\n\u003ctd\u003eA binary Eclipse case in a Grid Case Group\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"unresolved-issues\"\u003eUnresolved Issues\u003c/h3\u003e\n\n\u003cp\u003eThe issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.\u003c/p\u003e\n\n\u003ch2 id=\"specification\"\u003eSpecification\u003c/h2\u003e\n\n\u003ch3 id=\"project-information\"\u003eProject Information\u003c/h3\u003e\n\n\u003cp\u003eThe case information is presented in an octave Structure called CaseInfo, and contains the following fields:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eCaseInfo = {\n  CaseId      = int    # A project-unique integer used to address this\n                       # particular case \n  CaseName    = string # The name that has been assigned to the case\n                       # in ResInsight.\n  CaseType    = string # See the description above\n  CaseGroupId = int    # A project-unique integer identifying the\n                       # CaseGroup this case is a member of.\n                       # -1 if not in a CaseGroup. Valid only for \n                       # Statistics-, and SourceCases\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"caseinfo-rigetcurrentcase\"\u003eCaseInfo riGetCurrentCase()\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a CaseInfo Structure for the Case considered being the \u0026ldquo;Current Case\u0026rdquo; by ResInsight. When ResInsight loops over a selection of cases and executes an Octave script for each of them, this function returns the CaseInfo for that particular Case.\u003c/p\u003e\n\n\u003ch4 id=\"vector-caseinfo-rigetselectedcases\"\u003eVector[CaseInfo] riGetSelectedCases()\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a CaseInfo Structure for each of the cases selected in ResInsight at the time when the script launched.\u003c/p\u003e\n\n\u003ch4 id=\"vector-casegroupinfo-rigetcasegroups\"\u003eVector[CaseGroupInfo] riGetCaseGroups()\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a CaseGroupInfo Structure for each of the case groups in the current ResInsight project.\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eCaseGroupInfo = {\n  CaseGroupId   = int    # A project-unique integer used to address\n                         # this particular CaseGroup\n  CaseGroupName = string # The name assigned to the CaseGroup \n                         # in ResInsight\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"vector-caseinfo-rigetcases-casegroupid\"\u003eVector[CaseInfo] riGetCases([CaseGroupId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group.\nIf a CaseGroupId is provided, only the cases in that Case Group will be returned.\u003c/p\u003e\n\n\u003ch3 id=\"retrieving-grid-metadata\"\u003eRetrieving Grid Metadata\u003c/h3\u003e\n\n\u003ch4 id=\"matrix-numactivecells-9-rigetactivecellinfo-caseid-porositymodel-matrix-fracture\"\u003eMatrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;] )\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix containing grid and IJK information about each of the active cells in the requested case. The columns contain the following information:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e[GridIdx, I, J, K, ParentGridIdx, PI, PJ, PK, CoarseBoxIdx]\n  GridIdx       # The index of the grid the cell resides in.\n                # Main grid has index 0\n  I, J, K       # 1-based index address of the cell in the grid.\n  ParentGridIdx # The index to the grid that this cell's grid \n                # is residing in.\n  PI, PJ, PK    # 1-based address of the parent grid cell that\n                # this cell is a part of.\n  CoarseBoxIdx  # 1-based coarsening box index, -1 if none.\n                # Coarsening box info can be retrieved using\n                # **riGetCoarseningInfo()**\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numcoarsegroups-6-rigetcoarseninginfo-caseid\"\u003eMatrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns all coarse box definitions used in the grid.\nThe columns contain the following information:\n[I1, I2, J1, J2, K1, K2]: 1-based index addresses of the min and max corners of the coarsening box.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numgrids-3-rigetgriddimensions-caseid\"\u003eMatrix[numGrids][3] riGetGridDimensions([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix: One row for each grid, starting with the main grid.\u003c/p\u003e\n\n\u003cp\u003e\u003cem\u003eNOTE\u003c/em\u003e: This means that the \u0026ldquo;normal\u0026rdquo; GridIndices where 0 means Main Grid does not work directly with this matrix. You have to add 1.\u003c/p\u003e\n\n\u003cp\u003eThe columns contain the following information:\n[NI, NJ, NK]:  I, J, K dimensions of the grid.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"vector-timestepdate-rigettimestepdates-caseid\"\u003eVector[TimeStepDate] riGetTimeStepDates([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the date information for each of the time steps in the case as a Vector of Structures.\nThe Structure is defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eTimeStepDate = {\n  Year    = int # The year eg. 2013\n  Month   = int # The month. Eg. 12\n  Day     = int # The day in the month. Eg. 24\n  Hour    = int # The hour of the day. Eg. 17\n  Minute  = int # The minute in the hour. Eg. 55\n  Second  = int # The second within the minute. Eg. 30\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"vector-decimalday-rigettimestepdays-caseid\"\u003eVector[DecimalDay] riGetTimeStepDays([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the time from the simulation start as decimal days for all the time steps as a Vector of doubles.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch3 id=\"retrieving-property-data\"\u003eRetrieving Property Data\u003c/h3\u003e\n\n\u003ch4 id=\"vector-propertyinfo-rigetpropertynames-caseid-porositymodel-matrix-fracture\"\u003eVector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the name and type of all the properties in the case as a Vector of Structures.\nThe Structure is defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003ePropertyInfo {\n  PropName    = string # Name of the property as received from\n                       # the analysis tool\n  PropType    = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\n                       # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Input\u0026quot;, \u0026quot;Generated\u0026quot;\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numactivecells-numtimestepsrequested-rigetactivecellproperty-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture\"\u003eMatrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId.\nIf the case contains coarse-cells, the results are expanded onto the active cells.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numi-numj-numk-numtimestepsrequested-rigetgridproperty-caseid-gridindex-propertyname-requestedtimesteps-porositymodel-matrix-fracture\"\u003eMatrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step.\nGrids are indexed from 0 (main grid) to max number of LGR\u0026rsquo;s\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nWriting Back to ResInsight\u003c/p\u003e\n\n\u003ch4 id=\"risetactivecellproperty-matrix-numactivecells-numtimesteps-caseid-propertyname-timestepindices-porositymodel-matrix-fracture\"\u003eriSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eInterprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;.\nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\u003cbr /\u003e\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"risetgridproperty-matrix-numi-numj-numk-numtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel-matrix-fracture\"\u003eriSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eInterprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;.\nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch3 id=\"cell-geometry-functions\"\u003eCell Geometry Functions\u003c/h3\u003e\n\n\u003ch4 id=\"matrix-numi-numj-numk-3-rigetcellcenters-caseid-gridindex\"\u003eMatrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex)\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the center point of all the cells in the grid.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-activecells-3-rigetactivecellcenters-caseid-porositymodel-matrix-fracture\"\u003eMatrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the center point of each of the active cells.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nCell Corner Index layout\nThe corner indices follow the ECLIPSE standard:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e      6-------------7             |k     \n     /|            /|             | /j   \n    / |           / |             |/     \n   /  |          /  |             *---i  \n  4-------------5   |\n  |   |         |   |\n  |   2---------|---3\n  |  /          |  /\n  | /           | /\n  |/            |/\n  0-------------1\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"matrix-numi-numj-numk-8-3-rigetcellcorners-caseid-gridindex\"\u003eMatrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex)\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the UTM coordinates(X, Y, Z) of the 8 corners of all the cells in the grid.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-activecells-8-3-rigetactivecellcorners-caseid-porositymodel-matrix-fracture\"\u003eMatrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the 8 corners of each of the active cells.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch3 id=\"well-data-functions\"\u003eWell Data Functions\u003c/h3\u003e\n\n\u003ch4 id=\"vector-wellnames-rigetwellnames-caseid\"\u003eVector[WellNames] riGetWellNames([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the names of all the wells in the case as a Vector of strings.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[WellCellInfo] riGetWellCells([CaseId], WellName, TimeStep)\nThis function returns the cells defined in the specified well for the time step requested as a vector of Structures. The Structure is defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWellCellInfo {\n  I, J, K     = int # Index to the cell in the grid\n  GridIndex   = int # the index of the grid. Main grid has index 0.\n  CellStatus  = int # is either 0 or 1, meaning the cell is closed\n                    # or open respectively\n  BranchId    = int # Branch id of the branch intersecting the cell\n  SegmentId   = int # Branch segment id of the branch intersecting the cell\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"vector-wellstatus-rigetwellstatus-caseid-wellname-requestedtimesteps\"\u003eVector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the status information for a specified well for each requested time step as a vector of Structures. The Structure is defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWellStatus {\n  WellType    = string # \u0026quot;Producer\u0026quot;, \u0026quot;OilInjector\u0026quot;,\n                       # \u0026quot;WaterInjector\u0026quot;, \u0026quot;GasInjector\u0026quot;, \u0026quot;NotDefined\u0026quot;\n  WellStatus  = int    # is either 0 or 1, meaning the well is shut\n                       # or open respectively\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numselectedcells-5-rigetselectedcells-caseid\"\u003eMatrix[numSelectedCells][5] riGetSelectedCells([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix containing the cell info for each selected cell in the case with \u003ccode\u003eCaseId\u003c/code\u003e.\nThe columns contain the following information:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e[CaseId, GridIdx, I, J, K]\n  CaseId  # The ID of the case the cell resides in.\n  GridIdx # The index of the grid the cell resides in.\n          # Main grid has index 0\n  I, J, K # 1-based index of the cell in the grid.\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numselectedcells-numtimestepsrequested-rigetgridpropertyforselectedcells-caseid-propertyname-requestedtimesteps-porositymodel-matrix-fracture\"\u003eMatrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026rdquo;|\u0026ldquo;Fracture\u0026rdquo;] )\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.\u003c/p\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\n\u003ch4 id=\"vector-propertyinfo-rigetnncpropertynames-caseid\"\u003eVector[PropertyInfo] riGetNNCPropertyNames([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns the name and type of all NNC properties in the case as a vector of structures.\u003c/p\u003e\n\n\u003cp\u003eThe structure is defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003ePropertyInfo {\n  PropName    = string # Name of the property as received from\n                       # the analysis tool\n  PropType    = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\n                       # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Generated\u0026quot;\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"matrix-numnncconnections-2-rigetnncconnections-caseid\"\u003eMatrix[numNNCConnections][2] riGetNNCConnections([CaseId])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix containing grid and IJK information about each NNC connection.\nEach row contains a from and to cell for the connection.\nThe cells are specified in a structure defined as:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eCellInfo = {\n  GridIndex = int # Index of the grid the cell resides in.\n                  # Main grid has index 0.\n  I, J, K   = int # 1-based index address of the cell in the grid.\n}\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"matrix-numconnections-numtimestepsrequested-rigetdynamicnncvalues-caseid-propertyname-requestedtimesteps\"\u003eMatrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from \u003ccode\u003eriGetNNCConnections\u003c/code\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\n\u003ch4 id=\"vector-numconnections-rigetstaticnncvalues-caseid-propertyname\"\u003eVector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)\u003c/h4\u003e\n\n\u003cp\u003eThis function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from \u003ccode\u003eriGetNNCConnections\u003c/code\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\n\u003ch4 id=\"risetnncproperty-matrix-numnncconnections-numtimesteps-caseid-propertyname-timestepindices\"\u003eriSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])\u003c/h4\u003e\n\n\u003cp\u003eInterprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;.\nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the steps present in the supplied data matrix and must thus be complete.\nThe time step data will then be put into ResInsight at the time steps requested.\u003c/p\u003e\n\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n",
+                content:  "Introduction To identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the \u0026ldquo;Current Case\u0026rdquo;), or the script is designed to access the selection and traverse the cases by itself.\nNote:The Octave interface does not support Geomechanical cases and flow diagnostic results.\n\rSingle Case Scripts Single case scripts do not need to address cases explicitly, but works on what ResInsight considers being the \u0026ldquo;Current Case\u0026rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the \u0026ldquo;Current Case\u0026rdquo; from the script will then refer to the case currently being processed by ResInsight. The Current Case can be accessed directly using riGetCurrentCase(), but the more direct way is to omit the CaseId parameter in the functions, the Current Case is then automatically used.\nMulti Case Scripts Scripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.\nCase Types The case type (Labeled \u0026ldquo;CaseType\u0026rdquo; in the following specification) of a case is returned as a text string when retrieving lists of cases, and is one of the following:\n   Case Type Description     ResultCase A binary Eclipse case   InputCase A case based on ASCII Eclipse input data   StatisticsCase A statistics case based on many source cases in Grid Case Group   SourceCase A binary Eclipse case in a Grid Case Group    Unresolved Issues The issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.\nSpecification Project Information The case information is presented in an octave Structure called CaseInfo, and contains the following fields:\nCaseInfo = {\rCaseId = int # A project-unique integer used to address this\r# particular case CaseName = string # The name that has been assigned to the case\r# in ResInsight.\rCaseType = string # See the description above\rCaseGroupId = int # A project-unique integer identifying the\r# CaseGroup this case is a member of.\r# -1 if not in a CaseGroup. Valid only for # Statistics-, and SourceCases\r}\r CaseInfo riGetCurrentCase() This function returns a CaseInfo Structure for the Case considered being the \u0026ldquo;Current Case\u0026rdquo; by ResInsight. When ResInsight loops over a selection of cases and executes an Octave script for each of them, this function returns the CaseInfo for that particular Case.\nVector[CaseInfo] riGetSelectedCases() This function returns a CaseInfo Structure for each of the cases selected in ResInsight at the time when the script launched.\nVector[CaseGroupInfo] riGetCaseGroups() This function returns a CaseGroupInfo Structure for each of the case groups in the current ResInsight project.\nCaseGroupInfo = {\rCaseGroupId = int # A project-unique integer used to address\r# this particular CaseGroup\rCaseGroupName = string # The name assigned to the CaseGroup # in ResInsight\r}\r Vector[CaseInfo] riGetCases([CaseGroupId]) This function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group. If a CaseGroupId is provided, only the cases in that Case Group will be returned.\nRetrieving Grid Metadata Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;] ) This function returns a two dimensional matrix containing grid and IJK information about each of the active cells in the requested case. The columns contain the following information:\n[GridIdx, I, J, K, ParentGridIdx, PI, PJ, PK, CoarseBoxIdx]\rGridIdx # The index of the grid the cell resides in.\r# Main grid has index 0\rI, J, K # 1-based index address of the cell in the grid.\rParentGridIdx # The index to the grid that this cell's grid # is residing in.\rPI, PJ, PK # 1-based address of the parent grid cell that\r# this cell is a part of.\rCoarseBoxIdx # 1-based coarsening box index, -1 if none.\r# Coarsening box info can be retrieved using\r# **riGetCoarseningInfo()**\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId]) This function returns all coarse box definitions used in the grid. The columns contain the following information: [I1, I2, J1, J2, K1, K2]: 1-based index addresses of the min and max corners of the coarsening box. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numGrids][3] riGetGridDimensions([CaseId]) This function returns a two dimensional matrix: One row for each grid, starting with the main grid.\nNOTE: This means that the \u0026ldquo;normal\u0026rdquo; GridIndices where 0 means Main Grid does not work directly with this matrix. You have to add 1.\nThe columns contain the following information: [NI, NJ, NK]: I, J, K dimensions of the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[TimeStepDate] riGetTimeStepDates([CaseId]) This function returns the date information for each of the time steps in the case as a Vector of Structures. The Structure is defined as:\nTimeStepDate = {\rYear = int # The year eg. 2013\rMonth = int # The month. Eg. 12\rDay = int # The day in the month. Eg. 24\rHour = int # The hour of the day. Eg. 17\rMinute = int # The minute in the hour. Eg. 55\rSecond = int # The second within the minute. Eg. 30\r}\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[DecimalDay] riGetTimeStepDays([CaseId]) This function returns the time from the simulation start as decimal days for all the time steps as a Vector of doubles. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nRetrieving Property Data Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) This function returns the name and type of all the properties in the case as a Vector of Structures. The Structure is defined as:\nPropertyInfo {\rPropName = string # Name of the property as received from\r# the analysis tool\rPropType = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\r# \u0026quot;DynamicNative\u0026quot;, \u0026quot;Input\u0026quot;, \u0026quot;Generated\u0026quot;\r}\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) This function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId. If the case contains coarse-cells, the results are expanded onto the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nMatrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) This function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step. Grids are indexed from 0 (main grid) to max number of LGR\u0026rsquo;s If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned. Writing Back to ResInsight\nriSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) Interprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nriSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) Interprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nCell Geometry Functions Matrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex) This function returns the UTM coordinates (X, Y, Z) of the center point of all the cells in the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) This function returns the UTM coordinates (X, Y, Z) of the center point of each of the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. Cell Corner Index layout The corner indices follow the ECLIPSE standard:\n 6-------------7 |k /| /| | /j / | / | |/ / | / | *---i 4-------------5 |\r| | | |\r| 2---------|---3\r| / | /\r| / | /\r|/ |/\r0-------------1\r Matrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex) This function returns the UTM coordinates(X, Y, Z) of the 8 corners of all the cells in the grid. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;]) This function returns the UTM coordinates (X, Y, Z) of the 8 corners of each of the active cells. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nWell Data Functions Vector[WellNames] riGetWellNames([CaseId]) This function returns the names of all the wells in the case as a Vector of strings. If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. Vector[WellCellInfo] riGetWellCells([CaseId], WellName, TimeStep) This function returns the cells defined in the specified well for the time step requested as a vector of Structures. The Structure is defined as:\nWellCellInfo {\rI, J, K = int # Index to the cell in the grid\rGridIndex = int # the index of the grid. Main grid has index 0.\rCellStatus = int # is either 0 or 1, meaning the cell is closed\r# or open respectively\rBranchId = int # Branch id of the branch intersecting the cell\rSegmentId = int # Branch segment id of the branch intersecting the cell\r}\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps]) This function returns the status information for a specified well for each requested time step as a vector of Structures. The Structure is defined as:\nWellStatus {\rWellType = string # \u0026quot;Producer\u0026quot;, \u0026quot;OilInjector\u0026quot;,\r# \u0026quot;WaterInjector\u0026quot;, \u0026quot;GasInjector\u0026quot;, \u0026quot;NotDefined\u0026quot;\rWellStatus = int # is either 0 or 1, meaning the well is shut\r# or open respectively\r}\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numSelectedCells][5] riGetSelectedCells([CaseId]) This function returns a two dimensional matrix containing the cell info for each selected cell in the case with CaseId. The columns contain the following information:\n[CaseId, GridIdx, I, J, K]\rCaseId # The ID of the case the cell resides in.\rGridIdx # The index of the grid the cell resides in.\r# Main grid has index 0\rI, J, K # 1-based index of the cell in the grid.\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;] ) This function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.\nVector[PropertyInfo] riGetNNCPropertyNames([CaseId]) This function returns the name and type of all NNC properties in the case as a vector of structures.\nThe structure is defined as:\nPropertyInfo {\rPropName = string # Name of the property as received from\r# the analysis tool\rPropType = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\r# \u0026quot;DynamicNative\u0026quot;, \u0026quot;Generated\u0026quot;\r}\r If the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nMatrix[numNNCConnections][2] riGetNNCConnections([CaseId]) This function returns a two dimensional matrix containing grid and IJK information about each NNC connection. Each row contains a from and to cell for the connection. The cells are specified in a structure defined as:\nCellInfo = {\rGridIndex = int # Index of the grid the cell resides in.\r# Main grid has index 0.\rI, J, K = int # 1-based index address of the cell in the grid.\r}\r Matrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps]) This function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from riGetNNCConnections.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. The RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nVector[numConnections] riGetStaticNNCValues([CaseId], PropertyName) This function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from riGetNNCConnections.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nriSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices]) Interprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. The \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the steps present in the supplied data matrix and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\n",
+                html:     "\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\u003cp\u003eTo identify a ResInsight case uniquely in the Octave script, an integer Id (CaseId) is used. This Id can be retrieved in several ways, but there are two main modes of operation regarding this for a particular octave script: Either the script is designed to work on a single case (the \u0026ldquo;Current Case\u0026rdquo;), or the script is designed to access the selection and traverse the cases by itself.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003e\u003c!-- raw HTML omitted --\u003eNote:\u003c!-- raw HTML omitted --\u003e The Octave interface does not support Geomechanical cases and flow diagnostic results.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"single-case-scripts\"\u003eSingle Case Scripts\u003c/h3\u003e\n\u003cp\u003eSingle case scripts do not need to address cases explicitly, but works on what ResInsight considers being the \u0026ldquo;Current Case\u0026rdquo;. When the user selects several cases and executes a script on them, ResInsight loops over all cases in the selection, sets the current case and executes the script. All references to the \u0026ldquo;Current Case\u0026rdquo; from the script will then refer to the case currently being processed by ResInsight. \nThe Current Case can be accessed directly using \u003cstrong\u003eriGetCurrentCase()\u003c/strong\u003e, but the more direct way is to \u003cem\u003eomit the CaseId parameter\u003c/em\u003e in the functions, the Current Case is then automatically used.\u003c/p\u003e\n\u003ch3 id=\"multi-case-scripts\"\u003eMulti Case Scripts\u003c/h3\u003e\n\u003cp\u003eScripts can access the selection state in ResInsight, and also retrieve lists of Case Groups and cases including some meta information. This can be used if the scripts need to get values from some cases, and store the results in others, etc.\u003c/p\u003e\n\u003ch3 id=\"case-types\"\u003eCase Types\u003c/h3\u003e\n\u003cp\u003eThe case type (Labeled \u0026ldquo;CaseType\u0026rdquo; in the following specification) of a case is returned as a text string when retrieving lists of cases, and is one of the following:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCase Type\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eResultCase\u003c/td\u003e\n\u003ctd\u003eA binary Eclipse case\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eInputCase\u003c/td\u003e\n\u003ctd\u003eA case based on ASCII Eclipse input data\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eStatisticsCase\u003c/td\u003e\n\u003ctd\u003eA statistics case based on many source cases in Grid Case Group\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSourceCase\u003c/td\u003e\n\u003ctd\u003eA binary Eclipse case in a Grid Case Group\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"unresolved-issues\"\u003eUnresolved Issues\u003c/h3\u003e\n\u003cp\u003eThe issue around having multiple instances of ResInsight is still not addressed, but might affect the function signatures by adding a port number parameter to all of them. We will try to find ways to avoid this, but are still not certain that we will succeed.\u003c/p\u003e\n\u003ch2 id=\"specification\"\u003eSpecification\u003c/h2\u003e\n\u003ch3 id=\"project-information\"\u003eProject Information\u003c/h3\u003e\n\u003cp\u003eThe case information is presented in an octave Structure called CaseInfo, and contains the following fields:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eCaseInfo = {\r\n  CaseId      = int    # A project-unique integer used to address this\r\n                       # particular case \r\n  CaseName    = string # The name that has been assigned to the case\r\n                       # in ResInsight.\r\n  CaseType    = string # See the description above\r\n  CaseGroupId = int    # A project-unique integer identifying the\r\n                       # CaseGroup this case is a member of.\r\n                       # -1 if not in a CaseGroup. Valid only for \r\n                       # Statistics-, and SourceCases\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"caseinfo-rigetcurrentcase\"\u003eCaseInfo riGetCurrentCase()\u003c/h4\u003e\n\u003cp\u003eThis function returns a CaseInfo Structure for the Case considered being the \u0026ldquo;Current Case\u0026rdquo; by ResInsight. When ResInsight loops over a selection of cases and executes an Octave script for each of them, this function returns the CaseInfo for that particular Case.\u003c/p\u003e\n\u003ch4 id=\"vectorcaseinfo-rigetselectedcases\"\u003eVector[CaseInfo] riGetSelectedCases()\u003c/h4\u003e\n\u003cp\u003eThis function returns a CaseInfo Structure for each of the cases selected in ResInsight at the time when the script launched.\u003c/p\u003e\n\u003ch4 id=\"vectorcasegroupinfo-rigetcasegroups\"\u003eVector[CaseGroupInfo] riGetCaseGroups()\u003c/h4\u003e\n\u003cp\u003eThis function returns a CaseGroupInfo Structure for each of the case groups in the current ResInsight project.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eCaseGroupInfo = {\r\n  CaseGroupId   = int    # A project-unique integer used to address\r\n                         # this particular CaseGroup\r\n  CaseGroupName = string # The name assigned to the CaseGroup \r\n                         # in ResInsight\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"vectorcaseinfo-rigetcasescasegroupid\"\u003eVector[CaseInfo] riGetCases([CaseGroupId])\u003c/h4\u003e\n\u003cp\u003eThis function returns a CaseInfo Structure for all the cases in the current ResInsight project, including the Statistics cases and Source cases in a Grid Case Group. \nIf a CaseGroupId is provided, only the cases in that Case Group will be returned.\u003c/p\u003e\n\u003ch3 id=\"retrieving-grid-metadata\"\u003eRetrieving Grid Metadata\u003c/h3\u003e\n\u003ch4 id=\"matrixnumactivecells9-rigetactivecellinfocaseid-porositymodel--matrixfracture-\"\u003eMatrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;] )\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix containing grid and IJK information about each of the active cells in the requested case. The columns contain the following information:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e[GridIdx, I, J, K, ParentGridIdx, PI, PJ, PK, CoarseBoxIdx]\r\n  GridIdx       # The index of the grid the cell resides in.\r\n                # Main grid has index 0\r\n  I, J, K       # 1-based index address of the cell in the grid.\r\n  ParentGridIdx # The index to the grid that this cell's grid \r\n                # is residing in.\r\n  PI, PJ, PK    # 1-based address of the parent grid cell that\r\n                # this cell is a part of.\r\n  CoarseBoxIdx  # 1-based coarsening box index, -1 if none.\r\n                # Coarsening box info can be retrieved using\r\n                # **riGetCoarseningInfo()**\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumcoarsegroups6-rigetcoarseninginfocaseid\"\u003eMatrix[numCoarseGroups][6] riGetCoarseningInfo([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns all coarse box definitions used in the grid.\nThe columns contain the following information:\n[I1, I2, J1, J2, K1, K2]: 1-based index addresses of the min and max corners of the coarsening box.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumgrids3-rigetgriddimensionscaseid\"\u003eMatrix[numGrids][3] riGetGridDimensions([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix: One row for each grid, starting with the main grid.\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eNOTE\u003c/em\u003e: This means that the \u0026ldquo;normal\u0026rdquo; GridIndices where 0 means Main Grid does not work directly with this matrix. You have to add 1.\u003c/p\u003e\n\u003cp\u003eThe columns contain the following information:\n[NI, NJ, NK]:  I, J, K dimensions of the grid. \nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"vectortimestepdate-rigettimestepdatescaseid\"\u003eVector[TimeStepDate] riGetTimeStepDates([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns the date information for each of the time steps in the case as a Vector of Structures.\nThe Structure is defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eTimeStepDate = {\r\n  Year    = int # The year eg. 2013\r\n  Month   = int # The month. Eg. 12\r\n  Day     = int # The day in the month. Eg. 24\r\n  Hour    = int # The hour of the day. Eg. 17\r\n  Minute  = int # The minute in the hour. Eg. 55\r\n  Second  = int # The second within the minute. Eg. 30\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"vectordecimalday-rigettimestepdayscaseid\"\u003eVector[DecimalDay] riGetTimeStepDays([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns the time from the simulation start as decimal days for all the time steps as a Vector of doubles.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch3 id=\"retrieving-property-data\"\u003eRetrieving Property Data\u003c/h3\u003e\n\u003ch4 id=\"vectorpropertyinfo-rigetpropertynamescaseid--porositymodel--matrixfracture\"\u003eVector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eThis function returns the name and type of all the properties in the case as a Vector of Structures.\nThe Structure is defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ePropertyInfo {\r\n  PropName    = string # Name of the property as received from\r\n                       # the analysis tool\r\n  PropType    = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\r\n                       # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Input\u0026quot;, \u0026quot;Generated\u0026quot;\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumactivecellsnumtimestepsrequested-rigetactivecellpropertycaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture\"\u003eMatrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix: [ActiveCells][Num TimestepsRequested] containing the requested property data from the case with CaseId.\nIf the case contains coarse-cells, the results are expanded onto the active cells. \nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used. \nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\u003ch4 id=\"matrixnuminumjnumknumtimestepsrequested-rigetgridpropertycaseid-gridindex--propertyname-requestedtimesteps-porositymodel--matrixfracture\"\u003eMatrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eThis function returns a matrix of the requested property data for all the grid cells in the requested grid for each requested time step.\nGrids are indexed from 0 (main grid) to max number of LGR\u0026rsquo;s \nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\nWriting Back to ResInsight\u003c/p\u003e\n\u003ch4 id=\"risetactivecellproperty-matrixnumactivecellsnumtimesteps-caseid-propertyname-timestepindices-porositymodel--matrixfracture\"\u003eriSetActiveCellProperty( Matrix[numActiveCells][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eInterprets the supplied matrix as a property set defined for the active cells in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. \nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\u003cbr\u003e\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"risetgridproperty-matrixnuminumjnumknumtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel--matrixfracture\"\u003eriSetGridProperty( Matrix[numI][numJ][numK][numTimeSteps], [CaseId], GridIndex, PropertyName, [TimeStepIndices], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eInterprets the supplied matrix as a property set defined for all cells in one of the grids in a case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;. \nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the time steps present in the supplied data matrix, and must thus be complete. The time step data will then be put into ResInsight at the time steps requested.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch3 id=\"cell-geometry-functions\"\u003eCell Geometry Functions\u003c/h3\u003e\n\u003ch4 id=\"matrixnuminumjnumk3-rigetcellcenterscaseid-gridindex\"\u003eMatrix[numI][numJ][numK][3] riGetCellCenters([CaseId], GridIndex)\u003c/h4\u003e\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the center point of all the cells in the grid.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixactivecells3-rigetactivecellcenterscaseid-porositymodel--matrixfracture\"\u003eMatrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the center point of each of the active cells.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nCell Corner Index layout\nThe corner indices follow the ECLIPSE standard:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e      6-------------7             |k     \r\n     /|            /|             | /j   \r\n    / |           / |             |/     \r\n   /  |          /  |             *---i  \r\n  4-------------5   |\r\n  |   |         |   |\r\n  |   2---------|---3\r\n  |  /          |  /\r\n  | /           | /\r\n  |/            |/\r\n  0-------------1\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"matrixnuminumjnumk83-rigetcellcornerscaseid-gridindex\"\u003eMatrix[numI][numJ][numK][8][3] riGetCellCorners([CaseId], GridIndex)\u003c/h4\u003e\n\u003cp\u003eThis function returns the UTM coordinates(X, Y, Z) of the 8 corners of all the cells in the grid.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixactivecells83-rigetactivecellcornerscaseid-porositymodel--matrixfracture\"\u003eMatrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;])\u003c/h4\u003e\n\u003cp\u003eThis function returns the UTM coordinates (X, Y, Z) of the 8 corners of each of the active cells.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch3 id=\"well-data-functions\"\u003eWell Data Functions\u003c/h3\u003e\n\u003ch4 id=\"vectorwellnames-rigetwellnamescaseid\"\u003eVector[WellNames] riGetWellNames([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns the names of all the wells in the case as a Vector of strings.\nIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nVector[WellCellInfo] riGetWellCells([CaseId], WellName, TimeStep)\nThis function returns the cells defined in the specified well for the time step requested as a vector of Structures. The Structure is defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWellCellInfo {\r\n  I, J, K     = int # Index to the cell in the grid\r\n  GridIndex   = int # the index of the grid. Main grid has index 0.\r\n  CellStatus  = int # is either 0 or 1, meaning the cell is closed\r\n                    # or open respectively\r\n  BranchId    = int # Branch id of the branch intersecting the cell\r\n  SegmentId   = int # Branch segment id of the branch intersecting the cell\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"vectorwellstatus-rigetwellstatus-caseid-wellname-requestedtimesteps\"\u003eVector[WellStatus] riGetWellStatus ([CaseId], WellName, [RequestedTimeSteps])\u003c/h4\u003e\n\u003cp\u003eThis function returns the status information for a specified well for each requested time step as a vector of Structures. The Structure is defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWellStatus {\r\n  WellType    = string # \u0026quot;Producer\u0026quot;, \u0026quot;OilInjector\u0026quot;,\r\n                       # \u0026quot;WaterInjector\u0026quot;, \u0026quot;GasInjector\u0026quot;, \u0026quot;NotDefined\u0026quot;\r\n  WellStatus  = int    # is either 0 or 1, meaning the well is shut\r\n                       # or open respectively\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumselectedcells5-rigetselectedcellscaseid\"\u003eMatrix[numSelectedCells][5] riGetSelectedCells([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix containing the cell info for each selected cell in the case with \u003ccode\u003eCaseId\u003c/code\u003e.\nThe columns contain the following information:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e[CaseId, GridIdx, I, J, K]\r\n  CaseId  # The ID of the case the cell resides in.\r\n  GridIdx # The index of the grid the cell resides in.\r\n          # Main grid has index 0\r\n  I, J, K # 1-based index of the cell in the grid.\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumselectedcellsnumtimestepsrequested-rigetgridpropertyforselectedcellscaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture-\"\u003eMatrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = \u0026ldquo;Matrix\u0026quot;|\u0026quot;Fracture\u0026rdquo;] )\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix: [numSelectedCells][numTimestepsRequested] containing the requested property data from the case with CaseId.\u003c/p\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of 1-based indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\u003ch4 id=\"vectorpropertyinfo-rigetnncpropertynamescaseid\"\u003eVector[PropertyInfo] riGetNNCPropertyNames([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns the name and type of all NNC properties in the case as a vector of structures.\u003c/p\u003e\n\u003cp\u003eThe structure is defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ePropertyInfo {\r\n  PropName    = string # Name of the property as received from\r\n                       # the analysis tool\r\n  PropType    = string # The type of the property: \u0026quot;StaticNative\u0026quot;,\r\n                       # \u0026quot;DynamicNative\u0026quot;, \u0026quot;Generated\u0026quot;\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"matrixnumnncconnections2-rigetnncconnectionscaseid\"\u003eMatrix[numNNCConnections][2] riGetNNCConnections([CaseId])\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix containing grid and IJK information about each NNC connection.\nEach row contains a from and to cell for the connection.\nThe cells are specified in a structure defined as:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eCellInfo = {\r\n  GridIndex = int # Index of the grid the cell resides in.\r\n                  # Main grid has index 0.\r\n  I, J, K   = int # 1-based index address of the cell in the grid.\r\n}\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch4 id=\"matrixnumconnectionsnumtimestepsrequested-rigetdynamicnncvaluescaseid-propertyname-requestedtimesteps\"\u003eMatrix[numConnections][numTimestepsRequested] riGetDynamicNNCValues([CaseId], PropertyName, [RequestedTimeSteps])\u003c/h4\u003e\n\u003cp\u003eThis function returns a two dimensional matrix: [Num Connections][Num Time Steps Requested] containing the value of the requested property from the case with CaseId. The order of connections is the same as the order from \u003ccode\u003eriGetNNCConnections\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\nThe RequestedTimeSteps must contain a list of indices to the requested time steps. If not defined, all the time steps are returned.\u003c/p\u003e\n\u003ch4 id=\"vectornumconnections-rigetstaticnncvaluescaseid-propertyname\"\u003eVector[numConnections] riGetStaticNNCValues([CaseId], PropertyName)\u003c/h4\u003e\n\u003cp\u003eThis function returns a vector of values for the requested static property for each NNC connection. The order of connections is the same as the order from \u003ccode\u003eriGetNNCConnections\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n\u003ch4 id=\"risetnncpropertymatrixnumnncconnectionsnumtimesteps-caseid-propertyname-timestepindices\"\u003eriSetNNCProperty(Matrix[numNNCConnections][numTimeSteps], [CaseId], PropertyName, [TimeStepIndices])\u003c/h4\u003e\n\u003cp\u003eInterprets the supplied matrix as a property set defined for the NNC connections in the case, and puts the data into ResInsight as a \u0026ldquo;Generated\u0026rdquo; property with the name \u0026ldquo;PropertyName\u0026rdquo;.\nThe \u0026ldquo;TimeStepIndices\u0026rdquo; argument is used to \u0026ldquo;label\u0026rdquo; all the steps present in the supplied data matrix and must thus be complete.\nThe time step data will then be put into ResInsight at the time steps requested.\u003c/p\u003e\n\u003cp\u003eIf the CaseId is not defined, ResInsight\u0026rsquo;s Current Case is used.\u003c/p\u003e\n",
                 url:      "/scripting/octaveinterfacereference/"
             };
         
@@ -2343,8 +2376,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/resultinspection/"] = {
                 title:    "Result Inspection",
-                content:  " The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. The selected cells will be highlighted, text information displayed in the Result Info docking window, and the time-history values plotted in the Result Plot, if available.\nVisibility of the docking widows can be controlled from the Windows menu.\n\rResult Info Clicking cells will display slightly different information text based on the case type as described in the following tables.\nEclipse Model    Geometry Description     Reservoir cell Displays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section \u0026ndash; Grid cell result details \u0026ndash;   Fault face Displays the same info as for a Reservoir cell. In addition the section \u0026ndash; Fault result details \u0026ndash; containing Fault Name and Fault Face information.   Fault face with NNC Displays the same info as Fault face, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section \u0026ndash; NNC details \u0026ndash; is geometry information of the two cells connected by the NNC.   Formation names Displays name of formation the cell is part of    Geomechanical Model    Name Description     Closest result Closest node ID and result value   Element Element ID and IJK coordinate for the element   Intersection point Location of left-click intersection of the geometry   Element result details Lists all integration point IDs and results with associated node IDs and node coordinates   Formation names Displays name of formation the cell is part of    Result Plot If a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window Result Plot as one curve for each cell.\nAdditional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.\nTo clear the cell-selection, left-click outside the visible geometry.\nAdding the Curves to a Summary Plot The time history curves of the selected cells can be added to a Summary Plot by right-clicking in the Result Plot or in the 3D View.\nA dialog will appear to prompt you to select an existion plot, or to create a new one.\nPVT Plot (Eclipse Cases Only) Show the PVT Plot window by selecting Windows -\u0026gt; PVT Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\nThe PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots Phase Formation Volume Factor and the other plots Phase Viscosity, both against pressure. The Phase can be either oil or gas, and can be selected in the top left corner of the window.\nPressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.\nRelative Permeability Plot (Eclipse Cases Only) Show the Relative Permeability Plot window by selecting Windows -\u0026gt; Relative Permeability Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\nThe Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:\n   Name Description Axis     KRW Relative permeability water KR (Left)   KRG Relative permeability gas KR (Left)   KROW Relative permeability oil water KR (Left)   KROG Relative permeability oil gas KR (Left)   PCOW Capilar pressure oil water PC (Right)   PCOG Capilar pressure oil gas PC (Right)    Saturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.\n   Option Description     Log Scale Kr Axis Enable logarithmic Kr-axis   Show Unscaled Display curves unscaled   Fixed [0, 1] X-axis Use a fixed range on X-axis   Fixed [0, 1] Kr-axis Use a fixed range on Kr-axis    Mohr\u0026rsquo;s Circle Plot (Geo Mechanical Models Only) Show the Mohr\u0026rsquo;s Circle Plot window by selecting Windows -\u0026gt; Mohr\u0026rsquo;s Circle Plot. When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.\nThe Mohr\u0026rsquo;s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the cohesion and friction angle given in the geo mechanical view\u0026rsquo;s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultInspectionOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view.\nThe selected cells will be highlighted, text information displayed in the \u003cstrong\u003eResult Info\u003c/strong\u003e docking window, and the time-history values plotted in the \u003cstrong\u003eResult Plot\u003c/strong\u003e, if available.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eVisibility of the docking widows can be controlled from the \u003cb\u003eWindows\u003c/b\u003e menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"result-info\"\u003eResult Info\u003c/h2\u003e\n\n\u003cp\u003eClicking cells will display slightly different information text based on the case type as described in the following tables.\u003c/p\u003e\n\n\u003ch3 id=\"eclipse-model\"\u003eEclipse Model\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eGeometry\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eReservoir cell\u003c/td\u003e\n\u003ctd\u003eDisplays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section \u003cstrong\u003e\u0026ndash; Grid cell result details \u0026ndash;\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFault face\u003c/td\u003e\n\u003ctd\u003eDisplays the same info as for a \u003cem\u003eReservoir cell\u003c/em\u003e. In addition the section \u003cstrong\u003e\u0026ndash; Fault result details \u0026ndash;\u003c/strong\u003e containing Fault Name and Fault Face information.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFault face with NNC\u003c/td\u003e\n\u003ctd\u003eDisplays the same info as \u003cem\u003eFault face\u003c/em\u003e, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section \u003cstrong\u003e\u0026ndash; NNC details \u0026ndash;\u003c/strong\u003e is geometry information of the two cells connected by the NNC.\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFormation names\u003c/td\u003e\n\u003ctd\u003eDisplays name of formation the cell is part of\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch3 id=\"geomechanical-model\"\u003eGeomechanical Model\u003c/h3\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eClosest result\u003c/td\u003e\n\u003ctd\u003eClosest node ID and result value\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eElement\u003c/td\u003e\n\u003ctd\u003eElement ID and IJK coordinate for the element\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eIntersection point\u003c/td\u003e\n\u003ctd\u003eLocation of left-click intersection of the geometry\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eElement result details\u003c/td\u003e\n\u003ctd\u003eLists all integration point IDs and results with associated node IDs and node coordinates\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFormation names\u003c/td\u003e\n\u003ctd\u003eDisplays name of formation the cell is part of\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch2 id=\"result-plot\"\u003eResult Plot\u003c/h2\u003e\n\n\u003cp\u003eIf a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window \u003cstrong\u003eResult Plot\u003c/strong\u003e as one curve for each cell.\u003c/p\u003e\n\n\u003cp\u003eAdditional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.\u003c/p\u003e\n\n\u003cp\u003eTo clear the cell-selection, left-click outside the visible geometry.\u003c/p\u003e\n\n\u003ch3 id=\"adding-the-curves-to-a-summary-plot\"\u003eAdding the Curves to a Summary Plot\u003c/h3\u003e\n\n\u003cp\u003eThe time history curves of the selected cells can be added to a Summary Plot by right-clicking in the \u003cstrong\u003eResult Plot\u003c/strong\u003e or in the 3D View.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultPlotToSummaryPlotCommand.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA dialog will appear to prompt you to select an existion plot, or to create a new one.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultPlotToSummaryPlotDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"pvt-plot-eclipse-cases-only\"\u003ePVT Plot (Eclipse Cases Only)\u003c/h2\u003e\n\n\u003cp\u003eShow the PVT Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; PVT Plot\u003c/strong\u003e. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/pvtOil.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/pvtGas.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots \u003cem\u003ePhase Formation Volume Factor\u003c/em\u003e and the other plots \u003cem\u003ePhase Viscosity\u003c/em\u003e, both against pressure. The \u003cem\u003ePhase\u003c/em\u003e can be either oil or gas, and can be selected in the top left corner of the window.\u003c/p\u003e\n\n\u003cp\u003ePressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.\u003c/p\u003e\n\n\u003ch2 id=\"relative-permeability-plot-eclipse-cases-only\"\u003eRelative Permeability Plot (Eclipse Cases Only)\u003c/h2\u003e\n\n\u003cp\u003eShow the Relative Permeability Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; Relative Permeability Plot\u003c/strong\u003e.  When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/RelativePermeability.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eAxis\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eKRW\u003c/td\u003e\n\u003ctd\u003eRelative permeability water\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eKRG\u003c/td\u003e\n\u003ctd\u003eRelative permeability gas\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eKROW\u003c/td\u003e\n\u003ctd\u003eRelative permeability oil water\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eKROG\u003c/td\u003e\n\u003ctd\u003eRelative permeability oil gas\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ePCOW\u003c/td\u003e\n\u003ctd\u003eCapilar pressure oil water\u003c/td\u003e\n\u003ctd\u003ePC (Right)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ePCOG\u003c/td\u003e\n\u003ctd\u003eCapilar pressure oil gas\u003c/td\u003e\n\u003ctd\u003ePC (Right)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eSaturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLog Scale Kr Axis\u003c/td\u003e\n\u003ctd\u003eEnable logarithmic Kr-axis\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eShow Unscaled\u003c/td\u003e\n\u003ctd\u003eDisplay curves unscaled\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFixed [0, 1] X-axis\u003c/td\u003e\n\u003ctd\u003eUse a fixed range on X-axis\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFixed [0, 1] Kr-axis\u003c/td\u003e\n\u003ctd\u003eUse a fixed range on Kr-axis\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch2 id=\"mohr-s-circle-plot-geo-mechanical-models-only\"\u003eMohr\u0026rsquo;s Circle Plot (Geo Mechanical Models Only)\u003c/h2\u003e\n\n\u003cp\u003eShow the Mohr\u0026rsquo;s Circle Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; Mohr\u0026rsquo;s Circle Plot\u003c/strong\u003e.  When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/mohrsCircles.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Mohr\u0026rsquo;s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the \u003cem\u003ecohesion\u003c/em\u003e and \u003cem\u003efriction angle\u003c/em\u003e given in the geo mechanical view\u0026rsquo;s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).\u003c/p\u003e\n",
+                content:  "The results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. The selected cells will be highlighted, text information displayed in the Result Info docking window, and the time-history values plotted in the Result Plot, if available.\nVisibility of the docking widows can be controlled from the Windowsmenu.\n\rResult Info Clicking cells will display slightly different information text based on the case type as described in the following tables.\nEclipse Model    Geometry Description     Reservoir cell Displays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section \u0026ndash; Grid cell result details \u0026ndash;   Fault face Displays the same info as for a Reservoir cell. In addition the section \u0026ndash; Fault result details \u0026ndash; containing Fault Name and Fault Face information.   Fault face with NNC Displays the same info as Fault face, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section \u0026ndash; NNC details \u0026ndash; is geometry information of the two cells connected by the NNC.   Formation names Displays name of formation the cell is part of    Geomechanical Model    Name Description     Closest result Closest node ID and result value   Element Element ID and IJK coordinate for the element   Intersection point Location of left-click intersection of the geometry   Element result details Lists all integration point IDs and results with associated node IDs and node coordinates   Formation names Displays name of formation the cell is part of    Result Plot If a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window Result Plot as one curve for each cell.\nAdditional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.\nTo clear the cell-selection, left-click outside the visible geometry.\nAdding the Curves to a Summary Plot The time history curves of the selected cells can be added to a Summary Plot by right-clicking in the Result Plot or in the 3D View.\nA dialog will appear to prompt you to select an existion plot, or to create a new one.\nPVT Plot (Eclipse Cases Only) Show the PVT Plot window by selecting Windows -\u0026gt; PVT Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\nThe PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots Phase Formation Volume Factor and the other plots Phase Viscosity, both against pressure. The Phase can be either oil or gas, and can be selected in the top left corner of the window.\nPressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.\nRelative Permeability Plot (Eclipse Cases Only) Show the Relative Permeability Plot window by selecting Windows -\u0026gt; Relative Permeability Plot. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\nThe Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:\n   Name Description Axis     KRW Relative permeability water KR (Left)   KRG Relative permeability gas KR (Left)   KROW Relative permeability oil water KR (Left)   KROG Relative permeability oil gas KR (Left)   PCOW Capilar pressure oil water PC (Right)   PCOG Capilar pressure oil gas PC (Right)    Saturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.\n   Option Description     Log Scale Kr Axis Enable logarithmic Kr-axis   Show Unscaled Display curves unscaled   Fixed [0, 1] X-axis Use a fixed range on X-axis   Fixed [0, 1] Kr-axis Use a fixed range on Kr-axis    Mohr\u0026rsquo;s Circle Plot (Geo Mechanical Models Only) Show the Mohr\u0026rsquo;s Circle Plot window by selecting Windows -\u0026gt; Mohr\u0026rsquo;s Circle Plot. When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.\nThe Mohr\u0026rsquo;s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the cohesion and friction angle given in the geo mechanical view\u0026rsquo;s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultInspectionOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe results mapped on the 3D model can be inspected in detail by left clicking cells in the 3D view. \nThe selected cells will be highlighted, text information displayed in the \u003cstrong\u003eResult Info\u003c/strong\u003e docking window, and the time-history values plotted in the \u003cstrong\u003eResult Plot\u003c/strong\u003e, if available.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eVisibility of the docking widows can be controlled from the \u003c!-- raw HTML omitted --\u003eWindows\u003c!-- raw HTML omitted --\u003e menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"result-info\"\u003eResult Info\u003c/h2\u003e\n\u003cp\u003eClicking cells will display slightly different information text based on the case type as described in the following tables.\u003c/p\u003e\n\u003ch3 id=\"eclipse-model\"\u003eEclipse Model\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eGeometry\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eReservoir cell\u003c/td\u003e\n\u003ctd\u003eDisplays grid cell result value, cell face, grid index and IJK coordinates for the cell. The intersection point coordinates is also displayed. Additional result details are listed in the section \u003cstrong\u003e\u0026ndash; Grid cell result details \u0026ndash;\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFault face\u003c/td\u003e\n\u003ctd\u003eDisplays the same info as for a \u003cem\u003eReservoir cell\u003c/em\u003e. In addition the section \u003cstrong\u003e\u0026ndash; Fault result details \u0026ndash;\u003c/strong\u003e containing Fault Name and Fault Face information.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFault face with NNC\u003c/td\u003e\n\u003ctd\u003eDisplays the same info as \u003cem\u003eFault face\u003c/em\u003e, except the Non Neighbor Connections (NNC) result value is displayed instead of grid cell value. Information added in section \u003cstrong\u003e\u0026ndash; NNC details \u0026ndash;\u003c/strong\u003e is geometry information of the two cells connected by the NNC.\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFormation names\u003c/td\u003e\n\u003ctd\u003eDisplays name of formation the cell is part of\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"geomechanical-model\"\u003eGeomechanical Model\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eClosest result\u003c/td\u003e\n\u003ctd\u003eClosest node ID and result value\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eElement\u003c/td\u003e\n\u003ctd\u003eElement ID and IJK coordinate for the element\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eIntersection point\u003c/td\u003e\n\u003ctd\u003eLocation of left-click intersection of the geometry\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eElement result details\u003c/td\u003e\n\u003ctd\u003eLists all integration point IDs and results with associated node IDs and node coordinates\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFormation names\u003c/td\u003e\n\u003ctd\u003eDisplays name of formation the cell is part of\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch2 id=\"result-plot\"\u003eResult Plot\u003c/h2\u003e\n\u003cp\u003eIf a dynamic none-Flow Diagnostics result is active, the result values of the selected cells for all time steps are displayed in the docking window \u003cstrong\u003eResult Plot\u003c/strong\u003e as one curve for each cell.\u003c/p\u003e\n\u003cp\u003eAdditional curves can be added to the plot if CTRL-key is pressed during picking. The different cells are highlighted in different colors, and the corresponding curve is colored using the same color.\u003c/p\u003e\n\u003cp\u003eTo clear the cell-selection, left-click outside the visible geometry.\u003c/p\u003e\n\u003ch3 id=\"adding-the-curves-to-a-summary-plot\"\u003eAdding the Curves to a Summary Plot\u003c/h3\u003e\n\u003cp\u003eThe time history curves of the selected cells can be added to a Summary Plot by right-clicking in the \u003cstrong\u003eResult Plot\u003c/strong\u003e or in the 3D View.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultPlotToSummaryPlotCommand.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA dialog will appear to prompt you to select an existion plot, or to create a new one.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResultPlotToSummaryPlotDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"pvt-plot-eclipse-cases-only\"\u003ePVT Plot (Eclipse Cases Only)\u003c/h2\u003e\n\u003cp\u003eShow the PVT Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; PVT Plot\u003c/strong\u003e. When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/pvtOil.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/pvtGas.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe PVT plot window shows two plots, based on PVTNUM in the selected cell. One plots \u003cem\u003ePhase Formation Volume Factor\u003c/em\u003e and the other plots \u003cem\u003ePhase Viscosity\u003c/em\u003e, both against pressure. The \u003cem\u003ePhase\u003c/em\u003e can be either oil or gas, and can be selected in the top left corner of the window.\u003c/p\u003e\n\u003cp\u003ePressure for the selected cell, at the current time step, is marked on the plot as a vertical line, and a large circle marks the scalar value of the cell (formation volume factor/viscosity). RV for the selected cell is also shown.\u003c/p\u003e\n\u003ch2 id=\"relative-permeability-plot-eclipse-cases-only\"\u003eRelative Permeability Plot (Eclipse Cases Only)\u003c/h2\u003e\n\u003cp\u003eShow the Relative Permeability Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; Relative Permeability Plot\u003c/strong\u003e.  When it is turned on, it will only be visible when the active view is a view of an Eclipse case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/RelativePermeability.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Relative Permeability Plot window shows up to six curves, based on SATNUM in the selected cell. The curves can be turned on/off in the top left corner of the window, and they are described in the following table:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eName\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003cth\u003eAxis\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eKRW\u003c/td\u003e\n\u003ctd\u003eRelative permeability water\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eKRG\u003c/td\u003e\n\u003ctd\u003eRelative permeability gas\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eKROW\u003c/td\u003e\n\u003ctd\u003eRelative permeability oil water\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eKROG\u003c/td\u003e\n\u003ctd\u003eRelative permeability oil gas\u003c/td\u003e\n\u003ctd\u003eKR (Left)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePCOW\u003c/td\u003e\n\u003ctd\u003eCapilar pressure oil water\u003c/td\u003e\n\u003ctd\u003ePC (Right)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePCOG\u003c/td\u003e\n\u003ctd\u003eCapilar pressure oil gas\u003c/td\u003e\n\u003ctd\u003ePC (Right)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eSaturation of water and gas in the selected cell, at the current time step, are annotated in the plot by a blue and orange vertical line, respectively. The intersections between the lines and the relevant curves are marked with large circles.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOption\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eLog Scale Kr Axis\u003c/td\u003e\n\u003ctd\u003eEnable logarithmic Kr-axis\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eShow Unscaled\u003c/td\u003e\n\u003ctd\u003eDisplay curves unscaled\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFixed [0, 1] X-axis\u003c/td\u003e\n\u003ctd\u003eUse a fixed range on X-axis\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFixed [0, 1] Kr-axis\u003c/td\u003e\n\u003ctd\u003eUse a fixed range on Kr-axis\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch2 id=\"mohrs-circle-plot-geo-mechanical-models-only\"\u003eMohr\u0026rsquo;s Circle Plot (Geo Mechanical Models Only)\u003c/h2\u003e\n\u003cp\u003eShow the Mohr\u0026rsquo;s Circle Plot window by selecting \u003cstrong\u003eWindows -\u0026gt; Mohr\u0026rsquo;s Circle Plot\u003c/strong\u003e.  When it is turned on, it will only be visible when the active view is a view of an Geo Mech case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/mohrsCircles.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Mohr\u0026rsquo;s circle plot shows three circles representing the 3D state of stress for a selected cell. In addition, it shows the envelope, calculated from the \u003cem\u003ecohesion\u003c/em\u003e and \u003cem\u003efriction angle\u003c/em\u003e given in the geo mechanical view\u0026rsquo;s property editor. Several sets of circles and envelopes can be added by selecting more than one cell in any view (as in image above).\u003c/p\u003e\n",
                 url:      "/3d-main-window/resultinspection/"
             };
         
@@ -2352,8 +2385,8 @@ if (!doNotTrack) {
          
             window.store["/export/sectormodel/"] = {
                 title:    "Sector Model",
-                content:  " Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section.\nExporting an Eclipse Sector Model To launch the export dialog, right-click on either the 3D-view in question or the Cell Result.\nExporting Grid and Faults Grid Export The Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the Export Grid Data option. If the option Export in Local Coordinates is checked, the UTM-portion of the coordinates will be stripped and the Grid will be exported in a local coordinate system with no reference to actual location.\nGrid Box Selection The Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:\n All Visible Cells \u0026ndash; Controlled by range and property filters in the current view. All Active Cells \u0026ndash; All active cells in the Grid. The Full Grid \u0026ndash; The complete grid including inactive cells. User Defined Selection \u0026ndash; This will make the min and max IJK selection available to the user.  Furthermore, by checking Make Invisible Cells Inactive any cells that are within the IJK bounding box, but are invisible, will be made inactive (ACTNUM = 0) in the exported grid.\nGrid Refinement The grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.\nFaults Optionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing \u0026ldquo;Do not Export\u0026rdquo; from the Export Fault Data drop down list.\nExporting Parameters The Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are EQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.\nOther statuc result variables may be selected.\nBy default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to append them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the Export Parameters drop down list.\n",
-                html:     "\n\n\u003cp\u003eSub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new\nSimulations on the sub-section.\u003c/p\u003e\n\n\u003ch3 id=\"exporting-an-eclipse-sector-model\"\u003eExporting an Eclipse Sector Model\u003c/h3\u003e\n\n\u003cp\u003eTo launch the export dialog, right-click on either the \u003cstrong\u003e3D-view\u003c/strong\u003e in question or the \u003cstrong\u003eCell Result\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_RightClick.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"exporting-grid-and-faults\"\u003eExporting Grid and Faults\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_Grid.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"grid-export\"\u003eGrid Export\u003c/h4\u003e\n\n\u003cp\u003eThe Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the \u003cstrong\u003eExport Grid Data\u003c/strong\u003e option.\nIf the option \u003cstrong\u003eExport in Local Coordinates\u003c/strong\u003e is checked, the UTM-portion of the coordinates will be stripped and the Grid will\nbe exported in a local coordinate system with no reference to actual location.\u003c/p\u003e\n\n\u003ch4 id=\"grid-box-selection\"\u003eGrid Box Selection\u003c/h4\u003e\n\n\u003cp\u003eThe Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Visible Cells\u003c/strong\u003e \u0026ndash; Controlled by range and property filters in the current view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Active Cells\u003c/strong\u003e \u0026ndash; All active cells in the Grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThe Full Grid\u003c/strong\u003e \u0026ndash; The complete grid including inactive cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Selection\u003c/strong\u003e \u0026ndash; This will make the min and max IJK selection available to the user.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eFurthermore, by checking \u003cstrong\u003eMake Invisible Cells Inactive\u003c/strong\u003e any cells that are within the IJK bounding box, but are invisible, will be made\ninactive (ACTNUM = 0) in the exported grid.\u003c/p\u003e\n\n\u003ch4 id=\"grid-refinement\"\u003eGrid Refinement\u003c/h4\u003e\n\n\u003cp\u003eThe grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.\u003c/p\u003e\n\n\u003ch4 id=\"faults\"\u003eFaults\u003c/h4\u003e\n\n\u003cp\u003eOptionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing \u0026ldquo;Do not Export\u0026rdquo; from the\n\u003cstrong\u003eExport Fault Data\u003c/strong\u003e drop down list.\u003c/p\u003e\n\n\u003ch3 id=\"exporting-parameters\"\u003eExporting Parameters\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_Parameters.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are\nEQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.\u003c/p\u003e\n\n\u003cp\u003eOther statuc result variables may be selected.\u003c/p\u003e\n\n\u003cp\u003eBy default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to\nappend them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the \u003cstrong\u003eExport Parameters\u003c/strong\u003e drop down list.\u003c/p\u003e\n",
+                content:  "Sub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new Simulations on the sub-section.\nExporting an Eclipse Sector Model To launch the export dialog, right-click on either the 3D-view in question or the Cell Result.\nExporting Grid and Faults Grid Export The Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the Export Grid Data option. If the option Export in Local Coordinates is checked, the UTM-portion of the coordinates will be stripped and the Grid will be exported in a local coordinate system with no reference to actual location.\nGrid Box Selection The Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:\n All Visible Cells \u0026ndash; Controlled by range and property filters in the current view. All Active Cells \u0026ndash; All active cells in the Grid. The Full Grid \u0026ndash; The complete grid including inactive cells. User Defined Selection \u0026ndash; This will make the min and max IJK selection available to the user.  Furthermore, by checking Make Invisible Cells Inactive any cells that are within the IJK bounding box, but are invisible, will be made inactive (ACTNUM = 0) in the exported grid.\nGrid Refinement The grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.\nFaults Optionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing \u0026ldquo;Do not Export\u0026rdquo; from the Export Fault Data drop down list.\nExporting Parameters The Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are EQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.\nOther statuc result variables may be selected.\nBy default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to append them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the Export Parameters drop down list.\n",
+                html:     "\u003cp\u003eSub-sections of the Eclipse Grid with Parameters and Faults can be exported to Eclipse ASCII files in order to create new\nSimulations on the sub-section.\u003c/p\u003e\n\u003ch3 id=\"exporting-an-eclipse-sector-model\"\u003eExporting an Eclipse Sector Model\u003c/h3\u003e\n\u003cp\u003eTo launch the export dialog, right-click on either the \u003cstrong\u003e3D-view\u003c/strong\u003e in question or the \u003cstrong\u003eCell Result\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_RightClick.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"exporting-grid-and-faults\"\u003eExporting Grid and Faults\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_Grid.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"grid-export\"\u003eGrid Export\u003c/h4\u003e\n\u003cp\u003eThe Export dialog will allow the user to export grid data as ascii (An Eclipse Input Grid) to a specific file name by checking the \u003cstrong\u003eExport Grid Data\u003c/strong\u003e option.\nIf the option \u003cstrong\u003eExport in Local Coordinates\u003c/strong\u003e is checked, the UTM-portion of the coordinates will be stripped and the Grid will\nbe exported in a local coordinate system with no reference to actual location.\u003c/p\u003e\n\u003ch4 id=\"grid-box-selection\"\u003eGrid Box Selection\u003c/h4\u003e\n\u003cp\u003eThe Grid Box selection group will allow the user to choose whether to export an IJK bounding box surrounding:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Visible Cells\u003c/strong\u003e \u0026ndash; Controlled by range and property filters in the current view.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Active Cells\u003c/strong\u003e \u0026ndash; All active cells in the Grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThe Full Grid\u003c/strong\u003e \u0026ndash; The complete grid including inactive cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Selection\u003c/strong\u003e \u0026ndash; This will make the min and max IJK selection available to the user.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFurthermore, by checking \u003cstrong\u003eMake Invisible Cells Inactive\u003c/strong\u003e any cells that are within the IJK bounding box, but are invisible, will be made\ninactive (ACTNUM = 0) in the exported grid.\u003c/p\u003e\n\u003ch4 id=\"grid-refinement\"\u003eGrid Refinement\u003c/h4\u003e\n\u003cp\u003eThe grid can be refined by a different integer in all three directions by changing the default value of Cell Count = 1 for I, J or K. The grid results will be not be interpolated but all new cells will inherit the value of their original cell.\u003c/p\u003e\n\u003ch4 id=\"faults\"\u003eFaults\u003c/h4\u003e\n\u003cp\u003eOptionally export fault data to a separate fault file or append to the existing grid. Also, fault data can be ommitted by choosing \u0026ldquo;Do not Export\u0026rdquo; from the\n\u003cstrong\u003eExport Fault Data\u003c/strong\u003e drop down list.\u003c/p\u003e\n\u003ch3 id=\"exporting-parameters\"\u003eExporting Parameters\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportSectorModel_Parameters.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Static result values in the Grid may be exported as Eclipse Input Parameters. The default parameters are \nEQLNUM, FIPNUM, NTG, PERMX, PERMY, PERMZ, PORO, PVTNUM, SATNUM and SWATINIT. ACTNUM is exported by default in the Grid Export file.\u003c/p\u003e\n\u003cp\u003eOther statuc result variables may be selected.\u003c/p\u003e\n\u003cp\u003eBy default the Parameters will be exported to a separate file per parameter in the grid folder location. However it is possible to\nappend them to the grid file, export them all into a single parameter file or omit them completely be selecting different options in the \u003cstrong\u003eExport Parameters\u003c/strong\u003e drop down list.\u003c/p\u003e\n",
                 url:      "/export/sectormodel/"
             };
         
@@ -2361,8 +2394,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/other/testimonials/"] = {
                 title:    "Testimonials",
-                content:  "“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”\nDavid Baxendale\nSenior Petroleum Engineering Advisor, RPS Energy\n\u0026ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.\u0026rdquo;\nTor Harald Sandve\nResearcher, International Research Institute of Stavanger (IRIS)\nEquinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.\n\r",
-                html:     "\u003cp\u003e\u003cem\u003e“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”\u003c/em\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eDavid Baxendale\u003cbr\u003e\nSenior Petroleum Engineering Advisor, RPS Energy\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cem\u003e\u0026ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.\u0026rdquo;\u003c/em\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eTor Harald Sandve\u003cbr\u003e\nResearcher, International Research Institute of Stavanger (IRIS)\u003c/strong\u003e\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eEquinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
+                content:  "“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”\nDavid BaxendaleSenior Petroleum Engineering Advisor, RPS Energy\n\u0026ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.\u0026quot;\nTor Harald SandveResearcher, International Research Institute of Stavanger (IRIS)\nEquinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.\n\r",
+                html:     "\u003cp\u003e\u003cem\u003e“I have been using ResInsight now for some time and have stopped using the commercial software as ResInsight is much more responsive and easier to use. It really is an excellent piece of software.”\u003c/em\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eDavid Baxendale\u003c!-- raw HTML omitted --\u003e\nSenior Petroleum Engineering Advisor, RPS Energy\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cem\u003e\u0026ldquo;ResInsight is an excellent tool to visualize simulation results and offers good-looking and illustrative graphs for presentations. I found the integration with Octave especially powerful in my research.\u0026quot;\u003c/em\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTor Harald Sandve\u003c!-- raw HTML omitted --\u003e\nResearcher, International Research Institute of Stavanger (IRIS)\u003c/strong\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eEquinor ASA has initiated, financed and supervised the development of ResInsight and is using it on a daily basis.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
                 url:      "/getting-started/other/testimonials/"
             };
         
@@ -2370,8 +2403,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/filters/"] = {
                 title:    "Cell Filters",
-                content:  " Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:\n Range Filter \u0026ndash; Extracts an IJK subset of the model. Property Filter \u0026ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from  Simulation Wells .\n(Not applicable for Geomechanical cases)\n\rCommon Properties for Range and Property Filters Both filter types can be turned on or off using the toggle in the Project Tree and controlled from their corresponding Property Editor.\nRange Filters and Property filters can either be set to Include cells or to Exclude them.\nThe Exclude setting is used to explicitly remove cells from the visualization, regardless of what other filters say. The Include setting behaves differently for Range filters and Property Filters but marks the cells as visible. The icon in front of the filters show a + or - sign to indicate the setting Range filters Range filters enables the user to define a set of visible regions in the 3D view based on IJK boxes. Each Include range filter will add more cells to the visualization. The view will show the union of all the Include range filters.\nA new range filter can be added by activating the right-click menu for the Range Filters collection in the Project Tree.\nAn I,J or K-slice range filter can be added directly from a Cell in the 3D View by right-clicking the cell and using the right-click menu.\n\rBelow is a snapshot of the Property Editor of the Range Filter :\n Filter Type \u0026ndash; The filter can either make the specified range visible ( Include ), or remove the range from the View ( Exclude ). Grid \u0026ndash; This option selects which of the grids the range is addressing. Apply to Subgrids \u0026ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR\u0026rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.\n  The Start and Width labels in front of the sliders features a number in parenthesis denoting maximum available value.\nThe Start labels shows the index of the start of the active cells.\nThe Width labels shows the number of active cells from the start of the active cells.\nProperty Filters Property Filters applies to the results of the Range Filters and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.\nA new property filter can be made by activating the right-click menu on Property Filters or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.\nThe name of the property filter is automatically set to \u0026ldquo;propertyname (min .. max)\u0026rdquo; as you edit the property filter.\nThe context command Apply As Cell Result on a property filter, sets the Cell Color Result to the same values as the selected property filter.\n\rBelow is a snapshot of the Property Editor of the Property Filter.\nProperty Value Range The filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the Filter Type (Include/Exclude). Exclude-filters removes the selected cells from the View even if some other filter includes them.\nRange Behavior for Flow Diagnostic Results Normally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.\nWe still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.\nCategory Selection If the property is representing integer values, well tracer names or formation names , the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.\nIf it is more convenient to filter the values using a value range, toggle the Category Selection option off.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eCell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filter\u003c/strong\u003e \u0026ndash; Extracts an IJK subset of the model.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filter\u003c/strong\u003e \u0026ndash; Extracts cells with a property value matching a value range.\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe visibilities of cells connection to wells, and fences based on these cells can be controlled from \u003cb\u003e \u003ca href=\"/wells-and-completions/simulationwells/\"\u003eSimulation Wells\u003c/a\u003e \u003c/b\u003e.\u003cbr\u003e\n\u003csmall\u003e\u003ci\u003e(Not applicable for Geomechanical cases)\u003c/i\u003e\u003c/small\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"common-properties-for-range-and-property-filters\"\u003eCommon Properties for Range and Property Filters\u003c/h2\u003e\n\n\u003cp\u003eBoth filter types can be turned on or off using the toggle in the \u003cstrong\u003eProject Tree\u003c/strong\u003e and controlled from their corresponding \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersInTreeView.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eRange Filters and Property filters can either be set to \u003cstrong\u003eInclude\u003c/strong\u003e cells or to \u003cstrong\u003eExclude\u003c/strong\u003e them.\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eExclude\u003c/strong\u003e setting is used to explicitly remove cells from the visualization, regardless of what other filters say.\nThe \u003cstrong\u003eInclude\u003c/strong\u003e setting behaves differently for Range filters and Property Filters but marks the cells as visible.\nThe icon in front of the filters show a + or - sign to indicate the setting \u003cimg src=\"https://resinsight.org/images/3d-main-window/FilterIncEx.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\n\u003ch2 id=\"range-filters\"\u003eRange filters\u003c/h2\u003e\n\n\u003cp\u003eRange filters enables the user to define a set of visible regions in the 3D view based on IJK boxes.\nEach \u003cem\u003eInclude\u003c/em\u003e range filter will \u003cem\u003eadd more cells\u003c/em\u003e to the visualization. The view will show the union of all the \u003cem\u003eInclude\u003c/em\u003e range filters.\u003c/p\u003e\n\n\u003cp\u003eA new range filter can be added by activating the right-click menu for the \u003cstrong\u003eRange Filters\u003c/strong\u003e collection in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eAn I,J or K-slice range filter can be added directly from a Cell in the \u003cb\u003e3D View\u003c/b\u003e by right-clicking the cell and using the right-click menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eRange Filter\u003c/strong\u003e :\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/RangeFilterProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFilter Type\u003c/strong\u003e \u0026ndash; The filter can either make the specified range visible ( \u003cem\u003eInclude\u003c/em\u003e ), or remove the range from the View ( \u003cem\u003eExclude\u003c/em\u003e ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid\u003c/strong\u003e \u0026ndash;  This option selects which of the grids the range is addressing.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eApply to Subgrids\u003c/strong\u003e \u0026ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR\u0026rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eStart\u003c/strong\u003e and \u003cstrong\u003eWidth\u003c/strong\u003e labels in front of the sliders features a number in parenthesis denoting maximum available value.\u003cbr\u003e\nThe \u003cstrong\u003eStart\u003c/strong\u003e labels shows the index of the start of the active cells.\u003cbr\u003e\nThe \u003cstrong\u003eWidth\u003c/strong\u003e labels shows the number of active cells from the start of the active cells.\u003c/p\u003e\n\n\u003ch2 id=\"property-filters\"\u003eProperty Filters\u003c/h2\u003e\n\n\u003cp\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e applies to the results of the \u003cstrong\u003eRange Filters\u003c/strong\u003e and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.\u003c/p\u003e\n\n\u003cp\u003eA new property filter can be made by activating the right-click menu on \u003cstrong\u003eProperty Filters\u003c/strong\u003e or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.\u003c/p\u003e\n\n\u003cp\u003eThe name of the property filter is automatically set to \u003cem\u003e\u0026ldquo;propertyname (min .. max)\u0026rdquo;\u003c/em\u003e as you edit the property filter.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe context command \u003cb\u003eApply As Cell Result\u003c/b\u003e on a property filter, sets the Cell Color Result to the same values as the selected property filter.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eProperty Filter\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PropertyFilterProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"property-value-range\"\u003eProperty Value Range\u003c/h3\u003e\n\n\u003cp\u003eThe filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the \u003cstrong\u003eFilter Type\u003c/strong\u003e (\u003cem\u003eInclude\u003c/em\u003e/\u003cem\u003eExclude\u003c/em\u003e). Exclude-filters removes the selected cells from the \u003cstrong\u003eView\u003c/strong\u003e even if some other filter includes them.\u003c/p\u003e\n\n\u003ch4 id=\"range-behavior-for-flow-diagnostic-results\"\u003eRange Behavior for Flow Diagnostic Results\u003c/h4\u003e\n\n\u003cp\u003eNormally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.\u003c/p\u003e\n\n\u003cp\u003eWe still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.\u003c/p\u003e\n\n\u003ch3 id=\"category-selection\"\u003eCategory Selection\u003c/h3\u003e\n\n\u003cp\u003eIf the property is representing integer values, well tracer names or \u003ca href=\"/3d-main-window/formations\"\u003e formation names \u003c/a\u003e, the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PropertyFilterWithCategories.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIf it is more convenient to filter the values using a value range, toggle the \u003cstrong\u003eCategory Selection\u003c/strong\u003e option off.\u003c/p\u003e\n",
+                content:  "Cell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:\n Range Filter \u0026ndash; Extracts an IJK subset of the model. Property Filter \u0026ndash; Extracts cells with a property value matching a value range.  The visibilities of cells connection to wells, and fences based on these cells can be controlled from Simulation Wells.(Not applicable for Geomechanical cases)\rCommon Properties for Range and Property Filters Both filter types can be turned on or off using the toggle in the Project Tree and controlled from their corresponding Property Editor.\nRange Filters and Property filters can either be set to Include cells or to Exclude them.\nThe Exclude setting is used to explicitly remove cells from the visualization, regardless of what other filters say. The Include setting behaves differently for Range filters and Property Filters but marks the cells as visible. The icon in front of the filters show a + or - sign to indicate the setting Range filters Range filters enables the user to define a set of visible regions in the 3D view based on IJK boxes. Each Include range filter will add more cells to the visualization. The view will show the union of all the Include range filters.\nA new range filter can be added by activating the right-click menu for the Range Filters collection in the Project Tree.\nAn I,J or K-slice range filter can be added directly from a Cell in the 3D Viewby right-clicking the cell and using the right-click menu.\n\rBelow is a snapshot of the Property Editor of the Range Filter :\n Filter Type \u0026ndash; The filter can either make the specified range visible ( Include ), or remove the range from the View ( Exclude ). Grid \u0026ndash; This option selects which of the grids the range is addressing. Apply to Subgrids \u0026ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR\u0026rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.  The Start and Width labels in front of the sliders features a number in parenthesis denoting maximum available value.The Start labels shows the index of the start of the active cells.The Width labels shows the number of active cells from the start of the active cells.\nProperty Filters Property Filters applies to the results of the Range Filters and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.\nA new property filter can be made by activating the right-click menu on Property Filters or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.\nThe name of the property filter is automatically set to \u0026ldquo;propertyname (min .. max)\u0026quot; as you edit the property filter.\nThe context command Apply As Cell Resulton a property filter, sets the Cell Color Result to the same values as the selected property filter.\n\rBelow is a snapshot of the Property Editor of the Property Filter.\nProperty Value Range The filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the Filter Type (Include/Exclude). Exclude-filters removes the selected cells from the View even if some other filter includes them.\nRange Behavior for Flow Diagnostic Results Normally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.\nWe still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.\nCategory Selection If the property is representing integer values, well tracer names or formation names , the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.\nIf it is more convenient to filter the values using a value range, toggle the Category Selection option off.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eCell Filters are used to control visibility of the cells in the 3D view. Two types of filters exists:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filter\u003c/strong\u003e \u0026ndash; Extracts an IJK subset of the model.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filter\u003c/strong\u003e \u0026ndash; Extracts cells with a property value matching a value range.\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe visibilities of cells connection to wells, and fences based on these cells can be controlled from \u003c!-- raw HTML omitted --\u003e \u003c!-- raw HTML omitted --\u003eSimulation Wells\u003c!-- raw HTML omitted --\u003e \u003c!-- raw HTML omitted --\u003e.\u003c!-- raw HTML omitted --\u003e \n\u003c!-- raw HTML omitted --\u003e\u003c!-- raw HTML omitted --\u003e(Not applicable for Geomechanical cases)\u003c!-- raw HTML omitted --\u003e\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"common-properties-for-range-and-property-filters\"\u003eCommon Properties for Range and Property Filters\u003c/h2\u003e\n\u003cp\u003eBoth filter types can be turned on or off using the toggle in the \u003cstrong\u003eProject Tree\u003c/strong\u003e and controlled from their corresponding \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersInTreeView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eRange Filters and Property filters can either be set to \u003cstrong\u003eInclude\u003c/strong\u003e cells or to \u003cstrong\u003eExclude\u003c/strong\u003e them.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eExclude\u003c/strong\u003e setting is used to explicitly remove cells from the visualization, regardless of what other filters say. \nThe \u003cstrong\u003eInclude\u003c/strong\u003e setting behaves differently for Range filters and Property Filters but marks the cells as visible.\nThe icon in front of the filters show a + or - sign to indicate the setting \u003cimg src=\"https://resinsight.org/images/3d-main-window/FilterIncEx.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003ch2 id=\"range-filters\"\u003eRange filters\u003c/h2\u003e\n\u003cp\u003eRange filters enables the user to define a set of visible regions in the 3D view based on IJK boxes.\nEach \u003cem\u003eInclude\u003c/em\u003e range filter will \u003cem\u003eadd more cells\u003c/em\u003e to the visualization. The view will show the union of all the \u003cem\u003eInclude\u003c/em\u003e range filters.\u003c/p\u003e\n\u003cp\u003eA new range filter can be added by activating the right-click menu for the \u003cstrong\u003eRange Filters\u003c/strong\u003e collection in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eAn I,J or K-slice range filter can be added directly from a Cell in the \u003c!-- raw HTML omitted --\u003e3D View\u003c!-- raw HTML omitted --\u003e by right-clicking the cell and using the right-click menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eRange Filter\u003c/strong\u003e :\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/RangeFilterProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFilter Type\u003c/strong\u003e \u0026ndash; The filter can either make the specified range visible ( \u003cem\u003eInclude\u003c/em\u003e ), or remove the range from the View ( \u003cem\u003eExclude\u003c/em\u003e ).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid\u003c/strong\u003e \u0026ndash;  This option selects which of the grids the range is addressing.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eApply to Subgrids\u003c/strong\u003e \u0026ndash; This option tells ResInsight to use the visibility of the cells in the current grid to control the visibility of the cells in sub-LGR\u0026rsquo;s. If this option is turned off, Sub LGR-cells is not included in this particular Range Filter.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe \u003cstrong\u003eStart\u003c/strong\u003e and \u003cstrong\u003eWidth\u003c/strong\u003e labels in front of the sliders features a number in parenthesis denoting maximum available value.\u003c!-- raw HTML omitted --\u003e\nThe \u003cstrong\u003eStart\u003c/strong\u003e labels shows the index of the start of the active cells.\u003c!-- raw HTML omitted --\u003e\nThe \u003cstrong\u003eWidth\u003c/strong\u003e labels shows the number of active cells from the start of the active cells.\u003c/p\u003e\n\u003ch2 id=\"property-filters\"\u003eProperty Filters\u003c/h2\u003e\n\u003cp\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e applies to the results of the \u003cstrong\u003eRange Filters\u003c/strong\u003e and limits the visible cells to the ones approved by the filter. For a cell to be visible it must be accepted by all the property filters.\u003c/p\u003e\n\u003cp\u003eA new property filter can be made by activating the right-click menu on \u003cstrong\u003eProperty Filters\u003c/strong\u003e or by right-clicking inside a 3D view. The new property filter is based on the currently viewed cell result by default.\u003c/p\u003e\n\u003cp\u003eThe name of the property filter is automatically set to \u003cem\u003e\u0026ldquo;propertyname (min .. max)\u0026quot;\u003c/em\u003e as you edit the property filter.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe context command \u003c!-- raw HTML omitted --\u003eApply As Cell Result\u003c!-- raw HTML omitted --\u003e on a property filter, sets the Cell Color Result to the same values as the selected property filter.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the \u003cstrong\u003eProperty Filter\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PropertyFilterProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"property-value-range\"\u003eProperty Value Range\u003c/h3\u003e\n\u003cp\u003eThe filter is based on a property value range (Min - Max). Cells in the range are either shown or hidden depending on the \u003cstrong\u003eFilter Type\u003c/strong\u003e (\u003cem\u003eInclude\u003c/em\u003e/\u003cem\u003eExclude\u003c/em\u003e). Exclude-filters removes the selected cells from the \u003cstrong\u003eView\u003c/strong\u003e even if some other filter includes them.\u003c/p\u003e\n\u003ch4 id=\"range-behavior-for-flow-diagnostic-results\"\u003eRange Behavior for Flow Diagnostic Results\u003c/h4\u003e\n\u003cp\u003eNormally the available range in the sliders is the max and min of all the values in all the time steps. For Flow Diagnostics results, however, the available range is based on the current time step.\u003c/p\u003e\n\u003cp\u003eWe still need to keep the range somewhat fixed while moving from time step to time step, so in order to do so ResInsight tries to keep the intentions of your range settings, as the available range changes. If either the max or min value is set to the limit, ResInsight will keep that setting at the limit even when the limit changes. If you set a specific value for the max or the min, that setting will keep its value, even if it happens to end up outside the available range at a time step.\u003c/p\u003e\n\u003ch3 id=\"category-selection\"\u003eCategory Selection\u003c/h3\u003e\n\u003cp\u003eIf the property is representing integer values, well tracer names or \u003ca href=\"/3d-main-window/formations\"\u003e formation names \u003c/a\u003e, the property filter displays a list of available categories used to filter cells. The separate values can then be toggled on or off using the list in the Property Editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PropertyFilterWithCategories.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf it is more convenient to filter the values using a value range, toggle the \u003cstrong\u003eCategory Selection\u003c/strong\u003e option off.\u003c/p\u003e\n",
                 url:      "/3d-main-window/filters/"
             };
         
@@ -2379,8 +2412,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/"] = {
                 title:    "Scripting",
-                content:  " ResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:\n Command line interface and Command files Python interface Octave interface  Command Line Interface and Command files ResInsight supports several command line parameters for automation via shell scripts. By gathering commands into a Command file, you may run a sequence of commands by supplying the command file as a command line parameter.\nPython Interface ResInsight offers a Python Interface which allows you to interact with a running ResInsight instance from a Python script. This allows using the powerful Python language, numerical libraries, and other support modules in conjunction with ResInsight. The Python client package is compatible with Python 3.\nFor examples on how to use Python, see Examples\nOctave Interface By the interface to Octave you will find:\n Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.\n  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/scripting/ExecuteOctaveScriptOnSelectedCases.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eCommand line interface and Command files\u003c/li\u003e\n\u003cli\u003ePython interface\u003c/li\u003e\n\u003cli\u003eOctave interface\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"command-line-interface-and-command-files\"\u003eCommand Line Interface and Command files\u003c/h2\u003e\n\n\u003cp\u003eResInsight supports several \u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameters\u003c/a\u003e\nfor automation via shell scripts.\nBy gathering commands into a \u003ca href=\"/scripting/commandfile/\"\u003eCommand file\u003c/a\u003e,\nyou may run a sequence of commands by supplying the command file as a\n\u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"python-interface\"\u003ePython Interface\u003c/h2\u003e\n\n\u003cp\u003eResInsight offers a \u003ca href=\"/scripting/pythonrips/\"\u003ePython Interface\u003c/a\u003e\nwhich allows you to interact with a running ResInsight instance from a Python script.\nThis allows using the powerful Python language, numerical libraries, and other support modules in conjunction with ResInsight. The Python client package is compatible with \u003cstrong\u003ePython 3\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eFor examples on how to use Python, see \u003ca href=\"/scripting/pythonexamples/\"\u003eExamples\u003c/a\u003e\u003c/p\u003e\n\n\u003ch2 id=\"octave-interface\"\u003eOctave Interface\u003c/h2\u003e\n\n\u003cp\u003eBy the interface to \u003ca href=\"http://www.gnu.org/software/octave/\" title=\"Octave\"\u003eOctave\u003c/a\u003e you will find:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eOctave functions that communicates with a running ResInsight session\u003c/li\u003e\n\u003cli\u003eFeatures to simplify management and editing of Octave scripts from ResInsight\u003c/li\u003e\n\u003cli\u003eCommands to execute scripts using Octave.\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "ResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:\n Command line interface and Command files Python interface Octave interface  Command Line Interface and Command files ResInsight supports several [command line parameters] (/scripting/commandlineinterface/) for automation via shell scripts. By gathering commands into a Command file, you may run a sequence of commands by supplying the command file as a command line parameter.\nPython Interface ResInsight offers a [Python Interface] (/scripting/pythonrips/) which allows you to interact with a running ResInsight instance from a Python script. This allows using the powerful Python language, numerical libraries, and other support modules in conjunction with ResInsight. The Python client package is compatible with Python 3.\nFor examples on how to use Python, see Examples\nOctave Interface By the interface to Octave you will find:\n Octave functions that communicates with a running ResInsight session Features to simplify management and editing of Octave scripts from ResInsight Commands to execute scripts using Octave.  ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/ExecuteOctaveScriptOnSelectedCases.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCommand line interface and Command files\u003c/li\u003e\n\u003cli\u003ePython interface\u003c/li\u003e\n\u003cli\u003eOctave interface\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"command-line-interface-and-command-files\"\u003eCommand Line Interface and Command files\u003c/h2\u003e\n\u003cp\u003eResInsight supports several [command line parameters] (/scripting/commandlineinterface/)\nfor automation via shell scripts. \nBy gathering commands into a \u003ca href=\"/scripting/commandfile/\"\u003eCommand file\u003c/a\u003e,\nyou may run a sequence of commands by supplying the command file as a \n\u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"python-interface\"\u003ePython Interface\u003c/h2\u003e\n\u003cp\u003eResInsight offers a [Python Interface] (/scripting/pythonrips/)\nwhich allows you to interact with a running ResInsight instance from a Python script. \nThis allows using the powerful Python language, numerical libraries, and other support modules in conjunction with ResInsight. The Python client package is compatible with \u003cstrong\u003ePython 3\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eFor examples on how to use Python, see \u003ca href=\"/scripting/pythonexamples/\"\u003eExamples\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"octave-interface\"\u003eOctave Interface\u003c/h2\u003e\n\u003cp\u003eBy the interface to \u003ca href=\"http://www.gnu.org/software/octave/\" title=\"Octave\"\u003eOctave\u003c/a\u003e you will find:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOctave functions that communicates with a running ResInsight session\u003c/li\u003e\n\u003cli\u003eFeatures to simplify management and editing of Octave scripts from ResInsight\u003c/li\u003e\n\u003cli\u003eCommands to execute scripts using Octave.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/scripting/"
             };
         
@@ -2388,8 +2421,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/welllogsandplots/"] = {
                 title:    "Well Log Plots",
-                content:  " ResInsight can display well logs by extracting data from a simulation model along a well trajectory and from imported LAS-files. Extracted simulation data can be exported to LAS-files for further processing.\nWell Log Plots Well log plots can be created in several ways:\n Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.\nA new plot with a single Track and Curve is created matching active case and selected Well trajectory. Right-click Well Log Plots in the Plot Project Tree and select New Well Log Plot. A plot is created with one Track and Curve. Right-click Wells in the Project Tree and select Import-\u0026gt;Import Well Logs from file.  Each Well Log Plot can contain several Tracks, and each Track can contain several Curves.\nTracks and Curves can be organized using drag and drop of their entries in the Plot Project Tree. Tracks can be moved from one plot to another and you can alter the order of tracks within a Well Log Plot by drag and drop. In addition, Curves can be moved from one Track to another. Furthermore, copy and paste of a Well Log Plot, Track, and Curve is possible by right-clicking their entry.\nMeasured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL) All Tracks in the same Well Log Plot always display the same depth range, and share the True Vertical Depth (TVD) or Measured Depth (MD) setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).\nSimulation Wells however, is using a Pseudo Length instead of the real Measured Depth when the depth type is MD, as the MD information is not available in restart files. The Pseudo Length is a length along the coarsely interpolated visualization pipe, and serves only as a coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.\nDepth Unit The depth unit can be set using the Depth unit option. Currently ResInsight supports Meter and Feet. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.\nDepth Zoom and Pan The visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot. Pressing and holding CTRL while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.\nAccessing Plot Data Right-click a Well Log Plot and select Show Plot Data to show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the ascii data to a file by selecting a Well Log Plot in the Plot Project Tree and use the context command Export Plot Data to Text File.\nTracks Tracks can be created by right-clicking a Well Log Plot and select New Track.\nThe settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by Formations in Category colors.\nA track controls the x-axis range of the display which is set in the property panel. In addition to the range, logarithmic display is controlled by checking Logarithmic Scale, grid lines are controlled by the Show Grid Lines option.\nIt is also possible to visualize Well Attributes such as casing and liners. The following images show some of the possibilities in which the first track shows cross sections of a well and the second track shows a radial view labeled with formations.\nCurves Curves can be created by right-clicking a Track in the Plot Project Tree or by the commands mentioned above. The two types of curves are Well Log Extraction Curves and Well Log LAS Curves.\nWell Log Extraction Curves Extraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.\nThe property panel for an eclipse model is shown below:\nThe first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical cases and Eclipse cases. Time step can be specified for dynamic properties.\nCurve visual appearance and naming is controlled by the Appearance and Curve Name sections. The display name of a curve is normally generated automatically. Optionally, Auto Name can be switched off to use the options below to tailor curve name.\nPlacing keyboard focus in the Time Step drop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.\n\rCurve Extraction Calculation This section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.\nExtraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.\nFor Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a Directional combined results is used ( See Derived Results  ), it will be that particular face\u0026rsquo;s value.\nAbaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.\nChange Data Source for Plots and Curves It is possible to change some data source parameters in one go for either a full plot or several selected curves. To change the parameters for a whole plot use either the Data Source group in the Property Editor for the Well Log Plot or corresponding toolbar which is visible when a Well Log Plot or any of its children are selected. Changing parameters in the Data Source group for the plot will also change the source for Zonation/Formations and Well Path Attributes in addition to the data source for all Well Log Extraction Curves and Well Log LAS Curves. The source stepping icons allows to quickly step through cases, wells, and timesteps c.f. Summary Plot Source Stepping.\nTo change data source for curves, select the curves for which you wish to change source and select Change Data Source from the right-click menu. The following dialog will appear:\nIn both cases, the following parameters are available to change:\n Case \u0026ndash; Applies the selected case to all the curves. Trajectory Type \u0026ndash; Sets whether to use Simulation Wells or Well Paths as a data source for all curves. Well Name \u0026ndash; Applies this well path to all the curves. Time Step \u0026ndash; Applies this time step to all the curves.  Common for the different ways of changing data source is that if a parameter is not shared among all the curves, the drop down list will show \u0026ldquo;Mixed Cases, \u0026ldquo;Mixed Trajectory Types\u0026rdquo;, \u0026ldquo;Mixed Well Paths\u0026rdquo; or \u0026ldquo;Mixed Time Steps\u0026rdquo; to indicate that the curves have different values for that parameter. It is still possible to select a common parameter for them which will then be applied across the curves.\nWell Log RFT Curves Well Log RFT Curves shows the values in a RFT file. See RFT Plot for details about RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is Point to Point.\nWell Log LAS Curves LAS-curves shows the values in a particular channel in a LAS-file.\nThe property panel of a LAS-curve is shown below:\nYou can also create a LAS-curve by a simple drag-drop operation in the Project Tree: Drag one of the LAS channels and drop it onto a Track. A new curve will be created with the correct setting.\n\rLAS-file Support Importing LAS-files See Importing Well Log Files for details on LAS file import.\nExporting LAS-files A set of curves can be exported to LAS files by right-clicking the curves, well log track, or well log plots in Plot Project Tree and select Export To LAS Files \u0026hellip;. An export dialog is displayed, allowing the user to configure how to export curve data.\n Export Folder \u0026ndash; Location of the exported LAS files, one file per unique triplet of well path, case and time step. Resampling \u0026ndash; If enabled, all curves are resampled at the given resample interval before export. TVDRKB \u0026ndash; If enabled, TVDRKB for all curves based on the listed well paths are exported. If the difference field is blank, no TVDRKB values are exported.  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can display well logs by extracting data from a simulation model along a well trajectory and from imported LAS-files. Extracted simulation data can be exported to LAS-files for further processing.\u003c/p\u003e\n\n\u003ch2 id=\"well-log-plots\"\u003eWell Log Plots\u003c/h2\u003e\n\n\u003cp\u003eWell log plots can be created in several ways:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eRight-click a well path or a simulation well in the 3D-view and select \u003cstrong\u003eNew Well Log Extraction Curve\u003c/strong\u003e.\u003cbr /\u003e\nA new plot with a single \u003cstrong\u003eTrack\u003c/strong\u003e and \u003cstrong\u003eCurve\u003c/strong\u003e is created matching active case and selected Well trajectory.\u003c/li\u003e\n\u003cli\u003eRight-click \u003cstrong\u003eWell Log Plots\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and select \u003cstrong\u003eNew Well Log Plot\u003c/strong\u003e.\nA plot is created with one \u003cstrong\u003eTrack\u003c/strong\u003e and \u003cstrong\u003eCurve\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eRight-click \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e\nin the \u003cstrong\u003eProject Tree\u003c/strong\u003e and select \u003cstrong\u003eImport-\u0026gt;Import Well Logs from file\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eEach \u003cstrong\u003eWell Log Plot\u003c/strong\u003e can contain several \u003cem\u003eTracks\u003c/em\u003e, and each \u003cstrong\u003eTrack\u003c/strong\u003e can contain several \u003cstrong\u003eCurves\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotWindow.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTracks and Curves can be organized using \u003cstrong\u003edrag and drop\u003c/strong\u003e of their entries in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. Tracks can be moved from one plot to another and you can alter the order of tracks within a Well Log Plot by drag and drop. In addition, \u003cem\u003eCurves\u003c/em\u003e can be moved from one \u003cem\u003eTrack\u003c/em\u003e to another. Furthermore, \u003cstrong\u003ecopy and paste\u003c/strong\u003e of a \u003cem\u003eWell Log Plot\u003c/em\u003e, \u003cem\u003eTrack\u003c/em\u003e, and \u003cem\u003eCurve\u003c/em\u003e is possible by right-clicking their entry.\u003c/p\u003e\n\n\u003ch3 id=\"measured-depth-md-true-vertical-depth-tvd-and-pseudo-length-pl\"\u003eMeasured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)\u003c/h3\u003e\n\n\u003cp\u003eAll \u003cstrong\u003eTracks\u003c/strong\u003e in the same Well Log Plot always display the same depth range, and share the \u003cem\u003eTrue Vertical Depth (TVD)\u003c/em\u003e or \u003cem\u003eMeasured Depth (MD)\u003c/em\u003e setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eSimulation Wells\u003c/strong\u003e however, is using a \u003cem\u003ePseudo Length\u003c/em\u003e instead of the real \u003cem\u003eMeasured Depth\u003c/em\u003e when the depth type is MD, as the MD information is not available in restart files. The \u003cem\u003ePseudo Length\u003c/em\u003e is a length along the coarsely interpolated visualization pipe, and serves only as a coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.\u003c/p\u003e\n\n\u003ch3 id=\"depth-unit\"\u003eDepth Unit\u003c/h3\u003e\n\n\u003cp\u003eThe depth unit can be set using the \u003cstrong\u003eDepth unit\u003c/strong\u003e option. Currently ResInsight supports \u003cem\u003eMeter\u003c/em\u003e and \u003cem\u003eFeet\u003c/em\u003e. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.\u003c/p\u003e\n\n\u003ch3 id=\"depth-zoom-and-pan\"\u003eDepth Zoom and Pan\u003c/h3\u003e\n\n\u003cp\u003eThe visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot.\nPressing and holding \u003cstrong\u003eCTRL\u003c/strong\u003e while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.\u003c/p\u003e\n\n\u003ch3 id=\"accessing-plot-data\"\u003eAccessing Plot Data\u003c/h3\u003e\n\n\u003cp\u003eRight-click a Well Log Plot and select \u003cstrong\u003eShow Plot Data\u003c/strong\u003e to show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\u003c/p\u003e\n\n\u003cp\u003eIt is also possible to save the ascii data to a file by selecting a Well Log Plot in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and use the context command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"tracks\"\u003eTracks\u003c/h2\u003e\n\n\u003cp\u003eTracks can be created by right-clicking a \u003cstrong\u003eWell Log Plot\u003c/strong\u003e and select \u003cstrong\u003eNew Track\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e in \u003cem\u003eCategory colors\u003c/em\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/TrackProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA track controls the x-axis range of the display which is set in the property panel. In addition to the range, logarithmic display is controlled by checking \u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e, grid lines are controlled by the \u003cstrong\u003eShow Grid Lines\u003c/strong\u003e option.\u003c/p\u003e\n\n\u003cp\u003eIt is also possible to visualize \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Attributes\u003c/a\u003e such as casing and liners. The following images show some of the possibilities in which the first track shows cross sections of a well and the second track shows a radial view labeled with formations.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAttributeBothSides.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogTracksWidth.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"curves\"\u003eCurves\u003c/h2\u003e\n\n\u003cp\u003eCurves can be created by right-clicking a \u003cstrong\u003eTrack\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e or by the commands mentioned above.\nThe two types of curves are \u003cem\u003eWell Log Extraction Curves\u003c/em\u003e and \u003cem\u003eWell Log LAS Curves\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"well-log-extraction-curves\"\u003eWell Log Extraction Curves\u003c/h3\u003e\n\n\u003cp\u003eExtraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.\u003c/p\u003e\n\n\u003cp\u003eThe property panel for an eclipse model is shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogExtractionCurveProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical\ncases and Eclipse cases. Time step can be specified for dynamic properties.\u003c/p\u003e\n\n\u003cp\u003eCurve visual appearance and naming is controlled by the \u003cstrong\u003eAppearance\u003c/strong\u003e and \u003cstrong\u003eCurve Name\u003c/strong\u003e sections.\nThe display name of a curve is normally generated automatically. Optionally, \u003cstrong\u003eAuto Name\u003c/strong\u003e can be switched off to use the options below to tailor curve name.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003ePlacing keyboard focus in the \u003cb\u003eTime Step\u003c/b\u003e drop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"curve-extraction-calculation\"\u003eCurve Extraction Calculation\u003c/h4\u003e\n\n\u003cp\u003eThis section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.\u003c/p\u003e\n\n\u003cp\u003eExtraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.\u003c/p\u003e\n\n\u003cp\u003eFor Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a \u003cstrong\u003eDirectional combined results\u003c/strong\u003e is used ( See \u003ca href=\"/3d-main-window/derivedresults/\"\u003e Derived Results \u003c/a\u003e ), it will be that particular face\u0026rsquo;s value.\u003c/p\u003e\n\n\u003cp\u003eAbaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.\u003c/p\u003e\n\n\u003ch4 id=\"change-data-source-for-plots-and-curves\"\u003eChange Data Source for Plots and Curves\u003c/h4\u003e\n\n\u003cp\u003eIt is possible to change some data source parameters in one go for either a full plot or several selected curves. To change the parameters for a whole plot use either the \u003cstrong\u003eData Source\u003c/strong\u003e group in the Property Editor for the Well Log Plot or corresponding toolbar which is visible when a Well Log Plot or any of its children are selected. Changing parameters in the \u003cstrong\u003eData Source\u003c/strong\u003e group for the plot will also change the source for Zonation/Formations and Well Path Attributes in addition to the data source for all \u003cstrong\u003eWell Log Extraction Curves\u003c/strong\u003e and \u003cstrong\u003eWell Log LAS Curves\u003c/strong\u003e.\nThe source stepping icons \u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingIcons.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n allows to quickly step through cases, wells, and timesteps c.f.\n\u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotDataSource.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTo change data source for curves, select the curves for which you wish to change source and select \u003cstrong\u003eChange Data Source\u003c/strong\u003e from the right-click menu.\nThe following dialog will appear:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogExtractionChangeDataSource.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn both cases, the following parameters are available to change:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Applies the selected case to all the curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTrajectory Type\u003c/strong\u003e \u0026ndash; Sets whether to use Simulation Wells or Well Paths as a data source for all curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; Applies this well path to all the curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; Applies this time step to all the curves.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eCommon for the different ways of changing data source is that if a parameter is not shared among all the curves, the drop down list will show \u0026ldquo;Mixed Cases, \u0026ldquo;Mixed Trajectory Types\u0026rdquo;, \u0026ldquo;Mixed Well Paths\u0026rdquo; or \u0026ldquo;Mixed Time Steps\u0026rdquo; to indicate that the curves have different values for that parameter. It is still possible to select a common parameter for them which will then be applied across the curves.\u003c/p\u003e\n\n\u003ch3 id=\"well-log-rft-curves\"\u003eWell Log RFT Curves\u003c/h3\u003e\n\n\u003cp\u003eWell Log RFT Curves shows the values in a RFT file. See \u003ca href=\"/plot-window/rftplot/\"\u003eRFT Plot\u003c/a\u003e for details about RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is \u003cem\u003ePoint to Point\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"well-log-las-curves\"\u003eWell Log LAS Curves\u003c/h3\u003e\n\n\u003cp\u003eLAS-curves shows the values in a particular channel in a LAS-file.\u003c/p\u003e\n\n\u003cp\u003eThe property panel of a LAS-curve is shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogLasCurveProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eYou can also create a LAS-curve by a simple drag-drop operation in the \u003cb\u003eProject Tree\u003c/b\u003e: Drag one of the LAS channels and drop it onto a \u003cb\u003eTrack\u003c/b\u003e. A new curve will be created with the correct setting.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"las-file-support\"\u003eLAS-file Support\u003c/h2\u003e\n\n\u003ch3 id=\"importing-las-files\"\u003eImporting LAS-files\u003c/h3\u003e\n\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/wellpaths/#importing-well-log-files\"\u003eImporting Well Log Files\u003c/a\u003e for details on LAS file import.\u003c/p\u003e\n\n\u003ch3 id=\"exporting-las-files\"\u003eExporting LAS-files\u003c/h3\u003e\n\n\u003cp\u003eA set of curves can be exported to LAS files by right-clicking the curves, well log track, or well log plots in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and select \u003cstrong\u003eExport To LAS Files \u0026hellip;\u003c/strong\u003e. An export dialog is displayed, allowing the user to configure how to export curve data.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/export_to_las_files.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e \u0026ndash; Location of the exported LAS files, one file per unique triplet of well path, case and time step.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResampling\u003c/strong\u003e \u0026ndash; If enabled, all curves are resampled at the given resample interval before export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTVDRKB\u003c/strong\u003e \u0026ndash; If enabled, TVDRKB for all curves based on the listed well paths are exported. If the difference field is blank, no TVDRKB values are exported.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "ResInsight can display well logs by extracting data from a simulation model along a well trajectory and from imported LAS-files. Extracted simulation data can be exported to LAS-files for further processing.\nWell Log Plots Well log plots can be created in several ways:\n Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.\nA new plot with a single Track and Curve is created matching active case and selected Well trajectory. Right-click Well Log Plots in the Plot Project Tree and select New Well Log Plot. A plot is created with one Track and Curve. Right-click Wells in the Project Tree and select Import-\u0026gt;Import Well Logs from file.  Each Well Log Plot can contain several Tracks, and each Track can contain several Curves.\nTracks and Curves can be organized using drag and drop of their entries in the Plot Project Tree. Tracks can be moved from one plot to another and you can alter the order of tracks within a Well Log Plot by drag and drop. In addition, Curves can be moved from one Track to another. Furthermore, copy and paste of a Well Log Plot, Track, and Curve is possible by right-clicking their entry.\nMeasured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL) All Tracks in the same Well Log Plot always display the same depth range, and share the True Vertical Depth (TVD) or Measured Depth (MD) setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).\nSimulation Wells however, is using a Pseudo Length instead of the real Measured Depth when the depth type is MD, as the MD information is not available in restart files. The Pseudo Length is a length along the coarsely interpolated visualization pipe, and serves only as a coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.\nDepth Unit The depth unit can be set using the Depth unit option. Currently ResInsight supports Meter and Feet. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.\nDepth Zoom and Pan The visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot. Pressing and holding CTRL while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.\nAccessing Plot Data Right-click a Well Log Plot and select Show Plot Data to show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the ascii data to a file by selecting a Well Log Plot in the Plot Project Tree and use the context command Export Plot Data to Text File.\nTracks Tracks can be created by right-clicking a Well Log Plot and select New Track.\nThe settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by [Formations] (/3d-main-window/formations/) in Category colors.\nA track controls the x-axis range of the display which is set in the property panel. In addition to the range, logarithmic display is controlled by checking Logarithmic Scale, grid lines are controlled by the Show Grid Lines option.\nIt is also possible to visualize Well Attributes such as casing and liners. The following images show some of the possibilities in which the first track shows cross sections of a well and the second track shows a radial view labeled with formations.\nCurves Curves can be created by right-clicking a Track in the Plot Project Tree or by the commands mentioned above. The two types of curves are Well Log Extraction Curves and Well Log LAS Curves.\nWell Log Extraction Curves Extraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.\nThe property panel for an eclipse model is shown below:\nThe first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical cases and Eclipse cases. Time step can be specified for dynamic properties.\nCurve visual appearance and naming is controlled by the Appearance and Curve Name sections. The display name of a curve is normally generated automatically. Optionally, Auto Name can be switched off to use the options below to tailor curve name.\nPlacing keyboard focus in the Time Stepdrop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.\n\rCurve Extraction Calculation This section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.\nExtraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.\nFor Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a Directional combined results is used ( See Derived Results  ), it will be that particular face\u0026rsquo;s value.\nAbaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.\nChange Data Source for Plots and Curves It is possible to change some data source parameters in one go for either a full plot or several selected curves. To change the parameters for a whole plot use either the Data Source group in the Property Editor for the Well Log Plot or corresponding toolbar which is visible when a Well Log Plot or any of its children are selected. Changing parameters in the Data Source group for the plot will also change the source for Zonation/Formations and Well Path Attributes in addition to the data source for all Well Log Extraction Curves and Well Log LAS Curves. The source stepping icons allows to quickly step through cases, wells, and timesteps c.f. Summary Plot Source Stepping.\nTo change data source for curves, select the curves for which you wish to change source and select Change Data Source from the right-click menu. The following dialog will appear:\nIn both cases, the following parameters are available to change:\n Case \u0026ndash; Applies the selected case to all the curves. Trajectory Type \u0026ndash; Sets whether to use Simulation Wells or Well Paths as a data source for all curves. Well Name \u0026ndash; Applies this well path to all the curves. Time Step \u0026ndash; Applies this time step to all the curves.  Common for the different ways of changing data source is that if a parameter is not shared among all the curves, the drop down list will show \u0026ldquo;Mixed Cases, \u0026ldquo;Mixed Trajectory Types\u0026rdquo;, \u0026ldquo;Mixed Well Paths\u0026rdquo; or \u0026ldquo;Mixed Time Steps\u0026rdquo; to indicate that the curves have different values for that parameter. It is still possible to select a common parameter for them which will then be applied across the curves.\nWell Log RFT Curves Well Log RFT Curves shows the values in a RFT file. See RFT Plot for details about RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is Point to Point.\nWell Log LAS Curves LAS-curves shows the values in a particular channel in a LAS-file.\nThe property panel of a LAS-curve is shown below:\nYou can also create a LAS-curve by a simple drag-drop operation in the Project Tree: Drag one of the LAS channels and drop it onto a Track. A new curve will be created with the correct setting.\n\rLAS-file Support Importing LAS-files See Importing Well Log Files for details on LAS file import.\nExporting LAS-files A set of curves can be exported to LAS files by right-clicking the curves, well log track, or well log plots in Plot Project Tree and select Export To LAS Files \u0026hellip;. An export dialog is displayed, allowing the user to configure how to export curve data.\n Export Folder \u0026ndash; Location of the exported LAS files, one file per unique triplet of well path, case and time step. Resampling \u0026ndash; If enabled, all curves are resampled at the given resample interval before export. TVDRKB \u0026ndash; If enabled, TVDRKB for all curves based on the listed well paths are exported. If the difference field is blank, no TVDRKB values are exported.  ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can display well logs by extracting data from a simulation model along a well trajectory and from imported LAS-files. Extracted simulation data can be exported to LAS-files for further processing.\u003c/p\u003e\n\u003ch2 id=\"well-log-plots\"\u003eWell Log Plots\u003c/h2\u003e\n\u003cp\u003eWell log plots can be created in several ways:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eRight-click a well path or a simulation well in the 3D-view and select \u003cstrong\u003eNew Well Log Extraction Curve\u003c/strong\u003e.\u003cbr\u003e\nA new plot with a single \u003cstrong\u003eTrack\u003c/strong\u003e and \u003cstrong\u003eCurve\u003c/strong\u003e is created matching active case and selected Well trajectory.\u003c/li\u003e\n\u003cli\u003eRight-click \u003cstrong\u003eWell Log Plots\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and select \u003cstrong\u003eNew Well Log Plot\u003c/strong\u003e. \nA plot is created with one \u003cstrong\u003eTrack\u003c/strong\u003e and \u003cstrong\u003eCurve\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eRight-click \u003cimg src=\"https://resinsight.org/images/3d-main-window/WellCollection.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eWells\u003c/strong\u003e\nin the \u003cstrong\u003eProject Tree\u003c/strong\u003e and select \u003cstrong\u003eImport-\u0026gt;Import Well Logs from file\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eEach \u003cstrong\u003eWell Log Plot\u003c/strong\u003e can contain several \u003cem\u003eTracks\u003c/em\u003e, and each \u003cstrong\u003eTrack\u003c/strong\u003e can contain several \u003cstrong\u003eCurves\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotWindow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTracks and Curves can be organized using \u003cstrong\u003edrag and drop\u003c/strong\u003e of their entries in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. Tracks can be moved from one plot to another and you can alter the order of tracks within a Well Log Plot by drag and drop. In addition, \u003cem\u003eCurves\u003c/em\u003e can be moved from one \u003cem\u003eTrack\u003c/em\u003e to another. Furthermore, \u003cstrong\u003ecopy and paste\u003c/strong\u003e of a \u003cem\u003eWell Log Plot\u003c/em\u003e, \u003cem\u003eTrack\u003c/em\u003e, and \u003cem\u003eCurve\u003c/em\u003e is possible by right-clicking their entry.\u003c/p\u003e\n\u003ch3 id=\"measured-depth-md-true-vertical-depth-tvd-and-pseudo-length-pl\"\u003eMeasured Depth (MD), True Vertical Depth (TVD) and Pseudo Length (PL)\u003c/h3\u003e\n\u003cp\u003eAll \u003cstrong\u003eTracks\u003c/strong\u003e in the same Well Log Plot always display the same depth range, and share the \u003cem\u003eTrue Vertical Depth (TVD)\u003c/em\u003e or \u003cem\u003eMeasured Depth (MD)\u003c/em\u003e setting. In the property panel of the plot, the exact depth range can be adjusted along with the depth type setting (TVD/MD).\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSimulation Wells\u003c/strong\u003e however, is using a \u003cem\u003ePseudo Length\u003c/em\u003e instead of the real \u003cem\u003eMeasured Depth\u003c/em\u003e when the depth type is MD, as the MD information is not available in restart files. The \u003cem\u003ePseudo Length\u003c/em\u003e is a length along the coarsely interpolated visualization pipe, and serves only as a coarse estimation of an MD-like depth. Pseudo length is measured from the simulation-wells first connection-cell (well head connection) to the reservoir. This is very different from MD, which would start at RKB or at sea level.\u003c/p\u003e\n\u003ch3 id=\"depth-unit\"\u003eDepth Unit\u003c/h3\u003e\n\u003cp\u003eThe depth unit can be set using the \u003cstrong\u003eDepth unit\u003c/strong\u003e option. Currently ResInsight supports \u003cem\u003eMeter\u003c/em\u003e and \u003cem\u003eFeet\u003c/em\u003e. The first curve added to a plot will set the plot unit based on the curve unit. Additional curves added to a plot will be converted to the plot unit if needed.\u003c/p\u003e\n\u003ch3 id=\"depth-zoom-and-pan\"\u003eDepth Zoom and Pan\u003c/h3\u003e\n\u003cp\u003eThe visible depth range can be panned using the mouse wheel while the mouse pointer hovers over the plot.\nPressing and holding \u003cstrong\u003eCTRL\u003c/strong\u003e while using the mouse wheel will allow you to zoom in or out depth-wise, towards the mouse position.\u003c/p\u003e\n\u003ch3 id=\"accessing-plot-data\"\u003eAccessing Plot Data\u003c/h3\u003e\n\u003cp\u003eRight-click a Well Log Plot and select \u003cstrong\u003eShow Plot Data\u003c/strong\u003e to show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\u003c/p\u003e\n\u003cp\u003eIt is also possible to save the ascii data to a file by selecting a Well Log Plot in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and use the context command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"tracks\"\u003eTracks\u003c/h2\u003e\n\u003cp\u003eTracks can be created by right-clicking a \u003cstrong\u003eWell Log Plot\u003c/strong\u003e and select \u003cstrong\u003eNew Track\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe settings of each Track is controlled by the Property Editor. The figure below shows settings for the middle Track shown in the figure at top of this page which is annotated by [Formations] (/3d-main-window/formations/) in \u003cem\u003eCategory colors\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/TrackProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA track controls the x-axis range of the display which is set in the property panel. In addition to the range, logarithmic display is controlled by checking \u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e, grid lines are controlled by the \u003cstrong\u003eShow Grid Lines\u003c/strong\u003e option.\u003c/p\u003e\n\u003cp\u003eIt is also possible to visualize \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Attributes\u003c/a\u003e such as casing and liners. The following images show some of the possibilities in which the first track shows cross sections of a well and the second track shows a radial view labeled with formations.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAttributeBothSides.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogTracksWidth.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"curves\"\u003eCurves\u003c/h2\u003e\n\u003cp\u003eCurves can be created by right-clicking a \u003cstrong\u003eTrack\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e or by the commands mentioned above.\nThe two types of curves are \u003cem\u003eWell Log Extraction Curves\u003c/em\u003e and \u003cem\u003eWell Log LAS Curves\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"well-log-extraction-curves\"\u003eWell Log Extraction Curves\u003c/h3\u003e\n\u003cp\u003eExtraction curves acts as an artificial well log curves. Instead of probing the real well, a simulation model is probed instead.\u003c/p\u003e\n\u003cp\u003eThe property panel for an eclipse model is shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogExtractionCurveProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe first group of options controls all the input needed to setup curve data extraction. The selection of result value is somewhat different between geomechanical \ncases and Eclipse cases. Time step can be specified for dynamic properties.\u003c/p\u003e\n\u003cp\u003eCurve visual appearance and naming is controlled by the \u003cstrong\u003eAppearance\u003c/strong\u003e and \u003cstrong\u003eCurve Name\u003c/strong\u003e sections. \nThe display name of a curve is normally generated automatically. Optionally, \u003cstrong\u003eAuto Name\u003c/strong\u003e can be switched off to use the options below to tailor curve name.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003ePlacing keyboard focus in the \u003c!-- raw HTML omitted --\u003eTime Step\u003c!-- raw HTML omitted --\u003e drop-down box allows you to use arrow keys or mouse wheel to quickly step through the timesteps while watching the changes in the curve.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"curve-extraction-calculation\"\u003eCurve Extraction Calculation\u003c/h4\u003e\n\u003cp\u003eThis section describes how the values are extracted from the grid when creating a Well Log Extraction Curve.\u003c/p\u003e\n\u003cp\u003eExtraction curves are calculated by finding the intersections between a well trajectory and the cell-faces in a particular grid model. Usually there are two intersections at nearly the same spot; the one leaving the previous cell, and the one entering the next one. At each intersection point the measured depth along the trajectory is interpolated from the trajectory data. The result value is retrieved from the corresponding cell in different ways depending on the nature of the underlying result.\u003c/p\u003e\n\u003cp\u003eFor Eclipse results the cell face value is used directly. This is normally the same as the corresponding cell value, but if a \u003cstrong\u003eDirectional combined results\u003c/strong\u003e is used ( See \u003ca href=\"/3d-main-window/derivedresults/\"\u003e Derived Results \u003c/a\u003e ), it will be that particular face\u0026rsquo;s value.\u003c/p\u003e\n\u003cp\u003eAbaqus results are interpolated across the intersected cell-face from the result values associated with the nodes of that face. This is also the case for integration point results, as they are directly associated with their corresponding element node in ResInsight.\u003c/p\u003e\n\u003ch4 id=\"change-data-source-for-plots-and-curves\"\u003eChange Data Source for Plots and Curves\u003c/h4\u003e\n\u003cp\u003eIt is possible to change some data source parameters in one go for either a full plot or several selected curves. To change the parameters for a whole plot use either the \u003cstrong\u003eData Source\u003c/strong\u003e group in the Property Editor for the Well Log Plot or corresponding toolbar which is visible when a Well Log Plot or any of its children are selected. Changing parameters in the \u003cstrong\u003eData Source\u003c/strong\u003e group for the plot will also change the source for Zonation/Formations and Well Path Attributes in addition to the data source for all \u003cstrong\u003eWell Log Extraction Curves\u003c/strong\u003e and \u003cstrong\u003eWell Log LAS Curves\u003c/strong\u003e.\nThe source stepping icons \u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingIcons.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n allows to quickly step through cases, wells, and timesteps c.f. \n\u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogPlotDataSource.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo change data source for curves, select the curves for which you wish to change source and select \u003cstrong\u003eChange Data Source\u003c/strong\u003e from the right-click menu. \nThe following dialog will appear:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogExtractionChangeDataSource.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn both cases, the following parameters are available to change:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Applies the selected case to all the curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTrajectory Type\u003c/strong\u003e \u0026ndash; Sets whether to use Simulation Wells or Well Paths as a data source for all curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; Applies this well path to all the curves.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; Applies this time step to all the curves.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eCommon for the different ways of changing data source is that if a parameter is not shared among all the curves, the drop down list will show \u0026ldquo;Mixed Cases, \u0026ldquo;Mixed Trajectory Types\u0026rdquo;, \u0026ldquo;Mixed Well Paths\u0026rdquo; or \u0026ldquo;Mixed Time Steps\u0026rdquo; to indicate that the curves have different values for that parameter. It is still possible to select a common parameter for them which will then be applied across the curves.\u003c/p\u003e\n\u003ch3 id=\"well-log-rft-curves\"\u003eWell Log RFT Curves\u003c/h3\u003e\n\u003cp\u003eWell Log RFT Curves shows the values in a RFT file. See \u003ca href=\"/plot-window/rftplot/\"\u003eRFT Plot\u003c/a\u003e for details about RFT. A curve in a RFT plot will look identical to a RFT curve in a well log plot, if the depth type of the well log plot is TVD, and the interpolation type of the curve is \u003cem\u003ePoint to Point\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"well-log-las-curves\"\u003eWell Log LAS Curves\u003c/h3\u003e\n\u003cp\u003eLAS-curves shows the values in a particular channel in a LAS-file.\u003c/p\u003e\n\u003cp\u003eThe property panel of a LAS-curve is shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellLogLasCurveProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eYou can also create a LAS-curve by a simple drag-drop operation in the \u003c!-- raw HTML omitted --\u003eProject Tree\u003c!-- raw HTML omitted --\u003e: Drag one of the LAS channels and drop it onto a \u003c!-- raw HTML omitted --\u003eTrack\u003c!-- raw HTML omitted --\u003e. A new curve will be created with the correct setting.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"las-file-support\"\u003eLAS-file Support\u003c/h2\u003e\n\u003ch3 id=\"importing-las-files\"\u003eImporting LAS-files\u003c/h3\u003e\n\u003cp\u003eSee \u003ca href=\"/wells-and-completions/wellpaths/#importing-well-log-files\"\u003eImporting Well Log Files\u003c/a\u003e for details on LAS file import.\u003c/p\u003e\n\u003ch3 id=\"exporting-las-files\"\u003eExporting LAS-files\u003c/h3\u003e\n\u003cp\u003eA set of curves can be exported to LAS files by right-clicking the curves, well log track, or well log plots in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and select \u003cstrong\u003eExport To LAS Files \u0026hellip;\u003c/strong\u003e. An export dialog is displayed, allowing the user to configure how to export curve data.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/export_to_las_files.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eExport Folder\u003c/strong\u003e \u0026ndash; Location of the exported LAS files, one file per unique triplet of well path, case and time step.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResampling\u003c/strong\u003e \u0026ndash; If enabled, all curves are resampled at the given resample interval before export.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTVDRKB\u003c/strong\u003e \u0026ndash; If enabled, TVDRKB for all curves based on the listed well paths are exported. If the difference field is blank, no TVDRKB values are exported.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/welllogsandplots/"
             };
         
@@ -2397,8 +2430,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/intersections/"] = {
                 title:    "Intersections",
-                content:  " Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.\nThere are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate 2D Intersection View\nThe second intersection type is called an Intersection Box. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.\nAll types of intersections are stored in a folder named Intersections in a View as shown below. Once created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.\nOnce created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.\nCurve Based Intersections There are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane\u0026rsquo;s extrusion direction can be defined by the two angles.\nAny of these intersections can be created by activating New Intersection from the right-click menu of the Intersections item in the Project Tree.\nThey can also be created from the right-click menu in the 3D view, as described below.\nTo be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the Grids item in the Project Tree or activating the Hide Grid Cells toolbar button.\n\rCommon Curve Based Intersection Options The property panel of a well path based intersection is shown below:\n Name \u0026ndash; Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path. Intersecting Geometry \u0026ndash; These options controls the curve to be used for the cross section, and depends on the type of intersection you choose. Direction \u0026ndash; Horizontal, vertical or defined by two points. Extent Length \u0026ndash; Defines how far an intersection for well path or simulation Well is extended at intersection ends. Show Inactive Cells \u0026ndash; Controls if inactive cells are included when creating the intersection geometry.  Direction The direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.\nWhen selection the Horizontal option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\nWhen Defined by two points is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  Well Path Intersection A new Well Path intersection can be created by right-clicking the well path in the 3D view or in the Project Tree.\nWhen a well path intersection is created, the source well path can be changed by using the Well Path selection combo box in the Property Editor.\nSimulation Well Intersection A new Simulation Well intersection can be created by right-clicking the simulation well in the 3D view or in the Project Tree.\nWhen a simulation well intersection is created, the source simulation well can be changed by using the Simulation Well selection combo box in the Property Editor.\nIf the well contains more than one branch, the intersection geometry will be created for the selected branch in the Branch combo box.\nPolyline Intersection A new Polyline intersection can be created from the right-click menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the Property Editor.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using CTRL-V.\nAzimuth and Dip A new Azimuth and Dip intersection can be created from the right-click menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the Property Editor.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using CTRL-V.\nWhen two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees Dip, and the Azimuth angle calculated from the two points. The two angles can be edited in the Property Editor of the intersection, and is defined by the following:\n Dip is the angle between the horizontal plane and down. Azimuth is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.  The length of the plane can also be set manually in the Property Editor.\n Length Up is the distance from the user defined horizontal line, to the top of the plane intersecting the model. Length Down is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.  2D Intersection Views A 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.\nEach of the curve based intersections have a corresponding 2D Intersection View. Management of these views are automatic. They will be created and deleted along with the intersection.\nThe view can be shown either by right clicking the intersection and select the command Show 2D intersection View, or by toggling the view in the project tree directly.\nScales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.\nThe view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.\n Viewer  Name \u0026ndash; User editable name of the view. The default name is set by combining the name of the origin view and the intersection name. Background \u0026ndash; Color of the viewer background Disable Results Lighting \u0026ndash; Toggle the light effect. When the lighting is turned off, the colors are easier to compare with the legend, but the colors carry no visual cue to visualize the 3D shape. The effect is tiny on 2D Intersection Views.  Grid Appearance \u0026ndash; Controls the drawstyle of the grid geometry  Z Scale \u0026ndash; Scales the view in Z(depth) direction to make slim K-layers easier to see Grid Lines \u0026ndash; Controls what mesh lines to draw All \u0026ndash; All mesh lines are drawn Faults Only \u0026ndash; Only mesh lines associated with faults are drawn None \u0026ndash; Mesh lines are not drawn at all Grid Surface \u0026ndash; Controls what grid surface geometry to draw All \u0026ndash; All grid faces are drawn Faults Only \u0026ndash; Only faces that are included in a fault is drawn None \u0026ndash; Do not draw any faces  Defining Points  Show points \u0026ndash; Toggle the display of the defining points for Polyline or Azimuth and Dip intersections.   These options are similar to the options for a regular 3D view (See View Properties )\nIntersection Box and Intersection Planes A new Intersection Box or Intersection Plane can be created from the right-click menu in the 3D view or the right-click menu in the Project Tree.\nThe following list describes the properties for an Intersection Box:\n Name \u0026ndash; Automatically created based on the item specifying the intersection Box Type \u0026ndash; Box or x-plane, y-plane or z-plane Show Inactive Cells \u0026ndash; Controls if inactive cells are included when creating the intersection geometry X Coordinates \u0026ndash; Coordinates for x range Y Coordinates \u0026ndash; Coordinates for y range Depth \u0026ndash; Coordinates for depth range XY Slider Step Size \u0026ndash; Defines how much the value changes when the slider for XY values is changed, default value 1.0 Depth Slider Step Size \u0026ndash; Defines how much the value changes when the slider for depth values is changed, default value 0.5  Direct interaction in a 3D view is activated when Show 3D manipulator is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIntersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.\u003c/p\u003e\n\n\u003cp\u003eThere are two main types of intersections. The first one which simply is called \u003cstrong\u003eIntersection\u003c/strong\u003e, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate \u003ca href=\"/3d-main-window/intersections/#2d-intersection-views\"\u003e2D Intersection View\u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003eThe second intersection type is called an \u003cstrong\u003eIntersection Box\u003c/strong\u003e. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.\u003c/p\u003e\n\n\u003cp\u003eAll types of intersections are stored in a folder named \u003cstrong\u003eIntersections\u003c/strong\u003e in a \u003cstrong\u003eView\u003c/strong\u003e as shown below. Once created, the intersections may be copied to other views by selecting the \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e option from the right-click menu of each intersection.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionInTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eOnce created, the intersections may be copied to other views by selecting the \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e option from the right-click menu of each intersection.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionInTreeCopy.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"curve-based-intersections\"\u003eCurve Based \u003cstrong\u003eIntersections\u003c/strong\u003e\u003c/h2\u003e\n\n\u003cp\u003eThere are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane\u0026rsquo;s extrusion direction can be defined by the two angles.\u003c/p\u003e\n\n\u003cp\u003eAny of these intersections can be created by activating \u003cimg src=\"https://resinsight.org/images/3d-main-window/CrossSection16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Intersection\u003c/strong\u003e from the right-click menu of the \u003cstrong\u003eIntersections\u003c/strong\u003e item in the Project Tree.\u003c/p\u003e\n\n\u003cp\u003eThey can also be created from the right-click menu in the 3D view, as described below.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eTo be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the \u003cb\u003eGrids\u003c/b\u003e item in the Project Tree or activating the \u003cb\u003eHide Grid Cells\u003c/b\u003e toolbar button.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"common-curve-based-intersection-options\"\u003eCommon Curve Based Intersection Options\u003c/h3\u003e\n\n\u003cp\u003eThe property panel of a well path based intersection is shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionWellPath.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntersecting Geometry\u003c/strong\u003e \u0026ndash; These options controls the curve to be used for the cross section, and depends on the type of intersection you choose.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDirection\u003c/strong\u003e \u0026ndash; Horizontal, vertical or defined by two points.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExtent Length\u003c/strong\u003e \u0026ndash; Defines how far an intersection for well path or simulation Well is extended at intersection ends.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Inactive Cells\u003c/strong\u003e \u0026ndash; Controls if inactive cells are included when creating the intersection geometry.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"direction\"\u003eDirection\u003c/h4\u003e\n\n\u003cp\u003eThe direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.\u003c/p\u003e\n\n\u003cp\u003eWhen selection the \u003cstrong\u003eHorizontal\u003c/strong\u003e option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\u003c/p\u003e\n\n\u003cp\u003eWhen \u003cstrong\u003eDefined by two points\u003c/strong\u003e is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"well-path-intersection\"\u003eWell Path Intersection\u003c/h3\u003e\n\n\u003cp\u003eA new \u003cstrong\u003eWell Path\u003c/strong\u003e intersection can be created by right-clicking the well path in the 3D view or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionWellPath.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen a well path intersection is created, the source well path can be changed by using the \u003cstrong\u003eWell Path\u003c/strong\u003e selection combo box in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"simulation-well-intersection\"\u003eSimulation Well Intersection\u003c/h3\u003e\n\n\u003cp\u003eA new \u003cstrong\u003eSimulation Well\u003c/strong\u003e intersection can be created by right-clicking the simulation well in the 3D view or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionSimulationWellProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen a simulation well intersection is created, the source simulation well can be changed by using the \u003cstrong\u003eSimulation Well\u003c/strong\u003e selection combo box in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf the well contains more than one branch, the intersection geometry will be created for the selected branch in the \u003cstrong\u003eBranch\u003c/strong\u003e combo box.\u003c/p\u003e\n\n\u003ch3 id=\"polyline-intersection\"\u003ePolyline Intersection\u003c/h3\u003e\n\n\u003cp\u003eA new \u003cstrong\u003ePolyline\u003c/strong\u003e intersection can be created from the right-click menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPolyline.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\n\u003cp\u003eThe points in the list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using \u003cstrong\u003eCTRL-V\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"azimuth-and-dip\"\u003eAzimuth and Dip\u003c/h3\u003e\n\n\u003cp\u003eA new \u003cstrong\u003eAzimuth and Dip\u003c/strong\u003e intersection can be created from the right-click menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionAzimuthDip.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\n\u003cp\u003eThe points in the list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using \u003cstrong\u003eCTRL-V\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eWhen two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees \u003cstrong\u003eDip\u003c/strong\u003e, and the \u003cstrong\u003eAzimuth\u003c/strong\u003e angle calculated from the two points. The two angles can be edited in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the intersection, and is defined by the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e is the angle between the horizontal plane and down.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe length of the plane can also be set manually in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLength Up\u003c/strong\u003e is the distance from the user defined horizontal line, to the top of the plane intersecting the model.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength Down\u003c/strong\u003e is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/azimuthDip3DView.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"2d-intersection-views\"\u003e2D Intersection Views\u003c/h3\u003e\n\n\u003cp\u003eA 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionView.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEach of the curve based intersections have a corresponding \u003cstrong\u003e2D Intersection View\u003c/strong\u003e. Management of these views are automatic. They will be created and deleted along with the intersection.\u003c/p\u003e\n\n\u003cp\u003eThe view can be shown either by right clicking the intersection and select the command \u003cstrong\u003eShow 2D intersection View\u003c/strong\u003e, or by toggling the view in the project tree directly.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionViewsProjectTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eScales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.\u003c/p\u003e\n\n\u003cp\u003eThe view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/2DIntersectionViewProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User editable name of the view. The default name is set by combining the name of the origin view and the intersection name.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBackground\u003c/strong\u003e \u0026ndash; Color of the viewer background\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDisable Results Lighting\u003c/strong\u003e \u0026ndash; Toggle the light effect. When the lighting is turned off, the colors are easier to compare with the legend, but the colors carry no visual cue to visualize the 3D shape. The effect is tiny on 2D Intersection Views.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Appearance\u003c/strong\u003e \u0026ndash; Controls the drawstyle of the grid geometry\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eZ Scale\u003c/strong\u003e \u0026ndash; Scales the view in Z(depth) direction to make slim K-layers easier to see\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Lines\u003c/strong\u003e \u0026ndash; Controls what mesh lines to draw\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll\u003c/strong\u003e \u0026ndash; All mesh lines are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFaults Only\u003c/strong\u003e \u0026ndash; Only mesh lines associated with faults are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e \u0026ndash; Mesh lines are not drawn at all\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Surface\u003c/strong\u003e \u0026ndash; Controls what grid surface geometry to draw\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll\u003c/strong\u003e \u0026ndash; All grid faces are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFaults Only\u003c/strong\u003e \u0026ndash; Only faces that are included in a fault is drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e \u0026ndash; Do not draw any faces\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefining Points\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow points\u003c/strong\u003e \u0026ndash; Toggle the display of the defining points for Polyline or Azimuth and Dip intersections.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThese options are similar to the options for a regular 3D view (See \u003ca href=\"/3d-main-window/3dviews/#view-properties\"\u003eView Properties\u003c/a\u003e )\u003c/p\u003e\n\n\u003ch2 id=\"intersection-box-and-intersection-planes\"\u003eIntersection Box and Intersection Planes\u003c/h2\u003e\n\n\u003cp\u003eA new \u003cstrong\u003eIntersection Box\u003c/strong\u003e or \u003cstrong\u003eIntersection Plane\u003c/strong\u003e can be created from the right-click menu in the 3D view or the right-click menu in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3d_view_context_menu.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe following list describes the properties for an \u003cstrong\u003eIntersection Box\u003c/strong\u003e:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Automatically created based on the item specifying the intersection\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBox Type\u003c/strong\u003e \u0026ndash; Box or x-plane, y-plane or z-plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Inactive Cells\u003c/strong\u003e \u0026ndash; Controls if inactive cells are included when creating the intersection geometry\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eX Coordinates\u003c/strong\u003e \u0026ndash; Coordinates for x range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eY Coordinates\u003c/strong\u003e \u0026ndash; Coordinates for y range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth\u003c/strong\u003e \u0026ndash; Coordinates for depth range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXY Slider Step Size\u003c/strong\u003e \u0026ndash; Defines how much the value changes when the slider for XY values is changed, default value 1.0\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slider Step Size\u003c/strong\u003e \u0026ndash; Defines how much the value changes when the slider for depth values is changed, default value 0.5\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eDirect interaction in a 3D view is activated when \u003cstrong\u003eShow 3D manipulator\u003c/strong\u003e is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionBoxWithHandles.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "Intersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.\nThere are two main types of intersections. The first one which simply is called Intersection, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate 2D Intersection View\nThe second intersection type is called an Intersection Box. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.\nAll types of intersections are stored in a folder named Intersections in a View as shown below. Once created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.\nOnce created, the intersections may be copied to other views by selecting the Copy intersections to all views in case option from the right-click menu of each intersection.\nCurve Based Intersections There are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane\u0026rsquo;s extrusion direction can be defined by the two angles.\nAny of these intersections can be created by activating New Intersection from the right-click menu of the Intersections item in the Project Tree.\nThey can also be created from the right-click menu in the 3D view, as described below.\nTo be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the Gridsitem in the Project Tree or activating the Hide Grid Cellstoolbar button.\n\rCommon Curve Based Intersection Options The property panel of a well path based intersection is shown below:\n Name \u0026ndash; Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path. Intersecting Geometry \u0026ndash; These options controls the curve to be used for the cross section, and depends on the type of intersection you choose. Direction \u0026ndash; Horizontal, vertical or defined by two points. Extent Length \u0026ndash; Defines how far an intersection for well path or simulation Well is extended at intersection ends. Show Inactive Cells \u0026ndash; Controls if inactive cells are included when creating the intersection geometry.  Direction The direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.\nWhen selection the Horizontal option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\nWhen Defined by two points is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  Well Path Intersection A new Well Path intersection can be created by right-clicking the well path in the 3D view or in the Project Tree.\nWhen a well path intersection is created, the source well path can be changed by using the Well Path selection combo box in the Property Editor.\nSimulation Well Intersection A new Simulation Well intersection can be created by right-clicking the simulation well in the 3D view or in the Project Tree.\nWhen a simulation well intersection is created, the source simulation well can be changed by using the Simulation Well selection combo box in the Property Editor.\nIf the well contains more than one branch, the intersection geometry will be created for the selected branch in the Branch combo box.\nPolyline Intersection A new Polyline intersection can be created from the right-click menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the Property Editor.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using CTRL-V.\nAzimuth and Dip A new Azimuth and Dip intersection can be created from the right-click menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the Property Editor.\n The background color of this list is set to light pink when adding points by picking in the 3D view is active. To finish adding points, click the button Stop picking points in the Property Editor. The background color of the point list is then set to white.  The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using CTRL-V.\nWhen two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees Dip, and the Azimuth angle calculated from the two points. The two angles can be edited in the Property Editor of the intersection, and is defined by the following:\n Dip is the angle between the horizontal plane and down. Azimuth is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.  The length of the plane can also be set manually in the Property Editor.\n Length Up is the distance from the user defined horizontal line, to the top of the plane intersecting the model. Length Down is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.  2D Intersection Views A 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.\nEach of the curve based intersections have a corresponding 2D Intersection View. Management of these views are automatic. They will be created and deleted along with the intersection.\nThe view can be shown either by right clicking the intersection and select the command Show 2D intersection View, or by toggling the view in the project tree directly.\nScales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.\nThe view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.\n Viewer  Name \u0026ndash; User editable name of the view. The default name is set by combining the name of the origin view and the intersection name. Background \u0026ndash; Color of the viewer background Disable Results Lighting \u0026ndash; Toggle the light effect. When the lighting is turned off, the colors are easier to compare with the legend, but the colors carry no visual cue to visualize the 3D shape. The effect is tiny on 2D Intersection Views.   Grid Appearance \u0026ndash; Controls the drawstyle of the grid geometry  Z Scale \u0026ndash; Scales the view in Z(depth) direction to make slim K-layers easier to see Grid Lines \u0026ndash; Controls what mesh lines to draw  All \u0026ndash; All mesh lines are drawn Faults Only \u0026ndash; Only mesh lines associated with faults are drawn None \u0026ndash; Mesh lines are not drawn at all   Grid Surface \u0026ndash; Controls what grid surface geometry to draw  All \u0026ndash; All grid faces are drawn Faults Only \u0026ndash; Only faces that are included in a fault is drawn None \u0026ndash; Do not draw any faces     Defining Points  Show points \u0026ndash; Toggle the display of the defining points for Polyline or Azimuth and Dip intersections.    These options are similar to the options for a regular 3D view (See View Properties )\nIntersection Box and Intersection Planes A new Intersection Box or Intersection Plane can be created from the right-click menu in the 3D view or the right-click menu in the Project Tree.\nThe following list describes the properties for an Intersection Box:\n Name \u0026ndash; Automatically created based on the item specifying the intersection Box Type \u0026ndash; Box or x-plane, y-plane or z-plane Show Inactive Cells \u0026ndash; Controls if inactive cells are included when creating the intersection geometry X Coordinates \u0026ndash; Coordinates for x range Y Coordinates \u0026ndash; Coordinates for y range Depth \u0026ndash; Coordinates for depth range XY Slider Step Size \u0026ndash; Defines how much the value changes when the slider for XY values is changed, default value 1.0 Depth Slider Step Size \u0026ndash; Defines how much the value changes when the slider for depth values is changed, default value 0.5  Direct interaction in a 3D view is activated when Show 3D manipulator is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIntersections are cross sections of the grid model that displays the grid cell values on planes that cut through the grid in various ways.\u003c/p\u003e\n\u003cp\u003eThere are two main types of intersections. The first one which simply is called \u003cstrong\u003eIntersection\u003c/strong\u003e, is defined by a piece-wise linear curve and an extrusion direction. The curve can be either a Simulation Well, a Well Path, a user defined polyline, or a user defined line. These intersections can also be shown in their own separate \u003ca href=\"/3d-main-window/intersections/#2d-intersection-views\"\u003e2D Intersection View\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe second intersection type is called an \u003cstrong\u003eIntersection Box\u003c/strong\u003e. An Intersection Box can be used as a box cutting the grid cells, or collapsed to a restricted axis aligned plane.\u003c/p\u003e\n\u003cp\u003eAll types of intersections are stored in a folder named \u003cstrong\u003eIntersections\u003c/strong\u003e in a \u003cstrong\u003eView\u003c/strong\u003e as shown below. Once created, the intersections may be copied to other views by selecting the \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e option from the right-click menu of each intersection.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionInTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eOnce created, the intersections may be copied to other views by selecting the \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e option from the right-click menu of each intersection.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionInTreeCopy.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"curve-based-intersections\"\u003eCurve Based \u003cstrong\u003eIntersections\u003c/strong\u003e\u003c/h2\u003e\n\u003cp\u003eThere are four types of curve based intersections: Well Path, Simulation Well, Polyline, and Azimuth and Dip. Azimuth and Dip differs from the other three curves, as it is defined just by one straight line. It is called Azimuth and Dip because the plane\u0026rsquo;s extrusion direction can be defined by the two angles.\u003c/p\u003e\n\u003cp\u003eAny of these intersections can be created by activating \u003cimg src=\"https://resinsight.org/images/3d-main-window/CrossSection16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eNew Intersection\u003c/strong\u003e from the right-click menu of the \u003cstrong\u003eIntersections\u003c/strong\u003e item in the Project Tree.\u003c/p\u003e\n\u003cp\u003eThey can also be created from the right-click menu in the 3D view, as described below.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eTo be able to see the intersections in the 3D view, the grid cells can be hidden by disabling the \u003c!-- raw HTML omitted --\u003eGrids\u003c!-- raw HTML omitted --\u003e item in the Project Tree or activating the \u003c!-- raw HTML omitted --\u003eHide Grid Cells\u003c!-- raw HTML omitted --\u003e toolbar button.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"common-curve-based-intersection-options\"\u003eCommon Curve Based Intersection Options\u003c/h3\u003e\n\u003cp\u003eThe property panel of a well path based intersection is shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionWellPath.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Automatically created based on the item specifying the intersection. The user can customize the name by editing, but will be updated if you change the well or well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntersecting Geometry\u003c/strong\u003e \u0026ndash; These options controls the curve to be used for the cross section, and depends on the type of intersection you choose.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDirection\u003c/strong\u003e \u0026ndash; Horizontal, vertical or defined by two points.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExtent Length\u003c/strong\u003e \u0026ndash; Defines how far an intersection for well path or simulation Well is extended at intersection ends.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Inactive Cells\u003c/strong\u003e \u0026ndash; Controls if inactive cells are included when creating the intersection geometry.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"direction\"\u003eDirection\u003c/h4\u003e\n\u003cp\u003eThe direction defined is used to extrude the curve in the defined direction, and thereby create a set of planes.\u003c/p\u003e\n\u003cp\u003eWhen selection the \u003cstrong\u003eHorizontal\u003c/strong\u003e option, the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\u003c/p\u003e\n\u003cp\u003eWhen \u003cstrong\u003eDefined by two points\u003c/strong\u003e is the active option, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"well-path-intersection\"\u003eWell Path Intersection\u003c/h3\u003e\n\u003cp\u003eA new \u003cstrong\u003eWell Path\u003c/strong\u003e intersection can be created by right-clicking the well path in the 3D view or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionWellPath.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen a well path intersection is created, the source well path can be changed by using the \u003cstrong\u003eWell Path\u003c/strong\u003e selection combo box in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"simulation-well-intersection\"\u003eSimulation Well Intersection\u003c/h3\u003e\n\u003cp\u003eA new \u003cstrong\u003eSimulation Well\u003c/strong\u003e intersection can be created by right-clicking the simulation well in the 3D view or in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionSimulationWellProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen a simulation well intersection is created, the source simulation well can be changed by using the \u003cstrong\u003eSimulation Well\u003c/strong\u003e selection combo box in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eIf the well contains more than one branch, the intersection geometry will be created for the selected branch in the \u003cstrong\u003eBranch\u003c/strong\u003e combo box.\u003c/p\u003e\n\u003ch3 id=\"polyline-intersection\"\u003ePolyline Intersection\u003c/h3\u003e\n\u003cp\u003eA new \u003cstrong\u003ePolyline\u003c/strong\u003e intersection can be created from the right-click menu in the 3D view. Then, by left-clicking on reservoir geometry, a polyline is created. The points are added to the point list in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPolyline.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), push the button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\u003cp\u003eThe points in the list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using \u003cstrong\u003eCTRL-V\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"azimuth-and-dip\"\u003eAzimuth and Dip\u003c/h3\u003e\n\u003cp\u003eA new \u003cstrong\u003eAzimuth and Dip\u003c/strong\u003e intersection can be created from the right-click menu in the 3D view. Then, by left-clicking two points on reservoir geometry, a single line is created between the first point, and the second point projected down to the plane with same z-value as the first point. The two points are added to the point list in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionAzimuthDip.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe background color of this list is set to light pink when adding points by picking in the 3D view is active.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click the button \u003cstrong\u003eStop picking points\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eThe background color of the point list is then set to white.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, push the button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\u003cp\u003eThe points in the list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when keyboard focus is inside the point list. A new list of points can be pasted into the point list by using \u003cstrong\u003eCTRL-V\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eWhen two points are picked, a plane between the points will appear in the 3D view, with a 90 degrees \u003cstrong\u003eDip\u003c/strong\u003e, and the \u003cstrong\u003eAzimuth\u003c/strong\u003e angle calculated from the two points. The two angles can be edited in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of the intersection, and is defined by the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e is the angle between the horizontal plane and down.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e is the angle between North and the plane. Changing the azimuth will rotate the plane about the first point picked in the 3D view.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe length of the plane can also be set manually in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLength Up\u003c/strong\u003e is the distance from the user defined horizontal line, to the top of the plane intersecting the model.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLength Down\u003c/strong\u003e is the distance from the user defined horizontal line, to the bottom of the plane intersecting the model.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/azimuthDip3DView.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"2d-intersection-views\"\u003e2D Intersection Views\u003c/h3\u003e\n\u003cp\u003eA 2D Intersection View displays the intersection in a separate 2D view along with the defining curve. The intersection and the defining well path, simulation well or polyline is flattened to make it easier to see the intersected grid and how the well traverses it.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEach of the curve based intersections have a corresponding \u003cstrong\u003e2D Intersection View\u003c/strong\u003e. Management of these views are automatic. They will be created and deleted along with the intersection.\u003c/p\u003e\n\u003cp\u003eThe view can be shown either by right clicking the intersection and select the command \u003cstrong\u003eShow 2D intersection View\u003c/strong\u003e, or by toggling the view in the project tree directly.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionViewsProjectTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eScales along the edges of the view show the depth and the horizontal length of the intersection. The length is measured from the start of the wellpath or the well head of a simulation well.\u003c/p\u003e\n\u003cp\u003eThe view is mostly controlled by the options in the 3D view where the intersection is defined. There are, however some independent controls, like drawstyle, timestep and Z-scale.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/2DIntersectionViewProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eViewer\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; User editable name of the view. The default name is set by combining the name of the origin view and the intersection name.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBackground\u003c/strong\u003e \u0026ndash; Color of the viewer background\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDisable Results Lighting\u003c/strong\u003e \u0026ndash; Toggle the light effect. When the lighting is turned off, the colors are easier to compare with the legend, but the colors carry no visual cue to visualize the 3D shape. The effect is tiny on 2D Intersection Views.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Appearance\u003c/strong\u003e \u0026ndash; Controls the drawstyle of the grid geometry\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eZ Scale\u003c/strong\u003e \u0026ndash; Scales the view in Z(depth) direction to make slim K-layers easier to see\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Lines\u003c/strong\u003e \u0026ndash; Controls what mesh lines to draw\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll\u003c/strong\u003e \u0026ndash; All mesh lines are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFaults Only\u003c/strong\u003e \u0026ndash; Only mesh lines associated with faults are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e \u0026ndash; Mesh lines are not drawn at all\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Surface\u003c/strong\u003e \u0026ndash; Controls what grid surface geometry to draw\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll\u003c/strong\u003e \u0026ndash; All grid faces are drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFaults Only\u003c/strong\u003e \u0026ndash; Only faces that are included in a fault is drawn\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e \u0026ndash; Do not draw any faces\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefining Points\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow points\u003c/strong\u003e \u0026ndash; Toggle the display of the defining points for Polyline or Azimuth and Dip intersections.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThese options are similar to the options for a regular 3D view (See \u003ca href=\"/3d-main-window/3dviews/#view-properties\"\u003eView Properties\u003c/a\u003e )\u003c/p\u003e\n\u003ch2 id=\"intersection-box-and-intersection-planes\"\u003eIntersection Box and Intersection Planes\u003c/h2\u003e\n\u003cp\u003eA new \u003cstrong\u003eIntersection Box\u003c/strong\u003e or \u003cstrong\u003eIntersection Plane\u003c/strong\u003e can be created from the right-click menu in the 3D view or the right-click menu in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/3d_view_context_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe following list describes the properties for an \u003cstrong\u003eIntersection Box\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Automatically created based on the item specifying the intersection\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBox Type\u003c/strong\u003e \u0026ndash; Box or x-plane, y-plane or z-plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Inactive Cells\u003c/strong\u003e \u0026ndash; Controls if inactive cells are included when creating the intersection geometry\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eX Coordinates\u003c/strong\u003e \u0026ndash; Coordinates for x range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eY Coordinates\u003c/strong\u003e \u0026ndash; Coordinates for y range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth\u003c/strong\u003e \u0026ndash; Coordinates for depth range\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXY Slider Step Size\u003c/strong\u003e \u0026ndash; Defines how much the value changes when the slider for XY values is changed, default value 1.0\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slider Step Size\u003c/strong\u003e \u0026ndash; Defines how much the value changes when the slider for depth values is changed, default value 0.5\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eDirect interaction in a 3D view is activated when \u003cstrong\u003eShow 3D manipulator\u003c/strong\u003e is pressed. Handles are displayed at the sides of the intersection object, and interactive modification is done by dragging a handle in the 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionBoxWithHandles.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/intersections/"
             };
         
@@ -2407,7 +2440,7 @@ if (!doNotTrack) {
             window.store["/misc/"] = {
                 title:    "Miscellaneous",
                 content:  "This chapter of the ResInsight documentation describes the following:\n defining preferences to customize and adapt the behavior of ResInsight for your purposes and work flow memory management, i.e. how to determine consumption and clearing data from computer memory keyboard shortcuts for effective and convenient usage of ResInsight use of the built-in regression test system of ResInsight  See the subsequent subchapters for more information on each topic.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryManagementBanner.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis chapter of the ResInsight documentation describes the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003edefining preferences to customize and adapt the behavior of ResInsight for your purposes and work flow\u003c/li\u003e\n\u003cli\u003ememory management, i.e. how to determine consumption and clearing data from computer memory\u003c/li\u003e\n\u003cli\u003ekeyboard shortcuts for effective and convenient usage of ResInsight\u003c/li\u003e\n\u003cli\u003euse of the built-in regression test system of ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eSee the subsequent subchapters for more information on each topic.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MemoryManagementBanner.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis chapter of the ResInsight documentation describes the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003edefining preferences to customize and adapt the behavior of ResInsight for your purposes and work flow\u003c/li\u003e\n\u003cli\u003ememory management, i.e. how to determine consumption and clearing data from computer memory\u003c/li\u003e\n\u003cli\u003ekeyboard shortcuts for effective and convenient usage of ResInsight\u003c/li\u003e\n\u003cli\u003euse of the built-in regression test system of ResInsight\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee the subsequent subchapters for more information on each topic.\u003c/p\u003e\n",
                 url:      "/misc/"
             };
         
@@ -2415,8 +2448,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/wellborestabilityplots/"] = {
                 title:    "Well Bore Stability Plots",
-                content:  " ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots to visualize Formations, Well Path Attributes as well as a set of well path derived curves in different tracks.\nIn the figure above, the first track contains Formations while the second track contains well attributes of Casing Design. The third track shows the following stability gradients (all normalized by mud weight):\n FG: Fracture Gradient for sands based on Kirsch. OBG: Overburden stress gradient: Stress component S_33. PP: Pore pressure. SFG: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia. SH: Minimum horizontal stress.  The fourth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\nCreate Well Bore Stability plots Well Bore Stability plots can be created from the right-click menu for a well path in Project Tree or from the the right-click menu of the Well Log Plots entry in Plot Project Tree. In the former case, the well bore stability plot will be created for the selected Well Path. In the latter case, it will be created for the first well path in the well path list and the well path for the entire plot can be changed with the Change Data Source Feature.\nInput requirements In order to calculate FG and SFG, the following input parameters are required:\n   Curve Required Parameters     FG Pore Pressure (PP), Poissons\u0026rsquo; Ratio   SFG Uniaxial Compressive Strength (UCS)    These parameters may be read in in the following ways.\nChange Data Source Feature\nThe numbering for import is order of preference if multiple sources are found.\n   Parameter Default Import mechanisms     PP Hydrostatic PP (TVD x 9.81 / 100 bar) 1. Grid (Grid units), 2. LAS-file as mud-weight (Variable: \u0026ldquo;PP\u0026rdquo;, Units: kg / m^3), 3. Element Property Table (Variable: \u0026ldquo;POR\u0026rdquo;, Units: Pascal)   Poissons\u0026rsquo; Ratio 0.25 1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;)   UCS 100 bar 1. Las-file (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: MPa)    Equations and calculations Stresses at the borehole wall - Kirsch equations The basic input to wellbore stability models is the stresses at the borehole wall given by the Kirsch equations in cylindrical coordinates:\nThe transformation of stresses from cartesian coordinate system to x\u0026rsquo;, y\u0026rsquo;, z\u0026rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix M, i.e. .\nFracture gradient calculations based on Kirsch in sand To estimate the fracture gradient FG, first step is to find the principle effective stresses at the borehole wall:\nNext step is to find the well pressure Pw that gives for . Then calculate FG in equivalent mud weight units as FG = Pw / (TVDRKB * g * 1000) where TVDRKB = TVDMSL + RKB and g = 9.81.\nStassi-d\u0026rsquo;Alia failure criterion in shale Stassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure Pw that satisfies the following equation for .\nwhere are the effective principal stresses and UCS is the uniaxial compressive strength.\nShear Failure Gradient is then given as SFG = Pw / (TVDRKB * g * 1000) where TVDRKB = TVDMSL + RKB and g = 9.81.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStability.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create \u003cstrong\u003eWell Bore Stability\u003c/strong\u003e plots for Geomechanical cases. These plots are specialized \u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e to visualize \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e, \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Path Attributes\u003c/a\u003e as well as a set of well path derived curves in different tracks.\u003c/p\u003e\n\n\u003cp\u003eIn the figure above, the first track contains \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e while the second track contains well attributes of\n\u003ca href=\"/wells-and-completions/wellpaths/#casing-design\"\u003eCasing Design\u003c/a\u003e.\nThe third track shows the following stability gradients (all normalized by mud weight):\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFG\u003c/strong\u003e: Fracture Gradient for sands based on Kirsch.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOBG\u003c/strong\u003e: Overburden stress gradient: Stress component S_33.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePP\u003c/strong\u003e: Pore pressure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSFG\u003c/strong\u003e: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSH\u003c/strong\u003e: Minimum horizontal stress.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe fourth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\u003c/p\u003e\n\n\u003ch2 id=\"create-well-bore-stability-plots\"\u003eCreate Well Bore Stability plots\u003c/h2\u003e\n\n\u003cp\u003eWell Bore Stability plots can be created from the right-click menu for a well path in \u003cstrong\u003eProject Tree\u003c/strong\u003e or from the the right-click menu of the Well Log Plots entry in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. In the former case, the well bore stability plot will be created for the selected \u003cstrong\u003eWell Path\u003c/strong\u003e. In the latter case, it will be created for the first well path in the well path list and the well path for the entire plot can be changed with the \u003ca href=\"/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves\"\u003eChange Data Source Feature\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityCreation.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/WellBoreStabilityCreation2.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"input-requirements\"\u003eInput requirements\u003c/h2\u003e\n\n\u003cp\u003eIn order to calculate \u003cstrong\u003eFG\u003c/strong\u003e  and \u003cstrong\u003eSFG\u003c/strong\u003e, the following input parameters are required:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCurve\u003c/th\u003e\n\u003cth\u003eRequired Parameters\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG\u003c/td\u003e\n\u003ctd\u003ePore Pressure (PP), Poissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eSFG\u003c/td\u003e\n\u003ctd\u003eUniaxial Compressive Strength (UCS)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eThese parameters may be read in in the following ways.\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves\"\u003eChange Data Source Feature\u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003eThe numbering for import is order of preference if multiple sources are found.\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eImport mechanisms\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP\u003c/td\u003e\n\u003ctd\u003eHydrostatic PP (TVD x 9.81 / 100 bar)\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file as mud-weight (Variable: \u0026ldquo;PP\u0026rdquo;, Units: kg / m^3), 3. Element Property Table (Variable: \u0026ldquo;POR\u0026rdquo;, Units: Pascal)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003ePoissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003ctd\u003e0.25\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;)\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eUCS\u003c/td\u003e\n\u003ctd\u003e100 bar\u003c/td\u003e\n\u003ctd\u003e1. Las-file (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: MPa)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch2 id=\"equations-and-calculations\"\u003eEquations and calculations\u003c/h2\u003e\n\n\u003ch3 id=\"stresses-at-the-borehole-wall-kirsch-equations\"\u003eStresses at the borehole wall - Kirsch equations\u003c/h3\u003e\n\n\u003cp\u003eThe basic input to wellbore stability models is the stresses at the borehole wall given by the Kirsch equations in cylindrical coordinates:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityKirschEquations.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe transformation of stresses from cartesian coordinate system to x\u0026rsquo;, y\u0026rsquo;, z\u0026rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix \u003cstrong\u003eM\u003c/strong\u003e, i.e.\n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilityStressTransformation.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\n\u003ch3 id=\"fracture-gradient-calculations-based-on-kirsch-in-sand\"\u003eFracture gradient calculations based on Kirsch in sand\u003c/h3\u003e\n\n\u003cp\u003eTo estimate the fracture gradient \u003cem\u003eFG\u003c/em\u003e, first step is to find the principle effective stresses at the borehole wall:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityKirschSandEquations.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eNext step is to find the well pressure \u003cem\u003ePw\u003c/em\u003e that gives\n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTminZero.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n for\n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\nThen calculate \u003cem\u003eFG\u003c/em\u003e in equivalent mud weight units as \u003cem\u003eFG\u003c/em\u003e = \u003cem\u003ePw\u003c/em\u003e / (\u003cem\u003eTVDRKB\u003c/em\u003e * \u003cem\u003eg\u003c/em\u003e * 1000) where \u003cem\u003eTVDRKB = TVDMSL + RKB\u003c/em\u003e and\n\u003cem\u003eg = 9.81\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"stassi-d-alia-failure-criterion-in-shale\"\u003eStassi-d\u0026rsquo;Alia failure criterion in shale\u003c/h3\u003e\n\n\u003cp\u003eStassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure \u003cem\u003ePw\u003c/em\u003e that satisfies the following equation\nfor \u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityStassiEquations.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003ewhere \u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilityPrincipalStresses.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n are the effective principal stresses\nand \u003cem\u003eUCS\u003c/em\u003e is the \u003cem\u003euniaxial compressive strength\u003c/em\u003e.\u003c/p\u003e\n\n\u003cp\u003eShear Failure Gradient is then given as \u003cem\u003eSFG\u003c/em\u003e = \u003cem\u003ePw\u003c/em\u003e / (\u003cem\u003eTVDRKB\u003c/em\u003e * \u003cem\u003eg\u003c/em\u003e * 1000) where \u003cem\u003eTVDRKB = TVDMSL + RKB\u003c/em\u003e and \u003cem\u003eg = 9.81\u003c/em\u003e.\u003c/p\u003e\n",
+                content:  "ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots to visualize Formations, Well Path Attributes as well as a set of well path derived curves in different tracks.\nIn the figure above, the first track contains Formations while the second track contains well attributes of Casing Design. The third track shows the following stability gradients (all normalized by mud weight):\n FG: Fracture Gradient for sands based on Kirsch. OBG: Overburden stress gradient: Stress component S_33. PP: Pore pressure. SFG: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia. SH: Minimum horizontal stress.  The fourth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\nCreate Well Bore Stability plots Well Bore Stability plots can be created from the right-click menu for a well path in Project Tree or from the the right-click menu of the Well Log Plots entry in Plot Project Tree. In the former case, the well bore stability plot will be created for the selected Well Path. In the latter case, it will be created for the first well path in the well path list and the well path for the entire plot can be changed with the Change Data Source Feature.\nInput requirements In order to calculate FG and SFG, the following input parameters are required:\n   Curve Required Parameters     FG Pore Pressure (PP), Poissons\u0026rsquo; Ratio   SFG Uniaxial Compressive Strength (UCS)    These parameters may be read in in the following ways.\nChange Data Source Feature\nThe numbering for import is order of preference if multiple sources are found.\n   Parameter Default Import mechanisms     PP Hydrostatic PP (TVD x 9.81 / 100 bar) 1. Grid (Grid units), 2. LAS-file as mud-weight (Variable: \u0026ldquo;PP\u0026rdquo;, Units: kg / m^3), 3. Element Property Table (Variable: \u0026ldquo;POR\u0026rdquo;, Units: Pascal)   Poissons\u0026rsquo; Ratio 0.25 1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;)   UCS 100 bar 1. Las-file (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: MPa)    Equations and calculations Stresses at the borehole wall - Kirsch equations The basic input to wellbore stability models is the stresses at the borehole wall given by the Kirsch equations in cylindrical coordinates:\nThe transformation of stresses from cartesian coordinate system to x\u0026rsquo;, y\u0026rsquo;, z\u0026rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix M, i.e. .\nFracture gradient calculations based on Kirsch in sand To estimate the fracture gradient FG, first step is to find the principle effective stresses at the borehole wall:\nNext step is to find the well pressure Pw that gives for . Then calculate FG in equivalent mud weight units as FG = Pw / (TVDRKB * g * 1000) where TVDRKB = TVDMSL + RKB and g = 9.81.\nStassi-d\u0026rsquo;Alia failure criterion in shale Stassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure Pw that satisfies the following equation for .\nwhere are the effective principal stresses and UCS is the uniaxial compressive strength.\nShear Failure Gradient is then given as SFG = Pw / (TVDRKB * g * 1000) where TVDRKB = TVDMSL + RKB and g = 9.81.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStability.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create \u003cstrong\u003eWell Bore Stability\u003c/strong\u003e plots for Geomechanical cases. These plots are specialized \u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e to visualize \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e, \u003ca href=\"/wells-and-completions/wellpaths/#well-path-attributes\"\u003eWell Path Attributes\u003c/a\u003e as well as a set of well path derived curves in different tracks.\u003c/p\u003e\n\u003cp\u003eIn the figure above, the first track contains \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e while the second track contains well attributes of \n\u003ca href=\"/wells-and-completions/wellpaths/#casing-design\"\u003eCasing Design\u003c/a\u003e.\nThe third track shows the following stability gradients (all normalized by mud weight):\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFG\u003c/strong\u003e: Fracture Gradient for sands based on Kirsch.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOBG\u003c/strong\u003e: Overburden stress gradient: Stress component S_33.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePP\u003c/strong\u003e: Pore pressure.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSFG\u003c/strong\u003e: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSH\u003c/strong\u003e: Minimum horizontal stress.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe fourth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\u003c/p\u003e\n\u003ch2 id=\"create-well-bore-stability-plots\"\u003eCreate Well Bore Stability plots\u003c/h2\u003e\n\u003cp\u003eWell Bore Stability plots can be created from the right-click menu for a well path in \u003cstrong\u003eProject Tree\u003c/strong\u003e or from the the right-click menu of the Well Log Plots entry in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. In the former case, the well bore stability plot will be created for the selected \u003cstrong\u003eWell Path\u003c/strong\u003e. In the latter case, it will be created for the first well path in the well path list and the well path for the entire plot can be changed with the \u003ca href=\"/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves\"\u003eChange Data Source Feature\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityCreation.png\" alt=\"\"\u003e \n\u003cimg src=\"/images/plot-window/WellBoreStabilityCreation2.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"input-requirements\"\u003eInput requirements\u003c/h2\u003e\n\u003cp\u003eIn order to calculate \u003cstrong\u003eFG\u003c/strong\u003e  and \u003cstrong\u003eSFG\u003c/strong\u003e, the following input parameters are required:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eCurve\u003c/th\u003e\n\u003cth\u003eRequired Parameters\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG\u003c/td\u003e\n\u003ctd\u003ePore Pressure (PP), Poissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eSFG\u003c/td\u003e\n\u003ctd\u003eUniaxial Compressive Strength (UCS)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eThese parameters may be read in in the following ways.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/welllogsandplots/#change-data-source-for-plots-and-curves\"\u003eChange Data Source Feature\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe numbering for import is order of preference if multiple sources are found.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDefault\u003c/th\u003e\n\u003cth\u003eImport mechanisms\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP\u003c/td\u003e\n\u003ctd\u003eHydrostatic PP (TVD x 9.81 / 100 bar)\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file as mud-weight (Variable: \u0026ldquo;PP\u0026rdquo;, Units: kg / m^3), 3. Element Property Table (Variable: \u0026ldquo;POR\u0026rdquo;, Units: Pascal)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePoissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003ctd\u003e0.25\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO\u0026rdquo;)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eUCS\u003c/td\u003e\n\u003ctd\u003e100 bar\u003c/td\u003e\n\u003ctd\u003e1. Las-file (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS\u0026rdquo;, Units: MPa)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch2 id=\"equations-and-calculations\"\u003eEquations and calculations\u003c/h2\u003e\n\u003ch3 id=\"stresses-at-the-borehole-wall---kirsch-equations\"\u003eStresses at the borehole wall - Kirsch equations\u003c/h3\u003e\n\u003cp\u003eThe basic input to wellbore stability models is the stresses at the borehole wall given by the Kirsch equations in cylindrical coordinates:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityKirschEquations.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe transformation of stresses from cartesian coordinate system to x\u0026rsquo;, y\u0026rsquo;, z\u0026rsquo; is performed by pre- and transposed postmultiplication of the stress tensor with a 3x3 transformation matrix \u003cstrong\u003eM\u003c/strong\u003e, i.e. \n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilityStressTransformation.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003ch3 id=\"fracture-gradient-calculations-based-on-kirsch-in-sand\"\u003eFracture gradient calculations based on Kirsch in sand\u003c/h3\u003e\n\u003cp\u003eTo estimate the fracture gradient \u003cem\u003eFG\u003c/em\u003e, first step is to find the principle effective stresses at the borehole wall:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityKirschSandEquations.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNext step is to find the well pressure \u003cem\u003ePw\u003c/em\u003e that gives \n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTminZero.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n for \n\u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\nThen calculate \u003cem\u003eFG\u003c/em\u003e in equivalent mud weight units as \u003cem\u003eFG\u003c/em\u003e = \u003cem\u003ePw\u003c/em\u003e / (\u003cem\u003eTVDRKB\u003c/em\u003e * \u003cem\u003eg\u003c/em\u003e * 1000) where \u003cem\u003eTVDRKB = TVDMSL + RKB\u003c/em\u003e and \n\u003cem\u003eg = 9.81\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"stassi-dalia-failure-criterion-in-shale\"\u003eStassi-d\u0026rsquo;Alia failure criterion in shale\u003c/h3\u003e\n\u003cp\u003eStassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure \u003cem\u003ePw\u003c/em\u003e that satisfies the following equation \nfor \u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilitySigmaTmin.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityStassiEquations.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003ewhere \u003cimg src=\"https://resinsight.org/images/plot-window/WellBoreStabilityPrincipalStresses.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n are the effective principal stresses \nand \u003cem\u003eUCS\u003c/em\u003e is the \u003cem\u003euniaxial compressive strength\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eShear Failure Gradient is then given as \u003cem\u003eSFG\u003c/em\u003e = \u003cem\u003ePw\u003c/em\u003e / (\u003cem\u003eTVDRKB\u003c/em\u003e * \u003cem\u003eg\u003c/em\u003e * 1000) where \u003cem\u003eTVDRKB = TVDMSL + RKB\u003c/em\u003e and \u003cem\u003eg = 9.81\u003c/em\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/wellborestabilityplots/"
             };
         
@@ -2424,17 +2457,26 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/faults/"] = {
                 title:    "Faults",
-                content:  " This section describes how Faults are detected and visualized. NNC\u0026rsquo;s are a part of the Faults visualization and are thus also mentioned in this section.\nFault Detection ResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.\nAll the tagged cell faces are then compared to the faults possibly imported from the *.DATA file in order to group them. If a particular face is not found among the fault faces defined in the *.DATA file (or their opposite faces), the cell face is added to one of two predefined faults:\n Undefined grid faults Undefined grid faults With Inactive  The first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.\nThese particular Faults will always be present, even when reading of fault information from the *.DATA file is disabled.\nInformation from *.DATA-files Fault Information If enabled in Preferences, ResInsight will import fault information from the *.DATA files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.\nThe DATA file is parsed for the FAULT keyword while respecting any INCLUDE and PATH keywords.\nAs import of faults can be time consuming, reading of faults can be disabled from Preferences-\u0026gt;Import faults\n\rNNC Data If enabled in Preferences, ResInsight will read Non Neighbor Connections from the Eclipse output file (*.INIT), and create explicit visualizations of those. The NNC\u0026rsquo;s are sorted onto the Fault\u0026rsquo;s and their visibility is controlled along with them.\nFault Visualization Options Fault Visibility Faults can be hidden and shown in several ways.\n Checking or unchecking the checkbox in front of the fault will show or hide the fault. Visibility for multiple faults can be controlled at the same time by selecting multiple faults and use the right-click menu: On, Off and Toggle. Hide the fault from the right-click menu of a Fault in the 3D View.  Fault Color Each named Fault is given a color on import. This color can be controlled by selecting the fault and edit its Fault color in the Property Editor.\nSeparate Fault Result The default result mapping used on faults are to use the same as specified in Cell Result. If a different result mapping is wanted, enable the checkbox at Separate Fault Result and select the result from the result selection dialog in the Property Editor. A second legend for the fault result is then added to the view.\nToolbar Control Visualization mode and mesh lines can be controlled from the toolbar.\n Faults-Only visualization mode. When turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless Show faults outside filters are turned on. See below.) Turns faces on and mesh off Turns on all faces, and shows mesh lines on faults only. This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining. Shows labels for faults\n  Faults Properties By clicking the Faults item in the Project Tree, the following options common to all the faults are displayed:\nFault Labels  Show labels \u0026ndash; Displays one label per fault with the name defined in the *.DATA file Label color \u0026ndash; Defines the label color  Fault Options  Show faults outside filters \u0026ndash; Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.  Fault Face Visibility This group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.\nFirst of all, these options are only available in Faults-only visualization mode ( See Toolbar Control ). When not in Faults-Only mode, ResInsight overrides the options, and the controls are inactive.\nSecondly, the option you would normally want to adjust is Dynamic Face Selection ( See below ).\n Show defined faces \u0026ndash; Displays the fault cell faces that are defined on the Eclipse input file (*.DATA) Show opposite faces \u0026ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.\n*These two options should normally be left On. They are useful when investigating the exact faults information provided on the *.DATA file. If you need to use them, it is normally wise to set the Dynamic Face Selection to \u0026ldquo;Show Both\u0026rdquo;.* Dynamic Face Selection \u0026ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.\nThis option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.\nThis means that ResInsight turns on or off the faces based on your view position and this option to make sure that you always see the faces (and thus the result property) you request.  NNC Visibility  Show NNCs \u0026ndash; Toggles whether to display the Non Neighbor Connections, or not. Hide NNC geometry if no NNC result is available \u0026ndash; Automatically hides NNC geometry if no NNC results are available  The color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.\n\rFault Export Faults can be exported to separate files in the *grdecl file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.\nTo export some faults, select the faults you want to export in the Project Tree, and select the command Export Faults \u0026hellip; from the right-click menu.\nYou are then prompted to select a destination folder. Each Fault is exported to a file named Faults_\u0026lt;fault name\u0026gt;_\u0026lt;case name\u0026gt;.grdecl and stored in the selected folder.\nThe fault name of Undefined Grid Faults is simplified to UNDEF, while Undefined Grid Faults With Inactive is simplified to UNDEF_IA. All other faults keep their original name.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FaultsIllustration.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis section describes how Faults are detected and visualized. NNC\u0026rsquo;s are a part of the Faults visualization and are thus also mentioned in this section.\u003c/p\u003e\n\n\u003ch2 id=\"fault-detection\"\u003eFault Detection\u003c/h2\u003e\n\n\u003cp\u003eResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.\u003c/p\u003e\n\n\u003cp\u003eAll the tagged cell faces are then compared to the faults possibly imported from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file in order to group them. If a particular face is \u003cem\u003enot\u003c/em\u003e found among the fault faces defined in the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file (or their opposite faces), the cell face is added to one of two predefined faults:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined grid faults\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined grid faults With Inactive\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.\u003c/p\u003e\n\n\u003cp\u003eThese particular Faults will always be present, even when reading of fault information from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file is disabled.\u003c/p\u003e\n\n\u003ch3 id=\"information-from-data-files\"\u003eInformation from \u003ccode\u003e*.DATA\u003c/code\u003e-files\u003c/h3\u003e\n\n\u003ch4 id=\"fault-information\"\u003eFault Information\u003c/h4\u003e\n\n\u003cp\u003eIf enabled in \u003cstrong\u003ePreferences\u003c/strong\u003e, ResInsight will import fault information from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe \u003cb\u003eDATA\u003c/b\u003e file is parsed for the \u003cb\u003eFAULT\u003c/b\u003e keyword while respecting any \u003cb\u003eINCLUDE\u003c/b\u003e and \u003cb\u003ePATH\u003c/b\u003e keywords.\u003cbr\u003e\nAs import of faults can be time consuming, reading of faults can be disabled from \u003cb\u003ePreferences-\u0026gt;Import faults\u003c/b\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"nnc-data\"\u003eNNC Data\u003c/h4\u003e\n\n\u003cp\u003eIf enabled in \u003cstrong\u003ePreferences\u003c/strong\u003e, ResInsight will read Non Neighbor Connections from the Eclipse output file (\u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e), and create explicit visualizations of those.\nThe NNC\u0026rsquo;s are sorted onto the Fault\u0026rsquo;s and their visibility is controlled along with them.\u003c/p\u003e\n\n\u003ch2 id=\"fault-visualization-options\"\u003eFault Visualization Options\u003c/h2\u003e\n\n\u003ch3 id=\"fault-visibility\"\u003eFault Visibility\u003c/h3\u003e\n\n\u003cp\u003eFaults can be hidden and shown in several ways.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eChecking or unchecking the checkbox in front of the fault will show or hide the fault.\u003c/li\u003e\n\u003cli\u003eVisibility for multiple faults can be controlled at the same time by selecting multiple faults and use the right-click menu: \u003cstrong\u003eOn\u003c/strong\u003e, \u003cstrong\u003eOff\u003c/strong\u003e and \u003cstrong\u003eToggle\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eHide the fault from the  right-click menu of a Fault in the 3D View.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"fault-color\"\u003eFault Color\u003c/h3\u003e\n\n\u003cp\u003eEach named Fault is given a color on import. This color can be controlled by selecting the fault and edit its  \u003cstrong\u003eFault color\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor.\u003c/strong\u003e\u003c/p\u003e\n\n\u003ch3 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h3\u003e\n\n\u003cp\u003eThe default result mapping used on faults are to use the same as specified in \u003cstrong\u003eCell Result\u003c/strong\u003e. If a different result mapping is wanted, enable the checkbox at \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e and select the result from the result selection dialog in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. A second legend for the fault result is then added to the view.\u003c/p\u003e\n\n\u003ch3 id=\"toolbar-control\"\u003eToolbar Control\u003c/h3\u003e\n\n\u003cp\u003eVisualization mode and mesh lines can be controlled from the toolbar.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eFaults-Only\u003c/strong\u003e visualization mode.\n\u003cbr\u003eWhen turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless \u003cstrong\u003eShow faults outside filters\u003c/strong\u003e are turned on. See below.)\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_surface_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Turns faces on and mesh off\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_surface_w_fault_mesh_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Turns on all faces, and shows mesh lines on faults only.\n\u003cbr\u003e This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining.\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_label_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Shows labels for faults\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"faults-properties\"\u003eFaults Properties\u003c/h3\u003e\n\n\u003cp\u003eBy clicking the \u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eFaults\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, the following options common to all the faults are displayed:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FaultProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch5 id=\"fault-labels\"\u003eFault Labels\u003c/h5\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow labels\u003c/strong\u003e \u0026ndash; Displays one label per fault with the name defined in the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel color\u003c/strong\u003e \u0026ndash; Defines the label color\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"fault-options\"\u003eFault Options\u003c/h5\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow faults outside filters\u003c/strong\u003e \u0026ndash; Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"fault-face-visibility\"\u003eFault Face Visibility\u003c/h5\u003e\n\n\u003cp\u003eThis group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.\u003c/p\u003e\n\n\u003cp\u003eFirst of all, these options are only available in \u003cstrong\u003eFaults-only\u003c/strong\u003e visualization mode ( See \u003ca href=\"#toolbar-control\"\u003eToolbar Control\u003c/a\u003e ). When not in \u003cstrong\u003eFaults-Only\u003c/strong\u003e mode, ResInsight overrides the options, and the controls are inactive.\u003c/p\u003e\n\n\u003cp\u003eSecondly, the option you would normally want to adjust is \u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e ( See below ).\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow defined faces\u003c/strong\u003e \u0026ndash; Displays the fault cell faces that are defined on the Eclipse input file (\u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow opposite faces\u003c/strong\u003e \u0026ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.\u003cbr /\u003e\n*These two options should normally be left \u003cstrong\u003eOn\u003c/strong\u003e. They are useful when investigating the exact faults information provided on the \u003ccode\u003e*.DATA\u003c/code\u003e file. If you need to use them, it is normally wise to set the \u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e to \u0026ldquo;Show Both\u0026rdquo;.*\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e \u0026ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.\u003cbr /\u003e\nThis option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.\u003cbr /\u003e\nThis means that ResInsight turns on or off the faces based on your view position and this option to make sure that you always see the faces (and thus the result property) you request.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"nnc-visibility\"\u003eNNC Visibility\u003c/h5\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow NNCs\u003c/strong\u003e \u0026ndash; Toggles whether to display the Non Neighbor Connections, or not.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHide NNC geometry if no NNC result is available\u003c/strong\u003e \u0026ndash; Automatically hides NNC geometry if no NNC results are available\u003c/li\u003e\n\u003c/ul\u003e\n\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"fault-export\"\u003eFault Export\u003c/h2\u003e\n\n\u003cp\u003eFaults can be exported to separate files in the \u003cem\u003e\u003ccode\u003e*grdecl\u003c/code\u003e\u003c/em\u003e file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.\u003c/p\u003e\n\n\u003cp\u003eTo export some faults, select the faults you want to export in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and select the command \u003cstrong\u003eExport Faults \u0026hellip;\u003c/strong\u003e from the right-click menu.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ExportFaultsMenu.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eYou are then prompted to select a destination folder. Each Fault is exported to a file named \u003cem\u003e\u003ccode\u003eFaults_\u0026lt;fault name\u0026gt;_\u0026lt;case name\u0026gt;.grdecl\u003c/code\u003e\u003c/em\u003e and stored in the selected folder.\u003c/p\u003e\n\n\u003cp\u003eThe fault name of \u003cstrong\u003eUndefined Grid Faults\u003c/strong\u003e is simplified to \u003cem\u003e\u003ccode\u003eUNDEF\u003c/code\u003e\u003c/em\u003e, while \u003cstrong\u003eUndefined Grid Faults With Inactive\u003c/strong\u003e is simplified to \u003cem\u003e\u003ccode\u003eUNDEF_IA\u003c/code\u003e\u003c/em\u003e. All other faults keep their original name.\u003c/p\u003e\n",
+                content:  "This section describes how Faults are detected and visualized. NNC\u0026rsquo;s are a part of the Faults visualization and are thus also mentioned in this section.\nFault Detection ResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.\nAll the tagged cell faces are then compared to the faults possibly imported from the *.DATA file in order to group them. If a particular face is not found among the fault faces defined in the *.DATA file (or their opposite faces), the cell face is added to one of two predefined faults:\n Undefined grid faults Undefined grid faults With Inactive  The first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.\nThese particular Faults will always be present, even when reading of fault information from the *.DATA file is disabled.\nInformation from *.DATA-files Fault Information If enabled in Preferences, ResInsight will import fault information from the *.DATA files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.\nThe DATAfile is parsed for the FAULTkeyword while respecting any INCLUDEand PATHkeywords.As import of faults can be time consuming, reading of faults can be disabled from Preferences-\u0026gt;Import faults\rNNC Data If enabled in Preferences, ResInsight will read Non Neighbor Connections from the Eclipse output file (*.INIT), and create explicit visualizations of those. The NNC\u0026rsquo;s are sorted onto the Fault\u0026rsquo;s and their visibility is controlled along with them.\nFault Visualization Options Fault Visibility Faults can be hidden and shown in several ways.\n Checking or unchecking the checkbox in front of the fault will show or hide the fault. Visibility for multiple faults can be controlled at the same time by selecting multiple faults and use the right-click menu: On, Off and Toggle. Hide the fault from the right-click menu of a Fault in the 3D View.  Fault Color Each named Fault is given a color on import. This color can be controlled by selecting the fault and edit its Fault color in the Property Editor.\nSeparate Fault Result The default result mapping used on faults are to use the same as specified in Cell Result. If a different result mapping is wanted, enable the checkbox at Separate Fault Result and select the result from the result selection dialog in the Property Editor. A second legend for the fault result is then added to the view.\nToolbar Control Visualization mode and mesh lines can be controlled from the toolbar.\n Faults-Only visualization mode. When turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless Show faults outside filters are turned on. See below.) Turns faces on and mesh off Turns on all faces, and shows mesh lines on faults only. This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining. Shows labels for faults  Faults Properties By clicking the Faults item in the Project Tree, the following options common to all the faults are displayed:\nFault Labels  Show labels \u0026ndash; Displays one label per fault with the name defined in the *.DATA file Label color \u0026ndash; Defines the label color  Fault Options  Show faults outside filters \u0026ndash; Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.  Fault Face Visibility This group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.\nFirst of all, these options are only available in Faults-only visualization mode ( See Toolbar Control ). When not in Faults-Only mode, ResInsight overrides the options, and the controls are inactive.\nSecondly, the option you would normally want to adjust is Dynamic Face Selection ( See below ).\n Show defined faces \u0026ndash; Displays the fault cell faces that are defined on the Eclipse input file (*.DATA) Show opposite faces \u0026ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.\nThese two options should normally be left On. They are useful when investigating the exact faults information provided on the *.DATA file. If you need to use them, it is normally wise to set the Dynamic Face Selection to \u0026ldquo;Show Both\u0026rdquo;. Dynamic Face Selection \u0026ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.\nThis option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.\nThis means that ResInsight turns on or off the faces based on your view position and this option to make sure that you always see the faces (and thus the result property) you request.  NNC Visibility  Show NNCs \u0026ndash; Toggles whether to display the Non Neighbor Connections, or not. Hide NNC geometry if no NNC result is available \u0026ndash; Automatically hides NNC geometry if no NNC results are available  The color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.\n\rFault Export Faults can be exported to separate files in the *grdecl file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.\nTo export some faults, select the faults you want to export in the Project Tree, and select the command Export Faults \u0026hellip; from the right-click menu.\nYou are then prompted to select a destination folder. Each Fault is exported to a file named Faults_\u0026lt;fault name\u0026gt;_\u0026lt;case name\u0026gt;.grdecl and stored in the selected folder.\nThe fault name of Undefined Grid Faults is simplified to UNDEF, while Undefined Grid Faults With Inactive is simplified to UNDEF_IA. All other faults keep their original name.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FaultsIllustration.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis section describes how Faults are detected and visualized. NNC\u0026rsquo;s are a part of the Faults visualization and are thus also mentioned in this section.\u003c/p\u003e\n\u003ch2 id=\"fault-detection\"\u003eFault Detection\u003c/h2\u003e\n\u003cp\u003eResInsight always scans the grids for geometrical faults when they are loaded. When two opposite cell faces of I, J, K neighbor cells does not match geometrically, they are tagged.\u003c/p\u003e\n\u003cp\u003eAll the tagged cell faces are then compared to the faults possibly imported from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file in order to group them. If a particular face is \u003cem\u003enot\u003c/em\u003e found among the fault faces defined in the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file (or their opposite faces), the cell face is added to one of two predefined faults:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined grid faults\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUndefined grid faults With Inactive\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe first fault is used if both the neighbor cells are active. If one or both of the neighbor cells are inactive, the second fault is used.\u003c/p\u003e\n\u003cp\u003eThese particular Faults will always be present, even when reading of fault information from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file is disabled.\u003c/p\u003e\n\u003ch3 id=\"information-from-data-files\"\u003eInformation from \u003ccode\u003e*.DATA\u003c/code\u003e-files\u003c/h3\u003e\n\u003ch4 id=\"fault-information\"\u003eFault Information\u003c/h4\u003e\n\u003cp\u003eIf enabled in \u003cstrong\u003ePreferences\u003c/strong\u003e, ResInsight will import fault information from the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e files and use this information to group the cell faces into named items. The imported faults are ordered in ascending order based on their name.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe \u003c!-- raw HTML omitted --\u003eDATA\u003c!-- raw HTML omitted --\u003e file is parsed for the \u003c!-- raw HTML omitted --\u003eFAULT\u003c!-- raw HTML omitted --\u003e keyword while respecting any \u003c!-- raw HTML omitted --\u003eINCLUDE\u003c!-- raw HTML omitted --\u003e and \u003c!-- raw HTML omitted --\u003ePATH\u003c!-- raw HTML omitted --\u003e keywords.\u003c!-- raw HTML omitted --\u003e\nAs import of faults can be time consuming, reading of faults can be disabled from \u003c!-- raw HTML omitted --\u003ePreferences-\u0026gt;Import faults\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"nnc-data\"\u003eNNC Data\u003c/h4\u003e\n\u003cp\u003eIf enabled in \u003cstrong\u003ePreferences\u003c/strong\u003e, ResInsight will read Non Neighbor Connections from the Eclipse output file (\u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e), and create explicit visualizations of those. \nThe NNC\u0026rsquo;s are sorted onto the Fault\u0026rsquo;s and their visibility is controlled along with them.\u003c/p\u003e\n\u003ch2 id=\"fault-visualization-options\"\u003eFault Visualization Options\u003c/h2\u003e\n\u003ch3 id=\"fault-visibility\"\u003eFault Visibility\u003c/h3\u003e\n\u003cp\u003eFaults can be hidden and shown in several ways.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eChecking or unchecking the checkbox in front of the fault will show or hide the fault.\u003c/li\u003e\n\u003cli\u003eVisibility for multiple faults can be controlled at the same time by selecting multiple faults and use the right-click menu: \u003cstrong\u003eOn\u003c/strong\u003e, \u003cstrong\u003eOff\u003c/strong\u003e and \u003cstrong\u003eToggle\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eHide the fault from the  right-click menu of a Fault in the 3D View.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"fault-color\"\u003eFault Color\u003c/h3\u003e\n\u003cp\u003eEach named Fault is given a color on import. This color can be controlled by selecting the fault and edit its  \u003cstrong\u003eFault color\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor.\u003c/strong\u003e\u003c/p\u003e\n\u003ch3 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h3\u003e\n\u003cp\u003eThe default result mapping used on faults are to use the same as specified in \u003cstrong\u003eCell Result\u003c/strong\u003e. If a different result mapping is wanted, enable the checkbox at \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e and select the result from the result selection dialog in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e. A second legend for the fault result is then added to the view.\u003c/p\u003e\n\u003ch3 id=\"toolbar-control\"\u003eToolbar Control\u003c/h3\u003e\n\u003cp\u003eVisualization mode and mesh lines can be controlled from the toolbar.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eFaults-Only\u003c/strong\u003e visualization mode. \n\u003c!-- raw HTML omitted --\u003eWhen turned on, this option hides all the grid cells, and shows only the fault faces in the reservoir limited by the applied range and property filters. (Unless \u003cstrong\u003eShow faults outside filters\u003c/strong\u003e are turned on. See below.)\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_surface_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Turns faces on and mesh off\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_surface_w_fault_mesh_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Turns on all faces, and shows mesh lines on faults only.\n\u003c!-- raw HTML omitted --\u003e This is a useful method to highlight the faults in your reservoir, because the faults stands out with black outlining.\u003c/li\u003e\n\u003cli\u003e\u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_label_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n Shows labels for faults\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"faults-properties\"\u003eFaults Properties\u003c/h3\u003e\n\u003cp\u003eBy clicking the \u003cimg src=\"https://resinsight.org/images/3d-main-window/draw_style_faults_24x24.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eFaults\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, the following options common to all the faults are displayed:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FaultProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch5 id=\"fault-labels\"\u003eFault Labels\u003c/h5\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow labels\u003c/strong\u003e \u0026ndash; Displays one label per fault with the name defined in the \u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel color\u003c/strong\u003e \u0026ndash; Defines the label color\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"fault-options\"\u003eFault Options\u003c/h5\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow faults outside filters\u003c/strong\u003e \u0026ndash; Turning this option on, will display faults outside the filter region, making the fault visualization completely ignore the Range and Property filters in action.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"fault-face-visibility\"\u003eFault Face Visibility\u003c/h5\u003e\n\u003cp\u003eThis group of options controls the visibility of the fault faces. Since they work together, and in some cases are overridden by the system, they can be a bit confusing.\u003c/p\u003e\n\u003cp\u003eFirst of all, these options are only available in \u003cstrong\u003eFaults-only\u003c/strong\u003e visualization mode ( See \u003ca href=\"#toolbar-control\"\u003eToolbar Control\u003c/a\u003e ). When not in \u003cstrong\u003eFaults-Only\u003c/strong\u003e mode, ResInsight overrides the options, and the controls are inactive.\u003c/p\u003e\n\u003cp\u003eSecondly, the option you would normally want to adjust is \u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e ( See below ).\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow defined faces\u003c/strong\u003e \u0026ndash; Displays the fault cell faces that are defined on the Eclipse input file (\u003cem\u003e\u003ccode\u003e*.DATA\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow opposite faces\u003c/strong\u003e \u0026ndash; Displays the opposite fault cell faces from what is defined on the input file, based on IJK neighbors.\u003cbr\u003e\n\u003cem\u003eThese two options should normally be left \u003cstrong\u003eOn\u003c/strong\u003e. They are useful when investigating the exact faults information provided on the \u003ccode\u003e*.DATA\u003c/code\u003e file. If you need to use them, it is normally wise to set the \u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e to \u0026ldquo;Show Both\u0026rdquo;.\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDynamic Face Selection\u003c/strong\u003e \u0026ndash; At one particular position on a fault there are usually two cells competing for your attention: The cell closer to you as the viewer, or the one further from you. When showing results, this becomes important because these two cell faces have different result property values, and thus color.\u003cbr\u003e\nThis option controls which of the two cell faces you actually can see: The one behind the fault, or the one in front of the fault. There is also an option of showing both, which will give you an undefined mixture, making it hard to be certain what you see.\u003cbr\u003e\nThis means that ResInsight turns on or off the faces based on your view position and this option to make sure that you always see the faces (and thus the result property) you request.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"nnc-visibility\"\u003eNNC Visibility\u003c/h5\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow NNCs\u003c/strong\u003e \u0026ndash; Toggles whether to display the Non Neighbor Connections, or not.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHide NNC geometry if no NNC result is available\u003c/strong\u003e \u0026ndash; Automatically hides NNC geometry if no NNC results are available\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eThe color of the NNC faces are set to be a bit lighter than their corresponding named fault, and can not be controlled directly.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"fault-export\"\u003eFault Export\u003c/h2\u003e\n\u003cp\u003eFaults can be exported to separate files in the \u003cem\u003e\u003ccode\u003e*grdecl\u003c/code\u003e\u003c/em\u003e file format. This is useful for example if you need a list of the geometrically detected faults that has not been covered by entries in the eclipse FAULTS keyword.\u003c/p\u003e\n\u003cp\u003eTo export some faults, select the faults you want to export in the \u003cstrong\u003eProject Tree\u003c/strong\u003e, and select the command \u003cstrong\u003eExport Faults \u0026hellip;\u003c/strong\u003e from the right-click menu.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ExportFaultsMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eYou are then prompted to select a destination folder. Each Fault is exported to a file named \u003cem\u003e\u003ccode\u003eFaults_\u0026lt;fault name\u0026gt;_\u0026lt;case name\u0026gt;.grdecl\u003c/code\u003e\u003c/em\u003e and stored in the selected folder.\u003c/p\u003e\n\u003cp\u003eThe fault name of \u003cstrong\u003eUndefined Grid Faults\u003c/strong\u003e is simplified to \u003cem\u003e\u003ccode\u003eUNDEF\u003c/code\u003e\u003c/em\u003e, while \u003cstrong\u003eUndefined Grid Faults With Inactive\u003c/strong\u003e is simplified to \u003cem\u003e\u003ccode\u003eUNDEF_IA\u003c/code\u003e\u003c/em\u003e. All other faults keep their original name.\u003c/p\u003e\n",
                 url:      "/3d-main-window/faults/"
             };
         
     
          
+            window.store["/getting-started/other/"] = {
+                title:    "Other",
+                content:  "",
+                html:     "",
+                url:      "/getting-started/other/"
+            };
+        
+    
+         
             window.store["/plot-window/rftplot/"] = {
                 title:    "RFT Plot",
-                content:  " An RFT (Repeated Formation Tester) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD) or measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed pressure data are loaded from well log files (*.las).\nCreate New RFT Plot There are several ways to create new RFT Plots.\nFrom the Project Tree in the Plot Main Window\n Select context command New RFT Plot for Well Path node or RFT Plots node.  From the Project Tree in the 3D Main Window\n Select context command New RFT plot for a simulation well.  From a 3D view\n Right-click a simulation well select Well Plots -\u0026gt; New RFT Plot.  Import Observed RFT Data To be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name PRESSURE or _PRESFORM. If the well log file itself does not contain a TVD column (named TVDMSL), a well path file (See Well Trajectories) for the same well must also be imported to ResInsight.\nIf no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.\nProperty Editor The property editor lets the user select which curves to display in the RFT plot.\nWell Name Select the well to display in the plot. Wells postfixed by \u0026rsquo;(Well Path)\u0026rsquo; have an associated well trajectory loaded.\nSources After a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:\n RFT File Cases \u0026ndash; Simulation cases may have associated formation pressure data in *.rft file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword WRFTPLT in the Eclipse manual for information). Grid Cases \u0026ndash; The PRESSURE property in the 3D grid. Observed Cases \u0026ndash; Observed data imported from well log files.  When the user selects one or more sources, a selection of their time steps appears in the Time Steps field.\nTime Steps The Time Steps field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\n If a single source or sources of the same type are selected, all available time steps in those sources are shown. If sources from two or tree types are selected, the time steps are filtered:  The time steps matching the observed case(s) time steps. If no time steps from a case match the observed time step, the two adjacent ones are shown. The first time step from any grid case(s) (as initial pressure reference). If the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.   Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: [ O ], [ R G ].\n O \u0026ndash; Time step has observed data R \u0026ndash; Time step has RFT data G \u0026ndash; Time step has Grid data  More than one letter for one single time step, means that the time steps comes from multiple case types.\nZonation/Formation Names This property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.\nPlease see the full documentation on the formations property editor for details about formations.\nWhen the formation names property editor is used in the context of RFT plots, the fields Trajectory and Simulation Well are hidden because those values are given by the RFT plot definition.\n\rLegend and Axis This property editor lets the user control visual properties for the legend and axis.\n Title and Legends  Show Title \u0026ndash; Toggle on/off title in plot Show Legends \u0026ndash; Toggle on/off legend in plot Legend Orientation \u0026ndash; Vertical or horizontal  X Axis Settings  Logarithmic Scale \u0026ndash; Toggle between linear and logarithmic Min \u0026ndash; Set X axis minimum value Max \u0026ndash; Set X axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot  Depth Axis  Type \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD) Unit \u0026ndash; Min \u0026ndash; Set depth axis minimum value Max \u0026ndash; Set depth axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot   ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAn RFT (\u003cem\u003eRepeated Formation Tester\u003c/em\u003e) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD) or measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed pressure data are loaded from well log files (*.las).\u003c/p\u003e\n\n\u003ch2 id=\"create-new-rft-plot\"\u003eCreate New RFT Plot\u003c/h2\u003e\n\n\u003cp\u003eThere are several ways to create new RFT Plots.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the Plot Main Window\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew RFT Plot\u003c/strong\u003e for \u003cem\u003eWell Path\u003c/em\u003e node or \u003cem\u003eRFT Plots\u003c/em\u003e node.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the 3D Main Window\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew RFT plot\u003c/strong\u003e for a simulation well.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom a 3D view\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eRight-click a simulation well select \u003cstrong\u003eWell Plots -\u0026gt; New RFT Plot\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"import-observed-rft-data\"\u003eImport Observed RFT Data\u003c/h2\u003e\n\n\u003cp\u003eTo be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name \u003cem\u003ePRESSURE\u003c/em\u003e or _PRES\u003cem\u003eFORM\u003c/em\u003e. If the well log file itself does not contain a TVD column (named \u003cem\u003eTVDMSL\u003c/em\u003e), a well path file (See \u003ca href=\"/wells-and-completions/wellpaths/\"\u003eWell Trajectories\u003c/a\u003e) for the same well must also be imported to ResInsight.\u003c/p\u003e\n\n\u003cp\u003eIf no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/NoTvdWarningDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\n\u003cp\u003eThe property editor lets the user select which curves to display in the RFT plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPlotPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\n\u003cp\u003eSelect the well to display in the plot. Wells postfixed by \u003cem\u003e\u0026rsquo;(Well Path)\u0026rsquo;\u003c/em\u003e have an associated well trajectory loaded.\u003c/p\u003e\n\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\n\u003cp\u003eAfter a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRFT File Cases\u003c/strong\u003e \u0026ndash; Simulation cases may have associated formation pressure data in \u003cem\u003e*.rft\u003c/em\u003e file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword \u003ccode\u003eWRFTPLT\u003c/code\u003e in the Eclipse manual for information).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Cases\u003c/strong\u003e \u0026ndash; The PRESSURE property in the 3D grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved Cases\u003c/strong\u003e \u0026ndash; Observed data imported from well log files.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen the user selects one or more sources, a selection of their time steps appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eIf a single source or sources of the same type are selected, all available time steps in those sources are shown.\u003c/li\u003e\n\u003cli\u003eIf sources from two or tree types are selected, the time steps are filtered:\n\n\u003cul\u003e\n\u003cli\u003eThe time steps matching the observed case(s) time steps.\u003c/li\u003e\n\u003cli\u003eIf no time steps from a case match the observed time step, the two adjacent ones are shown.\u003c/li\u003e\n\u003cli\u003eThe first time step from any grid case(s) (as initial pressure reference).\nIf the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eEach time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: \u003cstrong\u003e[ O ]\u003c/strong\u003e, \u003cstrong\u003e[ R G ]\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step has observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step has RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step has Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eMore than one letter for one single time step, means that the time steps comes from multiple case types.\u003c/p\u003e\n\n\u003ch3 id=\"zonation-formation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\n\u003cp\u003eThis property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPltFormationNames.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003ePlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e on the formations property editor for details about formations.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen the formation names property editor is used in the context of RFT plots, the fields \u003cb\u003eTrajectory\u003c/b\u003e and \u003cb\u003eSimulation Well\u003c/b\u003e are hidden because those values are given by the RFT plot definition.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftLegendAndAxis.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis property editor lets the user control visual properties for the legend and axis.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eTitle and Legends\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggle on/off title in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggle on/off legend in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Orientation\u003c/strong\u003e \u0026ndash; Vertical or horizontal\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eX Axis Settings\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e \u0026ndash; Toggle between linear and logarithmic\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set X axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set X axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eDepth Axis\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnit\u003c/strong\u003e \u0026ndash;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set depth axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set depth axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "An RFT (Repeated Formation Tester) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD) or measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed pressure data are loaded from well log files (*.las).\nCreate New RFT Plot There are several ways to create new RFT Plots.\nFrom the Project Tree in the Plot Main Window\n Select context command New RFT Plot for Well Path node or RFT Plots node.  From the Project Tree in the 3D Main Window\n Select context command New RFT plot for a simulation well.  From a 3D view\n Right-click a simulation well select Well Plots -\u0026gt; New RFT Plot.  Import Observed RFT Data To be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name PRESSURE or PRES_FORM. If the well log file itself does not contain a TVD column (named TVDMSL), a well path file (See Well Trajectories) for the same well must also be imported to ResInsight.\nIf no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.\nProperty Editor The property editor lets the user select which curves to display in the RFT plot.\nWell Name Select the well to display in the plot. Wells postfixed by '(Well Path)' have an associated well trajectory loaded.\nSources After a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:\n RFT File Cases \u0026ndash; Simulation cases may have associated formation pressure data in *.rft file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword WRFTPLT in the Eclipse manual for information). Grid Cases \u0026ndash; The PRESSURE property in the 3D grid. Observed Cases \u0026ndash; Observed data imported from well log files.  When the user selects one or more sources, a selection of their time steps appears in the Time Steps field.\nTime Steps The Time Steps field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\n If a single source or sources of the same type are selected, all available time steps in those sources are shown. If sources from two or tree types are selected, the time steps are filtered:   The time steps matching the observed case(s) time steps. If no time steps from a case match the observed time step, the two adjacent ones are shown. The first time step from any grid case(s) (as initial pressure reference). If the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.  Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: [ O ], [ R G ].\n O \u0026ndash; Time step has observed data R \u0026ndash; Time step has RFT data G \u0026ndash; Time step has Grid data  More than one letter for one single time step, means that the time steps comes from multiple case types.\nZonation/Formation Names This property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.\nPlease see the full documentation on the formations property editor for details about formations.\nWhen the formation names property editor is used in the context of RFT plots, the fields Trajectoryand Simulation Wellare hidden because those values are given by the RFT plot definition.\n\rLegend and Axis This property editor lets the user control visual properties for the legend and axis.\n Title and Legends  Show Title \u0026ndash; Toggle on/off title in plot Show Legends \u0026ndash; Toggle on/off legend in plot Legend Orientation \u0026ndash; Vertical or horizontal   X Axis Settings  Logarithmic Scale \u0026ndash; Toggle between linear and logarithmic Min \u0026ndash; Set X axis minimum value Max \u0026ndash; Set X axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot   Depth Axis  Type \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD) Unit \u0026ndash; Min \u0026ndash; Set depth axis minimum value Max \u0026ndash; Set depth axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot    ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn RFT (\u003cem\u003eRepeated Formation Tester\u003c/em\u003e) plot is a special well plot for comparing observed formation pressure and simulated formation pressure. The curves are plotted as pressure against true vertical depth (TVD) or measured depth (MD). Simulated pressure data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed pressure data are loaded from well log files (*.las).\u003c/p\u003e\n\u003ch2 id=\"create-new-rft-plot\"\u003eCreate New RFT Plot\u003c/h2\u003e\n\u003cp\u003eThere are several ways to create new RFT Plots.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the Plot Main Window\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew RFT Plot\u003c/strong\u003e for \u003cem\u003eWell Path\u003c/em\u003e node or \u003cem\u003eRFT Plots\u003c/em\u003e node.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the 3D Main Window\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew RFT plot\u003c/strong\u003e for a simulation well.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eFrom a 3D view\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eRight-click a simulation well select \u003cstrong\u003eWell Plots -\u0026gt; New RFT Plot\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"import-observed-rft-data\"\u003eImport Observed RFT Data\u003c/h2\u003e\n\u003cp\u003eTo be able to plot observed pressure data for a well in an RFT plot, at least one well log file from that well (e.g. *.las) has to be imported to ResInsight. This file must contain a pressure column, which must have the name \u003cem\u003ePRESSURE\u003c/em\u003e or \u003cem\u003ePRES_FORM\u003c/em\u003e. If the well log file itself does not contain a TVD column (named \u003cem\u003eTVDMSL\u003c/em\u003e), a well path file (See \u003ca href=\"/wells-and-completions/wellpaths/\"\u003eWell Trajectories\u003c/a\u003e) for the same well must also be imported to ResInsight.\u003c/p\u003e\n\u003cp\u003eIf no TVD data for a well is found when the user tries to plot a curve, ResInsight will present a warning dialog to the user.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/NoTvdWarningDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe property editor lets the user select which curves to display in the RFT plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\u003cp\u003eSelect the well to display in the plot. Wells postfixed by \u003cem\u003e'(Well Path)'\u003c/em\u003e have an associated well trajectory loaded.\u003c/p\u003e\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\u003cp\u003eAfter a well has been selected in the Well Name field, the relevant sources for that well will appear in the sources field. The sources are placed in one of three different groups:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRFT File Cases\u003c/strong\u003e \u0026ndash; Simulation cases may have associated formation pressure data in \u003cem\u003e*.rft\u003c/em\u003e file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword \u003ccode\u003eWRFTPLT\u003c/code\u003e in the Eclipse manual for information).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Cases\u003c/strong\u003e \u0026ndash; The PRESSURE property in the 3D grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved Cases\u003c/strong\u003e \u0026ndash; Observed data imported from well log files.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen the user selects one or more sources, a selection of their time steps appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eIf a single source or sources of the same type are selected, all available time steps in those sources are shown.\u003c/li\u003e\n\u003cli\u003eIf sources from two or tree types are selected, the time steps are filtered:\u003c/li\u003e\n\u003c/ol\u003e\n\u003cul\u003e\n\u003cli\u003eThe time steps matching the observed case(s) time steps.\u003c/li\u003e\n\u003cli\u003eIf no time steps from a case match the observed time step, the two adjacent ones are shown.\u003c/li\u003e\n\u003cli\u003eThe first time step from any grid case(s) (as initial pressure reference).\nIf the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEach time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: \u003cstrong\u003e[ O ]\u003c/strong\u003e, \u003cstrong\u003e[ R G ]\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step has observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step has RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step has Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eMore than one letter for one single time step, means that the time steps comes from multiple case types.\u003c/p\u003e\n\u003ch3 id=\"zonationformation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\u003cp\u003eThis property editor lets the user control the visibility of formations lines. This is what it looks like in the RFT plot context.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPltFormationNames.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003ePlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e on the formations property editor for details about formations.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen the formation names property editor is used in the context of RFT plots, the fields \u003c!-- raw HTML omitted --\u003eTrajectory\u003c!-- raw HTML omitted --\u003e and \u003c!-- raw HTML omitted --\u003eSimulation Well\u003c!-- raw HTML omitted --\u003e are hidden because those values are given by the RFT plot definition.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftLegendAndAxis.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis property editor lets the user control visual properties for the legend and axis.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eTitle and Legends\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggle on/off title in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggle on/off legend in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Orientation\u003c/strong\u003e \u0026ndash; Vertical or horizontal\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eX Axis Settings\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e \u0026ndash; Toggle between linear and logarithmic\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set X axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set X axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eDepth Axis\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnit\u003c/strong\u003e \u0026ndash;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set depth axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set depth axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/rftplot/"
             };
         
@@ -2442,8 +2484,8 @@ if (!doNotTrack) {
          
             window.store["/export/contourmapexport/"] = {
                 title:    "Contour Map Export",
-                content:  " ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.\nExport of Contour Map Data To export a contour map, invoke one of the following options (c.f. figure above):\n Select context command Export Contour Map to text in the graphics window showing a contour map. Select context command Export Contour Map to text for a contour map in the Project Tree  This initiates the following dialog for export options:\nAs seen, the dialog facilitates the following options:\n Setting the file name for export. Export of local coordinates, i.e. coordinates measured from local origo defined in lower, left corner of contour map. Default is export of full UTM coordinates. Defining a text label to exclude undefined values. Default label is NaN. Exclude undefined values based on the given label.  Export file format The file format for export of contour maps supports use of Python and numpy. For instance, an exported file may can be imported into numpy using the loadtxt() function.\nMetadata is included as comments in the beginning of the file. The character # as first character denotes a comment line.\nIf local coordinates are exported, the UTM coordinate offset is included as a comment in the header of the export file (c.f. example file below). To anonymize the data, the UTM coordinate offset may be removed from file.\nExample file:\n# case name : 1_R001_REEK-0 # sampling points : nx=90 ny=100 # time and date : 01.Jan 2000 # property name : Arithmetic Mean, PRESSURE # UTM offset : x=456256 y=5.92663e+06 x y value 5209.20099 254.10737 341.09308 5336.25467 254.10737 341.13252 5463.30835 254.10737 341.36091 5590.36204 254.10737 341.62615 5717.41572 254.10737 341.70246 5082.14731 381.16105 340.56455 5209.20099 381.16105 340.79087 5336.25467 381.16105 341.02580 5463.30835 381.16105 341.40061 5590.36204 381.16105 341.86177 5717.41572 381.16105 342.34527 ... ... ...  Python interface for export of contour maps The ResInsight Python Interface allows the user to access all contour maps belonging to a project. A Python script for exporting contour maps to a text file is included as one of the Python examples.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMap.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight can create \u003ca href=\"/3d-main-window/contourmaps/\"\u003econtour maps\u003c/a\u003e based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.\u003c/p\u003e\n\n\u003ch2 id=\"export-of-contour-map-data\"\u003eExport of Contour Map Data\u003c/h2\u003e\n\n\u003cp\u003eTo export a contour map, invoke one of the following options (c.f. figure above):\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e in the graphics window showing a contour map.\u003c/li\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e for a contour map in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThis initiates the following dialog for export options:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMapDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eAs seen, the dialog facilitates the following options:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSetting the file name for export.\u003c/li\u003e\n\u003cli\u003eExport of local coordinates, i.e. coordinates measured from local origo defined in lower, left corner of contour map. Default is export of full UTM coordinates.\u003c/li\u003e\n\u003cli\u003eDefining a text label to exclude undefined values. Default label is \u003cem\u003eNaN\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eExclude undefined values based on the given label.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"export-file-format\"\u003eExport file format\u003c/h2\u003e\n\n\u003cp\u003eThe file format for export of contour maps supports use of Python and numpy. For instance, an exported file may can be imported into numpy using the \u003cem\u003eloadtxt()\u003c/em\u003e function.\u003c/p\u003e\n\n\u003cp\u003eMetadata is included as comments in the beginning of the file. The character \u003cem\u003e#\u003c/em\u003e as first character denotes a comment line.\u003c/p\u003e\n\n\u003cp\u003eIf local coordinates are exported, the UTM coordinate offset is included as a comment in the header of the export file (c.f. example file below).\nTo anonymize the data, the UTM coordinate offset may be removed from file.\u003c/p\u003e\n\n\u003cp\u003eExample file:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e# case name : 1_R001_REEK-0\n# sampling points : nx=90 ny=100\n# time and date : 01.Jan 2000\n# property name : Arithmetic Mean, PRESSURE\n# UTM offset : x=456256 y=5.92663e+06\n\nx               y               value    \n5209.20099      254.10737       341.09308\n5336.25467      254.10737       341.13252\n5463.30835      254.10737       341.36091\n5590.36204      254.10737       341.62615\n5717.41572      254.10737       341.70246\n5082.14731      381.16105       340.56455\n5209.20099      381.16105       340.79087\n5336.25467      381.16105       341.02580\n5463.30835      381.16105       341.40061\n5590.36204      381.16105       341.86177\n5717.41572      381.16105       342.34527\n...             ...             ...\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch2 id=\"python-interface-for-export-of-contour-maps\"\u003ePython interface for export of contour maps\u003c/h2\u003e\n\n\u003cp\u003eThe \u003ca href=\"/scripting/pythonrips/\"\u003eResInsight Python Interface\u003c/a\u003e\nallows the user to\n\u003ca href=\"/scripting/pythonrips/#contour-maps-map-type-contourmaptype-eclipse-1\"\u003eaccess all contour maps\u003c/a\u003e belonging to a project.\nA \u003ca href=\"/scripting/pythonrips/\"\u003ePython script\u003c/a\u003e for exporting contour maps to a text file is included as one of the \u003ca href=\"/scripting/pythonexamples/\"\u003ePython examples\u003c/a\u003e.\u003c/p\u003e\n",
+                content:  "ResInsight can create contour maps based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.\nExport of Contour Map Data To export a contour map, invoke one of the following options (c.f. figure above):\n Select context command Export Contour Map to text in the graphics window showing a contour map. Select context command Export Contour Map to text for a contour map in the Project Tree  This initiates the following dialog for export options:\nAs seen, the dialog facilitates the following options:\n Setting the file name for export. Export of local coordinates, i.e. coordinates measured from local origo defined in lower, left corner of contour map. Default is export of full UTM coordinates. Defining a text label to exclude undefined values. Default label is NaN. Exclude undefined values based on the given label.  Export file format The file format for export of contour maps supports use of Python and numpy. For instance, an exported file may can be imported into numpy using the loadtxt() function.\nMetadata is included as comments in the beginning of the file. The character # as first character denotes a comment line.\nIf local coordinates are exported, the UTM coordinate offset is included as a comment in the header of the export file (c.f. example file below). To anonymize the data, the UTM coordinate offset may be removed from file.\nExample file:\n# case name : 1_R001_REEK-0\r# sampling points : nx=90 ny=100\r# time and date : 01.Jan 2000\r# property name : Arithmetic Mean, PRESSURE\r# UTM offset : x=456256 y=5.92663e+06\rx y value 5209.20099 254.10737 341.09308\r5336.25467 254.10737 341.13252\r5463.30835 254.10737 341.36091\r5590.36204 254.10737 341.62615\r5717.41572 254.10737 341.70246\r5082.14731 381.16105 340.56455\r5209.20099 381.16105 340.79087\r5336.25467 381.16105 341.02580\r5463.30835 381.16105 341.40061\r5590.36204 381.16105 341.86177\r5717.41572 381.16105 342.34527\r... ... ...\rPython interface for export of contour maps The [ResInsight Python Interface] (/scripting/pythonrips/) allows the user to access all contour maps belonging to a project. A Python script for exporting contour maps to a text file is included as one of the [Python examples] (/scripting/pythonexamples/).\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMap.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can create \u003ca href=\"/3d-main-window/contourmaps/\"\u003econtour maps\u003c/a\u003e based on different forms of aggregation of 3D Eclipse data onto a 2D Plane. Any 3D result value can be aggregated, in addition to specialised results, such as oil, gas and hydrocarbon columns. A Contour Map is a specialised 2D view with many of the same features as the 3D views, including property filters, range filters and display of faults and wells.\u003c/p\u003e\n\u003ch2 id=\"export-of-contour-map-data\"\u003eExport of Contour Map Data\u003c/h2\u003e\n\u003cp\u003eTo export a contour map, invoke one of the following options (c.f. figure above):\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e in the graphics window showing a contour map.\u003c/li\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e for a contour map in the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThis initiates the following dialog for export options:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/export/ExportContourMapDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs seen, the dialog facilitates the following options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSetting the file name for export.\u003c/li\u003e\n\u003cli\u003eExport of local coordinates, i.e. coordinates measured from local origo defined in lower, left corner of contour map. Default is export of full UTM coordinates.\u003c/li\u003e\n\u003cli\u003eDefining a text label to exclude undefined values. Default label is \u003cem\u003eNaN\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003eExclude undefined values based on the given label.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"export-file-format\"\u003eExport file format\u003c/h2\u003e\n\u003cp\u003eThe file format for export of contour maps supports use of Python and numpy. For instance, an exported file may can be imported into numpy using the \u003cem\u003eloadtxt()\u003c/em\u003e function.\u003c/p\u003e\n\u003cp\u003eMetadata is included as comments in the beginning of the file. The character \u003cem\u003e#\u003c/em\u003e as first character denotes a comment line.\u003c/p\u003e\n\u003cp\u003eIf local coordinates are exported, the UTM coordinate offset is included as a comment in the header of the export file (c.f. example file below).\nTo anonymize the data, the UTM coordinate offset may be removed from file.\u003c/p\u003e\n\u003cp\u003eExample file:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e# case name : 1_R001_REEK-0\r\n# sampling points : nx=90 ny=100\r\n# time and date : 01.Jan 2000\r\n# property name : Arithmetic Mean, PRESSURE\r\n# UTM offset : x=456256 y=5.92663e+06\r\n\r\nx               y               value    \r\n5209.20099      254.10737       341.09308\r\n5336.25467      254.10737       341.13252\r\n5463.30835      254.10737       341.36091\r\n5590.36204      254.10737       341.62615\r\n5717.41572      254.10737       341.70246\r\n5082.14731      381.16105       340.56455\r\n5209.20099      381.16105       340.79087\r\n5336.25467      381.16105       341.02580\r\n5463.30835      381.16105       341.40061\r\n5590.36204      381.16105       341.86177\r\n5717.41572      381.16105       342.34527\r\n...             ...             ...\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch2 id=\"python-interface-for-export-of-contour-maps\"\u003ePython interface for export of contour maps\u003c/h2\u003e\n\u003cp\u003eThe [ResInsight Python Interface] (/scripting/pythonrips/)\nallows the user to \n\u003ca href=\"/scripting/pythonrips/\"\u003eaccess all contour maps\u003c/a\u003e belonging to a project.\nA \u003ca href=\"/scripting/pythonrips/\"\u003ePython script\u003c/a\u003e for exporting contour maps to a text file is included as one of the [Python examples]\n(/scripting/pythonexamples/).\u003c/p\u003e\n",
                 url:      "/export/contourmapexport/"
             };
         
@@ -2451,8 +2493,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/ensemblerftplot/"] = {
                 title:    "Ensemble RFT Plot",
-                content:  " ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. The functionality also computes statistics, e.g. P10, P90, and mean. When possible, ResInsight avoids loading the grid when reading ensemble RFT data.\nCreate New Ensemble RFT Plot When a summary ensemble has been imported, observed FMU data can be imported via right-clicking Observed Data in the Plot Project Tree, and selecting Import Observed FMU Data.\nTo create ensemble RFT plot, right-click RFT Plots and select New RFT Plot.\nProperty Editor The property editor lets the user select which curves to display in the RFT plot.\nWell Name Select the well to display in the plot. Wells postfixed by \u0026rsquo;(Well Path)\u0026rsquo; have an associated well trajectory loaded.\nSources Subsequent to selecting a well in the Well Name field, the relevant sources for that well will appear in the Sources field. The sources for this particular case are:\n Ensembles with RFT Data \u0026ndash; List of ensembles which contain RFT data with check-boxes to activate display. Observed FMU data \u0026ndash; Observed data imported from a FMU run.  When the user selects one or more sources, a selection of their time steps appears in the Time Steps field.\nTime Steps The Time Steps field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\n If a single source or sources of the same type are selected, all available time steps in those sources are shown. If sources from two or tree types are selected, the time steps are filtered:  The time steps matching the observed case(s) time steps. If no time steps from a case match the observed time step, the two adjacent ones are shown. The first time step from any grid case(s) (as initial pressure reference). If the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.   Each time step is postfixed by letter(s) to indicate source type(s) of each time step. The source types are indicated in square brackets:\n O \u0026ndash; Time step has Observed data E \u0026ndash; Time step has Ensemble data R \u0026ndash; Time step has RFT data G \u0026ndash; Time step has Grid data  More than one letter for one single time step, means that the time step comes from multiple case types.\nZonation/Formation Names The display of formations lines is controlled in the same manner as for RFT plots. Please see the full documentation of the formations property editor for details about formations.\nLegend and Axis Visual properties of legend and axes is controlled in the same manner as for RFT plots.\nImport of Observed Ensemble RFT data from FMU Observed RFT data as part of a FMU run is presupposed to be located in a folder which contains the following four file types:\n layer_zone_table.txt \u0026lt;well_name\u0026gt;.obs \u0026lt;well_name\u0026gt;.txt well_date_rft.txt  The purpose and format of the data files is explained below.\nThe data file well_date_rft.txt is required. If missing, no Observed FMU data will be imported.\n\rCorrelation of grid and formations The file layer_zone_table.txt can be used to correlate each grid k-layer with a formation name. This file is identical for all cases in the same ensemble.\nExample file layer_zone_table.txt:\n1 UpperReek 2 UpperReek 3 UpperReek 4 UpperReek 5 UpperReek 6 MidReek 7 MidReek 8 MidReek 9 MidReek 10 MidReek 11 LowerReek 12 LowerReek 13 LowerReek 14 LowerReek  Observed pressure and error For a given well name, the file \u0026lt;well_name\u0026gt;.obs is a data file containing two columns to specify observed pressure and error. Column one contains observed pressure and column two contains error. The observation data is valid for one and only one layer/formation.\nExample file for well OP_1, i.e. OP_1.obs:\n303.000 3.000 304.000 3.000 305.000 3.000  Reservoir zone name For a given well name, the file \u0026lt;well_name\u0026gt;.txt is a data file containing five columns that specify its correlation with reservoir zones. Each line of data must contain:\n Utmx: x-coordinate in UTM Utmy: y-coordinate in UTM Measured Depth relative to the Kelly Bushing (MDRKB) True Vertical Depth referenced to Mean Sea Level (TVDMSL) Reservoir zone name  Example file for well OP_1, i.e. OP_1.txt:\n461288.719 5933415.000 1816.200 1611.692 UpperReek 461288.685 5933415.027 1824.560 1620.052 MidReek 461288.683 5933415.029 1840.000 1635.492 LowerReek  Well measurements The data file well_date_rft.txt contains well measurements. The file contains four columns for each well measurement:\n Well Name Date in two digit form \u0026lt;DD\u0026gt; Month in two digit form \u0026lt;MM\u0026gt; Year in four digit form \u0026lt;YYYY\u0026gt; Measurement index  There can be multiple measurement for each well.\nExample file well_date_rft.txt:\nOP_1 01 02 2000 1 OP_2 01 02 2000 1 OP_4 01 01 2001 1 WI_1 01 02 2000 1 WI_3 01 03 2001 1  ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots.\nThe functionality also computes statistics, e.g. P10, P90, and mean.\nWhen possible, ResInsight avoids loading the grid when reading ensemble RFT data.\u003c/p\u003e\n\n\u003ch2 id=\"create-new-ensemble-rft-plot\"\u003eCreate New Ensemble RFT Plot\u003c/h2\u003e\n\n\u003cp\u003eWhen a \u003ca href=\"/plot-window/ensembleplotting/#import\"\u003esummary ensemble has been imported\u003c/a\u003e,\nobserved FMU data can be imported via right-clicking \u003cstrong\u003eObserved Data\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e,\nand selecting \u003cstrong\u003eImport Observed FMU Data\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftImportObservedData.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eTo create ensemble RFT plot, right-click \u003cstrong\u003eRFT Plots\u003c/strong\u003e and select \u003cstrong\u003eNew RFT Plot\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftNewRftPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\n\u003cp\u003eThe property editor lets the user select which curves to display in the RFT plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\n\u003cp\u003eSelect the well to display in the plot. Wells postfixed by \u003cem\u003e\u0026rsquo;(Well Path)\u0026rsquo;\u003c/em\u003e have an associated well trajectory loaded.\u003c/p\u003e\n\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\n\u003cp\u003eSubsequent to selecting a well in the Well Name field, the relevant sources for that well will appear in the \u003cstrong\u003eSources\u003c/strong\u003e field. The sources for this particular case are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eEnsembles with RFT Data\u003c/strong\u003e \u0026ndash; List of ensembles which contain RFT data with check-boxes to activate display.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved FMU data\u003c/strong\u003e \u0026ndash; Observed data imported from a FMU run.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen the user selects one or more sources, a selection of their time steps appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eIf a single source or sources of the same type are selected, all available time steps in those sources are shown.\u003c/li\u003e\n\u003cli\u003eIf sources from two or tree types are selected, the time steps are filtered:\n\n\u003cul\u003e\n\u003cli\u003eThe time steps matching the observed case(s) time steps.\u003c/li\u003e\n\u003cli\u003eIf no time steps from a case match the observed time step, the two adjacent ones are shown.\u003c/li\u003e\n\u003cli\u003eThe first time step from any grid case(s) (as initial pressure reference).\nIf the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eEach time step is postfixed by letter(s) to indicate source type(s) of each time step. The source types are indicated in square brackets:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step has Observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eE\u003c/strong\u003e \u0026ndash; Time step has Ensemble data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step has RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step has Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eMore than one letter for one single time step, means that the time step comes from multiple case types.\u003c/p\u003e\n\n\u003ch3 id=\"zonation-formation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\n\u003cp\u003eThe display of formations lines is controlled in the same manner as for \u003ca href=\"/plot-window/rftplot/#zonation-formation-names\"\u003eRFT plots\u003c/a\u003e.\nPlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e of the formations property editor for details about formations.\u003c/p\u003e\n\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\n\u003cp\u003eVisual properties of legend and axes is controlled in the same manner as for \u003ca href=\"/plot-window/rftplot/#legend-and-axis\"\u003eRFT plots\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"import-of-observed-ensemble-rft-data-from-fmu\"\u003eImport of Observed Ensemble RFT data from FMU\u003c/h2\u003e\n\n\u003cp\u003eObserved RFT data as part of a FMU run is presupposed to be located in a folder which contains the following four file types:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003elayer_zone_table.txt\u003c/li\u003e\n\u003cli\u003e\u0026lt;\u003cem\u003ewell_name\u003c/em\u003e\u0026gt;.obs\u003c/li\u003e\n\u003cli\u003e\u0026lt;\u003cem\u003ewell_name\u003c/em\u003e\u0026gt;.txt\u003c/li\u003e\n\u003cli\u003ewell_date_rft.txt\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe purpose and format of the data files is explained below.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe data file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e is required. If missing, no Observed FMU data will be imported.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch4 id=\"correlation-of-grid-and-formations\"\u003eCorrelation of grid and formations\u003c/h4\u003e\n\n\u003cp\u003eThe file \u003cem\u003elayer_zone_table.txt\u003c/em\u003e can be used to correlate each grid k-layer with a formation name.\nThis file is identical for all cases in the same ensemble.\u003c/p\u003e\n\n\u003cp\u003eExample file \u003cem\u003elayer_zone_table.txt\u003c/em\u003e:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e1   UpperReek\n2   UpperReek\n3   UpperReek\n4   UpperReek\n5   UpperReek\n6   MidReek\n7   MidReek\n8   MidReek\n9   MidReek\n10  MidReek\n11  LowerReek\n12  LowerReek\n13  LowerReek\n14  LowerReek\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"observed-pressure-and-error\"\u003eObserved pressure and error\u003c/h4\u003e\n\n\u003cp\u003eFor a given well name, the file \u003cem\u003e\u0026lt;well_name\u0026gt;.obs\u003c/em\u003e is a data file containing two columns to specify observed pressure and error.\nColumn one contains observed pressure and column two contains error. The observation data is valid for one and only one layer/formation.\u003c/p\u003e\n\n\u003cp\u003eExample file  for well \u003cem\u003eOP_1\u003c/em\u003e, i.e. \u003cem\u003eOP_1.obs\u003c/em\u003e:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e303.000   3.000\n304.000   3.000\n305.000   3.000\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"reservoir-zone-name\"\u003eReservoir zone name\u003c/h4\u003e\n\n\u003cp\u003eFor a given well name, the file \u003cem\u003e\u0026lt;well_name\u0026gt;.txt\u003c/em\u003e is a data file containing five columns that specify its correlation with reservoir zones.\nEach line of data must contain:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eUtmx: x-coordinate in UTM\u003c/li\u003e\n\u003cli\u003eUtmy: y-coordinate in UTM\u003c/li\u003e\n\u003cli\u003eMeasured Depth relative to the Kelly Bushing (MDRKB)\u003c/li\u003e\n\u003cli\u003eTrue Vertical Depth referenced to Mean Sea Level (TVDMSL)\u003c/li\u003e\n\u003cli\u003eReservoir zone name\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eExample file for well \u003cem\u003eOP_1\u003c/em\u003e, i.e. \u003cem\u003eOP_1.txt\u003c/em\u003e:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e461288.719   5933415.000   1816.200   1611.692   UpperReek\n461288.685   5933415.027   1824.560   1620.052   MidReek\n461288.683   5933415.029   1840.000   1635.492   LowerReek\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"well-measurements\"\u003eWell measurements\u003c/h4\u003e\n\n\u003cp\u003eThe data file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e contains well measurements. The file contains four columns for each well measurement:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eWell Name\u003c/li\u003e\n\u003cli\u003eDate in two digit form \u0026lt;DD\u0026gt;\u003c/li\u003e\n\u003cli\u003eMonth in two digit form \u0026lt;MM\u0026gt;\u003c/li\u003e\n\u003cli\u003eYear in four digit form \u0026lt;YYYY\u0026gt;\u003c/li\u003e\n\u003cli\u003eMeasurement index\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThere can be multiple measurement for each well.\u003c/p\u003e\n\n\u003cp\u003eExample file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eOP_1   01 02 2000   1\nOP_2   01 02 2000   1\nOP_4   01 01 2001   1\nWI_1   01 02 2000   1\nWI_3   01 03 2001   1\n\u003c/code\u003e\u003c/pre\u003e\n",
+                content:  "ResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. The functionality also computes statistics, e.g. P10, P90, and mean. When possible, ResInsight avoids loading the grid when reading ensemble RFT data.\nCreate New Ensemble RFT Plot When a summary ensemble has been imported, observed FMU data can be imported via right-clicking Observed Data in the Plot Project Tree, and selecting Import Observed FMU Data.\nTo create ensemble RFT plot, right-click RFT Plots and select New RFT Plot.\nProperty Editor The property editor lets the user select which curves to display in the RFT plot.\nWell Name Select the well to display in the plot. Wells postfixed by '(Well Path)' have an associated well trajectory loaded.\nSources Subsequent to selecting a well in the Well Name field, the relevant sources for that well will appear in the Sources field. The sources for this particular case are:\n Ensembles with RFT Data \u0026ndash; List of ensembles which contain RFT data with check-boxes to activate display. Observed FMU data \u0026ndash; Observed data imported from a FMU run.  When the user selects one or more sources, a selection of their time steps appears in the Time Steps field.\nTime Steps The Time Steps field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\n If a single source or sources of the same type are selected, all available time steps in those sources are shown. If sources from two or tree types are selected, the time steps are filtered:   The time steps matching the observed case(s) time steps. If no time steps from a case match the observed time step, the two adjacent ones are shown. The first time step from any grid case(s) (as initial pressure reference). If the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.  Each time step is postfixed by letter(s) to indicate source type(s) of each time step. The source types are indicated in square brackets:\n O \u0026ndash; Time step has Observed data E \u0026ndash; Time step has Ensemble data R \u0026ndash; Time step has RFT data G \u0026ndash; Time step has Grid data  More than one letter for one single time step, means that the time step comes from multiple case types.\nZonation/Formation Names The display of formations lines is controlled in the same manner as for RFT plots. Please see the full documentation of the formations property editor for details about formations.\nLegend and Axis Visual properties of legend and axes is controlled in the same manner as for RFT plots.\nImport of Observed Ensemble RFT data from FMU Observed RFT data as part of a FMU run is presupposed to be located in a folder which contains the following four file types:\n layer_zone_table.txt \u0026lt;well_name\u0026gt;.obs \u0026lt;well_name\u0026gt;.txt well_date_rft.txt  The purpose and format of the data files is explained below.\nThe data file well_date_rft.txt is required. If missing, no Observed FMU data will be imported.\n\rCorrelation of grid and formations The file layer_zone_table.txt can be used to correlate each grid k-layer with a formation name. This file is identical for all cases in the same ensemble.\nExample file layer_zone_table.txt:\n1 UpperReek\r2 UpperReek\r3 UpperReek\r4 UpperReek\r5 UpperReek\r6 MidReek\r7 MidReek\r8 MidReek\r9 MidReek\r10 MidReek\r11 LowerReek\r12 LowerReek\r13 LowerReek\r14 LowerReek\rObserved pressure and error For a given well name, the file \u0026lt;well_name\u0026gt;.obs is a data file containing two columns to specify observed pressure and error. Column one contains observed pressure and column two contains error. The observation data is valid for one and only one layer/formation.\nExample file for well OP_1, i.e. OP_1.obs:\n303.000 3.000\r304.000 3.000\r305.000 3.000\rReservoir zone name For a given well name, the file \u0026lt;well_name\u0026gt;.txt is a data file containing five columns that specify its correlation with reservoir zones. Each line of data must contain:\n Utmx: x-coordinate in UTM Utmy: y-coordinate in UTM Measured Depth relative to the Kelly Bushing (MDRKB) True Vertical Depth referenced to Mean Sea Level (TVDMSL) Reservoir zone name  Example file for well OP_1, i.e. OP_1.txt:\n461288.719 5933415.000 1816.200 1611.692 UpperReek\r461288.685 5933415.027 1824.560 1620.052 MidReek\r461288.683 5933415.029 1840.000 1635.492 LowerReek\rWell measurements The data file well_date_rft.txt contains well measurements. The file contains four columns for each well measurement:\n Well Name Date in two digit form \u0026lt;DD\u0026gt; Month in two digit form \u0026lt;MM\u0026gt; Year in four digit form \u0026lt;YYYY\u0026gt; Measurement index  There can be multiple measurement for each well.\nExample file well_date_rft.txt:\nOP_1 01 02 2000 1\rOP_2 01 02 2000 1\rOP_4 01 01 2001 1\rWI_1 01 02 2000 1\rWI_3 01 03 2001 1\r",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight allows the user to create a ensemble RFT plot similar to summary ensemble plots. \nThe functionality also computes statistics, e.g. P10, P90, and mean.\nWhen possible, ResInsight avoids loading the grid when reading ensemble RFT data.\u003c/p\u003e\n\u003ch2 id=\"create-new-ensemble-rft-plot\"\u003eCreate New Ensemble RFT Plot\u003c/h2\u003e\n\u003cp\u003eWhen a \u003ca href=\"/plot-window/ensembleplotting/#import\"\u003esummary ensemble has been imported\u003c/a\u003e,\nobserved FMU data can be imported via right-clicking \u003cstrong\u003eObserved Data\u003c/strong\u003e in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e, \nand selecting \u003cstrong\u003eImport Observed FMU Data\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftImportObservedData.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo create ensemble RFT plot, right-click \u003cstrong\u003eRFT Plots\u003c/strong\u003e and select \u003cstrong\u003eNew RFT Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftNewRftPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe property editor lets the user select which curves to display in the RFT plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\u003cp\u003eSelect the well to display in the plot. Wells postfixed by \u003cem\u003e'(Well Path)'\u003c/em\u003e have an associated well trajectory loaded.\u003c/p\u003e\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\u003cp\u003eSubsequent to selecting a well in the Well Name field, the relevant sources for that well will appear in the \u003cstrong\u003eSources\u003c/strong\u003e field. The sources for this particular case are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eEnsembles with RFT Data\u003c/strong\u003e \u0026ndash; List of ensembles which contain RFT data with check-boxes to activate display.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved FMU data\u003c/strong\u003e \u0026ndash; Observed data imported from a FMU run.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen the user selects one or more sources, a selection of their time steps appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains the relevant time steps according to the source selection. Time steps are deemed to be relevant by the following rules:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eIf a single source or sources of the same type are selected, all available time steps in those sources are shown.\u003c/li\u003e\n\u003cli\u003eIf sources from two or tree types are selected, the time steps are filtered:\u003c/li\u003e\n\u003c/ol\u003e\n\u003cul\u003e\n\u003cli\u003eThe time steps matching the observed case(s) time steps.\u003c/li\u003e\n\u003cli\u003eIf no time steps from a case match the observed time step, the two adjacent ones are shown.\u003c/li\u003e\n\u003cli\u003eThe first time step from any grid case(s) (as initial pressure reference).\nIf the Observed data isn\u0026rsquo;t selected, the RFT data serves as filter reference.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEach time step is postfixed by letter(s) to indicate source type(s) of each time step. The source types are indicated in square brackets:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step has Observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eE\u003c/strong\u003e \u0026ndash; Time step has Ensemble data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step has RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step has Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eMore than one letter for one single time step, means that the time step comes from multiple case types.\u003c/p\u003e\n\u003ch3 id=\"zonationformation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\u003cp\u003eThe display of formations lines is controlled in the same manner as for \u003ca href=\"/plot-window/rftplot/#zonation-formation-names\"\u003eRFT plots\u003c/a\u003e.\nPlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e of the formations property editor for details about formations.\u003c/p\u003e\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\u003cp\u003eVisual properties of legend and axes is controlled in the same manner as for \u003ca href=\"/plot-window/rftplot/#legend-and-axis\"\u003eRFT plots\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"import-of-observed-ensemble-rft-data-from-fmu\"\u003eImport of Observed Ensemble RFT data from FMU\u003c/h2\u003e\n\u003cp\u003eObserved RFT data as part of a FMU run is presupposed to be located in a folder which contains the following four file types:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003elayer_zone_table.txt\u003c/li\u003e\n\u003cli\u003e\u0026lt;\u003cem\u003ewell_name\u003c/em\u003e\u0026gt;.obs\u003c/li\u003e\n\u003cli\u003e\u0026lt;\u003cem\u003ewell_name\u003c/em\u003e\u0026gt;.txt\u003c/li\u003e\n\u003cli\u003ewell_date_rft.txt\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe purpose and format of the data files is explained below.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe data file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e is required. If missing, no Observed FMU data will be imported.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch4 id=\"correlation-of-grid-and-formations\"\u003eCorrelation of grid and formations\u003c/h4\u003e\n\u003cp\u003eThe file \u003cem\u003elayer_zone_table.txt\u003c/em\u003e can be used to correlate each grid k-layer with a formation name. \nThis file is identical for all cases in the same ensemble.\u003c/p\u003e\n\u003cp\u003eExample file \u003cem\u003elayer_zone_table.txt\u003c/em\u003e:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e1   UpperReek\r\n2   UpperReek\r\n3   UpperReek\r\n4   UpperReek\r\n5   UpperReek\r\n6   MidReek\r\n7   MidReek\r\n8   MidReek\r\n9   MidReek\r\n10  MidReek\r\n11  LowerReek\r\n12  LowerReek\r\n13  LowerReek\r\n14  LowerReek\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch4 id=\"observed-pressure-and-error\"\u003eObserved pressure and error\u003c/h4\u003e\n\u003cp\u003eFor a given well name, the file \u003cem\u003e\u0026lt;well_name\u0026gt;.obs\u003c/em\u003e is a data file containing two columns to specify observed pressure and error. \nColumn one contains observed pressure and column two contains error. The observation data is valid for one and only one layer/formation.\u003c/p\u003e\n\u003cp\u003eExample file  for well \u003cem\u003eOP_1\u003c/em\u003e, i.e. \u003cem\u003eOP_1.obs\u003c/em\u003e:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e303.000   3.000\r\n304.000   3.000\r\n305.000   3.000\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch4 id=\"reservoir-zone-name\"\u003eReservoir zone name\u003c/h4\u003e\n\u003cp\u003eFor a given well name, the file \u003cem\u003e\u0026lt;well_name\u0026gt;.txt\u003c/em\u003e is a data file containing five columns that specify its correlation with reservoir zones. \nEach line of data must contain:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUtmx: x-coordinate in UTM\u003c/li\u003e\n\u003cli\u003eUtmy: y-coordinate in UTM\u003c/li\u003e\n\u003cli\u003eMeasured Depth relative to the Kelly Bushing (MDRKB)\u003c/li\u003e\n\u003cli\u003eTrue Vertical Depth referenced to Mean Sea Level (TVDMSL)\u003c/li\u003e\n\u003cli\u003eReservoir zone name\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eExample file for well \u003cem\u003eOP_1\u003c/em\u003e, i.e. \u003cem\u003eOP_1.txt\u003c/em\u003e:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e461288.719   5933415.000   1816.200   1611.692   UpperReek\r\n461288.685   5933415.027   1824.560   1620.052   MidReek\r\n461288.683   5933415.029   1840.000   1635.492   LowerReek\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch4 id=\"well-measurements\"\u003eWell measurements\u003c/h4\u003e\n\u003cp\u003eThe data file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e contains well measurements. The file contains four columns for each well measurement:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eWell Name\u003c/li\u003e\n\u003cli\u003eDate in two digit form \u0026lt;DD\u0026gt;\u003c/li\u003e\n\u003cli\u003eMonth in two digit form \u0026lt;MM\u0026gt;\u003c/li\u003e\n\u003cli\u003eYear in four digit form \u0026lt;YYYY\u0026gt;\u003c/li\u003e\n\u003cli\u003eMeasurement index\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThere can be multiple measurement for each well.\u003c/p\u003e\n\u003cp\u003eExample file \u003cem\u003ewell_date_rft.txt\u003c/em\u003e:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eOP_1   01 02 2000   1\r\nOP_2   01 02 2000   1\r\nOP_4   01 01 2001   1\r\nWI_1   01 02 2000   1\r\nWI_3   01 03 2001   1\r\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/plot-window/ensemblerftplot/"
             };
         
@@ -2460,8 +2502,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/formations/"] = {
                 title:    " Zonations/Formations",
-                content:  " This section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.\nFormations for k-layers Formation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the Result info panel when selecting single cells.\nTo use this functionality you will need to :\n Import one or more Formation Names file(s) Select the correct Formation Names file in the Case of interest  Import of Formation Names Files Formation Names files can be imported by using the command: File-\u0026gt;Import-\u0026gt;Import Formation Names.\nSupported Formation Names files are:\n Formation Names description files (*.lyr) FMU Layer Zone Table (layer_zone_table.txt)  To select the appropriate file type, use the button to the right of file name in the Import Formation Names dialog. The imported Formation Names files are then listed in the Project Tree in a folder named Formations.\nFormation Names description files (*.lyr) Formation Names description files (*.lyr) consist of a list of formation names and their k-range. Below is an example of a Formation Names description file:\n-- Any text as comment 'MyFormationName' 4 - 12 'MySecondFormationName' 15 - 17 '3 k-layer thick 18,19 and 20' 3 'Last Name' 21 - 21  FMU Layer Zone Table (layer_zone_table.txt) The FMU Layer Zone Table (layer_zone_table.txt) contains two columns to correlate each grid k-layer with a formation name. Below is an example of a layer_zone_table.txt file:\n1 UpperReek 2 UpperReek 3 UpperReek 4 UpperReek 5 UpperReek 6 MidReek 7 MidReek 8 MidReek 9 MidReek 10 MidReek 11 LowerReek 12 LowerReek 13 LowerReek 14 LowerReek  Select the Formation File in a Case If only one formation file is imported, the formation will automatically be set in the active view\u0026rsquo;s case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the Property Editor for a case. The formation is selected in the combo box for property Formation Names File.\nReload of formation data If the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu Formations-\u0026gt;Reload. This command will import formations for the selected formation files.\nViewing the Formation Information Formations in 3D View The formations can be visualized as a result property in Cell Results, Cell Edge Result, and Separate Fault Result. When selected, a special legend displaying formation names is activated.\nProperty Filter Based on Formations Formation names are available in Property Filters as Result Type Formation Names. This makes it easy to filter geometry based on formation specifications.\nSee Cell Filters  for details.\nPicking in 3D View Picking on a cell being part of a formation will display the formation name in the Result Info windows, in addition to other pick info for the cell.\nAnnotations on Plots Formation can be used to annotate the following plot types:\n Well Log Plots RFT Plots PLT Plots Well Allocation Plots  MANGLER BILDE\nFor RFT and PLT Plots, Zonation/Formation Names can be found in the plot\u0026rsquo;s Property Editor. Tick \u0026ldquo;Show Formations\u0026rdquo; and choose the case with the desired formations.\nIn Well Log Plots and Well Allocation Plots, Zonation/Formation Names can be found in the Property Editor for a Track or Branch. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.\nWell Picks Well Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a fluid or a formation.\nImport of Well Pick Files Well Pick files can be imported by using the command: File-\u0026gt;Import-\u0026gt;Well Data-\u0026gt;Import Well Picks. The user is asked to select *.csv files for import.\nThe imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in Wells in the Project Tree. The file path of the formations can be found in a well path\u0026rsquo;s Property Editor.\nA Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:\nWell name; Column name; Unit name; Top MD; Base MD B-3H; FLUID; GAS;2203.2;2317.4 B-3H; FLUID; OIL;2317.4;2459 B-3H; STRAT; FANGST GP. ;2203.399902;2223.350098 B-3H; STRAT; Ile Fm. ;2203.399902;2223.350098 B-3H; STRAT; Ile Fm. 3 ;2203.401123;2219.26001 B-3H; STRAT; Ile Fm. 2 ;2219.26001;2222.399902 B-3H; STRAT; Ile Fm. 2.2 ;2219.26;2219.350098 B-3H; STRAT; Ile Fm. 2.1 ;2219.350098;2222.399902 B-3H; STRAT; Ile Fm. 1 ;2222.399902;2223.350098 B-3H; STRAT; BAAT GP. ;2223.350098;2979.28125 B-3H; STRAT; Ror Fm. ;2223.350098;2285.199951 B-3H; STRAT; Ror Fm. 2 ;2223.350098;2246 B-3H; STRAT; Ror Fm. 1 ;2246;2285.199951 B-2H; FLUID; GAS;2144.4;2338.5 B-2H; FLUID; OIL;2338.5;2440 B-2H; STRAT; FANGST GP. ;2144.199951;2158.389893 B-2H; STRAT; Ile Fm. ;2144.199951;2158.389893 B-2H; STRAT; Ile Fm. 2 ;2144.201416;2156.197266 B-2H; STRAT; Ile Fm. 1 ;2156.197266;2158.38501  The file must have the columns \u0026ldquo;Well name\u0026rdquo;, \u0026ldquo;Unit name\u0026rdquo; (i.e. formation name), \u0026ldquo;Top MD\u0026rdquo; and \u0026ldquo;Base MD\u0026rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.\nThe three unit names OIL, GAS and WATER are interpreted as fluids. Other unit names with only capital letters are groups. A unit name without an index is simply a formation. Unit names with one number is a formation 1, unit names with one punctuation is a formation 2, two punctuations, formation 3 and so on. Indentions in column name will be ignored.\nViewing the Well Picks See Annotations on plots. Annotations are added to plots in the same way as for k-layered formations, but the source is different.\nIn the Property Editor, choose Well Path as Source, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the Well Pick Filter can be used.\nThe Well Pick Filter will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as Fluids are only shown by ticking the Show Fluids mark.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formations_legend.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.\u003c/p\u003e\n\n\u003ch2 id=\"formations-for-k-layers\"\u003eFormations for k-layers\u003c/h2\u003e\n\n\u003cp\u003eFormation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the \u003cstrong\u003eResult info\u003c/strong\u003e panel when selecting single cells.\u003c/p\u003e\n\n\u003cp\u003eTo use this functionality you will need to :\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eImport one or more Formation Names file(s)\u003c/li\u003e\n\u003cli\u003eSelect the correct Formation Names file in the Case of interest\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003ch3 id=\"import-of-formation-names-files\"\u003eImport of Formation Names Files\u003c/h3\u003e\n\n\u003cp\u003eFormation Names files can be imported by using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Import Formation Names\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eSupported Formation Names files are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003eFMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eTo select the appropriate file type, use the button to the right of file name in the \u003cem\u003eImport Formation Names\u003c/em\u003e dialog.\nThe imported Formation Names files are then listed in the \u003cstrong\u003eProject Tree\u003c/strong\u003e in a folder named \u003cstrong\u003eFormations\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch4 id=\"formation-names-description-files-lyr\"\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e)\u003c/h4\u003e\n\n\u003cp\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e) consist of a list of formation names and their k-range.\nBelow is an example of a Formation Names description file:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e-- Any text as comment\n'MyFormationName'                 4 - 12\n'MySecondFormationName'          15 - 17\n'3 k-layer thick 18,19 and 20'    3\n'Last Name'                      21 - 21 \n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch4 id=\"fmu-layer-zone-table-layer-zone-table-txt\"\u003eFMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e)\u003c/h4\u003e\n\n\u003cp\u003eThe FMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e) contains two columns to correlate each grid k-layer with a formation name.\nBelow is an example of a \u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e file:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003e1   UpperReek\n2   UpperReek\n3   UpperReek\n4   UpperReek\n5   UpperReek\n6   MidReek\n7   MidReek\n8   MidReek\n9   MidReek\n10  MidReek\n11  LowerReek\n12  LowerReek\n13  LowerReek\n14  LowerReek\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003ch3 id=\"select-the-formation-file-in-a-case\"\u003eSelect the Formation File in a Case\u003c/h3\u003e\n\n\u003cp\u003eIf only one formation file is imported, the formation will automatically be set in the active view\u0026rsquo;s case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for a case. The formation is selected in the combo box for property \u003cstrong\u003eFormation Names File\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formations_property_editor.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"reload-of-formation-data\"\u003eReload of formation data\u003c/h4\u003e\n\n\u003cp\u003eIf the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu \u003cstrong\u003eFormations-\u0026gt;Reload\u003c/strong\u003e. This command will import formations for the selected formation files.\u003c/p\u003e\n\n\u003ch3 id=\"viewing-the-formation-information\"\u003eViewing the Formation Information\u003c/h3\u003e\n\n\u003ch4 id=\"formations-in-3d-view\"\u003eFormations in 3D View\u003c/h4\u003e\n\n\u003cp\u003eThe formations can be visualized as a result property in \u003cstrong\u003eCell Results\u003c/strong\u003e, \u003cstrong\u003eCell Edge Result\u003c/strong\u003e, and \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e. When selected, a special legend displaying formation names is activated.\u003c/p\u003e\n\n\u003ch4 id=\"property-filter-based-on-formations\"\u003eProperty Filter Based on Formations\u003c/h4\u003e\n\n\u003cp\u003eFormation names are available in Property Filters as Result Type \u003cstrong\u003eFormation Names\u003c/strong\u003e. This makes it easy to filter geometry based on formation specifications.\u003c/p\u003e\n\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/filters/\"\u003e Cell Filters \u003c/a\u003e for details.\u003c/p\u003e\n\n\u003ch4 id=\"picking-in-3d-view\"\u003ePicking in 3D View\u003c/h4\u003e\n\n\u003cp\u003ePicking on a cell being part of a formation will display the formation name in the \u003cstrong\u003eResult Info\u003c/strong\u003e windows, in addition to other pick info for the cell.\u003c/p\u003e\n\n\u003ch4 id=\"annotations-on-plots\"\u003eAnnotations on Plots\u003c/h4\u003e\n\n\u003cp\u003eFormation can be used to annotate the following plot types:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/rftplot/\"\u003eRFT Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/pltplot/\"\u003ePLT Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003eWell Allocation Plots\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formOnPlot.PNG\" alt=\"\" /\u003e MANGLER BILDE\u003c/p\u003e\n\n\u003cp\u003eFor RFT and PLT Plots, \u003cstrong\u003eZonation/Formation Names\u003c/strong\u003e can be found in the plot\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Tick \u0026ldquo;Show Formations\u0026rdquo; and choose the case with the desired formations.\u003c/p\u003e\n\n\u003cp\u003eIn Well Log Plots and Well Allocation Plots, \u003cstrong\u003eZonation/Formation Names\u003c/strong\u003e can be found in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for a \u003cstrong\u003eTrack\u003c/strong\u003e or \u003cstrong\u003eBranch\u003c/strong\u003e. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/caseFormationsPropEditor.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"well-picks\"\u003eWell Picks\u003c/h2\u003e\n\n\u003cp\u003eWell Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a \u003cem\u003efluid\u003c/em\u003e or a \u003cem\u003eformation\u003c/em\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"import-of-well-pick-files\"\u003eImport of Well Pick Files\u003c/h3\u003e\n\n\u003cp\u003eWell Pick files can be imported by using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Well Data-\u0026gt;Import Well Picks\u003c/strong\u003e.\nThe user is asked to select \u003cem\u003e\u003ccode\u003e*.csv\u003c/code\u003e\u003c/em\u003e files for import.\u003c/p\u003e\n\n\u003cp\u003eThe imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in \u003cstrong\u003eWells\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The file path of the formations can be found in a well path\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellPathFormationsInPropertyEditor.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:\u003c/p\u003e\n\n\u003cpre\u003e\u003ccode\u003eWell name; Column name; Unit name; Top MD; Base MD\nB-3H; FLUID; GAS;2203.2;2317.4\nB-3H; FLUID; OIL;2317.4;2459\nB-3H; STRAT; FANGST GP. ;2203.399902;2223.350098\nB-3H; STRAT;   Ile Fm. ;2203.399902;2223.350098\nB-3H; STRAT;     Ile Fm. 3 ;2203.401123;2219.26001\nB-3H; STRAT;     Ile Fm. 2 ;2219.26001;2222.399902\nB-3H; STRAT;       Ile Fm. 2.2 ;2219.26;2219.350098\nB-3H; STRAT;       Ile Fm. 2.1 ;2219.350098;2222.399902\nB-3H; STRAT;     Ile Fm. 1 ;2222.399902;2223.350098\nB-3H; STRAT; BAAT GP. ;2223.350098;2979.28125\nB-3H; STRAT;   Ror Fm. ;2223.350098;2285.199951\nB-3H; STRAT;     Ror Fm. 2 ;2223.350098;2246\nB-3H; STRAT;     Ror Fm. 1 ;2246;2285.199951\nB-2H; FLUID; GAS;2144.4;2338.5\nB-2H; FLUID; OIL;2338.5;2440\nB-2H; STRAT; FANGST GP. ;2144.199951;2158.389893\nB-2H; STRAT;   Ile Fm. ;2144.199951;2158.389893\nB-2H; STRAT;     Ile Fm. 2 ;2144.201416;2156.197266\nB-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501\n\u003c/code\u003e\u003c/pre\u003e\n\n\u003cp\u003eThe file must have the columns \u0026ldquo;Well name\u0026rdquo;, \u0026ldquo;Unit name\u0026rdquo; (i.e. formation name), \u0026ldquo;Top MD\u0026rdquo; and \u0026ldquo;Base MD\u0026rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.\u003c/p\u003e\n\n\u003cp\u003eThe three unit names \u003cem\u003eOIL\u003c/em\u003e, \u003cem\u003eGAS\u003c/em\u003e and \u003cem\u003eWATER\u003c/em\u003e are interpreted as \u003cem\u003efluids\u003c/em\u003e. Other unit names with only capital letters are \u003cem\u003egroups\u003c/em\u003e. A unit name without an index is simply a \u003cem\u003eformation\u003c/em\u003e. Unit names with one number is a \u003cem\u003eformation 1\u003c/em\u003e, unit names with \u003cem\u003eone\u003c/em\u003e punctuation is a \u003cem\u003eformation 2\u003c/em\u003e, two punctuations, \u003cem\u003eformation 3\u003c/em\u003e and so on. Indentions in column name will be ignored.\u003c/p\u003e\n\n\u003ch3 id=\"viewing-the-well-picks\"\u003eViewing the Well Picks\u003c/h3\u003e\n\n\u003cp\u003eSee \u003ca href=\"#annotations-on-plots\"\u003eAnnotations on plots\u003c/a\u003e. Annotations are added to plots in the same way as for k-layered formations, but the source is different.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellFormationsPropEditor.PNG\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIn the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, choose \u003cstrong\u003eWell Path\u003c/strong\u003e as \u003cstrong\u003eSource\u003c/strong\u003e, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the \u003cstrong\u003eWell Pick Filter\u003c/strong\u003e can be used.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellPickFilter.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eWell Pick Filter\u003c/strong\u003e will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as \u003cem\u003eFluids\u003c/em\u003e are only shown by ticking the \u003cstrong\u003eShow Fluids\u003c/strong\u003e mark.\u003c/p\u003e\n",
+                content:  "This section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.\nFormations for k-layers Formation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the Result info panel when selecting single cells.\nTo use this functionality you will need to :\n Import one or more Formation Names file(s) Select the correct Formation Names file in the Case of interest  Import of Formation Names Files Formation Names files can be imported by using the command: File-\u0026gt;Import-\u0026gt;Import Formation Names.\nSupported Formation Names files are:\n Formation Names description files (*.lyr) FMU Layer Zone Table (layer_zone_table.txt)  To select the appropriate file type, use the button to the right of file name in the Import Formation Names dialog. The imported Formation Names files are then listed in the Project Tree in a folder named Formations.\nFormation Names description files (*.lyr) Formation Names description files (*.lyr) consist of a list of formation names and their k-range. Below is an example of a Formation Names description file:\n-- Any text as comment\r'MyFormationName' 4 - 12\r'MySecondFormationName' 15 - 17\r'3 k-layer thick 18,19 and 20' 3\r'Last Name' 21 - 21 FMU Layer Zone Table (layer_zone_table.txt) The FMU Layer Zone Table (layer_zone_table.txt) contains two columns to correlate each grid k-layer with a formation name. Below is an example of a layer_zone_table.txt file:\n1 UpperReek\r2 UpperReek\r3 UpperReek\r4 UpperReek\r5 UpperReek\r6 MidReek\r7 MidReek\r8 MidReek\r9 MidReek\r10 MidReek\r11 LowerReek\r12 LowerReek\r13 LowerReek\r14 LowerReek\rSelect the Formation File in a Case If only one formation file is imported, the formation will automatically be set in the active view\u0026rsquo;s case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the Property Editor for a case. The formation is selected in the combo box for property Formation Names File.\nReload of formation data If the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu Formations-\u0026gt;Reload. This command will import formations for the selected formation files.\nViewing the Formation Information Formations in 3D View The formations can be visualized as a result property in Cell Results, Cell Edge Result, and Separate Fault Result. When selected, a special legend displaying formation names is activated.\nProperty Filter Based on Formations Formation names are available in Property Filters as Result Type Formation Names. This makes it easy to filter geometry based on formation specifications.\nSee Cell Filters  for details.\nPicking in 3D View Picking on a cell being part of a formation will display the formation name in the Result Info windows, in addition to other pick info for the cell.\nAnnotations on Plots Formation can be used to annotate the following plot types:\n Well Log Plots RFT Plots PLT Plots Well Allocation Plots  MANGLER BILDE\nFor RFT and PLT Plots, Zonation/Formation Names can be found in the plot\u0026rsquo;s Property Editor. Tick \u0026ldquo;Show Formations\u0026rdquo; and choose the case with the desired formations.\nIn Well Log Plots and Well Allocation Plots, Zonation/Formation Names can be found in the Property Editor for a Track or Branch. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.\nWell Picks Well Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a fluid or a formation.\nImport of Well Pick Files Well Pick files can be imported by using the command: File-\u0026gt;Import-\u0026gt;Well Data-\u0026gt;Import Well Picks. The user is asked to select *.csv files for import.\nThe imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in Wells in the Project Tree. The file path of the formations can be found in a well path\u0026rsquo;s Property Editor.\nA Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:\nWell name; Column name; Unit name; Top MD; Base MD\rB-3H; FLUID; GAS;2203.2;2317.4\rB-3H; FLUID; OIL;2317.4;2459\rB-3H; STRAT; FANGST GP. ;2203.399902;2223.350098\rB-3H; STRAT; Ile Fm. ;2203.399902;2223.350098\rB-3H; STRAT; Ile Fm. 3 ;2203.401123;2219.26001\rB-3H; STRAT; Ile Fm. 2 ;2219.26001;2222.399902\rB-3H; STRAT; Ile Fm. 2.2 ;2219.26;2219.350098\rB-3H; STRAT; Ile Fm. 2.1 ;2219.350098;2222.399902\rB-3H; STRAT; Ile Fm. 1 ;2222.399902;2223.350098\rB-3H; STRAT; BAAT GP. ;2223.350098;2979.28125\rB-3H; STRAT; Ror Fm. ;2223.350098;2285.199951\rB-3H; STRAT; Ror Fm. 2 ;2223.350098;2246\rB-3H; STRAT; Ror Fm. 1 ;2246;2285.199951\rB-2H; FLUID; GAS;2144.4;2338.5\rB-2H; FLUID; OIL;2338.5;2440\rB-2H; STRAT; FANGST GP. ;2144.199951;2158.389893\rB-2H; STRAT; Ile Fm. ;2144.199951;2158.389893\rB-2H; STRAT; Ile Fm. 2 ;2144.201416;2156.197266\rB-2H; STRAT; Ile Fm. 1 ;2156.197266;2158.38501\rThe file must have the columns \u0026ldquo;Well name\u0026rdquo;, \u0026ldquo;Unit name\u0026rdquo; (i.e. formation name), \u0026ldquo;Top MD\u0026rdquo; and \u0026ldquo;Base MD\u0026rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.\nThe three unit names OIL, GAS and WATER are interpreted as fluids. Other unit names with only capital letters are groups. A unit name without an index is simply a formation. Unit names with one number is a formation 1, unit names with one punctuation is a formation 2, two punctuations, formation 3 and so on. Indentions in column name will be ignored.\nViewing the Well Picks See Annotations on plots. Annotations are added to plots in the same way as for k-layered formations, but the source is different.\nIn the Property Editor, choose Well Path as Source, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the Well Pick Filter can be used.\nThe Well Pick Filter will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as Fluids are only shown by ticking the Show Fluids mark.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formations_legend.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis section will describe how to use formations for different k-layers of a case, and how to use well picks/zonations for ranges of measured depths of a well path.\u003c/p\u003e\n\u003ch2 id=\"formations-for-k-layers\"\u003eFormations for k-layers\u003c/h2\u003e\n\u003cp\u003eFormation information can be utilized in ResInsight as cell colors, used in property filters and are displayed in the \u003cstrong\u003eResult info\u003c/strong\u003e panel when selecting single cells.\u003c/p\u003e\n\u003cp\u003eTo use this functionality you will need to :\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eImport one or more Formation Names file(s)\u003c/li\u003e\n\u003cli\u003eSelect the correct Formation Names file in the Case of interest\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch3 id=\"import-of-formation-names-files\"\u003eImport of Formation Names Files\u003c/h3\u003e\n\u003cp\u003eFormation Names files can be imported by using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Import Formation Names\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eSupported Formation Names files are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003cli\u003eFMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eTo select the appropriate file type, use the button to the right of file name in the \u003cem\u003eImport Formation Names\u003c/em\u003e dialog. \nThe imported Formation Names files are then listed in the \u003cstrong\u003eProject Tree\u003c/strong\u003e in a folder named \u003cstrong\u003eFormations\u003c/strong\u003e.\u003c/p\u003e\n\u003ch4 id=\"formation-names-description-files-_lyr_\"\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e)\u003c/h4\u003e\n\u003cp\u003eFormation Names description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e) consist of a list of formation names and their k-range. \nBelow is an example of a Formation Names description file:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e-- Any text as comment\r\n'MyFormationName'                 4 - 12\r\n'MySecondFormationName'          15 - 17\r\n'3 k-layer thick 18,19 and 20'    3\r\n'Last Name'                      21 - 21 \r\n\u003c/code\u003e\u003c/pre\u003e\u003ch4 id=\"fmu-layer-zone-table-_layer_zone_tabletxt_\"\u003eFMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e)\u003c/h4\u003e\n\u003cp\u003eThe FMU Layer Zone Table (\u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e) contains two columns to correlate each grid k-layer with a formation name. \nBelow is an example of a \u003cem\u003e\u003ccode\u003elayer_zone_table.txt\u003c/code\u003e\u003c/em\u003e file:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e1   UpperReek\r\n2   UpperReek\r\n3   UpperReek\r\n4   UpperReek\r\n5   UpperReek\r\n6   MidReek\r\n7   MidReek\r\n8   MidReek\r\n9   MidReek\r\n10  MidReek\r\n11  LowerReek\r\n12  LowerReek\r\n13  LowerReek\r\n14  LowerReek\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"select-the-formation-file-in-a-case\"\u003eSelect the Formation File in a Case\u003c/h3\u003e\n\u003cp\u003eIf only one formation file is imported, the formation will automatically be set in the active view\u0026rsquo;s case. If more than one formation file is imported at once, or if a case must change formation file, the formation file for a case can be set later on. This option is available in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for a case. The formation is selected in the combo box for property \u003cstrong\u003eFormation Names File\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formations_property_editor.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"reload-of-formation-data\"\u003eReload of formation data\u003c/h4\u003e\n\u003cp\u003eIf the formation file is modified outside ResInsight, the formation data can be imported again by the right-click menu \u003cstrong\u003eFormations-\u0026gt;Reload\u003c/strong\u003e. This command will import formations for the selected formation files.\u003c/p\u003e\n\u003ch3 id=\"viewing-the-formation-information\"\u003eViewing the Formation Information\u003c/h3\u003e\n\u003ch4 id=\"formations-in-3d-view\"\u003eFormations in 3D View\u003c/h4\u003e\n\u003cp\u003eThe formations can be visualized as a result property in \u003cstrong\u003eCell Results\u003c/strong\u003e, \u003cstrong\u003eCell Edge Result\u003c/strong\u003e, and \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e. When selected, a special legend displaying formation names is activated.\u003c/p\u003e\n\u003ch4 id=\"property-filter-based-on-formations\"\u003eProperty Filter Based on Formations\u003c/h4\u003e\n\u003cp\u003eFormation names are available in Property Filters as Result Type \u003cstrong\u003eFormation Names\u003c/strong\u003e. This makes it easy to filter geometry based on formation specifications.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/filters/\"\u003e Cell Filters \u003c/a\u003e for details.\u003c/p\u003e\n\u003ch4 id=\"picking-in-3d-view\"\u003ePicking in 3D View\u003c/h4\u003e\n\u003cp\u003ePicking on a cell being part of a formation will display the formation name in the \u003cstrong\u003eResult Info\u003c/strong\u003e windows, in addition to other pick info for the cell.\u003c/p\u003e\n\u003ch4 id=\"annotations-on-plots\"\u003eAnnotations on Plots\u003c/h4\u003e\n\u003cp\u003eFormation can be used to annotate the following plot types:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/rftplot/\"\u003eRFT Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/pltplot/\"\u003ePLT Plots\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/flowdiagnosticsplots/\"\u003eWell Allocation Plots\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/formOnPlot.PNG\" alt=\"\"\u003e MANGLER BILDE\u003c/p\u003e\n\u003cp\u003eFor RFT and PLT Plots, \u003cstrong\u003eZonation/Formation Names\u003c/strong\u003e can be found in the plot\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e. Tick \u0026ldquo;Show Formations\u0026rdquo; and choose the case with the desired formations.\u003c/p\u003e\n\u003cp\u003eIn Well Log Plots and Well Allocation Plots, \u003cstrong\u003eZonation/Formation Names\u003c/strong\u003e can be found in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for a \u003cstrong\u003eTrack\u003c/strong\u003e or \u003cstrong\u003eBranch\u003c/strong\u003e. In addition to choosing case, the path to show formations for must also be selected, as each track can have curves with data from more than one path.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/caseFormationsPropEditor.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"well-picks\"\u003eWell Picks\u003c/h2\u003e\n\u003cp\u003eWell Picks can be set for a single well path, defined on measured depths of the well path. Unlike formations for k-layers, formations for a well path can only be used to annotate plots. A well pick can be either a \u003cem\u003efluid\u003c/em\u003e or a \u003cem\u003eformation\u003c/em\u003e.\u003c/p\u003e\n\u003ch3 id=\"import-of-well-pick-files\"\u003eImport of Well Pick Files\u003c/h3\u003e\n\u003cp\u003eWell Pick files can be imported by using the command: \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Well Data-\u0026gt;Import Well Picks\u003c/strong\u003e.\nThe user is asked to select \u003cem\u003e\u003ccode\u003e*.csv\u003c/code\u003e\u003c/em\u003e files for import.\u003c/p\u003e\n\u003cp\u003eThe imported Well Pick files will be added to their associated well path, if a match on well name can be found. If not, new paths will be created, and they can all be found in \u003cstrong\u003eWells\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The file path of the formations can be found in a well path\u0026rsquo;s \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellPathFormationsInPropertyEditor.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Well Pick file is a csv-file, which uses semicolon to separate entries in a table. Below is an example of such a file:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eWell name; Column name; Unit name; Top MD; Base MD\r\nB-3H; FLUID; GAS;2203.2;2317.4\r\nB-3H; FLUID; OIL;2317.4;2459\r\nB-3H; STRAT; FANGST GP. ;2203.399902;2223.350098\r\nB-3H; STRAT;   Ile Fm. ;2203.399902;2223.350098\r\nB-3H; STRAT;     Ile Fm. 3 ;2203.401123;2219.26001\r\nB-3H; STRAT;     Ile Fm. 2 ;2219.26001;2222.399902\r\nB-3H; STRAT;       Ile Fm. 2.2 ;2219.26;2219.350098\r\nB-3H; STRAT;       Ile Fm. 2.1 ;2219.350098;2222.399902\r\nB-3H; STRAT;     Ile Fm. 1 ;2222.399902;2223.350098\r\nB-3H; STRAT; BAAT GP. ;2223.350098;2979.28125\r\nB-3H; STRAT;   Ror Fm. ;2223.350098;2285.199951\r\nB-3H; STRAT;     Ror Fm. 2 ;2223.350098;2246\r\nB-3H; STRAT;     Ror Fm. 1 ;2246;2285.199951\r\nB-2H; FLUID; GAS;2144.4;2338.5\r\nB-2H; FLUID; OIL;2338.5;2440\r\nB-2H; STRAT; FANGST GP. ;2144.199951;2158.389893\r\nB-2H; STRAT;   Ile Fm. ;2144.199951;2158.389893\r\nB-2H; STRAT;     Ile Fm. 2 ;2144.201416;2156.197266\r\nB-2H; STRAT;     Ile Fm. 1 ;2156.197266;2158.38501\r\n\u003c/code\u003e\u003c/pre\u003e\u003cp\u003eThe file must have the columns \u0026ldquo;Well name\u0026rdquo;, \u0026ldquo;Unit name\u0026rdquo; (i.e. formation name), \u0026ldquo;Top MD\u0026rdquo; and \u0026ldquo;Base MD\u0026rdquo; (i.e. measured depth) to be regarded as a Well Pick file. They can be listed in any order, and all other columns will be ignorded.\u003c/p\u003e\n\u003cp\u003eThe three unit names \u003cem\u003eOIL\u003c/em\u003e, \u003cem\u003eGAS\u003c/em\u003e and \u003cem\u003eWATER\u003c/em\u003e are interpreted as \u003cem\u003efluids\u003c/em\u003e. Other unit names with only capital letters are \u003cem\u003egroups\u003c/em\u003e. A unit name without an index is simply a \u003cem\u003eformation\u003c/em\u003e. Unit names with one number is a \u003cem\u003eformation 1\u003c/em\u003e, unit names with \u003cem\u003eone\u003c/em\u003e punctuation is a \u003cem\u003eformation 2\u003c/em\u003e, two punctuations, \u003cem\u003eformation 3\u003c/em\u003e and so on. Indentions in column name will be ignored.\u003c/p\u003e\n\u003ch3 id=\"viewing-the-well-picks\"\u003eViewing the Well Picks\u003c/h3\u003e\n\u003cp\u003eSee \u003ca href=\"#annotations-on-plots\"\u003eAnnotations on plots\u003c/a\u003e. Annotations are added to plots in the same way as for k-layered formations, but the source is different.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellFormationsPropEditor.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, choose \u003cstrong\u003eWell Path\u003c/strong\u003e as \u003cstrong\u003eSource\u003c/strong\u003e, and all well paths with formations will be shown in the drop-down list below. All disjoint well picks for the chosen well path is shown on default. To reduce the number of annotations, the \u003cstrong\u003eWell Pick Filter\u003c/strong\u003e can be used.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/wellPickFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eWell Pick Filter\u003c/strong\u003e will show formations down to the specified level. If more there are more than one formation within 0.1m of an MD, only the lowermost formation is shown. Well picks interpreted as \u003cem\u003eFluids\u003c/em\u003e are only shown by ticking the \u003cstrong\u003eShow Fluids\u003c/strong\u003e mark.\u003c/p\u003e\n",
                 url:      "/3d-main-window/formations/"
             };
         
@@ -2469,8 +2511,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/pltplot/"] = {
                 title:    "PLT Plot",
-                content:  " A PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated production data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed production data are loaded from well log files (*.las).\nCreate New PLT Plot There are several ways to create new PLT Plots\nFrom Project Tree in the Plot Main Window\n Select context command New PLT Plot for the PLT Plots node.  From the Project Tree in the Main Window\n Select context command New PLT Plot for a Well Path node or a Simulation Well node that has an associated well path.  From the 3D view\n Right-click a well path, or a simulation well that has an associated well path, and select Well Plots -\u0026gt; New PLT Plot.  Plot Observed Data To be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:\n   Component Names     Oil QOZT, QOIL, _xxxxQOIL   Gas QOZT, QGAS, _xxxxQGAS   Water QGZT, QWAT, _xxxxQWAT   Total QTZT, QTOT, _xxxxQTOT    To be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.\nProperty Editor The property editor lets the user select which curves to display in the PLT plot.\nWell Name Select the well to display in the plot. Only observed well paths are displayed.\nSources After a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:\n RFT File Cases \u0026ndash; Simulation cases may have associated PLT data in *.rft file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword WRFTPLT in the Eclipse manual for information) Grid Cases \u0026ndash; Simulation cases Observed Cases \u0026ndash; Observed data imported from well log files and well path files  When the user selects a source, time steps for that source appears in the Time Steps field.\nTime Steps The Time Steps field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:\n Exclusively grid cases selected. All available time steps for the selected grid cases are displayed. Grid case(s) and observed data case selected. Time steps shown are:  The first time step from the merged time step list from all grid cases. If no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.  Grid case(s) and RFT File case(s) selected. Same display logic as point 2. All types of cases selected. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.  Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: [ O ], [ R G ].\n O \u0026ndash; Time step belongs to observed data R \u0026ndash; Time step belongs to RFT data G \u0026ndash; Time step belongs to Grid data  More than one letter for one single time step, means that the time step belongs to multiple case types.\nCurve Selection The curve selection group lets the user control which component(s) of the PLT data to display.\n Standard Volume \u0026ndash; Production data at standard conditions (normal air pressure) Reservoir Volume \u0026ndash; Production data at reservoir pressure (high air pressure) Oil \u0026ndash; The oil production component Gas \u0026ndash; The gas production component Water \u0026ndash; The water production component Total \u0026ndash; Total production  Zonation/Formation Names This property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.\nPlease see the full documentation on the formations property editor for details.\nWhen the formation names property editor is used in the context of PLT plots, the fields Trajectory and Simulation Well are hidden because those values are given by the PLT plot definition.\n\rLegend and Axis This property editor lets the user control visual properties for the legend and axis.\n Title and Legends  Show Title \u0026ndash; Toggle on/off title in plot Show Legends \u0026ndash; Toggle on/off legend in plot Legend Orientation \u0026ndash; Vertical or horizontal  X Axis Settings  Logarithmic Scale \u0026ndash; Toggle between linear and logarithmic Min \u0026ndash; Set X axis minimum value Max \u0026ndash; Set X axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot  Depth Axis  Type \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD) Unit \u0026ndash; Min \u0026ndash; Set depth axis minimum value Max \u0026ndash; Set depth axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot    Plot The PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/PltPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated production data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed production data are loaded from well log files (*.las).\u003c/p\u003e\n\n\u003ch2 id=\"create-new-plt-plot\"\u003eCreate New PLT Plot\u003c/h2\u003e\n\n\u003cp\u003eThere are several ways to create new PLT Plots\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom Project Tree in the Plot Main Window\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew PLT Plot\u003c/strong\u003e for the \u003cem\u003ePLT Plots\u003c/em\u003e node.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the Main Window\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew PLT Plot\u003c/strong\u003e for a \u003cem\u003eWell Path\u003c/em\u003e node or a \u003cem\u003eSimulation Well\u003c/em\u003e node that has an associated well path.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cstrong\u003eFrom the 3D view\u003c/strong\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eRight-click a well path, or a simulation well that has an associated well path, and select \u003cstrong\u003eWell Plots -\u0026gt; New PLT Plot\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"plot-observed-data\"\u003ePlot Observed Data\u003c/h2\u003e\n\n\u003cp\u003eTo be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eComponent\u003c/th\u003e\n\u003cth\u003eNames\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eOil\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQOZT\u003c/em\u003e, \u003cem\u003eQOIL\u003c/em\u003e, _xxxx\u003cem\u003eQOIL\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eGas\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQOZT\u003c/em\u003e, \u003cem\u003eQGAS\u003c/em\u003e, _xxxx\u003cem\u003eQGAS\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eWater\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQGZT\u003c/em\u003e, \u003cem\u003eQWAT\u003c/em\u003e, _xxxx\u003cem\u003eQWAT\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eTotal\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQTZT\u003c/em\u003e, \u003cem\u003eQTOT\u003c/em\u003e, _xxxx\u003cem\u003eQTOT\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003cp\u003eTo be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/NoMdWarningDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\n\u003cp\u003eThe property editor lets the user select which curves to display in the PLT plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/PltPlotPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\n\u003cp\u003eSelect the well to display in the plot. Only observed well paths are displayed.\u003c/p\u003e\n\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\n\u003cp\u003eAfter a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRFT File Cases\u003c/strong\u003e \u0026ndash; Simulation cases may have associated PLT data in \u003cem\u003e*.rft\u003c/em\u003e file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword \u003ccode\u003eWRFTPLT\u003c/code\u003e in the Eclipse manual for information)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Cases\u003c/strong\u003e \u0026ndash; Simulation cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved Cases\u003c/strong\u003e \u0026ndash; Observed data imported from well log files and well path files\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen the user selects a source, time steps for that source appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003e\u003cstrong\u003eExclusively grid cases selected\u003c/strong\u003e. All available time steps for the selected grid cases are displayed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid case(s) and observed data case selected\u003c/strong\u003e. Time steps shown are:\n\n\u003cul\u003e\n\u003cli\u003eThe first time step from the merged time step list from all grid cases.\u003c/li\u003e\n\u003cli\u003eIf no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid case(s) and RFT File case(s) selected\u003c/strong\u003e. Same display logic as point 2.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll types of cases selected\u003c/strong\u003e. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eEach time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: \u003cstrong\u003e[ O ]\u003c/strong\u003e, \u003cstrong\u003e[ R G ]\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step belongs to observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step belongs to RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step belongs to Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eMore than one letter for one single time step, means that the time step belongs to multiple case types.\u003c/p\u003e\n\n\u003ch3 id=\"curve-selection\"\u003eCurve Selection\u003c/h3\u003e\n\n\u003cp\u003eThe curve selection group lets the user control which component(s) of the PLT data to display.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStandard Volume\u003c/strong\u003e \u0026ndash; Production data at standard conditions (normal air pressure)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eReservoir Volume\u003c/strong\u003e \u0026ndash; Production data at reservoir pressure (high air pressure)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOil\u003c/strong\u003e \u0026ndash; The oil production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas\u003c/strong\u003e \u0026ndash; The gas production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWater\u003c/strong\u003e \u0026ndash; The water production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal\u003c/strong\u003e \u0026ndash; Total production\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"zonation-formation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\n\u003cp\u003eThis property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPltFormationNames.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003ePlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e on the formations property editor for details.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen the formation names property editor is used in the context of PLT plots, the fields \u003cb\u003eTrajectory\u003c/b\u003e and \u003cb\u003eSimulation Well\u003c/b\u003e are hidden because those values are given by the PLT plot definition.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/PltLegendAndAxis.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis property editor lets the user control visual properties for the legend and axis.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eTitle and Legends\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggle on/off title in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggle on/off legend in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Orientation\u003c/strong\u003e \u0026ndash; Vertical or horizontal\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eX Axis Settings\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e \u0026ndash; Toggle between linear and logarithmic\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set X axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set X axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eDepth Axis\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnit\u003c/strong\u003e \u0026ndash;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set depth axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set depth axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"plot\"\u003ePlot\u003c/h3\u003e\n\n\u003cp\u003eThe PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.\u003c/p\u003e\n",
+                content:  "A PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated production data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed production data are loaded from well log files (*.las).\nCreate New PLT Plot There are several ways to create new PLT Plots\nFrom Project Tree in the Plot Main Window\n Select context command New PLT Plot for the PLT Plots node.  From the Project Tree in the Main Window\n Select context command New PLT Plot for a Well Path node or a Simulation Well node that has an associated well path.  From the 3D view\n Right-click a well path, or a simulation well that has an associated well path, and select Well Plots -\u0026gt; New PLT Plot.  Plot Observed Data To be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:\n   Component Names     Oil QOZT, QOIL, xxxx_QOIL   Gas QOZT, QGAS, xxxx_QGAS   Water QGZT, QWAT, xxxx_QWAT   Total QTZT, QTOT, xxxx_QTOT    To be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.\nProperty Editor The property editor lets the user select which curves to display in the PLT plot.\nWell Name Select the well to display in the plot. Only observed well paths are displayed.\nSources After a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:\n RFT File Cases \u0026ndash; Simulation cases may have associated PLT data in *.rft file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword WRFTPLT in the Eclipse manual for information) Grid Cases \u0026ndash; Simulation cases Observed Cases \u0026ndash; Observed data imported from well log files and well path files  When the user selects a source, time steps for that source appears in the Time Steps field.\nTime Steps The Time Steps field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:\n Exclusively grid cases selected. All available time steps for the selected grid cases are displayed. Grid case(s) and observed data case selected. Time steps shown are:   The first time step from the merged time step list from all grid cases. If no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.  Grid case(s) and RFT File case(s) selected. Same display logic as point 2. All types of cases selected. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.  Each time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: [ O ], [ R G ].\n O \u0026ndash; Time step belongs to observed data R \u0026ndash; Time step belongs to RFT data G \u0026ndash; Time step belongs to Grid data  More than one letter for one single time step, means that the time step belongs to multiple case types.\nCurve Selection The curve selection group lets the user control which component(s) of the PLT data to display.\n Standard Volume \u0026ndash; Production data at standard conditions (normal air pressure) Reservoir Volume \u0026ndash; Production data at reservoir pressure (high air pressure) Oil \u0026ndash; The oil production component Gas \u0026ndash; The gas production component Water \u0026ndash; The water production component Total \u0026ndash; Total production  Zonation/Formation Names This property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.\nPlease see the full documentation on the formations property editor for details.\nWhen the formation names property editor is used in the context of PLT plots, the fields Trajectoryand Simulation Wellare hidden because those values are given by the PLT plot definition.\n\rLegend and Axis This property editor lets the user control visual properties for the legend and axis.\n Title and Legends  Show Title \u0026ndash; Toggle on/off title in plot Show Legends \u0026ndash; Toggle on/off legend in plot Legend Orientation \u0026ndash; Vertical or horizontal   X Axis Settings  Logarithmic Scale \u0026ndash; Toggle between linear and logarithmic Min \u0026ndash; Set X axis minimum value Max \u0026ndash; Set X axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot   Depth Axis  Type \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD) Unit \u0026ndash; Min \u0026ndash; Set depth axis minimum value Max \u0026ndash; Set depth axis maximum value Show Grid Lines \u0026ndash; Enable grid lines in background in plot    Plot The PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/PltPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA PLT (Production Log Tool) plot is a special well plot for comparing observed production (well flow rates) and simulated production. The curves are plotted as production against measured depth (MD). Simulated production data is retrieved directly from the grid model or from the corresponding (*.rft) files, while observed production data are loaded from well log files (*.las).\u003c/p\u003e\n\u003ch2 id=\"create-new-plt-plot\"\u003eCreate New PLT Plot\u003c/h2\u003e\n\u003cp\u003eThere are several ways to create new PLT Plots\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eFrom Project Tree in the Plot Main Window\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew PLT Plot\u003c/strong\u003e for the \u003cem\u003ePLT Plots\u003c/em\u003e node.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eFrom the Project Tree in the Main Window\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect context command \u003cstrong\u003eNew PLT Plot\u003c/strong\u003e for a \u003cem\u003eWell Path\u003c/em\u003e node or a \u003cem\u003eSimulation Well\u003c/em\u003e node that has an associated well path.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eFrom the 3D view\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eRight-click a well path, or a simulation well that has an associated well path, and select \u003cstrong\u003eWell Plots -\u0026gt; New PLT Plot\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"plot-observed-data\"\u003ePlot Observed Data\u003c/h2\u003e\n\u003cp\u003eTo be able to plot observed production data for a well, a well log file containing that data must be imported. Production data in a well log file is expected to have column names:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eComponent\u003c/th\u003e\n\u003cth\u003eNames\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eOil\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQOZT\u003c/em\u003e, \u003cem\u003eQOIL\u003c/em\u003e, \u003cem\u003exxxx_QOIL\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGas\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQOZT\u003c/em\u003e, \u003cem\u003eQGAS\u003c/em\u003e, \u003cem\u003exxxx_QGAS\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eWater\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQGZT\u003c/em\u003e, \u003cem\u003eQWAT\u003c/em\u003e, \u003cem\u003exxxx_QWAT\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTotal\u003c/td\u003e\n\u003ctd\u003e\u003cem\u003eQTZT\u003c/em\u003e, \u003cem\u003eQTOT\u003c/em\u003e, \u003cem\u003exxxx_QTOT\u003c/em\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eTo be able to plot simulated data for a well, the trajectory for that well have to be imported. If no well trajectory is found, ResInsight will present a warning dialog to the user.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/NoMdWarningDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe property editor lets the user select which curves to display in the PLT plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/PltPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"well-name\"\u003eWell Name\u003c/h3\u003e\n\u003cp\u003eSelect the well to display in the plot. Only observed well paths are displayed.\u003c/p\u003e\n\u003ch3 id=\"sources\"\u003eSources\u003c/h3\u003e\n\u003cp\u003eAfter a well has been selected in the Well Name field, sources for that well should appear in the sources field. The sources are placed in one of three different groups:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRFT File Cases\u003c/strong\u003e \u0026ndash; Simulation cases may have associated PLT data in \u003cem\u003e*.rft\u003c/em\u003e file(s). If the simulation case contains such files, those are imported together with the simulation case (See the keyword \u003ccode\u003eWRFTPLT\u003c/code\u003e in the Eclipse manual for information)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid Cases\u003c/strong\u003e \u0026ndash; Simulation cases\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eObserved Cases\u003c/strong\u003e \u0026ndash; Observed data imported from well log files and well path files\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen the user selects a source, time steps for that source appears in the \u003cstrong\u003eTime Steps\u003c/strong\u003e field.\u003c/p\u003e\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eTime Steps\u003c/strong\u003e field contains available time steps for the selected source(s). Some combinations of selected sources may display a filtered list of time steps instead of the union of all time steps for all selected sources. The policy is as follows:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003e\u003cstrong\u003eExclusively grid cases selected\u003c/strong\u003e. All available time steps for the selected grid cases are displayed.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGrid case(s) and observed data case selected\u003c/strong\u003e. Time steps shown are:\u003c/li\u003e\n\u003c/ol\u003e\n\u003cul\u003e\n\u003cli\u003eThe first time step from the merged time step list from all grid cases.\u003c/li\u003e\n\u003cli\u003eIf no time steps from grid cases match the observed time step, display the two adjacent grid case time steps.\u003c/li\u003e\n\u003c/ul\u003e\n\u003col start=\"3\"\u003e\n\u003cli\u003e\u003cstrong\u003eGrid case(s) and RFT File case(s) selected\u003c/strong\u003e. Same display logic as point 2.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll types of cases selected\u003c/strong\u003e. Same display logic as point 2 with the exception that RFT File case time steps are treated as grid time steps.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eEach time step is postfixed by an indication of which source type(s) the time step is belonging to. This indication is displayed as one or more letters within square brackets. Examples: \u003cstrong\u003e[ O ]\u003c/strong\u003e, \u003cstrong\u003e[ R G ]\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eO\u003c/strong\u003e \u0026ndash; Time step belongs to observed data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eR\u003c/strong\u003e \u0026ndash; Time step belongs to RFT data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eG\u003c/strong\u003e \u0026ndash; Time step belongs to Grid data\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eMore than one letter for one single time step, means that the time step belongs to multiple case types.\u003c/p\u003e\n\u003ch3 id=\"curve-selection\"\u003eCurve Selection\u003c/h3\u003e\n\u003cp\u003eThe curve selection group lets the user control which component(s) of the PLT data to display.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStandard Volume\u003c/strong\u003e \u0026ndash; Production data at standard conditions (normal air pressure)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eReservoir Volume\u003c/strong\u003e \u0026ndash; Production data at reservoir pressure (high air pressure)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOil\u003c/strong\u003e \u0026ndash; The oil production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGas\u003c/strong\u003e \u0026ndash; The gas production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWater\u003c/strong\u003e \u0026ndash; The water production component\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal\u003c/strong\u003e \u0026ndash; Total production\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"zonationformation-names\"\u003eZonation/Formation Names\u003c/h3\u003e\n\u003cp\u003eThis property editor lets the user control how formations are handled. This is what it looks like in the PLT plot context.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RftPltFormationNames.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003ePlease see the \u003ca href=\"/3d-main-window/formations/\"\u003efull documentation\u003c/a\u003e on the formations property editor for details.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen the formation names property editor is used in the context of PLT plots, the fields \u003c!-- raw HTML omitted --\u003eTrajectory\u003c!-- raw HTML omitted --\u003e and \u003c!-- raw HTML omitted --\u003eSimulation Well\u003c!-- raw HTML omitted --\u003e are hidden because those values are given by the PLT plot definition.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"legend-and-axis\"\u003eLegend and Axis\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/PltLegendAndAxis.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis property editor lets the user control visual properties for the legend and axis.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eTitle and Legends\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Title\u003c/strong\u003e \u0026ndash; Toggle on/off title in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Legends\u003c/strong\u003e \u0026ndash; Toggle on/off legend in plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Orientation\u003c/strong\u003e \u0026ndash; Vertical or horizontal\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eX Axis Settings\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLogarithmic Scale\u003c/strong\u003e \u0026ndash; Toggle between linear and logarithmic\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set X axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set X axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eDepth Axis\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eType\u003c/strong\u003e \u0026ndash; Toggle between True Vertical Depth (MSL) or Measured Depth (MD)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnit\u003c/strong\u003e \u0026ndash;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e \u0026ndash; Set depth axis minimum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Set depth axis maximum value\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Lines\u003c/strong\u003e \u0026ndash; Enable grid lines in background in plot\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"plot\"\u003ePlot\u003c/h3\u003e\n\u003cp\u003eThe PLT plot displays groups of curves. A group consists of the components oil, gas and water. The curves within a group are stacked, the biggest component first.\u003c/p\u003e\n",
                 url:      "/plot-window/pltplot/"
             };
         
@@ -2478,8 +2520,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/flowdiagnosticsplots/"] = {
                 title:    "Flow Diagnostics Plots",
-                content:  " Flow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.\nThey are managed from the folder Flow Diagnostics Plots located in Plot Project Tree in the Plot Main Window.\nThis folder contains a default Flow Characteristics Plot and Well Allocation Plot. In addition, two folders with stored well allocation and flow characteristics plots will show up if there are any of those in the model.\nPlease refer to Cell Results-\u0026gt; Flow Diagnostic Results for a description of the results and references to more information about the methodology.\nWell Allocation Plots Well allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.\nIn addition a Cumulative Saturation by Time of Flight plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.\nBranches Each branch of the well will be assigned a separate Track. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with Branch Detection On ( See Well Pipe Geometry ). Multi Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See Dummy branches ).\nCreating Well Allocation Plots To plot the Well allocation for a well, right-click the well in the Project Tree or in the 3D View and invoke the command Plot Well Allocation.\nThe command updates the default Well Allocation Plot with new values based on the selection and the settings in the active view. This plot can then be copied to the Stored Plots folder by the context command Add Stored Well Allocation Plot.\nOptions The Legend, Total Allocation pie chart, Cumulative Saturation, and the Well Flow/Allocation can be turned on or off from the toggles in the Project Tree. The other options are controlled from the property panel of a Well Allocation Plot:\n Name \u0026ndash; Auto generated name used as plot title Show Plot Title \u0026ndash; Toggles whether to show the title in the plot Plot Data \u0026ndash; Options controlling when and what the plot is based on  Case \u0026ndash; The case to plot data from Time Step \u0026ndash; The selected time step Well \u0026ndash; The simulation well to plot  Options  Plot Type  Allocation \u0026ndash; Plots Reservoir well flow rates along with how this well supports/are supported by other wells ( This option is only available for cases with Flux results available ) Well Flow \u0026ndash; Plots Surface Well Flow Rates together with phase split between Oil, Gas, and Water  Flow Type  Accumulated \u0026ndash; Plots an approximation of the accumulated flow along the well Inflow Rates \u0026ndash; Plots the rate of flow from the connection into the well  Group Small Contributions \u0026ndash; Groups small well contributions into a group called Other Threshold \u0026ndash; Threshold used by the Group Small Contributions option    Depth Settings The depth value in the plot can be controlled by selecting the Accumulated Flow/Inflow Rates item in the Project Tree. This item represents the Well-Log-like part of the Well Allocation Plot and its properties are shown below:\n Name \u0026ndash; The plot name, updated automatically based on the Flow Type and well. Depth Type  Pseudo Length \u0026ndash; Use the length along the visualized simulation well pipe as depth. In this mode the curves are extended somewhat above zero depth keeping the curve values constant. This is done to make it easier to see the final values of the curves relative to each other.\nThe depth are calculated with Branch detection On and using the Interpolated well pipe geometry.\n( See Well Pipe Geometry ) TVD \u0026ndash; Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells. Connection Number \u0026ndash; Use the number of connections counted from the top on the depth-axis.  Visible Depth Range \u0026ndash; These options control the depth zoom.  Auto Scale \u0026ndash; Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made. Min, Max \u0026ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.    Accessing the Plot Data The command context command Show Plot Data will show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the ascii data to a file directly by using the context command Export Plot Data to Text File on the Accumulated Flow/Inflow Rates item in the Project Tree.\nThe total accumulation data can also be viewed in ascci format by the command Show Total Allocation Data.\nFlow Characteristics Plot This window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.\n Lorenz Coefficient \u0026ndash; This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs. Flow Capacity vs Storage Capacity \u0026ndash; This plot displays one curve for each time step of the F-phi curve for the reservoir. Sweep Efficiency \u0026ndash; This plot displays one Sweep Efficiency curve for each selected time step.  Settings  Case \u0026ndash; Selects the source case for the plot. Time Steps \u0026ndash; These options selects the time steps to be used in the plot.  All With Calculated FlowDiagnostics \u0026ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using Cell Results, Well Allocation Plots, or Well Log Extraction Curves.\n Selected \u0026ndash; Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix *. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.  Region \u0026ndash; These group of options controls the cell region of interest for the plot.  Cell Filter \u0026ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection. All Active Cells \u0026ndash; Use all the active cells in the model (default) Visible Cells \u0026ndash; Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.  View \u0026ndash; The view to use as cell filter  Injector Producer Communication \u0026ndash; The region of communication between selected producers and injectors. See Flow Diagnostic Results  Tracer Filter \u0026ndash; Wild card based filter-text to filter the list of tracers list \u0026ndash; Producer and injector tracers to select Show Region \u0026ndash; Button to create (or edit) a 3D View showing the selected region of cells. Min communication \u0026ndash; A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.  Flooded by Injector/Drained by Producer \u0026ndash; The region with a Time Of Flight from the selected tracers below the selected threshold. Tracer Filter/list/Show Region \u0026ndash; See above. Max Time of Flight [days] \u0026ndash; Only cells with a Time of Flight value less then this value are used.  Options  Legend \u0026ndash; Toggles the legend on/off Aquifer Cell Threshold \u0026ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold * total pore volume.    ",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsPlotsOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eFlow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.\u003c/p\u003e\n\n\u003cp\u003eThey are managed from the folder \u003cstrong\u003eFlow Diagnostics Plots\u003c/strong\u003e located in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e in the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsPlotsProjectTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis folder contains a default \u003cstrong\u003eFlow Characteristics Plot\u003c/strong\u003e and \u003cstrong\u003eWell Allocation Plot\u003c/strong\u003e. In addition, two folders with stored  well allocation and flow characteristics plots will show up if there are any of those in the model.\u003c/p\u003e\n\n\u003cp\u003ePlease refer to \u003ca href=\"/3d-main-window/cellresults/#flow-diagnostic-results\"\u003eCell Results-\u0026gt; Flow Diagnostic Results\u003c/a\u003e for a description of the results and references to more information about the methodology.\u003c/p\u003e\n\n\u003ch2 id=\"well-allocation-plots\"\u003eWell Allocation Plots\u003c/h2\u003e\n\n\u003cp\u003eWell allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.\u003c/p\u003e\n\n\u003cp\u003eIn addition a \u003cstrong\u003eCumulative Saturation by Time of Flight\u003c/strong\u003e plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.\u003c/p\u003e\n\n\u003ch3 id=\"branches\"\u003eBranches\u003c/h3\u003e\n\n\u003cp\u003eEach branch of the well will be assigned a separate \u003cstrong\u003eTrack\u003c/strong\u003e. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with \u003cstrong\u003eBranch Detection\u003c/strong\u003e \u003cem\u003eOn\u003c/em\u003e ( See \u003ca href=\"/wells-and-completions/simulationwells/#well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/a\u003e ).\nMulti Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See  \u003ca href=\"/wells-and-completions/simulationwells/#dummy-branches\"\u003eDummy branches\u003c/a\u003e ).\u003c/p\u003e\n\n\u003ch3 id=\"creating-well-allocation-plots\"\u003eCreating Well Allocation Plots\u003c/h3\u003e\n\n\u003cp\u003eTo plot the Well allocation for a well, right-click the well in the \u003cstrong\u003eProject Tree\u003c/strong\u003e or in the \u003cstrong\u003e3D View\u003c/strong\u003e and invoke the command \u003cstrong\u003ePlot Well Allocation\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SimulationWellContextMenu.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe command updates the default \u003cstrong\u003eWell Allocation Plot\u003c/strong\u003e with new values based on the selection and the settings in the active view. This plot can then be copied to the \u003cstrong\u003eStored Plots\u003c/strong\u003e folder by the context command \u003cstrong\u003eAdd Stored Well Allocation Plot\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"options\"\u003eOptions\u003c/h3\u003e\n\n\u003cp\u003eThe \u003cstrong\u003eLegend\u003c/strong\u003e, \u003cstrong\u003eTotal Allocation\u003c/strong\u003e pie chart, \u003cstrong\u003eCumulative Saturation\u003c/strong\u003e, and the \u003cstrong\u003eWell Flow/Allocation\u003c/strong\u003e can be turned on or off from the toggles in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The other options are controlled from the property panel of a Well Allocation Plot:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Auto generated name used as plot title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Plot Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the title in the plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Data\u003c/strong\u003e \u0026ndash; Options controlling when and what the plot is based on\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; The case to plot data from\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; The selected time step\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e \u0026ndash; The simulation well to plot\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Type\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAllocation\u003c/strong\u003e \u0026ndash; Plots \u003cem\u003eReservoir well flow rates\u003c/em\u003e along with how this well supports/are\nsupported by other wells ( This option is only available for cases with Flux results available )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Flow\u003c/strong\u003e \u0026ndash; Plots \u003cem\u003eSurface Well Flow Rates\u003c/em\u003e together with phase split between Oil, Gas, and Water\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Type\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAccumulated\u003c/strong\u003e \u0026ndash; Plots an approximation of the accumulated flow along the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInflow Rates\u003c/strong\u003e \u0026ndash; Plots the rate of flow from the connection into the well\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup Small Contributions\u003c/strong\u003e \u0026ndash; Groups small well contributions into a group called \u003cstrong\u003eOther\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThreshold\u003c/strong\u003e \u0026ndash; Threshold used by the \u003cstrong\u003eGroup Small Contributions\u003c/strong\u003e option\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"depth-settings\"\u003eDepth Settings\u003c/h3\u003e\n\n\u003cp\u003eThe depth value in the plot can be controlled by selecting the \u003cstrong\u003eAccumulated Flow\u003c/strong\u003e/\u003cstrong\u003eInflow Rates\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. This item represents the Well-Log-like part of the Well Allocation Plot and its properties are shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationWellLogProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; The plot name, updated automatically based on the \u003cstrong\u003eFlow Type\u003c/strong\u003e and well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Type\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePseudo Length\u003c/strong\u003e  \u0026ndash; Use the length along the visualized simulation well pipe as depth.\nIn this mode the curves are extended somewhat above zero depth keeping the curve\nvalues constant. This is done to make it easier to see the final values of the curves relative to each other.\u003cbr /\u003e\nThe depth are calculated with \u003cstrong\u003eBranch detection\u003c/strong\u003e \u003cem\u003eOn\u003c/em\u003e and using the \u003cstrong\u003eInterpolated\u003c/strong\u003e well pipe geometry.\u003cbr /\u003e\n( See \u003ca href=\"/wells-and-completions/simulationwells/#well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTVD\u003c/strong\u003e \u0026ndash; Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConnection Number\u003c/strong\u003e \u0026ndash; Use the number of connections counted from the top on the depth-axis.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Depth Range\u003c/strong\u003e \u0026ndash; These options control the depth zoom.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Scale\u003c/strong\u003e \u0026ndash; Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e, \u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"accessing-the-plot-data\"\u003eAccessing the Plot Data\u003c/h3\u003e\n\n\u003cp\u003eThe command context command \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\u003c/p\u003e\n\n\u003cp\u003eIt is also possible to save the ascii data to a file directly by using the context command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e on the \u003cstrong\u003eAccumulated Flow\u003c/strong\u003e/\u003cstrong\u003eInflow Rates\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe total accumulation data can also be viewed in ascci format by the command \u003cstrong\u003eShow Total Allocation Data\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"flow-characteristics-plot\"\u003eFlow Characteristics Plot\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowCharacteristicsPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThis window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLorenz Coefficient\u003c/strong\u003e \u0026ndash; This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Capacity vs Storage Capacity\u003c/strong\u003e \u0026ndash; This plot displays one curve for each time step of the F-phi curve for the reservoir.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSweep Efficiency\u003c/strong\u003e \u0026ndash; This plot displays one Sweep Efficiency curve for each selected time step.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"settings\"\u003eSettings\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowCharacteristicsPropertyPanel.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Selects the source case for the plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Steps\u003c/strong\u003e \u0026ndash; These options selects the time steps to be used in the plot.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll With Calculated FlowDiagnostics\u003c/strong\u003e \u0026ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using  \u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e, Well Allocation Plots, or \u003ca href=\"/plot-window/welllogsandplots/#well-log-extraction-curves\"\u003eWell Log Extraction Curves\u003c/a\u003e.\u003cbr /\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelected\u003c/strong\u003e \u0026ndash; Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix \u003cem\u003e\u003ccode\u003e*\u003c/code\u003e\u003c/em\u003e. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e \u0026ndash; These group of options controls the cell region of interest for the plot.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Filter\u003c/strong\u003e \u0026ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAll Active Cells\u003c/strong\u003e \u0026ndash; Use all the active cells in the model (default)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Cells\u003c/strong\u003e \u0026ndash; Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e \u0026ndash; The view to use as cell filter\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjector Producer Communication\u003c/strong\u003e \u0026ndash; The region of communication between selected producers and injectors. See  \u003ca href=\"/3d-main-window/cellresults/#Flow-Diagnostic-Results\"\u003eFlow Diagnostic Results\u003c/a\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Filter\u003c/strong\u003e \u0026ndash; Wild card based filter-text to filter the list of tracers\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003elist\u003c/strong\u003e \u0026ndash; Producer and injector tracers to select\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Region\u003c/strong\u003e \u0026ndash; Button to create (or edit) a 3D View showing the selected region of cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin communication\u003c/strong\u003e \u0026ndash; A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlooded by Injector\u003c/strong\u003e/\u003cstrong\u003eDrained by Producer\u003c/strong\u003e \u0026ndash; The region with a Time Of Flight from the selected tracers below the selected threshold.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Filter\u003c/strong\u003e/\u003cem\u003elist\u003c/em\u003e/\u003cstrong\u003eShow Region\u003c/strong\u003e \u0026ndash; See above.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax Time of Flight [days]\u003c/strong\u003e \u0026ndash; Only cells with a Time of Flight value less then this value are used.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLegend\u003c/strong\u003e \u0026ndash; Toggles the legend on/off\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer Cell Threshold\u003c/strong\u003e \u0026ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold \u003cem\u003e\u003ccode\u003e*\u003c/code\u003e\u003c/em\u003e total pore volume.\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "Flow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.\nThey are managed from the folder Flow Diagnostics Plots located in Plot Project Tree in the Plot Main Window.\nThis folder contains a default Flow Characteristics Plot and Well Allocation Plot. In addition, two folders with stored well allocation and flow characteristics plots will show up if there are any of those in the model.\nPlease refer to Cell Results-\u0026gt; Flow Diagnostic Results for a description of the results and references to more information about the methodology.\nWell Allocation Plots Well allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.\nIn addition a Cumulative Saturation by Time of Flight plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.\nBranches Each branch of the well will be assigned a separate Track. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with Branch Detection On ( See Well Pipe Geometry ). Multi Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See Dummy branches ).\nCreating Well Allocation Plots To plot the Well allocation for a well, right-click the well in the Project Tree or in the 3D View and invoke the command Plot Well Allocation.\nThe command updates the default Well Allocation Plot with new values based on the selection and the settings in the active view. This plot can then be copied to the Stored Plots folder by the context command Add Stored Well Allocation Plot.\nOptions The Legend, Total Allocation pie chart, Cumulative Saturation, and the Well Flow/Allocation can be turned on or off from the toggles in the Project Tree. The other options are controlled from the property panel of a Well Allocation Plot:\n Name \u0026ndash; Auto generated name used as plot title Show Plot Title \u0026ndash; Toggles whether to show the title in the plot Plot Data \u0026ndash; Options controlling when and what the plot is based on  Case \u0026ndash; The case to plot data from Time Step \u0026ndash; The selected time step Well \u0026ndash; The simulation well to plot   Options  Plot Type  Allocation \u0026ndash; Plots Reservoir well flow rates along with how this well supports/are supported by other wells ( This option is only available for cases with Flux results available ) Well Flow \u0026ndash; Plots Surface Well Flow Rates together with phase split between Oil, Gas, and Water   Flow Type  Accumulated \u0026ndash; Plots an approximation of the accumulated flow along the well Inflow Rates \u0026ndash; Plots the rate of flow from the connection into the well   Group Small Contributions \u0026ndash; Groups small well contributions into a group called Other Threshold \u0026ndash; Threshold used by the Group Small Contributions option    Depth Settings The depth value in the plot can be controlled by selecting the Accumulated Flow/Inflow Rates item in the Project Tree. This item represents the Well-Log-like part of the Well Allocation Plot and its properties are shown below:\n Name \u0026ndash; The plot name, updated automatically based on the Flow Type and well. Depth Type  Pseudo Length \u0026ndash; Use the length along the visualized simulation well pipe as depth. In this mode the curves are extended somewhat above zero depth keeping the curve values constant. This is done to make it easier to see the final values of the curves relative to each other.\nThe depth are calculated with Branch detection On and using the Interpolated well pipe geometry.\n( See Well Pipe Geometry ) TVD \u0026ndash; Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells. Connection Number \u0026ndash; Use the number of connections counted from the top on the depth-axis.   Visible Depth Range \u0026ndash; These options control the depth zoom.  Auto Scale \u0026ndash; Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made. Min, Max \u0026ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.    Accessing the Plot Data The command context command Show Plot Data will show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\nIt is also possible to save the ascii data to a file directly by using the context command Export Plot Data to Text File on the Accumulated Flow/Inflow Rates item in the Project Tree.\nThe total accumulation data can also be viewed in ascci format by the command Show Total Allocation Data.\nFlow Characteristics Plot This window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.\n Lorenz Coefficient \u0026ndash; This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs. Flow Capacity vs Storage Capacity \u0026ndash; This plot displays one curve for each time step of the F-phi curve for the reservoir. Sweep Efficiency \u0026ndash; This plot displays one Sweep Efficiency curve for each selected time step.  Settings  Case \u0026ndash; Selects the source case for the plot. Time Steps \u0026ndash; These options selects the time steps to be used in the plot.  All With Calculated FlowDiagnostics \u0026ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using Cell Results, Well Allocation Plots, or Well Log Extraction Curves. Selected \u0026ndash; Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix *. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.   Region \u0026ndash; These group of options controls the cell region of interest for the plot.  Cell Filter \u0026ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.  All Active Cells \u0026ndash; Use all the active cells in the model (default) Visible Cells \u0026ndash; Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.  View \u0026ndash; The view to use as cell filter   Injector Producer Communication \u0026ndash; The region of communication between selected producers and injectors. See Flow Diagnostic Results  Tracer Filter \u0026ndash; Wild card based filter-text to filter the list of tracers list \u0026ndash; Producer and injector tracers to select Show Region \u0026ndash; Button to create (or edit) a 3D View showing the selected region of cells. Min communication \u0026ndash; A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.   Flooded by Injector/Drained by Producer \u0026ndash; The region with a Time Of Flight from the selected tracers below the selected threshold. Tracer Filter/list/Show Region \u0026ndash; See above. Max Time of Flight [days] \u0026ndash; Only cells with a Time of Flight value less then this value are used.     Options  Legend \u0026ndash; Toggles the legend on/off Aquifer Cell Threshold \u0026ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold * total pore volume.    ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsPlotsOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFlow Diagnostics Plots can be used to view well allocation, well inflow rates, cumulative saturation along time of flight and flow characteristics.\u003c/p\u003e\n\u003cp\u003eThey are managed from the folder \u003cstrong\u003eFlow Diagnostics Plots\u003c/strong\u003e located in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e in the \u003cstrong\u003ePlot Main Window\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsPlotsProjectTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis folder contains a default \u003cstrong\u003eFlow Characteristics Plot\u003c/strong\u003e and \u003cstrong\u003eWell Allocation Plot\u003c/strong\u003e. In addition, two folders with stored  well allocation and flow characteristics plots will show up if there are any of those in the model.\u003c/p\u003e\n\u003cp\u003ePlease refer to \u003ca href=\"/3d-main-window/cellresults/#flow-diagnostic-results\"\u003eCell Results-\u0026gt; Flow Diagnostic Results\u003c/a\u003e for a description of the results and references to more information about the methodology.\u003c/p\u003e\n\u003ch2 id=\"well-allocation-plots\"\u003eWell Allocation Plots\u003c/h2\u003e\n\u003cp\u003eWell allocation plots show the flow along a specified well, along with either phase distribution or the amount of support from/to other wells. The total phase or allocation is shown in the legend and as a pie chart, while the well flow is shown in a depth value vs flow graph.\u003c/p\u003e\n\u003cp\u003eIn addition a \u003cstrong\u003eCumulative Saturation by Time of Flight\u003c/strong\u003e plot may be shown. This little plot illustrates how the total saturation changes as you go from the well-connection-cells along increasing time of flight adding the cells as you go.\u003c/p\u003e\n\u003ch3 id=\"branches\"\u003eBranches\u003c/h3\u003e\n\u003cp\u003eEach branch of the well will be assigned a separate \u003cstrong\u003eTrack\u003c/strong\u003e. For normal wells this is based on the branch detection algorithm used for Well Pipe visualization, and will correspond to the pipe visualization with \u003cstrong\u003eBranch Detection\u003c/strong\u003e \u003cem\u003eOn\u003c/em\u003e ( See \u003ca href=\"/wells-and-completions/simulationwells/#well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/a\u003e ).\nMulti Segment Wells will be displayed according to their branch information, but tiny branches consisting of only one connection are lumped into the main branch to make the visualization more understandable ( See  \u003ca href=\"/wells-and-completions/simulationwells/#dummy-branches\"\u003eDummy branches\u003c/a\u003e ).\u003c/p\u003e\n\u003ch3 id=\"creating-well-allocation-plots\"\u003eCreating Well Allocation Plots\u003c/h3\u003e\n\u003cp\u003eTo plot the Well allocation for a well, right-click the well in the \u003cstrong\u003eProject Tree\u003c/strong\u003e or in the \u003cstrong\u003e3D View\u003c/strong\u003e and invoke the command \u003cstrong\u003ePlot Well Allocation\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SimulationWellContextMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe command updates the default \u003cstrong\u003eWell Allocation Plot\u003c/strong\u003e with new values based on the selection and the settings in the active view. This plot can then be copied to the \u003cstrong\u003eStored Plots\u003c/strong\u003e folder by the context command \u003cstrong\u003eAdd Stored Well Allocation Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"options\"\u003eOptions\u003c/h3\u003e\n\u003cp\u003eThe \u003cstrong\u003eLegend\u003c/strong\u003e, \u003cstrong\u003eTotal Allocation\u003c/strong\u003e pie chart, \u003cstrong\u003eCumulative Saturation\u003c/strong\u003e, and the \u003cstrong\u003eWell Flow/Allocation\u003c/strong\u003e can be turned on or off from the toggles in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. The other options are controlled from the property panel of a Well Allocation Plot:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Auto generated name used as plot title\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Plot Title\u003c/strong\u003e \u0026ndash; Toggles whether to show the title in the plot\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Data\u003c/strong\u003e \u0026ndash; Options controlling when and what the plot is based on\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; The case to plot data from\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; The selected time step\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e \u0026ndash; The simulation well to plot\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Type\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAllocation\u003c/strong\u003e \u0026ndash; Plots \u003cem\u003eReservoir well flow rates\u003c/em\u003e along with how this well supports/are \nsupported by other wells ( This option is only available for cases with Flux results available )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Flow\u003c/strong\u003e \u0026ndash; Plots \u003cem\u003eSurface Well Flow Rates\u003c/em\u003e together with phase split between Oil, Gas, and Water\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Type\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAccumulated\u003c/strong\u003e \u0026ndash; Plots an approximation of the accumulated flow along the well\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInflow Rates\u003c/strong\u003e \u0026ndash; Plots the rate of flow from the connection into the well\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup Small Contributions\u003c/strong\u003e \u0026ndash; Groups small well contributions into a group called \u003cstrong\u003eOther\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThreshold\u003c/strong\u003e \u0026ndash; Threshold used by the \u003cstrong\u003eGroup Small Contributions\u003c/strong\u003e option\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"depth-settings\"\u003eDepth Settings\u003c/h3\u003e\n\u003cp\u003eThe depth value in the plot can be controlled by selecting the \u003cstrong\u003eAccumulated Flow\u003c/strong\u003e/\u003cstrong\u003eInflow Rates\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. This item represents the Well-Log-like part of the Well Allocation Plot and its properties are shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationWellLogProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; The plot name, updated automatically based on the \u003cstrong\u003eFlow Type\u003c/strong\u003e and well.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Type\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePseudo Length\u003c/strong\u003e  \u0026ndash; Use the length along the visualized simulation well pipe as depth. \nIn this mode the curves are extended somewhat above zero depth keeping the curve \nvalues constant. This is done to make it easier to see the final values of the curves relative to each other.\u003cbr\u003e\nThe depth are calculated with \u003cstrong\u003eBranch detection\u003c/strong\u003e \u003cem\u003eOn\u003c/em\u003e and using the \u003cstrong\u003eInterpolated\u003c/strong\u003e well pipe geometry.\u003cbr\u003e\n( See \u003ca href=\"/wells-and-completions/simulationwells/#well-pipe-geometry\"\u003eWell Pipe Geometry\u003c/a\u003e )\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTVD\u003c/strong\u003e \u0026ndash; Use True Vertical Depth on the depth-axis. This will produce distorted plots for horizontal or near horizontal wells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConnection Number\u003c/strong\u003e \u0026ndash; Use the number of connections counted from the top on the depth-axis.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Depth Range\u003c/strong\u003e \u0026ndash; These options control the depth zoom.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAuto Scale\u003c/strong\u003e \u0026ndash; Toggles autoscale on/off. The plot is autoscaled when significant changes to its settings are made.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin\u003c/strong\u003e, \u003cstrong\u003eMax\u003c/strong\u003e \u0026ndash; Sets the visible depth range. These are updated when zooming using the mouse wheel etc.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"accessing-the-plot-data\"\u003eAccessing the Plot Data\u003c/h3\u003e\n\u003cp\u003eThe command context command \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will show a window containing the plot data in ascii format. The content of this window is easy to copy and paste into Excel or other tools for further processing.\u003c/p\u003e\n\u003cp\u003eIt is also possible to save the ascii data to a file directly by using the context command \u003cstrong\u003eExport Plot Data to Text File\u003c/strong\u003e on the \u003cstrong\u003eAccumulated Flow\u003c/strong\u003e/\u003cstrong\u003eInflow Rates\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe total accumulation data can also be viewed in ascci format by the command \u003cstrong\u003eShow Total Allocation Data\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"flow-characteristics-plot\"\u003eFlow Characteristics Plot\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowCharacteristicsPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis window displays three different graphs describing the overall behavior of the reservoir for each time step from a flow diagnostics point of view.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLorenz Coefficient\u003c/strong\u003e \u0026ndash; This plot displays the Lorenz coefficient for the complete reservoir for each selected time step. The time step color is used as a reference for the time step in the other graphs.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Capacity vs Storage Capacity\u003c/strong\u003e \u0026ndash; This plot displays one curve for each time step of the F-phi curve for the reservoir.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSweep Efficiency\u003c/strong\u003e \u0026ndash; This plot displays one Sweep Efficiency curve for each selected time step.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"settings\"\u003eSettings\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowCharacteristicsPropertyPanel.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e \u0026ndash; Selects the source case for the plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Steps\u003c/strong\u003e \u0026ndash; These options selects the time steps to be used in the plot.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll With Calculated FlowDiagnostics\u003c/strong\u003e \u0026ndash; Plot data from all the time steps already solved by the Flow Diagnostics Solver, but nothing more. The solver will be run implicitly when the user requests any Flow Diagnostics results on a particular time step using  \u003ca href=\"/3d-main-window/cellresults/\"\u003eCell Results\u003c/a\u003e, Well Allocation Plots, or \u003ca href=\"/plot-window/welllogsandplots/#well-log-extraction-curves\"\u003eWell Log Extraction Curves\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelected\u003c/strong\u003e \u0026ndash; Use the selected time steps only. Activating this options displays a listbox with all the available time steps in the 3D case. Time steps already solved by the Flow Diagnostics Solver are marked with an asterix \u003cem\u003e\u003ccode\u003e*\u003c/code\u003e\u003c/em\u003e. Select the interesting time steps and press apply to invoke the solver for unsolved time steps, and to show them in the plot.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e \u0026ndash; These group of options controls the cell region of interest for the plot.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Filter\u003c/strong\u003e \u0026ndash; Selects the type of cell filtering to apply. Sub-options are displayed depending on the selection.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAll Active Cells\u003c/strong\u003e \u0026ndash; Use all the active cells in the model (default)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVisible Cells\u003c/strong\u003e \u0026ndash; Use the visible cells in a particular predefined view as cell region. This option will respect all the filter settings in the view, and use the correct cell set for each time step.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eView\u003c/strong\u003e \u0026ndash; The view to use as cell filter\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInjector Producer Communication\u003c/strong\u003e \u0026ndash; The region of communication between selected producers and injectors. See  \u003ca href=\"/3d-main-window/cellresults/#Flow-Diagnostic-Results\"\u003eFlow Diagnostic Results\u003c/a\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Filter\u003c/strong\u003e \u0026ndash; Wild card based filter-text to filter the list of tracers\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003elist\u003c/strong\u003e \u0026ndash; Producer and injector tracers to select\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Region\u003c/strong\u003e \u0026ndash; Button to create (or edit) a 3D View showing the selected region of cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMin communication\u003c/strong\u003e \u0026ndash; A threshold for the cells communication value. Cells with communication below this threshold is omitted from the region.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlooded by Injector\u003c/strong\u003e/\u003cstrong\u003eDrained by Producer\u003c/strong\u003e \u0026ndash; The region with a Time Of Flight from the selected tracers below the selected threshold.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Filter\u003c/strong\u003e/\u003cem\u003elist\u003c/em\u003e/\u003cstrong\u003eShow Region\u003c/strong\u003e \u0026ndash; See above.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax Time of Flight [days]\u003c/strong\u003e \u0026ndash; Only cells with a Time of Flight value less then this value are used.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOptions\u003c/strong\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLegend\u003c/strong\u003e \u0026ndash; Toggles the legend on/off\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAquifer Cell Threshold\u003c/strong\u003e \u0026ndash; This threshold can be used to exclude unwanted effects of aquifers. Cells are excluded if their pore volume are larger than threshold \u003cem\u003e\u003ccode\u003e*\u003c/code\u003e\u003c/em\u003e total pore volume.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/flowdiagnosticsplots/"
             };
         
@@ -2487,8 +2529,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/gridstatisticsdialog/"] = {
                 title:    "Grid Statistics Dialog",
-                content:  " ResInsight 3D Views has an info box in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select Grid Statistics to bring up the dialog.\nGrid Statistics Dialog Fields The dialog consist of three information parts.\n Info text Histogram Cumulative Histogram  Info Text The Info Text field shows general info about the case, the selected results, and some statistics.\nHistogram The histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\n The mean value ( a blue line ) P10 and P90 ( red lines )  Cumulative Histogram The cumulative histogram shows av accumulated version of the histogram above.\nGrid Statistics Configuration A grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The Statistics Options of the info box is shown in the figure below with default settings. These settings become available by clicking in the info box or the info box node in Project Tree.\nThe options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.\nStatistics Options  Statistics Time Range -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option. Statistics Cell Range -– Controls if visible cells or all active cells is included when statistics is computed.  Snapshot The Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system\u0026rsquo;s clipboard, while the rightmost button creates a file containing the snapshot.\nThe main window also has a snapshot toolbar containing the button Snapshot All Views. This button will include a snapshot of the Grid Statistics dialog if opened.\n\r",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridStatisticsDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight 3D Views has an \u003ca href=\"/3d-main-window/3dviews/#info-box\"\u003einfo box\u003c/a\u003e in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select \u003cstrong\u003eGrid Statistics\u003c/strong\u003e to bring up the dialog.\u003c/p\u003e\n\n\u003ch2 id=\"grid-statistics-dialog-fields\"\u003eGrid Statistics Dialog Fields\u003c/h2\u003e\n\n\u003cp\u003eThe dialog consist of three information parts.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eInfo text\u003c/li\u003e\n\u003cli\u003eHistogram\u003c/li\u003e\n\u003cli\u003eCumulative Histogram\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"info-text\"\u003eInfo Text\u003c/h3\u003e\n\n\u003cp\u003eThe Info Text field shows general info about the case, the selected results, and some statistics.\u003c/p\u003e\n\n\u003ch3 id=\"histogram\"\u003eHistogram\u003c/h3\u003e\n\n\u003cp\u003eThe histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eThe mean value ( a blue line )\u003c/li\u003e\n\u003cli\u003eP10 and P90 ( red lines )\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"cumulative-histogram\"\u003eCumulative Histogram\u003c/h3\u003e\n\n\u003cp\u003eThe cumulative histogram shows av accumulated version of the histogram above.\u003c/p\u003e\n\n\u003ch2 id=\"grid-statistics-configuration\"\u003eGrid Statistics Configuration\u003c/h2\u003e\n\n\u003cp\u003eA grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The Statistics Options of the info box is shown in the figure below with default settings. These settings become available by clicking in the info box or the info box node in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InfoBoxConfig.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.\u003c/p\u003e\n\n\u003ch3 id=\"statistics-options\"\u003eStatistics Options\u003c/h3\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Time Range\u003c/strong\u003e -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Cell Range\u003c/strong\u003e -– Controls if visible cells or all active cells is included when statistics is computed.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"snapshot\"\u003eSnapshot\u003c/h2\u003e\n\n\u003cp\u003eThe Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system\u0026rsquo;s clipboard, while the rightmost button creates a file containing the snapshot.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe main window also has a snapshot toolbar containing the button \u003ca href=\"/export/snapshots/#snapshot-all-viewsplots-to-file-\"\u003eSnapshot All Views\u003c/a\u003e. This button will include a snapshot of the Grid Statistics dialog if opened.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
+                content:  "ResInsight 3D Views has an info box in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select Grid Statistics to bring up the dialog.\nGrid Statistics Dialog Fields The dialog consist of three information parts.\n Info text Histogram Cumulative Histogram  Info Text The Info Text field shows general info about the case, the selected results, and some statistics.\nHistogram The histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\n The mean value ( a blue line ) P10 and P90 ( red lines )  Cumulative Histogram The cumulative histogram shows av accumulated version of the histogram above.\nGrid Statistics Configuration A grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The Statistics Options of the info box is shown in the figure below with default settings. These settings become available by clicking in the info box or the info box node in Project Tree.\nThe options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.\nStatistics Options  Statistics Time Range -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option. Statistics Cell Range -– Controls if visible cells or all active cells is included when statistics is computed.  Snapshot The Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system\u0026rsquo;s clipboard, while the rightmost button creates a file containing the snapshot.\nThe main window also has a snapshot toolbar containing the button Snapshot All Views. This button will include a snapshot of the Grid Statistics dialog if opened.\n\r",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridStatisticsDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight 3D Views has an \u003ca href=\"/3d-main-window/3dviews/#info-box\"\u003einfo box\u003c/a\u003e in the upper right corner displaying statistics for the current view. A more detailed version of this information may also be displayed in a separate dialog window. Right click on the 3D view background and select \u003cstrong\u003eGrid Statistics\u003c/strong\u003e to bring up the dialog.\u003c/p\u003e\n\u003ch2 id=\"grid-statistics-dialog-fields\"\u003eGrid Statistics Dialog Fields\u003c/h2\u003e\n\u003cp\u003eThe dialog consist of three information parts.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eInfo text\u003c/li\u003e\n\u003cli\u003eHistogram\u003c/li\u003e\n\u003cli\u003eCumulative Histogram\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"info-text\"\u003eInfo Text\u003c/h3\u003e\n\u003cp\u003eThe Info Text field shows general info about the case, the selected results, and some statistics.\u003c/p\u003e\n\u003ch3 id=\"histogram\"\u003eHistogram\u003c/h3\u003e\n\u003cp\u003eThe histogram shows a histogram of the complete time series of the currently loaded Cell Result together with:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe mean value ( a blue line )\u003c/li\u003e\n\u003cli\u003eP10 and P90 ( red lines )\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"cumulative-histogram\"\u003eCumulative Histogram\u003c/h3\u003e\n\u003cp\u003eThe cumulative histogram shows av accumulated version of the histogram above.\u003c/p\u003e\n\u003ch2 id=\"grid-statistics-configuration\"\u003eGrid Statistics Configuration\u003c/h2\u003e\n\u003cp\u003eA grid statistics dialog is always connected to the 3D view from where it was opened. When the contents of the 3D view changes due to user interactions, the grid statistics dialog contents will be updated automatically along with the info box. The Statistics Options of the info box is shown in the figure below with default settings. These settings become available by clicking in the info box or the info box node in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/InfoBoxConfig.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe options in the Visibility group apply to the info box only and do not affect the Grid Statistics dialog, while the options in the Statistics Options group affect both.\u003c/p\u003e\n\u003ch3 id=\"statistics-options\"\u003eStatistics Options\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Time Range\u003c/strong\u003e -– Controls whether all time steps or only the current time step are included when statistics is computed. Flow Diagnostic results can only use the current time step option.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Cell Range\u003c/strong\u003e -– Controls if visible cells or all active cells is included when statistics is computed.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"snapshot\"\u003eSnapshot\u003c/h2\u003e\n\u003cp\u003eThe Grid Statistics dialog has a toolbar containing two buttons for snapshot functionality. The leftmost button copies a snapshot of the dialog contents to the operating system\u0026rsquo;s clipboard, while the rightmost button creates a file containing the snapshot.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe main window also has a snapshot toolbar containing the button \u003c!-- raw HTML omitted --\u003eSnapshot All Views\u003c!-- raw HTML omitted --\u003e. This button will include a snapshot of the Grid Statistics dialog if opened.\u003c/p\u003e\n\u003c/div\u003e\r\n\n",
                 url:      "/3d-main-window/gridstatisticsdialog/"
             };
         
@@ -2496,8 +2538,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/casegroupsandstatistics/"] = {
                 title:    "Grid Case Groups and Statistics",
-                content:  " Grid Case Group\u0026rsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).\nIf you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.\nCreating Grid Case Groups From Files The easiest way to create a Grid Case Group is to use the Import command: File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files or File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files Recursively\nThe latter command will display the recursive file import dialog described on the Summary Plots page.\nThe first command will display the \u0026ldquo;old\u0026rdquo; import dialog:  Add one or more search folders to the list on the left. The EGRID or GRID files found in these directories and sub directories are shown in the list to the right. If you want to remove some EGRID files from the list, select them and press the Remove button. When you are ready, press the OK button.  ResInsight then creates a Grid Case Group for you, and populates its Source Cases with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.\nManually A Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. Source Cases can then be added by using the mouse to drag and drop cases with equal grids into the Grid Case Group\u0026rsquo;s Source Case folder. This is useful if you want to create statistics based only on a subset of the source cases in an already created Grid Case Group.\nDrag and Drop of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the Shift key while dropping.\nViewing Special Source Cases To reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, select New view from the right-click menu. A new 3D View will the be created on that particular case.\nHow to limit system resource allocation To reduce memory usage, project loading time etc. remember to delete the 3D Views you do not need. 3D Views uses a lot of system resources.\n\rStatistics After creating a grid case group, an empty Statistics Case is created for you in the Derived Statistics folder of the Grid Case Group.\nSetting Up and Calculate The properties of non-calculated and calculated Statistics Case is shown below:\n Compute \u0026ndash; Starts to calculate requested statistical Properties. Edit \u0026ndash; Deletes the calculated results, and makes the controls to edit the setup available. Summary of calculation setup \u0026ndash; Summarizes what to calculate. Properties to consider \u0026ndash; These options makes it possible to select what Eclipse properties to include in the Statistical calculations. Adding variables increase the memory usage and the computational time. Percentile Setup \u0026ndash; Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations. Well Data Source Case \u0026ndash; This option selects which set of Simulation Wells to be shown along with the statistical results. You can select one of the Source Cases.  Percentile Methods Three Percentile methods are implemented:\n Interpolated Observation \u0026ndash; The values are sorted, and the two observations representing the probabilities closest to the percentile are interpolated to find the value for the percentile. This is the default method. Nearest Observation \u0026ndash; The values are sorted, and the first observation representing a probability higher or equal to the percentile probability is selected as the value for the percentile. This method is by some considered to be statistically more puristic. Histogram based estimate \u0026ndash; A histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.  Viewing the Results When the computation is complete, you have to create a 3D View on the Statistics Case to view the results. Use the right-click menu of the Statistics Case to create it.\nAdding Statistics Cases A new statistical calculation can be created by activating the right-click menu for Derived Statistic-\u0026gt;New Statistics Case.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridCaseGroupTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eGrid Case Group\u003c/strong\u003e\u0026rsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled \u003cem\u003erealizations\u003c/em\u003e).\u003c/p\u003e\n\n\u003cp\u003eIf you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.\u003c/p\u003e\n\n\u003ch2 id=\"creating-grid-case-groups\"\u003eCreating Grid Case Groups\u003c/h2\u003e\n\n\u003ch3 id=\"from-files\"\u003eFrom Files\u003c/h3\u003e\n\n\u003cp\u003eThe easiest way to create a \u003cstrong\u003eGrid Case Group\u003c/strong\u003e is to use the Import command:\n\u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files\u003c/strong\u003e or \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files Recursively\u003c/strong\u003e\u003c/p\u003e\n\n\u003cp\u003eThe latter command will display the recursive file import dialog described on the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe first command will display the \u0026ldquo;old\u0026rdquo; import dialog:\n\u003cimg src=\"/images/3d-main-window/CreateGridCaseGroupFromFileDialog.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eAdd one or more search folders to the list on the left.\u003c/li\u003e\n\u003cli\u003eThe EGRID or GRID files found in these directories and sub directories are shown in the list to the right.\u003c/li\u003e\n\u003cli\u003eIf you want to remove some EGRID files from the list, select them and press the \u003cstrong\u003eRemove\u003c/strong\u003e button.\u003c/li\u003e\n\u003cli\u003eWhen you are ready, press the \u003cstrong\u003eOK\u003c/strong\u003e button.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eResInsight then creates a \u003cstrong\u003eGrid Case Group\u003c/strong\u003e for you, and populates its \u003cstrong\u003eSource Cases\u003c/strong\u003e with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.\u003c/p\u003e\n\n\u003ch3 id=\"manually\"\u003eManually\u003c/h3\u003e\n\n\u003cp\u003eA Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. \u003cstrong\u003eSource Cases\u003c/strong\u003e can then be added by using the mouse to \u003cem\u003edrag and drop\u003c/em\u003e cases with equal grids into the \u003cstrong\u003eGrid Case Group\u003c/strong\u003e\u0026rsquo;s \u003cstrong\u003eSource Case\u003c/strong\u003e folder.\nThis is useful if you want to create statistics based only on a subset of the source cases in an already created \u003cstrong\u003eGrid Case Group\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cstrong\u003eDrag and Drop\u003c/strong\u003e of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the \u003cstrong\u003eShift\u003c/strong\u003e key while dropping.\u003c/p\u003e\n\n\u003ch2 id=\"viewing-special-source-cases\"\u003eViewing Special Source Cases\u003c/h2\u003e\n\n\u003cp\u003eTo reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, select \u003cstrong\u003eNew view\u003c/strong\u003e from the right-click menu. A new 3D View will the be created on that particular case.\u003c/p\u003e\n\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003ch5\u003eHow to limit system resource allocation\u003c/h5\u003e\nTo reduce memory usage, project loading time etc. remember to delete the 3D Views you do not need. 3D Views uses a lot of system resources.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\n\u003ch2 id=\"statistics\"\u003eStatistics\u003c/h2\u003e\n\n\u003cp\u003eAfter creating a grid case group, an empty \u003cstrong\u003eStatistics Case\u003c/strong\u003e is created for you in the \u003cstrong\u003eDerived Statistics\u003c/strong\u003e folder of the \u003cstrong\u003eGrid Case Group\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"setting-up-and-calculate\"\u003eSetting Up and Calculate\u003c/h3\u003e\n\n\u003cp\u003eThe properties of non-calculated and calculated \u003cstrong\u003eStatistics Case\u003c/strong\u003e is shown below:\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StatisticsCaseProperties.png\" alt=\"\" /\u003e  \u003cimg src=\"/images/3d-main-window/StatisticsCasePropertiesCalculated.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCompute\u003c/strong\u003e \u0026ndash;  Starts to calculate requested statistical Properties.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEdit\u003c/strong\u003e \u0026ndash; Deletes the calculated results, and makes the controls to edit the setup available.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSummary of calculation setup\u003c/strong\u003e \u0026ndash; Summarizes what to calculate.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties to consider\u003c/strong\u003e \u0026ndash; These options makes it possible to select what Eclipse properties to include in the Statistical calculations. Adding variables increase the memory usage and the computational time.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePercentile Setup\u003c/strong\u003e \u0026ndash; Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Data Source Case\u003c/strong\u003e \u0026ndash; This option selects which set of \u003cstrong\u003eSimulation Wells\u003c/strong\u003e to be shown along with the statistical results. You can select one of the \u003cstrong\u003eSource Cases\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"percentile-methods\"\u003ePercentile Methods\u003c/h4\u003e\n\n\u003cp\u003eThree Percentile methods are implemented:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInterpolated Observation\u003c/strong\u003e \u0026ndash;\nThe values are sorted, and the two observations representing the probabilities closest to the percentile are interpolated to find the value for the percentile. This is the default method.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNearest Observation\u003c/strong\u003e \u0026ndash;\nThe values are sorted, and the first observation representing a probability higher or equal to the percentile probability is selected as the value for the percentile. This method is by some considered to be statistically more puristic.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHistogram based estimate\u003c/strong\u003e \u0026ndash;\nA histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"viewing-the-results\"\u003eViewing the Results\u003c/h3\u003e\n\n\u003cp\u003eWhen the computation is complete, you have to create a 3D View on the \u003cstrong\u003eStatistics Case\u003c/strong\u003e to view the results. Use the right-click menu of the \u003cstrong\u003eStatistics Case\u003c/strong\u003e to create it.\u003c/p\u003e\n\n\u003ch3 id=\"adding-statistics-cases\"\u003eAdding Statistics Cases\u003c/h3\u003e\n\n\u003cp\u003eA new statistical calculation can be created by activating the right-click menu for \u003cstrong\u003eDerived Statistic-\u0026gt;New Statistics Case\u003c/strong\u003e.\u003c/p\u003e\n",
+                content:  "Grid Case Group\u0026lsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled realizations).\nIf you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.\nCreating Grid Case Groups From Files The easiest way to create a Grid Case Group is to use the Import command: File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files or File-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files Recursively\nThe latter command will display the recursive file import dialog described on the Summary Plots page.\nThe first command will display the \u0026ldquo;old\u0026rdquo; import dialog:  Add one or more search folders to the list on the left. The EGRID or GRID files found in these directories and sub directories are shown in the list to the right. If you want to remove some EGRID files from the list, select them and press the Remove button. When you are ready, press the OK button.  ResInsight then creates a Grid Case Group for you, and populates its Source Cases with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.\nManually A Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. Source Cases can then be added by using the mouse to drag and drop cases with equal grids into the Grid Case Group\u0026lsquo;s Source Case folder. This is useful if you want to create statistics based only on a subset of the source cases in an already created Grid Case Group.\nDrag and Drop of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the Shift key while dropping.\nViewing Special Source Cases To reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, select New view from the right-click menu. A new 3D View will the be created on that particular case.\n\rStatistics After creating a grid case group, an empty Statistics Case is created for you in the Derived Statistics folder of the Grid Case Group.\nSetting Up and Calculate The properties of non-calculated and calculated Statistics Case is shown below:\n Compute \u0026ndash; Starts to calculate requested statistical Properties. Edit \u0026ndash; Deletes the calculated results, and makes the controls to edit the setup available. Summary of calculation setup \u0026ndash; Summarizes what to calculate. Properties to consider \u0026ndash; These options makes it possible to select what Eclipse properties to include in the Statistical calculations. Adding variables increase the memory usage and the computational time. Percentile Setup \u0026ndash; Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations. Well Data Source Case \u0026ndash; This option selects which set of Simulation Wells to be shown along with the statistical results. You can select one of the Source Cases.  Percentile Methods Three Percentile methods are implemented:\n Interpolated Observation \u0026ndash; The values are sorted, and the two observations representing the probabilities closest to the percentile are interpolated to find the value for the percentile. This is the default method. Nearest Observation \u0026ndash; The values are sorted, and the first observation representing a probability higher or equal to the percentile probability is selected as the value for the percentile. This method is by some considered to be statistically more puristic. Histogram based estimate \u0026ndash; A histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.  Viewing the Results When the computation is complete, you have to create a 3D View on the Statistics Case to view the results. Use the right-click menu of the Statistics Case to create it.\nAdding Statistics Cases A new statistical calculation can be created by activating the right-click menu for Derived Statistic-\u0026gt;New Statistics Case.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridCaseGroupTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eGrid Case Group\u003c/strong\u003e\u0026lsquo;s are designed to make it easy to calculate statistics per cell and per time step of a large number of Eclipse simulation Cases with identical Grids (often labeled \u003cem\u003erealizations\u003c/em\u003e).\u003c/p\u003e\n\u003cp\u003eIf you have several Eclipse simulations with different input parameters available, you can put all the realizations into a Grid Case Group and easily calculate each of the cells mean value, range and max/min values at each time step between the realizations.\u003c/p\u003e\n\u003ch2 id=\"creating-grid-case-groups\"\u003eCreating Grid Case Groups\u003c/h2\u003e\n\u003ch3 id=\"from-files\"\u003eFrom Files\u003c/h3\u003e\n\u003cp\u003eThe easiest way to create a \u003cstrong\u003eGrid Case Group\u003c/strong\u003e is to use the Import command:\n\u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files\u003c/strong\u003e or \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Eclipse Cases-\u0026gt;Create Grid Case Group from Files Recursively\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThe latter command will display the recursive file import dialog described on the \u003ca href=\"/plot-window/summaryplots/#recursive-summary-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eThe first command will display the \u0026ldquo;old\u0026rdquo; import dialog:\n\u003cimg src=\"/images/3d-main-window/CreateGridCaseGroupFromFileDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eAdd one or more search folders to the list on the left.\u003c/li\u003e\n\u003cli\u003eThe EGRID or GRID files found in these directories and sub directories are shown in the list to the right.\u003c/li\u003e\n\u003cli\u003eIf you want to remove some EGRID files from the list, select them and press the \u003cstrong\u003eRemove\u003c/strong\u003e button.\u003c/li\u003e\n\u003cli\u003eWhen you are ready, press the \u003cstrong\u003eOK\u003c/strong\u003e button.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eResInsight then creates a \u003cstrong\u003eGrid Case Group\u003c/strong\u003e for you, and populates its \u003cstrong\u003eSource Cases\u003c/strong\u003e with the Cases you selected. Then the first of those Cases are read completely, while the others are just scanned to verify that the Grids match and to detect changes in the Active Cells layout. This makes it quite fast to load even a quite large number of realizations.\u003c/p\u003e\n\u003ch3 id=\"manually\"\u003eManually\u003c/h3\u003e\n\u003cp\u003eA Grid Case Group can be created from the right-click menu of a Result Case, Input Case or a different Grid Case Group. \u003cstrong\u003eSource Cases\u003c/strong\u003e can then be added by using the mouse to \u003cem\u003edrag and drop\u003c/em\u003e cases with equal grids into the \u003cstrong\u003eGrid Case Group\u003c/strong\u003e\u0026lsquo;s \u003cstrong\u003eSource Case\u003c/strong\u003e folder.\nThis is useful if you want to create statistics based only on a subset of the source cases in an already created \u003cstrong\u003eGrid Case Group\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eDrag and Drop\u003c/strong\u003e of cases will normally copy the cases to the new destination, but moving them is possible by pressing and holding the \u003cstrong\u003eShift\u003c/strong\u003e key while dropping.\u003c/p\u003e\n\u003ch2 id=\"viewing-special-source-cases\"\u003eViewing Special Source Cases\u003c/h2\u003e\n\u003cp\u003eTo reduce the number of views, only a view for the first case is created automatically. If you want to inspect the results of a particular source case, select \u003cstrong\u003eNew view\u003c/strong\u003e from the right-click menu. A new 3D View will the be created on that particular case.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003c!-- raw HTML omitted --\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"statistics\"\u003eStatistics\u003c/h2\u003e\n\u003cp\u003eAfter creating a grid case group, an empty \u003cstrong\u003eStatistics Case\u003c/strong\u003e is created for you in the \u003cstrong\u003eDerived Statistics\u003c/strong\u003e folder of the \u003cstrong\u003eGrid Case Group\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"setting-up-and-calculate\"\u003eSetting Up and Calculate\u003c/h3\u003e\n\u003cp\u003eThe properties of non-calculated and calculated \u003cstrong\u003eStatistics Case\u003c/strong\u003e is shown below:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StatisticsCaseProperties.png\" alt=\"\"\u003e  \u003cimg src=\"/images/3d-main-window/StatisticsCasePropertiesCalculated.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCompute\u003c/strong\u003e \u0026ndash;  Starts to calculate requested statistical Properties.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEdit\u003c/strong\u003e \u0026ndash; Deletes the calculated results, and makes the controls to edit the setup available.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSummary of calculation setup\u003c/strong\u003e \u0026ndash; Summarizes what to calculate.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperties to consider\u003c/strong\u003e \u0026ndash; These options makes it possible to select what Eclipse properties to include in the Statistical calculations. Adding variables increase the memory usage and the computational time.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePercentile Setup\u003c/strong\u003e \u0026ndash; Selects whether to calculate percentiles, what method and what percentile levels should be used. Turning this off speeds up the calculations.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Data Source Case\u003c/strong\u003e \u0026ndash; This option selects which set of \u003cstrong\u003eSimulation Wells\u003c/strong\u003e to be shown along with the statistical results. You can select one of the \u003cstrong\u003eSource Cases\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"percentile-methods\"\u003ePercentile Methods\u003c/h4\u003e\n\u003cp\u003eThree Percentile methods are implemented:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInterpolated Observation\u003c/strong\u003e \u0026ndash;\nThe values are sorted, and the two observations representing the probabilities closest to the percentile are interpolated to find the value for the percentile. This is the default method.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNearest Observation\u003c/strong\u003e \u0026ndash;\nThe values are sorted, and the first observation representing a probability higher or equal to the percentile probability is selected as the value for the percentile. This method is by some considered to be statistically more puristic.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHistogram based estimate\u003c/strong\u003e \u0026ndash;\nA histogram is created and the percentile is calculated based on the histogram. This method will be faster when having a large number of realizations, because no value sorting is involved. You would however need several hundred realizations before this method should be considered.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"viewing-the-results\"\u003eViewing the Results\u003c/h3\u003e\n\u003cp\u003eWhen the computation is complete, you have to create a 3D View on the \u003cstrong\u003eStatistics Case\u003c/strong\u003e to view the results. Use the right-click menu of the \u003cstrong\u003eStatistics Case\u003c/strong\u003e to create it.\u003c/p\u003e\n\u003ch3 id=\"adding-statistics-cases\"\u003eAdding Statistics Cases\u003c/h3\u003e\n\u003cp\u003eA new statistical calculation can be created by activating the right-click menu for \u003cstrong\u003eDerived Statistic-\u0026gt;New Statistics Case\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/3d-main-window/casegroupsandstatistics/"
             };
         
@@ -2505,8 +2547,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/gridcrossplots/"] = {
                 title:    "Grid Cross Plots",
-                content:  " ResInsight supports the creation of scatter / cross plots of two Eclipse results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations. giving a separate color and label for each group. The above example shows a classic Porosity vs Permeability plot, grouped by formations, showing different trends for each formation.\nFor continuous grouping parameters, the parameter will be divided into a set of equally sized intervals depending on the number of Color Legend intervals.\nEach cross plot can contain any number of Data Sets, representing a collection of cross plot points, where the Data Set can have a case source, time step and cell filter associated with it. This way, dynamic parameters for different time steps can be compared, or results from different case realizations.\nThe Grid Cross plots may have a Symbol Legend below the plot, separating the Data Sets, and a Color Legend within the plot separating between the different Grouping categories or intervals. In addition, an Info Box will be added to the upper right corner of the plot, showing the different data sets in the plot and the parameters used. The Color Legends and Info Box can be moved to other parts of the plot and will snap to edges and corners when moved close to them.\nCreating Grid Cross Plots Grid Cross Plots can be created in a couple of ways:\n Select a 3D view or Cell Result in the main ResInsight window, right-click and select Create Grid Cross Plot from 3d View. The resulting cross plot will display the current 3d Result x DEPTH and only contain data points for the visible cells. Right-click on the Grid Cross Plots entry under Plots in the Plot Window. By default the plot will contain the result values PORO x PERMX and will be grouped by formations (if any are loaded in the project). Data for all active cells will be displayed.  Having created a Grid Cross Plot, the appearance of the Legends, the Info box and the Plot Title can be set in the Property Editor of the Grid Cross Plot.\nThe plot also have some available settings for the two plot axes (X and Y), where the title position and font size can be altered plus the axis range may be controlled and the axis may be set as logarithmic and inverted so the smallest value is first (default for DEPTH on the Y-axis).\nGrid Cross Plot Data Sets Further Grid Cross Plot data sets can be added to a Plot by right clicking on the plot in the Project Tree and selecting New Data Set.\nThe Data Sets contain all the parameters controlling the data source and types of data being plotted.\nThe available parameters are:\n   Parameter Description     Case The Eclipse Case containing the data   Time Step Show data for All Time Steps or just a specific time step   Filter by 3d View Visibility Pick a view to use only the cells visible in that view. Allows the use of range and property filters   Group Data by Group and color data points by Time Step, Result Property or Formations   Data Grouping Property Available if grouping by Result Property and lets you pick any Eclipse result property and the number of intervals to divide the data into   X-Axis Property The property representing the X-axis in the cross plot   Y-Axis Property The property representing the Y-axis in the cross plot   Name Configuration Add Case Name, Axis Variables, Time Step and/or Data Group to the name of the Data set    Show Plot Data The data used to create the Cross Plot can be exported by either right-clicking on the Cross Plot in the project tree or right clicking on the plot itself and selecting Show Plot Data.\nEither method will bring up a dialog containing column-based text showing the X and Y result values, the Group index and Group Description (the latter two if Grouping is enabled). One tab in the dialog will be added for each Data Set. The data can be copied to the clipboard or exported to file by right-clicking on the text area.\nSwap Axes The X- and Y-axes can be swapped, both for invididual data sets, by choosing Swap Axis Properties from the right-click menu of the Grid Cross Plot Data Set, or for all data sets by right clicking on either the Cross Plot in the Project Tree or on the plot itself and selecting Swap Axis Properties for all Data Sets in Plot. The X- and Y-axis will swap place retaining the properties, such as Logarithmic or inverted axes.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports the creation of scatter / cross plots of two Eclipse results against each  other, with each cell in the grid\nrepresenting one data point in the plot. The data points can be grouped by a third result, by time step or by \u003cstrong\u003eFormations\u003c/strong\u003e.\ngiving a separate color and label for each group. The above example shows a classic Porosity vs Permeability plot, grouped by\nformations, showing different trends for each formation.\u003c/p\u003e\n\n\u003cp\u003eFor continuous grouping parameters, the parameter will be divided into a set of equally sized intervals depending on the number of Color Legend intervals.\u003c/p\u003e\n\n\u003cp\u003eEach cross plot can contain any number of \u003cstrong\u003eData Sets\u003c/strong\u003e, representing a collection of cross plot points, where the \u003cstrong\u003eData Set\u003c/strong\u003e can have a case source, time step and cell filter associated with it. This way, dynamic parameters for different time steps can be compared, or results from different case realizations.\u003c/p\u003e\n\n\u003cp\u003eThe Grid Cross plots may have a Symbol Legend below the plot, separating the Data Sets, and a Color Legend within the plot separating between the different Grouping categories or intervals. In addition, an Info Box will be added to the upper right corner of the plot, showing the different data sets in the plot and the parameters used. The Color Legends and Info Box can be moved to other parts of the plot and will snap to edges and corners when moved close to them.\u003c/p\u003e\n\n\u003ch2 id=\"creating-grid-cross-plots\"\u003eCreating Grid Cross Plots\u003c/h2\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_CreateFromView.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlot_Create.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eGrid Cross Plots can be created in a couple of ways:\u003c/p\u003e\n\n\u003col\u003e\n\u003cli\u003eSelect a 3D view or Cell Result in the main ResInsight window, right-click and select \u003cstrong\u003eCreate Grid Cross Plot from 3d View\u003c/strong\u003e. The resulting cross plot will display the current 3d Result x DEPTH and only contain data points for the visible cells.\u003c/li\u003e\n\u003cli\u003eRight-click on the \u003cstrong\u003eGrid Cross Plots\u003c/strong\u003e entry under \u003cstrong\u003ePlots\u003c/strong\u003e in the \u003cstrong\u003ePlot Window\u003c/strong\u003e. By default the plot will contain the result values PORO x PERMX and will be grouped by formations (if any are loaded in the project). Data for all active cells will be displayed.\u003c/li\u003e\n\u003c/ol\u003e\n\n\u003cp\u003eHaving created a Grid Cross Plot, the appearance of the Legends, the Info box and the Plot Title can be set in the Property Editor of the Grid Cross Plot.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_PropertyEditor.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlotAxis_PropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe plot also have some available settings for the two plot axes (X and Y), where the title position and font size can be altered plus the axis range may be controlled and the axis may be set as logarithmic and inverted so the smallest value is first (default for DEPTH on the Y-axis).\u003c/p\u003e\n\n\u003ch2 id=\"grid-cross-plot-data-sets\"\u003eGrid Cross Plot Data Sets\u003c/h2\u003e\n\n\u003cp\u003eFurther Grid Cross Plot data sets can be added to a Plot by right clicking on the plot in the Project Tree and selecting \u003cstrong\u003eNew Data Set\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlotDataSet_Create.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe Data Sets contain all the parameters controlling the data source and types of data being plotted.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlotDataSet_PropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe available parameters are:\u003c/p\u003e\n\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eCase\u003c/td\u003e\n\u003ctd\u003eThe Eclipse Case containing the data\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eTime Step\u003c/td\u003e\n\u003ctd\u003eShow data for All Time Steps or just a specific time step\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eFilter by 3d View Visibility\u003c/td\u003e\n\u003ctd\u003ePick a view to use only the cells visible in that view. Allows the use of range and property filters\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eGroup Data by\u003c/td\u003e\n\u003ctd\u003eGroup and color data points by \u003cstrong\u003eTime Step\u003c/strong\u003e, \u003cstrong\u003eResult Property\u003c/strong\u003e or \u003cstrong\u003eFormations\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eData Grouping Property\u003c/td\u003e\n\u003ctd\u003eAvailable if grouping by \u003cstrong\u003eResult Property\u003c/strong\u003e and lets you pick any Eclipse result property and the number of intervals to divide the data into\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eX-Axis Property\u003c/td\u003e\n\u003ctd\u003eThe property representing the X-axis in the cross plot\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eY-Axis Property\u003c/td\u003e\n\u003ctd\u003eThe property representing the Y-axis in the cross plot\u003c/td\u003e\n\u003c/tr\u003e\n\n\u003ctr\u003e\n\u003ctd\u003eName Configuration\u003c/td\u003e\n\u003ctd\u003eAdd Case Name, Axis Variables, Time Step and/or Data Group to the name of the Data set\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n\u003ch2 id=\"show-plot-data\"\u003eShow Plot Data\u003c/h2\u003e\n\n\u003cp\u003eThe data used to create the Cross Plot can be exported by either right-clicking on the Cross Plot in the project tree or right clicking on the plot itself and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData_ProjectTree.png\" alt=\"\" /\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData_PlotContext.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEither method will bring up a dialog containing column-based text showing the X and Y result values, the Group index and Group Description (the latter two if Grouping is enabled). One tab in the dialog will be added for each Data Set. The data can be copied to the clipboard or exported to file by right-clicking on the text area.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"swap-axes\"\u003eSwap Axes\u003c/h2\u003e\n\n\u003cp\u003eThe X- and Y-axes can be swapped, both for invididual data sets, by choosing \u003cstrong\u003eSwap Axis Properties\u003c/strong\u003e from the right-click menu of the Grid Cross Plot \u003cstrong\u003eData Set\u003c/strong\u003e, or for all data sets by right clicking on either the Cross Plot in the Project Tree or on the plot itself and selecting \u003cstrong\u003eSwap Axis Properties for all Data Sets in Plot\u003c/strong\u003e. The X- and Y-axis will swap place retaining the properties, such as Logarithmic or inverted axes.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_SwapAxes.png\" alt=\"\" /\u003e\u003c/p\u003e\n",
+                content:  "ResInsight supports the creation of scatter / cross plots of two Eclipse results against each other, with each cell in the grid representing one data point in the plot. The data points can be grouped by a third result, by time step or by Formations. giving a separate color and label for each group. The above example shows a classic Porosity vs Permeability plot, grouped by formations, showing different trends for each formation.\nFor continuous grouping parameters, the parameter will be divided into a set of equally sized intervals depending on the number of Color Legend intervals.\nEach cross plot can contain any number of Data Sets, representing a collection of cross plot points, where the Data Set can have a case source, time step and cell filter associated with it. This way, dynamic parameters for different time steps can be compared, or results from different case realizations.\nThe Grid Cross plots may have a Symbol Legend below the plot, separating the Data Sets, and a Color Legend within the plot separating between the different Grouping categories or intervals. In addition, an Info Box will be added to the upper right corner of the plot, showing the different data sets in the plot and the parameters used. The Color Legends and Info Box can be moved to other parts of the plot and will snap to edges and corners when moved close to them.\nCreating Grid Cross Plots Grid Cross Plots can be created in a couple of ways:\n Select a 3D view or Cell Result in the main ResInsight window, right-click and select Create Grid Cross Plot from 3d View. The resulting cross plot will display the current 3d Result x DEPTH and only contain data points for the visible cells. Right-click on the Grid Cross Plots entry under Plots in the Plot Window. By default the plot will contain the result values PORO x PERMX and will be grouped by formations (if any are loaded in the project). Data for all active cells will be displayed.  Having created a Grid Cross Plot, the appearance of the Legends, the Info box and the Plot Title can be set in the Property Editor of the Grid Cross Plot.\nThe plot also have some available settings for the two plot axes (X and Y), where the title position and font size can be altered plus the axis range may be controlled and the axis may be set as logarithmic and inverted so the smallest value is first (default for DEPTH on the Y-axis).\nGrid Cross Plot Data Sets Further Grid Cross Plot data sets can be added to a Plot by right clicking on the plot in the Project Tree and selecting New Data Set.\nThe Data Sets contain all the parameters controlling the data source and types of data being plotted.\nThe available parameters are:\n   Parameter Description     Case The Eclipse Case containing the data   Time Step Show data for All Time Steps or just a specific time step   Filter by 3d View Visibility Pick a view to use only the cells visible in that view. Allows the use of range and property filters   Group Data by Group and color data points by Time Step, Result Property or Formations   Data Grouping Property Available if grouping by Result Property and lets you pick any Eclipse result property and the number of intervals to divide the data into   X-Axis Property The property representing the X-axis in the cross plot   Y-Axis Property The property representing the Y-axis in the cross plot   Name Configuration Add Case Name, Axis Variables, Time Step and/or Data Group to the name of the Data set    Show Plot Data The data used to create the Cross Plot can be exported by either right-clicking on the Cross Plot in the project tree or right clicking on the plot itself and selecting Show Plot Data.\nEither method will bring up a dialog containing column-based text showing the X and Y result values, the Group index and Group Description (the latter two if Grouping is enabled). One tab in the dialog will be added for each Data Set. The data can be copied to the clipboard or exported to file by right-clicking on the text area.\nSwap Axes The X- and Y-axes can be swapped, both for invididual data sets, by choosing Swap Axis Properties from the right-click menu of the Grid Cross Plot Data Set, or for all data sets by right clicking on either the Cross Plot in the Project Tree or on the plot itself and selecting Swap Axis Properties for all Data Sets in Plot. The X- and Y-axis will swap place retaining the properties, such as Logarithmic or inverted axes.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports the creation of scatter / cross plots of two Eclipse results against each  other, with each cell in the grid\nrepresenting one data point in the plot. The data points can be grouped by a third result, by time step or by \u003cstrong\u003eFormations\u003c/strong\u003e.\ngiving a separate color and label for each group. The above example shows a classic Porosity vs Permeability plot, grouped by\nformations, showing different trends for each formation.\u003c/p\u003e\n\u003cp\u003eFor continuous grouping parameters, the parameter will be divided into a set of equally sized intervals depending on the number of Color Legend intervals.\u003c/p\u003e\n\u003cp\u003eEach cross plot can contain any number of \u003cstrong\u003eData Sets\u003c/strong\u003e, representing a collection of cross plot points, where the \u003cstrong\u003eData Set\u003c/strong\u003e can have a case source, time step and cell filter associated with it. This way, dynamic parameters for different time steps can be compared, or results from different case realizations.\u003c/p\u003e\n\u003cp\u003eThe Grid Cross plots may have a Symbol Legend below the plot, separating the Data Sets, and a Color Legend within the plot separating between the different Grouping categories or intervals. In addition, an Info Box will be added to the upper right corner of the plot, showing the different data sets in the plot and the parameters used. The Color Legends and Info Box can be moved to other parts of the plot and will snap to edges and corners when moved close to them.\u003c/p\u003e\n\u003ch2 id=\"creating-grid-cross-plots\"\u003eCreating Grid Cross Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_CreateFromView.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlot_Create.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eGrid Cross Plots can be created in a couple of ways:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eSelect a 3D view or Cell Result in the main ResInsight window, right-click and select \u003cstrong\u003eCreate Grid Cross Plot from 3d View\u003c/strong\u003e. The resulting cross plot will display the current 3d Result x DEPTH and only contain data points for the visible cells.\u003c/li\u003e\n\u003cli\u003eRight-click on the \u003cstrong\u003eGrid Cross Plots\u003c/strong\u003e entry under \u003cstrong\u003ePlots\u003c/strong\u003e in the \u003cstrong\u003ePlot Window\u003c/strong\u003e. By default the plot will contain the result values PORO x PERMX and will be grouped by formations (if any are loaded in the project). Data for all active cells will be displayed.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eHaving created a Grid Cross Plot, the appearance of the Legends, the Info box and the Plot Title can be set in the Property Editor of the Grid Cross Plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_PropertyEditor.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlotAxis_PropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe plot also have some available settings for the two plot axes (X and Y), where the title position and font size can be altered plus the axis range may be controlled and the axis may be set as logarithmic and inverted so the smallest value is first (default for DEPTH on the Y-axis).\u003c/p\u003e\n\u003ch2 id=\"grid-cross-plot-data-sets\"\u003eGrid Cross Plot Data Sets\u003c/h2\u003e\n\u003cp\u003eFurther Grid Cross Plot data sets can be added to a Plot by right clicking on the plot in the Project Tree and selecting \u003cstrong\u003eNew Data Set\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlotDataSet_Create.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Data Sets contain all the parameters controlling the data source and types of data being plotted.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlotDataSet_PropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe available parameters are:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eParameter\u003c/th\u003e\n\u003cth\u003eDescription\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eCase\u003c/td\u003e\n\u003ctd\u003eThe Eclipse Case containing the data\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eTime Step\u003c/td\u003e\n\u003ctd\u003eShow data for All Time Steps or just a specific time step\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFilter by 3d View Visibility\u003c/td\u003e\n\u003ctd\u003ePick a view to use only the cells visible in that view. Allows the use of range and property filters\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eGroup Data by\u003c/td\u003e\n\u003ctd\u003eGroup and color data points by \u003cstrong\u003eTime Step\u003c/strong\u003e, \u003cstrong\u003eResult Property\u003c/strong\u003e or \u003cstrong\u003eFormations\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eData Grouping Property\u003c/td\u003e\n\u003ctd\u003eAvailable if grouping by \u003cstrong\u003eResult Property\u003c/strong\u003e and lets you pick any Eclipse result property and the number of intervals to divide the data into\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eX-Axis Property\u003c/td\u003e\n\u003ctd\u003eThe property representing the X-axis in the cross plot\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eY-Axis Property\u003c/td\u003e\n\u003ctd\u003eThe property representing the Y-axis in the cross plot\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eName Configuration\u003c/td\u003e\n\u003ctd\u003eAdd Case Name, Axis Variables, Time Step and/or Data Group to the name of the Data set\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch2 id=\"show-plot-data\"\u003eShow Plot Data\u003c/h2\u003e\n\u003cp\u003eThe data used to create the Cross Plot can be exported by either right-clicking on the Cross Plot in the project tree or right clicking on the plot itself and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData_ProjectTree.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData_PlotContext.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEither method will bring up a dialog containing column-based text showing the X and Y result values, the Group index and Group Description (the latter two if Grouping is enabled). One tab in the dialog will be added for each Data Set. The data can be copied to the clipboard or exported to file by right-clicking on the text area.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_ShowData.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"swap-axes\"\u003eSwap Axes\u003c/h2\u003e\n\u003cp\u003eThe X- and Y-axes can be swapped, both for invididual data sets, by choosing \u003cstrong\u003eSwap Axis Properties\u003c/strong\u003e from the right-click menu of the Grid Cross Plot \u003cstrong\u003eData Set\u003c/strong\u003e, or for all data sets by right clicking on either the Cross Plot in the Project Tree or on the plot itself and selecting \u003cstrong\u003eSwap Axis Properties for all Data Sets in Plot\u003c/strong\u003e. The X- and Y-axis will swap place retaining the properties, such as Logarithmic or inverted axes.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridCrossPlot_SwapAxes.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/gridcrossplots/"
             };
         
@@ -2514,8 +2556,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/linkedviews/"] = {
                 title:    "Linked Views",
-                content:  " One or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.\nEstablish Linked Views To establish a link between views, select Link Visible Views from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the Linked Views items are displayed in the top of the Project Tree.\nIt is also possible to link specific views by selecting them and choosing Link Selected Views from the right-click menu. The following image shows the linking of a regular view with a Contour Map. Note that contour maps can never be the Master View.\nLinked View Options When selecting a linked view in the project tree, the different options are available in the Property Editor.\nLink Options  Camera \u0026ndash; Navigation in any of the views where this option is active will be applied to the other linked views with this option set. This option is not available for Contour Maps. Show Cursor \u0026ndash; Shows the position of the mouse cursor in the other views as a cross-hair. This option is not available for Contour Maps. Time Step \u0026ndash; Change of time step in any of the views where this option is active will be applied to the other linked views with this option set. Cell Color Result \u0026ndash; Change of cell result in the master view will be applied to all dependent views where this option is active. Cell Color Result is only supported between views of the same type. Legend Definition \u0026ndash; Links the legend between views already linking the Cell Results Color.  Link Cell Filters  Range Filters \u0026ndash; Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case. Property Filters \u0026ndash; Property filters in master view will be applied to all dependent views where this option is active. This option is only enabled between views of the same case.  Toggle Linking from the Project Tree A linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item Linked Views.\nProject Tree right-click menu Right-clicking one of the linked view entries in the Project Tree displays the following menu entries:\n Open All Linked Views \u0026ndash; Open all the views which is part of the linked view group. Delete All Linked Views \u0026ndash; Delete the linked views group, and thereby unlink all the views. Delete \u0026ndash; Remove an individual view from the group of linked views.  3D View right-click menu To activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model. Depending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:\n Show Link Options \u0026ndash; Activate the linked view item in the project tree, and show its properties. Set As Master View \u0026ndash; Use the view as Master View. This option is not available for Contour Maps. Link View \u0026ndash; Add the view to list of linked views. Unlink View \u0026ndash; Delete the view from list of linked views.  Master views have no available linking commands.\n",
-                html:     "\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsOverview.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eOne or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.\u003c/p\u003e\n\n\u003ch2 id=\"establish-linked-views\"\u003eEstablish Linked Views\u003c/h2\u003e\n\n\u003cp\u003eTo establish a link between views, select \u003cimg src=\"https://resinsight.org/images/3d-main-window/chain.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eLink Visible Views\u003c/strong\u003e from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the \u003cstrong\u003eLinked Views\u003c/strong\u003e items are displayed in the top of the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsInProjectTree.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eIt is also possible to link specific views by selecting them and choosing \u003cstrong\u003eLink Selected Views\u003c/strong\u003e from the right-click menu. The following image shows the linking of a regular view with a \u003cstrong\u003eContour Map\u003c/strong\u003e. Note that contour maps can never be the Master View.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedContourMap.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"linked-view-options\"\u003eLinked View Options\u003c/h2\u003e\n\n\u003cp\u003eWhen selecting a linked view in the project tree, the different options are available in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsProperties.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch4 id=\"link-options\"\u003eLink Options\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCamera\u003c/strong\u003e \u0026ndash; Navigation in any of the views where this option is active will be applied to the other linked views with this option set. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Cursor\u003c/strong\u003e \u0026ndash; Shows the position of the mouse cursor in the other views as a cross-hair. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; Change of time step in any of the views where this option is active will be applied to the other linked views with this option set.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Color Result\u003c/strong\u003e \u0026ndash; Change of cell result in the master view will be applied to all dependent views where this option is active. \u003cstrong\u003eCell Color Result\u003c/strong\u003e is only supported between views of the \u003cem\u003esame type\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Definition\u003c/strong\u003e \u0026ndash; Links the legend between views already linking the \u003cstrong\u003eCell Results Color\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"link-cell-filters\"\u003eLink Cell Filters\u003c/h4\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filters\u003c/strong\u003e \u0026ndash; Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e \u0026ndash; Property filters in master view will be applied to all dependent views where this option is active. This option is only enabled between views of the \u003cem\u003esame case\u003c/em\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"toggle-linking-from-the-project-tree\"\u003eToggle Linking from the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/h2\u003e\n\n\u003cp\u003eA linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item \u003cstrong\u003eLinked Views\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch2 id=\"project-tree-right-click-menu\"\u003eProject Tree right-click menu\u003c/h2\u003e\n\n\u003cp\u003eRight-clicking one of the linked view entries in the \u003cstrong\u003eProject Tree\u003c/strong\u003e displays the following menu entries:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOpen All Linked Views\u003c/strong\u003e \u0026ndash; Open all the views which is part of the linked view group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDelete All Linked Views\u003c/strong\u003e \u0026ndash; Delete the linked views group, and thereby unlink all the views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDelete\u003c/strong\u003e \u0026ndash; Remove an individual view from the group of linked views.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"3d-view-right-click-menu\"\u003e3D View right-click menu\u003c/h2\u003e\n\n\u003cp\u003eTo activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model.\nDepending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Link Options\u003c/strong\u003e \u0026ndash; Activate the linked view item in the project tree, and show its properties.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSet As Master View\u003c/strong\u003e \u0026ndash; Use the view as Master View. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLink View\u003c/strong\u003e \u0026ndash; Add the view to list of linked views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnlink View\u003c/strong\u003e \u0026ndash; Delete the view from list of linked views.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eMaster views have no available linking commands.\u003c/p\u003e\n",
+                content:  "One or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.\nEstablish Linked Views To establish a link between views, select Link Visible Views from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the Linked Views items are displayed in the top of the Project Tree.\nIt is also possible to link specific views by selecting them and choosing Link Selected Views from the right-click menu. The following image shows the linking of a regular view with a Contour Map. Note that contour maps can never be the Master View.\nLinked View Options When selecting a linked view in the project tree, the different options are available in the Property Editor.\nLink Options  Camera \u0026ndash; Navigation in any of the views where this option is active will be applied to the other linked views with this option set. This option is not available for Contour Maps. Show Cursor \u0026ndash; Shows the position of the mouse cursor in the other views as a cross-hair. This option is not available for Contour Maps. Time Step \u0026ndash; Change of time step in any of the views where this option is active will be applied to the other linked views with this option set. Cell Color Result \u0026ndash; Change of cell result in the master view will be applied to all dependent views where this option is active. Cell Color Result is only supported between views of the same type. Legend Definition \u0026ndash; Links the legend between views already linking the Cell Results Color.  Link Cell Filters  Range Filters \u0026ndash; Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case. Property Filters \u0026ndash; Property filters in master view will be applied to all dependent views where this option is active. This option is only enabled between views of the same case.  Toggle Linking from the Project Tree A linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item Linked Views.\nProject Tree right-click menu Right-clicking one of the linked view entries in the Project Tree displays the following menu entries:\n Open All Linked Views \u0026ndash; Open all the views which is part of the linked view group. Delete All Linked Views \u0026ndash; Delete the linked views group, and thereby unlink all the views. Delete \u0026ndash; Remove an individual view from the group of linked views.  3D View right-click menu To activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model. Depending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:\n Show Link Options \u0026ndash; Activate the linked view item in the project tree, and show its properties. Set As Master View \u0026ndash; Use the view as Master View. This option is not available for Contour Maps. Link View \u0026ndash; Add the view to list of linked views. Unlink View \u0026ndash; Delete the view from list of linked views.  Master views have no available linking commands.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eOne or more views can be linked together to allow some settings like camera position and range filters, propagate from one view to another.\u003c/p\u003e\n\u003ch2 id=\"establish-linked-views\"\u003eEstablish Linked Views\u003c/h2\u003e\n\u003cp\u003eTo establish a link between views, select \u003cimg src=\"https://resinsight.org/images/3d-main-window/chain.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eLink Visible Views\u003c/strong\u003e from the View toolbar. This will open a dialog where the Master View is selected. When pressing Ok in this dialog, the \u003cstrong\u003eLinked Views\u003c/strong\u003e items are displayed in the top of the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsInProjectTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIt is also possible to link specific views by selecting them and choosing \u003cstrong\u003eLink Selected Views\u003c/strong\u003e from the right-click menu. The following image shows the linking of a regular view with a \u003cstrong\u003eContour Map\u003c/strong\u003e. Note that contour maps can never be the Master View.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedContourMap.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"linked-view-options\"\u003eLinked View Options\u003c/h2\u003e\n\u003cp\u003eWhen selecting a linked view in the project tree, the different options are available in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LinkedViewsProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch4 id=\"link-options\"\u003eLink Options\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCamera\u003c/strong\u003e \u0026ndash; Navigation in any of the views where this option is active will be applied to the other linked views with this option set. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Cursor\u003c/strong\u003e \u0026ndash; Shows the position of the mouse cursor in the other views as a cross-hair. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e \u0026ndash; Change of time step in any of the views where this option is active will be applied to the other linked views with this option set.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCell Color Result\u003c/strong\u003e \u0026ndash; Change of cell result in the master view will be applied to all dependent views where this option is active. \u003cstrong\u003eCell Color Result\u003c/strong\u003e is only supported between views of the \u003cem\u003esame type\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLegend Definition\u003c/strong\u003e \u0026ndash; Links the legend between views already linking the \u003cstrong\u003eCell Results Color\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"link-cell-filters\"\u003eLink Cell Filters\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRange Filters\u003c/strong\u003e \u0026ndash; Range filters in master view will be applied to all dependent views where this option is active. Normally this is done by a direct copy, but if the master and dependent view is of different types (Eclipse and Geomechanical views) and the Eclipse case is within the bounds of the Geomechanical case, ResInsight tries to map the range filters to the corresponding cells in the other case.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Filters\u003c/strong\u003e \u0026ndash; Property filters in master view will be applied to all dependent views where this option is active. This option is only enabled between views of the \u003cem\u003esame case\u003c/em\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"toggle-linking-from-the-project-tree\"\u003eToggle Linking from the \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/h2\u003e\n\u003cp\u003eA linked view can temporarily be disabled by unchecking the linked view. To disable all linked views temporarily, uncheck the top level item \u003cstrong\u003eLinked Views\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"project-tree-right-click-menu\"\u003eProject Tree right-click menu\u003c/h2\u003e\n\u003cp\u003eRight-clicking one of the linked view entries in the \u003cstrong\u003eProject Tree\u003c/strong\u003e displays the following menu entries:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOpen All Linked Views\u003c/strong\u003e \u0026ndash; Open all the views which is part of the linked view group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDelete All Linked Views\u003c/strong\u003e \u0026ndash; Delete the linked views group, and thereby unlink all the views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDelete\u003c/strong\u003e \u0026ndash; Remove an individual view from the group of linked views.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"3d-view-right-click-menu\"\u003e3D View right-click menu\u003c/h2\u003e\n\u003cp\u003eTo activate the menu items for a linked view, right-click inside the 3D view anywhere outside the model. \nDepending on whether the view is a dependent-, or an unlinked view, some of the following commands are available:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eShow Link Options\u003c/strong\u003e \u0026ndash; Activate the linked view item in the project tree, and show its properties.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSet As Master View\u003c/strong\u003e \u0026ndash; Use the view as Master View. This option is not available for Contour Maps.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLink View\u003c/strong\u003e \u0026ndash; Add the view to list of linked views.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUnlink View\u003c/strong\u003e \u0026ndash; Delete the view from list of linked views.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eMaster views have no available linking commands.\u003c/p\u003e\n",
                 url:      "/3d-main-window/linkedviews/"
             };
         
@@ -2524,7 +2566,7 @@ if (!doNotTrack) {
             window.store["/plot-window/saturationpressureplots/"] = {
                 title:    "Saturation Pressure Plots",
                 content:  "A Saturation Pressure Plot a plot displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots. One Saturation Pressure Plot is created for each equilibrium region.\nTo be able to create these plots, output of saturation pressures need to be specified in the SOLUTION section of the Eclipse \u0026ldquo;.DATA\u0026rdquo; file.\nTo create these plots, right click on the view in the Property Editor, and select Create Saturation Pressure Plots. It is also possible to create these plots by right click on the item Saturation Pressure Plots in the Property Editor in the Plot Window.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SaturationPressurePlot.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eA Saturation Pressure Plot a plot displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots. One Saturation Pressure Plot is created for each equilibrium region.\u003c/p\u003e\n\n\u003cp\u003eTo be able to create these plots, output of saturation pressures need to be specified in the \u003cstrong\u003eSOLUTION\u003c/strong\u003e section of the Eclipse \u0026ldquo;.DATA\u0026rdquo; file.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SaturationPressurePlotPropertyEditor.png\" alt=\"\" /\u003e\nTo create these plots, right click on the view in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, and select \u003cstrong\u003eCreate Saturation Pressure Plots\u003c/strong\u003e. It is also possible to create these plots by right click on the item \u003cstrong\u003eSaturation Pressure Plots\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e in the \u003cstrong\u003ePlot Window\u003c/strong\u003e.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SaturationPressurePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Saturation Pressure Plot a plot displaying bubble and dew point pressures, together with initial pressure in model, versus depth. Fluid contacts (GOC and/or OWC) are displayed as annotation lines in the generated plots. One Saturation Pressure Plot is created for each equilibrium region.\u003c/p\u003e\n\u003cp\u003eTo be able to create these plots, output of saturation pressures need to be specified in the \u003cstrong\u003eSOLUTION\u003c/strong\u003e section of the Eclipse \u0026ldquo;.DATA\u0026rdquo; file.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SaturationPressurePlotPropertyEditor.png\" alt=\"\"\u003e\nTo create these plots, right click on the view in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, and select \u003cstrong\u003eCreate Saturation Pressure Plots\u003c/strong\u003e. It is also possible to create these plots by right click on the item \u003cstrong\u003eSaturation Pressure Plots\u003c/strong\u003e in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e in the \u003cstrong\u003ePlot Window\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/saturationpressureplots/"
             };
         
@@ -2533,7 +2575,7 @@ if (!doNotTrack) {
             window.store["/3d-main-window/measurement/"] = {
                 title:    "Measurement",
                 content:  "ResInsight supports measurements in the 3D views. To enter measurement mode, press the ruler toolbar button or the keyboard shortcut Ctrl-M. This mode can also be activated from the right-click menu in a 3D view.\nWhen ResInsight is in measurement mode, clicking on an surface in the 3D view will set the first measurement point. Clicking on a different surface will set the second measurement point, and display a label with measurements. Additional clicking will start a new measurement between two points.\nThe measurement label contains the following:\n Length - The length of the measurement segment Horizontal Length - The length of the measurement segment projected onto the XY plane  ResInsight also supports measuring a polyline (a set of line segments), which can be activated with the polyline ruler toolbar button or Ctrl-Shift-M. The measurement label will now contain additional measurements.\nThe measurement label contains several lengths.\n Segment Length - The length of the last segment Segment Horizontal Length - The length of the last segment projected onto the XY plane Total Length - The total length of the measurement polyline Total Horizontal Length - The total length of the measurement polyline projected onto the XY plane Horizontal area - The area of the polyline projected onto the XY plane  To leave measurement modes, press the toolbar button, press the Esc button or press the keyboard shortcut used to activate the mode again.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Measurement.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eResInsight supports measurements in the 3D views. To enter measurement mode, press the ruler toolbar button \u003cimg src=\"https://resinsight.org/images/3d-main-window/MeasurementButton.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or the keyboard shortcut \u003cstrong\u003eCtrl-M\u003c/strong\u003e. This mode can also be activated from the right-click menu in a 3D view.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MeasurementToolbar.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eWhen ResInsight is in measurement mode, clicking on an surface in the 3D view will set the first measurement point. Clicking on a different surface will set the second measurement point, and display a label with measurements. Additional clicking will start a new measurement between two points.\u003c/p\u003e\n\n\u003cp\u003eThe measurement label contains the following:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLength\u003c/strong\u003e - The length of the measurement segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHorizontal Length\u003c/strong\u003e - The length of the measurement segment projected onto the XY plane\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eResInsight also supports measuring a polyline (a set of line segments), which can be activated with the polyline ruler toolbar button \u003cimg src=\"https://resinsight.org/images/3d-main-window/PolylineMeasurementButton.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cstrong\u003eCtrl-Shift-M\u003c/strong\u003e. The measurement label will now contain additional measurements.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PolylineMeasurement.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe measurement label contains several lengths.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSegment Length\u003c/strong\u003e - The length of the last segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment Horizontal Length\u003c/strong\u003e - The length of the last segment projected onto the XY plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal Length\u003c/strong\u003e - The total length of the measurement polyline\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal Horizontal Length\u003c/strong\u003e - The total length of the measurement polyline projected onto the XY plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHorizontal area\u003c/strong\u003e - The area of the polyline projected onto the XY plane\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eTo leave measurement modes, press the toolbar button, press the \u003cstrong\u003eEsc\u003c/strong\u003e button  or press the keyboard shortcut used to activate the mode again.\u003c/p\u003e\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Measurement.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports measurements in the 3D views. To enter measurement mode, press the ruler toolbar button \u003cimg src=\"https://resinsight.org/images/3d-main-window/MeasurementButton.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or the keyboard shortcut \u003cstrong\u003eCtrl-M\u003c/strong\u003e. This mode can also be activated from the right-click menu in a 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MeasurementToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen ResInsight is in measurement mode, clicking on an surface in the 3D view will set the first measurement point. Clicking on a different surface will set the second measurement point, and display a label with measurements. Additional clicking will start a new measurement between two points.\u003c/p\u003e\n\u003cp\u003eThe measurement label contains the following:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eLength\u003c/strong\u003e - The length of the measurement segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHorizontal Length\u003c/strong\u003e - The length of the measurement segment projected onto the XY plane\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eResInsight also supports measuring a polyline (a set of line segments), which can be activated with the polyline ruler toolbar button \u003cimg src=\"https://resinsight.org/images/3d-main-window/PolylineMeasurementButton.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cstrong\u003eCtrl-Shift-M\u003c/strong\u003e. The measurement label will now contain additional measurements.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PolylineMeasurement.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe measurement label contains several lengths.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSegment Length\u003c/strong\u003e - The length of the last segment\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment Horizontal Length\u003c/strong\u003e - The length of the last segment projected onto the XY plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal Length\u003c/strong\u003e - The total length of the measurement polyline\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTotal Horizontal Length\u003c/strong\u003e - The total length of the measurement polyline projected onto the XY plane\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHorizontal area\u003c/strong\u003e - The area of the polyline projected onto the XY plane\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eTo leave measurement modes, press the toolbar button, press the \u003cstrong\u003eEsc\u003c/strong\u003e button  or press the keyboard shortcut used to activate the mode again.\u003c/p\u003e\n",
                 url:      "/3d-main-window/measurement/"
             };
         
@@ -2541,8 +2583,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/annotations/"] = {
                 title:    "Annotations",
-                content:  " ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.\n Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file   Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.\nAll global annotations also have a representation in the local Annotation tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with Global.\n Local annotations sub tree\n Global annotations sub tree\nText Annotations There are two ways of creating a new text annotation.\n Right click Annotations or Text Annotations tree node in either the global annotatyion sub tree or the local annotations sub tree. The scope of the annotation depends on which node was clicked. When text annotations are created this way, all text annotation fields must be entered manunally in the property editor. Right click on an object in the view and select Create Text Annotation. ResInsight will then create a text annotation at the clicked point. In this case, only th text must be entered manually in the property editor. When creating a text annotation this way, it will become a local annotation by default.   Anchor Point - The interesting point in the view Label Point - The point where the text label is placed Text - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree Text appearance - Set font size, font color, background color and anchor line color  When a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.\nReach Circle Annotations To create a reach circle annotation, right click Annotations or Reach Circle Annotations tree node in the global annotations sub tree. Then enter values in the property editor.\n Name - Name of the circle annotation Center Point - Center point of the circle. Format \u0026lsquo;x-pos y-pos depth\u0026rsquo; Radius - Circle radius Line Appearance - Set circle color and line thickness  User Defined Polyline Annotations To create a user defined polyline annotation, right click Annotations or User Defined Polyline Annotations tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click Stop Picking Points in the property editor.\n Targets - Polyline points. Can be edited in the table or interactively in the view Start Picking Points / Stop Picking Points - Button to start / stop picking mode Line Appearance - Set line color and thickness  When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.\nPolyline Imported From File To import a polyline annotation from file, right click Annotations or Polylines From File tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.\n File - Name of the imported file Line Appearance - Set line color and line thickness  Annotations visibility Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.\n",
-                html:     "\n\n\u003cp\u003eResInsight supports displaying a few types of annotations in 3D views and Contour Map view.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eText annotations\u003c/li\u003e\n\u003cli\u003eReach circle annotations\u003c/li\u003e\n\u003cli\u003ePolyline annotations\n\n\u003cul\u003e\n\u003cli\u003eUser defined polylines\u003c/li\u003e\n\u003cli\u003ePolylines imported from file\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Annotations.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch2 id=\"global-scope-vs-local-scope-annotations\"\u003eGlobal scope vs local scope annotations\u003c/h2\u003e\n\n\u003cp\u003eGlobal annotations may be displayed in all views and are located in the \u003cstrong\u003eAnnotations\u003c/strong\u003e project tree node right below \u003cstrong\u003eGrid Models\u003c/strong\u003e (Global annotations sub tree). Local annotations are associated with a specific view and are located in the \u003cstrong\u003eAnnotations\u003c/strong\u003e project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.\u003c/p\u003e\n\n\u003cp\u003eAll global annotations also have a representation in the local \u003cstrong\u003eAnnotation\u003c/strong\u003e tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with \u003cstrong\u003eGlobal\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LocalAnnotationsTree.png\" alt=\"\" /\u003e\u003cbr/\u003e\nLocal annotations sub tree\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GlobalAnnotationsTree.png\" alt=\"\" /\u003e\u003cbr/\u003e\nGlobal annotations sub tree\u003c/p\u003e\n\n\u003ch2 id=\"text-annotations\"\u003eText Annotations\u003c/h2\u003e\n\n\u003cp\u003eThere are two ways of creating a new text annotation.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eRight click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eText Annotations\u003c/strong\u003e tree node in either the global annotatyion sub tree or the local annotations sub tree. The scope of the annotation depends on which node was clicked. When text annotations are created this way, all text annotation fields must be entered manunally in the property editor.\u003c/li\u003e\n\u003cli\u003eRight click on an object in the view and select \u003cstrong\u003eCreate Text Annotation\u003c/strong\u003e. ResInsight will then create a text annotation at the clicked point. In this case, only th text must be entered manually in the property editor. When creating a text annotation this way, it will become a local annotation by default.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TextAnnotationPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAnchor Point\u003c/strong\u003e - The interesting point in the view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel Point\u003c/strong\u003e - The point where the text label is placed\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eText\u003c/strong\u003e - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eText appearance\u003c/strong\u003e - Set font size, font color, background color and anchor line color\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.\u003c/p\u003e\n\n\u003ch2 id=\"reach-circle-annotations\"\u003eReach Circle Annotations\u003c/h2\u003e\n\n\u003cp\u003eTo create a reach circle annotation, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eReach Circle Annotations\u003c/strong\u003e tree node in the global annotations sub tree. Then enter values in the property editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CircleAnnotationPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e - Name of the circle annotation\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCenter Point\u003c/strong\u003e - Center point of the circle. Format \u0026lsquo;x-pos y-pos depth\u0026rsquo;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRadius\u003c/strong\u003e - Circle radius\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set circle color and line thickness\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"user-defined-polyline-annotations\"\u003eUser Defined Polyline Annotations\u003c/h2\u003e\n\n\u003cp\u003eTo create a user defined polyline annotation, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eUser Defined Polyline Annotations\u003c/strong\u003e tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click \u003cstrong\u003eStop Picking Points\u003c/strong\u003e in the property editor.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/UserDefinedPolylineAnnotationPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTargets\u003c/strong\u003e - Polyline points. Can be edited in the table or interactively in the view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Picking Points / Stop Picking Points\u003c/strong\u003e - Button to start / stop picking mode\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set line color and thickness\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eWhen a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.\u003c/p\u003e\n\n\u003ch2 id=\"polyline-imported-from-file\"\u003ePolyline Imported From File\u003c/h2\u003e\n\n\u003cp\u003eTo import a polyline annotation from file, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003ePolylines From File\u003c/strong\u003e tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PolylineFromFileAnnotationPropertyEditor.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile\u003c/strong\u003e - Name of the imported file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set line color and line thickness\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch2 id=\"annotations-visibility\"\u003eAnnotations visibility\u003c/h2\u003e\n\n\u003cp\u003eLocal annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.\u003c/p\u003e\n",
+                content:  "ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.\n Text annotations Reach circle annotations Polyline annotations  User defined polylines Polylines imported from file    Global scope vs local scope annotations Global annotations may be displayed in all views and are located in the Annotations project tree node right below Grid Models (Global annotations sub tree). Local annotations are associated with a specific view and are located in the Annotations project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.\nAll global annotations also have a representation in the local Annotation tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with Global.\nLocal annotations sub tree\nGlobal annotations sub tree\nText Annotations There are two ways of creating a new text annotation.\n Right click Annotations or Text Annotations tree node in either the global annotatyion sub tree or the local annotations sub tree. The scope of the annotation depends on which node was clicked. When text annotations are created this way, all text annotation fields must be entered manunally in the property editor. Right click on an object in the view and select Create Text Annotation. ResInsight will then create a text annotation at the clicked point. In this case, only th text must be entered manually in the property editor. When creating a text annotation this way, it will become a local annotation by default.   Anchor Point - The interesting point in the view Label Point - The point where the text label is placed Text - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree Text appearance - Set font size, font color, background color and anchor line color  When a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.\nReach Circle Annotations To create a reach circle annotation, right click Annotations or Reach Circle Annotations tree node in the global annotations sub tree. Then enter values in the property editor.\n Name - Name of the circle annotation Center Point - Center point of the circle. Format \u0026lsquo;x-pos y-pos depth\u0026rsquo; Radius - Circle radius Line Appearance - Set circle color and line thickness  User Defined Polyline Annotations To create a user defined polyline annotation, right click Annotations or User Defined Polyline Annotations tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click Stop Picking Points in the property editor.\n Targets - Polyline points. Can be edited in the table or interactively in the view Start Picking Points / Stop Picking Points - Button to start / stop picking mode Line Appearance - Set line color and thickness  When a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.\nPolyline Imported From File To import a polyline annotation from file, right click Annotations or Polylines From File tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.\n File - Name of the imported file Line Appearance - Set line color and line thickness  Annotations visibility Local annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.\n",
+                html:     "\u003cp\u003eResInsight supports displaying a few types of annotations in 3D views and Contour Map view.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eText annotations\u003c/li\u003e\n\u003cli\u003eReach circle annotations\u003c/li\u003e\n\u003cli\u003ePolyline annotations\n\u003cul\u003e\n\u003cli\u003eUser defined polylines\u003c/li\u003e\n\u003cli\u003ePolylines imported from file\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Annotations.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"global-scope-vs-local-scope-annotations\"\u003eGlobal scope vs local scope annotations\u003c/h2\u003e\n\u003cp\u003eGlobal annotations may be displayed in all views and are located in the \u003cstrong\u003eAnnotations\u003c/strong\u003e project tree node right below \u003cstrong\u003eGrid Models\u003c/strong\u003e (Global annotations sub tree). Local annotations are associated with a specific view and are located in the \u003cstrong\u003eAnnotations\u003c/strong\u003e project tree node below the view node (Local annotations sub tree). All annotation types except text annotations are global only. Text annotation may be either global or local.\u003c/p\u003e\n\u003cp\u003eAll global annotations also have a representation in the local \u003cstrong\u003eAnnotation\u003c/strong\u003e tree node in order to toggle visibilty per view. Those annotations are located in tree nodes starting with \u003cstrong\u003eGlobal\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LocalAnnotationsTree.png\" alt=\"\"\u003e\u003c!-- raw HTML omitted --\u003e\nLocal annotations sub tree\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GlobalAnnotationsTree.png\" alt=\"\"\u003e\u003c!-- raw HTML omitted --\u003e\nGlobal annotations sub tree\u003c/p\u003e\n\u003ch2 id=\"text-annotations\"\u003eText Annotations\u003c/h2\u003e\n\u003cp\u003eThere are two ways of creating a new text annotation.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eRight click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eText Annotations\u003c/strong\u003e tree node in either the global annotatyion sub tree or the local annotations sub tree. The scope of the annotation depends on which node was clicked. When text annotations are created this way, all text annotation fields must be entered manunally in the property editor.\u003c/li\u003e\n\u003cli\u003eRight click on an object in the view and select \u003cstrong\u003eCreate Text Annotation\u003c/strong\u003e. ResInsight will then create a text annotation at the clicked point. In this case, only th text must be entered manually in the property editor. When creating a text annotation this way, it will become a local annotation by default.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/TextAnnotationPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAnchor Point\u003c/strong\u003e - The interesting point in the view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLabel Point\u003c/strong\u003e - The point where the text label is placed\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eText\u003c/strong\u003e - The text to display. Multiline supprted. The first line will be the name of the annotation in the project tree\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eText appearance\u003c/strong\u003e - Set font size, font color, background color and anchor line color\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen a text annotation tree node is selected, target markers in each end of the anchor line are displayed. The targets can be clicked and dragged. Clicking the blue part lets the user drag the target vertically (along Z axis). Clicking the magenta part lets the user drag the target in the XY plane.\u003c/p\u003e\n\u003ch2 id=\"reach-circle-annotations\"\u003eReach Circle Annotations\u003c/h2\u003e\n\u003cp\u003eTo create a reach circle annotation, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eReach Circle Annotations\u003c/strong\u003e tree node in the global annotations sub tree. Then enter values in the property editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CircleAnnotationPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e - Name of the circle annotation\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCenter Point\u003c/strong\u003e - Center point of the circle. Format \u0026lsquo;x-pos y-pos depth\u0026rsquo;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRadius\u003c/strong\u003e - Circle radius\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set circle color and line thickness\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"user-defined-polyline-annotations\"\u003eUser Defined Polyline Annotations\u003c/h2\u003e\n\u003cp\u003eTo create a user defined polyline annotation, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003eUser Defined Polyline Annotations\u003c/strong\u003e tree node in the global annotations sub tree. The property editor for the newly created annotation is displayed and is in picking points mode. The user may now click on objects in the view to create polyline points. When finished, click \u003cstrong\u003eStop Picking Points\u003c/strong\u003e in the property editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/UserDefinedPolylineAnnotationPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTargets\u003c/strong\u003e - Polyline points. Can be edited in the table or interactively in the view\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStart Picking Points / Stop Picking Points\u003c/strong\u003e - Button to start / stop picking mode\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set line color and thickness\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen a user defined polyline annotation tree node is selected, the polyline target markers become visible. Those can be dragged around as decribed above.\u003c/p\u003e\n\u003ch2 id=\"polyline-imported-from-file\"\u003ePolyline Imported From File\u003c/h2\u003e\n\u003cp\u003eTo import a polyline annotation from file, right click \u003cstrong\u003eAnnotations\u003c/strong\u003e or \u003cstrong\u003ePolylines From File\u003c/strong\u003e tree node in the global annotations sub tree. Then select the file to import and click OK. Imported polyline annotations are not editable.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/PolylineFromFileAnnotationPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFile\u003c/strong\u003e - Name of the imported file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLine Appearance\u003c/strong\u003e - Set line color and line thickness\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"annotations-visibility\"\u003eAnnotations visibility\u003c/h2\u003e\n\u003cp\u003eLocal annotations visibility is controlled by the check boxes in the local annotations sub tree only. Global annotations visibility, on the other hand, is controlled by the check boxes in both the global and local annotations sub trees. So in order to display a global annotation in a specific view, both the annotation tree note itself and its representation in the local sub tree must have visibilty enabled.\u003c/p\u003e\n",
                 url:      "/3d-main-window/annotations/"
             };
         
@@ -2550,8 +2592,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/derivedresults/"] = {
                 title:    "Derived Results",
-                content:  " ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.\nDerived Results for Eclipse Cases ResInsight calculates several derived cell properties that is made available as Static or Dynamic cell properties. The derived results listed at the bottom of the Static result properties, are shown below.\nTransmissibility Normalized by Area The transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named riTRANXbyArea, riTRANYbyArea and riTRANZbyArea respectively.\nThe normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.\nOverall Transmissibility Multiplier Transmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named riTRANX, riTRANY and riTRANZ respectively.\nThe TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named riMULTX, riMULTY and riMULTZ respectively. The derived properties are listed under Static properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.\nDirectional Combined Results Cell properties with names ending in I, J, K, X, Y, or Z, and an optional \u0026ldquo;+\u0026rdquo; or \u0026ldquo;-\u0026rdquo; are combined into derived results post-fixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).\nThese combined cell properties visualize the property as a color in all directions combined when selected in as a Cell Result and Separate Fault Result.\nThe face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.\nThe directional combined parameters available are:\n Static Properties  TRANXYZ (inluding NNCs) MULTXYZ riTRANXYZ (inluding NNCs) riMULTXYZ (inluding NNCs) riTRANXYZbyArea (inluding NNCs)  Dynamic Properties  FLRWATIJK (inluding NNCs) FLROILIJK (inluding NNCs) FLRGASIJK (inluding NNCs)  Generated  Octave generated results with same name but ending with I,J and K will also be combined into a \u0026lt;name\u0026gt;IJK cell property.   Completion Type The dynamic cell property named Completion Type is calculated from the intersections between Completions and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.\nIf a cell is completed with multiple completions, the following priority is used : Fracture, Fishbones, and Perforation Interval.\nIdentification of Questionable NNCs In the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the Faults/NNCs With No Common Area folder. These NNCs are questionable since flow normally is associated with a flow area.\nWater Flooded PV Water Flooded PV, also called Number of flooded porevolumes shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.\nDerived Geomechanical results ResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.\nRelative Results (Time Lapse Results) ResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results. When enabled, every result variable is calculated as :\nValue\u0026rsquo;(t) = Value(t) - Value(BaseTime)\nEnable the Enable Relative Result option in the Relative Result Options group, and select the appropriate Base Time Step.\nEach variable is then post-fixed with \u0026ldquo;_DTimeStepIndex\u0026rdquo; to distinguish them from the native variables.\nNote: Relative Results calculated based on Gamma values are calculated slightly differently:\nGamma_Dn = ST_Dn / POR_Dn\nDerived Result Fields The calculated result fields are:\n Nodal  COMPACTION (Magnitude of compression)  Element Nodal and Integration Points  ST (Total Stress)  All tensor components Principals, with directions (Siinc, Siazi) STM (Mean total stress) Q (Deviatoric stress)  Gamma (Stress path) SE (Effective Stress)  All tensor components Principals, with directions SEM (Mean effective stress) SFI FOS DSM  E (Strain)  All tensor components EV (Volumetric strain) ED (Deviatoric strain)   Element Nodal On Face  Plane Pinc (Face inclination angle) Pazi (Face azimuth angle) Transformed Total and Effective Stress SN (Stress component normal to face) TP (Total in-plane shear) TPinc (Direction of TP) TPH ( Horizontal in-plane shear component ) TPQV ( Quasi vertical in-plane shear component ) FAULTMOB PCRIT    Definitions of Derived Results In this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.\nComponents with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.\nComponents with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to X, Y, and Z and thus also easting, northing, and depth.\n Inclination is measured from the downwards direction Azimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.  Case Constants Two constants can be assigned to a Geomechanical case:\n Cohesion Friction angle  In the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.\nCOMPACTION Compaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer. The reference K layer is specified in the property editor.\nFor each node n in the grid, a node nref in the reference K layer is found by vertical intersection from the node n.\nIf Depthn \u0026lt;= Depthnref:\nCOMPACTIONn = -(U3n - U3nref)\nelse:\nCOMPACTIONn = -(U3nref - U3n)\nST - Total Stress STii = -Saii + POR (i= 1,2,3)\nSTij = -Saij (i,j = 1,2,3 and i not equal j)\nWe use a value of POR=0.0 where it is not defined.\nSTi = Principal value i of ST\nSTM - Total Mean Stress STM = (ST11 + ST22 + ST33)/3\nQ - Deviatoric Stress Q = sqrt( (3\u0026frasl;2) * ( (ST1 – STM)2 + (ST2 – STM)2 + (ST3 – STM)2 ))\nGamma - Stress Path Gammaii = STii/POR (i= 1,2,3)\nGammai = STi/POR\nIn these calculations we set Gamma to undefined if abs(POR) \u0026gt; 0.01 MPa.\nSE - Effective Stress SEij = -Saij (Where POR is defined)\nSEij = undefined (Were POR is not defined)\nSEi = Principal value i of SE\nSEM - Effective Mean Stress SEM = (SE11 + SE22 + SE33)/3\nSFI SFI = ( (s0/tan(fa) + 0.5*(SE1 + SE3))sin(fa) ) /(0.5(SE1-SE3) )\nDSM DSM = tan(rho)/tan(fa)\nwhere\nrho = 2 * (arctan (sqrt (( SE1 + a)/(SE3 + a)) ) – pi/4)\na = s0/tan(fa)\nFOS FOS = 1/DSM\nE - Strain Eij = -Eaij\nEV - Volumetric Strain EV = E11 + E22 + E33\nED - Deviatoric Strain ED = 2*(E1-E3)/3\nElement Nodal On Face For each face displayed, (might be an element face or an intersection/intersection box face), a coordinate system is established such that:\n Ez is normal to the face, named N - Normal Ex is horizontal and in the plane of the face, named H - Horizontal Ey is in the plane pointing upwards, named QV - Quasi Vertical  The stress tensors in that particular face are then transformed to that coordinate system. The following quantities are derived from the transformed tensor named TS in the following:\nSN - Stress component Normal to face SN = TS33\nTPH - Horizontal in-plane shear component TPH = TS31 = TSZX\nTNQV - Horizontal in-plane shear component TPQV = TS32 = TSZY\nTP - Total in-plane shear TP = sqrt(TPH2 + TPQV2)\nTPinc - Direction of TP Angle of the total in-plane shear relative to the Quasi Vertical direction\nTPinc = acos(TPQV/TP)\nPinc and Pazi - Face Inclination and Azimuth These are the directional angles of the face-normal itself.\n",
-                html:     "\n\n\u003cp\u003eResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.\u003c/p\u003e\n\n\u003ch2 id=\"derived-results-for-eclipse-cases\"\u003eDerived Results for Eclipse Cases\u003c/h2\u003e\n\n\u003cp\u003eResInsight calculates several derived cell properties that is made available as \u003cstrong\u003eStatic\u003c/strong\u003e or \u003cstrong\u003eDynamic\u003c/strong\u003e cell properties.\nThe derived results listed at the bottom of the \u003cstrong\u003eStatic\u003c/strong\u003e result properties, are shown below.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedStaticResults.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"transmissibility-normalized-by-area\"\u003eTransmissibility Normalized by Area\u003c/h3\u003e\n\n\u003cp\u003eThe transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named \u003cstrong\u003eriTRANXbyArea\u003c/strong\u003e, \u003cstrong\u003eriTRANYbyArea\u003c/strong\u003e and \u003cstrong\u003eriTRANZbyArea\u003c/strong\u003e respectively.\u003c/p\u003e\n\n\u003cp\u003eThe normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.\u003c/p\u003e\n\n\u003ch3 id=\"overall-transmissibility-multiplier\"\u003eOverall Transmissibility Multiplier\u003c/h3\u003e\n\n\u003cp\u003eTransmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named \u003cstrong\u003eriTRANX\u003c/strong\u003e, \u003cstrong\u003eriTRANY\u003c/strong\u003e and \u003cstrong\u003eriTRANZ\u003c/strong\u003e respectively.\u003c/p\u003e\n\n\u003cp\u003eThe TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named \u003cstrong\u003eriMULTX\u003c/strong\u003e, \u003cstrong\u003eriMULTY\u003c/strong\u003e and \u003cstrong\u003eriMULTZ\u003c/strong\u003e respectively. The derived properties are listed under \u003cstrong\u003eStatic\u003c/strong\u003e properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.\u003c/p\u003e\n\n\u003ch3 id=\"directional-combined-results\"\u003eDirectional Combined Results\u003c/h3\u003e\n\n\u003cp\u003eCell properties with names ending in I, J, K, X, Y, or Z, and an optional \u0026ldquo;+\u0026rdquo; or \u0026ldquo;-\u0026rdquo; are combined into derived results post-fixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).\u003c/p\u003e\n\n\u003cp\u003eThese combined cell properties visualize the property as a color in all directions combined when selected in\nas a \u003cstrong\u003eCell Result\u003c/strong\u003e and \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003eThe face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.\u003c/p\u003e\n\n\u003cp\u003eThe directional combined parameters available are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eStatic Properties\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTRANXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMULTXYZ\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriTRANXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriMULTXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriTRANXYZbyArea\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eDynamic Properties\n\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFLRWATIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFLROILIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFLRGASIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eGenerated\n\n\u003cul\u003e\n\u003cli\u003eOctave generated results with same name but ending with I,J and K will also be combined into a \u003cem\u003e\u003ccode\u003e\u0026lt;name\u0026gt;IJK\u003c/code\u003e\u003c/em\u003e cell property.\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"completion-type\"\u003eCompletion Type\u003c/h3\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/CompletionTypes.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eThe dynamic cell property named \u003cstrong\u003eCompletion Type\u003c/strong\u003e is calculated from the intersections between \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.\u003c/p\u003e\n\n\u003cp\u003eIf a cell is completed with multiple completions, the following priority is used : \u003cstrong\u003eFracture\u003c/strong\u003e, \u003cstrong\u003eFishbones\u003c/strong\u003e, and \u003cstrong\u003ePerforation Interval\u003c/strong\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"identification-of-questionable-nncs\"\u003eIdentification of Questionable NNCs\u003c/h3\u003e\n\n\u003cp\u003eIn the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the \u003cstrong\u003eFaults/NNCs With No Common Area\u003c/strong\u003e folder. These NNCs are questionable since flow normally is associated with a flow area.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/ResInsight_NNCsWithNoCommonArea.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch3 id=\"water-flooded-pv\"\u003eWater Flooded PV\u003c/h3\u003e\n\n\u003cp\u003eWater Flooded PV, also called \u003cem\u003eNumber of flooded porevolumes\u003c/em\u003e shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.\u003c/p\u003e\n\n\u003ch2 id=\"derived-geomechanical-results\"\u003eDerived Geomechanical results\u003c/h2\u003e\n\n\u003cp\u003eResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.\u003c/p\u003e\n\n\u003ch3 id=\"relative-results-time-lapse-results\"\u003eRelative Results (Time Lapse Results)\u003c/h3\u003e\n\n\u003cp\u003eResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results.\nWhen enabled, every result variable is calculated as :\u003c/p\u003e\n\n\u003cp\u003eValue\u0026rsquo;(t) = Value(t) - Value(BaseTime)\u003c/p\u003e\n\n\u003cp\u003eEnable the \u003cstrong\u003eEnable Relative Result\u003c/strong\u003e  option in the \u003cstrong\u003eRelative Result Options\u003c/strong\u003e group, and select the appropriate \u003cstrong\u003eBase Time Step\u003c/strong\u003e.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedRelativeResults.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003cp\u003eEach variable is then post-fixed with \u0026ldquo;_D\u003cem\u003eTimeStepIndex\u003c/em\u003e\u0026rdquo; to distinguish them from the native variables.\u003c/p\u003e\n\n\u003cp\u003eNote: Relative Results calculated based on Gamma values are calculated slightly differently:\u003c/p\u003e\n\n\u003cp\u003eGamma_D\u003cem\u003en\u003c/em\u003e = ST_D\u003cem\u003en\u003c/em\u003e / POR_D\u003cem\u003en\u003c/em\u003e\u003c/p\u003e\n\n\u003ch3 id=\"derived-result-fields\"\u003eDerived Result Fields\u003c/h3\u003e\n\n\u003cp\u003eThe calculated result fields are:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eNodal\n\n\u003cul\u003e\n\u003cli\u003eCOMPACTION (Magnitude of compression)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eElement Nodal and Integration Points\n\n\u003cul\u003e\n\u003cli\u003eST (Total Stress)\n\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003ePrincipals, with directions (S\u003csub\u003ei\u003c/sub\u003einc, S\u003csub\u003ei\u003c/sub\u003eazi)\u003c/li\u003e\n\u003cli\u003eSTM (Mean total stress)\u003c/li\u003e\n\u003cli\u003eQ (Deviatoric stress)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eGamma (Stress path)\u003c/li\u003e\n\u003cli\u003eSE (Effective Stress)\n\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003ePrincipals, with directions\u003c/li\u003e\n\u003cli\u003eSEM (Mean effective stress)\u003c/li\u003e\n\u003cli\u003eSFI\u003c/li\u003e\n\u003cli\u003eFOS\u003c/li\u003e\n\u003cli\u003eDSM\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eE (Strain)\n\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003eEV (Volumetric strain)\u003c/li\u003e\n\u003cli\u003eED (Deviatoric strain)\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003cli\u003eElement Nodal On Face\n\n\u003cul\u003e\n\u003cli\u003ePlane\u003c/li\u003e\n\u003cli\u003ePinc (Face inclination angle)\u003c/li\u003e\n\u003cli\u003ePazi (Face azimuth angle)\u003c/li\u003e\n\u003cli\u003eTransformed Total and Effective Stress\u003c/li\u003e\n\u003cli\u003eSN (Stress component normal to face)\u003c/li\u003e\n\u003cli\u003eTP (Total in-plane shear)\u003c/li\u003e\n\u003cli\u003eTPinc (Direction of TP)\u003c/li\u003e\n\u003cli\u003eTPH ( Horizontal in-plane shear component )\u003c/li\u003e\n\u003cli\u003eTPQV ( Quasi vertical in-plane shear component )\u003c/li\u003e\n\u003cli\u003eFAULTMOB\u003c/li\u003e\n\u003cli\u003ePCRIT\n\u003cbr /\u003e\u003c/li\u003e\n\u003c/ul\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch4 id=\"definitions-of-derived-results\"\u003eDefinitions of Derived Results\u003c/h4\u003e\n\n\u003cp\u003eIn this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.\u003c/p\u003e\n\n\u003cp\u003eComponents with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.\u003c/p\u003e\n\n\u003cp\u003eComponents with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to  X, Y, and Z and thus also easting, northing, and depth.\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eInclination is measured from the downwards direction\u003c/li\u003e\n\u003cli\u003eAzimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch5 id=\"case-constants\"\u003eCase Constants\u003c/h5\u003e\n\n\u003cp\u003eTwo constants can be assigned to a Geomechanical case:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eCohesion\u003c/li\u003e\n\u003cli\u003eFriction angle\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eIn the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.\u003c/p\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/appendix/GeoMechCasePropertyPanel.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003ch5 id=\"compaction\"\u003eCOMPACTION\u003c/h5\u003e\n\n\u003cp\u003eCompaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer.\nThe reference K layer is specified in the property editor.\u003c/p\u003e\n\n\u003cp\u003eFor each node \u003ci\u003en\u003c/i\u003e in the grid, a node \u003ci\u003enref\u003c/i\u003e in the reference K layer is found by vertical intersection from the node \u003ci\u003en\u003c/i\u003e.\u003c/p\u003e\n\n\u003cp\u003eIf Depth\u003csub\u003en\u003c/sub\u003e \u0026lt;= Depth\u003csub\u003enref\u003c/sub\u003e:\u003c/p\u003e\n\n\u003cp\u003eCOMPACTION\u003csub\u003en\u003c/sub\u003e = -(U3\u003csub\u003en\u003c/sub\u003e - U3\u003csub\u003enref\u003c/sub\u003e)\u003c/p\u003e\n\n\u003cp\u003eelse:\u003c/p\u003e\n\n\u003cp\u003eCOMPACTION\u003csub\u003en\u003c/sub\u003e = -(U3\u003csub\u003enref\u003c/sub\u003e - U3\u003csub\u003en\u003c/sub\u003e)\u003c/p\u003e\n\n\u003ch5 id=\"st-total-stress\"\u003eST - Total Stress\u003c/h5\u003e\n\n\u003cp\u003eST\u003csub\u003eii\u003c/sub\u003e = -Sa\u003csub\u003eii\u003c/sub\u003e + POR (i= 1,2,3)\u003c/p\u003e\n\n\u003cp\u003eST\u003csub\u003eij\u003c/sub\u003e = -Sa\u003csub\u003eij\u003c/sub\u003e (i,j = 1,2,3 and i not equal j)\u003c/p\u003e\n\n\u003cp\u003eWe use a value of POR=0.0 where it is not defined.\u003c/p\u003e\n\n\u003cp\u003eST\u003csub\u003ei\u003c/sub\u003e = Principal value i of ST\u003c/p\u003e\n\n\u003ch5 id=\"stm-total-mean-stress\"\u003eSTM - Total Mean Stress\u003c/h5\u003e\n\n\u003cp\u003eSTM = (ST\u003csub\u003e11\u003c/sub\u003e + ST\u003csub\u003e22\u003c/sub\u003e + ST\u003csub\u003e33\u003c/sub\u003e)/3\u003c/p\u003e\n\n\u003ch5 id=\"q-deviatoric-stress\"\u003eQ - Deviatoric Stress\u003c/h5\u003e\n\n\u003cp\u003eQ = sqrt( (\u003csup\u003e3\u003c/sup\u003e\u0026frasl;\u003csub\u003e2\u003c/sub\u003e) * ( (ST\u003csub\u003e1\u003c/sub\u003e – STM)\u003csup\u003e2\u003c/sup\u003e  + (ST\u003csub\u003e2\u003c/sub\u003e – STM)\u003csup\u003e2\u003c/sup\u003e  + (ST\u003csub\u003e3\u003c/sub\u003e – STM)\u003csup\u003e2\u003c/sup\u003e ))\u003c/p\u003e\n\n\u003ch5 id=\"gamma-stress-path\"\u003eGamma - Stress Path\u003c/h5\u003e\n\n\u003cp\u003eGamma\u003csub\u003eii\u003c/sub\u003e = ST\u003csub\u003eii\u003c/sub\u003e/POR (i= 1,2,3)\u003c/p\u003e\n\n\u003cp\u003eGamma\u003csub\u003ei\u003c/sub\u003e = ST\u003csub\u003ei\u003c/sub\u003e/POR\u003c/p\u003e\n\n\u003cp\u003eIn these calculations we set Gamma to \u003cem\u003eundefined\u003c/em\u003e if abs(POR) \u0026gt; 0.01 MPa.\u003c/p\u003e\n\n\u003ch5 id=\"se-effective-stress\"\u003eSE - Effective Stress\u003c/h5\u003e\n\n\u003cp\u003eSE\u003csub\u003eij\u003c/sub\u003e = -Sa\u003csub\u003eij\u003c/sub\u003e (Where POR is defined)\u003c/p\u003e\n\n\u003cp\u003eSE\u003csub\u003eij\u003c/sub\u003e = \u003cem\u003eundefined\u003c/em\u003e (Were POR is not defined)\u003c/p\u003e\n\n\u003cp\u003eSE\u003csub\u003ei\u003c/sub\u003e = Principal value i of SE\u003c/p\u003e\n\n\u003ch5 id=\"sem-effective-mean-stress\"\u003eSEM - Effective Mean Stress\u003c/h5\u003e\n\n\u003cp\u003eSEM = (SE\u003csub\u003e11\u003c/sub\u003e + SE\u003csub\u003e22\u003c/sub\u003e + SE\u003csub\u003e33\u003c/sub\u003e)/3\u003c/p\u003e\n\n\u003ch5 id=\"sfi\"\u003eSFI\u003c/h5\u003e\n\n\u003cp\u003eSFI  =   ( (s0/tan(fa)  + 0.5*(SE\u003csub\u003e1\u003c/sub\u003e + SE\u003csub\u003e3\u003c/sub\u003e))\u003cem\u003esin(fa)  ) /(0.5\u003c/em\u003e(SE\u003csub\u003e1\u003c/sub\u003e-SE\u003csub\u003e3\u003c/sub\u003e) )\u003c/p\u003e\n\n\u003ch5 id=\"dsm\"\u003eDSM\u003c/h5\u003e\n\n\u003cp\u003eDSM = tan(rho)/tan(fa)\u003c/p\u003e\n\n\u003cp\u003ewhere\u003c/p\u003e\n\n\u003cp\u003erho = 2 * (arctan (sqrt (( SE\u003csub\u003e1\u003c/sub\u003e + a)/(SE\u003csub\u003e3\u003c/sub\u003e + a)) ) – pi/4)\u003c/p\u003e\n\n\u003cp\u003ea = s0/tan(fa)\u003c/p\u003e\n\n\u003ch5 id=\"fos\"\u003eFOS\u003c/h5\u003e\n\n\u003cp\u003eFOS = 1/DSM\u003c/p\u003e\n\n\u003ch5 id=\"e-strain\"\u003eE - Strain\u003c/h5\u003e\n\n\u003cp\u003eE\u003csub\u003eij\u003c/sub\u003e = -Ea\u003csub\u003eij\u003c/sub\u003e\u003c/p\u003e\n\n\u003ch5 id=\"ev-volumetric-strain\"\u003eEV - Volumetric Strain\u003c/h5\u003e\n\n\u003cp\u003eEV = E11 + E22 + E33\u003c/p\u003e\n\n\u003ch5 id=\"ed-deviatoric-strain\"\u003eED - Deviatoric Strain\u003c/h5\u003e\n\n\u003cp\u003eED = 2*(E1-E3)/3\u003c/p\u003e\n\n\u003ch5 id=\"element-nodal-on-face\"\u003eElement Nodal On Face\u003c/h5\u003e\n\n\u003cp\u003eFor each face displayed, (might be an element face or an intersection/intersection box face),\na coordinate system is established such that:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eEz is normal to the face, named N - Normal\u003c/li\u003e\n\u003cli\u003eEx is horizontal and in the plane of the face, named H - Horizontal\u003c/li\u003e\n\u003cli\u003eEy is in the plane pointing upwards, named QV - Quasi Vertical\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003cp\u003eThe stress tensors in that particular face are then transformed to that coordinate system.  The following quantities are derived from the transformed tensor named TS in the following:\u003c/p\u003e\n\n\u003ch5 id=\"sn-stress-component-normal-to-face\"\u003eSN - Stress component Normal to face\u003c/h5\u003e\n\n\u003cp\u003eSN = TS\u003csub\u003e33\u003c/sub\u003e\u003c/p\u003e\n\n\u003ch5 id=\"tph-horizontal-in-plane-shear-component\"\u003eTPH - Horizontal in-plane shear component\u003c/h5\u003e\n\n\u003cp\u003eTPH = TS\u003csub\u003e31\u003c/sub\u003e = TS\u003csub\u003eZX\u003c/sub\u003e\u003c/p\u003e\n\n\u003ch5 id=\"tnqv-horizontal-in-plane-shear-component\"\u003eTNQV - Horizontal in-plane shear component\u003c/h5\u003e\n\n\u003cp\u003eTPQV = TS\u003csub\u003e32\u003c/sub\u003e = TS\u003csub\u003eZY\u003c/sub\u003e\u003c/p\u003e\n\n\u003ch5 id=\"tp-total-in-plane-shear\"\u003eTP - Total in-plane shear\u003c/h5\u003e\n\n\u003cp\u003eTP = sqrt(TPH\u003csup\u003e2\u003c/sup\u003e + TPQV\u003csup\u003e2\u003c/sup\u003e)\u003c/p\u003e\n\n\u003ch5 id=\"tpinc-direction-of-tp\"\u003eTPinc - Direction of TP\u003c/h5\u003e\n\n\u003cp\u003eAngle of the total in-plane shear relative to the Quasi Vertical direction\u003c/p\u003e\n\n\u003cp\u003eTPinc = acos(TPQV/TP)\u003c/p\u003e\n\n\u003ch5 id=\"pinc-and-pazi-face-inclination-and-azimuth\"\u003ePinc and Pazi - Face Inclination and Azimuth\u003c/h5\u003e\n\n\u003cp\u003eThese are the directional angles of the face-normal itself.\u003c/p\u003e\n",
+                content:  "ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.\nDerived Results for Eclipse Cases ResInsight calculates several derived cell properties that is made available as Static or Dynamic cell properties. The derived results listed at the bottom of the Static result properties, are shown below.\nTransmissibility Normalized by Area The transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named riTRANXbyArea, riTRANYbyArea and riTRANZbyArea respectively.\nThe normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.\nOverall Transmissibility Multiplier Transmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named riTRANX, riTRANY and riTRANZ respectively.\nThe TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named riMULTX, riMULTY and riMULTZ respectively. The derived properties are listed under Static properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.\nDirectional Combined Results Cell properties with names ending in I, J, K, X, Y, or Z, and an optional \u0026ldquo;+\u0026rdquo; or \u0026ldquo;-\u0026rdquo; are combined into derived results post-fixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).\nThese combined cell properties visualize the property as a color in all directions combined when selected in as a Cell Result and Separate Fault Result.\nThe face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.\nThe directional combined parameters available are:\n Static Properties  TRANXYZ (inluding NNCs) MULTXYZ riTRANXYZ (inluding NNCs) riMULTXYZ (inluding NNCs) riTRANXYZbyArea (inluding NNCs)   Dynamic Properties  FLRWATIJK (inluding NNCs) FLROILIJK (inluding NNCs) FLRGASIJK (inluding NNCs)   Generated  Octave generated results with same name but ending with I,J and K will also be combined into a \u0026lt;name\u0026gt;IJK cell property.    Completion Type The dynamic cell property named Completion Type is calculated from the intersections between Completions and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.\nIf a cell is completed with multiple completions, the following priority is used : Fracture, Fishbones, and Perforation Interval.\nIdentification of Questionable NNCs In the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the Faults/NNCs With No Common Area folder. These NNCs are questionable since flow normally is associated with a flow area.\nWater Flooded PV Water Flooded PV, also called Number of flooded porevolumes shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.\nDerived Geomechanical results ResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.\nRelative Results (Time Lapse Results) ResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results. When enabled, every result variable is calculated as :\nValue\u0026rsquo;(t) = Value(t) - Value(BaseTime)\nEnable the Enable Relative Result option in the Relative Result Options group, and select the appropriate Base Time Step.\nEach variable is then post-fixed with \u0026ldquo;_DTimeStepIndex\u0026rdquo; to distinguish them from the native variables.\nNote: Relative Results calculated based on Gamma values are calculated slightly differently:\nGamma_Dn = ST_Dn / POR_Dn\nDerived Result Fields The calculated result fields are:\n Nodal  COMPACTION (Magnitude of compression)   Element Nodal and Integration Points  ST (Total Stress)  All tensor components Principals, with directions (Siinc, Siazi) STM (Mean total stress) Q (Deviatoric stress)   Gamma (Stress path) SE (Effective Stress)  All tensor components Principals, with directions SEM (Mean effective stress) SFI FOS DSM   E (Strain)  All tensor components EV (Volumetric strain) ED (Deviatoric strain)     Element Nodal On Face  Plane  Pinc (Face inclination angle) Pazi (Face azimuth angle)   Transformed Total and Effective Stress  SN (Stress component normal to face) TP (Total in-plane shear) TPinc (Direction of TP) TPH ( Horizontal in-plane shear component ) TPQV ( Quasi vertical in-plane shear component ) FAULTMOB PCRIT      Definitions of Derived Results In this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.\nComponents with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.\nComponents with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to X, Y, and Z and thus also easting, northing, and depth.\n Inclination is measured from the downwards direction Azimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.  Case Constants Two constants can be assigned to a Geomechanical case:\n Cohesion Friction angle  In the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.\nCOMPACTION Compaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer. The reference K layer is specified in the property editor.\nFor each node nin the grid, a node nrefin the reference K layer is found by vertical intersection from the node n.\nIf Depthn\u0026lt;= Depthnref:\nCOMPACTIONn= -(U3n- U3nref)\nelse:\nCOMPACTIONn= -(U3nref- U3n)\nST - Total Stress STii= -Saii+ POR (i= 1,2,3)\nSTij= -Saij(i,j = 1,2,3 and i not equal j)\nWe use a value of POR=0.0 where it is not defined.\nSTi= Principal value i of ST\nSTM - Total Mean Stress STM = (ST11+ ST22+ ST33)/3\nQ - Deviatoric Stress Q = sqrt( (3/2) * ( (ST1– STM)2+ (ST2– STM)2+ (ST3– STM)2))\nGamma - Stress Path Gammaii= STii/POR (i= 1,2,3)\nGammai= STi/POR\nIn these calculations we set Gamma to undefined if abs(POR) \u0026gt; 0.01 MPa.\nSE - Effective Stress SEij= -Saij(Where POR is defined)\nSEij= undefined (Were POR is not defined)\nSEi= Principal value i of SE\nSEM - Effective Mean Stress SEM = (SE11+ SE22+ SE33)/3\nSFI SFI = ( (s0/tan(fa) + 0.5*(SE1+ SE3))*sin(fa) ) /(0.5*(SE1-SE3) )\nDSM DSM = tan(rho)/tan(fa)\nwhere\nrho = 2 * (arctan (sqrt (( SE1+ a)/(SE3+ a)) ) – pi/4)\na = s0/tan(fa)\nFOS FOS = 1/DSM\nE - Strain Eij= -EaijEV - Volumetric Strain EV = E11 + E22 + E33\nED - Deviatoric Strain ED = 2*(E1-E3)/3\nElement Nodal On Face For each face displayed, (might be an element face or an intersection/intersection box face), a coordinate system is established such that:\n Ez is normal to the face, named N - Normal Ex is horizontal and in the plane of the face, named H - Horizontal Ey is in the plane pointing upwards, named QV - Quasi Vertical  The stress tensors in that particular face are then transformed to that coordinate system. The following quantities are derived from the transformed tensor named TS in the following:\nSN - Stress component Normal to face SN = TS33TPH - Horizontal in-plane shear component TPH = TS31= TSZXTNQV - Horizontal in-plane shear component TPQV = TS32= TSZYTP - Total in-plane shear TP = sqrt(TPH2+ TPQV2)\nTPinc - Direction of TP Angle of the total in-plane shear relative to the Quasi Vertical direction\nTPinc = acos(TPQV/TP)\nPinc and Pazi - Face Inclination and Azimuth These are the directional angles of the face-normal itself.\n",
+                html:     "\u003cp\u003eResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.\u003c/p\u003e\n\u003ch2 id=\"derived-results-for-eclipse-cases\"\u003eDerived Results for Eclipse Cases\u003c/h2\u003e\n\u003cp\u003eResInsight calculates several derived cell properties that is made available as \u003cstrong\u003eStatic\u003c/strong\u003e or \u003cstrong\u003eDynamic\u003c/strong\u003e cell properties.\nThe derived results listed at the bottom of the \u003cstrong\u003eStatic\u003c/strong\u003e result properties, are shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedStaticResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"transmissibility-normalized-by-area\"\u003eTransmissibility Normalized by Area\u003c/h3\u003e\n\u003cp\u003eThe transmissibility for cells and Non-Neighbor Connections (NNCs) are dependent on both cell properties and geometry. ResInsight normalizes TRANX, TRANY and TRANZ with the overlapping flow area for both neighbor cells and NNC-cells. The results are named \u003cstrong\u003eriTRANXbyArea\u003c/strong\u003e, \u003cstrong\u003eriTRANYbyArea\u003c/strong\u003e and \u003cstrong\u003eriTRANZbyArea\u003c/strong\u003e respectively.\u003c/p\u003e\n\u003cp\u003eThe normalized transmissibilities make it easier to compare and check the flow capacity visually. This can be useful when history matching pressure differences across a fault.\u003c/p\u003e\n\u003ch3 id=\"overall-transmissibility-multiplier\"\u003eOverall Transmissibility Multiplier\u003c/h3\u003e\n\u003cp\u003eTransmissibility can be set or adjusted with multiple keywords in an Eclipse data deck. To visualize the adjustments made, ResInsight calculates a multiplicator for the overall change. First unadjusted transmissibilities for all neighbor cells and NNCs are evaluated based on geometry and permeabilities, similar to the NEWTRAN algorithm in Eclipse. For x- and y-directions, the NTG parameter is also included. The results are named \u003cstrong\u003eriTRANX\u003c/strong\u003e, \u003cstrong\u003eriTRANY\u003c/strong\u003e and \u003cstrong\u003eriTRANZ\u003c/strong\u003e respectively.\u003c/p\u003e\n\u003cp\u003eThe TRANX, TRANY and TRANZ used in the simulation are divided by the ResInsight calculated transmissibilities and the resulting multiplicators are named \u003cstrong\u003eriMULTX\u003c/strong\u003e, \u003cstrong\u003eriMULTY\u003c/strong\u003e and \u003cstrong\u003eriMULTZ\u003c/strong\u003e respectively. The derived properties are listed under \u003cstrong\u003eStatic\u003c/strong\u003e properties. The riMULT-properties are useful for quality checking consistence in user input for fault seal along a fault plane.\u003c/p\u003e\n\u003ch3 id=\"directional-combined-results\"\u003eDirectional Combined Results\u003c/h3\u003e\n\u003cp\u003eCell properties with names ending in I, J, K, X, Y, or Z, and an optional \u0026ldquo;+\u0026rdquo; or \u0026ldquo;-\u0026rdquo; are combined into derived results post-fixed with IJK, or XYZ depending on their origin. (Eg. the static cell properties MULTX, MULTY, MULTZ, and their negatives are combined into the result MULTXYZ, while the dynamic cell properties FLRGASI, FLRGASJ, FLRGASK are combined to FLRGASIJK).\u003c/p\u003e\n\u003cp\u003eThese combined cell properties visualize the property as a color in all directions combined when selected in \nas a \u003cstrong\u003eCell Result\u003c/strong\u003e and \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe face of a cell is then colored based on the value associated with that particular face. The Positive I-face of the cell gets the cell X/I-value, while the J-face gets the Y/J-value etc. The negative faces, however, get the value from the neighbor cell on that side. The negative I-face gets the X-value of the IJK-neighbor in negative I direction, and so on for the J- and K-faces.\u003c/p\u003e\n\u003cp\u003eThe directional combined parameters available are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eStatic Properties\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTRANXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMULTXYZ\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriTRANXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriMULTXYZ\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eriTRANXYZbyArea\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eDynamic Properties\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFLRWATIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFLROILIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFLRGASIJK\u003c/strong\u003e (inluding NNCs)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eGenerated\n\u003cul\u003e\n\u003cli\u003eOctave generated results with same name but ending with I,J and K will also be combined into a \u003cem\u003e\u003ccode\u003e\u0026lt;name\u0026gt;IJK\u003c/code\u003e\u003c/em\u003e cell property.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"completion-type\"\u003eCompletion Type\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/CompletionTypes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe dynamic cell property named \u003cstrong\u003eCompletion Type\u003c/strong\u003e is calculated from the intersections between \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e and the grid cells. All grid cells intersected by a completion will be assigned a color based on the type of completion that intersects the cell.\u003c/p\u003e\n\u003cp\u003eIf a cell is completed with multiple completions, the following priority is used : \u003cstrong\u003eFracture\u003c/strong\u003e, \u003cstrong\u003eFishbones\u003c/strong\u003e, and \u003cstrong\u003ePerforation Interval\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"identification-of-questionable-nncs\"\u003eIdentification of Questionable NNCs\u003c/h3\u003e\n\u003cp\u003eIn the process of normalizing transmissibility by the overlapping flow area, the NNCs in the model without any shared surface between two cells are identified. These NNCs are listed in the \u003cstrong\u003eFaults/NNCs With No Common Area\u003c/strong\u003e folder. These NNCs are questionable since flow normally is associated with a flow area.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/ResInsight_NNCsWithNoCommonArea.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"water-flooded-pv\"\u003eWater Flooded PV\u003c/h3\u003e\n\u003cp\u003eWater Flooded PV, also called \u003cem\u003eNumber of flooded porevolumes\u003c/em\u003e shows the amount of flow from a selected set of simulation tracers into a particular cell, compared to the cells mobile pore volume. A value of 1.0 will tell that the tracers accumulated flow into the cell has reached a volume equal to the mobile pore volume in the cell.\u003c/p\u003e\n\u003ch2 id=\"derived-geomechanical-results\"\u003eDerived Geomechanical results\u003c/h2\u003e\n\u003cp\u003eResInsight calculates several of the presented geomechanical results based on the native results present in the odb-files.\u003c/p\u003e\n\u003ch3 id=\"relative-results-time-lapse-results\"\u003eRelative Results (Time Lapse Results)\u003c/h3\u003e\n\u003cp\u003eResInsight can calculate and display relative results, sometimes also referred to as Time Lapse results.\nWhen enabled, every result variable is calculated as :\u003c/p\u003e\n\u003cp\u003eValue\u0026rsquo;(t) = Value(t) - Value(BaseTime)\u003c/p\u003e\n\u003cp\u003eEnable the \u003cstrong\u003eEnable Relative Result\u003c/strong\u003e  option in the \u003cstrong\u003eRelative Result Options\u003c/strong\u003e group, and select the appropriate \u003cstrong\u003eBase Time Step\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedRelativeResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eEach variable is then post-fixed with \u0026ldquo;_D\u003cem\u003eTimeStepIndex\u003c/em\u003e\u0026rdquo; to distinguish them from the native variables.\u003c/p\u003e\n\u003cp\u003eNote: Relative Results calculated based on Gamma values are calculated slightly differently:\u003c/p\u003e\n\u003cp\u003eGamma_D\u003cem\u003en\u003c/em\u003e = ST_D\u003cem\u003en\u003c/em\u003e / POR_D\u003cem\u003en\u003c/em\u003e\u003c/p\u003e\n\u003ch3 id=\"derived-result-fields\"\u003eDerived Result Fields\u003c/h3\u003e\n\u003cp\u003eThe calculated result fields are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eNodal\n\u003cul\u003e\n\u003cli\u003eCOMPACTION (Magnitude of compression)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eElement Nodal and Integration Points\n\u003cul\u003e\n\u003cli\u003eST (Total Stress)\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003ePrincipals, with directions (S\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003einc, S\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003eazi)\u003c/li\u003e\n\u003cli\u003eSTM (Mean total stress)\u003c/li\u003e\n\u003cli\u003eQ (Deviatoric stress)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eGamma (Stress path)\u003c/li\u003e\n\u003cli\u003eSE (Effective Stress)\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003ePrincipals, with directions\u003c/li\u003e\n\u003cli\u003eSEM (Mean effective stress)\u003c/li\u003e\n\u003cli\u003eSFI\u003c/li\u003e\n\u003cli\u003eFOS\u003c/li\u003e\n\u003cli\u003eDSM\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eE (Strain)\n\u003cul\u003e\n\u003cli\u003eAll tensor components\u003c/li\u003e\n\u003cli\u003eEV (Volumetric strain)\u003c/li\u003e\n\u003cli\u003eED (Deviatoric strain)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eElement Nodal On Face\n\u003cul\u003e\n\u003cli\u003ePlane\n\u003cul\u003e\n\u003cli\u003ePinc (Face inclination angle)\u003c/li\u003e\n\u003cli\u003ePazi (Face azimuth angle)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eTransformed Total and Effective Stress\n\u003cul\u003e\n\u003cli\u003eSN (Stress component normal to face)\u003c/li\u003e\n\u003cli\u003eTP (Total in-plane shear)\u003c/li\u003e\n\u003cli\u003eTPinc (Direction of TP)\u003c/li\u003e\n\u003cli\u003eTPH ( Horizontal in-plane shear component )\u003c/li\u003e\n\u003cli\u003eTPQV ( Quasi vertical in-plane shear component )\u003c/li\u003e\n\u003cli\u003eFAULTMOB\u003c/li\u003e\n\u003cli\u003ePCRIT\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"definitions-of-derived-results\"\u003eDefinitions of Derived Results\u003c/h4\u003e\n\u003cp\u003eIn this text the label Sa and Ea will be used to denote the unchanged stress and strain tensor respectively from the odb file.\u003c/p\u003e\n\u003cp\u003eComponents with one subscript denotes the principal values 1, 2, and 3 which refers to the maximum, middle, and minimum principals respectively.\u003c/p\u003e\n\u003cp\u003eComponents with two subscripts however, refers to the global directions 1, 2, and 3 which corresponds to  X, Y, and Z and thus also easting, northing, and depth.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eInclination is measured from the downwards direction\u003c/li\u003e\n\u003cli\u003eAzimuth is measured from the Northing (Y) Axis in Clockwise direction looking down.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"case-constants\"\u003eCase Constants\u003c/h5\u003e\n\u003cp\u003eTwo constants can be assigned to a Geomechanical case:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCohesion\u003c/li\u003e\n\u003cli\u003eFriction angle\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIn the following they are denoted s0 and fa respectively. Some of the derived results use these constants, that can be changed in the property panel of the Case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/GeoMechCasePropertyPanel.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch5 id=\"compaction\"\u003eCOMPACTION\u003c/h5\u003e\n\u003cp\u003eCompaction is the difference in vertical displacement (U3) between a grid node and a specified reference K layer.\nThe reference K layer is specified in the property editor.\u003c/p\u003e\n\u003cp\u003eFor each node \u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e in the grid, a node \u003c!-- raw HTML omitted --\u003enref\u003c!-- raw HTML omitted --\u003e in the reference K layer is found by vertical intersection from the node \u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e.\u003c/p\u003e\n\u003cp\u003eIf Depth\u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e \u0026lt;= Depth\u003c!-- raw HTML omitted --\u003enref\u003c!-- raw HTML omitted --\u003e:\u003c/p\u003e\n\u003cp\u003eCOMPACTION\u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e = -(U3\u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e - U3\u003c!-- raw HTML omitted --\u003enref\u003c!-- raw HTML omitted --\u003e)\u003c/p\u003e\n\u003cp\u003eelse:\u003c/p\u003e\n\u003cp\u003eCOMPACTION\u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e = -(U3\u003c!-- raw HTML omitted --\u003enref\u003c!-- raw HTML omitted --\u003e - U3\u003c!-- raw HTML omitted --\u003en\u003c!-- raw HTML omitted --\u003e)\u003c/p\u003e\n\u003ch5 id=\"st---total-stress\"\u003eST - Total Stress\u003c/h5\u003e\n\u003cp\u003eST\u003c!-- raw HTML omitted --\u003eii\u003c!-- raw HTML omitted --\u003e = -Sa\u003c!-- raw HTML omitted --\u003eii\u003c!-- raw HTML omitted --\u003e + POR (i= 1,2,3)\u003c/p\u003e\n\u003cp\u003eST\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e = -Sa\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e (i,j = 1,2,3 and i not equal j)\u003c/p\u003e\n\u003cp\u003eWe use a value of POR=0.0 where it is not defined.\u003c/p\u003e\n\u003cp\u003eST\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003e = Principal value i of ST\u003c/p\u003e\n\u003ch5 id=\"stm---total-mean-stress\"\u003eSTM - Total Mean Stress\u003c/h5\u003e\n\u003cp\u003eSTM = (ST\u003c!-- raw HTML omitted --\u003e11\u003c!-- raw HTML omitted --\u003e + ST\u003c!-- raw HTML omitted --\u003e22\u003c!-- raw HTML omitted --\u003e + ST\u003c!-- raw HTML omitted --\u003e33\u003c!-- raw HTML omitted --\u003e)/3\u003c/p\u003e\n\u003ch5 id=\"q---deviatoric-stress\"\u003eQ - Deviatoric Stress\u003c/h5\u003e\n\u003cp\u003eQ = sqrt( (3/2) * ( (ST\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e – STM)\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e  + (ST\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e – STM)\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e  + (ST\u003c!-- raw HTML omitted --\u003e3\u003c!-- raw HTML omitted --\u003e – STM)\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e ))\u003c/p\u003e\n\u003ch5 id=\"gamma---stress-path\"\u003eGamma - Stress Path\u003c/h5\u003e\n\u003cp\u003eGamma\u003c!-- raw HTML omitted --\u003eii\u003c!-- raw HTML omitted --\u003e = ST\u003c!-- raw HTML omitted --\u003eii\u003c!-- raw HTML omitted --\u003e/POR (i= 1,2,3)\u003c/p\u003e\n\u003cp\u003eGamma\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003e = ST\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003e/POR\u003c/p\u003e\n\u003cp\u003eIn these calculations we set Gamma to \u003cem\u003eundefined\u003c/em\u003e if abs(POR) \u0026gt; 0.01 MPa.\u003c/p\u003e\n\u003ch5 id=\"se---effective-stress\"\u003eSE - Effective Stress\u003c/h5\u003e\n\u003cp\u003eSE\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e = -Sa\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e (Where POR is defined)\u003c/p\u003e\n\u003cp\u003eSE\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e = \u003cem\u003eundefined\u003c/em\u003e (Were POR is not defined)\u003c/p\u003e\n\u003cp\u003eSE\u003c!-- raw HTML omitted --\u003ei\u003c!-- raw HTML omitted --\u003e = Principal value i of SE\u003c/p\u003e\n\u003ch5 id=\"sem---effective-mean-stress\"\u003eSEM - Effective Mean Stress\u003c/h5\u003e\n\u003cp\u003eSEM = (SE\u003c!-- raw HTML omitted --\u003e11\u003c!-- raw HTML omitted --\u003e + SE\u003c!-- raw HTML omitted --\u003e22\u003c!-- raw HTML omitted --\u003e + SE\u003c!-- raw HTML omitted --\u003e33\u003c!-- raw HTML omitted --\u003e)/3\u003c/p\u003e\n\u003ch5 id=\"sfi\"\u003eSFI\u003c/h5\u003e\n\u003cp\u003eSFI  =   ( (s0/tan(fa)  + 0.5*(SE\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e + SE\u003c!-- raw HTML omitted --\u003e3\u003c!-- raw HTML omitted --\u003e))*sin(fa)  ) /(0.5*(SE\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e-SE\u003c!-- raw HTML omitted --\u003e3\u003c!-- raw HTML omitted --\u003e) )\u003c/p\u003e\n\u003ch5 id=\"dsm\"\u003eDSM\u003c/h5\u003e\n\u003cp\u003eDSM = tan(rho)/tan(fa)\u003c/p\u003e\n\u003cp\u003ewhere\u003c/p\u003e\n\u003cp\u003erho = 2 * (arctan (sqrt (( SE\u003c!-- raw HTML omitted --\u003e1\u003c!-- raw HTML omitted --\u003e + a)/(SE\u003c!-- raw HTML omitted --\u003e3\u003c!-- raw HTML omitted --\u003e + a)) ) – pi/4)\u003c/p\u003e\n\u003cp\u003ea = s0/tan(fa)\u003c/p\u003e\n\u003ch5 id=\"fos\"\u003eFOS\u003c/h5\u003e\n\u003cp\u003eFOS = 1/DSM\u003c/p\u003e\n\u003ch5 id=\"e---strain\"\u003eE - Strain\u003c/h5\u003e\n\u003cp\u003eE\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e = -Ea\u003c!-- raw HTML omitted --\u003eij\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003ch5 id=\"ev---volumetric-strain\"\u003eEV - Volumetric Strain\u003c/h5\u003e\n\u003cp\u003eEV = E11 + E22 + E33\u003c/p\u003e\n\u003ch5 id=\"ed---deviatoric-strain\"\u003eED - Deviatoric Strain\u003c/h5\u003e\n\u003cp\u003eED = 2*(E1-E3)/3\u003c/p\u003e\n\u003ch5 id=\"element-nodal-on-face\"\u003eElement Nodal On Face\u003c/h5\u003e\n\u003cp\u003eFor each face displayed, (might be an element face or an intersection/intersection box face), \na coordinate system is established such that:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEz is normal to the face, named N - Normal\u003c/li\u003e\n\u003cli\u003eEx is horizontal and in the plane of the face, named H - Horizontal\u003c/li\u003e\n\u003cli\u003eEy is in the plane pointing upwards, named QV - Quasi Vertical\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe stress tensors in that particular face are then transformed to that coordinate system.  The following quantities are derived from the transformed tensor named TS in the following:\u003c/p\u003e\n\u003ch5 id=\"sn---stress-component-normal-to-face\"\u003eSN - Stress component Normal to face\u003c/h5\u003e\n\u003cp\u003eSN = TS\u003c!-- raw HTML omitted --\u003e33\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003ch5 id=\"tph---horizontal-in-plane-shear-component\"\u003eTPH - Horizontal in-plane shear component\u003c/h5\u003e\n\u003cp\u003eTPH = TS\u003c!-- raw HTML omitted --\u003e31\u003c!-- raw HTML omitted --\u003e = TS\u003c!-- raw HTML omitted --\u003eZX\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003ch5 id=\"tnqv---horizontal-in-plane-shear-component\"\u003eTNQV - Horizontal in-plane shear component\u003c/h5\u003e\n\u003cp\u003eTPQV = TS\u003c!-- raw HTML omitted --\u003e32\u003c!-- raw HTML omitted --\u003e = TS\u003c!-- raw HTML omitted --\u003eZY\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003ch5 id=\"tp---total-in-plane-shear\"\u003eTP - Total in-plane shear\u003c/h5\u003e\n\u003cp\u003eTP = sqrt(TPH\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e + TPQV\u003c!-- raw HTML omitted --\u003e2\u003c!-- raw HTML omitted --\u003e)\u003c/p\u003e\n\u003ch5 id=\"tpinc---direction-of-tp\"\u003eTPinc - Direction of TP\u003c/h5\u003e\n\u003cp\u003eAngle of the total in-plane shear relative to the Quasi Vertical direction\u003c/p\u003e\n\u003cp\u003eTPinc = acos(TPQV/TP)\u003c/p\u003e\n\u003ch5 id=\"pinc-and-pazi---face-inclination-and-azimuth\"\u003ePinc and Pazi - Face Inclination and Azimuth\u003c/h5\u003e\n\u003cp\u003eThese are the directional angles of the face-normal itself.\u003c/p\u003e\n",
                 url:      "/3d-main-window/derivedresults/"
             };
         
@@ -2559,8 +2601,8 @@ if (!doNotTrack) {
          
             window.store["/_footer/"] = {
                 title:    "",
-                content:  " About Ceetron Solutions in collaboration with Equinor ASA Support ",
-                html:     "\n\n\u003ch3 id=\"about-hahahugoshortcode-s0-hbhb\"\u003e\u003ca href=\"/about/\"\u003eAbout\u003c/a\u003e\u003c/h3\u003e\n\n\u003ch3 id=\"ceetron-solutions-http-www-ceetronsolutions-com-in-collaboration-with-equinor-asa-https-www-equinor-com\"\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003eCeetron Solutions\u003c/a\u003e in collaboration with \u003ca href=\"https://www.equinor.com/\"\u003eEquinor ASA\u003c/a\u003e\u003c/h3\u003e\n\n\u003ch3 id=\"support-hahahugoshortcode-s1-hbhb\"\u003e\u003ca href=\"/support/\"\u003eSupport\u003c/a\u003e\u003c/h3\u003e\n",
+                content:  "About Ceetron Solutions in collaboration with Equinor ASA Support ",
+                html:     "\u003ch3 id=\"abouthahahugoshortcode-s0-hbhb\"\u003e\u003ca href=\"/about/\"\u003eAbout\u003c/a\u003e\u003c/h3\u003e\n\u003ch3 id=\"ceetron-solutionshttpwwwceetronsolutionscom-in-collaboration-with-equinor-asahttpswwwequinorcom\"\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003eCeetron Solutions\u003c/a\u003e in collaboration with \u003ca href=\"https://www.equinor.com/\"\u003eEquinor ASA\u003c/a\u003e\u003c/h3\u003e\n\u003ch3 id=\"supporthahahugoshortcode-s1-hbhb\"\u003e\u003ca href=\"/support/\"\u003eSupport\u003c/a\u003e\u003c/h3\u003e\n",
                 url:      "/_footer/"
             };
         
@@ -2568,8 +2610,8 @@ if (!doNotTrack) {
          
             window.store["/_header/"] = {
                 title:    "",
-                content:  "\n",
-                html:     "\u003cp\u003e\u003ca href=\"/\"\u003e\u003cimg src=\"/images/ResInsightCroppedIconPicture.png\" alt=\"logo\" /\u003e\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "",
+                html:     "\u003cp\u003e\u003c!-- raw HTML omitted --\u003e\u003cimg src=\"/images/ResInsightCroppedIconPicture.png\" alt=\"logo\"\u003e\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n",
                 url:      "/_header/"
             };
         
@@ -2577,8 +2619,8 @@ if (!doNotTrack) {
          
             window.store["/about/"] = {
                 title:    "About",
-                content:  " ResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations. It can also be configured to visualize geomechanical simulations from ABAQUS.\nThe system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.\nEfficient User Interface The user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.\nData Support The main input data is *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. Summary vectors can be imported from *.SMSPEC files. ResInsight also supports selected parts of Eclipse input files and can read grid information and corresponding cell property data sets from *.GRDECL files. Well log data can be imported from *.LAS files.\nResInsight can also be built with support for Geomechanical models from ABAQUS in the *.odb file format.\nUpdating and Refining Eclipse simulation models ResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:\n Adding Well Path Completions such as fractures, fishbones and perforations to well paths, including transmissibility calculations to allow for simulation in Eclipse. Easily and visually generate setup files for Local Grid Refinement (LGR) The generation of Eclipse Multi Segment Well-models for well path completions.  Flow Diagnostics Flow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital. More\u0026hellip;\nOctave Integration Integration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.\nProject organization ResInsight is developed by Ceetron Solutions in collaboration with with Equinor.\nResInsight is a part of the Open Porous Media Initiative. The software is hosted at GitHub, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.\nLicensing The software is licensed under GPL 3+, see Licensing details.\nWeb site programming and design Web site is built with Grav and Hugo\n",
-                html:     "\n\n\u003cp\u003eResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations.\nIt can also be configured to visualize geomechanical simulations from ABAQUS.\u003c/p\u003e\n\n\u003cp\u003eThe system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.\u003c/p\u003e\n\n\u003ch3 id=\"efficient-user-interface\"\u003eEfficient User Interface\u003c/h3\u003e\n\n\u003cp\u003eThe user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.\u003c/p\u003e\n\n\u003ch3 id=\"data-support\"\u003eData Support\u003c/h3\u003e\n\n\u003cp\u003eThe main input data is\n\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e.\nSummary vectors can be imported from \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e files.\nResInsight also supports selected parts of Eclipse input files and can read grid\ninformation and corresponding cell property data sets from \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files.\nWell log data can be imported from \u003cem\u003e\u003ccode\u003e*.LAS\u003c/code\u003e\u003c/em\u003e files.\u003c/p\u003e\n\n\u003cp\u003eResInsight can also be built with support for Geomechanical models from ABAQUS in the \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e file format.\u003c/p\u003e\n\n\u003ch3 id=\"updating-and-refining-eclipse-simulation-models\"\u003eUpdating and Refining Eclipse simulation models\u003c/h3\u003e\n\n\u003cp\u003eResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:\u003c/p\u003e\n\n\u003cul\u003e\n\u003cli\u003eAdding \u003cstrong\u003eWell Path Completions\u003c/strong\u003e such as fractures, fishbones and perforations to well paths, including transmissibility calculations to allow for simulation in Eclipse.\u003c/li\u003e\n\u003cli\u003eEasily and visually generate setup files for \u003cstrong\u003eLocal Grid Refinement\u003c/strong\u003e (LGR)\u003c/li\u003e\n\u003cli\u003eThe generation of Eclipse \u003cstrong\u003eMulti Segment Well\u003c/strong\u003e-models for well path completions.\u003c/li\u003e\n\u003c/ul\u003e\n\n\u003ch3 id=\"flow-diagnostics\"\u003eFlow Diagnostics\u003c/h3\u003e\n\n\u003cp\u003eFlow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called \u003ca href=\"https://github.com/OPM/opm-flowdiagnostics\"\u003eopm-flowdiagnostics\u003c/a\u003e developed by \u003ca href=\"http://www.sintef.no/digital\"\u003eSINTEF Digital\u003c/a\u003e. \u003ca href=\"/3d-main-window/cellresults/#flow-diagnostic-results\"\u003eMore\u0026hellip;\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"octave-integration\"\u003eOctave Integration\u003c/h3\u003e\n\n\u003cp\u003eIntegration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.\u003c/p\u003e\n\n\u003ch3 id=\"project-organization\"\u003eProject organization\u003c/h3\u003e\n\n\u003cp\u003eResInsight is developed by \u003ca href=\"https://www.ceetronsolutions.com/\"\u003eCeetron Solutions\u003c/a\u003e in collaboration with with \u003ca href=\"https://www.equinor.com/\"\u003eEquinor\u003c/a\u003e.\u003c/p\u003e\n\n\u003cp\u003eResInsight is a part of the \u003ca href=\"http://opm-project.org/\"\u003eOpen Porous Media Initiative\u003c/a\u003e.\nThe software is hosted at \u003ca href=\"https://github.com/OPM/ResInsight\"\u003eGitHub\u003c/a\u003e, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.\u003c/p\u003e\n\n\u003ch3 id=\"licensing\"\u003eLicensing\u003c/h3\u003e\n\n\u003cp\u003eThe software is licensed under GPL 3+, see \u003ca href=\"https://github.com/OPM/ResInsight/blob/master/COPYING\"\u003eLicensing details\u003c/a\u003e.\u003c/p\u003e\n\n\u003ch3 id=\"web-site-programming-and-design\"\u003eWeb site programming and design\u003c/h3\u003e\n\n\u003cp\u003eWeb site is built with \u003ca href=\"https://getgrav.org\"\u003eGrav\u003c/a\u003e and \u003ca href=\"https://gohugo.io\"\u003eHugo\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "ResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations. It can also be configured to visualize geomechanical simulations from ABAQUS.\nThe system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.\nEfficient User Interface The user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.\nData Support The main input data is *.GRID and *.EGRID files along with their *.INIT and restart files *.XNNN and *.UNRST. Summary vectors can be imported from *.SMSPEC files. ResInsight also supports selected parts of Eclipse input files and can read grid information and corresponding cell property data sets from *.GRDECL files. Well log data can be imported from *.LAS files.\nResInsight can also be built with support for Geomechanical models from ABAQUS in the *.odb file format.\nUpdating and Refining Eclipse simulation models ResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:\n Adding Well Path Completions such as fractures, fishbones and perforations to well paths, including transmissibility calculations to allow for simulation in Eclipse. Easily and visually generate setup files for Local Grid Refinement (LGR) The generation of Eclipse Multi Segment Well-models for well path completions.  Flow Diagnostics Flow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called opm-flowdiagnostics developed by SINTEF Digital. More\u0026hellip;\nOctave Integration Integration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.\nProject organization ResInsight is developed by Ceetron Solutions in collaboration with with [Equinor] (https://www.equinor.com/).\nResInsight is a part of the Open Porous Media Initiative. The software is hosted at GitHub, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.\nLicensing The software is licensed under GPL 3+, see Licensing details.\nWeb site programming and design Web site is built with Grav and Hugo\n",
+                html:     "\u003cp\u003eResInsight is an open source, cross-platform 3D visualization, curve plotting and post processing tool for Eclipse reservoir models and simulations. \nIt can also be configured to visualize geomechanical simulations from ABAQUS.\u003c/p\u003e\n\u003cp\u003eThe system also constitutes a framework for further development and can be extended to support new data sources and visualization methods, e.g. additional solvers, seismic data, CSEM, and more.\u003c/p\u003e\n\u003ch3 id=\"efficient-user-interface\"\u003eEfficient User Interface\u003c/h3\u003e\n\u003cp\u003eThe user interface is tailored for efficient interpretation of reservoir simulation data with specialized visualizations of properties, faults and wells. It enables easy handling of a large number of realizations and calculation of statistics. To be highly responsive, ResInsight exploits multi-core CPUs and GPUs. Efficient plotting of well log plots and summary vectors is available through selected plotting features.\u003c/p\u003e\n\u003ch3 id=\"data-support\"\u003eData Support\u003c/h3\u003e\n\u003cp\u003eThe main input data is\n\u003cem\u003e\u003ccode\u003e*.GRID\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.EGRID\u003c/code\u003e\u003c/em\u003e files along with their \u003cem\u003e\u003ccode\u003e*.INIT\u003c/code\u003e\u003c/em\u003e and restart files \u003cem\u003e\u003ccode\u003e*.XNNN\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.UNRST\u003c/code\u003e\u003c/em\u003e. \nSummary vectors can be imported from \u003cem\u003e\u003ccode\u003e*.SMSPEC\u003c/code\u003e\u003c/em\u003e files.\nResInsight also supports selected parts of Eclipse input files and can read grid \ninformation and corresponding cell property data sets from \u003cem\u003e\u003ccode\u003e*.GRDECL\u003c/code\u003e\u003c/em\u003e files. \nWell log data can be imported from \u003cem\u003e\u003ccode\u003e*.LAS\u003c/code\u003e\u003c/em\u003e files.\u003c/p\u003e\n\u003cp\u003eResInsight can also be built with support for Geomechanical models from ABAQUS in the \u003cem\u003e\u003ccode\u003e*.odb\u003c/code\u003e\u003c/em\u003e file format.\u003c/p\u003e\n\u003ch3 id=\"updating-and-refining-eclipse-simulation-models\"\u003eUpdating and Refining Eclipse simulation models\u003c/h3\u003e\n\u003cp\u003eResInsight contains several pre-processing tools for updating and improving Eclipse reservoir models, including but not limited to:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAdding \u003cstrong\u003eWell Path Completions\u003c/strong\u003e such as fractures, fishbones and perforations to well paths, including transmissibility calculations to allow for simulation in Eclipse.\u003c/li\u003e\n\u003cli\u003eEasily and visually generate setup files for \u003cstrong\u003eLocal Grid Refinement\u003c/strong\u003e (LGR)\u003c/li\u003e\n\u003cli\u003eThe generation of Eclipse \u003cstrong\u003eMulti Segment Well\u003c/strong\u003e-models for well path completions.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"flow-diagnostics\"\u003eFlow Diagnostics\u003c/h3\u003e\n\u003cp\u003eFlow diagnostics calculations are embedded in the user interface and allows instant visualization of several well-based flow diagnostics properties, such as : Time of flight, flooding and drainage regions, well pair communication, well tracer fractions, well allocation plots and well communication lines. The calculations are performed by a library called \u003ca href=\"https://github.com/OPM/opm-flowdiagnostics\"\u003eopm-flowdiagnostics\u003c/a\u003e developed by \u003ca href=\"http://www.sintef.no/digital\"\u003eSINTEF Digital\u003c/a\u003e. \u003ca href=\"/3d-main-window/cellresults/\"\u003eMore\u0026hellip;\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"octave-integration\"\u003eOctave Integration\u003c/h3\u003e\n\u003cp\u003eIntegration with GNU Octave enables powerful and flexible result manipulation and computations. Derived results can be returned to ResInsight for further handling and visualization. Eventually, derived and computed properties can be directly exported to Eclipse input formats for further simulation cycles and parameter studies.\u003c/p\u003e\n\u003ch3 id=\"project-organization\"\u003eProject organization\u003c/h3\u003e\n\u003cp\u003eResInsight is developed by \u003ca href=\"https://www.ceetronsolutions.com/\"\u003eCeetron Solutions\u003c/a\u003e in collaboration with with [Equinor] (\u003ca href=\"https://www.equinor.com/)\"\u003ehttps://www.equinor.com/)\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eResInsight is a part of the \u003ca href=\"http://opm-project.org/\"\u003eOpen Porous Media Initiative\u003c/a\u003e.\nThe software is hosted at \u003ca href=\"https://github.com/OPM/ResInsight\"\u003eGitHub\u003c/a\u003e, and the development progress can be monitored there. The GitHub issue tracker is heavily used to organize the development process.\u003c/p\u003e\n\u003ch3 id=\"licensing\"\u003eLicensing\u003c/h3\u003e\n\u003cp\u003eThe software is licensed under GPL 3+, see \u003ca href=\"https://github.com/OPM/ResInsight/blob/master/COPYING\"\u003eLicensing details\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"web-site-programming-and-design\"\u003eWeb site programming and design\u003c/h3\u003e\n\u003cp\u003eWeb site is built with \u003ca href=\"https://getgrav.org\"\u003eGrav\u003c/a\u003e and \u003ca href=\"https://gohugo.io\"\u003eHugo\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/about/"
             };
         
@@ -2595,8 +2637,8 @@ if (!doNotTrack) {
          
             window.store["/"] = {
                 title:    "ResInsight",
-                content:  " ResInsight • 3D viewer and post processing of reservoir models\nPost Processing of Reservoir Simulations Post Processing of Reservoir Simulations\n    -- Fast and Free  \u0026#x2713; Open source\n\u0026#x2713; Efficient user interface\n\u0026#x2713; Handles large Eclipse cases\n\u0026#x2713; Plotting of summary vectors\n\u0026#x2713; Embedded Flow Diagnostics\n Unique Features  \u0026#x2713; NNC visualization\n\u0026#x2713; Cell Edge Coloring\n\u0026#x2713; Detailed MSW visualization\n\u0026#x2713; Seamless Octave integration\n\u0026#x2713; Supports geomechanical ABAQUS simulations\n Getting started  It's easy and free, both on Linux and Windows: Download and Install \u0026rarr;\nGetting Started \u0026rarr; Sign up to be notified of new releases: Release Notification \u0026rarr;    Here are some words from a few of the happy ResInsight users Testimonials \u0026rarr;    ",
-                html:     "\n\n\u003cp\u003e\u003ctitle\u003eResInsight • 3D viewer and post processing of reservoir models\u003c/title\u003e\u003c/p\u003e\n\n\u003ch1 id=\"post-processing-of-reservoir-simulations\"\u003ePost Processing of Reservoir Simulations\u003c/h1\u003e\n\n\u003cp\u003e\u003cimg src=\"/images/FrontPageImage.png\" alt=\"\" /\u003e\u003c/p\u003e\n\n\u003c!--\n\u003csection class=\"intro\"\u003e\n  \u003cdiv class=\"grid\"\u003e\n    \u003cdiv class=\"unit whole center-on-mobiles\"\u003e\n      \u003cp class=\"first\"\u003ePost Processing of Reservoir Simulations\u003c/p\u003e\n    \u003c/div\u003e\n    \u003cdiv class=\"post-content\"\u003e\n      \u003cimg src=\"/images/FrontPageImage.png\" alt=\"Reservoir\" /\u003e\n    \u003c/div\u003e\n  \u003c/div\u003e\n\u003c/section\u003e --\u003e\n\n\u003csection class=\"features\"\u003e\n  \u003cdiv class=\"grid\"\u003e\n    \u003cdiv class=\"unit one-third\"\u003e\n      \u003ch3\u003eFast and Free\u003c/h3\u003e\n      \u003cp\u003e\n        \u0026#x2713; Open source\u003cbr\u003e\n        \u0026#x2713; Efficient user interface\u003cbr\u003e\n    \u0026#x2713; Handles large Eclipse cases\u003cbr\u003e\n        \u0026#x2713; Plotting of summary vectors\u003cbr\u003e\n    \u0026#x2713; Embedded Flow Diagnostics\u003cbr\u003e\n      \u003c/p\u003e\n    \u003c/div\u003e\n    \u003cdiv class=\"unit one-third\"\u003e\n      \u003ch3\u003eUnique Features\u003c/h3\u003e\n      \u003cp\u003e\n        \u0026#x2713; NNC visualization\u003cbr\u003e\n        \u0026#x2713; Cell Edge Coloring\u003cbr\u003e\n        \u0026#x2713; Detailed MSW visualization\u003cbr\u003e\n        \u0026#x2713; Seamless \u003ca href=\"http://www.gnu.org/software/octave/\"\u003e Octave\u003c/a\u003e integration\u003cbr\u003e\n        \u0026#x2713; Supports geomechanical ABAQUS simulations\u003cbr\u003e\n      \u003c/p\u003e\n    \u003c/div\u003e\n    \u003cdiv class=\"unit one-third\"\u003e\n      \u003ch3\u003eGetting started\u003c/h3\u003e\n      \u003cp\u003e\n        It's easy and free, both on Linux and Windows:\n      \u003c/p\u003e\n      \u003ca href=\"/getting-started/download-and-install/\"\u003eDownload and Install \u0026rarr;\u003c/a\u003e\u003cbr\u003e\n      \u003ca href=\"/getting-started/\"\u003eGetting Started \u0026rarr;\u003c/a\u003e\n      \u003cp\u003eSign up to be notified of new releases:\n        \u003cbr\u003e\n        \u003ca href=\"/getting-started/other/releasenotification/\"\u003eRelease Notification \u0026rarr;\u003c/a\u003e\n      \u003c/p\u003e\n      \u003c/div\u003e\n    \u003cdiv class=\"clear\"\u003e\u003c/div\u003e\n  \u003c/div\u003e\n\n  \u003cdiv class=\"grid\"\u003e\n    \u003cdiv class=\"unit whole center-on-mobiles\"\u003e\n      \u003cp\u003eHere are some words from a few of the happy ResInsight users \u003ca href=\"/getting-started/other/testimonials/\"\u003eTestimonials \u0026rarr;\u003c/a\u003e \u003c/p\u003e\n    \u003c/div\u003e\n  \u003c/div\u003e\n\u003c/section\u003e\n",
+                content:  "Post Processing of Reservoir Simulations ",
+                html:     "\u003c!-- raw HTML omitted --\u003e\n\u003ch1 id=\"post-processing-of-reservoir-simulations\"\u003ePost Processing of Reservoir Simulations\u003c/h1\u003e\n\u003cp\u003e\u003cimg src=\"/images/FrontPageImage.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\n\u003c!-- raw HTML omitted --\u003e\n",
                 url:      "/"
             };
         
@@ -2606,8 +2648,8 @@ if (!doNotTrack) {
          
             window.store["/support/"] = {
                 title:    "Support",
-                content:  " For inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.\nPhone : +47 73 60 43 00 e-mail : info@ceetronsolutions.com\nBug reports and general feature requests can be filed directly on GitHub\n\nCeetron Solutions AS - Digitalization and visualization for engineers \n",
-                html:     "\n\n\u003cp\u003eFor inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.\u003c/p\u003e\n\n\u003cp\u003ePhone : +47 73 60 43 00 \u003cbr\u003e\ne-mail : info@ceetronsolutions.com\u003c/p\u003e\n\n\u003cp\u003eBug reports and general feature requests can be filed directly on \u003ca href=\"https://github.com/OPM/ResInsight/issues?state=open\"\u003eGitHub\u003c/a\u003e\u003c/p\u003e\n\n\u003cp\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003e\u003cimg src=\"/images/CeetronSolutionWebPage.png\" alt=\"\" /\u003e\u003c/a\u003e\u003c/p\u003e\n\n\u003ch3 id=\"ceetron-solutions-as-digitalization-and-visualization-for-engineers-http-www-ceetronsolutions-com\"\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003eCeetron Solutions AS - Digitalization and visualization for engineers\u003c/a\u003e\u003c/h3\u003e\n\n\u003cp\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003e\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "For inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.\nPhone : +47 73 60 43 00 e-mail : info@ceetronsolutions.com\nBug reports and general feature requests can be filed directly on GitHub\nCeetron Solutions AS - Digitalization and visualization for engineers ",
+                html:     "\u003cp\u003eFor inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.\u003c/p\u003e\n\u003cp\u003ePhone : +47 73 60 43 00 \u003c!-- raw HTML omitted --\u003e\ne-mail : \u003ca href=\"mailto:info@ceetronsolutions.com\"\u003einfo@ceetronsolutions.com\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBug reports and general feature requests can be filed directly on \u003ca href=\"https://github.com/OPM/ResInsight/issues?state=open\"\u003eGitHub\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003c!-- raw HTML omitted --\u003e\u003cimg src=\"/images/CeetronSolutionWebPage.png\" alt=\"\"\u003e\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n\u003ch3 id=\"ceetron-solutions-as---digitalization-and-visualization-for-engineershttpwwwceetronsolutionscom\"\u003e\u003ca href=\"http://www.ceetronsolutions.com\"\u003eCeetron Solutions AS - Digitalization and visualization for engineers\u003c/a\u003e\u003c/h3\u003e\n\u003cp\u003e\u003c!-- raw HTML omitted --\u003e\u003c!-- raw HTML omitted --\u003e\u003c/p\u003e\n",
                 url:      "/support/"
             };
         
@@ -2798,6 +2840,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2808,6 +2863,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3948,20 +4006,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/sitemap.xml b/sitemap.xml
index 33b14f46aa..c205784378 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
   xmlns:xhtml="http://www.w3.org/1999/xhtml">
   
@@ -282,6 +282,10 @@
     <loc>https://resinsight.org/3d-main-window/faults/</loc>
   </url>
   
+  <url>
+    <loc>https://resinsight.org/getting-started/other/</loc>
+  </url>
+  
   <url>
     <loc>https://resinsight.org/plot-window/rftplot/</loc>
   </url>
@@ -352,7 +356,6 @@
   
   <url>
     <loc>https://resinsight.org/categories/</loc>
-    <priority>0</priority>
   </url>
   
   <url>
@@ -369,7 +372,6 @@
   
   <url>
     <loc>https://resinsight.org/tags/</loc>
-    <priority>0</priority>
   </url>
   
 </urlset>
\ No newline at end of file
diff --git a/support/index.html b/support/index.html
index e57077301e..8411132622 100644
--- a/support/index.html
+++ b/support/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Support :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1762,15 +1796,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#ceetron-solutions-as-digitalization-and-visualization-for-engineers-http-www-ceetronsolutions-com"><a href="http://www.ceetronsolutions.com">Ceetron Solutions AS - Digitalization and visualization for engineers</a></a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#ceetron-solutions-as---digitalization-and-visualization-for-engineershttpwwwceetronsolutionscom"><a href="http://www.ceetronsolutions.com">Ceetron Solutions AS - Digitalization and visualization for engineers</a></a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1795,20 +1827,13 @@ if (!doNotTrack) {
 
 
 
-
-
 <p>For inquiries for new features, enhancements or support and maintenance agreements, please contact us for an offer.</p>
-
-<p>Phone : +47 73 60 43 00 <br>
-e-mail : info@ceetronsolutions.com</p>
-
+<p>Phone : +47 73 60 43 00 <!-- raw HTML omitted -->
+e-mail : <a href="mailto:info@ceetronsolutions.com">info@ceetronsolutions.com</a></p>
 <p>Bug reports and general feature requests can be filed directly on <a href="https://github.com/OPM/ResInsight/issues?state=open">GitHub</a></p>
-
-<p><a href="http://www.ceetronsolutions.com"><img src="/images/CeetronSolutionWebPage.png" alt="" /></a></p>
-
-<h3 id="ceetron-solutions-as-digitalization-and-visualization-for-engineers-http-www-ceetronsolutions-com"><a href="http://www.ceetronsolutions.com">Ceetron Solutions AS - Digitalization and visualization for engineers</a></h3>
-
-<p><a href="http://www.ceetronsolutions.com"></a></p>
+<p><!-- raw HTML omitted --><img src="/images/CeetronSolutionWebPage.png" alt=""><!-- raw HTML omitted --></p>
+<h3 id="ceetron-solutions-as---digitalization-and-visualization-for-engineershttpwwwceetronsolutionscom"><a href="http://www.ceetronsolutions.com">Ceetron Solutions AS - Digitalization and visualization for engineers</a></h3>
+<p><!-- raw HTML omitted --><!-- raw HTML omitted --></p>
 
 
 <footer class=" footline" >
@@ -1984,6 +2009,19 @@ e-mail : info@ceetronsolutions.com</p>
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1994,6 +2032,9 @@ e-mail : info@ceetronsolutions.com</p>
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3134,20 +3175,20 @@ e-mail : info@ceetronsolutions.com</p>
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/tags/index.html b/tags/index.html
index dc667236a6..332ba2c8b3 100644
--- a/tags/index.html
+++ b/tags/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Tags :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1746,7 +1780,13 @@ if (!doNotTrack) {
                     
           
           
-            Tags
+            
+            
+          
+          
+            <a href='/'>ResInsight</a> > Tags
+          
+         
           
         
                  
@@ -1959,6 +1999,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1969,6 +2022,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3109,20 +3165,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/tags/index.xml b/tags/index.xml
index fda6e4b6ce..b02605f875 100644
--- a/tags/index.xml
+++ b/tags/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Tags on ResInsight</title>
diff --git a/wells-and-completions/3dwelllogcurves/index.html b/wells-and-completions/3dwelllogcurves/index.html
index 71cebf9bae..47beeb6b2d 100644
--- a/wells-and-completions/3dwelllogcurves/index.html
+++ b/wells-and-completions/3dwelllogcurves/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Well Log Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,23 +1802,16 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#creating-new-3d-well-log-curves">Creating new 3D Well Log Curves</a></li>
-<li><a href="#deleting-3d-well-log-curves">Deleting 3D Well Log Curves</a></li>
-<li><a href="#configurating-the-3d-well-log-curves">Configurating the 3D Well Log Curves</a>
-<ul>
-<li><a href="#3d-track-and-draw-plane-appearance">3D Track and Draw Plane Appearance</a></li>
-<li><a href="#curve-configuration">Curve Configuration</a>
-<ul>
-<li><a href="#data-selection">Data Selection</a></li>
-<li><a href="#appearance">Appearance</a></li>
-<li><a href="#name-generation">Name Generation</a></li>
-</ul></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#creating-new-3d-well-log-curves">Creating new 3D Well Log Curves</a></li>
+    <li><a href="#deleting-3d-well-log-curves">Deleting 3D Well Log Curves</a></li>
+    <li><a href="#configurating-the-3d-well-log-curves">Configurating the 3D Well Log Curves</a>
+      <ul>
+        <li><a href="#3d-track-and-draw-plane-appearance">3D Track and Draw Plane Appearance</a></li>
+        <li><a href="#curve-configuration">Curve Configuration</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1809,32 +1836,18 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/3dWellLogCurves.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves.png" alt=""></p>
 <p>ResInsight can display well logs curves directly in the 3D view with a subset of the functionality of the full <a href="/plot-window/welllogsandplots/">2D Well Log Plot Editor</a>. The curves will be drawn in a plane next to or centered on the well trajectory they belong to and can display well log data from a simulation model and from imported LAS-files.</p>
-
 <h2 id="creating-new-3d-well-log-curves">Creating new 3D Well Log Curves</h2>
-
 <p>Add a new 3D well log curve by selecting a Well Path in the Project Tree, right-clicking and selecting <strong>3D Well Log Curves</strong> and <strong>Add 3D Well Log Curve</strong>.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurvesCreate.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurvesCreate.png" alt=""></p>
 <h2 id="deleting-3d-well-log-curves">Deleting 3D Well Log Curves</h2>
-
 <p>Delete one or more 3D well log curves by selecting them in the project tree, right-clicking on one of the selected items and choosing <strong>Delete 3D Well Log Curve(s)</strong>. The curves will be deleted with no further confirmation.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurvesDelete.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurvesDelete.png" alt=""></p>
 <h2 id="configurating-the-3d-well-log-curves">Configurating the 3D Well Log Curves</h2>
-
 <h3 id="3d-track-and-draw-plane-appearance">3D Track and Draw Plane Appearance</h3>
-
 <p>Each 3D well log curve belongs to a 3D Track which in turn is attached to a well path. The 3D track itself contains some settings related to the display of the curves.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurves_DrawPlaneAppearance.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves_DrawPlaneAppearance.png" alt=""></p>
 <table>
 <thead>
 <tr>
@@ -1843,20 +1856,17 @@ if (!doNotTrack) {
 <th>Range</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Show Grid</td>
 <td>Show axis markers for the value-axis of the curves along the draw surface</td>
 <td>True/False</td>
 </tr>
-
 <tr>
 <td>Show Background</td>
 <td>Draw a white background on the drawing surfaces of the curves</td>
 <td>True/False</td>
 </tr>
-
 <tr>
 <td>Width Scaling</td>
 <td>A scaling factor applied to the width of the draw surfaces</td>
@@ -1864,17 +1874,11 @@ if (!doNotTrack) {
 </tr>
 </tbody>
 </table>
-
 <h3 id="curve-configuration">Curve Configuration</h3>
-
 <p>In addition to the 3D track configuration, each 3D well log curve may be configured in its Property Editor. Here settings are grouped into three categories: Data Selection, Appearance and Name Generation.</p>
-
 <h4 id="data-selection">Data Selection</h4>
-
 <p>The <strong>Curve Data</strong> configuration allows you to select a case, result type, property and time step to plot.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurves_CurveData.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves_CurveData.png" alt=""></p>
 <table>
 <thead>
 <tr>
@@ -1882,42 +1886,31 @@ if (!doNotTrack) {
 <th>Description</th>
 </tr>
 </thead>
-
 <tbody>
 <tr>
 <td>Case</td>
 <td>The eclipse or geomechanical case to retrieve the data from</td>
 </tr>
-
 <tr>
 <td>Result Type</td>
 <td>Dynamic, static, generated, input property, formation names, flow diagnostics or injection flooding</td>
 </tr>
-
 <tr>
 <td>Result Property</td>
 <td>The parameter to plot</td>
 </tr>
-
 <tr>
 <td>Time Step</td>
 <td>Which time step to show</td>
 </tr>
 </tbody>
 </table>
-
 <h4 id="appearance">Appearance</h4>
-
 <p>In the <strong>Curve Appearance</strong> box, the curve can be assigned to a draw plane, the color can be changed and a range of curve values applied. The range of the result property can be set with the minimum and maximum curve value settings. The curve range is by default set to the minimum and maximum values found in the data set and these values are retained in the label if different values have been chosen.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurves_CurveConfiguration.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves_CurveConfiguration.png" alt=""></p>
 <p>The draw plane can be vertical (above well path, centered and below well path) and horizontal (left, centered and right). If multiple curves are added and assigned to the same draw plane, they will appear in the same curve plot.</p>
-
-<p><img src="/images/3d-main-window/3dWellLogCurves_DrawPlaneSelection.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/3dWellLogCurves_DrawPlaneSelection.png" alt=""></p>
 <h4 id="name-generation">Name Generation</h4>
-
 <p>Finally the name of the curve is created automatically from a set of parameters such as case, view, etc. The parameters that should make up the curve name can be selected in the <strong>Curve Name</strong> box. Only extraction log curves have multiple settings here. The automatic name generation will be automatically switched off if the curve has been renamed manually and can be switched back on by checking the <strong>Generate Name Automatically</strong> tick box.</p>
 
 
@@ -2094,6 +2087,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2104,6 +2110,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3254,20 +3263,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/completions/index.html b/wells-and-completions/completions/index.html
index a67cca0c3c..d5ab681ff8 100644
--- a/wells-and-completions/completions/index.html
+++ b/wells-and-completions/completions/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,39 +1802,30 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#visualization-and-inspection-of-well-connection-factors">Visualization and Inspection of Well Connection Factors</a></li>
-<li><a href="#perforation-intervals">Perforation Intervals</a>
-<ul>
-<li><a href="#perforation-interval-valves">Perforation Interval Valves</a></li>
-<li><a href="#import-perforation-intervals">Import Perforation Intervals</a>
-<ul>
-<li><a href="#perforation-interval-file-format">Perforation Interval File Format</a></li>
-</ul></li>
-</ul></li>
-<li><a href="#fishbones">Fishbones</a>
-<ul>
-<li><a href="#fishbones-subs-definition">Fishbones Subs Definition</a></li>
-<li><a href="#import-well-trajectories-as-fishbones-laterals">Import Well Trajectories as Fishbones Laterals</a></li>
-<li><a href="#export-fishbones-as-well-trajectories">Export Fishbones as Well Trajectories</a></li>
-</ul></li>
-<li><a href="#fractures">Fractures</a>
-<ul>
-<li><a href="#visualization-control">Visualization control</a></li>
-<li><a href="#fracture-templates">Fracture Templates</a>
-<ul>
-<li><a href="#common-fracture-template-options">Common Fracture Template Options</a></li>
-<li><a href="#non-darcy-flow">Non-Darcy Flow</a></li>
-<li><a href="#ellipse-fracture-template">Ellipse Fracture Template</a></li>
-<li><a href="#stimplan-fracture-template">Stimplan Fracture Template</a></li>
-</ul></li>
-<li><a href="#fracture-instances">Fracture Instances</a></li>
-<li><a href="#multiple-fracture-creation">Multiple Fracture Creation</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#visualization-and-inspection-of-well-connection-factors">Visualization and Inspection of Well Connection Factors</a></li>
+    <li><a href="#perforation-intervals">Perforation Intervals</a>
+      <ul>
+        <li><a href="#perforation-interval-valves">Perforation Interval Valves</a></li>
+        <li><a href="#import-perforation-intervals">Import Perforation Intervals</a></li>
+      </ul>
+    </li>
+    <li><a href="#fishbones">Fishbones</a>
+      <ul>
+        <li><a href="#fishbones-subs-definition">Fishbones Subs Definition</a></li>
+        <li><a href="#import-well-trajectories-as-fishbones-laterals">Import Well Trajectories as Fishbones Laterals</a></li>
+        <li><a href="#export-fishbones-as-well-trajectories">Export Fishbones as Well Trajectories</a></li>
+      </ul>
+    </li>
+    <li><a href="#fractures">Fractures</a>
+      <ul>
+        <li><a href="#visualization-control">Visualization control</a></li>
+        <li><a href="#fracture-templates">Fracture Templates</a></li>
+        <li><a href="#fracture-instances">Fracture Instances</a></li>
+        <li><a href="#multiple-fracture-creation">Multiple Fracture Creation</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1825,48 +1850,30 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/CompletionsIllustration.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CompletionsIllustration.png" alt=""></p>
 <p>Three types of completions are available for modeling and export: Perforation intervals, fishbone wells and fractures. The purpose of modeling these completions, is that it enables ResInsight to export Eclipse keywords for doing more refined simulations.</p>
-
 <p>Completions can be modeled by adding new perforation intervals, fishbones subs or fractures. Details about the completions must then be specified, such as the length of the perforation interval or number of fishbone subs and laterals. After modeling the completions, the transmissibility (cell connection factors) can be calculated and exported to the Eclipse COMPDAT Keyword. See <a href="/export/completionexport/"> Export Completions</a></p>
-
 <p>For fishbones completions, multi-segment well information can even be exported to the Eclipse Keywords WELSEGS, COMPSEGS and WSEGVALV,
 c.f. <a href="/export/completionexport/">Export Well Segments</a>.</p>
 
-
 <div class="notices note" ><p>The derived cell property <a href="/3d-main-window/derivedresults/#completion-type">Completion Type</a> displays wich cells are intersected by the completions.</p>
 </div>
 
-
 <h2 id="visualization-and-inspection-of-well-connection-factors">Visualization and Inspection of Well Connection Factors</h2>
-
-<p><img src="/images/3d-main-window/Completions_WellConnectionFactors.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Completions_WellConnectionFactors.png" alt=""></p>
 <p>Connection factors both from the Simulation Wells and the ones calculated from the modeled completions can be visualized in the 3D view by enabling <strong>Well Connection Factors</strong> in the <strong>Project Tree</strong>. The connection factors are displayed with a symbol as in the example shown above. The color of the symbol displays the magnitude of the connection factor and can be controlled by the legend settings.  Additional details of the connection factor are displayed in the <strong>Result Info</strong> window when clicking on the connection factor symbol.</p>
-
 <p>The <strong>Property Panel</strong> of the <strong>Well Connection Factors</strong> item has a few options:</p>
-
 <ul>
 <li><strong>Geometry Scale Factor</strong> &ndash; Scales the connection factor symbols relative to the displayed well path radius</li>
 <li><strong>Show on Closed Connections</strong> &ndash; Show the connection factors calculated for closed simulation well cells in addition to the ones at open cells.</li>
 </ul>
-
-<p>A combined view of well connection factors and the derived result <a href="/3d-main-window/derivedresults/#completion-type">Completion Type</a>
+<p>A combined view of well connection factors and the derived result <a href="/3d-main-window/derivedresults/#completion-type">Completion Type</a> 
 enables the user to see the completion type contributing to connection factor in a cell.</p>
-
 <h2 id="perforation-intervals">Perforation Intervals</h2>
-
 <p>A new perforation interval on a well can be set up by right-clicking on the well in the <strong>3D View</strong> or in the <strong>Project Tree</strong>, and choosing the command <strong>Create Perforation interval</strong> in the <strong>Create Completions</strong> sub-menu. In the 3D View the completion will be created at the specific depth the right-click occured at.</p>
-
-<p><img src="/images/3d-main-window/CreateCompletionOnWellPath.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/PerforationIntervals_propEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CreateCompletionOnWellPath.png" alt=""></p>
+<p><img src="/images/3d-main-window/PerforationIntervals_propEditor.png" alt=""></p>
 <p>After creating the perforation interval, the following properties of the perforation can be set in the property editor:</p>
-
 <ul>
 <li><strong>Start MD</strong>, <strong>End MD</strong> &ndash; Measured depth along the well path for the perforation to start/stop.</li>
 <li><strong>Diameter</strong> &ndash; Well bore diameter for the perforation interval, used in calculation of transmissibility ( For details on the transmissibility calculation, see <a href="/export/completionexport/#transmissibility-calculations">Transmissibility Calculations</a>).</li>
@@ -1874,41 +1881,32 @@ enables the user to see the completion type contributing to connection factor in
 <li><strong>All Timesteps</strong> &ndash; If on, the perforation interval will be present for all time steps</li>
 <li><strong>Start Date</strong> &ndash; The perforation will be included in the model for all time steps after this date. If &ldquo;All TimeSteps&rdquo; is turned on, this option is not available and the perforation is included for all time steps.</li>
 </ul>
-
 <p>The perforation intervals will be indicated by different color along the well path.</p>
-
-<p><img src="/images/3d-main-window/WellPerforationIntervalColor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellPerforationIntervalColor.png" alt=""></p>
 <p>For each well path there is a top level folder in the <strong>Project Tree</strong> containing all the perforation intervals definitions containing settings that applies to all the perforation intervals for this well path.</p>
-
-<p><img src="/images/3d-main-window/Perforations_PropEdit.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Perforations_PropEdit.png" alt=""></p>
 <p>For multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.</p>
-
-<p><img src="/images/3d-main-window/PerfIntervalMsw.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PerfIntervalMsw.PNG" alt=""></p>
 <ul>
 <li><strong>Multi Segment Well Options</strong> - Options used by the Well Segments Export
-
 <ul>
 <li><strong>Liner Inner Diameter</strong> &ndash; The liner inner diameter for the completion intervals.</li>
 <li><strong>Roughness Factor</strong> &ndash; The roughness factor used in export of main bore segments.</li>
 <li><strong>Pressure Drop</strong> &ndash; can be either <em>Hydrostatic</em>, <em>Hydrostatic + Friction</em> or <em>Hydrostatic + Friction + Acceleration</em>.</li>
-<li><strong>Length and Depth</strong> &ndash; Used in WELSEGS export - when specifying the length and depth change for each segment</li>
+<li><strong>Length and Depth</strong> &ndash; Used in WELSEGS export - when specifying the length and depth change for each segment
+<ul>
 <li><strong>Incremental</strong> &ndash; length / depth of given segment</li>
 <li><strong>Absolute</strong> &ndash; the length down the tube or depth of the last nodal point</li>
-<li><strong>Enforce Max Segment Length</strong> &ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.
-<br /></li>
-</ul></li>
 </ul>
-
+</li>
+<li><strong>Enforce Max Segment Length</strong> &ndash; Limit segment to max size. When this check box is checked, a max segment length input field is displayed.</li>
+</ul>
+</li>
+</ul>
 <p>There are three options for Non-Darcy Flow. <strong>None</strong>, <strong>User defined D-factor</strong> and <strong>Compute D-factor</strong>. The second option displays an input field where the user defined D-factor can be entered. The last options calculates D-factor for gas given Dake´s (1976) radiel inflow model and correlation for calculating matrix beta factor depending on permeability and porosity.</p>
-
-<p><img src="/images/3d-main-window/PerfIntervalNonDarcy.PNG" alt="" /></p>
-
+<p><img src="/images/3d-main-window/PerfIntervalNonDarcy.PNG" alt=""></p>
 <ul>
 <li><strong>Non-Darcy Flow</strong> - Non-Darcy settings for D factor computation
-
 <ul>
 <li><strong>Grid Permeability Kr Scaling Factor</strong> &ndash; Rel.perm. scaling factor to calculate effective permeability.</li>
 <li><strong>Well Radius</strong> &ndash; Well bore radius.</li>
@@ -1916,85 +1914,55 @@ enables the user to see the completion type contributing to connection factor in
 <li><strong>Gas Viscosity</strong> &ndash; Gas viscosity at flowing bottom hole pressure.</li>
 <li><strong>Inertial Coefficient</strong> &ndash; Coefficient to calculate beta factor.</li>
 <li><strong>Permeability Scaling Exponent</strong> &ndash; For beta factor calculation.</li>
-<li><strong>Porosity Scaling Exponent</strong> &ndash; For beta factor calculation.
-<br /></li>
-</ul></li>
+<li><strong>Porosity Scaling Exponent</strong> &ndash; For beta factor calculation.</li>
+</ul>
+</li>
 </ul>
-
 <h3 id="perforation-interval-valves">Perforation Interval Valves</h3>
-
 <p>Perforation Intervals can have valves (ICDs/AICDs/ICVs) associated with them.</p>
-
-<p><img src="/images/3d-main-window/ValveVisualisation.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ValveVisualisation.png" alt=""></p>
 <p>These valves can be created by right-clicking on the Perforation Interval and selecting <strong>Create Valve</strong>.</p>
-
-<p><img src="/images/3d-main-window/NewValve.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/NewValve.png" alt=""></p>
 <p>Each Valve require a <strong>Valve Template</strong> containing properties which can be shared among multiple Valves. If you have no Valve Template, a new one can be created by clicking the <strong>New</strong> button next to the Valve Template selection list.</p>
-
-<p><img src="/images/3d-main-window/NewValveWithoutTemplate.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/NewValveWithoutTemplate.png" alt=""></p>
 <p>This will create a new <strong>Valve Template</strong> which can be of three different types:</p>
-
 <ul>
 <li><strong>ICD</strong> - In-flow Control Device, allowing the setting of <strong>Orifice Diameter</strong> and <strong>Flow Coefficient</strong>. ICDs are displayed in Orange.</li>
 <li><strong>AICD</strong> - Autonomous In-flow Control Device, providing several more parameters associated with the Eclipse simulation and seen in the picture below. AICDs are displayed in Dark Purple.</li>
-<li><strong>ICV</strong> - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.
-<br /></li>
+<li><strong>ICV</strong> - Interval Control Valves. Contains the same parameters as ICDs. The difference between the two in ResInsight is that many ICDs can be added at the same time, while there is only expected to be one ICV per perforation interval. ICVs are displayed in Pink.</li>
 </ul>
-
 <p>An example of the ICD parameters can be seen below:
-<img src="/images/3d-main-window/ValveTemplate.png" alt="" /></p>
-
+<img src="/images/3d-main-window/ValveTemplate.png" alt=""></p>
 <p>An example of the AICD parameters:
-<img src="/images/3d-main-window/ValveTemplate_AICD.png" alt="" /></p>
-
+<img src="/images/3d-main-window/ValveTemplate_AICD.png" alt=""></p>
 <p>New templates can also be added by selecting the <strong>New Valve Template</strong> option from the right-click menu of the <strong>Valve Templates</strong> entry in the <strong>Completion Templates</strong> Project Tree item.</p>
-
-<p><img src="/images/3d-main-window/NewValveTemplate.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/NewValveTemplate.png" alt=""></p>
 <p>For ICDs and AICDs, multiple valves can be added in the same go by specifying the number of valves, spacing of valves or specific positions of valves as chosen in the <strong>Location Defined By</strong> drop down list.</p>
-
-<p><img src="/images/3d-main-window/ValveProperties_ICD.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ValveProperties_ICD.png" alt=""></p>
 <p>For ICVs only one valve is added at a time so only the measured depth of that valve can be chosen.</p>
-
-<p><img src="/images/3d-main-window/ValveProperties_ICV.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/ValveProperties_ICV.png" alt=""></p>
 <p>When you have a valid valve template selected, there is an <strong>Edit</strong> button next to the valve template selection. Clicking this will take you straight to modify the valve template.</p>
-
 <h3 id="import-perforation-intervals">Import Perforation Intervals</h3>
-
 <p>Perforation intervals can be imported into ResInsight from <em><code>*.ev</code></em> files. These files consist of a list of wells, and their corresponding measured depth values for perforation start and end.</p>
-
 <h4 id="perforation-interval-file-format">Perforation Interval File Format</h4>
-
-<p>&rdquo;&ndash;&rdquo; is interpreted as the start of a comment. The comment ends at the end of the line.
+<p>&ldquo;&ndash;&rdquo; is interpreted as the start of a comment. The comment ends at the end of the line. 
 The files can start with a unit definition line:</p>
-
 <pre><code>UNITS &lt;unitname&gt;
 </code></pre>
 
-
 <div class="notices info" ><p>This line is ignored for now. The numbers are interpreted to be in the units present in the case.</p>
 </div>
 
-
 <p>In the following any number of :</p>
-
 <pre><code>WELLNAME &lt;well-name&gt;
 &lt;date&gt;  &lt;well completion&gt;  &lt;top mMD&gt;  &lt;base mMD&gt;   &lt;bore hole diameter&gt;  &lt;skin factor&gt;
 &lt;date&gt;  &lt;well completion&gt;  &lt;top mMD&gt;  &lt;base mMD&gt;   &lt;bore hole diameter&gt;  &lt;skin factor&gt;
 </code></pre>
-
 <ul>
 <li><em>date</em> &ndash; Start date of the completion in the format &ldquo;dd mmm yyyy&rdquo;. Eg <code>01 SEP 2006</code>. A special <code>&quot;SOH&quot;</code>date is also allowed meaning Start Of History.</li>
 <li><em>well completion</em> &ndash; For now, only <code>&quot;perforation&quot;</code> is supported</li>
 </ul>
-
 <p>Here is an example:</p>
-
 <pre><code>UNITS METRIC
 
 -- R-2 AH sidetrack into Ile/Tilje
@@ -2007,55 +1975,46 @@ WELLNAME S-2AH
 &quot;SOH&quot;   perforation 4340 4369 0.212 0   -- target Garn 2, 29 m prodint (update 290915)
 01 SEP 2006   perforation 5060 6185 0.212 0   -- target Tilje 3, 1125 m prodint
 </code></pre>
-
 <h2 id="fishbones">Fishbones</h2>
-
 <p>Fishbones are completions created by drilling or by jetting a set of small lateral holes with a high deviation from the main bore.
 Each set of holes created at the same location along the main bore, is referred to as a <em>sub</em> while each individual hole is called a <em>lateral</em>.</p>
-
 <p>For each well path there is a top level folder in the <strong>Project Tree</strong> containing all the Fishbones definitions containing settings that applies to all the fishbones for this well path. To make use of the Multi Segment Well option for pressure loss along laterals, the grid resolution needs to be fine enough to allow a grid cell to be connected to only one lateral.</p>
-
-<p><img src="/images/3d-main-window/Fishbones_PropEdit.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Fishbones_PropEdit.png" alt=""></p>
 <ul>
 <li><strong>Fishbone Well Properties</strong> &ndash; Settings used when exporting well connection factors
-
 <ul>
-<li><strong>StartMD</strong> &ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.<br /></li>
+<li><strong>StartMD</strong> &ndash; the start position for the fishbones. This will be set to the highest possible value automatically, but can be set lower by the user. Gives the point along the well from which the transmissibility from the matrix to the main bore will be calculated.</li>
 <li><strong>Main Bore Diameter</strong> &ndash; The hole diameter for the main bore will be used in the calculation of the transmissibility (connection factor) into the main bore.</li>
-<li><strong>Main Bore Skin Factor</strong> &ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore.
+<li><strong>Main Bore Skin Factor</strong> &ndash; The skin factor for the main bore, used in calculation of the transmissibility (connection factor) into the main bore. 
 For multi-segment wells there are additional parameters which should be set. These are used in the export of WELSEGS data.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Multi Segment Wells</strong> - Options used by the Well Segments Export
-
 <ul>
 <li><strong>Liner Inner  eter</strong> &ndash; The liner inner diameter for the fishbones.</li>
 <li><strong>Roughness Factor</strong> &ndash; The roughness factor used in export of main bore segments.</li>
 <li><strong>Pressure Drop</strong> &ndash; can be either <em>Hydrostatic</em>, <em>Hydrostatic + Friction</em> or <em>Hydrostatic + Friction + Acceleration</em>.</li>
-<li><strong>Length and Depth</strong> &ndash; Used in WELSEGS export - when specifying the length and depth change for each segment</li>
+<li><strong>Length and Depth</strong> &ndash; Used in WELSEGS export - when specifying the length and depth change for each segment
+<ul>
 <li><strong>Incremental</strong> &ndash; length / depth of given segment</li>
 <li><strong>Absolute</strong> &ndash; the length down the tube or depth of the last nodal point</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
+</li>
+</ul>
 <h3 id="fishbones-subs-definition">Fishbones Subs Definition</h3>
-
 <p>To add new fishbones completions, select the <strong>New Fishbones Subs Definition</strong> command. This menu item is available by right clicking on <strong>Wells</strong> in the Project Tree or right clicking on the well trajectory in the 3D View.</p>
-
-<p><img src="/images/3d-main-window/CreateCompletionOnWellPath.png" alt="" /></p>
-
-<p>The new <strong>Fishbones Subs Definition</strong> (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 <sup>1</sup>&frasl;<sub>2</sub>&rdquo; main bore.</p>
-
-<p><img src="/images/3d-main-window/Fishbones_SubDefPropEdit.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CreateCompletionOnWellPath.png" alt=""></p>
+<p>The new <strong>Fishbones Subs Definition</strong> (a group of fishbone subs) is created in the Project tree. Several subs definitions can be created on the same well trajectory to give more flexibility in placing of the fishbones. The default sub definition is based on the Fishbones Drilling System with 3 laterals exiting per sub in a 8 1/2&rdquo; main bore.</p>
+<p><img src="/images/3d-main-window/Fishbones_SubDefPropEdit.png" alt=""></p>
 <ul>
 <li><strong>Appearance</strong>
-
 <ul>
 <li><strong>Fishbones Color</strong> &ndash; The 3D View color of the fishbones created by this definition</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Location</strong> &ndash; Options to control the position and number of fishbone subs created by this definition
-
 <ul>
 <li><strong>Location Defined By</strong> &ndash; This setting will select how to define the location of the subs in this group.</li>
 <li><strong>Start MD</strong> &ndash; Position, in Measured depth along the well, of the first fishbone Sub.</li>
@@ -2063,27 +2022,30 @@ For multi-segment wells there are additional parameters which should be set. The
 <li><strong>Number of Subs</strong> &ndash; Defines the number of subs to create in the defined interval</li>
 <li><strong>Spacing</strong> &ndash; Spacing between the subs within the interval</li>
 <li><strong>Measured Depths</strong> &ndash; The measured depth of each of the fishbone subs. If the <strong>Location Defined By</strong> is set to the <strong>User Specified</strong> this will be directly editable by the user.</li>
-</ul></li>
-<li><strong>Laterals Configuration</strong> &ndash; Configures the laterals at each sub position.<br />
-
+</ul>
+</li>
+<li><strong>Laterals Configuration</strong> &ndash; Configures the laterals at each sub position.
 <ul>
 <li><strong>Laterals Per Sub</strong> &ndash; Number of laterals for each sub position</li>
 <li><strong>Lenght(s)</strong> &ndash; Length of each lateral, in m or ft.</li>
 <li><strong>Exit Angle</strong> &ndash; Exit angle for fishbone lateral, in degree.</li>
 <li><strong>Build Angle</strong> &ndash; Build angle for fishbone lateral, in degree pr meter.</li>
-<li><strong>Orientation</strong></li>
+<li><strong>Orientation</strong>
+<ul>
 <li><strong>Fixed Angle</strong> &ndash; The user can specify the angle for the first lateral</li>
 <li><strong>Random angle</strong> &ndash; Each sub will have a random orientation. Notice that the angle between each of the laterals will be constant, with the laterals equally spaced.</li>
-<li><strong>Install Success Rate</strong> &ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.<br /></li>
-</ul></li>
+</ul>
+</li>
+<li><strong>Install Success Rate</strong> &ndash; Gives the probability of success for installation of each of the fishbones laterals. If 1, all laterals are installed.</li>
+</ul>
+</li>
 <li><strong>Well Properties</strong> &ndash; Settings to control the connection factor calculation used in <a href="/export/completionexport/">Completion Export</a>)
-
 <ul>
 <li><strong>Hole Diameter</strong> &ndash; The hole diameter of the lateral</li>
 <li><strong>Skin Factor</strong> &ndash; The skin factor used in the transmissibility calculation for the lateral.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Multi Segment Wells</strong> &ndash; Settings used for Well Segment Export
-
 <ul>
 <li><strong>Tubing Diameter</strong> &ndash; The diameter used in the <em>WELSEGS</em> export of the laterals.</li>
 <li><strong>Open Hole Roughness Factor</strong> &ndash; Exported directly to the <em>WELSEGS</em> keyword.</li>
@@ -2091,246 +2053,215 @@ For multi-segment wells there are additional parameters which should be set. The
 <li><strong>ICDs per Sub</strong> &ndash; The number of ICD (valves) per Sub, used for calculation of total ICD area for <em>WSEGVALV</em> export.</li>
 <li><strong>ICD Orifice Diameter</strong> &ndash; The Diameter of the ICD, used for calculation of ICD area for <em>WSEGVALV</em> export.</li>
 <li><strong>ICD Flow Coefficient</strong> &ndash; The flow coefficient, exported directly as a part of <em>WSEGVALV</em>.</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <h3 id="import-well-trajectories-as-fishbones-laterals">Import Well Trajectories as Fishbones Laterals</h3>
-
 <p>The command <strong>Import Completions From File</strong> can be used to import well trajectories in the <em><code>*.dev</code></em> format as fishbone laterals.  The imported laterals are listed under the folder <strong>Imported Laterals</strong> in the <strong>Project Tree</strong>. These laterals behave as completions, and will be exported when exporting completion data using the settings in the property panel of the <strong>Imported Laterals</strong> folder.</p>
-
-<p><img src="/images/3d-main-window/Fishbones_LateralsMSWprop.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/Fishbones_LateralsMSWprop.png" alt=""></p>
 <h3 id="export-fishbones-as-well-trajectories">Export Fishbones as Well Trajectories</h3>
-
 <p>The <strong>Export Laterals</strong> command will export the fishbone laterals as a well trajectory into a  <em><code>*.dev*</code></em> -file.</p>
 
-
-<div class="notices info" ><p>Notice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to <code><em>.dev</em></code> files.</p>
+<div class="notices info" ><p>Notice that only the trajectory data is exported. Properties related to well segment data or Completion Data export can not be written to <!-- raw HTML omitted -->*.dev*<!-- raw HTML omitted --> files.</p>
 </div>
 
-
 <h2 id="fractures">Fractures</h2>
-
 <p>Hydraulic fractures are completions created by pressurizing the reservoir at a certain point in the well, and thereby creating a crack in the formation. A substance is then injected into the crack to keep it open when relaxing the pressure.</p>
-
 <p>Fractures in ResInsight can be added both to simulation wells and Well Trajectories, and have two main types: Elliptical fractures and StimPlan fractures.</p>
-
 <h3 id="visualization-control">Visualization control</h3>
-
 <p>The <strong>Fractures</strong> item in the <strong>Project Tree</strong> controls whether to show the modeled fractures or not. For fractures along the well path the <strong>Perforation Length</strong> is shown as an olive green cylinder around the well path as shown in the image below.</p>
-
-<p><img src="/images/3d-main-window/FractureVizControl.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FractureVizControl.png" alt=""></p>
 <ul>
 <li><strong>Colors</strong> &ndash; Control the color settings for the fractures in the View
-
 <ul>
 <li><strong>Result Variable</strong> &ndash; Selects the fracture result to use for coloring the fracture. This is most interesting when you have imported a StimPlan fracture with varying width, conductivity and other parameters. The legend item in the <strong>Project Tree</strong> controls how the legend is set up.</li>
 <li><strong>Default Color</strong> &ndash; The color to use if the requested result is not available for some fracture.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>StimPlan</strong>
-
 <ul>
 <li><strong>Show Mesh</strong> &ndash; Toggles the visualization of the StimPlan mesh lines, showing the StimPlan cell borders</li>
-<li><strong>Color Interpolation</strong> &ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.
-<br /></li>
-</ul></li>
+<li><strong>Color Interpolation</strong> &ndash; Toggles interpolation of the StimPlan results. When Off, one color per StimplanCell is shown. When on, ResInsight interpolates the color between the cells.</li>
+</ul>
+</li>
 </ul>
-
 <h3 id="fracture-templates">Fracture Templates</h3>
-
 <p>To create a functioning fracture you first need a <strong>Fracture Template</strong>. The template collects settings that are likely to be shared among several fractures, most importantly the fracture geometry. A fracture at a particular place refers to the template, and it is thereby possible to share fracture geometry and other settings between fracture instances.</p>
-
 <p>Fracture Templates are listed in a folder with the same name in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/FractureTemplates.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FractureTemplates.png" alt=""></p>
 <p>To create a new fracture template, right-click the <strong>Fracture Template</strong> item in the tree, and select either <strong>New Ellipse Fracture Template</strong> or <strong>New StimPlan Fracture Template</strong>. If you have no existing fracture templates, you will be given the opportunity to create such templates through two buttons in the Fracture Property Editor as seen below.</p>
-
-<p><img src="/images/3d-main-window/CreateFractureTemplate.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CreateFractureTemplate.png" alt=""></p>
 <h4 id="common-fracture-template-options">Common Fracture Template Options</h4>
-
-<p><img src="/images/3d-main-window/CommonFractureTemplateProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CommonFractureTemplateProperties.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; User defined name for the template. Used when selecting which template to use in the Fracture</li>
 <li><strong>ID</strong> &ndash; Assigned ID to be used when addressing this template form a Command file script</li>
 <li><strong>Geometry</strong>
-
 <ul>
-<li><strong>Fracture Orientation</strong> &ndash; The fractures orientation</li>
+<li><strong>Fracture Orientation</strong> &ndash; The fractures orientation
+<ul>
 <li><strong>Transverse(normal) to Well Path</strong> &ndash; The fracture plane is vertical and normal to the well path at the intersection point.</li>
 <li><strong>Along Well Path</strong> &ndash; Fracture is vertical and along the well path. This option enables options to control the perforation length and the efficiency of the well in the fracture. See below.</li>
 <li><strong>Azimuth</strong> &ndash; The fracture is vertical and in line with the Azimuth Angle (measured from North) supplied.</li>
-</ul></li>
+</ul>
+</li>
+</ul>
+</li>
 <li><strong>Fracture Truncation</strong>
-
 <ul>
-<li><strong>Use Containment</strong> &ndash; Enable this option to activate layer containment.</li>
+<li><strong>Use Containment</strong> &ndash; Enable this option to activate layer containment.
+<ul>
 <li><strong>Top Layer</strong> &ndash; Topmost K-layer that the fracture will drain.</li>
 <li><strong>Base Layer</strong> &ndash; Lowest K-layer that the fracture will drain.</li>
-<li><strong>Truncate At Faults</strong> &ndash; Enable this option to activate fault truncation.</li>
-<li><strong>Minimum Fault Throw</strong> &ndash; Fault throw threshold to activate fault truncation.</li>
-</ul></li>
-<li><strong>Properties</strong> &ndash; The availability of these options depend on the <strong>Fracture Orientation</strong> and the <strong>Conductivity in Fracture</strong> setting.
-
+</ul>
+</li>
+<li><strong>Truncate At Faults</strong> &ndash; Enable this option to activate fault truncation.
+<ul>
+<li><strong>Minimum Fault Throw</strong> &ndash; Fault throw threshold to activate fault truncation.</li>
+</ul>
+</li>
+</ul>
+</li>
+<li><strong>Properties</strong> &ndash; The availability of these options depend on the <strong>Fracture Orientation</strong> and the <strong>Conductivity in Fracture</strong> setting.
+<ul>
+<li><strong>Conductivity in Fracture</strong>
 <ul>
-<li><strong>Conductivity in Fracture</strong></li>
 <li><strong>Finite Conductivity</strong> &ndash; Use a calculated conductivity for flow in the fracture. Either the StimPlan conductivity, or a constant conductivity in Ellipse fractures.</li>
 <li><strong>Infinite Conductivity</strong> &ndash; Assume infinite conductivity in the fracture itself. For StimPlan fractures this will ignore the conductivity in the StimPlan data.</li>
+</ul>
+</li>
 <li><strong>Skin Factor</strong> &ndash; Used when exporting to Eclipse.</li>
 <li><strong>Perforation Length</strong> &ndash; The length of the intersection between the well bore and the fracture when the fracture is along the well path ( Fractures <strong>Along Well Path</strong> only ).</li>
 <li><strong>Perforation Efficiency</strong> &ndash; The efficiency of the wellbore-fracture perforation ( Fractures <strong>Along Well Path</strong> only ).</li>
 <li><strong>Well Diameter</strong> &ndash; Used when exporting to Eclipse.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Sensitivity Scale Factors</strong> &ndash; Each of the properties are scaled by the scaling factor. When used interactively, the <strong>Apply</strong> button must be pressed to apply the scaling factors. These scaling factors are also available from command file scripting
-
 <ul>
 <li><strong>Height, Width</strong> &ndash; Scales the height or the <em><em>Halflength</em></em> of the fracture template</li>
 <li><strong>D-factor</strong> &ndash; Scales the none-darcy flow factor</li>
 <li><strong>Conductivity</strong> &ndash; Scales the conductivity in the fracture directly</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <h4 id="non-darcy-flow">Non-Darcy Flow</h4>
-
-<p><img src="/images/3d-main-window/FractureNonDarcyFlow.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FractureNonDarcyFlow.png" alt=""></p>
 <p>Non-Darcy Flow is used to improve the computation of connection factors for cells penetrated by well pipes. A pre-computed D-factor can be set using <strong>User Defined D-factor</strong>. Selecting the option <strong>Compute D-factor</strong> displays the following set of properties:</p>
-
 <ul>
 <li><strong>Inertial Coefficient</strong>
-
 <ul>
 <li><strong>User Defined</strong> &ndash; Beta-factor in Forcheimer units</li>
 <li><strong>Use Fracture Beta Factor</strong> &ndash; Extract beta factor from the fracture template at the well intersection location. For transversal fractures, the conductivity is computed from the geometric average of fracture cells intersected by the fracture perforation length.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Effective Permeability</strong>
-
 <ul>
 <li><strong>User Defined</strong> &ndash; Defines the permeability <em>Ke</em> in milliDarcy in the property <strong>Effective Permeability</strong></li>
 <li><strong>Use Fracture Conductivity</strong> &ndash; Extract conductivity from the fracture template at the well intersection location and scale with <strong>Relative Permeability</strong>. For transversal fractures, the conductivity is computed from the weighted average of fracture cells intersected by the fracture perforation length.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Width</strong>
-
 <ul>
 <li><strong>User Defined</strong> &ndash; Defines the width of the fracture</li>
 <li><strong>Use Fracture Width</strong> &ndash; Extract width from the fracture template at the well intersection location. For transversal fractures, the width is based on the weighted average of fracture cells intersected by the fracture perforation length.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Relative Gas Density</strong></li>
 <li><strong>Gas Viscosity</strong></li>
 <li><strong>D Factor</strong> &ndash; Displays the computed value of the D factor. NOTE : For <em>transversal fractures</em>, the computed D factor is scaled by 1.2 to compensate for a different flow model</li>
 <li><strong>D Factor Details</strong> &ndash; Displays the value of variables used to compute the D factor</li>
 </ul>
-
 <h4 id="ellipse-fracture-template">Ellipse Fracture Template</h4>
-
-<p><img src="/images/3d-main-window/EllipseFractureTemplateProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/EllipseFractureTemplateProperties.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; User name of this particular fracture template</li>
 <li><strong>Geometry</strong>
-
 <ul>
-<li><strong>Halflength X<sub>r</sub></strong> &ndash; Half the width of the ellipse</li>
+<li><strong>Halflength X<!-- raw HTML omitted -->r<!-- raw HTML omitted --></strong> &ndash; Half the width of the ellipse</li>
 <li><strong>Height</strong> &ndash; The height of the elliptical fracture</li>
 <li><strong>Fracture Orientation</strong> &ndash; See above</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Fracture Truncation</strong> &ndash; See above</li>
 <li><strong>Properties</strong> &ndash; The availability of these options depend on the <strong>Fracture Orientation</strong> and the <strong>Conductivity in Fracture</strong> setting
-
 <ul>
 <li><strong>Permeability</strong> &ndash; A constant permeability inside the fracture (Used to calculate conductivity in the fracture)</li>
 <li><strong>Width</strong> &ndash; Crack width (Used to calculate conductivity in the fracture)</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Sensivity Scale Factors</strong> &ndash; See above</li>
 <li><strong>Non-Darcy Flow</strong> &ndash; See above</li>
 </ul>
-
 <h4 id="stimplan-fracture-template">Stimplan Fracture Template</h4>
-
 <p>StimPlan fracture templates imports XML output from the StimPlan software. These XML files contains results from a simulated hydraulic fracture, describing both geometry, varying crack width, resulting conductivity etc. as time varying quantities. Both symmetric and asymmetric StimPlan fracture templates are supported.</p>
-
-<p><img src="/images/3d-main-window/StimplanFractureTemplateProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/StimplanFractureTemplateProperties.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; User name of this particular fracture template</li>
 <li><strong>Show StimPlan Mesh</strong> &ndash; Show or hide the mesh lines on the fracture in the 3D View</li>
 <li><strong>Input</strong>
-
 <ul>
 <li><strong>File Name</strong> &ndash; Path to the imported StimPlan XML-file</li>
 <li><strong>Active Time step Index</strong> &ndash; Time step in the StimPlan simulation to use for transmissibility calculations and visualization</li>
 <li><strong>Well/fracture Intersection Depth</strong> &ndash; The position of the fracture along the well path as MD.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Geometry</strong>
-
 <ul>
 <li><strong>Fracture Orientation</strong> &ndash; See above</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Fracture Truncation</strong> &ndash; See above</li>
 <li><strong>Properties</strong>
-
 <ul>
 <li><strong>Conductivity Scaling Factor</strong> &ndash; Scale the overall conductivity to do sensitivity studies.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Sensitivity Scale Factors</strong> &ndash; See above</li>
 <li><strong>Non-Darcy Flow</strong> &ndash; See above</li>
 </ul>
-
 <h3 id="fracture-instances">Fracture Instances</h3>
-
 <p>Instances of fractures can be created along well paths and simulation wells by right clicking the well pipe in the 3D view, or the corresponding items in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/FractureInstancePropertyPanel.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/FractureInstancePropertyPanel.png" alt=""></p>
 <ul>
 <li><strong>Name</strong> &ndash; User editable name</li>
 <li><strong>Fracture Template</strong> &ndash; Select the fracture template to use for this fracture. Click the <strong>Edit</strong> shortcut next to the template selection list to go directly to modify the selected template.</li>
 <li><strong>Location/Orientation</strong>
-
 <ul>
 <li><strong>Measured depth Location</strong> &ndash; The measured depth</li>
 <li><strong>Azimuth</strong> &ndash; Azimuth orientation of fracture.</li>
 <li><strong>Dip</strong> &ndash; Dip of fracture plane</li>
 <li><strong>Tilt</strong> &ndash; Rotation of fracture about its plane normal</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Properties</strong>
-
 <ul>
 <li><strong>Fracture Unit System</strong> &ndash; Read only display of the units used for the current template</li>
 <li><strong>StimPlan Time Step</strong> &ndash; Displays the time step used by the template</li>
-<li><strong>Perforation Length</strong> / <strong>Perforation Efficiency</strong> / <strong>Well Diameter</strong> &ndash; These values are copied from the new template when selecting a different one. See <a href="/wells-and-completions/completions/#common-fracture-template-options">Common Fracture Template Options</a><br /></li>
-</ul></li>
+<li><strong>Perforation Length</strong> / <strong>Perforation Efficiency</strong> / <strong>Well Diameter</strong> &ndash; These values are copied from the new template when selecting a different one. See <a href="/wells-and-completions/completions/#common-fracture-template-options">Common Fracture Template Options</a></li>
+</ul>
+</li>
 <li><strong>Fracture Center Info</strong> &ndash; This group displays info on where the center of the fracture is positioned. The center is defined to be where the well path intersects the fracture.</li>
 </ul>
-
 <h3 id="multiple-fracture-creation">Multiple Fracture Creation</h3>
-
 <p>In some cases the user wants to create a number of fractures on one or more well paths. Doing this by creating one by one fracture can be very error prone and time consuming. To ease this task, ResInsight has support for creating several fractures in one operation.</p>
-
 <p>Select one or more well paths in the project tree, right click and select <strong>Create Multiple Fractures</strong> from the right-click menu. Then the <strong>Create Multiple Fractures</strong> dialog appears. In this dialog, the user defines where fractures will be created on the selected well paths. Different fracture templates and spacing can be used for different K layer ranges in the grid, by adding new options lines to the table. To edit an option line, double click the field to edit. Adding and deleting option lines are done by right clicking the table.</p>
-
-<p><img src="/images/3d-main-window/CreateMultipleFracturesDialog.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CreateMultipleFracturesDialog.png" alt=""></p>
 <ul>
 <li><strong>Case</strong> &ndash; Current grid case</li>
 <li><strong>Min Distance From Well TD</strong> &ndash; Minimum distance from well tip for created fractures</li>
 <li><strong>Max Fractures Per Well</strong> &ndash; Maximum number of fractures to create per well</li>
 <li><strong>Options</strong>
-
 <ul>
 <li><strong>Top K Layer</strong> &ndash; The topmost K layer to add fractures to</li>
 <li><strong>Base K Layer</strong> &ndash; The bottommost K layer to add fractures to</li>
 <li><strong>Template</strong> &ndash; The fracture template used in the specified K layer range</li>
 <li><strong>Spacing</strong> &ndash; The distance between each fracture in the K layer range</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Generated Fractures</strong> &ndash; Output information to the user. Shows number of fractures that will be created on each selected well path</li>
 <li><strong>Replace Fractures</strong> &ndash; Press this button to delete all existing fractures on the selected wells before creating new fractures</li>
 <li><strong>Add Fractures</strong> &ndash; Press this button to add the new fractures to all selected wells (not deleting existing fractures)</li>
 </ul>
-
 <p>The Create Multiple Fractures function is also available as a CommandFile command. See the <a href="/scripting/commandfile/">CommandFile section</a></p>
 
 
@@ -2507,6 +2438,19 @@ For multi-segment wells there are additional parameters which should be set. The
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2517,6 +2461,9 @@ For multi-segment wells there are additional parameters which should be set. The
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3667,20 +3614,20 @@ For multi-segment wells there are additional parameters which should be set. The
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/completionslgr/index.html b/wells-and-completions/completionslgr/index.html
index 6120e1bcc0..8324e52a5c 100644
--- a/wells-and-completions/completionslgr/index.html
+++ b/wells-and-completions/completionslgr/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions LGR :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#create-temporary-lgrs">Create Temporary LGRs</a>
-<ul>
-<li><a href="#delete-temporary-lgrs">Delete temporary LGRs</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#create-temporary-lgrs">Create Temporary LGRs</a>
+      <ul>
+        <li><a href="#delete-temporary-lgrs">Delete temporary LGRs</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,41 +1833,29 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/TemporaryLGR_CompletionType_12_combined.png" alt=""></p>
 <p>ResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.</p>
-
 <h2 id="create-temporary-lgrs">Create Temporary LGRs</h2>
-
 <p>To create temporary LGR(s), first select one or more well paths in the project tree, right click and select &lsquo;Create Temporary LGR&rsquo;. This command brings up the following dialog.</p>
-
-<p><img src="/images/3d-main-window/TemporaryLgrDialog.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/TemporaryLgrDialog.png" alt=""></p>
 <p>The dialog contains several input fields</p>
-
 <ul>
 <li><strong>Source Case</strong> &ndash; The source case/grid</li>
 <li><strong>Time Step</strong> &ndash; The time step to use</li>
 <li><strong>Fractures, Fishbones, Perforations</strong> &ndash; Check boxes to control which completion types to create LGRs for</li>
 <li><strong>Split Type</strong> &ndash; Three options controlling how the LGRs will be created
-
 <ul>
 <li><strong>LGR Per Cell</strong> &ndash; One LGR is created for each main grid cell intersected by completions of the selected type</li>
 <li><strong>LGR Per Completion</strong> &ndash; One LGR is created for each completion of the selected types. Each LGR span all main grid cells that are located within an IJK bounding box containing all intersected cells.</li>
 <li><strong>LGR Per Well</strong> &ndash; One LGR is created for each of the selected well paths. The LGR spans all main grid cells that are located within an IJK bounding box containing all intersected cells for all selected completions on that well path.</li>
-</ul></li>
+</ul>
+</li>
 <li><strong>Cell Count I,J,K</strong> &ndash; The size of the LGR, in each main grid cell, in the I, J and K direction</li>
 </ul>
-
 <p>After pressing the OK button, LGR(s) are created and will be visible in the grid view.
 Temporary LGRs are stored in memory, and are thus not saved to file. After restarting ResInsight those LGRs have to be recreated.</p>
-
 <p>Individual visibility of generated LGRs can be controlled from the <a href="/3d-main-window/3dviews/#grids">Grids</a> section in a view.</p>
-
 <h3 id="delete-temporary-lgrs">Delete temporary LGRs</h3>
-
 <p>It is possible to explicitly delete all temporary LGRs. Right click on the <strong>View -&gt; Grids -&gt; Temporary LGRs</strong> project tree node and select <strong>Delete Temporary LGRs</strong>. This command deletes all temporary LGRs.</p>
 
 
@@ -2012,6 +2032,19 @@ Temporary LGRs are stored in memory, and are thus not saved to file. After resta
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2022,6 +2055,9 @@ Temporary LGRs are stored in memory, and are thus not saved to file. After resta
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3172,20 +3208,20 @@ Temporary LGRs are stored in memory, and are thus not saved to file. After resta
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/createnewwellpaths/index.html b/wells-and-completions/createnewwellpaths/index.html
index 2a1e389617..1b2bf5d9b4 100644
--- a/wells-and-completions/createnewwellpaths/index.html
+++ b/wells-and-completions/createnewwellpaths/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Create Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,15 +1802,13 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li>
-<ul>
-<li><a href="#well-plan">Well Plan</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li>
+      <ul>
+        <li><a href="#well-plan">Well Plan</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1801,32 +1833,22 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/WellPathCreation.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellPathCreation.png" alt=""></p>
 <p>ResInsight lets the user create new/custom well paths by clicking in the 3D view. A self created well path will behave the same way as an ordinary imported well path.</p>
-
 <p>To create a well path:</p>
-
 <ol>
 <li>Right click <strong>Wells</strong> in the project tree</li>
 <li>Select <strong>Create Well Path</strong> in the right-click menu. A new well node and a well targets node are created.</li>
 <li>Click in the 3D view on locations where the well path will pass (targets). Note. A 3D object must be hit when clicking. Clicking in thin air will not work.</li>
 <li>When finished placing targets, click on &ldquo;Stop Picking Targets&rdquo; in the property editor</li>
 </ol>
-
-<p><img src="/images/3d-main-window/WellTargetsTree.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/WellTargetsPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellTargetsTree.png" alt=""></p>
+<p><img src="/images/3d-main-window/WellTargetsPropertyEditor.png" alt=""></p>
 <p>Well targets property editor fields</p>
-
 <ul>
 <li><strong>UTM Reference Point</strong> - Reference point. Defaults to the first target point clicked</li>
 <li><strong>MDRKB at First Target</strong> - Define MD (referenced to Rotary Kelly Bushing) at first target point. Applies to well path export only.</li>
 <li><strong>Well Targets:</strong> List of targets. Will have pink background when in picking state.
-
 <ul>
 <li><strong>Point</strong> - Target position relative to reference point</li>
 <li><strong>DL in</strong> - Dog leg inwards. Unit: Degrees/30m</li>
@@ -1834,19 +1856,14 @@ if (!doNotTrack) {
 <li><strong>Dir</strong> - Check box for overriding well path auto calculated directions</li>
 <li><strong>Azi (deg)</strong> - Azimuth. Y axis is 0 degrees</li>
 <li><strong>Inc (deg)</strong> - Inclination. Z axis is 0 degrees</li>
-</ul></li>
 </ul>
-
+</li>
+</ul>
 <p>A self created well path may be edited by either editing coordinates in the property editor or clicking and dragging targets in the 3D view.</p>
-
-<p><img src="/images/3d-main-window/WellTargets.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellTargets.png" alt=""></p>
 <p>Clicking and dragging the blue part of a target, it can be moved along the Z axis only. Clicking and dragging the magenta part of a target, it can be moved freely around.</p>
-
 <h3 id="well-plan">Well Plan</h3>
-
 <p>A well plan can be displayed by selecting <strong>Show Well Plan</strong> from the right-click menu of a generated well path.</p>
-
 <pre><code>-- MDRKB          CL            Inc          Azi            TVDMSL         NS                EW               Dogleg      Build        Turn          
 0.00000        0.00000       91.23218     67.46458       2560.64104     7320830.60875     456093.37763     0.00000     0.00000      0.00000       
 109.69761      109.69761     91.23218     67.46458       2558.28210     7320872.64113     456194.67560     0.00000     0.00000      0.00000       
@@ -1857,7 +1874,6 @@ if (!doNotTrack) {
 1087.97847     357.93368     92.23380     -164.19586     2550.23230     7320460.45997     456856.25443     4.78528     0.14842      -25.38856     
 </code></pre>
 
-
 <footer class=" footline" >
 	
 </footer>
@@ -2031,6 +2047,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2041,6 +2070,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3191,20 +3223,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/index.html b/wells-and-completions/index.html
index 5d260d048e..3f7e587d87 100644
--- a/wells-and-completions/index.html
+++ b/wells-and-completions/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Wells and Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1761,7 +1795,7 @@ if (!doNotTrack) {
                 
                     <div class="progress">
     <div class="wrapper">
-
+<nav id="TableOfContents"></nav>
     </div>
 </div>
 
@@ -1786,10 +1820,8 @@ if (!doNotTrack) {
 
 
 
-	<p><img src="/images/3d-main-window/ValveVisualisation.png" alt="" /></p>
-
+	<p><img src="/images/3d-main-window/ValveVisualisation.png" alt=""></p>
 <p>This chaper describes the following aspects of wells and completions:</p>
-
 <ul>
 <li>how wells defined in the simulation are displayed and how to control the different aspects of their visualization</li>
 <li>retrieval of well trajectories from file and an internal Equinor web service</li>
@@ -1798,7 +1830,6 @@ if (!doNotTrack) {
 <li>modeling and export of completions including perforation intervals, fishbone wells and fractures in order to perform refined simulations</li>
 <li>creating and exporting local grid refinement (LGRs) in main grid cells intersected by completions</li>
 </ul>
-
 <p>The following subchapters details the functionality and capabilites.</p>
 
 
@@ -1977,6 +2008,19 @@ if (!doNotTrack) {
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -1987,6 +2031,9 @@ if (!doNotTrack) {
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3133,20 +3180,20 @@ if (!doNotTrack) {
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/index.xml b/wells-and-completions/index.xml
index ff549069ae..5553f0df23 100644
--- a/wells-and-completions/index.xml
+++ b/wells-and-completions/index.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
     <title>Wells and Completions on ResInsight</title>
diff --git a/wells-and-completions/simulationwells/index.html b/wells-and-completions/simulationwells/index.html
index 38fd55d75d..37b7b15876 100644
--- a/wells-and-completions/simulationwells/index.html
+++ b/wells-and-completions/simulationwells/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Simulation Wells :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,28 +1802,27 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#commands">Commands</a></li>
-<li><a href="#overall-settings-for-simulation-wells">Overall Settings for Simulation Wells</a>
-<ul>
-<li><a href="#visibility">Visibility</a></li>
-<li><a href="#well-cells-and-fence">Well Cells and Fence</a></li>
-<li><a href="#size-scaling">Size Scaling</a></li>
-<li><a href="#colors">Colors</a></li>
-<li><a href="#well-pipe-geometry">Well Pipe Geometry</a></li>
-<li><a href="#advanced">Advanced</a></li>
-</ul></li>
-<li><a href="#individual-simulation-well-options">Individual Simulation Well options</a></li>
-<li><a href="#well-pipes-of-multi-segment-wells">Well Pipes of Multi Segment Wells</a>
-<ul>
-<li><a href="#geometry-approximation">Geometry Approximation</a></li>
-<li><a href="#dummy-branches">Dummy Branches</a></li>
-<li><a href="#picking-reveals-segment-branch-info">Picking Reveals Segment/Branch Info</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#commands">Commands</a></li>
+    <li><a href="#overall-settings-for-simulation-wells">Overall Settings for Simulation Wells</a>
+      <ul>
+        <li><a href="#visibility">Visibility</a></li>
+        <li><a href="#well-cells-and-fence">Well Cells and Fence</a></li>
+        <li><a href="#size-scaling">Size Scaling</a></li>
+        <li><a href="#colors">Colors</a></li>
+        <li><a href="#well-pipe-geometry">Well Pipe Geometry</a></li>
+        <li><a href="#advanced">Advanced</a></li>
+      </ul>
+    </li>
+    <li><a href="#individual-simulation-well-options">Individual Simulation Well options</a></li>
+    <li><a href="#well-pipes-of-multi-segment-wells">Well Pipes of Multi Segment Wells</a>
+      <ul>
+        <li><a href="#geometry-approximation">Geometry Approximation</a></li>
+        <li><a href="#dummy-branches">Dummy Branches</a></li>
+        <li><a href="#picking-reveals-segmentbranch-info">Picking Reveals Segment/Branch Info</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1814,151 +1847,102 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/SimulationWells.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWells.png" alt=""></p>
 <p>This section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.</p>
-
 <h2 id="commands">Commands</h2>
-
 <p>Several commands are available as context commands on a simulation well. These commands are available either by right-clicking  the well in the <strong>3D View</strong> or in the <strong>Project Tree</strong>.</p>
-
 <ul>
 <li><strong>New Well Log Extraction Curve</strong> &ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.  ( See <a href="/plot-window/welllogsandplots/#well-log-extraction-curves">Well Log Plots</a> )</li>
 <li><strong>New Well Log RFT Curve</strong> &ndash; Creates a new RFT curve in a well log plot based on the selected simulation well. This option is only present if the current simulation well has RFT data. ( See <a href="/plot-window/welllogsandplots/#well-log-rft-curves">Well Log Plots</a> )</li>
 <li><strong>New RFT Plot</strong> &ndash;  See [Well Log Plots](/plot-window/rftplot/.</li>
-<li><strong>Plot Production Rates</strong> &ndash; Creates a summary plot of the selected wells production rates, along  with the bottom hole pressure.<br />
+<li><strong>Plot Production Rates</strong> &ndash; Creates a summary plot of the selected wells production rates, along  with the bottom hole pressure.<br>
 ( See <a href="/plot-window/summaryplots/">Summary Plots</a> )</li>
 <li><strong>Plot Well Allocation</strong> &ndash; Creates or modifies the default Well Allocation Plot to show the well.
-allocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.<br />
+allocation for the selected well. If the case has no Fluxes the well flow rates are shown instead.<br>
 ( See <a href="/plot-window/flowdiagnosticsplots/"> Flow Diagnostics Plots </a> )</li>
 <li><strong>Show Contributing Wells</strong> &ndash; This command sets up a 3D View by adding filters and modifying the Cell Result based on Flow Diagnostic Calculations to show which regions and wells that contribute to the selected well by doing:
-
 <ul>
 <li>Add a property filter of <strong>Time Of Flight</strong> to/from the selected well to show only the cells that contribute to/are influenced by the well.</li>
 <li>Sets the <strong>Cell Result</strong> to show <strong>Tracer With Max Fraction</strong> based on <strong>All Injectors</strong> or <strong>All Producers</strong> (the opposite of the selected well)</li>
 <li>Toggles the visibility of the other Simulation wells to show only wells contributing to/influenced by the selected well.</li>
-</ul></li>
-<li><strong>New Fracture</strong> &ndash; Creates a new fracture along the simulation well. (See <a href="/plot-window/welllogsandplots/#fracture-instances">Fracture instances</a>)</li>
-<li><strong>New Intersection</strong> &ndash; creates a new intersection based on the selected simulation well.<br />
-( See <a href="/3d-main-window/intersections/">Well Log Plots</a> )
-<br /></li>
 </ul>
-
+</li>
+<li><strong>New Fracture</strong> &ndash; Creates a new fracture along the simulation well. (See <a href="/plot-window/welllogsandplots/#fracture-instances">Fracture instances</a>)</li>
+<li><strong>New Intersection</strong> &ndash; creates a new intersection based on the selected simulation well.<br>
+( See <a href="/3d-main-window/intersections/">Well Log Plots</a> )</li>
+</ul>
 <h2 id="overall-settings-for-simulation-wells">Overall Settings for Simulation Wells</h2>
-
 <p>The Property Panel of the <strong>Simulation Wells</strong> item in the <strong>Project Tree</strong> contains options that are applied across all the wells, while the visualization of each single well can be controlled by the options in the property panel of that particular well, and will override the overall settings in the <strong>Simulation Wells</strong> item.</p>
-
 <p>If an option is overridden in any of the wells, this will be indicated in the corresponding top level toggle which will be partially checked. Toggling such a setting will overwrite the ones set on the individual level.</p>
-
 <p>In the following are the different parts of the <strong>Simulation Wells</strong> property panel explained.</p>
-
 <h3 id="visibility">Visibility</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsVisibilityProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsVisibilityProperties.png" alt=""></p>
 <p>These options controls the visibility of different aspects of the simulation wells.</p>
-
 <ul>
 <li><strong>Wells Trough Visible Cells Only</strong> &ndash; This option will only show wells with connections to cells deemed visible by the combined result of <strong>Range Filters</strong> and <strong>Property Filters</strong>.</li>
 <li><strong>Label</strong> &ndash; Controls visibility of well name labels in the 3D View</li>
 <li><strong>Well head</strong> &ndash; Controls visibility of the arrow displaying the production status of the well</li>
 <li><strong>Pipe</strong> &ndash; A symbolic pipe can be drawn between the well connection cells to illustrate the well. This option controls the visibility of the pipes.</li>
 <li><strong>Spheres</strong> &ndash; This option toggles the visibility of spheres drawn at the center of each well connection cell.</li>
-<li><strong>Communication Lines</strong> &ndash; Toggles the visibility of well communication lines.
-These arrows shows the communication between wells. Broader arrows indicate higher level of communication.
-These arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes.
-Arrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer &ldquo;under&rdquo; the other arrows, to make them easier to see.<br /></li>
+<li><strong>Communication Lines</strong> &ndash; Toggles the visibility of well communication lines. 
+These arrows shows the communication between wells. Broader arrows indicate higher level of communication. 
+These arrows are based on Flow Diagnostics calculations, and are only available if the eclipse results includes fluxes. 
+Arrows representing communication in the opposite direction from what is expected (eg. producers supporting another well due to cross flow) are displayed in a layer &ldquo;under&rdquo; the other arrows, to make them easier to see.</li>
 </ul>
-
 <h3 id="well-cells-and-fence">Well Cells and Fence</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsWellCellsProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsWellCellsProperties.png" alt=""></p>
 <ul>
-<li><strong>Show Well Cells</strong> &ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.<br /></li>
+<li><strong>Show Well Cells</strong> &ndash; This option toggles whether to add the well connection cells to the set of visible cells. If no cell filters are active, toggling this option will conveniently hide all other cells, displaying only the requested well cells.</li>
 <li><strong>Show Well Cell Fence</strong> &ndash; This options toggles whether to add all cells in a given direction ( I, J or K) to the set of visible cells, which has a connecting cell within its set.</li>
-<li><strong>Well Fence direction</strong> &ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells
-
-<br /></li>
+<li><strong>Well Fence direction</strong> &ndash; Controls whether to add extensions of the well cells in the I, J or K direction to the set of visible cells</li>
 </ul>
-
 <h3 id="size-scaling">Size Scaling</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsScalingProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsScalingProperties.png" alt=""></p>
 <ul>
 <li><strong>Well Head Scale</strong> &ndash; Scales the arrow displaying the production status of the well</li>
 <li><strong>Pipe Radius Scale</strong> &ndash; Scaling the pipe radius by the average i,j cell size.</li>
 <li><strong>Sphere Radius Scale</strong> &ndash; Scaling connection cell spheres radius by the average i,j cell size.</li>
 </ul>
-
 <p>Open Simulation Wells will be drawn with a slightly larger radius than closed wells. This makes open wells easier to see when they occupy the same cells as closed ones.</p>
-
 <h3 id="colors">Colors</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsColorsProperties.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/SimulationWellsColorsProperties_Uniform.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsColorsProperties.png" alt=""></p>
+<p><img src="/images/3d-main-window/SimulationWellsColorsProperties_Uniform.png" alt=""></p>
 <ul>
-<li><strong>Color Pipe Connections</strong> &ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.<br /></li>
+<li><strong>Color Pipe Connections</strong> &ndash; Applies a red, green, blue or gray color to the section of the pipe touching a connection cell indicating the production status of the connection. Gas injection, oil production, water injection or closed respectively.</li>
 <li><strong>Label Color</strong> &ndash; Sets the well label color in the 3D view.</li>
 <li><strong>Individual Pipe Colors</strong> - Select how each pipe will be colored.</li>
 </ul>
-
 <p>The <strong>Individual Pipe Color</strong> setting has two different options:</p>
-
 <ul>
 <li><strong>Unique Colors</strong> &ndash; Selecting this will apply unique colors from a pre-defined color palette to all the wells, overwriting the colors they had.</li>
 <li><strong>Uniform Default Color</strong> &ndash; Selecting this will apply the same color (made available in the <strong>Uniform Well Color</strong> option to all simulation wells.</li>
 </ul>
-
 <h3 id="well-pipe-geometry">Well Pipe Geometry</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsPipeGeometryProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsPipeGeometryProperties.png" alt=""></p>
 <ul>
 <li><strong>Type</strong> &ndash; Controls whether the pipe will go from cell center to cell center or in a smoother trajectory.</li>
 <li><strong>Branch Detection</strong> &ndash; Enables splitting of wells into branches based on the positions of the connection cells.  This option applies to ordinary wells only and has no effect on multi segment wells (MSW).</li>
 </ul>
-
 <h3 id="advanced">Advanced</h3>
-
-<p><img src="/images/3d-main-window/SimulationWellsAdvancedProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/SimulationWellsAdvancedProperties.png" alt=""></p>
 <ul>
 <li><strong>Well Cell Transparency</strong> &ndash; Controls the transparency level for the well cells.</li>
-<li><strong>Well Head Position</strong> &ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.<br /></li>
+<li><strong>Well Head Position</strong> &ndash; Controls the depth position of the wellhead. Either relative to the top of the active cells in the relevant IJ-column, or relative to the highest active cell overall.</li>
 </ul>
-
 <h2 id="individual-simulation-well-options">Individual Simulation Well options</h2>
-
-<p><img src="/images/3d-main-window/WellProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellProperties.png" alt=""></p>
 <p>Each of the wells has a set of individual settings which corresponds to the setting on the global level. See the documentation of <a href="#overall-settings-for-simulation-wells">Overall Settings for Simulation Wells</a>.</p>
-
-<p>Except for the <strong>Size Scaling</strong>, these options will override the corresponding setting on the global level,
-and will result in a partially checked state on the corresponding toggle in the <strong>Simulation Wells</strong> property panel.
+<p>Except for the <strong>Size Scaling</strong>, these options will override the corresponding setting on the global level, 
+and will result in a partially checked state on the corresponding toggle in the <strong>Simulation Wells</strong> property panel. 
 The <strong>Size Scaling</strong> options, however, works relative to the scaling level set on the top level.</p>
-
 <h2 id="well-pipes-of-multi-segment-wells">Well Pipes of Multi Segment Wells</h2>
-
 <p>ResInsight reads the MSW information in the result files and uses that to create a topologically correct visualization of the Multi Segment Well. Reading this information is somewhat time consuming, and can be turned off in the <a href="/misc/preferences/"> Preferences </a>.</p>
-
 <h3 id="geometry-approximation">Geometry Approximation</h3>
-
 <p>The pipe geometry generated for MSW&rsquo;s are based on the topology of the well (branch/segment structure) and the position of the cells being connected. The segment lengths are used as hints to place the branch points at sensible places. Thus the pipe geometry itself is not geometrically correct, but makes the topology of the well easier to see.</p>
-
 <h3 id="dummy-branches">Dummy Branches</h3>
-
 <p>Often MSW&rsquo;s are modeled using a long stem without connections and a multitude of small branches; one for each connection. ResInsight offsets the the pipe within the cell to clearly show how the topology of the well is defined.</p>
-
-<p><img src="/images/3d-main-window/MSWDummyBranchExample.png" alt="" /></p>
-
-<h3 id="picking-reveals-segment-branch-info">Picking Reveals Segment/Branch Info</h3>
-
+<p><img src="/images/3d-main-window/MSWDummyBranchExample.png" alt=""></p>
+<h3 id="picking-reveals-segmentbranch-info">Picking Reveals Segment/Branch Info</h3>
 <p>Branch and segment info of a MSW-connected-Cell is shown in the <strong>Result Info</strong> window when picking a cell in the 3D View. This can be handy when relating the visualization to the input files.</p>
 
 
@@ -2135,6 +2119,19 @@ The <strong>Size Scaling</strong> options, however, works relative to the scalin
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2145,6 +2142,9 @@ The <strong>Size Scaling</strong> options, however, works relative to the scalin
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3292,20 +3292,20 @@ The <strong>Size Scaling</strong> options, however, works relative to the scalin
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/wellpaths/index.html b/wells-and-completions/wellpaths/index.html
index 0846423b2c..60f4c1b189 100644
--- a/wells-and-completions/wellpaths/index.html
+++ b/wells-and-completions/wellpaths/index.html
@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta name="generator" content="Hugo 0.55.6" />
+    <meta name="generator" content="Hugo 0.65.3" />
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1580243646" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1580243646" rel="stylesheet">
-    <link href="/css/hybrid.css?1580243646" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1580243646" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1580243646" rel="stylesheet">
-    <link href="/css/auto-complete.css?1580243646" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1580243646" rel="stylesheet">
-    <link href="/css/theme.css?1580243646" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1580243646" rel="stylesheet">
+    <link href="/css/nucleus.css?1585823630" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1585823630" rel="stylesheet">
+    <link href="/css/hybrid.css?1585823630" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1585823630" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1585823630" rel="stylesheet">
+    <link href="/css/auto-complete.css?1585823630" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1585823630" rel="stylesheet">
+    <link href="/css/theme.css?1585823630" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1585823630" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1580243646"></script>
+    <script src="/js/jquery-3.3.1.min.js?1585823630"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -233,6 +233,31 @@
 
             
           
+            
+            
+
+
+ 
+  
+    
+    <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
+        
+        
+        
+        ">
+      <a href="/getting-started/other/">
+          Other
+          
+      </a>
+      
+      
+        <ul>
+          
+          
+          
+          
+        
+          
              
             
           
@@ -240,6 +265,15 @@
             
           
         
+        </ul>
+              
+    </li>
+  
+ 
+
+            
+          
+        
         </ul>
               
     </li>
@@ -1768,28 +1802,23 @@ if (!doNotTrack) {
                     <div class="progress">
     <div class="wrapper">
 <nav id="TableOfContents">
-<ul>
-<li>
-<ul>
-<li><a href="#ascii-well-paths">Ascii Well Paths</a>
-<ul>
-<li>
-<ul>
-<li><a href="#example-1">Example 1:</a></li>
-<li><a href="#example-2">Example 2:</a></li>
-</ul></li>
-<li><a href="#well-path-files-are-referenced">Well Path Files are Referenced</a></li>
-</ul></li>
-<li><a href="#importing-well-paths-from-ssi-hub">Importing well paths from SSI-Hub</a></li>
-<li><a href="#well-path-visualization">Well Path Visualization</a></li>
-<li><a href="#individual-well-path">Individual Well Path</a>
-<ul>
-<li><a href="#importing-well-log-files">Importing Well Log Files</a></li>
-<li><a href="#well-path-property-editor">Well Path Property Editor</a></li>
-<li><a href="#casing-design">Casing Design</a></li>
-</ul></li>
-</ul></li>
-</ul>
+  <ul>
+    <li><a href="#ascii-well-paths">Ascii Well Paths</a>
+      <ul>
+        <li></li>
+        <li><a href="#well-path-files-are-referenced">Well Path Files are Referenced</a></li>
+      </ul>
+    </li>
+    <li><a href="#importing-well-paths-from-ssi-hub">Importing well paths from SSI-Hub</a></li>
+    <li><a href="#well-path-visualization">Well Path Visualization</a></li>
+    <li><a href="#individual-well-path">Individual Well Path</a>
+      <ul>
+        <li><a href="#importing-well-log-files">Importing Well Log Files</a></li>
+        <li><a href="#well-path-property-editor">Well Path Property Editor</a></li>
+        <li><a href="#casing-design">Casing Design</a></li>
+      </ul>
+    </li>
+  </ul>
 </nav>
     </div>
 </div>
@@ -1814,42 +1843,32 @@ if (!doNotTrack) {
 
 
 
-
-
-<p><img src="/images/3d-main-window/ResInsight_WellPathWithSimulationWell.png" alt="" /></p>
-
-<p>ResInsight can import well paths from simple Ascii files.
+<p><img src="/images/3d-main-window/ResInsight_WellPathWithSimulationWell.png" alt=""></p>
+<p>ResInsight can import well paths from simple Ascii files. 
 In addition, ResInsight is able to retrieve well paths from an Equinor internal web service.</p>
-
 <p>ResInsight also supports creation of your own user-defined well paths. See <a href="/wells-and-completions/createnewwellpaths/">Create Well Paths</a></p>
-
 <h2 id="ascii-well-paths">Ascii Well Paths</h2>
-
 <p>The command <strong>File -&gt; Import -&gt; Well Data -&gt; Import Well Paths From File</strong> will read the well paths in the selected file, and create one entry for each well path under the <img src="https://resinsight.org/images/3d-main-window/WellCollection.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Wells</strong> item in the <strong>Project Tree</strong>.</p>
-
 <p>The supported ASCII format is quite flexible but the main requirements are:</p>
-
 <ul>
 <li>Each data line must contain four numbers: X Y TVD(MSL) MD(RKB) separated with white-space.</li>
 <li>Lines starting with <code>&quot;--&quot; or &quot;#&quot;</code> is considered to be comment lines</li>
 <li>A line starting with none-number-characters are used as a well name after the following rules:
-
 <ul>
-<li>If the line contains a pair of : <code>&quot;'&quot;, &quot;`&quot;, &quot;´&quot;, &quot;’&quot; or &quot;‘&quot;</code> the text between the quotation marks is used as a well name.</li>
+<li>If the line contains a pair of : <code> &quot;'&quot;, &quot;`&quot;, &quot;´&quot;, &quot;’&quot; or &quot;‘&quot;</code> the text between the quotation marks is used as a well name.</li>
 <li>If the line contains the case insensitive string &ldquo;name&rdquo; with an optional &ldquo;:&rdquo; after then the rest of the line is used as a well name.</li>
-<li>If there are no quotes or &ldquo;name&rdquo;&rsquo;s, the complete line is used as a well name.</li>
+<li>If there are no quotes or &ldquo;name&rdquo;&lsquo;s, the complete line is used as a well name.</li>
 <li>If there are several consecutive name-like lines, only the last one will be used</li>
-</ul></li>
+</ul>
+</li>
 <li>If a well name is found, a new well is created and the following data points are added to it.</li>
 </ul>
-
 <h4 id="example-1">Example 1:</h4>
-
 <pre><code>WELLNAME: WELL1
-6507.1  725 2542    2590
-6523.5  757 2549    2626.6
-6523.5  760 2559    2637.1
+6507.1	725	2542	2590
+6523.5	757	2549	2626.6
+6523.5	760	2559	2637.1
 -999
 WELLNAME: WELL2
 550.7 1020.2  2410   2410
@@ -1857,84 +1876,60 @@ WELLNAME: WELL2
 555.2  993.9  2425   2441.6
 -999
 </code></pre>
-
 <h4 id="example-2">Example 2:</h4>
-
 <pre><code>X Y TVD(MSL) MD(RKB)
 Name Well_1
-6507.1  725 2542    2542
-6523.5  757 2549    2578.6
-6523.5  760 2559    2589.1
+6507.1	725	2542	2542
+6523.5	757	2549	2578.6
+6523.5	760	2559	2589.1
 
 -- A Comment new well
 This is not its name
 Name Well_2
-550.7   1020.2  2410    2520
-551 1004.1  2422.2  2540.2
+550.7	1020.2	2410	2520
+551	1004.1	2422.2	2540.2
 # a comment inside the data 
-555.2   993.9   2425    2551.6
+555.2	993.9	2425	2551.6
 
 3Q AHB-J
-5507.0  4638.5  0.0 0.0
-5507    4638.5  1628.6  1628.6
+5507.0	4638.5	0.0	0.0
+5507	4638.5	1628.6	1628.6
 </code></pre>
-
 <h3 id="well-path-files-are-referenced">Well Path Files are Referenced</h3>
-
 <p>The well path data is not copied into the ResInsight project as such. The project file only stores the file path, and the next time you open the project, ResInsight will try to read the well data from the file again.</p>
 
-
 <div class="notices info" ><p>If the well path file is changed and you would like a running ResInsight to update accordingly, you will need to delete all the well paths that emerge from that file, and import it again.</p>
 </div>
 
-
 <h2 id="importing-well-paths-from-ssi-hub">Importing well paths from SSI-Hub</h2>
-
 <p>SSI-Hub is an Equinor internal webservice. In order to import well paths from SSI-Hub, a project file must be present and stored to file. All imported well paths from the web service will be stored relative to this project file location. If no project file exists, the menu item is disabled.</p>
-
 <p>The command <strong>File -&gt; Import -&gt; Well Data -&gt; Import Well Paths From SSI-hub</strong> launches a wizard to guide you through the process of selecting the well paths you need.
 Having completed the wizard, the imported wells are accessible as Items under the <img src="https://resinsight.org/images/3d-main-window/WellCollection.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Wells</strong> item in the <strong>Project Tree</strong>.</p>
-
 <p>The well path data is not copied into the ResInsight project as such, but is stored in files in a directory called <em>ProjectFileName_wellpaths</em> in the same directory as your project file.</p>
 
-
-<div class="notices info" ><p><strong>Access to web service: </strong>
+<div class="notices info" ><p><!-- raw HTML omitted -->Access to web service: <!-- raw HTML omitted -->
 If you are an Equinor employee, make sure you have access to &ldquo;EDM Landmark&rdquo; and &ldquo;EDM Compass&rdquo;.</p>
 </div>
 
-
 <h2 id="well-path-visualization">Well Path Visualization</h2>
-
 <p>All the imported well paths are available below the <img src="https://resinsight.org/images/3d-main-window/WellCollection.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Wells</strong> item in the <strong>Project Tree</strong>.</p>
-
-<p><img src="/images/3d-main-window/WellsInTree.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellsInTree.png" alt=""></p>
 <p>The visible wells are always shown in all the 3D Views in the complete project, so the toggles and settings control the overall project visibility of the Well Paths. The <strong>Property Editor</strong> of the <strong>Wells</strong> item is shown below</p>
-
-<p><img src="/images/3d-main-window/WellPathCollectionProperties.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellPathCollectionProperties.png" alt=""></p>
 <ul>
 <li><strong>Global well path visibility</strong> &ndash; This option forces the well paths on or off, ignoring the individual settings unless it is set to Individual.</li>
 <li><strong>Clip Well Paths</strong> &ndash; This option hides the top of the Well Paths to avoid displaying the very long lines from the reservoir to the sea surface.</li>
 <li><strong>Well Path clipping depth distance</strong> &ndash; This number is the distance from the top of the reservoir to the clipping depth.</li>
 </ul>
-
 <h2 id="individual-well-path">Individual Well Path</h2>
-
 <p>A well path will hold well log data and well path data imported from files. A well path file is placed inside the well path item, while one or more well log files are placed as child items under the well path in the project tree.</p>
-
 <h3 id="importing-well-log-files">Importing Well Log Files</h3>
-
 <p>Well log data is <a href="/import/lasfile/#importing-a-las-file">imported from LAS-files</a>.</p>
-
 <h3 id="well-path-property-editor">Well Path Property Editor</h3>
-
 <p>The well path property editor lets the user control the appearance of the well path and associate the well path to a simulation well. It also gives some information about the well path metadata.</p>
-
-<p><img src="/images/3d-main-window/WellPathPropertyEditor.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/WellPathPropertyEditor.png" alt=""></p>
 <ul>
 <li><strong>Appearance group</strong> &ndash; Settings in this group affect the well path appearance in the 3D view</li>
 <li><strong>File group</strong> &ndash; Information about the well path file</li>
@@ -1942,21 +1937,14 @@ If you are an Equinor employee, make sure you have access to &ldquo;EDM Landmark
 <li><strong>Well Info group</strong> &ndash; Metadata for the well path</li>
 <li><strong>Well Picks group</strong> &ndash; Information about imported <a href="/3d-main-window/formations/#well-picks">well picks</a> file containing data for the current well path</li>
 </ul>
-
 <h3 id="casing-design">Casing Design</h3>
-
 <p>Some Casing Design elements can be assigned to the well path by selecting <strong>Create Casign Design</strong> from the right-click menu of the well path.</p>
-
-<p>This will create a new child object for the Well Path, named <strong>Casing Design</strong>. In the <strong>Casign Design</strong> Property editor
+<p>This will create a new child object for the Well Path, named <strong>Casing Design</strong>. In the <strong>Casign Design</strong> Property editor 
 well path containment properties such as Casing (with Casing Shoe) and Liner can be added to the well path along with a start and end depth and a diameter.</p>
-
-<p><img src="/images/3d-main-window/CasignDesign.png" alt="" /></p>
-
+<p><img src="/images/3d-main-window/CasignDesign.png" alt=""></p>
 <p>These can be visualised in the 3D View and Well Log Plots on a <a href="/plot-window/welllogsandplots/#tracks">Well Log Track</a>.</p>
-
-<p><img src="/images/3d-main-window/CasignDesign3D.png" alt="" /></p>
-
-<p><img src="/images/3d-main-window/CasignDesignPlot.png" alt="" /></p>
+<p><img src="/images/3d-main-window/CasignDesign3D.png" alt=""></p>
+<p><img src="/images/3d-main-window/CasignDesignPlot.png" alt=""></p>
 
 
 <footer class=" footline" >
@@ -2132,6 +2120,19 @@ well path containment properties such as Casing (with Casing Shoe) and Liner can
                         
             
             
+                
+                    
+                
+                
+
+                    
+                    
+                    
+
+                    
+                        
+            
+            
         
                     
                         
@@ -2142,6 +2143,9 @@ well path containment properties such as Casing (with Casing Shoe) and Liner can
             
         
                     
+            
+        
+                    
                         
             
             
@@ -3292,20 +3296,20 @@ well path containment properties such as Casing (with Casing Shoe) and Liner can
     <div style="left: -1000px; overflow: scroll; position: absolute; top: -1000px; border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;">
       <div style="border: none; box-sizing: content-box; height: 200px; margin: 0px; padding: 0px; width: 200px;"></div>
     </div>
-    <script src="/js/clipboard.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.min.js?1580243646"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1580243646"></script>
-    <script src="/js/jquery.sticky.js?1580243646"></script>
-    <script src="/js/featherlight.min.js?1580243646"></script>
-    <script src="/js/html5shiv-printshiv.min.js?1580243646"></script>
-    <script src="/js/highlight.pack.js?1580243646"></script>
+    <script src="/js/clipboard.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.min.js?1585823630"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1585823630"></script>
+    <script src="/js/jquery.sticky.js?1585823630"></script>
+    <script src="/js/featherlight.min.js?1585823630"></script>
+    <script src="/js/html5shiv-printshiv.min.js?1585823630"></script>
+    <script src="/js/highlight.pack.js?1585823630"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1580243646"></script>
-    <script src="/js/learn.js?1580243646"></script>
-    <script src="/js/hugo-learn.js?1580243646"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1585823630"></script>
+    <script src="/js/learn.js?1585823630"></script>
+    <script src="/js/hugo-learn.js?1585823630"></script>
 
-    <link href="/mermaid/mermaid.css?1580243646" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1580243646"></script>
+    <link href="/mermaid/mermaid.css?1585823630" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1585823630"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
