diff --git a/3d-main-window/3dviews/index.html b/3d-main-window/3dviews/index.html
index be1afa8f1b..049d61ce4f 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Views :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2900,7 +2899,7 @@ See <a href="/wells-and-completions/completions/#visualization-and-inspection-of
 <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>
 
 
@@ -5032,19 +5031,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/allandiagrams/index.html b/3d-main-window/allandiagrams/index.html
index a79d1b6989..9f401cca82 100644
--- a/3d-main-window/allandiagrams/index.html
+++ b/3d-main-window/allandiagrams/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Allan Diagram :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2816,7 +2815,7 @@ if (!doNotTrack) {
 <p><img src="/images/3d-main-window/AllanDiagram.png" alt=""></p>
 <p><strong>Allan Diagrams</strong> displays the overlap of formations and layers across fault faces.</p>
 <h2 id="separate-fault-result">Separate Fault Result</h2>
-<p>The <strong>Allan Diagram</strong> is dispayed by selecting the <strong>Separate Fault Result</strong> in the project tree. 
+<p>The <strong>Allan Diagram</strong> is dispayed by selecting the <strong>Separate Fault Result</strong> in the project tree.
 <img src="/images/3d-main-window/AllanDiagramPropertyEditor.png" alt=""></p>
 <p>See <a href="/3d-main-window/faults/#separate-fault-result">Faults </a> for more details.</p>
 <h2 id="property-editor-settings">Property Editor Settings</h2>
@@ -4962,19 +4961,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/annotations/index.html b/3d-main-window/annotations/index.html
index df5dccd7cd..5b13d6b5be 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Annotations :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2879,20 +2878,20 @@ Global annotations sub tree</p>
 </ul>
 <h3 id="polyline-file-format">Polyline File format</h3>
 <p>Define each point as three double per line (<strong>X Y Depth</strong>). Comment lines are supported by using <strong>#</strong> at the start of the line</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt"># This is a comment
-# This is a comment
-58177.76 732.7 1643.6 
-58260.83 732.8 1596.6 
-57985.66 732.7 1542.0 
-59601.45 732.4 3639.0 
-59422.01 732.2 3639.0 
-59793.41 732.2 3639.0 
-999 999 999
-# starting polyline 2
-58260.83 732.8 1596.6 
-57985.66 732.7 1542.0 
-59601.45 732.4 3639.0 
-</code></pre></div><h2 id="annotations-visibility">Annotations visibility</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span># This is a comment
+</span></span><span style="display:flex;"><span># This is a comment
+</span></span><span style="display:flex;"><span>58177.76 732.7 1643.6 
+</span></span><span style="display:flex;"><span>58260.83 732.8 1596.6 
+</span></span><span style="display:flex;"><span>57985.66 732.7 1542.0 
+</span></span><span style="display:flex;"><span>59601.45 732.4 3639.0 
+</span></span><span style="display:flex;"><span>59422.01 732.2 3639.0 
+</span></span><span style="display:flex;"><span>59793.41 732.2 3639.0 
+</span></span><span style="display:flex;"><span>999 999 999
+</span></span><span style="display:flex;"><span># starting polyline 2
+</span></span><span style="display:flex;"><span>58260.83 732.8 1596.6 
+</span></span><span style="display:flex;"><span>57985.66 732.7 1542.0 
+</span></span><span style="display:flex;"><span>59601.45 732.4 3639.0 
+</span></span></code></pre></div><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>
 
 
@@ -5027,19 +5026,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/casegroupsandstatistics/index.html b/3d-main-window/casegroupsandstatistics/index.html
index b91b4c4154..b329958034 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Case Groups and Statistics :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2824,7 +2823,7 @@ if (!doNotTrack) {
 
 
 <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><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>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>
@@ -2833,7 +2832,7 @@ if (!doNotTrack) {
 <p>This command will display the recursive file import dialog described on the <a href="/import/eclipsesummarydata/#ensemble-file-import">Summary Plots page</a>.</p>
 <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>&lsquo;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>&rsquo;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>
@@ -5003,19 +5002,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/cellresults/index.html b/3d-main-window/cellresults/index.html
index 6f66678746..687e7f90de 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Cell Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,7 +2821,7 @@ 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>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>
@@ -2840,16 +2839,16 @@ In the following we will describe these options.</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="/calculated-data/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="/calculated-data/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>
@@ -2863,15 +2862,15 @@ c.f. <a href="/3d-main-window/cellresults/#injection-flooding">below</a></li>
 </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/flow-diagnostics-plots/"> Flow Diagnostics Plots</a> and <a href="/plot-window/flow-diagnostics-plots/#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: 
+<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.
@@ -2899,19 +2898,19 @@ Each well is assigned an opposite flow name by adding &ldquo;-XF&rdquo; to the e
 <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>
@@ -2931,7 +2930,7 @@ have a high influence.</li>
 <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. 
+<li><strong>Element Nodal on Face</strong> &ndash; Results with values transformed to element faces or intersections.
 See <a href="/calculated-data/derivedresultsgeomech/">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>
@@ -5076,19 +5075,19 @@ See <a href="/calculated-data/derivedresultsgeomech/">Element Nodal on Face</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/colorlegends/index.html b/3d-main-window/colorlegends/index.html
index 063f83b973..e513bcb285 100644
--- a/3d-main-window/colorlegends/index.html
+++ b/3d-main-window/colorlegends/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Color Legends :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2814,14 +2813,14 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/3d-main-window/ColorLegendCollections.png" alt=""></p>
-<p>ResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends. 
+<p>ResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends.
 All color legends are available from the <strong>Color Legends</strong> item in <strong>Project Tree</strong>.</p>
 <h2 id="standard-color-legends">Standard Color Legends</h2>
 <p>ResInsight offers an extensive set of built-in color legends as listed by <em>Standard Color Legends</em>.
 As <em>Standard Color Legends</em> cannot be modified, you must create a <em>Custom Color Legend</em> when needing a legend that is not covered by <em>Standard Color Legends</em>.</p>
 <p><img src="/images/3d-main-window/ColorLegendStandardCollection.png" alt=""></p>
 <h2 id="create-a-custom-color-legend">Create a Custom Color Legend</h2>
-<p>Custom Color Legends are created by right-clicking the <strong>Color Legends</strong> item in <strong>Project Tree</strong> to either import a 
+<p>Custom Color Legends are created by right-clicking the <strong>Color Legends</strong> item in <strong>Project Tree</strong> to either import a
 <a href="/3d-main-window/formations/">Formation file</a> with color settings or create a new <em>Custom Color Legend</em>.</p>
 <p><img src="/images/3d-main-window/ColorLegendCreateCustomColorLegend.png" alt=""></p>
 <p>It is also possible to copy a standard legend to create a <em>Custom Color Legend</em> as basis for customization.</p>
@@ -2835,7 +2834,7 @@ The property editor is used to define each <em>Color Legend Item</em>.</p>
 <p>The sequence of <em>Color Legend Items</em> can be modified by clicking the arrow symbols seen below.</p>
 <p><img src="/images/3d-main-window/ColorLegendCollectionSequenceColorLegendItem.png" alt=""></p>
 <p>The listed <em>Custom Color Legend</em> is used to form the 3D visualization of formations seen by the top figure of this page.
-Activating this particular <em>Custom Color Legend</em> is performed by specifying it as 
+Activating this particular <em>Custom Color Legend</em> is performed by specifying it as
 <a href="/3d-main-window/resultcolorlegend/">Result Color Legend</a>.</p>
 <h2 id="integer-cell-results">Integer Cell Results</h2>
 <p>When displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying <strong>Formation Names</strong>. If an integer result is loaded, a custom color legend with names can be used.</p>
@@ -4980,19 +4979,19 @@ Activating this particular <em>Custom Color Legend</em> is performed by specifyi
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/comparisonview/index.html b/3d-main-window/comparisonview/index.html
index c5b7e71ff7..7978920707 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Comparison View :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2813,13 +2812,13 @@ 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>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>
@@ -2832,10 +2831,10 @@ Thus two cell results can easily be seen together in the same view.</p>
 <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>
 <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>
@@ -4977,19 +4976,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/contourmaps/index.html b/3d-main-window/contourmaps/index.html
index 4974dafeef..ec3929877f 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Contour Maps :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2819,7 +2818,7 @@ 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>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>
@@ -2901,7 +2900,7 @@ ResInsight is able to <a href="/export/contourmapexport/">export a contour map</
 <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">
@@ -5042,19 +5041,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/depthplot/index.html b/3d-main-window/depthplot/index.html
index bae3994b21..c1ff9487b1 100644
--- a/3d-main-window/depthplot/index.html
+++ b/3d-main-window/depthplot/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Depth Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4938,19 +4937,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/derivedresults/index.html b/3d-main-window/derivedresults/index.html
index fb5176b55a..33a31452c0 100644
--- a/3d-main-window/derivedresults/index.html
+++ b/3d-main-window/derivedresults/index.html
@@ -1 +1,10 @@
-<!DOCTYPE html><html><head><title>https://resinsight.org/calculated-data/derivedresults/</title><link rel="canonical" href="https://resinsight.org/calculated-data/derivedresults/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/derivedresults/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <title>https://resinsight.org/calculated-data/derivedresults/</title>
+    <link rel="canonical" href="https://resinsight.org/calculated-data/derivedresults/">
+    <meta name="robots" content="noindex">
+    <meta charset="utf-8">
+    <meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/derivedresults/">
+  </head>
+</html>
diff --git a/3d-main-window/derivedresultsgeomech/index.html b/3d-main-window/derivedresultsgeomech/index.html
index 65b9008d27..1ea18c88fe 100644
--- a/3d-main-window/derivedresultsgeomech/index.html
+++ b/3d-main-window/derivedresultsgeomech/index.html
@@ -1 +1,10 @@
-<!DOCTYPE html><html><head><title>https://resinsight.org/calculated-data/derivedresultsgeomech/</title><link rel="canonical" href="https://resinsight.org/calculated-data/derivedresultsgeomech/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/derivedresultsgeomech/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <title>https://resinsight.org/calculated-data/derivedresultsgeomech/</title>
+    <link rel="canonical" href="https://resinsight.org/calculated-data/derivedresultsgeomech/">
+    <meta name="robots" content="noindex">
+    <meta charset="utf-8">
+    <meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/derivedresultsgeomech/">
+  </head>
+</html>
diff --git a/3d-main-window/faults/index.html b/3d-main-window/faults/index.html
index 28ebba1417..aca28bdc78 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Faults :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2847,7 +2846,7 @@ As import of faults can be time consuming, reading of faults can be disabled fro
 </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>
 <p>When the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See <a href="/calculated-data/derivedresults/">Derived Results</a> for details on other NNC related results.</p>
 <h2 id="fault-visualization-options">Fault Visualization Options</h2>
@@ -2868,7 +2867,7 @@ The NNC&rsquo;s are sorted onto the Fault&rsquo;s and their visibility is contro
 <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. 
+<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>
 <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>
@@ -5051,19 +5050,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/filters/index.html b/3d-main-window/filters/index.html
index 0c5280b3ce..d2ecf21e56 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Filters :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2824,15 +2823,15 @@ if (!doNotTrack) {
 <li><strong>Property Filter</strong> &ndash; Extracts cells with a property value matching a value range</li>
 </ul>
 
-<div class="notices note" ><p>The visibility of cells connected to wells, and fences can be controlled from <b> <a href="/wells-and-completions/simulationwells/">Simulation Wells</a></b>.<br> 
+<div class="notices note" ><p>The visibility of cells connected to wells, and fences 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>
 
 <h2 id="common-properties-cell-and-property-filters">Common Properties Cell and Property Filters</h2>
 <p>Filters can be turned on and off using their check-boxes in <strong>Project Tree</strong> and controlled by their corresponding <strong>Property Editor</strong>. The sequence of the filters can be rearranged by clicking the arrow icons of selected filter.</p>
 <p><img src="/images/3d-main-window/FiltersInTreeView.png" alt=""></p>
-<p>Cell Filters and Property filters can either be set to <strong>Include</strong> or <strong>Exclude</strong> the matching cells. 
-The <em>Include</em> setting marks the cells as visible while the <em>Exclude</em> setting is used to remove cells from visualization regardless of other filters. 
+<p>Cell Filters and Property filters can either be set to <strong>Include</strong> or <strong>Exclude</strong> the matching cells.
+The <em>Include</em> setting marks the cells as visible while the <em>Exclude</em> setting is used to remove cells from visualization regardless of other filters.
 The icon in front of each filter show a + or - sign to indicate <em>Include</em> or <em>Exclude</em> <img src="https://resinsight.org/images/3d-main-window/FilterIncEx.png" style="display:inline; vertical-align:middle; margin:0">
 .</p>
 <h2 id="cell-filters">Cell Filters</h2>
@@ -2874,7 +2873,7 @@ The <strong>Width</strong> labels show the number of active cells from the start
 <h2 id="property-filters">Property Filters</h2>
 <p><strong>Property Filters</strong> applies to the results of the <strong>Cell 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 property filters.</p>
 <p>A new property filter is created 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 right-click 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>
@@ -5023,19 +5022,19 @@ The <strong>Width</strong> labels show the number of active cells from the start
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/flowvectorresult/index.html b/3d-main-window/flowvectorresult/index.html
index 3695832e4a..55f82c7ebb 100644
--- a/3d-main-window/flowvectorresult/index.html
+++ b/3d-main-window/flowvectorresult/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Flow Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,7 +2814,7 @@ if (!doNotTrack) {
 <p><img src="/images/3d-main-window/FlowVectorResult.PNG" alt=""></p>
 <p>Flow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.</p>
 <h2 id="flow-vectors">Flow Vectors</h2>
-<p>Flow vectors are computed based on the Eclipse properties <strong>FLRGASI/J/K FLRWATI/J/K FLROILI/J/K</strong>. 
+<p>Flow vectors are computed based on the Eclipse properties <strong>FLRGASI/J/K FLRWATI/J/K FLROILI/J/K</strong>.
 Visualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.</p>
 <p>In order to show flow vectors, check the checkbox next to <strong>Flow Vector Result</strong> in <strong>Project Tree</strong>.</p>
 <p><img src="/images/3d-main-window/FlowVectorResultMenu.PNG" alt=""></p>
@@ -2836,7 +2835,7 @@ Visualization of flow vector results always use velocity instead of rate. Veloci
 <li>
 <p><strong>Visibility</strong></p>
 <p>&ndash; <strong>View Vectors</strong>: Select <em>Per Face</em> to show one flow vector per cell face or <em>Cell Center Total</em> to show only one vector per cell center (as an aggregation of all single direction vectors).</p>
-<p>&ndash; <strong>Vectors Touching Surface</strong>: Select <em>At Vector Anchor</em> to display vectors starting at cell faces or <em>At Vector Center</em> to center vectors at cell faces. 
+<p>&ndash; <strong>Vectors Touching Surface</strong>: Select <em>At Vector Anchor</em> to display vectors starting at cell faces or <em>At Vector Center</em> to center vectors at cell faces.
 <em>Vectors Touching Surface</em> is enabled when <em>View vectors</em> is set to <em>Per Face</em>.</p>
 <p>&ndash; <strong>I/J/K</strong>: Use flows in I/J/K direction for computing vectors.</p>
 <p>&ndash; <strong>Show NNC data</strong>: Visualize flows between non-neighbouring cells.</p>
@@ -4985,19 +4984,19 @@ These results are listed in ResInsight postfixed by <em>IJK+-</em> or <em>XYZ</e
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/formations/index.html b/3d-main-window/formations/index.html
index afe7618519..c22d723c5d 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> Zonations/Formations :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2838,36 +2837,36 @@ if (!doNotTrack) {
 <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 entries containing formation name, k-range, and <em>optionally</em> a formation color.
 Formation color can be given as a World Wide Web Consortium <a href="https://www.w3.org/TR/SVG11/types.html#ColorKeywords">SVG color keyword name</a>
-or a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and 
+or a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and
 blue components of the color, c.f. example below:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">-- Any text as comment
-&#39;My First  Formation Name&#39;                             4 - 12   red
-&#39;My Second Formation Name&#39;                            15 - 17   green
-&#39;Formation spanning 3 k-layers, i.e. 18,19 and 20&#39;       3      blue
-&#39;Last Formation Name&#39;                                 21 - 21   #FFFF00
-</code></pre></div><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. 
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>-- Any text as comment
+</span></span><span style="display:flex;"><span>&#39;My First  Formation Name&#39;                             4 - 12   red
+</span></span><span style="display:flex;"><span>&#39;My Second Formation Name&#39;                            15 - 17   green
+</span></span><span style="display:flex;"><span>&#39;Formation spanning 3 k-layers, i.e. 18,19 and 20&#39;       3      blue
+</span></span><span style="display:flex;"><span>&#39;Last Formation Name&#39;                                 21 - 21   #FFFF00
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">1   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
-</code></pre></div><h3 id="select-the-formation-file-in-a-case">Select the Formation File in a Case</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>1   UpperReek
+</span></span><span style="display:flex;"><span>2   UpperReek
+</span></span><span style="display:flex;"><span>3   UpperReek
+</span></span><span style="display:flex;"><span>4   UpperReek
+</span></span><span style="display:flex;"><span>5   UpperReek
+</span></span><span style="display:flex;"><span>6   MidReek
+</span></span><span style="display:flex;"><span>7   MidReek
+</span></span><span style="display:flex;"><span>8   MidReek
+</span></span><span style="display:flex;"><span>9   MidReek
+</span></span><span style="display:flex;"><span>10  MidReek
+</span></span><span style="display:flex;"><span>11  LowerReek
+</span></span><span style="display:flex;"><span>12  LowerReek
+</span></span><span style="display:flex;"><span>13  LowerReek
+</span></span><span style="display:flex;"><span>14  LowerReek
+</span></span></code></pre></div><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>
 <h4 id="reload-of-formation-data">Reload of formation data</h4>
@@ -2900,7 +2899,7 @@ 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>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
+<pre tabindex="0"><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
 B-3H; STRAT; FANGST GP. ;2203.399902;2223.350098
@@ -5061,19 +5060,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/gridpropertycalculator/index.html b/3d-main-window/gridpropertycalculator/index.html
index ad8009461c..e07f701a33 100644
--- a/3d-main-window/gridpropertycalculator/index.html
+++ b/3d-main-window/gridpropertycalculator/index.html
@@ -1 +1,10 @@
-<!DOCTYPE html><html><head><title>https://resinsight.org/calculated-data/gridpropertycalculator/</title><link rel="canonical" href="https://resinsight.org/calculated-data/gridpropertycalculator/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/gridpropertycalculator/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <title>https://resinsight.org/calculated-data/gridpropertycalculator/</title>
+    <link rel="canonical" href="https://resinsight.org/calculated-data/gridpropertycalculator/">
+    <meta name="robots" content="noindex">
+    <meta charset="utf-8">
+    <meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/gridpropertycalculator/">
+  </head>
+</html>
diff --git a/3d-main-window/gridstatisticsdialog/index.html b/3d-main-window/gridstatisticsdialog/index.html
index ac7770786c..fab34af667 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Statistics Dialog :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4989,19 +4988,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/index.html b/3d-main-window/index.html
index 71e7a57d66..b53c4d631b 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Main Window :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -439,7 +439,7 @@
   
     
     <li data-nav-id="/3d-main-window/" title="3D Main Window" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2798,8 +2797,8 @@ 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>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>
@@ -4943,19 +4942,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/index.xml b/3d-main-window/index.xml
index 5385f12a74..7d9bb3fa9b 100644
--- a/3d-main-window/index.xml
+++ b/3d-main-window/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/3d-main-window/</link>
     <description>Recent content in 3D Main Window on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/3d-main-window/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/3d-main-window/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>3D Views</title>
       <link>https://resinsight.org/3d-main-window/3dviews/</link>
@@ -29,7 +25,7 @@ Several views can be added to the same case by right-clicking the case or a view
       <guid>https://resinsight.org/3d-main-window/cellresults/</guid>
       <description>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.
 Cell Results are used in several operations and settings:
- 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.</description>
+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.</description>
     </item>
     
     <item>
@@ -40,7 +36,7 @@ Cell Results are used in several operations and settings:
       <guid>https://resinsight.org/3d-main-window/resultcolorlegend/</guid>
       <description>The color mapping of the displayed cell result is controlled by the Color Legend item in Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Color Legend item.
 Legend configuration As shown above, the Legend configuration for cell results allows the following settings:
- Number of levels &amp;ndash; Defines the number of tick marks displayed next to the color legend Significant digits &amp;ndash; Defines the number of significant digits in the number formatting Number format &amp;ndash; Defines how the numbers are formatted Colors &amp;ndash; Defines the color palette for the legend by selecting from Color Legends Mapping &amp;ndash; Defines the mapping of numerical values to legend colors:  Discrete Linear &amp;ndash; Legend divided into linear levels defined by Number of levels Continuous Linear &amp;ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic &amp;ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic &amp;ndash; Logarithmic legend divided into levels defined by Number of levels Category &amp;ndash; Legend with one level per category for formation names and discrete data (e.</description>
+Number of levels &amp;ndash; Defines the number of tick marks displayed next to the color legend Significant digits &amp;ndash; Defines the number of significant digits in the number formatting Number format &amp;ndash; Defines how the numbers are formatted Colors &amp;ndash; Defines the color palette for the legend by selecting from Color Legends Mapping &amp;ndash; Defines the mapping of numerical values to legend colors: Discrete Linear &amp;ndash; Legend divided into linear levels defined by Number of levels Continuous Linear &amp;ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic &amp;ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic &amp;ndash; Logarithmic legend divided into levels defined by Number of levels Category &amp;ndash; Legend with one level per category for formation names and discrete data (e.</description>
     </item>
     
     <item>
@@ -70,7 +66,7 @@ Standard Color Legends ResInsight offers an extensive set of built-in color lege
       
       <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. 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>
+The figure above exemplifies a Comparison View for comparison of two different simulations models and results.</description>
     </item>
     
     <item>
@@ -133,9 +129,9 @@ Visibility of the docking widows can be controlled from the Windows menu.</descr
       
       <guid>https://resinsight.org/3d-main-window/filters/</guid>
       <description>Filters are used to control the visibility of cells in the 3D view. Two types of filters exist:
- Cell Filter &amp;ndash; Extracts subset(s) of grid cells Property Filter &amp;ndash; Extracts cells with a property value matching a value range  The visibility of cells connected to wells, and fences can be controlled from  Simulation Wells.
+Cell Filter &amp;ndash; Extracts subset(s) of grid cells Property Filter &amp;ndash; Extracts cells with a property value matching a value range The visibility of cells connected to wells, and fences can be controlled from Simulation Wells.
 (Not applicable for Geomechanical cases)
-Common Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor.</description>
+Common Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor.</description>
     </item>
     
     <item>
@@ -145,7 +141,7 @@ Visibility of the docking widows can be controlled from the Windows menu.</descr
       
       <guid>https://resinsight.org/3d-main-window/intersections/</guid>
       <description>Intersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. There are two main types of intersections:
-  Intersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.</description>
+Intersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.</description>
     </item>
     
     <item>
@@ -157,7 +153,7 @@ Visibility of the docking widows can be controlled from the Windows menu.</descr
       <description>Creating a Seismic Section Import of data is described in Seismic Data
 Seismic Sections are cross sections that cut a grid model in various ways to display seismic data. A Seismic Section is created by right-clicking the Seismic Section item in Project Tree
 The following types of Seismic Sections are available:
- Inline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired.</description>
+Inline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired.</description>
     </item>
     
     <item>
@@ -178,8 +174,8 @@ Imported surfaces are listed under the entry in the Project Tree. You can click
       
       <guid>https://resinsight.org/3d-main-window/allandiagrams/</guid>
       <description>Allan Diagrams displays the overlap of formations and layers across fault faces.
-Separate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults  for more details.
-Property Editor Settings  Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault  Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault.</description>
+Separate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults for more details.
+Property Editor Settings Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault.</description>
     </item>
     
     <item>
@@ -205,7 +201,7 @@ All the tagged cell faces are then compared to the faults possibly imported from
       <description>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.
 Formations 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.
 To use this functionality you will need to :
- 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-&amp;gt;Import-&amp;gt;Import Formation Names.</description>
+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-&amp;gt;Import-&amp;gt;Import Formation Names.</description>
     </item>
     
     <item>
@@ -226,7 +222,7 @@ Result Inspection</description>
       <guid>https://resinsight.org/3d-main-window/gridstatisticsdialog/</guid>
       <description>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.
 Grid Statistics Dialog Fields The dialog consist of three information parts.
- Info text Histogram Cumulative Histogram  Info Text The Info Text field shows general info about the case, the selected results, and some statistics.</description>
+Info text Histogram Cumulative Histogram Info Text The Info Text field shows general info about the case, the selected results, and some statistics.</description>
     </item>
     
     <item>
@@ -235,7 +231,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;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).
+      <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).
 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>
     
@@ -266,8 +262,8 @@ 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>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/3d-main-window/intersections/index.html b/3d-main-window/intersections/index.html
index a24261678f..6fcfd6d8eb 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Intersections :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2823,7 +2822,7 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/3d-main-window/IntersectionOverview.png" alt=""></p>
-<p>Intersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. 
+<p>Intersections are cross sections of a grid model that cut the grid in various ways to display grid cell values.
 There are two main types of intersections:</p>
 <ol>
 <li>
@@ -2955,7 +2954,7 @@ By <strong>Defined by two points</strong>, the user can define the direction bas
 <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>
 <h2 id="depth-and-range-filter">Depth and Range Filter</h2>
-<p>An intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined <strong>Depth Filter</strong>. 
+<p>An intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined <strong>Depth Filter</strong>.
 Depth filtering is performed by selecting an intersection in <strong>Project Tree</strong> and setting <strong>Depth Filter</strong> properties in <strong>Property Editor</strong>:</p>
 <ul>
 <li><strong>None</strong>: no depth filtering</li>
@@ -2963,7 +2962,7 @@ Depth filtering is performed by selecting an intersection in <strong>Project Tre
 <li><strong>Below</strong>: show below the specified <em>Depth</em></li>
 <li><strong>Between</strong>: show between the specified <em>Upper Depth</em> and the specified <em>Lower Depth</em></li>
 </ul>
-<p>An intersection can be also be visually filtered by a user defined <strong>K Range Filter</strong>. 
+<p>An intersection can be also be visually filtered by a user defined <strong>K Range Filter</strong>.
 K Range filtering is performed by enabling <strong>K Range Filter</strong> of an intersection. The filtering is defined using a text string, i.e. &ldquo;5,10-15,20:3&rdquo;, see <a href="/misc/advancedtextinput/">Advanced Text Input</a> for details.</p>
 <p><img src="/images/3d-main-window/IntersectionPropEdDepthFilter.png" alt=""></p>
 <h2 id="filter-options-for-all-intersections">Filter Options for all Intersections</h2>
@@ -2974,7 +2973,7 @@ K Range filtering is performed by enabling <strong>K Range Filter</strong> of an
 <p>To select a simulation result to display on an intersection, right-click <strong>Intersection Results</strong> in <strong>Project Tree</strong> and select <strong>New Result Definition</strong>.</p>
 <p><img src="/images/3d-main-window/SeparateIntersectionResults.png" alt=""></p>
 <p>By selecting a specific <strong>Intersection Result</strong>, the <strong>Property Editor</strong> allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.</p>
-<p>The next step is to select an <strong>Intersection</strong> in <strong>Project Tree</strong> and define <strong>Result Reference</strong>. 
+<p>The next step is to select an <strong>Intersection</strong> in <strong>Project Tree</strong> and define <strong>Result Reference</strong>.
 In the example below, available sources are the two <strong>Intersections Results</strong> of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.</p>
 <p><img src="/images/3d-main-window/IntersectionSeparateResultReference.png" alt=""></p>
 
@@ -5110,19 +5109,19 @@ In the example below, available sources are the two <strong>Intersections Result
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/linkedviews/index.html b/3d-main-window/linkedviews/index.html
index 0172a50ee6..de9c42b997 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Linked Views :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2852,7 +2851,7 @@ if (!doNotTrack) {
 <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>
@@ -4994,19 +4993,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/measurement/index.html b/3d-main-window/measurement/index.html
index 470d51b924..5ca06cf0fb 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Measurement :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4957,19 +4956,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/resultcolorlegend/index.html b/3d-main-window/resultcolorlegend/index.html
index 7362e73525..6ba4ccfc9a 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Result Color Legend :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2812,7 +2811,7 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/3d-main-window/legend_configuration.PNG" alt="Legend Configuration"></p>
-<p>The color mapping of the displayed cell result is controlled by the <strong>Color Legend</strong> item in <strong>Project Tree</strong>. 
+<p>The color mapping of the displayed cell result is controlled by the <strong>Color Legend</strong> item in <strong>Project Tree</strong>.
 The legend can be shown or hidden by checking or unchecking the box in front of the <strong>Color Legend</strong> item.</p>
 <h2 id="legend-configuration">Legend configuration</h2>
 <p>As shown above, the Legend configuration for cell results allows the following settings:</p>
@@ -2838,16 +2837,16 @@ The legend can be shown or hidden by checking or unchecking the box in front of
 </ul>
 </li>
 </ul>
-<p>Furthermore, the legend may display semi-transparent with a sorrounding box by selecting the <strong>Show Box around Legends</strong> option of the 
+<p>Furthermore, the legend may display semi-transparent with a sorrounding box by selecting the <strong>Show Box around Legends</strong> option of the
 <a href="/misc/preferences/">Preferences dialog</a>.</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>
 <h2 id="legend-configuration-for-category-results">Legend configuration for category results</h2>
 <p>The <strong>Category</strong> type of legend mapping concerns such as formation names and discrete numbered results (e.g. result names with trailing <em><code>NUM</code></em>).</p>
-<p><strong>Category</strong> type of legends invoke the Property Editor shown below. 
+<p><strong>Category</strong> type of legends invoke the Property Editor shown below.
 Here the default <strong>Category Mode</strong> <em>Interpolate</em> is shown to color all formations.</p>
 <p><img src="/images/3d-main-window/LegendConfigCategoryInterpolate.png" alt="Legend Configuration"></p>
-<p>In the example below, the <strong>Category Mode</strong> <em>Exclusively Category Colors</em> has been selected to produce a 3D visualization of formations according to the category numbers of <em>Selected Formations Legend</em>. 
-As seen, formations according to the category numbers are displayed in colors while the others are displayed in grey. 
+<p>In the example below, the <strong>Category Mode</strong> <em>Exclusively Category Colors</em> has been selected to produce a 3D visualization of formations according to the category numbers of <em>Selected Formations Legend</em>.
+As seen, formations according to the category numbers are displayed in colors while the others are displayed in grey.
 Please see <a href="/3d-main-window/colorlegends/">Color Legends</a> for more information about legends and category numbers.</p>
 <p><img src="/images/3d-main-window/LegendConfigCategoryExclusive.png" alt="Legend Configuration"></p>
 
@@ -4983,19 +4982,19 @@ Please see <a href="/3d-main-window/colorlegends/">Color Legends</a> for more in
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/resultinfo/index.html b/3d-main-window/resultinfo/index.html
index a9f6142e5e..09d0bab7e7 100644
--- a/3d-main-window/resultinfo/index.html
+++ b/3d-main-window/resultinfo/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Result Info :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4953,19 +4952,19 @@ If you want to show additional properties, activate and select additional proper
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/resultinspection/index.html b/3d-main-window/resultinspection/index.html
index 46046795e7..5998d68161 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Result Inspection :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2824,7 +2823,7 @@ 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>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>
 <p>The values along the different K-layers is available in the <a href="/3d-main-window/depthplot/">Depth Plot</a></p>
 
@@ -5116,19 +5115,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/seismicsections/index.html b/3d-main-window/seismicsections/index.html
index a4831593df..c9f1dc503c 100644
--- a/3d-main-window/seismicsections/index.html
+++ b/3d-main-window/seismicsections/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Seismic Sections :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2814,7 +2813,7 @@ if (!doNotTrack) {
 <p><img src="/images/3d-main-window/SeismicHeaderImage.png" alt=""></p>
 <h2 id="creating-a-seismic-section">Creating a Seismic Section</h2>
 <p>Import of data is described in <a href="/import/seismicdata/">Seismic Data</a></p>
-<p><strong>Seismic Sections</strong> are cross sections that cut a grid model in various ways to display seismic data. 
+<p><strong>Seismic Sections</strong> are cross sections that cut a grid model in various ways to display seismic data.
 A <strong>Seismic Section</strong> is created by right-clicking the <strong>Seismic Section</strong> item in <strong>Project Tree</strong></p>
 <p><img src="/images/3d-main-window/SeismicSectionsNew.png" alt=""></p>
 <p>The following types of Seismic Sections are available:</p>
@@ -4975,19 +4974,19 @@ A <strong>Seismic Section</strong> is created by right-clicking the <strong>Seis
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/streamlines/index.html b/3d-main-window/streamlines/index.html
index 975b15b297..9c955d5577 100644
--- a/3d-main-window/streamlines/index.html
+++ b/3d-main-window/streamlines/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Streamlines :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4984,19 +4983,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/surfaces/index.html b/3d-main-window/surfaces/index.html
index 2deef089a7..13246a9698 100644
--- a/3d-main-window/surfaces/index.html
+++ b/3d-main-window/surfaces/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Surfaces :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2826,11 +2825,11 @@ if (!doNotTrack) {
 <p><img src="/images/3d-main-window/SurfacesOverview.png" alt=""></p>
 <p>ResInsight is capable of mapping properties and simulation results onto 3D surfaces imported from GOCAD and Petrel as specified below.</p>
 <h2 id="import-and-appearance-of-surfaces">Import and appearance of surfaces</h2>
-<p>3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option <strong>File</strong>-&gt;<strong>Import</strong>-&gt;<strong>Import Surfaces</strong> 
+<p>3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option <strong>File</strong>-&gt;<strong>Import</strong>-&gt;<strong>Import Surfaces</strong>
 in the <strong>3D Main Window</strong>.</p>
 <p><img src="/images/3d-main-window/SurfacesImport.png" alt=""></p>
 <p>Imported surfaces are listed under the <img src="https://resinsight.org/images/3d-main-window/SurfacesProjectTreeNode.png" style="display:inline; vertical-align:middle; margin:0">
- entry 
+ entry
 in the <strong>Project Tree</strong>. You can click on a surface to change i.e. the name or color of the surface, or change the file to read the surface data from.</p>
 <p><img src="/images/3d-main-window/SurfacesPropertyEditor.png" alt=""></p>
 <p>You can also change the depth of the surface by adding a depth offset (positive or negative). This could be used i.e. to import the same surface file multiple times and assign each instance of the surface a separate depth offset. When a depth offset is set, the offset value will be shown as part of the surface name in the project tree.</p>
@@ -2843,7 +2842,7 @@ in the <strong>Project Tree</strong>. You can click on a surface to change i.e.
 <p>To make it easier to organize the surfaces you import into your project, ResInsight supports creating surface folders in the project tree. To create a new folder, right-click on the top level <strong>Surfaces</strong> folder in the project tree and choose <strong>Add Folder</strong>.</p>
 <p><img src="/images/3d-main-window/surface_addfolder.png" alt=""></p>
 <h2 id="surface-results">Surface Results</h2>
-<p>Per default, ResInsight maps current <strong>Cell Result</strong> on a given surface. 
+<p>Per default, ResInsight maps current <strong>Cell Result</strong> on a given surface.
 If another result is to be displayed, specify the result under <strong>Surface Results</strong> as shown below.</p>
 <p><img src="/images/3d-main-window/SurfacesSeparateSurfaceResults.png" alt=""></p>
 <p>Clicking a surface of a <strong>View</strong> in the <strong>Project Tree</strong> activates the Property Editor for allowing view settings as shown below.</p>
@@ -2868,100 +2867,100 @@ section of the <strong>Property Editor</strong>.</p>
 <h2 id="supported-surface-formats">Supported Surface Formats</h2>
 <h3 id="gocad-surface-format">GOCAD Surface format</h3>
 <p>GOCAD is a computer application that allows you to import, create, modify, integrate, view, and export geological objects in 3D.
-The GOCAD export file format supported by ResInsight is <strong>TSURF</strong> (*.ts). 
-A TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below. 
+The GOCAD export file format supported by ResInsight is <strong>TSURF</strong> (*.ts).
+A TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below.
 ResInsight import vertex and triangle identifiers from the first TFACE section in such a file.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">GOCAD TSurf 1 
-HEADER { 
-name:MF_027_SU 
-} 
-GOCAD_ORIGINAL_COORDINATE_SYSTEM 
-NAME Default 
-AXIS_NAME &#34;X&#34; &#34;Y&#34; &#34;Z&#34; 
-AXIS_UNIT &#34;m&#34; &#34;m&#34; &#34;m&#34; 
-ZPOSITIVE Depth 
-END_ORIGINAL_COORDINATE_SYSTEM 
-TFACE 
-VRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ 
-VRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ 
-VRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ 
-VRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ 
-VRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ 
-VRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ 
-...
-TRGL 2 61 98  
-TRGL 20 153 66  
-TRGL 152 19 65  
-END 
-</code></pre></div><h3 id="petrel-surface-ptl-files">Petrel Surface PTL files</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>GOCAD TSurf 1 
+</span></span><span style="display:flex;"><span>HEADER { 
+</span></span><span style="display:flex;"><span>name:MF_027_SU 
+</span></span><span style="display:flex;"><span>} 
+</span></span><span style="display:flex;"><span>GOCAD_ORIGINAL_COORDINATE_SYSTEM 
+</span></span><span style="display:flex;"><span>NAME Default 
+</span></span><span style="display:flex;"><span>AXIS_NAME &#34;X&#34; &#34;Y&#34; &#34;Z&#34; 
+</span></span><span style="display:flex;"><span>AXIS_UNIT &#34;m&#34; &#34;m&#34; &#34;m&#34; 
+</span></span><span style="display:flex;"><span>ZPOSITIVE Depth 
+</span></span><span style="display:flex;"><span>END_ORIGINAL_COORDINATE_SYSTEM 
+</span></span><span style="display:flex;"><span>TFACE 
+</span></span><span style="display:flex;"><span>VRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ 
+</span></span><span style="display:flex;"><span>VRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ 
+</span></span><span style="display:flex;"><span>VRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ 
+</span></span><span style="display:flex;"><span>VRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ 
+</span></span><span style="display:flex;"><span>VRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ 
+</span></span><span style="display:flex;"><span>VRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ 
+</span></span><span style="display:flex;"><span>...
+</span></span><span style="display:flex;"><span>TRGL 2 61 98  
+</span></span><span style="display:flex;"><span>TRGL 20 153 66  
+</span></span><span style="display:flex;"><span>TRGL 152 19 65  
+</span></span><span style="display:flex;"><span>END 
+</span></span></code></pre></div><h3 id="petrel-surface-ptl-files">Petrel Surface PTL files</h3>
 <p>ResInsight is capable of importing a surface defined by a <strong>PTL</strong> (*.ptl) file format.
-A PTL data file specifies the quads of a surface by <em>x</em>, <em>y</em>, <em>z</em> nodal coordinates and the <em>i</em> and <em>j</em> indices as exemplified below. 
+A PTL data file specifies the quads of a surface by <em>x</em>, <em>y</em>, <em>z</em> nodal coordinates and the <em>i</em> and <em>j</em> indices as exemplified below.
 As seen, <em>#</em> denotes comment lines.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">#Type: scattered data
-#Version: 6
-#Description: No description
-#Format: free
-#Field: 1 x
-#Field: 2 y
-#Field: 3 z meters
-#Field: 4 column
-#Field: 5 row
-#Projection: Local Rectangular
-#Units: meters
-#End: 
-#Information from grid
-#Grid_size: Not_avaiable
-#Grid_space: Not_available
-#Z_field: z
-#Vertical_faults: Not_available
-#History: No history
-#Z_units: meters
-443479.500000 7305390.500000 -1000.000000 1 1
-443479.500000 7305488.500000 -1000.000000 1 2
-443479.500000 7305586.500000 -1000.000000 1 3
-443479.500000 7305684.500000 -1000.000000 1 4
-443479.500000 7305782.500000 -1000.000000 1 5
-443479.500000 7305880.500000 -1000.000000 1 6
-...
-</code></pre></div><h3 id="openworks-xyz-surface-files">OpenWorks XYZ Surface files</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>#Type: scattered data
+</span></span><span style="display:flex;"><span>#Version: 6
+</span></span><span style="display:flex;"><span>#Description: No description
+</span></span><span style="display:flex;"><span>#Format: free
+</span></span><span style="display:flex;"><span>#Field: 1 x
+</span></span><span style="display:flex;"><span>#Field: 2 y
+</span></span><span style="display:flex;"><span>#Field: 3 z meters
+</span></span><span style="display:flex;"><span>#Field: 4 column
+</span></span><span style="display:flex;"><span>#Field: 5 row
+</span></span><span style="display:flex;"><span>#Projection: Local Rectangular
+</span></span><span style="display:flex;"><span>#Units: meters
+</span></span><span style="display:flex;"><span>#End: 
+</span></span><span style="display:flex;"><span>#Information from grid
+</span></span><span style="display:flex;"><span>#Grid_size: Not_avaiable
+</span></span><span style="display:flex;"><span>#Grid_space: Not_available
+</span></span><span style="display:flex;"><span>#Z_field: z
+</span></span><span style="display:flex;"><span>#Vertical_faults: Not_available
+</span></span><span style="display:flex;"><span>#History: No history
+</span></span><span style="display:flex;"><span>#Z_units: meters
+</span></span><span style="display:flex;"><span>443479.500000 7305390.500000 -1000.000000 1 1
+</span></span><span style="display:flex;"><span>443479.500000 7305488.500000 -1000.000000 1 2
+</span></span><span style="display:flex;"><span>443479.500000 7305586.500000 -1000.000000 1 3
+</span></span><span style="display:flex;"><span>443479.500000 7305684.500000 -1000.000000 1 4
+</span></span><span style="display:flex;"><span>443479.500000 7305782.500000 -1000.000000 1 5
+</span></span><span style="display:flex;"><span>443479.500000 7305880.500000 -1000.000000 1 6
+</span></span><span style="display:flex;"><span>...
+</span></span></code></pre></div><h3 id="openworks-xyz-surface-files">OpenWorks XYZ Surface files</h3>
 <p>ResInsight is capable of importing a surface defined by a <strong>XYZ</strong> (*.dat) file from OpenWorks.
-A XYZ data file specifies the quads of a surface by <em>x</em>, <em>y</em>, <em>z</em> nodal coordinates organized in a regular grid. 
+A XYZ data file specifies the quads of a surface by <em>x</em>, <em>y</em>, <em>z</em> nodal coordinates organized in a regular grid.
 As seen, <em>#</em> and <em>@</em> denotes comment lines.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">@File_Version: 4
-@Coordinate_Type_is: 1
-@Export_Type_is: 1
-@Number_of_Projects 1
-@Project_Type_Name: , 3,xxx,
-@Project_Unit_is: meters , xxx
-#File_Version____________-&gt; 4
-#Project_Name____________-&gt; xxx
-#Project_Type____________-&gt; 3
-#Export_XY_Unit__________-&gt; meters
-#OpenWorks_Project_______-&gt; &#39;xxx&#39;
-#Master_Project_______-&gt;
-#Coordinate_type_________-&gt; 1
-#Number_of_points_in_hzd_-&gt; 1
-#Horizon_internal_id_____-&gt; xxx
-#Horizon_extremes_are____-&gt; xxx,xxx
-#Horizon_onset_is_Minimum_____-&gt; 1
-#Horizon_type_is_DEPTH_STRUCTURE______-&gt; 2
-#Horizon_color_is________-&gt; 255 0 0
-#Horizon_name____________-&gt; xxx
-#Horizon_attribute_______-&gt; DEPTH_STRUCTURE
-#Horizon_version_________-&gt; UNKNOWN
-#Horizon_interp_status___-&gt; defaultStat
-#Horizon_class___________-&gt; defaultClass
-#Export_Z_Unit___________-&gt; meters
-#Horizon_onset_type______-&gt; Minimum
-#Horizon_data_domain_____-&gt; DEPTH
-#Horizon_remark_size_____-&gt; 50
-Horizon from Grid on Fri Aug 14 13:42:10 CEST 2020
-#End_of_Horizon_ASCII_Header_
-   4.5423435e+05   7.3239079e+06   1.5970070e+03
-   4.5424414e+05   7.3239157e+06   1.5970485e+03
-   4.5425392e+05   7.3239234e+06   1.5970899e+03
-   4.5426371e+05   7.3239312e+06   1.5971314e+03 
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>@File_Version: 4
+</span></span><span style="display:flex;"><span>@Coordinate_Type_is: 1
+</span></span><span style="display:flex;"><span>@Export_Type_is: 1
+</span></span><span style="display:flex;"><span>@Number_of_Projects 1
+</span></span><span style="display:flex;"><span>@Project_Type_Name: , 3,xxx,
+</span></span><span style="display:flex;"><span>@Project_Unit_is: meters , xxx
+</span></span><span style="display:flex;"><span>#File_Version____________-&gt; 4
+</span></span><span style="display:flex;"><span>#Project_Name____________-&gt; xxx
+</span></span><span style="display:flex;"><span>#Project_Type____________-&gt; 3
+</span></span><span style="display:flex;"><span>#Export_XY_Unit__________-&gt; meters
+</span></span><span style="display:flex;"><span>#OpenWorks_Project_______-&gt; &#39;xxx&#39;
+</span></span><span style="display:flex;"><span>#Master_Project_______-&gt;
+</span></span><span style="display:flex;"><span>#Coordinate_type_________-&gt; 1
+</span></span><span style="display:flex;"><span>#Number_of_points_in_hzd_-&gt; 1
+</span></span><span style="display:flex;"><span>#Horizon_internal_id_____-&gt; xxx
+</span></span><span style="display:flex;"><span>#Horizon_extremes_are____-&gt; xxx,xxx
+</span></span><span style="display:flex;"><span>#Horizon_onset_is_Minimum_____-&gt; 1
+</span></span><span style="display:flex;"><span>#Horizon_type_is_DEPTH_STRUCTURE______-&gt; 2
+</span></span><span style="display:flex;"><span>#Horizon_color_is________-&gt; 255 0 0
+</span></span><span style="display:flex;"><span>#Horizon_name____________-&gt; xxx
+</span></span><span style="display:flex;"><span>#Horizon_attribute_______-&gt; DEPTH_STRUCTURE
+</span></span><span style="display:flex;"><span>#Horizon_version_________-&gt; UNKNOWN
+</span></span><span style="display:flex;"><span>#Horizon_interp_status___-&gt; defaultStat
+</span></span><span style="display:flex;"><span>#Horizon_class___________-&gt; defaultClass
+</span></span><span style="display:flex;"><span>#Export_Z_Unit___________-&gt; meters
+</span></span><span style="display:flex;"><span>#Horizon_onset_type______-&gt; Minimum
+</span></span><span style="display:flex;"><span>#Horizon_data_domain_____-&gt; DEPTH
+</span></span><span style="display:flex;"><span>#Horizon_remark_size_____-&gt; 50
+</span></span><span style="display:flex;"><span>Horizon from Grid on Fri Aug 14 13:42:10 CEST 2020
+</span></span><span style="display:flex;"><span>#End_of_Horizon_ASCII_Header_
+</span></span><span style="display:flex;"><span>   4.5423435e+05   7.3239079e+06   1.5970070e+03
+</span></span><span style="display:flex;"><span>   4.5424414e+05   7.3239157e+06   1.5970485e+03
+</span></span><span style="display:flex;"><span>   4.5425392e+05   7.3239234e+06   1.5970899e+03
+</span></span><span style="display:flex;"><span>   4.5426371e+05   7.3239312e+06   1.5971314e+03 
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5094,19 +5093,19 @@ Horizon from Grid on Fri Aug 14 13:42:10 CEST 2020
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/3d-main-window/tensors/index.html b/3d-main-window/tensors/index.html
index 9b0e515acf..c8f5aa213b 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Tensor Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4971,19 +4970,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/404.html b/404.html
index c8f7f80024..d9e4c42920 100644
--- a/404.html
+++ b/404.html
@@ -9,13 +9,13 @@
   <title>404 Page not found</title>
 
    
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 <style>
     :root #header + #content > #left > #rlblock_left {
diff --git a/_footer/index.html b/_footer/index.html
index 4b646f768e..990a9990f5 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2778,9 +2777,9 @@ if (!doNotTrack) {
       <ul>
         <li>
           <ul>
-            <li><a href="#abouthahahugoshortcode-s0-hbhb"><a href="HAHAHUGOSHORTCODE-s0-HBHB">About</a></a></li>
+            <li><a href="#abouthahahugoshortcodes0hbhb"><a href="HAHAHUGOSHORTCODEs0HBHB">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>
+            <li><a href="#supporthahahugoshortcodes1hbhb"><a href="HAHAHUGOSHORTCODEs1HBHB">Support</a></a></li>
           </ul>
         </li>
       </ul>
@@ -2810,9 +2809,9 @@ if (!doNotTrack) {
 
 
 
-<h3 id="abouthahahugoshortcode-s0-hbhb"><a href="/about/">About</a></h3>
+<h3 id="abouthahahugoshortcodes0hbhb"><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>
+<h3 id="supporthahahugoshortcodes1hbhb"><a href="/support/">Support</a></h3>
 
 
 <footer class="footline">
@@ -4936,19 +4935,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/_header/index.html b/_header/index.html
index 2d1aa720c0..faf7f2b3f6 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title> :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4920,19 +4919,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/about/index.html b/about/index.html
index 29a39df4ab..a8bf269b63 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>About :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,17 +2814,17 @@ 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>
@@ -4970,19 +4969,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/calculatorexpressions/index.html b/calculated-data/calculatorexpressions/index.html
index 7cd6c33a5e..4b2afbce67 100644
--- a/calculated-data/calculatorexpressions/index.html
+++ b/calculated-data/calculatorexpressions/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Calculator Expressions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2829,7 +2828,7 @@ if (!doNotTrack) {
 <p>Possible operations and functions are found by right-clicking in the expression window.</p>
 <h3 id="comment-lines">Comment lines</h3>
 <p>Create a  comment line by prefixing with <code>//</code> or <code>##</code></p>
-<pre><code>// Valid comment line 2
+<pre tabindex="0"><code>// Valid comment line 2
 ## Valid comment line 1
 </code></pre><h3 id="assignment-operators">Assignment Operators</h3>
 <table>
@@ -2846,7 +2845,7 @@ if (!doNotTrack) {
 </tr>
 </tbody>
 </table>
-<pre><code>## Example
+<pre tabindex="0"><code>## Example
 MY_VARIABLE := b + c
 </code></pre><h3 id="basic-operators">Basic Operators</h3>
 <table>
@@ -2883,11 +2882,11 @@ MY_VARIABLE := b + c
 </tr>
 </tbody>
 </table>
-<pre><code>## Example
+<pre tabindex="0"><code>## Example
 a := (b * c) + d / 10.5
 </code></pre><h3 id="conditionals">Conditionals</h3>
 <p><strong>if-then-else</strong> statements can be used to assign values based on the individual values in a vector. The following case will assign 0.01 if the <strong>TRANX</strong> is below 0.01, else copy the original <strong>TRANX</strong> value.</p>
-<pre><code>## Example
+<pre tabindex="0"><code>## Example
 NEW_TRANX := if((TRANX &lt; 0.01), 0.01, TRANX)
 </code></pre><h3 id="scalar-functions">Scalar Functions</h3>
 <table>
@@ -2916,7 +2915,7 @@ NEW_TRANX := if((TRANX &lt; 0.01), 0.01, TRANX)
 </tr>
 </tbody>
 </table>
-<pre><code>## Example: Use the accumulated sum for all PORV values to compute the normalized PORV
+<pre tabindex="0"><code>## Example: Use the accumulated sum for all PORV values to compute the normalized PORV
 NORMALIZED_PORV := x/sum(PORV)
 </code></pre><h3 id="trigonometry-functions">Trigonometry Functions</h3>
 <table>
@@ -5194,19 +5193,19 @@ NORMALIZED_PORV := x/sum(PORV)
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/curvecalculator/index.html b/calculated-data/curvecalculator/index.html
index 1884dba309..109b4a82b3 100644
--- a/calculated-data/curvecalculator/index.html
+++ b/calculated-data/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Curve Calculator :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4973,19 +4972,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/derivedresults/index.html b/calculated-data/derivedresults/index.html
index 1624439f69..4ff78bac38 100644
--- a/calculated-data/derivedresults/index.html
+++ b/calculated-data/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Derived Results - Eclipse :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2832,7 +2831,7 @@ The derived results listed at the bottom of the <strong>Static</strong> result 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>
@@ -5001,19 +5000,19 @@ as a <strong>Cell Result</strong> and <strong>Separate Fault Result</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/derivedresultsgeomech/index.html b/calculated-data/derivedresultsgeomech/index.html
index 32a8784a4d..1e340e7fdc 100644
--- a/calculated-data/derivedresultsgeomech/index.html
+++ b/calculated-data/derivedresultsgeomech/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Derived Results - Geomechanical :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -3001,7 +3000,7 @@ $$ a = \frac {s0} {tan(fa)} $$</p>
 <h3 id="ed---deviatoric-strain">ED - Deviatoric Strain</h3>
 <p>$ED = 2*\frac {E1-E3} {3}  $</p>
 <h3 id="element-nodal-on-face">Element Nodal On Face</h3>
-<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>
@@ -3089,7 +3088,7 @@ mud weight between specific formation layers representing top and base of a fict
 </ul>
 <h4 id="finding-upper-and-lower-mud-weight-limit">Finding Upper and Lower Mud Weight Limit</h4>
 <p>The upper mud weight limit (UMWL) and lower mud weight limit (LMWL) is found for each element intersected by the fictitious well.
-The UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale. 
+The UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale.
 The LMWL is defined as the maximum of shear fracture gradient (SFG) and/or pore pressure in shale, and as pore pressure in sand.</p>
 <p>The calculations for fracture gradient and shear fracture gradient, and the needed input, are described in detail
 in <a href="/plot-window/wellborestabilityplots/">Well Bore Stability Plots</a>.</p>
@@ -5234,19 +5233,19 @@ Otherwise, MWM should is undefined.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/faultdistance/index.html b/calculated-data/faultdistance/index.html
index e6beb0bc94..ea5f3a7a89 100644
--- a/calculated-data/faultdistance/index.html
+++ b/calculated-data/faultdistance/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Fault Distance :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4949,19 +4948,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/gridpropertycalculator/index.html b/calculated-data/gridpropertycalculator/index.html
index 2b0cf60150..d55d1acf11 100644
--- a/calculated-data/gridpropertycalculator/index.html
+++ b/calculated-data/gridpropertycalculator/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Property Calculator :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2813,21 +2812,21 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/3d-main-window/GridPropertyCalculatorMain.png" alt=""></p>
-<p>ResInsight offers a built-in property calculator for grid parameters. 
+<p>ResInsight offers a built-in property calculator for grid parameters.
 The <strong>Grid Property Calculator</strong> enables arithmetic expressions to be parsed and calculated for visualization purposes.</p>
 <p>More details on mathematical operations are described in <a href="/calculated-data/calculatorexpressions/">Calculator Expressions</a></p>
 <h2 id="invoking-the-grid-property-calculator">Invoking the Grid Property Calculator</h2>
 <p>Invoke the the <strong>Grid Property Calculator</strong> by pressing the calculator icon <img src="https://resinsight.org/images/Calculator.svg" style="display:inline; vertical-align:middle; margin:0">
- in the menu bar or by right-clicking 
+ in the menu bar or by right-clicking
 <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Cell Result</strong> in <strong>Project Tree</strong>.</p>
 <p><img src="/images/3d-main-window/GridPropertyCalculatorInvoke.png" alt=""></p>
 <h2 id="example-using-grid-property-calculator">Example using Grid Property Calculator</h2>
-<p>As shown, the <strong>Grid Property Calculator</strong> is invoked by right-clicking 
+<p>As shown, the <strong>Grid Property Calculator</strong> is invoked by right-clicking
 <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Cell Result</strong> in <strong>Project Tree</strong>.
-As seen below, the <strong>Grid Property Calculator</strong> is per default prefilled with the simple summation 
-<em>Calculation_1 := x + y</em>. 
+As seen below, the <strong>Grid Property Calculator</strong> is per default prefilled with the simple summation
+<em>Calculation_1 := x + y</em>.
 This simple summation suffices for exemplifying its use.
 However, you may change name of the calculation and add additional variables and arithmetic operators in the <strong>Expression</strong> field.</p>
 
@@ -2835,8 +2834,8 @@ However, you may change name of the calculation and add additional variables and
 </div>
 
 <p><img src="/images/3d-main-window/GridPropertyCalculatorDefault.png" alt=""></p>
-<p>The next step is to define the variables <em>x</em> and <em>y</em>. 
-An easy way to define each variable is to drag and drop properties from <strong>Data Sources</strong>. See screenshot below for drag and drop of <em>SOIL</em> from <strong>Data Sources</strong> to the row of variable <em>x</em> in <strong>Grid Property Calculator</strong> (emphasized in red). 
+<p>The next step is to define the variables <em>x</em> and <em>y</em>.
+An easy way to define each variable is to drag and drop properties from <strong>Data Sources</strong>. See screenshot below for drag and drop of <em>SOIL</em> from <strong>Data Sources</strong> to the row of variable <em>x</em> in <strong>Grid Property Calculator</strong> (emphasized in red).
 Continue with drag and drop of <em>SGAS</em> to define <em>y</em>.</p>
 <p><img src="/images/3d-main-window/GridPropertyCalculatorDragDrop.png" alt=""></p>
 <p>Finally, press <strong>Calculate</strong> to perform the actual calculation.</p>
@@ -2844,7 +2843,7 @@ Continue with drag and drop of <em>SGAS</em> to define <em>y</em>.</p>
 <p><img src="/images/3d-main-window/GridPropertyCalculatorGeneratedProperty.png" alt=""></p>
 <h2 id="reference-procedure-using-grid-property-calculator">Reference Procedure using Grid Property Calculator</h2>
 <ol>
-<li>Invoke the the <strong>Grid Property Calculator</strong> by right-clicking 
+<li>Invoke the the <strong>Grid Property Calculator</strong> by right-clicking
 <img src="https://resinsight.org/images/3d-main-window/CellResult.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Cell Result</strong> in <strong>Project Tree</strong>.</li>
 <li>Define the expression for calculation by the involved variables and arithmetic operators
@@ -4991,19 +4990,19 @@ Continue with drag and drop of <em>SGAS</em> to define <em>y</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/index.html b/calculated-data/index.html
index 0ed976874c..04275f61eb 100644
--- a/calculated-data/index.html
+++ b/calculated-data/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Calculated Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2536,7 +2536,7 @@
   
     
     <li data-nav-id="/calculated-data/" title="Calculated Data" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4929,19 +4928,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/calculated-data/index.xml b/calculated-data/index.xml
index e5c1826c08..7083be7c78 100644
--- a/calculated-data/index.xml
+++ b/calculated-data/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/calculated-data/</link>
     <description>Recent content in Calculated Data on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/calculated-data/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/calculated-data/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Calculator Expressions</title>
       <link>https://resinsight.org/calculated-data/calculatorexpressions/</link>
@@ -81,4 +77,4 @@ $Value_{[t-b]} = Value_{[t]} - Value_{[b]}$</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/categories/index.html b/categories/index.html
index b7cefe0ba8..08a8dd6adf 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Categories :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2788,6 +2787,8 @@ if (!doNotTrack) {
           
             <h1>
               
+                taxonomy ::
+              
               Categories
             </h1>
           
@@ -4925,19 +4926,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/categories/index.xml b/categories/index.xml
index 2a63b1acd3..bb3a7f0074 100644
--- a/categories/index.xml
+++ b/categories/index.xml
@@ -5,10 +5,6 @@
     <link>https://resinsight.org/categories/</link>
     <description>Recent content in Categories on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/categories/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/categories/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/docs/home/index.html b/docs/home/index.html
index 5fb9162502..e941f0777c 100644
--- a/docs/home/index.html
+++ b/docs/home/index.html
@@ -1 +1,10 @@
-<!DOCTYPE html><html><head><title>https://resinsight.org/getting-started/</title><link rel="canonical" href="https://resinsight.org/getting-started/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://resinsight.org/getting-started/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <title>https://resinsight.org/getting-started/</title>
+    <link rel="canonical" href="https://resinsight.org/getting-started/">
+    <meta name="robots" content="noindex">
+    <meta charset="utf-8">
+    <meta http-equiv="refresh" content="0; url=https://resinsight.org/getting-started/">
+  </head>
+</html>
diff --git a/export/completionexport/index.html b/export/completionexport/index.html
index 2a312f31b6..8a6be6dd82 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2898,11 +2897,11 @@ if (!doNotTrack) {
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">               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></div><ul>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>               Tr   #con       Fcd       Area     KfWf         Kf      Wf       Xf        H       Km
+</span></span><span style="display:flex;"><span>[cP.rm3/day/bars]               []       [m2]    [mDm]       [mD]     [m]      [m]      [m]     [mD]
+</span></span><span style="display:flex;"><span>----------------------------------------------------------------------------------------------------
+</span></span><span style="display:flex;"><span>         110.834     24   276.168   9315.748   54.889   3805.029   0.014   61.628   75.580   13.778
+</span></span></code></pre></div><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>
 <li><strong>Fcd</strong> &ndash; Area weighted fracture conductivity divided by area weighted matrix transmissibility (Kf/Km)</li>
@@ -2916,72 +2915,72 @@ if (!doNotTrack) {
 </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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">--
--- 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            
--- 
-</code></pre></div><h3 id="export-of-fishbone-completion-data">Export of Fishbone Completion Data</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>--
+</span></span><span style="display:flex;"><span>-- Pressure Depletion Time step: 01.Feb 2001
+</span></span><span style="display:flex;"><span>-- WBHP Source: WBHP From Summary Case
+</span></span><span style="display:flex;"><span>-- User Defined WBHP: 200
+</span></span><span style="display:flex;"><span>-- Well    Fracture      Actual WBHP   Min Pressure Drop   Max Pressure Drop   
+</span></span><span style="display:flex;"><span>------------------------------------------------------------------------------
+</span></span><span style="display:flex;"><span>-- B-1H    Fracture_01   221.68147     0.04077             45.10402            
+</span></span><span style="display:flex;"><span>-- B-1H    Fracture_02   221.68147     0.00624             36.02608            
+</span></span><span style="display:flex;"><span>-- B-4DH   Fracture_07   200.00000     28.21733            97.34970            
+</span></span><span style="display:flex;"><span>-- 
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSPECS
--- 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
--- 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      /
-/
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSPECS
+</span></span><span style="display:flex;"><span>-- Well          Grp   I   J    RefDepth   WellType   
+</span></span><span style="display:flex;"><span>   Well Path B   GR    26  45   1230       Oil        \
+</span></span><span style="display:flex;"><span>\
+</span></span><span style="display:flex;"><span>COMPDAT
+</span></span><span style="display:flex;"><span>-- Well            I      J      K1     K2     Status     SAT     TR               DIAM     KH     S     Df
+</span></span><span style="display:flex;"><span>-- Well Path B main bore : 0.0569986
+</span></span><span style="display:flex;"><span>   Well Path B     26     45     29     29     OPEN       1*      5.699858E-02      /
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964
+</span></span><span style="display:flex;"><span>-- Well Path B main bore : 0.230572
+</span></span><span style="display:flex;"><span>   Well Path B     27     41     15     15     OPEN       1*      2.645858E-01      /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSPEC
--- 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     
--- Well Path B main bore : 0.0569986
-   Well Path B     26     45     29     29     OPEN       1*      1*     0.21600     1*     0.00000     1*     &#39;Z&#39;  
--- 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*     &#39;Z&#39;  
-/
-WPIMULT
--- Well            Mult         I      J      K      
-   Well Path B     0.70133      25     45     29      /
-   Well Path B     25.11396     27     41     15      /
-/
-</code></pre></div><h3 id="completions-for-lgr-welspecl-and-compdatl">Completions for LGR (WELSPECL and COMPDATL)</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSPEC
+</span></span><span style="display:flex;"><span>-- Well          Grp   I   J    RefDepth   WellType   
+</span></span><span style="display:flex;"><span>   Well Path B   GR    26  45   1230       Oil        \
+</span></span><span style="display:flex;"><span>\
+</span></span><span style="display:flex;"><span>COMPDAT
+</span></span><span style="display:flex;"><span>-- Well            I      J      K1     K2     Status     SAT     TR     DIAM        KH     S           Df     DIR     
+</span></span><span style="display:flex;"><span>-- Well Path B main bore : 0.0569986
+</span></span><span style="display:flex;"><span>   Well Path B     26     45     29     29     OPEN       1*      1*     0.21600     1*     0.00000     1*     &#39;Z&#39;  
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929
+</span></span><span style="display:flex;"><span>-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964
+</span></span><span style="display:flex;"><span>-- Well Path B main bore : 0.230572
+</span></span><span style="display:flex;"><span>   Well Path B     27     41     15     15     OPEN       1*      1*     0.21600     1*     0.00000     1*     &#39;Z&#39;  
+</span></span><span style="display:flex;"><span>/
+</span></span><span style="display:flex;"><span>WPIMULT
+</span></span><span style="display:flex;"><span>-- Well            Mult         I      J      K      
+</span></span><span style="display:flex;"><span>   Well Path B     0.70133      25     45     29      /
+</span></span><span style="display:flex;"><span>   Well Path B     25.11396     27     41     15      /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSPECL
--- 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*   &#39;Y&#39;    /
--- 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*   &#39;Y&#39;    /
-</code></pre></div><h3 id="lgr-for-completions-temporary-lgrs">LGR for completions (Temporary LGRs)</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSPECL
+</span></span><span style="display:flex;"><span>-- Well      Grp   LGR      I   J   RefDepth   WellType   
+</span></span><span style="display:flex;"><span>   UWell-1   1*    WELLI1   2   9   1*         OIL         /
+</span></span><span style="display:flex;"><span>   /
+</span></span><span style="display:flex;"><span>COMPDATL
+</span></span><span style="display:flex;"><span>-- Well      LgrName   I   J   K1   K2   Status   SAT   TR             DIAM      KH   S         Df   DIR   
+</span></span><span style="display:flex;"><span>-- ---- Completions for completion type Perforation ----
+</span></span><span style="display:flex;"><span>-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676
+</span></span><span style="display:flex;"><span>   UWell-1   WELLI1    2   9   6    6    OPEN     1*    6.106763E+00   0.21600   1*   0.00000   1*   &#39;Y&#39;    /
+</span></span><span style="display:flex;"><span>-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679
+</span></span><span style="display:flex;"><span>   UWell-1   WELLI1    2   8   6    6    OPEN     1*    6.106791E+00   0.21600   1*   0.00000   1*   &#39;Y&#39;    /
+</span></span></code></pre></div><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>
@@ -2993,29 +2992,29 @@ To accomplish this, do the following:</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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSEGS
--- Name            Dep 1          Tlen 1       Vol 1     Len&amp;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      /
-/
-</code></pre></div><ul>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSEGS
+</span></span><span style="display:flex;"><span>-- Name            Dep 1          Tlen 1       Vol 1     Len&amp;Dep     PresDrop     
+</span></span><span style="display:flex;"><span>   Well Path A     4137.09154     87.00000     1*        ABS         H--           /
+</span></span><span style="display:flex;"><span>-- First Seg     Last Seg     Branch Num     Outlet Seg     Length        Depth Change     Diam        Rough       
+</span></span><span style="display:flex;"><span>-- Main stem
+</span></span><span style="display:flex;"><span>-- Segment for sub 0
+</span></span><span style="display:flex;"><span>   2             2            1              1              13.00000      0.53667          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>-- Laterals
+</span></span><span style="display:flex;"><span>-- Diam: MSW - Tubing Radius
+</span></span><span style="display:flex;"><span>-- Rough: MSW - Open Hole Roughness Factor
+</span></span><span style="display:flex;"><span>-- ICD
+</span></span><span style="display:flex;"><span>   3             3            2              2              0.10000       0                0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>-- Fishbone 0 : Sub index 0 - Lateral 0
+</span></span><span style="display:flex;"><span>   52            52           27             3              1.70326       -0.57276         0.00960     0.00100      /
+</span></span><span style="display:flex;"><span>   53            53           27             52             2.34748       -0.81635         0.00960     0.00100      /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div><ul>
 <li>
 <p>The first <em>WELSEGS</em> entry contains information about the well:</p>
 <ul>
@@ -3041,15 +3040,15 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
 </ul>
 <h5 id="compsegs">COMPSEGS</h5>
 <p>An example of the COMPSEGS keyword as exported is shown below.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">COMPSEGS
--- 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         /
-/
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>COMPSEGS
+</span></span><span style="display:flex;"><span>-- Name            
+</span></span><span style="display:flex;"><span>   Well Path A      /
+</span></span><span style="display:flex;"><span>-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     
+</span></span><span style="display:flex;"><span>   28     40     6      27            0.00000          1.70326         /
+</span></span><span style="display:flex;"><span>   28     40     7      27            1.70326          2.34748         /
+</span></span><span style="display:flex;"><span>   28     40     8      27            2.34748          2.96577         /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div><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>
@@ -3057,13 +3056,13 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
 </ul>
 <h5 id="wsegvalv">WSEGVALV</h5>
 <p>An example of the WSEGVALV keyword as exported is shown below.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WSEGVALV
--- 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      /
-/
-</code></pre></div><p>The parameters exported in the WEGVALV keyword are</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WSEGVALV
+</span></span><span style="display:flex;"><span>-- Well Name       Seg No     Cv          Ac          
+</span></span><span style="display:flex;"><span>   Well Path A     3          1.50000     0.00008      /
+</span></span><span style="display:flex;"><span>   Well Path A     5          1.50000     0.00008      /
+</span></span><span style="display:flex;"><span>   Well Path A     7          1.50000     0.00008      /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div><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>
@@ -3072,49 +3071,49 @@ keywords needed to represent the completions as a Multi Segment Well. This is do
 </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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSEGS
--- Name      Dep 1          Tlen 1         Vol 1     Len&amp;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        /
-</code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">WELSEGS
--- Name       Dep 1          Tlen 1         Vol 1     Len&amp;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      /
-/
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSEGS
+</span></span><span style="display:flex;"><span>-- Name      Dep 1          Tlen 1         Vol 1     Len&amp;Dep     PresDrop     
+</span></span><span style="display:flex;"><span>   C-1 H     2575.39553     2919.53029     1*        INC         H--           /
+</span></span><span style="display:flex;"><span>-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       
+</span></span><span style="display:flex;"><span>-- Fracture Segments
+</span></span><span style="display:flex;"><span>-- Diam: MSW - Default Dummy
+</span></span><span style="display:flex;"><span>-- Rough: MSW - Default Dummy
+</span></span><span style="display:flex;"><span>-- Traversal Fracture 02 connected to Main stem segment 11
+</span></span><span style="display:flex;"><span>   25            25           2              11             0.01000      0.00000          0.15000     0.00005      /
+</span></span><span style="display:flex;"><span>/
+</span></span><span style="display:flex;"><span>COMPSEGS
+</span></span><span style="display:flex;"><span>-- Fractures
+</span></span><span style="display:flex;"><span>-- Name      
+</span></span><span style="display:flex;"><span>   C-1 H      /
+</span></span><span style="display:flex;"><span>-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     
+</span></span><span style="display:flex;"><span>   27     43     1      2             11.27214         11.28214        /
+</span></span><span style="display:flex;"><span>   26     44     1      2             11.27214         11.28214        /
+</span></span></code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELSEGS
+</span></span><span style="display:flex;"><span>-- Name       Dep 1          Tlen 1         Vol 1     Len&amp;Dep     PresDrop     
+</span></span><span style="display:flex;"><span>   B-1 AH     2530.38706     3137.28258     1*        INC         H--           /
+</span></span><span style="display:flex;"><span>-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       
+</span></span><span style="display:flex;"><span>-- Main Stem Segments
+</span></span><span style="display:flex;"><span>   2             2            1              1              16.33624     6.96924          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   3             3            1              2              11.77390     4.75668          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   4             4            1              3              9.49721      3.63598          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   5             5            1              4              6.77104      2.59228          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   6             6            1              5              29.44930     10.10431         0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   7             7            1              6              27.93603     7.96718          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>   8             8            1              7              13.95369     3.66086          0.15200     0.00001      /
+</span></span><span style="display:flex;"><span>/
+</span></span><span style="display:flex;"><span>COMPSEGS
+</span></span><span style="display:flex;"><span>-- Name       
+</span></span><span style="display:flex;"><span>   B-1 AH      /
+</span></span><span style="display:flex;"><span>-- I      J      K     Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     
+</span></span><span style="display:flex;"><span>   10     24     1     1             3137.28258       3153.61882      /
+</span></span><span style="display:flex;"><span>   10     24     2     1             3153.61882       3165.39273      /
+</span></span><span style="display:flex;"><span>   9      24     2     1             3165.39273       3174.88994      /
+</span></span><span style="display:flex;"><span>   9      25     2     1             3174.88994       3181.66098      /
+</span></span><span style="display:flex;"><span>   9      25     3     1             3181.66098       3211.11028      /
+</span></span><span style="display:flex;"><span>   9      25     5     1             3239.04631       3253.00000      /
+</span></span><span style="display:flex;"><span>/
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5247,19 +5246,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/contourmapexport/index.html b/export/contourmapexport/index.html
index c0a815d990..3182ebe373 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Contour Map Export :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2835,26 +2834,26 @@ if (!doNotTrack) {
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt"># 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
-...             ...             ...
-</code></pre></div><h2 id="python-interface-for-export-of-contour-maps">Python interface for export of contour maps</h2>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span># case name : 1_R001_REEK-0
+</span></span><span style="display:flex;"><span># sampling points : nx=90 ny=100
+</span></span><span style="display:flex;"><span># time and date : 01.Jan 2000
+</span></span><span style="display:flex;"><span># property name : Arithmetic Mean, PRESSURE
+</span></span><span style="display:flex;"><span># UTM offset : x=456256 y=5.92663e+06
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>x               y               value    
+</span></span><span style="display:flex;"><span>5209.20099      254.10737       341.09308
+</span></span><span style="display:flex;"><span>5336.25467      254.10737       341.13252
+</span></span><span style="display:flex;"><span>5463.30835      254.10737       341.36091
+</span></span><span style="display:flex;"><span>5590.36204      254.10737       341.62615
+</span></span><span style="display:flex;"><span>5717.41572      254.10737       341.70246
+</span></span><span style="display:flex;"><span>5082.14731      381.16105       340.56455
+</span></span><span style="display:flex;"><span>5209.20099      381.16105       340.79087
+</span></span><span style="display:flex;"><span>5336.25467      381.16105       341.02580
+</span></span><span style="display:flex;"><span>5463.30835      381.16105       341.40061
+</span></span><span style="display:flex;"><span>5590.36204      381.16105       341.86177
+</span></span><span style="display:flex;"><span>5717.41572      381.16105       342.34527
+</span></span><span style="display:flex;"><span>...             ...             ...
+</span></span></code></pre></div><h2 id="python-interface-for-export-of-contour-maps">Python interface for export of contour maps</h2>
 <p>The <a href="https://api.resinsight.org">ResInsight Python API</a> 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 examples of the
 <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
@@ -4991,19 +4990,19 @@ A Python script for exporting contour maps to a text file is included as one of
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/eclipseproperties/index.html b/export/eclipseproperties/index.html
index f93183182b..9a2333624b 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Eclipse Properties :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,8 +2814,8 @@ 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>
@@ -4969,19 +4968,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/exportwellpaths/index.html b/export/exportwellpaths/index.html
index 5092bdcba4..dfe7e8fa30 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4942,19 +4941,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/fluxnummultnum/index.html b/export/fluxnummultnum/index.html
index cbd1e4bc65..706774477c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>FLUXNUM/MULTNUM :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4951,19 +4950,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/index.html b/export/index.html
index 18a459b013..959c8157a0 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Export :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2079,7 +2079,7 @@
   
     
     <li data-nav-id="/export/" title="Export" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4941,19 +4940,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/index.xml b/export/index.xml
index 69d8d4a218..47b6da0477 100644
--- a/export/index.xml
+++ b/export/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/export/</link>
     <description>Recent content in Export on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/export/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/export/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Snapshots</title>
       <link>https://resinsight.org/export/snapshots/</link>
@@ -29,7 +25,7 @@ Snapshots of Existing Views The commands to snapshot existing views and plots ar
       <description>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.
 Export 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.
 The following dialog will appear:
- Export File Name &amp;ndash; The path to exported file Eclipse Keyword &amp;ndash; The keyword to use for the property in the eclipse file Undefined Value &amp;ndash; This value is written to the file for all values that are flagged as undefined in ResInsight  For import this type of property data see Import: Eclipse Cases</description>
+Export File Name &amp;ndash; The path to exported file Eclipse Keyword &amp;ndash; The keyword to use for the property in the eclipse file Undefined Value &amp;ndash; This value is written to the file for all values that are flagged as undefined in ResInsight For import this type of property data see Import: Eclipse Cases</description>
     </item>
     
     <item>
@@ -40,7 +36,7 @@ The following dialog will appear:
       <guid>https://resinsight.org/export/fluxnummultnum/</guid>
       <description>The visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.
 You can do this by using the command Export Visible Cells as FLUXNUM/MULTNUM found by right clicking:
- View in the Project Tree. Cell Result in the Project Tree. In any Eclipse 3D View.  The command can also be found in File -&amp;gt; Export. If the command is used in the project tree, the visible cells from the selected view are used for calculation.</description>
+View in the Project Tree. Cell Result in the Project Tree. In any Eclipse 3D View. The command can also be found in File -&amp;gt; Export. If the command is used in the project tree, the visible cells from the selected view are used for calculation.</description>
     </item>
     
     <item>
@@ -60,7 +56,7 @@ You can do this by using the command Export Visible Cells as FLUXNUM/MULTNUM fou
       <guid>https://resinsight.org/export/exportwellpaths/</guid>
       <description>In order to export well paths to dev files, select the menu item File -&amp;gt; Export -&amp;gt; Export Visible Well Paths or select one or more well paths and then select one of the items in the sub menu Export Well Paths.
 A dialog appears after selecting an export well path command.
- 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 &amp;lt;well name&amp;gt;.</description>
+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 &amp;lt;well name&amp;gt;.</description>
     </item>
     
     <item>
@@ -85,4 +81,4 @@ Export of Contour Map Data To export a contour map, invoke one of the following
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/export/sectormodel/index.html b/export/sectormodel/index.html
index 669a48acc0..e51053573d 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Sector Model :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2844,7 +2843,7 @@ inactive (ACTNUM = 0) in the exported grid.</p>
 <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>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
@@ -4982,19 +4981,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/export/snapshots/index.html b/export/snapshots/index.html
index 11989321da..b78db65d0d 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Snapshots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2832,14 +2831,14 @@ if (!doNotTrack) {
 . 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 
+<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>
 
 <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>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>
@@ -4985,19 +4984,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/download-and-install/build-instructions-ubuntu/index.html b/getting-started/download-and-install/build-instructions-ubuntu/index.html
index c9ff1944f2..569c2ded7e 100644
--- a/getting-started/download-and-install/build-instructions-ubuntu/index.html
+++ b/getting-started/download-and-install/build-instructions-ubuntu/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Build Instructions Ubuntu :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5029,19 +5028,19 @@ make -j8
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 4061366221..8200122803 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Build Instructions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2850,9 +2849,9 @@ if (!doNotTrack) {
 <h3 id="cmake">CMake</h3>
 <p><a href="https://cmake.org/download/">CMake</a> version 3.15 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>
@@ -3010,17 +3009,17 @@ This makes it easier to see all of the options for ResInsight.</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 libqt5svg5-dev qtbase5-private-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>
@@ -5160,19 +5159,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 8831100b48..a8b10f9119 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Download and Install :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -164,7 +164,7 @@
   
     
     <li data-nav-id="/getting-started/download-and-install/" title="Download and Install" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,10 +2821,10 @@ if (!doNotTrack) {
 <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="whats-new">What&rsquo;s new</h2>
-<p>ResInsight is under continuous development targeting two major releases per year. 
+<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>
@@ -5012,19 +5011,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></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 15c06fceea..84cf6efdac 100644
--- a/getting-started/download-and-install/index.xml
+++ b/getting-started/download-and-install/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/getting-started/download-and-install/</link>
     <description>Recent content in Download and Install on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/getting-started/download-and-install/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/getting-started/download-and-install/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Linux Installation</title>
       <link>https://resinsight.org/getting-started/download-and-install/linux-installation/</link>
@@ -17,10 +13,10 @@
       
       <guid>https://resinsight.org/getting-started/download-and-install/linux-installation/</guid>
       <description>Install From Binary Packages on Linux Please not that the distribution by the OPM Project will be 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 Launch the application using the command ResInsight
+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Launch the application using the command ResInsight
 Ubuntu On the command line do:
-sudo 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 Launch the application using the command ResInsight</description>
+sudo 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Launch the application using the command ResInsight</description>
     </item>
     
     <item>
@@ -29,9 +25,9 @@ sudo apt-get updatesudo apt-get install software-properties-commonsudo apt-add
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/getting-started/download-and-install/windows-installation/</guid>
-      <description>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.
-Octave Installation (optional)  Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-&amp;gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.
-( Usually C:\Your\Path\To\Octave-x.</description>
+      <description>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.
+Octave Installation (optional) Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-&amp;gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.
+( 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.</description>
     </item>
     
     <item>
@@ -44,7 +40,7 @@ sudo apt-get updatesudo apt-get install software-properties-commonsudo apt-add
 In a git enabled shell do: git clone https://github.com/OPM/ResInsight.git
 Dependencies and Prerequisites Windows Compiler Visual Studio 2019 and later is supported.
 GCC Compiler On RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with
-source /opt/rh/devtoolset-10/enable Qt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.
+source /opt/rh/devtoolset-10/enableQt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.
 Qt download
 On some configurations you will be asked to specify the location of Qt.</description>
     </item>
@@ -55,10 +51,12 @@ On some configurations you will be asked to specify the location of Qt.</descrip
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/getting-started/download-and-install/build-instructions-ubuntu/</guid>
-      <description>Dependencies and Prerequisites Configuration and build    Tool Minimum version     git 2.7.4   gcc 10   python 3    Update apt installer
-sudo apt update Install GCC and related tools
-sudo apt install build-essentialsudo apt install curl zip unzip tar As gcc 10 is required, it can be useful to set the default compiler. Set default compiler</description>
+      <description>Dependencies and Prerequisites Configuration and build Tool Minimum version git 2.7.4 gcc 10 python 3 Update apt installer
+sudo apt updateInstall GCC and related tools
+sudo apt install build-essentialsudo apt install curl zip unzip tarAs gcc 10 is required, it can be useful to set the default compiler. Set default compiler
+Install Qt
+sudo apt install -y qtbase5-dev libqt5svg5-dev qtbase5-private-devClone and update sub modules git clone git://github.</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/getting-started/download-and-install/linux-installation/index.html b/getting-started/download-and-install/linux-installation/index.html
index 6ad7519c9a..cbef4d5228 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Linux Installation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2855,7 +2854,7 @@ sudo apt-get install octave-resinsight
 </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>
 
@@ -2866,9 +2865,9 @@ export QT_PLUGIN_PATH=/path_to_qt/plugins:$QT_PLUGIN_PATH
 </code></pre>
 <h3 id="display-menu-icons-in-gnome-optional">Display Menu Icons in GNOME (Optional)</h3>
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">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></div><p>This fix was taken from reply number 11 in this <a href="https://bbs.archlinux.org/viewtopic.php?id=117414">thread</a></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>gconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true
+</span></span><span style="display:flex;"><span>gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true
+</span></span></code></pre></div><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>
@@ -2880,7 +2879,7 @@ gconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true
 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> 
+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>
 
@@ -5019,19 +5018,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 17d99ef6b0..4f9d302b7c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Windows Installation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2829,7 +2828,7 @@ if (!doNotTrack) {
 <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>
 
@@ -4990,19 +4989,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/helpmenuanddocumentation/index.html b/getting-started/helpmenuanddocumentation/index.html
index 1b82c31180..0ae16617d1 100644
--- a/getting-started/helpmenuanddocumentation/index.html
+++ b/getting-started/helpmenuanddocumentation/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Help Menu and Documentation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2830,7 +2829,7 @@ if (!doNotTrack) {
 <li><strong>Command Line Help</strong> &ndash; Provides an overview of ResInsight <a href="/scripting/commandlineinterface/">Command line parameters</a> and their syntax.</li>
 <li><strong>Summary Command Line Help</strong> &ndash; Provides an overview of ResInsight <a href="/scripting/commandlineinterface/#summary-plotting">Summary command line parameters</a> and their syntax.</li>
 <li><strong>Users Guide</strong> &ndash; Opens the <a href="https://resinsight.org">ResInsight documentation</a> in your default browser</li>
-<li><strong>Search Help</strong> &ndash; Searches the <a href="https://resinsight.org">ResInsight documentation</a> for help on the selected item  in <strong>Project Tree</strong>. 
+<li><strong>Search Help</strong> &ndash; Searches the <a href="https://resinsight.org">ResInsight documentation</a> for help on the selected item  in <strong>Project Tree</strong>.
 Please note that the function key <strong>F1</strong> is a shortcut to this menu option.</li>
 </ul>
 <h2 id="resinsight-documentation-overview">ResInsight Documentation Overview</h2>
@@ -4969,19 +4968,19 @@ Please note that the function key <strong>F1</strong> is a shortcut to this menu
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/index.html b/getting-started/index.html
index 9b280c27cd..51aecf1250 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Getting Started :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -99,7 +99,7 @@
   
     
     <li data-nav-id="/getting-started/" title="Getting Started" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2806,7 +2805,7 @@ 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>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>
@@ -4943,19 +4942,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/index.xml b/getting-started/index.xml
index 99ec3b521c..0b7150803d 100644
--- a/getting-started/index.xml
+++ b/getting-started/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/getting-started/</link>
     <description>Recent content in Getting Started on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/getting-started/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/getting-started/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Overview</title>
       <link>https://resinsight.org/getting-started/overview/</link>
@@ -28,7 +24,7 @@ Docking Windows Each of the main windows has a central area and several docking
       
       <guid>https://resinsight.org/getting-started/projecttree/</guid>
       <description>As described in Overview, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the Project Tree and the Plots windows. Some of their general functionality is described and exemplified below.
-Multiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. To exemplify, consider the plot of Bottom Hole Pressure for a number of wells atop this page.</description>
+Multiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions.</description>
     </item>
     
     <item>
@@ -49,7 +45,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>
@@ -71,8 +67,7 @@ Comparison View ResInsight offers a Comparison View to compare two existing view
       <description>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.
 Bugfixes Release info on GitHub
 Changes in behavior WELSEGS Output of segment depth is based on center of segment. Previously the segment end was reported.
-Export of Completions and MSW 
-Multiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell.</description>
+Export of Completions and MSW Multiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell.</description>
     </item>
     
     <item>
@@ -94,7 +89,7 @@ Allan Diagrams Allan Diagrams displays the overlap of formations and layers acro
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2020_04_1/</guid>
       <description>ResInsight 2020.04.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 2020.04.1 is a patch update with several critical fixes.
 Most important fixes
- Performance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export  Release notes for 2020.</description>
+Performance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export Release notes for 2020.</description>
     </item>
     
     <item>
@@ -115,7 +110,7 @@ Surfaces ResInsight supports import of 3D Surfaces , and allows mapping properti
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2020_10_1/</guid>
       <description>ResInsight 2020.10.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 2020.04.1 is a patch update with several critical fixes.
 Most important fixes
- Using text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level  Python API fixes</description>
+Using text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level Python API fixes</description>
     </item>
     
     <item>
@@ -147,7 +142,7 @@ Performance Improved performance for grid model import from GRDECL. Improved per
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2022_06/</guid>
       <description>Summary Plotting Summary Plotting is updated with new features and improved workflows:
- data sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file  Plot Templates Plot Templates now offer extended features and support for multiplots.</description>
+data sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file Plot Templates Plot Templates now offer extended features and support for multiplots.</description>
     </item>
     
     <item>
@@ -168,7 +163,7 @@ Icons are added to the docking windows to make it easy to find a window.</descri
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2023_01/</guid>
       <description>Summary Plotting Summary Plotting is updated with new features and improved workflows:
- Improved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements  Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.</description>
+Improved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.</description>
     </item>
     
     <item>
@@ -190,7 +185,7 @@ Multi Segment Well Improvements Multi Segmented Wells - MSW is updated with new
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2023_06/</guid>
       <description>Seismic Data ResInsight supports the following seismic file formats:
- SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  Seismic Data
+SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY Seismic Data
 Seismic Sections
 Summary Table Summary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format.</description>
     </item>
@@ -214,8 +209,8 @@ Well Path Creation ResInsight lets the user create new/custom well paths by clic
       
       <guid>https://resinsight.org/getting-started/helpmenuanddocumentation/</guid>
       <description>Integrated ResInsight Help If you need the user manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.
-ResInsight Online Tutorials  ResInsight Tutorial Videos (YouTube) ResInsight Tutorials  ResInsight Help Menu ResInsight Help menu options are:
- About &amp;ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.</description>
+ResInsight Online Tutorials ResInsight Tutorial Videos (YouTube) ResInsight Tutorials ResInsight Help Menu ResInsight Help menu options are:
+About &amp;ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.</description>
     </item>
     
     <item>
@@ -227,8 +222,8 @@ ResInsight Online Tutorials  ResInsight Tutorial Videos (YouTube) ResInsight Tut
       <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>
+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>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/getting-started/modelnavigation/index.html b/getting-started/modelnavigation/index.html
index 6bbe08279a..63478af5b2 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Model Navigation :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5092,19 +5091,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/other/index.html b/getting-started/other/index.html
index b0034a874a..3c840531f6 100644
--- a/getting-started/other/index.html
+++ b/getting-started/other/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Other :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -360,7 +360,7 @@
   
     
     <li data-nav-id="/getting-started/other/" title="Other" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4936,19 +4935,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/other/index.xml b/getting-started/other/index.xml
index 849dad3072..0178923bb3 100644
--- a/getting-started/other/index.xml
+++ b/getting-started/other/index.xml
@@ -5,11 +5,7 @@
     <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" />
-    
-    
+    <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>
@@ -30,8 +26,8 @@ Subscribe</description>
       <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;quot;</description>
+&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
+</rss>
diff --git a/getting-started/other/releasenotification/index.html b/getting-started/other/releasenotification/index.html
index c2ca870073..bf7272021c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Release Notification Subscription :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2824,7 +2823,7 @@ 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>
 
@@ -4958,19 +4957,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/other/testimonials/index.html b/getting-started/other/testimonials/index.html
index ac8e856e2e..9e726901ef 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Testimonials :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2811,7 +2810,7 @@ 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>
 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.&quot;</em></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>
 Researcher, International Research Institute of Stavanger (IRIS)</strong></p>
 
@@ -4952,19 +4951,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/overview/index.html b/getting-started/overview/index.html
index 523a3674a3..8672b64f72 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Overview :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2828,7 +2827,7 @@ if (!doNotTrack) {
 </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>
@@ -2841,7 +2840,7 @@ windows can be managed from the <strong>Windows</strong> menu or directly using
 <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 
+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>
 
@@ -2871,7 +2870,7 @@ Right-click menu commands are also available to do special operations on a selec
 <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>
@@ -2890,7 +2889,7 @@ See <a href="/import/eclipsecases/"> Grid Import and Property Export </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>
@@ -5027,19 +5026,19 @@ When ResInsight is compiled with ABAQUS-odb support, <em><code>*.odb</code></em>
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/projecttree/index.html b/getting-started/projecttree/index.html
index 60df0c4fb7..d43b9e4c38 100644
--- a/getting-started/projecttree/index.html
+++ b/getting-started/projecttree/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Project Tree :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,7 +2814,7 @@ if (!doNotTrack) {
 <p><img src="/images/getting-started/ResInsightPlotProjectTreeAndWindow.png" alt=""></p>
 <p>As described in <a href="/getting-started/overview/">Overview</a>, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the <strong>Project Tree</strong> and the <strong>Plots</strong> windows. Some of their general functionality is described and exemplified below.</p>
 <h2 id="multiple-selection-and-collective-actions">Multiple selection and collective actions</h2>
-<p>Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. 
+<p>Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions.
 To exemplify, consider the plot of <em>Bottom Hole Pressure</em> for a number of wells atop this page. By multi-selection in <strong>Plots</strong>, you may for instance change the color of multiple curves as shown below.</p>
 <p><img src="/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png" alt=""></p>
 <p>Several options are available for multi selection of items which can be used in combination for efficiency and convenience:</p>
@@ -4973,19 +4972,19 @@ To exemplify, consider the plot of <em>Bottom Hole Pressure</em> for a number of
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 22077d9703..cf0a5f4264 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2018.11 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4964,19 +4963,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 b3b4c0c98f..849e75cea0 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.04 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4973,19 +4972,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 0c99e2b69f..9c36b5f028 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.08 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,24 +2814,24 @@ 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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-python" data-lang="python"><span style="color:#f92672">import</span> rips
-<span style="color:#75715e"># Connect to ResInsight instance</span>
-resInsight <span style="color:#f92672">=</span> rips<span style="color:#f92672">.</span>Instance<span style="color:#f92672">.</span>find()
-
-<span style="color:#75715e"># Check if connection worked</span>
-<span style="color:#66d9ef">if</span> resInsight <span style="color:#f92672">is</span> <span style="color:#f92672">not</span> None:
-    <span style="color:#75715e"># Get a list of all cases</span>
-    cases <span style="color:#f92672">=</span> resInsight<span style="color:#f92672">.</span>project<span style="color:#f92672">.</span>cases()
-    <span style="color:#66d9ef">for</span> case <span style="color:#f92672">in</span> cases:
-        <span style="color:#75715e"># Get a list of all views</span>
-        views <span style="color:#f92672">=</span> case<span style="color:#f92672">.</span>views()
-        <span style="color:#66d9ef">for</span> view <span style="color:#f92672">in</span> views:
-            <span style="color:#75715e"># Set some parameters for the view</span>
-            view<span style="color:#f92672">.</span>setShowGridBox(<span style="color:#f92672">not</span> view<span style="color:#f92672">.</span>showGridBox())
-            view<span style="color:#f92672">.</span>setBackgroundColor(<span style="color:#e6db74">&#34;#3388AA&#34;</span>)            
-            <span style="color:#75715e"># Update the view in ResInsight</span>
-            view<span style="color:#f92672">.</span>update()
-</code></pre></div><p>For more information and examples, please see the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-python" data-lang="python"><span style="display:flex;"><span><span style="color:#f92672">import</span> rips
+</span></span><span style="display:flex;"><span><span style="color:#75715e"># Connect to ResInsight instance</span>
+</span></span><span style="display:flex;"><span>resInsight <span style="color:#f92672">=</span> rips<span style="color:#f92672">.</span>Instance<span style="color:#f92672">.</span>find()
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#75715e"># Check if connection worked</span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">if</span> resInsight <span style="color:#f92672">is</span> <span style="color:#f92672">not</span> <span style="color:#66d9ef">None</span>:
+</span></span><span style="display:flex;"><span>    <span style="color:#75715e"># Get a list of all cases</span>
+</span></span><span style="display:flex;"><span>    cases <span style="color:#f92672">=</span> resInsight<span style="color:#f92672">.</span>project<span style="color:#f92672">.</span>cases()
+</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> <span style="color:#66d9ef">case</span> <span style="color:#f92672">in</span> cases:
+</span></span><span style="display:flex;"><span>        <span style="color:#75715e"># Get a list of all views</span>
+</span></span><span style="display:flex;"><span>        views <span style="color:#f92672">=</span> <span style="color:#66d9ef">case</span><span style="color:#f92672">.</span>views()
+</span></span><span style="display:flex;"><span>        <span style="color:#66d9ef">for</span> view <span style="color:#f92672">in</span> views:
+</span></span><span style="display:flex;"><span>            <span style="color:#75715e"># Set some parameters for the view</span>
+</span></span><span style="display:flex;"><span>            view<span style="color:#f92672">.</span>setShowGridBox(<span style="color:#f92672">not</span> view<span style="color:#f92672">.</span>showGridBox())
+</span></span><span style="display:flex;"><span>            view<span style="color:#f92672">.</span>setBackgroundColor(<span style="color:#e6db74">&#34;#3388AA&#34;</span>)            
+</span></span><span style="display:flex;"><span>            <span style="color:#75715e"># Update the view in ResInsight</span>
+</span></span><span style="display:flex;"><span>            view<span style="color:#f92672">.</span>update()
+</span></span></code></pre></div><p>For more information and examples, please see the <a href="https://api.resinsight.org">ResInsight Python API</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>
@@ -4970,19 +4969,19 @@ resInsight <span style="color:#f92672">=</span> rips<span style="color:#f92672">
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 0fb1626a2f..111b2f9631 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.12 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,14 +2821,14 @@ 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>
 <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>
 <h2 id="ensemble-rft-data-import-and-plotting">Ensemble RFT data import and plotting</h2>
@@ -2843,7 +2842,7 @@ Having tailored a plot setup, the user can save the setup as a template definiti
 <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>
 <h2 id="well-bore-stability-plots">Well Bore Stability plots</h2>
@@ -4983,19 +4982,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></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 c10238190f..eea8454acd 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2019.12.1 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4953,19 +4952,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2020_04/index.html b/getting-started/whats-new/releasenotes_2020_04/index.html
index f51516c29d..b544149543 100644
--- a/getting-started/whats-new/releasenotes_2020_04/index.html
+++ b/getting-started/whats-new/releasenotes_2020_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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2020.04 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4985,19 +4984,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2020_04_1/index.html b/getting-started/whats-new/releasenotes_2020_04_1/index.html
index 1377b90fe6..e443b63ee9 100644
--- a/getting-started/whats-new/releasenotes_2020_04_1/index.html
+++ b/getting-started/whats-new/releasenotes_2020_04_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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2020.04.1 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4953,19 +4952,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2020_10/index.html b/getting-started/whats-new/releasenotes_2020_10/index.html
index 0b9098d0a5..0cac760cc1 100644
--- a/getting-started/whats-new/releasenotes_2020_10/index.html
+++ b/getting-started/whats-new/releasenotes_2020_10/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2020.10 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4978,19 +4977,19 @@ Several visualizations can be created, including tornado plots, correlation matr
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2020_10_1/index.html b/getting-started/whats-new/releasenotes_2020_10_1/index.html
index 10199f2abc..564305bb46 100644
--- a/getting-started/whats-new/releasenotes_2020_10_1/index.html
+++ b/getting-started/whats-new/releasenotes_2020_10_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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2020.10.1 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4973,19 +4972,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2021_06/index.html b/getting-started/whats-new/releasenotes_2021_06/index.html
index 9d8c8e6ea8..4c5ed63844 100644
--- a/getting-started/whats-new/releasenotes_2021_06/index.html
+++ b/getting-started/whats-new/releasenotes_2021_06/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2021.06 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,7 +2821,7 @@ if (!doNotTrack) {
 <p>Version 2021.06 is a major update bringing a range of significant new and enhanced features as described below.</p>
 <h2 id="multilateral-wells">Multilateral Wells</h2>
 <p><img src="/images/3d-main-window/MultiLateralWell_3d_view.png" alt="">
-ResInsight lets the user create <a href="/wells-and-completions/createmultilateralwellpaths/">Multilateral Well Paths</a> by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can 
+ResInsight lets the user create <a href="/wells-and-completions/createmultilateralwellpaths/">Multilateral Well Paths</a> by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can
 be exported using the <a href="/export/completionexport/">Completion Export</a></p>
 <h2 id="streamlines">Streamlines</h2>
 <p><img src="/images/3d-main-window/Streamlines.png" alt=""></p>
@@ -4986,19 +4985,19 @@ be exported using the <a href="/export/completionexport/">Completion Export</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2021_10/index.html b/getting-started/whats-new/releasenotes_2021_10/index.html
index 53e99b3a3e..014deb7e88 100644
--- a/getting-started/whats-new/releasenotes_2021_10/index.html
+++ b/getting-started/whats-new/releasenotes_2021_10/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2021.10 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4971,19 +4970,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2022_06/index.html b/getting-started/whats-new/releasenotes_2022_06/index.html
index baf5cf79d1..ce9dc85738 100644
--- a/getting-started/whats-new/releasenotes_2022_06/index.html
+++ b/getting-started/whats-new/releasenotes_2022_06/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2022.06 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2846,15 +2845,15 @@ The new functionality includes, for instance, support for multiple plots and add
 <p>The new <a href="/plot-window/summaryplotmanager/">Plot Manager</a> offers a powerful approach to create multiple summary plots based on a user specified text filter.</p>
 <h2 id="grid-property-calculator">Grid Property Calculator</h2>
 <p><img src="/images/3d-main-window/GridPropertyCalculatorMain.png" alt=""></p>
-<p>The new <a href="/calculated-data/gridpropertycalculator/">Grid Property Calculator</a> can be used to create derived results based on arithmetic expressions. 
+<p>The new <a href="/calculated-data/gridpropertycalculator/">Grid Property Calculator</a> can be used to create derived results based on arithmetic expressions.
 One of the features are easy definition of derived results by drag and drop of grid properties from data sources window.</p>
 <h2 id="filter-intersection">Filter intersection</h2>
 <p><img src="/images/3d-main-window/IntersectionPropEdDepthFilter.png" alt=""></p>
-<p>An intersection can be visually filtered by employing a user defined 
+<p>An intersection can be visually filtered by employing a user defined
 <a href="/3d-main-window/intersections/#depth-filter">Depth Filter</a>.
 Depth filtering is simple to perform by selecting an intersection and setting <em>Depth Filter</em> properties.</p>
 <h2 id="restructured-windows">Restructured windows</h2>
-<p>The new release offers a restructured windows layout for improved user experience and efficiency. 
+<p>The new release offers a restructured windows layout for improved user experience and efficiency.
 The following are separated into individually dockable windows:</p>
 <ul>
 <li>Data sources for summary data can be used for drag/drop operations and efficient creation of plots</li>
@@ -4991,19 +4990,19 @@ The following are separated into individually dockable windows:</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2022_06_1/index.html b/getting-started/whats-new/releasenotes_2022_06_1/index.html
index 924bec7164..bc49d95811 100644
--- a/getting-started/whats-new/releasenotes_2022_06_1/index.html
+++ b/getting-started/whats-new/releasenotes_2022_06_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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2022.06.1 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4955,19 +4954,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2023_01/index.html b/getting-started/whats-new/releasenotes_2023_01/index.html
index 28707ee7fe..d540f75572 100644
--- a/getting-started/whats-new/releasenotes_2023_01/index.html
+++ b/getting-started/whats-new/releasenotes_2023_01/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2023.01 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4978,19 +4977,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2023_03/index.html b/getting-started/whats-new/releasenotes_2023_03/index.html
index 7365d086fe..5bc3361758 100644
--- a/getting-started/whats-new/releasenotes_2023_03/index.html
+++ b/getting-started/whats-new/releasenotes_2023_03/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2023.03 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4990,19 +4989,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/getting-started/whats-new/releasenotes_2023_06/index.html b/getting-started/whats-new/releasenotes_2023_06/index.html
index d1f5737d79..d870adffe8 100644
--- a/getting-started/whats-new/releasenotes_2023_06/index.html
+++ b/getting-started/whats-new/releasenotes_2023_06/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>What&#39;s New in 2023.06 :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4988,19 +4987,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/appendingadditionalproperties/index.html b/import/appendingadditionalproperties/index.html
index c04ef0217d..7684247faa 100644
--- a/import/appendingadditionalproperties/index.html
+++ b/import/appendingadditionalproperties/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Appending Additional Properties :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4945,19 +4944,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/eclipsecases/index.html b/import/eclipsecases/index.html
index 963fde31ed..84bba40287 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Eclipse Cases :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5006,19 +5005,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/eclipsesummarydata/index.html b/import/eclipsesummarydata/index.html
index 2d3c3bcd69..5425e87372 100644
--- a/import/eclipsesummarydata/index.html
+++ b/import/eclipsesummarydata/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Eclipse Summary Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5000,19 +4999,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/elementpropertytable/index.html b/import/elementpropertytable/index.html
index 4280e11a63..8b5020ed7e 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Element Property Table :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2830,27 +2829,27 @@ if (!doNotTrack) {
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">** 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
-</code></pre></div><div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">** 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
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>** ELASTIC SETTING FOR EACH ELEMENT
+</span></span><span style="display:flex;"><span>*Distribution Table, name=RSV_Res-1_Elastic_Table
+</span></span><span style="display:flex;"><span>MODULUS, RATIO
+</span></span><span style="display:flex;"><span>*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table
+</span></span><span style="display:flex;"><span>** Description: Element-by-Element Elastic properties
+</span></span><span style="display:flex;"><span>,     2.
+</span></span><span style="display:flex;"><span>Res-1.210, 11198814808.2538, 0.19041
+</span></span><span style="display:flex;"><span>Res-1.209, 11207002032.1436, 0.19063
+</span></span><span style="display:flex;"><span>Res-1.208, 11222989223.0933, 0.19104
+</span></span><span style="display:flex;"><span>Res-1.207, 11202549454.349, 0.19051
+</span></span></code></pre></div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>** DENSITY SETTING FOR EACH ELEMENT
+</span></span><span style="display:flex;"><span>*Distribution Table, name=RSV_Res-1_Density_Table
+</span></span><span style="display:flex;"><span>Density
+</span></span><span style="display:flex;"><span>*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table
+</span></span><span style="display:flex;"><span>** Description: Element-by-Element Densities
+</span></span><span style="display:flex;"><span>,     1.
+</span></span><span style="display:flex;"><span>Res-1.210, 2500
+</span></span><span style="display:flex;"><span>Res-1.209, 2500
+</span></span><span style="display:flex;"><span>Res-1.208, 2500
+</span></span><span style="display:flex;"><span>Res-1.207, 2500
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -4983,19 +4982,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/ensemblefiledialog/index.html b/import/ensemblefiledialog/index.html
index 71544ac50c..b789399a5d 100644
--- a/import/ensemblefiledialog/index.html
+++ b/import/ensemblefiledialog/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble File Dialog :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2826,7 +2825,7 @@ if (!doNotTrack) {
 <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;**&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.</li>
+<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/*&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>
 <li><strong>File Pattern</strong>: The search pattern that applies to the file name.
 <ul>
 <li><strong>*</strong> Matches any number of any characters except the path separator</li>
@@ -5001,19 +5000,19 @@ case-2/real-3
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/geomechanicaldata/index.html b/import/geomechanicaldata/index.html
index a77de01693..60091b819e 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Geomechanical Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4966,19 +4965,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/index.html b/import/index.html
index b7db28a693..21b5bac7a1 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Import :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -1800,7 +1800,7 @@
   
     
     <li data-nav-id="/import/" title="Import" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2799,9 +2798,9 @@ if (!doNotTrack) {
 
 	<p><img src="/images/import/GeoMechImport.png" alt=""></p>
 <p>ResInsight is able to import a wide span of Eclipse files, seismic data files, and ROFF grid models.</p>
-<p>For import of Eclipse data pertinent to summary vectors and well log data, see 
+<p>For import of Eclipse data pertinent to summary vectors and well log data, see
 <a href="/plot-window/">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>In addition, 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>
 
@@ -4936,19 +4935,19 @@ transient reservoir souring data from the SourSimRL simulation software.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/index.xml b/import/index.xml
index 7d0c85f64f..fdb8d285b5 100644
--- a/import/index.xml
+++ b/import/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/import/</link>
     <description>Recent content in Import on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/import/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/import/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Eclipse Cases</title>
       <link>https://resinsight.org/import/eclipsecases/</link>
@@ -17,8 +13,8 @@
       
       <guid>https://resinsight.org/import/eclipsecases/</guid>
       <description>ResInsight supports the following type of Eclipse input data:
- *.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.
-Eclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-&amp;gt;Import-&amp;gt;Eclipse Cases menu:</description>
+*.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.
+Eclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-&amp;gt;Import-&amp;gt;Eclipse Cases menu:</description>
     </item>
     
     <item>
@@ -50,7 +46,7 @@ This dialog is used for import of different file types like *.</description>
       
       <guid>https://resinsight.org/import/roffgridmodels/</guid>
       <description>ResInsight supports the following type of ROFF input data:
- *.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format.  Roff Data Roff Data can be imported from File-&amp;gt;Import-&amp;gt;Roff Grid Models-&amp;gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.</description>
+*.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format. Roff Data Roff Data can be imported from File-&amp;gt;Import-&amp;gt;Roff Grid Models-&amp;gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.</description>
     </item>
     
     <item>
@@ -60,7 +56,7 @@ This dialog is used for import of different file types like *.</description>
       
       <guid>https://resinsight.org/import/seismicdata/</guid>
       <description>Importing Seismic Data ResInsight supports the following seismic file formats:
- SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-&amp;gt;Import-&amp;gt;Import Seismic.</description>
+SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-&amp;gt;Import-&amp;gt;Import Seismic.</description>
     </item>
     
     <item>
@@ -81,7 +77,7 @@ ResInsight will look for the the well name in the imported LAS-files among the e
       
       <guid>https://resinsight.org/import/geomechanicaldata/</guid>
       <description>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.
-If 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.</description>
+If 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.</description>
     </item>
     
     <item>
@@ -103,7 +99,7 @@ Importing such a file will enable result type called SourSimRL as explained in E
       <description>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.
 To view the data as a Color Result select the Result Position: Element ( See Geomechanical Results )
 A couple of property names are recognized and treated specially:
- MODULUS &amp;ndash; Scaled by 1.0e-9 and shown as &amp;ldquo;Young&amp;rsquo;s Modulus&amp;rdquo; in the user interface RATIO &amp;ndash; Shown as &amp;ldquo;Poisson&amp;rsquo;s Ratio&amp;rdquo; in the user interface  File Format A couple of examples on the file format are shown below.</description>
+MODULUS &amp;ndash; Scaled by 1.0e-9 and shown as &amp;ldquo;Young&amp;rsquo;s Modulus&amp;rdquo; in the user interface RATIO &amp;ndash; Shown as &amp;ldquo;Poisson&amp;rsquo;s Ratio&amp;rdquo; in the user interface File Format A couple of examples on the file format are shown below.</description>
     </item>
     
     <item>
@@ -114,7 +110,7 @@ A couple of property names are recognized and treated specially:
       <guid>https://resinsight.org/import/observeddata/</guid>
       <description>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.
 Import Observed Time History Data Importing observed time history data to ResInsight may be performed in two different ways:
- By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Observed Data By using the right-click command Import Observed Data on the Observed Data item in the Plot Main Window Project Tree  The following file types are supported:</description>
+By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Observed Data By using the right-click command Import Observed Data on the Observed Data item in the Plot Main Window Project Tree The following file types are supported:</description>
     </item>
     
     <item>
@@ -124,8 +120,8 @@ Import Observed Time History Data Importing observed time history data to ResIns
       
       <guid>https://resinsight.org/import/pressuredata/</guid>
       <description>Import Pressure/Depth Data Importing pressure data to ResInsight may be performed in two different ways:
- By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree  The imported pressure data can visualized in [RFT Plots]
-Pressure/Depth File Format --TVDMSL RFT --WELLNAME &amp;#39;OP_1&amp;#39;DATE 28-FEB-2000PRESSURE DEPTHBARSA METRES302.</description>
+By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree The imported pressure data can visualized in [RFT Plots]
+Pressure/Depth File Format --TVDMSL RFT -- WELLNAME &amp;#39;OP_1&amp;#39; DATE 28-FEB-2000 PRESSURE DEPTH BARSA METRES 302.</description>
     </item>
     
     <item>
@@ -136,7 +132,7 @@ Pressure/Depth File Format --TVDMSL RFT --WELLNAME &amp;#39;OP_1&amp;#39;DATE
       <guid>https://resinsight.org/import/appendingadditionalproperties/</guid>
       <description>A grid model can be imported from several sources, either Eclipse binary/ascii or ROFF binary/ascii. Grid properties in separate files can be imported into any grid type as long as the number of grid cells is matching.
 Appending properties
- From the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list.</description>
+From the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list.</description>
     </item>
     
     <item>
@@ -150,4 +146,4 @@ Paste Options Dialog Most of the fields in this dialog are the same as in the CS
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/import/lasfile/index.html b/import/lasfile/index.html
index 5986fc9aea..732913620e 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Log ASCII Standard File :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5047,19 +5046,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/observeddata/index.html b/import/observeddata/index.html
index 925f358f29..4a90e900d8 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Observed Time History Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2857,64 +2856,64 @@ The imported <img src="https://resinsight.org/images/import/Default.png" style="
 <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;.&lsquo;&gt;
+<li><strong>Field</strong> - &lt;VECTOR &lsquo;F&hellip;.'&gt;
 <ul>
 <li>Example: &lsquo;FOPT&rsquo;</li>
 </ul>
 </li>
-<li><strong>Aquifer</strong> - &lt;VECTOR &lsquo;A&hellip;.&lsquo;&gt;:&lt;AQUIFER NUMBER&gt;
+<li><strong>Aquifer</strong> - &lt;VECTOR &lsquo;A&hellip;.&rsquo;&gt;:&lt;AQUIFER NUMBER&gt;
 <ul>
 <li>Example: &lsquo;AAQR:1&rsquo;</li>
 </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;
+<li><strong>Network</strong> - &lt;VECTOR &lsquo;N&hellip;.'&gt;</li>
+<li><strong>Misc</strong> - &lt;VECTOR &lsquo;&hellip;.'&gt;</li>
+<li><strong>Region</strong> - &lt;VECTOR &lsquo;R&hellip;.&rsquo;&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..&lsquo;&gt;:&lt;REGION NUMBER&gt;-&lt;REGION NUMBER&gt;
+<li><strong>Region to Region</strong> - &lt;VECTOR &lsquo;R.F..&rsquo;&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;.&lsquo;&gt;:&lt;GROUP NAME&gt;
+<li><strong>Group</strong> - &lt;VECTOR &lsquo;G&hellip;.&rsquo;&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;.&lsquo;&gt;:&lt;WELL NAME&gt;
+<li><strong>Well</strong> - &lt;VECTOR &lsquo;W&hellip;.&rsquo;&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;.&lsquo;&gt;:&lt;WELL NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
+<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>Example: &lsquo;COFRL:C-1H:26,44,16&rsquo;</li>
 </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;
+<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>Example: &lsquo;LCWIT:WELLI1:I1:5,5,5&rsquo;</li>
 </ul>
 </li>
-<li><strong>LGR Well</strong> - &lt;VECTOR &lsquo;LW&hellip;&lsquo;&gt;:&lt;LGR NAME&gt;:&lt;WELL NAME&gt;
+<li><strong>LGR Well</strong> - &lt;VECTOR &lsquo;LW&hellip;&rsquo;&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 &lsquo;S&hellip;.&lsquo;&gt;:&lt;WELL NAME&gt;:&lt;SEGMENT NUMBER&gt;
+<li><strong>Segment</strong> - &lt;VECTOR &lsquo;S&hellip;.&rsquo;&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;.&lsquo;&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
+<li><strong>Block</strong> - &lt;Vector &lsquo;B&hellip;.&rsquo;&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;&lsquo;&gt;:&lt;LGR NAME&gt;:&lt;I&gt;,&lt;J&gt;,&lt;K&gt;
+<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>Example: &lsquo;LBOSAT:CENTER:5,5,5&rsquo;</li>
 </ul>
@@ -2925,11 +2924,11 @@ The imported <img src="https://resinsight.org/images/import/Default.png" style="
 <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>
+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:&rsquo;, &lsquo;ERR:&rsquo; or &lsquo;ERROR:&rsquo;. 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>
 <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>ResInsight supports a &rsquo;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>
@@ -2942,14 +2941,14 @@ Any address may have associated error data. Those type of data will have the sam
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">DATE       ;VECTOR ;VALUE ;ERROR
-2018-04-16 ;FOPT   ;12.5  ;0.45
-2018-04-18 ;FOPT   ;8.6   ;0.31
-</code></pre></div><p>Normal CSV:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">DATE       ;FOPT ;ERR:FOPT
-2018-04-16 ;12.5 ;0.45
-2018-04-18 ;8.6  ;0.31
-</code></pre></div><h3 id="import-rsm-observed-time-history-data">Import RSM observed time history data</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>DATE       ;VECTOR ;VALUE ;ERROR
+</span></span><span style="display:flex;"><span>2018-04-16 ;FOPT   ;12.5  ;0.45
+</span></span><span style="display:flex;"><span>2018-04-18 ;FOPT   ;8.6   ;0.31
+</span></span></code></pre></div><p>Normal CSV:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>DATE       ;FOPT ;ERR:FOPT
+</span></span><span style="display:flex;"><span>2018-04-16 ;12.5 ;0.45
+</span></span><span style="display:flex;"><span>2018-04-18 ;8.6  ;0.31
+</span></span></code></pre></div><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 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>
@@ -2957,83 +2956,83 @@ Any address may have associated error data. Those type of data will have the sam
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">1                                                                                                      
- -------------------------------------------------------------------------
- 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
-</code></pre></div><h5 id="column-based-with-random-header-width">Column Based with Random Header Width</h5>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>1                                                                                                      
+</span></span><span style="display:flex;"><span> -------------------------------------------------------------------------
+</span></span><span style="display:flex;"><span> SUMMARY
+</span></span><span style="display:flex;"><span> -------------------------------------------------------------------------
+</span></span><span style="display:flex;"><span> DATE         FGIRH        FVPT         FWPT         FOPT         FLPT  
+</span></span><span style="display:flex;"><span>              SM3/DAY      RM3          SM3          SM3          SM3    
+</span></span><span style="display:flex;"><span>                           *10**3       *10**3       *10**3       *10**3 
+</span></span><span style="display:flex;"><span>                                                                         
+</span></span><span style="display:flex;"><span>                                                                         
+</span></span><span style="display:flex;"><span> -------------------------------------------------------------------------
+</span></span><span style="display:flex;"><span>  6-NOV-1997         0            0            0            0            0 
+</span></span><span style="display:flex;"><span>  7-NOV-1997         0     5.749954     0.004548     4.379801     4.384350  
+</span></span><span style="display:flex;"><span>  8-NOV-1997         0     13.76883     0.010841     10.48852     10.49936
+</span></span><span style="display:flex;"><span>  9-NOV-1997         0     19.38692     0.015243     14.76847     14.78372  
+</span></span><span style="display:flex;"><span> 10-NOV-1997         0     24.07161     0.018914     18.33751     18.35642
+</span></span><span style="display:flex;"><span> 11-NOV-1997         0     28.79427     0.022613     21.93558     21.95819
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">TIME      WWCTH      WGORH
-DAYS               SM3/SM3          
-
-          A-5HP          A-5HP
-     1     0.000   0.000
-     2     0.000   0.000
-     3     0.000   0.000
-</code></pre></div><h4 id="keyword-based-file-format">Keyword Based File Format</h4>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>TIME      WWCTH      WGORH
+</span></span><span style="display:flex;"><span>DAYS               SM3/SM3          
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>          A-5HP          A-5HP
+</span></span><span style="display:flex;"><span>     1     0.000   0.000
+</span></span><span style="display:flex;"><span>     2     0.000   0.000
+</span></span><span style="display:flex;"><span>     3     0.000   0.000
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">----------------------------------------------
--- 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
-</code></pre></div><p>Please seek &ldquo;User data file formats&rdquo; in <strong>Eclipse: File Formats Reference Manual</strong> for details.</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>----------------------------------------------
+</span></span><span style="display:flex;"><span>-- GOR data 
+</span></span><span style="display:flex;"><span>----------------------------------------------
+</span></span><span style="display:flex;"><span>VECTOR S-122AH-GOR
+</span></span><span style="display:flex;"><span>UNITS SM3/SM3
+</span></span><span style="display:flex;"><span>ORIGIN GORS-122AH
+</span></span><span style="display:flex;"><span>330.6601
+</span></span><span style="display:flex;"><span>257.7500
+</span></span><span style="display:flex;"><span>335.9894
+</span></span><span style="display:flex;"><span>301.4388
+</span></span><span style="display:flex;"><span>260.4193
+</span></span><span style="display:flex;"><span>306.0298
+</span></span><span style="display:flex;"><span>280.2883
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>VECTOR YEARX
+</span></span><span style="display:flex;"><span>ORIGIN GORS-112AH
+</span></span><span style="display:flex;"><span>UNITS YEAR
+</span></span><span style="display:flex;"><span>1999.7902
+</span></span><span style="display:flex;"><span>1999.8446
+</span></span><span style="display:flex;"><span>1999.9285
+</span></span><span style="display:flex;"><span>2000.0391
+</span></span><span style="display:flex;"><span>2000.0800
+</span></span><span style="display:flex;"><span>2000.0862
+</span></span><span style="display:flex;"><span>2000.1285
+</span></span><span style="display:flex;"><span>---comment
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>----------------------------------------------
+</span></span><span style="display:flex;"><span>-- GOR data
+</span></span><span style="display:flex;"><span>----------------------------------------------
+</span></span><span style="display:flex;"><span>VECTOR S-211H-GOR
+</span></span><span style="display:flex;"><span>UNITS SM3/SM3
+</span></span><span style="display:flex;"><span>ORIGIN GORS-211H
+</span></span><span style="display:flex;"><span>293.8103
+</span></span><span style="display:flex;"><span>293.1634
+</span></span><span style="display:flex;"><span>304.0000
+</span></span><span style="display:flex;"><span>334.5932
+</span></span><span style="display:flex;"><span>306.4610
+</span></span><span style="display:flex;"><span>293.7571
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>VECTOR YEARX
+</span></span><span style="display:flex;"><span>ORIGIN GORS-22H
+</span></span><span style="display:flex;"><span>UNITS YEAR
+</span></span><span style="display:flex;"><span>1999.8255
+</span></span><span style="display:flex;"><span>2000.1274
+</span></span><span style="display:flex;"><span>2000.2075
+</span></span><span style="display:flex;"><span>2000.2367
+</span></span><span style="display:flex;"><span>2000.4033
+</span></span><span style="display:flex;"><span>2000.4966
+</span></span></code></pre></div><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>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>
@@ -5170,19 +5169,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/pasteexceltimedata/index.html b/import/pasteexceltimedata/index.html
index 2996d3cb9c..f844e7c652 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Paste Excel Time History Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4953,19 +4952,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/pressuredata/index.html b/import/pressuredata/index.html
index 89f6f135e3..ff152f6a73 100644
--- a/import/pressuredata/index.html
+++ b/import/pressuredata/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Pressure/Depth Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,28 +2821,27 @@ if (!doNotTrack) {
 </ul>
 <p>The imported pressure data can visualized in <a href="/plot-window/rftplot/">[RFT Plots]</a></p>
 <h4 id="pressuredepth-file-format">Pressure/Depth File Format</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-txt" data-lang="txt">--TVDMSL 
-RFT  
---
-WELLNAME &#39;OP_1&#39;
-DATE 28-FEB-2000
-PRESSURE DEPTH
-BARSA METRES
-302.88 1605.91
-303.88 1615.91
-304.88 1625.91
-304.38 1635.91
---
-WELLNAME &#39;OP_2&#39;
-DATE 28-FEB-2000
-PRESSURE DEPTH
-BARSA METRES
-302.88 1600.91
-303.68 1610.91
-303.88 1612.91
-303.99 1620.91
-
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>--TVDMSL 
+</span></span><span style="display:flex;"><span>RFT  
+</span></span><span style="display:flex;"><span>--
+</span></span><span style="display:flex;"><span>WELLNAME &#39;OP_1&#39;
+</span></span><span style="display:flex;"><span>DATE 28-FEB-2000
+</span></span><span style="display:flex;"><span>PRESSURE DEPTH
+</span></span><span style="display:flex;"><span>BARSA METRES
+</span></span><span style="display:flex;"><span>302.88 1605.91
+</span></span><span style="display:flex;"><span>303.88 1615.91
+</span></span><span style="display:flex;"><span>304.88 1625.91
+</span></span><span style="display:flex;"><span>304.38 1635.91
+</span></span><span style="display:flex;"><span>--
+</span></span><span style="display:flex;"><span>WELLNAME &#39;OP_2&#39;
+</span></span><span style="display:flex;"><span>DATE 28-FEB-2000
+</span></span><span style="display:flex;"><span>PRESSURE DEPTH
+</span></span><span style="display:flex;"><span>BARSA METRES
+</span></span><span style="display:flex;"><span>302.88 1600.91
+</span></span><span style="display:flex;"><span>303.68 1610.91
+</span></span><span style="display:flex;"><span>303.88 1612.91
+</span></span><span style="display:flex;"><span>303.99 1620.91
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -4976,19 +4974,19 @@ BARSA METRES
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/roffgridmodels/index.html b/import/roffgridmodels/index.html
index a75946d937..6536551c65 100644
--- a/import/roffgridmodels/index.html
+++ b/import/roffgridmodels/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>ROFF Grid Models :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4950,19 +4949,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/seismicdata/index.html b/import/seismicdata/index.html
index ef6559757a..4e4f0a0cc6 100644
--- a/import/seismicdata/index.html
+++ b/import/seismicdata/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Seismic Data :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5005,19 +5004,19 @@ In case of discrepancy, the conversion of SEG-Y file has to be performed anew by
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/import/soursimrlresults/index.html b/import/soursimrlresults/index.html
index abd51d403f..05b280d095 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>SourSimRL Results :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2802,7 +2801,7 @@ 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</a></p>
@@ -4939,19 +4938,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/index.html b/index.html
index 7b9dd813ec..a2f503acff 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>ResInsight :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4918,19 +4917,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/index.xml b/index.xml
index 5ff8ab5ab0..8d99e80578 100644
--- a/index.xml
+++ b/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/</link>
     <description>Recent content on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Overview</title>
       <link>https://resinsight.org/getting-started/overview/</link>
@@ -28,7 +24,7 @@ Docking Windows Each of the main windows has a central area and several docking
       
       <guid>https://resinsight.org/getting-started/projecttree/</guid>
       <description>As described in Overview, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the Project Tree and the Plots windows. Some of their general functionality is described and exemplified below.
-Multiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. To exemplify, consider the plot of Bottom Hole Pressure for a number of wells atop this page.</description>
+Multiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions.</description>
     </item>
     
     <item>
@@ -62,8 +58,8 @@ Operators and Functions Possible operations and functions are found by right-cli
       
       <guid>https://resinsight.org/import/eclipsecases/</guid>
       <description>ResInsight supports the following type of Eclipse input data:
- *.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.
-Eclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-&amp;gt;Import-&amp;gt;Eclipse Cases menu:</description>
+*.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.
+Eclipse Results ResInsight offers several ways to import Eclipse (grid) files. Use one of the following commands in the File-&amp;gt;Import-&amp;gt;Eclipse Cases menu:</description>
     </item>
     
     <item>
@@ -95,10 +91,10 @@ This dialog is used for import of different file types like *.</description>
       
       <guid>https://resinsight.org/getting-started/download-and-install/linux-installation/</guid>
       <description>Install From Binary Packages on Linux Please not that the distribution by the OPM Project will be 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 Launch the application using the command ResInsight
+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Launch the application using the command ResInsight
 Ubuntu On the command line do:
-sudo 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 Launch the application using the command ResInsight</description>
+sudo 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Launch the application using the command ResInsight</description>
     </item>
     
     <item>
@@ -118,7 +114,7 @@ General When changing the preferences, any default color, font or Z-scale Factor
       
       <guid>https://resinsight.org/import/roffgridmodels/</guid>
       <description>ResInsight supports the following type of ROFF input data:
- *.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format.  Roff Data Roff Data can be imported from File-&amp;gt;Import-&amp;gt;Roff Grid Models-&amp;gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.</description>
+*.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format. Roff Data Roff Data can be imported from File-&amp;gt;Import-&amp;gt;Roff Grid Models-&amp;gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.</description>
     </item>
     
     <item>
@@ -129,7 +125,7 @@ General When changing the preferences, any default color, font or Z-scale Factor
       <guid>https://resinsight.org/wells-and-completions/simulationwells/</guid>
       <description>This section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.
 Commands Several commands are available as right-click commands on a simulation well. These commands are available either by right-clicking the well in the 3D View or in the Project Tree.
- New Well Log Extraction Curve &amp;ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.</description>
+New Well Log Extraction Curve &amp;ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.</description>
     </item>
     
     <item>
@@ -170,7 +166,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>
@@ -192,8 +188,7 @@ Comparison View ResInsight offers a Comparison View to compare two existing view
       <description>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.
 Bugfixes Release info on GitHub
 Changes in behavior WELSEGS Output of segment depth is based on center of segment. Previously the segment end was reported.
-Export of Completions and MSW 
-Multiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell.</description>
+Export of Completions and MSW Multiple completions in same cell In previous releases, no connection factor has been reported if multiple fracture completions has been detected in the same cell.</description>
     </item>
     
     <item>
@@ -215,7 +210,7 @@ Allan Diagrams Allan Diagrams displays the overlap of formations and layers acro
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2020_04_1/</guid>
       <description>ResInsight 2020.04.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 2020.04.1 is a patch update with several critical fixes.
 Most important fixes
- Performance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export  Release notes for 2020.</description>
+Performance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export Release notes for 2020.</description>
     </item>
     
     <item>
@@ -236,7 +231,7 @@ Surfaces ResInsight supports import of 3D Surfaces , and allows mapping properti
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2020_10_1/</guid>
       <description>ResInsight 2020.10.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 2020.04.1 is a patch update with several critical fixes.
 Most important fixes
- Using text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level  Python API fixes</description>
+Using text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level Python API fixes</description>
     </item>
     
     <item>
@@ -268,7 +263,7 @@ Performance Improved performance for grid model import from GRDECL. Improved per
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2022_06/</guid>
       <description>Summary Plotting Summary Plotting is updated with new features and improved workflows:
- data sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file  Plot Templates Plot Templates now offer extended features and support for multiplots.</description>
+data sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file Plot Templates Plot Templates now offer extended features and support for multiplots.</description>
     </item>
     
     <item>
@@ -289,7 +284,7 @@ Icons are added to the docking windows to make it easy to find a window.</descri
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2023_01/</guid>
       <description>Summary Plotting Summary Plotting is updated with new features and improved workflows:
- Improved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements  Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.</description>
+Improved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.</description>
     </item>
     
     <item>
@@ -311,7 +306,7 @@ Multi Segment Well Improvements Multi Segmented Wells - MSW is updated with new
       
       <guid>https://resinsight.org/getting-started/whats-new/releasenotes_2023_06/</guid>
       <description>Seismic Data ResInsight supports the following seismic file formats:
- SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  Seismic Data
+SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY Seismic Data
 Seismic Sections
 Summary Table Summary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format.</description>
     </item>
@@ -334,7 +329,7 @@ Searching for data sources Atop the Data Sources window, there is a search field
       
       <guid>https://resinsight.org/import/seismicdata/</guid>
       <description>Importing Seismic Data ResInsight supports the following seismic file formats:
- SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-&amp;gt;Import-&amp;gt;Import Seismic.</description>
+SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-&amp;gt;Import-&amp;gt;Import Seismic.</description>
     </item>
     
     <item>
@@ -365,7 +360,7 @@ The *.rsp file is an XML file, and can be edited by any text editor.</descriptio
       
       <guid>https://resinsight.org/scripting/pythoninterface/</guid>
       <description>ResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance from Python 3. This enables you to:
- start ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics  Please refer to the ResInsight Python API for configuration and details.</description>
+start ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics Please refer to the ResInsight Python API for configuration and details.</description>
     </item>
     
     <item>
@@ -396,7 +391,7 @@ Default Horizontally Vertically Window Management The window management system w
       <guid>https://resinsight.org/3d-main-window/cellresults/</guid>
       <description>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.
 Cell Results are used in several operations and settings:
- 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.</description>
+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.</description>
     </item>
     
     <item>
@@ -408,7 +403,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     --help, --?</description>
+Command line options General Parameter Description --help, --? Displays help text and version info --project &amp;lt;filename&amp;gt; Open project file &amp;lt;filename&amp;gt;.</description>
     </item>
     
     <item>
@@ -432,7 +427,7 @@ Calculation Settings To make a new calculated curve, click on New Calculation.</
       <description>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.
 Export 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.
 The following dialog will appear:
- Export File Name &amp;ndash; The path to exported file Eclipse Keyword &amp;ndash; The keyword to use for the property in the eclipse file Undefined Value &amp;ndash; This value is written to the file for all values that are flagged as undefined in ResInsight  For import this type of property data see Import: Eclipse Cases</description>
+Export File Name &amp;ndash; The path to exported file Eclipse Keyword &amp;ndash; The keyword to use for the property in the eclipse file Undefined Value &amp;ndash; This value is written to the file for all values that are flagged as undefined in ResInsight For import this type of property data see Import: Eclipse Cases</description>
     </item>
     
     <item>
@@ -442,7 +437,7 @@ The following dialog will appear:
       
       <guid>https://resinsight.org/import/geomechanicaldata/</guid>
       <description>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.
-If 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.</description>
+If 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.</description>
     </item>
     
     <item>
@@ -464,7 +459,7 @@ Memory Indicator The tools are available from the memory indicator in the bottom
       <description>Summary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes. Source stepping is available from both the Source Stepping Toolbar and the Property editor as described below.
 Source Stepping using the toolbar The toolbar for source stepping is:
 Following this example, the available options are:
- Explicitly setting Step By to vector WBHP by  Change existing plot to display previous or next vector by pressing one of the buttons  Step previous or next vector and add a plot by the buttons  Step previous or next vector and add a curve by the buttons   Source Stepping using the Property Editor Source Stepping is also available through the Property Editor.</description>
+Explicitly setting Step By to vector WBHP by Change existing plot to display previous or next vector by pressing one of the buttons Step previous or next vector and add a plot by the buttons Step previous or next vector and add a curve by the buttons Source Stepping using the Property Editor Source Stepping is also available through the Property Editor.</description>
     </item>
     
     <item>
@@ -496,9 +491,9 @@ 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/download-and-install/windows-installation/</guid>
-      <description>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.
-Octave Installation (optional)  Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-&amp;gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.
-( Usually C:\Your\Path\To\Octave-x.</description>
+      <description>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.
+Octave Installation (optional) Download Octave-4.0.0 and install it. (Newer versions will not work) Launch ResInsight.exe, open Edit-&amp;gt;Preferences. On the Octave tab, enter the path to the Octave command line interpreter executable.
+( 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.</description>
     </item>
     
     <item>
@@ -508,8 +503,8 @@ Well Path Creation ResInsight lets the user create new/custom well paths by clic
       
       <guid>https://resinsight.org/getting-started/helpmenuanddocumentation/</guid>
       <description>Integrated ResInsight Help If you need the user manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.
-ResInsight Online Tutorials  ResInsight Tutorial Videos (YouTube) ResInsight Tutorials  ResInsight Help Menu ResInsight Help menu options are:
- About &amp;ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.</description>
+ResInsight Online Tutorials ResInsight Tutorial Videos (YouTube) ResInsight Tutorials ResInsight Help Menu ResInsight Help menu options are:
+About &amp;ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.</description>
     </item>
     
     <item>
@@ -529,8 +524,8 @@ Importing such a file will enable result type called SourSimRL as explained in E
       
       <guid>https://resinsight.org/misc/advancedtextinput/</guid>
       <description>When the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.
-Supported text format 5,10-13,20-26:2This text will produce an integer array with values
-[5, 10, 11, 12, 13, 20, 22, 24, 26]Using the syntax &amp;ldquo;20-26:2&amp;rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]</description>
+Supported text format 5,10-13,20-26:2 This text will produce an integer array with values
+[5, 10, 11, 12, 13, 20, 22, 24, 26] Using the syntax &amp;ldquo;20-26:2&amp;rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]</description>
     </item>
     
     <item>
@@ -543,7 +538,7 @@ Supported text format 5,10-13,20-26:2This text will produce an integer array wi
 In a git enabled shell do: git clone https://github.com/OPM/ResInsight.git
 Dependencies and Prerequisites Windows Compiler Visual Studio 2019 and later is supported.
 GCC Compiler On RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with
-source /opt/rh/devtoolset-10/enable Qt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.
+source /opt/rh/devtoolset-10/enableQt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.
 Qt download
 On some configurations you will be asked to specify the location of Qt.</description>
     </item>
@@ -554,9 +549,11 @@ On some configurations you will be asked to specify the location of Qt.</descrip
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/getting-started/download-and-install/build-instructions-ubuntu/</guid>
-      <description>Dependencies and Prerequisites Configuration and build    Tool Minimum version     git 2.7.4   gcc 10   python 3    Update apt installer
-sudo apt update Install GCC and related tools
-sudo apt install build-essentialsudo apt install curl zip unzip tar As gcc 10 is required, it can be useful to set the default compiler. Set default compiler</description>
+      <description>Dependencies and Prerequisites Configuration and build Tool Minimum version git 2.7.4 gcc 10 python 3 Update apt installer
+sudo apt updateInstall GCC and related tools
+sudo apt install build-essentialsudo apt install curl zip unzip tarAs gcc 10 is required, it can be useful to set the default compiler. Set default compiler
+Install Qt
+sudo apt install -y qtbase5-dev libqt5svg5-dev qtbase5-private-devClone and update sub modules git clone git://github.</description>
     </item>
     
     <item>
@@ -567,7 +564,7 @@ sudo apt install build-essentialsudo apt install curl zip unzip tar As gcc 10
       <guid>https://resinsight.org/scripting/commandfile/</guid>
       <description>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.
 It is possible to use these commands directly from a Python script. For further details, please see the ResInsight Python API.
-Command 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.</description>
+Command 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.</description>
     </item>
     
     <item>
@@ -578,7 +575,7 @@ Command List Case Control Commands  openProject closeProject setStartDir loadCas
       <guid>https://resinsight.org/wells-and-completions/createnewwellpaths/</guid>
       <description>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 imported well path.
 Building a multilateral well path
-Building a well path  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 should pass (well path targets) When finished placing targets, click on &amp;ldquo;Stop Picking Targets&amp;rdquo; in the property editor  Well targets property editor fields:</description>
+Building a well path 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 should pass (well path targets) When finished placing targets, click on &amp;ldquo;Stop Picking Targets&amp;rdquo; in the property editor Well targets property editor fields:</description>
     </item>
     
     <item>
@@ -590,7 +587,7 @@ Building a well path  Right click Wells in the project tree Select Create Well P
       <description>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.
 To view the data as a Color Result select the Result Position: Element ( See Geomechanical Results )
 A couple of property names are recognized and treated specially:
- MODULUS &amp;ndash; Scaled by 1.0e-9 and shown as &amp;ldquo;Young&amp;rsquo;s Modulus&amp;rdquo; in the user interface RATIO &amp;ndash; Shown as &amp;ldquo;Poisson&amp;rsquo;s Ratio&amp;rdquo; in the user interface  File Format A couple of examples on the file format are shown below.</description>
+MODULUS &amp;ndash; Scaled by 1.0e-9 and shown as &amp;ldquo;Young&amp;rsquo;s Modulus&amp;rdquo; in the user interface RATIO &amp;ndash; Shown as &amp;ldquo;Poisson&amp;rsquo;s Ratio&amp;rdquo; in the user interface File Format A couple of examples on the file format are shown below.</description>
     </item>
     
     <item>
@@ -601,7 +598,7 @@ A couple of property names are recognized and treated specially:
       <guid>https://resinsight.org/export/fluxnummultnum/</guid>
       <description>The visible cells can be exported as a FLUXNUM or MULTNUM keyword that can be used in an Eclipse input data deck.
 You can do this by using the command Export Visible Cells as FLUXNUM/MULTNUM found by right clicking:
- View in the Project Tree. Cell Result in the Project Tree. In any Eclipse 3D View.  The command can also be found in File -&amp;gt; Export. If the command is used in the project tree, the visible cells from the selected view are used for calculation.</description>
+View in the Project Tree. Cell Result in the Project Tree. In any Eclipse 3D View. The command can also be found in File -&amp;gt; Export. If the command is used in the project tree, the visible cells from the selected view are used for calculation.</description>
     </item>
     
     <item>
@@ -624,7 +621,7 @@ Example using Grid Property Calculator As shown, the Grid Property Calculator is
       <guid>https://resinsight.org/misc/keyboardshortcuts/</guid>
       <description>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.
 Other available keyboard shortcuts are
- 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.</description>
+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.</description>
     </item>
     
     <item>
@@ -636,7 +633,7 @@ Other available keyboard shortcuts are
       <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>
+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>
@@ -647,7 +644,7 @@ These abbreviations are used in the tables below:
       <guid>https://resinsight.org/import/observeddata/</guid>
       <description>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.
 Import Observed Time History Data Importing observed time history data to ResInsight may be performed in two different ways:
- By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Observed Data By using the right-click command Import Observed Data on the Observed Data item in the Plot Main Window Project Tree  The following file types are supported:</description>
+By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Observed Data By using the right-click command Import Observed Data on the Observed Data item in the Plot Main Window Project Tree The following file types are supported:</description>
     </item>
     
     <item>
@@ -657,8 +654,8 @@ Import Observed Time History Data Importing observed time history data to ResIns
       
       <guid>https://resinsight.org/import/pressuredata/</guid>
       <description>Import Pressure/Depth Data Importing pressure data to ResInsight may be performed in two different ways:
- By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree  The imported pressure data can visualized in [RFT Plots]
-Pressure/Depth File Format --TVDMSL RFT --WELLNAME &amp;#39;OP_1&amp;#39;DATE 28-FEB-2000PRESSURE DEPTHBARSA METRES302.</description>
+By selecting the main menu item File -&amp;gt; Import -&amp;gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree The imported pressure data can visualized in [RFT Plots]
+Pressure/Depth File Format --TVDMSL RFT -- WELLNAME &amp;#39;OP_1&amp;#39; DATE 28-FEB-2000 PRESSURE DEPTH BARSA METRES 302.</description>
     </item>
     
     <item>
@@ -669,7 +666,7 @@ Pressure/Depth File Format --TVDMSL RFT --WELLNAME &amp;#39;OP_1&amp;#39;DATE
       <guid>https://resinsight.org/3d-main-window/resultcolorlegend/</guid>
       <description>The color mapping of the displayed cell result is controlled by the Color Legend item in Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Color Legend item.
 Legend configuration As shown above, the Legend configuration for cell results allows the following settings:
- Number of levels &amp;ndash; Defines the number of tick marks displayed next to the color legend Significant digits &amp;ndash; Defines the number of significant digits in the number formatting Number format &amp;ndash; Defines how the numbers are formatted Colors &amp;ndash; Defines the color palette for the legend by selecting from Color Legends Mapping &amp;ndash; Defines the mapping of numerical values to legend colors:  Discrete Linear &amp;ndash; Legend divided into linear levels defined by Number of levels Continuous Linear &amp;ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic &amp;ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic &amp;ndash; Logarithmic legend divided into levels defined by Number of levels Category &amp;ndash; Legend with one level per category for formation names and discrete data (e.</description>
+Number of levels &amp;ndash; Defines the number of tick marks displayed next to the color legend Significant digits &amp;ndash; Defines the number of significant digits in the number formatting Number format &amp;ndash; Defines how the numbers are formatted Colors &amp;ndash; Defines the color palette for the legend by selecting from Color Legends Mapping &amp;ndash; Defines the mapping of numerical values to legend colors: Discrete Linear &amp;ndash; Legend divided into linear levels defined by Number of levels Continuous Linear &amp;ndash; Continuous linear legend with tick mark count defined by Number of levels Continuous Logarithmic &amp;ndash; Continuous logarithmic legend with tick mark count defined by Number of levels Discrete Logarithmic &amp;ndash; Logarithmic legend divided into levels defined by Number of levels Category &amp;ndash; Legend with one level per category for formation names and discrete data (e.</description>
     </item>
     
     <item>
@@ -710,7 +707,7 @@ Standard Color Legends ResInsight offers an extensive set of built-in color lege
       
       <guid>https://resinsight.org/wells-and-completions/createmultilateralwellpaths/</guid>
       <description>ResInsight lets the user create additional well path laterals by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export
-Building a well path  Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral  A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2.</description>
+Building a well path Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2.</description>
     </item>
     
     <item>
@@ -720,7 +717,7 @@ Building a well path  Start from an existing well path, either imported or creat
       
       <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. 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>
+The figure above exemplifies a Comparison View for comparison of two different simulations models and results.</description>
     </item>
     
     <item>
@@ -741,7 +738,7 @@ Creating new 3D Well Log Curves Add a new 3D well log curve by selecting a Well
       <guid>https://resinsight.org/import/appendingadditionalproperties/</guid>
       <description>A grid model can be imported from several sources, either Eclipse binary/ascii or ROFF binary/ascii. Grid properties in separate files can be imported into any grid type as long as the number of grid cells is matching.
 Appending properties
- From the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list.</description>
+From the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list.</description>
     </item>
     
     <item>
@@ -779,7 +776,7 @@ Paste Options Dialog Most of the fields in this dialog are the same as in the CS
       
       <guid>https://resinsight.org/misc/regressiontestsystem/</guid>
       <description>A regression tool for QA is build into ResInsight. This tool will do the following:
- 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.</description>
+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.</description>
     </item>
     
     <item>
@@ -800,7 +797,7 @@ Subscribe</description>
       
       <guid>https://resinsight.org/plot-window/summarycrossplots/</guid>
       <description>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:
- 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 right-click command New Summary Cross Plot on the Plot Main Window -&amp;gt; Project Tree -&amp;gt; Summary Cross Plots item.</description>
+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 right-click command New Summary Cross Plot on the Plot Main Window -&amp;gt; Project Tree -&amp;gt; Summary Cross Plots item.</description>
     </item>
     
     <item>
@@ -853,7 +850,7 @@ Completions can be modeled by adding new perforation intervals, fishbones subs o
       <guid>https://resinsight.org/wells-and-completions/ensemblefracturestatistics/</guid>
       <description>Importing Ensemble Fracture Statistics Right-click on Completion Templates &amp;gt; Ensemble Fracture Statistics in the Project Tree and select the Import StimPlan Fracture Recursively option. Then select the StimPlan fracture Xml files to be part of the ensemble.
 After importing the Property Panel of the Ensemble Fracture Statistics item has these options:
- Name &amp;ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures &amp;ndash; Toggle to remove zero width fractures from the statistics.</description>
+Name &amp;ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures &amp;ndash; Toggle to remove zero width fractures from the statistics.</description>
     </item>
     
     <item>
@@ -864,7 +861,7 @@ After importing the Property Panel of the Ensemble Fracture Statistics item has
       <guid>https://resinsight.org/plot-window/ensembleplotting/</guid>
       <description>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.
 Import There are several ways to import an ensemble:
- Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;Import Ensemble Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;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.</description>
+Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;Import Ensemble Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;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.</description>
     </item>
     
     <item>
@@ -885,9 +882,9 @@ In order to show flow vectors, check the checkbox next to Flow Vector Result in
       
       <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.
+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>
+Octave Script Management Octave scripts are available in the Scripts folder in the Project Tree.</description>
     </item>
     
     <item>
@@ -920,7 +917,7 @@ Visualization The tensor arrows visualize the principal vectors in three directi
       <guid>https://resinsight.org/export/exportwellpaths/</guid>
       <description>In order to export well paths to dev files, select the menu item File -&amp;gt; Export -&amp;gt; Export Visible Well Paths or select one or more well paths and then select one of the items in the sub menu Export Well Paths.
 A dialog appears after selecting an export well path command.
- 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 &amp;lt;well name&amp;gt;.</description>
+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 &amp;lt;well name&amp;gt;.</description>
     </item>
     
     <item>
@@ -977,7 +974,7 @@ Alternatively, Correlation Plots can be created by right-clicking the Correlatio
       <description>ResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.
 Create Temporary LGRs To create temporary LGR(s), first select one or more well paths in the project tree, right click and select &amp;lsquo;Create Temporary LGR&amp;rsquo;. This command brings up the following dialog.
 The dialog contains several input fields
- Source Case &amp;ndash; The source case/grid Time Step &amp;ndash; The time step to use Fractures, Fishbones, Perforations &amp;ndash; Check boxes to control which completion types to create LGRs for Split Type &amp;ndash; Three options controlling how the LGRs will be created  LGR Per Cell &amp;ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion &amp;ndash; One LGR is created for each completion of the selected types.</description>
+Source Case &amp;ndash; The source case/grid Time Step &amp;ndash; The time step to use Fractures, Fishbones, Perforations &amp;ndash; Check boxes to control which completion types to create LGRs for Split Type &amp;ndash; Three options controlling how the LGRs will be created LGR Per Cell &amp;ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion &amp;ndash; One LGR is created for each completion of the selected types.</description>
     </item>
     
     <item>
@@ -1021,7 +1018,7 @@ Exporting Grid and Faults Grid Export The Export dialog will allow the user to e
       <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;quot;</description>
+&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>
     
     <item>
@@ -1031,9 +1028,9 @@ Senior Petroleum Engineering Advisor, RPS Energy
       
       <guid>https://resinsight.org/3d-main-window/filters/</guid>
       <description>Filters are used to control the visibility of cells in the 3D view. Two types of filters exist:
- Cell Filter &amp;ndash; Extracts subset(s) of grid cells Property Filter &amp;ndash; Extracts cells with a property value matching a value range  The visibility of cells connected to wells, and fences can be controlled from  Simulation Wells.
+Cell Filter &amp;ndash; Extracts subset(s) of grid cells Property Filter &amp;ndash; Extracts cells with a property value matching a value range The visibility of cells connected to wells, and fences can be controlled from Simulation Wells.
 (Not applicable for Geomechanical cases)
-Common Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor.</description>
+Common Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor.</description>
     </item>
     
     <item>
@@ -1044,7 +1041,7 @@ Senior Petroleum Engineering Advisor, RPS Energy
       <guid>https://resinsight.org/plot-window/welllogsandplots/</guid>
       <description>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.
 Well Log Plots Well log plots can be created in several ways:
- Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.
+Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.
 A new plot with a single Track and Curve is created matching active case and selected Well trajectory.</description>
     </item>
     
@@ -1056,8 +1053,7 @@ A new plot with a single Track and Curve is created matching active case and sel
       <guid>https://resinsight.org/wells-and-completions/wellmeasurements/</guid>
       <description>ResInsight can import well measurements from a comma-separated values file.
 Importing Well Measurements The command File -&amp;gt; Import -&amp;gt; Well Data -&amp;gt; Import Measurements will read well measurements from the selected files, and create one entry for each file under the Wells -&amp;gt; Well Measurements item in the Project Tree.
-File Format The format is comma-separated values with one measurement per line. The following requirements have to be met:
- Each data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment.</description>
+File Format The format is comma-separated values with one measurement per line. The following requirements have to be met:</description>
     </item>
     
     <item>
@@ -1078,7 +1074,7 @@ Origins J.J. Arps [1] concluded that the decline in oil production rate ($q_i$)
       
       <guid>https://resinsight.org/3d-main-window/intersections/</guid>
       <description>Intersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. There are two main types of intersections:
-  Intersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.</description>
+Intersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.</description>
     </item>
     
     <item>
@@ -1100,7 +1096,7 @@ $$ y = a + bx $$</description>
       <guid>https://resinsight.org/plot-window/wellborestabilityplots/</guid>
       <description>ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots to visualize Formations, Well Measurements, Well Path Attributes as well as a set of well path derived curves in different tracks.
 In the figure above, the first track contains Formations and an indication of sea level.
-   Sea Level Formations          The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions</description>
+Sea Level Formations The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions</description>
     </item>
     
     <item>
@@ -1112,7 +1108,7 @@ In the figure above, the first track contains Formations and an indication of se
       <description>Creating a Seismic Section Import of data is described in Seismic Data
 Seismic Sections are cross sections that cut a grid model in various ways to display seismic data. A Seismic Section is created by right-clicking the Seismic Section item in Project Tree
 The following types of Seismic Sections are available:
- Inline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired.</description>
+Inline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired.</description>
     </item>
     
     <item>
@@ -1133,8 +1129,8 @@ Imported surfaces are listed under the entry in the Project Tree. You can click
       
       <guid>https://resinsight.org/3d-main-window/allandiagrams/</guid>
       <description>Allan Diagrams displays the overlap of formations and layers across fault faces.
-Separate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults  for more details.
-Property Editor Settings  Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault  Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault.</description>
+Separate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults for more details.
+Property Editor Settings Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault.</description>
     </item>
     
     <item>
@@ -1146,7 +1142,7 @@ Property Editor Settings  Binary Formation Allan One color for all NNC areas wit
       <description>Background
 The Biot porelastic coefficient defines the compressibility of sand grains, and will influence some of the calculations in ResInsight.
 Description The Biot coefficient can be defined in three ways:
- Default (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table  These settings are controlled from the Property Editor when a Geomechanical Case is selected.</description>
+Default (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table These settings are controlled from the Property Editor when a Geomechanical Case is selected. To use Biot coefficients for each element, perform the following steps:</description>
     </item>
     
     <item>
@@ -1156,7 +1152,7 @@ Description The Biot coefficient can be defined in three ways:
       
       <guid>https://resinsight.org/workflows/ensemblesurface/</guid>
       <description>Introduction To study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of Ensemble Surfaces. See Python Examples for more details.
-Create Ensemble Surface   From the right-click menu of surfaces, select Import Ensemble Surface   Select the ensemble grid models to create surfaces for, either &amp;quot;*.</description>
+Create Ensemble Surface From the right-click menu of surfaces, select Import Ensemble Surface Select the ensemble grid models to create surfaces for, either &amp;quot;*.</description>
     </item>
     
     <item>
@@ -1166,7 +1162,7 @@ Create Ensemble Surface   From the right-click menu of surfaces, select Import E
       
       <guid>https://resinsight.org/workflows/ensemblewelllog/</guid>
       <description>Introduction To study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.
-Workflow   From the right-click menu of Wells, select Create Ensemble Well Log   In the ensemble import dialog, select the files for import into ensembles   Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files   Click OK when you are ready</description>
+Workflow From the right-click menu of Wells, select Create Ensemble Well Log In the ensemble import dialog, select the files for import into ensembles Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files Click OK when you are ready</description>
     </item>
     
     <item>
@@ -1233,7 +1229,7 @@ Create New Ensemble RFT Plot When a summary ensemble has been imported, observed
       <description>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.
 Formations 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.
 To use this functionality you will need to :
- 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-&amp;gt;Import-&amp;gt;Import Formation Names.</description>
+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-&amp;gt;Import-&amp;gt;Import Formation Names.</description>
     </item>
     
     <item>
@@ -1308,7 +1304,7 @@ $Value_{[t-b]} = Value_{[t]} - Value_{[b]}$</description>
       <guid>https://resinsight.org/3d-main-window/gridstatisticsdialog/</guid>
       <description>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.
 Grid Statistics Dialog Fields The dialog consist of three information parts.
- Info text Histogram Cumulative Histogram  Info Text The Info Text field shows general info about the case, the selected results, and some statistics.</description>
+Info text Histogram Cumulative Histogram Info Text The Info Text field shows general info about the case, the selected results, and some statistics.</description>
     </item>
     
     <item>
@@ -1337,7 +1333,7 @@ The plot utilize the Flow Diagnostics to provide an overview of which well or ph
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/3d-main-window/casegroupsandstatistics/</guid>
-      <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).
+      <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).
 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>
     
@@ -1388,7 +1384,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>
@@ -1426,7 +1422,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: </description>
     </item>
     
     <item>
@@ -1438,8 +1434,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>
     
     <item>
@@ -1448,10 +1443,10 @@ Ceetron Solutions AS - Digitalization and visualization for engineers</descripti
       <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
       
       <guid>https://resinsight.org/training/</guid>
-      <description>ResInsight Introduction Course Content  3D visualization of Eclipse models including faults, intersections, surfaces, and contour maps Eclipse Summary plots, ensemble plots and observed data RFT plots, correlation plots, and analysis plots Flow Diagnostics Linking and comparison of views  Course goals Proficiency in evaluating Eclipse simulation results by 3D visualization and plotting in ResInsight.
+      <description>ResInsight Introduction Course Content 3D visualization of Eclipse models including faults, intersections, surfaces, and contour maps Eclipse Summary plots, ensemble plots and observed data RFT plots, correlation plots, and analysis plots Flow Diagnostics Linking and comparison of views Course goals Proficiency in evaluating Eclipse simulation results by 3D visualization and plotting in ResInsight.
 Prerequisites Knowledge about Eclipse reservoir simulations.
 Notes The course is offered online on both Windows and Linux systems.</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/misc/advancedtextinput/index.html b/misc/advancedtextinput/index.html
index a3874d5898..b3c71b4b32 100644
--- a/misc/advancedtextinput/index.html
+++ b/misc/advancedtextinput/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Advanced Text Input :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2812,10 +2811,10 @@ if (!doNotTrack) {
 
 <p>When the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.</p>
 <h2 id="supported-text-format">Supported text format</h2>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">5,10-13,20-26:2
-</code></pre></div><p>This text will produce an integer array with values</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">[5, 10, 11, 12, 13, 20, 22, 24, 26]
-</code></pre></div><p>Using the syntax <strong>&ldquo;20-26:2&rdquo;</strong> will produce integer values in the range at a step of 2, resulting in <strong>[20, 22, 24, 26]</strong></p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>5,10-13,20-26:2
+</span></span></code></pre></div><p>This text will produce an integer array with values</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>[5, 10, 11, 12, 13, 20, 22, 24, 26]
+</span></span></code></pre></div><p>Using the syntax <strong>&ldquo;20-26:2&rdquo;</strong> will produce integer values in the range at a step of 2, resulting in <strong>[20, 22, 24, 26]</strong></p>
 
 
 <footer class="footline">
@@ -4949,19 +4948,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/index.html b/misc/index.html
index 3e8d9582c8..89ee6fede2 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Miscellaneous :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2371,7 +2371,7 @@
   
     
     <li data-nav-id="/misc/" title="Miscellaneous" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4938,19 +4937,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/index.xml b/misc/index.xml
index 3bcee62f71..9d03f0a468 100644
--- a/misc/index.xml
+++ b/misc/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/misc/</link>
     <description>Recent content in Miscellaneous on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/misc/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/misc/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Preferences</title>
       <link>https://resinsight.org/misc/preferences/</link>
@@ -57,8 +53,8 @@ Memory Indicator The tools are available from the memory indicator in the bottom
       
       <guid>https://resinsight.org/misc/advancedtextinput/</guid>
       <description>When the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.
-Supported text format 5,10-13,20-26:2This text will produce an integer array with values
-[5, 10, 11, 12, 13, 20, 22, 24, 26]Using the syntax &amp;ldquo;20-26:2&amp;rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]</description>
+Supported text format 5,10-13,20-26:2 This text will produce an integer array with values
+[5, 10, 11, 12, 13, 20, 22, 24, 26] Using the syntax &amp;ldquo;20-26:2&amp;rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]</description>
     </item>
     
     <item>
@@ -69,7 +65,7 @@ Supported text format 5,10-13,20-26:2This text will produce an integer array wi
       <guid>https://resinsight.org/misc/keyboardshortcuts/</guid>
       <description>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.
 Other available keyboard shortcuts are
- 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.</description>
+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.</description>
     </item>
     
     <item>
@@ -79,8 +75,8 @@ Other available keyboard shortcuts are
       
       <guid>https://resinsight.org/misc/regressiontestsystem/</guid>
       <description>A regression tool for QA is build into ResInsight. This tool will do the following:
- 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.</description>
+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.</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/misc/keyboardshortcuts/index.html b/misc/keyboardshortcuts/index.html
index 7bff22afeb..9b17ce513a 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Keyboard Shortcuts :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4987,19 +4986,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/memorymanagement/index.html b/misc/memorymanagement/index.html
index 9a885e7e6f..96273efb0c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Memory Management :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4954,19 +4953,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/preferences/index.html b/misc/preferences/index.html
index eb586db02c..908c977ca0 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Preferences :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5078,19 +5077,19 @@ Essential preferences are listed below.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/projectfile/index.html b/misc/projectfile/index.html
index ab64c36dcf..efb9e196f3 100644
--- a/misc/projectfile/index.html
+++ b/misc/projectfile/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Project File and Caching :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2785,6 +2784,8 @@ if (!doNotTrack) {
         <li>
           <ul>
             <li><a href="#the-project-file">The Project File</a></li>
+            <li><a href="#external-file-references">External File References</a></li>
+            <li><a href="#the-cache-directory">The Cache Directory</a></li>
           </ul>
         </li>
       </ul>
@@ -2815,24 +2816,24 @@ if (!doNotTrack) {
 
 
 <h3 id="the-project-file">The Project File</h3>
-<p>ResInsight stores all views and settings in a <strong>Project File</strong> with the extension <em><code>*.rsp</code></em> to easily continue work in a subsequent session. 
-This file only contains <em>references</em> to the real data files, and does not in any way copy the data itself. 
+<p>ResInsight stores all views and settings in a <strong>Project File</strong> with the extension <em><code>*.rsp</code></em> to easily continue work in a subsequent session.
+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 by the Project File.</p>
 
 <div class="notices note" ><p>The <code>*.rsp</code> file is an XML file, and can be edited by any text editor.</p>
+</div>
+
 </div>
 <h3 id="external-file-references">External File References</h3>
 <p>Editing the <strong>Project File</strong> is one effective way to replace source cases and other file references. At top of a <strong>Project File</strong>, the section <strong>ReferencedExternalFiles</strong> contains aliases to file paths which can be modified using a text editor. It is also possible to use automated tools to modify these text strings.</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">&lt;ReferencedExternalFiles&gt;
-    $PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID;
-    $PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb;
-    $PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC;
-    $PathId_004$ D:/resinsight-data/summary_templates;
-&lt;/ReferencedExternalFiles&gt;
-</code></pre></div><h3 id="the-cache-directory">The Cache Directory</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>&lt;ReferencedExternalFiles&gt;
+</span></span><span style="display:flex;"><span>    $PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID;
+</span></span><span style="display:flex;"><span>    $PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb;
+</span></span><span style="display:flex;"><span>    $PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC;
+</span></span><span style="display:flex;"><span>    $PathId_004$ D:/resinsight-data/summary_templates;
+</span></span><span style="display:flex;"><span>&lt;/ReferencedExternalFiles&gt;
+</span></span></code></pre></div><h3 id="the-cache-directory">The Cache Directory</h3>
 <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>
-
 
 
 <footer class="footline">
@@ -4966,19 +4967,19 @@ Data files generated by ResInsight are also referenced by the Project File.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/regressiontestsystem/index.html b/misc/regressiontestsystem/index.html
index 82adf8227f..e2207edea1 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Regression Test System :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4977,19 +4976,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/misc/windowmanagement/index.html b/misc/windowmanagement/index.html
index 3871be76b4..adf03dd4e4 100644
--- a/misc/windowmanagement/index.html
+++ b/misc/windowmanagement/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Window Management :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4968,19 +4967,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/analysisplots/index.html b/plot-window/analysisplots/index.html
index 5f6dd6afc8..16b4caa505 100644
--- a/plot-window/analysisplots/index.html
+++ b/plot-window/analysisplots/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Analysis Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2821,7 +2820,7 @@ if (!doNotTrack) {
 <p><img src="/images/plot-window/AnalysisPlotsEnsemble.png" alt=""></p>
 <p>Analysis Plots are bar charts used to compare summary data at specific timesteps across <em>Ensembles</em> and <em>Summary Cases</em>.</p>
 <h2 id="creating-an-analysis-plot">Creating an Analysis Plot</h2>
-<p>The most convenient way to create an Analysis Plot at a given time step is often to right-click an 
+<p>The most convenient way to create an Analysis Plot at a given time step is often to right-click an
 <a href="/plot-window/ensembleplotting/">Ensemble Plot</a> and invoke <em>New Analysis Plot</em> as shown below.</p>
 <p><img src="/images/plot-window/AnalysisPlotsCreateFromEnsemblePlot.png" alt=""></p>
 <p>Alternatively, Analysis Plots can be created by right-clicking the <strong>Analysis Plots</strong> item in <strong>Plot Project Tree</strong>.</p>
@@ -2830,7 +2829,7 @@ if (!doNotTrack) {
 <h2 id="specifying-setup-and-settings">Specifying Setup and Settings</h2>
 <p>The Analysis Plots property editor allows the user to specify a number of settings and optionally select a reference case in order to analyse vector data relatively to that particular case. The property editor groups further setup and settings as listed below.</p>
 <h3 id="selected-vectors">Selected Vectors</h3>
-<p>The summary data to analyze is selected by a set of summary vectors. 
+<p>The summary data to analyze is selected by a set of summary vectors.
 Press the available button to activate the <strong>Summary Adress Selection</strong> dialog to select a set of vectors from different ensembles,
 summary types and summaries.</p>
 <p><img src="/images/plot-window/AnalysisPlotsSelectedVectors.png" alt=""></p>
@@ -4984,19 +4983,19 @@ summary types and summaries.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/correlationplots/index.html b/plot-window/correlationplots/index.html
index 842616dc81..8c02e338f9 100644
--- a/plot-window/correlationplots/index.html
+++ b/plot-window/correlationplots/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Correlation Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2822,7 +2821,7 @@ if (!doNotTrack) {
 <p>Correlation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors.
 Several visualizations can be created, including tornado plots, correlation matrices, and cross plots.</p>
 <h2 id="creating-a-correlation-plot">Creating a Correlation Plot</h2>
-<p>The most convenient way to create a Correlation Plot at a given time step is often to right-click an 
+<p>The most convenient way to create a Correlation Plot at a given time step is often to right-click an
 <a href="/plot-window/ensembleplotting/">Ensemble Plot</a> and invoke the submenu shown below.</p>
 <p><img src="/images/plot-window/CorrelationPlotsCreateFromEnsemblePlot.png" alt=""></p>
 <p>Alternatively, Correlation Plots can be created by right-clicking the <strong>Correlation Plots</strong> item in <strong>Plot Project Tree</strong>.</p>
@@ -2834,7 +2833,7 @@ Several visualizations can be created, including tornado plots, correlation matr
 Being irrelevant, please note that the section will not display for <em>Correlation Cross Plots</em> and that the field <em>Sort Matrix by Values</em> will not display for tornado plots.</p>
 <p><img src="/images/plot-window/CorrelationPlotsCorrFactorSettings.png" alt=""></p>
 <h3 id="summary-vector-settings">Summary Vector Settings</h3>
-<p>This section of the property editor allows for setting summary vector(s) and time step. 
+<p>This section of the property editor allows for setting summary vector(s) and time step.
 To ease the selection of time step, the <em>Time Step Filter</em> may be used to skip time steps by years, quarters, months, weeks, or days.</p>
 <p><img src="/images/plot-window/CorrelationPlotsSummaryVectorSettings.png" alt=""></p>
 <h3 id="plot-settings">Plot Settings</h3>
@@ -4977,19 +4976,19 @@ Please note that the <em>Colors</em> setting for specifying legend is irrelevant
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/curvecalculator/index.html b/plot-window/curvecalculator/index.html
index cdcfb81f6c..0b29aa512e 100644
--- a/plot-window/curvecalculator/index.html
+++ b/plot-window/curvecalculator/index.html
@@ -1 +1,10 @@
-<!DOCTYPE html><html><head><title>https://resinsight.org/calculated-data/curvecalculator/</title><link rel="canonical" href="https://resinsight.org/calculated-data/curvecalculator/"/><meta name="robots" content="noindex"><meta charset="utf-8" /><meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/curvecalculator/" /></head></html>
\ No newline at end of file
+<!DOCTYPE html>
+<html lang="en-us">
+  <head>
+    <title>https://resinsight.org/calculated-data/curvecalculator/</title>
+    <link rel="canonical" href="https://resinsight.org/calculated-data/curvecalculator/">
+    <meta name="robots" content="noindex">
+    <meta charset="utf-8">
+    <meta http-equiv="refresh" content="0; url=https://resinsight.org/calculated-data/curvecalculator/">
+  </head>
+</html>
diff --git a/plot-window/declinecurveanalysis/index.html b/plot-window/declinecurveanalysis/index.html
index 9e28f07031..72c7d23d75 100644
--- a/plot-window/declinecurveanalysis/index.html
+++ b/plot-window/declinecurveanalysis/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Decline Curve Analysis :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5019,19 +5018,19 @@ Arps, J. J.: “Analysis of Decline Curves,” SPE-945228-G, Trans. of the AIME
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/ensembleplotting/index.html b/plot-window/ensembleplotting/index.html
index 667902466c..230d0e3d7d 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble Plotting :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2862,15 +2861,15 @@ if (!doNotTrack) {
 </ul>
 <p>Statistics curves may be toggled on or off in the curve set&rsquo;s property editor.</p>
 <h2 id="delta-ensemble">Delta Ensemble</h2>
-<p>A new ensemble can be created based on calculations on two or more ensembles. 
-Such an ensemble is called an <strong>Delta Ensemble</strong>. 
-A delta ensemble will contain data which are either the sum or difference between two other ensembles. 
+<p>A new ensemble can be created based on calculations on two or more ensembles.
+Such an ensemble is called an <strong>Delta Ensemble</strong>.
+A delta ensemble will contain data which are either the sum or difference between two other ensembles.
 An existing delta ensemble may be input to a new delta ensemble, making it possible to, for instance, add more than two ensembles.</p>
-<p>To create a delta ensemble, select two existing ensembles in <strong>Plot Project Tree</strong>, then right-click and select <strong>New Delta Ensemble</strong>. 
-A new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator. 
+<p>To create a delta ensemble, select two existing ensembles in <strong>Plot Project Tree</strong>, then right-click and select <strong>New Delta Ensemble</strong>.
+A new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator.
 In the property for the delta ensemble, both input ensembles and operator can be modified.
-Checking <em>Match On Parameters</em> ensures strict match on ensemble parameters. 
-In addition, it is possible to specify a fixed time step to be used in delta computation, see 
+Checking <em>Match On Parameters</em> ensures strict match on ensemble parameters.
+In addition, it is possible to specify a fixed time step to be used in delta computation, see
 <a href="/plot-window/summaryplots/#delta-summary-case">Delta Summary Case</a> for an example.</p>
 <p><img src="/images/plot-window/DeltaEnsemblePropertyEditor.png" alt=""></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 delta ensemble or not.</p>
@@ -5007,19 +5006,19 @@ In addition, it is possible to specify a fixed time step to be used in delta com
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/ensemblerftplot/index.html b/plot-window/ensemblerftplot/index.html
index b752ca0dca..52c7922d73 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble RFT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2826,12 +2825,12 @@ 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>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>To create ensemble RFT plot, right-click <strong>RFT Plots</strong> and select <strong>New RFT Plot</strong>.</p>
@@ -2840,7 +2839,7 @@ and selecting <strong>Import Observed FMU Data</strong>.</p>
 <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>
 <h3 id="well-name">Well Name</h3>
-<p>Select the well to display in the plot. Wells postfixed by <em>'(Well Path)'</em> have an associated well trajectory loaded.</p>
+<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>
 <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>
@@ -2890,32 +2889,32 @@ Please see the <a href="/3d-main-window/formations/">full documentation</a> of t
 </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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">1   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
-</code></pre></div><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. 
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>1   UpperReek
+</span></span><span style="display:flex;"><span>2   UpperReek
+</span></span><span style="display:flex;"><span>3   UpperReek
+</span></span><span style="display:flex;"><span>4   UpperReek
+</span></span><span style="display:flex;"><span>5   UpperReek
+</span></span><span style="display:flex;"><span>6   MidReek
+</span></span><span style="display:flex;"><span>7   MidReek
+</span></span><span style="display:flex;"><span>8   MidReek
+</span></span><span style="display:flex;"><span>9   MidReek
+</span></span><span style="display:flex;"><span>10  MidReek
+</span></span><span style="display:flex;"><span>11  LowerReek
+</span></span><span style="display:flex;"><span>12  LowerReek
+</span></span><span style="display:flex;"><span>13  LowerReek
+</span></span><span style="display:flex;"><span>14  LowerReek
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">303.000   3.000
-304.000   3.000
-305.000   3.000
-</code></pre></div><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. 
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>303.000   3.000
+</span></span><span style="display:flex;"><span>304.000   3.000
+</span></span><span style="display:flex;"><span>305.000   3.000
+</span></span></code></pre></div><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>
@@ -2925,10 +2924,10 @@ Each line of data must contain:</p>
 <li>Reservoir zone name</li>
 </ul>
 <p>Example file for well <em>OP_1</em>, i.e. <em>OP_1.txt</em>:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">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></div><h4 id="well-measurements">Well measurements</h4>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>461288.719   5933415.000   1816.200   1611.692   UpperReek
+</span></span><span style="display:flex;"><span>461288.685   5933415.027   1824.560   1620.052   MidReek
+</span></span><span style="display:flex;"><span>461288.683   5933415.029   1840.000   1635.492   LowerReek
+</span></span></code></pre></div><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>
@@ -2939,12 +2938,12 @@ Each line of data must contain:</p>
 </ul>
 <p>There can be multiple measurement for each well.</p>
 <p>Example file <em>well_date_rft.txt</em>:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">OP_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
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>OP_1   01 02 2000   1
+</span></span><span style="display:flex;"><span>OP_2   01 02 2000   1
+</span></span><span style="display:flex;"><span>OP_4   01 01 2001   1
+</span></span><span style="display:flex;"><span>WI_1   01 02 2000   1
+</span></span><span style="display:flex;"><span>WI_3   01 03 2001   1
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5077,19 +5076,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/flow-diagnostics-plots/index.html b/plot-window/flow-diagnostics-plots/index.html
index 5fbbaba10a..5acb01b43a 100644
--- a/plot-window/flow-diagnostics-plots/index.html
+++ b/plot-window/flow-diagnostics-plots/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Flow Diagnostics Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -1391,7 +1391,7 @@
   
     
     <li data-nav-id="/plot-window/flow-diagnostics-plots/" title="Flow Diagnostics Plots" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2860,7 +2859,7 @@ Multi Segment Wells will be displayed according to their branch information, but
 <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>
@@ -2883,8 +2882,8 @@ supported by other wells ( This option is only available for cases with Flux res
 <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 
+<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>
@@ -5103,19 +5102,19 @@ For producer B-2H, for instance, such a plot can be created by right-clicking it
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/flow-diagnostics-plots/index.xml b/plot-window/flow-diagnostics-plots/index.xml
index 2b96855dea..37fb64dea8 100644
--- a/plot-window/flow-diagnostics-plots/index.xml
+++ b/plot-window/flow-diagnostics-plots/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/plot-window/flow-diagnostics-plots/</link>
     <description>Recent content in Flow Diagnostics Plots on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/plot-window/flow-diagnostics-plots/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/plot-window/flow-diagnostics-plots/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Producer/Injector Connectivity Tables</title>
       <link>https://resinsight.org/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/</link>
@@ -31,4 +27,4 @@ The plot utilize the Flow Diagnostics to provide an overview of which well or ph
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/index.html b/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/index.html
index d2aa346e28..7e4730efa2 100644
--- a/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/index.html
+++ b/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Producer/Injector Connectivity Tables :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5025,19 +5024,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/index.html b/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/index.html
index 873f6d5e6c..c0d09c3993 100644
--- a/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/index.html
+++ b/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Allocation Over Time Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4998,19 +4997,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/gridcrossplots/index.html b/plot-window/gridcrossplots/index.html
index 0ee3e8ebbf..1f84ff5e6a 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Cross Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5023,19 +5022,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/gridstatisticsplots/index.html b/plot-window/gridstatisticsplots/index.html
index f59036a6d4..2a5413fb88 100644
--- a/plot-window/gridstatisticsplots/index.html
+++ b/plot-window/gridstatisticsplots/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Grid Statistics Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4953,19 +4952,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/index.html b/plot-window/index.html
index d0a73f1c36..2a277408a2 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Plot Main Window :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -927,7 +927,7 @@
   
     
     <li data-nav-id="/plot-window/" title="Plot Main Window" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2809,7 +2808,7 @@ overview, management and use of templates for summary plotting</li>
 <li><a href="/plot-window/summaryplotmanager/"><strong>Plot Manager</strong></a>:
 powerful text-based selection of vectors for summary plotting</li>
 </ul>
-<p>Essential actions are presented as controls in the toolbar for ease of use. 
+<p>Essential actions are presented as controls in the toolbar for ease of use.
 The following subchapters describe the capabilities, functionality, graphs, and plots in more detail.</p>
 
 
@@ -4943,19 +4942,19 @@ The following subchapters describe the capabilities, functionality, graphs, 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/index.xml b/plot-window/index.xml
index 8bd608daa2..6332bcb3cd 100644
--- a/plot-window/index.xml
+++ b/plot-window/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/plot-window/</link>
     <description>Recent content in Plot Main Window on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/plot-window/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/plot-window/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Summary Plots</title>
       <link>https://resinsight.org/plot-window/summaryplots/</link>
@@ -50,7 +46,7 @@ The user writes a text string defining the summary vectors and optionally data s
       <description>Summary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes. Source stepping is available from both the Source Stepping Toolbar and the Property editor as described below.
 Source Stepping using the toolbar The toolbar for source stepping is:
 Following this example, the available options are:
- Explicitly setting Step By to vector WBHP by  Change existing plot to display previous or next vector by pressing one of the buttons  Step previous or next vector and add a plot by the buttons  Step previous or next vector and add a curve by the buttons   Source Stepping using the Property Editor Source Stepping is also available through the Property Editor.</description>
+Explicitly setting Step By to vector WBHP by Change existing plot to display previous or next vector by pressing one of the buttons Step previous or next vector and add a plot by the buttons Step previous or next vector and add a curve by the buttons Source Stepping using the Property Editor Source Stepping is also available through the Property Editor.</description>
     </item>
     
     <item>
@@ -71,7 +67,7 @@ Here highlighted means marked item with different background color, while select
       
       <guid>https://resinsight.org/plot-window/summarycrossplots/</guid>
       <description>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:
- 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 right-click command New Summary Cross Plot on the Plot Main Window -&amp;gt; Project Tree -&amp;gt; Summary Cross Plots item.</description>
+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 right-click command New Summary Cross Plot on the Plot Main Window -&amp;gt; Project Tree -&amp;gt; Summary Cross Plots item.</description>
     </item>
     
     <item>
@@ -114,7 +110,7 @@ The currenly supported types of plots to be part of a Multi Plot are:</descripti
       <guid>https://resinsight.org/plot-window/ensembleplotting/</guid>
       <description>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.
 Import There are several ways to import an ensemble:
- Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;Import Ensemble Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;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.</description>
+Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;Import Ensemble Use menu option File-&amp;gt;Import-&amp;gt;Summary Cases-&amp;gt;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.</description>
     </item>
     
     <item>
@@ -170,7 +166,7 @@ Alternatively, Correlation Plots can be created by right-clicking the Correlatio
       <guid>https://resinsight.org/plot-window/welllogsandplots/</guid>
       <description>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.
 Well Log Plots Well log plots can be created in several ways:
- Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.
+Right-click a well path or a simulation well in the 3D-view and select New Well Log Extraction Curve.
 A new plot with a single Track and Curve is created matching active case and selected Well trajectory.</description>
     </item>
     
@@ -204,7 +200,7 @@ $$ y = a + bx $$</description>
       <guid>https://resinsight.org/plot-window/wellborestabilityplots/</guid>
       <description>ResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots to visualize Formations, Well Measurements, Well Path Attributes as well as a set of well path derived curves in different tracks.
 In the figure above, the first track contains Formations and an indication of sea level.
-   Sea Level Formations          The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions</description>
+Sea Level Formations The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions</description>
     </item>
     
     <item>
@@ -280,4 +276,4 @@ To create these plots, right click on the view in the Property Editor, and selec
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/plot-window/multiplots/index.html b/plot-window/multiplots/index.html
index cda0306ccb..6c647a7278 100644
--- a/plot-window/multiplots/index.html
+++ b/plot-window/multiplots/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Multi Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4967,19 +4966,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/objectivefunctions/index.html b/plot-window/objectivefunctions/index.html
index 43938b4e6c..486e971b85 100644
--- a/plot-window/objectivefunctions/index.html
+++ b/plot-window/objectivefunctions/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Objective Functions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4981,19 +4980,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/pltplot/index.html b/plot-window/pltplot/index.html
index 59f9c11175..bba405981c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>PLT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5084,19 +5083,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/regressionanalysis/index.html b/plot-window/regressionanalysis/index.html
index d7eeb2b73b..de05d64cc0 100644
--- a/plot-window/regressionanalysis/index.html
+++ b/plot-window/regressionanalysis/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Regression Analysis :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5011,19 +5010,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/rftplot/index.html b/plot-window/rftplot/index.html
index 159a1b1302..73db4e0a7f 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>RFT Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2847,7 +2846,7 @@ if (!doNotTrack) {
 <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>
 <h3 id="well-name">Well Name</h3>
-<p>Select the well to display in the plot. Wells postfixed by <em>'(Well Path)'</em> have an associated well trajectory loaded.</p>
+<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>
 <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>
@@ -5045,19 +5044,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/rftsegmentplot/index.html b/plot-window/rftsegmentplot/index.html
index 04e8e97afa..020b742835 100644
--- a/plot-window/rftsegmentplot/index.html
+++ b/plot-window/rftsegmentplot/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>RFT Segment Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4989,19 +4988,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/saturationpressureplots/index.html b/plot-window/saturationpressureplots/index.html
index 30a4b3db51..5f78a44580 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Saturation Pressure Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4940,19 +4939,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summarycrossplots/index.html b/plot-window/summarycrossplots/index.html
index df79d4c41e..76a5a48a27 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Cross Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4965,19 +4964,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplotdatasources/index.html b/plot-window/summaryplotdatasources/index.html
index 712b6f2b7e..87401bdc64 100644
--- a/plot-window/summaryplotdatasources/index.html
+++ b/plot-window/summaryplotdatasources/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Data Sources :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2829,7 +2828,7 @@ See <a href="/plot-window/summaryplots/">Summary Plots</a> which illustrates use
 <p><img src="/images/plot-window/DataSourcesSummaryCase.png" alt=""></p>
 <h3 id="delta-summary-case-and-delta-ensemble">Delta Summary Case and Delta Ensemble</h3>
 <p>A <strong>Delta Summary Case</strong> or <strong>Delta Ensemble</strong> can be created as either the sum or difference between two existing summary cases or ensembles, respectively.</p>
-<p>To create a delta summary case, for instance, right click and select <strong>New Delta Summary Case</strong>. 
+<p>To create a delta summary case, for instance, right click and select <strong>New Delta Summary Case</strong>.
 The Property Editor for the new delta case allows to modify display name, the two base summary cases, and the arithmetic operator.
 In addition, it is possible to specify a specific time step to be used in delta computation.
 As exemplified below, the delta computation between two cases for a given parameter, e.g. <em>WBHP</em>, will be:
@@ -4978,19 +4977,19 @@ is a tool to perform vector calculations on a set of curves. The created curves
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryploteditor/index.html b/plot-window/summaryploteditor/index.html
index 284a014a44..f583f25988 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Editor :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5018,19 +5017,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplotmanager/index.html b/plot-window/summaryplotmanager/index.html
index ac75f7827f..42e36930de 100644
--- a/plot-window/summaryplotmanager/index.html
+++ b/plot-window/summaryplotmanager/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Manager :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5020,19 +5019,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplots/index.html b/plot-window/summaryplots/index.html
index ee256974a6..b1467a7beb 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2837,13 +2836,13 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/plot-window/SummaryPlotsMain.png" alt=""></p>
-<p>Summary Plots are a display of curves based on 
+<p>Summary Plots are a display of curves based on
 <a href="/import/eclipsesummarydata/">Eclipse Summary Data</a>
-which can be combined with 
-<a href="/import/observeddata/">imported observed data</a>, 
-<a href="/3d-main-window/resultinspection/#result-plot">grid cell time history curve</a>, and 
+which can be combined with
+<a href="/import/observeddata/">imported observed data</a>,
+<a href="/3d-main-window/resultinspection/#result-plot">grid cell time history curve</a>, and
 <a href="/import/pasteexceltimedata/">pasted ascii curves</a>.</p>
-<p>Summary plots are displayed on screen by maximum four rows by four columns of plots. 
+<p>Summary plots are displayed on screen by maximum four rows by four columns of plots.
 In the example above, ResInsight displays two columns and two rows of plots, each plot comprising a single curve. However, a plot may contain an arbitrary number of curves.
 As shown in the screenshot above, essential helpers for setup of Summary Plots are:</p>
 <ul>
@@ -2865,12 +2864,12 @@ powerful text-based selection of vectors for summary plotting</li>
 <li><em>Right-click</em> selected vector(s) and select <strong>New Summary Plot</strong></li>
 <li><em>Drag &amp; Drop</em> additional vector(s) to append curves into an existing plot or vacant plot area</li>
 </ul>
-<p>Creating a new summary plot of <em>WBHP</em> of <em>Well B-1H</em> and subsequent <em>Drag &amp; Drop</em> of WGOR and WGORH into the same subplot produces the following. 
+<p>Creating a new summary plot of <em>WBHP</em> of <em>Well B-1H</em> and subsequent <em>Drag &amp; Drop</em> of WGOR and WGORH into the same subplot produces the following.
 ResInsight will automatically make new axes if necessary. If units are the same as for WGOR and WGORH, a new axis is unnecessary.</p>
 <p><img src="/images/plot-window/SummaryPlots_WBHP_WGOR.png" alt=""></p>
 <h3 id="using-plot-manager-to-create-summary-plots">Using Plot Manager to create Summary Plots</h3>
-<p>Having imported <a href="/import/eclipsesummarydata/">Eclipse Summary Data</a>, the 
-<a href="/plot-window/summaryplotmanager/"><strong>Plot Manager</strong></a> 
+<p>Having imported <a href="/import/eclipsesummarydata/">Eclipse Summary Data</a>, the
+<a href="/plot-window/summaryplotmanager/"><strong>Plot Manager</strong></a>
 provides an alternative and powerful approach to create Summary Plots by text-based selection of data sources and vectors to plot.</p>
 <h2 id="summary-plots-and-functionality">Summary Plots and Functionality</h2>
 <h3 id="multiple-summary-plots-and-curves">Multiple Summary Plots and Curves</h3>
@@ -2929,7 +2928,7 @@ Use toolbar button <img src="https://resinsight.org/images/plot-window/ZoomAll16
 <p><img src="/images/plot-window/SummaryCurveHighlight.png" alt=""></p>
 <p>Summary curves can also be activated and deactivated by clicking the check-boxes in <strong>Plots</strong> window. See also <strong>Plots</strong> right-click menu items, e.g. <em>On - Others Off</em> which is an effective way to deactivate all curves not selected.</p>
 <h3 id="duplicate-plot-copy-and-paste">Duplicate plot, Copy and Paste</h3>
-<p>An entire summary plot may be duplicated using the toolbar button 
+<p>An entire summary plot may be duplicated using the toolbar button
 <img src="https://resinsight.org/images/plot-window/ToolbarDuplicatePlot.png" style="display:inline; vertical-align:middle; margin:0">
  <strong>Duplicate Plot</strong>.</p>
 <p>Copy and Paste of a summary plot, subplot (see below) or curve is also possible using the <strong>Plots</strong> right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V). This enables pasting a subplot or curve to wherever desired in the the <strong>Plots</strong> tree.</p>
@@ -2939,11 +2938,11 @@ Use toolbar button <img src="https://resinsight.org/images/plot-window/ZoomAll16
 To activate filtering of subplots, click a plot in <strong>Plots</strong> window, set the <em>Y-axis Threshold</em> in Property Editor, and click <em>Apply Filter</em>.</p>
 <p><img src="/images/plot-window/SummaryPlotVisibilityFilter.png" alt=""></p>
 <h3 id="splitting-a-plot-into-subplots">Splitting a plot into subplots</h3>
-<p>A plot with many curves can easily be split into multiple subplots. 
+<p>A plot with many curves can easily be split into multiple subplots.
 Right-click a composite plot in <strong>Plots</strong> and select <strong>Split Into Single Curve Plots</strong> to split  into subplots each comprising one curve.</p>
 <p><img src="/images/plot-window/SummaryPlotSplitIntoSingleCurvePlots.png" alt=""></p>
 <h3 id="accessing-plot-data">Accessing Plot Data</h3>
-<p>Right-clicking a plot in <strong>Plots</strong> window and selecting <strong>Show Plot Data</strong> will open a window containing the plot data as text columns. 
+<p>Right-clicking a plot in <strong>Plots</strong> window and selecting <strong>Show Plot Data</strong> will open a window containing the plot data as text columns.
 The window displays plot data 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 by the right-click command <strong>Export to File</strong>.</p>
@@ -2978,11 +2977,11 @@ It is also possible to save the text data to a file by the right-click command <
 <ul>
 <li><strong>Title Text</strong>: Caters for automatic or user specification of title and inclusion of vector name, acronym, and units in plot.</li>
 <li><strong>Title Layout</strong>: Positioning of title (<em>Center</em> or <em>At End</em>) and font size.</li>
-<li><strong>Axis Values</strong>: Logarithmic scale, inversion of axis, legend number formatting, scale factor, 
+<li><strong>Axis Values</strong>: Logarithmic scale, inversion of axis, legend number formatting, scale factor,
 max/max range, and font size.</li>
 </ul>
 <h3 id="changing-content-of-a-summary-plot">Changing content of a Summary Plot</h3>
-<p>Right-clicking an existing summary plot in <strong>Plots</strong> and selecting <em>Edit Summary Plot</em> initiates the 
+<p>Right-clicking an existing summary plot in <strong>Plots</strong> and selecting <em>Edit Summary Plot</em> initiates the
 <a href="/plot-window/summaryploteditor/"><em>Summary Plot Editor</em></a> which offers complete functionality to navigate and select vectors from all summary types.</p>
 
 
@@ -5114,19 +5113,19 @@ max/max range, and font size.</li>
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summaryplottemplate/index.html b/plot-window/summaryplottemplate/index.html
index 5ac4842448..4e4e3b0684 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Template :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2815,7 +2814,7 @@ if (!doNotTrack) {
 
 <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 subplots and curves with preset appearance and vector names. 
+<p>A summary plot template is defined by a number of subplots and curves with preset appearance and vector names.
 Having tailored a plot setup, the user can save the setup as a template for later reuse via the <strong>Plots</strong> window right-click command <strong>Save As Plot Template</strong> which pops the <strong>Export Plot Template</strong> dialog seen above.</p>
 <p><img src="/images/plot-window/SummaryPlotTemplateSave.png" alt=""></p>
 <p>A Summary Plot Template can subsequently be used for summary plotting of various data sources. The data sources that can be selected and varied by the user are:</p>
@@ -2823,20 +2822,20 @@ Having tailored a plot setup, the user can save the setup as a template for late
 <li>case(s), ensemble(s), and realization(s)</li>
 <li>well(s), group(s), and region(s)</li>
 </ul>
-<p>When saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions. 
+<p>When saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions.
 On the other hand, expand and check the appropriate boxes if you want to <strong>persist</strong> the specific wells, groups, and/or regions as part of the plot template definition.
 To exemplify, checking <em>Wells</em> for persistence enables plotting of data for the exact wells of the template in conjunction with any ensemble realization.</p>
 <p><img src="/images/plot-window/SummaryPlotTemplateSavePersistentObjectNames.png" alt=""></p>
-<p>Upon export, ResInsight automatically categorizes the template as an <strong>Ensemble Template</strong> if the template involves plotting of data for an ensemble. 
+<p>Upon export, ResInsight automatically categorizes the template as an <strong>Ensemble Template</strong> if the template involves plotting of data for an ensemble.
 Otherwise the template is categorized as a <strong>Summary Case</strong> template.
-Ensemble Templates are listed with the icon 
+Ensemble Templates are listed with the icon
 <img src="https://resinsight.org/images/plot-window/IconEnsembleTemplate.png" style="display:inline; vertical-align:middle; margin:0">
- 
+
 while Summary Case templates are listed with the icon
 <img src="https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png" style="display:inline; vertical-align:middle; margin:0">
 
 in the <a href="/plot-window/summaryplottemplate/#templates-window">Templates Window</a>, c.f. below.</p>
-<p>Each summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by <a href="/misc/preferences/#plotting"><strong>Plotting Preferences</strong></a>. 
+<p>Each summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by <a href="/misc/preferences/#plotting"><strong>Plotting Preferences</strong></a>.
 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>
 <h2 id="template-usage">Template usage</h2>
@@ -2854,7 +2853,7 @@ Then activate the use of default templates by specifying <strong>Use Plot Templa
 <p>As shown, default templates are listed with a green color in their icon.
 Both <img src="https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png" style="display:inline; vertical-align:middle; margin:0">
 <strong>Summary Case templates</strong> and <img src="https://resinsight.org/images/plot-window/IconEnsembleTemplate.png" style="display:inline; vertical-align:middle; margin:0">
-<strong>Ensemble templates</strong> may constitute default templates. 
+<strong>Ensemble templates</strong> may constitute default templates.
 When loading a summary case, the default Summary Case templates will be applied automatically, while default Ensemble templates will be applied automatically when loading an ensemble.</p>
 <h2 id="templates-window">Templates window</h2>
 <p>As seen above, the <strong>Templates</strong> window enables management and overview of summary plot templates by directory and offers the following functionality:</p>
@@ -2862,7 +2861,7 @@ When loading a summary case, the default Summary Case templates will be applied
 <li>create new plot based on selected template</li>
 <li>rename template</li>
 <li>delete template</li>
-<li>edit template XML file in the <em>Script Editor</em> specified in 
+<li>edit template XML file in the <em>Script Editor</em> specified in
 <a href="/misc/preferences/#scripting">Preferences</a></li>
 <li>specifying default template as described above</li>
 <li>reload templates in ResInsight in case of directory or file changes on disk</li>
@@ -5001,19 +5000,19 @@ When loading a summary case, the default Summary Case templates will be applied
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summarysourcestepping/index.html b/plot-window/summarysourcestepping/index.html
index 3d5885bb9f..b2c5c7c407 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Plot Source Stepping :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2821,7 +2820,7 @@ Source stepping is available from both the <strong>Source Stepping Toolbar</stro
 <p><img src="/images/plot-window/SummarySourceSteppingToolbar.png" alt=""></p>
 <p>Following this example, the available options are:</p>
 <ul>
-<li>Explicitly setting <strong>Step By</strong> to vector WBHP by 
+<li>Explicitly setting <strong>Step By</strong> to vector WBHP by
 <img src="https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarExplicit.png" style="display:inline; vertical-align:middle; margin:0">
 </li>
 <li>Change existing plot to display previous or next vector by pressing one of the buttons
@@ -2844,7 +2843,7 @@ As seen, ResInsight per default lists the most probable stepping dimensions by a
 <ul>
 <li>Create plots based on well summary vectors</li>
 <li>Make sure source stepping <strong>Step By</strong> is set to <strong>Well</strong></li>
-<li>Activate the update of plots by clicking on button with tool tip text <em>&ldquo;Update wells used in plots from well selections in 3D view.&quot;</em></li>
+<li>Activate the update of plots by clicking on button with tool tip text <em>&ldquo;Update wells used in plots from well selections in 3D view.&rdquo;</em></li>
 <li>Open a 3D view, click on wells</li>
 <li>The well data source in changed, and plot content will be updated accordingly</li>
 </ul>
@@ -2862,7 +2861,7 @@ However, the complete set of source stepping dimensions is always available in b
 <li>Block</li>
 <li>Aquifer</li>
 </ul>
-<p>When clicking a <em>next</em> or <em>previous</em> button, all curves are changed to display data for the selected source stepping dimension. 
+<p>When clicking a <em>next</em> or <em>previous</em> button, all curves are changed to display data for the selected source stepping dimension.
 For instance, when clicking <img src="https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarPrevNext.png" style="display:inline; vertical-align:middle; margin:0">
 
 with <em>Well</em> as source stepping dimension, all curves in the current plot are changed to display data for previous/next well.</p>
@@ -4999,19 +4998,19 @@ with <em>Well</em> as source stepping dimension, all curves in the current 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/summarytables/index.html b/plot-window/summarytables/index.html
index f684dcf76c..f4e7ed0198 100644
--- a/plot-window/summarytables/index.html
+++ b/plot-window/summarytables/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Summary Tables :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4979,19 +4978,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/vfpplot/index.html b/plot-window/vfpplot/index.html
index 8abf8d9851..6e01d8980a 100644
--- a/plot-window/vfpplot/index.html
+++ b/plot-window/vfpplot/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>VFP Plot :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5013,19 +5012,19 @@ lift quantities like gas lift gas), or phases ratios, flowing up the wellbore. T
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/wellborestabilityplots/index.html b/plot-window/wellborestabilityplots/index.html
index 095e2cd8a7..a00b21b01d 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Bore Stability Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2853,7 +2852,7 @@ if (!doNotTrack) {
 <p>If any <a href="/wells-and-completions/wellmeasurements/">Well Measurements</a> are present, they will be visible as symbols in the track <strong>Stability Curves</strong>.</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=""> 
+<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>PP</strong>, <strong>FG</strong>, <strong>SFG</strong> and <strong>SH_MK</strong>, the following input parameters are required:</p>
@@ -2951,7 +2950,7 @@ if (!doNotTrack) {
 <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>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>
@@ -2967,7 +2966,7 @@ $$ FG = \frac{P_w}{TVD_{RKB} \: g  \: \rho}$$ where $TVD_{RKB} = TVD_{MSL} + Air
 <h3 id="sh-from-matthews--kelly">SH from Matthews &amp; Kelly</h3>
 <p>$$SH_{MK} = K0_{SH} \times (OBG0 - PP0) + PP0 + DF \times (PP-PP0)$$</p>
 <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 $P_w$ that satisfies the following equation 
+<p>Stassi-d&rsquo;Alia failure criterion in shale is calculated by finding the well pressure $P_w$ that satisfies the following equation
 for  $\theta \in [0 - 180]$:</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">
@@ -5112,19 +5111,19 @@ under <em>Python Examples</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/plot-window/welllogsandplots/index.html b/plot-window/welllogsandplots/index.html
index 5510632bea..006d789c29 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Log Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2839,7 +2838,7 @@ if (!doNotTrack) {
 <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>
 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>
@@ -2877,9 +2876,9 @@ The two types of curves are <em>Well Log Extraction Curves</em> and <em>Well Log
 <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>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>
@@ -2893,10 +2892,10 @@ The display name of a curve is normally generated automatically. Optionally, <st
 <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>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>In both cases, the following parameters are available to change:</p>
@@ -5061,19 +5060,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/commandfile/index.html b/scripting/commandfile/index.html
index 1c0810ecd0..7e15a4a3c9 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Command File :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2862,7 +2861,7 @@ 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, please see 
+<p>It is possible to use these commands directly from a Python script. For further details, please see
 the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
 <h2 id="command-list">Command List</h2>
 <h4 id="case-control-commands">Case Control Commands</h4>
@@ -2907,7 +2906,7 @@ the <a href="https://api.resinsight.org">ResInsight Python API</a>.</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.
+<pre tabindex="0"><code>Command file examples are displayed in sections like this.
 </code></pre><h3 id="types">Types</h3>
 <p>There are different types of parameters that can be supplied.</p>
 <table>
@@ -2973,10 +2972,10 @@ the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
 </tr>
 </tbody>
 </table>
-<pre><code>openProject(path=&quot;/home/user/ResInsightProject.rsp&quot;)
+<pre tabindex="0"><code>openProject(path=&#34;/home/user/ResInsightProject.rsp&#34;)
 </code></pre><h3 id="closeproject">closeProject</h3>
 <p>Closes the current open project.</p>
-<pre><code>closeProject()
+<pre tabindex="0"><code>closeProject()
 </code></pre><h3 id="setstartdir">setStartDir</h3>
 <p>Set startup directory.</p>
 <table>
@@ -2997,7 +2996,7 @@ the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
 </tr>
 </tbody>
 </table>
-<pre><code>setStartDir(path=&quot;/home/user&quot;)
+<pre tabindex="0"><code>setStartDir(path=&#34;/home/user&#34;)
 </code></pre><h3 id="loadcase">loadCase</h3>
 <p>Import Eclipse case from file.</p>
 <table>
@@ -3018,7 +3017,7 @@ the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
 </tr>
 </tbody>
 </table>
-<pre><code>loadCase(path=&quot;/home/user/reservoir.EGRID&quot;)
+<pre tabindex="0"><code>loadCase(path=&#34;/home/user/reservoir.EGRID&#34;)
 </code></pre><h3 id="creategridcasegroup">createGridCaseGroup</h3>
 <p>Create a Grid Case Group from a list of files.</p>
 <table>
@@ -3059,7 +3058,7 @@ the <a href="https://api.resinsight.org">ResInsight Python API</a>.</p>
 </tr>
 </tbody>
 </table>
-<pre><code>createGridCaseGroup(path=[&quot;/home/user/reservoir.EGRID&quot;, &quot;/home/user/other_reservoir.EGRID&quot;])
+<pre tabindex="0"><code>createGridCaseGroup(path=[&#34;/home/user/reservoir.EGRID&#34;, &#34;/home/user/other_reservoir.EGRID&#34;])
 createStatisticsCase(caseGroupId=0)
 </code></pre><h3 id="replacecase">replaceCase</h3>
 <p>Replaces a case in the current project with the specified new case.</p>
@@ -3088,7 +3087,7 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>replaceCase(newGridFile=&quot;/home/user/otherReservoir.EGRID&quot;, caseId=4)
+<pre tabindex="0"><code>replaceCase(newGridFile=&#34;/home/user/otherReservoir.EGRID&#34;, caseId=4)
 </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>
@@ -3116,7 +3115,7 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>replaceSourceCases(gridListFile=&quot;C:/resinsight/replacement_files.txt&quot;)
+<pre tabindex="0"><code>replaceSourceCases(gridListFile=&#34;C:/resinsight/replacement_files.txt&#34;)
 </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>
@@ -3140,7 +3139,7 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>exportMultiCaseSnapshots(gridListFile=&quot;C:\\resinsight\\replacement_files.txt&quot;)
+<pre tabindex="0"><code>exportMultiCaseSnapshots(gridListFile=&#34;C:\\resinsight\\replacement_files.txt&#34;)
 </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>
@@ -3174,7 +3173,7 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>exportSnapshots(type=PLOTS)
+<pre tabindex="0"><code>exportSnapshots(type=PLOTS)
 </code></pre><h3 id="exportproperty">exportProperty</h3>
 <p>Exports property values for all cells in the grid to file in Eclipse format.</p>
 <table>
@@ -3225,7 +3224,7 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>exportProperty(caseId=1, timeStep=4, property=&quot;SOIL&quot;)
+<pre tabindex="0"><code>exportProperty(caseId=1, timeStep=4, property=&#34;SOIL&#34;)
 </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>
@@ -3258,9 +3257,9 @@ createStatisticsCase(caseGroupId=0)
 </tr>
 </tbody>
 </table>
-<pre><code>exportPropertyInViews(caseId=1)
+<pre tabindex="0"><code>exportPropertyInViews(caseId=1)
 
-exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot;])
+exportPropertyInViews(caseId=1, viewNames=[&#34;view A&#34;, &#34;view 4&#34;])
 </code></pre><h3 id="exportwellpathcompletions">exportWellPathCompletions</h3>
 <p>Export well path completions.</p>
 <table>
@@ -3329,7 +3328,7 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-<pre><code>exportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)
+<pre tabindex="0"><code>exportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)
 </code></pre><h3 id="exportsimwellfracturecompletions">exportSimWellFractureCompletions</h3>
 <p>Export fracture completions for simulation wells.</p>
 <table>
@@ -3380,7 +3379,7 @@ 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)
+<pre tabindex="0"><code>exportSimWellFractureCompletions(caseId=3, viewName=&#34;View 2&#34;, timeStep=5)
 </code></pre><h3 id="exportmsw">exportMsw</h3>
 <p>Export multi-segment wells.</p>
 <table>
@@ -3407,7 +3406,7 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-<pre><code>exportMsw(caseId=1, wellPath=&quot;MainWell&quot;)
+<pre tabindex="0"><code>exportMsw(caseId=1, wellPath=&#34;MainWell&#34;)
 </code></pre><h3 id="exportwellpaths">exportWellPaths</h3>
 <p>Export well paths.</p>
 <table>
@@ -3434,7 +3433,7 @@ 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)
+<pre tabindex="0"><code>exportWellPaths(wellPathNames=[&#34;B-1H&#34;, &#34;B-2H&#34;], mdStepSize=1.5)
 </code></pre><h3 id="exportvisiblecells">exportVisibleCells</h3>
 <p>Export visible cells</p>
 <table>
@@ -3485,7 +3484,7 @@ 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)
+<pre tabindex="0"><code>exporVisibleCells(caseId=0, viewName=&#34;View 1&#34;, exportKeyword=MULTNUM)
 </code></pre><h3 id="exportflowcharacteristics">exportFlowCharacteristics</h3>
 <p>Export Flow Characteristics data to text file in CSV format</p>
 <table>
@@ -3542,7 +3541,7 @@ 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;)
+<pre tabindex="0"><code>exportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[&#34;INJA&#34;, &#34;INJB&#34;], producers=[&#34;PROD_F&#34;], fileName=&#34;myData.csv&#34;)
 </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>
@@ -3575,7 +3574,7 @@ 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;)
+<pre tabindex="0"><code>setExportFolder(type=SNAPSHOTS, path=&#34;/home/user/snapshots&#34;)
 </code></pre><h2 id="other">Other</h2>
 <h3 id="runoctavescript">runOctaveScript</h3>
 <p>Execute an Octave script.</p>
@@ -3603,7 +3602,7 @@ 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])
+<pre tabindex="0"><code>runOctaveScript(path=&#34;/home/user/octave/something.m&#34;, caseIds=[1,2,6])
 </code></pre><h3 id="setmainwindowsize">setMainWindowSize</h3>
 <p>Resize the main window to the specified size.</p>
 <table>
@@ -3630,7 +3629,7 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-<pre><code>setMainWindowSize(width=1920, height=1200)
+<pre tabindex="0"><code>setMainWindowSize(width=1920, height=1200)
 </code></pre><h3 id="computecasegroupstatistics">computeCaseGroupStatistics</h3>
 <p>Compute statistics for statistics cases.</p>
 <table>
@@ -3651,7 +3650,7 @@ exportPropertyInViews(caseId=1, viewNames=[&quot;view A&quot;, &quot;view 4&quot
 </tr>
 </tbody>
 </table>
-<pre><code>computeCaseGroupStatistics(caseIds=[5])
+<pre tabindex="0"><code>computeCaseGroupStatistics(caseIds=[5])
 
 computeCaseGroupStatistics(caseIds=[2,4,8])
 </code></pre><h3 id="settimestep">setTimeStep</h3>
@@ -3680,7 +3679,7 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-<pre><code>setTimeStep(caseId=1, timeStep=8)
+<pre tabindex="0"><code>setTimeStep(caseId=1, timeStep=8)
 </code></pre><h3 id="scalefracturetemplate">scaleFractureTemplate</h3>
 <p>Scale fracture template parameters.</p>
 <table>
@@ -3725,7 +3724,7 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-<pre><code>scaleFractureTemplate(id=1, width=2, height=1.5)
+<pre tabindex="0"><code>scaleFractureTemplate(id=1, width=2, height=1.5)
 </code></pre><h3 id="setfracturecontainment">setFractureContainment</h3>
 <p>Set fracture template containment parameters.</p>
 <table>
@@ -3758,7 +3757,7 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-<pre><code>setFractureContainment(id=1, topLayer=2, baseLayer=7)
+<pre tabindex="0"><code>setFractureContainment(id=1, topLayer=2, baseLayer=7)
 </code></pre><h3 id="createmultiplefractures">createMultipleFractures</h3>
 <p>Create multiple fractures on one or more well paths.</p>
 <table>
@@ -3827,7 +3826,7 @@ 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)
+<pre tabindex="0"><code>createMultipleFractures(caseId=0, templateId=1, wellPathNames=[&#34;B-1H&#34;, &#34;B-2H&#34;], action=REPLACE_FRACTURES)
 </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>
@@ -3884,7 +3883,7 @@ 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)
+<pre tabindex="0"><code>createLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[&#34;B-1H&#34;, &#34;B-2H&#34;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)
 </code></pre><h3 id="createsaturationpressureplots">createSaturationPressurePlots</h3>
 <p>Create saturation pressure plots for the specified cases.</p>
 <table>
@@ -3905,7 +3904,7 @@ computeCaseGroupStatistics(caseIds=[2,4,8])
 </tr>
 </tbody>
 </table>
-<pre><code>createSaturationPressurePlots(caseIds=[0])
+<pre tabindex="0"><code>createSaturationPressurePlots(caseIds=[0])
 </code></pre>
 
 <footer class="footline">
@@ -6039,19 +6038,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/commandlineinterface/index.html b/scripting/commandlineinterface/index.html
index c7d374e1e3..67ef9b85c0 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Command Line Interface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2954,15 +2953,15 @@ ResInsight stores data computed by statistics calculation in a cache file. When
 
 <h3 id="summary-plotting">Summary plotting</h3>
 <p>The summary plotting command option follows the following syntax:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">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></div><p>The summary plotting command option creates one summary plot for each of the the summary vectors matched by<br>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>resinsight --summaryplot [&lt;plotOptions&gt;] &lt;eclipsesummaryvectorfilters&gt; &lt;eclipsedatafiles&gt;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>where:
+</span></span><span style="display:flex;"><span>&lt;plotOptions&gt;                 denote summary plot options, see table below
+</span></span><span style="display:flex;"><span>&lt;eclipsesummaryvectorfilters&gt; has the syntax &lt;vectorname&gt;[:&lt;item&gt;[:&lt;subitem&gt;[:i,j,k]]]
+</span></span><span style="display:flex;"><span>&lt;eclipsedatafiles&gt;            lists a set of Eclipse data files with or without extension
+</span></span></code></pre></div><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>
@@ -3047,40 +3046,40 @@ However, if a grid property is requested, the corresponding EGRID and restart da
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">Real0/BRUGGE_0000.EGRID
-Real10/BRUGGE_0010.EGRID
-Real30/BRUGGE_0030.EGRID
-Real40/BRUGGE_0040.EGRID
-</code></pre></div><p>The command line used to run this example is shown here:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>Real0/BRUGGE_0000.EGRID
+</span></span><span style="display:flex;"><span>Real10/BRUGGE_0010.EGRID
+</span></span><span style="display:flex;"><span>Real30/BRUGGE_0030.EGRID
+</span></span><span style="display:flex;"><span>Real40/BRUGGE_0040.EGRID
+</span></span></code></pre></div><p>The command line used to run this example is shown here:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --project BatchTest.rsp --replaceCase &#34;Real10\BRUGGE_0010.EGRID&#34; --savesnapshots
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --project BatchTest.rsp --replaceCase &#34;Real10\BRUGGE_0010.EGRID&#34; --savesnapshots
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">Real0/BRUGGE_0000.EGRID
-Real10/BRUGGE_0010.EGRID
-</code></pre></div><p>The command line used to run this example is shown here:</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>Real0/BRUGGE_0000.EGRID
+</span></span><span style="display:flex;"><span>Real10/BRUGGE_0010.EGRID
+</span></span></code></pre></div><p>The command line used to run this example is shown here:</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots
-</code></pre></div><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>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --summaryplot FOPT 1_R001_REEK-0 
-</code></pre></div><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> 
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --summaryplot FOPT 1_R001_REEK-0 
+</span></span></code></pre></div><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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --summaryplot -s FOPT WOPT*:op_2 1_R001_REEK-0
-</code></pre></div><p>Adding to previous example, the following command line also plots the 3D grid property <code>SOIL</code> for cell (20, 21, 1).</p>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">ResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --summaryplot -s FOPT WOPT*:op_2 1_R001_REEK-0
+</span></span></code></pre></div><p>Adding to previous example, the following command line also plots the 3D grid property <code>SOIL</code> for cell (20, 21, 1).</p>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>ResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5213,19 +5212,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/index.html b/scripting/index.html
index ac3bdb3f14..56f8c152e6 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Scripting :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2244,7 +2244,7 @@
   
     
     <li data-nav-id="/scripting/" title="Scripting" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2817,8 +2816,8 @@ if (!doNotTrack) {
 <h2 id="python-interface">Python interface</h2>
 <p>ResInsight incorporates a powerful Python interface which allows you to interact with ResInsight and load data for further processing and automation.</p>
 <h2 id="command-line-interface-and-command-files">Command Line Interface and Command files</h2>
-<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 
+<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 <a href="/scripting/commandlineinterface/">command line parameter</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>
@@ -4959,19 +4958,19 @@ command file as a <a href="/scripting/commandlineinterface/">command line parame
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/index.xml b/scripting/index.xml
index 32bc86cfbf..7fa397e7bd 100644
--- a/scripting/index.xml
+++ b/scripting/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/scripting/</link>
     <description>Recent content in Scripting on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/scripting/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/scripting/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Python interface</title>
       <link>https://resinsight.org/scripting/pythoninterface/</link>
@@ -17,7 +13,7 @@
       
       <guid>https://resinsight.org/scripting/pythoninterface/</guid>
       <description>ResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance from Python 3. This enables you to:
- start ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics  Please refer to the ResInsight Python API for configuration and details.</description>
+start ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics Please refer to the ResInsight Python API for configuration and details.</description>
     </item>
     
     <item>
@@ -29,7 +25,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     --help, --?</description>
+Command line options General Parameter Description --help, --? Displays help text and version info --project &amp;lt;filename&amp;gt; Open project file &amp;lt;filename&amp;gt;.</description>
     </item>
     
     <item>
@@ -40,7 +36,7 @@ Command line options General    Parameter Description     --help, --?</descripti
       <guid>https://resinsight.org/scripting/commandfile/</guid>
       <description>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.
 It is possible to use these commands directly from a Python script. For further details, please see the ResInsight Python API.
-Command 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.</description>
+Command 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.</description>
     </item>
     
     <item>
@@ -50,9 +46,9 @@ Command List Case Control Commands  openProject closeProject setStartDir loadCas
       
       <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.
+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>
+Octave Script Management Octave scripts are available in the Scripts folder in the Project Tree.</description>
     </item>
     
     <item>
@@ -66,4 +62,4 @@ Note: The Octave interface does not support Geomechanical cases and flow diagnos
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/scripting/octaveinterface/index.html b/scripting/octaveinterface/index.html
index b828990649..c06bcf3646 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Octave Interface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2867,75 +2866,75 @@ if (!doNotTrack) {
 </div>
 
 <h4 id="example-1">Example 1</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 change of oil saturation from time step to time step
-SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
-SOILDIFF = SOIL;
-
-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) = <span style="color:#ae81ff">0</span>;
-
-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(&#34;SOIL&#34;);
-
-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 = <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, &#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(&#34;SOIL&#34;);
-
-Mask = (CInfo(:,<span style="color:#ae81ff">1</span>) != <span style="color:#ae81ff">1</span>);
-
-LGRSOIL = SOIL;
-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, &#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(&#34;SOIL&#34;);
-
-SOIL_KAverage = SOIL;
-SOIL_KAverage(:) = nan;
-
-mini = min(CInfo(:,<span style="color:#ae81ff">2</span>))
-maxi = max(CInfo(:,<span style="color:#ae81ff">2</span>))
-
-minj = min(CInfo(:,<span style="color:#ae81ff">3</span>))
-maxj = max(CInfo(:,<span style="color:#ae81ff">3</span>))
-
-<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) ;
-
-    <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, &#34;SOIL_KAverage&#34;);
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-matlab" data-lang="matlab"><span style="display:flex;"><span># Calculate change of oil saturation from time step to time step
+</span></span><span style="display:flex;"><span>SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
+</span></span><span style="display:flex;"><span>SOILDIFF = SOIL;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>i = <span style="color:#ae81ff">0</span>;
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> timestep = SOIL
+</span></span><span style="display:flex;"><span>	<span style="color:#66d9ef">if</span> (i <span style="color:#f92672">&gt;</span> <span style="color:#ae81ff">0</span>) 
+</span></span><span style="display:flex;"><span>		SOILDIFF(:,i) = timestep <span style="color:#f92672">-</span> SOIL(:,i);
+</span></span><span style="display:flex;"><span>	endif
+</span></span><span style="display:flex;"><span>	i<span style="color:#f92672">++</span>;
+</span></span><span style="display:flex;"><span>endfor
+</span></span><span style="display:flex;"><span>SOILDIFF(:,i) = <span style="color:#ae81ff">0</span>;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>riSetActiveCellProperty(SOILDIFF, &#34;SOILDIFF&#34;);
+</span></span></code></pre></div><h4 id="example-2">Example 2</h4>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-matlab" data-lang="matlab"><span style="display:flex;"><span># 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>
+</span></span><span style="display:flex;"><span>CInfo = riGetActiveCellInfo();
+</span></span><span style="display:flex;"><span>SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>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>)
+</span></span><span style="display:flex;"><span>LGRSOIL = SOIL;
+</span></span><span style="display:flex;"><span>i = <span style="color:#ae81ff">0</span>;
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> i = (<span style="color:#ae81ff">1</span>:columns(LGRSOIL))
+</span></span><span style="display:flex;"><span>    LGRSOIL(Mask,i) = nan;
+</span></span><span style="display:flex;"><span>endfor
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>riSetActiveCellProperty(LGRSOIL, &#34;KSlice&#34;);
+</span></span></code></pre></div><h4 id="example-3">Example 3</h4>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-matlab" data-lang="matlab"><span style="display:flex;"><span># Keep the values in the first LGR only
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>CInfo = riGetActiveCellInfo();
+</span></span><span style="display:flex;"><span>SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>Mask = (CInfo(:,<span style="color:#ae81ff">1</span>) != <span style="color:#ae81ff">1</span>);
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>LGRSOIL = SOIL;
+</span></span><span style="display:flex;"><span>i = <span style="color:#ae81ff">0</span>;
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> i = (<span style="color:#ae81ff">1</span>:columns(LGRSOIL))
+</span></span><span style="display:flex;"><span>    LGRSOIL(Mask,i) = nan;
+</span></span><span style="display:flex;"><span>endfor
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>riSetActiveCellProperty(LGRSOIL, &#34;LGRSOIL&#34;);
+</span></span></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 tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-matlab" data-lang="matlab"><span style="display:flex;"><span># Calculate the average SOIL value across K layers
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>CInfo = riGetActiveCellInfo();
+</span></span><span style="display:flex;"><span>SOIL = riGetActiveCellProperty(&#34;SOIL&#34;);
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>SOIL_KAverage = SOIL;
+</span></span><span style="display:flex;"><span>SOIL_KAverage(:) = nan;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>mini = min(CInfo(:,<span style="color:#ae81ff">2</span>))
+</span></span><span style="display:flex;"><span>maxi = max(CInfo(:,<span style="color:#ae81ff">2</span>))
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>minj = min(CInfo(:,<span style="color:#ae81ff">3</span>))
+</span></span><span style="display:flex;"><span>maxj = max(CInfo(:,<span style="color:#ae81ff">3</span>))
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span><span style="color:#66d9ef">for</span> i = mini:maxi
+</span></span><span style="display:flex;"><span>  <span style="color:#66d9ef">for</span> j = minj:maxj 
+</span></span><span style="display:flex;"><span>    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) ;
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>    <span style="color:#66d9ef">for</span> ts = (<span style="color:#ae81ff">1</span>:columns(SOIL)) 
+</span></span><span style="display:flex;"><span>      SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));
+</span></span><span style="display:flex;"><span>    endfor
+</span></span><span style="display:flex;"><span>  endfor
+</span></span><span style="display:flex;"><span>endfor
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>riSetActiveCellProperty(SOIL_KAverage, &#34;SOIL_KAverage&#34;);
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5068,19 +5067,19 @@ riSetActiveCellProperty(SOIL_KAverage, &#34;SOIL_KAverage&#34;);
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/octaveinterfacereference/index.html b/scripting/octaveinterfacereference/index.html
index b617407250..6b00963273 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Octave Interface Reference :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2833,7 +2832,7 @@ if (!doNotTrack) {
 </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>
@@ -2896,10 +2895,10 @@ The Current Case can be accessed directly using <strong>riGetCurrentCase()</stro
 }
 </code></pre>
 <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. 
+<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="matrixnumactivecells9-rigetactivecellinfocaseid-porositymodel--matrixfracture-">Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;] )</h4>
+<h4 id="matrixnumactivecells9-rigetactivecellinfocaseid-porositymodel--matrixfracture-">Matrix[numActiveCells][9] riGetActiveCellInfo([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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.
@@ -2923,7 +2922,7 @@ If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
 <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="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.
@@ -2942,7 +2941,7 @@ The Structure is defined as:</p>
 <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="vectorpropertyinfo-rigetpropertynamescaseid--porositymodel--matrixfracture">Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<h4 id="vectorpropertyinfo-rigetpropertynamescaseid--porositymodel--matrixfracture">Vector[PropertyInfo] riGetPropertyNames([CaseId] ], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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 {
@@ -2953,30 +2952,30 @@ The Structure is defined as:</p>
 }
 </code></pre>
 <p>If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-<h4 id="matrixnumactivecellsnumtimestepsrequested-rigetactivecellpropertycaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture">Matrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<h4 id="matrixnumactivecellsnumtimestepsrequested-rigetactivecellpropertycaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture">Matrix[numActiveCells][numTimestepsRequested] riGetActiveCellProperty([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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="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>
+<h4 id="matrixnuminumjnumknumtimestepsrequested-rigetgridpropertycaseid-gridindex--propertyname-requestedtimesteps-porositymodel--matrixfracture">Matrix[numI][numJ][numK][numTimestepsRequested] riGetGridProperty([CaseId], GridIndex , PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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-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;. 
+<h4 id="risetactivecellproperty-matrixnumactivecellsnumtimesteps-caseid-propertyname-timestepindices-porositymodel--matrixfracture">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>
 If the CaseId is not defined, ResInsight&rsquo;s Current Case is used.</p>
-<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;. 
+<h4 id="risetgridproperty-matrixnuminumjnumknumtimesteps-caseid-gridindex-propertyname-timestepindices-porositymodel--matrixfracture">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;.
 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="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="matrixactivecells3-rigetactivecellcenterscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<h4 id="matrixactivecells3-rigetactivecellcenterscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][3] riGetActiveCellCenters([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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
@@ -2996,7 +2995,7 @@ The corner indices follow the ECLIPSE standard:</p>
 <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="matrixactivecells83-rigetactivecellcornerscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;])</h4>
+<h4 id="matrixactivecells83-rigetactivecellcornerscaseid-porositymodel--matrixfracture">Matrix[ActiveCells][8][3] riGetActiveCellCorners([CaseId], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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>
@@ -3035,7 +3034,7 @@ The columns contain the following information:</p>
   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="matrixnumselectedcellsnumtimestepsrequested-rigetgridpropertyforselectedcellscaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture-">Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&quot;|&quot;Fracture&rdquo;] )</h4>
+<h4 id="matrixnumselectedcellsnumtimestepsrequested-rigetgridpropertyforselectedcellscaseid-propertyname-requestedtimesteps-porositymodel--matrixfracture-">Matrix[numSelectedCells][numTimestepsRequested] riGetGridPropertyForSelectedCells([CaseId], PropertyName, [RequestedTimeSteps], [PorosityModel = &ldquo;Matrix&rdquo;|&ldquo;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>
@@ -5205,19 +5204,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/scripting/pythoninterface/index.html b/scripting/pythoninterface/index.html
index bb5021b626..3e823f0a21 100644
--- a/scripting/pythoninterface/index.html
+++ b/scripting/pythoninterface/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Python interface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2803,8 +2802,8 @@ if (!doNotTrack) {
 
 
 <p><img src="/images/scripting/python-logo-master-v3-TM.png" alt=""></p>
-<p>ResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance 
-from <a href="https://www.python.org/download/releases/3.0/">Python 3</a>. 
+<p>ResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance
+from <a href="https://www.python.org/download/releases/3.0/">Python 3</a>.
 This enables you to:</p>
 <ul>
 <li>start ResInsight from Python</li>
@@ -4945,19 +4944,19 @@ This enables you to:</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/search/index.html b/search/index.html
index 7ac7866dd4..aeb3bbda37 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Search :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2813,8 +2812,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.\nResInsight stores all views and settings in a Project File to easily continue the work in a subsequent session.\nModel Navigation describes how to interact and manipulate the 3D model.\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 .\n",
-                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\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\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.\nRight-click menu commands are also available to do special operations on a selected set of items.\u003c/p\u003e\n\u003cp\u003eResInsight stores all views and settings in a \u003ca href=\"/misc/projectfile/\"\u003eProject File\u003c/a\u003e to easily continue the work in a subsequent session.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e describes how to interact and manipulate the 3D model.\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",
+                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.\nProject 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 Use 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.\nToolbars 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\nTile 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.\nResInsight stores all views and settings in a Project File to easily continue the work in a subsequent session.\nModel Navigation describes how to interact and manipulate the 3D model.\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 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.\nInput Case This 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 Statistics Case This 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 This 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 .\n",
+                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\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\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.\nRight-click menu commands are also available to do special operations on a selected set of items.\u003c/p\u003e\n\u003cp\u003eResInsight stores all views and settings in a \u003ca href=\"/misc/projectfile/\"\u003eProject File\u003c/a\u003e to easily continue the work in a subsequent session.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e describes how to interact and manipulate the 3D model.\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",
                 url:      "/getting-started/overview/"
             };
         
@@ -2822,8 +2821,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/projecttree/"] = {
                 title:    "Project Tree",
-                content:  "As described in Overview, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the Project Tree and the Plots windows. Some of their general functionality is described and exemplified below.\nMultiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. To exemplify, consider the plot of Bottom Hole Pressure for a number of wells atop this page. By multi-selection in Plots, you may for instance change the color of multiple curves as shown below.\nSeveral options are available for multi selection of items which can be used in combination for efficiency and convenience:\n Ctrl + left mouse button for selecting individual items Shift + left mouse button for selecting a range of consecutive items Item right-click menu: offers context sensitive actions, e.g.:  Sub Items On: select all sub-items of an item Sub Items Off: deselect all sub-items of an item Toggle Sub Items: deselect previously selected sub-items and select previously not selected sub-items On - Others Off: Turns on selected plot and turns off all other plots    Undo and Redo Undo and Redo is available via:\n Toolbar icons  Edit menu items Undo and Redo Shortcuts Ctrl-Z and Ctrl-Y  Context sensitive help ResInsight offers context sensitive help for any item in project tree. Most convenient is just to press the F1 help key for any selected item. Alternatively, you may right-click an item and invoke menu item Search Help For.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeAndWindow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs described in \u003ca href=\"/getting-started/overview/\"\u003eOverview\u003c/a\u003e, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the \u003cstrong\u003eProject Tree\u003c/strong\u003e and the \u003cstrong\u003ePlots\u003c/strong\u003e windows. Some of their general functionality is described and exemplified below.\u003c/p\u003e\n\u003ch2 id=\"multiple-selection-and-collective-actions\"\u003eMultiple selection and collective actions\u003c/h2\u003e\n\u003cp\u003eMultiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. \nTo exemplify, consider the plot of \u003cem\u003eBottom Hole Pressure\u003c/em\u003e for a number of wells atop this page. By multi-selection in \u003cstrong\u003ePlots\u003c/strong\u003e, you may for instance change the color of multiple curves as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSeveral options are available for multi selection of items which can be used in combination for efficiency and convenience:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl + left mouse button\u003c/strong\u003e for selecting individual items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShift + left mouse button\u003c/strong\u003e for selecting a range of consecutive items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eItem right-click menu\u003c/strong\u003e: offers context sensitive actions, e.g.:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSub Items On\u003c/strong\u003e: select all sub-items of an item\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSub Items Off\u003c/strong\u003e: deselect all sub-items of an item\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eToggle Sub Items\u003c/strong\u003e: deselect previously selected sub-items and select previously not selected sub-items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOn - Others Off\u003c/strong\u003e: Turns on selected plot and turns off all other plots\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeItemMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"undo-and-redo\"\u003eUndo and Redo\u003c/h2\u003e\n\u003cp\u003e\u003cstrong\u003eUndo\u003c/strong\u003e and \u003cstrong\u003eRedo\u003c/strong\u003e is available via:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eToolbar icons \u003cimg src=\"https://resinsight.org/images/getting-started//ResInsightPlotProjectTreeToolbarUndoRedo.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEdit menu\u003c/strong\u003e items \u003cstrong\u003eUndo\u003c/strong\u003e and \u003cstrong\u003eRedo\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eShortcuts \u003cstrong\u003eCtrl-Z\u003c/strong\u003e and \u003cstrong\u003eCtrl-Y\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"context-sensitive-help\"\u003eContext sensitive help\u003c/h2\u003e\n\u003cp\u003eResInsight offers context sensitive help for any item in project tree. Most convenient is just to press the \u003cstrong\u003eF1\u003c/strong\u003e help key for any selected item. Alternatively, you may right-click an item and invoke menu item \u003cstrong\u003eSearch Help For\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ContextSensitiveHelp.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nAs described in Overview, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the Project Tree and the Plots windows. Some of their general functionality is described and exemplified below.\nMultiple selection and collective actions Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions. To exemplify, consider the plot of Bottom Hole Pressure for a number of wells atop this page. By multi-selection in Plots, you may for instance change the color of multiple curves as shown below.\nSeveral options are available for multi selection of items which can be used in combination for efficiency and convenience:\nCtrl + left mouse button for selecting individual items Shift + left mouse button for selecting a range of consecutive items Item right-click menu: offers context sensitive actions, e.g.: Sub Items On: select all sub-items of an item Sub Items Off: deselect all sub-items of an item Toggle Sub Items: deselect previously selected sub-items and select previously not selected sub-items On - Others Off: Turns on selected plot and turns off all other plots Undo and Redo Undo and Redo is available via:\nToolbar icons Edit menu items Undo and Redo Shortcuts Ctrl-Z and Ctrl-Y Context sensitive help ResInsight offers context sensitive help for any item in project tree. Most convenient is just to press the F1 help key for any selected item. Alternatively, you may right-click an item and invoke menu item Search Help For.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeAndWindow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs described in \u003ca href=\"/getting-started/overview/\"\u003eOverview\u003c/a\u003e, ResInsight has two main windows, one for 3D related visualizations and one for 2D graphs and plots. The content and appearance of displayed information is managed and controlled by the \u003cstrong\u003eProject Tree\u003c/strong\u003e and the \u003cstrong\u003ePlots\u003c/strong\u003e windows. Some of their general functionality is described and exemplified below.\u003c/p\u003e\n\u003ch2 id=\"multiple-selection-and-collective-actions\"\u003eMultiple selection and collective actions\u003c/h2\u003e\n\u003cp\u003eMultiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions.\nTo exemplify, consider the plot of \u003cem\u003eBottom Hole Pressure\u003c/em\u003e for a number of wells atop this page. By multi-selection in \u003cstrong\u003ePlots\u003c/strong\u003e, you may for instance change the color of multiple curves as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSeveral options are available for multi selection of items which can be used in combination for efficiency and convenience:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCtrl + left mouse button\u003c/strong\u003e for selecting individual items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShift + left mouse button\u003c/strong\u003e for selecting a range of consecutive items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eItem right-click menu\u003c/strong\u003e: offers context sensitive actions, e.g.:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSub Items On\u003c/strong\u003e: select all sub-items of an item\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSub Items Off\u003c/strong\u003e: deselect all sub-items of an item\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eToggle Sub Items\u003c/strong\u003e: deselect previously selected sub-items and select previously not selected sub-items\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOn - Others Off\u003c/strong\u003e: Turns on selected plot and turns off all other plots\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeItemMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"undo-and-redo\"\u003eUndo and Redo\u003c/h2\u003e\n\u003cp\u003e\u003cstrong\u003eUndo\u003c/strong\u003e and \u003cstrong\u003eRedo\u003c/strong\u003e is available via:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eToolbar icons \u003cimg src=\"https://resinsight.org/images/getting-started//ResInsightPlotProjectTreeToolbarUndoRedo.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eEdit menu\u003c/strong\u003e items \u003cstrong\u003eUndo\u003c/strong\u003e and \u003cstrong\u003eRedo\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eShortcuts \u003cstrong\u003eCtrl-Z\u003c/strong\u003e and \u003cstrong\u003eCtrl-Y\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"context-sensitive-help\"\u003eContext sensitive help\u003c/h2\u003e\n\u003cp\u003eResInsight offers context sensitive help for any item in project tree. Most convenient is just to press the \u003cstrong\u003eF1\u003c/strong\u003e help key for any selected item. Alternatively, you may right-click an item and invoke menu item \u003cstrong\u003eSearch Help For\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ContextSensitiveHelp.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/projecttree/"
             };
         
@@ -2831,8 +2830,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. 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:     "\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 \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\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",
+                content:  "\n3D 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 Definition\ralong 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:\nThe 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 Box settings can be activated by clicking on the Info Text in the 3D view.\nGrids 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 \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\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/"
             };
         
@@ -2840,8 +2839,8 @@ if (!doNotTrack) {
          
             window.store["/calculated-data/calculatorexpressions/"] = {
                 title:    "Calculator Expressions",
-                content:  "Two similar calculators use expressions, summary curve calculator and grid cell calculator. These two variants share the text parsing for calculator expressions.\nGrid Property Calculator\nSummary Curve Calculator\nResInsight supports a subset of the features supported in the exprtk parsing library. Scripting features like for/while loops are not supported. The full documentation for the expression parser is available at C++ Mathematical Expression Toolkit Library\nOperators and Functions Possible operations and functions are found by right-clicking in the expression window.\nComment lines Create a comment line by prefixing with // or ##\n// Valid comment line 2\r## Valid comment line 1\rAssignment Operators    OPERATOR DEFINITION     := Assignment    ## Example\rMY_VARIABLE := b + c\rBasic Operators    OPERATOR DEFINITION     + Addition   - Subtraction   * Multiplication   / Division   % Modulus   ^ Power    ## Example\ra := (b * c) + d / 10.5\rConditionals if-then-else statements can be used to assign values based on the individual values in a vector. The following case will assign 0.01 if the TRANX is below 0.01, else copy the original TRANX value.\n## Example\rNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\rScalar Functions    FUNCTION DEFINITION     avg Average   max Maximum   min Minimum   sum Sum    ## Example: Use the accumulated sum for all PORV values to compute the normalized PORV\rNORMALIZED_PORV := x/sum(PORV)\rTrigonometry 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    ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/calculated-data/calculator-text-expression.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTwo similar calculators use expressions, summary curve calculator and grid cell calculator. These two variants share the text parsing for calculator expressions.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Property Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/curvecalculator/\"\u003eSummary Curve Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports a subset of the features supported in the \u003cstrong\u003eexprtk\u003c/strong\u003e  parsing library. Scripting features like for/while loops are not supported. The full documentation for the expression parser is available at \u003ca href=\"https://github.com/ArashPartow/exprtk\"\u003eC++ Mathematical Expression Toolkit Library\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"operators-and-functions\"\u003eOperators and Functions\u003c/h2\u003e\n\u003cp\u003ePossible operations and functions are found by right-clicking in the expression window.\u003c/p\u003e\n\u003ch3 id=\"comment-lines\"\u003eComment lines\u003c/h3\u003e\n\u003cp\u003eCreate a  comment line by prefixing with \u003ccode\u003e//\u003c/code\u003e or \u003ccode\u003e##\u003c/code\u003e\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e// Valid comment line 2\r\n## Valid comment line 1\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"assignment-operators\"\u003eAssignment Operators\u003c/h3\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\u003eAssignment\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre\u003e\u003ccode\u003e## Example\r\nMY_VARIABLE := b + c\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"basic-operators\"\u003eBasic Operators\u003c/h3\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\u003cpre\u003e\u003ccode\u003e## Example\r\na := (b * c) + d / 10.5\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"conditionals\"\u003eConditionals\u003c/h3\u003e\n\u003cp\u003e\u003cstrong\u003eif-then-else\u003c/strong\u003e statements can be used to assign values based on the individual values in a vector. The following case will assign 0.01 if the \u003cstrong\u003eTRANX\u003c/strong\u003e is below 0.01, else copy the original \u003cstrong\u003eTRANX\u003c/strong\u003e value.\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003e## Example\r\nNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"scalar-functions\"\u003eScalar Functions\u003c/h3\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\u003cpre\u003e\u003ccode\u003e## Example: Use the accumulated sum for all PORV values to compute the normalized PORV\r\nNORMALIZED_PORV := x/sum(PORV)\r\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"trigonometry-functions\"\u003eTrigonometry Functions\u003c/h3\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\u003ch3 id=\"vector-functions\"\u003eVector Functions\u003c/h3\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",
+                content:  "\nTwo similar calculators use expressions, summary curve calculator and grid cell calculator. These two variants share the text parsing for calculator expressions.\nGrid Property Calculator\nSummary Curve Calculator\nResInsight supports a subset of the features supported in the exprtk parsing library. Scripting features like for/while loops are not supported. The full documentation for the expression parser is available at C++ Mathematical Expression Toolkit Library\nOperators and Functions Possible operations and functions are found by right-clicking in the expression window.\nComment lines Create a comment line by prefixing with // or ##\n// Valid comment line 2\r## Valid comment line 1 Assignment Operators OPERATOR DEFINITION := Assignment ## Example\rMY_VARIABLE := b + c Basic Operators OPERATOR DEFINITION + Addition - Subtraction * Multiplication / Division % Modulus ^ Power ## Example\ra := (b * c) + d / 10.5 Conditionals if-then-else statements can be used to assign values based on the individual values in a vector. The following case will assign 0.01 if the TRANX is below 0.01, else copy the original TRANX value.\n## Example\rNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX) Scalar Functions FUNCTION DEFINITION avg Average max Maximum min Minimum sum Sum ## Example: Use the accumulated sum for all PORV values to compute the normalized PORV\rNORMALIZED_PORV := x/sum(PORV) 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 ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/calculated-data/calculator-text-expression.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTwo similar calculators use expressions, summary curve calculator and grid cell calculator. These two variants share the text parsing for calculator expressions.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Property Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/curvecalculator/\"\u003eSummary Curve Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports a subset of the features supported in the \u003cstrong\u003eexprtk\u003c/strong\u003e  parsing library. Scripting features like for/while loops are not supported. The full documentation for the expression parser is available at \u003ca href=\"https://github.com/ArashPartow/exprtk\"\u003eC++ Mathematical Expression Toolkit Library\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"operators-and-functions\"\u003eOperators and Functions\u003c/h2\u003e\n\u003cp\u003ePossible operations and functions are found by right-clicking in the expression window.\u003c/p\u003e\n\u003ch3 id=\"comment-lines\"\u003eComment lines\u003c/h3\u003e\n\u003cp\u003eCreate a  comment line by prefixing with \u003ccode\u003e//\u003c/code\u003e or \u003ccode\u003e##\u003c/code\u003e\u003c/p\u003e\n\u003cpre tabindex=\"0\"\u003e\u003ccode\u003e// Valid comment line 2\r\n## Valid comment line 1\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"assignment-operators\"\u003eAssignment Operators\u003c/h3\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\u003eAssignment\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cpre tabindex=\"0\"\u003e\u003ccode\u003e## Example\r\nMY_VARIABLE := b + c\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"basic-operators\"\u003eBasic Operators\u003c/h3\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\u003cpre tabindex=\"0\"\u003e\u003ccode\u003e## Example\r\na := (b * c) + d / 10.5\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"conditionals\"\u003eConditionals\u003c/h3\u003e\n\u003cp\u003e\u003cstrong\u003eif-then-else\u003c/strong\u003e statements can be used to assign values based on the individual values in a vector. The following case will assign 0.01 if the \u003cstrong\u003eTRANX\u003c/strong\u003e is below 0.01, else copy the original \u003cstrong\u003eTRANX\u003c/strong\u003e value.\u003c/p\u003e\n\u003cpre tabindex=\"0\"\u003e\u003ccode\u003e## Example\r\nNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"scalar-functions\"\u003eScalar Functions\u003c/h3\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\u003cpre tabindex=\"0\"\u003e\u003ccode\u003e## Example: Use the accumulated sum for all PORV values to compute the normalized PORV\r\nNORMALIZED_PORV := x/sum(PORV)\n\u003c/code\u003e\u003c/pre\u003e\u003ch3 id=\"trigonometry-functions\"\u003eTrigonometry Functions\u003c/h3\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\u003ch3 id=\"vector-functions\"\u003eVector Functions\u003c/h3\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",
                 url:      "/calculated-data/calculatorexpressions/"
             };
         
@@ -2849,8 +2848,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 2023.06 \n  ResInsight 2023.03 \n  ResInsight 2023.01 \n  ResInsight 2022.06.1 \n  ResInsight 2022.06 \n  ResInsight 2021.10 \n  ResInsight 2021.06 \n  ResInsight 2020.10.1 \n  ResInsight 2020.10 \n  ResInsight 2020.04.1 \n  ResInsight 2020.04 \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_2023_06/\"\u003e ResInsight 2023.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2023_03/\"\u003e ResInsight 2023.03 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2023_01/\"\u003e ResInsight 2023.01 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2022_06_1/\"\u003e ResInsight 2022.06.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2022_06/\"\u003e ResInsight 2022.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2021_10/\"\u003e ResInsight 2021.10 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2021_06/\"\u003e ResInsight 2021.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_10_1/\"\u003e ResInsight 2020.10.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_10/\"\u003e ResInsight 2020.10 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_04_1/\"\u003e ResInsight 2020.04.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_04/\"\u003e ResInsight 2020.04 \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_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",
+                content:  "Installation See the following for common install procedures and options:\nLinux Installation Windows Installation 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:\nResInsight 2023.06 ResInsight 2023.03 ResInsight 2023.01 ResInsight 2022.06.1 ResInsight 2022.06 ResInsight 2021.10 ResInsight 2021.06 ResInsight 2020.10.1 ResInsight 2020.10 ResInsight 2020.04.1 ResInsight 2020.04 ResInsight 2019.12.1 ResInsight 2019.12 ResInsight 2019.08 ResInsight 2019.04 ResInsight 2018.11 Sign up to be notified of new releases For 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_2023_06/\"\u003e ResInsight 2023.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2023_03/\"\u003e ResInsight 2023.03 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2023_01/\"\u003e ResInsight 2023.01 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2022_06_1/\"\u003e ResInsight 2022.06.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2022_06/\"\u003e ResInsight 2022.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2021_10/\"\u003e ResInsight 2021.10 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2021_06/\"\u003e ResInsight 2021.06 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_10_1/\"\u003e ResInsight 2020.10.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_10/\"\u003e ResInsight 2020.10 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_04_1/\"\u003e ResInsight 2020.04.1 \u003c/a\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/whats-new/releasenotes_2020_04/\"\u003e ResInsight 2020.04 \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_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/"
             };
         
@@ -2858,7 +2857,7 @@ 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 : Import a number of Eclipse files and places the cases in a grid case group See File Selection Dialog for how to import multiple 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.  Appending additional properties to a binary case If a binary or text Eclipse case is loaded, additional properties can be appended to this binary case. Make sure that the number of values in the GRDECL file matches the total number of cells in the binary case.\nAppending Additional Properties\nFor export of currently selected cell result values to text file, see Export: Eclipse Properties\nHandling 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",
+                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.\nEclipse 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:\nImport 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 : Import a number of Eclipse files and places the cases in a grid case group See File Selection Dialog for how to import multiple 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).\nResult 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:\nFirst 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. Appending additional properties to a binary case If a binary or text Eclipse case is loaded, additional properties can be appended to this binary case. Make sure that the number of values in the GRDECL file matches the total number of cells in the binary case.\nAppending Additional Properties\nFor export of currently selected cell result values to text file, see Export: Eclipse Properties\nHandling 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\u003ch2 id=\"eclipse-results\"\u003eEclipse Results\u003c/h2\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=\"/import/eclipsesummarydata/#ensemble-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\u003c/strong\u003e : 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 See \u003ca href=\"/import/eclipsesummarydata/#ensemble-file-import\"\u003eFile Selection Dialog\u003c/a\u003e for how to import multiple 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\u003ch3 id=\"result-index-file\"\u003eResult Index File\u003c/h3\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\u003ch2 id=\"time-step-filtered-eclipse-result\"\u003eTime Step Filtered Eclipse Result\u003c/h2\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\u003ch2 id=\"eclipse-ascii-input-data\"\u003eEclipse ASCII Input Data\u003c/h2\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=\"appending-additional-properties-to-a-binary-case\"\u003eAppending additional properties to a binary case\u003c/h3\u003e\n\u003cp\u003eIf a binary or text Eclipse case is loaded, additional properties can be appended to this binary case. Make sure that the number of values in the GRDECL file matches the total number of cells in the binary case.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/import/appendingadditionalproperties/\"\u003eAppending Additional Properties\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor export of currently selected cell result values to text file, see \u003ca href=\"/export/eclipseproperties/\"\u003eExport: Eclipse Properties\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"handling-missing-or-wrong-mapaxes\"\u003eHandling Missing or Wrong MAPAXES\u003c/h2\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/"
             };
@@ -2867,7 +2866,7 @@ if (!doNotTrack) {
          
             window.store["/import/eclipsesummarydata/"] = {
                 title:    "Eclipse Summary Data",
-                content:  "Summary data can be imported as a single summary file or an ensemble of summary files.\nBasic Summary Import Summary data is located in two files, summary vector names in *.SMSPEC and curve data in *.UNSMRY.\nFor import of ensemble datasets, see Ensemble File Dialog.\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.\nNaming The name of a summary case can be changed by interactive edit of the name in the Project Tree (by clicking or using F2) or selecting the summary case in the Property Editor and edit the name.\nSummary Data File Formats ResInsight is able to import summary data in three file formats. Default exported by Eclipse is *.SMSPEC/.UNSMRY. In addition, Eclipse can export into *.h5 for improved performance.\nFor best performance, ResInsight has support for *.ESMRY file format. ResInsight is able to produce this file format based on *.SMSPEC/UNSMRY files.\nSee configuration in Eclipse Summary Preferences.\nSMSPEC/UNSMRY File Format Eclipse will by default export summary data to *.SMSPEC and *.UNSMRY. Data is organized by simulation time step and extraction of data for one summary vector can be time consuming for large data sets.\nESMRY File Format *.ESMRY files contains the same data as SMSPEC/UNSMRY. The data in these files are organized in a different way that will give significantly better performance when accessing single summary vectors compared to SMSPEC/UNSMRY.\nResInsight will by default use this file format.\nh5 File Format Eclipse is able to produce summary data in a file format with the extension *.H5 with the same content as *.UNSMRY.\n",
+                content:  "Summary data can be imported as a single summary file or an ensemble of summary files.\nBasic Summary Import Summary data is located in two files, summary vector names in *.SMSPEC and curve data in *.UNSMRY.\nFor import of ensemble datasets, see Ensemble File Dialog.\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:\nCurrent 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.\nNaming The name of a summary case can be changed by interactive edit of the name in the Project Tree (by clicking or using F2) or selecting the summary case in the Property Editor and edit the name.\nSummary Data File Formats ResInsight is able to import summary data in three file formats. Default exported by Eclipse is *.SMSPEC/.UNSMRY. In addition, Eclipse can export into *.h5 for improved performance.\nFor best performance, ResInsight has support for *.ESMRY file format. ResInsight is able to produce this file format based on *.SMSPEC/UNSMRY files.\nSee configuration in Eclipse Summary Preferences.\nSMSPEC/UNSMRY File Format Eclipse will by default export summary data to *.SMSPEC and *.UNSMRY. Data is organized by simulation time step and extraction of data for one summary vector can be time consuming for large data sets.\nESMRY File Format *.ESMRY files contains the same data as SMSPEC/UNSMRY. The data in these files are organized in a different way that will give significantly better performance when accessing single summary vectors compared to SMSPEC/UNSMRY.\nResInsight will by default use this file format.\nh5 File Format Eclipse is able to produce summary data in a file format with the extension *.H5 with the same content as *.UNSMRY.\n",
                 html:     "\u003cp\u003eSummary data can be imported as a single summary file or an ensemble of summary files.\u003c/p\u003e\n\u003ch2 id=\"basic-summary-import\"\u003eBasic Summary Import\u003c/h2\u003e\n\u003cp\u003eSummary data is located in two files, summary vector names in \u003cstrong\u003e*.SMSPEC\u003c/strong\u003e and curve data in \u003cstrong\u003e*.UNSMRY\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eFor import of ensemble datasets, see \u003ca href=\"/import/ensemblefiledialog/\"\u003eEnsemble File Dialog\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"origin-files\"\u003eOrigin Files\u003c/h2\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\u003ch2 id=\"naming\"\u003eNaming\u003c/h2\u003e\n\u003cp\u003eThe name of a summary case can be changed by interactive edit of the name in the \u003cstrong\u003eProject Tree\u003c/strong\u003e (by clicking or using \u003cstrong\u003eF2\u003c/strong\u003e) or selecting the summary case in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e and edit the name.\u003c/p\u003e\n\u003ch2 id=\"summary-data-file-formats\"\u003eSummary Data File Formats\u003c/h2\u003e\n\u003cp\u003e\u003cstrong\u003eResInsight\u003c/strong\u003e is able to import summary data in three file formats. Default exported by \u003cem\u003eEclipse\u003c/em\u003e is \u003cstrong\u003e*.SMSPEC/.UNSMRY\u003c/strong\u003e. In addition, \u003cem\u003eEclipse\u003c/em\u003e can export into \u003cstrong\u003e*.h5\u003c/strong\u003e for improved performance.\u003c/p\u003e\n\u003cp\u003eFor best performance, \u003cstrong\u003eResInsight\u003c/strong\u003e has support for \u003cstrong\u003e*.ESMRY\u003c/strong\u003e file format. \u003cstrong\u003eResInsight\u003c/strong\u003e is able to produce this file format based on \u003cstrong\u003e*.SMSPEC/UNSMRY\u003c/strong\u003e files.\u003c/p\u003e\n\u003cp\u003eSee configuration in \u003ca href=\"/misc/preferences/#eclipse-summary\"\u003eEclipse Summary Preferences\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"smspecunsmry-file-format\"\u003eSMSPEC/UNSMRY File Format\u003c/h3\u003e\n\u003cp\u003e\u003cem\u003eEclipse\u003c/em\u003e will by default export summary data to \u003cstrong\u003e*.SMSPEC\u003c/strong\u003e and \u003cstrong\u003e*.UNSMRY\u003c/strong\u003e. Data is organized by simulation time step and extraction of data for one summary vector can be time consuming for large data sets.\u003c/p\u003e\n\u003ch3 id=\"esmry-file-format\"\u003eESMRY File Format\u003c/h3\u003e\n\u003cp\u003e\u003cstrong\u003e*.ESMRY\u003c/strong\u003e files contains the same data as \u003cstrong\u003eSMSPEC/UNSMRY\u003c/strong\u003e. The data in these files are organized in a different way that will give significantly better performance when accessing single summary vectors compared to \u003cstrong\u003eSMSPEC/UNSMRY\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eResInsight\u003c/strong\u003e will by default use this file format.\u003c/p\u003e\n\u003ch3 id=\"h5-file-format\"\u003eh5 File Format\u003c/h3\u003e\n\u003cp\u003e\u003cem\u003eEclipse\u003c/em\u003e is able to produce summary data in a file format with the extension \u003cstrong\u003e*.H5\u003c/strong\u003e with the same content as \u003cstrong\u003e*.UNSMRY\u003c/strong\u003e.\u003c/p\u003e\n",
                 url:      "/import/eclipsesummarydata/"
             };
@@ -2876,8 +2875,8 @@ if (!doNotTrack) {
          
             window.store["/import/ensemblefiledialog/"] = {
                 title:    "Ensemble File Dialog",
-                content:  "Ensemble 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.\nThis dialog is used for import of different file types like *.EGRID, *.SMSPEC, *.TS, *.GRDECL, \u0026hellip;\n\rThe 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. File Pattern: The search pattern that applies to the file name.  * 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 *[!D] Exclude files ending with the character \u0026lsquo;D\u0026rsquo; (file extension is not considered)   File Extensions: List of file extensions, ie \u0026ldquo;.EGRID .GRID\u0026rdquo; Use \u0026lsquo;realization-*\u0026rsquo; in filter : Replace the text \u0026ldquo;realization-12\u0026rdquo; with \u0026ldquo;realization-*\u0026rdquo; Ensemble grouping : Group ensemble by Main folder or Sub Folder (Used by FMU workflow) 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.  Ensemble File Structure Multiple summary files defining an ensemble can be organized differently in folders. ResInsight support two different modes, Sub Folder and Main Folder.\nSub Folder Example folder structure\nreal-1/case-1\r/case-2\rreal-2/case-1\r/case-2\rreal-3/case-1\r/case-2\r Using the option Group By Sub Folder will identify case-1 and case-2 as the ensemble names. This folder structure is used by the FMU workflow.\nMain Folder Example folder structure\ncase-1/real-1\rcase-1/real-2\rcase-1/real-3\rcase-2/real-1\rcase-2/real-2\rcase-2/real-3\r Using the option Group By Main Folder will identify case-1 and case-2 as the ensemble names. This folder structure is used by the Everest workflow.\nAfter 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.\nExamples of Use of Ensemble Import Dialog Ensemble Surface\nEnsemble Summary\n",
-                html:     "\u003ch2 id=\"ensemble-file-import\"\u003eEnsemble 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\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThis dialog is used for import of different file types like *.EGRID, *.SMSPEC, *.TS, *.GRDECL, \u0026hellip;\u003c/p\u003e\n\u003c/div\u003e\r\n\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.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Pattern\u003c/strong\u003e: The search pattern that applies to the file name.\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\u003cli\u003e\u003cstrong\u003e*[!D]\u003c/strong\u003e Exclude files ending with the character \u0026lsquo;D\u0026rsquo; (file extension is not considered)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Extensions\u003c/strong\u003e: List of file extensions, ie \u0026ldquo;.EGRID .GRID\u0026rdquo;\u003c/li\u003e\n\u003cli\u003eUse \u0026lsquo;realization-*\u0026rsquo; in filter : Replace the text \u0026ldquo;realization-12\u0026rdquo; with \u0026ldquo;realization-*\u0026rdquo;\u003c/li\u003e\n\u003cli\u003eEnsemble grouping : Group ensemble by Main folder or Sub Folder (Used by FMU workflow)\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\u003ch2 id=\"ensemble-file-structure\"\u003eEnsemble File Structure\u003c/h2\u003e\n\u003cp\u003eMultiple summary files defining an ensemble can be organized differently in folders. ResInsight support two different modes, Sub Folder and Main Folder.\u003c/p\u003e\n\u003ch3 id=\"sub-folder\"\u003eSub Folder\u003c/h3\u003e\n\u003cp\u003eExample folder structure\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ereal-1/case-1\r\n      /case-2\r\nreal-2/case-1\r\n      /case-2\r\nreal-3/case-1\r\n      /case-2\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eUsing the option \u003cstrong\u003eGroup By Sub Folder\u003c/strong\u003e will identify \u003cstrong\u003ecase-1\u003c/strong\u003e and \u003cstrong\u003ecase-2\u003c/strong\u003e as the ensemble names. This folder structure is used by the \u003cstrong\u003eFMU workflow\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"main-folder\"\u003eMain Folder\u003c/h3\u003e\n\u003cp\u003eExample folder structure\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ecase-1/real-1\r\ncase-1/real-2\r\ncase-1/real-3\r\n\r\ncase-2/real-1\r\ncase-2/real-2\r\ncase-2/real-3\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eUsing the option \u003cstrong\u003eGroup By Main Folder\u003c/strong\u003e will identify \u003cstrong\u003ecase-1\u003c/strong\u003e and \u003cstrong\u003ecase-2\u003c/strong\u003e as the ensemble names. This folder structure is used by the \u003cstrong\u003eEverest workflow\u003c/strong\u003e.\u003c/p\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\u003ch2 id=\"examples-of-use-of-ensemble-import-dialog\"\u003eExamples of Use of Ensemble Import Dialog\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/workflows/ensemblesurface/\"\u003eEnsemble Surface\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Summary\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "Ensemble 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.\nThis dialog is used for import of different file types like *.EGRID, *.SMSPEC, *.TS, *.GRDECL, \u0026hellip;\nThe dialog consists of the following fields:\nPath 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. File Pattern: The search pattern that applies to the file name. * 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 *[!D] Exclude files ending with the character \u0026lsquo;D\u0026rsquo; (file extension is not considered) File Extensions: List of file extensions, ie \u0026ldquo;.EGRID .GRID\u0026rdquo; Use \u0026lsquo;realization-*\u0026rsquo; in filter : Replace the text \u0026ldquo;realization-12\u0026rdquo; with \u0026ldquo;realization-*\u0026rdquo; Ensemble grouping : Group ensemble by Main folder or Sub Folder (Used by FMU workflow) 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. Ensemble File Structure Multiple summary files defining an ensemble can be organized differently in folders. ResInsight support two different modes, Sub Folder and Main Folder.\nSub Folder Example folder structure\nreal-1/case-1\r/case-2\rreal-2/case-1\r/case-2\rreal-3/case-1\r/case-2\rUsing the option Group By Sub Folder will identify case-1 and case-2 as the ensemble names. This folder structure is used by the FMU workflow.\nMain Folder Example folder structure\ncase-1/real-1\rcase-1/real-2\rcase-1/real-3\rcase-2/real-1\rcase-2/real-2\rcase-2/real-3\rUsing the option Group By Main Folder will identify case-1 and case-2 as the ensemble names. This folder structure is used by the Everest workflow.\nAfter 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.\nExamples of Use of Ensemble Import Dialog Ensemble Surface\nEnsemble Summary\n",
+                html:     "\u003ch2 id=\"ensemble-file-import\"\u003eEnsemble 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\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThis dialog is used for import of different file types like *.EGRID, *.SMSPEC, *.TS, *.GRDECL, \u0026hellip;\u003c/p\u003e\n\u003c/div\u003e\r\n\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/*\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.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Pattern\u003c/strong\u003e: The search pattern that applies to the file name.\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\u003cli\u003e\u003cstrong\u003e*[!D]\u003c/strong\u003e Exclude files ending with the character \u0026lsquo;D\u0026rsquo; (file extension is not considered)\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Extensions\u003c/strong\u003e: List of file extensions, ie \u0026ldquo;.EGRID .GRID\u0026rdquo;\u003c/li\u003e\n\u003cli\u003eUse \u0026lsquo;realization-*\u0026rsquo; in filter : Replace the text \u0026ldquo;realization-12\u0026rdquo; with \u0026ldquo;realization-*\u0026rdquo;\u003c/li\u003e\n\u003cli\u003eEnsemble grouping : Group ensemble by Main folder or Sub Folder (Used by FMU workflow)\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\u003ch2 id=\"ensemble-file-structure\"\u003eEnsemble File Structure\u003c/h2\u003e\n\u003cp\u003eMultiple summary files defining an ensemble can be organized differently in folders. ResInsight support two different modes, Sub Folder and Main Folder.\u003c/p\u003e\n\u003ch3 id=\"sub-folder\"\u003eSub Folder\u003c/h3\u003e\n\u003cp\u003eExample folder structure\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ereal-1/case-1\r\n      /case-2\r\nreal-2/case-1\r\n      /case-2\r\nreal-3/case-1\r\n      /case-2\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eUsing the option \u003cstrong\u003eGroup By Sub Folder\u003c/strong\u003e will identify \u003cstrong\u003ecase-1\u003c/strong\u003e and \u003cstrong\u003ecase-2\u003c/strong\u003e as the ensemble names. This folder structure is used by the \u003cstrong\u003eFMU workflow\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"main-folder\"\u003eMain Folder\u003c/h3\u003e\n\u003cp\u003eExample folder structure\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003ecase-1/real-1\r\ncase-1/real-2\r\ncase-1/real-3\r\n\r\ncase-2/real-1\r\ncase-2/real-2\r\ncase-2/real-3\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eUsing the option \u003cstrong\u003eGroup By Main Folder\u003c/strong\u003e will identify \u003cstrong\u003ecase-1\u003c/strong\u003e and \u003cstrong\u003ecase-2\u003c/strong\u003e as the ensemble names. This folder structure is used by the \u003cstrong\u003eEverest workflow\u003c/strong\u003e.\u003c/p\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\u003ch2 id=\"examples-of-use-of-ensemble-import-dialog\"\u003eExamples of Use of Ensemble Import Dialog\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/workflows/ensemblesurface/\"\u003eEnsemble Surface\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Summary\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/import/ensemblefiledialog/"
             };
         
@@ -2885,8 +2884,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.\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",
+                content:  "\nResInsight 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/"
             };
         
@@ -2894,8 +2893,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/linux-installation/"] = {
                 title:    "Linux Installation",
-                content:  "Install From Binary Packages on Linux Please not that the distribution by the OPM Project will be 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 Launch the application using the command ResInsight\nUbuntu 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 Launch the application using the command 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\rCustom Qt configuration If you are using a version of Qt that is not available in system path, you need to do the following to make runtime Qt paths available to ResInsight\nexport LD_LIBRARY_PATH=/path_to_qt\rexport QT_PLUGIN_PATH=/path_to_qt/plugins:$QT_PLUGIN_PATH\r 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 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:     "\u003ch2 id=\"install-from-binary-packages-on-linux\"\u003eInstall From Binary Packages on Linux\u003c/h2\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003ePlease not that the distribution by the OPM Project will be updated some time after the release of a new version on GitHub.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"red-hat-enterprise-linux-6-or-7\"\u003eRed Hat Enterprise Linux 6 or 7\u003c/h3\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\u003eLaunch the application using the command \u003ccode\u003eResInsight\u003c/code\u003e\u003c/p\u003e\n\u003ch3 id=\"ubuntu\"\u003eUbuntu\u003c/h3\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\u003eLaunch the application using the command \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\u003ch2 id=\"custom-qt-configuration\"\u003eCustom Qt configuration\u003c/h2\u003e\n\u003cp\u003eIf you are using a version of Qt that is not available in system path, you need to do the following to make runtime Qt paths available to ResInsight\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eexport LD_LIBRARY_PATH=/path_to_qt\r\nexport QT_PLUGIN_PATH=/path_to_qt/plugins:$QT_PLUGIN_PATH\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"display-menu-icons-in-gnome-optional\"\u003eDisplay Menu Icons in GNOME (Optional)\u003c/h3\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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. \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\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",
+                content:  "Install From Binary Packages on Linux Please not that the distribution by the OPM Project will be updated some time after the release of a new version on GitHub.\nRed 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\rLaunch the application using the command ResInsight\nUbuntu 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\rLaunch the application using the command ResInsight\nFor further installation details, see the ResInsight distribution on Opm Project Downloading and Installing.\nThe binary distributions does not support ABAQUS odb files. For building ResInsight with ABAQUS support, see Build Instructions.\nCustom Qt configuration If you are using a version of Qt that is not available in system path, you need to do the following to make runtime Qt paths available to ResInsight\nexport LD_LIBRARY_PATH=/path_to_qt\rexport QT_PLUGIN_PATH=/path_to_qt/plugins:$QT_PLUGIN_PATH\rDisplay 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\nWorkaround 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-from-binary-packages-on-linux\"\u003eInstall From Binary Packages on Linux\u003c/h2\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003ePlease not that the distribution by the OPM Project will be updated some time after the release of a new version on GitHub.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch3 id=\"red-hat-enterprise-linux-6-or-7\"\u003eRed Hat Enterprise Linux 6 or 7\u003c/h3\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\u003eLaunch the application using the command \u003ccode\u003eResInsight\u003c/code\u003e\u003c/p\u003e\n\u003ch3 id=\"ubuntu\"\u003eUbuntu\u003c/h3\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\u003eLaunch the application using the command \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\u003ch2 id=\"custom-qt-configuration\"\u003eCustom Qt configuration\u003c/h2\u003e\n\u003cp\u003eIf you are using a version of Qt that is not available in system path, you need to do the following to make runtime Qt paths available to ResInsight\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eexport LD_LIBRARY_PATH=/path_to_qt\r\nexport QT_PLUGIN_PATH=/path_to_qt/plugins:$QT_PLUGIN_PATH\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"display-menu-icons-in-gnome-optional\"\u003eDisplay Menu Icons in GNOME (Optional)\u003c/h3\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003egconftool-2 --type boolean --set /desktop/gnome/interface/buttons_have_icons true\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003egconftool-2 --type boolean --set /desktop/gnome/interface/menus_have_icons true\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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. \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\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/"
             };
         
@@ -2903,7 +2902,7 @@ 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 Preferences dialog available from the Edit -\u0026gt; Preferences menu. Preferences are not stored in project files, but in a platform specific way for each user. Essential preferences are listed below.\nGeneral 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.\n  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 fonts preferences when using 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 plot legends, axes, and labels.    3D Views: This group of options controls visual settings to 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 the use of mouse for interaction with 3D model, c.f. Model Navigation. 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. Enable Faults by Default \u0026ndash; Controls default visibility of faults in views Show Info Box in New Projects \u0026ndash; Controls default visibility Info Box in upper right corner Show Grid Box in New Projects \u0026ndash; Controls default visibility of grid box    Other:\n SSIHUB Address \u0026ndash; Optional URL to Equinor internal web service used to import well paths Enable Undo/Redo for Property Editor Changes \u0026ndash; enable undo/redo functionality    Grid  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 per default. Import Faults/NNCs/Advanced MSW Data \u0026ndash; Disable options 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 (stored in the same directory as the *.EGRID file with filename \u0026lt;casename\u0026gt;.RESINSIGHT_IDX) If existing, ResInsight will use the index file when loading the case resulting in a significant speedup. Skip Import of Simulation Well Data \u0026ndash; Disable import of simulation well data for reducing case import time.  Summary  Origin Files: c.f. Origin Files for details. Summary Data Import including file format for summary data import, c.f. Ensemble Summary:  h5 (HDF5) Import data from h5 files UNSMRY (libecl) Import data from native UNSMRY files ESMRY (opm-common) Import data from ESMRY files    Plotting   Summary Plots:\n Create Plot On Summary Data Import: governs automatic creation of summary plots when importing a summary case  No Plots: do not automatically create summary plots Use Data Vector Names: Create summary plots automatically based on given vector names, e.g. FOPT WOPT* Use Plot Templates: Create summary plots automatically based on default templates.   Default Curve Style for History Vectors: allows specifying symbols and/or lines as preference. Append History Vectors: automatically include the corresponding history vector when appending a simulated summary vector. Curve Color By Phase: distinguish each phase by separate color.    Multi Plot Defaults: specification of number of rows and columns for each page containing multiple summary plots.\n  Plot Templates: specification of folders and folder search depth for templates.\n Press Append to browse for folder to append. Specify Maximum Plot Template Folder Search Depth to restrict the depth of subdirectories to be searched for templates.    General\n Date and Time format preferences. Page Setup: Physical page size, orientation, and margins.    Please consider the location and folders of your templates with care to cater for structured usage but also to limit the folder search depth for performance reasons.\n\rScripting   Octave c.f. Octave Interface for details:\n Octave Executable Location \u0026ndash; Define 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 from octave when started.    Python c.f. ResInsight Python API for details:\n Enable Python Script Server Show Python Debug Info Default Python Script Server Port Python Executable Location    Script Files:\n Shared Script Folder(s) \u0026ndash; Defines the search paths for octave scripts Script Editor \u0026ndash; The text editor to invoke when editing scripts    ",
+                content:  "In this section the different settings that controls the default behavior of ResInsight is described. These settings can be controlled using the Preferences dialog available from the Edit -\u0026gt; Preferences menu. Preferences are not stored in project files, but in a platform specific way for each user. Essential preferences are listed below.\nGeneral 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.\nDefault Colors: This group contains the colors that will be applied to the 3D views:\nViewer Background Mesh Color Mesh Color Along Faults Well Label Color Default Font Sizes: This group contains fonts preferences when using ResInsight:\nViewer 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 plot legends, axes, and labels. 3D Views: This group of options controls visual settings to be used when creating new views:\nShow Grid Lines \u0026ndash; Controls whether to show the grid lines by default for all cells or just along faults. Navigation mode \u0026ndash; Defines the use of mouse for interaction with 3D model, c.f. Model Navigation. 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. Enable Faults by Default \u0026ndash; Controls default visibility of faults in views Show Info Box in New Projects \u0026ndash; Controls default visibility Info Box in upper right corner Show Grid Box in New Projects \u0026ndash; Controls default visibility of grid box Other:\nSSIHUB Address \u0026ndash; Optional URL to Equinor internal web service used to import well paths Enable Undo/Redo for Property Editor Changes \u0026ndash; enable undo/redo functionality Grid 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 per default. Import Faults/NNCs/Advanced MSW Data \u0026ndash; Disable options 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 (stored in the same directory as the *.EGRID file with filename \u0026lt;casename\u0026gt;.RESINSIGHT_IDX) If existing, ResInsight will use the index file when loading the case resulting in a significant speedup. Skip Import of Simulation Well Data \u0026ndash; Disable import of simulation well data for reducing case import time. Summary Origin Files: c.f. Origin Files for details. Summary Data Import including file format for summary data import, c.f. Ensemble Summary: h5 (HDF5) Import data from h5 files UNSMRY (libecl) Import data from native UNSMRY files ESMRY (opm-common) Import data from ESMRY files Plotting Summary Plots:\nCreate Plot On Summary Data Import: governs automatic creation of summary plots when importing a summary case No Plots: do not automatically create summary plots Use Data Vector Names: Create summary plots automatically based on given vector names, e.g. FOPT WOPT* Use Plot Templates: Create summary plots automatically based on default templates. Default Curve Style for History Vectors: allows specifying symbols and/or lines as preference. Append History Vectors: automatically include the corresponding history vector when appending a simulated summary vector. Curve Color By Phase: distinguish each phase by separate color. Multi Plot Defaults: specification of number of rows and columns for each page containing multiple summary plots.\nPlot Templates: specification of folders and folder search depth for templates.\nPress Append to browse for folder to append. Specify Maximum Plot Template Folder Search Depth to restrict the depth of subdirectories to be searched for templates. General\nDate and Time format preferences. Page Setup: Physical page size, orientation, and margins. Please consider the location and folders of your templates with care to cater for structured usage but also to limit the folder search depth for performance reasons.\nScripting Octave c.f. Octave Interface for details:\nOctave Executable Location \u0026ndash; Define 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 from octave when started. Python c.f. ResInsight Python API for details:\nEnable Python Script Server Show Python Debug Info Default Python Script Server Port Python Executable Location Script Files:\nShared Script Folder(s) \u0026ndash; Defines the search paths for octave scripts Script Editor \u0026ndash; The text editor to invoke when editing scripts ",
                 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\u003ePreferences\u003c/strong\u003e dialog available from the \u003cstrong\u003eEdit -\u0026gt; Preferences\u003c/strong\u003e menu.\nPreferences are not stored in project files, but in a platform specific way for each user.\nEssential preferences are listed below.\u003c/p\u003e\n\u003ch2 id=\"general\"\u003eGeneral\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesGeneral.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\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDefault Colors\u003c/strong\u003e: This 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\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eDefault Font Sizes\u003c/strong\u003e: This group contains fonts preferences when using 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 plot legends, axes, and labels.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003e3D Views\u003c/strong\u003e: This group of options controls visual settings to 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 the use of mouse for interaction with 3D model, c.f.  \u003ca href=\"/getting-started/modelnavigation/\"\u003eModel Navigation\u003c/a\u003e.\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\u003eEnable Faults by Default\u003c/strong\u003e \u0026ndash; Controls default visibility of faults in views\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Info Box in New Projects\u003c/strong\u003e \u0026ndash; Controls default visibility Info Box in upper right corner\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Grid Box in New Projects\u003c/strong\u003e \u0026ndash; Controls default visibility of grid box\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eOther\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\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\u003eEnable Undo/Redo for Property Editor Changes\u003c/strong\u003e \u0026ndash; enable undo/redo functionality\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"grid\"\u003eGrid\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesEclipseGrid.png\" alt=\"\"\u003e\u003c/p\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 per default.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eImport Faults/NNCs/Advanced MSW Data\u003c/strong\u003e \u0026ndash; Disable options 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 (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 existing, ResInsight will use the index file 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 reducing case import time.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"summary\"\u003eSummary\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesEclipseSummary.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOrigin Files\u003c/strong\u003e: c.f. \u003ca href=\"/import/eclipsesummarydata/#origin-files\"\u003eOrigin Files\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSummary Data Import\u003c/strong\u003e including file format for summary data import, c.f. \u003ca href=\"/import/eclipsesummarydata/#summary-data-file-formats\"\u003eEnsemble Summary\u003c/a\u003e:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eh5 (HDF5)\u003c/strong\u003e Import data from h5 files\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUNSMRY (libecl)\u003c/strong\u003e Import data from native UNSMRY files\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eESMRY (opm-common)\u003c/strong\u003e Import data from ESMRY files\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"plotting\"\u003ePlotting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesPlotting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eSummary Plots\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCreate Plot On Summary Data Import\u003c/strong\u003e: governs automatic creation of summary plots when importing a summary case\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eNo Plots\u003c/em\u003e: do not automatically create summary plots\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eUse Data Vector Names\u003c/em\u003e: Create summary plots automatically based on given vector names, e.g. \u003ccode\u003eFOPT WOPT*\u003c/code\u003e\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eUse Plot Templates\u003c/em\u003e: Create summary plots automatically based on default templates.\u003c/li\u003e\n\u003c/ul\u003e\n\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\u003eAppend History Vectors\u003c/strong\u003e: automatically include the corresponding history vector when appending a simulated summary vector.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurve Color By Phase\u003c/strong\u003e: distinguish each phase by separate color.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eMulti Plot Defaults\u003c/strong\u003e: specification of number of rows and columns for each page containing multiple summary plots.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ePlot Templates\u003c/strong\u003e: specification of folders and folder search depth for templates.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ePress \u003cstrong\u003eAppend\u003c/strong\u003e to browse for folder to append.\u003c/li\u003e\n\u003cli\u003eSpecify \u003cstrong\u003eMaximum Plot Template Folder Search Depth\u003c/strong\u003e to restrict the depth of subdirectories to be searched for templates.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eGeneral\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDate\u003c/strong\u003e and \u003cstrong\u003eTime\u003c/strong\u003e format preferences.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePage Setup\u003c/strong\u003e: Physical page size, orientation, and margins.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003ePlease consider the location and folders of your templates with care to cater for structured usage but also to limit the folder search depth for performance reasons.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"scripting\"\u003eScripting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/PreferencesScripting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eOctave\u003c/strong\u003e c.f. \u003ca href=\"/scripting/octaveinterface/\"\u003eOctave Interface\u003c/a\u003e for details:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eOctave Executable Location\u003c/strong\u003e \u0026ndash; Define 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 from octave when started.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ePython\u003c/strong\u003e c.f.  \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e for details:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eEnable Python Script Server\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Python Debug Info\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDefault Python Script Server Port\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePython Executable Location\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eScript Files\u003c/strong\u003e:\u003c/p\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\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/misc/preferences/"
             };
@@ -2912,7 +2911,7 @@ if (!doNotTrack) {
          
             window.store["/import/roffgridmodels/"] = {
                 title:    "ROFF Grid Models",
-                content:  "ResInsight supports the following type of ROFF input data:\n *.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format.  Roff Data Roff Data can be imported from File-\u0026gt;Import-\u0026gt;Roff Grid Models-\u0026gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.\nOperations on 3D Grid Models\n",
+                content:  "ResInsight supports the following type of ROFF input data:\n*.ROFF and *.ROFFASC containing data from RMS as Roxar Open File Format (ROFF) in binary or ascii format. Roff Data Roff Data can be imported from File-\u0026gt;Import-\u0026gt;Roff Grid Models-\u0026gt;Import Roff Case menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.\nOperations on 3D Grid Models\n",
                 html:     "\u003cp\u003eResInsight supports the following type of \u003cstrong\u003eROFF\u003c/strong\u003e input data:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003e\u003ccode\u003e*.ROFF\u003c/code\u003e\u003c/em\u003e and \u003cem\u003e\u003ccode\u003e*.ROFFASC\u003c/code\u003e\u003c/em\u003e containing data from \u003cstrong\u003eRMS\u003c/strong\u003e as Roxar Open File Format (ROFF) in binary or ascii format.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"roff-data\"\u003eRoff Data\u003c/h2\u003e\n\u003cp\u003eRoff Data can be imported from \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Roff Grid Models-\u0026gt;Import Roff Case\u003c/strong\u003e menu. Select a grid file and additional files with properties in the import dialog. The grid will be displayed and used in the same way as an Eclipse grid model.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/3dviews/\"\u003eOperations on 3D Grid Models\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/import/roffgridmodels/"
             };
@@ -2921,8 +2920,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 right-click 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. Disks \u0026ndash; Visualization of production and injection rates and cumulative production and injection with oil, gas, and water phases. 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.  Disks Disks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\nDisplay of Disks are enabled from Simulations Wells, c.f. figure below. Property Type defaults to predefined production and injection properties but also allows for selection of a single property. When showing Quantity Labels, it is often useful to also activate Show Label Background.\nIndividual 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. Valves are visulized on the pipe geometry.\nReading this information is somewhat time consuming, and can be turned off in Preferences .\nGeometry Approximation If the import of MSW data is disabled, or MSW data is not present, the topology of the well is estimated. This feature works in most cases, but can generate invalid well geometry in some cases.\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 right-click 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/flow-diagnostics-plots/\"\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\u003eDisks\u003c/strong\u003e \u0026ndash; Visualization of production and injection rates and cumulative production and injection with oil, gas, and water phases.\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\u003ch3 id=\"disks\"\u003eDisks\u003c/h3\u003e\n\u003cp\u003eDisks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\u003c/p\u003e\n\u003cp\u003eDisplay of \u003cstrong\u003eDisks\u003c/strong\u003e are enabled from \u003cstrong\u003eSimulations Wells\u003c/strong\u003e, c.f. figure below. \u003cem\u003eProperty Type\u003c/em\u003e defaults to predefined production and injection properties but also allows for selection of a single property. When showing \u003cem\u003eQuantity Labels\u003c/em\u003e, it is often useful to also activate \u003cem\u003eShow Label Background\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellDisks.png\" alt=\"\"\u003e\u003c/p\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\u003e\u003cimg src=\"/images/getting-started/msw_with_valves.png\" alt=\"\"\u003e\u003c/p\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. Valves are visulized on the pipe geometry.\u003c/p\u003e\n\u003cp\u003eReading this information is somewhat time consuming, and can be turned off in \u003ca href=\"/misc/preferences/\"\u003e Preferences \u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"geometry-approximation\"\u003eGeometry Approximation\u003c/h3\u003e\n\u003cp\u003eIf the import of MSW data is disabled, or MSW data is not present, the topology of the well is estimated. This feature works in most cases, but can generate invalid well geometry in some cases.\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",
+                content:  "\nThis 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 right-click commands on a simulation well. These commands are available either by right-clicking the well in the 3D View or in the Project Tree.\nNew 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.\nWells 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. Disks \u0026ndash; Visualization of production and injection rates and cumulative production and injection with oil, gas, and water phases. 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:\nUnique 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. Disks Disks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\nDisplay of Disks are enabled from Simulations Wells, c.f. figure below. Property Type defaults to predefined production and injection properties but also allows for selection of a single property. When showing Quantity Labels, it is often useful to also activate Show Label Background.\nIndividual 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. Valves are visulized on the pipe geometry.\nReading this information is somewhat time consuming, and can be turned off in Preferences .\nGeometry Approximation If the import of MSW data is disabled, or MSW data is not present, the topology of the well is estimated. This feature works in most cases, but can generate invalid well geometry in some cases.\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 right-click 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/flow-diagnostics-plots/\"\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\u003eDisks\u003c/strong\u003e \u0026ndash; Visualization of production and injection rates and cumulative production and injection with oil, gas, and water phases.\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\u003ch3 id=\"disks\"\u003eDisks\u003c/h3\u003e\n\u003cp\u003eDisks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\u003c/p\u003e\n\u003cp\u003eDisplay of \u003cstrong\u003eDisks\u003c/strong\u003e are enabled from \u003cstrong\u003eSimulations Wells\u003c/strong\u003e, c.f. figure below. \u003cem\u003eProperty Type\u003c/em\u003e defaults to predefined production and injection properties but also allows for selection of a single property. When showing \u003cem\u003eQuantity Labels\u003c/em\u003e, it is often useful to also activate \u003cem\u003eShow Label Background\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellDisks.png\" alt=\"\"\u003e\u003c/p\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\u003e\u003cimg src=\"/images/getting-started/msw_with_valves.png\" alt=\"\"\u003e\u003c/p\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. Valves are visulized on the pipe geometry.\u003c/p\u003e\n\u003cp\u003eReading this information is somewhat time consuming, and can be turned off in \u003ca href=\"/misc/preferences/\"\u003e Preferences \u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"geometry-approximation\"\u003eGeometry Approximation\u003c/h3\u003e\n\u003cp\u003eIf the import of MSW data is disabled, or MSW data is not present, the topology of the well is estimated. This feature works in most cases, but can generate invalid well geometry in some cases.\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/"
             };
         
@@ -2930,8 +2929,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:     "\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 \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand Line Interface\u003c/a\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",
+                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 ).\nAdvanced 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:\nView \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 \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand Line Interface\u003c/a\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/"
             };
         
@@ -2939,8 +2938,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryplots/"] = {
                 title:    "Summary Plots",
-                content:  "Summary Plots are a display of curves based on Eclipse Summary Data which can be combined with imported observed data, grid cell time history curve, and pasted ascii curves.\nSummary plots are displayed on screen by maximum four rows by four columns of plots. In the example above, ResInsight displays two columns and two rows of plots, each plot comprising a single curve. However, a plot may contain an arbitrary number of curves. As shown in the screenshot above, essential helpers for setup of Summary Plots are:\n Plots: overview of established plots and their components Property Editor: settings for titles, legends, layout, axes, and appearance Data Sources: searching and sourcing data from case, field, regions, wells, groups, or ensemble Templates: overview, management and use of templates for summary plotting Plot Manager: powerful text-based selection of vectors for summary plotting  Essential actions are presented as controls in the toolbar to increase productivity and ease of use.\nCreating Summary Plots Using Data Sources to create Summary Plots Having imported Eclipse Summary Data, Data Sources provides an easy approach to create Summary Plots:\n Search or navigate Data Sources to find the desired source(s) and vector(s) Right-click selected vector(s) and select New Summary Plot Drag \u0026amp; Drop additional vector(s) to append curves into an existing plot or vacant plot area  Creating a new summary plot of WBHP of Well B-1H and subsequent Drag \u0026amp; Drop of WGOR and WGORH into the same subplot produces the following. ResInsight will automatically make new axes if necessary. If units are the same as for WGOR and WGORH, a new axis is unnecessary.\nUsing Plot Manager to create Summary Plots Having imported Eclipse Summary Data, the Plot Manager provides an alternative and powerful approach to create Summary Plots by text-based selection of data sources and vectors to plot.\nSummary Plots and Functionality Multiple Summary Plots and Curves The Data Sources window enables efficient creation of multiple plots and curves by Right-clicking:\n Use Append Curves to append curves for the selected vectors into all existing plots. Use Append Plots for Wells to create separate plots for the selected vectors.  If a plot contains curves pertinent to a single data source, you may easily append corresponding plots for other entries of the type by right-clicking or drag and drop. In the examples above, the curves are pertinent to the single data source well B-1H. Thus you may easily append corresponding plots for other wells by right-clicking as shown below.\nAlternatively, you may simply and efficiently drag and drop the selected wells into the plot area. In fact, you may drag the entire folder into plot area to append plots for all wells.\nSubsequently, you may:\n Adjust the number of columns and rows and preview the pages of plots using the toolbar  Use keyboard PgUp/PgDown or scroll wheel to browse and validate the pages of plots Snapshot the curves or export to PDF-file via the toolbar-buttons or Edit menu  The data source of displayed curves is rapidly changed by Summary Plot Source Stepping.\nVisual comparison of multiple summary curves ResInsight may ease comparison of multiple summary curves by selecting a plot in Plots and using the settings in Property Editor group Axes.\nThe different options are:\n Y Axis Range: Defines the data source for Y Axis range to either individual, all subplots, all wells, all regions, or all realizations. Link Y Axes: When checked, the axes of all subplots will be treated to obtain plots with identical axes. Link Time Axis: When checked, the time axes of all subplots will identical. Auto Plot Settings: When checked, ResInsight creates axes with titles, ranges, tickmarks, and units for best possible appearance.  Plot Mouse Interaction  Value Tracking: When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value is displayed in a tooltip. Selection: Left mouse button click can be used to select several items of the plot and display them in the Property Editor:  The closest curve Each plot axis The summary plot itself if none of the above is hit and the Plots window is activated by the mouse click   Window Zoom: Available by dragging the mouse with left mouse button pressed across plot area of interest. Wheel Zoom: The mouse wheel will zoom the plot in and out towards the current mouse cursor position presupposing use of mouse wheel is not disabled by toolbar button .  You may simply double click a subplot to restore its default zoom level. Use toolbar button or View menu option Zoom All to restore default zoom level for the entire plot.\nFor scrolling multiple pages of plots by using the mouse wheel, disable Wheel Zoom by the toolbar button .\nHighlighting a curve or axis A summary curve is highlighted when left-clicked in a plot. This eases detailed investigation of a specific curve in plots comprising many curves.\nAnother essential feature is to left-click an axis in a summary plot which will highlight the curves corresponding to the particular axis. As exemplified below, clicking the axis Gas Production Total highlights the WGPT curve and dims the other curves.\nSummary curves can also be activated and deactivated by clicking the check-boxes in Plots window. See also Plots right-click menu items, e.g. On - Others Off which is an effective way to deactivate all curves not selected.\nDuplicate plot, Copy and Paste An entire summary plot may be duplicated using the toolbar button Duplicate Plot.\nCopy and Paste of a summary plot, subplot (see below) or curve is also possible using the Plots right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V). This enables pasting a subplot or curve to wherever desired in the the Plots tree.\nFiltering of subplots Filtering of subplots allows the user to disable/hide subplots containing data below a user defined threshold. To activate filtering of subplots, click a plot in Plots window, set the Y-axis Threshold in Property Editor, and click Apply Filter.\nSplitting a plot into subplots A plot with many curves can easily be split into multiple subplots. Right-click a composite plot in Plots and select Split Into Single Curve Plots to split into subplots each comprising one curve.\nAccessing Plot Data Right-clicking a plot in Plots window and selecting Show Plot Data will open a window containing the plot data as text columns. The window displays plot data 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 by the right-click command Export to File.\nEditing Summary Plots A color selection dialog can be opened by clicking on the color icon in the Project Tree. The settings of each plot are listed in the Plots window for overview and are controlled by its sub-items and the Property Editor. Editing a Summary Curve By selecting a specific summary curve in the Plots window, its properties are displayed by the Property Editor.\nThe Property Editor organizes the available options into the following groups:\n Summary Vector \u0026ndash; Options to select case, vector to plot, resampling, axis specification, and error bars. Stacking - Options to control stacking of curves optionally with phase colors. 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.  Other actions are available via right-click menu for selected curve. For instance, the Y-Axis for one or more curves can be switched for using the right-click command Switch Plot Axis.\nDefault Time Axis Properties Time axis properties are displayed by clicking the Time Axis subitem of a summary plot in Plots window.\nCustom Time Axis Properties The time labels are automatically defined based on the available date range. The tick marks can be controlled in details by setting Tickmark Type to Custom. Then a tickmark interval and tickmark interval step can be defined.\nIn the screenshot above, the interval is set to three years, and the plot displays labesl with three years between each.\nY-axis Properties Y-axis properties are displayed by clicking one of the left/right axis subitems of a summary plot in Plots window.\nThe property groups are:\n Title Text: Caters for automatic or user specification of title and inclusion of vector name, acronym, and units in plot. Title Layout: Positioning of title (Center or At End) and font size. Axis Values: Logarithmic scale, inversion of axis, legend number formatting, scale factor, max/max range, and font size.  Changing content of a Summary Plot Right-clicking an existing summary plot in Plots and selecting Edit Summary Plot initiates the Summary Plot Editor which offers complete functionality to navigate and select vectors from all summary types.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary Plots are a display of curves based on \n\u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e\nwhich can be combined with \n\u003ca href=\"/import/observeddata/\"\u003eimported observed data\u003c/a\u003e, \n\u003ca href=\"/3d-main-window/resultinspection/#result-plot\"\u003egrid cell time history curve\u003c/a\u003e, and \n\u003ca href=\"/import/pasteexceltimedata/\"\u003epasted ascii curves\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eSummary plots are displayed on screen by maximum four rows by four columns of plots. \nIn the example above, ResInsight displays two columns and two rows of plots, each plot comprising a single curve. However, a plot may contain an arbitrary number of curves.\nAs shown in the screenshot above, essential helpers for setup of Summary Plots are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlots\u003c/strong\u003e: overview of established plots and their components\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e: settings for titles, legends, layout, axes, and appearance\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e:\nsearching and sourcing data from case, field, regions, wells, groups, or ensemble\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003e\u003cstrong\u003eTemplates\u003c/strong\u003e\u003c/a\u003e:\noverview, management and use of templates for summary plotting\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e:\npowerful text-based selection of vectors for summary plotting\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEssential actions are presented as controls in the toolbar to increase productivity and ease of use.\u003c/p\u003e\n\u003ch2 id=\"creating-summary-plots\"\u003eCreating Summary Plots\u003c/h2\u003e\n\u003ch3 id=\"using-data-sources-to-create-summary-plots\"\u003eUsing Data Sources to create Summary Plots\u003c/h3\u003e\n\u003cp\u003eHaving imported \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e, \u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e provides an easy approach to create Summary Plots:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSearch or navigate \u003cstrong\u003eData Sources\u003c/strong\u003e to find the desired source(s) and vector(s)\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eRight-click\u003c/em\u003e selected vector(s) and select \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eDrag \u0026amp; Drop\u003c/em\u003e additional vector(s) to append curves into an existing plot or vacant plot area\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eCreating a new summary plot of \u003cem\u003eWBHP\u003c/em\u003e of \u003cem\u003eWell B-1H\u003c/em\u003e and subsequent \u003cem\u003eDrag \u0026amp; Drop\u003c/em\u003e of WGOR and WGORH into the same subplot produces the following. \nResInsight will automatically make new axes if necessary. If units are the same as for WGOR and WGORH, a new axis is unnecessary.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlots_WBHP_WGOR.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"using-plot-manager-to-create-summary-plots\"\u003eUsing Plot Manager to create Summary Plots\u003c/h3\u003e\n\u003cp\u003eHaving imported \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e, the \n\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e \nprovides an alternative and powerful approach to create Summary Plots by text-based selection of data sources and vectors to plot.\u003c/p\u003e\n\u003ch2 id=\"summary-plots-and-functionality\"\u003eSummary Plots and Functionality\u003c/h2\u003e\n\u003ch3 id=\"multiple-summary-plots-and-curves\"\u003eMultiple Summary Plots and Curves\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e window enables efficient creation of multiple plots and curves by Right-clicking:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUse \u003cem\u003eAppend Curves\u003c/em\u003e to append curves for the selected vectors into all existing plots.\u003c/li\u003e\n\u003cli\u003eUse \u003cem\u003eAppend Plots for Wells\u003c/em\u003e to create separate plots for the selected vectors.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsAppendVectorsForWells.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf a plot contains curves pertinent to a single data source, you may easily append corresponding plots for other entries of the type by right-clicking or \u003cem\u003edrag and drop\u003c/em\u003e. In the examples above, the curves are pertinent to the single data source well B-1H. Thus you may easily append corresponding plots for other wells by right-clicking as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsAppendPlotsForWells.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, you may simply and efficiently \u003cstrong\u003edrag and drop\u003c/strong\u003e the selected wells into the plot area.\nIn fact, you may drag the entire folder \u003cimg src=\"https://resinsight.org/images/plot-window/DataSourcesWell.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n into plot area to append plots for all wells.\u003c/p\u003e\n\u003cp\u003eSubsequently, you may:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAdjust the number of columns and rows and preview the pages of plots using the toolbar \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlotToolbarRowColumnPreview.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eUse keyboard PgUp/PgDown or scroll wheel to browse and validate the pages of plots\u003c/li\u003e\n\u003cli\u003eSnapshot the curves or export to PDF-file via the toolbar-buttons \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlotToolbarSnapshot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cem\u003eEdit\u003c/em\u003e menu\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe data source of displayed curves is rapidly changed by \u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"visual-comparison-of-multiple-summary-curves\"\u003eVisual comparison of multiple summary curves\u003c/h3\u003e\n\u003cp\u003eResInsight may ease comparison of multiple summary curves by selecting a plot in \u003cstrong\u003ePlots\u003c/strong\u003e and using the settings in \u003cstrong\u003eProperty Editor\u003c/strong\u003e group \u003cstrong\u003eAxes\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotPropertyEditorAxes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe different options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eY Axis Range\u003c/em\u003e: Defines the data source for Y Axis range to either individual, all subplots, all wells, all regions, or all realizations.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eLink Y Axes\u003c/em\u003e: When checked, the axes of all subplots will be treated to obtain plots with identical axes.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eLink Time Axis\u003c/em\u003e: When checked, the time axes of all subplots will identical.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eAuto Plot Settings\u003c/em\u003e: When checked, ResInsight creates axes with titles, ranges, tickmarks, and units for best possible appearance.\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: When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value is displayed in a tooltip.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelection\u003c/strong\u003e: Left mouse button click can be used to select several items of the plot and display them in the Property Editor:\n\u003cul\u003e\n\u003cli\u003eThe closest curve\u003c/li\u003e\n\u003cli\u003eEach plot axis\u003c/li\u003e\n\u003cli\u003eThe summary plot itself if none of the above is hit and the \u003cstrong\u003ePlots\u003c/strong\u003e 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: Available by dragging the mouse with left mouse button pressed across plot area of interest.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWheel Zoom\u003c/strong\u003e: The mouse wheel will zoom the plot in and out towards the current mouse cursor position presupposing use of mouse wheel is not disabled by toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomDisableMouseWheelCapture.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eYou may simply \u003cstrong\u003edouble click\u003c/strong\u003e a subplot to restore its default zoom level.\nUse toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomAll16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cem\u003eView\u003c/em\u003e menu option \u003cstrong\u003eZoom All\u003c/strong\u003e to restore default zoom level for the entire plot.\u003c/p\u003e\n\u003cp\u003eFor scrolling multiple pages of plots by using the mouse wheel, disable \u003cem\u003eWheel Zoom\u003c/em\u003e by the toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomDisableMouseWheelCapture.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003ch3 id=\"highlighting-a-curve-or-axis\"\u003eHighlighting a curve or axis\u003c/h3\u003e\n\u003cp\u003eA summary curve is highlighted when left-clicked in a plot. This eases detailed investigation of a specific curve in plots comprising many curves.\u003c/p\u003e\n\u003cp\u003eAnother essential feature is to left-click an axis in a summary plot which will highlight the curves corresponding to the particular axis. As exemplified below, clicking the axis \u003cem\u003eGas Production Total\u003c/em\u003e highlights the \u003cem\u003eWGPT\u003c/em\u003e curve and dims the other curves.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary curves can also be activated and deactivated by clicking the check-boxes in \u003cstrong\u003ePlots\u003c/strong\u003e window. See also \u003cstrong\u003ePlots\u003c/strong\u003e right-click menu items, e.g. \u003cem\u003eOn - Others Off\u003c/em\u003e which is an effective way to deactivate all curves not selected.\u003c/p\u003e\n\u003ch3 id=\"duplicate-plot-copy-and-paste\"\u003eDuplicate plot, Copy and Paste\u003c/h3\u003e\n\u003cp\u003eAn entire summary plot may be duplicated using the toolbar button \n\u003cimg src=\"https://resinsight.org/images/plot-window/ToolbarDuplicatePlot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eDuplicate Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eCopy and Paste of a summary plot, subplot (see below) or curve is also possible using the \u003cstrong\u003ePlots\u003c/strong\u003e right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V). This enables pasting a subplot or curve to wherever desired in the the \u003cstrong\u003ePlots\u003c/strong\u003e tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySubplotCopy.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"filtering-of-subplots\"\u003eFiltering of subplots\u003c/h3\u003e\n\u003cp\u003eFiltering of subplots allows the user to disable/hide subplots containing data below a user defined threshold.\nTo activate filtering of subplots, click a plot in \u003cstrong\u003ePlots\u003c/strong\u003e window, set the \u003cem\u003eY-axis Threshold\u003c/em\u003e in Property Editor, and click \u003cem\u003eApply Filter\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotVisibilityFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"splitting-a-plot-into-subplots\"\u003eSplitting a plot into subplots\u003c/h3\u003e\n\u003cp\u003eA plot with many curves can easily be split into multiple subplots. \nRight-click a composite plot in \u003cstrong\u003ePlots\u003c/strong\u003e and select \u003cstrong\u003eSplit Into Single Curve Plots\u003c/strong\u003e to split  into subplots each comprising one curve.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotSplitIntoSingleCurvePlots.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"accessing-plot-data\"\u003eAccessing Plot Data\u003c/h3\u003e\n\u003cp\u003eRight-clicking a plot in \u003cstrong\u003ePlots\u003c/strong\u003e window and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will open a window containing the plot data as text columns. \nThe window displays plot data 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 by the right-click command \u003cstrong\u003eExport to File\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"editing-summary-plots\"\u003eEditing Summary Plots\u003c/h2\u003e\n\u003cp\u003eA color selection dialog can be opened by clicking on the color icon in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/ColorSelectionDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe settings of each plot are listed in the \u003cstrong\u003ePlots\u003c/strong\u003e window for overview and are controlled by its sub-items and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/SummaryCurveSelection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"editing-a-summary-curve\"\u003eEditing a Summary Curve\u003c/h3\u003e\n\u003cp\u003eBy selecting a specific summary curve in the \u003cstrong\u003ePlots\u003c/strong\u003e window, its properties are displayed 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\u003eThe 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, resampling, axis specification, and error bars.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStacking\u003c/strong\u003e - Options to control stacking of curves optionally with phase colors.\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\u003cp\u003eOther actions are available via right-click menu for selected curve. For instance, the Y-Axis for one or more curves can be switched for using the right-click command \u003cb\u003eSwitch Plot Axis\u003c/b\u003e.\u003c/p\u003e\n\u003ch3 id=\"default-time-axis-properties\"\u003eDefault Time Axis Properties\u003c/h3\u003e\n\u003cp\u003eTime axis properties are displayed by clicking the \u003cstrong\u003eTime Axis\u003c/strong\u003e subitem of a summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryTimeAxisProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"custom-time-axis-properties\"\u003eCustom Time Axis Properties\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary-custom-tick-marks.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe time labels are automatically defined based on the available date range. The tick marks can be controlled in details by setting \u003cstrong\u003eTickmark Type\u003c/strong\u003e to \u003cstrong\u003eCustom\u003c/strong\u003e. Then a tickmark interval and tickmark interval step can be defined.\u003c/p\u003e\n\u003cp\u003eIn the screenshot above, the interval is set to three years, and the plot displays labesl with three years between each.\u003c/p\u003e\n\u003ch3 id=\"y-axis-properties\"\u003eY-axis Properties\u003c/h3\u003e\n\u003cp\u003eY-axis properties are displayed by clicking one of the left/right axis subitems of a summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_plot_yaxis_properties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe property groups are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Text\u003c/strong\u003e: Caters for automatic or user specification of title and inclusion of vector name, acronym, and units in plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Layout\u003c/strong\u003e: Positioning of title (\u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e) and font size.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Values\u003c/strong\u003e: Logarithmic scale, inversion of axis, legend number formatting, scale factor, \nmax/max range, and font size.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"changing-content-of-a-summary-plot\"\u003eChanging content of a Summary Plot\u003c/h3\u003e\n\u003cp\u003eRight-clicking an existing summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e and selecting \u003cem\u003eEdit Summary Plot\u003c/em\u003e initiates the \n\u003ca href=\"/plot-window/summaryploteditor/\"\u003e\u003cem\u003eSummary Plot Editor\u003c/em\u003e\u003c/a\u003e which offers complete functionality to navigate and select vectors from all summary types.\u003c/p\u003e\n",
+                content:  "\nSummary Plots are a display of curves based on Eclipse Summary Data which can be combined with imported observed data, grid cell time history curve, and pasted ascii curves.\nSummary plots are displayed on screen by maximum four rows by four columns of plots. In the example above, ResInsight displays two columns and two rows of plots, each plot comprising a single curve. However, a plot may contain an arbitrary number of curves. As shown in the screenshot above, essential helpers for setup of Summary Plots are:\nPlots: overview of established plots and their components Property Editor: settings for titles, legends, layout, axes, and appearance Data Sources: searching and sourcing data from case, field, regions, wells, groups, or ensemble Templates: overview, management and use of templates for summary plotting Plot Manager: powerful text-based selection of vectors for summary plotting Essential actions are presented as controls in the toolbar to increase productivity and ease of use.\nCreating Summary Plots Using Data Sources to create Summary Plots Having imported Eclipse Summary Data, Data Sources provides an easy approach to create Summary Plots:\nSearch or navigate Data Sources to find the desired source(s) and vector(s) Right-click selected vector(s) and select New Summary Plot Drag \u0026amp; Drop additional vector(s) to append curves into an existing plot or vacant plot area Creating a new summary plot of WBHP of Well B-1H and subsequent Drag \u0026amp; Drop of WGOR and WGORH into the same subplot produces the following. ResInsight will automatically make new axes if necessary. If units are the same as for WGOR and WGORH, a new axis is unnecessary.\nUsing Plot Manager to create Summary Plots Having imported Eclipse Summary Data, the Plot Manager provides an alternative and powerful approach to create Summary Plots by text-based selection of data sources and vectors to plot.\nSummary Plots and Functionality Multiple Summary Plots and Curves The Data Sources window enables efficient creation of multiple plots and curves by Right-clicking:\nUse Append Curves to append curves for the selected vectors into all existing plots. Use Append Plots for Wells to create separate plots for the selected vectors. If a plot contains curves pertinent to a single data source, you may easily append corresponding plots for other entries of the type by right-clicking or drag and drop. In the examples above, the curves are pertinent to the single data source well B-1H. Thus you may easily append corresponding plots for other wells by right-clicking as shown below.\nAlternatively, you may simply and efficiently drag and drop the selected wells into the plot area. In fact, you may drag the entire folder into plot area to append plots for all wells.\nSubsequently, you may:\nAdjust the number of columns and rows and preview the pages of plots using the toolbar Use keyboard PgUp/PgDown or scroll wheel to browse and validate the pages of plots Snapshot the curves or export to PDF-file via the toolbar-buttons or Edit menu The data source of displayed curves is rapidly changed by Summary Plot Source Stepping.\nVisual comparison of multiple summary curves ResInsight may ease comparison of multiple summary curves by selecting a plot in Plots and using the settings in Property Editor group Axes.\nThe different options are:\nY Axis Range: Defines the data source for Y Axis range to either individual, all subplots, all wells, all regions, or all realizations. Link Y Axes: When checked, the axes of all subplots will be treated to obtain plots with identical axes. Link Time Axis: When checked, the time axes of all subplots will identical. Auto Plot Settings: When checked, ResInsight creates axes with titles, ranges, tickmarks, and units for best possible appearance. Plot Mouse Interaction Value Tracking: When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value is displayed in a tooltip. Selection: Left mouse button click can be used to select several items of the plot and display them in the Property Editor: The closest curve Each plot axis The summary plot itself if none of the above is hit and the Plots window is activated by the mouse click Window Zoom: Available by dragging the mouse with left mouse button pressed across plot area of interest. Wheel Zoom: The mouse wheel will zoom the plot in and out towards the current mouse cursor position presupposing use of mouse wheel is not disabled by toolbar button . You may simply double click a subplot to restore its default zoom level. Use toolbar button or View menu option Zoom All to restore default zoom level for the entire plot.\nFor scrolling multiple pages of plots by using the mouse wheel, disable Wheel Zoom by the toolbar button .\nHighlighting a curve or axis A summary curve is highlighted when left-clicked in a plot. This eases detailed investigation of a specific curve in plots comprising many curves.\nAnother essential feature is to left-click an axis in a summary plot which will highlight the curves corresponding to the particular axis. As exemplified below, clicking the axis Gas Production Total highlights the WGPT curve and dims the other curves.\nSummary curves can also be activated and deactivated by clicking the check-boxes in Plots window. See also Plots right-click menu items, e.g. On - Others Off which is an effective way to deactivate all curves not selected.\nDuplicate plot, Copy and Paste An entire summary plot may be duplicated using the toolbar button Duplicate Plot.\nCopy and Paste of a summary plot, subplot (see below) or curve is also possible using the Plots right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V). This enables pasting a subplot or curve to wherever desired in the the Plots tree.\nFiltering of subplots Filtering of subplots allows the user to disable/hide subplots containing data below a user defined threshold. To activate filtering of subplots, click a plot in Plots window, set the Y-axis Threshold in Property Editor, and click Apply Filter.\nSplitting a plot into subplots A plot with many curves can easily be split into multiple subplots. Right-click a composite plot in Plots and select Split Into Single Curve Plots to split into subplots each comprising one curve.\nAccessing Plot Data Right-clicking a plot in Plots window and selecting Show Plot Data will open a window containing the plot data as text columns. The window displays plot data 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 by the right-click command Export to File.\nEditing Summary Plots A color selection dialog can be opened by clicking on the color icon in the Project Tree. The settings of each plot are listed in the Plots window for overview and are controlled by its sub-items and the Property Editor. Editing a Summary Curve By selecting a specific summary curve in the Plots window, its properties are displayed by the Property Editor.\nThe Property Editor organizes the available options into the following groups:\nSummary Vector \u0026ndash; Options to select case, vector to plot, resampling, axis specification, and error bars. Stacking - Options to control stacking of curves optionally with phase colors. 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. Other actions are available via right-click menu for selected curve. For instance, the Y-Axis for one or more curves can be switched for using the right-click command Switch Plot Axis.\nDefault Time Axis Properties Time axis properties are displayed by clicking the Time Axis subitem of a summary plot in Plots window.\nCustom Time Axis Properties The time labels are automatically defined based on the available date range. The tick marks can be controlled in details by setting Tickmark Type to Custom. Then a tickmark interval and tickmark interval step can be defined.\nIn the screenshot above, the interval is set to three years, and the plot displays labesl with three years between each.\nY-axis Properties Y-axis properties are displayed by clicking one of the left/right axis subitems of a summary plot in Plots window.\nThe property groups are:\nTitle Text: Caters for automatic or user specification of title and inclusion of vector name, acronym, and units in plot. Title Layout: Positioning of title (Center or At End) and font size. Axis Values: Logarithmic scale, inversion of axis, legend number formatting, scale factor, max/max range, and font size. Changing content of a Summary Plot Right-clicking an existing summary plot in Plots and selecting Edit Summary Plot initiates the Summary Plot Editor which offers complete functionality to navigate and select vectors from all summary types.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary Plots are a display of curves based on\n\u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e\nwhich can be combined with\n\u003ca href=\"/import/observeddata/\"\u003eimported observed data\u003c/a\u003e,\n\u003ca href=\"/3d-main-window/resultinspection/#result-plot\"\u003egrid cell time history curve\u003c/a\u003e, and\n\u003ca href=\"/import/pasteexceltimedata/\"\u003epasted ascii curves\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eSummary plots are displayed on screen by maximum four rows by four columns of plots.\nIn the example above, ResInsight displays two columns and two rows of plots, each plot comprising a single curve. However, a plot may contain an arbitrary number of curves.\nAs shown in the screenshot above, essential helpers for setup of Summary Plots are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlots\u003c/strong\u003e: overview of established plots and their components\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e: settings for titles, legends, layout, axes, and appearance\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e:\nsearching and sourcing data from case, field, regions, wells, groups, or ensemble\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003e\u003cstrong\u003eTemplates\u003c/strong\u003e\u003c/a\u003e:\noverview, management and use of templates for summary plotting\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e:\npowerful text-based selection of vectors for summary plotting\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEssential actions are presented as controls in the toolbar to increase productivity and ease of use.\u003c/p\u003e\n\u003ch2 id=\"creating-summary-plots\"\u003eCreating Summary Plots\u003c/h2\u003e\n\u003ch3 id=\"using-data-sources-to-create-summary-plots\"\u003eUsing Data Sources to create Summary Plots\u003c/h3\u003e\n\u003cp\u003eHaving imported \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e, \u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e provides an easy approach to create Summary Plots:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSearch or navigate \u003cstrong\u003eData Sources\u003c/strong\u003e to find the desired source(s) and vector(s)\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eRight-click\u003c/em\u003e selected vector(s) and select \u003cstrong\u003eNew Summary Plot\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eDrag \u0026amp; Drop\u003c/em\u003e additional vector(s) to append curves into an existing plot or vacant plot area\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eCreating a new summary plot of \u003cem\u003eWBHP\u003c/em\u003e of \u003cem\u003eWell B-1H\u003c/em\u003e and subsequent \u003cem\u003eDrag \u0026amp; Drop\u003c/em\u003e of WGOR and WGORH into the same subplot produces the following.\nResInsight will automatically make new axes if necessary. If units are the same as for WGOR and WGORH, a new axis is unnecessary.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlots_WBHP_WGOR.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"using-plot-manager-to-create-summary-plots\"\u003eUsing Plot Manager to create Summary Plots\u003c/h3\u003e\n\u003cp\u003eHaving imported \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e, the\n\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e\nprovides an alternative and powerful approach to create Summary Plots by text-based selection of data sources and vectors to plot.\u003c/p\u003e\n\u003ch2 id=\"summary-plots-and-functionality\"\u003eSummary Plots and Functionality\u003c/h2\u003e\n\u003ch3 id=\"multiple-summary-plots-and-curves\"\u003eMultiple Summary Plots and Curves\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e window enables efficient creation of multiple plots and curves by Right-clicking:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUse \u003cem\u003eAppend Curves\u003c/em\u003e to append curves for the selected vectors into all existing plots.\u003c/li\u003e\n\u003cli\u003eUse \u003cem\u003eAppend Plots for Wells\u003c/em\u003e to create separate plots for the selected vectors.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsAppendVectorsForWells.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIf a plot contains curves pertinent to a single data source, you may easily append corresponding plots for other entries of the type by right-clicking or \u003cem\u003edrag and drop\u003c/em\u003e. In the examples above, the curves are pertinent to the single data source well B-1H. Thus you may easily append corresponding plots for other wells by right-clicking as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsAppendPlotsForWells.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, you may simply and efficiently \u003cstrong\u003edrag and drop\u003c/strong\u003e the selected wells into the plot area.\nIn fact, you may drag the entire folder \u003cimg src=\"https://resinsight.org/images/plot-window/DataSourcesWell.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n into plot area to append plots for all wells.\u003c/p\u003e\n\u003cp\u003eSubsequently, you may:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAdjust the number of columns and rows and preview the pages of plots using the toolbar \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlotToolbarRowColumnPreview.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eUse keyboard PgUp/PgDown or scroll wheel to browse and validate the pages of plots\u003c/li\u003e\n\u003cli\u003eSnapshot the curves or export to PDF-file via the toolbar-buttons \u003cimg src=\"https://resinsight.org/images/plot-window/SummaryPlotToolbarSnapshot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cem\u003eEdit\u003c/em\u003e menu\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe data source of displayed curves is rapidly changed by \u003ca href=\"/plot-window/summarysourcestepping/\"\u003eSummary Plot Source Stepping\u003c/a\u003e.\u003c/p\u003e\n\u003ch3 id=\"visual-comparison-of-multiple-summary-curves\"\u003eVisual comparison of multiple summary curves\u003c/h3\u003e\n\u003cp\u003eResInsight may ease comparison of multiple summary curves by selecting a plot in \u003cstrong\u003ePlots\u003c/strong\u003e and using the settings in \u003cstrong\u003eProperty Editor\u003c/strong\u003e group \u003cstrong\u003eAxes\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotPropertyEditorAxes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe different options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eY Axis Range\u003c/em\u003e: Defines the data source for Y Axis range to either individual, all subplots, all wells, all regions, or all realizations.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eLink Y Axes\u003c/em\u003e: When checked, the axes of all subplots will be treated to obtain plots with identical axes.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eLink Time Axis\u003c/em\u003e: When checked, the time axes of all subplots will identical.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eAuto Plot Settings\u003c/em\u003e: When checked, ResInsight creates axes with titles, ranges, tickmarks, and units for best possible appearance.\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: When the mouse cursor is close to a curve, the closest curve sample is highlighted and the curve sample value is displayed in a tooltip.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSelection\u003c/strong\u003e: Left mouse button click can be used to select several items of the plot and display them in the Property Editor:\n\u003cul\u003e\n\u003cli\u003eThe closest curve\u003c/li\u003e\n\u003cli\u003eEach plot axis\u003c/li\u003e\n\u003cli\u003eThe summary plot itself if none of the above is hit and the \u003cstrong\u003ePlots\u003c/strong\u003e 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: Available by dragging the mouse with left mouse button pressed across plot area of interest.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWheel Zoom\u003c/strong\u003e: The mouse wheel will zoom the plot in and out towards the current mouse cursor position presupposing use of mouse wheel is not disabled by toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomDisableMouseWheelCapture.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eYou may simply \u003cstrong\u003edouble click\u003c/strong\u003e a subplot to restore its default zoom level.\nUse toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomAll16x16.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n or \u003cem\u003eView\u003c/em\u003e menu option \u003cstrong\u003eZoom All\u003c/strong\u003e to restore default zoom level for the entire plot.\u003c/p\u003e\n\u003cp\u003eFor scrolling multiple pages of plots by using the mouse wheel, disable \u003cem\u003eWheel Zoom\u003c/em\u003e by the toolbar button \u003cimg src=\"https://resinsight.org/images/plot-window/ZoomDisableMouseWheelCapture.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n.\u003c/p\u003e\n\u003ch3 id=\"highlighting-a-curve-or-axis\"\u003eHighlighting a curve or axis\u003c/h3\u003e\n\u003cp\u003eA summary curve is highlighted when left-clicked in a plot. This eases detailed investigation of a specific curve in plots comprising many curves.\u003c/p\u003e\n\u003cp\u003eAnother essential feature is to left-click an axis in a summary plot which will highlight the curves corresponding to the particular axis. As exemplified below, clicking the axis \u003cem\u003eGas Production Total\u003c/em\u003e highlights the \u003cem\u003eWGPT\u003c/em\u003e curve and dims the other curves.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary curves can also be activated and deactivated by clicking the check-boxes in \u003cstrong\u003ePlots\u003c/strong\u003e window. See also \u003cstrong\u003ePlots\u003c/strong\u003e right-click menu items, e.g. \u003cem\u003eOn - Others Off\u003c/em\u003e which is an effective way to deactivate all curves not selected.\u003c/p\u003e\n\u003ch3 id=\"duplicate-plot-copy-and-paste\"\u003eDuplicate plot, Copy and Paste\u003c/h3\u003e\n\u003cp\u003eAn entire summary plot may be duplicated using the toolbar button\n\u003cimg src=\"https://resinsight.org/images/plot-window/ToolbarDuplicatePlot.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \u003cstrong\u003eDuplicate Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eCopy and Paste of a summary plot, subplot (see below) or curve is also possible using the \u003cstrong\u003ePlots\u003c/strong\u003e right-click menu and standard keyboard shortcuts (CTRL-C/CTRL-V). This enables pasting a subplot or curve to wherever desired in the the \u003cstrong\u003ePlots\u003c/strong\u003e tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySubplotCopy.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"filtering-of-subplots\"\u003eFiltering of subplots\u003c/h3\u003e\n\u003cp\u003eFiltering of subplots allows the user to disable/hide subplots containing data below a user defined threshold.\nTo activate filtering of subplots, click a plot in \u003cstrong\u003ePlots\u003c/strong\u003e window, set the \u003cem\u003eY-axis Threshold\u003c/em\u003e in Property Editor, and click \u003cem\u003eApply Filter\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotVisibilityFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"splitting-a-plot-into-subplots\"\u003eSplitting a plot into subplots\u003c/h3\u003e\n\u003cp\u003eA plot with many curves can easily be split into multiple subplots.\nRight-click a composite plot in \u003cstrong\u003ePlots\u003c/strong\u003e and select \u003cstrong\u003eSplit Into Single Curve Plots\u003c/strong\u003e to split  into subplots each comprising one curve.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotSplitIntoSingleCurvePlots.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"accessing-plot-data\"\u003eAccessing Plot Data\u003c/h3\u003e\n\u003cp\u003eRight-clicking a plot in \u003cstrong\u003ePlots\u003c/strong\u003e window and selecting \u003cstrong\u003eShow Plot Data\u003c/strong\u003e will open a window containing the plot data as text columns.\nThe window displays plot data 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 by the right-click command \u003cstrong\u003eExport to File\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"editing-summary-plots\"\u003eEditing Summary Plots\u003c/h2\u003e\n\u003cp\u003eA color selection dialog can be opened by clicking on the color icon in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/ColorSelectionDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe settings of each plot are listed in the \u003cstrong\u003ePlots\u003c/strong\u003e window for overview and are controlled by its sub-items and the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/SummaryCurveSelection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"editing-a-summary-curve\"\u003eEditing a Summary Curve\u003c/h3\u003e\n\u003cp\u003eBy selecting a specific summary curve in the \u003cstrong\u003ePlots\u003c/strong\u003e window, its properties are displayed 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\u003eThe 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, resampling, axis specification, and error bars.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStacking\u003c/strong\u003e - Options to control stacking of curves optionally with phase colors.\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\u003cp\u003eOther actions are available via right-click menu for selected curve. For instance, the Y-Axis for one or more curves can be switched for using the right-click command \u003cb\u003eSwitch Plot Axis\u003c/b\u003e.\u003c/p\u003e\n\u003ch3 id=\"default-time-axis-properties\"\u003eDefault Time Axis Properties\u003c/h3\u003e\n\u003cp\u003eTime axis properties are displayed by clicking the \u003cstrong\u003eTime Axis\u003c/strong\u003e subitem of a summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryTimeAxisProperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"custom-time-axis-properties\"\u003eCustom Time Axis Properties\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary-custom-tick-marks.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe time labels are automatically defined based on the available date range. The tick marks can be controlled in details by setting \u003cstrong\u003eTickmark Type\u003c/strong\u003e to \u003cstrong\u003eCustom\u003c/strong\u003e. Then a tickmark interval and tickmark interval step can be defined.\u003c/p\u003e\n\u003cp\u003eIn the screenshot above, the interval is set to three years, and the plot displays labesl with three years between each.\u003c/p\u003e\n\u003ch3 id=\"y-axis-properties\"\u003eY-axis Properties\u003c/h3\u003e\n\u003cp\u003eY-axis properties are displayed by clicking one of the left/right axis subitems of a summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/summary_plot_yaxis_properties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe property groups are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Text\u003c/strong\u003e: Caters for automatic or user specification of title and inclusion of vector name, acronym, and units in plot.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTitle Layout\u003c/strong\u003e: Positioning of title (\u003cem\u003eCenter\u003c/em\u003e or \u003cem\u003eAt End\u003c/em\u003e) and font size.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAxis Values\u003c/strong\u003e: Logarithmic scale, inversion of axis, legend number formatting, scale factor,\nmax/max range, and font size.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"changing-content-of-a-summary-plot\"\u003eChanging content of a Summary Plot\u003c/h3\u003e\n\u003cp\u003eRight-clicking an existing summary plot in \u003cstrong\u003ePlots\u003c/strong\u003e and selecting \u003cem\u003eEdit Summary Plot\u003c/em\u003e initiates the\n\u003ca href=\"/plot-window/summaryploteditor/\"\u003e\u003cem\u003eSummary Plot Editor\u003c/em\u003e\u003c/a\u003e which offers complete functionality to navigate and select vectors from all summary types.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryplots/"
             };
         
@@ -2957,8 +2956,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\r# Connect to ResInsight instance\r resInsight = rips.Instance.find()\r# Check if connection worked\r if resInsight is not None:\r# Get a list of all cases\r cases = resInsight.project.cases()\rfor case in cases:\r# Get a list of all views\r views = case.views()\rfor view in views:\r# Set some parameters for the view\r view.setShowGridBox(not view.showGridBox())\rview.setBackgroundColor(\u0026#34;#3388AA\u0026#34;) # Update the view in ResInsight\r view.update()\rFor more information and examples, please see the ResInsight Python API.\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\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-python\" data-lang=\"python\"\u003e\u003cspan style=\"color:#f92672\"\u003eimport\u003c/span\u003e rips\r\n\u003cspan style=\"color:#75715e\"\u003e# Connect to ResInsight instance\r\u003c/span\u003e\nresInsight \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e rips\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eInstance\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003efind()\r\n\r\n\u003cspan style=\"color:#75715e\"\u003e# Check if connection worked\r\u003c/span\u003e\n\u003cspan style=\"color:#66d9ef\"\u003eif\u003c/span\u003e resInsight \u003cspan style=\"color:#f92672\"\u003eis\u003c/span\u003e \u003cspan style=\"color:#f92672\"\u003enot\u003c/span\u003e None:\r\n    \u003cspan style=\"color:#75715e\"\u003e# Get a list of all cases\r\u003c/span\u003e\n    cases \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e resInsight\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eproject\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003ecases()\r\n    \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e case \u003cspan style=\"color:#f92672\"\u003ein\u003c/span\u003e cases:\r\n        \u003cspan style=\"color:#75715e\"\u003e# Get a list of all views\r\u003c/span\u003e\n        views \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e case\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eviews()\r\n        \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e view \u003cspan style=\"color:#f92672\"\u003ein\u003c/span\u003e views:\r\n            \u003cspan style=\"color:#75715e\"\u003e# Set some parameters for the view\r\u003c/span\u003e\n            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003esetShowGridBox(\u003cspan style=\"color:#f92672\"\u003enot\u003c/span\u003e view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eshowGridBox())\r\n            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003esetBackgroundColor(\u003cspan style=\"color:#e6db74\"\u003e\u0026#34;#3388AA\u0026#34;\u003c/span\u003e)            \r\n            \u003cspan style=\"color:#75715e\"\u003e# Update the view in ResInsight\r\u003c/span\u003e\n            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eupdate()\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eFor more information and examples, please see the \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\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",
+                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(\u0026#34;#3388AA\u0026#34;) # Update the view in ResInsight view.update() For more information and examples, please see the ResInsight Python API.\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-python\" data-lang=\"python\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#f92672\"\u003eimport\u003c/span\u003e rips\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#75715e\"\u003e# Connect to ResInsight instance\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eresInsight \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e rips\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eInstance\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003efind()\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#75715e\"\u003e# Check if connection worked\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#66d9ef\"\u003eif\u003c/span\u003e resInsight \u003cspan style=\"color:#f92672\"\u003eis\u003c/span\u003e \u003cspan style=\"color:#f92672\"\u003enot\u003c/span\u003e \u003cspan style=\"color:#66d9ef\"\u003eNone\u003c/span\u003e:\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    \u003cspan style=\"color:#75715e\"\u003e# Get a list of all cases\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    cases \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e resInsight\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eproject\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003ecases()\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e \u003cspan style=\"color:#66d9ef\"\u003ecase\u003c/span\u003e \u003cspan style=\"color:#f92672\"\u003ein\u003c/span\u003e cases:\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e        \u003cspan style=\"color:#75715e\"\u003e# Get a list of all views\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e        views \u003cspan style=\"color:#f92672\"\u003e=\u003c/span\u003e \u003cspan style=\"color:#66d9ef\"\u003ecase\u003c/span\u003e\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eviews()\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e        \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e view \u003cspan style=\"color:#f92672\"\u003ein\u003c/span\u003e views:\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e            \u003cspan style=\"color:#75715e\"\u003e# Set some parameters for the view\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003esetShowGridBox(\u003cspan style=\"color:#f92672\"\u003enot\u003c/span\u003e view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eshowGridBox())\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003esetBackgroundColor(\u003cspan style=\"color:#e6db74\"\u003e\u0026#34;#3388AA\u0026#34;\u003c/span\u003e)            \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e            \u003cspan style=\"color:#75715e\"\u003e# Update the view in ResInsight\u003c/span\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e            view\u003cspan style=\"color:#f92672\"\u003e.\u003c/span\u003eupdate()\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eFor more information and examples, please see the \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\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/"
             };
         
@@ -2966,8 +2965,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:     "\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",
+                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:\nStatistics 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/"
             };
         
@@ -2975,7 +2974,7 @@ 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",
+                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 Multiple 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 ",
                 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/"
             };
@@ -2984,7 +2983,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2020_04/"] = {
                 title:    "What's New in 2020.04",
-                content:  "ResInsight 2020.04 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 2020.04 is a major update bringing a range of significant new and enhanced features.\nSurfaces ResInsight supports import of 3D Surfaces , and allows mapping properties and simulation results onto these surfaces.\nAllan Diagrams Allan Diagrams displays the overlap of formations and layers across fault faces.\nCumulative Phase Distribution Plots A Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well.\nDelta Summary Case and Ensemble Case The difference between two summary cases or two ensembles can be established using Delta Ensemble and Delta Summary Case.\nWell Disks Well Disks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\nPython Documentation The Python documentation is now available on a separate site.\nHere are the highlights of new features for Python\n Summary data Simulation well data - status and active connection for given time step Grid and cell geometry NNC data  Python Documentation \nMulti Plot A Multi Plot  allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\nWell Measurements ResInsight can import Well Measurements  and show the location of measurements by using symbols in the 3D view.\nAdditional News Well Bore Stability Plot\nMore parameters are now available for Well Bore Stability Plot, and it is now possible to create and modify these plots from Python.\nCombine Multi Case Results in one View\nIn a view displaying result values from one case, ResInsight also supports display of results from other cases. This feature is available for Faults , Intersections , and Surfaces \nReferences to External Files\nAll external file references are now located at the top of the Project File  enabling the user to efficiently change referenced data.\nRelease Notes on GitHub\nRelease info on GitHub\n",
+                content:  "ResInsight 2020.04 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 2020.04 is a major update bringing a range of significant new and enhanced features.\nSurfaces ResInsight supports import of 3D Surfaces , and allows mapping properties and simulation results onto these surfaces.\nAllan Diagrams Allan Diagrams displays the overlap of formations and layers across fault faces.\nCumulative Phase Distribution Plots A Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well.\nDelta Summary Case and Ensemble Case The difference between two summary cases or two ensembles can be established using Delta Ensemble and Delta Summary Case.\nWell Disks Well Disks may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\nPython Documentation The Python documentation is now available on a separate site.\nHere are the highlights of new features for Python\nSummary data Simulation well data - status and active connection for given time step Grid and cell geometry NNC data Python Documentation Multi Plot A Multi Plot allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\nWell Measurements ResInsight can import Well Measurements and show the location of measurements by using symbols in the 3D view.\nAdditional News Well Bore Stability Plot\nMore parameters are now available for Well Bore Stability Plot, and it is now possible to create and modify these plots from Python.\nCombine Multi Case Results in one View\nIn a view displaying result values from one case, ResInsight also supports display of results from other cases. This feature is available for Faults , Intersections , and Surfaces References to External Files\nAll external file references are now located at the top of the Project File enabling the user to efficiently change referenced data.\nRelease Notes on GitHub\nRelease info on GitHub\n",
                 html:     "\u003cp\u003eResInsight 2020.04 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 2020.04 is a major update bringing a range of significant new and enhanced features.\u003c/p\u003e\n\u003ch2 id=\"surfaces\"\u003eSurfaces\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports import of \u003ca href=\"/3d-main-window/surfaces/\"\u003e 3D Surfaces \u003c/a\u003e, and allows mapping properties and simulation results onto these surfaces.\u003c/p\u003e\n\u003ch2 id=\"allan-diagrams\"\u003eAllan Diagrams\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AllanDiagram.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/allandiagrams/\"\u003eAllan Diagrams\u003c/a\u003e displays the overlap of formations and layers across fault faces.\u003c/p\u003e\n\u003ch2 id=\"cumulative-phase-distribution-plots\"\u003eCumulative Phase Distribution Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA \u003ca href=\"/plot-window/flow-diagnostics-plots/#cumulative-phase-distribution-plot\"\u003eCumulative Phase Distribution Plot\u003c/a\u003e shows the volumetric oil, gas, and water distribution from contributing wells to a target well.\u003c/p\u003e\n\u003ch2 id=\"delta-summary-case-and-ensemble-case\"\u003eDelta Summary Case and Ensemble Case\u003c/h2\u003e\n\u003cp\u003eThe difference between two summary cases or two ensembles can be established using \u003ca href=\"/plot-window/ensembleplotting/#delta-ensemble\"\u003eDelta Ensemble\u003c/a\u003e and \u003ca href=\"/plot-window/summaryplots/#delta-summary-case\"\u003eDelta Summary Case\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"well-disks\"\u003eWell Disks\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellDisks.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/simulationwells/#disks\"\u003eWell Disks\u003c/a\u003e may be used to visualize production and injection rates and cumulative production and injection with oil, gas, and water phases shown in green, red, and blue, respectively. Optionally, the quantity of production and injection can be displayed.\u003c/p\u003e\n\u003ch2 id=\"python-documentation\"\u003ePython Documentation\u003c/h2\u003e\n\u003cp\u003eThe Python documentation is now available on a separate site.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/apiResInsightOrg.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHere are the highlights of new features for Python\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSummary data\u003c/li\u003e\n\u003cli\u003eSimulation well data - status and active connection for given time step\u003c/li\u003e\n\u003cli\u003eGrid and cell geometry\u003c/li\u003e\n\u003cli\u003eNNC data\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"https://api.resinsight.org\"\u003e Python Documentation \u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"multi-plot\"\u003eMulti Plot\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/MultiPlotHeading.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA \u003ca href=\"/plot-window/multiplots/\"\u003e Multi Plot \u003c/a\u003e allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\u003c/p\u003e\n\u003ch2 id=\"well-measurements\"\u003eWell Measurements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResInsight_WellMeasurements.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can import \u003ca href=\"/wells-and-completions/wellmeasurements/\"\u003e Well Measurements \u003c/a\u003e and show the location of measurements by using symbols in the 3D view.\u003c/p\u003e\n\u003ch2 id=\"additional-news\"\u003eAdditional News\u003c/h2\u003e\n\u003cp\u003e\u003cstrong\u003eWell Bore Stability Plot\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eMore parameters are now available for \u003ca href=\"/plot-window/wellborestabilityplots/\"\u003eWell Bore Stability Plot\u003c/a\u003e, and it is now possible to create and modify these plots from Python.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eCombine Multi Case Results in one View\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eIn a view displaying result values from one case, ResInsight also supports display of results from other cases. This feature is available for \u003ca href=\"/3d-main-window/faults/#separate-fault-result\"\u003e Faults \u003c/a\u003e, \u003ca href=\"/3d-main-window/intersections/#intersection-results\"\u003e Intersections \u003c/a\u003e, and \u003ca href=\"/3d-main-window/surfaces/#surface-results\"\u003e Surfaces \u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eReferences to External Files\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eAll external file references are now located at the top of the \u003ca href=\"/misc/projectfile/\"\u003e Project File \u003c/a\u003e enabling the user to efficiently change referenced data.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2020_04/"
             };
@@ -2993,7 +2992,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2020_04_1/"] = {
                 title:    "What's New in 2020.04.1",
-                content:  "ResInsight 2020.04.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 2020.04.1 is a patch update with several critical fixes.\nMost important fixes\n Performance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export  Release notes for 2020.04.1\nFixes since ResInsight 2020.04 https://github.com/OPM/ResInsight/milestone/274?closed=1\nRelease Notes on GitHub\nRelease info on GitHub\n",
+                content:  "ResInsight 2020.04.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 2020.04.1 is a patch update with several critical fixes.\nMost important fixes\nPerformance improvements related to import and calculations of faults and NNCs Performance related to well disks and import of summary data Adjustments for well bore stability plots Completions : Use well name defined in project for export Release notes for 2020.04.1\nFixes since ResInsight 2020.04 https://github.com/OPM/ResInsight/milestone/274?closed=1\nRelease Notes on GitHub\nRelease info on GitHub\n",
                 html:     "\u003cp\u003eResInsight 2020.04.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 2020.04.1 is a patch update with several critical fixes.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eMost important fixes\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ePerformance improvements related to import and calculations of faults and NNCs\u003c/li\u003e\n\u003cli\u003ePerformance related to well disks and import of summary data\u003c/li\u003e\n\u003cli\u003eAdjustments for well bore stability plots\u003c/li\u003e\n\u003cli\u003eCompletions : Use well name defined in project for export\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"https://resinsight.org/getting-started/whats-new/releasenotes_2020_04_1\"\u003eRelease notes for 2020.04.1\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"fixes-since-resinsight-202004\"\u003eFixes since ResInsight 2020.04\u003c/h3\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/milestone/274?closed=1\"\u003ehttps://github.com/OPM/ResInsight/milestone/274?closed=1\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2020_04_1/"
             };
@@ -3002,7 +3001,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2020_10/"] = {
                 title:    "What's New in 2020.10",
-                content:  "ResInsight 2020.10 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 2020.10 is a major update bringing a range of significant new and enhanced features.\nSurfaces ResInsight supports import of 3D Surfaces , and allows mapping properties and simulation results onto these surfaces. In addition, it is now possible to create a surface from the top of a K-layer in a grid model.\nOpenWorks XYZ file format is now supported.\nColor Management Color Legends  can be customized and managed by the user. User defined color legends can be used for any result mapping.\nAnalysis Plots Analysis Plots  are bar charts used to compare summary data at specific timesteps across Ensembles and Summary Cases.\nCorrelation Plots Correlation Plots  are plots used to visualize correlations between ensemble parameters and summary result vectors. Several visualizations can be created, including tornado plots, correlation matrices, and cross plots.\nDerived Geomechanical Results More derived geomechanical results are now available. These includes Mud Weight Window, Stress Anisotropy timelapse, Shear Slip Indicator and Pore Compressibility.\nFor more details on these parameters see Geomechanical Derived Results\nFlow Vectors The Flow Vector Result View lets the user investigate fluxes by visualizing flow vectors in the reservoir. It allows for selecting and combining different fluids and directions.\nFlow Vector Result\nApplication Themes An increasing number of engineers are now used to working with customized visual themes on their desktops. In order to allow the users to work with ResInsight in this settings, we have established support for application themes. Many icons are also updated to improve communication with the user.\nThe active application theme can be modified from Preferences-\u0026gt;GUI Theme\nPython Documentation The Python documentation is updated with new features\nHere are the highlights of new features for Python\n Surface management  Python Documentation \nRelease Notes on GitHub\nRelease info on GitHub\n",
+                content:  "ResInsight 2020.10 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 2020.10 is a major update bringing a range of significant new and enhanced features.\nSurfaces ResInsight supports import of 3D Surfaces , and allows mapping properties and simulation results onto these surfaces. In addition, it is now possible to create a surface from the top of a K-layer in a grid model.\nOpenWorks XYZ file format is now supported.\nColor Management Color Legends can be customized and managed by the user. User defined color legends can be used for any result mapping.\nAnalysis Plots Analysis Plots are bar charts used to compare summary data at specific timesteps across Ensembles and Summary Cases.\nCorrelation Plots Correlation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors. Several visualizations can be created, including tornado plots, correlation matrices, and cross plots.\nDerived Geomechanical Results More derived geomechanical results are now available. These includes Mud Weight Window, Stress Anisotropy timelapse, Shear Slip Indicator and Pore Compressibility.\nFor more details on these parameters see Geomechanical Derived Results\nFlow Vectors The Flow Vector Result View lets the user investigate fluxes by visualizing flow vectors in the reservoir. It allows for selecting and combining different fluids and directions.\nFlow Vector Result\nApplication Themes An increasing number of engineers are now used to working with customized visual themes on their desktops. In order to allow the users to work with ResInsight in this settings, we have established support for application themes. Many icons are also updated to improve communication with the user.\nThe active application theme can be modified from Preferences-\u0026gt;GUI Theme\nPython Documentation The Python documentation is updated with new features\nHere are the highlights of new features for Python\nSurface management Python Documentation Release Notes on GitHub\nRelease info on GitHub\n",
                 html:     "\u003cp\u003eResInsight 2020.10 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 2020.10 is a major update bringing a range of significant new and enhanced features.\u003c/p\u003e\n\u003ch2 id=\"surfaces\"\u003eSurfaces\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports import of \u003ca href=\"/3d-main-window/surfaces/\"\u003e 3D Surfaces \u003c/a\u003e, and allows mapping properties and simulation results onto these surfaces. In addition, it is now possible to create a surface from the top of a K-layer in a grid model.\u003c/p\u003e\n\u003cp\u003eOpenWorks XYZ file format is now supported.\u003c/p\u003e\n\u003ch2 id=\"color-management\"\u003eColor Management\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/colorlegends/\"\u003e Color Legends \u003c/a\u003e can be customized and managed by the user. User defined color legends can be used for any result mapping.\u003c/p\u003e\n\u003ch2 id=\"analysis-plots\"\u003eAnalysis Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsEnsemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/analysisplots/\"\u003e Analysis Plots \u003c/a\u003e are bar charts used to compare summary data at specific timesteps across \u003cem\u003eEnsembles\u003c/em\u003e and \u003cem\u003eSummary Cases\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"correlation-plots\"\u003eCorrelation Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsPearsonCoefficient.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/correlationplots/\"\u003e Correlation Plots \u003c/a\u003e are plots used to visualize correlations between ensemble parameters and summary result vectors.\nSeveral visualizations can be created, including tornado plots, correlation matrices, and cross plots.\u003c/p\u003e\n\u003ch2 id=\"derived-geomechanical-results\"\u003eDerived Geomechanical Results\u003c/h2\u003e\n\u003cp\u003eMore derived geomechanical results are now available. These includes Mud Weight Window, Stress Anisotropy timelapse, Shear Slip Indicator and Pore Compressibility.\u003c/p\u003e\n\u003cp\u003eFor more details on these parameters see \u003ca href=\"/calculated-data/derivedresultsgeomech/\"\u003eGeomechanical Derived Results\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"flow-vectors\"\u003eFlow Vectors\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResult.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Flow Vector Result View lets the user investigate fluxes by visualizing flow vectors in the reservoir. It allows for selecting and combining different fluids and directions.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/flowvectorresult/\"\u003eFlow Vector Result\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"application-themes\"\u003eApplication Themes\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ApplicationTheme.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn increasing number of engineers are now used to working with customized visual themes on their desktops. In order to allow the users to work with ResInsight in this settings, we have established support for application themes. Many icons are also updated to improve communication with the user.\u003c/p\u003e\n\u003cp\u003eThe active application theme can be modified from \u003cstrong\u003ePreferences-\u0026gt;GUI Theme\u003c/strong\u003e\u003c/p\u003e\n\u003ch2 id=\"python-documentation\"\u003ePython Documentation\u003c/h2\u003e\n\u003cp\u003eThe Python documentation is updated with new features\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/scripting/apiResInsightOrg.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHere are the highlights of new features for Python\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSurface management\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"https://api.resinsight.org\"\u003e Python Documentation \u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2020_10/"
             };
@@ -3011,7 +3010,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2020_10_1/"] = {
                 title:    "What's New in 2020.10.1",
-                content:  "ResInsight 2020.10.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 2020.04.1 is a patch update with several critical fixes.\nMost important fixes\n Using text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level  Python API fixes\n case.replace() created wrong model name project.open() caused currently running Python script to be disconnected set_grid_property() caused crash for ASCXII cases Avoid crash when UNSMRY file is missing  Improvements\n Data source stepping supports aquifers Import dialog : Add recently use folders Import dialog : Support replace of \u0026lsquo;realization-n\u0026rsquo; to \u0026lsquo;realization-*\u0026rsquo; Import dialog : Sort file names based on numbers instead of text Color Legend : Improved default settings for logarithmic variables  Release notes for 2020.10.1\nFixes since ResInsight 2020.10.1 https://github.com/OPM/ResInsight/milestone/310?closed=1\nRelease Notes on GitHub\nRelease info on GitHub\n",
+                content:  "ResInsight 2020.10.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 2020.04.1 is a patch update with several critical fixes.\nMost important fixes\nUsing text filter to select summary curves for ensembles now works Summary address selection for analysis and tornado plots can now select single address instead of always all wells Fixed several visualization issues related to contour plots Make sure the color legend is drawn as discrete instead of continuous Recalculate required curves when summary case is replaced Fixed crash when closing combined view Fixed crash for color legends with less than two colors 2D plots : Allow inverted y-axis when user defined min/max is active Well Targets : Fixed crash when toggling target at sea level Python API fixes\ncase.replace() created wrong model name project.open() caused currently running Python script to be disconnected set_grid_property() caused crash for ASCXII cases Avoid crash when UNSMRY file is missing Improvements\nData source stepping supports aquifers Import dialog : Add recently use folders Import dialog : Support replace of \u0026lsquo;realization-n\u0026rsquo; to \u0026lsquo;realization-*\u0026rsquo; Import dialog : Sort file names based on numbers instead of text Color Legend : Improved default settings for logarithmic variables Release notes for 2020.10.1\nFixes since ResInsight 2020.10.1 https://github.com/OPM/ResInsight/milestone/310?closed=1\nRelease Notes on GitHub\nRelease info on GitHub\n",
                 html:     "\u003cp\u003eResInsight 2020.10.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 2020.04.1 is a patch update with several critical fixes.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eMost important fixes\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eUsing text filter to select summary curves for ensembles now works\u003c/li\u003e\n\u003cli\u003eSummary address selection for analysis and tornado plots can now select single address instead of always all wells\u003c/li\u003e\n\u003cli\u003eFixed several visualization issues related to contour plots\u003c/li\u003e\n\u003cli\u003eMake sure the color legend is drawn as discrete instead of continuous\u003c/li\u003e\n\u003cli\u003eRecalculate required curves when summary case is replaced\u003c/li\u003e\n\u003cli\u003eFixed crash when closing combined view\u003c/li\u003e\n\u003cli\u003eFixed crash for color legends with less than two colors\u003c/li\u003e\n\u003cli\u003e2D plots : Allow inverted y-axis when user defined min/max is active\u003c/li\u003e\n\u003cli\u003eWell Targets : Fixed crash when toggling target at sea level\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003ePython API fixes\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecase.replace() created wrong model name\u003c/li\u003e\n\u003cli\u003eproject.open() caused currently running Python script to be disconnected\u003c/li\u003e\n\u003cli\u003eset_grid_property() caused crash for ASCXII cases\u003c/li\u003e\n\u003cli\u003eAvoid crash when UNSMRY file is missing\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eImprovements\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eData source stepping supports aquifers\u003c/li\u003e\n\u003cli\u003eImport dialog : Add recently use folders\u003c/li\u003e\n\u003cli\u003eImport dialog : Support replace of \u0026lsquo;realization-n\u0026rsquo; to \u0026lsquo;realization-*\u0026rsquo;\u003c/li\u003e\n\u003cli\u003eImport dialog : Sort file names based on numbers instead of text\u003c/li\u003e\n\u003cli\u003eColor Legend : Improved default settings for logarithmic variables\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"https://resinsight.org/getting-started/whats-new/releasenotes_2020_10_1\"\u003eRelease notes for 2020.10.1\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"fixes-since-resinsight-2020101\"\u003eFixes since ResInsight 2020.10.1\u003c/h3\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/milestone/310?closed=1\"\u003ehttps://github.com/OPM/ResInsight/milestone/310?closed=1\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003eRelease info on GitHub\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2020_10_1/"
             };
@@ -3020,8 +3019,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2021_06/"] = {
                 title:    "What's New in 2021.06",
-                content:  "Version 2021.06 is a major update bringing a range of significant new and enhanced features as described below.\nMultilateral Wells ResInsight lets the user create Multilateral Well Paths by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export\nStreamlines Streamlines lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K.\nObjective Functions Objective Functions are used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\nVertical Flow Performance Plots A Vertical Flow Performance Plot (VFP Plot) shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\nIntegrated ResInsight Help If you need the User Manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.\nResInsight Online Tutorials  ResInsight Tutorial Videos (YouTube) ResInsight Tutorials  Polygon Cell Filter Polygon Cell Filter allows the user to define a filter by marking target points of a polygon in 3D view to include or exclude matching cells. Target points are defined and manipulated in 3D view as decribed in User Defined Polyline Annotations. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\nMultiselect including Undo/Redo of Operations Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions including Undo and Redo functionality . If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing Undo.\nEnsemble RFT Plot - Color by Ensemble Parameter Ensemble RFT Plot can be colored 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.\nAdditional New Features and Enhancements  Support for relperm and PVT plots for dual porosity models Fixed issue related to negative values in delta case contour maps Color legend for water saturations (SWAT) will now have blue on top Execute last script from context menu of script folder  See Release Notes on GitHub for further details and information.\n",
-                html:     "\u003cp\u003eVersion 2021.06 is a major update bringing a range of significant new and enhanced features as described below.\u003c/p\u003e\n\u003ch2 id=\"multilateral-wells\"\u003eMultilateral Wells\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MultiLateralWell_3d_view.png\" alt=\"\"\u003e\nResInsight lets the user create \u003ca href=\"/wells-and-completions/createmultilateralwellpaths/\"\u003eMultilateral Well Paths\u003c/a\u003e by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can \nbe exported using the \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"streamlines\"\u003eStreamlines\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Streamlines.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/streamlines/\"\u003eStreamlines\u003c/a\u003e lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties \u003cstrong\u003eFLRGASI/J/K FLRWATI/J/K FLROILI/J/K\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"objective-functions\"\u003eObjective Functions\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsPlotColoring.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/objectivefunctions/\"\u003eObjective Functions\u003c/a\u003e are used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\u003c/p\u003e\n\u003ch2 id=\"vertical-flow-performance-plots\"\u003eVertical Flow Performance Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_Plot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA \u003ca href=\"/plot-window/vfpplot/\"\u003eVertical Flow Performance Plot (VFP Plot)\u003c/a\u003e shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\u003c/p\u003e\n\u003ch2 id=\"integrated-resinsight-help\"\u003eIntegrated ResInsight Help\u003c/h2\u003e\n\u003cp\u003eIf you need the \u003ca href=\"/getting-started/helpmenuanddocumentation/\"\u003eUser Manual\u003c/a\u003e for an object, you can use the right-click menu of the object and select \u003cstrong\u003eSearch Help for:\u003c/strong\u003e. This will open up the user manual for the selected object from \u003cstrong\u003eresinsight.org\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/help_on_context_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"resinsight-online-tutorials\"\u003eResInsight Online Tutorials\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/tutorials-you-tube.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://www.youtube.com/channel/UCEJoH_ti1YZXz4hPMeAKMgw\"\u003eResInsight Tutorial Videos (YouTube)\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/CeetronSolutions/resinsight-tutorials\"\u003eResInsight Tutorials\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"polygon-cell-filter\"\u003ePolygon Cell Filter\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilter_Polygon.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/filters/#cell-filters\"\u003ePolygon Cell Filter\u003c/a\u003e allows the user to define a filter by marking target points of a polygon in 3D view to include or exclude matching cells. Target points are defined and manipulated in 3D view as decribed in \u003ca href=\"/3d-main-window/annotations/\"\u003eUser Defined Polyline Annotations\u003c/a\u003e. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\u003c/p\u003e\n\u003ch2 id=\"multiselect-including-undoredo-of-operations\"\u003eMultiselect including Undo/Redo of Operations\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/projecttree/\"\u003eMultiple selection\u003c/a\u003e of items in ResInsight offers an entrance to powerful combinations and collective actions including \u003ca href=\"/getting-started/projecttree/\"\u003eUndo and Redo\u003c/a\u003e functionality \u003cimg src=\"https://resinsight.org/images/getting-started//ResInsightPlotProjectTreeToolbarUndoRedo.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n. If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing \u003cem\u003eUndo\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"ensemble-rft-plot---color-by-ensemble-parameter\"\u003eEnsemble RFT Plot - Color by Ensemble Parameter\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotColors.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/ensemblerftplot/#color-by-ensemble-parameter\"\u003eEnsemble RFT Plot\u003c/a\u003e can be colored 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.\u003c/p\u003e\n\u003ch2 id=\"additional-new-features-and-enhancements\"\u003eAdditional New Features and Enhancements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eSupport for relperm and PVT plots for dual porosity models\u003c/li\u003e\n\u003cli\u003eFixed issue related to negative values in delta case contour maps\u003c/li\u003e\n\u003cli\u003eColor legend for water saturations (SWAT) will now have blue on top\u003c/li\u003e\n\u003cli\u003eExecute last script from context menu of script folder\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
+                content:  "Version 2021.06 is a major update bringing a range of significant new and enhanced features as described below.\nMultilateral Wells ResInsight lets the user create Multilateral Well Paths by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export\nStreamlines Streamlines lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K.\nObjective Functions Objective Functions are used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\nVertical Flow Performance Plots A Vertical Flow Performance Plot (VFP Plot) shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\nIntegrated ResInsight Help If you need the User Manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.\nResInsight Online Tutorials ResInsight Tutorial Videos (YouTube) ResInsight Tutorials Polygon Cell Filter Polygon Cell Filter allows the user to define a filter by marking target points of a polygon in 3D view to include or exclude matching cells. Target points are defined and manipulated in 3D view as decribed in User Defined Polyline Annotations. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\nMultiselect including Undo/Redo of Operations Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions including Undo and Redo functionality . If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing Undo.\nEnsemble RFT Plot - Color by Ensemble Parameter Ensemble RFT Plot can be colored 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.\nAdditional New Features and Enhancements Support for relperm and PVT plots for dual porosity models Fixed issue related to negative values in delta case contour maps Color legend for water saturations (SWAT) will now have blue on top Execute last script from context menu of script folder See Release Notes on GitHub for further details and information.\n",
+                html:     "\u003cp\u003eVersion 2021.06 is a major update bringing a range of significant new and enhanced features as described below.\u003c/p\u003e\n\u003ch2 id=\"multilateral-wells\"\u003eMultilateral Wells\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MultiLateralWell_3d_view.png\" alt=\"\"\u003e\nResInsight lets the user create \u003ca href=\"/wells-and-completions/createmultilateralwellpaths/\"\u003eMultilateral Well Paths\u003c/a\u003e by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can\nbe exported using the \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"streamlines\"\u003eStreamlines\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Streamlines.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/streamlines/\"\u003eStreamlines\u003c/a\u003e lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties \u003cstrong\u003eFLRGASI/J/K FLRWATI/J/K FLROILI/J/K\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"objective-functions\"\u003eObjective Functions\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsPlotColoring.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/objectivefunctions/\"\u003eObjective Functions\u003c/a\u003e are used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\u003c/p\u003e\n\u003ch2 id=\"vertical-flow-performance-plots\"\u003eVertical Flow Performance Plots\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_Plot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA \u003ca href=\"/plot-window/vfpplot/\"\u003eVertical Flow Performance Plot (VFP Plot)\u003c/a\u003e shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\u003c/p\u003e\n\u003ch2 id=\"integrated-resinsight-help\"\u003eIntegrated ResInsight Help\u003c/h2\u003e\n\u003cp\u003eIf you need the \u003ca href=\"/getting-started/helpmenuanddocumentation/\"\u003eUser Manual\u003c/a\u003e for an object, you can use the right-click menu of the object and select \u003cstrong\u003eSearch Help for:\u003c/strong\u003e. This will open up the user manual for the selected object from \u003cstrong\u003eresinsight.org\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/help_on_context_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"resinsight-online-tutorials\"\u003eResInsight Online Tutorials\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/tutorials-you-tube.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://www.youtube.com/channel/UCEJoH_ti1YZXz4hPMeAKMgw\"\u003eResInsight Tutorial Videos (YouTube)\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/CeetronSolutions/resinsight-tutorials\"\u003eResInsight Tutorials\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"polygon-cell-filter\"\u003ePolygon Cell Filter\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilter_Polygon.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/filters/#cell-filters\"\u003ePolygon Cell Filter\u003c/a\u003e allows the user to define a filter by marking target points of a polygon in 3D view to include or exclude matching cells. Target points are defined and manipulated in 3D view as decribed in \u003ca href=\"/3d-main-window/annotations/\"\u003eUser Defined Polyline Annotations\u003c/a\u003e. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\u003c/p\u003e\n\u003ch2 id=\"multiselect-including-undoredo-of-operations\"\u003eMultiselect including Undo/Redo of Operations\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/projecttree/\"\u003eMultiple selection\u003c/a\u003e of items in ResInsight offers an entrance to powerful combinations and collective actions including \u003ca href=\"/getting-started/projecttree/\"\u003eUndo and Redo\u003c/a\u003e functionality \u003cimg src=\"https://resinsight.org/images/getting-started//ResInsightPlotProjectTreeToolbarUndoRedo.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n. If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing \u003cem\u003eUndo\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"ensemble-rft-plot---color-by-ensemble-parameter\"\u003eEnsemble RFT Plot - Color by Ensemble Parameter\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotColors.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/ensemblerftplot/#color-by-ensemble-parameter\"\u003eEnsemble RFT Plot\u003c/a\u003e can be colored 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.\u003c/p\u003e\n\u003ch2 id=\"additional-new-features-and-enhancements\"\u003eAdditional New Features and Enhancements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eSupport for relperm and PVT plots for dual porosity models\u003c/li\u003e\n\u003cli\u003eFixed issue related to negative values in delta case contour maps\u003c/li\u003e\n\u003cli\u003eColor legend for water saturations (SWAT) will now have blue on top\u003c/li\u003e\n\u003cli\u003eExecute last script from context menu of script folder\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2021_06/"
             };
         
@@ -3029,7 +3028,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2021_10/"] = {
                 title:    "What's New in 2021.10",
-                content:  "Ensemble Surface To study the structural uncertainty for an ensemble of cases, ResInsight enables the user to import an Ensemble Surface and compute the statistical surfaces based on this ensemble.\nEnsemble Well Log To study the uncertainty for well log extraction curves, ResInsight enables the user to import an Ensemble Well Log and compute the statistical distribution in this ensemble.\nPerformance Improved performance for grid model import from GRDECL. Improved performace for surface geometry import.\nMultiselect including Undo/Redo of Operations Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions including Undo and Redo functionality . If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing Undo.\nPython API Several improvements and more examples\n well path completion export generate ensemble of well logs generate ensemble of surfaces modeled well path with laterals create well path from well targets  https://api.resinsight.org/en/stable/PythonExamples.html\nAdditional New Features and Enhancements  Support for relperm and PVT plots for dual porosity models Fixed issue related to negative values in delta case contour maps Color legend for water saturations (SWAT) will now have blue on top Execute last script from context menu of script folder  See Release Notes on GitHub for further details and information.\n",
+                content:  "Ensemble Surface To study the structural uncertainty for an ensemble of cases, ResInsight enables the user to import an Ensemble Surface and compute the statistical surfaces based on this ensemble.\nEnsemble Well Log To study the uncertainty for well log extraction curves, ResInsight enables the user to import an Ensemble Well Log and compute the statistical distribution in this ensemble.\nPerformance Improved performance for grid model import from GRDECL. Improved performace for surface geometry import.\nMultiselect including Undo/Redo of Operations Multiple selection of items in ResInsight offers an entrance to powerful combinations and collective actions including Undo and Redo functionality . If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing Undo.\nPython API Several improvements and more examples\nwell path completion export generate ensemble of well logs generate ensemble of surfaces modeled well path with laterals create well path from well targets https://api.resinsight.org/en/stable/PythonExamples.html\nAdditional New Features and Enhancements Support for relperm and PVT plots for dual porosity models Fixed issue related to negative values in delta case contour maps Color legend for water saturations (SWAT) will now have blue on top Execute last script from context menu of script folder See Release Notes on GitHub for further details and information.\n",
                 html:     "\u003ch2 id=\"ensemble-surface\"\u003eEnsemble Surface\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/surface/surface-in-3d.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo study the structural uncertainty for an ensemble of cases, ResInsight enables the user to import an \u003ca href=\"/workflows/ensemblesurface/\"\u003eEnsemble Surface\u003c/a\u003e and compute the statistical surfaces based on this ensemble.\u003c/p\u003e\n\u003ch2 id=\"ensemble-well-log\"\u003eEnsemble Well Log\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/workflows/well_log_ensemble_plot_depth_eq.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo study the uncertainty for well log extraction curves, ResInsight enables the user to import an \u003ca href=\"/workflows/ensemblewelllog/\"\u003eEnsemble Well Log\u003c/a\u003e and compute the statistical distribution in this ensemble.\u003c/p\u003e\n\u003ch2 id=\"performance\"\u003ePerformance\u003c/h2\u003e\n\u003cp\u003eImproved performance for grid model import from \u003cstrong\u003eGRDECL\u003c/strong\u003e. Improved performace for surface geometry import.\u003c/p\u003e\n\u003ch2 id=\"multiselect-including-undoredo-of-operations\"\u003eMultiselect including Undo/Redo of Operations\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightPlotProjectTreeMultiSelectAction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/getting-started/projecttree/\"\u003eMultiple selection\u003c/a\u003e of items in ResInsight offers an entrance to powerful combinations and collective actions including \u003ca href=\"/getting-started/projecttree/\"\u003eUndo and Redo\u003c/a\u003e functionality \u003cimg src=\"https://resinsight.org/images/getting-started//ResInsightPlotProjectTreeToolbarUndoRedo.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n. If the user regrets an action, for instance the color setting for multiple wells as exemplified above, the collective action can be undone by pressing \u003cem\u003eUndo\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"python-api\"\u003ePython API\u003c/h2\u003e\n\u003cp\u003eSeveral improvements and more examples\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ewell path completion export\u003c/li\u003e\n\u003cli\u003egenerate ensemble of well logs\u003c/li\u003e\n\u003cli\u003egenerate ensemble of surfaces\u003c/li\u003e\n\u003cli\u003emodeled well path with laterals\u003c/li\u003e\n\u003cli\u003ecreate well path from well targets\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"https://api.resinsight.org/en/stable/PythonExamples.html\"\u003ehttps://api.resinsight.org/en/stable/PythonExamples.html\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"additional-new-features-and-enhancements\"\u003eAdditional New Features and Enhancements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eSupport for relperm and PVT plots for dual porosity models\u003c/li\u003e\n\u003cli\u003eFixed issue related to negative values in delta case contour maps\u003c/li\u003e\n\u003cli\u003eColor legend for water saturations (SWAT) will now have blue on top\u003c/li\u003e\n\u003cli\u003eExecute last script from context menu of script folder\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2021_10/"
             };
@@ -3038,8 +3037,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2022_06/"] = {
                 title:    "What's New in 2022.06",
-                content:  "Summary Plotting Summary Plotting is updated with new features and improved workflows:\n data sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file  Plot Templates Plot Templates now offer extended features and support for multiplots. For instance, Default templates is a powerful feature to automate the generation of summary plots when importing a summary case.\nImproved data source stepping The new release offers improved features for data source stepping. The new functionality includes, for instance, support for multiple plots and addition of new plots and curves while source stepping.\nMultiple Axes Summary plots can now have Multiple Axes on both left and right side. Clicking on a curve will highlight the curve and connected axis. Clicking on an axis highlights the axis and related curves.\nWhen a new curve is added to a plot, ResInsight automatically creates a new axis if needed.\nPlot Manager The new Plot Manager offers a powerful approach to create multiple summary plots based on a user specified text filter.\nGrid Property Calculator The new Grid Property Calculator can be used to create derived results based on arithmetic expressions. One of the features are easy definition of derived results by drag and drop of grid properties from data sources window.\nFilter intersection An intersection can be visually filtered by employing a user defined Depth Filter. Depth filtering is simple to perform by selecting an intersection and setting Depth Filter properties.\nRestructured windows The new release offers a restructured windows layout for improved user experience and efficiency. The following are separated into individually dockable windows:\n Data sources for summary data can be used for drag/drop operations and efficient creation of plots Scripts are now available as separate windows Templates are available in a separate window  Display of RFT segment curves RFT Segment Data can be plotted as horizontal Well Log Plots.\nSee Release Notes on GitHub for further details and information.\n",
-                html:     "\u003ch2 id=\"summary-plotting\"\u003eSummary Plotting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plotting\u003c/a\u003e is updated with new features and improved workflows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003edata sources for summary data can be used for drag/drop operations and efficient and easy production of plots\u003c/li\u003e\n\u003cli\u003eextended summary template features enable more powerful and efficient use of preset appearances and layouts\u003c/li\u003e\n\u003cli\u003eoptional curve coloring based on the summary vector phase\u003c/li\u003e\n\u003cli\u003eimproved management of multiple subplots\u003c/li\u003e\n\u003cli\u003erestructured organization of plot items in Property Editor\u003c/li\u003e\n\u003cli\u003eeasy and efficient documentation and paging of multiple summary plots to PDF file\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"plot-templates\"\u003ePlot Templates\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003ePlot Templates\u003c/a\u003e now offer extended features and support for multiplots. For instance, \u003ca href=\"/plot-window/summaryplottemplate/#default-templates\"\u003eDefault templates\u003c/a\u003e\nis a powerful feature to automate the generation of summary plots when importing a summary case.\u003c/p\u003e\n\u003ch2 id=\"improved-data-source-stepping\"\u003eImproved data source stepping\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new release offers improved features for \u003ca href=\"/plot-window/summarysourcestepping/\"\u003edata source stepping\u003c/a\u003e.\nThe new functionality includes, for instance, support for multiple plots and addition of new plots and curves while source stepping.\u003c/p\u003e\n\u003ch2 id=\"multiple-axes\"\u003eMultiple Axes\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary plots can now have \u003ca href=\"/plot-window/summaryplots/#highlighting-a-curve-or-axis\"\u003eMultiple Axes\u003c/a\u003e on both left and right side. Clicking on a curve will highlight the curve and connected axis. Clicking on an axis highlights the axis and related curves.\u003c/p\u003e\n\u003cp\u003eWhen a new curve is added to a plot, ResInsight automatically creates a new axis if needed.\u003c/p\u003e\n\u003ch2 id=\"plot-manager\"\u003ePlot Manager\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotManagerOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003ca href=\"/plot-window/summaryplotmanager/\"\u003ePlot Manager\u003c/a\u003e offers a powerful approach to create multiple summary plots based on a user specified text filter.\u003c/p\u003e\n\u003ch2 id=\"grid-property-calculator\"\u003eGrid Property Calculator\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Property Calculator\u003c/a\u003e can be used to create derived results based on arithmetic expressions. \nOne of the features are easy definition of derived results by drag and drop of grid properties from data sources window.\u003c/p\u003e\n\u003ch2 id=\"filter-intersection\"\u003eFilter intersection\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPropEdDepthFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn intersection can be visually filtered by employing a user defined \n\u003ca href=\"/3d-main-window/intersections/#depth-filter\"\u003eDepth Filter\u003c/a\u003e.\nDepth filtering is simple to perform by selecting an intersection and setting \u003cem\u003eDepth Filter\u003c/em\u003e properties.\u003c/p\u003e\n\u003ch2 id=\"restructured-windows\"\u003eRestructured windows\u003c/h2\u003e\n\u003cp\u003eThe new release offers a restructured windows layout for improved user experience and efficiency. \nThe following are separated into individually dockable windows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eData sources for summary data can be used for drag/drop operations and efficient creation of plots\u003c/li\u003e\n\u003cli\u003eScripts are now available as separate windows\u003c/li\u003e\n\u003cli\u003eTemplates are available in a separate window\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"display-of-rft-segment-curves\"\u003eDisplay of RFT segment curves\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eRFT Segment Data can be plotted as horizontal Well Log Plots.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
+                content:  "Summary Plotting Summary Plotting is updated with new features and improved workflows:\ndata sources for summary data can be used for drag/drop operations and efficient and easy production of plots extended summary template features enable more powerful and efficient use of preset appearances and layouts optional curve coloring based on the summary vector phase improved management of multiple subplots restructured organization of plot items in Property Editor easy and efficient documentation and paging of multiple summary plots to PDF file Plot Templates Plot Templates now offer extended features and support for multiplots. For instance, Default templates is a powerful feature to automate the generation of summary plots when importing a summary case.\nImproved data source stepping The new release offers improved features for data source stepping. The new functionality includes, for instance, support for multiple plots and addition of new plots and curves while source stepping.\nMultiple Axes Summary plots can now have Multiple Axes on both left and right side. Clicking on a curve will highlight the curve and connected axis. Clicking on an axis highlights the axis and related curves.\nWhen a new curve is added to a plot, ResInsight automatically creates a new axis if needed.\nPlot Manager The new Plot Manager offers a powerful approach to create multiple summary plots based on a user specified text filter.\nGrid Property Calculator The new Grid Property Calculator can be used to create derived results based on arithmetic expressions. One of the features are easy definition of derived results by drag and drop of grid properties from data sources window.\nFilter intersection An intersection can be visually filtered by employing a user defined Depth Filter. Depth filtering is simple to perform by selecting an intersection and setting Depth Filter properties.\nRestructured windows The new release offers a restructured windows layout for improved user experience and efficiency. The following are separated into individually dockable windows:\nData sources for summary data can be used for drag/drop operations and efficient creation of plots Scripts are now available as separate windows Templates are available in a separate window Display of RFT segment curves RFT Segment Data can be plotted as horizontal Well Log Plots.\nSee Release Notes on GitHub for further details and information.\n",
+                html:     "\u003ch2 id=\"summary-plotting\"\u003eSummary Plotting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plotting\u003c/a\u003e is updated with new features and improved workflows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003edata sources for summary data can be used for drag/drop operations and efficient and easy production of plots\u003c/li\u003e\n\u003cli\u003eextended summary template features enable more powerful and efficient use of preset appearances and layouts\u003c/li\u003e\n\u003cli\u003eoptional curve coloring based on the summary vector phase\u003c/li\u003e\n\u003cli\u003eimproved management of multiple subplots\u003c/li\u003e\n\u003cli\u003erestructured organization of plot items in Property Editor\u003c/li\u003e\n\u003cli\u003eeasy and efficient documentation and paging of multiple summary plots to PDF file\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"plot-templates\"\u003ePlot Templates\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003ePlot Templates\u003c/a\u003e now offer extended features and support for multiplots. For instance, \u003ca href=\"/plot-window/summaryplottemplate/#default-templates\"\u003eDefault templates\u003c/a\u003e\nis a powerful feature to automate the generation of summary plots when importing a summary case.\u003c/p\u003e\n\u003ch2 id=\"improved-data-source-stepping\"\u003eImproved data source stepping\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new release offers improved features for \u003ca href=\"/plot-window/summarysourcestepping/\"\u003edata source stepping\u003c/a\u003e.\nThe new functionality includes, for instance, support for multiple plots and addition of new plots and curves while source stepping.\u003c/p\u003e\n\u003ch2 id=\"multiple-axes\"\u003eMultiple Axes\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryCurveHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary plots can now have \u003ca href=\"/plot-window/summaryplots/#highlighting-a-curve-or-axis\"\u003eMultiple Axes\u003c/a\u003e on both left and right side. Clicking on a curve will highlight the curve and connected axis. Clicking on an axis highlights the axis and related curves.\u003c/p\u003e\n\u003cp\u003eWhen a new curve is added to a plot, ResInsight automatically creates a new axis if needed.\u003c/p\u003e\n\u003ch2 id=\"plot-manager\"\u003ePlot Manager\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotManagerOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003ca href=\"/plot-window/summaryplotmanager/\"\u003ePlot Manager\u003c/a\u003e offers a powerful approach to create multiple summary plots based on a user specified text filter.\u003c/p\u003e\n\u003ch2 id=\"grid-property-calculator\"\u003eGrid Property Calculator\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Property Calculator\u003c/a\u003e can be used to create derived results based on arithmetic expressions.\nOne of the features are easy definition of derived results by drag and drop of grid properties from data sources window.\u003c/p\u003e\n\u003ch2 id=\"filter-intersection\"\u003eFilter intersection\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPropEdDepthFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn intersection can be visually filtered by employing a user defined\n\u003ca href=\"/3d-main-window/intersections/#depth-filter\"\u003eDepth Filter\u003c/a\u003e.\nDepth filtering is simple to perform by selecting an intersection and setting \u003cem\u003eDepth Filter\u003c/em\u003e properties.\u003c/p\u003e\n\u003ch2 id=\"restructured-windows\"\u003eRestructured windows\u003c/h2\u003e\n\u003cp\u003eThe new release offers a restructured windows layout for improved user experience and efficiency.\nThe following are separated into individually dockable windows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eData sources for summary data can be used for drag/drop operations and efficient creation of plots\u003c/li\u003e\n\u003cli\u003eScripts are now available as separate windows\u003c/li\u003e\n\u003cli\u003eTemplates are available in a separate window\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"display-of-rft-segment-curves\"\u003eDisplay of RFT segment curves\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eRFT Segment Data can be plotted as horizontal Well Log Plots.\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2022_06/"
             };
         
@@ -3047,7 +3046,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2022_06_1/"] = {
                 title:    "What's New in 2022.06.1",
-                content:  "General Release 2022.06.1 is mainly a bug fix release in addition to a few new features.\nWindow Management The Window Management was updated allowing an easy to use and powerful management system. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\nIcons are added to the docking windows to make it easy to find a window.\nAdjustments to Summary Plotting Summary Plotting is updated with new features and improved workflows:\n Settings for how to use the automation for naming of plots and axis range has been updated and is now easiser to use. Several bug fixes and visual adjustments Make sure font settings are applied when required Make sure ordering of curve legend items is stable and identical to project tree ordering Clicking on a legend item will highlight the curve  See Release Notes on GitHub for further details and information.\n",
+                content:  "General Release 2022.06.1 is mainly a bug fix release in addition to a few new features.\nWindow Management The Window Management was updated allowing an easy to use and powerful management system. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\nIcons are added to the docking windows to make it easy to find a window.\nAdjustments to Summary Plotting Summary Plotting is updated with new features and improved workflows:\nSettings for how to use the automation for naming of plots and axis range has been updated and is now easiser to use. Several bug fixes and visual adjustments Make sure font settings are applied when required Make sure ordering of curve legend items is stable and identical to project tree ordering Clicking on a legend item will highlight the curve See Release Notes on GitHub for further details and information.\n",
                 html:     "\u003ch2 id=\"general\"\u003eGeneral\u003c/h2\u003e\n\u003cp\u003eRelease 2022.06.1 is mainly a bug fix release in addition to a few new features.\u003c/p\u003e\n\u003ch2 id=\"window-management\"\u003eWindow Management\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/misc/WindowManagementSystem.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003ca href=\"/misc/windowmanagement/\"\u003eWindow Management\u003c/a\u003e was updated allowing an easy to use and powerful management system. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\u003c/p\u003e\n\u003cp\u003eIcons are added to the docking windows to make it easy to find a window.\u003c/p\u003e\n\u003ch2 id=\"adjustments-to-summary-plotting\"\u003eAdjustments to Summary Plotting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plotting\u003c/a\u003e is updated with new features and improved workflows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSettings for how to use the automation for naming of plots and axis range has been updated and is now easiser to use.\u003c/li\u003e\n\u003cli\u003eSeveral bug fixes and visual adjustments\u003c/li\u003e\n\u003cli\u003eMake sure font settings are applied when required\u003c/li\u003e\n\u003cli\u003eMake sure ordering of curve legend items is stable and identical to project tree ordering\u003c/li\u003e\n\u003cli\u003eClicking on a legend item will highlight the curve\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2022_06_1/"
             };
@@ -3056,7 +3055,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2023_01/"] = {
                 title:    "What's New in 2023.01",
-                content:  "Summary Plotting Summary Plotting is updated with new features and improved workflows:\n Improved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements  Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.\nSource Stepping\nLinked Views Improvements It is now possible to get the result property values from all linked views when left-clicking on a cell in a view. Text is displayed in Result Info, and values from other properties can also be appended. Property filters can now be linked between views, and will also work between multiple cases.\nLinked Views\nCalculator Improvements The grid calculator and summary curve calculator is updated with more help and improved usability. The grid property calculations will now always calculate values for active cells and do nothing for other inactive cells.\nGrid Calculator\nSummary Calculator\nCalculator Expressions\nBreaking changes for user defined well paths The calculation of the geometry for a user defined well path had some defects. These issues are now fixed, and can affect the generated geometry of a user-defined well path. If the ResInsight project file was stored with a version before 2023.01, loading the project in version 2023.01 and later can potentially generate a slightly different well path geometry from the target at sea level to the first user-defined well target (the location of user-defined well targets are unchanged). The location of perforation intervals and completions are specified by measured depth, and could be shifted to a different location.\nThanks to https://github.com/EdmundStephens for reporting this issue.\nUser defined well paths\nDisplay of RFT segment curves RFT Segment Data can be plotted as horizontal Well Log Plots. This feature is now improved with more tracks and improved visual quality.\nRFT Segment plots\nImport of ROFF files (Preview) ROFF files with properties can be imported, both in ASCII and binary form. Grid geometry and properties per cell can be imported.\nROFF grid models\nOther improvements Wrong area for scaled fractures\nImproved Window Tiling\nSee Release Notes on GitHub for further details and information.\n",
+                content:  "Summary Plotting Summary Plotting is updated with new features and improved workflows:\nImproved logarithmic legend and default ranges Visual appearance of curves is now stable when doing Source Stepping Curve name and plot name improvements Change Data Source by Clicking in 3D The data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.\nSource Stepping\nLinked Views Improvements It is now possible to get the result property values from all linked views when left-clicking on a cell in a view. Text is displayed in Result Info, and values from other properties can also be appended. Property filters can now be linked between views, and will also work between multiple cases.\nLinked Views\nCalculator Improvements The grid calculator and summary curve calculator is updated with more help and improved usability. The grid property calculations will now always calculate values for active cells and do nothing for other inactive cells.\nGrid Calculator\nSummary Calculator\nCalculator Expressions\nBreaking changes for user defined well paths The calculation of the geometry for a user defined well path had some defects. These issues are now fixed, and can affect the generated geometry of a user-defined well path. If the ResInsight project file was stored with a version before 2023.01, loading the project in version 2023.01 and later can potentially generate a slightly different well path geometry from the target at sea level to the first user-defined well target (the location of user-defined well targets are unchanged). The location of perforation intervals and completions are specified by measured depth, and could be shifted to a different location.\nThanks to https://github.com/EdmundStephens for reporting this issue.\nUser defined well paths\nDisplay of RFT segment curves RFT Segment Data can be plotted as horizontal Well Log Plots. This feature is now improved with more tracks and improved visual quality.\nRFT Segment plots\nImport of ROFF files (Preview) ROFF files with properties can be imported, both in ASCII and binary form. Grid geometry and properties per cell can be imported.\nROFF grid models\nOther improvements Wrong area for scaled fractures\nImproved Window Tiling\nSee Release Notes on GitHub for further details and information.\n",
                 html:     "\u003ch2 id=\"summary-plotting\"\u003eSummary Plotting\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plotting\u003c/a\u003e is updated with new features and improved workflows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eImproved logarithmic legend and default ranges\u003c/li\u003e\n\u003cli\u003eVisual appearance of curves is now stable when doing \u003cstrong\u003eSource Stepping\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eCurve name and plot name improvements\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"change-data-source-by-clicking-in-3d\"\u003eChange Data Source by Clicking in 3D\u003c/h2\u003e\n\u003cp\u003eThe data source for multiple plots can be updated by clicking on a well path in 3D. This feature can be useful for large fields with many wells and you want to investigate a small subset of wells.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summarysourcestepping/#change-well-data-source-from-3d-view\"\u003eSource Stepping\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"linked-views-improvements\"\u003eLinked Views Improvements\u003c/h2\u003e\n\u003cp\u003eIt is now possible to get the result property values from all linked views when left-clicking on a cell in a view. Text is displayed in \u003ca href=\"/3d-main-window/resultinfo/\"\u003eResult Info\u003c/a\u003e, and values from other properties can also be appended. Property filters can now be linked between views, and will also work between multiple cases.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/linkedviews/\"\u003eLinked Views\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"calculator-improvements\"\u003eCalculator Improvements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe grid calculator and summary curve calculator is updated with more help and improved usability. The grid property calculations will now always calculate values for active cells and do nothing for other inactive cells.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/curvecalculator/\"\u003eSummary Calculator\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/calculatorexpressions/\"\u003eCalculator Expressions\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"breaking-changes-for-user-defined-well-paths\"\u003eBreaking changes for user defined well paths\u003c/h2\u003e\n\u003cp\u003eThe calculation of the geometry for a user defined well path had some defects. These issues are now fixed, and can affect the generated geometry of a user-defined well path. If the ResInsight project file was stored with a version before 2023.01, loading the project in version 2023.01 and later can potentially generate a slightly different well path geometry from the target at sea level to the first user-defined well target (the location of user-defined well targets are unchanged). The location of perforation intervals and completions are specified by measured depth, and could be shifted to a different location.\u003c/p\u003e\n\u003cp\u003eThanks to \u003ca href=\"https://github.com/EdmundStephens\"\u003ehttps://github.com/EdmundStephens\u003c/a\u003e for reporting this \u003ca href=\"https://github.com/OPM/ResInsight/issues/9439\"\u003eissue\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eUser defined well paths\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"display-of-rft-segment-curves\"\u003eDisplay of RFT segment curves\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eRFT Segment Data\u003c/strong\u003e can be plotted as horizontal \u003cstrong\u003eWell Log Plots\u003c/strong\u003e. This feature is now improved with more tracks and improved visual quality.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/rftsegmentplot/\"\u003eRFT Segment plots\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"import-of-roff-files-preview\"\u003eImport of ROFF files (Preview)\u003c/h2\u003e\n\u003cp\u003eROFF files with properties can be imported, both in ASCII and binary form. Grid geometry and properties per cell can be imported.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/import/roffgridmodels/\"\u003eROFF grid models\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"other-improvements\"\u003eOther improvements\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/issues/9473\"\u003eWrong area for scaled fractures\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/misc/windowmanagement/\"\u003eImproved Window Tiling\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2023_01/"
             };
@@ -3065,7 +3064,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2023_03/"] = {
                 title:    "What's New in 2023.03",
-                content:  "Calculator Improvements A calculated summary vector is now by default available for all wells, all cases and all ensembles.\n[Summary Calculator] [Calculator Expressions] [Grid Calculator]\nRadial Grids Import of radial grids including local grid refinement(LGR) are now supported. Using I and J range filters will filter the grid case based on angle and radius (Theta and R).\nMulti Segment Well Improvements Multi Segmented Wells - MSW is updated with new features and improved visualization\n Fixes wrong well geometry for some cases Added optional visualization of valves  Well Allocation Over Time Use Well Allocation Over Time to see the allocation over multiple restart time steps.\nDepth Plot The [Depth Plot] can be used to display values for all K-cells for one or multiple selected IJ cells.\nSummary Plot Improvements  Make sure on/off state for ensemble statistics is stable during source stepping Custom time axis tick marks [Custom Time Axis Properties] Show correct group name for group vectors Blank space around legend items has been reduced, makes it possible to show legends on less screen space Fixed issue for import of simulations for large time span into future (after year 2262) Default name for summary vector is now a descriptive text (Oil Production instead of FOPT) The settings for curve names can be controlled from [Curve Properties]  Improved RFT Plotting  [Pressure Depth Data] can be imported from a custom file format. More flexible RFT plotting; it is now possible to combine ensemble RFT data with single RFT curves and other observed curves.  Other improvements  Fixed parsing of GRDECL files if a comment is added on the same line after a keyword end character ‘/’ Fixed freeze during import of grid model (Progress bar freezes at 28%) New button next to file path to quickly copy text to clipboard Added more scaling factors to 3D view, and support for custom scale value in Preferences GRDECL export: Added option to export NOECHO and ECHO to generated text file CTRL-E as shortcut to open [Summary Plot Editor] Added slider to quickly switch between time step Improved user interface for range filters When clicking on a cell: Show center coordinates and corner coordinates [Result Info]  See Release Notes on GitHub for further details and information.\n",
+                content:  "Calculator Improvements A calculated summary vector is now by default available for all wells, all cases and all ensembles.\n[Summary Calculator] [Calculator Expressions] [Grid Calculator]\nRadial Grids Import of radial grids including local grid refinement(LGR) are now supported. Using I and J range filters will filter the grid case based on angle and radius (Theta and R).\nMulti Segment Well Improvements Multi Segmented Wells - MSW is updated with new features and improved visualization\nFixes wrong well geometry for some cases Added optional visualization of valves Well Allocation Over Time Use Well Allocation Over Time to see the allocation over multiple restart time steps.\nDepth Plot The [Depth Plot] can be used to display values for all K-cells for one or multiple selected IJ cells.\nSummary Plot Improvements Make sure on/off state for ensemble statistics is stable during source stepping Custom time axis tick marks [Custom Time Axis Properties] Show correct group name for group vectors Blank space around legend items has been reduced, makes it possible to show legends on less screen space Fixed issue for import of simulations for large time span into future (after year 2262) Default name for summary vector is now a descriptive text (Oil Production instead of FOPT) The settings for curve names can be controlled from [Curve Properties] Improved RFT Plotting [Pressure Depth Data] can be imported from a custom file format. More flexible RFT plotting; it is now possible to combine ensemble RFT data with single RFT curves and other observed curves. Other improvements Fixed parsing of GRDECL files if a comment is added on the same line after a keyword end character ‘/’ Fixed freeze during import of grid model (Progress bar freezes at 28%) New button next to file path to quickly copy text to clipboard Added more scaling factors to 3D view, and support for custom scale value in Preferences GRDECL export: Added option to export NOECHO and ECHO to generated text file CTRL-E as shortcut to open [Summary Plot Editor] Added slider to quickly switch between time step Improved user interface for range filters When clicking on a cell: Show center coordinates and corner coordinates [Result Info] See Release Notes on GitHub for further details and information.\n",
                 html:     "\u003ch2 id=\"calculator-improvements\"\u003eCalculator Improvements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/calculated-data/calculated-well-curve-ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA calculated summary vector is now by default available for all wells, all cases and all ensembles.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/curvecalculator/\"\u003e[Summary Calculator]\u003c/a\u003e  \u003ca href=\"/calculated-data/calculatorexpressions/\"\u003e[Calculator Expressions]\u003c/a\u003e \u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003e[Grid Calculator]\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"radial-grids\"\u003eRadial Grids\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/radial-grid.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eImport of radial grids including local grid refinement(LGR) are now supported. Using I and J range filters will filter the grid case based on angle and radius (Theta and R).\u003c/p\u003e\n\u003ch2 id=\"multi-segment-well-improvements\"\u003eMulti Segment Well Improvements\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/msw_with_valves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/simulationwells/\"\u003eMulti Segmented Wells - MSW\u003c/a\u003e is updated with new features and improved visualization\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eFixes wrong well geometry for some cases\u003c/li\u003e\n\u003cli\u003eAdded optional visualization of valves\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"well-allocation-over-time\"\u003eWell Allocation Over Time\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationOverTime.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ca href=\"/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/\"\u003eWell Allocation Over Time\u003c/a\u003e to see the allocation over multiple restart time steps.\u003c/p\u003e\n\u003ch2 id=\"depth-plot\"\u003eDepth Plot\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/DepthPlotIn3D.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003ca href=\"/3d-main-window/depthplot/\"\u003e[Depth Plot]\u003c/a\u003e can be used to display values for all K-cells for one or multiple selected IJ cells.\u003c/p\u003e\n\u003ch2 id=\"summary-plot-improvements\"\u003eSummary Plot Improvements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eMake sure on/off state for ensemble statistics is stable during source stepping\u003c/li\u003e\n\u003cli\u003eCustom time axis tick marks \u003ca href=\"/plot-window/summaryplots/#custom-time-axis-properties\"\u003e[Custom Time Axis Properties]\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eShow correct group name for group vectors\u003c/li\u003e\n\u003cli\u003eBlank space around legend items has been reduced, makes it possible to show legends on less screen space\u003c/li\u003e\n\u003cli\u003eFixed issue for import of simulations for large time span into future (after year 2262)\u003c/li\u003e\n\u003cli\u003eDefault name for summary vector is now a descriptive text (Oil Production instead of FOPT) The settings for curve names can be controlled from \u003ca href=\"/plot-window/summaryplots/#editing-a-summary-curve\"\u003e[Curve Properties]\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"improved-rft-plotting\"\u003eImproved RFT Plotting\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"/import/pressuredata/\"\u003e[Pressure Depth Data]\u003c/a\u003e can be imported from a custom file format.\u003c/li\u003e\n\u003cli\u003eMore flexible RFT plotting; it is now possible to combine ensemble RFT data with single RFT curves and other observed curves.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"other-improvements\"\u003eOther improvements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003eFixed parsing of GRDECL files if a comment is added on the same line after a keyword end character ‘/’\u003c/li\u003e\n\u003cli\u003eFixed freeze during import of grid model (Progress bar freezes at 28%)\u003c/li\u003e\n\u003cli\u003eNew button next to file path to quickly copy text to clipboard\u003c/li\u003e\n\u003cli\u003eAdded more scaling factors to 3D view, and support for custom scale value in \u003cstrong\u003ePreferences\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eGRDECL export: Added option to export NOECHO and ECHO to generated text file\u003c/li\u003e\n\u003cli\u003e\u003ccode\u003eCTRL-E\u003c/code\u003e as shortcut to open \u003ca href=\"/plot-window/summaryploteditor/\"\u003e[Summary Plot Editor]\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eAdded slider to quickly switch between time step\u003c/li\u003e\n\u003cli\u003eImproved user interface for range filters\u003c/li\u003e\n\u003cli\u003eWhen clicking on a cell: Show center coordinates and corner coordinates \u003ca href=\"/3d-main-window/resultinfo/\"\u003e[Result Info]\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2023_03/"
             };
@@ -3074,7 +3073,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/whats-new/releasenotes_2023_06/"] = {
                 title:    "What's New in 2023.06",
-                content:  "Seismic Data ResInsight supports the following seismic file formats:\n SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  Seismic Data\nSeismic Sections\nSummary Table Summary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format. It shows summary data of vectors for the selectable categories: Well, Group or Region.\nSummary tables are displayed with the summary vectors on each row, and time step values according to selected Date Resampling in each column - as shown with resampling Year in the screenshot above.\nSummary Tables\nProducer/Injector Connectivity Table Producer/Injector Connectivity Tables is a display of Flow Diagnostics Data as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\nCell Filters for Faults and Intersections Intersections and faults can now be visually filtered by using cell filters, and can be useful if faults and intersections obscure other interesting parts of the model. The filtering using cell filters is by default activated.\nIntersection Filters\nFault Filters\nRegression Analysis and Decline Curve Analysis Decline Curve Analysis\nRegression Analysis\nInteger Cell Results Integer Cell Results can now be visualized using Integer Color Legends and use custom color names that can be displayed in the 3D view.\nImproved Visualisation of Ensemble Curves The visual appearance of ensemble curves has been improved. Ensemble curves are displayed using a brighter color than the statistics curves.\nA color selection dialog can be opened by clicking on the color icon in the Project Tree. This feature is also supported for single summary curves. Other improvements  Create a new well based on an existing well path Improve renaming of summary and ensemble models Show Python version in About Dialog Full screen mode to maximize screen space for 3D view Fault distance calculations performs faster In some models, the size of well targets was to small to work with. A scaling factor for Well Targets is now available.  See Release Notes on GitHub for further details and information.\n",
+                content:  "Seismic Data ResInsight supports the following seismic file formats:\nSEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY Seismic Data\nSeismic Sections\nSummary Table Summary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format. It shows summary data of vectors for the selectable categories: Well, Group or Region.\nSummary tables are displayed with the summary vectors on each row, and time step values according to selected Date Resampling in each column - as shown with resampling Year in the screenshot above.\nSummary Tables\nProducer/Injector Connectivity Table Producer/Injector Connectivity Tables is a display of Flow Diagnostics Data as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\nCell Filters for Faults and Intersections Intersections and faults can now be visually filtered by using cell filters, and can be useful if faults and intersections obscure other interesting parts of the model. The filtering using cell filters is by default activated.\nIntersection Filters\nFault Filters\nRegression Analysis and Decline Curve Analysis Decline Curve Analysis\nRegression Analysis\nInteger Cell Results Integer Cell Results can now be visualized using Integer Color Legends and use custom color names that can be displayed in the 3D view.\nImproved Visualisation of Ensemble Curves The visual appearance of ensemble curves has been improved. Ensemble curves are displayed using a brighter color than the statistics curves.\nA color selection dialog can be opened by clicking on the color icon in the Project Tree. This feature is also supported for single summary curves. Other improvements Create a new well based on an existing well path Improve renaming of summary and ensemble models Show Python version in About Dialog Full screen mode to maximize screen space for 3D view Fault distance calculations performs faster In some models, the size of well targets was to small to work with. A scaling factor for Well Targets is now available. See Release Notes on GitHub for further details and information.\n",
                 html:     "\u003ch2 id=\"seismic-data\"\u003eSeismic Data\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicHeaderImage.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight supports the following seismic file formats:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSEGY\u003c/strong\u003e: file format developed by the \u003cstrong\u003eSociety of Exploration Geophysicists\u003c/strong\u003e for storing geophysical data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVDS\u003c/strong\u003e: file format for fast random access to multi-dimensional volumetric data as supported by \u003cstrong\u003eOSDU OpenVDS\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eZGY\u003c/strong\u003e: file format for fast random access to multi-dimensional volumetric data as supported by \u003cstrong\u003eOSDU OpenZGY\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003ca href=\"/import/seismicdata/\"\u003eSeismic Data\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/seismicsections/\"\u003eSeismic Sections\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"summary-table\"\u003eSummary Table\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_WOPR.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSummary Tables\u003c/strong\u003e are a display of curve data based on \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e as a color map in table format. It shows summary data of vectors for the selectable categories: \u003cem\u003eWell\u003c/em\u003e, \u003cem\u003eGroup\u003c/em\u003e or \u003cem\u003eRegion\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eSummary tables are displayed with the summary vectors on each row, and time step values according to selected \u003cem\u003eDate Resampling\u003c/em\u003e in each column - as shown with resampling \u003cem\u003eYear\u003c/em\u003e in the screenshot above.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summarytables/\"\u003eSummary Tables\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"producerinjector-connectivity-table\"\u003eProducer/Injector Connectivity Table\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/\"\u003eProducer/Injector Connectivity Tables\u003c/a\u003e is a display of \u003ca href=\"/plot-window/flow-diagnostics-plots/\"\u003eFlow Diagnostics Data\u003c/a\u003e as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\u003c/p\u003e\n\u003ch2 id=\"cell-filters-for-faults-and-intersections\"\u003eCell Filters for Faults and Intersections\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/release-notes/CellFilteredIntersection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIntersections and faults can now be visually filtered by using cell filters, and can be useful if faults and intersections obscure other interesting parts of the model. The filtering using cell filters is by default activated.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/intersections/#depth-and-range-filter\"\u003eIntersection Filters\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/faults/#faults-properties\"\u003eFault Filters\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"regression-analysis-and-decline-curve-analysis\"\u003eRegression Analysis and Decline Curve Analysis\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeclineCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/declinecurveanalysis/\"\u003eDecline Curve Analysis\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/regressionanalysis/\"\u003eRegression Analysis\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"integer-cell-results\"\u003eInteger Cell Results\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CustomCategoryLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eInteger Cell Results\u003c/strong\u003e can now be visualized using \u003ca href=\"/3d-main-window/colorlegends/#integer-cell-results\"\u003eInteger Color Legends\u003c/a\u003e and use custom color names that can be displayed in the 3D view.\u003c/p\u003e\n\u003ch2 id=\"improved-visualisation-of-ensemble-curves\"\u003eImproved Visualisation of Ensemble Curves\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe visual appearance of ensemble curves has been improved. Ensemble curves are displayed using a brighter color than the statistics curves.\u003c/p\u003e\n\u003cp\u003eA color selection dialog can be opened by clicking on the color icon in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. This feature is also supported for single summary curves.\n\u003cimg src=\"/images/plot-window/ColorSelectionDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"other-improvements\"\u003eOther improvements\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate a new well\u003c/a\u003e based on an existing well path\u003c/li\u003e\n\u003cli\u003eImprove renaming of summary and ensemble models\u003c/li\u003e\n\u003cli\u003eShow Python version in About Dialog\u003c/li\u003e\n\u003cli\u003eFull screen mode to maximize screen space for 3D view\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/calculated-data/faultdistance/\"\u003eFault distance\u003c/a\u003e calculations performs faster\u003c/li\u003e\n\u003cli\u003eIn some models, the size of well targets was to small to work with. A scaling factor for \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eWell Targets\u003c/a\u003e is now available.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee \u003ca href=\"https://github.com/OPM/ResInsight/releases/\"\u003e\u003cstrong\u003eRelease Notes on GitHub\u003c/strong\u003e\u003c/a\u003e for further details and information.\u003c/p\u003e\n",
                 url:      "/getting-started/whats-new/releasenotes_2023_06/"
             };
@@ -3083,8 +3082,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryplotdatasources/"] = {
                 title:    "Data Sources",
-                content:  "Data Sources provides an overview of all data sources for summary plots by category to provide search, selection, and essential functionality pertinent to summary cases.\nAs seen above, Data Sources enables search and sourcing of data from case, field, regions, wells, groups, or ensemble. See Summary Plots which illustrates use of Data Sources for effective search and selection of data for summary plots.\nSearching for data sources Atop the Data Sources window, there is a search field for effective searches across all available data sources. As exemplified below, typing just a few letters initiates a search for vectors prefixed by wbh across all data groups listing all hits.\nSummary Cases functionality Right-clicking the Summary Cases entry in Data Sources displays the functionality pertinent to summary cases.\nDelta Summary Case and Delta Ensemble A Delta Summary Case or Delta Ensemble can be created as either the sum or difference between two existing summary cases or ensembles, respectively.\nTo create a delta summary case, for instance, right click and select New Delta Summary Case. The Property Editor for the new delta case allows to modify display name, the two base summary cases, and the arithmetic operator. In addition, it is possible to specify a specific time step to be used in delta computation. As exemplified below, the delta computation between two cases for a given parameter, e.g. WBHP, will be: $$WBHP_{delta}(t) = WBHP_{case1}(@02.01.2000) - WBHP_{case2}(t)$$ An existing delta summary case may be input to a new delta summary case.\nCurve calculator The Curve Calculator is a tool to perform vector calculations on a set of curves. The created curves can be stored for later use.\nSummary Case functionality Right-clicking a specific Summary Case in Data Sources displays the functionality pertinent to a single summary case.\nThe highlighted menu item, right-clicking a summary case in Data Sources and select Replace will redisplay all configured plots with data from another case.\nPlease also note the menu options to create summary plot from Template which is a powerful and effective way to create summary plots with a specific appearance and content. When invoking a well-specific template on Summary Case level as shown above, the convention is that ResInsight selects the first well listed under as data source.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSources.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e provides an overview of all data sources for summary plots by category to provide search, selection, and essential functionality pertinent to summary cases.\u003c/p\u003e\n\u003cp\u003eAs seen above, \u003cstrong\u003eData Sources\u003c/strong\u003e enables search and sourcing of data from case, field, regions, wells, groups, or ensemble.\nSee \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plots\u003c/a\u003e which illustrates use of \u003cstrong\u003eData Sources\u003c/strong\u003e for effective search and selection of data for summary plots.\u003c/p\u003e\n\u003ch2 id=\"searching-for-data-sources\"\u003eSearching for data sources\u003c/h2\u003e\n\u003cp\u003eAtop the \u003cstrong\u003eData Sources\u003c/strong\u003e window, there is a search field for effective searches across all available data sources. As exemplified below, typing just a few letters initiates a search for vectors prefixed by \u003cem\u003ewbh\u003c/em\u003e across all data groups listing all hits.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSearching.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"summary-cases-functionality\"\u003eSummary Cases functionality\u003c/h2\u003e\n\u003cp\u003eRight-clicking the \u003cstrong\u003eSummary Cases\u003c/strong\u003e entry in \u003cstrong\u003eData Sources\u003c/strong\u003e displays the functionality pertinent to summary cases.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSummaryCase.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"delta-summary-case-and-delta-ensemble\"\u003eDelta Summary Case and Delta Ensemble\u003c/h3\u003e\n\u003cp\u003eA \u003cstrong\u003eDelta Summary Case\u003c/strong\u003e or \u003cstrong\u003eDelta Ensemble\u003c/strong\u003e can be created as either the sum or difference between two existing summary cases or ensembles, respectively.\u003c/p\u003e\n\u003cp\u003eTo create a delta summary case, for instance, right click and select \u003cstrong\u003eNew Delta Summary Case\u003c/strong\u003e. \nThe Property Editor for the new delta case allows to modify display name, the two base summary cases, and the arithmetic operator.\nIn addition, it is possible to specify a specific time step to be used in delta computation.\nAs exemplified below, the delta computation between two cases for a given parameter, e.g. \u003cem\u003eWBHP\u003c/em\u003e, will be:\n$$WBHP_{delta}(t) = WBHP_{case1}(@02.01.2000) - WBHP_{case2}(t)$$\nAn existing delta summary case may be input to a new delta summary case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeltaSummaryCasePropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"curve-calculator\"\u003eCurve calculator\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"/calculated-data/curvecalculator/\"\u003eCurve Calculator\u003c/a\u003e\nis a tool to perform vector calculations on a set of curves. The created curves can be stored for later use.\u003c/p\u003e\n\u003ch2 id=\"summary-case-functionality\"\u003eSummary Case functionality\u003c/h2\u003e\n\u003cp\u003eRight-clicking a specific \u003cem\u003eSummary Case\u003c/em\u003e in \u003cstrong\u003eData Sources\u003c/strong\u003e displays the functionality pertinent to a single summary case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSummaryCaseSingle.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe highlighted menu item, right-clicking a summary case in \u003cstrong\u003eData Sources\u003c/strong\u003e and select \u003cem\u003eReplace\u003c/em\u003e will redisplay all configured plots with data from another case.\u003c/p\u003e\n\u003cp\u003ePlease also note the menu options to create summary plot from \u003ca href=\"/plot-window/summaryplottemplate/\"\u003eTemplate\u003c/a\u003e which is a powerful and effective way to create summary plots with a specific appearance and content. When invoking a well-specific template on Summary Case level as shown above, the convention is that ResInsight selects the first well listed under \u003cimg src=\"https://resinsight.org/images/plot-window/DataSourcesWell.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n as data source.\u003c/p\u003e\n",
+                content:  "\nData Sources provides an overview of all data sources for summary plots by category to provide search, selection, and essential functionality pertinent to summary cases.\nAs seen above, Data Sources enables search and sourcing of data from case, field, regions, wells, groups, or ensemble. See Summary Plots which illustrates use of Data Sources for effective search and selection of data for summary plots.\nSearching for data sources Atop the Data Sources window, there is a search field for effective searches across all available data sources. As exemplified below, typing just a few letters initiates a search for vectors prefixed by wbh across all data groups listing all hits.\nSummary Cases functionality Right-clicking the Summary Cases entry in Data Sources displays the functionality pertinent to summary cases.\nDelta Summary Case and Delta Ensemble A Delta Summary Case or Delta Ensemble can be created as either the sum or difference between two existing summary cases or ensembles, respectively.\nTo create a delta summary case, for instance, right click and select New Delta Summary Case. The Property Editor for the new delta case allows to modify display name, the two base summary cases, and the arithmetic operator. In addition, it is possible to specify a specific time step to be used in delta computation. As exemplified below, the delta computation between two cases for a given parameter, e.g. WBHP, will be: $$WBHP_{delta}(t) = WBHP_{case1}(@02.01.2000) - WBHP_{case2}(t)$$ An existing delta summary case may be input to a new delta summary case.\nCurve calculator The Curve Calculator is a tool to perform vector calculations on a set of curves. The created curves can be stored for later use.\nSummary Case functionality Right-clicking a specific Summary Case in Data Sources displays the functionality pertinent to a single summary case.\nThe highlighted menu item, right-clicking a summary case in Data Sources and select Replace will redisplay all configured plots with data from another case.\nPlease also note the menu options to create summary plot from Template which is a powerful and effective way to create summary plots with a specific appearance and content. When invoking a well-specific template on Summary Case level as shown above, the convention is that ResInsight selects the first well listed under as data source.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSources.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e provides an overview of all data sources for summary plots by category to provide search, selection, and essential functionality pertinent to summary cases.\u003c/p\u003e\n\u003cp\u003eAs seen above, \u003cstrong\u003eData Sources\u003c/strong\u003e enables search and sourcing of data from case, field, regions, wells, groups, or ensemble.\nSee \u003ca href=\"/plot-window/summaryplots/\"\u003eSummary Plots\u003c/a\u003e which illustrates use of \u003cstrong\u003eData Sources\u003c/strong\u003e for effective search and selection of data for summary plots.\u003c/p\u003e\n\u003ch2 id=\"searching-for-data-sources\"\u003eSearching for data sources\u003c/h2\u003e\n\u003cp\u003eAtop the \u003cstrong\u003eData Sources\u003c/strong\u003e window, there is a search field for effective searches across all available data sources. As exemplified below, typing just a few letters initiates a search for vectors prefixed by \u003cem\u003ewbh\u003c/em\u003e across all data groups listing all hits.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSearching.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"summary-cases-functionality\"\u003eSummary Cases functionality\u003c/h2\u003e\n\u003cp\u003eRight-clicking the \u003cstrong\u003eSummary Cases\u003c/strong\u003e entry in \u003cstrong\u003eData Sources\u003c/strong\u003e displays the functionality pertinent to summary cases.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSummaryCase.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"delta-summary-case-and-delta-ensemble\"\u003eDelta Summary Case and Delta Ensemble\u003c/h3\u003e\n\u003cp\u003eA \u003cstrong\u003eDelta Summary Case\u003c/strong\u003e or \u003cstrong\u003eDelta Ensemble\u003c/strong\u003e can be created as either the sum or difference between two existing summary cases or ensembles, respectively.\u003c/p\u003e\n\u003cp\u003eTo create a delta summary case, for instance, right click and select \u003cstrong\u003eNew Delta Summary Case\u003c/strong\u003e.\nThe Property Editor for the new delta case allows to modify display name, the two base summary cases, and the arithmetic operator.\nIn addition, it is possible to specify a specific time step to be used in delta computation.\nAs exemplified below, the delta computation between two cases for a given parameter, e.g. \u003cem\u003eWBHP\u003c/em\u003e, will be:\n$$WBHP_{delta}(t) = WBHP_{case1}(@02.01.2000) - WBHP_{case2}(t)$$\nAn existing delta summary case may be input to a new delta summary case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeltaSummaryCasePropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"curve-calculator\"\u003eCurve calculator\u003c/h3\u003e\n\u003cp\u003eThe \u003ca href=\"/calculated-data/curvecalculator/\"\u003eCurve Calculator\u003c/a\u003e\nis a tool to perform vector calculations on a set of curves. The created curves can be stored for later use.\u003c/p\u003e\n\u003ch2 id=\"summary-case-functionality\"\u003eSummary Case functionality\u003c/h2\u003e\n\u003cp\u003eRight-clicking a specific \u003cem\u003eSummary Case\u003c/em\u003e in \u003cstrong\u003eData Sources\u003c/strong\u003e displays the functionality pertinent to a single summary case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DataSourcesSummaryCaseSingle.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe highlighted menu item, right-clicking a summary case in \u003cstrong\u003eData Sources\u003c/strong\u003e and select \u003cem\u003eReplace\u003c/em\u003e will redisplay all configured plots with data from another case.\u003c/p\u003e\n\u003cp\u003ePlease also note the menu options to create summary plot from \u003ca href=\"/plot-window/summaryplottemplate/\"\u003eTemplate\u003c/a\u003e which is a powerful and effective way to create summary plots with a specific appearance and content. When invoking a well-specific template on Summary Case level as shown above, the convention is that ResInsight selects the first well listed under \u003cimg src=\"https://resinsight.org/images/plot-window/DataSourcesWell.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n as data source.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryplotdatasources/"
             };
         
@@ -3092,7 +3091,7 @@ if (!doNotTrack) {
          
             window.store["/import/seismicdata/"] = {
                 title:    "Seismic Data",
-                content:  "Importing Seismic Data ResInsight supports the following seismic file formats:\n SEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY  A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-\u0026gt;Import-\u0026gt;Import Seismic.\nDisplay of data is described in Seismic Sections\nDifference Cube The difference between two seismic cubes can be created using the following workflow:\n Select two seismic cubes with identical geometry (same count of XLines and Inlines located at identical geometrical locations) From the right-click menu select \u0026ldquo;Create Seismic Difference\u0026rdquo; A new seismic data source is created, and data can be mapped onto seismic intersections  Property Editor The Property Editor for seismic data lists the available properties:\n General: Name and file for fast random access Color Mapping:  Colors: Color Legend applicable to all Seismic Sections using this data set Override Data Range: option to override data range by specifying clip value, c.f. below   File Information: key information such as ranges and data channels  To improve visualization of seismic data, the data range can be overridden by checking Override Data Range and specify Clip Value.\nThe Seismic Histogram may provide valuable information for deciding how to map the data values to colors.\n Clip Value: Defines the maximum and minimum value for color legend Mute Value: All values below the specified threshold is set to zero  Conversion of SEGY files for fast random access ResInsight converts SEG-Y files to VDS to obtain fast random access. Selecting a SEG-Y file (*.sgy, *.segy) thus triggers the Convert SEG-Y to VDS file format dialog shown below.\nThe options for conversion of SEG-Y files are:\n Input/Output files: specifying path and file name of input SEG-Y and output VDS file Convert Options:  Depth (Z) Unit: specifying unit of depth for display purposes (no conversion performed) Depth (Z) Offset Override: correction of incorrect or missing depth offset on file Header Definition File: optional file specifying OpenVDS SEG-Y Import Options.    Subsequent to SEG-Y conversion, please check resulting key information for correctness by inspecting File Information of the Property Editor, notably Inline, Xline, and Z ranges. In case of discrepancy, the conversion of SEG-Y file has to be performed anew by specifying Depth (Z) Offset Override or specifying a JSON file as described in the documentation of the OpenVDS SEG-Y Import Tool.\nA further option is to run the OpenVDS SEG-Y Import Tool from command line as the OpenVDS SEGYImport tool is part of your ResInsight intallation.\n",
+                content:  "\nImporting Seismic Data ResInsight supports the following seismic file formats:\nSEGY: file format developed by the Society of Exploration Geophysicists for storing geophysical data VDS: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenVDS ZGY: file format for fast random access to multi-dimensional volumetric data as supported by OSDU OpenZGY A seismic file is imported by right-clicking the Seismic item in Project Tree or by using menu item File-\u0026gt;Import-\u0026gt;Import Seismic.\nDisplay of data is described in Seismic Sections\nDifference Cube The difference between two seismic cubes can be created using the following workflow:\nSelect two seismic cubes with identical geometry (same count of XLines and Inlines located at identical geometrical locations) From the right-click menu select \u0026ldquo;Create Seismic Difference\u0026rdquo; A new seismic data source is created, and data can be mapped onto seismic intersections Property Editor The Property Editor for seismic data lists the available properties:\nGeneral: Name and file for fast random access Color Mapping: Colors: Color Legend applicable to all Seismic Sections using this data set Override Data Range: option to override data range by specifying clip value, c.f. below File Information: key information such as ranges and data channels To improve visualization of seismic data, the data range can be overridden by checking Override Data Range and specify Clip Value.\nThe Seismic Histogram may provide valuable information for deciding how to map the data values to colors.\nClip Value: Defines the maximum and minimum value for color legend Mute Value: All values below the specified threshold is set to zero Conversion of SEGY files for fast random access ResInsight converts SEG-Y files to VDS to obtain fast random access. Selecting a SEG-Y file (*.sgy, *.segy) thus triggers the Convert SEG-Y to VDS file format dialog shown below.\nThe options for conversion of SEG-Y files are:\nInput/Output files: specifying path and file name of input SEG-Y and output VDS file Convert Options: Depth (Z) Unit: specifying unit of depth for display purposes (no conversion performed) Depth (Z) Offset Override: correction of incorrect or missing depth offset on file Header Definition File: optional file specifying OpenVDS SEG-Y Import Options. Subsequent to SEG-Y conversion, please check resulting key information for correctness by inspecting File Information of the Property Editor, notably Inline, Xline, and Z ranges. In case of discrepancy, the conversion of SEG-Y file has to be performed anew by specifying Depth (Z) Offset Override or specifying a JSON file as described in the documentation of the OpenVDS SEG-Y Import Tool.\nA further option is to run the OpenVDS SEG-Y Import Tool from command line as the OpenVDS SEGYImport tool is part of your ResInsight intallation.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/import/SeismicHeaderImage.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"importing-seismic-data\"\u003eImporting Seismic Data\u003c/h2\u003e\n\u003cp\u003eResInsight supports the following seismic file formats:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSEGY\u003c/strong\u003e: file format developed by the \u003cstrong\u003eSociety of Exploration Geophysicists\u003c/strong\u003e for storing geophysical data\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVDS\u003c/strong\u003e: file format for fast random access to multi-dimensional volumetric data as supported by \u003cstrong\u003eOSDU OpenVDS\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eZGY\u003c/strong\u003e: file format for fast random access to multi-dimensional volumetric data as supported by \u003cstrong\u003eOSDU OpenZGY\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eA seismic file is imported by right-clicking the \u003cstrong\u003eSeismic\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e or by using menu item \u003cstrong\u003eFile-\u0026gt;Import-\u0026gt;Import Seismic\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicImport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eDisplay of data is described in \u003ca href=\"/3d-main-window/seismicsections/\"\u003eSeismic Sections\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"difference-cube\"\u003eDifference Cube\u003c/h2\u003e\n\u003cp\u003eThe difference between two seismic cubes can be created using the following workflow:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect two seismic cubes with identical geometry (same count of \u003cstrong\u003eXLines\u003c/strong\u003e and \u003cstrong\u003eInlines\u003c/strong\u003e located at identical geometrical locations)\u003c/li\u003e\n\u003cli\u003eFrom the right-click menu select \u0026ldquo;Create Seismic Difference\u0026rdquo;\u003c/li\u003e\n\u003cli\u003eA new seismic data source is created, and data can be mapped onto seismic intersections\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicCreateDifference.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe Property Editor for seismic data lists the available properties:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGeneral\u003c/strong\u003e: Name and file for fast random access\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColor Mapping\u003c/strong\u003e:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e: \u003ca href=\"/3d-main-window/colorlegends/\"\u003eColor Legend\u003c/a\u003e applicable to all \u003ca href=\"/3d-main-window/seismicsections/\"\u003eSeismic Sections\u003c/a\u003e using this data set\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOverride Data Range\u003c/strong\u003e: option to override data range by specifying clip value, c.f. below\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFile Information\u003c/strong\u003e: key information such as ranges and data channels\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eTo improve visualization of seismic data, the data range can be overridden by checking \u003cstrong\u003eOverride Data Range\u003c/strong\u003e and specify \u003cstrong\u003eClip Value\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicOverrideDataRange.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eSeismic Histogram\u003c/strong\u003e may provide valuable information for deciding how to map the data values to colors.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eClip Value\u003c/strong\u003e: Defines the maximum and minimum value for color legend\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMute Value\u003c/strong\u003e: All values below the specified threshold is set to zero\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicHistogram.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"conversion-of-segy-files-for-fast-random-access\"\u003eConversion of SEGY files for fast random access\u003c/h2\u003e\n\u003cp\u003eResInsight converts SEG-Y files to VDS to obtain fast random access.\nSelecting a SEG-Y file (\u003ccode\u003e*.sgy\u003c/code\u003e, \u003ccode\u003e*.segy\u003c/code\u003e) thus triggers the \u003cstrong\u003eConvert SEG-Y to VDS file format\u003c/strong\u003e dialog shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicConvertSEGYtoVDS.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe options for conversion of SEG-Y files are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInput/Output files\u003c/strong\u003e: specifying path and file name of input SEG-Y and output VDS file\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConvert Options\u003c/strong\u003e:\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eDepth (Z) Unit\u003c/em\u003e: specifying unit of depth for display purposes (no conversion performed)\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eDepth (Z) Offset Override\u003c/em\u003e: correction of incorrect or missing depth offset on file\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eHeader Definition File\u003c/em\u003e: optional file specifying \u003ca href=\"https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/SEGYImport/README.html\"\u003eOpenVDS SEG-Y Import Options\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSubsequent to SEG-Y conversion, please check resulting key information for correctness by inspecting \u003cstrong\u003eFile Information\u003c/strong\u003e of the \u003ca href=\"/import/seismicdata/#property-editor\"\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/a\u003e, notably \u003cem\u003eInline\u003c/em\u003e, \u003cem\u003eXline\u003c/em\u003e, and \u003cem\u003eZ\u003c/em\u003e ranges.\nIn case of discrepancy, the conversion of SEG-Y file has to be performed anew by specifying \u003cstrong\u003eDepth (Z) Offset Override\u003c/strong\u003e or specifying a JSON file as described in the documentation of the \u003ca href=\"https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/SEGYImport/README.html\"\u003eOpenVDS SEG-Y Import Tool\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/SeismicOpenVDSdoc_snip.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA further option is to run the \u003ca href=\"https://osdu.pages.opengroup.org/platform/domain-data-mgmt-services/seismic/open-vds/tools/SEGYImport/README.html\"\u003eOpenVDS SEG-Y Import Tool\u003c/a\u003e from command line as the OpenVDS \u003cem\u003eSEGYImport\u003c/em\u003e tool is part of your ResInsight intallation.\u003c/p\u003e\n",
                 url:      "/import/seismicdata/"
             };
@@ -3101,7 +3100,7 @@ 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    ",
+                content:  "\nLog 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:\nFirst 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.\nExpression 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.\nExpression 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/"
             };
@@ -3110,8 +3109,8 @@ if (!doNotTrack) {
          
             window.store["/misc/projectfile/"] = {
                 title:    "Project File and Caching",
-                content:  "The Project File ResInsight stores all views and settings in a Project File with the extension *.rsp to easily continue work in a subsequent session. 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 by the Project File.\nThe *.rsp file is an XML file, and can be edited by any text editor.\n\rExternal File References Editing the Project File is one effective way to replace source cases and other file references. At top of a Project File, the section ReferencedExternalFiles contains aliases to file paths which can be modified using a text editor. It is also possible to use automated tools to modify these text strings.\n\u0026lt;ReferencedExternalFiles\u0026gt;\r$PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID;\r$PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb;\r$PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC;\r$PathId_004$ D:/resinsight-data/summary_templates;\r\u0026lt;/ReferencedExternalFiles\u0026gt;\rThe Cache Directory Statistics 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.\n\r",
-                html:     "\u003ch3 id=\"the-project-file\"\u003eThe Project File\u003c/h3\u003e\n\u003cp\u003eResInsight stores all views and settings in a \u003cstrong\u003eProject File\u003c/strong\u003e with the extension \u003cem\u003e\u003ccode\u003e*.rsp\u003c/code\u003e\u003c/em\u003e to easily continue work in a subsequent session. \nThis file only contains \u003cem\u003ereferences\u003c/em\u003e to the real data files, and does not in any way copy the data itself. \nData files generated by ResInsight are also referenced by the Project File.\u003c/p\u003e\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.\u003c/p\u003e\n\u003c/div\u003e\r\n\u003ch3 id=\"external-file-references\"\u003eExternal File References\u003c/h3\u003e\n\u003cp\u003eEditing the \u003cstrong\u003eProject File\u003c/strong\u003e is one effective way to replace source cases and other file references. At top of a \u003cstrong\u003eProject File\u003c/strong\u003e, the section \u003cstrong\u003eReferencedExternalFiles\u003c/strong\u003e contains aliases to file paths which can be modified using a text editor. It is also possible to use automated tools to modify these text strings.\u003c/p\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-txt\" data-lang=\"txt\"\u003e\u0026lt;ReferencedExternalFiles\u0026gt;\r\n    $PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID;\r\n    $PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb;\r\n    $PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC;\r\n    $PathId_004$ D:/resinsight-data/summary_templates;\r\n\u0026lt;/ReferencedExternalFiles\u0026gt;\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"the-cache-directory\"\u003eThe Cache Directory\u003c/h3\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\u003c/div\u003e\r\n\n",
+                content:  "The Project File ResInsight stores all views and settings in a Project File with the extension *.rsp to easily continue work in a subsequent session. 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 by the Project File.\nThe *.rsp file is an XML file, and can be edited by any text editor.\nExternal File References Editing the Project File is one effective way to replace source cases and other file references. At top of a Project File, the section ReferencedExternalFiles contains aliases to file paths which can be modified using a text editor. It is also possible to use automated tools to modify these text strings.\n\u0026lt;ReferencedExternalFiles\u0026gt; $PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID; $PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb; $PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC; $PathId_004$ D:/resinsight-data/summary_templates; \u0026lt;/ReferencedExternalFiles\u0026gt; The Cache Directory Statistics 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.\n",
+                html:     "\u003ch3 id=\"the-project-file\"\u003eThe Project File\u003c/h3\u003e\n\u003cp\u003eResInsight stores all views and settings in a \u003cstrong\u003eProject File\u003c/strong\u003e with the extension \u003cem\u003e\u003ccode\u003e*.rsp\u003c/code\u003e\u003c/em\u003e to easily continue work in a subsequent session.\nThis file only contains \u003cem\u003ereferences\u003c/em\u003e to the real data files, and does not in any way copy the data itself.\nData files generated by ResInsight are also referenced by the Project File.\u003c/p\u003e\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.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003c/div\u003e\r\n\u003ch3 id=\"external-file-references\"\u003eExternal File References\u003c/h3\u003e\n\u003cp\u003eEditing the \u003cstrong\u003eProject File\u003c/strong\u003e is one effective way to replace source cases and other file references. At top of a \u003cstrong\u003eProject File\u003c/strong\u003e, the section \u003cstrong\u003eReferencedExternalFiles\u003c/strong\u003e contains aliases to file paths which can be modified using a text editor. It is also possible to use automated tools to modify these text strings.\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026lt;ReferencedExternalFiles\u0026gt;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    $PathId_001$ D:/resinsight-data/norne/NORNE_ATW2013.EGRID;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    $PathId_002$ D:/resinsight-data/NorneODB/norne_case2.odb;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    $PathId_003$ D:/resinsight-data/norne/NORNE_ATW2013.SMSPEC;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    $PathId_004$ D:/resinsight-data/summary_templates;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026lt;/ReferencedExternalFiles\u0026gt;\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"the-cache-directory\"\u003eThe Cache Directory\u003c/h3\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",
                 url:      "/misc/projectfile/"
             };
         
@@ -3119,8 +3118,8 @@ if (!doNotTrack) {
          
             window.store["/scripting/pythoninterface/"] = {
                 title:    "Python interface",
-                content:  "ResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance from Python 3. This enables you to:\n start ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics  Please refer to the ResInsight Python API for configuration and details.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance \nfrom \u003ca href=\"https://www.python.org/download/releases/3.0/\"\u003ePython 3\u003c/a\u003e. \nThis enables you to:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003estart ResInsight from Python\u003c/li\u003e\n\u003cli\u003ecommunicate with an a running ResInsight instance\u003c/li\u003e\n\u003cli\u003eload a ResInsight project file\u003c/li\u003e\n\u003cli\u003eload data files such as Eclipse EGRID files and summary files\u003c/li\u003e\n\u003cli\u003eextract data to Python for further processing and automation\u003c/li\u003e\n\u003cli\u003eexport snapshots of graphics\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlease refer to the \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e for configuration and details.\u003c/p\u003e\n",
+                content:  "\nResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance from Python 3. This enables you to:\nstart ResInsight from Python communicate with an a running ResInsight instance load a ResInsight project file load data files such as Eclipse EGRID files and summary files extract data to Python for further processing and automation export snapshots of graphics Please refer to the ResInsight Python API for configuration and details.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/scripting/python-logo-master-v3-TM.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers a powerful programming interface which allows you to interact with a running ResInsight instance\nfrom \u003ca href=\"https://www.python.org/download/releases/3.0/\"\u003ePython 3\u003c/a\u003e.\nThis enables you to:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003estart ResInsight from Python\u003c/li\u003e\n\u003cli\u003ecommunicate with an a running ResInsight instance\u003c/li\u003e\n\u003cli\u003eload a ResInsight project file\u003c/li\u003e\n\u003cli\u003eload data files such as Eclipse EGRID files and summary files\u003c/li\u003e\n\u003cli\u003eextract data to Python for further processing and automation\u003c/li\u003e\n\u003cli\u003eexport snapshots of graphics\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlease refer to the \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e for configuration and details.\u003c/p\u003e\n",
                 url:      "/scripting/pythoninterface/"
             };
         
@@ -3128,7 +3127,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summaryplotmanager/"] = {
                 title:    "Summary Plot Manager",
-                content:  "The Summary Plot Manager is a separate ResInsight dialog window where the user can select which vectors to plot in a summary plot. This dialog is intented to be used from the keyboard with easy access to operations for management of summary plots. This dialog can be opened by using CTRL-K from anywhere in the Plot Window.\nThe user writes a text string defining the summary vectors and optionally data sources for curves to be plotted. Example: wopt:A? iter*. This text string will filter all WOPT vectors for wells with two characters where the first character is A. Additionally, this will filter select ensemble datasources starting with the string iter\nResInsight will automatically compupte the difference between a simulated and observed vector if both are available (WOPT/WOPTH). This will be displayed as WOPT_DIFF. These difference vectors can be included in the filter if the Include Difference Vectors is checked.\nThe resulting vectors and data sources are displayed in the corresponding lists below the filter text.\nWhen the intended vectors and data sources is defined, the currently selected summary plot can be updated using buttons Append Curve or Replace Curves. Press button Create New Plot to create a new plot.\nKeyboard shortcuts    Operation Shortcut     Display Summary Manager CTRL-K   Append Curves SHIFT-Enter   Replace Curves CTRL-Enter   Create New Plot ALT-Enter    Filter text examples    Filter Text Description     wop* All vectors starting with WOP for all wells   wopt:* WOPT for all wells   wopt:a* WOPT for all wells starting with character A   *opt* All vectors having opt as a sub string (FOPT, FOPR, GOPT, GOPR, WOPT, WOPR, \u0026hellip;)   wopt:* real-1? WOPT for all wells for all realizations starting with text real-1 and one additional character   wopt:* iter-* WOPT for all wells for all ensembles starting with text iter-1 and one additional character   wopt:* iter-1:real-2* WOPT for all wells for all realizations starting with text iter-1:real-2    ",
+                content:  "\nThe Summary Plot Manager is a separate ResInsight dialog window where the user can select which vectors to plot in a summary plot. This dialog is intented to be used from the keyboard with easy access to operations for management of summary plots. This dialog can be opened by using CTRL-K from anywhere in the Plot Window.\nThe user writes a text string defining the summary vectors and optionally data sources for curves to be plotted. Example: wopt:A? iter*. This text string will filter all WOPT vectors for wells with two characters where the first character is A. Additionally, this will filter select ensemble datasources starting with the string iter\nResInsight will automatically compupte the difference between a simulated and observed vector if both are available (WOPT/WOPTH). This will be displayed as WOPT_DIFF. These difference vectors can be included in the filter if the Include Difference Vectors is checked.\nThe resulting vectors and data sources are displayed in the corresponding lists below the filter text.\nWhen the intended vectors and data sources is defined, the currently selected summary plot can be updated using buttons Append Curve or Replace Curves. Press button Create New Plot to create a new plot.\nKeyboard shortcuts Operation Shortcut Display Summary Manager CTRL-K Append Curves SHIFT-Enter Replace Curves CTRL-Enter Create New Plot ALT-Enter Filter text examples Filter Text Description wop* All vectors starting with WOP for all wells wopt:* WOPT for all wells wopt:a* WOPT for all wells starting with character A *opt* All vectors having opt as a sub string (FOPT, FOPR, GOPT, GOPR, WOPT, WOPR, \u0026hellip;) wopt:* real-1? WOPT for all wells for all realizations starting with text real-1 and one additional character wopt:* iter-* WOPT for all wells for all ensembles starting with text iter-1 and one additional character wopt:* iter-1:real-2* WOPT for all wells for all realizations starting with text iter-1:real-2 ",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotManagerOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003eSummary Plot Manager\u003c/strong\u003e is a separate \u003cstrong\u003eResInsight\u003c/strong\u003e dialog window where the user can select which vectors to plot in a summary plot. This dialog is intented to be used from the keyboard with easy access to operations for management of summary plots. This dialog can be opened by using \u003cstrong\u003eCTRL-K\u003c/strong\u003e from anywhere in the \u003cstrong\u003ePlot Window\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThe user writes a text string defining the summary vectors and optionally data sources for curves to be plotted. Example: \u003cem\u003ewopt:A? iter*\u003c/em\u003e. This text string will filter all \u003cstrong\u003eWOPT\u003c/strong\u003e vectors for wells with two characters where the first character is \u003cstrong\u003eA\u003c/strong\u003e. Additionally, this will filter select ensemble datasources starting with the string \u003cstrong\u003eiter\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eResInsight will automatically compupte the difference between a simulated and observed vector if both are available (WOPT/WOPTH). This will be displayed as WOPT_DIFF. These difference vectors can be included in the filter if the \u003cstrong\u003eInclude Difference Vectors\u003c/strong\u003e is checked.\u003c/p\u003e\n\u003cp\u003eThe resulting vectors and data sources are displayed in the corresponding lists below the filter text.\u003c/p\u003e\n\u003cp\u003eWhen the intended vectors and data sources is defined, the currently selected summary plot can be updated using buttons \u003cstrong\u003eAppend Curve\u003c/strong\u003e or \u003cstrong\u003eReplace Curves\u003c/strong\u003e. Press button \u003cstrong\u003eCreate New Plot\u003c/strong\u003e to create a new plot.\u003c/p\u003e\n\u003ch3 id=\"keyboard-shortcuts\"\u003eKeyboard shortcuts\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOperation\u003c/th\u003e\n\u003cth\u003eShortcut\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eDisplay Summary Manager\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eCTRL-K\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eAppend Curves\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eSHIFT-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eReplace Curves\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eCTRL-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCreate New Plot\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eALT-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"filter-text-examples\"\u003eFilter text examples\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eFilter Text\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\u003ewop*\u003c/td\u003e\n\u003ctd\u003eAll vectors starting with \u003cstrong\u003eWOP\u003c/strong\u003e for all wells\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewopt:*\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eWOPT\u003c/strong\u003e for all wells\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewopt:a*\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eWOPT\u003c/strong\u003e for all wells starting with character A\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e*opt*\u003c/td\u003e\n\u003ctd\u003eAll vectors having \u003cstrong\u003eopt\u003c/strong\u003e as a sub string (FOPT, FOPR, GOPT, GOPR, WOPT, WOPR, \u0026hellip;)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewopt:* real-1?\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eWOPT\u003c/strong\u003e for all wells for all realizations starting with text \u003cstrong\u003ereal-1\u003c/strong\u003e and one additional character\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewopt:* iter-*\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eWOPT\u003c/strong\u003e for all wells for all ensembles starting with text \u003cstrong\u003eiter-1\u003c/strong\u003e and one additional character\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ewopt:* iter-1:real-2*\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eWOPT\u003c/strong\u003e for all wells for all realizations starting with text \u003cstrong\u003eiter-1:real-2\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
                 url:      "/plot-window/summaryplotmanager/"
             };
@@ -3137,7 +3136,7 @@ if (!doNotTrack) {
          
             window.store["/misc/windowmanagement/"] = {
                 title:    "Window Management",
-                content:  "Window Tiling Tiling of windows can be accessed from the tool bar. The default tiling will organize the windows in a grid pattern. It is also possible perform tiling of the windows horizontally or vertically. This feature is availble from the Windows menu at the main menbu bar.\nDefault Horizontally Vertically Window Management The window management system was updated in release 2022.06.1. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\nThe window management is available from the Windows menu.\nSee the following demonstration of some of the Window Management features:\n  ",
+                content:  "Window Tiling Tiling of windows can be accessed from the tool bar. The default tiling will organize the windows in a grid pattern. It is also possible perform tiling of the windows horizontally or vertically. This feature is availble from the Windows menu at the main menbu bar.\nDefault Horizontally Vertically Window Management The window management system was updated in release 2022.06.1. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\nThe window management is available from the Windows menu.\nSee the following demonstration of some of the Window Management features:\n",
                 html:     "\u003ch3 id=\"window-tiling\"\u003eWindow Tiling\u003c/h3\u003e\n\u003cp\u003eTiling of windows can be accessed from the tool bar. The default tiling will organize the windows in a grid pattern. It is also possible perform tiling of the windows horizontally or vertically. This feature is availble from the \u003cstrong\u003eWindows\u003c/strong\u003e menu at the main menbu bar.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eDefault\u003c/strong\u003e\n\u003cimg src=\"https://resinsight.org/images/misc/WindowTilingDefault.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eHorizontally\u003c/strong\u003e\n\u003cimg src=\"https://resinsight.org/images/misc/WindowTilingHorizontally.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eVertically\u003c/strong\u003e\n\u003cimg src=\"https://resinsight.org/images/misc/WindowTilingVertically.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/p\u003e\n\u003ch3 id=\"window-management\"\u003eWindow Management\u003c/h3\u003e\n\u003cp\u003eThe window management system was updated in release 2022.06.1. ResInsight stores application window visibility and location between sessions. It is also possible to store the window configuration to a file for later reuse.\u003c/p\u003e\n\u003cp\u003eThe window management is available from the \u003cstrong\u003eWindows\u003c/strong\u003e menu.\u003c/p\u003e\n\u003cp\u003eSee the following demonstration of some of the Window Management features:\u003c/p\u003e\n\n\u003cdiv style=\"position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;\"\u003e\n  \u003ciframe src=\"https://www.youtube.com/embed/HzLaQ1p6AUc\" style=\"position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;\" allowfullscreen title=\"YouTube Video\"\u003e\u003c/iframe\u003e\n\u003c/div\u003e\n\n",
                 url:      "/misc/windowmanagement/"
             };
@@ -3146,8 +3145,8 @@ 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\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",
+                content:  "\nThis 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:\nProject 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\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/"
             };
         
@@ -3155,8 +3154,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  For some cell face results, it is possible to normalize the results by cell face area.\nThe 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=\"/calculated-data/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=\"/calculated-data/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\u003cp\u003eFor \u003ca href=\"/3d-main-window/flowvectorresult/#cell-result-view\"\u003esome cell face results\u003c/a\u003e, it is possible to normalize the results by cell face area.\u003c/p\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/flow-diagnostics-plots/\"\u003e Flow Diagnostics Plots\u003c/a\u003e and \u003ca href=\"/plot-window/flow-diagnostics-plots/#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=\"/calculated-data/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=\"/calculated-data/derivedresultsgeomech/\"\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=\"/calculated-data/derivedresultsgeomech/\"\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=\"/calculated-data/derivedresultsgeomech/\"\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",
+                content:  "\nThe 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:\nCell 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:\nDynamic \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:\nDifference Case \u0026ndash; Base case for calculation of difference Base Time Step \u0026ndash; Base time step for calculation of difference For some cell face results, it is possible to normalize the results by cell face area.\nThe difference option is not applicable for TERNARY result display.\nFlow 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\nTracers \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.\nTracers \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:\nNodal \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=\"/calculated-data/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=\"/calculated-data/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\u003cp\u003eFor \u003ca href=\"/3d-main-window/flowvectorresult/#cell-result-view\"\u003esome cell face results\u003c/a\u003e, it is possible to normalize the results by cell face area.\u003c/p\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/flow-diagnostics-plots/\"\u003e Flow Diagnostics Plots\u003c/a\u003e and \u003ca href=\"/plot-window/flow-diagnostics-plots/#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=\"/calculated-data/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=\"/calculated-data/derivedresultsgeomech/\"\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=\"/calculated-data/derivedresultsgeomech/\"\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=\"/calculated-data/derivedresultsgeomech/\"\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/"
             };
         
@@ -3164,8 +3163,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     --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;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  \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 \u0026#34;Real10\\BRUGGE_0010.EGRID\u0026#34; --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 FOPT 1_R001_REEK-0 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 -s FOPT WOPT*:op_2 1_R001_REEK-0\rAdding to previous example, the following command line also plots the 3D grid property SOIL for cell (20, 21, 1).\nResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 ",
-                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\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\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOpen the project file used to produce statistics\n\u003cbr\u003e\u003c/li\u003e\n\u003cli\u003eSelect the statistics object in the project tree\n\u003cbr\u003e\u003c/li\u003e\n\u003cli\u003eClick the button \u003cb\u003eEdit (Will DELETE current result)\u003c/b\u003e\n\u003cbr\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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 \u003cparametername\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\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-txt\" data-lang=\"txt\"\u003eResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eResInsight --project BatchTest.rsp --replaceCase \u0026#34;Real10\\BRUGGE_0010.EGRID\u0026#34; --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eReal0/BRUGGE_0000.EGRID\r\nReal10/BRUGGE_0010.EGRID\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\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-txt\" data-lang=\"txt\"\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eResInsight --summaryplot FOPT 1_R001_REEK-0 \r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eResInsight --summaryplot -s FOPT WOPT*:op_2 1_R001_REEK-0\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\u003eResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 \r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
+                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;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 Summary 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:\nWOPT:*: 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.\nOption 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 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 \u0026#34;Real10\\BRUGGE_0010.EGRID\u0026#34; --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 FOPT 1_R001_REEK-0 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 -s FOPT WOPT*:op_2 1_R001_REEK-0 Adding to previous example, the following command line also plots the 3D grid property SOIL for cell (20, 21, 1).\nResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 ",
+                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\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\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eOpen the project file used to produce statistics\n\u003cbr\u003e\u003c/li\u003e\n\u003cli\u003eSelect the statistics object in the project tree\n\u003cbr\u003e\u003c/li\u003e\n\u003cli\u003eClick the button \u003cb\u003eEdit (Will DELETE current result)\u003c/b\u003e\n\u003cbr\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eresinsight --summaryplot [\u0026lt;plotOptions\u0026gt;] \u0026lt;eclipsesummaryvectorfilters\u0026gt; \u0026lt;eclipsedatafiles\u0026gt;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ewhere:\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026lt;plotOptions\u0026gt;                 denote summary plot options, see table below\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026lt;eclipsesummaryvectorfilters\u0026gt; has the syntax \u0026lt;vectorname\u0026gt;[:\u0026lt;item\u0026gt;[:\u0026lt;subitem\u0026gt;[:i,j,k]]]\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026lt;eclipsedatafiles\u0026gt;            lists a set of Eclipse data files with or without extension\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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 \u003cparametername\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal0/BRUGGE_0000.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal10/BRUGGE_0010.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal30/BRUGGE_0030.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal40/BRUGGE_0040.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --project BatchTest.rsp --multiCaseSnapshots CaseList.txt --size 500 500\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --project BatchTest.rsp --replaceCase \u0026#34;Real10\\BRUGGE_0010.EGRID\u0026#34; --savesnapshots\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal0/BRUGGE_0000.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eReal10/BRUGGE_0010.EGRID\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eThe command line used to run this example is shown here:\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases CaseList2.txt --savesnapshots\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --project BatchStatistics.rsp --replaceSourceCases 0 CaseList2.txt --replaceSourceCases 1 CaseList3.txt --savesnapshots\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --summaryplot FOPT 1_R001_REEK-0 \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --summaryplot -s FOPT WOPT*:op_2 1_R001_REEK-0\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eResInsight --summaryplot FOPT WOPT*:op_2 SOIL:20,21,1 1_R001_REEK-0 \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/scripting/commandlineinterface/"
             };
         
@@ -3173,7 +3172,7 @@ if (!doNotTrack) {
          
             window.store["/calculated-data/curvecalculator/"] = {
                 title:    "Curve Calculator",
-                content:  "The summary curve calculator is a tool to do 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.\nMore details on mathematical operations are described in Calculator Expressions\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.\nTo assign a summary address to a variable, select a summary vector in Data Sources, and drag/drop this vector into the address field in the Curve Calculator. Further details on variable assignment is covered in section Summary Address Selection.\nBy default, a calculation defined for one well will be distributed to all other wells. This feature can be disabled by unticking Distribute to other items\nUnit 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 displayed in plots.\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, select a summary vector in Data Sources, and drag/drop this vector into the address field in the Curve Calculator.\nIt is also possible to select the address by pressing the Edit button. This action will open a Summary Address Selection dialog. Use the dialog to select a summary address and press OK.\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.\nCalculation for Ensembles All calculation expressions are available for ensemble plotting. Use the calculation objects the same way as they are used for single summary cases.\nReferences The similar concept is also used for Grid Property Calculator\n",
+                content:  "\nThe summary curve calculator is a tool to do 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.\nMore details on mathematical operations are described in Calculator Expressions\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.\nTo assign a summary address to a variable, select a summary vector in Data Sources, and drag/drop this vector into the address field in the Curve Calculator. Further details on variable assignment is covered in section Summary Address Selection.\nBy default, a calculation defined for one well will be distributed to all other wells. This feature can be disabled by unticking Distribute to other items\nUnit 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 displayed in plots.\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, select a summary vector in Data Sources, and drag/drop this vector into the address field in the Curve Calculator.\nIt is also possible to select the address by pressing the Edit button. This action will open a Summary Address Selection dialog. Use the dialog to select a summary address and press OK.\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.\nCalculation for Ensembles All calculation expressions are available for ensemble plotting. Use the calculation objects the same way as they are used for single summary cases.\nReferences The similar concept is also used for Grid Property Calculator\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/calculated-data/curve-calculator-ui.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe summary curve calculator is a tool to do 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/Calculator.svg\" 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\u003cp\u003eMore details on mathematical operations are described in \u003ca href=\"/calculated-data/calculatorexpressions/\"\u003eCalculator Expressions\u003c/a\u003e\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.\u003c/p\u003e\n\u003cp\u003eTo assign a summary address to a variable, select a summary vector in \u003cstrong\u003eData Sources\u003c/strong\u003e, and drag/drop this vector into the address field in the \u003cstrong\u003eCurve Calculator\u003c/strong\u003e. Further details on variable assignment is covered in section \u003ca href=\"#summary-address-selection\"\u003eSummary Address Selection\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eBy default, a calculation defined for one well will be distributed to all other wells. This feature can be disabled by unticking \u003cstrong\u003eDistribute to other items\u003c/strong\u003e\u003c/p\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 displayed in plots.\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, select a summary vector in \u003cstrong\u003eData Sources\u003c/strong\u003e, and drag/drop this vector into the address field in the \u003cstrong\u003eCurve Calculator\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eIt is also possible to select the address by pressing the \u003cstrong\u003eEdit\u003c/strong\u003e button. 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.\u003c/p\u003e\n\u003ch2 id=\"generating-curves\"\u003eGenerating Curves\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/calculated-data/calculated-well-curve.png\" alt=\"\"\u003e\u003c/p\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.\u003c/p\u003e\n\u003ch2 id=\"calculation-for-ensembles\"\u003eCalculation for Ensembles\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/calculated-data/calculated-well-curve-ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAll calculation expressions are available for ensemble plotting. Use the calculation objects the same way as they are used for single summary cases.\u003c/p\u003e\n\u003ch2 id=\"references\"\u003eReferences\u003c/h2\u003e\n\u003cp\u003eThe similar concept is also used for \u003ca href=\"/calculated-data/gridpropertycalculator/\"\u003eGrid Property Calculator\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/calculated-data/curvecalculator/"
             };
@@ -3182,8 +3181,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  For import this type of property data see Import: Eclipse Cases\nFile 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\u003cp\u003eFor import this type of property data see \u003ca href=\"/import/eclipsecases//#appending-additional-properties-to-a-binary-case\"\u003eImport: Eclipse Cases\u003c/a\u003e\u003c/p\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",
+                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:\nExport 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 For import this type of property data see Import: Eclipse Cases\nFile 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\u003cp\u003eFor import this type of property data see \u003ca href=\"/import/eclipsecases//#appending-additional-properties-to-a-binary-case\"\u003eImport: Eclipse Cases\u003c/a\u003e\u003c/p\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/"
             };
         
@@ -3191,7 +3190,7 @@ 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",
+                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 ResInsight 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=\"/calculated-data/derivedresultsgeomech/\"\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/"
             };
@@ -3200,7 +3199,7 @@ 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, depending 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",
+                content:  "\nResInsight 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, depending 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, depending 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/"
             };
@@ -3209,8 +3208,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summarysourcestepping/"] = {
                 title:    "Summary Plot Source Stepping",
-                content:  "Summary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes. Source stepping is available from both the Source Stepping Toolbar and the Property editor as described below.\nSource Stepping using the toolbar The toolbar for source stepping is:\nFollowing this example, the available options are:\n Explicitly setting Step By to vector WBHP by  Change existing plot to display previous or next vector by pressing one of the buttons  Step previous or next vector and add a plot by the buttons  Step previous or next vector and add a curve by the buttons   Source Stepping using the Property Editor Source Stepping is also available through the Property Editor. By selecting a subplot in Plots as in the example below, the Data Sources section of the Property editor emerges. As seen, ResInsight per default lists the most probable stepping dimensions by a consideration of the actual plot being a vector of a specific well.\nChange Well Data Source from 3D View If multiple plots are using well as data source, the plot content can be uptedate by clicking on well geometry in 3D. This can be efficient if there are many wells in a model.\n Create plots based on well summary vectors Make sure source stepping Step By is set to Well Activate the update of plots by clicking on button with tool tip text \u0026ldquo;Update wells used in plots from well selections in 3D view.\u0026quot; Open a 3D view, click on wells The well data source in changed, and plot content will be updated accordingly  Source Stepping dimensions ResInsight decides default step dimensions based on a consideration of visible curves in the current plot or subplot. For instance, well stepping is set as default if all curves display data from the same well, c.f. examples above. However, the complete set of source stepping dimensions is always available in both the toolbar and Property Editor:\n Vector Well Summary Case Ensemble Group Region Block Aquifer  When clicking a next or previous button, all curves are changed to display data for the selected source stepping dimension. For instance, when clicking with Well as source stepping dimension, all curves in the current plot are changed to display data for previous/next well.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingBanner.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes.\nSource stepping is available from both the \u003cstrong\u003eSource Stepping Toolbar\u003c/strong\u003e and the \u003cstrong\u003eProperty editor\u003c/strong\u003e as described below.\u003c/p\u003e\n\u003ch2 id=\"source-stepping-using-the-toolbar\"\u003eSource Stepping using the toolbar\u003c/h2\u003e\n\u003cp\u003eThe toolbar for source stepping is:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFollowing this example, the available options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eExplicitly setting \u003cstrong\u003eStep By\u003c/strong\u003e to vector WBHP by \n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarExplicit.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eChange existing plot to display previous or next vector by pressing one of the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eStep previous or next vector and add a \u003cem\u003eplot\u003c/em\u003e by the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarAddPlotPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eStep previous or next vector and add a \u003cem\u003ecurve\u003c/em\u003e by the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarAddCurvePrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"source-stepping-using-the-property-editor\"\u003eSource Stepping using the Property Editor\u003c/h2\u003e\n\u003cp\u003eSource Stepping is also available through the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\nBy selecting a subplot in \u003cstrong\u003ePlots\u003c/strong\u003e as in the example below, the \u003cem\u003eData Sources\u003c/em\u003e section of the \u003cstrong\u003eProperty editor\u003c/strong\u003e emerges.\nAs seen, ResInsight per default lists the most probable stepping dimensions by a consideration of the actual plot being a vector of a specific well.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"change-well-data-source-from-3d-view\"\u003eChange Well Data Source from 3D View\u003c/h2\u003e\n\u003cp\u003eIf multiple plots are using well as data source, the plot content can be uptedate by clicking on well geometry in 3D. This can be efficient if there are many wells in a model.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCreate plots based on well summary vectors\u003c/li\u003e\n\u003cli\u003eMake sure source stepping \u003cstrong\u003eStep By\u003c/strong\u003e is set to \u003cstrong\u003eWell\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eActivate the update of plots by clicking on button with tool tip text \u003cem\u003e\u0026ldquo;Update wells used in plots from well selections in 3D view.\u0026quot;\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003eOpen a 3D view, click on wells\u003c/li\u003e\n\u003cli\u003eThe well data source in changed, and plot content will be updated accordingly\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceStepping3dview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"source-stepping-dimensions\"\u003eSource Stepping dimensions\u003c/h2\u003e\n\u003cp\u003eResInsight decides default step dimensions based on a consideration of visible curves in the current plot or subplot. For instance, well stepping is set as default if all curves display data from the same well, c.f. examples above.\nHowever, the complete set of source stepping dimensions is always available in both the toolbar and \u003cstrong\u003eProperty Editor\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eVector\u003c/li\u003e\n\u003cli\u003eWell\u003c/li\u003e\n\u003cli\u003eSummary Case\u003c/li\u003e\n\u003cli\u003eEnsemble\u003c/li\u003e\n\u003cli\u003eGroup\u003c/li\u003e\n\u003cli\u003eRegion\u003c/li\u003e\n\u003cli\u003eBlock\u003c/li\u003e\n\u003cli\u003eAquifer\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen clicking a \u003cem\u003enext\u003c/em\u003e or \u003cem\u003eprevious\u003c/em\u003e button, all curves are changed to display data for the selected source stepping dimension. \nFor instance, when clicking \u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\nwith \u003cem\u003eWell\u003c/em\u003e as source stepping dimension, all curves in the current plot are changed to display data for previous/next well.\u003c/p\u003e\n",
+                content:  "\nSummary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes. Source stepping is available from both the Source Stepping Toolbar and the Property editor as described below.\nSource Stepping using the toolbar The toolbar for source stepping is:\nFollowing this example, the available options are:\nExplicitly setting Step By to vector WBHP by Change existing plot to display previous or next vector by pressing one of the buttons Step previous or next vector and add a plot by the buttons Step previous or next vector and add a curve by the buttons Source Stepping using the Property Editor Source Stepping is also available through the Property Editor. By selecting a subplot in Plots as in the example below, the Data Sources section of the Property editor emerges. As seen, ResInsight per default lists the most probable stepping dimensions by a consideration of the actual plot being a vector of a specific well.\nChange Well Data Source from 3D View If multiple plots are using well as data source, the plot content can be uptedate by clicking on well geometry in 3D. This can be efficient if there are many wells in a model.\nCreate plots based on well summary vectors Make sure source stepping Step By is set to Well Activate the update of plots by clicking on button with tool tip text \u0026ldquo;Update wells used in plots from well selections in 3D view.\u0026rdquo; Open a 3D view, click on wells The well data source in changed, and plot content will be updated accordingly Source Stepping dimensions ResInsight decides default step dimensions based on a consideration of visible curves in the current plot or subplot. For instance, well stepping is set as default if all curves display data from the same well, c.f. examples above. However, the complete set of source stepping dimensions is always available in both the toolbar and Property Editor:\nVector Well Summary Case Ensemble Group Region Block Aquifer When clicking a next or previous button, all curves are changed to display data for the selected source stepping dimension. For instance, when clicking with Well as source stepping dimension, all curves in the current plot are changed to display data for previous/next well.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingBanner.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSummary Plot Source Stepping enables the user to efficiently step through multiple vectors, wells, summary cases, ensembles, groups, regions, blocks, and aquifers for plotting purposes.\nSource stepping is available from both the \u003cstrong\u003eSource Stepping Toolbar\u003c/strong\u003e and the \u003cstrong\u003eProperty editor\u003c/strong\u003e as described below.\u003c/p\u003e\n\u003ch2 id=\"source-stepping-using-the-toolbar\"\u003eSource Stepping using the toolbar\u003c/h2\u003e\n\u003cp\u003eThe toolbar for source stepping is:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFollowing this example, the available options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eExplicitly setting \u003cstrong\u003eStep By\u003c/strong\u003e to vector WBHP by\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarExplicit.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eChange existing plot to display previous or next vector by pressing one of the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eStep previous or next vector and add a \u003cem\u003eplot\u003c/em\u003e by the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarAddPlotPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003cli\u003eStep previous or next vector and add a \u003cem\u003ecurve\u003c/em\u003e by the buttons\n\u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarAddCurvePrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"source-stepping-using-the-property-editor\"\u003eSource Stepping using the Property Editor\u003c/h2\u003e\n\u003cp\u003eSource Stepping is also available through the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\nBy selecting a subplot in \u003cstrong\u003ePlots\u003c/strong\u003e as in the example below, the \u003cem\u003eData Sources\u003c/em\u003e section of the \u003cstrong\u003eProperty editor\u003c/strong\u003e emerges.\nAs seen, ResInsight per default lists the most probable stepping dimensions by a consideration of the actual plot being a vector of a specific well.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceSteppingPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"change-well-data-source-from-3d-view\"\u003eChange Well Data Source from 3D View\u003c/h2\u003e\n\u003cp\u003eIf multiple plots are using well as data source, the plot content can be uptedate by clicking on well geometry in 3D. This can be efficient if there are many wells in a model.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eCreate plots based on well summary vectors\u003c/li\u003e\n\u003cli\u003eMake sure source stepping \u003cstrong\u003eStep By\u003c/strong\u003e is set to \u003cstrong\u003eWell\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eActivate the update of plots by clicking on button with tool tip text \u003cem\u003e\u0026ldquo;Update wells used in plots from well selections in 3D view.\u0026rdquo;\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003eOpen a 3D view, click on wells\u003c/li\u003e\n\u003cli\u003eThe well data source in changed, and plot content will be updated accordingly\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummarySourceStepping3dview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"source-stepping-dimensions\"\u003eSource Stepping dimensions\u003c/h2\u003e\n\u003cp\u003eResInsight decides default step dimensions based on a consideration of visible curves in the current plot or subplot. For instance, well stepping is set as default if all curves display data from the same well, c.f. examples above.\nHowever, the complete set of source stepping dimensions is always available in both the toolbar and \u003cstrong\u003eProperty Editor\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eVector\u003c/li\u003e\n\u003cli\u003eWell\u003c/li\u003e\n\u003cli\u003eSummary Case\u003c/li\u003e\n\u003cli\u003eEnsemble\u003c/li\u003e\n\u003cli\u003eGroup\u003c/li\u003e\n\u003cli\u003eRegion\u003c/li\u003e\n\u003cli\u003eBlock\u003c/li\u003e\n\u003cli\u003eAquifer\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen clicking a \u003cem\u003enext\u003c/em\u003e or \u003cem\u003eprevious\u003c/em\u003e button, all curves are changed to display data for the selected source stepping dimension.\nFor instance, when clicking \u003cimg src=\"https://resinsight.org/images/plot-window/SummarySourceSteppingToolbarPrevNext.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\nwith \u003cem\u003eWell\u003c/em\u003e as source stepping dimension, all curves in the current plot are changed to display data for previous/next well.\u003c/p\u003e\n",
                 url:      "/plot-window/summarysourcestepping/"
             };
         
@@ -3218,8 +3217,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;\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\rExample 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\rWell 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\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-txt\" data-lang=\"txt\"\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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\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",
+                content:  "\nResInsight 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:\nEach 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\t725\t2542\t2590 6523.5\t757\t2549\t2626.6 6523.5\t760\t2559\t2637.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\t725\t2542\t2542 6523.5\t757\t2549\t2578.6 6523.5\t760\t2559\t2589.1 -- A Comment new well This is not its name Name Well_2 550.7\t1020.2\t2410\t2520 551\t1004.1\t2422.2\t2540.2 # a comment inside the data 555.2\t993.9\t2425\t2551.6 3Q AHB-J 5507.0\t4638.5\t0.0\t0.0 5507\t4638.5\t1628.6\t1628.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.\nImporting 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;.\nWell 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\nGlobal 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.\nAppearance 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;\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\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELLNAME: WELL1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6507.1\t725\t2542\t2590\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6523.5\t757\t2549\t2626.6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6523.5\t760\t2559\t2637.1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-999\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELLNAME: WELL2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e550.7 1020.2  2410   2410\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e551   1004.1  2422.2 2430.2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e555.2  993.9  2425   2441.6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-999\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-2\"\u003eExample 2:\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eX Y TVD(MSL) MD(RKB)\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eName Well_1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6507.1\t725\t2542\t2542\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6523.5\t757\t2549\t2578.6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6523.5\t760\t2559\t2589.1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- A Comment new well\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eThis is not its name\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eName Well_2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e550.7\t1020.2\t2410\t2520\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e551\t1004.1\t2422.2\t2540.2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# a comment inside the data \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e555.2\t993.9\t2425\t2551.6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e3Q AHB-J\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5507.0\t4638.5\t0.0\t0.0\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5507\t4638.5\t1628.6\t1628.6\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\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\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/"
             };
         
@@ -3227,7 +3226,7 @@ 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",
+                content:  "\nResInsight 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/"
             };
@@ -3236,8 +3235,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\rFAQ Smartscreen warnings When launching ResInsight at the first time, a Smartscreen warning might be displayed. This is a security feature by Microsoft, and will warn the user when an unknown program is launched. This warning is displayed once for each installation.\nPress the More info link in the upper left section.\nNotice the information and digital signature by Ceetron Solutions AS.\nPress Run anyway, and the application starts. This warning is only displayed once.\n",
-                html:     "\u003ch2 id=\"resinsight-installation\"\u003eResInsight Installation\u003c/h2\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\u003ch2 id=\"octave-installation-optional\"\u003eOctave Installation (optional)\u003c/h2\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 \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\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\u003ch2 id=\"faq\"\u003eFAQ\u003c/h2\u003e\n\u003ch3 id=\"smartscreen-warnings\"\u003eSmartscreen warnings\u003c/h3\u003e\n\u003cp\u003eWhen launching ResInsight at the first time, a Smartscreen warning might be displayed. This is a security feature by Microsoft, and will warn the user when an unknown program is launched. This warning is displayed once for each installation.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/Smartscreen_01.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003ePress the \u003cstrong\u003eMore info\u003c/strong\u003e link in the upper left section.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/Smartscreen_02.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNotice the information and digital signature by \u003cstrong\u003eCeetron Solutions AS\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003ePress \u003cstrong\u003eRun anyway\u003c/strong\u003e, and the application starts. This warning is only displayed once.\u003c/p\u003e\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.\nOctave 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.\nYou 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.\nFAQ Smartscreen warnings When launching ResInsight at the first time, a Smartscreen warning might be displayed. This is a security feature by Microsoft, and will warn the user when an unknown program is launched. This warning is displayed once for each installation.\nPress the More info link in the upper left section.\nNotice the information and digital signature by Ceetron Solutions AS.\nPress Run anyway, and the application starts. This warning is only displayed once.\n",
+                html:     "\u003ch2 id=\"resinsight-installation\"\u003eResInsight Installation\u003c/h2\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\u003ch2 id=\"octave-installation-optional\"\u003eOctave Installation (optional)\u003c/h2\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 \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\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\u003ch2 id=\"faq\"\u003eFAQ\u003c/h2\u003e\n\u003ch3 id=\"smartscreen-warnings\"\u003eSmartscreen warnings\u003c/h3\u003e\n\u003cp\u003eWhen launching ResInsight at the first time, a Smartscreen warning might be displayed. This is a security feature by Microsoft, and will warn the user when an unknown program is launched. This warning is displayed once for each installation.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/Smartscreen_01.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003ePress the \u003cstrong\u003eMore info\u003c/strong\u003e link in the upper left section.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/Smartscreen_02.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNotice the information and digital signature by \u003cstrong\u003eCeetron Solutions AS\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003ePress \u003cstrong\u003eRun anyway\u003c/strong\u003e, and the application starts. This warning is only displayed once.\u003c/p\u003e\n",
                 url:      "/getting-started/download-and-install/windows-installation/"
             };
         
@@ -3245,8 +3244,8 @@ if (!doNotTrack) {
          
             window.store["/getting-started/helpmenuanddocumentation/"] = {
                 title:    "Help Menu and Documentation",
-                content:  "Integrated ResInsight Help If you need the user manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.\nResInsight Online Tutorials  ResInsight Tutorial Videos (YouTube) ResInsight Tutorials  ResInsight Help Menu ResInsight Help menu options are:\n About \u0026ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems. Command Line Help \u0026ndash; Provides an overview of ResInsight Command line parameters and their syntax. Summary Command Line Help \u0026ndash; Provides an overview of ResInsight Summary command line parameters and their syntax. Users Guide \u0026ndash; Opens the ResInsight documentation in your default browser Search Help \u0026ndash; Searches the ResInsight documentation for help on the selected item in Project Tree. Please note that the function key F1 is a shortcut to this menu option.  ResInsight 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:     "\u003ch2 id=\"integrated-resinsight-help\"\u003eIntegrated ResInsight Help\u003c/h2\u003e\n\u003cp\u003eIf you need the user manual for an object, you can use the right-click menu of the object and select \u003cstrong\u003eSearch Help for:\u003c/strong\u003e. This will open up the user manual for the selected object from \u003cstrong\u003eresinsight.org\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/help_on_context_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"resinsight-online-tutorials\"\u003eResInsight Online Tutorials\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/tutorials-you-tube.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://www.youtube.com/channel/UCEJoH_ti1YZXz4hPMeAKMgw\"\u003eResInsight Tutorial Videos (YouTube)\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/CeetronSolutions/resinsight-tutorials\"\u003eResInsight Tutorials\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"resinsight-help-menu\"\u003eResInsight Help Menu\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/HelpMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight Help menu options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAbout\u003c/strong\u003e \u0026ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCommand Line Help\u003c/strong\u003e \u0026ndash; Provides an overview of ResInsight \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand line parameters\u003c/a\u003e and their syntax.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSummary Command Line Help\u003c/strong\u003e \u0026ndash; Provides an overview of ResInsight \u003ca href=\"/scripting/commandlineinterface/#summary-plotting\"\u003eSummary command line parameters\u003c/a\u003e and their syntax.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUsers Guide\u003c/strong\u003e \u0026ndash; Opens the \u003ca href=\"https://resinsight.org\"\u003eResInsight documentation\u003c/a\u003e in your default browser\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSearch Help\u003c/strong\u003e \u0026ndash; Searches the \u003ca href=\"https://resinsight.org\"\u003eResInsight documentation\u003c/a\u003e for help on the selected item  in \u003cstrong\u003eProject Tree\u003c/strong\u003e. \nPlease note that the function key \u003cstrong\u003eF1\u003c/strong\u003e is a shortcut to this menu option.\u003c/li\u003e\n\u003c/ul\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",
+                content:  "Integrated ResInsight Help If you need the user manual for an object, you can use the right-click menu of the object and select Search Help for:. This will open up the user manual for the selected object from resinsight.org.\nResInsight Online Tutorials ResInsight Tutorial Videos (YouTube) ResInsight Tutorials ResInsight Help Menu ResInsight Help menu options are:\nAbout \u0026ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems. Command Line Help \u0026ndash; Provides an overview of ResInsight Command line parameters and their syntax. Summary Command Line Help \u0026ndash; Provides an overview of ResInsight Summary command line parameters and their syntax. Users Guide \u0026ndash; Opens the ResInsight documentation in your default browser Search Help \u0026ndash; Searches the ResInsight documentation for help on the selected item in Project Tree. Please note that the function key F1 is a shortcut to this menu option. ResInsight 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:     "\u003ch2 id=\"integrated-resinsight-help\"\u003eIntegrated ResInsight Help\u003c/h2\u003e\n\u003cp\u003eIf you need the user manual for an object, you can use the right-click menu of the object and select \u003cstrong\u003eSearch Help for:\u003c/strong\u003e. This will open up the user manual for the selected object from \u003cstrong\u003eresinsight.org\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/help_on_context_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"resinsight-online-tutorials\"\u003eResInsight Online Tutorials\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/tutorials-you-tube.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003ca href=\"https://www.youtube.com/channel/UCEJoH_ti1YZXz4hPMeAKMgw\"\u003eResInsight Tutorial Videos (YouTube)\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"https://github.com/CeetronSolutions/resinsight-tutorials\"\u003eResInsight Tutorials\u003c/a\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"resinsight-help-menu\"\u003eResInsight Help Menu\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/getting-started/HelpMenu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight Help menu options are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAbout\u003c/strong\u003e \u0026ndash; Opens a dialog with information on ResInsight version, enabled features, and technical information of subsystems.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCommand Line Help\u003c/strong\u003e \u0026ndash; Provides an overview of ResInsight \u003ca href=\"/scripting/commandlineinterface/\"\u003eCommand line parameters\u003c/a\u003e and their syntax.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSummary Command Line Help\u003c/strong\u003e \u0026ndash; Provides an overview of ResInsight \u003ca href=\"/scripting/commandlineinterface/#summary-plotting\"\u003eSummary command line parameters\u003c/a\u003e and their syntax.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUsers Guide\u003c/strong\u003e \u0026ndash; Opens the \u003ca href=\"https://resinsight.org\"\u003eResInsight documentation\u003c/a\u003e in your default browser\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSearch Help\u003c/strong\u003e \u0026ndash; Searches the \u003ca href=\"https://resinsight.org\"\u003eResInsight documentation\u003c/a\u003e for help on the selected item  in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\nPlease note that the function key \u003cstrong\u003eF1\u003c/strong\u003e is a shortcut to this menu option.\u003c/li\u003e\n\u003c/ul\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/helpmenuanddocumentation/"
             };
         
@@ -3255,7 +3254,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\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",
+                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/"
             };
         
@@ -3263,8 +3262,8 @@ if (!doNotTrack) {
          
             window.store["/misc/advancedtextinput/"] = {
                 title:    "Advanced Text Input",
-                content:  "When the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.\nSupported text format 5,10-13,20-26:2\rThis text will produce an integer array with values\n[5, 10, 11, 12, 13, 20, 22, 24, 26]\rUsing the syntax \u0026ldquo;20-26:2\u0026rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]\n",
-                html:     "\u003cp\u003eWhen the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.\u003c/p\u003e\n\u003ch2 id=\"supported-text-format\"\u003eSupported text format\u003c/h2\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-txt\" data-lang=\"txt\"\u003e5,10-13,20-26:2\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eThis text will produce an integer array with values\u003c/p\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-txt\" data-lang=\"txt\"\u003e[5, 10, 11, 12, 13, 20, 22, 24, 26]\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eUsing the syntax \u003cstrong\u003e\u0026ldquo;20-26:2\u0026rdquo;\u003c/strong\u003e will produce integer values in the range at a step of 2, resulting in \u003cstrong\u003e[20, 22, 24, 26]\u003c/strong\u003e\u003c/p\u003e\n",
+                content:  "When the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.\nSupported text format 5,10-13,20-26:2 This text will produce an integer array with values\n[5, 10, 11, 12, 13, 20, 22, 24, 26] Using the syntax \u0026ldquo;20-26:2\u0026rdquo; will produce integer values in the range at a step of 2, resulting in [20, 22, 24, 26]\n",
+                html:     "\u003cp\u003eWhen the user is requested to specify a list of integer values, it can be useful to input the list using a text string. This can be a selection of K slices, a selection of realisations or a selection of integer values in a integer cell result.\u003c/p\u003e\n\u003ch2 id=\"supported-text-format\"\u003eSupported text format\u003c/h2\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5,10-13,20-26:2\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eThis text will produce an integer array with values\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e[5, 10, 11, 12, 13, 20, 22, 24, 26]\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eUsing the syntax \u003cstrong\u003e\u0026ldquo;20-26:2\u0026rdquo;\u003c/strong\u003e will produce integer values in the range at a step of 2, resulting in \u003cstrong\u003e[20, 22, 24, 26]\u003c/strong\u003e\u003c/p\u003e\n",
                 url:      "/misc/advancedtextinput/"
             };
         
@@ -3272,8 +3271,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 2019 and later is supported.\nGCC Compiler On RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with\nsource /opt/rh/devtoolset-10/enable\r Qt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.\nQt download\nOn some configurations you will be asked to specify the location of Qt. Preferred method is to add Qt path to CMake variable CMAKE_PREFIX_PATH\nExample for Windows : CMAKE_PREFIX_PATH=F:/Qt/5.15.2/msvc2019_64\nCMake CMake version 3.15 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 10/11 using Microsoft Visual Studio 2019/2022. 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 For a reference build instruction for Ubuntu, see Reference installation description for Ubuntu\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_ENABLE_HDF5 ON Windows Only: Download and use HDF5 library   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_QT5_BUNDLE_LIBRARIES OFF Linux only: Include Qt5 libraries in the installation package   RESINSIGHT_BUILD_LIBS_FROM_SOURCE ON If ON: Build some ThirdParty libs locally. If OFF: Download precompiled libraries   RESINSIGHT_BUNDLE_OPENSSL OFF Bundle the OpenSSL library binaries   RESINSIGHT_ENABLE_UNITY_BUILD OFF Activate use of CMAKE_UNITY_BUILD on some libraries to improve build speed   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   RESINSIGHT_TREAT_WARNINGS_AS_ERRORS OFF Enable warnings as errors   RESINSIGHT_UPDATE_SUBMODULES ON Automatically issue \u0026lsquo;git submodule update \u0026ndash;init \u0026ndash;recursively\u0026rsquo; on ThirdParty folder   RESINSIGHT_VCPKG_AUTO_INSTALL OFF Automatically build required dependencies using \u0026lsquo;vcpkg\u0026rsquo;    Configuration parameters for Python    CMake Name Default Description     RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python   RESINSIGHT_GRPC_BUNDLE_PYTHON_MODULE OFF Bundle GRPC Python module in install folder   RESINSIGHT_GRPC_DOWNLOAD_PYTHON_MODULE ON Download GRPC Python module   RESINSIGHT_GRPC_PYTHON_EXECUTABLE Blank Location of Python3 executable    Optional Libraries and features Python Please see ResInsight Python API for installation and configuration.\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 libqt5svg5-dev qtbase5-private-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 2019 and later is supported.\u003c/p\u003e\n\u003ch3 id=\"gcc-compiler\"\u003eGCC Compiler\u003c/h3\u003e\n\u003cp\u003eOn RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esource /opt/rh/devtoolset-10/enable\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"qt-5\"\u003eQt 5\u003c/h3\u003e\n\u003cp\u003eQt 5.12 or later is supported, Qt 5.15 is recommended.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt download\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eOn some configurations you will be asked to specify the location of Qt. Preferred method is to add Qt path to CMake variable \u003cstrong\u003eCMAKE_PREFIX_PATH\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eExample for Windows : \u003ccode\u003eCMAKE_PREFIX_PATH=F:/Qt/5.15.2/msvc2019_64\u003c/code\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 3.15 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 10/11 using Microsoft Visual Studio 2019/2022. 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.\u003c/p\u003e\n\u003ch3 id=\"linux\"\u003eLinux\u003c/h3\u003e\n\u003cp\u003eFor a reference build instruction for Ubuntu, see \u003ca href=\"/getting-started/download-and-install/build-instructions-ubuntu/\"\u003eReference installation description for Ubuntu\u003c/a\u003e\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_ENABLE_HDF5\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eWindows Only: Download and use HDF5 library\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_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_BUILD_LIBS_FROM_SOURCE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eIf ON: Build some ThirdParty libs locally. If OFF: Download precompiled libraries\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 binaries\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_UNITY_BUILD\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eActivate use of CMAKE_UNITY_BUILD on some libraries to improve build speed\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\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_TREAT_WARNINGS_AS_ERRORS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable warnings as errors\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_UPDATE_SUBMODULES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eAutomatically issue \u0026lsquo;git submodule update \u0026ndash;init \u0026ndash;recursively\u0026rsquo; on ThirdParty folder\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_VCPKG_AUTO_INSTALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eAutomatically build required dependencies using \u0026lsquo;vcpkg\u0026rsquo;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"configuration-parameters-for-python\"\u003eConfiguration parameters for Python\u003c/h4\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_BUNDLE_PYTHON_MODULE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eBundle GRPC Python module in install folder\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_DOWNLOAD_PYTHON_MODULE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eDownload GRPC Python module\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\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\"\u003ePython\u003c/h4\u003e\n\u003cp\u003ePlease see \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e for installation and configuration.\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 libqt5svg5-dev qtbase5-private-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",
+                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 2019 and later is supported.\nGCC Compiler On RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with\nsource /opt/rh/devtoolset-10/enable\rQt 5 Qt 5.12 or later is supported, Qt 5.15 is recommended.\nQt download\nOn some configurations you will be asked to specify the location of Qt. Preferred method is to add Qt path to CMake variable CMAKE_PREFIX_PATH\nExample for Windows : CMAKE_PREFIX_PATH=F:/Qt/5.15.2/msvc2019_64\nCMake CMake version 3.15 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.\nOpen 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 10/11 using Microsoft Visual Studio 2019/2022. 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 For a reference build instruction for Ubuntu, see Reference installation description for Ubuntu\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_ENABLE_HDF5 ON Windows Only: Download and use HDF5 library 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\nCMake Name Default Description RESINSIGHT_QT5_BUNDLE_LIBRARIES OFF Linux only: Include Qt5 libraries in the installation package RESINSIGHT_BUILD_LIBS_FROM_SOURCE ON If ON: Build some ThirdParty libs locally. If OFF: Download precompiled libraries RESINSIGHT_BUNDLE_OPENSSL OFF Bundle the OpenSSL library binaries RESINSIGHT_ENABLE_UNITY_BUILD OFF Activate use of CMAKE_UNITY_BUILD on some libraries to improve build speed 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 RESINSIGHT_TREAT_WARNINGS_AS_ERRORS OFF Enable warnings as errors RESINSIGHT_UPDATE_SUBMODULES ON Automatically issue \u0026lsquo;git submodule update \u0026ndash;init \u0026ndash;recursively\u0026rsquo; on ThirdParty folder RESINSIGHT_VCPKG_AUTO_INSTALL OFF Automatically build required dependencies using \u0026lsquo;vcpkg\u0026rsquo; Configuration parameters for Python CMake Name Default Description RESINSIGHT_ENABLE_GRPC OFF Enable gRPC scripting server. Required to be able to use ResInsight from Python RESINSIGHT_GRPC_BUNDLE_PYTHON_MODULE OFF Bundle GRPC Python module in install folder RESINSIGHT_GRPC_DOWNLOAD_PYTHON_MODULE ON Download GRPC Python module RESINSIGHT_GRPC_PYTHON_EXECUTABLE Blank Location of Python3 executable Optional Libraries and features Python Please see ResInsight Python API for installation and configuration.\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 libqt5svg5-dev qtbase5-private-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 2019 and later is supported.\u003c/p\u003e\n\u003ch3 id=\"gcc-compiler\"\u003eGCC Compiler\u003c/h3\u003e\n\u003cp\u003eOn RedHat Linux 7 or CentOS 7 you need to install devtoolset-10, and enable it with\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esource /opt/rh/devtoolset-10/enable\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"qt-5\"\u003eQt 5\u003c/h3\u003e\n\u003cp\u003eQt 5.12 or later is supported, Qt 5.15 is recommended.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"http://download.qt.io/archive/qt/\"\u003eQt download\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eOn some configurations you will be asked to specify the location of Qt. Preferred method is to add Qt path to CMake variable \u003cstrong\u003eCMAKE_PREFIX_PATH\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eExample for Windows : \u003ccode\u003eCMAKE_PREFIX_PATH=F:/Qt/5.15.2/msvc2019_64\u003c/code\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 3.15 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 10/11 using Microsoft Visual Studio 2019/2022. 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.\u003c/p\u003e\n\u003ch3 id=\"linux\"\u003eLinux\u003c/h3\u003e\n\u003cp\u003eFor a reference build instruction for Ubuntu, see \u003ca href=\"/getting-started/download-and-install/build-instructions-ubuntu/\"\u003eReference installation description for Ubuntu\u003c/a\u003e\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_ENABLE_HDF5\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eWindows Only: Download and use HDF5 library\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_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_BUILD_LIBS_FROM_SOURCE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eIf ON: Build some ThirdParty libs locally. If OFF: Download precompiled libraries\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 binaries\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_ENABLE_UNITY_BUILD\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eActivate use of CMAKE_UNITY_BUILD on some libraries to improve build speed\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\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_TREAT_WARNINGS_AS_ERRORS\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eEnable warnings as errors\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_UPDATE_SUBMODULES\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eAutomatically issue \u0026lsquo;git submodule update \u0026ndash;init \u0026ndash;recursively\u0026rsquo; on ThirdParty folder\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_VCPKG_AUTO_INSTALL\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eAutomatically build required dependencies using \u0026lsquo;vcpkg\u0026rsquo;\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch4 id=\"configuration-parameters-for-python\"\u003eConfiguration parameters for Python\u003c/h4\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_BUNDLE_PYTHON_MODULE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eOFF\u003c/td\u003e\n\u003ctd\u003eBundle GRPC Python module in install folder\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003ccode\u003eRESINSIGHT_GRPC_DOWNLOAD_PYTHON_MODULE\u003c/code\u003e\u003c/td\u003e\n\u003ctd\u003eON\u003c/td\u003e\n\u003ctd\u003eDownload GRPC Python module\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\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\"\u003ePython\u003c/h4\u003e\n\u003cp\u003ePlease see \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e for installation and configuration.\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 libqt5svg5-dev qtbase5-private-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/"
             };
         
@@ -3281,7 +3280,7 @@ if (!doNotTrack) {
          
             window.store["/getting-started/download-and-install/build-instructions-ubuntu/"] = {
                 title:    "Build Instructions Ubuntu",
-                content:  "Dependencies and Prerequisites Configuration and build    Tool Minimum version     git 2.7.4   gcc 10   python 3    Update apt installer\nsudo apt update\r Install GCC and related tools\nsudo apt install build-essential\rsudo apt install curl zip unzip tar\r As gcc 10 is required, it can be useful to set the default compiler. Set default compiler\nInstall Qt\nsudo apt install -y qtbase5-dev libqt5svg5-dev qtbase5-private-dev\r Clone and update sub modules git clone git://github.com/OPM/ResInsight.git ResInsight\rcd ResInsight\rgit submodule update --init\r Build and install required dependencies using vcpkg vcpkg is located in the folder ThirdParty/vcpkg\nThirdParty/vcpkg/bootstrap-vcpkg.sh\rThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3\r (Windows) Build and install required dependencies using vcpkg Open a command prompt for Visual Studio x64\nThirdParty/vcpkg/bootstrap-vcpkg.bat\rThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3 --triplet x64-windows\r[Developer notes](https://ceetronsolutions.github.io/resinsight-system-doc/editor/vcpkg)\r Build ResInsight mkdir cmakebuild\rcd cmakebuild\rcmake \\\r-DRESINSIGHT_ENABLE_GRPC=true \\\r-DVCPKG_TARGET_TRIPLET=x64-linux \\\r-DCMAKE_TOOLCHAIN_FILE=../ThirdParty/vcpkg/scripts/buildsystems/vcpkg.cmake \\\r-DRESINSIGHT_GRPC_PYTHON_EXECUTABLE=python \\\r..\rmake -j8\r Notes for CentOS The dependency on atomic can be installed using the following code, adjust the devtoolset version to match your installation:\nsudo yum install devtoolset-11-libatomic-devel\r Link to workflow for CentOS 7\n",
+                content:  "Dependencies and Prerequisites Configuration and build Tool Minimum version git 2.7.4 gcc 10 python 3 Update apt installer\nsudo apt update\rInstall GCC and related tools\nsudo apt install build-essential\rsudo apt install curl zip unzip tar\rAs gcc 10 is required, it can be useful to set the default compiler. Set default compiler\nInstall Qt\nsudo apt install -y qtbase5-dev libqt5svg5-dev qtbase5-private-dev\rClone and update sub modules git clone git://github.com/OPM/ResInsight.git ResInsight\rcd ResInsight\rgit submodule update --init\rBuild and install required dependencies using vcpkg vcpkg is located in the folder ThirdParty/vcpkg\nThirdParty/vcpkg/bootstrap-vcpkg.sh\rThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3\r(Windows) Build and install required dependencies using vcpkg Open a command prompt for Visual Studio x64\nThirdParty/vcpkg/bootstrap-vcpkg.bat\rThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3 --triplet x64-windows\r[Developer notes](https://ceetronsolutions.github.io/resinsight-system-doc/editor/vcpkg)\rBuild ResInsight mkdir cmakebuild\rcd cmakebuild\rcmake \\\r-DRESINSIGHT_ENABLE_GRPC=true \\\r-DVCPKG_TARGET_TRIPLET=x64-linux \\\r-DCMAKE_TOOLCHAIN_FILE=../ThirdParty/vcpkg/scripts/buildsystems/vcpkg.cmake \\\r-DRESINSIGHT_GRPC_PYTHON_EXECUTABLE=python \\\r..\rmake -j8\rNotes for CentOS The dependency on atomic can be installed using the following code, adjust the devtoolset version to match your installation:\nsudo yum install devtoolset-11-libatomic-devel\rLink to workflow for CentOS 7\n",
                 html:     "\u003ch2 id=\"dependencies-and-prerequisites\"\u003eDependencies and Prerequisites\u003c/h2\u003e\n\u003ch3 id=\"configuration-and-build\"\u003eConfiguration and build\u003c/h3\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eTool\u003c/th\u003e\n\u003cth\u003eMinimum version\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003egit\u003c/td\u003e\n\u003ctd\u003e2.7.4\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003egcc\u003c/td\u003e\n\u003ctd\u003e10\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003epython\u003c/td\u003e\n\u003ctd\u003e3\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eUpdate apt installer\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esudo apt update\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eInstall GCC and related tools\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esudo apt install build-essential\r\nsudo apt install curl zip unzip tar\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003eAs gcc 10 is required, it can be useful to set the default compiler.\n\u003ca href=\"https://linuxconfig.org/how-to-switch-between-multiple-gcc-and-g-compiler-versions-on-ubuntu-20-04-lts-focal-fossa\"\u003eSet default compiler\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eInstall Qt\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esudo apt install -y qtbase5-dev libqt5svg5-dev qtbase5-private-dev\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"clone-and-update-sub-modules\"\u003eClone and update sub modules\u003c/h3\u003e\n\u003cpre\u003e\u003ccode\u003egit clone git://github.com/OPM/ResInsight.git ResInsight\r\ncd ResInsight\r\ngit submodule update --init\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"build-and-install-required-dependencies-using-vcpkg\"\u003eBuild and install required dependencies using vcpkg\u003c/h3\u003e\n\u003cp\u003evcpkg is located in the folder ThirdParty/vcpkg\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eThirdParty/vcpkg/bootstrap-vcpkg.sh\r\nThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"windows-build-and-install-required-dependencies-using-vcpkg\"\u003e(Windows) Build and install required dependencies using vcpkg\u003c/h3\u003e\n\u003cp\u003eOpen a command prompt for Visual Studio x64\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003eThirdParty/vcpkg/bootstrap-vcpkg.bat\r\nThirdParty/vcpkg/vcpkg install grpc boost-filesystem boost-spirit eigen3 --triplet x64-windows\r\n\r\n[Developer notes](https://ceetronsolutions.github.io/resinsight-system-doc/editor/vcpkg)\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"build-resinsight\"\u003eBuild ResInsight\u003c/h3\u003e\n\u003cpre\u003e\u003ccode\u003emkdir cmakebuild\r\ncd cmakebuild\r\ncmake \\\r\n-DRESINSIGHT_ENABLE_GRPC=true \\\r\n-DVCPKG_TARGET_TRIPLET=x64-linux \\\r\n-DCMAKE_TOOLCHAIN_FILE=../ThirdParty/vcpkg/scripts/buildsystems/vcpkg.cmake \\\r\n-DRESINSIGHT_GRPC_PYTHON_EXECUTABLE=python \\\r\n..\r\n\r\nmake -j8\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003ch3 id=\"notes-for-centos\"\u003eNotes for CentOS\u003c/h3\u003e\n\u003cp\u003eThe dependency on \u003ccode\u003eatomic\u003c/code\u003e can be installed using the following code, adjust the devtoolset version to match your installation:\u003c/p\u003e\n\u003cpre\u003e\u003ccode\u003esudo yum install devtoolset-11-libatomic-devel\r\n\u003c/code\u003e\u003c/pre\u003e\n\u003cp\u003e\u003ca href=\"https://github.com/OPM/ResInsight/blob/dev/.github/workflows/centos7.yml\"\u003eLink to workflow for CentOS 7\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/getting-started/download-and-install/build-instructions-ubuntu/"
             };
@@ -3290,8 +3289,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, please see the ResInsight Python API.\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]    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 ✔    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, please see \nthe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\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)\u003csup\u003e1\u003c/sup\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\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\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",
+                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, please see the ResInsight Python API.\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.\nType 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] 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.\nParameter Description Type Required path File path to the project file String ✔ openProject(path=\u0026#34;/home/user/ResInsightProject.rsp\u0026#34;) closeProject Closes the current open project.\ncloseProject() setStartDir Set startup directory.\nParameter Description Type Required path Path to directory to use as startup directory String ✔ setStartDir(path=\u0026#34;/home/user\u0026#34;) loadCase Import Eclipse case from file.\nParameter Description Type Required path File path to the case to load String ✔ loadCase(path=\u0026#34;/home/user/reservoir.EGRID\u0026#34;) createGridCaseGroup Create a Grid Case Group from a list of files.\nParameter Description Type Required casePaths List of Paths to Case Files String ✔ createStatisticsCase Create a Statistics Case in a Grid Case Group.\nParameter Description Type Required caseGroupId ID to the Case Group Integer ✔ createGridCaseGroup(path=[\u0026#34;/home/user/reservoir.EGRID\u0026#34;, \u0026#34;/home/user/other_reservoir.EGRID\u0026#34;])\rcreateStatisticsCase(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.\nParameter 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=\u0026#34;/home/user/otherReservoir.EGRID\u0026#34;, 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.\nParameter 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=\u0026#34;C:/resinsight/replacement_files.txt\u0026#34;) 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.\nParameter Description Type Required gridListFile File path to file containing list of cases to create snapshots of String ✔ exportMultiCaseSnapshots(gridListFile=\u0026#34;C:\\\\resinsight\\\\replacement_files.txt\u0026#34;) exportSnapshots Export snapshots of specified type.\nFolder to output snapshots should be set using setExportFolder with SNAPSHOTS type.\nParameter 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.\nParameter 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=\u0026#34;SOIL\u0026#34;) 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.\nParameter 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=[\u0026#34;view A\u0026#34;, \u0026#34;view 4\u0026#34;]) exportWellPathCompletions Export well path completions.\nParameter 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) exportSimWellFractureCompletions Export fracture completions for simulation wells.\nParameter 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=\u0026#34;View 2\u0026#34;, timeStep=5) exportMsw Export multi-segment wells.\nParameter 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=\u0026#34;MainWell\u0026#34;) exportWellPaths Export well paths.\nParameter 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=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], mdStepSize=1.5) exportVisibleCells Export visible cells\nParameter 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=\u0026#34;View 1\u0026#34;, exportKeyword=MULTNUM) exportFlowCharacteristics Export Flow Characteristics data to text file in CSV format\nParameter 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=[\u0026#34;INJA\u0026#34;, \u0026#34;INJB\u0026#34;], producers=[\u0026#34;PROD_F\u0026#34;], fileName=\u0026#34;myData.csv\u0026#34;) 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.\nParameter 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=\u0026#34;/home/user/snapshots\u0026#34;) Other runOctaveScript Execute an Octave script.\nParameter 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=\u0026#34;/home/user/octave/something.m\u0026#34;, caseIds=[1,2,6]) setMainWindowSize Resize the main window to the specified size.\nParameter 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) computeCaseGroupStatistics Compute statistics for statistics cases.\nParameter 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]) setTimeStep Set the time step for a given case. The time step is used for all views on the case.\nParameter 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) scaleFractureTemplate Scale fracture template parameters.\nParameter 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) setFractureContainment Set fracture template containment parameters.\nParameter 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) createMultipleFractures Create multiple fractures on one or more well paths.\nParameter 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=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], 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.\nParameter 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=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL) createSaturationPressurePlots Create saturation pressure plots for the specified cases.\nParameter Description Type Required caseIds IDs of cases to create plots for. Default is all cases List of Integer createSaturationPressurePlots(caseIds=[0]) ",
+                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, please see\nthe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\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 tabindex=\"0\"\u003e\u003ccode\u003eCommand file examples are displayed in sections like this.\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)\u003csup\u003e1\u003c/sup\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\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\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 tabindex=\"0\"\u003e\u003ccode\u003eopenProject(path=\u0026#34;/home/user/ResInsightProject.rsp\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003ecloseProject()\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 tabindex=\"0\"\u003e\u003ccode\u003esetStartDir(path=\u0026#34;/home/user\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003eloadCase(path=\u0026#34;/home/user/reservoir.EGRID\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003ecreateGridCaseGroup(path=[\u0026#34;/home/user/reservoir.EGRID\u0026#34;, \u0026#34;/home/user/other_reservoir.EGRID\u0026#34;])\r\ncreateStatisticsCase(caseGroupId=0)\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 tabindex=\"0\"\u003e\u003ccode\u003ereplaceCase(newGridFile=\u0026#34;/home/user/otherReservoir.EGRID\u0026#34;, caseId=4)\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 tabindex=\"0\"\u003e\u003ccode\u003ereplaceSourceCases(gridListFile=\u0026#34;C:/resinsight/replacement_files.txt\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportMultiCaseSnapshots(gridListFile=\u0026#34;C:\\\\resinsight\\\\replacement_files.txt\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportSnapshots(type=PLOTS)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportProperty(caseId=1, timeStep=4, property=\u0026#34;SOIL\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportPropertyInViews(caseId=1)\r\n\r\nexportPropertyInViews(caseId=1, viewNames=[\u0026#34;view A\u0026#34;, \u0026#34;view 4\u0026#34;])\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 tabindex=\"0\"\u003e\u003ccode\u003eexportWellPathCompletions(caseId=3, timeStep=5, includeFishbones=false)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportSimWellFractureCompletions(caseId=3, viewName=\u0026#34;View 2\u0026#34;, timeStep=5)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportMsw(caseId=1, wellPath=\u0026#34;MainWell\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportWellPaths(wellPathNames=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], mdStepSize=1.5)\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 tabindex=\"0\"\u003e\u003ccode\u003eexporVisibleCells(caseId=0, viewName=\u0026#34;View 1\u0026#34;, exportKeyword=MULTNUM)\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 tabindex=\"0\"\u003e\u003ccode\u003eexportFlowCharacteristics(caseId=0, timeSteps=[1, 5, 6], injectors=[\u0026#34;INJA\u0026#34;, \u0026#34;INJB\u0026#34;], producers=[\u0026#34;PROD_F\u0026#34;], fileName=\u0026#34;myData.csv\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003esetExportFolder(type=SNAPSHOTS, path=\u0026#34;/home/user/snapshots\u0026#34;)\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 tabindex=\"0\"\u003e\u003ccode\u003erunOctaveScript(path=\u0026#34;/home/user/octave/something.m\u0026#34;, caseIds=[1,2,6])\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 tabindex=\"0\"\u003e\u003ccode\u003esetMainWindowSize(width=1920, height=1200)\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 tabindex=\"0\"\u003e\u003ccode\u003ecomputeCaseGroupStatistics(caseIds=[5])\r\n\r\ncomputeCaseGroupStatistics(caseIds=[2,4,8])\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 tabindex=\"0\"\u003e\u003ccode\u003esetTimeStep(caseId=1, timeStep=8)\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 tabindex=\"0\"\u003e\u003ccode\u003escaleFractureTemplate(id=1, width=2, height=1.5)\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 tabindex=\"0\"\u003e\u003ccode\u003esetFractureContainment(id=1, topLayer=2, baseLayer=7)\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 tabindex=\"0\"\u003e\u003ccode\u003ecreateMultipleFractures(caseId=0, templateId=1, wellPathNames=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], action=REPLACE_FRACTURES)\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 tabindex=\"0\"\u003e\u003ccode\u003ecreateLgrForCompletions(caseId=0, timeStep=0, wellPathNames=[\u0026#34;B-1H\u0026#34;, \u0026#34;B-2H\u0026#34;], refinementI=2, refinementJ=3, refinementK=4, splitType=LGR_PER_WELL)\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 tabindex=\"0\"\u003e\u003ccode\u003ecreateSaturationPressurePlots(caseIds=[0])\n\u003c/code\u003e\u003c/pre\u003e",
                 url:      "/scripting/commandfile/"
             };
         
@@ -3299,8 +3298,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 imported well path.\nBuilding a multilateral well path\nBuilding a well path  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 should pass (well path targets) 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. Link Reference Point - All wells with this option checked will be moved as a group. Air Gap - Specify Air Gap, i.e. distance from Rotary Kelling Bushing to sea surface. Applies to well path export only. MD at First Target - Defines the measured depth at the first defined well target. Generate Target at Sea Level - Automatically create a target at sea level based on a reasonable well path from reservoir to sea level  Well Targets Appearance\nControls the visibility and appearance of spheres at well target locations in addition to 3D interaction handles. The 3D interaction handles will be visible only when the Well Target object is selected, but the spheres will be always be visible if enabled.\nWell Targets\nList of all defined well targets. The editor will have a contrast background color when in picking state.\n Relative Coord - Target position relative to reference point. UTM Coords can be displayed using a checkbox option above the table. MD - Measured depth along the well path. DL in - Dog leg inwards [degrees/30m]. DL out - Dog leg outwards [degrees/30m]. Azi (deg) - Azimuth. Y axis is 0 degrees. If the Azi checkbox is ticked, the user can provide a fixed value for Azimuth. Inc (deg) - Inclination. Z axis is 0 degrees. If the Inc checkbox is ticked, the user can provide a fixed value for Inclination.  The other columns defined by the \u0026ldquo;Est\u0026rdquo;-prefix displays the result of dog leg and direction values produced by the well path geometry estimation algorithm.\nA well path defined by well targets 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 Path Duplication To duplicate an existing well path, select Duplicate from the right-click menu of a well path in the Project Tree or right-click on the well path geometry in the 3D view. This operation will create a new well path with a set of well targets.\nThe full geometry of the new well path is an estimate of the source well path, so the geometry might differ slightly.\nWell Target Interaction Operations When the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\n   User Interaction Description     Mouse Move Modification of a single target   Mouse Move + CTRL Modification of all well target on selected well (laterals excluded)   Mouse Move + CTRL + SHIFT Modification of all well targets (laterals included)    Starting well path at a fixed position The toggle Generate Target at Sea Level is on by default. If the well path is supposed to start at a predefined location at the sea level, the following procedure can be used:\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. Clear Generate Target at Sea Level Right-click in the pink well target area, and select Insert new Target above In the UTM Reference Point field, enter the predefined UTM coordinate (usually, the depth is set to 0.0 for sea level) Continue clicking on geometry in the 3D view to add more well targets and make sure the first well target is defined by [0.00 0.00 0.00] to make sure the first target is located at the predefined UTM reference position  Well 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 imported well path.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/createmultilateralwellpaths/\"\u003eBuilding a multilateral well path\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"building-a-well-path\"\u003eBuilding a well path\u003c/h3\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 should pass (well path targets)\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\u003eLink Reference Point\u003c/strong\u003e - All wells with this option checked will be moved as a group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAir Gap\u003c/strong\u003e - Specify Air Gap, i.e. distance from Rotary Kelling Bushing to sea surface. Applies to well path export only.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD at First Target\u003c/strong\u003e - Defines the measured depth at the first defined well target.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e - Automatically create a target at sea level based on a reasonable well path from reservoir to sea level\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eWell Targets Appearance\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eControls the visibility and appearance of spheres at well target locations in addition to 3D interaction handles. The 3D interaction handles will be visible only when the Well Target object is selected, but the spheres will be always be visible if enabled.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eWell Targets\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eList of all defined well targets. The editor will have a contrast background color when in picking state.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Coord\u003c/strong\u003e - Target position relative to reference point. \u003cstrong\u003eUTM Coords\u003c/strong\u003e can be displayed using a checkbox option above the table.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD\u003c/strong\u003e - Measured depth along the well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL in\u003c/strong\u003e - Dog leg inwards [degrees/30m].\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL out\u003c/strong\u003e - Dog leg outwards [degrees/30m].\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzi (deg)\u003c/strong\u003e - Azimuth. Y axis is 0 degrees. If the \u003cstrong\u003eAzi\u003c/strong\u003e checkbox is ticked, the user can provide a fixed value for Azimuth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInc (deg)\u003c/strong\u003e - Inclination. Z axis is 0 degrees. If the \u003cstrong\u003eInc\u003c/strong\u003e checkbox is ticked, the user can provide a fixed value for Inclination.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe other columns defined by the \u0026ldquo;Est\u0026rdquo;-prefix displays the result of dog leg and direction values produced by the well path geometry estimation algorithm.\u003c/p\u003e\n\u003cp\u003eA well path defined by well targets 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-path-duplication\"\u003eWell Path Duplication\u003c/h3\u003e\n\u003cp\u003eTo duplicate an existing well path, select \u003cstrong\u003eDuplicate\u003c/strong\u003e from the right-click menu of a well path in the \u003cstrong\u003eProject Tree\u003c/strong\u003e or right-click on the well path geometry in the 3D view. This operation will create a new well path with a set of well targets.\u003c/p\u003e\n\u003cp\u003eThe full geometry of the new well path is an estimate of the source well path, so the geometry might differ slightly.\u003c/p\u003e\n\u003ch3 id=\"well-target-interaction-operations\"\u003eWell Target Interaction Operations\u003c/h3\u003e\n\u003cp\u003eWhen the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eUser Interaction\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\u003eMouse Move\u003c/td\u003e\n\u003ctd\u003eModification of a single target\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL\u003c/td\u003e\n\u003ctd\u003eModification of all well target on selected well (laterals excluded)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL + SHIFT\u003c/td\u003e\n\u003ctd\u003eModification of all well targets (laterals included)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"starting-well-path-at-a-fixed-position\"\u003eStarting well path at a fixed position\u003c/h3\u003e\n\u003cp\u003eThe toggle \u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e is on by default. If the well path is supposed to start at a predefined location at the sea level, the following procedure can be used:\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\u003eClear \u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eRight-click in the pink well target area, and select \u003cstrong\u003eInsert new Target above\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eIn the \u003cstrong\u003eUTM Reference Point\u003c/strong\u003e field, enter the predefined UTM coordinate (usually, the depth is set to 0.0 for sea level)\u003c/li\u003e\n\u003cli\u003eContinue clicking on geometry in the 3D view to add more well targets and make sure the first well target is defined by [0.00 0.00 0.00] to make sure the first target is located at the predefined UTM reference position\u003c/li\u003e\n\u003c/ol\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e",
+                content:  "\nResInsight 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 imported well path.\nBuilding a multilateral well path\nBuilding a well path 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 should pass (well path targets) When finished placing targets, click on \u0026ldquo;Stop Picking Targets\u0026rdquo; in the property editor Well targets property editor fields:\nUTM Reference Point - Reference point. Defaults to the first target point clicked. Link Reference Point - All wells with this option checked will be moved as a group. Air Gap - Specify Air Gap, i.e. distance from Rotary Kelling Bushing to sea surface. Applies to well path export only. MD at First Target - Defines the measured depth at the first defined well target. Generate Target at Sea Level - Automatically create a target at sea level based on a reasonable well path from reservoir to sea level Well Targets Appearance\nControls the visibility and appearance of spheres at well target locations in addition to 3D interaction handles. The 3D interaction handles will be visible only when the Well Target object is selected, but the spheres will be always be visible if enabled.\nWell Targets\nList of all defined well targets. The editor will have a contrast background color when in picking state.\nRelative Coord - Target position relative to reference point. UTM Coords can be displayed using a checkbox option above the table. MD - Measured depth along the well path. DL in - Dog leg inwards [degrees/30m]. DL out - Dog leg outwards [degrees/30m]. Azi (deg) - Azimuth. Y axis is 0 degrees. If the Azi checkbox is ticked, the user can provide a fixed value for Azimuth. Inc (deg) - Inclination. Z axis is 0 degrees. If the Inc checkbox is ticked, the user can provide a fixed value for Inclination. The other columns defined by the \u0026ldquo;Est\u0026rdquo;-prefix displays the result of dog leg and direction values produced by the well path geometry estimation algorithm.\nA well path defined by well targets 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 Path Duplication To duplicate an existing well path, select Duplicate from the right-click menu of a well path in the Project Tree or right-click on the well path geometry in the 3D view. This operation will create a new well path with a set of well targets.\nThe full geometry of the new well path is an estimate of the source well path, so the geometry might differ slightly.\nWell Target Interaction Operations When the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\nUser Interaction Description Mouse Move Modification of a single target Mouse Move + CTRL Modification of all well target on selected well (laterals excluded) Mouse Move + CTRL + SHIFT Modification of all well targets (laterals included) Starting well path at a fixed position The toggle Generate Target at Sea Level is on by default. If the well path is supposed to start at a predefined location at the sea level, the following procedure can be used:\nRight 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. Clear Generate Target at Sea Level Right-click in the pink well target area, and select Insert new Target above In the UTM Reference Point field, enter the predefined UTM coordinate (usually, the depth is set to 0.0 for sea level) Continue clicking on geometry in the 3D view to add more well targets and make sure the first well target is defined by [0.00 0.00 0.00] to make sure the first target is located at the predefined UTM reference position Well 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 imported well path.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/createmultilateralwellpaths/\"\u003eBuilding a multilateral well path\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"building-a-well-path\"\u003eBuilding a well path\u003c/h3\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 should pass (well path targets)\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\u003eLink Reference Point\u003c/strong\u003e - All wells with this option checked will be moved as a group.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAir Gap\u003c/strong\u003e - Specify Air Gap, i.e. distance from Rotary Kelling Bushing to sea surface. Applies to well path export only.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD at First Target\u003c/strong\u003e - Defines the measured depth at the first defined well target.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e - Automatically create a target at sea level based on a reasonable well path from reservoir to sea level\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eWell Targets Appearance\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eControls the visibility and appearance of spheres at well target locations in addition to 3D interaction handles. The 3D interaction handles will be visible only when the Well Target object is selected, but the spheres will be always be visible if enabled.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eWell Targets\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eList of all defined well targets. The editor will have a contrast background color when in picking state.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eRelative Coord\u003c/strong\u003e - Target position relative to reference point. \u003cstrong\u003eUTM Coords\u003c/strong\u003e can be displayed using a checkbox option above the table.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD\u003c/strong\u003e - Measured depth along the well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL in\u003c/strong\u003e - Dog leg inwards [degrees/30m].\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDL out\u003c/strong\u003e - Dog leg outwards [degrees/30m].\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzi (deg)\u003c/strong\u003e - Azimuth. Y axis is 0 degrees. If the \u003cstrong\u003eAzi\u003c/strong\u003e checkbox is ticked, the user can provide a fixed value for Azimuth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eInc (deg)\u003c/strong\u003e - Inclination. Z axis is 0 degrees. If the \u003cstrong\u003eInc\u003c/strong\u003e checkbox is ticked, the user can provide a fixed value for Inclination.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe other columns defined by the \u0026ldquo;Est\u0026rdquo;-prefix displays the result of dog leg and direction values produced by the well path geometry estimation algorithm.\u003c/p\u003e\n\u003cp\u003eA well path defined by well targets 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-path-duplication\"\u003eWell Path Duplication\u003c/h3\u003e\n\u003cp\u003eTo duplicate an existing well path, select \u003cstrong\u003eDuplicate\u003c/strong\u003e from the right-click menu of a well path in the \u003cstrong\u003eProject Tree\u003c/strong\u003e or right-click on the well path geometry in the 3D view. This operation will create a new well path with a set of well targets.\u003c/p\u003e\n\u003cp\u003eThe full geometry of the new well path is an estimate of the source well path, so the geometry might differ slightly.\u003c/p\u003e\n\u003ch3 id=\"well-target-interaction-operations\"\u003eWell Target Interaction Operations\u003c/h3\u003e\n\u003cp\u003eWhen the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eUser Interaction\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\u003eMouse Move\u003c/td\u003e\n\u003ctd\u003eModification of a single target\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL\u003c/td\u003e\n\u003ctd\u003eModification of all well target on selected well (laterals excluded)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL + SHIFT\u003c/td\u003e\n\u003ctd\u003eModification of all well targets (laterals included)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003ch3 id=\"starting-well-path-at-a-fixed-position\"\u003eStarting well path at a fixed position\u003c/h3\u003e\n\u003cp\u003eThe toggle \u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e is on by default. If the well path is supposed to start at a predefined location at the sea level, the following procedure can be used:\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\u003eClear \u003cstrong\u003eGenerate Target at Sea Level\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eRight-click in the pink well target area, and select \u003cstrong\u003eInsert new Target above\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eIn the \u003cstrong\u003eUTM Reference Point\u003c/strong\u003e field, enter the predefined UTM coordinate (usually, the depth is set to 0.0 for sea level)\u003c/li\u003e\n\u003cli\u003eContinue clicking on geometry in the 3D view to add more well targets and make sure the first well target is defined by [0.00 0.00 0.00] to make sure the first target is located at the predefined UTM reference position\u003c/li\u003e\n\u003c/ol\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- MDRKB          CL            Inc          Azi            TVDMSL         NS                EW               Dogleg      Build        Turn          \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e0.00000        0.00000       91.23218     67.46458       2560.64104     7320830.60875     456093.37763     0.00000     0.00000      0.00000       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e109.69761      109.69761     91.23218     67.46458       2558.28210     7320872.64113     456194.67560     0.00000     0.00000      0.00000       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e383.74602      274.04841     90.01335     94.84447       2555.24550     7320914.37090     456462.87518     3.00000     -0.13343     2.99727       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e518.95310      135.20708     88.73259     106.92696      2556.73062     7320888.88803     456595.39303     2.69569     -0.28418     2.68089       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e597.83872      78.88561      88.73259     106.92696      2558.47547     7320865.92593     456670.84259     0.00000     0.00000      0.00000       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e730.04479      132.20607     90.46303     138.71821      2559.42803     7320795.18191     456780.51358     7.22424     0.39267      7.21402       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1087.97847     357.93368     92.23380     -164.19586     2550.23230     7320460.45997     456856.25443     4.78528     0.14842      -25.38856     \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/wells-and-completions/createnewwellpaths/"
             };
         
@@ -3308,8 +3307,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;Young\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;Young\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e",
+                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:\nMODULUS \u0026ndash; Scaled by 1.0e-9 and shown as \u0026ldquo;Young\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\nstarting 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:     "\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;Young\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e** ELASTIC SETTING FOR EACH ELEMENT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e*Distribution Table, name=RSV_Res-1_Elastic_Table\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eMODULUS, RATIO\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e*Distribution, name=RSV_Res-1_ELASTICS, location=ELEMENT, Table=RSV_Res-1_Elastic_Table\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e** Description: Element-by-Element Elastic properties\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e,     2.\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.210, 11198814808.2538, 0.19041\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.209, 11207002032.1436, 0.19063\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.208, 11222989223.0933, 0.19104\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.207, 11202549454.349, 0.19051\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e** DENSITY SETTING FOR EACH ELEMENT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e*Distribution Table, name=RSV_Res-1_Density_Table\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDensity\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e*Distribution, name=RSV_Res-1_DENSITIES, location=ELEMENT, Table=RSV_Res-1_Density_Table\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e** Description: Element-by-Element Densities\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e,     1.\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.210, 2500\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.209, 2500\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.208, 2500\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRes-1.207, 2500\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/import/elementpropertytable/"
             };
         
@@ -3317,7 +3316,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.  ",
+                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:\nView 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.\nExport 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\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/"
             };
@@ -3326,8 +3325,8 @@ if (!doNotTrack) {
          
             window.store["/calculated-data/gridpropertycalculator/"] = {
                 title:    "Grid Property Calculator",
-                content:  "ResInsight offers a built-in property calculator for grid parameters. The Grid Property Calculator enables arithmetic expressions to be parsed and calculated for visualization purposes.\nMore details on mathematical operations are described in Calculator Expressions\nInvoking the Grid Property Calculator Invoke the the Grid Property Calculator by pressing the calculator icon in the menu bar or by right-clicking Cell Result in Project Tree.\nExample using Grid Property Calculator As shown, the Grid Property Calculator is invoked by right-clicking Cell Result in Project Tree. As seen below, the Grid Property Calculator is per default prefilled with the simple summation Calculation_1 := x + y. This simple summation suffices for exemplifying its use. However, you may change name of the calculation and add additional variables and arithmetic operators in the Expression field.\nIf statements are also supported with the following syntax NEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\n\rThe next step is to define the variables x and y. An easy way to define each variable is to drag and drop properties from Data Sources. See screenshot below for drag and drop of SOIL from Data Sources to the row of variable x in Grid Property Calculator (emphasized in red). Continue with drag and drop of SGAS to define y.\nFinally, press Calculate to perform the actual calculation.\nThe calculated result is accessable via Property Editor as Type Generated Result Property.\nReference Procedure using Grid Property Calculator  Invoke the the Grid Property Calculator by right-clicking Cell Result in Project Tree. Define the expression for calculation by the involved variables and arithmetic operators  Type the name of calculation, required variables and aritmetic operators into Expression Press button Parse Expression to verify the expression and referrals to actual variables   Define each actual variable referred by the expression, either manually or by drag and drop from Data Sources Press Calculate to perform the actual calculation Access the calculated result in Property Editor as Type Generated Result Property  ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers a built-in property calculator for grid parameters. \nThe \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e enables arithmetic expressions to be parsed and calculated for visualization purposes.\u003c/p\u003e\n\u003cp\u003eMore details on mathematical operations are described in \u003ca href=\"/calculated-data/calculatorexpressions/\"\u003eCalculator Expressions\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"invoking-the-grid-property-calculator\"\u003eInvoking the Grid Property Calculator\u003c/h2\u003e\n\u003cp\u003eInvoke the the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e by pressing the calculator icon \u003cimg src=\"https://resinsight.org/images/Calculator.svg\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n in the menu bar or by right-clicking \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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorInvoke.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"example-using-grid-property-calculator\"\u003eExample using Grid Property Calculator\u003c/h2\u003e\n\u003cp\u003eAs shown, the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e is invoked by right-clicking \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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\nAs seen below, the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e is per default prefilled with the simple summation \n\u003cem\u003eCalculation_1 := x + y\u003c/em\u003e. \nThis simple summation suffices for exemplifying its use.\nHowever, you may change name of the calculation and add additional variables and arithmetic operators in the \u003cstrong\u003eExpression\u003c/strong\u003e field.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cstrong\u003eIf\u003c/strong\u003e statements are also supported with the following syntax \u003ccode\u003eNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\u003c/code\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorDefault.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe next step is to define the variables \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e. \nAn easy way to define each variable is to drag and drop properties from \u003cstrong\u003eData Sources\u003c/strong\u003e. See screenshot below for drag and drop of \u003cem\u003eSOIL\u003c/em\u003e from \u003cstrong\u003eData Sources\u003c/strong\u003e to the row of variable \u003cem\u003ex\u003c/em\u003e in \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e (emphasized in red). \nContinue with drag and drop of \u003cem\u003eSGAS\u003c/em\u003e to define \u003cem\u003ey\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorDragDrop.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFinally, press \u003cstrong\u003eCalculate\u003c/strong\u003e to perform the actual calculation.\u003c/p\u003e\n\u003cp\u003eThe calculated result is accessable via \u003cstrong\u003eProperty Editor\u003c/strong\u003e as \u003cstrong\u003eType\u003c/strong\u003e \u003cem\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e\u003c/em\u003e \u003cstrong\u003eResult Property\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorGeneratedProperty.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"reference-procedure-using-grid-property-calculator\"\u003eReference Procedure using Grid Property Calculator\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eInvoke the the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e by right-clicking \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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eDefine the expression for calculation by the involved variables and arithmetic operators\n\u003cul\u003e\n\u003cli\u003eType the name of calculation, required variables and aritmetic operators into \u003cstrong\u003eExpression\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003ePress button \u003cstrong\u003eParse Expression\u003c/strong\u003e to verify the expression and referrals to actual variables\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eDefine each actual variable referred by the expression, either manually or by drag and drop from \u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003ePress \u003cstrong\u003eCalculate\u003c/strong\u003e to perform the actual calculation\u003c/li\u003e\n\u003cli\u003eAccess the calculated result in \u003cstrong\u003eProperty Editor\u003c/strong\u003e as \u003cstrong\u003eType\u003c/strong\u003e \u003cem\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e\u003c/em\u003e \u003cstrong\u003eResult Property\u003c/strong\u003e\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorSolo.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nResInsight offers a built-in property calculator for grid parameters. The Grid Property Calculator enables arithmetic expressions to be parsed and calculated for visualization purposes.\nMore details on mathematical operations are described in Calculator Expressions\nInvoking the Grid Property Calculator Invoke the the Grid Property Calculator by pressing the calculator icon in the menu bar or by right-clicking Cell Result in Project Tree.\nExample using Grid Property Calculator As shown, the Grid Property Calculator is invoked by right-clicking Cell Result in Project Tree. As seen below, the Grid Property Calculator is per default prefilled with the simple summation Calculation_1 := x + y. This simple summation suffices for exemplifying its use. However, you may change name of the calculation and add additional variables and arithmetic operators in the Expression field.\nIf statements are also supported with the following syntax NEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\nThe next step is to define the variables x and y. An easy way to define each variable is to drag and drop properties from Data Sources. See screenshot below for drag and drop of SOIL from Data Sources to the row of variable x in Grid Property Calculator (emphasized in red). Continue with drag and drop of SGAS to define y.\nFinally, press Calculate to perform the actual calculation.\nThe calculated result is accessable via Property Editor as Type Generated Result Property.\nReference Procedure using Grid Property Calculator Invoke the the Grid Property Calculator by right-clicking Cell Result in Project Tree. Define the expression for calculation by the involved variables and arithmetic operators Type the name of calculation, required variables and aritmetic operators into Expression Press button Parse Expression to verify the expression and referrals to actual variables Define each actual variable referred by the expression, either manually or by drag and drop from Data Sources Press Calculate to perform the actual calculation Access the calculated result in Property Editor as Type Generated Result Property ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers a built-in property calculator for grid parameters.\nThe \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e enables arithmetic expressions to be parsed and calculated for visualization purposes.\u003c/p\u003e\n\u003cp\u003eMore details on mathematical operations are described in \u003ca href=\"/calculated-data/calculatorexpressions/\"\u003eCalculator Expressions\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"invoking-the-grid-property-calculator\"\u003eInvoking the Grid Property Calculator\u003c/h2\u003e\n\u003cp\u003eInvoke the the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e by pressing the calculator icon \u003cimg src=\"https://resinsight.org/images/Calculator.svg\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n in the menu bar or by right-clicking\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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorInvoke.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"example-using-grid-property-calculator\"\u003eExample using Grid Property Calculator\u003c/h2\u003e\n\u003cp\u003eAs shown, the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e is invoked by right-clicking\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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\nAs seen below, the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e is per default prefilled with the simple summation\n\u003cem\u003eCalculation_1 := x + y\u003c/em\u003e.\nThis simple summation suffices for exemplifying its use.\nHowever, you may change name of the calculation and add additional variables and arithmetic operators in the \u003cstrong\u003eExpression\u003c/strong\u003e field.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003e\u003cstrong\u003eIf\u003c/strong\u003e statements are also supported with the following syntax \u003ccode\u003eNEW_TRANX := if((TRANX \u0026lt; 0.01), 0.01, TRANX)\u003c/code\u003e\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorDefault.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe next step is to define the variables \u003cem\u003ex\u003c/em\u003e and \u003cem\u003ey\u003c/em\u003e.\nAn easy way to define each variable is to drag and drop properties from \u003cstrong\u003eData Sources\u003c/strong\u003e. See screenshot below for drag and drop of \u003cem\u003eSOIL\u003c/em\u003e from \u003cstrong\u003eData Sources\u003c/strong\u003e to the row of variable \u003cem\u003ex\u003c/em\u003e in \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e (emphasized in red).\nContinue with drag and drop of \u003cem\u003eSGAS\u003c/em\u003e to define \u003cem\u003ey\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorDragDrop.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFinally, press \u003cstrong\u003eCalculate\u003c/strong\u003e to perform the actual calculation.\u003c/p\u003e\n\u003cp\u003eThe calculated result is accessable via \u003cstrong\u003eProperty Editor\u003c/strong\u003e as \u003cstrong\u003eType\u003c/strong\u003e \u003cem\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e\u003c/em\u003e \u003cstrong\u003eResult Property\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorGeneratedProperty.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"reference-procedure-using-grid-property-calculator\"\u003eReference Procedure using Grid Property Calculator\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eInvoke the the \u003cstrong\u003eGrid Property Calculator\u003c/strong\u003e by right-clicking\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 in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003eDefine the expression for calculation by the involved variables and arithmetic operators\n\u003cul\u003e\n\u003cli\u003eType the name of calculation, required variables and aritmetic operators into \u003cstrong\u003eExpression\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003ePress button \u003cstrong\u003eParse Expression\u003c/strong\u003e to verify the expression and referrals to actual variables\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003eDefine each actual variable referred by the expression, either manually or by drag and drop from \u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003ePress \u003cstrong\u003eCalculate\u003c/strong\u003e to perform the actual calculation\u003c/li\u003e\n\u003cli\u003eAccess the calculated result in \u003cstrong\u003eProperty Editor\u003c/strong\u003e as \u003cstrong\u003eType\u003c/strong\u003e \u003cem\u003e\u003cstrong\u003eGenerated\u003c/strong\u003e\u003c/em\u003e \u003cstrong\u003eResult Property\u003c/strong\u003e\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GridPropertyCalculatorSolo.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/calculated-data/gridpropertycalculator/"
             };
         
@@ -3335,7 +3334,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  Summary Plot Manager Summary Plot Manager\n   Operation Shortcut     Display Summary Manager CTRL-K   Append Curves SHIFT-Enter   Replace Curves CTRL-Enter   Create New Plot ALT-Enter    ",
+                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\nCtrl-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 Summary Plot Manager Summary Plot Manager\nOperation Shortcut Display Summary Manager CTRL-K Append Curves SHIFT-Enter Replace Curves CTRL-Enter Create New Plot ALT-Enter ",
                 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\u003ch2 id=\"summary-plot-manager\"\u003eSummary Plot Manager\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/summaryplotmanager/\"\u003eSummary Plot Manager\u003c/a\u003e\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eOperation\u003c/th\u003e\n\u003cth\u003eShortcut\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eDisplay Summary Manager\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eCTRL-K\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eAppend Curves\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eSHIFT-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eReplace Curves\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eCTRL-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eCreate New Plot\u003c/td\u003e\n\u003ctd\u003e\u003cstrong\u003eALT-Enter\u003c/strong\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n",
                 url:      "/misc/keyboardshortcuts/"
             };
@@ -3344,7 +3343,7 @@ 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] (/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    ",
+                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:\nAbbreviation 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:\nMouse 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/"
             };
@@ -3353,8 +3352,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 Data By using the right-click command Import Observed Data on the Observed 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 Data files will be added to Observed Data.  Which summaries that has been detected in a Observed Data file can be read in an Observed 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 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 Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the right-click command \u003cstrong\u003eImport Observed Data\u003c/strong\u003e on the \u003cstrong\u003eObserved 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 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 Data\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhich summaries that has been detected in a Observed Data file can be read in an Observed 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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\u003cp\u003eNormal CSV:\u003c/p\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-txt\" data-lang=\"txt\"\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\u003c/div\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 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\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-txt\" data-lang=\"txt\"\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\u003c/div\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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",
+                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:\nBy selecting the main menu item File -\u0026gt; Import -\u0026gt; Import Observed Data By using the right-click command Import Observed Data on the Observed Data item in the Plot Main Window Project Tree The following file types are supported:\nRSM observed time history data file (*.rsm) Column based (Comma Separated Values, CSV) time history data file (*.csv/*.txt) The imported Observed Data files will be added to Observed Data. Which summaries that has been detected in a Observed Data file can be read in an Observed 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:\nCell 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:\nField - \u0026lt;VECTOR \u0026lsquo;F\u0026hellip;.'\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;.'\u0026gt; Misc - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.'\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 \u0026lsquo;S\u0026hellip;.\u0026rsquo;\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 \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:\u0026rsquo;, \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:\u0026rsquo;. 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 \u0026rsquo;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:\nAt 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 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:     "\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 Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the right-click command \u003cstrong\u003eImport Observed Data\u003c/strong\u003e on the \u003cstrong\u003eObserved 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 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 Data\u003c/strong\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhich summaries that has been detected in a Observed Data file can be read in an Observed 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;.'\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;.\u0026rsquo;\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;.'\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMisc\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;\u0026hellip;.'\u0026gt;\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion\u003c/strong\u003e - \u0026lt;VECTOR \u0026lsquo;R\u0026hellip;.\u0026rsquo;\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..\u0026rsquo;\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;.\u0026rsquo;\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;.\u0026rsquo;\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;.\u0026rsquo;\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;\u0026rsquo;\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;\u0026rsquo;\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;.\u0026rsquo;\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;.\u0026rsquo;\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;\u0026rsquo;\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:\u0026rsquo;, \u0026lsquo;ERR:\u0026rsquo; or \u0026lsquo;ERROR:\u0026rsquo;. 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 \u0026rsquo;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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDATE       ;VECTOR ;VALUE ;ERROR\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2018-04-16 ;FOPT   ;12.5  ;0.45\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2018-04-18 ;FOPT   ;8.6   ;0.31\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003cp\u003eNormal CSV:\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDATE       ;FOPT ;ERR:FOPT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2018-04-16 ;12.5 ;0.45\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2018-04-18 ;8.6  ;0.31\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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 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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1                                                                                                      \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e -------------------------------------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e SUMMARY\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e -------------------------------------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e DATE         FGIRH        FVPT         FWPT         FOPT         FLPT  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e              SM3/DAY      RM3          SM3          SM3          SM3    \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e                           *10**3       *10**3       *10**3       *10**3 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e                                                                         \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e                                                                         \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e -------------------------------------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  6-NOV-1997         0            0            0            0            0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  7-NOV-1997         0     5.749954     0.004548     4.379801     4.384350  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  8-NOV-1997         0     13.76883     0.010841     10.48852     10.49936\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  9-NOV-1997         0     19.38692     0.015243     14.76847     14.78372  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e 10-NOV-1997         0     24.07161     0.018914     18.33751     18.35642\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e 11-NOV-1997         0     28.79427     0.022613     21.93558     21.95819\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eTIME      WWCTH      WGORH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDAYS               SM3/SM3          \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e          A-5HP          A-5HP\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e     1     0.000   0.000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e     2     0.000   0.000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e     3     0.000   0.000\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e----------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- GOR data \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e----------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVECTOR S-122AH-GOR\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eUNITS SM3/SM3\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eORIGIN GORS-122AH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e330.6601\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e257.7500\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e335.9894\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e301.4388\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e260.4193\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e306.0298\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e280.2883\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVECTOR YEARX\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eORIGIN GORS-112AH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eUNITS YEAR\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1999.7902\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1999.8446\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1999.9285\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.0391\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.0800\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.0862\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.1285\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e---comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e----------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- GOR data\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e----------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVECTOR S-211H-GOR\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eUNITS SM3/SM3\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eORIGIN GORS-211H\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e293.8103\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e293.1634\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e304.0000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e334.5932\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e306.4610\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e293.7571\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVECTOR YEARX\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eORIGIN GORS-22H\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eUNITS YEAR\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1999.8255\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.1274\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.2075\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.2367\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.4033\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2000.4966\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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/"
             };
         
@@ -3362,8 +3361,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/"] = {
                 title:    "Plot Main Window",
-                content:  "The Plot Main Window is the main window of ResInsight for 2D graphing and plotting as shown above surrounded by the following docking windows:\n Plots: overview of the various types of plots and their components Property Editor: settings for titles, legends, layout, axes, and appearance Data Sources: searching and sourcing data from case, field, regions, wells, groups, or ensemble Templates: overview, management and use of templates for summary plotting Plot Manager: powerful text-based selection of vectors for summary plotting  Essential actions are presented as controls in the toolbar for ease of use. The following subchapters describe the capabilities, functionality, graphs, and plots in more detail.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003ePlot Main Window\u003c/strong\u003e is the main window of ResInsight for 2D graphing and plotting as shown above surrounded by the following docking windows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlots\u003c/strong\u003e: overview of the various types of plots and their components\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e: settings for titles, legends, layout, axes, and appearance\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e:\nsearching and sourcing data from case, field, regions, wells, groups, or ensemble\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003e\u003cstrong\u003eTemplates\u003c/strong\u003e\u003c/a\u003e:\noverview, management and use of templates for summary plotting\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e:\npowerful text-based selection of vectors for summary plotting\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEssential actions are presented as controls in the toolbar for ease of use. \nThe following subchapters describe the capabilities, functionality, graphs, and plots in more detail.\u003c/p\u003e\n",
+                content:  "\nThe Plot Main Window is the main window of ResInsight for 2D graphing and plotting as shown above surrounded by the following docking windows:\nPlots: overview of the various types of plots and their components Property Editor: settings for titles, legends, layout, axes, and appearance Data Sources: searching and sourcing data from case, field, regions, wells, groups, or ensemble Templates: overview, management and use of templates for summary plotting Plot Manager: powerful text-based selection of vectors for summary plotting Essential actions are presented as controls in the toolbar for ease of use. The following subchapters describe the capabilities, functionality, graphs, and plots in more detail.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotsMain.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003ePlot Main Window\u003c/strong\u003e is the main window of ResInsight for 2D graphing and plotting as shown above surrounded by the following docking windows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlots\u003c/strong\u003e: overview of the various types of plots and their components\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProperty Editor\u003c/strong\u003e: settings for titles, legends, layout, axes, and appearance\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e:\nsearching and sourcing data from case, field, regions, wells, groups, or ensemble\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplottemplate/\"\u003e\u003cstrong\u003eTemplates\u003c/strong\u003e\u003c/a\u003e:\noverview, management and use of templates for summary plotting\u003c/li\u003e\n\u003cli\u003e\u003ca href=\"/plot-window/summaryplotmanager/\"\u003e\u003cstrong\u003ePlot Manager\u003c/strong\u003e\u003c/a\u003e:\npowerful text-based selection of vectors for summary plotting\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEssential actions are presented as controls in the toolbar for ease of use.\nThe following subchapters describe the capabilities, functionality, graphs, and plots in more detail.\u003c/p\u003e\n",
                 url:      "/plot-window/"
             };
         
@@ -3371,8 +3370,8 @@ if (!doNotTrack) {
          
             window.store["/import/pressuredata/"] = {
                 title:    "Pressure/Depth Data",
-                content:  "Import Pressure/Depth Data Importing pressure data to ResInsight may be performed in two different ways:\n By selecting the main menu item File -\u0026gt; Import -\u0026gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree  The imported pressure data can visualized in [RFT Plots]\nPressure/Depth File Format --TVDMSL RFT --\rWELLNAME \u0026#39;OP_1\u0026#39;\rDATE 28-FEB-2000\rPRESSURE DEPTH\rBARSA METRES\r302.88 1605.91\r303.88 1615.91\r304.88 1625.91\r304.38 1635.91\r--\rWELLNAME \u0026#39;OP_2\u0026#39;\rDATE 28-FEB-2000\rPRESSURE DEPTH\rBARSA METRES\r302.88 1600.91\r303.68 1610.91\r303.88 1612.91\r303.99 1620.91\r",
-                html:     "\u003ch2 id=\"import-pressuredepth-data\"\u003eImport Pressure/Depth Data\u003c/h2\u003e\n\u003cp\u003eImporting pressure 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 Pressure Depth Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the right-click command \u003cstrong\u003eImport Pressure Data\u003c/strong\u003e on the \u003cstrong\u003eObserved 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 imported pressure data can visualized in \u003ca href=\"/plot-window/rftplot/\"\u003e[RFT Plots]\u003c/a\u003e\u003c/p\u003e\n\u003ch4 id=\"pressuredepth-file-format\"\u003ePressure/Depth File Format\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-txt\" data-lang=\"txt\"\u003e--TVDMSL \r\nRFT  \r\n--\r\nWELLNAME \u0026#39;OP_1\u0026#39;\r\nDATE 28-FEB-2000\r\nPRESSURE DEPTH\r\nBARSA METRES\r\n302.88 1605.91\r\n303.88 1615.91\r\n304.88 1625.91\r\n304.38 1635.91\r\n--\r\nWELLNAME \u0026#39;OP_2\u0026#39;\r\nDATE 28-FEB-2000\r\nPRESSURE DEPTH\r\nBARSA METRES\r\n302.88 1600.91\r\n303.68 1610.91\r\n303.88 1612.91\r\n303.99 1620.91\r\n\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
+                content:  "Import Pressure/Depth Data Importing pressure data to ResInsight may be performed in two different ways:\nBy selecting the main menu item File -\u0026gt; Import -\u0026gt; Import Pressure Depth Data By using the right-click command Import Pressure Data on the Observed Data item in the Plot Main Window Project Tree The imported pressure data can visualized in [RFT Plots]\nPressure/Depth File Format --TVDMSL RFT -- WELLNAME \u0026#39;OP_1\u0026#39; DATE 28-FEB-2000 PRESSURE DEPTH BARSA METRES 302.88 1605.91 303.88 1615.91 304.88 1625.91 304.38 1635.91 -- WELLNAME \u0026#39;OP_2\u0026#39; DATE 28-FEB-2000 PRESSURE DEPTH BARSA METRES 302.88 1600.91 303.68 1610.91 303.88 1612.91 303.99 1620.91 ",
+                html:     "\u003ch2 id=\"import-pressuredepth-data\"\u003eImport Pressure/Depth Data\u003c/h2\u003e\n\u003cp\u003eImporting pressure 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 Pressure Depth Data\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eBy using the right-click command \u003cstrong\u003eImport Pressure Data\u003c/strong\u003e on the \u003cstrong\u003eObserved 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 imported pressure data can visualized in \u003ca href=\"/plot-window/rftplot/\"\u003e[RFT Plots]\u003c/a\u003e\u003c/p\u003e\n\u003ch4 id=\"pressuredepth-file-format\"\u003ePressure/Depth File Format\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e--TVDMSL \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eRFT  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e--\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELLNAME \u0026#39;OP_1\u0026#39;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDATE 28-FEB-2000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ePRESSURE DEPTH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eBARSA METRES\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e302.88 1605.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e303.88 1615.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e304.88 1625.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e304.38 1635.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e--\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELLNAME \u0026#39;OP_2\u0026#39;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eDATE 28-FEB-2000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ePRESSURE DEPTH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eBARSA METRES\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e302.88 1600.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e303.68 1610.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e303.88 1612.91\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e303.99 1620.91\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/import/pressuredata/"
             };
         
@@ -3380,8 +3379,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 item in Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Color Legend item.\nLegend configuration As shown above, the Legend configuration for cell results allows the following settings:\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 for the legend by selecting from Color Legends Mapping \u0026ndash; Defines the mapping of numerical values to legend colors:  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; Legend with one level per category for formation names and discrete data (e.g. result names ending with NUM)   Range type:  All Timesteps \u0026ndash; use of values for all time steps to find numerical range of legend (unavailable for Flow Diagnostics results) Current Timestep \u0026ndash; use of current (single) time step to find min and max values User Defined Range \u0026ndash; user specified range from minimum to maximum numerical value    Furthermore, the legend may display semi-transparent with a sorrounding box by selecting the Show Box around Legends option of the Preferences dialog.\nLegend configuration for category results The Category type of legend mapping concerns such as formation names and discrete numbered results (e.g. result names with trailing NUM).\nCategory type of legends invoke the Property Editor shown below. Here the default Category Mode Interpolate is shown to color all formations.\nIn the example below, the Category Mode Exclusively Category Colors has been selected to produce a 3D visualization of formations according to the category numbers of Selected Formations Legend. As seen, formations according to the category numbers are displayed in colors while the others are displayed in grey. Please see Color Legends for more information about legends and category numbers.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_configuration.PNG\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cp\u003eThe color mapping of the displayed cell result is controlled by the \u003cstrong\u003eColor Legend\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e. \nThe legend can be shown or hidden by checking or unchecking the box in front of the \u003cstrong\u003eColor Legend\u003c/strong\u003e item.\u003c/p\u003e\n\u003ch2 id=\"legend-configuration\"\u003eLegend configuration\u003c/h2\u003e\n\u003cp\u003eAs shown above, the Legend configuration for cell results allows the following settings:\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 for the legend by selecting from \u003ca href=\"/3d-main-window/colorlegends/\"\u003eColor Legends\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMapping\u003c/strong\u003e \u0026ndash; Defines the mapping of numerical values to legend colors:\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; Legend with one level per category for formation names and discrete data (e.g. result names ending with \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e)\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; use of values for all time steps to find numerical range of legend (unavailable for Flow Diagnostics results)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Timestep\u003c/strong\u003e \u0026ndash; use of current (single) time step to find min and max values\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Range\u003c/strong\u003e \u0026ndash; user specified range from minimum to maximum numerical value\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFurthermore, the legend may display semi-transparent with a sorrounding box by selecting the \u003cstrong\u003eShow Box around Legends\u003c/strong\u003e option of the \n\u003ca href=\"/misc/preferences/\"\u003ePreferences dialog\u003c/a\u003e.\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\u003ch2 id=\"legend-configuration-for-category-results\"\u003eLegend configuration for category results\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eCategory\u003c/strong\u003e type of legend mapping concerns such as formation names and discrete numbered results (e.g. result names with trailing \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e).\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eCategory\u003c/strong\u003e type of legends invoke the Property Editor shown below. \nHere the default \u003cstrong\u003eCategory Mode\u003c/strong\u003e \u003cem\u003eInterpolate\u003c/em\u003e is shown to color all formations.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LegendConfigCategoryInterpolate.png\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the example below, the \u003cstrong\u003eCategory Mode\u003c/strong\u003e \u003cem\u003eExclusively Category Colors\u003c/em\u003e has been selected to produce a 3D visualization of formations according to the category numbers of \u003cem\u003eSelected Formations Legend\u003c/em\u003e. \nAs seen, formations according to the category numbers are displayed in colors while the others are displayed in grey. \nPlease see \u003ca href=\"/3d-main-window/colorlegends/\"\u003eColor Legends\u003c/a\u003e for more information about legends and category numbers.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LegendConfigCategoryExclusive.png\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n",
+                content:  "\nThe color mapping of the displayed cell result is controlled by the Color Legend item in Project Tree. The legend can be shown or hidden by checking or unchecking the box in front of the Color Legend item.\nLegend configuration As shown above, the Legend configuration for cell results allows the following settings:\nNumber 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 for the legend by selecting from Color Legends Mapping \u0026ndash; Defines the mapping of numerical values to legend colors: 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; Legend with one level per category for formation names and discrete data (e.g. result names ending with NUM) Range type: All Timesteps \u0026ndash; use of values for all time steps to find numerical range of legend (unavailable for Flow Diagnostics results) Current Timestep \u0026ndash; use of current (single) time step to find min and max values User Defined Range \u0026ndash; user specified range from minimum to maximum numerical value Furthermore, the legend may display semi-transparent with a sorrounding box by selecting the Show Box around Legends option of the Preferences dialog.\nLegend configuration for category results The Category type of legend mapping concerns such as formation names and discrete numbered results (e.g. result names with trailing NUM).\nCategory type of legends invoke the Property Editor shown below. Here the default Category Mode Interpolate is shown to color all formations.\nIn the example below, the Category Mode Exclusively Category Colors has been selected to produce a 3D visualization of formations according to the category numbers of Selected Formations Legend. As seen, formations according to the category numbers are displayed in colors while the others are displayed in grey. Please see Color Legends for more information about legends and category numbers.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/legend_configuration.PNG\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cp\u003eThe color mapping of the displayed cell result is controlled by the \u003cstrong\u003eColor Legend\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\nThe legend can be shown or hidden by checking or unchecking the box in front of the \u003cstrong\u003eColor Legend\u003c/strong\u003e item.\u003c/p\u003e\n\u003ch2 id=\"legend-configuration\"\u003eLegend configuration\u003c/h2\u003e\n\u003cp\u003eAs shown above, the Legend configuration for cell results allows the following settings:\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 for the legend by selecting from \u003ca href=\"/3d-main-window/colorlegends/\"\u003eColor Legends\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMapping\u003c/strong\u003e \u0026ndash; Defines the mapping of numerical values to legend colors:\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; Legend with one level per category for formation names and discrete data (e.g. result names ending with \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e)\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; use of values for all time steps to find numerical range of legend (unavailable for Flow Diagnostics results)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCurrent Timestep\u003c/strong\u003e \u0026ndash; use of current (single) time step to find min and max values\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser Defined Range\u003c/strong\u003e \u0026ndash; user specified range from minimum to maximum numerical value\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eFurthermore, the legend may display semi-transparent with a sorrounding box by selecting the \u003cstrong\u003eShow Box around Legends\u003c/strong\u003e option of the\n\u003ca href=\"/misc/preferences/\"\u003ePreferences dialog\u003c/a\u003e.\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\u003ch2 id=\"legend-configuration-for-category-results\"\u003eLegend configuration for category results\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eCategory\u003c/strong\u003e type of legend mapping concerns such as formation names and discrete numbered results (e.g. result names with trailing \u003cem\u003e\u003ccode\u003eNUM\u003c/code\u003e\u003c/em\u003e).\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eCategory\u003c/strong\u003e type of legends invoke the Property Editor shown below.\nHere the default \u003cstrong\u003eCategory Mode\u003c/strong\u003e \u003cem\u003eInterpolate\u003c/em\u003e is shown to color all formations.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LegendConfigCategoryInterpolate.png\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the example below, the \u003cstrong\u003eCategory Mode\u003c/strong\u003e \u003cem\u003eExclusively Category Colors\u003c/em\u003e has been selected to produce a 3D visualization of formations according to the category numbers of \u003cem\u003eSelected Formations Legend\u003c/em\u003e.\nAs seen, formations according to the category numbers are displayed in colors while the others are displayed in grey.\nPlease see \u003ca href=\"/3d-main-window/colorlegends/\"\u003eColor Legends\u003c/a\u003e for more information about legends and category numbers.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/LegendConfigCategoryExclusive.png\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/resultcolorlegend/"
             };
         
@@ -3389,7 +3388,7 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/resultinfo/"] = {
                 title:    "Result Info",
-                content:  "The result info window displays text information based on selected geometry in the 3D view. This is information related to IJK cell values, the value of the currently selected result property, and the intersection point for the last mouse click in the 3D view.\nIf you want to show additional properties, activate and select additional properties from Multiple Result Info in the Project Tree. Additional values are displayed in addition to currently selected property.\nCoordinates Select Multiple Result Info in the Project Tree. Coordinates for the selected cell can be displayed by ticking \u0026ldquo;Show Center Coordinates\u0026rdquo; and \u0026ldquo;Show Corner Coordinates\u0026rdquo;\n",
+                content:  "\nThe result info window displays text information based on selected geometry in the 3D view. This is information related to IJK cell values, the value of the currently selected result property, and the intersection point for the last mouse click in the 3D view.\nIf you want to show additional properties, activate and select additional properties from Multiple Result Info in the Project Tree. Additional values are displayed in addition to currently selected property.\nCoordinates Select Multiple Result Info in the Project Tree. Coordinates for the selected cell can be displayed by ticking \u0026ldquo;Show Center Coordinates\u0026rdquo; and \u0026ldquo;Show Corner Coordinates\u0026rdquo;\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/result-info.png\" alt=\"Legend Configuration\"\u003e\u003c/p\u003e\n\u003cp\u003eThe result info window displays text information based on selected geometry in the 3D view. This is information related to IJK cell values, the value of the currently selected result property, and the intersection point for the last mouse click in the 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/multiple-result-info.png\" alt=\"Multiple Result Info\"\u003e\nIf you want to show additional properties, activate and select additional properties from \u003cstrong\u003eMultiple Result Info\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e. Additional values are displayed in addition to currently selected property.\u003c/p\u003e\n\u003ch3 id=\"coordinates\"\u003eCoordinates\u003c/h3\u003e\n\u003cp\u003eSelect Multiple Result Info in the Project Tree. Coordinates for the selected cell can be displayed by ticking \u0026ldquo;Show Center Coordinates\u0026rdquo; and \u0026ldquo;Show Corner Coordinates\u0026rdquo;\u003c/p\u003e\n",
                 url:      "/3d-main-window/resultinfo/"
             };
@@ -3398,7 +3397,7 @@ 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.\nHere highlighted means marked item with different background color, while selected means item(s) having 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-Region \u0026ndash; Select Region to Region related vectors only Group - Select Group related vectors only Well \u0026ndash; Select Well related vectors only Completion \u0026ndash; Select Completion related vectors only Lgr-Completion \u0026ndash; Select Completion in LGR related vectors only Lgr-Well \u0026ndash; Select Well in LGR related vectors only Segment \u0026ndash; Select Segment related vectors only Block \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only Lgr-Block \u0026ndash; Select I, J, K - Block in LGR related vectors only 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",
+                content:  "\nThe 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.\nHere highlighted means marked item with different background color, while selected means item(s) having a ticked check box.\nSelection 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.\nField \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-Region \u0026ndash; Select Region to Region related vectors only Group - Select Group related vectors only Well \u0026ndash; Select Well related vectors only Completion \u0026ndash; Select Completion related vectors only Lgr-Completion \u0026ndash; Select Completion in LGR related vectors only Lgr-Well \u0026ndash; Select Well in LGR related vectors only Segment \u0026ndash; Select Segment related vectors only Block \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only Lgr-Block \u0026ndash; Select I, J, K - Block in LGR related vectors only 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.\nCurves 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\u003eHere \u003cb\u003ehighlighted\u003c/b\u003e means marked item with different background color, while \u003cb\u003eselected\u003c/b\u003e means item(s) having  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\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRegion-Region\u003c/strong\u003e \u0026ndash; Select Region to Region related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup\u003c/strong\u003e - Select Group related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e \u0026ndash; Select Well related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCompletion\u003c/strong\u003e   \u0026ndash; Select Completion related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Completion\u003c/strong\u003e \u0026ndash; Select Completion in LGR related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Well\u003c/strong\u003e \u0026ndash; Select Well in LGR related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSegment\u003c/strong\u003e \u0026ndash; Select Segment related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBlock\u003c/strong\u003e \u0026ndash; Select I, J, K \u0026ndash; Block related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eLgr-Block\u003c/strong\u003e \u0026ndash; Select I, J, K - Block in LGR related vectors only\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCalculated\u003c/strong\u003e \u0026ndash; Select calculated vectors created by the \u003ca href=\"/calculated-data/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 \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\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/"
             };
@@ -3407,8 +3406,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/colorlegends/"] = {
                 title:    "Color Legends",
-                content:  "ResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends. All color legends are available from the Color Legends item in Project Tree.\nStandard Color Legends ResInsight offers an extensive set of built-in color legends as listed by Standard Color Legends. As Standard Color Legends cannot be modified, you must create a Custom Color Legend when needing a legend that is not covered by Standard Color Legends.\nCreate a Custom Color Legend Custom Color Legends are created by right-clicking the Color Legends item in Project Tree to either import a Formation file with color settings or create a new Custom Color Legend.\nIt is also possible to copy a standard legend to create a Custom Color Legend as basis for customization.\nWhen importing a Formation Names description files (*.lyr) with colors, ResInsight automatically creates a color legend and use this as default color legend when visualizing formations in the 3D view.\nCustomizing a Color Legend A newly created Custom Color Legend is initially empty as basis for inclusion of Color Legend Items by right-clicking its entry.\nAs seen below, the right-click menu also allows for deletion of a Color Legend Item. The property editor is used to define each Color Legend Item.\nThe sequence of Color Legend Items can be modified by clicking the arrow symbols seen below.\nThe listed Custom Color Legend is used to form the 3D visualization of formations seen by the top figure of this page. Activating this particular Custom Color Legend is performed by specifying it as Result Color Legend.\nInteger Cell Results When displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying Formation Names. If an integer result is loaded, a custom color legend with names can be used.\nExample workflow\n Select an integer cell result, i.e. FIPNUM Create a custom color legend or create a copy of an existing color legend, name it \u0026ldquo;MyColorLegend\u0026rdquo; Define colors and assign names to colors Use the custom color legend. Note that the color item names are visible in the color legend in the view.  ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollections.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends. \nAll color legends are available from the \u003cstrong\u003eColor Legends\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"standard-color-legends\"\u003eStandard Color Legends\u003c/h2\u003e\n\u003cp\u003eResInsight offers an extensive set of built-in color legends as listed by \u003cem\u003eStandard Color Legends\u003c/em\u003e.\nAs \u003cem\u003eStandard Color Legends\u003c/em\u003e cannot be modified, you must create a \u003cem\u003eCustom Color Legend\u003c/em\u003e when needing a legend that is not covered by \u003cem\u003eStandard Color Legends\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendStandardCollection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-a-custom-color-legend\"\u003eCreate a Custom Color Legend\u003c/h2\u003e\n\u003cp\u003eCustom Color Legends are created by right-clicking the \u003cstrong\u003eColor Legends\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e to either import a \n\u003ca href=\"/3d-main-window/formations/\"\u003eFormation file\u003c/a\u003e with color settings or create a new \u003cem\u003eCustom Color Legend\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCreateCustomColorLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIt is also possible to copy a standard legend to create a \u003cem\u003eCustom Color Legend\u003c/em\u003e as basis for customization.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionCopyStandardLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen importing a \u003ca href=\"/3d-main-window/formations/\"\u003eFormation Names\u003c/a\u003e description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e) with colors, ResInsight automatically creates a color legend and use this as default color legend when visualizing formations in the 3D view.\u003c/p\u003e\n\u003ch2 id=\"customizing-a-color-legend\"\u003eCustomizing a Color Legend\u003c/h2\u003e\n\u003cp\u003eA newly created \u003cem\u003eCustom Color Legend\u003c/em\u003e is initially empty as basis for inclusion of \u003cem\u003eColor Legend Items\u003c/em\u003e by right-clicking its entry.\u003cbr\u003e\nAs seen below, the right-click menu also allows for deletion of a \u003cem\u003eColor Legend Item\u003c/em\u003e.\nThe property editor is used to define each \u003cem\u003eColor Legend Item\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionColorLegendItem.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe sequence of \u003cem\u003eColor Legend Items\u003c/em\u003e can be modified by clicking the arrow symbols seen below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionSequenceColorLegendItem.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe listed \u003cem\u003eCustom Color Legend\u003c/em\u003e is used to form the 3D visualization of formations seen by the top figure of this page.\nActivating this particular \u003cem\u003eCustom Color Legend\u003c/em\u003e is performed by specifying it as \n\u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"integer-cell-results\"\u003eInteger Cell Results\u003c/h2\u003e\n\u003cp\u003eWhen displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying \u003cstrong\u003eFormation Names\u003c/strong\u003e. If an integer result is loaded, a custom color legend with names can be used.\u003c/p\u003e\n\u003cp\u003eExample workflow\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect an integer cell result, i.e. FIPNUM\u003c/li\u003e\n\u003cli\u003eCreate a custom color legend or create a copy of an existing color legend, name it \u003cstrong\u003e\u0026ldquo;MyColorLegend\u0026rdquo;\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eDefine colors and assign names to colors\u003c/li\u003e\n\u003cli\u003eUse the custom color legend. Note that the color item names are visible in the color legend in the view.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CustomCategoryLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends. All color legends are available from the Color Legends item in Project Tree.\nStandard Color Legends ResInsight offers an extensive set of built-in color legends as listed by Standard Color Legends. As Standard Color Legends cannot be modified, you must create a Custom Color Legend when needing a legend that is not covered by Standard Color Legends.\nCreate a Custom Color Legend Custom Color Legends are created by right-clicking the Color Legends item in Project Tree to either import a Formation file with color settings or create a new Custom Color Legend.\nIt is also possible to copy a standard legend to create a Custom Color Legend as basis for customization.\nWhen importing a Formation Names description files (*.lyr) with colors, ResInsight automatically creates a color legend and use this as default color legend when visualizing formations in the 3D view.\nCustomizing a Color Legend A newly created Custom Color Legend is initially empty as basis for inclusion of Color Legend Items by right-clicking its entry.\nAs seen below, the right-click menu also allows for deletion of a Color Legend Item. The property editor is used to define each Color Legend Item.\nThe sequence of Color Legend Items can be modified by clicking the arrow symbols seen below.\nThe listed Custom Color Legend is used to form the 3D visualization of formations seen by the top figure of this page. Activating this particular Custom Color Legend is performed by specifying it as Result Color Legend.\nInteger Cell Results When displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying Formation Names. If an integer result is loaded, a custom color legend with names can be used.\nExample workflow\nSelect an integer cell result, i.e. FIPNUM Create a custom color legend or create a copy of an existing color legend, name it \u0026ldquo;MyColorLegend\u0026rdquo; Define colors and assign names to colors Use the custom color legend. Note that the color item names are visible in the color legend in the view. ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollections.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight offers both a rich set of built-in color legends and functionality for import and customizing color legends.\nAll color legends are available from the \u003cstrong\u003eColor Legends\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"standard-color-legends\"\u003eStandard Color Legends\u003c/h2\u003e\n\u003cp\u003eResInsight offers an extensive set of built-in color legends as listed by \u003cem\u003eStandard Color Legends\u003c/em\u003e.\nAs \u003cem\u003eStandard Color Legends\u003c/em\u003e cannot be modified, you must create a \u003cem\u003eCustom Color Legend\u003c/em\u003e when needing a legend that is not covered by \u003cem\u003eStandard Color Legends\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendStandardCollection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-a-custom-color-legend\"\u003eCreate a Custom Color Legend\u003c/h2\u003e\n\u003cp\u003eCustom Color Legends are created by right-clicking the \u003cstrong\u003eColor Legends\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e to either import a\n\u003ca href=\"/3d-main-window/formations/\"\u003eFormation file\u003c/a\u003e with color settings or create a new \u003cem\u003eCustom Color Legend\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCreateCustomColorLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIt is also possible to copy a standard legend to create a \u003cem\u003eCustom Color Legend\u003c/em\u003e as basis for customization.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionCopyStandardLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen importing a \u003ca href=\"/3d-main-window/formations/\"\u003eFormation Names\u003c/a\u003e description files (\u003cem\u003e\u003ccode\u003e*.lyr\u003c/code\u003e\u003c/em\u003e) with colors, ResInsight automatically creates a color legend and use this as default color legend when visualizing formations in the 3D view.\u003c/p\u003e\n\u003ch2 id=\"customizing-a-color-legend\"\u003eCustomizing a Color Legend\u003c/h2\u003e\n\u003cp\u003eA newly created \u003cem\u003eCustom Color Legend\u003c/em\u003e is initially empty as basis for inclusion of \u003cem\u003eColor Legend Items\u003c/em\u003e by right-clicking its entry.\u003cbr\u003e\nAs seen below, the right-click menu also allows for deletion of a \u003cem\u003eColor Legend Item\u003c/em\u003e.\nThe property editor is used to define each \u003cem\u003eColor Legend Item\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionColorLegendItem.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe sequence of \u003cem\u003eColor Legend Items\u003c/em\u003e can be modified by clicking the arrow symbols seen below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ColorLegendCollectionSequenceColorLegendItem.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe listed \u003cem\u003eCustom Color Legend\u003c/em\u003e is used to form the 3D visualization of formations seen by the top figure of this page.\nActivating this particular \u003cem\u003eCustom Color Legend\u003c/em\u003e is performed by specifying it as\n\u003ca href=\"/3d-main-window/resultcolorlegend/\"\u003eResult Color Legend\u003c/a\u003e.\u003c/p\u003e\n\u003ch2 id=\"integer-cell-results\"\u003eInteger Cell Results\u003c/h2\u003e\n\u003cp\u003eWhen displaying interger cell results, the default color mapping will be set to a category color mapping. This color legend is used when displaying \u003cstrong\u003eFormation Names\u003c/strong\u003e. If an integer result is loaded, a custom color legend with names can be used.\u003c/p\u003e\n\u003cp\u003eExample workflow\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSelect an integer cell result, i.e. FIPNUM\u003c/li\u003e\n\u003cli\u003eCreate a custom color legend or create a copy of an existing color legend, name it \u003cstrong\u003e\u0026ldquo;MyColorLegend\u0026rdquo;\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eDefine colors and assign names to colors\u003c/li\u003e\n\u003cli\u003eUse the custom color legend. Note that the color item names are visible in the color legend in the view.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CustomCategoryLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/colorlegends/"
             };
         
@@ -3416,7 +3415,7 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/createmultilateralwellpaths/"] = {
                 title:    "Create Multilaterals Well Paths",
-                content:  "ResInsight lets the user create additional well path laterals by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export\nBuilding a well path  Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral  A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2. for more laterals  Tie In Control The parent well and the measured depth of the tie in location can be adjusted from the property editor.\nNaming of laterals When a lateral is created, the postfix Y1 is added to the original well path. The first lateral is given the postfix Y2. See the image above for an example of naming.\nWell Target Interaction Activate well targets Activate the well target handles, either by clicking on the well target spheres or by selecting Well Targets in the Project Tree.\nWell Target Interaction Operations When the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\n   User Interaction Description     Mouse Move Modification of a single target   Mouse Move + CTRL Modification of all well target on selected well (laterals excluded)   Mouse Move + CTRL + SHIFT Modification of all well targets (laterals included)    Similar behaviour is available when modifying the well target for the tie-in well target.\nLink Reference Point If you want to move multiple wells at the same time, you can activate Link Reference Point. If the reference point is updated in any of the linked wells, all wells will be updated accordingly. Selection of multiple well, and activation of Link Reference Point ",
+                content:  "\nResInsight lets the user create additional well path laterals by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export\nBuilding a well path Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2. for more laterals Tie In Control The parent well and the measured depth of the tie in location can be adjusted from the property editor.\nNaming of laterals When a lateral is created, the postfix Y1 is added to the original well path. The first lateral is given the postfix Y2. See the image above for an example of naming.\nWell Target Interaction Activate well targets Activate the well target handles, either by clicking on the well target spheres or by selecting Well Targets in the Project Tree.\nWell Target Interaction Operations When the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\nUser Interaction Description Mouse Move Modification of a single target Mouse Move + CTRL Modification of all well target on selected well (laterals excluded) Mouse Move + CTRL + SHIFT Modification of all well targets (laterals included) Similar behaviour is available when modifying the well target for the tie-in well target.\nLink Reference Point If you want to move multiple wells at the same time, you can activate Link Reference Point. If the reference point is updated in any of the linked wells, all wells will be updated accordingly. Selection of multiple well, and activation of Link Reference Point ",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MultiLateralWell_3d_view.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight lets the user create additional well path laterals by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the \u003ca href=\"/export/completionexport/\"\u003eCompletion Export\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"building-a-well-path\"\u003eBuilding a well path\u003c/h2\u003e\n\u003col\u003e\n\u003cli\u003eStart from an existing well path, either imported or \u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003ecreate a new well path\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003eIn the 3D view, right-click on the well path at the depth location for your lateral\n\u003cimg src=\"/images/3d-main-window/MultiLateralWell_create.png\" alt=\"\"\u003e\u003c/li\u003e\n\u003cli\u003eA new well path lateral is created, and click in the 3D scene to define targets for the lateral\u003c/li\u003e\n\u003cli\u003eRepeat from 2. for more laterals\u003c/li\u003e\n\u003c/ol\u003e\n\u003ch2 id=\"tie-in-control\"\u003eTie In Control\u003c/h2\u003e\n\u003cp\u003eThe parent well and the measured depth of the tie in location can be adjusted from the property editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/MultiLateralWell_property_editor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"naming-of-laterals\"\u003eNaming of laterals\u003c/h2\u003e\n\u003cp\u003eWhen a lateral is created, the postfix \u003cstrong\u003eY1\u003c/strong\u003e is added to the original well path. The first lateral is given the postfix \u003cstrong\u003eY2\u003c/strong\u003e. See the image above for an example of naming.\u003c/p\u003e\n\u003ch2 id=\"well-target-interaction\"\u003eWell Target Interaction\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/well-modeling/well-targets-and-handles-2.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"activate-well-targets\"\u003eActivate well targets\u003c/h3\u003e\n\u003cp\u003eActivate the well target handles, either by clicking on the well target spheres or by selecting \u003cstrong\u003eWell Targets\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch3 id=\"well-target-interaction-operations\"\u003eWell Target Interaction Operations\u003c/h3\u003e\n\u003cp\u003eWhen the well target handles are active in the 3D view, the following operations are possible when pressing left mouse button on well target handles:\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eUser Interaction\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\u003eMouse Move\u003c/td\u003e\n\u003ctd\u003eModification of a single target\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL\u003c/td\u003e\n\u003ctd\u003eModification of all well target on selected well (laterals excluded)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eMouse Move + CTRL + SHIFT\u003c/td\u003e\n\u003ctd\u003eModification of all well targets (laterals included)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eSimilar behaviour is available when modifying the well target for the tie-in well target.\u003c/p\u003e\n\u003ch2 id=\"link-reference-point\"\u003eLink Reference Point\u003c/h2\u003e\n\u003cp\u003eIf you want to move multiple wells at the same time, you can activate Link Reference Point. If the reference point is updated in any of the linked wells, all wells will be updated accordingly.\n\u003cimg src=\"/images/well-modeling/well-modeling-link-reference-property-editor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSelection of multiple well, and activation of \u003cstrong\u003eLink Reference Point\u003c/strong\u003e\n\u003cimg src=\"/images/well-modeling/well-modeling-link-reference.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/wells-and-completions/createmultilateralwellpaths/"
             };
@@ -3425,7 +3424,7 @@ if (!doNotTrack) {
          
             window.store["/workflows/"] = {
                 title:    "Workflows",
-                content:  "ResInsight is used in many different ways. This section will describe some selected workflows describing how to solve specific tasks.\n",
+                content:  "\nResInsight is used in many different ways. This section will describe some selected workflows describing how to solve specific tasks.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/getting-started/ResInsightUIMediumSize.png\" alt=\"ResInsight User Interface\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight is used in many different ways. This section will describe some selected workflows describing how to solve specific tasks.\u003c/p\u003e\n",
                 url:      "/workflows/"
             };
@@ -3434,8 +3433,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:     "\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",
+                content:  "\nResInsight 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:\nIn 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",
+                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/"
             };
         
@@ -3443,7 +3442,7 @@ 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",
+                content:  "\nResInsight 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.\nParameter 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.\nParameter 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/"
             };
@@ -3452,7 +3451,7 @@ if (!doNotTrack) {
          
             window.store["/import/appendingadditionalproperties/"] = {
                 title:    "Appending Additional Properties",
-                content:  "A grid model can be imported from several sources, either Eclipse binary/ascii or ROFF binary/ascii. Grid properties in separate files can be imported into any grid type as long as the number of grid cells is matching.\nAppending properties\n From the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list.  Eclipse Grid Models\nROFF Grid Models\n",
+                content:  "A grid model can be imported from several sources, either Eclipse binary/ascii or ROFF binary/ascii. Grid properties in separate files can be imported into any grid type as long as the number of grid cells is matching.\nAppending properties\nFrom the right-click menu of the case or Cell Result, select Add Input Property Select the file with properties The imported data is then available in the Cell Result by activating the Input Property in the Type drop down list. Eclipse Grid Models\nROFF Grid Models\n",
                 html:     "\u003cp\u003eA grid model can be imported from several sources, either \u003cstrong\u003eEclipse\u003c/strong\u003e binary/ascii or \u003cstrong\u003eROFF\u003c/strong\u003e binary/ascii. Grid properties in separate files can be imported into any grid type as long as the number of grid cells is matching.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAppending properties\u003c/strong\u003e\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003eFrom the right-click menu of the case or Cell Result, select \u003cstrong\u003eAdd Input Property\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eSelect the file with properties\u003c/li\u003e\n\u003cli\u003eThe imported data is then available in the \u003cstrong\u003eCell Result\u003c/strong\u003e by activating the \u003cstrong\u003eInput Property\u003c/strong\u003e in the \u003cstrong\u003eType\u003c/strong\u003e drop down list.\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003e\u003cimg src=\"/images/import/additional-properties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/import/eclipsecases/\"\u003eEclipse Grid Models\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/import/roffgridmodels/\"\u003eROFF Grid Models\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/import/appendingadditionalproperties/"
             };
@@ -3461,8 +3460,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. 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 (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:\nTr #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\r-- 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/\rFor 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 -- Well Path B main bore : 0.0569986\rWell Path B 26 45 29 29 OPEN 1* 1* 0.21600 1* 0.00000 1* \u0026#39;Z\u0026#39; -- 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* \u0026#39;Z\u0026#39; /\rWPIMULT\r-- Well Mult I J K Well Path B 0.70133 25 45 29 /\rWell Path B 25.11396 27 41 15 /\r/\rCompletions 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* \u0026#39;Y\u0026#39; /\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* \u0026#39;Y\u0026#39; /\rLGR 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/\rThe 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/\rThe 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 /\rThe 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\u003csub\u003ey\u003c/sub\u003e) and PERMZ (K\u003csub\u003ez\u003c/sub\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\u003csub\u003ey\u003c/sub\u003e and D\u003csub\u003ez\u003c/sub\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\u003csub\u003ex\u003c/sub\u003e), the well radius (r\u003csub\u003ew\u003c/sub\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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     \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*     \u0026#39;Z\u0026#39;  \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*     \u0026#39;Z\u0026#39;  \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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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*   \u0026#39;Y\u0026#39;    /\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*   \u0026#39;Y\u0026#39;    /\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e",
+                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.\nExport 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 (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:\nTr #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 -- 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 -- Well Path B main bore : 0.0569986 Well Path B 26 45 29 29 OPEN 1* 1* 0.21600 1* 0.00000 1* \u0026#39;Z\u0026#39; -- 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* \u0026#39;Z\u0026#39; / 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* \u0026#39;Y\u0026#39; / -- 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* \u0026#39;Y\u0026#39; / 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:\nCreate 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.\nMulti 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:\nName - 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:\nFirst 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 -- 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:\nI, 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\nWell 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 -- 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:     "\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\u003csub\u003ey\u003c/sub\u003e) and PERMZ (K\u003csub\u003ez\u003c/sub\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\u003csub\u003ey\u003c/sub\u003e and D\u003csub\u003ez\u003c/sub\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\u003csub\u003ex\u003c/sub\u003e), the well radius (r\u003csub\u003ew\u003c/sub\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e               Tr   #con       Fcd       Area     KfWf         Kf      Wf       Xf        H       Km\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e[cP.rm3/day/bars]               []       [m2]    [mDm]       [mD]     [m]      [m]      [m]     [mD]\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e----------------------------------------------------------------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e         110.834     24   276.168   9315.748   54.889   3805.029   0.014   61.628   75.580   13.778\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e--\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Pressure Depletion Time step: 01.Feb 2001\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- WBHP Source: WBHP From Summary Case\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- User Defined WBHP: 200\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well    Fracture      Actual WBHP   Min Pressure Drop   Max Pressure Drop   \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e------------------------------------------------------------------------------\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- B-1H    Fracture_01   221.68147     0.04077             45.10402            \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- B-1H    Fracture_02   221.68147     0.00624             36.02608            \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- B-4DH   Fracture_07   200.00000     28.21733            97.34970            \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSPECS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well          Grp   I   J    RefDepth   WellType   \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B   GR    26  45   1230       Oil        \\\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\\\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPDAT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well            I      J      K1     K2     Status     SAT     TR               DIAM     KH     S     Df\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well Path B main bore : 0.0569986\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     26     45     29     29     OPEN       1*      5.699858E-02      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well Path B main bore : 0.230572\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     27     41     15     15     OPEN       1*      2.645858E-01      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSPEC\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well          Grp   I   J    RefDepth   WellType   \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B   GR    26  45   1230       Oil        \\\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\\\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPDAT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well            I      J      K1     K2     Status     SAT     TR     DIAM        KH     S           Df     DIR     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well Path B main bore : 0.0569986\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     26     45     29     29     OPEN       1*      1*     0.21600     1*     0.00000     1*     \u0026#39;Z\u0026#39;  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 0 : 0.0021382\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 1 : 0.00228575\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 0 Lateral: 2 : 0.0126269\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 1 Lateral: 1 : 0.0112929\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0: Sub: 2 Lateral: 0 : 0.00566964\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well Path B main bore : 0.230572\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     27     41     15     15     OPEN       1*      1*     0.21600     1*     0.00000     1*     \u0026#39;Z\u0026#39;  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWPIMULT\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well            Mult         I      J      K      \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     0.70133      25     45     29      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path B     25.11396     27     41     15      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSPECL\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well      Grp   LGR      I   J   RefDepth   WellType   \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   UWell-1   1*    WELLI1   2   9   1*         OIL         /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPDATL\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well      LgrName   I   J   K1   K2   Status   SAT   TR             DIAM      KH   S         Df   DIR   \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- ---- Completions for completion type Perforation ----\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Perforation Completion : MD In: 63.6509 - MD Out: 67.0264 Transmissibility: 6.10676\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   UWell-1   WELLI1    2   9   6    6    OPEN     1*    6.106763E+00   0.21600   1*   0.00000   1*   \u0026#39;Y\u0026#39;    /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Perforation Completion : MD In: 67.0264 - MD Out: 70.402 Transmissibility: 6.10679\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   UWell-1   WELLI1    2   8   6    6    OPEN     1*    6.106791E+00   0.21600   1*   0.00000   1*   \u0026#39;Y\u0026#39;    /\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name            Dep 1          Tlen 1       Vol 1     Len\u0026amp;Dep     PresDrop     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path A     4137.09154     87.00000     1*        ABS         H--           /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- First Seg     Last Seg     Branch Num     Outlet Seg     Length        Depth Change     Diam        Rough       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Main stem\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Segment for sub 0\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   2             2            1              1              13.00000      0.53667          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Laterals\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Diam: MSW - Tubing Radius\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Rough: MSW - Open Hole Roughness Factor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- ICD\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   3             3            2              2              0.10000       0                0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fishbone 0 : Sub index 0 - Lateral 0\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   52            52           27             3              1.70326       -0.57276         0.00960     0.00100      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   53            53           27             52             2.34748       -0.81635         0.00960     0.00100      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name            \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path A      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   28     40     6      27            0.00000          1.70326         /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   28     40     7      27            1.70326          2.34748         /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   28     40     8      27            2.34748          2.96577         /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWSEGVALV\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Well Name       Seg No     Cv          Ac          \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path A     3          1.50000     0.00008      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path A     5          1.50000     0.00008      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   Well Path A     7          1.50000     0.00008      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name      Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   C-1 H     2575.39553     2919.53029     1*        INC         H--           /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fracture Segments\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Diam: MSW - Default Dummy\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Rough: MSW - Default Dummy\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Traversal Fracture 02 connected to Main stem segment 11\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   25            25           2              11             0.01000      0.00000          0.15000     0.00005      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Fractures\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name      \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   C-1 H      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- I      J      K      Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   27     43     1      2             11.27214         11.28214        /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   26     44     1      2             11.27214         11.28214        /\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWELSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name       Dep 1          Tlen 1         Vol 1     Len\u0026amp;Dep     PresDrop     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   B-1 AH     2530.38706     3137.28258     1*        INC         H--           /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- First Seg     Last Seg     Branch Num     Outlet Seg     Length       Depth Change     Diam        Rough       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Main Stem Segments\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   2             2            1              1              16.33624     6.96924          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   3             3            1              2              11.77390     4.75668          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   4             4            1              3              9.49721      3.63598          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   5             5            1              4              6.77104      2.59228          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   6             6            1              5              29.44930     10.10431         0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   7             7            1              6              27.93603     7.96718          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   8             8            1              7              13.95369     3.66086          0.15200     0.00001      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCOMPSEGS\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Name       \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   B-1 AH      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- I      J      K     Branch no     Start Length     End Length     Dir Pen     End Range     Connection Depth     \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   10     24     1     1             3137.28258       3153.61882      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   10     24     2     1             3153.61882       3165.39273      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   9      24     2     1             3165.39273       3174.88994      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   9      25     2     1             3174.88994       3181.66098      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   9      25     3     1             3181.66098       3211.11028      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   9      25     5     1             3239.04631       3253.00000      /\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e/\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/export/completionexport/"
             };
         
@@ -3470,8 +3469,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] (/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",
+                content:  "\nResInsight 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:\nNew 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:\nThe 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/"
             };
         
@@ -3479,7 +3478,7 @@ 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.  ",
+                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:\nCurve 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/"
             };
@@ -3488,7 +3487,7 @@ 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/\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",
+                content:  "A regression tool for QA is build into ResInsight. This tool will do the following:\nScan 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...\rTo create regression tests you need to do the following:\nCreate 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/"
             };
@@ -3498,7 +3497,7 @@ 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:     "\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\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",
+                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\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",
                 url:      "/getting-started/other/releasenotification/"
             };
         
@@ -3506,7 +3505,7 @@ 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 right-click 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 right-click 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",
+                content:  "\nA 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:\nSummary 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 right-click 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 right-click 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 right-click 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 right-click 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/"
             };
@@ -3515,7 +3514,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",
+                content:  "\nThis chaper describes the following aspects of wells and completions:\nhow 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\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/"
             };
@@ -3524,8 +3523,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 subplots and curves with preset appearance and vector names. Having tailored a plot setup, the user can save the setup as a template for later reuse via the Plots window right-click command Save As Plot Template which pops the Export Plot Template dialog seen above.\nA Summary Plot Template can subsequently be used for summary plotting of various data sources. The data sources that can be selected and varied by the user are:\n case(s), ensemble(s), and realization(s) well(s), group(s), and region(s)  When saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions. On the other hand, expand and check the appropriate boxes if you want to persist the specific wells, groups, and/or regions as part of the plot template definition. To exemplify, checking Wells for persistence enables plotting of data for the exact wells of the template in conjunction with any ensemble realization.\nUpon export, ResInsight automatically categorizes the template as an Ensemble Template if the template involves plotting of data for an ensemble. Otherwise the template is categorized as a Summary Case template. Ensemble Templates are listed with the icon while Summary Case templates are listed with the icon in the Templates Window, c.f. below.\nEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by Plotting Preferences. 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.\nTemplate usage Right-clicking in Data Sources and clicking Create Summary Plot from Template will list available summary plot templates for selection. To reapply the previously used template, invoke Create Plot from Last Used Template or simply press Ctrl-T. Both approaces create a summary plot according to template.\nSummary templates made with prior versions are incompatible with ResInsight 2022 due to significant extensions of functionality. Please load summary plots of prior versions via project files or re-establish plots prior to saving templates with ResInsight 2022.\n\rDefault templates Default templates is a powerful feature to automate the generation of summary plots when importing a summary case or ensemble. The basis for automation is the selection of one or more default templates.\nSpecify each default template by right-clicking in the Templates window. Then activate the use of default templates by specifying Use Plot Templates in the Plotting tab of Preferences, c.f. menu option Edit→Preferences.\nAs shown, default templates are listed with a green color in their icon. Both Summary Case templates and Ensemble templates may constitute default templates. When loading a summary case, the default Summary Case templates will be applied automatically, while default Ensemble templates will be applied automatically when loading an ensemble.\nTemplates window As seen above, the Templates window enables management and overview of summary plot templates by directory and offers the following functionality:\n create new plot based on selected template rename template delete template edit template XML file in the Script Editor specified in Preferences specifying default template as described above reload templates in ResInsight in case of directory or file changes on disk  See also menu option Edit→Preferences for managing template folders and template searches.\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 subplots and curves with preset appearance and vector names. \nHaving tailored a plot setup, the user can save the setup as a template for later reuse via the \u003cstrong\u003ePlots\u003c/strong\u003e window right-click command \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e which pops the \u003cstrong\u003eExport Plot Template\u003c/strong\u003e dialog seen above.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateSave.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Summary Plot Template can subsequently be used for summary plotting of various data sources. The data sources that can be selected and varied by the user are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecase(s), ensemble(s), and realization(s)\u003c/li\u003e\n\u003cli\u003ewell(s), group(s), and region(s)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions. \nOn the other hand, expand and check the appropriate boxes if you want to \u003cstrong\u003epersist\u003c/strong\u003e the specific wells, groups, and/or regions as part of the plot template definition.\nTo exemplify, checking \u003cem\u003eWells\u003c/em\u003e for persistence enables plotting of data for the exact wells of the template in conjunction with any ensemble realization.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateSavePersistentObjectNames.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUpon export, ResInsight automatically categorizes the template as an \u003cstrong\u003eEnsemble Template\u003c/strong\u003e if the template involves plotting of data for an ensemble. \nOtherwise the template is categorized as a \u003cstrong\u003eSummary Case\u003c/strong\u003e template.\nEnsemble Templates are listed with the icon \n\u003cimg src=\"https://resinsight.org/images/plot-window/IconEnsembleTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n \nwhile Summary Case templates are listed with the icon\n\u003cimg src=\"https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\nin the \u003ca href=\"/plot-window/summaryplottemplate/#templates-window\"\u003eTemplates Window\u003c/a\u003e, c.f. below.\u003c/p\u003e\n\u003cp\u003eEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003ePlotting Preferences\u003c/strong\u003e\u003c/a\u003e. \nGiven 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\u003eRight-clicking in \u003cstrong\u003eData Sources\u003c/strong\u003e and clicking \u003cstrong\u003eCreate Summary Plot from Template\u003c/strong\u003e will list available summary plot templates for selection. To reapply the previously used template, invoke \u003cstrong\u003eCreate Plot from Last Used Template\u003c/strong\u003e or simply press \u003cstrong\u003eCtrl-T\u003c/strong\u003e. Both approaces create a summary plot according to template.\u003c/p\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\u003eSummary templates made with prior versions are incompatible with ResInsight 2022 due to significant extensions of functionality. Please load summary plots of prior versions via project files or re-establish plots prior to saving templates with ResInsight 2022.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"default-templates\"\u003eDefault templates\u003c/h2\u003e\n\u003cp\u003eDefault templates is a powerful feature to automate the generation of summary plots when importing a summary case or ensemble. The basis for automation is the selection of one or more default templates.\u003c/p\u003e\n\u003cp\u003eSpecify each default template by right-clicking in the \u003cstrong\u003eTemplates\u003c/strong\u003e window.\nThen activate the use of default templates by specifying \u003cstrong\u003eUse Plot Templates\u003c/strong\u003e in the \u003cstrong\u003ePlotting tab\u003c/strong\u003e of Preferences, c.f. menu option \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003eEdit→Preferences\u003c/strong\u003e\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateWindow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs shown, default templates are listed with a green color in their icon.\nBoth \u003cimg src=\"https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eSummary Case templates\u003c/strong\u003e and \u003cimg src=\"https://resinsight.org/images/plot-window/IconEnsembleTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eEnsemble templates\u003c/strong\u003e may constitute default templates. \nWhen loading a summary case, the default Summary Case templates will be applied automatically, while default Ensemble templates will be applied automatically when loading an ensemble.\u003c/p\u003e\n\u003ch2 id=\"templates-window\"\u003eTemplates window\u003c/h2\u003e\n\u003cp\u003eAs seen above, the \u003cstrong\u003eTemplates\u003c/strong\u003e window enables management and overview of summary plot templates by directory and offers the following functionality:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecreate new plot based on selected template\u003c/li\u003e\n\u003cli\u003erename template\u003c/li\u003e\n\u003cli\u003edelete template\u003c/li\u003e\n\u003cli\u003eedit template XML file in the \u003cem\u003eScript Editor\u003c/em\u003e specified in \n\u003ca href=\"/misc/preferences/#scripting\"\u003ePreferences\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003especifying default template as described above\u003c/li\u003e\n\u003cli\u003ereload templates in ResInsight in case of directory or file changes on disk\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee also menu option \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003eEdit→Preferences\u003c/strong\u003e\u003c/a\u003e for managing template folders and template searches.\u003c/p\u003e\n",
+                content:  "\nTemplate creation A summary plot template is defined by a number of subplots and curves with preset appearance and vector names. Having tailored a plot setup, the user can save the setup as a template for later reuse via the Plots window right-click command Save As Plot Template which pops the Export Plot Template dialog seen above.\nA Summary Plot Template can subsequently be used for summary plotting of various data sources. The data sources that can be selected and varied by the user are:\ncase(s), ensemble(s), and realization(s) well(s), group(s), and region(s) When saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions. On the other hand, expand and check the appropriate boxes if you want to persist the specific wells, groups, and/or regions as part of the plot template definition. To exemplify, checking Wells for persistence enables plotting of data for the exact wells of the template in conjunction with any ensemble realization.\nUpon export, ResInsight automatically categorizes the template as an Ensemble Template if the template involves plotting of data for an ensemble. Otherwise the template is categorized as a Summary Case template. Ensemble Templates are listed with the icon while Summary Case templates are listed with the icon in the Templates Window, c.f. below.\nEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by Plotting Preferences. 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.\nTemplate usage Right-clicking in Data Sources and clicking Create Summary Plot from Template will list available summary plot templates for selection. To reapply the previously used template, invoke Create Plot from Last Used Template or simply press Ctrl-T. Both approaces create a summary plot according to template.\nSummary templates made with prior versions are incompatible with ResInsight 2022 due to significant extensions of functionality. Please load summary plots of prior versions via project files or re-establish plots prior to saving templates with ResInsight 2022.\nDefault templates Default templates is a powerful feature to automate the generation of summary plots when importing a summary case or ensemble. The basis for automation is the selection of one or more default templates.\nSpecify each default template by right-clicking in the Templates window. Then activate the use of default templates by specifying Use Plot Templates in the Plotting tab of Preferences, c.f. menu option Edit→Preferences.\nAs shown, default templates are listed with a green color in their icon. Both Summary Case templates and Ensemble templates may constitute default templates. When loading a summary case, the default Summary Case templates will be applied automatically, while default Ensemble templates will be applied automatically when loading an ensemble.\nTemplates window As seen above, the Templates window enables management and overview of summary plot templates by directory and offers the following functionality:\ncreate new plot based on selected template rename template delete template edit template XML file in the Script Editor specified in Preferences specifying default template as described above reload templates in ResInsight in case of directory or file changes on disk See also menu option Edit→Preferences for managing template folders and template searches.\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 subplots and curves with preset appearance and vector names.\nHaving tailored a plot setup, the user can save the setup as a template for later reuse via the \u003cstrong\u003ePlots\u003c/strong\u003e window right-click command \u003cstrong\u003eSave As Plot Template\u003c/strong\u003e which pops the \u003cstrong\u003eExport Plot Template\u003c/strong\u003e dialog seen above.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateSave.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Summary Plot Template can subsequently be used for summary plotting of various data sources. The data sources that can be selected and varied by the user are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecase(s), ensemble(s), and realization(s)\u003c/li\u003e\n\u003cli\u003ewell(s), group(s), and region(s)\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eWhen saving a Summary Plot Template, ResInsight incorporates by default placeholders for using the template in conjunction with various wells, groups, and regions.\nOn the other hand, expand and check the appropriate boxes if you want to \u003cstrong\u003epersist\u003c/strong\u003e the specific wells, groups, and/or regions as part of the plot template definition.\nTo exemplify, checking \u003cem\u003eWells\u003c/em\u003e for persistence enables plotting of data for the exact wells of the template in conjunction with any ensemble realization.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateSavePersistentObjectNames.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUpon export, ResInsight automatically categorizes the template as an \u003cstrong\u003eEnsemble Template\u003c/strong\u003e if the template involves plotting of data for an ensemble.\nOtherwise the template is categorized as a \u003cstrong\u003eSummary Case\u003c/strong\u003e template.\nEnsemble Templates are listed with the icon\n\u003cimg src=\"https://resinsight.org/images/plot-window/IconEnsembleTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\nwhile Summary Case templates are listed with the icon\n\u003cimg src=\"https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\nin the \u003ca href=\"/plot-window/summaryplottemplate/#templates-window\"\u003eTemplates Window\u003c/a\u003e, c.f. below.\u003c/p\u003e\n\u003cp\u003eEach summary plot template is stored in a single file on disk. ResInsight searches a set of directories for template files which are listed and managed by \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003ePlotting Preferences\u003c/strong\u003e\u003c/a\u003e.\nGiven 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\u003eRight-clicking in \u003cstrong\u003eData Sources\u003c/strong\u003e and clicking \u003cstrong\u003eCreate Summary Plot from Template\u003c/strong\u003e will list available summary plot templates for selection. To reapply the previously used template, invoke \u003cstrong\u003eCreate Plot from Last Used Template\u003c/strong\u003e or simply press \u003cstrong\u003eCtrl-T\u003c/strong\u003e. Both approaces create a summary plot according to template.\u003c/p\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\u003eSummary templates made with prior versions are incompatible with ResInsight 2022 due to significant extensions of functionality. Please load summary plots of prior versions via project files or re-establish plots prior to saving templates with ResInsight 2022.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"default-templates\"\u003eDefault templates\u003c/h2\u003e\n\u003cp\u003eDefault templates is a powerful feature to automate the generation of summary plots when importing a summary case or ensemble. The basis for automation is the selection of one or more default templates.\u003c/p\u003e\n\u003cp\u003eSpecify each default template by right-clicking in the \u003cstrong\u003eTemplates\u003c/strong\u003e window.\nThen activate the use of default templates by specifying \u003cstrong\u003eUse Plot Templates\u003c/strong\u003e in the \u003cstrong\u003ePlotting tab\u003c/strong\u003e of Preferences, c.f. menu option \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003eEdit→Preferences\u003c/strong\u003e\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/SummaryPlotTemplateWindow.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs shown, default templates are listed with a green color in their icon.\nBoth \u003cimg src=\"https://resinsight.org/images/plot-window/IconSummaryCaseTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eSummary Case templates\u003c/strong\u003e and \u003cimg src=\"https://resinsight.org/images/plot-window/IconEnsembleTemplate.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n\u003cstrong\u003eEnsemble templates\u003c/strong\u003e may constitute default templates.\nWhen loading a summary case, the default Summary Case templates will be applied automatically, while default Ensemble templates will be applied automatically when loading an ensemble.\u003c/p\u003e\n\u003ch2 id=\"templates-window\"\u003eTemplates window\u003c/h2\u003e\n\u003cp\u003eAs seen above, the \u003cstrong\u003eTemplates\u003c/strong\u003e window enables management and overview of summary plot templates by directory and offers the following functionality:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ecreate new plot based on selected template\u003c/li\u003e\n\u003cli\u003erename template\u003c/li\u003e\n\u003cli\u003edelete template\u003c/li\u003e\n\u003cli\u003eedit template XML file in the \u003cem\u003eScript Editor\u003c/em\u003e specified in\n\u003ca href=\"/misc/preferences/#scripting\"\u003ePreferences\u003c/a\u003e\u003c/li\u003e\n\u003cli\u003especifying default template as described above\u003c/li\u003e\n\u003cli\u003ereload templates in ResInsight in case of directory or file changes on disk\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSee also menu option \u003ca href=\"/misc/preferences/#plotting\"\u003e\u003cstrong\u003eEdit→Preferences\u003c/strong\u003e\u003c/a\u003e for managing template folders and template searches.\u003c/p\u003e\n",
                 url:      "/plot-window/summaryplottemplate/"
             };
         
@@ -3533,7 +3532,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/summarytables/"] = {
                 title:    "Summary Tables",
-                content:  "Summary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format. It shows summary data of vectors for the selectable categories: Well, Group or Region.\nSummary tables are displayed with the summary vectors on each row, and time step values according to selected Date Resampling in each column - as shown with resampling Year in the screenshot above.\nThe table can be formatted by use of the Property Editor, shown below. Columns are controlled by the selection of resampling, and rows are controlled by selected Threshold value and Exclude Rows.\nCreating Summary Tables Using Data Sources to create Summary Tables Having imported Eclipse Summary Data, Data Sources provides an easy approach to create Summary Tables:\n Search or navigate Data Sources to find the desired source and vector Right-click selected vector and select New Summary Table  Duplicate Summary Table When a Summary Table is created and configured, the table can be duplicated by Right-click on the respective table in the Project Tree and selecting Duplicate Summary Table. This creates a new Summary Table with the same configuration, and a new table can be created with minor adjustments in the Property Editor.\nCreate default Summary Table A default Summary Table can be created by Right-click on the Summary Table collection and select New Summary Table. This creates a new default Summary Table, which can be configured by selections in the Property Editor\nEditing Summary Table The settings of each table is listed in the Property Editor for a Summary Table. By selecting a Summary Table, its properties are displayed.\nThe main controls for a Summary Table is listed below:\n Category - Select which category to select vectors from: Well, Group or Region. Vector - Selection of vector type available for selected category in case. Date Resampling - Select date resampling to control number data values for each vector - i.e. number of columns. The resampling is ensuring equal time stamps across all summary vectors in table. Threshold - Set threshold value for summary vector. Exclude row (vector) if each time stamp value are below selected threshold. Exclude Rows - Select which rows (vectors) to exclude from the table.  ",
+                content:  "\nSummary Tables are a display of curve data based on Eclipse Summary Data as a color map in table format. It shows summary data of vectors for the selectable categories: Well, Group or Region.\nSummary tables are displayed with the summary vectors on each row, and time step values according to selected Date Resampling in each column - as shown with resampling Year in the screenshot above.\nThe table can be formatted by use of the Property Editor, shown below. Columns are controlled by the selection of resampling, and rows are controlled by selected Threshold value and Exclude Rows.\nCreating Summary Tables Using Data Sources to create Summary Tables Having imported Eclipse Summary Data, Data Sources provides an easy approach to create Summary Tables:\nSearch or navigate Data Sources to find the desired source and vector Right-click selected vector and select New Summary Table Duplicate Summary Table When a Summary Table is created and configured, the table can be duplicated by Right-click on the respective table in the Project Tree and selecting Duplicate Summary Table. This creates a new Summary Table with the same configuration, and a new table can be created with minor adjustments in the Property Editor.\nCreate default Summary Table A default Summary Table can be created by Right-click on the Summary Table collection and select New Summary Table. This creates a new default Summary Table, which can be configured by selections in the Property Editor\nEditing Summary Table The settings of each table is listed in the Property Editor for a Summary Table. By selecting a Summary Table, its properties are displayed.\nThe main controls for a Summary Table is listed below:\nCategory - Select which category to select vectors from: Well, Group or Region. Vector - Selection of vector type available for selected category in case. Date Resampling - Select date resampling to control number data values for each vector - i.e. number of columns. The resampling is ensuring equal time stamps across all summary vectors in table. Threshold - Set threshold value for summary vector. Exclude row (vector) if each time stamp value are below selected threshold. Exclude Rows - Select which rows (vectors) to exclude from the table. ",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_WOPR.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSummary Tables\u003c/strong\u003e are a display of curve data based on \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e as a color map in table format. It shows summary data of vectors for the selectable categories: \u003cem\u003eWell\u003c/em\u003e,  \u003cem\u003eGroup\u003c/em\u003e or \u003cem\u003eRegion\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eSummary tables are displayed with the summary vectors on each row, and time step values according to selected \u003cem\u003eDate Resampling\u003c/em\u003e in each column - as shown with resampling \u003cem\u003eYear\u003c/em\u003e in the screenshot above.\u003c/p\u003e\n\u003cp\u003eThe table can be formatted by use of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, shown below. Columns are controlled by the selection of resampling, and rows are controlled by selected \u003cem\u003eThreshold\u003c/em\u003e value and \u003cem\u003eExclude Rows\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"creating-summary-tables\"\u003eCreating Summary Tables\u003c/h2\u003e\n\u003ch3 id=\"using-data-sources-to-create-summary-tables\"\u003eUsing Data Sources to create Summary Tables\u003c/h3\u003e\n\u003cp\u003eHaving imported \u003ca href=\"/import/eclipsesummarydata/\"\u003eEclipse Summary Data\u003c/a\u003e, \u003ca href=\"/plot-window/summaryplotdatasources/\"\u003e\u003cstrong\u003eData Sources\u003c/strong\u003e\u003c/a\u003e provides an easy approach to create Summary Tables:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSearch or navigate \u003cstrong\u003eData Sources\u003c/strong\u003e to find the desired source and vector\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eRight-click\u003c/em\u003e selected vector and select \u003cstrong\u003eNew Summary Table\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_CreateNewSummaryTable.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"duplicate-summary-table\"\u003eDuplicate Summary Table\u003c/h3\u003e\n\u003cp\u003eWhen a Summary Table is created and configured, the table can be duplicated by \u003cem\u003eRight-click\u003c/em\u003e on the respective table in the \u003ca href=\"/getting-started/projecttree/\"\u003eProject Tree\u003c/a\u003e and selecting \u003cstrong\u003eDuplicate Summary Table\u003c/strong\u003e. This creates a new Summary Table with the same configuration, and a new table can be created with minor adjustments in the \u003cem\u003eProperty Editor\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_DuplicateSummaryTable.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"create-default-summary-table\"\u003eCreate default Summary Table\u003c/h3\u003e\n\u003cp\u003eA default Summary Table can be created by \u003cem\u003eRight-click\u003c/em\u003e on the Summary Table collection and select \u003cstrong\u003eNew Summary Table\u003c/strong\u003e. This creates a new default Summary Table, which can be configured by selections in the \u003cem\u003eProperty Editor\u003c/em\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_CreateNewSummaryTable2.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"editing-summary-table\"\u003eEditing Summary Table\u003c/h2\u003e\n\u003cp\u003eThe settings of each table is listed in the \u003cem\u003eProperty Editor\u003c/em\u003e for a Summary Table. By selecting a Summary Table, its properties are displayed.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Summary_Table_PropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe main controls for a Summary Table is listed below:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCategory\u003c/strong\u003e - Select which category to select vectors from: \u003cem\u003eWell\u003c/em\u003e, \u003cem\u003eGroup\u003c/em\u003e or \u003cem\u003eRegion\u003c/em\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eVector\u003c/strong\u003e - Selection of vector type available for selected category in case.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate Resampling\u003c/strong\u003e - Select date resampling to control number data values for each vector - i.e. number of columns. The resampling is ensuring equal time stamps across all summary vectors in table.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThreshold\u003c/strong\u003e - Set threshold value for summary vector. Exclude row (vector) if each time stamp value are below selected threshold.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Rows\u003c/strong\u003e - Select which rows (vectors) to exclude from the table.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/summarytables/"
             };
@@ -3542,7 +3541,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/multiplots/"] = {
                 title:    "Multi Plots",
-                content:  "A Multi Plot allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\nMulti Plot Usage A new Multi Plot can be created by selecting a set of plots and from the right-click menu select Create Multi Plot from Selected Plots\nThe currenly supported types of plots to be part of a Multi Plot are:\n Summary Plots Ensemble Plots Grid Cross Plots Saturation Pressure Plots Phase Distribution Plots  Properties The main page layout is controlled from Preferences The property editor of a multi plot allows further customization\nThe number of columns can also be controlled from the Multi Plot toolbar. Export to PDF Export to PDF is available from the right-click menu of a Multi Plot, or directly from the PDF export button in the toolbar.\n",
+                content:  "\nA Multi Plot allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\nMulti Plot Usage A new Multi Plot can be created by selecting a set of plots and from the right-click menu select Create Multi Plot from Selected Plots\nThe currenly supported types of plots to be part of a Multi Plot are:\nSummary Plots Ensemble Plots Grid Cross Plots Saturation Pressure Plots Phase Distribution Plots Properties The main page layout is controlled from Preferences The property editor of a multi plot allows further customization\nThe number of columns can also be controlled from the Multi Plot toolbar. Export to PDF Export to PDF is available from the right-click menu of a Multi Plot, or directly from the PDF export button in the toolbar.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/MultiPlotHeading.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Multi Plot allows the user to combine multiple plots in a grid layout. Plots from different types can be combined. This plot type is tailored for export to PDF.\u003c/p\u003e\n\u003ch2 id=\"multi-plot-usage\"\u003eMulti Plot Usage\u003c/h2\u003e\n\u003cp\u003eA new Multi Plot can be created by selecting a set of plots and from the right-click menu select \u003cstrong\u003eCreate Multi Plot from Selected Plots\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/MultiPlotCreate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe currenly supported types of plots to be part of a \u003cstrong\u003eMulti Plot\u003c/strong\u003e are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eSummary Plots\u003c/li\u003e\n\u003cli\u003eEnsemble Plots\u003c/li\u003e\n\u003cli\u003eGrid Cross Plots\u003c/li\u003e\n\u003cli\u003eSaturation Pressure Plots\u003c/li\u003e\n\u003cli\u003ePhase Distribution Plots\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"properties\"\u003eProperties\u003c/h2\u003e\n\u003cp\u003eThe main page layout is controlled from \u003cstrong\u003ePreferences\u003c/strong\u003e\n\u003cimg src=\"/images/misc/PreferencesPlotting.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe property editor of a multi plot allows further customization\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/MultiPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe number of columns can also be controlled from the \u003cstrong\u003eMulti Plot\u003c/strong\u003e toolbar.\n\u003cimg src=\"/images/plot-window/MultiPlotToolbar.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"export-to-pdf\"\u003eExport to PDF\u003c/h2\u003e\n\u003cp\u003eExport to PDF is available from the right-click menu of a Multi Plot, or directly from the PDF export button in the toolbar.\u003c/p\u003e\n",
                 url:      "/plot-window/multiplots/"
             };
@@ -3551,8 +3550,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 occurred 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 Length(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=\"/calculated-data/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=\"/calculated-data/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 occurred 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\u003eLength(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 \u003ccode\u003e*.dev*\u003c/code\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\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\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",
+                content:  "\nThree 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.\nVisualization 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:\nGeometry 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 occurred at.\nAfter creating the perforation interval, the following properties of the perforation can be set in the property editor:\nStart 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.\nMulti 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.\nNon-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:\nICD - 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;\rThis line is ignored for now. The numbers are interpreted to be in the units present in the case.\nIn 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;\rdate \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\rFishbones 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.\nFishbone 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\u0026quot; main bore.\nAppearance 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 Length(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.\nFractures 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.\nColors \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:\nInertial 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.\nName \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.\nName \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.\nCase \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=\"/calculated-data/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=\"/calculated-data/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 occurred 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\u0026quot; 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\u003eLength(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 \u003ccode\u003e\u003cem\u003e.dev\u003c/em\u003e\u003c/code\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\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\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/"
             };
         
@@ -3560,8 +3559,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/ensemblefracturestatistics/"] = {
                 title:    "Ensemble Fracture Statistics",
-                content:  "Importing Ensemble Fracture Statistics Right-click on Completion Templates \u0026gt; Ensemble Fracture Statistics in the Project Tree and select the Import StimPlan Fracture Recursively option. Then select the StimPlan fracture Xml files to be part of the ensemble.\nAfter importing the Property Panel of the Ensemble Fracture Statistics item has these options:\n Name \u0026ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures \u0026ndash; Toggle to remove zero width fractures from the statistics. Mesh Alignment \u0026ndash; Specifies how to align the mesh.  Mesh Depth \u0026ndash; Use the raw mesh depths from file without adjustment. Perforation Depth \u0026ndash; Adjusts the mesh location to have the perforation at the same location when computing the statistics.   Mesh Type \u0026ndash; Specifies the meshing strategy. See details below. Statistics Type \u0026ndash; The statistics to compute.  Mesh Types The imported StimPlan fractures are stacked on top of each, and a statistics mesh is created. The statistics mesh covers the extents of all the individual meshes in the ensemble.\nAdaptive Mesh The adaptive mesh tries to optimize the horizontal depth spacing to have coarse sampling where the source meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of the individual meshes into fixed bins, and then scaling the vertical size of each layer according to their mean size.\n Mean Type \u0026ndash; The mean calculation used to scale the layer thickness.  Harmonic \u0026ndash; See Harmonic mean for details. Arithmetic \u0026ndash; Average. See Arithmetic Mean for details. Geometric \u0026ndash; See Geometric Mean for details. Minimum \u0026ndash; Use the minimum thickness.   Number of Layers \u0026ndash; Specifies the number of layers to create.  Average \u0026ndash; Use the average number of layers of the individual fractures of the ensemble. Minimum \u0026ndash; Use the minimum number of layers of the individual fractures of the ensemble. Maximum \u0026ndash; Use the maximum number of layers of the individual fractures of the ensemble. User-Defined \u0026ndash; The user specifies the number of layers.    The mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\nUniform Mesh The uniform mesh has cells of a equal size. The minimum and maximum extents of all the meshes in both directions is found, and the interval is divided into equal cells.\n X \u0026ndash; The number of cells in lateral direction. Y \u0026ndash; The number of cells in depth direction.  Naive Mesh The naive method produces a mesh where every depth in all the individual fractures of the ensemble is present.\nThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\nStatistics Mesh Computation The statistics mesh samples each individual fracture of the ensemble in each cell center. The value of the cell containing the statistics mesh cell center is used. Invalid values or empty cells are ignored. The values at each cell center are gathered, and the chosen statistics (e.g. P10 and Mean) is computed per cell.\nThe statistics meshes are written to file in a StimPlan compatible XML file, and is imported into Fracture Templates in the Project Tree.\nStatistics Table The statistics table contains overall statistics on key properties of the fractures.\n Height \u0026ndash; Longest aggregate height of conductive cells. Area \u0026ndash; Area of the conductive cells of the fracture. Width \u0026ndash; Width of conductive cells weighted by their area. Halflength (Xf) \u0026ndash; Length of the fracture is area divided by height. Xf is half of the length. Conductivity (KfWf) \u0026ndash; Conductivity weighted by area. Permeability \u0026ndash; Permeability (i.e. conductivity divided by width) weighted by area. Formation Dip \u0026ndash; Formation dip as reported in the Xml file.  ",
-                html:     "\u003ch2 id=\"importing-ensemble-fracture-statistics\"\u003eImporting Ensemble Fracture Statistics\u003c/h2\u003e\n\u003cp\u003eRight-click on \u003cstrong\u003eCompletion Templates \u0026gt; Ensemble Fracture Statistics\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e and select the \u003cstrong\u003eImport StimPlan Fracture Recursively\u003c/strong\u003e option. Then select the StimPlan fracture Xml files to be part of the ensemble.\u003c/p\u003e\n\u003cp\u003eAfter importing the \u003cstrong\u003eProperty Panel\u003c/strong\u003e of the \u003cstrong\u003eEnsemble Fracture Statistics\u003c/strong\u003e item has these options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Name of the ensemble fracture statistics.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Zero Width Fractures\u003c/strong\u003e \u0026ndash; Toggle to remove zero width fractures from the statistics.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Alignment\u003c/strong\u003e \u0026ndash; Specifies how to align the mesh.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Depth\u003c/strong\u003e \u0026ndash; Use the raw mesh depths from file without adjustment.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Depth\u003c/strong\u003e \u0026ndash; Adjusts the mesh location to have the perforation at the same location when computing the statistics.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Type\u003c/strong\u003e \u0026ndash; Specifies the meshing strategy. See details below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Type\u003c/strong\u003e \u0026ndash; The statistics to compute.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"mesh-types\"\u003eMesh Types\u003c/h2\u003e\n\u003cp\u003eThe imported StimPlan fractures are stacked on top of each, and a statistics mesh is created. The statistics mesh covers the extents of\nall the individual meshes in the ensemble.\u003c/p\u003e\n\u003ch3 id=\"adaptive-mesh\"\u003eAdaptive Mesh\u003c/h3\u003e\n\u003cp\u003eThe adaptive mesh tries to optimize the horizontal depth spacing to have coarse sampling where the\nsource meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of \nthe individual meshes into fixed bins, and then scaling the vertical size of each layer according to their mean size.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMean Type\u003c/strong\u003e \u0026ndash; The mean calculation used to scale the layer thickness.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHarmonic\u003c/strong\u003e \u0026ndash; See \u003ca href=\"https://en.wikipedia.org/wiki/Harmonic_mean\"\u003eHarmonic mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArithmetic\u003c/strong\u003e \u0026ndash; Average. See \u003ca href=\"https://en.wikipedia.org/wiki/Arithmetic_mean\"\u003eArithmetic Mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometric\u003c/strong\u003e \u0026ndash; See \u003ca href=\"https://en.wikipedia.org/wiki/Geometric_mean\"\u003eGeometric Mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum\u003c/strong\u003e \u0026ndash; Use the minimum thickness.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Layers\u003c/strong\u003e \u0026ndash; Specifies the number of layers to create.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAverage\u003c/strong\u003e \u0026ndash; Use the average number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum\u003c/strong\u003e \u0026ndash; Use the minimum number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMaximum\u003c/strong\u003e \u0026ndash; Use the maximum number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser-Defined\u003c/strong\u003e \u0026ndash; The user specifies the number of layers.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\u003c/p\u003e\n\u003ch3 id=\"uniform-mesh\"\u003eUniform Mesh\u003c/h3\u003e\n\u003cp\u003eThe uniform mesh has cells of a equal size. The minimum and maximum extents of all the meshes in both directions is found, and the interval is divided into equal cells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eX\u003c/strong\u003e \u0026ndash; The number of cells in lateral direction.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eY\u003c/strong\u003e \u0026ndash; The number of cells in depth direction.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"naive-mesh\"\u003eNaive Mesh\u003c/h3\u003e\n\u003cp\u003eThe naive method produces a mesh where every depth in all the individual fractures of the ensemble is present.\u003c/p\u003e\n\u003cp\u003eThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\u003c/p\u003e\n\u003ch2 id=\"statistics-mesh-computation\"\u003eStatistics Mesh Computation\u003c/h2\u003e\n\u003cp\u003eThe statistics mesh samples each individual fracture of the ensemble in each cell center. The value of the cell containing the\nstatistics mesh cell center is used. Invalid values or empty cells are ignored. The values at each cell center are gathered, and\nthe chosen statistics (e.g. P10 and Mean) is computed per cell.\u003c/p\u003e\n\u003cp\u003eThe statistics meshes are written to file in a StimPlan compatible XML file, and is imported into \u003cstrong\u003eFracture Templates\u003c/strong\u003e in the \n\u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"statistics-table\"\u003eStatistics Table\u003c/h2\u003e\n\u003cp\u003eThe statistics table contains overall statistics on key properties of the fractures.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHeight\u003c/strong\u003e \u0026ndash; Longest aggregate height of conductive cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArea\u003c/strong\u003e \u0026ndash; Area of the conductive cells of the fracture.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e \u0026ndash; Width of conductive cells weighted by their area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHalflength (Xf)\u003c/strong\u003e \u0026ndash; Length of the fracture is area divided by height. Xf is half of the length.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity (KfWf)\u003c/strong\u003e \u0026ndash; Conductivity weighted by area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability\u003c/strong\u003e \u0026ndash; Permeability (i.e. conductivity divided by width) weighted by area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Dip\u003c/strong\u003e \u0026ndash; Formation dip as reported in the Xml file.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "Importing Ensemble Fracture Statistics Right-click on Completion Templates \u0026gt; Ensemble Fracture Statistics in the Project Tree and select the Import StimPlan Fracture Recursively option. Then select the StimPlan fracture Xml files to be part of the ensemble.\nAfter importing the Property Panel of the Ensemble Fracture Statistics item has these options:\nName \u0026ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures \u0026ndash; Toggle to remove zero width fractures from the statistics. Mesh Alignment \u0026ndash; Specifies how to align the mesh. Mesh Depth \u0026ndash; Use the raw mesh depths from file without adjustment. Perforation Depth \u0026ndash; Adjusts the mesh location to have the perforation at the same location when computing the statistics. Mesh Type \u0026ndash; Specifies the meshing strategy. See details below. Statistics Type \u0026ndash; The statistics to compute. Mesh Types The imported StimPlan fractures are stacked on top of each, and a statistics mesh is created. The statistics mesh covers the extents of all the individual meshes in the ensemble.\nAdaptive Mesh The adaptive mesh tries to optimize the horizontal depth spacing to have coarse sampling where the source meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of the individual meshes into fixed bins, and then scaling the vertical size of each layer according to their mean size.\nMean Type \u0026ndash; The mean calculation used to scale the layer thickness. Harmonic \u0026ndash; See Harmonic mean for details. Arithmetic \u0026ndash; Average. See Arithmetic Mean for details. Geometric \u0026ndash; See Geometric Mean for details. Minimum \u0026ndash; Use the minimum thickness. Number of Layers \u0026ndash; Specifies the number of layers to create. Average \u0026ndash; Use the average number of layers of the individual fractures of the ensemble. Minimum \u0026ndash; Use the minimum number of layers of the individual fractures of the ensemble. Maximum \u0026ndash; Use the maximum number of layers of the individual fractures of the ensemble. User-Defined \u0026ndash; The user specifies the number of layers. The mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\nUniform Mesh The uniform mesh has cells of a equal size. The minimum and maximum extents of all the meshes in both directions is found, and the interval is divided into equal cells.\nX \u0026ndash; The number of cells in lateral direction. Y \u0026ndash; The number of cells in depth direction. Naive Mesh The naive method produces a mesh where every depth in all the individual fractures of the ensemble is present.\nThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\nStatistics Mesh Computation The statistics mesh samples each individual fracture of the ensemble in each cell center. The value of the cell containing the statistics mesh cell center is used. Invalid values or empty cells are ignored. The values at each cell center are gathered, and the chosen statistics (e.g. P10 and Mean) is computed per cell.\nThe statistics meshes are written to file in a StimPlan compatible XML file, and is imported into Fracture Templates in the Project Tree.\nStatistics Table The statistics table contains overall statistics on key properties of the fractures.\nHeight \u0026ndash; Longest aggregate height of conductive cells. Area \u0026ndash; Area of the conductive cells of the fracture. Width \u0026ndash; Width of conductive cells weighted by their area. Halflength (Xf) \u0026ndash; Length of the fracture is area divided by height. Xf is half of the length. Conductivity (KfWf) \u0026ndash; Conductivity weighted by area. Permeability \u0026ndash; Permeability (i.e. conductivity divided by width) weighted by area. Formation Dip \u0026ndash; Formation dip as reported in the Xml file. ",
+                html:     "\u003ch2 id=\"importing-ensemble-fracture-statistics\"\u003eImporting Ensemble Fracture Statistics\u003c/h2\u003e\n\u003cp\u003eRight-click on \u003cstrong\u003eCompletion Templates \u0026gt; Ensemble Fracture Statistics\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e and select the \u003cstrong\u003eImport StimPlan Fracture Recursively\u003c/strong\u003e option. Then select the StimPlan fracture Xml files to be part of the ensemble.\u003c/p\u003e\n\u003cp\u003eAfter importing the \u003cstrong\u003eProperty Panel\u003c/strong\u003e of the \u003cstrong\u003eEnsemble Fracture Statistics\u003c/strong\u003e item has these options:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eName\u003c/strong\u003e \u0026ndash; Name of the ensemble fracture statistics.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Zero Width Fractures\u003c/strong\u003e \u0026ndash; Toggle to remove zero width fractures from the statistics.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Alignment\u003c/strong\u003e \u0026ndash; Specifies how to align the mesh.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Depth\u003c/strong\u003e \u0026ndash; Use the raw mesh depths from file without adjustment.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePerforation Depth\u003c/strong\u003e \u0026ndash; Adjusts the mesh location to have the perforation at the same location when computing the statistics.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMesh Type\u003c/strong\u003e \u0026ndash; Specifies the meshing strategy. See details below.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eStatistics Type\u003c/strong\u003e \u0026ndash; The statistics to compute.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"mesh-types\"\u003eMesh Types\u003c/h2\u003e\n\u003cp\u003eThe imported StimPlan fractures are stacked on top of each, and a statistics mesh is created. The statistics mesh covers the extents of\nall the individual meshes in the ensemble.\u003c/p\u003e\n\u003ch3 id=\"adaptive-mesh\"\u003eAdaptive Mesh\u003c/h3\u003e\n\u003cp\u003eThe adaptive mesh tries to optimize the horizontal depth spacing to have coarse sampling where the\nsource meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of\nthe individual meshes into fixed bins, and then scaling the vertical size of each layer according to their mean size.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eMean Type\u003c/strong\u003e \u0026ndash; The mean calculation used to scale the layer thickness.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHarmonic\u003c/strong\u003e \u0026ndash; See \u003ca href=\"https://en.wikipedia.org/wiki/Harmonic_mean\"\u003eHarmonic mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArithmetic\u003c/strong\u003e \u0026ndash; Average. See \u003ca href=\"https://en.wikipedia.org/wiki/Arithmetic_mean\"\u003eArithmetic Mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGeometric\u003c/strong\u003e \u0026ndash; See \u003ca href=\"https://en.wikipedia.org/wiki/Geometric_mean\"\u003eGeometric Mean\u003c/a\u003e for details.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum\u003c/strong\u003e \u0026ndash; Use the minimum thickness.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Layers\u003c/strong\u003e \u0026ndash; Specifies the number of layers to create.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eAverage\u003c/strong\u003e \u0026ndash; Use the average number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum\u003c/strong\u003e \u0026ndash; Use the minimum number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMaximum\u003c/strong\u003e \u0026ndash; Use the maximum number of layers of the individual fractures of the ensemble.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eUser-Defined\u003c/strong\u003e \u0026ndash; The user specifies the number of layers.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\u003c/p\u003e\n\u003ch3 id=\"uniform-mesh\"\u003eUniform Mesh\u003c/h3\u003e\n\u003cp\u003eThe uniform mesh has cells of a equal size. The minimum and maximum extents of all the meshes in both directions is found, and the interval is divided into equal cells.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eX\u003c/strong\u003e \u0026ndash; The number of cells in lateral direction.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eY\u003c/strong\u003e \u0026ndash; The number of cells in depth direction.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"naive-mesh\"\u003eNaive Mesh\u003c/h3\u003e\n\u003cp\u003eThe naive method produces a mesh where every depth in all the individual fractures of the ensemble is present.\u003c/p\u003e\n\u003cp\u003eThe mesh is evenly spaced in the lateral direction using the maximum number of cells in the individual fractures of the ensemble.\u003c/p\u003e\n\u003ch2 id=\"statistics-mesh-computation\"\u003eStatistics Mesh Computation\u003c/h2\u003e\n\u003cp\u003eThe statistics mesh samples each individual fracture of the ensemble in each cell center. The value of the cell containing the\nstatistics mesh cell center is used. Invalid values or empty cells are ignored. The values at each cell center are gathered, and\nthe chosen statistics (e.g. P10 and Mean) is computed per cell.\u003c/p\u003e\n\u003cp\u003eThe statistics meshes are written to file in a StimPlan compatible XML file, and is imported into \u003cstrong\u003eFracture Templates\u003c/strong\u003e in the\n\u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"statistics-table\"\u003eStatistics Table\u003c/h2\u003e\n\u003cp\u003eThe statistics table contains overall statistics on key properties of the fractures.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eHeight\u003c/strong\u003e \u0026ndash; Longest aggregate height of conductive cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eArea\u003c/strong\u003e \u0026ndash; Area of the conductive cells of the fracture.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWidth\u003c/strong\u003e \u0026ndash; Width of conductive cells weighted by their area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eHalflength (Xf)\u003c/strong\u003e \u0026ndash; Length of the fracture is area divided by height. Xf is half of the length.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eConductivity (KfWf)\u003c/strong\u003e \u0026ndash; Conductivity weighted by area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePermeability\u003c/strong\u003e \u0026ndash; Permeability (i.e. conductivity divided by width) weighted by area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Dip\u003c/strong\u003e \u0026ndash; Formation dip as reported in the Xml file.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/wells-and-completions/ensemblefracturestatistics/"
             };
         
@@ -3569,8 +3568,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  Ensemble File Dialog\nNaming The name of an ensemble can be changed by interactive edit of the name in the Project Tree (by clicking or using F2) or selecting the ensemble and changing the name in the Property Editor.\nPlotting 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.\nA color selection dialog can be opened by clicking on the color icon in the Project Tree. 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 Single color with Transparency Use transparency for the ensemble curves 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. By Objective Function Use the value of an objective function for colors. By Custom Objective Function Use the value of an objective function for colors.  Stepping of data source for ensemble curves is described in Summary Plot Source Stepping\nObjective Functions\nResampling Resampling of curves is possibly by selecting the actual curve(s) listed by the Ensemble Curve Sets item in Plot Project Tree and using the Resampling feature of Property Editor.\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.\nDelta Ensemble A new ensemble can be created based on calculations on two or more ensembles. Such an ensemble is called an Delta Ensemble. A delta ensemble will contain data which are either the sum or difference between two other ensembles. An existing delta ensemble may be input to a new delta ensemble, making it possible to, for instance, add more than two ensembles.\nTo create a delta ensemble, select two existing ensembles in Plot Project Tree, then right-click and select New Delta Ensemble. A new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the delta ensemble, both input ensembles and operator can be modified. Checking Match On Parameters ensures strict match on ensemble parameters. In addition, it is possible to specify a fixed time step to be used in delta computation, see Delta Summary Case for an example.\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 delta ensemble or not.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/Ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\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\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\u003cp\u003e\u003ca href=\"/import/ensemblefiledialog/\"\u003eEnsemble File Dialog\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"naming\"\u003eNaming\u003c/h2\u003e\n\u003cp\u003eThe name of an ensemble can be changed by interactive edit of the name in the \u003cstrong\u003eProject Tree\u003c/strong\u003e (by clicking or using \u003cstrong\u003eF2\u003c/strong\u003e) or selecting the ensemble and changing the name in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\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.\u003c/p\u003e\n\u003cp\u003eA color selection dialog can be opened by clicking on the color icon in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/ColorSelectionDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe 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\u003eSingle color with Transparency\u003c/strong\u003e Use transparency for the ensemble curves\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\u003cli\u003e\u003cstrong\u003eBy Objective Function\u003c/strong\u003e Use the value of an objective function for colors.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Custom Objective Function\u003c/strong\u003e Use the value of an objective function for colors.\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\u003cp\u003e\u003ca href=\"/plot-window/objectivefunctions/\"\u003eObjective Functions\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"resampling\"\u003eResampling\u003c/h3\u003e\n\u003cp\u003eResampling of curves is possibly by selecting the actual curve(s) listed by the \u003cem\u003eEnsemble Curve Sets\u003c/em\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and using the \u003cstrong\u003eResampling\u003c/strong\u003e feature of \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsemblePlottingResampling.png\" alt=\"\"\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\u003ch2 id=\"delta-ensemble\"\u003eDelta Ensemble\u003c/h2\u003e\n\u003cp\u003eA new ensemble can be created based on calculations on two or more ensembles. \nSuch an ensemble is called an \u003cstrong\u003eDelta Ensemble\u003c/strong\u003e. \nA delta ensemble will contain data which are either the sum or difference between two other ensembles. \nAn existing delta ensemble may be input to a new delta ensemble, making it possible to, for instance, add more than two ensembles.\u003c/p\u003e\n\u003cp\u003eTo create a delta ensemble, select two existing ensembles in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e, then right-click and select \u003cstrong\u003eNew Delta Ensemble\u003c/strong\u003e. \nA new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator. \nIn the property for the delta ensemble, both input ensembles and operator can be modified.\nChecking \u003cem\u003eMatch On Parameters\u003c/em\u003e ensures strict match on ensemble parameters. \nIn addition, it is possible to specify a fixed time step to be used in delta computation, see \n\u003ca href=\"/plot-window/summaryplots/#delta-summary-case\"\u003eDelta Summary Case\u003c/a\u003e for an example.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeltaEnsemblePropertyEditor.png\" alt=\"\"\u003e\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 delta ensemble or not.\u003c/p\u003e\n",
+                content:  "\nAn 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:\nUse 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:\nOne or more of the cases in the ensemble have no ensemble parameters The list of ensemble parameters differ between cases in the ensemble Ensemble File Dialog\nNaming The name of an ensemble can be changed by interactive edit of the name in the Project Tree (by clicking or using F2) or selecting the ensemble and changing the name in the Property Editor.\nPlotting 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.\nA color selection dialog can be opened by clicking on the color icon in the Project Tree. 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:\nSingle color Use the same color for all curves in a curve set Single color with Transparency Use transparency for the ensemble curves 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. By Objective Function Use the value of an objective function for colors. By Custom Objective Function Use the value of an objective function for colors. Stepping of data source for ensemble curves is described in Summary Plot Source Stepping\nObjective Functions\nResampling Resampling of curves is possibly by selecting the actual curve(s) listed by the Ensemble Curve Sets item in Plot Project Tree and using the Resampling feature of Property Editor.\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:\nP10 \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.\nDelta Ensemble A new ensemble can be created based on calculations on two or more ensembles. Such an ensemble is called an Delta Ensemble. A delta ensemble will contain data which are either the sum or difference between two other ensembles. An existing delta ensemble may be input to a new delta ensemble, making it possible to, for instance, add more than two ensembles.\nTo create a delta ensemble, select two existing ensembles in Plot Project Tree, then right-click and select New Delta Ensemble. A new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator. In the property for the delta ensemble, both input ensembles and operator can be modified. Checking Match On Parameters ensures strict match on ensemble parameters. In addition, it is possible to specify a fixed time step to be used in delta computation, see Delta Summary Case for an example.\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 delta ensemble or not.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/Ensemble.png\" alt=\"\"\u003e\u003c/p\u003e\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\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\u003cp\u003e\u003ca href=\"/import/ensemblefiledialog/\"\u003eEnsemble File Dialog\u003c/a\u003e\u003c/p\u003e\n\u003ch2 id=\"naming\"\u003eNaming\u003c/h2\u003e\n\u003cp\u003eThe name of an ensemble can be changed by interactive edit of the name in the \u003cstrong\u003eProject Tree\u003c/strong\u003e (by clicking or using \u003cstrong\u003eF2\u003c/strong\u003e) or selecting the ensemble and changing the name in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\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.\u003c/p\u003e\n\u003cp\u003eA color selection dialog can be opened by clicking on the color icon in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\n\u003cimg src=\"/images/plot-window/ColorSelectionDialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe 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\u003eSingle color with Transparency\u003c/strong\u003e Use transparency for the ensemble curves\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\u003cli\u003e\u003cstrong\u003eBy Objective Function\u003c/strong\u003e Use the value of an objective function for colors.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBy Custom Objective Function\u003c/strong\u003e Use the value of an objective function for colors.\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\u003cp\u003e\u003ca href=\"/plot-window/objectivefunctions/\"\u003eObjective Functions\u003c/a\u003e\u003c/p\u003e\n\u003ch3 id=\"resampling\"\u003eResampling\u003c/h3\u003e\n\u003cp\u003eResampling of curves is possibly by selecting the actual curve(s) listed by the \u003cem\u003eEnsemble Curve Sets\u003c/em\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e and using the \u003cstrong\u003eResampling\u003c/strong\u003e feature of \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsemblePlottingResampling.png\" alt=\"\"\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\u003ch2 id=\"delta-ensemble\"\u003eDelta Ensemble\u003c/h2\u003e\n\u003cp\u003eA new ensemble can be created based on calculations on two or more ensembles.\nSuch an ensemble is called an \u003cstrong\u003eDelta Ensemble\u003c/strong\u003e.\nA delta ensemble will contain data which are either the sum or difference between two other ensembles.\nAn existing delta ensemble may be input to a new delta ensemble, making it possible to, for instance, add more than two ensembles.\u003c/p\u003e\n\u003cp\u003eTo create a delta ensemble, select two existing ensembles in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e, then right-click and select \u003cstrong\u003eNew Delta Ensemble\u003c/strong\u003e.\nA new delta ensemble is created with the two selected ensembles as input and a default arithmetic operator.\nIn the property for the delta ensemble, both input ensembles and operator can be modified.\nChecking \u003cem\u003eMatch On Parameters\u003c/em\u003e ensures strict match on ensemble parameters.\nIn addition, it is possible to specify a fixed time step to be used in delta computation, see\n\u003ca href=\"/plot-window/summaryplots/#delta-summary-case\"\u003eDelta Summary Case\u003c/a\u003e for an example.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeltaEnsemblePropertyEditor.png\" alt=\"\"\u003e\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 delta ensemble or not.\u003c/p\u003e\n",
                 url:      "/plot-window/ensembleplotting/"
             };
         
@@ -3578,8 +3577,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/flowvectorresult/"] = {
                 title:    "Flow Results",
-                content:  "Flow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.\nFlow Vectors Flow vectors are computed based on the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K. Visualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.\nIn order to show flow vectors, check the checkbox next to Flow Vector Result in Project Tree.\nThis updates the 3D View with arrows visualizing the fluxes for the given time step or animation. The directions, data source fluids, color, scale and threshold can be adjusted in the Property Editor.\nThe legend in 3D View maps the Flow Vector colors to their respective result values. By default it shows the max values for all time steps. The legend settings can be changed in the Color Legend sub item of the Flow Vector Result item in Project Tree.\nWhen combining several fluids, the max value shown in legend is an aggregation of the single max values of each selected fluid. This means that this number might be higher than the result of any flow vector.\n\rFlow Vector Settings The Property Editor controls the following settings:\n  Fluids: Selection of fluids for displaying fluxes as aggregated vectors in 3D view.\n  Visibility\n\u0026ndash; View Vectors: Select Per Face to show one flow vector per cell face or Cell Center Total to show only one vector per cell center (as an aggregation of all single direction vectors).\n\u0026ndash; Vectors Touching Surface: Select At Vector Anchor to display vectors starting at cell faces or At Vector Center to center vectors at cell faces. Vectors Touching Surface is enabled when View vectors is set to Per Face.\n\u0026ndash; I/J/K: Use flows in I/J/K direction for computing vectors.\n\u0026ndash; Show NNC data: Visualize flows between non-neighbouring cells.\n\u0026ndash; Threshold: All vectors with flow result values below this number are hidden.\n  Appearance: Select Result Colors to color vectors according to Element Vector Result legend in 3D View or Uniform for uniform color. Use Size Scale to scale vector length.\n  Cell Result View ResInsight may visualize intercell flows, flow rates, and transmissibilities as Cell Results optionally divided by face area, c.f. check-box Divide By Area below. For instance, the option enables comparison of horisontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.\nSpecifically, the check-box Divide By Area is applicable to Eclipse properties FLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT, and transmissibilities TRAN and riTRAN. These results are listed in ResInsight postfixed by IJK+- or XYZ as shown above. As seen, checking Divide By Area is reflected by text /A in legend.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResult.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFlow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.\u003c/p\u003e\n\u003ch2 id=\"flow-vectors\"\u003eFlow Vectors\u003c/h2\u003e\n\u003cp\u003eFlow vectors are computed based on the Eclipse properties \u003cstrong\u003eFLRGASI/J/K FLRWATI/J/K FLROILI/J/K\u003c/strong\u003e. \nVisualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.\u003c/p\u003e\n\u003cp\u003eIn order to show flow vectors, check the checkbox next to \u003cstrong\u003eFlow Vector Result\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultMenu.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis updates the 3D View with arrows visualizing the fluxes for the given time step or animation. The directions, data source fluids, color, scale and threshold can be adjusted in the Property Editor.\u003c/p\u003e\n\u003cp\u003eThe legend in 3D View maps the Flow Vector colors to their respective result values. By default it shows the max values for all time steps. The legend settings can be changed in the \u003cstrong\u003eColor Legend\u003c/strong\u003e sub item of the \u003cstrong\u003eFlow Vector Result\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultLegend.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen combining several fluids, the max value shown in legend is an aggregation of the single max values of each selected fluid. This means that this number might be higher than the result of any flow vector.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"flow-vector-settings\"\u003eFlow Vector Settings\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultProperties.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Property Editor controls the following settings:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFluids\u003c/strong\u003e: Selection of fluids for displaying fluxes as aggregated vectors in 3D view.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eVisibility\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eView Vectors\u003c/strong\u003e: Select \u003cem\u003ePer Face\u003c/em\u003e to show one flow vector per cell face or \u003cem\u003eCell Center Total\u003c/em\u003e to show only one vector per cell center (as an aggregation of all single direction vectors).\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eVectors Touching Surface\u003c/strong\u003e: Select \u003cem\u003eAt Vector Anchor\u003c/em\u003e to display vectors starting at cell faces or \u003cem\u003eAt Vector Center\u003c/em\u003e to center vectors at cell faces. \n\u003cem\u003eVectors Touching Surface\u003c/em\u003e is enabled when \u003cem\u003eView vectors\u003c/em\u003e is set to \u003cem\u003ePer Face\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eI/J/K\u003c/strong\u003e: Use flows in I/J/K direction for computing vectors.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eShow NNC data\u003c/strong\u003e: Visualize flows between non-neighbouring cells.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eThreshold\u003c/strong\u003e: All vectors with flow result values below this number are hidden.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e: Select \u003cem\u003eResult Colors\u003c/em\u003e to color vectors according to \u003cem\u003eElement Vector Result\u003c/em\u003e legend in 3D View or \u003cem\u003eUniform\u003c/em\u003e for uniform color. Use \u003cem\u003eSize Scale\u003c/em\u003e to scale vector length.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"cell-result-view\"\u003eCell Result View\u003c/h2\u003e\n\u003cp\u003eResInsight may visualize intercell flows, flow rates, and transmissibilities as \u003cem\u003eCell Results\u003c/em\u003e optionally divided by face area, c.f. check-box \u003cem\u003eDivide By Area\u003c/em\u003e below.\nFor instance, the option enables comparison of horisontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowRateCellResultAndLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSpecifically, the check-box \u003cem\u003eDivide By Area\u003c/em\u003e is applicable to Eclipse properties \u003cem\u003eFLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT\u003c/em\u003e, and transmissibilities \u003cem\u003eTRAN\u003c/em\u003e and \u003cem\u003eriTRAN\u003c/em\u003e.\nThese results are listed in ResInsight postfixed by \u003cem\u003eIJK+-\u003c/em\u003e or \u003cem\u003eXYZ\u003c/em\u003e as shown above. As seen, checking \u003cem\u003eDivide By Area\u003c/em\u003e is reflected by text \u003cem\u003e/A\u003c/em\u003e in legend.\u003c/p\u003e\n",
+                content:  "\nFlow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.\nFlow Vectors Flow vectors are computed based on the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K. Visualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.\nIn order to show flow vectors, check the checkbox next to Flow Vector Result in Project Tree.\nThis updates the 3D View with arrows visualizing the fluxes for the given time step or animation. The directions, data source fluids, color, scale and threshold can be adjusted in the Property Editor.\nThe legend in 3D View maps the Flow Vector colors to their respective result values. By default it shows the max values for all time steps. The legend settings can be changed in the Color Legend sub item of the Flow Vector Result item in Project Tree.\nWhen combining several fluids, the max value shown in legend is an aggregation of the single max values of each selected fluid. This means that this number might be higher than the result of any flow vector.\nFlow Vector Settings The Property Editor controls the following settings:\nFluids: Selection of fluids for displaying fluxes as aggregated vectors in 3D view.\nVisibility\n\u0026ndash; View Vectors: Select Per Face to show one flow vector per cell face or Cell Center Total to show only one vector per cell center (as an aggregation of all single direction vectors).\n\u0026ndash; Vectors Touching Surface: Select At Vector Anchor to display vectors starting at cell faces or At Vector Center to center vectors at cell faces. Vectors Touching Surface is enabled when View vectors is set to Per Face.\n\u0026ndash; I/J/K: Use flows in I/J/K direction for computing vectors.\n\u0026ndash; Show NNC data: Visualize flows between non-neighbouring cells.\n\u0026ndash; Threshold: All vectors with flow result values below this number are hidden.\nAppearance: Select Result Colors to color vectors according to Element Vector Result legend in 3D View or Uniform for uniform color. Use Size Scale to scale vector length.\nCell Result View ResInsight may visualize intercell flows, flow rates, and transmissibilities as Cell Results optionally divided by face area, c.f. check-box Divide By Area below. For instance, the option enables comparison of horisontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.\nSpecifically, the check-box Divide By Area is applicable to Eclipse properties FLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT, and transmissibilities TRAN and riTRAN. These results are listed in ResInsight postfixed by IJK+- or XYZ as shown above. As seen, checking Divide By Area is reflected by text /A in legend.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResult.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFlow Results lets the user investigate flow properties and fluxes in a reservoir, e.g. by flow vector visualizations selecting and combining different fluids and directions.\u003c/p\u003e\n\u003ch2 id=\"flow-vectors\"\u003eFlow Vectors\u003c/h2\u003e\n\u003cp\u003eFlow vectors are computed based on the Eclipse properties \u003cstrong\u003eFLRGASI/J/K FLRWATI/J/K FLROILI/J/K\u003c/strong\u003e.\nVisualization of flow vector results always use velocity instead of rate. Velocity is computed as flow rate divided by cell face area.\u003c/p\u003e\n\u003cp\u003eIn order to show flow vectors, check the checkbox next to \u003cstrong\u003eFlow Vector Result\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultMenu.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThis updates the 3D View with arrows visualizing the fluxes for the given time step or animation. The directions, data source fluids, color, scale and threshold can be adjusted in the Property Editor.\u003c/p\u003e\n\u003cp\u003eThe legend in 3D View maps the Flow Vector colors to their respective result values. By default it shows the max values for all time steps. The legend settings can be changed in the \u003cstrong\u003eColor Legend\u003c/strong\u003e sub item of the \u003cstrong\u003eFlow Vector Result\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultLegend.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eWhen combining several fluids, the max value shown in legend is an aggregation of the single max values of each selected fluid. This means that this number might be higher than the result of any flow vector.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"flow-vector-settings\"\u003eFlow Vector Settings\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowVectorResultProperties.PNG\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe Property Editor controls the following settings:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFluids\u003c/strong\u003e: Selection of fluids for displaying fluxes as aggregated vectors in 3D view.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eVisibility\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eView Vectors\u003c/strong\u003e: Select \u003cem\u003ePer Face\u003c/em\u003e to show one flow vector per cell face or \u003cem\u003eCell Center Total\u003c/em\u003e to show only one vector per cell center (as an aggregation of all single direction vectors).\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eVectors Touching Surface\u003c/strong\u003e: Select \u003cem\u003eAt Vector Anchor\u003c/em\u003e to display vectors starting at cell faces or \u003cem\u003eAt Vector Center\u003c/em\u003e to center vectors at cell faces.\n\u003cem\u003eVectors Touching Surface\u003c/em\u003e is enabled when \u003cem\u003eView vectors\u003c/em\u003e is set to \u003cem\u003ePer Face\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eI/J/K\u003c/strong\u003e: Use flows in I/J/K direction for computing vectors.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eShow NNC data\u003c/strong\u003e: Visualize flows between non-neighbouring cells.\u003c/p\u003e\n\u003cp\u003e\u0026ndash; \u003cstrong\u003eThreshold\u003c/strong\u003e: All vectors with flow result values below this number are hidden.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eAppearance\u003c/strong\u003e: Select \u003cem\u003eResult Colors\u003c/em\u003e to color vectors according to \u003cem\u003eElement Vector Result\u003c/em\u003e legend in 3D View or \u003cem\u003eUniform\u003c/em\u003e for uniform color. Use \u003cem\u003eSize Scale\u003c/em\u003e to scale vector length.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"cell-result-view\"\u003eCell Result View\u003c/h2\u003e\n\u003cp\u003eResInsight may visualize intercell flows, flow rates, and transmissibilities as \u003cem\u003eCell Results\u003c/em\u003e optionally divided by face area, c.f. check-box \u003cem\u003eDivide By Area\u003c/em\u003e below.\nFor instance, the option enables comparison of horisontal and vertical flow velocities as alternative to flow rates as the latter is typically influenced by significant differences in cell face areas.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FlowRateCellResultAndLegend.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSpecifically, the check-box \u003cem\u003eDivide By Area\u003c/em\u003e is applicable to Eclipse properties \u003cem\u003eFLROIL, FLRGAS, FLRWAT, FLOOIL, FLOGAS, FLOWAT\u003c/em\u003e, and transmissibilities \u003cem\u003eTRAN\u003c/em\u003e and \u003cem\u003eriTRAN\u003c/em\u003e.\nThese results are listed in ResInsight postfixed by \u003cem\u003eIJK+-\u003c/em\u003e or \u003cem\u003eXYZ\u003c/em\u003e as shown above. As seen, checking \u003cem\u003eDivide By Area\u003c/em\u003e is reflected by text \u003cem\u003e/A\u003c/em\u003e in legend.\u003c/p\u003e\n",
                 url:      "/3d-main-window/flowvectorresult/"
             };
         
@@ -3587,8 +3586,8 @@ if (!doNotTrack) {
          
             window.store["/import/"] = {
                 title:    "Import",
-                content:  "ResInsight is able to import a wide span of Eclipse files, seismic data files, and ROFF grid models.\nFor 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.\nIn addition, 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\u003cp\u003eResInsight is able to import a wide span of Eclipse files, seismic data files, and ROFF grid models.\u003c/p\u003e\n\u003cp\u003eFor import of Eclipse data pertinent to summary vectors and well log data, see \n\u003ca href=\"/plot-window/\"\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\u003eIn addition, 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.\u003c/p\u003e\n",
+                content:  "\nResInsight is able to import a wide span of Eclipse files, seismic data files, and ROFF grid models.\nFor 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.\nIn addition, 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\u003cp\u003eResInsight is able to import a wide span of Eclipse files, seismic data files, and ROFF grid models.\u003c/p\u003e\n\u003cp\u003eFor import of Eclipse data pertinent to summary vectors and well log data, see\n\u003ca href=\"/plot-window/\"\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\u003eIn addition, 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.\u003c/p\u003e\n",
                 url:      "/import/"
             };
         
@@ -3596,8 +3595,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.  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\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\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\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\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",
+                content:  "ResInsight provides a flexible interface to Octave including:\nOctave 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.\nOctave 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.\nExample 1 # Calculate change of oil saturation from time step to time step SOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;); SOILDIFF = SOIL; i = 0; for timestep = SOIL if (i \u0026gt; 0) SOILDIFF(:,i) = timestep - SOIL(:,i); endif i++; endfor SOILDIFF(:,i) = 0; riSetActiveCellProperty(SOILDIFF, \u0026#34;SOILDIFF\u0026#34;); Example 2 # Set all values to \u0026#34;Undefined\u0026#34; exept k-layers from 17 to 20 CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;); 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, \u0026#34;KSlice\u0026#34;); Example 3 # Keep the values in the first LGR only CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;); Mask = (CInfo(:,1) != 1); LGRSOIL = SOIL; i = 0; for i = (1:columns(LGRSOIL)) LGRSOIL(Mask,i) = nan; endfor riSetActiveCellProperty(LGRSOIL, \u0026#34;LGRSOIL\u0026#34;); Example 4 ( Might be slow on big models) # Calculate the average SOIL value across K layers CInfo = riGetActiveCellInfo(); SOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;); 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, \u0026#34;SOIL_KAverage\u0026#34;); ",
+                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\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\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\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\u003ch4 id=\"example-1\"\u003eExample 1\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" 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\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# Calculate change of oil saturation from time step to time step\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOILDIFF = SOIL;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ei = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e timestep = SOIL\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\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) \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\t\tSOILDIFF(:,i) = timestep \u003cspan style=\"color:#f92672\"\u003e-\u003c/span\u003e SOIL(:,i);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\tendif\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\ti\u003cspan style=\"color:#f92672\"\u003e++\u003c/span\u003e;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eendfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOILDIFF(:,i) = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eriSetActiveCellProperty(SOILDIFF, \u0026#34;SOILDIFF\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-2\"\u003eExample 2\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" 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\u003cspan style=\"display:flex;\"\u003e\u003cspan\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\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCInfo = riGetActiveCellInfo();\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eMask = (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)\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eLGRSOIL = SOIL;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ei = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(LGRSOIL))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    LGRSOIL(Mask,i) = nan;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eendfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eriSetActiveCellProperty(LGRSOIL, \u0026#34;KSlice\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch4 id=\"example-3\"\u003eExample 3\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" 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\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# Keep the values in the first LGR only\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCInfo = riGetActiveCellInfo();\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eMask = (CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e) != \u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eLGRSOIL = SOIL;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ei = \u003cspan style=\"color:#ae81ff\"\u003e0\u003c/span\u003e;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(LGRSOIL))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    LGRSOIL(Mask,i) = nan;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eendfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eriSetActiveCellProperty(LGRSOIL, \u0026#34;LGRSOIL\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\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 tabindex=\"0\" 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\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# Calculate the average SOIL value across K layers\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eCInfo = riGetActiveCellInfo();\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL = riGetActiveCellProperty(\u0026#34;SOIL\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL_KAverage = SOIL;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eSOIL_KAverage(:) = nan;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003emini = min(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e2\u003c/span\u003e))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003emaxi = max(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e2\u003c/span\u003e))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eminj = min(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e3\u003c/span\u003e))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003emaxj = max(CInfo(:,\u003cspan style=\"color:#ae81ff\"\u003e3\u003c/span\u003e))\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e i = mini:maxi\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e j = minj:maxj \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    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) ;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    \u003cspan style=\"color:#66d9ef\"\u003efor\u003c/span\u003e ts = (\u003cspan style=\"color:#ae81ff\"\u003e1\u003c/span\u003e:columns(SOIL)) \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e      SOIL_KAverage(Mask, ts) = mean(SOIL(Mask, ts));\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e    endfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e  endfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eendfor\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eriSetActiveCellProperty(SOIL_KAverage, \u0026#34;SOIL_KAverage\u0026#34;);\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/scripting/octaveinterface/"
             };
         
@@ -3605,7 +3604,7 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/streamlines/"] = {
                 title:    "Streamlines",
-                content:  "Streamlines lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K.\nDisplaying Streamlines To display streamlines, select a time step and check the Streamlines checkbox in Project Tree.\nProperty Editor The display and animation of streamlines is controlled by the Property Editor.\nThe following groups of settings control the content, display and animation of streamlines:\nData Selection\n Phase: Selection of an individual phase (Oil, Gas, Water) or Combined display. Flow Threshold: Minimum flow threshold calculated as I/J/K flow rate divided by corresponding face area. Minimum Length: Minimum length of streamlines in meters. Resolution: Resolution of streamline animation in days (governing the number of individual animation steps). Max Days: Maximum calculation range in days for streamline animation.  Well Selection\n Injector Wells: Calculate streamlines stemming from injector wells. Producer Wells: Calculate streamlines backtracing from producer wells.  Visualization Settings\n Visualization Mode: Perform an animation of streamlines or manually control the display. Colors: Color the streamlines by dominant phase or by velocity. Animation Speed: Adjust the speed of streamline animation. Tracer Length: Adjust the length of the individual tracers pertinent to a streamline.  In case Visualization Mode is set to Manual control, the setting Animation Index replaces the two latter settings. Animation Index allows for displaying an individual animation step.\nAlgorithm in brief Streamlines are generated by starting in open injector well cells and tracing out through the face with the largest flow rate (in m/day) into the next cell and so on. If flow rates above the given threshold exists for multiple cell faces, additional trace branches are spawned off for those faces. The distance between each point added to a trace is controlled by the resolution, as $ distance = rate * resolution $. The trace ends when either:\n the flow goes below the user specified threshold the maximum number of days since the start of the trace have been reached a cell that already has a trace in it is encountered an active well cell is encountered  Streamlines could also be generated using production wells as starting cells. In that case, the flow is reversed and the flow is traced backwards from the starting well using the same algorithm as for injector wells. Once reaching the end, the trace is reversed again to have the flow go into the production well in the final streamline.\n",
+                content:  "\nStreamlines lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties FLRGASI/J/K FLRWATI/J/K FLROILI/J/K.\nDisplaying Streamlines To display streamlines, select a time step and check the Streamlines checkbox in Project Tree.\nProperty Editor The display and animation of streamlines is controlled by the Property Editor.\nThe following groups of settings control the content, display and animation of streamlines:\nData Selection\nPhase: Selection of an individual phase (Oil, Gas, Water) or Combined display. Flow Threshold: Minimum flow threshold calculated as I/J/K flow rate divided by corresponding face area. Minimum Length: Minimum length of streamlines in meters. Resolution: Resolution of streamline animation in days (governing the number of individual animation steps). Max Days: Maximum calculation range in days for streamline animation. Well Selection\nInjector Wells: Calculate streamlines stemming from injector wells. Producer Wells: Calculate streamlines backtracing from producer wells. Visualization Settings\nVisualization Mode: Perform an animation of streamlines or manually control the display. Colors: Color the streamlines by dominant phase or by velocity. Animation Speed: Adjust the speed of streamline animation. Tracer Length: Adjust the length of the individual tracers pertinent to a streamline. In case Visualization Mode is set to Manual control, the setting Animation Index replaces the two latter settings. Animation Index allows for displaying an individual animation step.\nAlgorithm in brief Streamlines are generated by starting in open injector well cells and tracing out through the face with the largest flow rate (in m/day) into the next cell and so on. If flow rates above the given threshold exists for multiple cell faces, additional trace branches are spawned off for those faces. The distance between each point added to a trace is controlled by the resolution, as $ distance = rate * resolution $. The trace ends when either:\nthe flow goes below the user specified threshold the maximum number of days since the start of the trace have been reached a cell that already has a trace in it is encountered an active well cell is encountered Streamlines could also be generated using production wells as starting cells. In that case, the flow is reversed and the flow is traced backwards from the starting well using the same algorithm as for injector wells. Once reaching the end, the trace is reversed again to have the flow go into the production well in the final streamline.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/Streamlines.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eStreamlines lets the user investigate the flow of different phases through a reservoar. It allows for selecting both an individual phase or a combination of phases colored by the dominant phase or velocity. The visualization and animation of streamlines requires the Eclipse properties \u003cstrong\u003eFLRGASI/J/K FLRWATI/J/K FLROILI/J/K\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"displaying-streamlines\"\u003eDisplaying Streamlines\u003c/h2\u003e\n\u003cp\u003eTo display streamlines, select a time step and check the \u003cstrong\u003eStreamlines\u003c/strong\u003e checkbox in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StreamlinesProjectTreeCheckBox.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe display and animation of streamlines is controlled by the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/StreamlinesPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe following groups of settings control the content, display and animation of streamlines:\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eData Selection\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePhase\u003c/strong\u003e: Selection of an individual phase (\u003cem\u003eOil\u003c/em\u003e, \u003cem\u003eGas\u003c/em\u003e, \u003cem\u003eWater\u003c/em\u003e) or \u003cem\u003eCombined\u003c/em\u003e display.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFlow Threshold\u003c/strong\u003e: Minimum flow threshold calculated as I/J/K flow rate divided by corresponding face area.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMinimum Length\u003c/strong\u003e: Minimum length of streamlines in meters.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eResolution\u003c/strong\u003e: Resolution of streamline animation in days (governing the number of individual animation steps).\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMax Days\u003c/strong\u003e: Maximum calculation range in days for streamline animation.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eWell Selection\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInjector Wells\u003c/strong\u003e: Calculate streamlines stemming from injector wells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eProducer Wells\u003c/strong\u003e: Calculate streamlines backtracing from producer wells.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eVisualization Settings\u003c/strong\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eVisualization Mode\u003c/strong\u003e: Perform an animation of streamlines or manually control the display.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eColors\u003c/strong\u003e: Color the streamlines by dominant phase or by velocity.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAnimation Speed\u003c/strong\u003e: Adjust the speed of streamline animation.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTracer Length\u003c/strong\u003e: Adjust the length of the individual tracers pertinent to a streamline.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIn case \u003cstrong\u003eVisualization Mode\u003c/strong\u003e is set to \u003cstrong\u003eManual control\u003c/strong\u003e, the setting \u003cstrong\u003eAnimation Index\u003c/strong\u003e replaces the two latter settings. \u003cstrong\u003eAnimation Index\u003c/strong\u003e allows for displaying an individual animation step.\u003c/p\u003e\n\u003ch2 id=\"algorithm-in-brief\"\u003eAlgorithm in brief\u003c/h2\u003e\n\u003cp\u003eStreamlines are generated by starting in open injector well cells and tracing out through the face with the largest flow rate (in m/day) into the next cell and so on. If flow rates above the given threshold exists for multiple cell faces, additional trace branches are spawned off for those faces. The distance between each point added to a trace is controlled by the resolution, as $ distance = rate * resolution $. The trace ends when either:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003ethe flow goes below the user specified threshold\u003c/li\u003e\n\u003cli\u003ethe maximum number of days since the start of the trace have been reached\u003c/li\u003e\n\u003cli\u003ea cell that already has a trace in it is encountered\u003c/li\u003e\n\u003cli\u003ean active well cell is encountered\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eStreamlines could also be generated using production wells as starting cells. In that case, the flow is reversed and the flow is traced backwards from the starting well using the same algorithm as for injector wells. Once reaching the end, the trace is reversed again to have the flow go into the production well in the final streamline.\u003c/p\u003e\n",
                 url:      "/3d-main-window/streamlines/"
             };
@@ -3614,7 +3613,7 @@ 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",
+                content:  "\nTensors 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/"
             };
@@ -3623,7 +3622,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 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  ",
+                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 sub menu Export Well Paths.\nA dialog appears after selecting an export well path command.\nExport 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 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/"
             };
@@ -3632,7 +3631,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/objectivefunctions/"] = {
                 title:    "Objective Functions",
-                content:  "An Objective Function is used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\nUsing Objective Functions Curve coloring by Objective Function is activated as shown below.\nObjective Function\nResInsight uses the following objective function definition:\n$ F = \\frac {1} {N} \\Sigma (\\frac{ \\mid (t_i - tH_i) \\mid }{ \\epsilon * tH_i } )^n $\n$ t_i $ : Simulated value for time step $i$\n$ tH_i $ : History (observed) value for time step $i$\n$ N $ : Number of Observations\n$ \\epsilon $ : Error estimate [0..100 %]\n$ n $ : Either 1 - Basic error term, or 2 - Squared error term\nThe time step selection is either specified using Time Range (F1) to define all time steps in a time range or Selected Time Steps (F2)\nCreating Custom Objective Functions It is also possible to create a Custom Objective Function to customize the coloring of ensemble plots:\n  Custom objective functions can express a weighted sum of the default objective functions (applied to any vector)\n  Custom objective functions allow for an arbitrary combination of weigthed default objective functions\n  Thus, $ M_{custom} = \\Sigma_i^N weight_i * f_i(vectors) $ where $ f_i \\in \\lbrace F1, F2 \\rbrace $\n  A Custom Objective Function is created by invoking the context menu on the Custom Objective Functions item in Plot Project Tree.\nAdding a new weighted function expression to an existing objective function is performed by invoking the context menu as shown below.\nDisplay settings Changing objective function can be performed by the property editor of actual ensemble. The property editor also allows toggling the display of formula by the Show Formula in Plot check-box and setting of time step range.\nAs seen below, selected range is displayed by color frame and labels in plot background. The range determines the time range for which the objective function is utilized for coloring the curves.\n",
+                content:  "\nAn Objective Function is used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\nUsing Objective Functions Curve coloring by Objective Function is activated as shown below.\nObjective Function\nResInsight uses the following objective function definition:\n$ F = \\frac {1} {N} \\Sigma (\\frac{ \\mid (t_i - tH_i) \\mid }{ \\epsilon * tH_i } )^n $\n$ t_i $ : Simulated value for time step $i$\n$ tH_i $ : History (observed) value for time step $i$\n$ N $ : Number of Observations\n$ \\epsilon $ : Error estimate [0..100 %]\n$ n $ : Either 1 - Basic error term, or 2 - Squared error term\nThe time step selection is either specified using Time Range (F1) to define all time steps in a time range or Selected Time Steps (F2)\nCreating Custom Objective Functions It is also possible to create a Custom Objective Function to customize the coloring of ensemble plots:\nCustom objective functions can express a weighted sum of the default objective functions (applied to any vector)\nCustom objective functions allow for an arbitrary combination of weigthed default objective functions\nThus, $ M_{custom} = \\Sigma_i^N weight_i * f_i(vectors) $ where $ f_i \\in \\lbrace F1, F2 \\rbrace $\nA Custom Objective Function is created by invoking the context menu on the Custom Objective Functions item in Plot Project Tree.\nAdding a new weighted function expression to an existing objective function is performed by invoking the context menu as shown below.\nDisplay settings Changing objective function can be performed by the property editor of actual ensemble. The property editor also allows toggling the display of formula by the Show Formula in Plot check-box and setting of time step range.\nAs seen below, selected range is displayed by color frame and labels in plot background. The range determines the time range for which the objective function is utilized for coloring the curves.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsPlotColoring.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAn \u003cstrong\u003eObjective Function\u003c/strong\u003e is used to color the curves of an ensemble plot in ResInsight to highlight characteristics by a function definition based on individual summary vectors. As shown in the example above, the legend relates colours to values as calculated by a particular objective function and shows the use and formula of the objective function in the plot.\u003c/p\u003e\n\u003ch2 id=\"using-objective-functions\"\u003eUsing Objective Functions\u003c/h2\u003e\n\u003cp\u003eCurve coloring by \u003cstrong\u003eObjective Function\u003c/strong\u003e is activated as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsPlotProjectTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eObjective Function\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eResInsight uses the following objective function definition:\u003c/p\u003e\n\u003cp\u003e$ F = \\frac {1} {N} \\Sigma (\\frac{  \\mid (t_i - tH_i) \\mid }{ \\epsilon * tH_i } )^n $\u003c/p\u003e\n\u003cp\u003e$ t_i $ : Simulated value for time step $i$\u003c/p\u003e\n\u003cp\u003e$ tH_i $ : History (observed) value for time step $i$\u003c/p\u003e\n\u003cp\u003e$ N $ : Number of Observations\u003c/p\u003e\n\u003cp\u003e$ \\epsilon $ : Error estimate [0..100 %]\u003c/p\u003e\n\u003cp\u003e$ n $ : Either 1 - Basic error term, or 2 - Squared error term\u003c/p\u003e\n\u003cp\u003eThe time step selection is either specified using \u003cstrong\u003eTime Range (F1)\u003c/strong\u003e to define all time steps in a time range or \u003cstrong\u003eSelected Time Steps (F2)\u003c/strong\u003e\u003c/p\u003e\n\u003ch2 id=\"creating-custom-objective-functions\"\u003eCreating Custom Objective Functions\u003c/h2\u003e\n\u003cp\u003eIt is also possible to create a \u003cstrong\u003eCustom Objective Function\u003c/strong\u003e to customize the coloring of ensemble plots:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eCustom objective functions can express a weighted sum of the default objective functions (applied to any vector)\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eCustom objective functions allow for an arbitrary combination of weigthed default objective functions\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eThus, $ M_{custom} = \\Sigma_i^N weight_i * f_i(vectors) $ where $ f_i \\in \\lbrace F1, F2 \\rbrace $\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eA Custom Objective Function is created by invoking the context menu on the \u003cstrong\u003eCustom Objective Functions\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsCustomFunction.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAdding a new weighted function expression to an existing objective function is performed by invoking the context menu as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsWeightsNaming.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"display-settings\"\u003eDisplay settings\u003c/h2\u003e\n\u003cp\u003eChanging objective function can be performed by the property editor of actual ensemble. The property editor also allows toggling the display of formula by the \u003cem\u003eShow Formula in Plot\u003c/em\u003e check-box and setting of time step range.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAs seen below, selected range is displayed by color frame and labels in plot background. The range determines the  time range for which the objective function is utilized for coloring the curves.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/ObjectiveFunctionsRangeDisplay.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/objectivefunctions/"
             };
@@ -3641,8 +3640,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/analysisplots/"] = {
                 title:    "Analysis Plots",
-                content:  "Analysis Plots are bar charts used to compare summary data at specific timesteps across Ensembles and Summary Cases.\nCreating an Analysis Plot The most convenient way to create an Analysis Plot at a given time step is often to right-click an Ensemble Plot and invoke New Analysis Plot as shown below.\nAlternatively, Analysis Plots can be created by right-clicking the Analysis Plots item in Plot Project Tree.\nHaving created an Analysis Plot, subitems Value Axis and Plot Data Filters emerges in Plot Project Tree. Value Axis allows for settings of title text, layout, and axis formatting. Plot Data Filters enables filtering of data.\nSpecifying Setup and Settings The Analysis Plots property editor allows the user to specify a number of settings and optionally select a reference case in order to analyse vector data relatively to that particular case. The property editor groups further setup and settings as listed below.\nSelected Vectors The summary data to analyze is selected by a set of summary vectors. Press the available button to activate the Summary Adress Selection dialog to select a set of vectors from different ensembles, summary types and summaries.\nTime Steps As shown below, a single or multiple time steps is possible to select. The timestep filter enables the user to skip time steps by years, quarters, months, weeks, or days.\nSorting, Grouping and Coloring As shown below, the bar chart of Analysis Plots can be ordered by a major, medium, and minor grouping precedence according to the following fields:\n Ensemble Case Summary Item Quantity Timestep  In addition, the bar chart may be colored according to these fields, sorted according to signed or absolute value and restricted to top bars.\nLegend and Bar Labels Check the appropriate buttons to display the color legend for the bar chart, bar labels of interest, and font sizes.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsEnsemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAnalysis Plots are bar charts used to compare summary data at specific timesteps across \u003cem\u003eEnsembles\u003c/em\u003e and \u003cem\u003eSummary Cases\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"creating-an-analysis-plot\"\u003eCreating an Analysis Plot\u003c/h2\u003e\n\u003cp\u003eThe most convenient way to create an Analysis Plot at a given time step is often to right-click an \n\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Plot\u003c/a\u003e and invoke \u003cem\u003eNew Analysis Plot\u003c/em\u003e as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsCreateFromEnsemblePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, Analysis Plots can be created by right-clicking the \u003cstrong\u003eAnalysis Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsCreateFromPlotTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHaving created an Analysis Plot, subitems \u003cstrong\u003eValue Axis\u003c/strong\u003e and \u003cstrong\u003ePlot Data Filters\u003c/strong\u003e emerges in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. \u003cstrong\u003eValue Axis\u003c/strong\u003e allows for settings of title text, layout, and axis formatting. \u003cstrong\u003ePlot Data Filters\u003c/strong\u003e enables filtering of data.\u003c/p\u003e\n\u003ch2 id=\"specifying-setup-and-settings\"\u003eSpecifying Setup and Settings\u003c/h2\u003e\n\u003cp\u003eThe Analysis Plots property editor allows the user to specify a number of settings and optionally select a reference case in order to analyse vector data relatively to that particular case. The property editor groups further setup and settings as listed below.\u003c/p\u003e\n\u003ch3 id=\"selected-vectors\"\u003eSelected Vectors\u003c/h3\u003e\n\u003cp\u003eThe summary data to analyze is selected by a set of summary vectors. \nPress the available button to activate the \u003cstrong\u003eSummary Adress Selection\u003c/strong\u003e dialog to select a set of vectors from different ensembles,\nsummary types and summaries.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsSelectedVectors.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\u003cp\u003eAs shown below, a single or multiple time steps is possible to select. The timestep filter enables the user to skip time steps by years, quarters, months, weeks, or days.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsTimeSteps.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"sorting-grouping-and-coloring\"\u003eSorting, Grouping and Coloring\u003c/h3\u003e\n\u003cp\u003eAs shown below, the bar chart of Analysis Plots can be ordered by a major, medium, and minor grouping precedence according to the following fields:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEnsemble\u003c/li\u003e\n\u003cli\u003eCase\u003c/li\u003e\n\u003cli\u003eSummary Item\u003c/li\u003e\n\u003cli\u003eQuantity\u003c/li\u003e\n\u003cli\u003eTimestep\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsGrouping.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn addition, the bar chart may be colored according to these fields, sorted according to signed or absolute value and restricted to top bars.\u003c/p\u003e\n\u003ch3 id=\"legend-and-bar-labels\"\u003eLegend and Bar Labels\u003c/h3\u003e\n\u003cp\u003eCheck the appropriate buttons to display the color legend for the bar chart, bar labels of interest, and font sizes.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsLegendandLabels.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nAnalysis Plots are bar charts used to compare summary data at specific timesteps across Ensembles and Summary Cases.\nCreating an Analysis Plot The most convenient way to create an Analysis Plot at a given time step is often to right-click an Ensemble Plot and invoke New Analysis Plot as shown below.\nAlternatively, Analysis Plots can be created by right-clicking the Analysis Plots item in Plot Project Tree.\nHaving created an Analysis Plot, subitems Value Axis and Plot Data Filters emerges in Plot Project Tree. Value Axis allows for settings of title text, layout, and axis formatting. Plot Data Filters enables filtering of data.\nSpecifying Setup and Settings The Analysis Plots property editor allows the user to specify a number of settings and optionally select a reference case in order to analyse vector data relatively to that particular case. The property editor groups further setup and settings as listed below.\nSelected Vectors The summary data to analyze is selected by a set of summary vectors. Press the available button to activate the Summary Adress Selection dialog to select a set of vectors from different ensembles, summary types and summaries.\nTime Steps As shown below, a single or multiple time steps is possible to select. The timestep filter enables the user to skip time steps by years, quarters, months, weeks, or days.\nSorting, Grouping and Coloring As shown below, the bar chart of Analysis Plots can be ordered by a major, medium, and minor grouping precedence according to the following fields:\nEnsemble Case Summary Item Quantity Timestep In addition, the bar chart may be colored according to these fields, sorted according to signed or absolute value and restricted to top bars.\nLegend and Bar Labels Check the appropriate buttons to display the color legend for the bar chart, bar labels of interest, and font sizes.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsEnsemble.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAnalysis Plots are bar charts used to compare summary data at specific timesteps across \u003cem\u003eEnsembles\u003c/em\u003e and \u003cem\u003eSummary Cases\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"creating-an-analysis-plot\"\u003eCreating an Analysis Plot\u003c/h2\u003e\n\u003cp\u003eThe most convenient way to create an Analysis Plot at a given time step is often to right-click an\n\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Plot\u003c/a\u003e and invoke \u003cem\u003eNew Analysis Plot\u003c/em\u003e as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsCreateFromEnsemblePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, Analysis Plots can be created by right-clicking the \u003cstrong\u003eAnalysis Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsCreateFromPlotTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eHaving created an Analysis Plot, subitems \u003cstrong\u003eValue Axis\u003c/strong\u003e and \u003cstrong\u003ePlot Data Filters\u003c/strong\u003e emerges in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e. \u003cstrong\u003eValue Axis\u003c/strong\u003e allows for settings of title text, layout, and axis formatting. \u003cstrong\u003ePlot Data Filters\u003c/strong\u003e enables filtering of data.\u003c/p\u003e\n\u003ch2 id=\"specifying-setup-and-settings\"\u003eSpecifying Setup and Settings\u003c/h2\u003e\n\u003cp\u003eThe Analysis Plots property editor allows the user to specify a number of settings and optionally select a reference case in order to analyse vector data relatively to that particular case. The property editor groups further setup and settings as listed below.\u003c/p\u003e\n\u003ch3 id=\"selected-vectors\"\u003eSelected Vectors\u003c/h3\u003e\n\u003cp\u003eThe summary data to analyze is selected by a set of summary vectors.\nPress the available button to activate the \u003cstrong\u003eSummary Adress Selection\u003c/strong\u003e dialog to select a set of vectors from different ensembles,\nsummary types and summaries.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsSelectedVectors.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"time-steps\"\u003eTime Steps\u003c/h3\u003e\n\u003cp\u003eAs shown below, a single or multiple time steps is possible to select. The timestep filter enables the user to skip time steps by years, quarters, months, weeks, or days.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsTimeSteps.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"sorting-grouping-and-coloring\"\u003eSorting, Grouping and Coloring\u003c/h3\u003e\n\u003cp\u003eAs shown below, the bar chart of Analysis Plots can be ordered by a major, medium, and minor grouping precedence according to the following fields:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEnsemble\u003c/li\u003e\n\u003cli\u003eCase\u003c/li\u003e\n\u003cli\u003eSummary Item\u003c/li\u003e\n\u003cli\u003eQuantity\u003c/li\u003e\n\u003cli\u003eTimestep\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsGrouping.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn addition, the bar chart may be colored according to these fields, sorted according to signed or absolute value and restricted to top bars.\u003c/p\u003e\n\u003ch3 id=\"legend-and-bar-labels\"\u003eLegend and Bar Labels\u003c/h3\u003e\n\u003cp\u003eCheck the appropriate buttons to display the color legend for the bar chart, bar labels of interest, and font sizes.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/AnalysisPlotsLegendandLabels.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/analysisplots/"
             };
         
@@ -3650,7 +3649,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/gridstatisticsplots/"] = {
                 title:    "Grid Statistics Plots",
-                content:  "Grid Statistics Plots displays the histogram and statistics values for grid cells.\nCreating an Grid Statistics Plot The most convenient way to create an Grid Statistics Plot is often to right-click in the 3D view and invoke Create Grid Statistics Plot as shown below.\nAlternatively, Grid Statistics Plots can be created by right-clicking the Grid Statistics Plots item in Plot Project Tree.\nFilter by 3d View Visibility If you want to display the statistics for a subset of cells, you can select a view to use only the cells visible in that view. This option is activated by selecting a view from the drop down list at Filter by 3d View Visibility\n",
+                content:  "\nGrid Statistics Plots displays the histogram and statistics values for grid cells.\nCreating an Grid Statistics Plot The most convenient way to create an Grid Statistics Plot is often to right-click in the 3D view and invoke Create Grid Statistics Plot as shown below.\nAlternatively, Grid Statistics Plots can be created by right-clicking the Grid Statistics Plots item in Plot Project Tree.\nFilter by 3d View Visibility If you want to display the statistics for a subset of cells, you can select a view to use only the cells visible in that view. This option is activated by selecting a view from the drop down list at Filter by 3d View Visibility\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/GridStatisticsPlots.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eGrid Statistics Plots displays the histogram and statistics values for grid cells.\u003c/p\u003e\n\u003ch2 id=\"creating-an-grid-statistics-plot\"\u003eCreating an Grid Statistics Plot\u003c/h2\u003e\n\u003cp\u003eThe most convenient way to create an Grid Statistics Plot is often to right-click in the 3D view and invoke \u003cem\u003eCreate Grid Statistics Plot\u003c/em\u003e as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridStatisticsPlots_create_from_3d.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, Grid Statistics Plots can be created by right-clicking the \u003cstrong\u003eGrid Statistics Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/GridStatisticsPlots_create_from_project_tree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"filter-by-3d-view-visibility\"\u003eFilter by 3d View Visibility\u003c/h2\u003e\n\u003cp\u003eIf you want to display the statistics for a subset of cells, you can select a view to use only the cells visible in that view. This option is activated by selecting a view from the drop down list at \u003cstrong\u003eFilter by 3d View Visibility\u003c/strong\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/gridstatisticsplots/"
             };
@@ -3659,8 +3658,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/correlationplots/"] = {
                 title:    "Correlation Plots",
-                content:  "Correlation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors. Several visualizations can be created, including tornado plots, correlation matrices, and cross plots.\nCreating a Correlation Plot The most convenient way to create a Correlation Plot at a given time step is often to right-click an Ensemble Plot and invoke the submenu shown below.\nAlternatively, Correlation Plots can be created by right-clicking the Correlation Plots item in Plot Project Tree.\nSpecifying Setup and Settings The Correlation Plots property editor allows the user to specify an extensive number of settings dependent on the actual type of correlation plot. The complete set of settings are listed below according to the individual sections of the property editor.\nCorrelation Factor Settings This section of the property editor allows for setting correlation factor to either Pearson Correlation Coefficient or Spearman\u0026rsquo;s Rank Correlation Coefficient as basis for Correlation Plots and to select ensemble parameter(s) of choice. Being irrelevant, please note that the section will not display for Correlation Cross Plots and that the field Sort Matrix by Values will not display for tornado plots.\nSummary Vector Settings This section of the property editor allows for setting summary vector(s) and time step. To ease the selection of time step, the Time Step Filter may be used to skip time steps by years, quarters, months, weeks, or days.\nPlot Settings This section of the property editor allows for setting plot title, font sizes, and legend if relevant. Please note that the Colors setting for specifying legend is irrelevant to tornado plots and cross plots and will not display for these types of Correlation Plots.\nCross Plot Parameter Setting This section of the property editor will only display for cross plots to allow specification of ensemble parameter to cross plot with summary vector(s).\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsPearsonCoefficient.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eCorrelation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors.\nSeveral visualizations can be created, including tornado plots, correlation matrices, and cross plots.\u003c/p\u003e\n\u003ch2 id=\"creating-a-correlation-plot\"\u003eCreating a Correlation Plot\u003c/h2\u003e\n\u003cp\u003eThe most convenient way to create a Correlation Plot at a given time step is often to right-click an \n\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Plot\u003c/a\u003e and invoke the submenu shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCreateFromEnsemblePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, Correlation Plots can be created by right-clicking the \u003cstrong\u003eCorrelation Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCreateFromPlotTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"specifying-setup-and-settings\"\u003eSpecifying Setup and Settings\u003c/h2\u003e\n\u003cp\u003eThe Correlation Plots property editor allows the user to specify an extensive number of settings dependent on the actual type of correlation plot. The complete set of settings are listed below according to the individual sections of the property editor.\u003c/p\u003e\n\u003ch3 id=\"correlation-factor-settings\"\u003eCorrelation Factor Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting correlation factor to either \u003cem\u003ePearson Correlation Coefficient\u003c/em\u003e or \u003cem\u003eSpearman\u0026rsquo;s Rank Correlation Coefficient\u003c/em\u003e as basis for Correlation Plots and to select ensemble parameter(s) of choice.\nBeing irrelevant, please note that the section will not display for \u003cem\u003eCorrelation Cross Plots\u003c/em\u003e and that the field \u003cem\u003eSort Matrix by Values\u003c/em\u003e will not display for tornado plots.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCorrFactorSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"summary-vector-settings\"\u003eSummary Vector Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting summary vector(s) and time step. \nTo ease the selection of time step, the \u003cem\u003eTime Step Filter\u003c/em\u003e may be used to skip time steps by years, quarters, months, weeks, or days.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsSummaryVectorSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"plot-settings\"\u003ePlot Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting plot title, font sizes, and legend if relevant.\nPlease note that the \u003cem\u003eColors\u003c/em\u003e setting for specifying legend is irrelevant to tornado plots and cross plots and will not display for these types of Correlation Plots.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsPlotSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"cross-plot-parameter-setting\"\u003eCross Plot Parameter Setting\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor will only display for cross plots to allow specification of ensemble parameter to cross plot with summary vector(s).\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCrossPlotSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nCorrelation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors. Several visualizations can be created, including tornado plots, correlation matrices, and cross plots.\nCreating a Correlation Plot The most convenient way to create a Correlation Plot at a given time step is often to right-click an Ensemble Plot and invoke the submenu shown below.\nAlternatively, Correlation Plots can be created by right-clicking the Correlation Plots item in Plot Project Tree.\nSpecifying Setup and Settings The Correlation Plots property editor allows the user to specify an extensive number of settings dependent on the actual type of correlation plot. The complete set of settings are listed below according to the individual sections of the property editor.\nCorrelation Factor Settings This section of the property editor allows for setting correlation factor to either Pearson Correlation Coefficient or Spearman\u0026rsquo;s Rank Correlation Coefficient as basis for Correlation Plots and to select ensemble parameter(s) of choice. Being irrelevant, please note that the section will not display for Correlation Cross Plots and that the field Sort Matrix by Values will not display for tornado plots.\nSummary Vector Settings This section of the property editor allows for setting summary vector(s) and time step. To ease the selection of time step, the Time Step Filter may be used to skip time steps by years, quarters, months, weeks, or days.\nPlot Settings This section of the property editor allows for setting plot title, font sizes, and legend if relevant. Please note that the Colors setting for specifying legend is irrelevant to tornado plots and cross plots and will not display for these types of Correlation Plots.\nCross Plot Parameter Setting This section of the property editor will only display for cross plots to allow specification of ensemble parameter to cross plot with summary vector(s).\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsPearsonCoefficient.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eCorrelation Plots are plots used to visualize correlations between ensemble parameters and summary result vectors.\nSeveral visualizations can be created, including tornado plots, correlation matrices, and cross plots.\u003c/p\u003e\n\u003ch2 id=\"creating-a-correlation-plot\"\u003eCreating a Correlation Plot\u003c/h2\u003e\n\u003cp\u003eThe most convenient way to create a Correlation Plot at a given time step is often to right-click an\n\u003ca href=\"/plot-window/ensembleplotting/\"\u003eEnsemble Plot\u003c/a\u003e and invoke the submenu shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCreateFromEnsemblePlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eAlternatively, Correlation Plots can be created by right-clicking the \u003cstrong\u003eCorrelation Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCreateFromPlotTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"specifying-setup-and-settings\"\u003eSpecifying Setup and Settings\u003c/h2\u003e\n\u003cp\u003eThe Correlation Plots property editor allows the user to specify an extensive number of settings dependent on the actual type of correlation plot. The complete set of settings are listed below according to the individual sections of the property editor.\u003c/p\u003e\n\u003ch3 id=\"correlation-factor-settings\"\u003eCorrelation Factor Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting correlation factor to either \u003cem\u003ePearson Correlation Coefficient\u003c/em\u003e or \u003cem\u003eSpearman\u0026rsquo;s Rank Correlation Coefficient\u003c/em\u003e as basis for Correlation Plots and to select ensemble parameter(s) of choice.\nBeing irrelevant, please note that the section will not display for \u003cem\u003eCorrelation Cross Plots\u003c/em\u003e and that the field \u003cem\u003eSort Matrix by Values\u003c/em\u003e will not display for tornado plots.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCorrFactorSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"summary-vector-settings\"\u003eSummary Vector Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting summary vector(s) and time step.\nTo ease the selection of time step, the \u003cem\u003eTime Step Filter\u003c/em\u003e may be used to skip time steps by years, quarters, months, weeks, or days.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsSummaryVectorSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"plot-settings\"\u003ePlot Settings\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor allows for setting plot title, font sizes, and legend if relevant.\nPlease note that the \u003cem\u003eColors\u003c/em\u003e setting for specifying legend is irrelevant to tornado plots and cross plots and will not display for these types of Correlation Plots.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsPlotSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"cross-plot-parameter-setting\"\u003eCross Plot Parameter Setting\u003c/h3\u003e\n\u003cp\u003eThis section of the property editor will only display for cross plots to allow specification of ensemble parameter to cross plot with summary vector(s).\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/CorrelationPlotsCrossPlotSettings.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/correlationplots/"
             };
         
@@ -3668,7 +3667,7 @@ 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",
+                content:  "\nResInsight 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\nSource 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/"
             };
@@ -3677,7 +3676,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",
+                content:  "\nResInsight features the following capabilities for export of data to reporting or further analysis:\nconvenient 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\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/"
             };
@@ -3686,8 +3685,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 = {\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\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\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",
+                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.\nSingle 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:\nCase 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}\rCaseInfo 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}\rVector[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]\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()**\rIf 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}\rIf 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 {\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}\rIf 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:\n6-------------7 |k /| /| | /j / | / | |/ / | / | *---i 4-------------5 |\r| | | |\r| 2---------|---3\r| / | /\r| / | /\r|/ |/\r0-------------1\rMatrix[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 {\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}\rIf 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}\rIf 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.\rIf 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 {\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}\rIf 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}\rMatrix[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\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\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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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\u0026rdquo;|\u0026ldquo;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/"
             };
         
@@ -3695,8 +3694,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.\nThe values along the different K-layers is available in the Depth Plot\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 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.\n[Result Info]\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\u003cp\u003eThe values along the different K-layers is available in the \u003ca href=\"/3d-main-window/depthplot/\"\u003eDepth Plot\u003c/a\u003e\u003c/p\u003e\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\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\u003eThe 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\u003cp\u003e\u003ca href=\"/3d-main-window/resultinfo/\"\u003e[Result Info]\u003c/a\u003e\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",
+                content:  "\nThe 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.\nThe values along the different K-layers is available in the Depth Plot\nVisibility of the docking widows can be controlled from the Windows menu.\nResult 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 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.\n[Result Info]\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:\nName 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.\nOption 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\u003cp\u003eThe values along the different K-layers is available in the \u003ca href=\"/3d-main-window/depthplot/\"\u003eDepth Plot\u003c/a\u003e\u003c/p\u003e\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\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\u003eThe 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\u003cp\u003e\u003ca href=\"/3d-main-window/resultinfo/\"\u003e[Result Info]\u003c/a\u003e\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/"
             };
         
@@ -3704,8 +3703,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:     "\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",
+                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:\nAll 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/"
             };
         
@@ -3713,8 +3712,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.\u0026quot;\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\u003cp\u003e\u003cstrong\u003eDavid Baxendale\u003cbr\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\u003cbr\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",
+                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",
+                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\u003cbr\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.\u0026rdquo;\u003c/em\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eTor Harald Sandve\u003cbr\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/"
             };
         
@@ -3722,8 +3721,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/filters/"] = {
                 title:    "Filters",
-                content:  "Filters are used to control the visibility of cells in the 3D view. Two types of filters exist:\n Cell Filter \u0026ndash; Extracts subset(s) of grid cells Property Filter \u0026ndash; Extracts cells with a property value matching a value range  The visibility of cells connected to wells, and fences can be controlled from  Simulation Wells.\n(Not applicable for Geomechanical cases)\n\rCommon Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor. The sequence of the filters can be rearranged by clicking the arrow icons of selected filter.\nCell Filters and Property filters can either be set to Include or Exclude the matching cells. The Include setting marks the cells as visible while the Exclude setting is used to remove cells from visualization regardless of other filters. The icon in front of each filter show a + or - sign to indicate Include or Exclude .\nCell Filters Cell Filters enables the user to define a set of visible regions in the 3D view. Each Include cell filter will add cells to the visualization and the resulting 3D view will show the union of all the Include cell filters.\nA new cell filter can be added by invoking the right-click menu for the Cell Filters collection in Project Tree.\nThe available cell filters are:\n  Polygon Filter: Defining a filter by marking target points of a polygon in 3D view to include or exclude matching cells.\n  User Defined Filter: Defining a filter by specifying explicit cells to include or exclude by their IJK-index.\n  Range Filter: Defining a filter to include or exclude cells by specifying IJK-ranges. For radial models, IJ represents angle and radius.\n  Slice Filter: Defining a filter to include or exclude a slice of cells in either I-, J-, or K-direction.\n  The following exemplifies the use of a Polygon Filter and target points. Target points are defined and manipulated in 3D view as decribed in User Defined Polyline Annotations. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\nA filter can be added directly from 3D View by right-clicking a cell using the displayed menu.\n\rBelow is a snapshot of the Property Editor for the Range Filter type of Cell 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 show the index of the start of the active cells. The Width labels show the number of active cells from the start of the active cells.\nProperty Filters Property Filters applies to the results of the Cell 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 property filters.\nA new property filter is created 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 right-click 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:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eFilters are used to control the visibility of cells in the 3D view. Two types of filters exist:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Filter\u003c/strong\u003e \u0026ndash; Extracts subset(s) of grid cells\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 visibility of cells connected to wells, and fences 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\u003ch2 id=\"common-properties-cell-and-property-filters\"\u003eCommon Properties Cell and Property Filters\u003c/h2\u003e\n\u003cp\u003eFilters can be turned on and off using their check-boxes in \u003cstrong\u003eProject Tree\u003c/strong\u003e and controlled by their corresponding \u003cstrong\u003eProperty Editor\u003c/strong\u003e. The sequence of the filters can be rearranged by clicking the arrow icons of selected filter.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersInTreeView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eCell Filters and Property filters can either be set to \u003cstrong\u003eInclude\u003c/strong\u003e or \u003cstrong\u003eExclude\u003c/strong\u003e the matching cells. \nThe \u003cem\u003eInclude\u003c/em\u003e setting marks the cells as visible while the \u003cem\u003eExclude\u003c/em\u003e setting is used to remove cells from visualization regardless of other filters. \nThe icon in front of each filter show a + or - sign to indicate \u003cem\u003eInclude\u003c/em\u003e or \u003cem\u003eExclude\u003c/em\u003e \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=\"cell-filters\"\u003eCell Filters\u003c/h2\u003e\n\u003cp\u003eCell Filters enables the user to define a set of visible regions in the 3D view.\nEach \u003cem\u003eInclude\u003c/em\u003e cell filter will add cells to the visualization and the resulting 3D view will show the union of all the \u003cem\u003eInclude\u003c/em\u003e cell filters.\u003c/p\u003e\n\u003cp\u003eA new cell filter can be added by invoking the right-click menu for the \u003cstrong\u003eCell Filters\u003c/strong\u003e collection in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilterTypes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe available cell filters are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ePolygon Filter\u003c/strong\u003e: Defining a filter by marking target points of a polygon in 3D view to include or exclude matching cells.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eUser Defined Filter\u003c/strong\u003e: Defining a filter by specifying explicit cells to include or exclude by their IJK-index.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eRange Filter\u003c/strong\u003e: Defining a filter to include or exclude cells by specifying IJK-ranges. For radial models, IJ represents angle and radius.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eSlice Filter\u003c/strong\u003e: Defining a filter to include or exclude a slice of cells in either I-, J-, or K-direction.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe following exemplifies the use of a \u003cstrong\u003ePolygon Filter\u003c/strong\u003e and target points. Target points are defined and manipulated in 3D view as decribed in \u003ca href=\"/3d-main-window/annotations/\"\u003eUser Defined Polyline Annotations\u003c/a\u003e. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilter_Polygon.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eA filter can be added directly from \u003cb\u003e3D View\u003c/b\u003e by right-clicking a cell using the displayed menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for the \u003cstrong\u003eRange Filter\u003c/strong\u003e type of Cell Filter:\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.\nThe \u003cstrong\u003eStart\u003c/strong\u003e labels show the index of the start of the active cells.\nThe \u003cstrong\u003eWidth\u003c/strong\u003e labels show 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\u003eCell 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 property filters.\u003c/p\u003e\n\u003cp\u003eA new property filter is created 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 right-click 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\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",
+                content:  "\nFilters are used to control the visibility of cells in the 3D view. Two types of filters exist:\nCell Filter \u0026ndash; Extracts subset(s) of grid cells Property Filter \u0026ndash; Extracts cells with a property value matching a value range The visibility of cells connected to wells, and fences can be controlled from Simulation Wells.\n(Not applicable for Geomechanical cases)\nCommon Properties Cell and Property Filters Filters can be turned on and off using their check-boxes in Project Tree and controlled by their corresponding Property Editor. The sequence of the filters can be rearranged by clicking the arrow icons of selected filter.\nCell Filters and Property filters can either be set to Include or Exclude the matching cells. The Include setting marks the cells as visible while the Exclude setting is used to remove cells from visualization regardless of other filters. The icon in front of each filter show a + or - sign to indicate Include or Exclude .\nCell Filters Cell Filters enables the user to define a set of visible regions in the 3D view. Each Include cell filter will add cells to the visualization and the resulting 3D view will show the union of all the Include cell filters.\nA new cell filter can be added by invoking the right-click menu for the Cell Filters collection in Project Tree.\nThe available cell filters are:\nPolygon Filter: Defining a filter by marking target points of a polygon in 3D view to include or exclude matching cells.\nUser Defined Filter: Defining a filter by specifying explicit cells to include or exclude by their IJK-index.\nRange Filter: Defining a filter to include or exclude cells by specifying IJK-ranges. For radial models, IJ represents angle and radius.\nSlice Filter: Defining a filter to include or exclude a slice of cells in either I-, J-, or K-direction.\nThe following exemplifies the use of a Polygon Filter and target points. Target points are defined and manipulated in 3D view as decribed in User Defined Polyline Annotations. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\nA filter can be added directly from 3D View by right-clicking a cell using the displayed menu.\nBelow is a snapshot of the Property Editor for the Range Filter type of Cell Filter:\nFilter 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 show the index of the start of the active cells. The Width labels show the number of active cells from the start of the active cells.\nProperty Filters Property Filters applies to the results of the Cell 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 property filters.\nA new property filter is created 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 right-click command Apply As Cell Result on a property filter, sets the Cell Color Result to the same values as the selected property filter.\nBelow 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\u003eFilters are used to control the visibility of cells in the 3D view. Two types of filters exist:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCell Filter\u003c/strong\u003e \u0026ndash; Extracts subset(s) of grid cells\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 visibility of cells connected to wells, and fences 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\u003ch2 id=\"common-properties-cell-and-property-filters\"\u003eCommon Properties Cell and Property Filters\u003c/h2\u003e\n\u003cp\u003eFilters can be turned on and off using their check-boxes in \u003cstrong\u003eProject Tree\u003c/strong\u003e and controlled by their corresponding \u003cstrong\u003eProperty Editor\u003c/strong\u003e. The sequence of the filters can be rearranged by clicking the arrow icons of selected filter.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/FiltersInTreeView.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eCell Filters and Property filters can either be set to \u003cstrong\u003eInclude\u003c/strong\u003e or \u003cstrong\u003eExclude\u003c/strong\u003e the matching cells.\nThe \u003cem\u003eInclude\u003c/em\u003e setting marks the cells as visible while the \u003cem\u003eExclude\u003c/em\u003e setting is used to remove cells from visualization regardless of other filters.\nThe icon in front of each filter show a + or - sign to indicate \u003cem\u003eInclude\u003c/em\u003e or \u003cem\u003eExclude\u003c/em\u003e \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=\"cell-filters\"\u003eCell Filters\u003c/h2\u003e\n\u003cp\u003eCell Filters enables the user to define a set of visible regions in the 3D view.\nEach \u003cem\u003eInclude\u003c/em\u003e cell filter will add cells to the visualization and the resulting 3D view will show the union of all the \u003cem\u003eInclude\u003c/em\u003e cell filters.\u003c/p\u003e\n\u003cp\u003eA new cell filter can be added by invoking the right-click menu for the \u003cstrong\u003eCell Filters\u003c/strong\u003e collection in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilterTypes.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe available cell filters are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ePolygon Filter\u003c/strong\u003e: Defining a filter by marking target points of a polygon in 3D view to include or exclude matching cells.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eUser Defined Filter\u003c/strong\u003e: Defining a filter by specifying explicit cells to include or exclude by their IJK-index.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eRange Filter\u003c/strong\u003e: Defining a filter to include or exclude cells by specifying IJK-ranges. For radial models, IJ represents angle and radius.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eSlice Filter\u003c/strong\u003e: Defining a filter to include or exclude a slice of cells in either I-, J-, or K-direction.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe following exemplifies the use of a \u003cstrong\u003ePolygon Filter\u003c/strong\u003e and target points. Target points are defined and manipulated in 3D view as decribed in \u003ca href=\"/3d-main-window/annotations/\"\u003eUser Defined Polyline Annotations\u003c/a\u003e. Vertically, the filter can be set to use the XY target positions or IJK-index of targeted cells. The actual filtering can be specified to whole cells inside polygon, cell center inside polygon, or any cell corner inside polygon.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/CellFilter_Polygon.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eA filter can be added directly from \u003cb\u003e3D View\u003c/b\u003e by right-clicking a cell using the displayed menu.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003cp\u003eBelow is a snapshot of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for the \u003cstrong\u003eRange Filter\u003c/strong\u003e type of Cell Filter:\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.\nThe \u003cstrong\u003eStart\u003c/strong\u003e labels show the index of the start of the active cells.\nThe \u003cstrong\u003eWidth\u003c/strong\u003e labels show 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\u003eCell 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 property filters.\u003c/p\u003e\n\u003cp\u003eA new property filter is created 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)\u0026rdquo;\u003c/em\u003e as you edit the property filter.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe right-click 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\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/"
             };
         
@@ -3731,8 +3730,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 Python interface Command line interface and Command files Octave interface  Python interface ResInsight incorporates a powerful Python interface which allows you to interact with ResInsight and load data for further processing and automation.\nCommand 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.\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\u003ePython interface\u003c/li\u003e\n\u003cli\u003eCommand line interface and Command files\u003c/li\u003e\n\u003cli\u003eOctave interface\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"python-interface\"\u003ePython interface\u003c/h2\u003e\n\u003cp\u003eResInsight incorporates a powerful Python interface which allows you to interact with ResInsight and load data for further processing and automation.\u003c/p\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/) for automation via shell scripts. \nBy gathering commands into a \u003ca href=\"/scripting/commandfile/\"\u003eCommand file\u003c/a\u003e, you may run a sequence of commands by supplying the \ncommand file as a \u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\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",
+                content:  "\nResInsight provides powerful and flexible mechanisms for post-processing of results and automation by its scripting interfaces:\nPython interface Command line interface and Command files Octave interface Python interface ResInsight incorporates a powerful Python interface which allows you to interact with ResInsight and load data for further processing and automation.\nCommand 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.\nOctave Interface By the interface to Octave you will find:\nOctave 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\u003ePython interface\u003c/li\u003e\n\u003cli\u003eCommand line interface and Command files\u003c/li\u003e\n\u003cli\u003eOctave interface\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"python-interface\"\u003ePython interface\u003c/h2\u003e\n\u003cp\u003eResInsight incorporates a powerful Python interface which allows you to interact with ResInsight and load data for further processing and automation.\u003c/p\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/) for automation via shell scripts.\nBy gathering commands into a \u003ca href=\"/scripting/commandfile/\"\u003eCommand file\u003c/a\u003e, you may run a sequence of commands by supplying the\ncommand file as a \u003ca href=\"/scripting/commandlineinterface/\"\u003ecommand line parameter\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/"
             };
         
@@ -3740,8 +3739,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), True Vertical Depth RKB (TVDRKB) 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.\nDepth Marker Line If there are multiple tracks in the same plot, it can be useful to show a horizontal line across the plot based on the location of the mouse cursor. This can be activated from the Property Editor of a Well Log Plot.\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 right-click 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. For GeoMechanical models, adding formations will also indicate the sea level.\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:     "\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-true-vertical-depth-rkb-tvdrkb-and-pseudo-length-pl\"\u003eMeasured Depth (MD), True Vertical Depth (TVD), True Vertical Depth RKB (TVDRKB) 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=\"depth-marker-line\"\u003eDepth Marker Line\u003c/h3\u003e\n\u003cp\u003eIf there are multiple tracks in the same plot, it can be useful to show a horizontal line across the plot based on the location of the mouse cursor. This can be activated from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of a \u003cstrong\u003eWell Log Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/well-log-track-depth-axis.png\" alt=\"\"\u003e\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 right-click 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 \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e in \u003cem\u003eCategory colors\u003c/em\u003e. For GeoMechanical models, adding formations will also indicate the sea level.\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 \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\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=\"/calculated-data/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 \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\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",
+                content:  "\nResInsight 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:\nRight-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), True Vertical Depth RKB (TVDRKB) 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.\nDepth Marker Line If there are multiple tracks in the same plot, it can be useful to show a horizontal line across the plot based on the location of the mouse cursor. This can be activated from the Property Editor of a Well Log Plot.\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 right-click 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. For GeoMechanical models, adding formations will also indicate the sea level.\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.\nCurve 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:\nCase \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.\nLAS-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.\nExport 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-true-vertical-depth-rkb-tvdrkb-and-pseudo-length-pl\"\u003eMeasured Depth (MD), True Vertical Depth (TVD), True Vertical Depth RKB (TVDRKB) 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=\"depth-marker-line\"\u003eDepth Marker Line\u003c/h3\u003e\n\u003cp\u003eIf there are multiple tracks in the same plot, it can be useful to show a horizontal line across the plot based on the location of the mouse cursor. This can be activated from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e of a \u003cstrong\u003eWell Log Plot\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/well-log-track-depth-axis.png\" alt=\"\"\u003e\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 right-click 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 \u003ca href=\"/3d-main-window/formations/\"\u003eFormations\u003c/a\u003e in \u003cem\u003eCategory colors\u003c/em\u003e. For GeoMechanical models, adding formations will also indicate the sea level.\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 \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\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=\"/calculated-data/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 \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\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/"
             };
         
@@ -3749,8 +3748,8 @@ if (!doNotTrack) {
          
             window.store["/wells-and-completions/wellmeasurements/"] = {
                 title:    "Well Measurements",
-                content:  "ResInsight can import well measurements from a comma-separated values file.\nImporting Well Measurements The command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Measurements will read well measurements from the selected files, and create one entry for each file under the Wells -\u0026gt; Well Measurements item in the Project Tree.\nFile Format The format is comma-separated values with one measurement per line. The following requirements have to be met:\n Each data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment. The values must be separated by commas. Lines starting with \u0026quot;#\u0026quot; is considered to be comment lines, and will be ignored. Blank lines are also ignored.  Example 1: # Example well measurements csv file.\r# This is a comment\r#\r# Well Name, MD, Date, Kind, Value, Quality, Comment\rC-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test\rC-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test\rC-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test\rC-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test\rE-3 H, 634.12, 2005-10-24, DP, 0.0, 0, Wash outs\rE-3 H, 1000.12, 2005-10-24, DP, 0.0, 0, Wash outs\rMeasurement properties  Well Name \u0026ndash; The name of the well. ResInsight will try to associate each measurement with a well path with a matching name. The well name should be the same as imported here. MD \u0026ndash; Measured depth. Date \u0026ndash; The date of the measurement. Expects ISO 8601 extended format: yyyy-MM-dd, e.g. 2019-12-24. Kind \u0026ndash; The type of measurement. Value \u0026ndash; Floating point value. Quality \u0026ndash; Integer describing the quality of the measurement. Comment \u0026ndash; Short description of the measurement.  Reloading Well Measurements The well measurements are copied into the ResInsight project. Each measurement is linked to the file it was imported from. The contents of the file can be reloaded by right-clicking on one of the files under Wells -\u0026gt; Well Measurements and selecting Reload.\nReloading measurements from a file will delete all the previously imported measurements from this particular file, and then reimport the current contents of the file.\n\rWell Measurements Visualization All the imported well measurements are available Project Tree under the Well Measurements for each 3D view.\nThe measurements are shown in all the 3D Views in the project as cylinders on the well path at the specified MD. Double-clicking on measurement will show details in the Result Info panel.\nWell Measurement Property Editor The well measurement property editor lets the user filter which measurement to show based on quality, value and measurement kind. The value of the measurement is used to determine the color, and this changed in the Color Legend.\n Value Filter Settings \u0026ndash; Filter measurements by value range. Wells \u0026ndash; Show this measurement kind for the selected wells. Quality \u0026ndash; Filter by measurement quality. Radius Scale \u0026ndash; Scale the radius of well measurement in the 3D view. Relative to the radius of the well path.  ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResInsight_WellMeasurements.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can import well measurements from a comma-separated values file.\u003c/p\u003e\n\u003ch2 id=\"importing-well-measurements\"\u003eImporting Well Measurements\u003c/h2\u003e\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Measurements\u003c/strong\u003e will read well measurements from the selected files, and create one entry for each file 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 -\u0026gt; Well Measurements\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"file-format\"\u003eFile Format\u003c/h2\u003e\n\u003cp\u003eThe format is comma-separated values with one measurement per line. The following requirements have to be met:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEach data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment.\u003c/li\u003e\n\u003cli\u003eThe values must be separated by commas.\u003c/li\u003e\n\u003cli\u003eLines starting with \u003ccode\u003e\u0026quot;#\u0026quot;\u003c/code\u003e is considered to be comment lines, and will be ignored.\u003c/li\u003e\n\u003cli\u003eBlank lines are also ignored.\u003c/li\u003e\n\u003c/ul\u003e\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-txt\" data-lang=\"txt\"\u003e# Example well measurements csv file.\r\n# This is a comment\r\n#\r\n# Well Name, MD, Date, Kind, Value, Quality, Comment\r\nC-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test\r\nC-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test\r\nC-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test\r\nC-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test\r\nE-3 H,  634.12, 2005-10-24, DP,    0.0, 0, Wash outs\r\nE-3 H, 1000.12, 2005-10-24, DP,    0.0, 0, Wash outs\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"measurement-properties\"\u003eMeasurement properties\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; The name of the well. ResInsight will try to associate each measurement with a well path with a matching name. The well name should be the same as imported \u003ca href=\"/wells-and-completions/wellpaths/\"\u003ehere\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD\u003c/strong\u003e \u0026ndash; Measured depth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate\u003c/strong\u003e \u0026ndash; The date of the measurement. Expects \u003ca href=\"https://en.wikipedia.org/wiki/ISO_8601#Calendar_dates\"\u003eISO 8601\u003c/a\u003e extended format: \u003ccode\u003eyyyy-MM-dd\u003c/code\u003e, e.g. \u003ccode\u003e2019-12-24\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKind\u003c/strong\u003e \u0026ndash; The type of measurement.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eValue\u003c/strong\u003e \u0026ndash; Floating point value.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eQuality\u003c/strong\u003e \u0026ndash; Integer describing the quality of the measurement.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eComment\u003c/strong\u003e \u0026ndash; Short description of the measurement.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"reloading-well-measurements\"\u003eReloading Well Measurements\u003c/h3\u003e\n\u003cp\u003eThe well measurements are copied into the ResInsight project. Each measurement is linked to the file it was imported from. The contents of the file can be reloaded by right-clicking on one of the files under \u003cstrong\u003eWells -\u0026gt; Well Measurements\u003c/strong\u003e and selecting \u003cstrong\u003eReload\u003c/strong\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eReloading measurements from a file will delete all the previously imported measurements from this particular file, and then reimport the current contents of the file.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"well-measurements-visualization\"\u003eWell Measurements Visualization\u003c/h2\u003e\n\u003cp\u003eAll the imported well measurements are available \u003cstrong\u003eProject Tree\u003c/strong\u003e under the \u003cstrong\u003eWell Measurements\u003c/strong\u003e for each 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellMeasurementsInTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe measurements are shown in all the 3D Views in the project as cylinders on the well path at the specified MD. Double-clicking on measurement will show details in the \u003cstrong\u003eResult Info\u003c/strong\u003e panel.\u003c/p\u003e\n\u003ch3 id=\"well-measurement-property-editor\"\u003eWell Measurement Property Editor\u003c/h3\u003e\n\u003cp\u003eThe well measurement property editor lets the user filter which measurement to show based on quality, value and measurement kind. The value of the measurement is used to determine the color, and this changed in the \u003cstrong\u003eColor Legend\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellMeasurementsPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Filter Settings\u003c/strong\u003e \u0026ndash; Filter measurements by value range.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWells\u003c/strong\u003e \u0026ndash; Show this measurement kind for the selected wells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eQuality\u003c/strong\u003e \u0026ndash; Filter by measurement quality.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRadius Scale\u003c/strong\u003e \u0026ndash; Scale the radius of well measurement in the 3D view. Relative to the radius of the well path.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "\nResInsight can import well measurements from a comma-separated values file.\nImporting Well Measurements The command File -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Measurements will read well measurements from the selected files, and create one entry for each file under the Wells -\u0026gt; Well Measurements item in the Project Tree.\nFile Format The format is comma-separated values with one measurement per line. The following requirements have to be met:\nEach data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment. The values must be separated by commas. Lines starting with \u0026quot;#\u0026quot; is considered to be comment lines, and will be ignored. Blank lines are also ignored. Example 1: # Example well measurements csv file. # This is a comment # # Well Name, MD, Date, Kind, Value, Quality, Comment C-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test C-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test C-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test C-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test E-3 H, 634.12, 2005-10-24, DP, 0.0, 0, Wash outs E-3 H, 1000.12, 2005-10-24, DP, 0.0, 0, Wash outs Measurement properties Well Name \u0026ndash; The name of the well. ResInsight will try to associate each measurement with a well path with a matching name. The well name should be the same as imported here. MD \u0026ndash; Measured depth. Date \u0026ndash; The date of the measurement. Expects ISO 8601 extended format: yyyy-MM-dd, e.g. 2019-12-24. Kind \u0026ndash; The type of measurement. Value \u0026ndash; Floating point value. Quality \u0026ndash; Integer describing the quality of the measurement. Comment \u0026ndash; Short description of the measurement. Reloading Well Measurements The well measurements are copied into the ResInsight project. Each measurement is linked to the file it was imported from. The contents of the file can be reloaded by right-clicking on one of the files under Wells -\u0026gt; Well Measurements and selecting Reload.\nReloading measurements from a file will delete all the previously imported measurements from this particular file, and then reimport the current contents of the file.\nWell Measurements Visualization All the imported well measurements are available Project Tree under the Well Measurements for each 3D view.\nThe measurements are shown in all the 3D Views in the project as cylinders on the well path at the specified MD. Double-clicking on measurement will show details in the Result Info panel.\nWell Measurement Property Editor The well measurement property editor lets the user filter which measurement to show based on quality, value and measurement kind. The value of the measurement is used to determine the color, and this changed in the Color Legend.\nValue Filter Settings \u0026ndash; Filter measurements by value range. Wells \u0026ndash; Show this measurement kind for the selected wells. Quality \u0026ndash; Filter by measurement quality. Radius Scale \u0026ndash; Scale the radius of well measurement in the 3D view. Relative to the radius of the well path. ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/ResInsight_WellMeasurements.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight can import well measurements from a comma-separated values file.\u003c/p\u003e\n\u003ch2 id=\"importing-well-measurements\"\u003eImporting Well Measurements\u003c/h2\u003e\n\u003cp\u003eThe command \u003cstrong\u003eFile -\u0026gt; Import -\u0026gt; Well Data -\u0026gt; Import Measurements\u003c/strong\u003e will read well measurements from the selected files, and create one entry for each file 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 -\u0026gt; Well Measurements\u003c/strong\u003e item in the \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"file-format\"\u003eFile Format\u003c/h2\u003e\n\u003cp\u003eThe format is comma-separated values with one measurement per line. The following requirements have to be met:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eEach data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment.\u003c/li\u003e\n\u003cli\u003eThe values must be separated by commas.\u003c/li\u003e\n\u003cli\u003eLines starting with \u003ccode\u003e\u0026quot;#\u0026quot;\u003c/code\u003e is considered to be comment lines, and will be ignored.\u003c/li\u003e\n\u003cli\u003eBlank lines are also ignored.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"example-1\"\u003eExample 1:\u003c/h4\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# Example well measurements csv file.\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# This is a comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# Well Name, MD, Date, Kind, Value, Quality, Comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eC-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eC-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eC-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eC-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eE-3 H,  634.12, 2005-10-24, DP,    0.0, 0, Wash outs\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eE-3 H, 1000.12, 2005-10-24, DP,    0.0, 0, Wash outs\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"measurement-properties\"\u003eMeasurement properties\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eWell Name\u003c/strong\u003e \u0026ndash; The name of the well. ResInsight will try to associate each measurement with a well path with a matching name. The well name should be the same as imported \u003ca href=\"/wells-and-completions/wellpaths/\"\u003ehere\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eMD\u003c/strong\u003e \u0026ndash; Measured depth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDate\u003c/strong\u003e \u0026ndash; The date of the measurement. Expects \u003ca href=\"https://en.wikipedia.org/wiki/ISO_8601#Calendar_dates\"\u003eISO 8601\u003c/a\u003e extended format: \u003ccode\u003eyyyy-MM-dd\u003c/code\u003e, e.g. \u003ccode\u003e2019-12-24\u003c/code\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eKind\u003c/strong\u003e \u0026ndash; The type of measurement.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eValue\u003c/strong\u003e \u0026ndash; Floating point value.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eQuality\u003c/strong\u003e \u0026ndash; Integer describing the quality of the measurement.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eComment\u003c/strong\u003e \u0026ndash; Short description of the measurement.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"reloading-well-measurements\"\u003eReloading Well Measurements\u003c/h3\u003e\n\u003cp\u003eThe well measurements are copied into the ResInsight project. Each measurement is linked to the file it was imported from. The contents of the file can be reloaded by right-clicking on one of the files under \u003cstrong\u003eWells -\u0026gt; Well Measurements\u003c/strong\u003e and selecting \u003cstrong\u003eReload\u003c/strong\u003e.\u003c/p\u003e\n\r\n\u003cdiv class=\"notices info\" \u003e\u003cp\u003eReloading measurements from a file will delete all the previously imported measurements from this particular file, and then reimport the current contents of the file.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"well-measurements-visualization\"\u003eWell Measurements Visualization\u003c/h2\u003e\n\u003cp\u003eAll the imported well measurements are available \u003cstrong\u003eProject Tree\u003c/strong\u003e under the \u003cstrong\u003eWell Measurements\u003c/strong\u003e for each 3D view.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellMeasurementsInTree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe measurements are shown in all the 3D Views in the project as cylinders on the well path at the specified MD. Double-clicking on measurement will show details in the \u003cstrong\u003eResult Info\u003c/strong\u003e panel.\u003c/p\u003e\n\u003ch3 id=\"well-measurement-property-editor\"\u003eWell Measurement Property Editor\u003c/h3\u003e\n\u003cp\u003eThe well measurement property editor lets the user filter which measurement to show based on quality, value and measurement kind. The value of the measurement is used to determine the color, and this changed in the \u003cstrong\u003eColor Legend\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/WellMeasurementsPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Filter Settings\u003c/strong\u003e \u0026ndash; Filter measurements by value range.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWells\u003c/strong\u003e \u0026ndash; Show this measurement kind for the selected wells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eQuality\u003c/strong\u003e \u0026ndash; Filter by measurement quality.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eRadius Scale\u003c/strong\u003e \u0026ndash; Scale the radius of well measurement in the 3D view. Relative to the radius of the well path.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/wells-and-completions/wellmeasurements/"
             };
         
@@ -3758,7 +3757,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/declinecurveanalysis/"] = {
                 title:    "Decline Curve Analysis",
-                content:  "Create Decline Curves Decline curves can be created from the right-click menu for a curve in the Plot Project Tree.\nThree decline curves are created, and the values for the decline curves can be inspected visually in the plot and values can be displayed using Show Plot Data from the menu inside the plot window.\nOrigins J.J. Arps [1] concluded that the decline in oil production rate ($q_i$) over time can be described by these equations:\n$$\\frac{ 1 }{ q_0 } \\frac{\\partial q_0}{ \\partial t} = -D$$\nwhere the decline rate, $D$ is a time-dependent function:\n$$D = \\frac{D_i}{1+bD_i t}$$\nwhere:\n $q_0$ is the production rate (e.g. oil production) in a unit of choice (e.g STB/day) $t$ is the time $D$ is the time dependent decline rate $D_i$ is the initial decline rate (constant) $b$ is a dimensionless constant (typically used as a tuning parameter to match actual field data) and is in the range of $ 0 \u0026lt;= b \u0026lt;= 1 $.  The equations can be used to forecast future reservoir and well production.\nBased on the value of $b$ in the function, Arps classified the decline curves into three types:\n The exponential decline has $b = 0$. The harmonic decline has $b = 1$. The hyperbolic decline has $b$ ranges between 0 and 1.  It is important to note that the decline curve is an empirical model and assumes a simplified representation of the complex physical and geological factors affecting production decline.\nRate-Time Decline Curves Exponential Decline Exponential decline is the production decline when $ b = 0 $. This gives a constant decline ($D_i = D$).\n$$q_0 = q_i e^{-Dt }$$\nHyperbolic Decline Hyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\n$$q_0 = \\frac{q_i}{ (1+bD_i t )^\\frac{1}{b} }$$\nHarmonic Decline Harmonic decline is the production decline when $b = 1$:\n$$q_0 = \\frac{q_i}{ (1+D_i t ) }$$\nRate-Cumulative Production Decline Curves Exponential Decline Exponential decline is the production decline when $b = 0$. This gives a constant decline ($D_i = D$).\n$$N_p = \\frac{q_i - q_0}{D}$$\nHyperbolic Decline Hyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\n$$N_p = \\frac{q_i^b}{D_i(1-b)} [q_i^{(1-b)} - q_0^{(1-b)}]$$\nHarmonic Decline Harmonic decline is the production decline when $ b = 1 $:\n$$N_p = \\frac{q_i}{ D_i } * \\ln(\\frac{q_i}{ q_0} )$$\nDecline Rate The continuous decline rate ($D_i$) can be determined from production history data. Using production rate and time data the value is the slope of the straight line on a semi-log plot. Taking two points on from the data $(t_1, q_1)$ and $(t_2, q_2)$:\n$$D_i = \\frac{1}{t_2 - t_1} \\ln(\\frac{q_1}{q_2})$$\nwhere:\n $t_1$ is the time of the first point. $q_1$ is the production rate in the first point. $t_2$ is the time of the second point. $q_2$ is the production rate in the second point.  References [1] Arps, J. J.: “Analysis of Decline Curves,” SPE-945228-G, Trans. of the AIME (1945)\n",
+                content:  "\nCreate Decline Curves Decline curves can be created from the right-click menu for a curve in the Plot Project Tree.\nThree decline curves are created, and the values for the decline curves can be inspected visually in the plot and values can be displayed using Show Plot Data from the menu inside the plot window.\nOrigins J.J. Arps [1] concluded that the decline in oil production rate ($q_i$) over time can be described by these equations:\n$$\\frac{ 1 }{ q_0 } \\frac{\\partial q_0}{ \\partial t} = -D$$\nwhere the decline rate, $D$ is a time-dependent function:\n$$D = \\frac{D_i}{1+bD_i t}$$\nwhere:\n$q_0$ is the production rate (e.g. oil production) in a unit of choice (e.g STB/day) $t$ is the time $D$ is the time dependent decline rate $D_i$ is the initial decline rate (constant) $b$ is a dimensionless constant (typically used as a tuning parameter to match actual field data) and is in the range of $ 0 \u0026lt;= b \u0026lt;= 1 $. The equations can be used to forecast future reservoir and well production.\nBased on the value of $b$ in the function, Arps classified the decline curves into three types:\nThe exponential decline has $b = 0$. The harmonic decline has $b = 1$. The hyperbolic decline has $b$ ranges between 0 and 1. It is important to note that the decline curve is an empirical model and assumes a simplified representation of the complex physical and geological factors affecting production decline.\nRate-Time Decline Curves Exponential Decline Exponential decline is the production decline when $ b = 0 $. This gives a constant decline ($D_i = D$).\n$$q_0 = q_i e^{-Dt }$$\nHyperbolic Decline Hyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\n$$q_0 = \\frac{q_i}{ (1+bD_i t )^\\frac{1}{b} }$$\nHarmonic Decline Harmonic decline is the production decline when $b = 1$:\n$$q_0 = \\frac{q_i}{ (1+D_i t ) }$$\nRate-Cumulative Production Decline Curves Exponential Decline Exponential decline is the production decline when $b = 0$. This gives a constant decline ($D_i = D$).\n$$N_p = \\frac{q_i - q_0}{D}$$\nHyperbolic Decline Hyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\n$$N_p = \\frac{q_i^b}{D_i(1-b)} [q_i^{(1-b)} - q_0^{(1-b)}]$$\nHarmonic Decline Harmonic decline is the production decline when $ b = 1 $:\n$$N_p = \\frac{q_i}{ D_i } * \\ln(\\frac{q_i}{ q_0} )$$\nDecline Rate The continuous decline rate ($D_i$) can be determined from production history data. Using production rate and time data the value is the slope of the straight line on a semi-log plot. Taking two points on from the data $(t_1, q_1)$ and $(t_2, q_2)$:\n$$D_i = \\frac{1}{t_2 - t_1} \\ln(\\frac{q_1}{q_2})$$\nwhere:\n$t_1$ is the time of the first point. $q_1$ is the production rate in the first point. $t_2$ is the time of the second point. $q_2$ is the production rate in the second point. References [1] Arps, J. J.: “Analysis of Decline Curves,” SPE-945228-G, Trans. of the AIME (1945)\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/DeclineCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-decline-curves\"\u003eCreate Decline Curves\u003c/h2\u003e\n\u003cp\u003eDecline curves can be created from the right-click menu for a curve in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThree decline curves are created, and the values for the decline curves can be inspected visually in the plot and values can be displayed using \u003cstrong\u003eShow Plot Data\u003c/strong\u003e from the menu inside the plot window.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/DeclineCurves_create.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"origins\"\u003eOrigins\u003c/h2\u003e\n\u003cp\u003eJ.J. Arps \u003ca href=\"#1\"\u003e[1]\u003c/a\u003e concluded that the decline in oil production rate ($q_i$) over time can be described by these equations:\u003c/p\u003e\n\u003cp\u003e$$\\frac{ 1 }{ q_0 }  \\frac{\\partial q_0}{ \\partial t}  = -D$$\u003c/p\u003e\n\u003cp\u003ewhere the decline rate, $D$ is a time-dependent function:\u003c/p\u003e\n\u003cp\u003e$$D = \\frac{D_i}{1+bD_i t}$$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$q_0$ is the production rate (e.g. oil production) in a unit of choice (e.g STB/day)\u003c/li\u003e\n\u003cli\u003e$t$ is the time\u003c/li\u003e\n\u003cli\u003e$D$ is the time dependent decline rate\u003c/li\u003e\n\u003cli\u003e$D_i$ is the initial decline rate (constant)\u003c/li\u003e\n\u003cli\u003e$b$ is a dimensionless constant (typically used as a tuning parameter to match actual field data) and is in the range of $ 0 \u0026lt;= b \u0026lt;= 1 $.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe equations can be used to forecast future reservoir and well production.\u003c/p\u003e\n\u003cp\u003eBased on the value of $b$ in the function, Arps classified the decline curves into three types:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe exponential decline has $b = 0$.\u003c/li\u003e\n\u003cli\u003eThe harmonic decline has $b = 1$.\u003c/li\u003e\n\u003cli\u003eThe hyperbolic decline has $b$ ranges between 0 and 1.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIt is important to note that the decline curve is an empirical model and assumes a simplified representation of the complex physical and geological factors affecting production decline.\u003c/p\u003e\n\u003ch2 id=\"rate-time-decline-curves\"\u003eRate-Time Decline Curves\u003c/h2\u003e\n\u003ch3 id=\"exponential-decline\"\u003eExponential Decline\u003c/h3\u003e\n\u003cp\u003eExponential decline is the production decline when $ b = 0 $. This gives a constant decline  ($D_i = D$).\u003c/p\u003e\n\u003cp\u003e$$q_0 = q_i e^{-Dt }$$\u003c/p\u003e\n\u003ch3 id=\"hyperbolic-decline\"\u003eHyperbolic Decline\u003c/h3\u003e\n\u003cp\u003eHyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\u003c/p\u003e\n\u003cp\u003e$$q_0 = \\frac{q_i}{ (1+bD_i t )^\\frac{1}{b} }$$\u003c/p\u003e\n\u003ch3 id=\"harmonic-decline\"\u003eHarmonic Decline\u003c/h3\u003e\n\u003cp\u003eHarmonic decline is the production decline when $b = 1$:\u003c/p\u003e\n\u003cp\u003e$$q_0 = \\frac{q_i}{ (1+D_i t ) }$$\u003c/p\u003e\n\u003ch2 id=\"rate-cumulative-production-decline-curves\"\u003eRate-Cumulative Production Decline Curves\u003c/h2\u003e\n\u003ch3 id=\"exponential-decline-1\"\u003eExponential Decline\u003c/h3\u003e\n\u003cp\u003eExponential decline is the production decline when $b = 0$. This gives a constant decline  ($D_i = D$).\u003c/p\u003e\n\u003cp\u003e$$N_p = \\frac{q_i - q_0}{D}$$\u003c/p\u003e\n\u003ch3 id=\"hyperbolic-decline-1\"\u003eHyperbolic Decline\u003c/h3\u003e\n\u003cp\u003eHyperbolic decline is the generic case where $ 0 \u0026lt; b \u0026lt; 1 $.\u003c/p\u003e\n\u003cp\u003e$$N_p = \\frac{q_i^b}{D_i(1-b)} [q_i^{(1-b)} - q_0^{(1-b)}]$$\u003c/p\u003e\n\u003ch3 id=\"harmonic-decline-1\"\u003eHarmonic Decline\u003c/h3\u003e\n\u003cp\u003eHarmonic decline is the production decline when $ b = 1 $:\u003c/p\u003e\n\u003cp\u003e$$N_p = \\frac{q_i}{ D_i } * \\ln(\\frac{q_i}{ q_0} )$$\u003c/p\u003e\n\u003ch2 id=\"decline-rate\"\u003eDecline Rate\u003c/h2\u003e\n\u003cp\u003eThe continuous decline rate ($D_i$) can be determined from production history data. Using production rate and time data the value is the slope of the straight line on a semi-log plot. Taking two points on from the data $(t_1, q_1)$ and $(t_2, q_2)$:\u003c/p\u003e\n\u003cp\u003e$$D_i = \\frac{1}{t_2 - t_1} \\ln(\\frac{q_1}{q_2})$$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$t_1$ is the time of the first point.\u003c/li\u003e\n\u003cli\u003e$q_1$ is the production rate in the first point.\u003c/li\u003e\n\u003cli\u003e$t_2$ is the time of the second point.\u003c/li\u003e\n\u003cli\u003e$q_2$ is the production rate in the second point.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"references\"\u003eReferences\u003c/h2\u003e\n\u003cp\u003e\u003ca id=\"1\"\u003e[1]\u003c/a\u003e\nArps, J. J.: “Analysis of Decline Curves,” SPE-945228-G, Trans. of the AIME (1945)\u003c/p\u003e\n",
                 url:      "/plot-window/declinecurveanalysis/"
             };
@@ -3767,8 +3766,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/intersections/"] = {
                 title:    "Intersections",
-                content:  "Intersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. There are two main types of intersections:\n  Intersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.\n  Intersection Box: can be used as a box cutting grid cells or collapsed to a restricted axis aligned plane.\n  Structural uncertainty can be visualized on intersections as described in Ensemble Surface.\nAll types of intersections are stored in the folder Intersections of a View. An intersection may be copied to other views by the menu option Copy intersections to all views in case in the right-click menu.\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. They 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 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 edit the name, but it will be updated if you change well or well path. Intersecting Geometry \u0026ndash; Options to control the curve used for the cross section dependant on the type of intersection. Depth Filter \u0026ndash; Controls the depth/z-range for visible geometry. Can be controlled from the Intersections folder object. K Range Filter \u0026ndash; Controls the visible K slices. Can be controlled from the Intersections folder object.  Advanced options  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 intersection geometry.  Direction is used to extrude the curve in the defined direction, and thereby create a set of planes. Horizontal implies the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line. By Defined by two points, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\nWell Path Intersections A new Well Path intersection can be created by right-clicking the well path in the 3D view or in the Project Tree.\nA 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 point list is light pink when additional points can be picked in 3D view. To finish adding points, click button Stop picking points (color of point list turns white).  The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), press button Start picking points again.\nThe point list can be copied to clipboard using CTRL-C when in keyboard focus. 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 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 point list is light pink when additional points can be picked in 3D view. To finish adding points, click button Stop picking points (color of point list turns white).  The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, press button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when in keyboard focus. 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:\n Dip: angle between the horizontal plane and down. Azimuth: angle between North and the plane. Changing azimuth will rotate the plane about the first point picked in 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.\nA 2D Intersection View is shown either by right clicking an intersection and select Show 2D intersection View or by checking its entry in Project tree.\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 view. The default name combines the name of the origin view and intersection name. Background \u0026ndash; Color of the viewer background Disable Results Lighting \u0026ndash; Toggle the light effect. When turned off, the colors are easier to compare with legend, but carry no visual cue to visualize 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 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 incremental changes for slider when XY values are changed (default value 1.0) Depth Slider Step Size \u0026ndash; Defines incremental changes for slider when depth values are 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.\nDepth and Range Filter An intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined Depth Filter. Depth filtering is performed by selecting an intersection in Project Tree and setting Depth Filter properties in Property Editor:\n None: no depth filtering Above: show above the specified Depth Below: show below the specified Depth Between: show between the specified Upper Depth and the specified Lower Depth  An intersection can be also be visually filtered by a user defined K Range Filter. K Range filtering is performed by enabling K Range Filter of an intersection. The filtering is defined using a text string, i.e. \u0026ldquo;5,10-15,20:3\u0026rdquo;, see Advanced Text Input for details.\nFilter Options for all Intersections The filtering of all intersections can be controlled when selecting the Intersections folder object. Activating these options will override the settings defined locally on each intersection.\nSimilar options can also be activated for Faults.\nIntersection Results To select a simulation result to display on an intersection, right-click Intersection Results in Project Tree and select New Result Definition.\nBy selecting a specific Intersection Result, the Property Editor allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.\nThe next step is to select an Intersection in Project Tree and define Result Reference. In the example below, available sources are the two Intersections Results of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIntersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. \nThere are two main types of intersections:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eIntersection\u003c/strong\u003e: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An  intersection can also be shown in a separate \u003ca href=\"/3d-main-window/intersections/#2d-intersection-views\"\u003e2D Intersection View\u003c/a\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eIntersection Box\u003c/strong\u003e: can be used as a box cutting grid cells or collapsed to a restricted axis aligned plane.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eStructural uncertainty can be visualized on intersections as described in \u003ca href=\"/workflows/ensemblesurface/\"\u003eEnsemble Surface\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eAll types of intersections are stored in the folder \u003cstrong\u003eIntersections\u003c/strong\u003e of a \u003cstrong\u003eView\u003c/strong\u003e. An intersection may be copied to other views by the menu option \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e in the right-click menu.\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 Intersections\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. They 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 \u003cb\u003eGrids\u003c/b\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e or activating the \u003cb\u003eHide Grid Cells\u003c/b\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 edit the name, but it will be updated if you change well or well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntersecting Geometry\u003c/strong\u003e \u0026ndash; Options to control the curve used for the cross section dependant on the type of intersection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Filter\u003c/strong\u003e \u0026ndash; Controls the depth/z-range for visible geometry. Can be controlled from the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eK Range Filter\u003c/strong\u003e \u0026ndash; Controls the visible K slices. Can be controlled from the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"advanced-options\"\u003eAdvanced options\u003c/h4\u003e\n\u003cul\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 intersection geometry.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eDirection\u003c/strong\u003e is used to extrude the curve in the defined direction, and thereby create a set of planes. \u003cstrong\u003eHorizontal\u003c/strong\u003e implies the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\nBy \u003cstrong\u003eDefined by two points\u003c/strong\u003e, 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\u003ch3 id=\"well-path-intersections\"\u003eWell Path Intersections\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\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\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 point list is light pink when additional points can be picked in 3D view.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click button \u003cstrong\u003eStop picking points\u003c/strong\u003e (color of point list turns 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), press button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\u003cp\u003eThe point list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when in keyboard focus. 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 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 point list is light pink when additional points can be picked in 3D view.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click button \u003cstrong\u003eStop picking points\u003c/strong\u003e (color of point list turns 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, press 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 in keyboard focus. 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:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e: angle between the horizontal plane and down.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e: angle between North and the plane. Changing azimuth will rotate the plane about the first point picked in 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\u003eA 2D Intersection View is shown either by right clicking an intersection and select \u003cstrong\u003eShow 2D intersection View\u003c/strong\u003e or by checking its entry in \u003cstrong\u003eProject tree\u003c/strong\u003e.\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 view. The default name combines the name of the origin view and 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 turned off, the colors are easier to compare with legend, but carry no visual cue to visualize 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 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 incremental changes for slider when XY values are changed (default value 1.0)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slider Step Size\u003c/strong\u003e \u0026ndash; Defines incremental changes for slider when depth values are 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\u003ch2 id=\"depth-and-range-filter\"\u003eDepth and Range Filter\u003c/h2\u003e\n\u003cp\u003eAn intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined \u003cstrong\u003eDepth Filter\u003c/strong\u003e. \nDepth filtering is performed by selecting an intersection in \u003cstrong\u003eProject Tree\u003c/strong\u003e and setting \u003cstrong\u003eDepth Filter\u003c/strong\u003e properties in \u003cstrong\u003eProperty Editor\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e: no depth filtering\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbove\u003c/strong\u003e: show above the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBelow\u003c/strong\u003e: show below the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBetween\u003c/strong\u003e: show between the specified \u003cem\u003eUpper Depth\u003c/em\u003e and the specified \u003cem\u003eLower Depth\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eAn intersection can be also be visually filtered by a user defined \u003cstrong\u003eK Range Filter\u003c/strong\u003e. \nK Range filtering is performed by enabling \u003cstrong\u003eK Range Filter\u003c/strong\u003e of an intersection. The filtering is defined using a text string, i.e. \u0026ldquo;5,10-15,20:3\u0026rdquo;, see \u003ca href=\"/misc/advancedtextinput/\"\u003eAdvanced Text Input\u003c/a\u003e for details.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPropEdDepthFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"filter-options-for-all-intersections\"\u003eFilter Options for all Intersections\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionFolderOverrides.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe filtering of all intersections can be controlled when selecting the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object. Activating these options will override the settings defined locally on each intersection.\u003c/p\u003e\n\u003cp\u003eSimilar options can also be activated for \u003cstrong\u003eFaults\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"intersection-results\"\u003eIntersection Results\u003c/h2\u003e\n\u003cp\u003eTo select a simulation result to display on an intersection, right-click \u003cstrong\u003eIntersection Results\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e and select \u003cstrong\u003eNew Result Definition\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeparateIntersectionResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eBy selecting a specific \u003cstrong\u003eIntersection Result\u003c/strong\u003e, the \u003cstrong\u003eProperty Editor\u003c/strong\u003e allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.\u003c/p\u003e\n\u003cp\u003eThe next step is to select an \u003cstrong\u003eIntersection\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e and define \u003cstrong\u003eResult Reference\u003c/strong\u003e. \nIn the example below, available sources are the two \u003cstrong\u003eIntersections Results\u003c/strong\u003e of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionSeparateResultReference.png\" alt=\"\"\u003e\u003c/p\u003e\n",
+                content:  "\nIntersections are cross sections of a grid model that cut the grid in various ways to display grid cell values. There are two main types of intersections:\nIntersection: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An intersection can also be shown in a separate 2D Intersection View.\nIntersection Box: can be used as a box cutting grid cells or collapsed to a restricted axis aligned plane.\nStructural uncertainty can be visualized on intersections as described in Ensemble Surface.\nAll types of intersections are stored in the folder Intersections of a View. An intersection may be copied to other views by the menu option Copy intersections to all views in case in the right-click menu.\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. They 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 Project Tree or activating the Hide Grid Cells toolbar button.\nCommon Curve Based Intersection Options The property panel of a well path based intersection is shown below:\nName \u0026ndash; Automatically created based on the item specifying the intersection. The user can edit the name, but it will be updated if you change well or well path. Intersecting Geometry \u0026ndash; Options to control the curve used for the cross section dependant on the type of intersection. Depth Filter \u0026ndash; Controls the depth/z-range for visible geometry. Can be controlled from the Intersections folder object. K Range Filter \u0026ndash; Controls the visible K slices. Can be controlled from the Intersections folder object. Advanced options 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 intersection geometry. Direction is used to extrude the curve in the defined direction, and thereby create a set of planes. Horizontal implies the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line. By Defined by two points, the user can define the direction based on any two points. The direction from the first to the second point defines the extrude direction.\nWell Path Intersections A new Well Path intersection can be created by right-clicking the well path in the 3D view or in the Project Tree.\nA 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.\nThe background color of point list is light pink when additional points can be picked in 3D view. To finish adding points, click button Stop picking points (color of point list turns white). The points in the list can be deleted and edited using the keyboard. To append more points (by clicking in the 3D view), press button Start picking points again.\nThe point list can be copied to clipboard using CTRL-C when in keyboard focus. 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 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.\nThe background color of point list is light pink when additional points can be picked in 3D view. To finish adding points, click button Stop picking points (color of point list turns white). The points in the list can be deleted and edited using the keyboard. To append more points by clicking in the 3D view, press button Start picking points again.\nThe points in the list can be copied to clipboard using CTRL-C when in keyboard focus. 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:\nDip: angle between the horizontal plane and down. Azimuth: angle between North and the plane. Changing azimuth will rotate the plane about the first point picked in 3D view. The length of the plane can also be set manually in the Property Editor.\nLength 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.\nA 2D Intersection View is shown either by right clicking an intersection and select Show 2D intersection View or by checking its entry in Project tree.\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:\nViewer Name \u0026ndash; User editable name of view. The default name combines the name of the origin view and intersection name. Background \u0026ndash; Color of the viewer background Disable Results Lighting \u0026ndash; Toggle the light effect. When turned off, the colors are easier to compare with legend, but carry no visual cue to visualize 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:\nName \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 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 incremental changes for slider when XY values are changed (default value 1.0) Depth Slider Step Size \u0026ndash; Defines incremental changes for slider when depth values are 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.\nDepth and Range Filter An intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined Depth Filter. Depth filtering is performed by selecting an intersection in Project Tree and setting Depth Filter properties in Property Editor:\nNone: no depth filtering Above: show above the specified Depth Below: show below the specified Depth Between: show between the specified Upper Depth and the specified Lower Depth An intersection can be also be visually filtered by a user defined K Range Filter. K Range filtering is performed by enabling K Range Filter of an intersection. The filtering is defined using a text string, i.e. \u0026ldquo;5,10-15,20:3\u0026rdquo;, see Advanced Text Input for details.\nFilter Options for all Intersections The filtering of all intersections can be controlled when selecting the Intersections folder object. Activating these options will override the settings defined locally on each intersection.\nSimilar options can also be activated for Faults.\nIntersection Results To select a simulation result to display on an intersection, right-click Intersection Results in Project Tree and select New Result Definition.\nBy selecting a specific Intersection Result, the Property Editor allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.\nThe next step is to select an Intersection in Project Tree and define Result Reference. In the example below, available sources are the two Intersections Results of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIntersections are cross sections of a grid model that cut the grid in various ways to display grid cell values.\nThere are two main types of intersections:\u003c/p\u003e\n\u003col\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eIntersection\u003c/strong\u003e: is defined by a piece-wise linear curve and a direction of extrusion. The curve can be either a simulation well, a well path, a user defined polyline, or a user defined line. An  intersection can also be shown in a separate \u003ca href=\"/3d-main-window/intersections/#2d-intersection-views\"\u003e2D Intersection View\u003c/a\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eIntersection Box\u003c/strong\u003e: can be used as a box cutting grid cells or collapsed to a restricted axis aligned plane.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp\u003eStructural uncertainty can be visualized on intersections as described in \u003ca href=\"/workflows/ensemblesurface/\"\u003eEnsemble Surface\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eAll types of intersections are stored in the folder \u003cstrong\u003eIntersections\u003c/strong\u003e of a \u003cstrong\u003eView\u003c/strong\u003e. An intersection may be copied to other views by the menu option \u003cstrong\u003eCopy intersections to all views in case\u003c/strong\u003e in the right-click menu.\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 Intersections\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. They 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 \u003cb\u003eGrids\u003c/b\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e or activating the \u003cb\u003eHide Grid Cells\u003c/b\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 edit the name, but it will be updated if you change well or well path.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eIntersecting Geometry\u003c/strong\u003e \u0026ndash; Options to control the curve used for the cross section dependant on the type of intersection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Filter\u003c/strong\u003e \u0026ndash; Controls the depth/z-range for visible geometry. Can be controlled from the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eK Range Filter\u003c/strong\u003e \u0026ndash; Controls the visible K slices. Can be controlled from the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"advanced-options\"\u003eAdvanced options\u003c/h4\u003e\n\u003cul\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 intersection geometry.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cstrong\u003eDirection\u003c/strong\u003e is used to extrude the curve in the defined direction, and thereby create a set of planes. \u003cstrong\u003eHorizontal\u003c/strong\u003e implies the start and end point of the curve is used as a baseline, and the horizontal direction is thus perpendicular to that line.\nBy \u003cstrong\u003eDefined by two points\u003c/strong\u003e, 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\u003ch3 id=\"well-path-intersections\"\u003eWell Path Intersections\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\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\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 point list is light pink when additional points can be picked in 3D view.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click button \u003cstrong\u003eStop picking points\u003c/strong\u003e (color of point list turns 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), press button \u003cstrong\u003eStart picking points\u003c/strong\u003e again.\u003c/p\u003e\n\u003cp\u003eThe point list can be copied to clipboard using \u003cstrong\u003eCTRL-C\u003c/strong\u003e when in keyboard focus. 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 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 point list is light pink when additional points can be picked in 3D view.\u003c/li\u003e\n\u003cli\u003eTo finish adding points, click button \u003cstrong\u003eStop picking points\u003c/strong\u003e (color of point list turns 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, press 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 in keyboard focus. 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:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eDip\u003c/strong\u003e: angle between the horizontal plane and down.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAzimuth\u003c/strong\u003e: angle between North and the plane. Changing azimuth will rotate the plane about the first point picked in 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\u003eA 2D Intersection View is shown either by right clicking an intersection and select \u003cstrong\u003eShow 2D intersection View\u003c/strong\u003e or by checking its entry in \u003cstrong\u003eProject tree\u003c/strong\u003e.\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 view. The default name combines the name of the origin view and 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 turned off, the colors are easier to compare with legend, but carry no visual cue to visualize 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 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 incremental changes for slider when XY values are changed (default value 1.0)\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slider Step Size\u003c/strong\u003e \u0026ndash; Defines incremental changes for slider when depth values are 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\u003ch2 id=\"depth-and-range-filter\"\u003eDepth and Range Filter\u003c/h2\u003e\n\u003cp\u003eAn intersection can be visually filtered, i.e. partly hidden from display, by employing a user defined \u003cstrong\u003eDepth Filter\u003c/strong\u003e.\nDepth filtering is performed by selecting an intersection in \u003cstrong\u003eProject Tree\u003c/strong\u003e and setting \u003cstrong\u003eDepth Filter\u003c/strong\u003e properties in \u003cstrong\u003eProperty Editor\u003c/strong\u003e:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e: no depth filtering\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbove\u003c/strong\u003e: show above the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBelow\u003c/strong\u003e: show below the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBetween\u003c/strong\u003e: show between the specified \u003cem\u003eUpper Depth\u003c/em\u003e and the specified \u003cem\u003eLower Depth\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eAn intersection can be also be visually filtered by a user defined \u003cstrong\u003eK Range Filter\u003c/strong\u003e.\nK Range filtering is performed by enabling \u003cstrong\u003eK Range Filter\u003c/strong\u003e of an intersection. The filtering is defined using a text string, i.e. \u0026ldquo;5,10-15,20:3\u0026rdquo;, see \u003ca href=\"/misc/advancedtextinput/\"\u003eAdvanced Text Input\u003c/a\u003e for details.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionPropEdDepthFilter.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"filter-options-for-all-intersections\"\u003eFilter Options for all Intersections\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionFolderOverrides.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe filtering of all intersections can be controlled when selecting the \u003cstrong\u003eIntersections\u003c/strong\u003e folder object. Activating these options will override the settings defined locally on each intersection.\u003c/p\u003e\n\u003cp\u003eSimilar options can also be activated for \u003cstrong\u003eFaults\u003c/strong\u003e.\u003c/p\u003e\n\u003ch2 id=\"intersection-results\"\u003eIntersection Results\u003c/h2\u003e\n\u003cp\u003eTo select a simulation result to display on an intersection, right-click \u003cstrong\u003eIntersection Results\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e and select \u003cstrong\u003eNew Result Definition\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeparateIntersectionResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eBy selecting a specific \u003cstrong\u003eIntersection Result\u003c/strong\u003e, the \u003cstrong\u003eProperty Editor\u003c/strong\u003e allows to specify case, type or position etc depending on whether the result stem from an Eclipse case or a Geomechanical case.\u003c/p\u003e\n\u003cp\u003eThe next step is to select an \u003cstrong\u003eIntersection\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e and define \u003cstrong\u003eResult Reference\u003c/strong\u003e.\nIn the example below, available sources are the two \u003cstrong\u003eIntersections Results\u003c/strong\u003e of previous figure, one of which stems from a geomechanical case and the other from an Eclipse case.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/IntersectionSeparateResultReference.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/intersections/"
             };
         
@@ -3776,7 +3775,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",
+                content:  "\nThis chapter of the ResInsight documentation describes the following:\ndefining 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\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/"
             };
@@ -3785,7 +3784,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/regressionanalysis/"] = {
                 title:    "Regression Analysis",
-                content:  "Create Regression Analysis Regression analysis curves can be created from the right-click menu for a curve in the Plot Project Tree.\nRegression Types Linear Regression The linear regression (i.e. straight line fit) is calculated by choosing the line that minimizes the sum of the squared differences between the observed dependent variable values and the values predicted by the linear equation. The straight line equation can be written as:\n$$ y = a + bx $$\nwhere:\n $y$ is the dependent variable, $x$ is the independent variable, $a$ is the intercept, $b$ is the slope.  Polynomial Regression Polynomial regression is a form of linear regression where the relationship between the independent variable(s) and the dependent variable is modeled as an nth-degree polynomial. It allows for more complex relationships between the variables by introducing polynomial terms into the regression equation.\nA polynomial in a single indeterminate x can always be written (or rewritten) in the form\n$$ y = a_{n}x^n + a_{n-1}x^{n-1} + \\dots + a_{2}x^{2}+a_{1}x+a_{0} $$\nwhere:\n $a_0 , \\ldots, a_n$ are constants that are called the coefficients of the polynomial, $x$ is the indeterminate. $n$ is the degree of the polynomial.  To determine the degree of the polynomial, one needs to consider the complexity of the relationship between the variables and the nature of the data. A higher degree polynomial can capture more intricate relationships but may also lead to overfitting if the model becomes too flexible.\nPolynomial regression can be beneficial when the relationship between the variables is curvilinear or nonlinear. By introducing polynomial terms, it can capture the curvature in the data and provide a better fit compared to simple linear regression.\nPower Fit Regression The Power Fit regression is described by the following equation:\n$$ y = ax^b $$\nwhere:\n $y$ is the dependent variable, $x$ is the independent variable, $a$ is the coefficient, $b$ is the exponent.  In power fit regression, the goal is to estimate the values of $a$ and $b$ that best describe the relationship between the variables. This is done by minimizing the sum of the squared differences between the observed dependent variable values and the values predicted by the power-law equation.\nExponential Regression Exponential regression is a type of nonlinear regression used to model relationships where the dependent variable changes exponentially with the independent variable. It is suitable when the data exhibits exponential growth or decay patterns.\nThe equation for exponential regression can be written as:\n$$ y = ae^{bx} $$\nwhere:\n $y$ is the dependent variable, $x$ is the independent variable, $a$ is the coefficient, $b$ is the rate of growth or decay, $e$ is the base of the natural logarithm (approximately 2.71828).  Exponential models are commonly used in biological applications, for example, for exponential growth of bacteria. Spotfire uses a nonlinear regression method for this calculation. This will result in better accuracy of the calculation compared to using linear regression on transformed values only.\nLogarithmic Regression The logarithmic fit calculates the least squares fit through points by using the following equation:\n$$ y = a + b \\ln( x ) $$\n $y$ is the dependent variable, $x$ is the independent variable, $a$ and $b$ are coefficients.  ",
+                content:  "\nCreate Regression Analysis Regression analysis curves can be created from the right-click menu for a curve in the Plot Project Tree.\nRegression Types Linear Regression The linear regression (i.e. straight line fit) is calculated by choosing the line that minimizes the sum of the squared differences between the observed dependent variable values and the values predicted by the linear equation. The straight line equation can be written as:\n$$ y = a + bx $$\nwhere:\n$y$ is the dependent variable, $x$ is the independent variable, $a$ is the intercept, $b$ is the slope. Polynomial Regression Polynomial regression is a form of linear regression where the relationship between the independent variable(s) and the dependent variable is modeled as an nth-degree polynomial. It allows for more complex relationships between the variables by introducing polynomial terms into the regression equation.\nA polynomial in a single indeterminate x can always be written (or rewritten) in the form\n$$ y = a_{n}x^n + a_{n-1}x^{n-1} + \\dots + a_{2}x^{2}+a_{1}x+a_{0} $$\nwhere:\n$a_0 , \\ldots, a_n$ are constants that are called the coefficients of the polynomial, $x$ is the indeterminate. $n$ is the degree of the polynomial. To determine the degree of the polynomial, one needs to consider the complexity of the relationship between the variables and the nature of the data. A higher degree polynomial can capture more intricate relationships but may also lead to overfitting if the model becomes too flexible.\nPolynomial regression can be beneficial when the relationship between the variables is curvilinear or nonlinear. By introducing polynomial terms, it can capture the curvature in the data and provide a better fit compared to simple linear regression.\nPower Fit Regression The Power Fit regression is described by the following equation:\n$$ y = ax^b $$\nwhere:\n$y$ is the dependent variable, $x$ is the independent variable, $a$ is the coefficient, $b$ is the exponent. In power fit regression, the goal is to estimate the values of $a$ and $b$ that best describe the relationship between the variables. This is done by minimizing the sum of the squared differences between the observed dependent variable values and the values predicted by the power-law equation.\nExponential Regression Exponential regression is a type of nonlinear regression used to model relationships where the dependent variable changes exponentially with the independent variable. It is suitable when the data exhibits exponential growth or decay patterns.\nThe equation for exponential regression can be written as:\n$$ y = ae^{bx} $$\nwhere:\n$y$ is the dependent variable, $x$ is the independent variable, $a$ is the coefficient, $b$ is the rate of growth or decay, $e$ is the base of the natural logarithm (approximately 2.71828). Exponential models are commonly used in biological applications, for example, for exponential growth of bacteria. Spotfire uses a nonlinear regression method for this calculation. This will result in better accuracy of the calculation compared to using linear regression on transformed values only.\nLogarithmic Regression The logarithmic fit calculates the least squares fit through points by using the following equation:\n$$ y = a + b \\ln( x ) $$\n$y$ is the dependent variable, $x$ is the independent variable, $a$ and $b$ are coefficients. ",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/RegressionAnalysis.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-regression-analysis\"\u003eCreate Regression Analysis\u003c/h2\u003e\n\u003cp\u003eRegression analysis curves can be created from the right-click menu for a curve in the \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RegressionAnalysis_create.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"regression-types\"\u003eRegression Types\u003c/h2\u003e\n\u003ch3 id=\"linear-regression\"\u003eLinear Regression\u003c/h3\u003e\n\u003cp\u003eThe linear regression (i.e. straight line fit) is calculated by choosing the line that minimizes the sum of the squared differences between the observed dependent variable values and the values predicted by the linear equation. The straight line equation can be written as:\u003c/p\u003e\n\u003cp\u003e$$ y = a + bx $$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$y$ is the dependent variable,\u003c/li\u003e\n\u003cli\u003e$x$ is the independent variable,\u003c/li\u003e\n\u003cli\u003e$a$ is the intercept,\u003c/li\u003e\n\u003cli\u003e$b$ is the slope.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"polynomial-regression\"\u003ePolynomial Regression\u003c/h3\u003e\n\u003cp\u003ePolynomial regression is a form of linear regression where the relationship between the independent variable(s) and the dependent variable is modeled as an nth-degree polynomial. It allows for more complex relationships between the variables by introducing polynomial terms into the regression equation.\u003c/p\u003e\n\u003cp\u003eA polynomial in a single indeterminate x can always be written (or rewritten) in the form\u003c/p\u003e\n\u003cp\u003e$$ y = a_{n}x^n + a_{n-1}x^{n-1} + \\dots + a_{2}x^{2}+a_{1}x+a_{0} $$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$a_0 , \\ldots, a_n$ are constants that are called the coefficients of the polynomial,\u003c/li\u003e\n\u003cli\u003e$x$ is the indeterminate.\u003c/li\u003e\n\u003cli\u003e$n$ is the degree of the polynomial.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eTo determine the degree of the polynomial, one needs to consider the complexity of the relationship between the variables and the nature of the data. A higher degree polynomial can capture more intricate relationships but may also lead to overfitting if the model becomes too flexible.\u003c/p\u003e\n\u003cp\u003ePolynomial regression can be beneficial when the relationship between the variables is curvilinear or nonlinear. By introducing polynomial terms, it can capture the curvature in the data and provide a better fit compared to simple linear regression.\u003c/p\u003e\n\u003ch3 id=\"power-fit-regression\"\u003ePower Fit Regression\u003c/h3\u003e\n\u003cp\u003eThe Power Fit regression is described by the following equation:\u003c/p\u003e\n\u003cp\u003e$$ y = ax^b $$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$y$ is the dependent variable,\u003c/li\u003e\n\u003cli\u003e$x$ is the independent variable,\u003c/li\u003e\n\u003cli\u003e$a$ is the coefficient,\u003c/li\u003e\n\u003cli\u003e$b$ is the exponent.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eIn power fit regression, the goal is to estimate the values of $a$ and $b$ that best describe the relationship between the variables. This is done by minimizing the sum of the squared differences between the observed dependent variable values and the values predicted by the power-law equation.\u003c/p\u003e\n\u003ch3 id=\"exponential-regression\"\u003eExponential Regression\u003c/h3\u003e\n\u003cp\u003eExponential regression is a type of nonlinear regression used to model relationships where the dependent variable changes exponentially with the independent variable. It is suitable when the data exhibits exponential growth or decay patterns.\u003c/p\u003e\n\u003cp\u003eThe equation for exponential regression can be written as:\u003c/p\u003e\n\u003cp\u003e$$ y = ae^{bx} $$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$y$ is the dependent variable,\u003c/li\u003e\n\u003cli\u003e$x$ is the independent variable,\u003c/li\u003e\n\u003cli\u003e$a$ is the coefficient,\u003c/li\u003e\n\u003cli\u003e$b$ is the rate of growth or decay,\u003c/li\u003e\n\u003cli\u003e$e$ is the base of the natural logarithm (approximately 2.71828).\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eExponential models are commonly used in biological applications, for example, for exponential growth of bacteria. Spotfire uses a nonlinear regression method for this calculation. This will result in better accuracy of the calculation compared to using linear regression on transformed values only.\u003c/p\u003e\n\u003ch3 id=\"logarithmic-regression\"\u003eLogarithmic Regression\u003c/h3\u003e\n\u003cp\u003eThe logarithmic fit calculates the least squares fit through points by using the following equation:\u003c/p\u003e\n\u003cp\u003e$$ y = a + b \\ln( x ) $$\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$y$ is the dependent variable,\u003c/li\u003e\n\u003cli\u003e$x$ is the independent variable,\u003c/li\u003e\n\u003cli\u003e$a$ and $b$ are coefficients.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/regressionanalysis/"
             };
@@ -3794,8 +3793,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 Measurements, 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 and an indication of sea level.\n   Sea Level Formations          The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions\nThe third track, which is disabled by default, contains the input parameters of the plot as described in the Input Requirements section.\nThe fourth track (third visible by default) shows the following stability gradients (all normalized by mud weight):\n FG: Fracture Gradient in sands based on Kirsch and in shale based on the K0_FG parameter or proportional to SHMIN. OBG: Overburden stress gradient: Stress component S_33. PP: Pore pressure. SFG: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia. SHMIN: Minimum horizontal stress from grid. SH_MK: Minimum horizontal stress from Matthews \u0026amp; Kelly.  The fifth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\nIf any Well Measurements are present, they will be visible as symbols in the track Stability Curves.\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 PP, FG, SFG and SH_MK, the following input parameters are required:\n   Curve Required Parameters     PP Pore Pressure in reservoir (PP Reservoir) and outside the reservoir (PP Non-Reservoir)   FG Pore Pressure (PP Reservoir), Poissons\u0026rsquo; Ratio in Sand, FG Shale in shale   SFG Uniaxial Compressive Strength (UCS)   SH_MK K0_SH, Overburden Gradient at initial time (OBG0) and the Depletion Factor (DF)    For parameters with multiple available sources, the sources will be tried in numbered order for each curve point (where well path intersects with grid). However, the options for FG Shale are mutually exclusive and will apply to the whole domain.\n   Parameter Default Sources     Density of Sea Water $1.03 g/cm^3$ User setting in GUI   PP Reservoir Grid Nodal Values (POR) 1. Grid (Grid units), 2. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_INP\u0026rdquo; or \u0026ldquo;PP_RES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_INP\u0026rdquo; with Units: SG_EMW)   PP Non-Reservoir Hydrostatic PP (from TVDRKB, Density of Sea Water and gravity) 1. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_NONRES_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo; with Units: SG_EMW), 4. Hydrostatic Pressure   Poissons\u0026rsquo; Ratio 0.35 1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;)   UCS 100 bar 1. LAS-file (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: Pascal)   Initial Overburden Gradient (OBG0) OBG at initial time step 1. Grid (Grid units), 2. LAS-file (Variable: \u0026ldquo;OBG0_INP\u0026rdquo;, Units: Bar)   DF 0.7 1. LAS-file (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No Units), 2. Element Property Table (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No units), 3 User Defined   K0_SH 0.65 1. LAS-file (Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units), 3. User Defined   FG Shale Derived from K0_FG Derived from K0_FG and PP Non-Reservoir, Proportional to SH or LAS-file (Variable: \u0026ldquo;FG_SHALE_INP\u0026rdquo;, Units: SG_EMW)   K0_FG 0.75 1. LAS-file (Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units), 3. User Defined    In addition to the units above, it LAS-files it is possible to supply PP in Bar and UCS in Pascal or MPa. Conversion will be handled automatically.\nEquations 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 principal effective stresses at the borehole wall:\n$$\\sigma\u0026rsquo;_1 = \\sigma\u0026rsquo;_1 (\\theta)= \\sigma\u0026rsquo;_r = p_w - p_0$$\n$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_2 (\\theta) = \\sigma_{t \\max} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) + \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\n$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_3 (\\theta) = \\sigma_{t \\min} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) - \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\nNext step is to solve for the value of $\\theta \\in [0 - 180]$ that yields $\\sigma\u0026rsquo;_3 (\\theta) = 0$ which in turn gives us $\\sigma_\\theta$ which can be used to solve for $P_w$ in the Kirsch equations.\nThen calculate FG in equivalent mud weight units as $$ FG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$ where $TVD_{RKB} = TVD_{MSL} + AirGap$, the gravity acceleration $g = 9.81 m/s^2$ and the density of sea water $\\rho$ in $kg/m^3$ (thus 1000 x the UI input in $g/cm^3$).\nFracture gradient in shale $$FG_{shale} = K0_{FG} \\times (OBG0 - PP0) + PP0$$\nSH from Matthews \u0026amp; Kelly $$SH_{MK} = K0_{SH} \\times (OBG0 - PP0) + PP0 + DF \\times (PP-PP0)$$\nStassi-d\u0026rsquo;Alia failure criterion in shale Stassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure $P_w$ that satisfies the following equation for $\\theta \\in [0 - 180]$:\nwhere are the effective principal stresses from the Fracture Gradient calculation. and UCS is the uniaxial compressive strength.\nThe Shear Failure Gradient is then given as\n$$SFG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$\nPython Interface The ResInsight Python API offers functionality for creating Well Bore Stability Plots from Python. For an example of use, see ResInsight Python API, and the Create WBS Plot script listed under Python Examples.\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/wellmeasurements/\"\u003eWell Measurements\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 and an indication of sea level.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eSea Level\u003c/th\u003e\n\u003cth\u003eFormations\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003cimg src=\"/images/plot-window/WaterLevel.png\" alt=\"\"\u003e\u003c/td\u003e\n\u003ctd\u003e\u003cimg src=\"/images/plot-window/FormationLevels.png\" alt=\"\"\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eThe second track contains a visualisation of the well, with well attributes of \u003ca href=\"/wells-and-completions/wellpaths/#casing-design\"\u003eCasing Design\u003c/a\u003e as well \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe third track, which is disabled by default, contains the input parameters of the plot as described in the \u003ca href=\"#input-requirements\"\u003eInput Requirements\u003c/a\u003e section.\u003c/p\u003e\n\u003cp\u003eThe fourth track (third visible by default) 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 in sands based on Kirsch and in shale based on the K0_FG parameter or proportional to SHMIN.\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\u003eSHMIN\u003c/strong\u003e: Minimum horizontal stress from grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSH_MK\u003c/strong\u003e: Minimum horizontal stress from Matthews \u0026amp; Kelly.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe fifth 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\u003cp\u003eIf any \u003ca href=\"/wells-and-completions/wellmeasurements/\"\u003eWell Measurements\u003c/a\u003e are present, they will be visible as symbols in the track \u003cstrong\u003eStability Curves\u003c/strong\u003e.\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\u003ePP\u003c/strong\u003e, \u003cstrong\u003eFG\u003c/strong\u003e, \u003cstrong\u003eSFG\u003c/strong\u003e and \u003cstrong\u003eSH_MK\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\u003ePP\u003c/td\u003e\n\u003ctd\u003ePore Pressure in reservoir (PP Reservoir) and outside the reservoir (PP Non-Reservoir)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG\u003c/td\u003e\n\u003ctd\u003ePore Pressure (PP Reservoir), Poissons\u0026rsquo; Ratio in Sand, FG Shale in shale\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\u003ctr\u003e\n\u003ctd\u003eSH_MK\u003c/td\u003e\n\u003ctd\u003eK0_SH, Overburden Gradient at initial time (OBG0) and the Depletion Factor (DF)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eFor parameters with multiple available sources, the sources will be tried in numbered order for each curve point (where well path intersects with grid). However, the options for \u003cstrong\u003eFG Shale\u003c/strong\u003e are mutually exclusive and will apply to the whole domain.\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\u003eSources\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eDensity of Sea Water\u003c/td\u003e\n\u003ctd\u003e$1.03 g/cm^3$\u003c/td\u003e\n\u003ctd\u003eUser setting in GUI\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP Reservoir\u003c/td\u003e\n\u003ctd\u003eGrid Nodal Values (POR)\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_INP\u0026rdquo; or \u0026ldquo;PP_RES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_INP\u0026rdquo; with Units: SG_EMW)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP Non-Reservoir\u003c/td\u003e\n\u003ctd\u003eHydrostatic PP (from TVDRKB, Density of Sea Water and gravity)\u003c/td\u003e\n\u003ctd\u003e1. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_NONRES_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo; with Units: SG_EMW), 4. Hydrostatic Pressure\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePoissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003ctd\u003e0.35\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO_INP\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_INP\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: Pascal)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eInitial Overburden Gradient (OBG0)\u003c/td\u003e\n\u003ctd\u003eOBG at initial time step\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file (Variable: \u0026ldquo;OBG0_INP\u0026rdquo;, Units: Bar)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDF\u003c/td\u003e\n\u003ctd\u003e0.7\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No Units), 2. Element Property Table (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No units), 3 User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eK0_SH\u003c/td\u003e\n\u003ctd\u003e0.65\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units), 3. User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG Shale\u003c/td\u003e\n\u003ctd\u003eDerived from K0_FG\u003c/td\u003e\n\u003ctd\u003eDerived from K0_FG and PP Non-Reservoir, Proportional to SH or LAS-file (Variable: \u0026ldquo;FG_SHALE_INP\u0026rdquo;, Units: SG_EMW)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eK0_FG\u003c/td\u003e\n\u003ctd\u003e0.75\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units), 3. User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eIn addition to the units above, it LAS-files it is possible to supply PP in Bar and UCS in Pascal or MPa. Conversion will be handled automatically.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityParameters.png\" alt=\"\"\u003e\u003c/p\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 principal effective stresses at the borehole wall:\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_1 = \\sigma\u0026rsquo;_1 (\\theta)= \\sigma\u0026rsquo;_r = p_w - p_0$$\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_2 (\\theta) = \\sigma_{t \\max} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) + \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_3 (\\theta) = \\sigma_{t \\min} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) - \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\u003c/p\u003e\n\u003cp\u003eNext step is to solve for the value of $\\theta \\in [0 - 180]$ that yields $\\sigma\u0026rsquo;_3 (\\theta) = 0$ which in turn gives us $\\sigma_\\theta$ which can be used to solve for $P_w$ in the Kirsch equations.\u003c/p\u003e\n\u003cp\u003eThen calculate \u003cem\u003eFG\u003c/em\u003e in equivalent mud weight units as\n$$ FG = \\frac{P_w}{TVD_{RKB} \\: g  \\: \\rho}$$ where $TVD_{RKB} = TVD_{MSL} + AirGap$, the gravity acceleration $g = 9.81 m/s^2$ and  the density of sea water $\\rho$ in $kg/m^3$ (thus 1000 x the UI input in $g/cm^3$).\u003c/p\u003e\n\u003ch3 id=\"fracture-gradient-in-shale\"\u003eFracture gradient in shale\u003c/h3\u003e\n\u003cp\u003e$$FG_{shale} = K0_{FG} \\times (OBG0 - PP0) + PP0$$\u003c/p\u003e\n\u003ch3 id=\"sh-from-matthews--kelly\"\u003eSH from Matthews \u0026amp; Kelly\u003c/h3\u003e\n\u003cp\u003e$$SH_{MK} = K0_{SH} \\times (OBG0 - PP0) + PP0 + DF \\times (PP-PP0)$$\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 $P_w$ that satisfies the following equation \nfor  $\\theta \\in [0 - 180]$:\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 from the Fracture Gradient calculation.\nand \u003cem\u003eUCS\u003c/em\u003e is the \u003cem\u003euniaxial compressive strength\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eThe Shear Failure Gradient is then given as\u003c/p\u003e\n\u003cp\u003e$$SFG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$\u003c/p\u003e\n\u003ch2 id=\"python-interface\"\u003ePython Interface\u003c/h2\u003e\n\u003cp\u003eThe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e offers functionality for creating Well Bore Stability Plots from Python.\nFor an example of use, see \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e, and the \u003cem\u003eCreate WBS Plot\u003c/em\u003e script listed\nunder \u003cem\u003ePython Examples\u003c/em\u003e.\u003c/p\u003e\n",
+                content:  "\nResInsight can create Well Bore Stability plots for Geomechanical cases. These plots are specialized Well Log Plots to visualize Formations, Well Measurements, 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 and an indication of sea level.\nSea Level Formations The second track contains a visualisation of the well, with well attributes of Casing Design as well Completions\nThe third track, which is disabled by default, contains the input parameters of the plot as described in the Input Requirements section.\nThe fourth track (third visible by default) shows the following stability gradients (all normalized by mud weight):\nFG: Fracture Gradient in sands based on Kirsch and in shale based on the K0_FG parameter or proportional to SHMIN. OBG: Overburden stress gradient: Stress component S_33. PP: Pore pressure. SFG: Shear Failure Gradient for shale based on Stassi-d\u0026rsquo;Alia. SHMIN: Minimum horizontal stress from grid. SH_MK: Minimum horizontal stress from Matthews \u0026amp; Kelly. The fifth track contains curves showing the angular orientation of the well path as azimuth (deviation from vertical) and inclination (deviation from x-axis) in degrees.\nIf any Well Measurements are present, they will be visible as symbols in the track Stability Curves.\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 PP, FG, SFG and SH_MK, the following input parameters are required:\nCurve Required Parameters PP Pore Pressure in reservoir (PP Reservoir) and outside the reservoir (PP Non-Reservoir) FG Pore Pressure (PP Reservoir), Poissons\u0026rsquo; Ratio in Sand, FG Shale in shale SFG Uniaxial Compressive Strength (UCS) SH_MK K0_SH, Overburden Gradient at initial time (OBG0) and the Depletion Factor (DF) For parameters with multiple available sources, the sources will be tried in numbered order for each curve point (where well path intersects with grid). However, the options for FG Shale are mutually exclusive and will apply to the whole domain.\nParameter Default Sources Density of Sea Water $1.03 g/cm^3$ User setting in GUI PP Reservoir Grid Nodal Values (POR) 1. Grid (Grid units), 2. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_INP\u0026rdquo; or \u0026ldquo;PP_RES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_INP\u0026rdquo; with Units: SG_EMW) PP Non-Reservoir Hydrostatic PP (from TVDRKB, Density of Sea Water and gravity) 1. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_NONRES_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo; with Units: SG_EMW), 4. Hydrostatic Pressure Poissons\u0026rsquo; Ratio 0.35 1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;) UCS 100 bar 1. LAS-file (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: Pascal) Initial Overburden Gradient (OBG0) OBG at initial time step 1. Grid (Grid units), 2. LAS-file (Variable: \u0026ldquo;OBG0_INP\u0026rdquo;, Units: Bar) DF 0.7 1. LAS-file (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No Units), 2. Element Property Table (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No units), 3 User Defined K0_SH 0.65 1. LAS-file (Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units), 3. User Defined FG Shale Derived from K0_FG Derived from K0_FG and PP Non-Reservoir, Proportional to SH or LAS-file (Variable: \u0026ldquo;FG_SHALE_INP\u0026rdquo;, Units: SG_EMW) K0_FG 0.75 1. LAS-file (Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units), 3. User Defined In addition to the units above, it LAS-files it is possible to supply PP in Bar and UCS in Pascal or MPa. Conversion will be handled automatically.\nEquations 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 principal effective stresses at the borehole wall:\n$$\\sigma\u0026rsquo;_1 = \\sigma\u0026rsquo;_1 (\\theta)= \\sigma\u0026rsquo;_r = p_w - p_0$$\n$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_2 (\\theta) = \\sigma_{t \\max} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) + \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\n$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_3 (\\theta) = \\sigma_{t \\min} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) - \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\nNext step is to solve for the value of $\\theta \\in [0 - 180]$ that yields $\\sigma\u0026rsquo;_3 (\\theta) = 0$ which in turn gives us $\\sigma_\\theta$ which can be used to solve for $P_w$ in the Kirsch equations.\nThen calculate FG in equivalent mud weight units as $$ FG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$ where $TVD_{RKB} = TVD_{MSL} + AirGap$, the gravity acceleration $g = 9.81 m/s^2$ and the density of sea water $\\rho$ in $kg/m^3$ (thus 1000 x the UI input in $g/cm^3$).\nFracture gradient in shale $$FG_{shale} = K0_{FG} \\times (OBG0 - PP0) + PP0$$\nSH from Matthews \u0026amp; Kelly $$SH_{MK} = K0_{SH} \\times (OBG0 - PP0) + PP0 + DF \\times (PP-PP0)$$\nStassi-d\u0026rsquo;Alia failure criterion in shale Stassi-d\u0026rsquo;Alia failure criterion in shale is calculated by finding the well pressure $P_w$ that satisfies the following equation for $\\theta \\in [0 - 180]$:\nwhere are the effective principal stresses from the Fracture Gradient calculation. and UCS is the uniaxial compressive strength.\nThe Shear Failure Gradient is then given as\n$$SFG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$\nPython Interface The ResInsight Python API offers functionality for creating Well Bore Stability Plots from Python. For an example of use, see ResInsight Python API, and the Create WBS Plot script listed under Python Examples.\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/wellmeasurements/\"\u003eWell Measurements\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 and an indication of sea level.\u003c/p\u003e\n\u003ctable\u003e\n\u003cthead\u003e\n\u003ctr\u003e\n\u003cth\u003eSea Level\u003c/th\u003e\n\u003cth\u003eFormations\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003e\u003cimg src=\"/images/plot-window/WaterLevel.png\" alt=\"\"\u003e\u003c/td\u003e\n\u003ctd\u003e\u003cimg src=\"/images/plot-window/FormationLevels.png\" alt=\"\"\u003e\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eThe second track contains a visualisation of the well, with well attributes of \u003ca href=\"/wells-and-completions/wellpaths/#casing-design\"\u003eCasing Design\u003c/a\u003e as well \u003ca href=\"/wells-and-completions/completions/\"\u003eCompletions\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe third track, which is disabled by default, contains the input parameters of the plot as described in the \u003ca href=\"#input-requirements\"\u003eInput Requirements\u003c/a\u003e section.\u003c/p\u003e\n\u003cp\u003eThe fourth track (third visible by default) 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 in sands based on Kirsch and in shale based on the K0_FG parameter or proportional to SHMIN.\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\u003eSHMIN\u003c/strong\u003e: Minimum horizontal stress from grid.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eSH_MK\u003c/strong\u003e: Minimum horizontal stress from Matthews \u0026amp; Kelly.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe fifth 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\u003cp\u003eIf any \u003ca href=\"/wells-and-completions/wellmeasurements/\"\u003eWell Measurements\u003c/a\u003e are present, they will be visible as symbols in the track \u003cstrong\u003eStability Curves\u003c/strong\u003e.\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\u003ePP\u003c/strong\u003e, \u003cstrong\u003eFG\u003c/strong\u003e, \u003cstrong\u003eSFG\u003c/strong\u003e and \u003cstrong\u003eSH_MK\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\u003ePP\u003c/td\u003e\n\u003ctd\u003ePore Pressure in reservoir (PP Reservoir) and outside the reservoir (PP Non-Reservoir)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG\u003c/td\u003e\n\u003ctd\u003ePore Pressure (PP Reservoir), Poissons\u0026rsquo; Ratio in Sand, FG Shale in shale\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\u003ctr\u003e\n\u003ctd\u003eSH_MK\u003c/td\u003e\n\u003ctd\u003eK0_SH, Overburden Gradient at initial time (OBG0) and the Depletion Factor (DF)\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eFor parameters with multiple available sources, the sources will be tried in numbered order for each curve point (where well path intersects with grid). However, the options for \u003cstrong\u003eFG Shale\u003c/strong\u003e are mutually exclusive and will apply to the whole domain.\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\u003eSources\u003c/th\u003e\n\u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n\u003ctr\u003e\n\u003ctd\u003eDensity of Sea Water\u003c/td\u003e\n\u003ctd\u003e$1.03 g/cm^3$\u003c/td\u003e\n\u003ctd\u003eUser setting in GUI\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP Reservoir\u003c/td\u003e\n\u003ctd\u003eGrid Nodal Values (POR)\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_INP\u0026rdquo; or \u0026ldquo;PP_RES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_INP\u0026rdquo; with Units: SG_EMW)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePP Non-Reservoir\u003c/td\u003e\n\u003ctd\u003eHydrostatic PP (from TVDRKB, Density of Sea Water and gravity)\u003c/td\u003e\n\u003ctd\u003e1. LAS-file as equivalent mud-weight (Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo;, Units: SG_EMW), 3. Element Property Table (Variable: \u0026ldquo;POR_NONRES_INP\u0026rdquo; with Units: Pascal or Variable: \u0026ldquo;PP_NONRES_INP\u0026rdquo; with Units: SG_EMW), 4. Hydrostatic Pressure\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003ePoissons\u0026rsquo; Ratio\u003c/td\u003e\n\u003ctd\u003e0.35\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;POISSON_RATIO_INP\u0026rdquo;), 2. Element Property Table (Variable: \u0026ldquo;POISSON_RATIO_INP\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_INP\u0026rdquo;, Units: bar), 2. Element Property Table (Variable: \u0026ldquo;UCS_INP\u0026rdquo;, Units: Pascal)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eInitial Overburden Gradient (OBG0)\u003c/td\u003e\n\u003ctd\u003eOBG at initial time step\u003c/td\u003e\n\u003ctd\u003e1. Grid (Grid units), 2. LAS-file (Variable: \u0026ldquo;OBG0_INP\u0026rdquo;, Units: Bar)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eDF\u003c/td\u003e\n\u003ctd\u003e0.7\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No Units), 2. Element Property Table (Variable: \u0026ldquo;DF_INP\u0026rdquo;, No units), 3 User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eK0_SH\u003c/td\u003e\n\u003ctd\u003e0.65\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_SH_INP\u0026rdquo;, No Units), 3. User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eFG Shale\u003c/td\u003e\n\u003ctd\u003eDerived from K0_FG\u003c/td\u003e\n\u003ctd\u003eDerived from K0_FG and PP Non-Reservoir, Proportional to SH or LAS-file (Variable: \u0026ldquo;FG_SHALE_INP\u0026rdquo;, Units: SG_EMW)\u003c/td\u003e\n\u003c/tr\u003e\n\u003ctr\u003e\n\u003ctd\u003eK0_FG\u003c/td\u003e\n\u003ctd\u003e0.75\u003c/td\u003e\n\u003ctd\u003e1. LAS-file (Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units ), 2. Element Property Table(\u0026ldquo;Variable: \u0026ldquo;K0_FG_INP\u0026rdquo;, No Units), 3. User Defined\u003c/td\u003e\n\u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\u003cp\u003eIn addition to the units above, it LAS-files it is possible to supply PP in Bar and UCS in Pascal or MPa. Conversion will be handled automatically.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellBoreStabilityParameters.png\" alt=\"\"\u003e\u003c/p\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 principal effective stresses at the borehole wall:\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_1 = \\sigma\u0026rsquo;_1 (\\theta)= \\sigma\u0026rsquo;_r = p_w - p_0$$\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_2 (\\theta) = \\sigma_{t \\max} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) + \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\u003c/p\u003e\n\u003cp\u003e$$\\sigma\u0026rsquo;_2 = \\sigma\u0026rsquo;_3 (\\theta) = \\sigma_{t \\min} = \\frac{1}{2} \\left( (\\sigma_z + \\sigma_\\theta) - \\sqrt{(\\sigma_z + \\sigma_\\theta)^2 + 4\\tau_{\\theta z}^2} \\right) - p_0$$\u003c/p\u003e\n\u003cp\u003eNext step is to solve for the value of $\\theta \\in [0 - 180]$ that yields $\\sigma\u0026rsquo;_3 (\\theta) = 0$ which in turn gives us $\\sigma_\\theta$ which can be used to solve for $P_w$ in the Kirsch equations.\u003c/p\u003e\n\u003cp\u003eThen calculate \u003cem\u003eFG\u003c/em\u003e in equivalent mud weight units as\n$$ FG = \\frac{P_w}{TVD_{RKB} \\: g  \\: \\rho}$$ where $TVD_{RKB} = TVD_{MSL} + AirGap$, the gravity acceleration $g = 9.81 m/s^2$ and  the density of sea water $\\rho$ in $kg/m^3$ (thus 1000 x the UI input in $g/cm^3$).\u003c/p\u003e\n\u003ch3 id=\"fracture-gradient-in-shale\"\u003eFracture gradient in shale\u003c/h3\u003e\n\u003cp\u003e$$FG_{shale} = K0_{FG} \\times (OBG0 - PP0) + PP0$$\u003c/p\u003e\n\u003ch3 id=\"sh-from-matthews--kelly\"\u003eSH from Matthews \u0026amp; Kelly\u003c/h3\u003e\n\u003cp\u003e$$SH_{MK} = K0_{SH} \\times (OBG0 - PP0) + PP0 + DF \\times (PP-PP0)$$\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 $P_w$ that satisfies the following equation\nfor  $\\theta \\in [0 - 180]$:\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 from the Fracture Gradient calculation.\nand \u003cem\u003eUCS\u003c/em\u003e is the \u003cem\u003euniaxial compressive strength\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eThe Shear Failure Gradient is then given as\u003c/p\u003e\n\u003cp\u003e$$SFG = \\frac{P_w}{TVD_{RKB} \\: g \\: \\rho}$$\u003c/p\u003e\n\u003ch2 id=\"python-interface\"\u003ePython Interface\u003c/h2\u003e\n\u003cp\u003eThe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e offers functionality for creating Well Bore Stability Plots from Python.\nFor an example of use, see \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e, and the \u003cem\u003eCreate WBS Plot\u003c/em\u003e script listed\nunder \u003cem\u003ePython Examples\u003c/em\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/wellborestabilityplots/"
             };
         
@@ -3803,8 +3802,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/seismicsections/"] = {
                 title:    "Seismic Sections",
-                content:  "Creating a Seismic Section Import of data is described in Seismic Data\nSeismic Sections are cross sections that cut a grid model in various ways to display seismic data. A Seismic Section is created by right-clicking the Seismic Section item in Project Tree\nThe following types of Seismic Sections are available:\n Inline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired. Xline Section: A seismic line within a 3D survey perpendicular to the direction in which the data were acquired. Depth Slice: Horizontal slice through the volume data of a 3D survey at a specific depth. Polyline Section: Seismic section following a user defined polyline ontop a grid model for displaying volume data of a 3D survey, c.f. Polyline Intersection for specification of polyline. Well Path Section: Seismic section following a specific well path through the volume data of a 3D survey.  Property Editor The Property Editor of a Seismic Section is shown below.\nThe properties are grouped as follows:\n General: Enables the user to provide a description, select seismic data, type and position of a Seismic Section. Depth Filter: Enables filtering of a Seismic Section by setting Depth Filter properties:  None: no depth filtering Above: show above the specified Depth Below: show below the specified Depth Between: show between the specified Upper Depth and the specified Lower Depth   Outline: Specifying line thickness, line color, and display of seismic data outline. Show Image: Displays the Seismic Section in a separate 2D view.  ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicHeaderImage.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"creating-a-seismic-section\"\u003eCreating a Seismic Section\u003c/h2\u003e\n\u003cp\u003eImport of data is described in \u003ca href=\"/import/seismicdata/\"\u003eSeismic Data\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSeismic Sections\u003c/strong\u003e are cross sections that cut a grid model in various ways to display seismic data. \nA \u003cstrong\u003eSeismic Section\u003c/strong\u003e is created by right-clicking the \u003cstrong\u003eSeismic Section\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicSectionsNew.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe following types of Seismic Sections are available:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInline Section\u003c/strong\u003e: A seismic line within a 3D survey \u003cem\u003eparallel\u003c/em\u003e to the direction in which the data were acquired.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXline Section\u003c/strong\u003e: A seismic line within a 3D survey \u003cem\u003eperpendicular\u003c/em\u003e to the direction in which the data were acquired.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slice\u003c/strong\u003e: Horizontal slice through the volume data of a 3D survey at a specific depth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePolyline Section\u003c/strong\u003e: Seismic section following a \u003cem\u003euser defined polyline\u003c/em\u003e ontop a grid model for displaying volume data of a 3D survey, c.f. \u003ca href=\"/3d-main-window/intersections/#polyline-intersection\"\u003ePolyline Intersection\u003c/a\u003e for specification of polyline.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Path Section\u003c/strong\u003e: Seismic section following a \u003cem\u003especific well path\u003c/em\u003e through the volume data of a 3D survey.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eProperty Editor\u003c/strong\u003e of a Seismic Section is shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicSectionsPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe properties are grouped as follows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGeneral\u003c/strong\u003e: Enables the user to provide a description, select seismic data, type and position of a Seismic Section.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Filter\u003c/strong\u003e: Enables filtering of a Seismic Section by setting \u003cstrong\u003eDepth Filter\u003c/strong\u003e properties:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e: no depth filtering\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbove\u003c/strong\u003e: show above the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBelow\u003c/strong\u003e: show below the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBetween\u003c/strong\u003e: show between the specified \u003cem\u003eUpper Depth\u003c/em\u003e and the specified \u003cem\u003eLower Depth\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOutline\u003c/strong\u003e: Specifying line thickness, line color, and display of seismic data outline.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Image\u003c/strong\u003e: Displays the Seismic Section in a separate 2D view.\u003c/li\u003e\n\u003c/ul\u003e\n",
+                content:  "\nCreating a Seismic Section Import of data is described in Seismic Data\nSeismic Sections are cross sections that cut a grid model in various ways to display seismic data. A Seismic Section is created by right-clicking the Seismic Section item in Project Tree\nThe following types of Seismic Sections are available:\nInline Section: A seismic line within a 3D survey parallel to the direction in which the data were acquired. Xline Section: A seismic line within a 3D survey perpendicular to the direction in which the data were acquired. Depth Slice: Horizontal slice through the volume data of a 3D survey at a specific depth. Polyline Section: Seismic section following a user defined polyline ontop a grid model for displaying volume data of a 3D survey, c.f. Polyline Intersection for specification of polyline. Well Path Section: Seismic section following a specific well path through the volume data of a 3D survey. Property Editor The Property Editor of a Seismic Section is shown below.\nThe properties are grouped as follows:\nGeneral: Enables the user to provide a description, select seismic data, type and position of a Seismic Section. Depth Filter: Enables filtering of a Seismic Section by setting Depth Filter properties: None: no depth filtering Above: show above the specified Depth Below: show below the specified Depth Between: show between the specified Upper Depth and the specified Lower Depth Outline: Specifying line thickness, line color, and display of seismic data outline. Show Image: Displays the Seismic Section in a separate 2D view. ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicHeaderImage.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"creating-a-seismic-section\"\u003eCreating a Seismic Section\u003c/h2\u003e\n\u003cp\u003eImport of data is described in \u003ca href=\"/import/seismicdata/\"\u003eSeismic Data\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eSeismic Sections\u003c/strong\u003e are cross sections that cut a grid model in various ways to display seismic data.\nA \u003cstrong\u003eSeismic Section\u003c/strong\u003e is created by right-clicking the \u003cstrong\u003eSeismic Section\u003c/strong\u003e item in \u003cstrong\u003eProject Tree\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicSectionsNew.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe following types of Seismic Sections are available:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eInline Section\u003c/strong\u003e: A seismic line within a 3D survey \u003cem\u003eparallel\u003c/em\u003e to the direction in which the data were acquired.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eXline Section\u003c/strong\u003e: A seismic line within a 3D survey \u003cem\u003eperpendicular\u003c/em\u003e to the direction in which the data were acquired.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Slice\u003c/strong\u003e: Horizontal slice through the volume data of a 3D survey at a specific depth.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003ePolyline Section\u003c/strong\u003e: Seismic section following a \u003cem\u003euser defined polyline\u003c/em\u003e ontop a grid model for displaying volume data of a 3D survey, c.f. \u003ca href=\"/3d-main-window/intersections/#polyline-intersection\"\u003ePolyline Intersection\u003c/a\u003e for specification of polyline.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell Path Section\u003c/strong\u003e: Seismic section following a \u003cem\u003especific well path\u003c/em\u003e through the volume data of a 3D survey.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"property-editor\"\u003eProperty Editor\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eProperty Editor\u003c/strong\u003e of a Seismic Section is shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SeismicSectionsPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe properties are grouped as follows:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eGeneral\u003c/strong\u003e: Enables the user to provide a description, select seismic data, type and position of a Seismic Section.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eDepth Filter\u003c/strong\u003e: Enables filtering of a Seismic Section by setting \u003cstrong\u003eDepth Filter\u003c/strong\u003e properties:\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eNone\u003c/strong\u003e: no depth filtering\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eAbove\u003c/strong\u003e: show above the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBelow\u003c/strong\u003e: show below the specified \u003cem\u003eDepth\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eBetween\u003c/strong\u003e: show between the specified \u003cem\u003eUpper Depth\u003c/em\u003e and the specified \u003cem\u003eLower Depth\u003c/em\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eOutline\u003c/strong\u003e: Specifying line thickness, line color, and display of seismic data outline.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eShow Image\u003c/strong\u003e: Displays the Seismic Section in a separate 2D view.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/3d-main-window/seismicsections/"
             };
         
@@ -3812,8 +3811,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/surfaces/"] = {
                 title:    "Surfaces",
-                content:  "ResInsight is capable of mapping properties and simulation results onto 3D surfaces imported from GOCAD and Petrel as specified below.\nImport and appearance of surfaces 3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option File-\u0026gt;Import-\u0026gt;Import Surfaces in the 3D Main Window.\nImported surfaces are listed under the entry in the Project Tree. You can click on a surface to change i.e. the name or color of the surface, or change the file to read the surface data from.\nYou can also change the depth of the surface by adding a depth offset (positive or negative). This could be used i.e. to import the same surface file multiple times and assign each instance of the surface a separate depth offset. When a depth offset is set, the offset value will be shown as part of the surface name in the project tree.\nMultiple surfaces can be imported at the same time by choosing more than one input file in the file selection window that shows up when you start an import.\n\rUsing folders To make it easier to organize the surfaces you import into your project, ResInsight supports creating surface folders in the project tree. To create a new folder, right-click on the top level Surfaces folder in the project tree and choose Add Folder.\nSurface Results Per default, ResInsight maps current Cell Result on a given surface. If another result is to be displayed, specify the result under Surface Results as shown below.\nClicking a surface of a View in the Project Tree activates the Property Editor for allowing view settings as shown below.\nTo change result displayed on the surface, please specify the desired result in the Result Reference section of the Property Editor.\nReloading Surfaces If you have modified a surface file using an external program, you can easily load the changes into ResInsight by using the reload surface feature. Bring up the right-click menu for the surface you want to reload and choose Reload. The views will automatically update with the new data (could take a few seconds).\nCreate a copy You can easily create a copy of an existing surface by choosing Create Copy in the surface right-click menu. A new, identical surface will show up at the same level in the project tree. You can now give it a new name, change depth offset etc.\nGrid Case Surfaces In addition to importing surfaces from file, ResInsight can also generate grid case surfaces. You do that by bringing up the right-click menu for the project tree entry and choose Create Grid Case Surfaces.\nA grid case surface has the same properties as a surface imported from file, but instead of choosing which file the data should come from, you choose a source case, a slice direction and a slice index. The slice direction and index will be added to the surface name shown in the project tree.\nExporting Surfaces ResInsight can export surfaces to the GOCAD TSurf file format. Grid case surfaces can additionally be exported to Petrel Surface PTL format. Use the right-click menu for the surface you want to export and choose the export format you want to use. A file selection window will show up allowing you to choose where you want to save the exported data.\nSupported Surface Formats GOCAD Surface format GOCAD is a computer application that allows you to import, create, modify, integrate, view, and export geological objects in 3D. The GOCAD export file format supported by ResInsight is TSURF (*.ts). A TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below. ResInsight import vertex and triangle identifiers from the first TFACE section in such a file.\nGOCAD TSurf 1 HEADER { name:MF_027_SU } GOCAD_ORIGINAL_COORDINATE_SYSTEM NAME Default AXIS_NAME \u0026#34;X\u0026#34; \u0026#34;Y\u0026#34; \u0026#34;Z\u0026#34; AXIS_UNIT \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; ZPOSITIVE Depth END_ORIGINAL_COORDINATE_SYSTEM TFACE VRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ VRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ VRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ VRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ VRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ VRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ ...\rTRGL 2 61 98 TRGL 20 153 66 TRGL 152 19 65 END Petrel Surface PTL files ResInsight is capable of importing a surface defined by a PTL (*.ptl) file format. A PTL data file specifies the quads of a surface by x, y, z nodal coordinates and the i and j indices as exemplified below. As seen, # denotes comment lines.\n#Type: scattered data\r#Version: 6\r#Description: No description\r#Format: free\r#Field: 1 x\r#Field: 2 y\r#Field: 3 z meters\r#Field: 4 column\r#Field: 5 row\r#Projection: Local Rectangular\r#Units: meters\r#End: #Information from grid\r#Grid_size: Not_avaiable\r#Grid_space: Not_available\r#Z_field: z\r#Vertical_faults: Not_available\r#History: No history\r#Z_units: meters\r443479.500000 7305390.500000 -1000.000000 1 1\r443479.500000 7305488.500000 -1000.000000 1 2\r443479.500000 7305586.500000 -1000.000000 1 3\r443479.500000 7305684.500000 -1000.000000 1 4\r443479.500000 7305782.500000 -1000.000000 1 5\r443479.500000 7305880.500000 -1000.000000 1 6\r...\rOpenWorks XYZ Surface files ResInsight is capable of importing a surface defined by a XYZ (*.dat) file from OpenWorks. A XYZ data file specifies the quads of a surface by x, y, z nodal coordinates organized in a regular grid. As seen, # and @ denotes comment lines.\n@File_Version: 4\r@Coordinate_Type_is: 1\r@Export_Type_is: 1\r@Number_of_Projects 1\r@Project_Type_Name: , 3,xxx,\r@Project_Unit_is: meters , xxx\r#File_Version____________-\u0026gt; 4\r#Project_Name____________-\u0026gt; xxx\r#Project_Type____________-\u0026gt; 3\r#Export_XY_Unit__________-\u0026gt; meters\r#OpenWorks_Project_______-\u0026gt; \u0026#39;xxx\u0026#39;\r#Master_Project_______-\u0026gt;\r#Coordinate_type_________-\u0026gt; 1\r#Number_of_points_in_hzd_-\u0026gt; 1\r#Horizon_internal_id_____-\u0026gt; xxx\r#Horizon_extremes_are____-\u0026gt; xxx,xxx\r#Horizon_onset_is_Minimum_____-\u0026gt; 1\r#Horizon_type_is_DEPTH_STRUCTURE______-\u0026gt; 2\r#Horizon_color_is________-\u0026gt; 255 0 0\r#Horizon_name____________-\u0026gt; xxx\r#Horizon_attribute_______-\u0026gt; DEPTH_STRUCTURE\r#Horizon_version_________-\u0026gt; UNKNOWN\r#Horizon_interp_status___-\u0026gt; defaultStat\r#Horizon_class___________-\u0026gt; defaultClass\r#Export_Z_Unit___________-\u0026gt; meters\r#Horizon_onset_type______-\u0026gt; Minimum\r#Horizon_data_domain_____-\u0026gt; DEPTH\r#Horizon_remark_size_____-\u0026gt; 50\rHorizon from Grid on Fri Aug 14 13:42:10 CEST 2020\r#End_of_Horizon_ASCII_Header_\r4.5423435e+05 7.3239079e+06 1.5970070e+03\r4.5424414e+05 7.3239157e+06 1.5970485e+03\r4.5425392e+05 7.3239234e+06 1.5970899e+03\r4.5426371e+05 7.3239312e+06 1.5971314e+03 ",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight is capable of mapping properties and simulation results onto 3D surfaces imported from GOCAD and Petrel as specified below.\u003c/p\u003e\n\u003ch2 id=\"import-and-appearance-of-surfaces\"\u003eImport and appearance of surfaces\u003c/h2\u003e\n\u003cp\u003e3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eImport\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eImport Surfaces\u003c/strong\u003e \nin the \u003cstrong\u003e3D Main Window\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesImport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eImported surfaces are listed under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/SurfacesProjectTreeNode.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n entry \nin the \u003cstrong\u003eProject Tree\u003c/strong\u003e. You can click on a surface to change i.e. the name or color of the surface, or change the file to read the surface data from.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eYou can also change the depth of the surface by adding a depth offset (positive or negative). This could be used i.e. to import the same surface file multiple times and assign each instance of the surface a separate depth offset. When a depth offset is set, the offset value will be shown as part of the surface name in the project tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_multiple.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eMultiple surfaces can be imported at the same time by choosing more than one input file in the file selection window that shows up when you start an import.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"using-folders\"\u003eUsing folders\u003c/h2\u003e\n\u003cp\u003eTo make it easier to organize the surfaces you import into your project, ResInsight supports creating surface folders in the project tree. To create a new folder, right-click on the top level \u003cstrong\u003eSurfaces\u003c/strong\u003e folder in the project tree and choose \u003cstrong\u003eAdd Folder\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_addfolder.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"surface-results\"\u003eSurface Results\u003c/h2\u003e\n\u003cp\u003ePer default, ResInsight maps current \u003cstrong\u003eCell Result\u003c/strong\u003e on a given surface. \nIf another result is to be displayed, specify the result under \u003cstrong\u003eSurface Results\u003c/strong\u003e as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesSeparateSurfaceResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eClicking a surface of a \u003cstrong\u003eView\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e activates the Property Editor for allowing view settings as shown below.\u003c/p\u003e\n\u003cp\u003eTo change result displayed on the surface, please specify the desired result in the \u003cstrong\u003eResult Reference\u003c/strong\u003e\nsection of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesViewPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"reloading-surfaces\"\u003eReloading Surfaces\u003c/h2\u003e\n\u003cp\u003eIf you have modified a surface file using an external program, you can easily load the changes into ResInsight by using the reload surface feature. Bring up the right-click menu for the surface you want to reload and choose  \u003cstrong\u003eReload\u003c/strong\u003e. The views will automatically update with the new data (could take a few seconds).\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_reload.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-a-copy\"\u003eCreate a copy\u003c/h2\u003e\n\u003cp\u003eYou can easily create a copy of an existing surface by choosing  \u003cstrong\u003eCreate Copy\u003c/strong\u003e in the surface right-click menu. A new, identical surface will show up at the same level in the project tree. You can now give it a new name, change depth offset etc.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_copy.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"grid-case-surfaces\"\u003eGrid Case Surfaces\u003c/h2\u003e\n\u003cp\u003eIn addition to importing surfaces from file, ResInsight can also generate grid case surfaces. You do that by bringing up the right-click menu for the \u003cimg src=\"https://resinsight.org/images/3d-main-window/SurfacesProjectTreeNode.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n project tree entry and choose \u003cstrong\u003eCreate Grid Case Surfaces\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_gridcase.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA grid case surface has the same properties as a surface imported from file, but instead of choosing which file the data should come from, you choose a source case, a slice direction and a slice index. The slice direction and index will be added to the surface name shown in the project tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surfaces_gridcaseproperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"exporting-surfaces\"\u003eExporting Surfaces\u003c/h2\u003e\n\u003cp\u003eResInsight can export surfaces to the GOCAD TSurf file format. Grid case surfaces can additionally be exported to Petrel Surface PTL format. Use the right-click menu for the surface you want to export and choose the export format you want to use. A file selection window will show up allowing you to choose where you want to save the exported data.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_export.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"supported-surface-formats\"\u003eSupported Surface Formats\u003c/h2\u003e\n\u003ch3 id=\"gocad-surface-format\"\u003eGOCAD Surface format\u003c/h3\u003e\n\u003cp\u003eGOCAD is a computer application that allows you to import, create, modify, integrate, view, and export geological objects in 3D.\nThe GOCAD export file format supported by ResInsight is \u003cstrong\u003eTSURF\u003c/strong\u003e (*.ts). \nA TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below. \nResInsight import vertex and triangle identifiers from the first TFACE section in such a file.\u003c/p\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-txt\" data-lang=\"txt\"\u003eGOCAD TSurf 1 \r\nHEADER { \r\nname:MF_027_SU \r\n} \r\nGOCAD_ORIGINAL_COORDINATE_SYSTEM \r\nNAME Default \r\nAXIS_NAME \u0026#34;X\u0026#34; \u0026#34;Y\u0026#34; \u0026#34;Z\u0026#34; \r\nAXIS_UNIT \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \r\nZPOSITIVE Depth \r\nEND_ORIGINAL_COORDINATE_SYSTEM \r\nTFACE \r\nVRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ \r\nVRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ \r\nVRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ \r\nVRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ \r\nVRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ \r\nVRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ \r\n...\r\nTRGL 2 61 98  \r\nTRGL 20 153 66  \r\nTRGL 152 19 65  \r\nEND \r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"petrel-surface-ptl-files\"\u003ePetrel Surface PTL files\u003c/h3\u003e\n\u003cp\u003eResInsight is capable of importing a surface defined by a \u003cstrong\u003ePTL\u003c/strong\u003e (*.ptl) file format.\nA PTL data file specifies the quads of a surface by \u003cem\u003ex\u003c/em\u003e, \u003cem\u003ey\u003c/em\u003e, \u003cem\u003ez\u003c/em\u003e nodal coordinates and the \u003cem\u003ei\u003c/em\u003e and \u003cem\u003ej\u003c/em\u003e indices as exemplified below. \nAs seen, \u003cem\u003e#\u003c/em\u003e denotes comment lines.\u003c/p\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-txt\" data-lang=\"txt\"\u003e#Type: scattered data\r\n#Version: 6\r\n#Description: No description\r\n#Format: free\r\n#Field: 1 x\r\n#Field: 2 y\r\n#Field: 3 z meters\r\n#Field: 4 column\r\n#Field: 5 row\r\n#Projection: Local Rectangular\r\n#Units: meters\r\n#End: \r\n#Information from grid\r\n#Grid_size: Not_avaiable\r\n#Grid_space: Not_available\r\n#Z_field: z\r\n#Vertical_faults: Not_available\r\n#History: No history\r\n#Z_units: meters\r\n443479.500000 7305390.500000 -1000.000000 1 1\r\n443479.500000 7305488.500000 -1000.000000 1 2\r\n443479.500000 7305586.500000 -1000.000000 1 3\r\n443479.500000 7305684.500000 -1000.000000 1 4\r\n443479.500000 7305782.500000 -1000.000000 1 5\r\n443479.500000 7305880.500000 -1000.000000 1 6\r\n...\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"openworks-xyz-surface-files\"\u003eOpenWorks XYZ Surface files\u003c/h3\u003e\n\u003cp\u003eResInsight is capable of importing a surface defined by a \u003cstrong\u003eXYZ\u003c/strong\u003e (*.dat) file from OpenWorks.\nA XYZ data file specifies the quads of a surface by \u003cem\u003ex\u003c/em\u003e, \u003cem\u003ey\u003c/em\u003e, \u003cem\u003ez\u003c/em\u003e nodal coordinates organized in a regular grid. \nAs seen, \u003cem\u003e#\u003c/em\u003e and \u003cem\u003e@\u003c/em\u003e denotes comment lines.\u003c/p\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-txt\" data-lang=\"txt\"\u003e@File_Version: 4\r\n@Coordinate_Type_is: 1\r\n@Export_Type_is: 1\r\n@Number_of_Projects 1\r\n@Project_Type_Name: , 3,xxx,\r\n@Project_Unit_is: meters , xxx\r\n#File_Version____________-\u0026gt; 4\r\n#Project_Name____________-\u0026gt; xxx\r\n#Project_Type____________-\u0026gt; 3\r\n#Export_XY_Unit__________-\u0026gt; meters\r\n#OpenWorks_Project_______-\u0026gt; \u0026#39;xxx\u0026#39;\r\n#Master_Project_______-\u0026gt;\r\n#Coordinate_type_________-\u0026gt; 1\r\n#Number_of_points_in_hzd_-\u0026gt; 1\r\n#Horizon_internal_id_____-\u0026gt; xxx\r\n#Horizon_extremes_are____-\u0026gt; xxx,xxx\r\n#Horizon_onset_is_Minimum_____-\u0026gt; 1\r\n#Horizon_type_is_DEPTH_STRUCTURE______-\u0026gt; 2\r\n#Horizon_color_is________-\u0026gt; 255 0 0\r\n#Horizon_name____________-\u0026gt; xxx\r\n#Horizon_attribute_______-\u0026gt; DEPTH_STRUCTURE\r\n#Horizon_version_________-\u0026gt; UNKNOWN\r\n#Horizon_interp_status___-\u0026gt; defaultStat\r\n#Horizon_class___________-\u0026gt; defaultClass\r\n#Export_Z_Unit___________-\u0026gt; meters\r\n#Horizon_onset_type______-\u0026gt; Minimum\r\n#Horizon_data_domain_____-\u0026gt; DEPTH\r\n#Horizon_remark_size_____-\u0026gt; 50\r\nHorizon from Grid on Fri Aug 14 13:42:10 CEST 2020\r\n#End_of_Horizon_ASCII_Header_\r\n   4.5423435e+05   7.3239079e+06   1.5970070e+03\r\n   4.5424414e+05   7.3239157e+06   1.5970485e+03\r\n   4.5425392e+05   7.3239234e+06   1.5970899e+03\r\n   4.5426371e+05   7.3239312e+06   1.5971314e+03 \r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
+                content:  "\nResInsight is capable of mapping properties and simulation results onto 3D surfaces imported from GOCAD and Petrel as specified below.\nImport and appearance of surfaces 3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option File-\u0026gt;Import-\u0026gt;Import Surfaces in the 3D Main Window.\nImported surfaces are listed under the entry in the Project Tree. You can click on a surface to change i.e. the name or color of the surface, or change the file to read the surface data from.\nYou can also change the depth of the surface by adding a depth offset (positive or negative). This could be used i.e. to import the same surface file multiple times and assign each instance of the surface a separate depth offset. When a depth offset is set, the offset value will be shown as part of the surface name in the project tree.\nMultiple surfaces can be imported at the same time by choosing more than one input file in the file selection window that shows up when you start an import.\nUsing folders To make it easier to organize the surfaces you import into your project, ResInsight supports creating surface folders in the project tree. To create a new folder, right-click on the top level Surfaces folder in the project tree and choose Add Folder.\nSurface Results Per default, ResInsight maps current Cell Result on a given surface. If another result is to be displayed, specify the result under Surface Results as shown below.\nClicking a surface of a View in the Project Tree activates the Property Editor for allowing view settings as shown below.\nTo change result displayed on the surface, please specify the desired result in the Result Reference section of the Property Editor.\nReloading Surfaces If you have modified a surface file using an external program, you can easily load the changes into ResInsight by using the reload surface feature. Bring up the right-click menu for the surface you want to reload and choose Reload. The views will automatically update with the new data (could take a few seconds).\nCreate a copy You can easily create a copy of an existing surface by choosing Create Copy in the surface right-click menu. A new, identical surface will show up at the same level in the project tree. You can now give it a new name, change depth offset etc.\nGrid Case Surfaces In addition to importing surfaces from file, ResInsight can also generate grid case surfaces. You do that by bringing up the right-click menu for the project tree entry and choose Create Grid Case Surfaces.\nA grid case surface has the same properties as a surface imported from file, but instead of choosing which file the data should come from, you choose a source case, a slice direction and a slice index. The slice direction and index will be added to the surface name shown in the project tree.\nExporting Surfaces ResInsight can export surfaces to the GOCAD TSurf file format. Grid case surfaces can additionally be exported to Petrel Surface PTL format. Use the right-click menu for the surface you want to export and choose the export format you want to use. A file selection window will show up allowing you to choose where you want to save the exported data.\nSupported Surface Formats GOCAD Surface format GOCAD is a computer application that allows you to import, create, modify, integrate, view, and export geological objects in 3D. The GOCAD export file format supported by ResInsight is TSURF (*.ts). A TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below. ResInsight import vertex and triangle identifiers from the first TFACE section in such a file.\nGOCAD TSurf 1 HEADER { name:MF_027_SU } GOCAD_ORIGINAL_COORDINATE_SYSTEM NAME Default AXIS_NAME \u0026#34;X\u0026#34; \u0026#34;Y\u0026#34; \u0026#34;Z\u0026#34; AXIS_UNIT \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; ZPOSITIVE Depth END_ORIGINAL_COORDINATE_SYSTEM TFACE VRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ VRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ VRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ VRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ VRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ VRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ ... TRGL 2 61 98 TRGL 20 153 66 TRGL 152 19 65 END Petrel Surface PTL files ResInsight is capable of importing a surface defined by a PTL (*.ptl) file format. A PTL data file specifies the quads of a surface by x, y, z nodal coordinates and the i and j indices as exemplified below. As seen, # denotes comment lines.\n#Type: scattered data #Version: 6 #Description: No description #Format: free #Field: 1 x #Field: 2 y #Field: 3 z meters #Field: 4 column #Field: 5 row #Projection: Local Rectangular #Units: meters #End: #Information from grid #Grid_size: Not_avaiable #Grid_space: Not_available #Z_field: z #Vertical_faults: Not_available #History: No history #Z_units: meters 443479.500000 7305390.500000 -1000.000000 1 1 443479.500000 7305488.500000 -1000.000000 1 2 443479.500000 7305586.500000 -1000.000000 1 3 443479.500000 7305684.500000 -1000.000000 1 4 443479.500000 7305782.500000 -1000.000000 1 5 443479.500000 7305880.500000 -1000.000000 1 6 ... OpenWorks XYZ Surface files ResInsight is capable of importing a surface defined by a XYZ (*.dat) file from OpenWorks. A XYZ data file specifies the quads of a surface by x, y, z nodal coordinates organized in a regular grid. As seen, # and @ denotes comment lines.\n@File_Version: 4 @Coordinate_Type_is: 1 @Export_Type_is: 1 @Number_of_Projects 1 @Project_Type_Name: , 3,xxx, @Project_Unit_is: meters , xxx #File_Version____________-\u0026gt; 4 #Project_Name____________-\u0026gt; xxx #Project_Type____________-\u0026gt; 3 #Export_XY_Unit__________-\u0026gt; meters #OpenWorks_Project_______-\u0026gt; \u0026#39;xxx\u0026#39; #Master_Project_______-\u0026gt; #Coordinate_type_________-\u0026gt; 1 #Number_of_points_in_hzd_-\u0026gt; 1 #Horizon_internal_id_____-\u0026gt; xxx #Horizon_extremes_are____-\u0026gt; xxx,xxx #Horizon_onset_is_Minimum_____-\u0026gt; 1 #Horizon_type_is_DEPTH_STRUCTURE______-\u0026gt; 2 #Horizon_color_is________-\u0026gt; 255 0 0 #Horizon_name____________-\u0026gt; xxx #Horizon_attribute_______-\u0026gt; DEPTH_STRUCTURE #Horizon_version_________-\u0026gt; UNKNOWN #Horizon_interp_status___-\u0026gt; defaultStat #Horizon_class___________-\u0026gt; defaultClass #Export_Z_Unit___________-\u0026gt; meters #Horizon_onset_type______-\u0026gt; Minimum #Horizon_data_domain_____-\u0026gt; DEPTH #Horizon_remark_size_____-\u0026gt; 50 Horizon from Grid on Fri Aug 14 13:42:10 CEST 2020 #End_of_Horizon_ASCII_Header_ 4.5423435e+05 7.3239079e+06 1.5970070e+03 4.5424414e+05 7.3239157e+06 1.5970485e+03 4.5425392e+05 7.3239234e+06 1.5970899e+03 4.5426371e+05 7.3239312e+06 1.5971314e+03 ",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesOverview.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eResInsight is capable of mapping properties and simulation results onto 3D surfaces imported from GOCAD and Petrel as specified below.\u003c/p\u003e\n\u003ch2 id=\"import-and-appearance-of-surfaces\"\u003eImport and appearance of surfaces\u003c/h2\u003e\n\u003cp\u003e3D surfaces from GOCAD and Petrel are imported into ResInsight by the menu option \u003cstrong\u003eFile\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eImport\u003c/strong\u003e-\u0026gt;\u003cstrong\u003eImport Surfaces\u003c/strong\u003e\nin the \u003cstrong\u003e3D Main Window\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesImport.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eImported surfaces are listed under the \u003cimg src=\"https://resinsight.org/images/3d-main-window/SurfacesProjectTreeNode.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n entry\nin the \u003cstrong\u003eProject Tree\u003c/strong\u003e. You can click on a surface to change i.e. the name or color of the surface, or change the file to read the surface data from.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eYou can also change the depth of the surface by adding a depth offset (positive or negative). This could be used i.e. to import the same surface file multiple times and assign each instance of the surface a separate depth offset. When a depth offset is set, the offset value will be shown as part of the surface name in the project tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_multiple.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eMultiple surfaces can be imported at the same time by choosing more than one input file in the file selection window that shows up when you start an import.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"using-folders\"\u003eUsing folders\u003c/h2\u003e\n\u003cp\u003eTo make it easier to organize the surfaces you import into your project, ResInsight supports creating surface folders in the project tree. To create a new folder, right-click on the top level \u003cstrong\u003eSurfaces\u003c/strong\u003e folder in the project tree and choose \u003cstrong\u003eAdd Folder\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_addfolder.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"surface-results\"\u003eSurface Results\u003c/h2\u003e\n\u003cp\u003ePer default, ResInsight maps current \u003cstrong\u003eCell Result\u003c/strong\u003e on a given surface.\nIf another result is to be displayed, specify the result under \u003cstrong\u003eSurface Results\u003c/strong\u003e as shown below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesSeparateSurfaceResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eClicking a surface of a \u003cstrong\u003eView\u003c/strong\u003e in the \u003cstrong\u003eProject Tree\u003c/strong\u003e activates the Property Editor for allowing view settings as shown below.\u003c/p\u003e\n\u003cp\u003eTo change result displayed on the surface, please specify the desired result in the \u003cstrong\u003eResult Reference\u003c/strong\u003e\nsection of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/SurfacesViewPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"reloading-surfaces\"\u003eReloading Surfaces\u003c/h2\u003e\n\u003cp\u003eIf you have modified a surface file using an external program, you can easily load the changes into ResInsight by using the reload surface feature. Bring up the right-click menu for the surface you want to reload and choose  \u003cstrong\u003eReload\u003c/strong\u003e. The views will automatically update with the new data (could take a few seconds).\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_reload.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"create-a-copy\"\u003eCreate a copy\u003c/h2\u003e\n\u003cp\u003eYou can easily create a copy of an existing surface by choosing  \u003cstrong\u003eCreate Copy\u003c/strong\u003e in the surface right-click menu. A new, identical surface will show up at the same level in the project tree. You can now give it a new name, change depth offset etc.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_copy.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"grid-case-surfaces\"\u003eGrid Case Surfaces\u003c/h2\u003e\n\u003cp\u003eIn addition to importing surfaces from file, ResInsight can also generate grid case surfaces. You do that by bringing up the right-click menu for the \u003cimg src=\"https://resinsight.org/images/3d-main-window/SurfacesProjectTreeNode.png\" style=\"display:inline; vertical-align:middle; margin:0\"\u003e\r\n project tree entry and choose \u003cstrong\u003eCreate Grid Case Surfaces\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_gridcase.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA grid case surface has the same properties as a surface imported from file, but instead of choosing which file the data should come from, you choose a source case, a slice direction and a slice index. The slice direction and index will be added to the surface name shown in the project tree.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surfaces_gridcaseproperties.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"exporting-surfaces\"\u003eExporting Surfaces\u003c/h2\u003e\n\u003cp\u003eResInsight can export surfaces to the GOCAD TSurf file format. Grid case surfaces can additionally be exported to Petrel Surface PTL format. Use the right-click menu for the surface you want to export and choose the export format you want to use. A file selection window will show up allowing you to choose where you want to save the exported data.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/surface_export.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"supported-surface-formats\"\u003eSupported Surface Formats\u003c/h2\u003e\n\u003ch3 id=\"gocad-surface-format\"\u003eGOCAD Surface format\u003c/h3\u003e\n\u003cp\u003eGOCAD is a computer application that allows you to import, create, modify, integrate, view, and export geological objects in 3D.\nThe GOCAD export file format supported by ResInsight is \u003cstrong\u003eTSURF\u003c/strong\u003e (*.ts).\nA TSURF data file is a triangle based surface format containing vertex coordinates and triangle to vertex connectivities as exemplified below.\nResInsight import vertex and triangle identifiers from the first TFACE section in such a file.\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eGOCAD TSurf 1 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eHEADER { \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ename:MF_027_SU \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e} \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eGOCAD_ORIGINAL_COORDINATE_SYSTEM \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eNAME Default \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eAXIS_NAME \u0026#34;X\u0026#34; \u0026#34;Y\u0026#34; \u0026#34;Z\u0026#34; \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eAXIS_UNIT \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \u0026#34;m\u0026#34; \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eZPOSITIVE Depth \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eEND_ORIGINAL_COORDINATE_SYSTEM \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eTFACE \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 1 458177.767090 7322538.712891 1643.655884 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 2 458260.834961 7322392.890625 1596.685303 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 3 457985.662109 7322783.783203 1542.060059 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 4 459601.453125 7322511.427734 3639.000000 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 5 459422.015625 7322689.230469 3639.000000 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eVRTX 6 459793.410156 7322338.230469 3639.000000 CNXYZ \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e...\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eTRGL 2 61 98  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eTRGL 20 153 66  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eTRGL 152 19 65  \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eEND \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"petrel-surface-ptl-files\"\u003ePetrel Surface PTL files\u003c/h3\u003e\n\u003cp\u003eResInsight is capable of importing a surface defined by a \u003cstrong\u003ePTL\u003c/strong\u003e (*.ptl) file format.\nA PTL data file specifies the quads of a surface by \u003cem\u003ex\u003c/em\u003e, \u003cem\u003ey\u003c/em\u003e, \u003cem\u003ez\u003c/em\u003e nodal coordinates and the \u003cem\u003ei\u003c/em\u003e and \u003cem\u003ej\u003c/em\u003e indices as exemplified below.\nAs seen, \u003cem\u003e#\u003c/em\u003e denotes comment lines.\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Type: scattered data\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Version: 6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Description: No description\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Format: free\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Field: 1 x\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Field: 2 y\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Field: 3 z meters\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Field: 4 column\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Field: 5 row\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Projection: Local Rectangular\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Units: meters\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#End: \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Information from grid\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Grid_size: Not_avaiable\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Grid_space: Not_available\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Z_field: z\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Vertical_faults: Not_available\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#History: No history\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Z_units: meters\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305390.500000 -1000.000000 1 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305488.500000 -1000.000000 1 2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305586.500000 -1000.000000 1 3\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305684.500000 -1000.000000 1 4\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305782.500000 -1000.000000 1 5\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e443479.500000 7305880.500000 -1000.000000 1 6\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e...\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch3 id=\"openworks-xyz-surface-files\"\u003eOpenWorks XYZ Surface files\u003c/h3\u003e\n\u003cp\u003eResInsight is capable of importing a surface defined by a \u003cstrong\u003eXYZ\u003c/strong\u003e (*.dat) file from OpenWorks.\nA XYZ data file specifies the quads of a surface by \u003cem\u003ex\u003c/em\u003e, \u003cem\u003ey\u003c/em\u003e, \u003cem\u003ez\u003c/em\u003e nodal coordinates organized in a regular grid.\nAs seen, \u003cem\u003e#\u003c/em\u003e and \u003cem\u003e@\u003c/em\u003e denotes comment lines.\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@File_Version: 4\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@Coordinate_Type_is: 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@Export_Type_is: 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@Number_of_Projects 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@Project_Type_Name: , 3,xxx,\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e@Project_Unit_is: meters , xxx\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#File_Version____________-\u0026gt; 4\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Project_Name____________-\u0026gt; xxx\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Project_Type____________-\u0026gt; 3\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Export_XY_Unit__________-\u0026gt; meters\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#OpenWorks_Project_______-\u0026gt; \u0026#39;xxx\u0026#39;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Master_Project_______-\u0026gt;\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Coordinate_type_________-\u0026gt; 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Number_of_points_in_hzd_-\u0026gt; 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_internal_id_____-\u0026gt; xxx\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_extremes_are____-\u0026gt; xxx,xxx\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_onset_is_Minimum_____-\u0026gt; 1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_type_is_DEPTH_STRUCTURE______-\u0026gt; 2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_color_is________-\u0026gt; 255 0 0\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_name____________-\u0026gt; xxx\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_attribute_______-\u0026gt; DEPTH_STRUCTURE\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_version_________-\u0026gt; UNKNOWN\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_interp_status___-\u0026gt; defaultStat\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_class___________-\u0026gt; defaultClass\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Export_Z_Unit___________-\u0026gt; meters\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_onset_type______-\u0026gt; Minimum\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_data_domain_____-\u0026gt; DEPTH\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#Horizon_remark_size_____-\u0026gt; 50\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eHorizon from Grid on Fri Aug 14 13:42:10 CEST 2020\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e#End_of_Horizon_ASCII_Header_\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   4.5423435e+05   7.3239079e+06   1.5970070e+03\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   4.5424414e+05   7.3239157e+06   1.5970485e+03\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   4.5425392e+05   7.3239234e+06   1.5970899e+03\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e   4.5426371e+05   7.3239312e+06   1.5971314e+03 \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/3d-main-window/surfaces/"
             };
         
@@ -3821,8 +3820,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/allandiagrams/"] = {
                 title:    "Allan Diagram",
-                content:  "Allan Diagrams displays the overlap of formations and layers across fault faces.\nSeparate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults  for more details.\nProperty Editor Settings  Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault  Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault. The Result Info text is updated when the selected cell is changed.\nOther related results Other useful NNC results are descrived in Derived Results\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AllanDiagram.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAllan Diagrams\u003c/strong\u003e displays the overlap of formations and layers across fault faces.\u003c/p\u003e\n\u003ch2 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eAllan Diagram\u003c/strong\u003e is dispayed by selecting the \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e in the project tree. \n\u003cimg src=\"/images/3d-main-window/AllanDiagramPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/faults/#separate-fault-result\"\u003eFaults \u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch2 id=\"property-editor-settings\"\u003eProperty Editor Settings\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eBinary Formation Allan\u003c/strong\u003e One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Allan\u003c/strong\u003e Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"mouse-interaction\"\u003eMouse interaction\u003c/h2\u003e\n\u003cp\u003eWhen clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault. The Result Info text is updated when the selected cell is changed.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AllanDiagramCellHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"other-related-results\"\u003eOther related results\u003c/h2\u003e\n\u003cp\u003eOther useful NNC results are descrived in \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "\nAllan Diagrams displays the overlap of formations and layers across fault faces.\nSeparate Fault Result The Allan Diagram is dispayed by selecting the Separate Fault Result in the project tree. See Faults for more details.\nProperty Editor Settings Binary Formation Allan One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault Formation Allan Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault Mouse interaction When clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault. The Result Info text is updated when the selected cell is changed.\nOther related results Other useful NNC results are descrived in Derived Results\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AllanDiagram.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eAllan Diagrams\u003c/strong\u003e displays the overlap of formations and layers across fault faces.\u003c/p\u003e\n\u003ch2 id=\"separate-fault-result\"\u003eSeparate Fault Result\u003c/h2\u003e\n\u003cp\u003eThe \u003cstrong\u003eAllan Diagram\u003c/strong\u003e is dispayed by selecting the \u003cstrong\u003eSeparate Fault Result\u003c/strong\u003e in the project tree.\n\u003cimg src=\"/images/3d-main-window/AllanDiagramPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eSee \u003ca href=\"/3d-main-window/faults/#separate-fault-result\"\u003eFaults \u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch2 id=\"property-editor-settings\"\u003eProperty Editor Settings\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eBinary Formation Allan\u003c/strong\u003e One color for all NNC areas with same formation on across fault, and one color for NNC with different formations across fault\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFormation Allan\u003c/strong\u003e Formation colors are used, and a mix of the two formation colors are displayed if we have different formations across fault\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"mouse-interaction\"\u003eMouse interaction\u003c/h2\u003e\n\u003cp\u003eWhen clicking on an NNC area multiple times, the highlighted cell switched from the cell in front of the formation and behind the fault. The Result Info text is updated when the selected cell is changed.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/AllanDiagramCellHighlight.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"other-related-results\"\u003eOther related results\u003c/h2\u003e\n\u003cp\u003eOther useful NNC results are descrived in \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/allandiagrams/"
             };
         
@@ -3830,7 +3829,7 @@ if (!doNotTrack) {
          
             window.store["/workflows/biotcoefficient/"] = {
                 title:    "Biot Coefficient",
-                content:  "Background\nThe Biot porelastic coefficient defines the compressibility of sand grains, and will influence some of the calculations in ResInsight.\nDescription The Biot coefficient can be defined in three ways:\n Default (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table  These settings are controlled from the Property Editor when a Geomechanical Case is selected. To use Biot coefficients for each element, perform the following steps:\n Import values using Import Element Property Select Biot Coefficient from element properties Select the property to be used for Biot coefficient values  The state of an active Biot coefficient is indicated in the info box in upper right coner in the 3D view. This will make sure the Biot coefficient information is availalbe when a snapshot is produced.\n\rRelated documents Element Property Table\nDerived Results\n",
+                content:  "Background\nThe Biot porelastic coefficient defines the compressibility of sand grains, and will influence some of the calculations in ResInsight.\nDescription The Biot coefficient can be defined in three ways:\nDefault (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table These settings are controlled from the Property Editor when a Geomechanical Case is selected. To use Biot coefficients for each element, perform the following steps:\nImport values using Import Element Property Select Biot Coefficient from element properties Select the property to be used for Biot coefficient values The state of an active Biot coefficient is indicated in the info box in upper right coner in the 3D view. This will make sure the Biot coefficient information is availalbe when a snapshot is produced.\nRelated documents Element Property Table\nDerived Results\n",
                 html:     "\u003cp\u003e\u003cstrong\u003eBackground\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThe Biot porelastic coefficient defines the compressibility of sand grains, and will influence some of the calculations in ResInsight.\u003c/p\u003e\n\u003ch2 id=\"description\"\u003eDescription\u003c/h2\u003e\n\u003cp\u003eThe Biot coefficient can be defined in three ways:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eDefault (Constant value of 1.0)\u003c/li\u003e\n\u003cli\u003eUser defined constant for all element\u003c/li\u003e\n\u003cli\u003eOne value for each element based on imported values from an element property table\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThese settings are controlled from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e when a \u003cstrong\u003eGeomechanical Case\u003c/strong\u003e is selected. To use Biot coefficients for each element, perform the following steps:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eImport values using \u003cstrong\u003eImport Element Property\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eSelect Biot Coefficient from element properties\u003c/li\u003e\n\u003cli\u003eSelect the property to be used for Biot coefficient values\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GeoMechCasePropertyPanel.png\" alt=\"\"\u003e\u003c/p\u003e\n\r\n\u003cdiv class=\"notices note\" \u003e\u003cp\u003eThe state of an active Biot coefficient is indicated in the info box in upper right coner in the 3D view. This will  make sure the Biot coefficient information is availalbe when a snapshot is produced.\u003c/p\u003e\n\u003c/div\u003e\r\n\n\u003ch2 id=\"related-documents\"\u003eRelated documents\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/import/elementpropertytable/\"\u003eElement Property Table\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/derivedresultsgeomech/#st---total-stress\"\u003eDerived Results\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/workflows/biotcoefficient/"
             };
@@ -3839,8 +3838,8 @@ if (!doNotTrack) {
          
             window.store["/workflows/ensemblesurface/"] = {
                 title:    "Ensemble Surface",
-                content:  "Introduction To study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of Ensemble Surfaces. See Python Examples for more details.\nCreate Ensemble Surface   From the right-click menu of surfaces, select Import Ensemble Surface   Select the ensemble grid models to create surfaces for, either \u0026quot;*.EGRID\u0026rdquo; or \u0026quot;*.GRDECL\u0026rdquo;\n  In the following dialog, select the K layers. Control if the generated surfaces should be imported into an ensemble surface immediately.   Import Ensemble Surface An Ensemble Surface can be imported for one or multiple K-layers.\n  From the right-click menu of surfaces, select Import Ensemble Surface   In the ensemble import dialog, select the surface files for import into ensembles   One or multiple ensemble surface objects will be created   Import one source grid model and create a 3D view\n  Control the visibility of the statistics surfaces in the Surfaces section in the Property Editor for the 3D view   Show uncertainty on intersections   Create a well path\n  Create an intersection along the well path\n  Select the intersection in the Property Editor\n  From the right-click menu, select Create Intersection Band   Optionally add an Intersection Curve\n  Adjust options for the intersection bands and curves   Related documentation Create a Well Path\nIntersections\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/surface/surface-in-3d.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\u003cp\u003eTo study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of \u003cstrong\u003eEnsemble Surfaces\u003c/strong\u003e. See  \u003ca href=\"https://api.resinsight.org/en/stable/PythonExamples.html\"\u003ePython Examples\u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch2 id=\"create-ensemble-surface\"\u003eCreate Ensemble Surface\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of surfaces, select \u003cstrong\u003eImport Ensemble Surface\u003c/strong\u003e\n\u003cimg src=\"/images/workflows/create_ensemble_surface_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect the ensemble grid models to create surfaces for, either \u003cstrong\u003e\u0026quot;*.EGRID\u0026rdquo;\u003c/strong\u003e or \u003cstrong\u003e\u0026quot;*.GRDECL\u0026rdquo;\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the following dialog, select the K layers. Control if the generated surfaces should be imported into an ensemble surface immediately.\n\u003cimg src=\"/images/workflows/ensemble_surface_select_k_layers.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"import-ensemble-surface\"\u003eImport Ensemble Surface\u003c/h2\u003e\n\u003cp\u003eAn \u003cstrong\u003eEnsemble Surface\u003c/strong\u003e can be imported for one or multiple K-layers.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of surfaces, select \u003cstrong\u003eImport Ensemble Surface\u003c/strong\u003e\n\u003cimg src=\"/images/surface/import-ensemble-surface.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the ensemble import dialog, select the surface files for import into ensembles\n\u003cimg src=\"/images/surface/ensemble-surface-file-selection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eOne or multiple ensemble surface objects will be created\n\u003cimg src=\"/images/surface/surface-project-tree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eImport one source grid model and create a 3D view\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eControl the visibility of the statistics surfaces in the \u003cstrong\u003eSurfaces\u003c/strong\u003e section in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for the 3D view\n\u003cimg src=\"/images/surface/surface-in-view-project-tree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"show-uncertainty-on-intersections\"\u003eShow uncertainty on intersections\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eCreate a well path\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eCreate an intersection along the well path\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect the intersection in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu, select \u003cstrong\u003eCreate Intersection Band\u003c/strong\u003e\n\u003cimg src=\"/images/surface/create-surface-intersection-band.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eOptionally add an Intersection Curve\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAdjust options for the intersection bands and curves\n\u003cimg src=\"/images/surface/intersection-band-in-3d-view.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"related-documentation\"\u003eRelated documentation\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate a Well Path\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "\nIntroduction To study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of Ensemble Surfaces. See Python Examples for more details.\nCreate Ensemble Surface From the right-click menu of surfaces, select Import Ensemble Surface Select the ensemble grid models to create surfaces for, either \u0026quot;*.EGRID\u0026quot; or \u0026quot;*.GRDECL\u0026quot;\nIn the following dialog, select the K layers. Control if the generated surfaces should be imported into an ensemble surface immediately. Import Ensemble Surface An Ensemble Surface can be imported for one or multiple K-layers.\nFrom the right-click menu of surfaces, select Import Ensemble Surface In the ensemble import dialog, select the surface files for import into ensembles One or multiple ensemble surface objects will be created Import one source grid model and create a 3D view\nControl the visibility of the statistics surfaces in the Surfaces section in the Property Editor for the 3D view Show uncertainty on intersections Create a well path\nCreate an intersection along the well path\nSelect the intersection in the Property Editor\nFrom the right-click menu, select Create Intersection Band Optionally add an Intersection Curve\nAdjust options for the intersection bands and curves Related documentation Create a Well Path\nIntersections\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/surface/surface-in-3d.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\u003cp\u003eTo study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of \u003cstrong\u003eEnsemble Surfaces\u003c/strong\u003e. See  \u003ca href=\"https://api.resinsight.org/en/stable/PythonExamples.html\"\u003ePython Examples\u003c/a\u003e for more details.\u003c/p\u003e\n\u003ch2 id=\"create-ensemble-surface\"\u003eCreate Ensemble Surface\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of surfaces, select \u003cstrong\u003eImport Ensemble Surface\u003c/strong\u003e\n\u003cimg src=\"/images/workflows/create_ensemble_surface_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect the ensemble grid models to create surfaces for, either \u003cstrong\u003e\u0026quot;*.EGRID\u0026quot;\u003c/strong\u003e or \u003cstrong\u003e\u0026quot;*.GRDECL\u0026quot;\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the following dialog, select the K layers. Control if the generated surfaces should be imported into an ensemble surface immediately.\n\u003cimg src=\"/images/workflows/ensemble_surface_select_k_layers.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"import-ensemble-surface\"\u003eImport Ensemble Surface\u003c/h2\u003e\n\u003cp\u003eAn \u003cstrong\u003eEnsemble Surface\u003c/strong\u003e can be imported for one or multiple K-layers.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of surfaces, select \u003cstrong\u003eImport Ensemble Surface\u003c/strong\u003e\n\u003cimg src=\"/images/surface/import-ensemble-surface.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the ensemble import dialog, select the surface files for import into ensembles\n\u003cimg src=\"/images/surface/ensemble-surface-file-selection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eOne or multiple ensemble surface objects will be created\n\u003cimg src=\"/images/surface/surface-project-tree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eImport one source grid model and create a 3D view\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eControl the visibility of the statistics surfaces in the \u003cstrong\u003eSurfaces\u003c/strong\u003e section in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e for the 3D view\n\u003cimg src=\"/images/surface/surface-in-view-project-tree.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"show-uncertainty-on-intersections\"\u003eShow uncertainty on intersections\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eCreate a well path\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eCreate an intersection along the well path\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect the intersection in the \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu, select \u003cstrong\u003eCreate Intersection Band\u003c/strong\u003e\n\u003cimg src=\"/images/surface/create-surface-intersection-band.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eOptionally add an Intersection Curve\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eAdjust options for the intersection bands and curves\n\u003cimg src=\"/images/surface/intersection-band-in-3d-view.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"related-documentation\"\u003eRelated documentation\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/wells-and-completions/createnewwellpaths/\"\u003eCreate a Well Path\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/intersections/\"\u003eIntersections\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/workflows/ensemblesurface/"
             };
         
@@ -3848,8 +3847,8 @@ if (!doNotTrack) {
          
             window.store["/workflows/ensemblewelllog/"] = {
                 title:    "Ensemble Well Log",
-                content:  "Introduction To study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.\nWorkflow   From the right-click menu of Wells, select Create Ensemble Well Log   In the ensemble import dialog, select the files for import into ensembles   Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files   Click OK when you are ready\n  A Well Log Plot is created in the Plot Window   If the geometry is different in the ensembles (structural uncertainty), a depth equalization method is implemented. If the well is crossing layers in the same order across the different ensembles, it is possible to apply a depth equalization from the Property Editor\n  In the plot above, the part where the crossing of K-layers is consistent, we get an easy to read plot. When the K-layer crossings do not match anymore, it is clearly visible that the plot is not able to display the information correctly.\nRelated documentation Well Log Extraction Ensemble File Dialog\n",
-                html:     "\u003cp\u003e\u003cimg src=\"/images/workflows/well_log_ensemble_plot_depth_eq.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\u003cp\u003eTo study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.\u003c/p\u003e\n\u003ch2 id=\"workflow\"\u003eWorkflow\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of Wells, select \u003cstrong\u003eCreate Ensemble Well Log\u003c/strong\u003e\n\u003cimg src=\"/images/workflows/create_ensemble_well_log_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the ensemble import dialog, select the files for import into ensembles\n\u003cimg src=\"/images/workflows/well_log_ensemble_file_dialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files\n\u003cimg src=\"/images/workflows/well_log_ensemble_well_path.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eClick \u003cstrong\u003eOK\u003c/strong\u003e when you are ready\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eA \u003cstrong\u003eWell Log Plot\u003c/strong\u003e is created in the \u003cstrong\u003ePlot Window\u003c/strong\u003e \n\u003cimg src=\"/images/workflows/well_log_ensemble_plot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIf the geometry is different in the ensembles (structural uncertainty), a depth equalization method is implemented. If the well is crossing layers in the same order across the different ensembles, it is possible to apply a depth equalization from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/workflows/property_editor_depth_eq.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/workflows/well_log_ensemble_plot_depth_eq.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the plot above, the part where the crossing of K-layers is consistent, we get an easy to read plot. When the K-layer crossings do not match anymore, it is clearly visible that the plot is not able to display the information correctly.\u003c/p\u003e\n\u003ch2 id=\"related-documentation\"\u003eRelated documentation\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Extraction\u003c/a\u003e\n\u003ca href=\"/import/ensemblefiledialog/\"\u003eEnsemble File Dialog\u003c/a\u003e\u003c/p\u003e\n",
+                content:  "\nIntroduction To study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.\nWorkflow From the right-click menu of Wells, select Create Ensemble Well Log In the ensemble import dialog, select the files for import into ensembles Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files Click OK when you are ready\nA Well Log Plot is created in the Plot Window If the geometry is different in the ensembles (structural uncertainty), a depth equalization method is implemented. If the well is crossing layers in the same order across the different ensembles, it is possible to apply a depth equalization from the Property Editor\nIn the plot above, the part where the crossing of K-layers is consistent, we get an easy to read plot. When the K-layer crossings do not match anymore, it is clearly visible that the plot is not able to display the information correctly.\nRelated documentation Well Log Extraction Ensemble File Dialog\n",
+                html:     "\u003cp\u003e\u003cimg src=\"/images/workflows/well_log_ensemble_plot_depth_eq.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"introduction\"\u003eIntroduction\u003c/h2\u003e\n\u003cp\u003eTo study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.\u003c/p\u003e\n\u003ch2 id=\"workflow\"\u003eWorkflow\u003c/h2\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eFrom the right-click menu of Wells, select \u003cstrong\u003eCreate Ensemble Well Log\u003c/strong\u003e\n\u003cimg src=\"/images/workflows/create_ensemble_well_log_menu.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIn the ensemble import dialog, select the files for import into ensembles\n\u003cimg src=\"/images/workflows/well_log_ensemble_file_dialog.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eSelect well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files\n\u003cimg src=\"/images/workflows/well_log_ensemble_well_path.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eClick \u003cstrong\u003eOK\u003c/strong\u003e when you are ready\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003eA \u003cstrong\u003eWell Log Plot\u003c/strong\u003e is created in the \u003cstrong\u003ePlot Window\u003c/strong\u003e\n\u003cimg src=\"/images/workflows/well_log_ensemble_plot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003eIf the geometry is different in the ensembles (structural uncertainty), a depth equalization method is implemented. If the well is crossing layers in the same order across the different ensembles, it is possible to apply a depth equalization from the \u003cstrong\u003eProperty Editor\u003c/strong\u003e\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/workflows/property_editor_depth_eq.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/workflows/well_log_ensemble_plot_depth_eq.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eIn the plot above, the part where the crossing of K-layers is consistent, we get an easy to read plot. When the K-layer crossings do not match anymore, it is clearly visible that the plot is not able to display the information correctly.\u003c/p\u003e\n\u003ch2 id=\"related-documentation\"\u003eRelated documentation\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Extraction\u003c/a\u003e\n\u003ca href=\"/import/ensemblefiledialog/\"\u003eEnsemble File Dialog\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/workflows/ensemblewelllog/"
             };
         
@@ -3857,8 +3856,8 @@ 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.\nRelated pages :\nAllan Diagrams\nDerived Results\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.\nWhen the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See Derived Results for details on other NNC related results.\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.\nFault 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 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.\nPlease note that the groups Fault Face Visibility and NNC Visibility are available below result selection.\nUseful NNC results are descrived in Derived Results\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 Options  Use Cell filters for Faults \u0026ndash; When checked, use the currently active cell filters to filter the visible faults.  Fault 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 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\u003cp\u003e\u003cstrong\u003eRelated pages :\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/allandiagrams/\"\u003eAllan Diagrams\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\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 \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\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\u003cp\u003eWhen the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e for details on other NNC related results.\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=\"fault-result\"\u003eFault 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\u003eFault 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\u003cp\u003ePlease note that the groups \u003ca href=\"#fault-face-visibility\"\u003eFault Face Visibility\u003c/a\u003e and \u003ca href=\"#nnc-visibility\"\u003eNNC Visibility\u003c/a\u003e are available below result selection.\u003c/p\u003e\n\u003cp\u003eUseful NNC results are descrived in \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\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\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\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-options\"\u003eFault Options\u003c/h5\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUse Cell filters for Faults\u003c/strong\u003e \u0026ndash; When checked, use the currently active cell filters to filter the visible faults.\u003c/li\u003e\n\u003c/ul\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-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",
+                content:  "\nThis 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.\nRelated pages :\nAllan Diagrams\nDerived Results\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:\nUndefined 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\nNNC 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.\nWhen the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See Derived Results for details on other NNC related results.\nFault Visualization Options Fault Visibility Faults can be hidden and shown in several ways.\nChecking 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.\nFault 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 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.\nPlease note that the groups Fault Face Visibility and NNC Visibility are available below result selection.\nUseful NNC results are descrived in Derived Results\nToolbar Control Visualization mode and mesh lines can be controlled from the toolbar.\nFaults-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 Options Use Cell filters for Faults \u0026ndash; When checked, use the currently active cell filters to filter the visible faults. Fault 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 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 ).\nShow 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.\nFault 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\u003cp\u003e\u003cstrong\u003eRelated pages :\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/allandiagrams/\"\u003eAllan Diagrams\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\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 \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\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\u003cp\u003eWhen the NNCs are imported from file, ResInsight will identify NNCs not defined in the input file (Faces with zero transmissibility is not exported from the simulator). See \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e for details on other NNC related results.\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=\"fault-result\"\u003eFault 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\u003eFault 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\u003cp\u003ePlease note that the groups \u003ca href=\"#fault-face-visibility\"\u003eFault Face Visibility\u003c/a\u003e and \u003ca href=\"#nnc-visibility\"\u003eNNC Visibility\u003c/a\u003e are available below result selection.\u003c/p\u003e\n\u003cp\u003eUseful NNC results are descrived in \u003ca href=\"/calculated-data/derivedresults/\"\u003eDerived Results\u003c/a\u003e\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\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\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-options\"\u003eFault Options\u003c/h5\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eUse Cell filters for Faults\u003c/strong\u003e \u0026ndash; When checked, use the currently active cell filters to filter the visible faults.\u003c/li\u003e\n\u003c/ul\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-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/"
             };
         
@@ -3875,8 +3874,8 @@ if (!doNotTrack) {
          
             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 right-click command New RFT Plot for Well Path node or RFT Plots node.  From the Project Tree in the 3D Main Window\n Select right-click 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 Pressure Depth Data\nA custom file format for Pressure Depth Data is supported.\nLAS Pressure Data\nTo 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 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:     "\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 right-click 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 right-click 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\u003e\u003cstrong\u003ePressure Depth Data\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA custom file format for \u003ca href=\"/import/pressuredata/\"\u003ePressure Depth Data\u003c/a\u003e is supported.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eLAS Pressure Data\u003c/strong\u003e\u003c/p\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 \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\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",
+                content:  "\nAn 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\nSelect right-click command New RFT Plot for Well Path node or RFT Plots node. From the Project Tree in the 3D Main Window\nSelect right-click command New RFT plot for a simulation well. From a 3D view\nRight-click a simulation well select Well Plots -\u0026gt; New RFT Plot. Import Observed RFT Data Pressure Depth Data\nA custom file format for Pressure Depth Data is supported.\nLAS Pressure Data\nTo 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 \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:\nRFT 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:\nIf 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 ].\nO \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.\nLegend and Axis This property editor lets the user control visual properties for the legend and axis.\nTitle 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 right-click 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 right-click 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\u003e\u003cstrong\u003ePressure Depth Data\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eA custom file format for \u003ca href=\"/import/pressuredata/\"\u003ePressure Depth Data\u003c/a\u003e is supported.\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eLAS Pressure Data\u003c/strong\u003e\u003c/p\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\u0026rsquo;(Well Path)\u0026rsquo;\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 \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\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/"
             };
         
@@ -3884,7 +3883,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/rftsegmentplot/"] = {
                 title:    "RFT Segment Plot",
-                content:  "RFT Segment Data can be plotted as horizontal Well Log Plots. RFT data can be imported based on a summary case or a grid case.\nCreate RFT Segment Plot Open a summary case with RFT data\nAdditional data from WSEGLINK Some cases require data from WSEGLINK keyword. When importing summary data, ResInsight will automatically search for the related *.DATA file. The identified file can be seen or changed from the Property Editor.\nCreate Default Plot From the right-click menu of the RFT Case object , select Create RFT Segment Plot or Create RFT Multi Phase Segment Plot\nSelect the generated Well Log Plot. Adjust the data source to desired well or branch. These settings are also available from the toolbar above the plot. Useful options to adjust for a curve is color, line style and area fill.\nAdditional settings and adjustments General  Select the plot, and use Data Source to change wells, dates and branch numbers   If TVD depth is plotted, optionally invert the Y-axis when the track is selected   Add more tracks with to the same plot, and use copy/paste of a track for fast duplication. Stacking can be used when plotting curves for multiple phases.  Axis and legend settings  Control if the depth axis should be visible for a single or all track from Axis Visibility. Use the Plot Title group to adjust the text of the title. Define a Template Text for full flexibility. Available variable names can be seen when hoovering over the Template Text label. Define where the location of curve legend using the Legend Position control.  Related documents Well Log Plots\n",
+                content:  "\nRFT Segment Data can be plotted as horizontal Well Log Plots. RFT data can be imported based on a summary case or a grid case.\nCreate RFT Segment Plot Open a summary case with RFT data\nAdditional data from WSEGLINK Some cases require data from WSEGLINK keyword. When importing summary data, ResInsight will automatically search for the related *.DATA file. The identified file can be seen or changed from the Property Editor.\nCreate Default Plot From the right-click menu of the RFT Case object , select Create RFT Segment Plot or Create RFT Multi Phase Segment Plot\nSelect the generated Well Log Plot. Adjust the data source to desired well or branch. These settings are also available from the toolbar above the plot. Useful options to adjust for a curve is color, line style and area fill.\nAdditional settings and adjustments General Select the plot, and use Data Source to change wells, dates and branch numbers If TVD depth is plotted, optionally invert the Y-axis when the track is selected Add more tracks with to the same plot, and use copy/paste of a track for fast duplication. Stacking can be used when plotting curves for multiple phases. Axis and legend settings Control if the depth axis should be visible for a single or all track from Axis Visibility. Use the Plot Title group to adjust the text of the title. Define a Template Text for full flexibility. Available variable names can be seen when hoovering over the Template Text label. Define where the location of curve legend using the Legend Position control. Related documents Well Log Plots\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eRFT Segment Data can be plotted as horizontal Well Log Plots. RFT data can be imported based on a summary case or a grid case.\u003c/p\u003e\n\u003ch2 id=\"create-rft-segment-plot\"\u003eCreate RFT Segment Plot\u003c/h2\u003e\n\u003cp\u003eOpen a summary case with RFT data\u003c/p\u003e\n\u003ch3 id=\"additional-data-from-wseglink\"\u003eAdditional data from WSEGLINK\u003c/h3\u003e\n\u003cp\u003eSome cases require data from \u003cstrong\u003eWSEGLINK\u003c/strong\u003e keyword. When importing summary data, ResInsight will automatically search for the related *\u003cstrong\u003e.DATA\u003c/strong\u003e  file. The identified file can be seen or changed from the \u003cstrong\u003eProperty Editor.\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSummaryDataSource.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/RftSegmentDataDeck.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"create-default-plot\"\u003eCreate Default Plot\u003c/h3\u003e\n\u003cp\u003eFrom the right-click menu of the \u003cstrong\u003eRFT Case\u003c/strong\u003e object , select \u003cstrong\u003eCreate RFT Segment Plot\u003c/strong\u003e or \u003cstrong\u003eCreate RFT Multi Phase Segment Plot\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eSelect the generated \u003cstrong\u003eWell Log Plot\u003c/strong\u003e. Adjust the data source to desired well or branch. These settings are also available from the toolbar above the plot. Useful options to adjust for a curve is color, line style and area fill.\u003c/p\u003e\n\u003ch2 id=\"additional-settings-and-adjustments\"\u003eAdditional settings and adjustments\u003c/h2\u003e\n\u003ch3 id=\"general\"\u003eGeneral\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003eSelect the plot, and use \u003cstrong\u003eData Source\u003c/strong\u003e to change wells, dates and branch numbers\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentDataSourceStepping.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eIf TVD depth is plotted, optionally invert the Y-axis when the track is selected\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentInvertAxis.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAdd more tracks with to the same plot, and use copy/paste of a track for fast duplication. Stacking can be used when plotting curves for multiple phases.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentStackCurves.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch3 id=\"axis-and-legend-settings\"\u003eAxis and legend settings\u003c/h3\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/RFTSegmentPlotPropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eControl if the depth axis should be visible for a single or all track from \u003cstrong\u003eAxis Visibility.\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003eUse the \u003cstrong\u003ePlot Title\u003c/strong\u003e group to adjust the text of the title. Define a Template Text for full flexibility. Available variable names can be seen when hoovering over the Template Text label.\u003c/li\u003e\n\u003cli\u003eDefine where the location of curve legend using the \u003cstrong\u003eLegend Position\u003c/strong\u003e control.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch2 id=\"related-documents\"\u003eRelated documents\u003c/h2\u003e\n\u003cp\u003e\u003ca href=\"/plot-window/welllogsandplots/\"\u003eWell Log Plots\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/plot-window/rftsegmentplot/"
             };
@@ -3893,8 +3892,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 right-click command Export Contour Map to text in the graphics window showing a contour map. Select right-click 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 API 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 examples of the ResInsight Python API.\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 right-click command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e in the graphics window showing a contour map.\u003c/li\u003e\n\u003cli\u003eSelect right-click 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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e\u003ch2 id=\"python-interface-for-export-of-contour-maps\"\u003ePython interface for export of contour maps\u003c/h2\u003e\n\u003cp\u003eThe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e allows the user to access all contour maps belonging to a project.\nA Python script for exporting contour maps to a text file is included as one of the examples of the\n\u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e.\u003c/p\u003e\n",
+                content:  "\nResInsight 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):\nSelect right-click command Export Contour Map to text in the graphics window showing a contour map. Select right-click 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:\nSetting 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 API 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 examples of the ResInsight Python API.\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 right-click command \u003cstrong\u003eExport Contour Map to text\u003c/strong\u003e in the graphics window showing a contour map.\u003c/li\u003e\n\u003cli\u003eSelect right-click 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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# case name : 1_R001_REEK-0\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# sampling points : nx=90 ny=100\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# time and date : 01.Jan 2000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# property name : Arithmetic Mean, PRESSURE\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# UTM offset : x=456256 y=5.92663e+06\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003ex               y               value    \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5209.20099      254.10737       341.09308\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5336.25467      254.10737       341.13252\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5463.30835      254.10737       341.36091\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5590.36204      254.10737       341.62615\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5717.41572      254.10737       341.70246\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5082.14731      381.16105       340.56455\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5209.20099      381.16105       340.79087\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5336.25467      381.16105       341.02580\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5463.30835      381.16105       341.40061\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5590.36204      381.16105       341.86177\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5717.41572      381.16105       342.34527\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e...             ...             ...\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\u003ch2 id=\"python-interface-for-export-of-contour-maps\"\u003ePython interface for export of contour maps\u003c/h2\u003e\n\u003cp\u003eThe \u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e allows the user to access all contour maps belonging to a project.\nA Python script for exporting contour maps to a text file is included as one of the examples of the\n\u003ca href=\"https://api.resinsight.org\"\u003eResInsight Python API\u003c/a\u003e.\u003c/p\u003e\n",
                 url:      "/export/contourmapexport/"
             };
         
@@ -3902,8 +3901,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 '(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.\nColor 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.\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\u003ch3 id=\"color-by-ensemble-parameter\"\u003eColor by Ensemble Parameter\u003c/h3\u003e\n\u003cp\u003eOne 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/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotColors.png\" alt=\"\"\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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\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-txt\" data-lang=\"txt\"\u003e303.000   3.000\r\n304.000   3.000\r\n305.000   3.000\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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\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-txt\" data-lang=\"txt\"\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\u003c/div\u003e",
+                content:  "\nResInsight 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:\nEnsembles 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:\nIf 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:\nO \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.\nColor 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.\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:\nlayer_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.\nCorrelation 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:\nUtmx: 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:\nWell 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:     "\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\u0026rsquo;(Well Path)\u0026rsquo;\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\u003ch3 id=\"color-by-ensemble-parameter\"\u003eColor by Ensemble Parameter\u003c/h3\u003e\n\u003cp\u003eOne 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/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/EnsembleRftPlotColors.png\" alt=\"\"\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e3   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e4   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e7   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e8   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e9   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e10  MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e11  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e12  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e13  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e14  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e303.000   3.000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e304.000   3.000\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e305.000   3.000\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e461288.719   5933415.000   1816.200   1611.692   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e461288.685   5933415.027   1824.560   1620.052   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e461288.683   5933415.029   1840.000   1635.492   LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eOP_1   01 02 2000   1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eOP_2   01 02 2000   1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eOP_4   01 01 2001   1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWI_1   01 02 2000   1\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003eWI_3   01 03 2001   1\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e",
                 url:      "/plot-window/ensemblerftplot/"
             };
         
@@ -3911,8 +3910,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 entries containing formation name, k-range, and optionally a formation color. Formation color can be given as a World Wide Web Consortium SVG color keyword name or a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and blue components of the color, c.f. example below:\n-- Any text as comment\r\u0026#39;My First Formation Name\u0026#39; 4 - 12 red\r\u0026#39;My Second Formation Name\u0026#39; 15 - 17 green\r\u0026#39;Formation spanning 3 k-layers, i.e. 18,19 and 20\u0026#39; 3 blue\r\u0026#39;Last Formation Name\u0026#39; 21 - 21 #FFFF00\rFMU 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 entries containing formation name, k-range, and \u003cem\u003eoptionally\u003c/em\u003e a formation color.\nFormation color can be given as a World Wide Web Consortium \u003ca href=\"https://www.w3.org/TR/SVG11/types.html#ColorKeywords\"\u003eSVG color keyword name\u003c/a\u003e\nor a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and \nblue components of the color, c.f. example below:\u003c/p\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-txt\" data-lang=\"txt\"\u003e-- Any text as comment\r\n\u0026#39;My First  Formation Name\u0026#39;                             4 - 12   red\r\n\u0026#39;My Second Formation Name\u0026#39;                            15 - 17   green\r\n\u0026#39;Formation spanning 3 k-layers, i.e. 18,19 and 20\u0026#39;       3      blue\r\n\u0026#39;Last Formation Name\u0026#39;                                 21 - 21   #FFFF00\r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\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-txt\" data-lang=\"txt\"\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\u003c/div\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/flow-diagnostics-plots/\"\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",
+                content:  "\nThis 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 :\nImport 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:\nFormation 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 entries containing formation name, k-range, and optionally a formation color. Formation color can be given as a World Wide Web Consortium SVG color keyword name or a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and blue components of the color, c.f. example below:\n-- Any text as comment \u0026#39;My First Formation Name\u0026#39; 4 - 12 red \u0026#39;My Second Formation Name\u0026#39; 15 - 17 green \u0026#39;Formation spanning 3 k-layers, i.e. 18,19 and 20\u0026#39; 3 blue \u0026#39;Last Formation Name\u0026#39; 21 - 21 #FFFF00 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:\nWell 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 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:     "\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 entries containing formation name, k-range, and \u003cem\u003eoptionally\u003c/em\u003e a formation color.\nFormation color can be given as a World Wide Web Consortium \u003ca href=\"https://www.w3.org/TR/SVG11/types.html#ColorKeywords\"\u003eSVG color keyword name\u003c/a\u003e\nor a six-digit, three-byte hexadecimal number used in HTML, CSS, SVG, and other computing applications to represent the red, green and\nblue components of the color, c.f. example below:\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e-- Any text as comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026#39;My First  Formation Name\u0026#39;                             4 - 12   red\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026#39;My Second Formation Name\u0026#39;                            15 - 17   green\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026#39;Formation spanning 3 k-layers, i.e. 18,19 and 20\u0026#39;       3      blue\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e\u0026#39;Last Formation Name\u0026#39;                                 21 - 21   #FFFF00\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e1   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e2   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e3   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e4   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e5   UpperReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e6   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e7   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e8   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e9   MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e10  MidReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e11  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e12  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e13  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e14  LowerReek\n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\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/flow-diagnostics-plots/\"\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 tabindex=\"0\"\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\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/"
             };
         
@@ -3920,8 +3919,8 @@ if (!doNotTrack) {
          
             window.store["/calculated-data/derivedresults/"] = {
                 title:    "Derived Results - Eclipse",
-                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.\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",
+                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:\nStatic 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.\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",
                 url:      "/calculated-data/derivedresults/"
             };
         
@@ -3938,7 +3937,7 @@ 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 right-click command New PLT Plot for the PLT Plots node.  From the Project Tree in the Main Window\n Select right-click 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 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",
+                content:  "\nA 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\nSelect right-click command New PLT Plot for the PLT Plots node. From the Project Tree in the Main Window\nSelect right-click command New PLT Plot for a Well Path node or a Simulation Well node that has an associated well path. From the 3D view\nRight-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:\nComponent 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:\nRFT 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:\nExclusively 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 ].\nO \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.\nStandard 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.\nLegend and Axis This property editor lets the user control visual properties for the legend and axis.\nTitle 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 right-click 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 right-click 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 \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\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/"
             };
@@ -3947,7 +3946,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/vfpplot/"] = {
                 title:    "VFP Plot",
-                content:  "A Vertical Flow Performance Plot (VFP Plot) shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\nCreating VFP Plots VFP Plots are created by right-clicking the VFP Plots item in Plot Project Tree.\nProduction VFP Plot The production VFP Plot shows the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a well this means the table relates the flowing bottom-hole pressure (BHP) to the well\u0026rsquo;s tubing head pressure (THP) based on the oil, gas and water rates (and any artificial lift quantities like gas lift gas), or phases ratios, flowing up the wellbore. The data is read from files containing the VFPPROD Eclipse keyword.\nThe following is an example of a production VFP Plot and corresponding Property Editor.\nThe available settings of the production Property Editor are:\n  File Path: The VFP data file(s) to plot. Multi-selection of files is possible.\n  Table Number: The table number, i.e. VFPTAB keyword in Eclipse data.\n  Reference Depth: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\n  Interpolated Variable: Y-axis variable.\n  Flowing Phase: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\n  Flowing Water Fraction: Corresponds to the WFR keyword in Eclipse data.\n  Flowing Gas Fraction: Corresponds to the GFR keyword in Eclipse data.\n  Primary Variable: Variable on X-axis.\n  Family Variable: Variable for grouping of properties.\n  Fixed Variables: Used to choose which table to display.\n  Plot data can be exported by right-clicking the actual plot and selecting Show Plot Data.\nInjection VFP Plot The Injection VFP Plot shows the outflow or downstream pressure based on the inlet or upstream pressure and the phases being injected into the system. For a well this means the table relates the flowing bottom-hole pressure (BHP) to the well\u0026rsquo;s tubing head pressure (THP) based on the oil, gas or water injection rates. The data can be read from files containing the VFPINJ Eclipse keyword.\nThe following is an example of a production VFP Plot and corresponding Property Editor.\nThe available settings of the injection VFP Property Editor are:\n  File Path: The VFP data file(s) to plot. Multi-selection of files is possible.\n  Table Number: The table number, i.e. VFPTAB keyword in Eclipse data.\n  Reference Depth: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\n  Interpolated Variable: Y-axis variable.\n  Flowing Phase: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\n  Plot data can be exported by right-clicking the actual plot and selecting Show Plot Data.\n",
+                content:  "\nA Vertical Flow Performance Plot (VFP Plot) shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\nCreating VFP Plots VFP Plots are created by right-clicking the VFP Plots item in Plot Project Tree.\nProduction VFP Plot The production VFP Plot shows the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a well this means the table relates the flowing bottom-hole pressure (BHP) to the well\u0026rsquo;s tubing head pressure (THP) based on the oil, gas and water rates (and any artificial lift quantities like gas lift gas), or phases ratios, flowing up the wellbore. The data is read from files containing the VFPPROD Eclipse keyword.\nThe following is an example of a production VFP Plot and corresponding Property Editor.\nThe available settings of the production Property Editor are:\nFile Path: The VFP data file(s) to plot. Multi-selection of files is possible.\nTable Number: The table number, i.e. VFPTAB keyword in Eclipse data.\nReference Depth: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\nInterpolated Variable: Y-axis variable.\nFlowing Phase: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\nFlowing Water Fraction: Corresponds to the WFR keyword in Eclipse data.\nFlowing Gas Fraction: Corresponds to the GFR keyword in Eclipse data.\nPrimary Variable: Variable on X-axis.\nFamily Variable: Variable for grouping of properties.\nFixed Variables: Used to choose which table to display.\nPlot data can be exported by right-clicking the actual plot and selecting Show Plot Data.\nInjection VFP Plot The Injection VFP Plot shows the outflow or downstream pressure based on the inlet or upstream pressure and the phases being injected into the system. For a well this means the table relates the flowing bottom-hole pressure (BHP) to the well\u0026rsquo;s tubing head pressure (THP) based on the oil, gas or water injection rates. The data can be read from files containing the VFPINJ Eclipse keyword.\nThe following is an example of a production VFP Plot and corresponding Property Editor.\nThe available settings of the injection VFP Property Editor are:\nFile Path: The VFP data file(s) to plot. Multi-selection of files is possible.\nTable Number: The table number, i.e. VFPTAB keyword in Eclipse data.\nReference Depth: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\nInterpolated Variable: Y-axis variable.\nFlowing Phase: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\nPlot data can be exported by right-clicking the actual plot and selecting Show Plot Data.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_Plot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Vertical Flow Performance Plot (VFP Plot) shows the relationship between bottom hole well conditions and wellhead pressure describing a well\u0026rsquo;s ability to lift fluids to the surface. ResInsight can display both production and injection VFP plots.\u003c/p\u003e\n\u003ch2 id=\"creating-vfp-plots\"\u003eCreating VFP Plots\u003c/h2\u003e\n\u003cp\u003eVFP Plots are created by right-clicking the \u003cstrong\u003eVFP Plots\u003c/strong\u003e item in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_PlotNew.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"production-vfp-plot\"\u003eProduction VFP Plot\u003c/h2\u003e\n\u003cp\u003eThe production VFP Plot shows  the outflow or downstream pressure based on the inlet or upstream pressure and the phases flowing through the system. For a well this means the table relates the flowing bottom-hole pressure\n(\u003cem\u003eBHP\u003c/em\u003e) to the well\u0026rsquo;s tubing head pressure (\u003cem\u003eTHP\u003c/em\u003e) based on the oil, gas and water rates (and any artificial\nlift quantities like gas lift gas), or phases ratios, flowing up the wellbore. The data is read from files containing the \u003cem\u003eVFPPROD\u003c/em\u003e Eclipse keyword.\u003c/p\u003e\n\u003cp\u003eThe following is an example of a production VFP Plot and corresponding Property Editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_Production.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe available settings of the production Property Editor are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFile Path\u003c/strong\u003e: The VFP data file(s) to plot. Multi-selection of files is possible.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eTable Number\u003c/strong\u003e: The table number, i.e. VFPTAB keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReference Depth\u003c/strong\u003e: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eInterpolated Variable\u003c/strong\u003e: Y-axis variable.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFlowing Phase\u003c/strong\u003e: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFlowing Water Fraction\u003c/strong\u003e: Corresponds to the WFR keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFlowing Gas Fraction\u003c/strong\u003e: Corresponds to the GFR keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003ePrimary Variable\u003c/strong\u003e: Variable on X-axis.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFamily Variable\u003c/strong\u003e: Variable for grouping of properties.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFixed Variables\u003c/strong\u003e: Used to choose which table to display.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlot data can be exported by right-clicking the actual plot and selecting \u003cem\u003eShow Plot Data\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"injection-vfp-plot\"\u003eInjection VFP Plot\u003c/h2\u003e\n\u003cp\u003eThe Injection VFP Plot shows the outflow or downstream pressure based on the inlet or upstream pressure and the phases being injected into the system. For a well this means the table relates the flowing bottom-hole pressure (\u003cem\u003eBHP\u003c/em\u003e) to the well\u0026rsquo;s tubing head pressure (\u003cem\u003eTHP\u003c/em\u003e) based on the oil, gas or water injection rates. The data can be read from files containing the \u003cem\u003eVFPINJ\u003c/em\u003e Eclipse keyword.\u003c/p\u003e\n\u003cp\u003eThe following is an example of a production VFP Plot and corresponding Property Editor.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/VFP_Injection.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe available settings of the injection VFP Property Editor are:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFile Path\u003c/strong\u003e: The VFP data file(s) to plot. Multi-selection of files is possible.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eTable Number\u003c/strong\u003e: The table number, i.e. VFPTAB keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eReference Depth\u003c/strong\u003e: The reference depth used to generate the table, i.e. VFPREF keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eInterpolated Variable\u003c/strong\u003e: Y-axis variable.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp\u003e\u003cstrong\u003eFlowing Phase\u003c/strong\u003e: The flowing phase in the system, i.e. FLO keyword in Eclipse data.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003ePlot data can be exported by right-clicking the actual plot and selecting \u003cem\u003eShow Plot Data\u003c/em\u003e.\u003c/p\u003e\n",
                 url:      "/plot-window/vfpplot/"
             };
@@ -3956,7 +3955,7 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/depthplot/"] = {
                 title:    "Depth Plot",
-                content:  "When clicking on cells in 3D, all values along the IJ column of the selected cells can be displayed in a depth plot. This can be combined with a Result Plot displaying the change for selected cells over time.\nResult Inspection\n",
+                content:  "\nWhen clicking on cells in 3D, all values along the IJ column of the selected cells can be displayed in a depth plot. This can be combined with a Result Plot displaying the change for selected cells over time.\nResult Inspection\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/3d-main-window/DepthPlotIn3D.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eWhen clicking on cells in 3D, all values along the IJ column of the selected cells can be displayed in a depth plot. This can be combined with a \u003cstrong\u003eResult Plot\u003c/strong\u003e displaying the change for selected cells over time.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/3d-main-window/resultinspection/\"\u003eResult Inspection\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/3d-main-window/depthplot/"
             };
@@ -3965,8 +3964,8 @@ if (!doNotTrack) {
          
             window.store["/calculated-data/derivedresultsgeomech/"] = {
                 title:    "Derived Results - Geomechanical",
-                content:  "ResInsight computes several derived results. In this section we will explain what they are, and briefly how they are calculated.\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:\n$Value_{[t-b]} = Value_{[t]} - Value_{[b]}$\nwhere:\n $b$ is the base time step, $t$ is the current time step  Select the appropriate Base Time Step option in the Difference Options group to enable the time lapse result.\nNote: Relative Results calculated based on Gamma values and Stress Anisotropy are calculated slightly differently:\nGamma:\n$Gamma_{i[t-b]} = \\frac{ST_{i[t]} - ST_{i[b]}}{ POR_{[t]} - POR_{[b]} }$\nStress Anisotropy:\n$SA_{ij[t-b]} = 2 * \\frac{(ST_{i[t]} - ST_{i[b]}) - (ST_{j[t]} - ST_{j[b]})}{(ST_{i[t]} - ST_{i[b]}) + (ST_{j[t]} - ST_{j[b]})}$\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 ($S_iinc, S_iazi$) 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.\n$ If (Depth_n \u0026lt;= Depth_{nref}) $\n$ \\space \\space COMPACTION_n = -(U3_n - U3_{nref})$\n$ else $\n$\\space \\space COMPACTION_n = -(U3_{nref} - U3_n )$\nST - Total Stress $ST_{ii} = -Sa_{ii} + POR (i= 1,2,3)$\nWe use a value of $POR=0.0$ where it is not defined.\n$ST_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ and i $\\ne$ j})$\n$Sa_{ii}$ and $Sa_{ij}$ are the stresses calculated by Abaqus.\n$ST_i = \\text{Principal value i of ST}$\nSTM - Total Mean Stress $STM = \\frac{ST_{11} + ST_{22} + ST_{33}}{3} $\nQ - Deviatoric Stress $Q = \\sqrt {\\frac{3}{2} * ((ST_1 - STM)^2 + (ST_2 - STM)^2 + (ST_3 - STM)^2 }$\nDPN - Shear Slip Indicator Excess pore pressure parameter is defined as\n$DPN = \\frac{P_p - P_0} { \\sigma_v - P_0 }$\nWhere:\n $P_0$ is hydrostatic pore pressure, $P_p$ is pore pressure (at the time of the incident) and $\\sigma_v$ total vertical stress ($ ST_{33} $).  Hydrostatic pore pressure is\n$ P_0 = \\rho_w * TVDMSL * g $\nWhere:\n $\\rho_w$ is (average) density of formation water (default = 1.03), TVDMSL is true vertical depth mean sea level and $g$ is gravity.  Gamma - Stress Path $Gamma_{ii} = \\frac{ST_{ii}} {POR} (i= 1,2,3) $\n$Gamma_{i} = \\frac{ST_{i}} {POR} $\nIn these calculations we set Gamma to undefined if abs(POR) \u0026gt; 0.01 MPa.\nSE - Effective Stress $SE_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ where POR is defined})$\nwhere $Sa_{ij}$ is the stress calculated by Abaqus.\n$SE_i = \\text{Principal value i of SE} $\nSEM - Effective Mean Stress $SEM = \\frac{SE_{11} + SE_{22} + SE_{33}} {3} $\nSA - Stress Anisotropy $SA_{ij} = 2 \\frac{ST_{i} - ST_{j}}{ ST_{i} + ST_{j}} (i,j = 1,2,3 \\text{ and i $\\lt$ j})$\nThe same expressions are available for effective stresses (where SE replaces ST in the equation above).\nSFI $$SFI = \\frac{\\frac{S0}{tan(fa)} + 0.5 * (SE_1 + SE_3) * sin(fa)} {0.5*(SE_1-SE_3)} $$\nDSM $DSM = \\frac{tan(\\rho)} {tan(fa)} $\nwhere\n$$ \\rho = 2 * (arctan (\\sqrt \\frac{ SE_1 + a} {SE_3 + a}) \\space – \\frac {\\pi} {4}) $$ $$ a = \\frac {s0} {tan(fa)} $$\nFOS $FOS = \\frac{1}{DSM}$\nE - Strain $E_{ij} = -Ea_{ij}$\nEV - Volumetric Strain $EV = E_{11} + E_{22} + E_{33} $\nED - Deviatoric Strain $ED = 2*\\frac {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 = TS_{33}$\nTPH - Horizontal in-plane shear component $TPH = TS_{31} = TS_{ZX} $\nTNQV - Horizontal in-plane shear component $TPQV = TS_{32} = TS_{ZY}$\nTP - Total in-plane shear $TP = \\sqrt {(TPH^2 + TPQV^2)} $\nTPinc - Direction of TP Angle of the total in-plane shear relative to the Quasi Vertical direction\n$TPinc = acos (\\frac {TPQV} {TP}) $\nPinc and Pazi - Face Inclination and Azimuth These are the directional angles of the face-normal itself.\nPore Compressibility Pore Compressibility Pore compressibility between a reference state and the current stress state is defined as:\n$ C_{p} = -\\frac{ \\alpha \\Delta\\epsilon_{vol}}{ \\Delta P_p \\phi_0} + \\frac{1}{K_s} ( \\frac{ \\alpha } { \\phi_0 } - 1) $\nWhere:\n $ \\alpha $ is the Biot coefficient, $ \\Delta\\epsilon_{vol} $ is volumetric strain change (EV in ResInsight) between curret state and reference state, $ \\phi_0 $ is porosity on the Geostatic step, $ \\Delta P_p $ is change in pore pressure between current state and reference state, $ K_s $ bulk modulus for the solid material (grain).  The Biot porelastic coefficient ($\\alpha$) defines the compressibility of sand grains: $\\alpha = 1.0$ for incompressible grains, and $\\alpha \u0026lt; 1.0$ for compressible grains. $\\alpha$ is not used for the initial (Geostatic) time step. The default value is 1.0, but values per element can be imported as an element property table.\nThe bulk modulus for solid material is defined as:\n$ K_s = \\frac{ K_{fr} }{ 1 - \\alpha}, K_{fr} = \\frac{ E }{ 3(1-2\\nu)} $\nWhere:\n $ E $ is the elastic modulus (Young\u0026rsquo;s modulus) from element property table MODULUS. $ \\nu $ is Poisson\u0026rsquo;s ratio imported from element property table RATIO.  Vertical Compressibility $ C_{v} = - \\frac{ \\Delta\\epsilon_{\\nu}}{ \\alpha \\Delta P_p } $\n$ \\Delta\\epsilon_\\nu $ is the vertical strain change between current state and reference state (E33 in ResInsight).\nVertical Compressibility Ratio $ C_{vr} = \\frac{ C_v E(1-\\nu) } { (1+\\nu) ( 1 - 2\\nu) } $\nVertical Compression Ratio is the ratio between the real vertical compression and the compression in a uniaxial strain case. All parameters are described above.\nPorosity and Permeability Porosity Porosity change is defined as either total change in porosity between initial (geostatic) state and current state, or change in porosity between a reference state and the current state $ \\Delta\\phi $. The latter is given as\n$ \\Delta\\phi = \\phi_0(C_p \\Delta P_p + \\Delta\\epsilon_{vol}) $\nHere, $\\Delta\\phi_0$ is found from this equation with the reference state being the initial state (geostatic). The current porosity is then given as\n$ \\phi = \\phi_0 + \\Delta\\phi_0 $\nwith $ \\phi_0 $ being the porosity at the initial state, $\\Delta\\phi_0$ is porosity change between initial (geostatic) state current, $C_p$ is pore compressibility (between reference and current state), $\\Delta P_p$ is change in pore pressure and $\\Delta\\epsilon_{vol}$ is volumetric strain change.\nInitial Porosity Porosity at the initial state:\n$ \\phi_0 = \\frac{VOIDR} {1 + VOIDR} $\nWhere:\n VOIDR is void ratio from Abaqus.  Permeability An expression for permeability is taken from Petunin (2011).\n$ k = k_0( \\frac{\\phi}{\\phi_0} )^A $\nWhere:\n $k_0$ is the permeability at the initial state (unit: mD), $\\phi$ is porosity at current state, $\\phi_0$ is initial porosity, $A$ is a constant  Mud Weight Window Mud Weight Window (MWW) represents the difference between the minimum and the maximum possible mud weight between specific formation layers representing top and base of a fictitious well section.\nTo find MWW a two step procedure is needed:\n first find the limits per element, determine the MWW for each element based on the vertical column.  Finding Upper and Lower Mud Weight Limit The upper mud weight limit (UMWL) and lower mud weight limit (LMWL) is found for each element intersected by the fictitious well. The UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale. The LMWL is defined as the maximum of shear fracture gradient (SFG) and/or pore pressure in shale, and as pore pressure in sand.\nThe calculations for fracture gradient and shear fracture gradient, and the needed input, are described in detail in Well Bore Stability Plots.\nMud Weight Window Thereafter, the combined use of mud weight limits for all elements between the top and base (for a given IJ) determines the MWW parameters as will be further described below.\nA reference element index ($K_{ref}$) represents the base or the top of the fictitious well. Then for a set of elements with i = I, j = J and k = K to $K_{ref}$ the maximum LWML and the minimum UWML must be found from these element values. Then the difference between the two defines the MWW parameter.\nThus for a vertical stack of elements $element_{ijk} = K \\to K_{ref}$, $MWW_{ijk}$ is given as\n$ MWW_{ijk} = maximum(LMWL) - minimum(UMWL) (k = K \\to K_{ref}) $\nSimilar calculations are made below the reference layer, but then with the reference layer as the top layer.\nIn addition to the MWW parameter, the mud weight representing the middle of the drilling window (MWM) is calculated if MWW \u0026gt; 0. Otherwise, MWM should is undefined.\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-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\u003e$Value_{[t-b]} = Value_{[t]} - Value_{[b]}$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$b$ is the base time step,\u003c/li\u003e\n\u003cli\u003e$t$ is the current time step\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSelect the appropriate \u003cstrong\u003eBase Time Step\u003c/strong\u003e option in the \u003cstrong\u003eDifference Options\u003c/strong\u003e group to enable the time lapse result.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedRelativeResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNote: Relative Results calculated based on Gamma values and Stress Anisotropy are calculated slightly differently:\u003c/p\u003e\n\u003cp\u003eGamma:\u003c/p\u003e\n\u003cp\u003e$Gamma_{i[t-b]} = \\frac{ST_{i[t]} - ST_{i[b]}}{ POR_{[t]} - POR_{[b]}  }$\u003c/p\u003e\n\u003cp\u003eStress Anisotropy:\u003c/p\u003e\n\u003cp\u003e$SA_{ij[t-b]} = 2 * \\frac{(ST_{i[t]} - ST_{i[b]}) - (ST_{j[t]} - ST_{j[b]})}{(ST_{i[t]} - ST_{i[b]}) + (ST_{j[t]} - ST_{j[b]})}$\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_iinc, S_iazi$)\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\u003ch3 id=\"definitions-of-derived-results\"\u003eDefinitions of Derived Results\u003c/h3\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\u003ch3 id=\"case-constants\"\u003eCase Constants\u003c/h3\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\u003ch3 id=\"compaction\"\u003eCOMPACTION\u003c/h3\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 \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\u003cp\u003e$ If (Depth_n \u0026lt;= Depth_{nref}) $\u003c/p\u003e\n\u003cp\u003e$ \\space \\space COMPACTION_n = -(U3_n - U3_{nref})$\u003c/p\u003e\n\u003cp\u003e$ else $\u003c/p\u003e\n\u003cp\u003e$\\space \\space COMPACTION_n = -(U3_{nref} - U3_n )$\u003c/p\u003e\n\u003ch3 id=\"st---total-stress\"\u003eST - Total Stress\u003c/h3\u003e\n\u003cp\u003e$ST_{ii} = -Sa_{ii} + POR (i= 1,2,3)$\u003c/p\u003e\n\u003cp\u003eWe use a value of $POR=0.0$ where it is not defined.\u003c/p\u003e\n\u003cp\u003e$ST_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ and i $\\ne$ j})$\u003c/p\u003e\n\u003cp\u003e$Sa_{ii}$ and $Sa_{ij}$ are the stresses calculated by Abaqus.\u003c/p\u003e\n\u003cp\u003e$ST_i = \\text{Principal value i of ST}$\u003c/p\u003e\n\u003ch3 id=\"stm---total-mean-stress\"\u003eSTM - Total Mean Stress\u003c/h3\u003e\n\u003cp\u003e$STM = \\frac{ST_{11} + ST_{22} + ST_{33}}{3} $\u003c/p\u003e\n\u003ch3 id=\"q---deviatoric-stress\"\u003eQ - Deviatoric Stress\u003c/h3\u003e\n\u003cp\u003e$Q = \\sqrt {\\frac{3}{2} * ((ST_1 - STM)^2 + (ST_2 - STM)^2 + (ST_3 - STM)^2 }$\u003c/p\u003e\n\u003ch3 id=\"dpn---shear-slip-indicator\"\u003eDPN - Shear Slip Indicator\u003c/h3\u003e\n\u003cp\u003eExcess pore pressure parameter is defined as\u003c/p\u003e\n\u003cp\u003e$DPN = \\frac{P_p - P_0} { \\sigma_v - P_0  }$\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$P_0$ is hydrostatic pore pressure,\u003c/li\u003e\n\u003cli\u003e$P_p$ is pore pressure (at the time of the incident) and\u003c/li\u003e\n\u003cli\u003e$\\sigma_v$ total vertical stress ($ ST_{33} $).\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eHydrostatic pore pressure is\u003c/p\u003e\n\u003cp\u003e$ P_0 = \\rho_w * TVDMSL * g $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$\\rho_w$ is (average) density of formation water (default = 1.03),\u003c/li\u003e\n\u003cli\u003eTVDMSL is true vertical depth mean sea level and\u003c/li\u003e\n\u003cli\u003e$g$ is gravity.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"gamma---stress-path\"\u003eGamma - Stress Path\u003c/h3\u003e\n\u003cp\u003e$Gamma_{ii} = \\frac{ST_{ii}} {POR} (i= 1,2,3) $\u003c/p\u003e\n\u003cp\u003e$Gamma_{i} = \\frac{ST_{i}} {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\u003ch3 id=\"se---effective-stress\"\u003eSE - Effective Stress\u003c/h3\u003e\n\u003cp\u003e$SE_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ where POR is defined})$\u003c/p\u003e\n\u003cp\u003ewhere $Sa_{ij}$ is the stress calculated by Abaqus.\u003c/p\u003e\n\u003cp\u003e$SE_i = \\text{Principal value i of SE} $\u003c/p\u003e\n\u003ch3 id=\"sem---effective-mean-stress\"\u003eSEM - Effective Mean Stress\u003c/h3\u003e\n\u003cp\u003e$SEM = \\frac{SE_{11} + SE_{22} + SE_{33}} {3}  $\u003c/p\u003e\n\u003ch3 id=\"sa---stress-anisotropy\"\u003eSA - Stress Anisotropy\u003c/h3\u003e\n\u003cp\u003e$SA_{ij} = 2 \\frac{ST_{i} - ST_{j}}{ ST_{i} + ST_{j}} (i,j = 1,2,3 \\text{ and i $\\lt$ j})$\u003c/p\u003e\n\u003cp\u003eThe same expressions are available for effective stresses (where SE replaces ST in the equation above).\u003c/p\u003e\n\u003ch3 id=\"sfi\"\u003eSFI\u003c/h3\u003e\n\u003cp\u003e$$SFI = \\frac{\\frac{S0}{tan(fa)} + 0.5 * (SE_1 + SE_3) * sin(fa)} {0.5*(SE_1-SE_3)}  $$\u003c/p\u003e\n\u003ch3 id=\"dsm\"\u003eDSM\u003c/h3\u003e\n\u003cp\u003e$DSM = \\frac{tan(\\rho)} {tan(fa)} $\u003c/p\u003e\n\u003cp\u003ewhere\u003c/p\u003e\n\u003cp\u003e$$ \\rho = 2 * (arctan (\\sqrt \\frac{ SE_1 + a} {SE_3 + a}) \\space – \\frac {\\pi} {4}) $$\n$$ a = \\frac {s0} {tan(fa)} $$\u003c/p\u003e\n\u003ch3 id=\"fos\"\u003eFOS\u003c/h3\u003e\n\u003cp\u003e$FOS = \\frac{1}{DSM}$\u003c/p\u003e\n\u003ch3 id=\"e---strain\"\u003eE - Strain\u003c/h3\u003e\n\u003cp\u003e$E_{ij} = -Ea_{ij}$\u003c/p\u003e\n\u003ch3 id=\"ev---volumetric-strain\"\u003eEV - Volumetric Strain\u003c/h3\u003e\n\u003cp\u003e$EV = E_{11} + E_{22} + E_{33} $\u003c/p\u003e\n\u003ch3 id=\"ed---deviatoric-strain\"\u003eED - Deviatoric Strain\u003c/h3\u003e\n\u003cp\u003e$ED = 2*\\frac {E1-E3} {3}  $\u003c/p\u003e\n\u003ch3 id=\"element-nodal-on-face\"\u003eElement Nodal On Face\u003c/h3\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\u003ch3 id=\"sn---stress-component-normal-to-face\"\u003eSN - Stress component Normal to face\u003c/h3\u003e\n\u003cp\u003e$SN = TS_{33}$\u003c/p\u003e\n\u003ch3 id=\"tph---horizontal-in-plane-shear-component\"\u003eTPH - Horizontal in-plane shear component\u003c/h3\u003e\n\u003cp\u003e$TPH = TS_{31} = TS_{ZX} $\u003c/p\u003e\n\u003ch3 id=\"tnqv---horizontal-in-plane-shear-component\"\u003eTNQV - Horizontal in-plane shear component\u003c/h3\u003e\n\u003cp\u003e$TPQV = TS_{32} = TS_{ZY}$\u003c/p\u003e\n\u003ch3 id=\"tp---total-in-plane-shear\"\u003eTP - Total in-plane shear\u003c/h3\u003e\n\u003cp\u003e$TP = \\sqrt {(TPH^2 + TPQV^2)} $\u003c/p\u003e\n\u003ch3 id=\"tpinc---direction-of-tp\"\u003eTPinc - Direction of TP\u003c/h3\u003e\n\u003cp\u003eAngle of the total in-plane shear relative to the Quasi Vertical direction\u003c/p\u003e\n\u003cp\u003e$TPinc = acos (\\frac {TPQV} {TP}) $\u003c/p\u003e\n\u003ch3 id=\"pinc-and-pazi---face-inclination-and-azimuth\"\u003ePinc and Pazi - Face Inclination and Azimuth\u003c/h3\u003e\n\u003cp\u003eThese are the directional angles of the face-normal itself.\u003c/p\u003e\n\u003ch3 id=\"pore-compressibility\"\u003ePore Compressibility\u003c/h3\u003e\n\u003ch4 id=\"pore-compressibility-1\"\u003ePore Compressibility\u003c/h4\u003e\n\u003cp\u003ePore compressibility between a reference state and the current stress state is defined as:\u003c/p\u003e\n\u003cp\u003e$ C_{p} = -\\frac{ \\alpha \\Delta\\epsilon_{vol}}{ \\Delta P_p \\phi_0} + \\frac{1}{K_s} ( \\frac{ \\alpha } { \\phi_0 } - 1) $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$ \\alpha $ is the Biot coefficient,\u003c/li\u003e\n\u003cli\u003e$ \\Delta\\epsilon_{vol} $ is volumetric strain change (EV in ResInsight) between curret state and reference state,\u003c/li\u003e\n\u003cli\u003e$ \\phi_0 $ is porosity on the Geostatic step,\u003c/li\u003e\n\u003cli\u003e$ \\Delta P_p $ is change in pore pressure between current state and reference state,\u003c/li\u003e\n\u003cli\u003e$ K_s $ bulk modulus for the solid material (grain).\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe Biot porelastic coefficient ($\\alpha$) defines the compressibility of sand grains: $\\alpha = 1.0$ for incompressible grains,\nand $\\alpha \u0026lt; 1.0$ for compressible grains. $\\alpha$ is not used for the initial (Geostatic) time step. The default value is 1.0, but values\nper element can be imported as an \u003ca href=\"/import/elementpropertytable/\"\u003eelement property table\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eThe bulk modulus for solid material is defined as:\u003c/p\u003e\n\u003cp\u003e$ K_s = \\frac{ K_{fr} }{ 1 - \\alpha}, K_{fr} = \\frac{ E }{ 3(1-2\\nu)} $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$ E $ is the elastic modulus (Young\u0026rsquo;s modulus) from element property table \u003ca href=\"/import/elementpropertytable/\"\u003eMODULUS\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e$ \\nu $ is Poisson\u0026rsquo;s ratio imported from element property table \u003ca href=\"/import/elementpropertytable/\"\u003eRATIO\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"vertical-compressibility\"\u003eVertical Compressibility\u003c/h4\u003e\n\u003cp\u003e$ C_{v} = - \\frac{ \\Delta\\epsilon_{\\nu}}{ \\alpha \\Delta P_p } $\u003c/p\u003e\n\u003cp\u003e$ \\Delta\\epsilon_\\nu $ is the vertical strain change between current state and reference state (E33 in ResInsight).\u003c/p\u003e\n\u003ch4 id=\"vertical-compressibility-ratio\"\u003eVertical Compressibility Ratio\u003c/h4\u003e\n\u003cp\u003e$ C_{vr} = \\frac{ C_v E(1-\\nu) } { (1+\\nu) ( 1 - 2\\nu) } $\u003c/p\u003e\n\u003cp\u003eVertical Compression Ratio is the ratio between the real vertical compression and the compression in a uniaxial strain case.\nAll parameters are described above.\u003c/p\u003e\n\u003ch3 id=\"porosity-and-permeability\"\u003ePorosity and Permeability\u003c/h3\u003e\n\u003ch4 id=\"porosity\"\u003ePorosity\u003c/h4\u003e\n\u003cp\u003ePorosity change is defined as either total change in porosity between initial (geostatic) state and current state,\nor change in porosity between a reference state and the current state $ \\Delta\\phi $. The latter is given as\u003c/p\u003e\n\u003cp\u003e$ \\Delta\\phi = \\phi_0(C_p \\Delta P_p + \\Delta\\epsilon_{vol}) $\u003c/p\u003e\n\u003cp\u003eHere, $\\Delta\\phi_0$ is found from this equation with the reference state being the initial state (geostatic).\nThe current porosity is then given as\u003c/p\u003e\n\u003cp\u003e$ \\phi = \\phi_0 + \\Delta\\phi_0 $\u003c/p\u003e\n\u003cp\u003ewith $ \\phi_0 $ being the porosity at the initial state, $\\Delta\\phi_0$ is porosity change between initial (geostatic)\nstate current, $C_p$ is pore compressibility (between reference and current state), $\\Delta P_p$ is change in pore pressure\nand $\\Delta\\epsilon_{vol}$ is volumetric strain change.\u003c/p\u003e\n\u003ch4 id=\"initial-porosity\"\u003eInitial Porosity\u003c/h4\u003e\n\u003cp\u003ePorosity at the initial state:\u003c/p\u003e\n\u003cp\u003e$ \\phi_0 = \\frac{VOIDR} {1 + VOIDR} $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eVOIDR is void ratio from Abaqus.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"permeability\"\u003ePermeability\u003c/h4\u003e\n\u003cp\u003eAn expression for permeability is taken from Petunin (2011).\u003c/p\u003e\n\u003cp\u003e$ k = k_0( \\frac{\\phi}{\\phi_0} )^A $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$k_0$ is the permeability at the initial state (unit: mD),\u003c/li\u003e\n\u003cli\u003e$\\phi$ is porosity at current state,\u003c/li\u003e\n\u003cli\u003e$\\phi_0$ is initial porosity,\u003c/li\u003e\n\u003cli\u003e$A$ is a constant\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"mud-weight-window\"\u003eMud Weight Window\u003c/h3\u003e\n\u003cp\u003eMud Weight Window (MWW) represents the difference between the minimum and the maximum possible\nmud weight between specific formation layers representing top and base of a fictitious well section.\u003c/p\u003e\n\u003cp\u003eTo find MWW a two step procedure is needed:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003efirst find the limits per element,\u003c/li\u003e\n\u003cli\u003edetermine the MWW for each element based on the vertical column.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"finding-upper-and-lower-mud-weight-limit\"\u003eFinding Upper and Lower Mud Weight Limit\u003c/h4\u003e\n\u003cp\u003eThe upper mud weight limit (UMWL) and lower mud weight limit (LMWL) is found for each element intersected by the fictitious well.\nThe UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale. \nThe LMWL is defined as the maximum of shear fracture gradient (SFG) and/or pore pressure in shale, and as pore pressure in sand.\u003c/p\u003e\n\u003cp\u003eThe calculations for fracture gradient and shear fracture gradient, and the needed input, are described in detail\nin \u003ca href=\"/plot-window/wellborestabilityplots/\"\u003eWell Bore Stability Plots\u003c/a\u003e.\u003c/p\u003e\n\u003ch4 id=\"mud-weight-window-1\"\u003eMud Weight Window\u003c/h4\u003e\n\u003cp\u003eThereafter, the combined use of mud weight limits for all elements between the top and base (for a given IJ)\ndetermines the MWW parameters as will be further described below.\u003c/p\u003e\n\u003cp\u003eA reference element index ($K_{ref}$) represents the base or the top of the fictitious well. Then for a set\nof elements with i = I, j = J and k = K to $K_{ref}$ the maximum LWML and the minimum UWML must be found from\nthese element values. Then the difference between the two defines the MWW parameter.\u003c/p\u003e\n\u003cp\u003eThus for a vertical stack of elements $element_{ijk} = K \\to K_{ref}$, $MWW_{ijk}$ is given as\u003c/p\u003e\n\u003cp\u003e$ MWW_{ijk} = maximum(LMWL) - minimum(UMWL) (k = K \\to K_{ref}) $\u003c/p\u003e\n\u003cp\u003eSimilar calculations are made below the reference layer, but then with the reference layer as the top layer.\u003c/p\u003e\n\u003cp\u003eIn addition to the MWW parameter, the mud weight representing the middle of the drilling window (MWM) is calculated if MWW \u0026gt; 0.\nOtherwise, MWM should is undefined.\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 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:\n$Value_{[t-b]} = Value_{[t]} - Value_{[b]}$\nwhere:\n$b$ is the base time step, $t$ is the current time step Select the appropriate Base Time Step option in the Difference Options group to enable the time lapse result.\nNote: Relative Results calculated based on Gamma values and Stress Anisotropy are calculated slightly differently:\nGamma:\n$Gamma_{i[t-b]} = \\frac{ST_{i[t]} - ST_{i[b]}}{ POR_{[t]} - POR_{[b]} }$\nStress Anisotropy:\n$SA_{ij[t-b]} = 2 * \\frac{(ST_{i[t]} - ST_{i[b]}) - (ST_{j[t]} - ST_{j[b]})}{(ST_{i[t]} - ST_{i[b]}) + (ST_{j[t]} - ST_{j[b]})}$\nDerived Result Fields The calculated result fields are:\nNodal COMPACTION (Magnitude of compression) Element Nodal and Integration Points ST (Total Stress) All tensor components Principals, with directions ($S_iinc, S_iazi$) 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.\nInclination 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:\nCohesion 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.\n$ If (Depth_n \u0026lt;= Depth_{nref}) $\n$ \\space \\space COMPACTION_n = -(U3_n - U3_{nref})$\n$ else $\n$\\space \\space COMPACTION_n = -(U3_{nref} - U3_n )$\nST - Total Stress $ST_{ii} = -Sa_{ii} + POR (i= 1,2,3)$\nWe use a value of $POR=0.0$ where it is not defined.\n$ST_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ and i $\\ne$ j})$\n$Sa_{ii}$ and $Sa_{ij}$ are the stresses calculated by Abaqus.\n$ST_i = \\text{Principal value i of ST}$\nSTM - Total Mean Stress $STM = \\frac{ST_{11} + ST_{22} + ST_{33}}{3} $\nQ - Deviatoric Stress $Q = \\sqrt {\\frac{3}{2} * ((ST_1 - STM)^2 + (ST_2 - STM)^2 + (ST_3 - STM)^2 }$\nDPN - Shear Slip Indicator Excess pore pressure parameter is defined as\n$DPN = \\frac{P_p - P_0} { \\sigma_v - P_0 }$\nWhere:\n$P_0$ is hydrostatic pore pressure, $P_p$ is pore pressure (at the time of the incident) and $\\sigma_v$ total vertical stress ($ ST_{33} $). Hydrostatic pore pressure is\n$ P_0 = \\rho_w * TVDMSL * g $\nWhere:\n$\\rho_w$ is (average) density of formation water (default = 1.03), TVDMSL is true vertical depth mean sea level and $g$ is gravity. Gamma - Stress Path $Gamma_{ii} = \\frac{ST_{ii}} {POR} (i= 1,2,3) $\n$Gamma_{i} = \\frac{ST_{i}} {POR} $\nIn these calculations we set Gamma to undefined if abs(POR) \u0026gt; 0.01 MPa.\nSE - Effective Stress $SE_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ where POR is defined})$\nwhere $Sa_{ij}$ is the stress calculated by Abaqus.\n$SE_i = \\text{Principal value i of SE} $\nSEM - Effective Mean Stress $SEM = \\frac{SE_{11} + SE_{22} + SE_{33}} {3} $\nSA - Stress Anisotropy $SA_{ij} = 2 \\frac{ST_{i} - ST_{j}}{ ST_{i} + ST_{j}} (i,j = 1,2,3 \\text{ and i $\\lt$ j})$\nThe same expressions are available for effective stresses (where SE replaces ST in the equation above).\nSFI $$SFI = \\frac{\\frac{S0}{tan(fa)} + 0.5 * (SE_1 + SE_3) * sin(fa)} {0.5*(SE_1-SE_3)} $$\nDSM $DSM = \\frac{tan(\\rho)} {tan(fa)} $\nwhere\n$$ \\rho = 2 * (arctan (\\sqrt \\frac{ SE_1 + a} {SE_3 + a}) \\space – \\frac {\\pi} {4}) $$ $$ a = \\frac {s0} {tan(fa)} $$\nFOS $FOS = \\frac{1}{DSM}$\nE - Strain $E_{ij} = -Ea_{ij}$\nEV - Volumetric Strain $EV = E_{11} + E_{22} + E_{33} $\nED - Deviatoric Strain $ED = 2*\\frac {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:\nEz 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 = TS_{33}$\nTPH - Horizontal in-plane shear component $TPH = TS_{31} = TS_{ZX} $\nTNQV - Horizontal in-plane shear component $TPQV = TS_{32} = TS_{ZY}$\nTP - Total in-plane shear $TP = \\sqrt {(TPH^2 + TPQV^2)} $\nTPinc - Direction of TP Angle of the total in-plane shear relative to the Quasi Vertical direction\n$TPinc = acos (\\frac {TPQV} {TP}) $\nPinc and Pazi - Face Inclination and Azimuth These are the directional angles of the face-normal itself.\nPore Compressibility Pore Compressibility Pore compressibility between a reference state and the current stress state is defined as:\n$ C_{p} = -\\frac{ \\alpha \\Delta\\epsilon_{vol}}{ \\Delta P_p \\phi_0} + \\frac{1}{K_s} ( \\frac{ \\alpha } { \\phi_0 } - 1) $\nWhere:\n$ \\alpha $ is the Biot coefficient, $ \\Delta\\epsilon_{vol} $ is volumetric strain change (EV in ResInsight) between curret state and reference state, $ \\phi_0 $ is porosity on the Geostatic step, $ \\Delta P_p $ is change in pore pressure between current state and reference state, $ K_s $ bulk modulus for the solid material (grain). The Biot porelastic coefficient ($\\alpha$) defines the compressibility of sand grains: $\\alpha = 1.0$ for incompressible grains, and $\\alpha \u0026lt; 1.0$ for compressible grains. $\\alpha$ is not used for the initial (Geostatic) time step. The default value is 1.0, but values per element can be imported as an element property table.\nThe bulk modulus for solid material is defined as:\n$ K_s = \\frac{ K_{fr} }{ 1 - \\alpha}, K_{fr} = \\frac{ E }{ 3(1-2\\nu)} $\nWhere:\n$ E $ is the elastic modulus (Young\u0026rsquo;s modulus) from element property table MODULUS. $ \\nu $ is Poisson\u0026rsquo;s ratio imported from element property table RATIO. Vertical Compressibility $ C_{v} = - \\frac{ \\Delta\\epsilon_{\\nu}}{ \\alpha \\Delta P_p } $\n$ \\Delta\\epsilon_\\nu $ is the vertical strain change between current state and reference state (E33 in ResInsight).\nVertical Compressibility Ratio $ C_{vr} = \\frac{ C_v E(1-\\nu) } { (1+\\nu) ( 1 - 2\\nu) } $\nVertical Compression Ratio is the ratio between the real vertical compression and the compression in a uniaxial strain case. All parameters are described above.\nPorosity and Permeability Porosity Porosity change is defined as either total change in porosity between initial (geostatic) state and current state, or change in porosity between a reference state and the current state $ \\Delta\\phi $. The latter is given as\n$ \\Delta\\phi = \\phi_0(C_p \\Delta P_p + \\Delta\\epsilon_{vol}) $\nHere, $\\Delta\\phi_0$ is found from this equation with the reference state being the initial state (geostatic). The current porosity is then given as\n$ \\phi = \\phi_0 + \\Delta\\phi_0 $\nwith $ \\phi_0 $ being the porosity at the initial state, $\\Delta\\phi_0$ is porosity change between initial (geostatic) state current, $C_p$ is pore compressibility (between reference and current state), $\\Delta P_p$ is change in pore pressure and $\\Delta\\epsilon_{vol}$ is volumetric strain change.\nInitial Porosity Porosity at the initial state:\n$ \\phi_0 = \\frac{VOIDR} {1 + VOIDR} $\nWhere:\nVOIDR is void ratio from Abaqus. Permeability An expression for permeability is taken from Petunin (2011).\n$ k = k_0( \\frac{\\phi}{\\phi_0} )^A $\nWhere:\n$k_0$ is the permeability at the initial state (unit: mD), $\\phi$ is porosity at current state, $\\phi_0$ is initial porosity, $A$ is a constant Mud Weight Window Mud Weight Window (MWW) represents the difference between the minimum and the maximum possible mud weight between specific formation layers representing top and base of a fictitious well section.\nTo find MWW a two step procedure is needed:\nfirst find the limits per element, determine the MWW for each element based on the vertical column. Finding Upper and Lower Mud Weight Limit The upper mud weight limit (UMWL) and lower mud weight limit (LMWL) is found for each element intersected by the fictitious well. The UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale. The LMWL is defined as the maximum of shear fracture gradient (SFG) and/or pore pressure in shale, and as pore pressure in sand.\nThe calculations for fracture gradient and shear fracture gradient, and the needed input, are described in detail in Well Bore Stability Plots.\nMud Weight Window Thereafter, the combined use of mud weight limits for all elements between the top and base (for a given IJ) determines the MWW parameters as will be further described below.\nA reference element index ($K_{ref}$) represents the base or the top of the fictitious well. Then for a set of elements with i = I, j = J and k = K to $K_{ref}$ the maximum LWML and the minimum UWML must be found from these element values. Then the difference between the two defines the MWW parameter.\nThus for a vertical stack of elements $element_{ijk} = K \\to K_{ref}$, $MWW_{ijk}$ is given as\n$ MWW_{ijk} = maximum(LMWL) - minimum(UMWL) (k = K \\to K_{ref}) $\nSimilar calculations are made below the reference layer, but then with the reference layer as the top layer.\nIn addition to the MWW parameter, the mud weight representing the middle of the drilling window (MWM) is calculated if MWW \u0026gt; 0. Otherwise, MWM should is undefined.\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-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\u003e$Value_{[t-b]} = Value_{[t]} - Value_{[b]}$\u003c/p\u003e\n\u003cp\u003ewhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$b$ is the base time step,\u003c/li\u003e\n\u003cli\u003e$t$ is the current time step\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eSelect the appropriate \u003cstrong\u003eBase Time Step\u003c/strong\u003e option in the \u003cstrong\u003eDifference Options\u003c/strong\u003e group to enable the time lapse result.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/appendix/DerivedRelativeResults.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eNote: Relative Results calculated based on Gamma values and Stress Anisotropy are calculated slightly differently:\u003c/p\u003e\n\u003cp\u003eGamma:\u003c/p\u003e\n\u003cp\u003e$Gamma_{i[t-b]} = \\frac{ST_{i[t]} - ST_{i[b]}}{ POR_{[t]} - POR_{[b]}  }$\u003c/p\u003e\n\u003cp\u003eStress Anisotropy:\u003c/p\u003e\n\u003cp\u003e$SA_{ij[t-b]} = 2 * \\frac{(ST_{i[t]} - ST_{i[b]}) - (ST_{j[t]} - ST_{j[b]})}{(ST_{i[t]} - ST_{i[b]}) + (ST_{j[t]} - ST_{j[b]})}$\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_iinc, S_iazi$)\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\u003ch3 id=\"definitions-of-derived-results\"\u003eDefinitions of Derived Results\u003c/h3\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\u003ch3 id=\"case-constants\"\u003eCase Constants\u003c/h3\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\u003ch3 id=\"compaction\"\u003eCOMPACTION\u003c/h3\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 \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\u003cp\u003e$ If (Depth_n \u0026lt;= Depth_{nref}) $\u003c/p\u003e\n\u003cp\u003e$ \\space \\space COMPACTION_n = -(U3_n - U3_{nref})$\u003c/p\u003e\n\u003cp\u003e$ else $\u003c/p\u003e\n\u003cp\u003e$\\space \\space COMPACTION_n = -(U3_{nref} - U3_n )$\u003c/p\u003e\n\u003ch3 id=\"st---total-stress\"\u003eST - Total Stress\u003c/h3\u003e\n\u003cp\u003e$ST_{ii} = -Sa_{ii} + POR (i= 1,2,3)$\u003c/p\u003e\n\u003cp\u003eWe use a value of $POR=0.0$ where it is not defined.\u003c/p\u003e\n\u003cp\u003e$ST_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ and i $\\ne$ j})$\u003c/p\u003e\n\u003cp\u003e$Sa_{ii}$ and $Sa_{ij}$ are the stresses calculated by Abaqus.\u003c/p\u003e\n\u003cp\u003e$ST_i = \\text{Principal value i of ST}$\u003c/p\u003e\n\u003ch3 id=\"stm---total-mean-stress\"\u003eSTM - Total Mean Stress\u003c/h3\u003e\n\u003cp\u003e$STM = \\frac{ST_{11} + ST_{22} + ST_{33}}{3} $\u003c/p\u003e\n\u003ch3 id=\"q---deviatoric-stress\"\u003eQ - Deviatoric Stress\u003c/h3\u003e\n\u003cp\u003e$Q = \\sqrt {\\frac{3}{2} * ((ST_1 - STM)^2 + (ST_2 - STM)^2 + (ST_3 - STM)^2 }$\u003c/p\u003e\n\u003ch3 id=\"dpn---shear-slip-indicator\"\u003eDPN - Shear Slip Indicator\u003c/h3\u003e\n\u003cp\u003eExcess pore pressure parameter is defined as\u003c/p\u003e\n\u003cp\u003e$DPN = \\frac{P_p - P_0} { \\sigma_v - P_0  }$\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$P_0$ is hydrostatic pore pressure,\u003c/li\u003e\n\u003cli\u003e$P_p$ is pore pressure (at the time of the incident) and\u003c/li\u003e\n\u003cli\u003e$\\sigma_v$ total vertical stress ($ ST_{33} $).\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eHydrostatic pore pressure is\u003c/p\u003e\n\u003cp\u003e$ P_0 = \\rho_w * TVDMSL * g $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$\\rho_w$ is (average) density of formation water (default = 1.03),\u003c/li\u003e\n\u003cli\u003eTVDMSL is true vertical depth mean sea level and\u003c/li\u003e\n\u003cli\u003e$g$ is gravity.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"gamma---stress-path\"\u003eGamma - Stress Path\u003c/h3\u003e\n\u003cp\u003e$Gamma_{ii} = \\frac{ST_{ii}} {POR} (i= 1,2,3) $\u003c/p\u003e\n\u003cp\u003e$Gamma_{i} = \\frac{ST_{i}} {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\u003ch3 id=\"se---effective-stress\"\u003eSE - Effective Stress\u003c/h3\u003e\n\u003cp\u003e$SE_{ij} = -Sa_{ij} (i,j = 1,2,3 \\text{ where POR is defined})$\u003c/p\u003e\n\u003cp\u003ewhere $Sa_{ij}$ is the stress calculated by Abaqus.\u003c/p\u003e\n\u003cp\u003e$SE_i = \\text{Principal value i of SE} $\u003c/p\u003e\n\u003ch3 id=\"sem---effective-mean-stress\"\u003eSEM - Effective Mean Stress\u003c/h3\u003e\n\u003cp\u003e$SEM = \\frac{SE_{11} + SE_{22} + SE_{33}} {3}  $\u003c/p\u003e\n\u003ch3 id=\"sa---stress-anisotropy\"\u003eSA - Stress Anisotropy\u003c/h3\u003e\n\u003cp\u003e$SA_{ij} = 2 \\frac{ST_{i} - ST_{j}}{ ST_{i} + ST_{j}} (i,j = 1,2,3 \\text{ and i $\\lt$ j})$\u003c/p\u003e\n\u003cp\u003eThe same expressions are available for effective stresses (where SE replaces ST in the equation above).\u003c/p\u003e\n\u003ch3 id=\"sfi\"\u003eSFI\u003c/h3\u003e\n\u003cp\u003e$$SFI = \\frac{\\frac{S0}{tan(fa)} + 0.5 * (SE_1 + SE_3) * sin(fa)} {0.5*(SE_1-SE_3)}  $$\u003c/p\u003e\n\u003ch3 id=\"dsm\"\u003eDSM\u003c/h3\u003e\n\u003cp\u003e$DSM = \\frac{tan(\\rho)} {tan(fa)} $\u003c/p\u003e\n\u003cp\u003ewhere\u003c/p\u003e\n\u003cp\u003e$$ \\rho = 2 * (arctan (\\sqrt \\frac{ SE_1 + a} {SE_3 + a}) \\space – \\frac {\\pi} {4}) $$\n$$ a = \\frac {s0} {tan(fa)} $$\u003c/p\u003e\n\u003ch3 id=\"fos\"\u003eFOS\u003c/h3\u003e\n\u003cp\u003e$FOS = \\frac{1}{DSM}$\u003c/p\u003e\n\u003ch3 id=\"e---strain\"\u003eE - Strain\u003c/h3\u003e\n\u003cp\u003e$E_{ij} = -Ea_{ij}$\u003c/p\u003e\n\u003ch3 id=\"ev---volumetric-strain\"\u003eEV - Volumetric Strain\u003c/h3\u003e\n\u003cp\u003e$EV = E_{11} + E_{22} + E_{33} $\u003c/p\u003e\n\u003ch3 id=\"ed---deviatoric-strain\"\u003eED - Deviatoric Strain\u003c/h3\u003e\n\u003cp\u003e$ED = 2*\\frac {E1-E3} {3}  $\u003c/p\u003e\n\u003ch3 id=\"element-nodal-on-face\"\u003eElement Nodal On Face\u003c/h3\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\u003ch3 id=\"sn---stress-component-normal-to-face\"\u003eSN - Stress component Normal to face\u003c/h3\u003e\n\u003cp\u003e$SN = TS_{33}$\u003c/p\u003e\n\u003ch3 id=\"tph---horizontal-in-plane-shear-component\"\u003eTPH - Horizontal in-plane shear component\u003c/h3\u003e\n\u003cp\u003e$TPH = TS_{31} = TS_{ZX} $\u003c/p\u003e\n\u003ch3 id=\"tnqv---horizontal-in-plane-shear-component\"\u003eTNQV - Horizontal in-plane shear component\u003c/h3\u003e\n\u003cp\u003e$TPQV = TS_{32} = TS_{ZY}$\u003c/p\u003e\n\u003ch3 id=\"tp---total-in-plane-shear\"\u003eTP - Total in-plane shear\u003c/h3\u003e\n\u003cp\u003e$TP = \\sqrt {(TPH^2 + TPQV^2)} $\u003c/p\u003e\n\u003ch3 id=\"tpinc---direction-of-tp\"\u003eTPinc - Direction of TP\u003c/h3\u003e\n\u003cp\u003eAngle of the total in-plane shear relative to the Quasi Vertical direction\u003c/p\u003e\n\u003cp\u003e$TPinc = acos (\\frac {TPQV} {TP}) $\u003c/p\u003e\n\u003ch3 id=\"pinc-and-pazi---face-inclination-and-azimuth\"\u003ePinc and Pazi - Face Inclination and Azimuth\u003c/h3\u003e\n\u003cp\u003eThese are the directional angles of the face-normal itself.\u003c/p\u003e\n\u003ch3 id=\"pore-compressibility\"\u003ePore Compressibility\u003c/h3\u003e\n\u003ch4 id=\"pore-compressibility-1\"\u003ePore Compressibility\u003c/h4\u003e\n\u003cp\u003ePore compressibility between a reference state and the current stress state is defined as:\u003c/p\u003e\n\u003cp\u003e$ C_{p} = -\\frac{ \\alpha \\Delta\\epsilon_{vol}}{ \\Delta P_p \\phi_0} + \\frac{1}{K_s} ( \\frac{ \\alpha } { \\phi_0 } - 1) $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$ \\alpha $ is the Biot coefficient,\u003c/li\u003e\n\u003cli\u003e$ \\Delta\\epsilon_{vol} $ is volumetric strain change (EV in ResInsight) between curret state and reference state,\u003c/li\u003e\n\u003cli\u003e$ \\phi_0 $ is porosity on the Geostatic step,\u003c/li\u003e\n\u003cli\u003e$ \\Delta P_p $ is change in pore pressure between current state and reference state,\u003c/li\u003e\n\u003cli\u003e$ K_s $ bulk modulus for the solid material (grain).\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe Biot porelastic coefficient ($\\alpha$) defines the compressibility of sand grains: $\\alpha = 1.0$ for incompressible grains,\nand $\\alpha \u0026lt; 1.0$ for compressible grains. $\\alpha$ is not used for the initial (Geostatic) time step. The default value is 1.0, but values\nper element can be imported as an \u003ca href=\"/import/elementpropertytable/\"\u003eelement property table\u003c/a\u003e.\u003c/p\u003e\n\u003cp\u003eThe bulk modulus for solid material is defined as:\u003c/p\u003e\n\u003cp\u003e$ K_s = \\frac{ K_{fr} }{ 1 - \\alpha}, K_{fr} = \\frac{ E }{ 3(1-2\\nu)} $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$ E $ is the elastic modulus (Young\u0026rsquo;s modulus) from element property table \u003ca href=\"/import/elementpropertytable/\"\u003eMODULUS\u003c/a\u003e.\u003c/li\u003e\n\u003cli\u003e$ \\nu $ is Poisson\u0026rsquo;s ratio imported from element property table \u003ca href=\"/import/elementpropertytable/\"\u003eRATIO\u003c/a\u003e.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"vertical-compressibility\"\u003eVertical Compressibility\u003c/h4\u003e\n\u003cp\u003e$ C_{v} = - \\frac{ \\Delta\\epsilon_{\\nu}}{ \\alpha \\Delta P_p } $\u003c/p\u003e\n\u003cp\u003e$ \\Delta\\epsilon_\\nu $ is the vertical strain change between current state and reference state (E33 in ResInsight).\u003c/p\u003e\n\u003ch4 id=\"vertical-compressibility-ratio\"\u003eVertical Compressibility Ratio\u003c/h4\u003e\n\u003cp\u003e$ C_{vr} = \\frac{ C_v E(1-\\nu) } { (1+\\nu) ( 1 - 2\\nu) } $\u003c/p\u003e\n\u003cp\u003eVertical Compression Ratio is the ratio between the real vertical compression and the compression in a uniaxial strain case.\nAll parameters are described above.\u003c/p\u003e\n\u003ch3 id=\"porosity-and-permeability\"\u003ePorosity and Permeability\u003c/h3\u003e\n\u003ch4 id=\"porosity\"\u003ePorosity\u003c/h4\u003e\n\u003cp\u003ePorosity change is defined as either total change in porosity between initial (geostatic) state and current state,\nor change in porosity between a reference state and the current state $ \\Delta\\phi $. The latter is given as\u003c/p\u003e\n\u003cp\u003e$ \\Delta\\phi = \\phi_0(C_p \\Delta P_p + \\Delta\\epsilon_{vol}) $\u003c/p\u003e\n\u003cp\u003eHere, $\\Delta\\phi_0$ is found from this equation with the reference state being the initial state (geostatic).\nThe current porosity is then given as\u003c/p\u003e\n\u003cp\u003e$ \\phi = \\phi_0 + \\Delta\\phi_0 $\u003c/p\u003e\n\u003cp\u003ewith $ \\phi_0 $ being the porosity at the initial state, $\\Delta\\phi_0$ is porosity change between initial (geostatic)\nstate current, $C_p$ is pore compressibility (between reference and current state), $\\Delta P_p$ is change in pore pressure\nand $\\Delta\\epsilon_{vol}$ is volumetric strain change.\u003c/p\u003e\n\u003ch4 id=\"initial-porosity\"\u003eInitial Porosity\u003c/h4\u003e\n\u003cp\u003ePorosity at the initial state:\u003c/p\u003e\n\u003cp\u003e$ \\phi_0 = \\frac{VOIDR} {1 + VOIDR} $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eVOIDR is void ratio from Abaqus.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"permeability\"\u003ePermeability\u003c/h4\u003e\n\u003cp\u003eAn expression for permeability is taken from Petunin (2011).\u003c/p\u003e\n\u003cp\u003e$ k = k_0( \\frac{\\phi}{\\phi_0} )^A $\u003c/p\u003e\n\u003cp\u003eWhere:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e$k_0$ is the permeability at the initial state (unit: mD),\u003c/li\u003e\n\u003cli\u003e$\\phi$ is porosity at current state,\u003c/li\u003e\n\u003cli\u003e$\\phi_0$ is initial porosity,\u003c/li\u003e\n\u003cli\u003e$A$ is a constant\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"mud-weight-window\"\u003eMud Weight Window\u003c/h3\u003e\n\u003cp\u003eMud Weight Window (MWW) represents the difference between the minimum and the maximum possible\nmud weight between specific formation layers representing top and base of a fictitious well section.\u003c/p\u003e\n\u003cp\u003eTo find MWW a two step procedure is needed:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003efirst find the limits per element,\u003c/li\u003e\n\u003cli\u003edetermine the MWW for each element based on the vertical column.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"finding-upper-and-lower-mud-weight-limit\"\u003eFinding Upper and Lower Mud Weight Limit\u003c/h4\u003e\n\u003cp\u003eThe upper mud weight limit (UMWL) and lower mud weight limit (LMWL) is found for each element intersected by the fictitious well.\nThe UMWL is either the fracture gradient (FG) or minimum horizontal stress (SHmin) for both sand and shale.\nThe LMWL is defined as the maximum of shear fracture gradient (SFG) and/or pore pressure in shale, and as pore pressure in sand.\u003c/p\u003e\n\u003cp\u003eThe calculations for fracture gradient and shear fracture gradient, and the needed input, are described in detail\nin \u003ca href=\"/plot-window/wellborestabilityplots/\"\u003eWell Bore Stability Plots\u003c/a\u003e.\u003c/p\u003e\n\u003ch4 id=\"mud-weight-window-1\"\u003eMud Weight Window\u003c/h4\u003e\n\u003cp\u003eThereafter, the combined use of mud weight limits for all elements between the top and base (for a given IJ)\ndetermines the MWW parameters as will be further described below.\u003c/p\u003e\n\u003cp\u003eA reference element index ($K_{ref}$) represents the base or the top of the fictitious well. Then for a set\nof elements with i = I, j = J and k = K to $K_{ref}$ the maximum LWML and the minimum UWML must be found from\nthese element values. Then the difference between the two defines the MWW parameter.\u003c/p\u003e\n\u003cp\u003eThus for a vertical stack of elements $element_{ijk} = K \\to K_{ref}$, $MWW_{ijk}$ is given as\u003c/p\u003e\n\u003cp\u003e$ MWW_{ijk} = maximum(LMWL) - minimum(UMWL) (k = K \\to K_{ref}) $\u003c/p\u003e\n\u003cp\u003eSimilar calculations are made below the reference layer, but then with the reference layer as the top layer.\u003c/p\u003e\n\u003cp\u003eIn addition to the MWW parameter, the mud weight representing the middle of the drilling window (MWM) is calculated if MWW \u0026gt; 0.\nOtherwise, MWM should is undefined.\u003c/p\u003e\n",
                 url:      "/calculated-data/derivedresultsgeomech/"
             };
         
@@ -3974,8 +3973,8 @@ if (!doNotTrack) {
          
             window.store["/plot-window/flow-diagnostics-plots/"] = {
                 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 right-click 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 right-click 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 right-click 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.\nProducer/Injector Connectivity Table Use Producer/Injector Connectivity Table to see the flow diagnostics communication between producer and injector wells for selected time steps.\nWell Allocation Over Time Use Well Allocation Over Time to see the allocation over multiple restart time steps.\nCumulative Phase Distribution Plot A Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well. For producer B-2H, for instance, such a plot can be created by right-clicking its entry under Simulation Wells in Project Tree.\nA Cumulative Phase Distribution Plot can also be created by right-clicking a Cumulative Saturation plot, c.f. figure below.\nClicking its entry in Plot Project Tree, displays content and settings of the Cumulative Phase Distribution Plot.\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 right-click 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 right-click 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 right-click 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=\"producerinjector-connectivity-table\"\u003eProducer/Injector Connectivity Table\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ca href=\"/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/\"\u003eProducer/Injector Connectivity Table\u003c/a\u003e to see the flow diagnostics communication between producer and injector wells for selected time steps.\u003c/p\u003e\n\u003ch2 id=\"well-allocation-over-time\"\u003eWell Allocation Over Time\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationOverTime.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ca href=\"/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/\"\u003eWell Allocation Over Time\u003c/a\u003e to see the allocation over multiple restart time steps.\u003c/p\u003e\n\u003ch2 id=\"cumulative-phase-distribution-plot\"\u003eCumulative Phase Distribution Plot\u003c/h2\u003e\n\u003cp\u003eA Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well.\nFor producer B-2H, for instance, such a plot can be created by right-clicking its entry under \u003cstrong\u003eSimulation Wells\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionCreate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Cumulative Phase Distribution Plot can also be created by right-clicking a Cumulative Saturation plot, c.f. figure below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eClicking its entry in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e, displays content and settings of the Cumulative Phase Distribution Plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionProperties.png\" alt=\"\"\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",
+                content:  "\nFlow 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 right-click 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:\nName \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:\nName \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 right-click 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 right-click 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.\nProducer/Injector Connectivity Table Use Producer/Injector Connectivity Table to see the flow diagnostics communication between producer and injector wells for selected time steps.\nWell Allocation Over Time Use Well Allocation Over Time to see the allocation over multiple restart time steps.\nCumulative Phase Distribution Plot A Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well. For producer B-2H, for instance, such a plot can be created by right-clicking its entry under Simulation Wells in Project Tree.\nA Cumulative Phase Distribution Plot can also be created by right-clicking a Cumulative Saturation plot, c.f. figure below.\nClicking its entry in Plot Project Tree, displays content and settings of the Cumulative Phase Distribution Plot.\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.\nLorenz 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 right-click 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 right-click 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 right-click 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=\"producerinjector-connectivity-table\"\u003eProducer/Injector Connectivity Table\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ca href=\"/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/\"\u003eProducer/Injector Connectivity Table\u003c/a\u003e to see the flow diagnostics communication between producer and injector wells for selected time steps.\u003c/p\u003e\n\u003ch2 id=\"well-allocation-over-time\"\u003eWell Allocation Over Time\u003c/h2\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationOverTime.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ca href=\"/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/\"\u003eWell Allocation Over Time\u003c/a\u003e to see the allocation over multiple restart time steps.\u003c/p\u003e\n\u003ch2 id=\"cumulative-phase-distribution-plot\"\u003eCumulative Phase Distribution Plot\u003c/h2\u003e\n\u003cp\u003eA Cumulative Phase Distribution Plot shows the volumetric oil, gas, and water distribution from contributing wells to a target well.\nFor producer B-2H, for instance, such a plot can be created by right-clicking its entry under \u003cstrong\u003eSimulation Wells\u003c/strong\u003e in \u003cstrong\u003eProject Tree\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionCreate.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eA Cumulative Phase Distribution Plot can also be created by right-clicking a Cumulative Saturation plot, c.f. figure below.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionPlot.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eClicking its entry in \u003cstrong\u003ePlot Project Tree\u003c/strong\u003e, displays content and settings of the Cumulative Phase Distribution Plot.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/FlowDiagnosticsCumulativePhaseDistributionProperties.png\" alt=\"\"\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/flow-diagnostics-plots/"
             };
         
@@ -3983,7 +3982,7 @@ 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",
+                content:  "\nResInsight 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.\nInfo 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:\nThe 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",
                 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 \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",
                 url:      "/3d-main-window/gridstatisticsdialog/"
             };
@@ -3992,7 +3991,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/"] = {
                 title:    "Producer/Injector Connectivity Tables",
-                content:  "Producer/Injector Connectivity Tables is a display of Flow Diagnostics Data as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\nThe table lists one producer per row and one injector per column. The cell data is the flow rate data or accumulated flow volume data based on the selected Time Step Type. This table data provides an overview of the communicating wells in the reservoir, and shows which injector contributes to which producer, and who are the largest contributors to production.\nThe table can be formatted by use of the Property Editor, shown below. The cell data type is controlled by Value Type and the rows/columns can be filtered by selectecting producers and injectors in the Tracer Selection. Columns are controlled by the selection of resampling, and rows are controlled by selected Threshold value and Exclude Rows.\nCreating Producer/Injector Connectivity Tables The Producer/Injector Connectivity Tables are a part of the Flow Diagnostics Plots. Click here for how to generate the plots from 3D view.\nEditing Table The settings for the Producer/Injector Connectivity Table is listed in the Property Editor.\nThe main controls for a Producer/Injector Connectivity Table is listed below:\nPlot Data The plot data can be configured, and controls are depending on selections in Filter by 3D View.\n Filter by 3D View - Utilize the active filters in 3D view (see Filter) to collect which wells are present in the visible cells. Time Step Type - Select between single time step or a range of time steps.  Single Time Step - Shows flow rate - as raw value, fraction or percentage. Time Step Range - Shows accumulated flow volume - as raw value, fraction or percentage.   Threshold - Set threshold value for injectors. Exclude columns (injectors) if no row in column has value above threshold.  With filtering Disabled:  Select Wells For Time Step(s) - Automatically select producer and injector wells present for selected time step(s):  With filtering Enabled:  Filter type - Select how to apply the 3D view filtering to the table data.  Filter Producers - Select producer wells visible in selected Filter by 3D view, and synch communicating injectors. Filter Injectors - Select injector wells visible in selected Filter by 3D view, and synch communicating producers. Calculate By Visible Cells - Provide the cell filter to the calculation of well flow, and produce flow rate and accumulated flow volume data only using the cells present in the visible cells of 3D view.    Flow Diagnostics Configuration The content of flow diagnostics configuration is dependent on the selected Time Step Type.\n Value Type - Select which value type to fill in table cells  Single Time Step - Select between Flow Rate, Flow Rate Fraction and Flow Rate Percentage Time Step Range - Select between Accumulate Flow Volume, Accumulate Flow Volume Fraction and Accumulate Flow Volume Percentage    Single Time Step:  Value Type - Select which value type to fill in table cells: Flow Rate, Flow Rate Fraction and Flow Rate Percentage. Time Step - Select which time step to get data from  Time Step Range:  Value Type - Select which value type to fill in table cells: Accumulate Flow Volume, Accumulate Flow Volume Fraction and Accumulate Flow Volume Percentage From Time Step - Select time step to start range from. To Time Step - Select time step to end range on. Filter - Filter number of time steps to include: Show All Time Steps or Time Step Count. Number of Time Steps - Set number of time steps to include between From and To selection. Exclude Time Steps - Exclude specific time step if wanted.  Tracer Selection Select which Producers and Injectors to include in the table. If no wells are selected, no filtering is active - thereby all producers and injectors present among the selected time steps are visible in the table when values are above threshold.\nAn example of applying a Slice Filter in Filter by 3D View and select Filter Type: Filter Producers, produces the following Tracer Selection and table view:\nNote: If a selected well does not exist among the selected time steps, it will not be present in the table.\n",
+                content:  "\nProducer/Injector Connectivity Tables is a display of Flow Diagnostics Data as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\nThe table lists one producer per row and one injector per column. The cell data is the flow rate data or accumulated flow volume data based on the selected Time Step Type. This table data provides an overview of the communicating wells in the reservoir, and shows which injector contributes to which producer, and who are the largest contributors to production.\nThe table can be formatted by use of the Property Editor, shown below. The cell data type is controlled by Value Type and the rows/columns can be filtered by selectecting producers and injectors in the Tracer Selection. Columns are controlled by the selection of resampling, and rows are controlled by selected Threshold value and Exclude Rows.\nCreating Producer/Injector Connectivity Tables The Producer/Injector Connectivity Tables are a part of the Flow Diagnostics Plots. Click here for how to generate the plots from 3D view.\nEditing Table The settings for the Producer/Injector Connectivity Table is listed in the Property Editor.\nThe main controls for a Producer/Injector Connectivity Table is listed below:\nPlot Data The plot data can be configured, and controls are depending on selections in Filter by 3D View.\nFilter by 3D View - Utilize the active filters in 3D view (see Filter) to collect which wells are present in the visible cells. Time Step Type - Select between single time step or a range of time steps. Single Time Step - Shows flow rate - as raw value, fraction or percentage. Time Step Range - Shows accumulated flow volume - as raw value, fraction or percentage. Threshold - Set threshold value for injectors. Exclude columns (injectors) if no row in column has value above threshold. With filtering Disabled: Select Wells For Time Step(s) - Automatically select producer and injector wells present for selected time step(s): With filtering Enabled: Filter type - Select how to apply the 3D view filtering to the table data. Filter Producers - Select producer wells visible in selected Filter by 3D view, and synch communicating injectors. Filter Injectors - Select injector wells visible in selected Filter by 3D view, and synch communicating producers. Calculate By Visible Cells - Provide the cell filter to the calculation of well flow, and produce flow rate and accumulated flow volume data only using the cells present in the visible cells of 3D view. Flow Diagnostics Configuration The content of flow diagnostics configuration is dependent on the selected Time Step Type.\nValue Type - Select which value type to fill in table cells Single Time Step - Select between Flow Rate, Flow Rate Fraction and Flow Rate Percentage Time Step Range - Select between Accumulate Flow Volume, Accumulate Flow Volume Fraction and Accumulate Flow Volume Percentage Single Time Step: Value Type - Select which value type to fill in table cells: Flow Rate, Flow Rate Fraction and Flow Rate Percentage. Time Step - Select which time step to get data from Time Step Range: Value Type - Select which value type to fill in table cells: Accumulate Flow Volume, Accumulate Flow Volume Fraction and Accumulate Flow Volume Percentage From Time Step - Select time step to start range from. To Time Step - Select time step to end range on. Filter - Filter number of time steps to include: Show All Time Steps or Time Step Count. Number of Time Steps - Set number of time steps to include between From and To selection. Exclude Time Steps - Exclude specific time step if wanted. Tracer Selection Select which Producers and Injectors to include in the table. If no wells are selected, no filtering is active - thereby all producers and injectors present among the selected time steps are visible in the table when values are above threshold.\nAn example of applying a Slice Filter in Filter by 3D View and select Filter Type: Filter Producers, produces the following Tracer Selection and table view:\nNote: If a selected well does not exist among the selected time steps, it will not be present in the table.\n",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eProducer/Injector Connectivity Tables\u003c/strong\u003e is a display of \u003ca href=\"/plot-window/flow-diagnostics-plots/\"\u003eFlow Diagnostics Data\u003c/a\u003e as a color map in table format. The table either shows flow rate data for a single time step, or accumulated flow volume data over a range of time steps.\u003c/p\u003e\n\u003cp\u003eThe table lists one producer per row and one injector per column. The cell data is the flow rate data or accumulated flow volume data based on the selected \u003cstrong\u003eTime Step Type\u003c/strong\u003e. This table data provides an overview of the communicating wells in the reservoir, and shows which injector contributes to which producer, and who are the largest contributors to production.\u003c/p\u003e\n\u003cp\u003eThe table can be formatted by use of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, shown below. The cell data type is controlled by \u003cstrong\u003eValue Type\u003c/strong\u003e and the rows/columns can be filtered by selectecting producers and injectors in the \u003cstrong\u003eTracer Selection\u003c/strong\u003e. Columns are controlled by the selection of resampling, and rows are controlled by selected \u003cem\u003eThreshold\u003c/em\u003e value and \u003cem\u003eExclude Rows\u003c/em\u003e.\u003c/p\u003e\n\u003ch2 id=\"creating-producerinjector-connectivity-tables\"\u003eCreating Producer/Injector Connectivity Tables\u003c/h2\u003e\n\u003cp\u003eThe Producer/Injector Connectivity Tables are a part of the \u003cem\u003eFlow Diagnostics Plots\u003c/em\u003e. Click \u003ca href=\"/plot-window/flow-diagnostics-plots/#creating-well-allocation-plots\"\u003ehere\u003c/a\u003e for how to generate the plots from 3D view.\u003c/p\u003e\n\u003ch2 id=\"editing-table\"\u003eEditing Table\u003c/h2\u003e\n\u003cp\u003eThe settings for the Producer/Injector Connectivity Table is listed in the \u003cem\u003eProperty Editor\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_PropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe main controls for a Producer/Injector Connectivity Table is listed below:\u003c/p\u003e\n\u003ch4 id=\"plot-data\"\u003ePlot Data\u003c/h4\u003e\n\u003cp\u003eThe plot data can be configured, and controls are depending on selections in \u003cstrong\u003eFilter by 3D View\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFilter by 3D View\u003c/strong\u003e - Utilize the active filters in 3D view (see \u003ca href=\"/3d-main-window/filters/\"\u003eFilter\u003c/a\u003e) to collect which wells are present in the visible cells.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step Type\u003c/strong\u003e - Select between single time step or a range of time steps.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSingle Time Step\u003c/strong\u003e - Shows flow rate - as raw value, fraction or percentage.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step Range\u003c/strong\u003e - Shows accumulated flow volume - as raw value, fraction or percentage.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThreshold\u003c/strong\u003e - Set threshold value for injectors. Exclude columns (injectors) if no row in column has value above threshold.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"with-filtering-disabled\"\u003eWith filtering \u003cstrong\u003eDisabled\u003c/strong\u003e:\u003c/h5\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_FilterBy3DViewDisabled.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eSelect Wells For Time Step(s)\u003c/strong\u003e - Automatically select producer and injector wells present for selected time step(s):\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"with-filtering-enabled\"\u003eWith filtering \u003cstrong\u003eEnabled\u003c/strong\u003e:\u003c/h5\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_FilterBy3DViewEnabled.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFilter type\u003c/strong\u003e - Select how to apply the 3D view filtering to the table data.\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFilter Producers\u003c/strong\u003e - Select producer wells visible in selected \u003cem\u003eFilter by 3D view\u003c/em\u003e, and synch communicating injectors.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFilter Injectors\u003c/strong\u003e - Select injector wells visible in selected \u003cem\u003eFilter by 3D view\u003c/em\u003e, and synch communicating producers.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eCalculate By Visible Cells\u003c/strong\u003e - Provide the cell filter to the calculation of well flow, and produce flow rate and accumulated flow volume data only using the cells present in the visible cells of 3D view.\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"flow-diagnostics-configuration\"\u003eFlow Diagnostics Configuration\u003c/h4\u003e\n\u003cp\u003eThe content of flow diagnostics configuration is dependent on the selected \u003cstrong\u003eTime Step Type\u003c/strong\u003e.\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Type\u003c/strong\u003e - Select which value type to fill in table cells\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eSingle Time Step\u003c/em\u003e - Select between \u003cstrong\u003eFlow Rate\u003c/strong\u003e, \u003cstrong\u003eFlow Rate Fraction\u003c/strong\u003e and \u003cstrong\u003eFlow Rate Percentage\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eTime Step Range\u003c/em\u003e - Select between \u003cstrong\u003eAccumulate Flow Volume\u003c/strong\u003e, \u003cstrong\u003eAccumulate Flow Volume Fraction\u003c/strong\u003e and \u003cstrong\u003eAccumulate Flow Volume Percentage\u003c/strong\u003e\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"single-time-step\"\u003eSingle Time Step:\u003c/h5\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_SingleTimeStepFlowDiagnosticsConfiguration.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Type\u003c/strong\u003e - Select which value type to fill in table cells: \u003cstrong\u003eFlow Rate\u003c/strong\u003e, \u003cstrong\u003eFlow Rate Fraction\u003c/strong\u003e and \u003cstrong\u003eFlow Rate Percentage\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTime Step\u003c/strong\u003e - Select which time step to get data from\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch5 id=\"time-step-range\"\u003eTime Step Range:\u003c/h5\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_TimeStepRangeFlowDiagnosticsConfiguration.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eValue Type\u003c/strong\u003e - Select which value type to fill in table cells: \u003cstrong\u003eAccumulate Flow Volume\u003c/strong\u003e, \u003cstrong\u003eAccumulate Flow Volume Fraction\u003c/strong\u003e and \u003cstrong\u003eAccumulate Flow Volume Percentage\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFrom Time Step\u003c/strong\u003e - Select time step to start range from.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTo Time Step\u003c/strong\u003e - Select time step to end range on.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFilter\u003c/strong\u003e - Filter number of time steps to include: \u003cstrong\u003eShow All Time Steps\u003c/strong\u003e or \u003cstrong\u003eTime Step Count\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Time Steps\u003c/strong\u003e - Set number of time steps to include between \u003cstrong\u003eFrom\u003c/strong\u003e and \u003cstrong\u003eTo\u003c/strong\u003e selection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Time Steps\u003c/strong\u003e - Exclude specific time step if wanted.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"tracer-selection\"\u003eTracer Selection\u003c/h4\u003e\n\u003cp\u003eSelect which \u003cstrong\u003eProducers\u003c/strong\u003e and \u003cstrong\u003eInjectors\u003c/strong\u003e to include in the table. If no wells are selected, no filtering is active - thereby all producers and injectors present among the selected time steps are visible in the table when values are above \u003cem\u003ethreshold\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eAn example of applying a \u003ca href=\"/3d-main-window/filters/#cell-filters\"\u003eSlice Filter\u003c/a\u003e in \u003cem\u003eFilter by 3D View\u003c/em\u003e and select \u003cem\u003eFilter Type: Filter Producers\u003c/em\u003e, produces the following \u003cem\u003eTracer Selection\u003c/em\u003e and table view:\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_FilterProducerTracerSelection.png\" alt=\"\"\u003e\n\u003cimg src=\"/images/plot-window/Producer_Injector_Connectivity_FilterProducerTable.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eNote\u003c/strong\u003e: If a selected well does not exist among the selected time steps, it will not be present in the table.\u003c/p\u003e\n",
                 url:      "/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/"
             };
@@ -4001,7 +4000,7 @@ if (!doNotTrack) {
          
             window.store["/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/"] = {
                 title:    "Well Allocation Over Time Plot",
-                content:  "Well Allocation Over Time Plot is a plot displaying the flow data of Well Allocation Plots over a range of time steps. The plot provides the union of wells existing across all time steps for the selected case.\nThe plot utilize the Flow Diagnostics to provide an overview of which well or phase contributes most to the flow in a selected well. One can e.g. see which injectors are contributing to production of a producing well, and vice versa, over the selected time step range. The plot can be configured with a From and To time step to create the defined time step range. One can either utilize all time steps in the defined range, or one can down sample the date resolution by defining a number of time steps to utilize. Specific time steps flow values can be excluded by selection - the flow rate value for next time step is then utilized for calculations for excluded time step.\nThe Plot Type can either be Allocation or Well Flow. Allocation shows flow data for wells contributing to the flow of the selected Well, whereas Well Flow shows the flow data for contributing phases (Oil, Water and Gas) for the selected Well.\nThe data values are controlled by Value Type, where one can select between:\n Flow Rates - [$m^{3}/day$] The flow rate at each time step. Flow Rate percentage - [$\\text{%}$] The flow rate contribution in percentage of total flow rate at each time step. Flow Volumes - [$m^{3}$] The flow volume between a time step and previous time step (flow rate multiplied with days between time steps). Accumulated Flow Volumes - [$m^{3}$] The flow volume accumulated for each time step. Accumulated Flow Volume Percentage - [$\\text{%}$] The flow volume accumulated for each time step in percentage of total accumulated flow volume at time step.  Note that flow rates and flow volume is constant for a time step and back in time to previous time step in the selected time step range. Accumulated flow volume values are linear interpolated from the respective time step and to previous time step. Small contributors can be grouped into Other by enabling grouping and setting a Threshold value.\nFurther plot configuration is performed by use of the Property Editor, shown below.\nCreating Well Allocation Over Time Plot The Well Allocation Over Time Plot is a part of the Flow Diagnostics Plots. Click here for how to generate the plots from 3D view.\nEditing Table The settings for the Well Allocation Over Time Plot is listed in the Property Editor.\nThe main controls for a Well Allocation Over Time Plot is listed below:\nPlot Data  Case - Select case to retrieve data from. Well - Which case well to calculate Flow Diagnostics over time for.  Time Step  From Time Step - Select time step to start range from. To Time Step - Select time step to end range on. Filter - Filter number of time steps to include: Show All Time Steps or Time Step Count. Number of Time Steps - Set number of time steps to include between From and To selection. Exclude Time Steps - Exclude specific time step if wanted (utilize flow rate value for next time step).  Options  Plot Type - Select between Allocation or Well Flow. Value Type - Select between: Flow Rates, Flow Rate percentage, Flow Volumes, Accumulated Flow Volumes and Accumulated Flow Volume Percentage Group Small Contributions - Enable to group small contributors in category Other Threshold - [$0, 1$] Contributor values below threshold is grouped into category Other when grouping is enabled.  ",
+                content:  "\nWell Allocation Over Time Plot is a plot displaying the flow data of Well Allocation Plots over a range of time steps. The plot provides the union of wells existing across all time steps for the selected case.\nThe plot utilize the Flow Diagnostics to provide an overview of which well or phase contributes most to the flow in a selected well. One can e.g. see which injectors are contributing to production of a producing well, and vice versa, over the selected time step range. The plot can be configured with a From and To time step to create the defined time step range. One can either utilize all time steps in the defined range, or one can down sample the date resolution by defining a number of time steps to utilize. Specific time steps flow values can be excluded by selection - the flow rate value for next time step is then utilized for calculations for excluded time step.\nThe Plot Type can either be Allocation or Well Flow. Allocation shows flow data for wells contributing to the flow of the selected Well, whereas Well Flow shows the flow data for contributing phases (Oil, Water and Gas) for the selected Well.\nThe data values are controlled by Value Type, where one can select between:\nFlow Rates - [$m^{3}/day$] The flow rate at each time step. Flow Rate percentage - [$\\text{%}$] The flow rate contribution in percentage of total flow rate at each time step. Flow Volumes - [$m^{3}$] The flow volume between a time step and previous time step (flow rate multiplied with days between time steps). Accumulated Flow Volumes - [$m^{3}$] The flow volume accumulated for each time step. Accumulated Flow Volume Percentage - [$\\text{%}$] The flow volume accumulated for each time step in percentage of total accumulated flow volume at time step. Note that flow rates and flow volume is constant for a time step and back in time to previous time step in the selected time step range. Accumulated flow volume values are linear interpolated from the respective time step and to previous time step. Small contributors can be grouped into Other by enabling grouping and setting a Threshold value.\nFurther plot configuration is performed by use of the Property Editor, shown below.\nCreating Well Allocation Over Time Plot The Well Allocation Over Time Plot is a part of the Flow Diagnostics Plots. Click here for how to generate the plots from 3D view.\nEditing Table The settings for the Well Allocation Over Time Plot is listed in the Property Editor.\nThe main controls for a Well Allocation Over Time Plot is listed below:\nPlot Data Case - Select case to retrieve data from. Well - Which case well to calculate Flow Diagnostics over time for. Time Step From Time Step - Select time step to start range from. To Time Step - Select time step to end range on. Filter - Filter number of time steps to include: Show All Time Steps or Time Step Count. Number of Time Steps - Set number of time steps to include between From and To selection. Exclude Time Steps - Exclude specific time step if wanted (utilize flow rate value for next time step). Options Plot Type - Select between Allocation or Well Flow. Value Type - Select between: Flow Rates, Flow Rate percentage, Flow Volumes, Accumulated Flow Volumes and Accumulated Flow Volume Percentage Group Small Contributions - Enable to group small contributors in category Other Threshold - [$0, 1$] Contributor values below threshold is grouped into category Other when grouping is enabled. ",
                 html:     "\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationOverTime.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003e\u003cstrong\u003eWell Allocation Over Time Plot\u003c/strong\u003e is a plot displaying the flow data of \u003ca href=\"/plot-window/flow-diagnostics-plots/#well-allocation-plots\"\u003eWell Allocation Plots\u003c/a\u003e over a range of time steps. The plot provides the union of wells existing across all time steps for the selected case.\u003c/p\u003e\n\u003cp\u003eThe plot utilize the \u003cem\u003eFlow Diagnostics\u003c/em\u003e to provide an overview of which well or phase contributes most to the flow in a selected well. One can e.g. see which injectors are contributing to production of a producing well, and vice versa, over the selected time step range. The plot can be configured with a \u003cem\u003eFrom\u003c/em\u003e and \u003cem\u003eTo\u003c/em\u003e time step to create the defined time step range. One can either utilize all time steps in the defined range, or one can down sample the date resolution by defining a number of time steps to utilize. Specific time steps flow values can be excluded by selection - the flow rate value for next time step is then utilized for calculations for excluded time step.\u003c/p\u003e\n\u003cp\u003eThe \u003cstrong\u003ePlot Type\u003c/strong\u003e can either be \u003cstrong\u003eAllocation\u003c/strong\u003e or \u003cstrong\u003eWell Flow\u003c/strong\u003e. \u003cem\u003eAllocation\u003c/em\u003e shows flow data for wells contributing to the flow of the selected \u003cem\u003eWell\u003c/em\u003e, whereas \u003cem\u003eWell Flow\u003c/em\u003e shows the flow data for contributing phases (\u003cem\u003eOil\u003c/em\u003e, \u003cem\u003eWater\u003c/em\u003e and \u003cem\u003eGas\u003c/em\u003e) for the selected \u003cem\u003eWell\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003eThe data values are controlled by \u003cstrong\u003eValue Type\u003c/strong\u003e, where one can select between:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cem\u003eFlow Rates\u003c/em\u003e - [$m^{3}/day$] The flow rate at each time step.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eFlow Rate percentage\u003c/em\u003e - [$\\text{%}$] The flow rate contribution in percentage of total flow rate at each time step.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eFlow Volumes\u003c/em\u003e - [$m^{3}$] The flow volume between a time step and previous time step (flow rate multiplied with days between time steps).\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eAccumulated Flow Volumes\u003c/em\u003e - [$m^{3}$] The flow volume accumulated for each time step.\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eAccumulated Flow Volume Percentage\u003c/em\u003e - [$\\text{%}$] The flow volume accumulated for each time step in percentage of total accumulated flow volume at time step.\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eNote that flow rates and flow volume is constant for a time step and back in time to previous time step in the selected time step range. Accumulated flow volume values are linear interpolated from the respective time step and to previous time step. Small contributors can be grouped into \u003cstrong\u003eOther\u003c/strong\u003e by enabling grouping and setting a \u003cstrong\u003eThreshold\u003c/strong\u003e value.\u003c/p\u003e\n\u003cp\u003eFurther plot configuration is performed by use of the \u003cstrong\u003eProperty Editor\u003c/strong\u003e, shown below.\u003c/p\u003e\n\u003ch2 id=\"creating-well-allocation-over-time-plot\"\u003eCreating Well Allocation Over Time Plot\u003c/h2\u003e\n\u003cp\u003eThe Well Allocation Over Time Plot is a part of the \u003cem\u003eFlow Diagnostics Plots\u003c/em\u003e. Click \u003ca href=\"/plot-window/flow-diagnostics-plots/#creating-well-allocation-plots\"\u003ehere\u003c/a\u003e for how to generate the plots from 3D view.\u003c/p\u003e\n\u003ch2 id=\"editing-table\"\u003eEditing Table\u003c/h2\u003e\n\u003cp\u003eThe settings for the Well Allocation Over Time Plot is listed in the \u003cem\u003eProperty Editor\u003c/em\u003e.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/plot-window/WellAllocationOverTimePlot_PropertyEditor.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003cp\u003eThe main controls for a Well Allocation Over Time Plot is listed below:\u003c/p\u003e\n\u003ch4 id=\"plot-data\"\u003ePlot Data\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eCase\u003c/strong\u003e - Select case to retrieve data from.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eWell\u003c/strong\u003e - Which case well to calculate \u003cem\u003eFlow Diagnostics\u003c/em\u003e over time for.\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"time-step\"\u003eTime Step\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003eFrom Time Step\u003c/strong\u003e - Select time step to start range from.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eTo Time Step\u003c/strong\u003e - Select time step to end range on.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eFilter\u003c/strong\u003e - Filter number of time steps to include: \u003cstrong\u003eShow All Time Steps\u003c/strong\u003e or \u003cstrong\u003eTime Step Count\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eNumber of Time Steps\u003c/strong\u003e - Set number of time steps to include between \u003cstrong\u003eFrom\u003c/strong\u003e and \u003cstrong\u003eTo\u003c/strong\u003e selection.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eExclude Time Steps\u003c/strong\u003e - Exclude specific time step if wanted (utilize flow rate value for next time step).\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch4 id=\"options\"\u003eOptions\u003c/h4\u003e\n\u003cul\u003e\n\u003cli\u003e\u003cstrong\u003ePlot Type\u003c/strong\u003e - Select between \u003cstrong\u003eAllocation\u003c/strong\u003e or \u003cstrong\u003eWell Flow\u003c/strong\u003e.\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eValue Type\u003c/strong\u003e - Select between: \u003cem\u003eFlow Rates\u003c/em\u003e, \u003cem\u003eFlow Rate percentage\u003c/em\u003e, \u003cem\u003eFlow Volumes\u003c/em\u003e, \u003cem\u003eAccumulated Flow Volumes\u003c/em\u003e and \u003cem\u003eAccumulated Flow Volume Percentage\u003c/em\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eGroup Small Contributions\u003c/strong\u003e - Enable to group small contributors in category \u003cstrong\u003eOther\u003c/strong\u003e\u003c/li\u003e\n\u003cli\u003e\u003cstrong\u003eThreshold\u003c/strong\u003e - [$0, 1$] Contributor values below threshold is grouped into category \u003cstrong\u003eOther\u003c/strong\u003e when grouping is enabled.\u003c/li\u003e\n\u003c/ul\u003e\n",
                 url:      "/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/"
             };
@@ -4010,8 +4009,8 @@ if (!doNotTrack) {
          
             window.store["/3d-main-window/casegroupsandstatistics/"] = {
                 title:    "Grid Case Groups and Statistics",
-                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\nThis command will display the recursive file import dialog described on the Summary Plots page.\nResInsight 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.\nHow to limit system resource allocation\rTo 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. \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\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis command will display the recursive file import dialog described on the \u003ca href=\"/import/eclipsesummarydata/#ensemble-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/p\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\u003ch5\u003eHow to limit system resource allocation\u003c/h5\u003e\r\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. \r\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",
+                content:  "\nGrid 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\nThis command will display the recursive file import dialog described on the Summary Plots page.\nResInsight 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\rTo 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. Statistics 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:\nCompute \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:\nInterpolated 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\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\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\u003c/strong\u003e\u003c/p\u003e\n\u003cp\u003eThis command will display the recursive file import dialog described on the \u003ca href=\"/import/eclipsesummarydata/#ensemble-file-import\"\u003eSummary Plots page\u003c/a\u003e.\u003c/p\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\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\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\u003ch5\u003eHow to limit system resource allocation\u003c/h5\u003e\r\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. \r\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/"
             };
         
@@ -4019,7 +4018,7 @@ 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",
+                content:  "\nResInsight 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:\nSelect 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:\nParameter 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/"
             };
@@ -4028,8 +4027,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.  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.\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",
+                content:  "\nOne 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. 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:\nOpen 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:\nShow 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.\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/"
             };
         
@@ -4037,7 +4036,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",
+                content:  "\nA 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\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/"
             };
@@ -4046,7 +4045,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",
+                content:  "\nResInsight 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:\nLength - 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.\nSegment 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\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/"
             };
@@ -4055,8 +4054,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  Polyline File format Define each point as three double per line (X Y Depth). Comment lines are supported by using # at the start of the line\n# This is a comment\r# This is a comment\r58177.76 732.7 1643.6 58260.83 732.8 1596.6 57985.66 732.7 1542.0 59601.45 732.4 3639.0 59422.01 732.2 3639.0 59793.41 732.2 3639.0 999 999 999\r# starting polyline 2\r58260.83 732.8 1596.6 57985.66 732.7 1542.0 59601.45 732.4 3639.0 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\u003cbr/\u003e\nLocal annotations sub tree\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GlobalAnnotationsTree.png\" alt=\"\"\u003e\u003cbr/\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\u003ch3 id=\"polyline-file-format\"\u003ePolyline File format\u003c/h3\u003e\n\u003cp\u003eDefine each point as three double per line (\u003cstrong\u003eX Y Depth\u003c/strong\u003e). Comment lines are supported by using \u003cstrong\u003e#\u003c/strong\u003e at the start of the line\u003c/p\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-txt\" data-lang=\"txt\"\u003e# This is a comment\r\n# This is a comment\r\n58177.76 732.7 1643.6 \r\n58260.83 732.8 1596.6 \r\n57985.66 732.7 1542.0 \r\n59601.45 732.4 3639.0 \r\n59422.01 732.2 3639.0 \r\n59793.41 732.2 3639.0 \r\n999 999 999\r\n# starting polyline 2\r\n58260.83 732.8 1596.6 \r\n57985.66 732.7 1542.0 \r\n59601.45 732.4 3639.0 \r\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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",
+                content:  "ResInsight supports displaying a few types of annotations in 3D views and Contour Map view.\nText 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.\nRight 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.\nName - 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.\nTargets - 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.\nFile - Name of the imported file Line Appearance - Set line color and line thickness Polyline File format Define each point as three double per line (X Y Depth). Comment lines are supported by using # at the start of the line\n# This is a comment # This is a comment 58177.76 732.7 1643.6 58260.83 732.8 1596.6 57985.66 732.7 1542.0 59601.45 732.4 3639.0 59422.01 732.2 3639.0 59793.41 732.2 3639.0 999 999 999 # starting polyline 2 58260.83 732.8 1596.6 57985.66 732.7 1542.0 59601.45 732.4 3639.0 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\u003cbr/\u003e\nLocal annotations sub tree\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/3d-main-window/GlobalAnnotationsTree.png\" alt=\"\"\u003e\u003cbr/\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\u003ch3 id=\"polyline-file-format\"\u003ePolyline File format\u003c/h3\u003e\n\u003cp\u003eDefine each point as three double per line (\u003cstrong\u003eX Y Depth\u003c/strong\u003e). Comment lines are supported by using \u003cstrong\u003e#\u003c/strong\u003e at the start of the line\u003c/p\u003e\n\u003cdiv class=\"highlight\"\u003e\u003cpre tabindex=\"0\" style=\"color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;\"\u003e\u003ccode class=\"language-txt\" data-lang=\"txt\"\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# This is a comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# This is a comment\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e58177.76 732.7 1643.6 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e58260.83 732.8 1596.6 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e57985.66 732.7 1542.0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e59601.45 732.4 3639.0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e59422.01 732.2 3639.0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e59793.41 732.2 3639.0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e999 999 999\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e# starting polyline 2\n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e58260.83 732.8 1596.6 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e57985.66 732.7 1542.0 \n\u003c/span\u003e\u003c/span\u003e\u003cspan style=\"display:flex;\"\u003e\u003cspan\u003e59601.45 732.4 3639.0 \n\u003c/span\u003e\u003c/span\u003e\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\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/"
             };
         
@@ -4065,7 +4064,7 @@ if (!doNotTrack) {
             window.store["/_footer/"] = {
                 title:    "",
                 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",
+                html:     "\u003ch3 id=\"abouthahahugoshortcodes0hbhb\"\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=\"supporthahahugoshortcodes1hbhb\"\u003e\u003ca href=\"/support/\"\u003eSupport\u003c/a\u003e\u003c/h3\u003e\n",
                 url:      "/_footer/"
             };
         
@@ -4082,8 +4081,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:     "\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 \u003ca href=\"https://www.equinor.com/\"\u003eEquinor\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",
+                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:\nAdding 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:     "\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 \u003ca href=\"https://www.equinor.com/\"\u003eEquinor\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/"
             };
         
@@ -4109,7 +4108,7 @@ if (!doNotTrack) {
          
             window.store["/"] = {
                 title:    "ResInsight",
-                content:  "ResInsight • 3D viewer and post processing of reservoir models\rPost Processing of Reservoir Simulations Fast and Free\r\r\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\u0026#x2713; Python API for scripting\n\rUnique Features\r\r\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\rGetting started\r\rIt's easy and free, both on Linux and Windows:\rDownload and Install \u0026rarr;\nGetting Started \u0026rarr;\rSign up to be notified of new releases:\rRelease Notification \u0026rarr;\r\r\r\rHere are some words from a few of the happy ResInsight users Testimonials \u0026rarr; \r\r\r",
+                content:  "ResInsight • 3D viewer and post processing of reservoir models\rPost Processing of Reservoir Simulations Fast and Free\r\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\u0026#x2713; Python API for scripting\nUnique Features\r\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\nGetting started\rIt's easy and free, both on Linux and Windows:\rDownload and Install \u0026rarr;\nGetting Started \u0026rarr;\rSign up to be notified of new releases:\rRelease Notification \u0026rarr;\rHere are some words from a few of the happy ResInsight users Testimonials \u0026rarr; ",
                 html:     "\u003ctitle\u003eResInsight • 3D viewer and post processing of reservoir models\u003c/title\u003e\r\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\u003csection class=\"features\"\u003e\r\n  \u003cdiv class=\"grid\"\u003e\r\n    \u003cdiv class=\"unit one-third\"\u003e\r\n      \u003ch3\u003eFast and Free\u003c/h3\u003e\r\n      \u003cp\u003e\r\n        \u0026#x2713; Open source\u003cbr\u003e\r\n        \u0026#x2713; Efficient user interface\u003cbr\u003e\r\n\t\u0026#x2713; Handles large Eclipse cases\u003cbr\u003e\r\n        \u0026#x2713; Plotting of summary vectors\u003cbr\u003e\r\n\t\u0026#x2713; Embedded Flow Diagnostics\u003cbr\u003e\r\n        \u0026#x2713; Python API for scripting\u003cbr\u003e\r\n      \u003c/p\u003e\r\n    \u003c/div\u003e\r\n    \u003cdiv class=\"unit one-third\"\u003e\r\n      \u003ch3\u003eUnique Features\u003c/h3\u003e\r\n      \u003cp\u003e\r\n        \u0026#x2713; NNC visualization\u003cbr\u003e\r\n        \u0026#x2713; Cell Edge Coloring\u003cbr\u003e\r\n        \u0026#x2713; Detailed MSW visualization\u003cbr\u003e\r\n        \u0026#x2713; Seamless \u003ca href=\"http://www.gnu.org/software/octave/\"\u003e Octave\u003c/a\u003e integration\u003cbr\u003e\r\n        \u0026#x2713; Supports geomechanical ABAQUS simulations\u003cbr\u003e\r\n      \u003c/p\u003e\r\n    \u003c/div\u003e\r\n    \u003cdiv class=\"unit one-third\"\u003e\r\n      \u003ch3\u003eGetting started\u003c/h3\u003e\r\n      \u003cp\u003e\r\n        It's easy and free, both on Linux and Windows:\r\n      \u003c/p\u003e\r\n      \u003ca href=\"/getting-started/download-and-install/\"\u003eDownload and Install \u0026rarr;\u003c/a\u003e\u003cbr\u003e\r\n      \u003ca href=\"/getting-started/\"\u003eGetting Started \u0026rarr;\u003c/a\u003e\r\n      \u003cp\u003eSign up to be notified of new releases:\r\n        \u003cbr\u003e\r\n        \u003ca href=\"/getting-started/other/releasenotification/\"\u003eRelease Notification \u0026rarr;\u003c/a\u003e\r\n      \u003c/p\u003e\r\n      \u003c/div\u003e\r\n    \u003cdiv class=\"clear\"\u003e\u003c/div\u003e\r\n  \u003c/div\u003e\r\n  \u003cdiv class=\"grid\"\u003e\r\n    \u003cdiv class=\"unit whole center-on-mobiles\"\u003e\r\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\r\n    \u003c/div\u003e\r\n  \u003c/div\u003e\r\n\u003c/section\u003e\r\n",
                 url:      "/"
             };
@@ -4120,7 +4119,7 @@ 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",
+                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 \u003cbr\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\u003ca href=\"http://www.ceetronsolutions.com\"\u003e\u003cimg src=\"/images/CeetronSolutionWebPage.png\" alt=\"\"\u003e\u003c/a\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\u003ca href=\"http://www.ceetronsolutions.com\"\u003e\u003c/a\u003e\u003c/p\u003e\n",
                 url:      "/support/"
             };
@@ -4138,7 +4137,7 @@ if (!doNotTrack) {
          
             window.store["/training/"] = {
                 title:    "Training Courses",
-                content:  "ResInsight Introduction Course Content  3D visualization of Eclipse models including faults, intersections, surfaces, and contour maps Eclipse Summary plots, ensemble plots and observed data RFT plots, correlation plots, and analysis plots Flow Diagnostics Linking and comparison of views  Course goals Proficiency in evaluating Eclipse simulation results by 3D visualization and plotting in ResInsight.\nPrerequisites Knowledge about Eclipse reservoir simulations.\nNotes The course is offered online on both Windows and Linux systems.\nContact information Please contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: info@ceetronsolutions.com\nResInsight Advanced Course Content  Data analysis, grid properties cross-plotting, grid statistics across ensemble of models Import and create well paths, extraction and plotting of grid data along well Sector model export Create well completions with perforations, Fishbones and hydraulic fractures (StimPlan import) ResInsight project file format  Course goals Proficiency in analyzing grid data, make sector models, visualize well data and create well completions using ResInsight.\nNotes The course is offered online on both Windows and Linux systems.\nPrerequisites  Knowledge about Eclipse reservoir simulations. Experience with basic use of ResInsight (c.f. ResInsight Introduction course).  Contact information Please contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: info@ceetronsolutions.com\n",
+                content:  "ResInsight Introduction Course Content 3D visualization of Eclipse models including faults, intersections, surfaces, and contour maps Eclipse Summary plots, ensemble plots and observed data RFT plots, correlation plots, and analysis plots Flow Diagnostics Linking and comparison of views Course goals Proficiency in evaluating Eclipse simulation results by 3D visualization and plotting in ResInsight.\nPrerequisites Knowledge about Eclipse reservoir simulations.\nNotes The course is offered online on both Windows and Linux systems.\nContact information Please contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: info@ceetronsolutions.com\nResInsight Advanced Course Content Data analysis, grid properties cross-plotting, grid statistics across ensemble of models Import and create well paths, extraction and plotting of grid data along well Sector model export Create well completions with perforations, Fishbones and hydraulic fractures (StimPlan import) ResInsight project file format Course goals Proficiency in analyzing grid data, make sector models, visualize well data and create well completions using ResInsight.\nNotes The course is offered online on both Windows and Linux systems.\nPrerequisites Knowledge about Eclipse reservoir simulations. Experience with basic use of ResInsight (c.f. ResInsight Introduction course). Contact information Please contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: info@ceetronsolutions.com\n",
                 html:     "\u003ch2 id=\"resinsight-introduction-course\"\u003eResInsight Introduction Course\u003c/h2\u003e\n\u003ch3 id=\"content\"\u003eContent\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003e3D visualization of Eclipse models including faults, intersections, surfaces, and contour maps\u003c/li\u003e\n\u003cli\u003eEclipse Summary plots, ensemble plots and observed data\u003c/li\u003e\n\u003cli\u003eRFT plots, correlation plots, and analysis plots\u003c/li\u003e\n\u003cli\u003eFlow Diagnostics\u003c/li\u003e\n\u003cli\u003eLinking and comparison of views\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"course-goals\"\u003eCourse goals\u003c/h3\u003e\n\u003cp\u003eProficiency in evaluating Eclipse simulation results by 3D visualization and plotting in ResInsight.\u003c/p\u003e\n\u003ch3 id=\"prerequisites\"\u003ePrerequisites\u003c/h3\u003e\n\u003cp\u003eKnowledge about Eclipse reservoir simulations.\u003c/p\u003e\n\u003ch3 id=\"notes\"\u003eNotes\u003c/h3\u003e\n\u003cp\u003eThe course is offered online on both Windows and Linux systems.\u003c/p\u003e\n\u003ch3 id=\"contact-information\"\u003eContact information\u003c/h3\u003e\n\u003cp\u003ePlease contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: \u003ca href=\"mailto:info@ceetronsolutions.com\"\u003einfo@ceetronsolutions.com\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/ResInsightIntroductionCourse.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"resinsight-advanced-course\"\u003eResInsight Advanced Course\u003c/h2\u003e\n\u003ch3 id=\"content-1\"\u003eContent\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003eData analysis, grid properties cross-plotting, grid statistics across ensemble of models\u003c/li\u003e\n\u003cli\u003eImport and create well paths, extraction and plotting of grid data along well\u003c/li\u003e\n\u003cli\u003eSector model export\u003c/li\u003e\n\u003cli\u003eCreate well completions with perforations, Fishbones and hydraulic fractures (StimPlan import)\u003c/li\u003e\n\u003cli\u003eResInsight project file format\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"course-goals-1\"\u003eCourse goals\u003c/h3\u003e\n\u003cp\u003eProficiency in analyzing grid data, make sector models, visualize well data and create well completions using ResInsight.\u003c/p\u003e\n\u003ch3 id=\"notes-1\"\u003eNotes\u003c/h3\u003e\n\u003cp\u003eThe course is offered online on both Windows and Linux systems.\u003c/p\u003e\n\u003ch3 id=\"prerequisites-1\"\u003ePrerequisites\u003c/h3\u003e\n\u003cul\u003e\n\u003cli\u003eKnowledge about Eclipse reservoir simulations.\u003c/li\u003e\n\u003cli\u003eExperience with basic use of ResInsight (c.f. ResInsight Introduction course).\u003c/li\u003e\n\u003c/ul\u003e\n\u003ch3 id=\"contact-information-1\"\u003eContact information\u003c/h3\u003e\n\u003cp\u003ePlease contact Ceetron Solutions for requests, phone +47 73 60 43 00, e-mail: \u003ca href=\"mailto:info@ceetronsolutions.com\"\u003einfo@ceetronsolutions.com\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/images/ResInsightAdvancedCourse.png\" alt=\"\"\u003e\u003c/p\u003e\n",
                 url:      "/training/"
             };
@@ -6269,19 +6268,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/sitemap.xml b/sitemap.xml
index fe0c44155a..44d85de4f6 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,601 +1,303 @@
 <?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">
-  
   <url>
     <loc>https://resinsight.org/getting-started/overview/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/projecttree/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/3dviews/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/calculatorexpressions/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/download-and-install/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/eclipsecases/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/eclipsesummarydata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/ensemblefiledialog/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/download-and-install/linux-installation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/preferences/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/roffgridmodels/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/simulationwells/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/snapshots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summaryplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2019_04/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2019_08/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2019_12/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2019_12_1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2020_04/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2020_04_1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2020_10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2020_10_1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2021_06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2021_10/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2022_06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2022_06_1/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2023_01/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2023_03/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2023_06/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summaryplotdatasources/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/seismicdata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/lasfile/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/projectfile/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/pythoninterface/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summaryplotmanager/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/windowmanagement/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/cellresults/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/commandlineinterface/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/curvecalculator/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/eclipseproperties/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/geomechanicaldata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/memorymanagement/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summarysourcestepping/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/wellpaths/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/whats-new/releasenotes_2018_11/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/download-and-install/windows-installation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/helpmenuanddocumentation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/soursimrlresults/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/advancedtextinput/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/download-and-install/buildinstructions/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/download-and-install/build-instructions-ubuntu/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/commandfile/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/createnewwellpaths/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/elementpropertytable/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/fluxnummultnum/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/gridpropertycalculator/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/keyboardshortcuts/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/modelnavigation/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/observeddata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/pressuredata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/resultcolorlegend/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/resultinfo/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summaryploteditor/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/colorlegends/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/createmultilateralwellpaths/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/workflows/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/comparisonview/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/3dwelllogcurves/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/appendingadditionalproperties/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/completionexport/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/contourmaps/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/pasteexceltimedata/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/regressiontestsystem/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/other/releasenotification/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summarycrossplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summaryplottemplate/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/summarytables/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/multiplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/completions/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/ensemblefracturestatistics/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/ensembleplotting/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/flowvectorresult/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/import/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/octaveinterface/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/streamlines/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/tensors/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/exportwellpaths/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/objectivefunctions/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/analysisplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/gridstatisticsplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/correlationplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/completionslgr/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/octaveinterfacereference/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/resultinspection/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/sectormodel/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/other/testimonials/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/filters/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/scripting/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/welllogsandplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/wells-and-completions/wellmeasurements/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/declinecurveanalysis/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/intersections/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/misc/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/regressionanalysis/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/wellborestabilityplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/seismicsections/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/surfaces/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/allandiagrams/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/workflows/biotcoefficient/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/workflows/ensemblesurface/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/workflows/ensemblewelllog/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/faults/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/getting-started/other/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/rftplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/rftsegmentplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/export/contourmapexport/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/ensemblerftplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/formations/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/derivedresults/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/faultdistance/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/pltplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/vfpplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/depthplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/derivedresultsgeomech/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/flow-diagnostics-plots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/gridstatisticsdialog/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/flow-diagnostics-plots/producerinjectorconnectivitytable/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/flow-diagnostics-plots/wellallocationovertimeplot/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/casegroupsandstatistics/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/gridcrossplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/linkedviews/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/plot-window/saturationpressureplots/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/measurement/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/3d-main-window/annotations/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/_footer/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/_header/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/about/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/calculated-data/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/categories/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/search/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/support/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/tags/</loc>
-  </url>
-  
-  <url>
+  </url><url>
     <loc>https://resinsight.org/training/</loc>
   </url>
-  
-</urlset>
\ No newline at end of file
+</urlset>
diff --git a/support/index.html b/support/index.html
index eb74093bf5..63a30798c1 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Support :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4938,19 +4937,19 @@ e-mail : <a href="mailto:info@ceetronsolutions.com">info@ceetronsolutions.com</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/tags/index.html b/tags/index.html
index 76514968e5..d85028a61a 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Tags :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2788,6 +2787,8 @@ if (!doNotTrack) {
           
             <h1>
               
+                taxonomy ::
+              
               Tags
             </h1>
           
@@ -4925,19 +4926,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/tags/index.xml b/tags/index.xml
index b02605f875..e06b697eca 100644
--- a/tags/index.xml
+++ b/tags/index.xml
@@ -5,10 +5,6 @@
     <link>https://resinsight.org/tags/</link>
     <description>Recent content in Tags on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/tags/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/tags/index.xml" rel="self" type="application/rss+xml" />
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/training/index.html b/training/index.html
index 2285b085df..360a10d0f6 100644
--- a/training/index.html
+++ b/training/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Training Courses :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337812" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337812" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337812" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337812" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337812" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337812" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337812" rel="stylesheet">
+    <link href="/css/theme.css?1687337812" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337812" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337812"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4983,19 +4982,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337812"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337812"></script>
+    <script src="/js/jquery.sticky.js?1687337812"></script>
+    <script src="/js/featherlight.min.js?1687337812"></script>
+    <script src="/js/highlight.pack.js?1687337812"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337812"></script>
+    <script src="/js/learn.js?1687337812"></script>
+    <script src="/js/hugo-learn.js?1687337812"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337812" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337812"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/3dwelllogcurves/index.html b/wells-and-completions/3dwelllogcurves/index.html
index 710260c419..0789468d21 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>3D Well Log Plots :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5026,19 +5025,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/completions/index.html b/wells-and-completions/completions/index.html
index 8456feb866..0d270f3a31 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2848,7 +2847,7 @@ c.f. <a href="/export/completionexport/">Export Well Segments</a>.</p>
 <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="/calculated-data/derivedresults/#completion-type">Completion Type</a> 
+<p>A combined view of well connection factors and the derived result <a href="/calculated-data/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 occurred at.</p>
@@ -2926,7 +2925,7 @@ enables the user to see the completion type contributing to connection factor in
 <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>&ldquo;&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>
@@ -2966,7 +2965,7 @@ Each set of holes created at the same location along the main bore, is referred
 <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.</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>
@@ -2987,7 +2986,7 @@ For multi-segment wells there are additional parameters which should be set. The
 <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 1/2&rdquo; main bore.</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&quot; main bore.</p>
 <p><img src="/images/3d-main-window/Fishbones_SubDefPropEdit.png" alt=""></p>
 <ul>
 <li><strong>Appearance</strong>
@@ -3043,7 +3042,7 @@ For multi-segment wells there are additional parameters which should be set. The
 <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>*.dev*</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 <code><em>.dev</em></code> files.</p>
 </div>
 
 <h2 id="fractures">Fractures</h2>
@@ -5377,19 +5376,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/completionslgr/index.html b/wells-and-completions/completionslgr/index.html
index 0cc530370b..0848826339 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Completions LGR :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4971,19 +4970,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/createmultilateralwellpaths/index.html b/wells-and-completions/createmultilateralwellpaths/index.html
index 45fc2f20cf..339f21887c 100644
--- a/wells-and-completions/createmultilateralwellpaths/index.html
+++ b/wells-and-completions/createmultilateralwellpaths/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Create Multilaterals Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -5001,19 +5000,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/createnewwellpaths/index.html b/wells-and-completions/createnewwellpaths/index.html
index b968991db9..63d31cc51c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Create Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2893,15 +2892,15 @@ if (!doNotTrack) {
 </ol>
 <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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">-- 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     
-</code></pre></div>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>-- MDRKB          CL            Inc          Azi            TVDMSL         NS                EW               Dogleg      Build        Turn          
+</span></span><span style="display:flex;"><span>0.00000        0.00000       91.23218     67.46458       2560.64104     7320830.60875     456093.37763     0.00000     0.00000      0.00000       
+</span></span><span style="display:flex;"><span>109.69761      109.69761     91.23218     67.46458       2558.28210     7320872.64113     456194.67560     0.00000     0.00000      0.00000       
+</span></span><span style="display:flex;"><span>383.74602      274.04841     90.01335     94.84447       2555.24550     7320914.37090     456462.87518     3.00000     -0.13343     2.99727       
+</span></span><span style="display:flex;"><span>518.95310      135.20708     88.73259     106.92696      2556.73062     7320888.88803     456595.39303     2.69569     -0.28418     2.68089       
+</span></span><span style="display:flex;"><span>597.83872      78.88561      88.73259     106.92696      2558.47547     7320865.92593     456670.84259     0.00000     0.00000      0.00000       
+</span></span><span style="display:flex;"><span>730.04479      132.20607     90.46303     138.71821      2559.42803     7320795.18191     456780.51358     7.22424     0.39267      7.21402       
+</span></span><span style="display:flex;"><span>1087.97847     357.93368     92.23380     -164.19586     2550.23230     7320460.45997     456856.25443     4.78528     0.14842      -25.38856     
+</span></span></code></pre></div>
 
 <footer class="footline">
 	
@@ -5034,19 +5033,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/ensemblefracturestatistics/index.html b/wells-and-completions/ensemblefracturestatistics/index.html
index 1aae8dec73..e9433f03c2 100644
--- a/wells-and-completions/ensemblefracturestatistics/index.html
+++ b/wells-and-completions/ensemblefracturestatistics/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble Fracture Statistics :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2839,7 +2838,7 @@ if (!doNotTrack) {
 all the individual meshes in the ensemble.</p>
 <h3 id="adaptive-mesh">Adaptive Mesh</h3>
 <p>The adaptive mesh tries to optimize the horizontal depth spacing to have coarse sampling where the
-source meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of 
+source meshes are coarse, and fine sampling where necessary. This is achieved by grouping the layer thicknesses of
 the individual meshes into fixed bins, and then scaling the vertical size of each layer according to their mean size.</p>
 <ul>
 <li><strong>Mean Type</strong> &ndash; The mean calculation used to scale the layer thickness.
@@ -2873,7 +2872,7 @@ the individual meshes into fixed bins, and then scaling the vertical size of eac
 <p>The statistics mesh samples each individual fracture of the ensemble in each cell center. The value of the cell containing the
 statistics mesh cell center is used. Invalid values or empty cells are ignored. The values at each cell center are gathered, and
 the chosen statistics (e.g. P10 and Mean) is computed per cell.</p>
-<p>The statistics meshes are written to file in a StimPlan compatible XML file, and is imported into <strong>Fracture Templates</strong> in the 
+<p>The statistics meshes are written to file in a StimPlan compatible XML file, and is imported into <strong>Fracture Templates</strong> in the
 <strong>Project Tree</strong>.</p>
 <h2 id="statistics-table">Statistics Table</h2>
 <p>The statistics table contains overall statistics on key properties of the fractures.</p>
@@ -5019,19 +5018,19 @@ the chosen statistics (e.g. P10 and Mean) is computed per cell.</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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/index.html b/wells-and-completions/index.html
index 6425aceb1c..780dfdd815 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Wells and Completions :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -1597,7 +1597,7 @@
   
     
     <li data-nav-id="/wells-and-completions/" title="Wells and Completions" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4940,19 +4939,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/index.xml b/wells-and-completions/index.xml
index 1732b76115..d5198c73fa 100644
--- a/wells-and-completions/index.xml
+++ b/wells-and-completions/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/wells-and-completions/</link>
     <description>Recent content in Wells and Completions on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/wells-and-completions/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/wells-and-completions/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Simulation Wells</title>
       <link>https://resinsight.org/wells-and-completions/simulationwells/</link>
@@ -18,7 +14,7 @@
       <guid>https://resinsight.org/wells-and-completions/simulationwells/</guid>
       <description>This section describes how wells defined in the simulation are displayed, and how to control the different aspects of their visualization.
 Commands Several commands are available as right-click commands on a simulation well. These commands are available either by right-clicking the well in the 3D View or in the Project Tree.
- New Well Log Extraction Curve &amp;ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.</description>
+New Well Log Extraction Curve &amp;ndash; Creates a new Well Log curve based on the selected simulation well, the current time step and cell property.</description>
     </item>
     
     <item>
@@ -40,7 +36,7 @@ Ascii Well Paths The command File -&amp;gt; Import -&amp;gt; Well Data -&amp;gt;
       <guid>https://resinsight.org/wells-and-completions/createnewwellpaths/</guid>
       <description>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 imported well path.
 Building a multilateral well path
-Building a well path  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 should pass (well path targets) When finished placing targets, click on &amp;ldquo;Stop Picking Targets&amp;rdquo; in the property editor  Well targets property editor fields:</description>
+Building a well path 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 should pass (well path targets) When finished placing targets, click on &amp;ldquo;Stop Picking Targets&amp;rdquo; in the property editor Well targets property editor fields:</description>
     </item>
     
     <item>
@@ -50,7 +46,7 @@ Building a well path  Right click Wells in the project tree Select Create Well P
       
       <guid>https://resinsight.org/wells-and-completions/createmultilateralwellpaths/</guid>
       <description>ResInsight lets the user create additional well path laterals by clicking in the 3D view. Completions can be added to laterals, and the complete specification of the well can be exported using the Completion Export
-Building a well path  Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral  A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2.</description>
+Building a well path Start from an existing well path, either imported or create a new well path In the 3D view, right-click on the well path at the depth location for your lateral A new well path lateral is created, and click in the 3D scene to define targets for the lateral Repeat from 2.</description>
     </item>
     
     <item>
@@ -81,7 +77,7 @@ Completions can be modeled by adding new perforation intervals, fishbones subs o
       <guid>https://resinsight.org/wells-and-completions/ensemblefracturestatistics/</guid>
       <description>Importing Ensemble Fracture Statistics Right-click on Completion Templates &amp;gt; Ensemble Fracture Statistics in the Project Tree and select the Import StimPlan Fracture Recursively option. Then select the StimPlan fracture Xml files to be part of the ensemble.
 After importing the Property Panel of the Ensemble Fracture Statistics item has these options:
- Name &amp;ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures &amp;ndash; Toggle to remove zero width fractures from the statistics.</description>
+Name &amp;ndash; Name of the ensemble fracture statistics. Exclude Zero Width Fractures &amp;ndash; Toggle to remove zero width fractures from the statistics.</description>
     </item>
     
     <item>
@@ -93,7 +89,7 @@ After importing the Property Panel of the Ensemble Fracture Statistics item has
       <description>ResInsight supports creating and exporting LGRs (Local Grid Refinement) in main grid cells intersected by completions.
 Create Temporary LGRs To create temporary LGR(s), first select one or more well paths in the project tree, right click and select &amp;lsquo;Create Temporary LGR&amp;rsquo;. This command brings up the following dialog.
 The dialog contains several input fields
- Source Case &amp;ndash; The source case/grid Time Step &amp;ndash; The time step to use Fractures, Fishbones, Perforations &amp;ndash; Check boxes to control which completion types to create LGRs for Split Type &amp;ndash; Three options controlling how the LGRs will be created  LGR Per Cell &amp;ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion &amp;ndash; One LGR is created for each completion of the selected types.</description>
+Source Case &amp;ndash; The source case/grid Time Step &amp;ndash; The time step to use Fractures, Fishbones, Perforations &amp;ndash; Check boxes to control which completion types to create LGRs for Split Type &amp;ndash; Three options controlling how the LGRs will be created LGR Per Cell &amp;ndash; One LGR is created for each main grid cell intersected by completions of the selected type LGR Per Completion &amp;ndash; One LGR is created for each completion of the selected types.</description>
     </item>
     
     <item>
@@ -104,9 +100,8 @@ The dialog contains several input fields
       <guid>https://resinsight.org/wells-and-completions/wellmeasurements/</guid>
       <description>ResInsight can import well measurements from a comma-separated values file.
 Importing Well Measurements The command File -&amp;gt; Import -&amp;gt; Well Data -&amp;gt; Import Measurements will read well measurements from the selected files, and create one entry for each file under the Wells -&amp;gt; Well Measurements item in the Project Tree.
-File Format The format is comma-separated values with one measurement per line. The following requirements have to be met:
- Each data line must contain seven values: Well Name, MD, Date, Measurement Kind, Value, Quality, and Comment.</description>
+File Format The format is comma-separated values with one measurement per line. The following requirements have to be met:</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
diff --git a/wells-and-completions/simulationwells/index.html b/wells-and-completions/simulationwells/index.html
index 9c010af0ab..64415cd53c 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Simulation Wells :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2866,9 +2865,9 @@ allocation for the selected well. If the case has no Fluxes the well flow rates
 <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>Disks</strong> &ndash; Visualization of production and injection rates and cumulative production and injection with oil, gas, and water phases.</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. 
+<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>
@@ -2918,8 +2917,8 @@ Arrows representing communication in the opposite direction from what is expecte
 <h2 id="individual-simulation-well-options">Individual Simulation Well options</h2>
 <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><img src="/images/getting-started/msw_with_valves.png" alt=""></p>
@@ -5059,19 +5058,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/wellmeasurements/index.html b/wells-and-completions/wellmeasurements/index.html
index 3ecb66d584..1c05658e8d 100644
--- a/wells-and-completions/wellmeasurements/index.html
+++ b/wells-and-completions/wellmeasurements/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Measurements :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2836,17 +2835,17 @@ if (!doNotTrack) {
 <li>Blank lines are also ignored.</li>
 </ul>
 <h4 id="example-1">Example 1:</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-txt" data-lang="txt"># Example well measurements csv file.
-# This is a comment
-#
-# Well Name, MD, Date, Kind, Value, Quality, Comment
-C-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test
-C-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test
-C-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test
-C-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test
-E-3 H,  634.12, 2005-10-24, DP,    0.0, 0, Wash outs
-E-3 H, 1000.12, 2005-10-24, DP,    0.0, 0, Wash outs
-</code></pre></div><h3 id="measurement-properties">Measurement properties</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span># Example well measurements csv file.
+</span></span><span style="display:flex;"><span># This is a comment
+</span></span><span style="display:flex;"><span>#
+</span></span><span style="display:flex;"><span># Well Name, MD, Date, Kind, Value, Quality, Comment
+</span></span><span style="display:flex;"><span>C-3 H, 1465.18, 2001-10-13, XLOT, 1.76, 3, Good test
+</span></span><span style="display:flex;"><span>C-3 H, 1865.18, 2002-10-13, XLOT, 1.91, 1, Poor test
+</span></span><span style="display:flex;"><span>C-3 H, 1995.18, 2002-10-13, XLOT, 2.45, 1, Poor test
+</span></span><span style="display:flex;"><span>C-3 H, 2065.18, 2002-10-13, XLOT, 2.91, 1, Poor test
+</span></span><span style="display:flex;"><span>E-3 H,  634.12, 2005-10-24, DP,    0.0, 0, Wash outs
+</span></span><span style="display:flex;"><span>E-3 H, 1000.12, 2005-10-24, DP,    0.0, 0, Wash outs
+</span></span></code></pre></div><h3 id="measurement-properties">Measurement properties</h3>
 <ul>
 <li><strong>Well Name</strong> &ndash; The name of the well. ResInsight will try to associate each measurement with a well path with a matching name. The well name should be the same as imported <a href="/wells-and-completions/wellpaths/">here</a>.</li>
 <li><strong>MD</strong> &ndash; Measured depth.</li>
@@ -5008,19 +5007,19 @@ E-3 H, 1000.12, 2005-10-24, DP,    0.0, 0, Wash outs
     <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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/wells-and-completions/wellpaths/index.html b/wells-and-completions/wellpaths/index.html
index 4ec743aba7..aedebf94d4 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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Well Paths :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2825,7 +2824,7 @@ 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>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>
@@ -2839,42 +2838,42 @@ In addition, ResInsight is able to retrieve well paths from an Equinor internal
 <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 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;&lsquo;s, the complete 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 several consecutive name-like lines, only the last one will be used</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>
-<div class="highlight"><pre style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-txt" data-lang="txt">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
-</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-txt" data-lang="txt">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
-</code></pre></div><h3 id="well-path-files-are-referenced">Well Path Files are Referenced</h3>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>WELLNAME: WELL1
+</span></span><span style="display:flex;"><span>6507.1	725	2542	2590
+</span></span><span style="display:flex;"><span>6523.5	757	2549	2626.6
+</span></span><span style="display:flex;"><span>6523.5	760	2559	2637.1
+</span></span><span style="display:flex;"><span>-999
+</span></span><span style="display:flex;"><span>WELLNAME: WELL2
+</span></span><span style="display:flex;"><span>550.7 1020.2  2410   2410
+</span></span><span style="display:flex;"><span>551   1004.1  2422.2 2430.2
+</span></span><span style="display:flex;"><span>555.2  993.9  2425   2441.6
+</span></span><span style="display:flex;"><span>-999
+</span></span></code></pre></div><h4 id="example-2">Example 2:</h4>
+<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-txt" data-lang="txt"><span style="display:flex;"><span>X Y TVD(MSL) MD(RKB)
+</span></span><span style="display:flex;"><span>Name Well_1
+</span></span><span style="display:flex;"><span>6507.1	725	2542	2542
+</span></span><span style="display:flex;"><span>6523.5	757	2549	2578.6
+</span></span><span style="display:flex;"><span>6523.5	760	2559	2589.1
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>-- A Comment new well
+</span></span><span style="display:flex;"><span>This is not its name
+</span></span><span style="display:flex;"><span>Name Well_2
+</span></span><span style="display:flex;"><span>550.7	1020.2	2410	2520
+</span></span><span style="display:flex;"><span>551	1004.1	2422.2	2540.2
+</span></span><span style="display:flex;"><span># a comment inside the data 
+</span></span><span style="display:flex;"><span>555.2	993.9	2425	2551.6
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>3Q AHB-J
+</span></span><span style="display:flex;"><span>5507.0	4638.5	0.0	0.0
+</span></span><span style="display:flex;"><span>5507	4638.5	1628.6	1628.6
+</span></span></code></pre></div><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>
@@ -2918,7 +2917,7 @@ If you are an Equinor employee, make sure you have access to &ldquo;EDM Landmark
 </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>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>
@@ -5057,19 +5056,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/workflows/biotcoefficient/index.html b/workflows/biotcoefficient/index.html
index 299cba32e4..f83e8cbad3 100644
--- a/workflows/biotcoefficient/index.html
+++ b/workflows/biotcoefficient/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Biot Coefficient :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4964,19 +4963,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/workflows/ensemblesurface/index.html b/workflows/ensemblesurface/index.html
index 92c87fc872..f5ba9d2f1a 100644
--- a/workflows/ensemblesurface/index.html
+++ b/workflows/ensemblesurface/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble Surface :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2824,7 +2823,7 @@ if (!doNotTrack) {
 <img src="/images/workflows/create_ensemble_surface_menu.png" alt=""></p>
 </li>
 <li>
-<p>Select the ensemble grid models to create surfaces for, either <strong>&quot;*.EGRID&rdquo;</strong> or <strong>&quot;*.GRDECL&rdquo;</strong></p>
+<p>Select the ensemble grid models to create surfaces for, either <strong>&quot;*.EGRID&quot;</strong> or <strong>&quot;*.GRDECL&quot;</strong></p>
 </li>
 <li>
 <p>In the following dialog, select the K layers. Control if the generated surfaces should be imported into an ensemble surface immediately.
@@ -5013,19 +5012,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/workflows/ensemblewelllog/index.html b/workflows/ensemblewelllog/index.html
index 2773628c26..6198b1e98d 100644
--- a/workflows/ensemblewelllog/index.html
+++ b/workflows/ensemblewelllog/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Ensemble Well Log :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -2833,7 +2832,7 @@ if (!doNotTrack) {
 <p>Click <strong>OK</strong> when you are ready</p>
 <ul>
 <li>
-<p>A <strong>Well Log Plot</strong> is created in the <strong>Plot Window</strong> 
+<p>A <strong>Well Log Plot</strong> is created in the <strong>Plot Window</strong>
 <img src="/images/workflows/well_log_ensemble_plot.png" alt=""></p>
 </li>
 <li>
@@ -4979,19 +4978,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/workflows/index.html b/workflows/index.html
index 4c3d788d9d..16ed089e4f 100644
--- a/workflows/index.html
+++ b/workflows/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.68.0" />
+    <meta name="generator" content="Hugo 0.113.0">
     <meta name="description" content="">
 
 
@@ -12,18 +12,18 @@
     <title>Workflows :: ResInsight</title>
 
     
-    <link href="/css/nucleus.css?1687178621" rel="stylesheet">
-    <link href="/css/fontawesome-all.min.css?1687178621" rel="stylesheet">
-    <link href="/css/hybrid.css?1687178621" rel="stylesheet">
-    <link href="/css/featherlight.min.css?1687178621" rel="stylesheet">
-    <link href="/css/perfect-scrollbar.min.css?1687178621" rel="stylesheet">
-    <link href="/css/auto-complete.css?1687178621" rel="stylesheet">
-    <link href="/css/atom-one-dark-reasonable.css?1687178621" rel="stylesheet">
-    <link href="/css/theme.css?1687178621" rel="stylesheet">
-    <link href="/css/hugo-theme.css?1687178621" rel="stylesheet">
+    <link href="/css/nucleus.css?1687337813" rel="stylesheet">
+    <link href="/css/fontawesome-all.min.css?1687337813" rel="stylesheet">
+    <link href="/css/hybrid.css?1687337813" rel="stylesheet">
+    <link href="/css/featherlight.min.css?1687337813" rel="stylesheet">
+    <link href="/css/perfect-scrollbar.min.css?1687337813" rel="stylesheet">
+    <link href="/css/auto-complete.css?1687337813" rel="stylesheet">
+    <link href="/css/atom-one-dark-reasonable.css?1687337813" rel="stylesheet">
+    <link href="/css/theme.css?1687337813" rel="stylesheet">
+    <link href="/css/hugo-theme.css?1687337813" rel="stylesheet">
     
 
-    <script src="/js/jquery-3.3.1.min.js?1687178621"></script>
+    <script src="/js/jquery-3.3.1.min.js?1687337813"></script>
 
     <style>
       :root #header + #content > #left > #rlblock_left{
@@ -1508,7 +1508,7 @@
   
     
     <li data-nav-id="/workflows/" title="Workflows" class="dd-item 
-        parent
+        
         active
         
         ">
@@ -2713,19 +2713,18 @@ ResInsight is developed by <br> <a href="https://www.ceetronsolutions.com">Ceetr
 <a href="https://www.equinor.com">Equinor ASA</a>
 
 
-<script type="application/javascript">
+<script async src="https://www.googletagmanager.com/gtag/js?id=G-6BNMNQQY0H"></script>
+<script>
 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', 'G-6BNMNQQY0H', 'auto');
-	
-	ga('send', 'pageview');
+	window.dataLayer = window.dataLayer || [];
+	function gtag(){dataLayer.push(arguments);}
+	gtag('js', new Date());
+	gtag('config', 'G-6BNMNQQY0H', { 'anonymize_ip': false });
 }
 </script>
 
+      
     </section>
   </div>
 </nav>
@@ -4931,19 +4930,19 @@ 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?1687178621"></script>
-    <script src="/js/perfect-scrollbar.min.js?1687178621"></script>
-    <script src="/js/perfect-scrollbar.jquery.min.js?1687178621"></script>
-    <script src="/js/jquery.sticky.js?1687178621"></script>
-    <script src="/js/featherlight.min.js?1687178621"></script>
-    <script src="/js/highlight.pack.js?1687178621"></script>
+    <script src="/js/clipboard.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.min.js?1687337813"></script>
+    <script src="/js/perfect-scrollbar.jquery.min.js?1687337813"></script>
+    <script src="/js/jquery.sticky.js?1687337813"></script>
+    <script src="/js/featherlight.min.js?1687337813"></script>
+    <script src="/js/highlight.pack.js?1687337813"></script>
     <script>hljs.initHighlightingOnLoad();</script>
-    <script src="/js/modernizr.custom-3.6.0.js?1687178621"></script>
-    <script src="/js/learn.js?1687178621"></script>
-    <script src="/js/hugo-learn.js?1687178621"></script>
+    <script src="/js/modernizr.custom-3.6.0.js?1687337813"></script>
+    <script src="/js/learn.js?1687337813"></script>
+    <script src="/js/hugo-learn.js?1687337813"></script>
 
-    <link href="/mermaid/mermaid.css?1687178621" rel="stylesheet" />
-    <script src="/mermaid/mermaid.js?1687178621"></script>
+    <link href="/mermaid/mermaid.css?1687337813" rel="stylesheet" />
+    <script src="/mermaid/mermaid.js?1687337813"></script>
     <script>
         mermaid.initialize({ startOnLoad: true });
     </script>
diff --git a/workflows/index.xml b/workflows/index.xml
index 0b34b6f2a2..fbd0f15add 100644
--- a/workflows/index.xml
+++ b/workflows/index.xml
@@ -5,11 +5,7 @@
     <link>https://resinsight.org/workflows/</link>
     <description>Recent content in Workflows on ResInsight</description>
     <generator>Hugo -- gohugo.io</generator>
-    <language>en-us</language>
-    
-	<atom:link href="https://resinsight.org/workflows/index.xml" rel="self" type="application/rss+xml" />
-    
-    
+    <language>en-us</language><atom:link href="https://resinsight.org/workflows/index.xml" rel="self" type="application/rss+xml" />
     <item>
       <title>Biot Coefficient</title>
       <link>https://resinsight.org/workflows/biotcoefficient/</link>
@@ -19,7 +15,7 @@
       <description>Background
 The Biot porelastic coefficient defines the compressibility of sand grains, and will influence some of the calculations in ResInsight.
 Description The Biot coefficient can be defined in three ways:
- Default (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table  These settings are controlled from the Property Editor when a Geomechanical Case is selected.</description>
+Default (Constant value of 1.0) User defined constant for all element One value for each element based on imported values from an element property table These settings are controlled from the Property Editor when a Geomechanical Case is selected. To use Biot coefficients for each element, perform the following steps:</description>
     </item>
     
     <item>
@@ -29,7 +25,7 @@ Description The Biot coefficient can be defined in three ways:
       
       <guid>https://resinsight.org/workflows/ensemblesurface/</guid>
       <description>Introduction To study the structural uncertainty, ResInsight enables the user to create and import an ensemble of surfaces and compute the statistical surfaces based on this ensemble. This page describes the interactive workflow, but in many cases it can be useful to create scripts related to mangement of Ensemble Surfaces. See Python Examples for more details.
-Create Ensemble Surface   From the right-click menu of surfaces, select Import Ensemble Surface   Select the ensemble grid models to create surfaces for, either &amp;quot;*.</description>
+Create Ensemble Surface From the right-click menu of surfaces, select Import Ensemble Surface Select the ensemble grid models to create surfaces for, either &amp;quot;*.</description>
     </item>
     
     <item>
@@ -39,8 +35,8 @@ Create Ensemble Surface   From the right-click menu of surfaces, select Import E
       
       <guid>https://resinsight.org/workflows/ensemblewelllog/</guid>
       <description>Introduction To study the uncertainty for well log extraction curves, ResInsight enables the user to import an ensemble of well logs and compute the statistical distribution in this ensemble.
-Workflow   From the right-click menu of Wells, select Create Ensemble Well Log   In the ensemble import dialog, select the files for import into ensembles   Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files   Click OK when you are ready</description>
+Workflow From the right-click menu of Wells, select Create Ensemble Well Log In the ensemble import dialog, select the files for import into ensembles Select well path and properties for export, select time step for dynamic properties, and use the checkbox to control if you want to create a well log ensemble based on the exported well log files Click OK when you are ready</description>
     </item>
     
   </channel>
-</rss>
\ No newline at end of file
+</rss>
