LEAPFROG GEOTHERMAL 3.4

Transcription

1 LEAPFROG GEOTHERMAL LEAPFROG GEOTHERMAL 3.4 Technical Release Notes This document outlines the major features and improvements in Leapfrog Geothermal 3.4 Document Version 1

2 LEAPFROG GEOTHERMAL 3.4 New Features 2 Convert Leapfrog Geo projects to Geothermal 2 TOUGH2 geometry grid export 2 TOUGH2, not Tough2 2 Grid Block order when exporting to a TOUGH2.dat file 2 Grid Block centroid coordinates exported to a TOUGH2.dat file 3 Importing AUTOUGH2.dat files containing SHORT data 3 Displaying time-dependent data imported from a TOUGH2 listing file 3 Isosurfacing geophysical data 3 Importing Magnetotelluric Resistivity Models 4 Geophysical point import/export in.csv only 5 Assign selected intervals to the base lithology 5 Filtered wells and points for distance functions 5 Evaluations can now use section extents 6 Evaluations on sections 6 Evaluate wells onto fence sections 7 Distance filtering 9 Updating fence sections 9 Copying fence section layouts with well evaluations 9 Batch export of section layouts relocated 10 Sill renamed to Total Sill in RBF interpolants 10 Identify mesh parts in the scene 10 Leapfrog Central UI updates 11 Projects organised by Location 12 Local copy tiles 12 Drilling comparison in Leapfrog Browser 13 Group projects by location in Leapfrog Browser 15 Local project display 16 Issues addressed 17 Upgrade notes 18 Project upgrades bit architectures 18 System Requirements 19 1

3 New Features Convert Leapfrog Geo projects to Geothermal It is now possible to convert Leapfrog Geo projects for use in Leapfrog Geothermal. Unconverted Leapfrog Geo projects are highlighted in the Projects tab: The process is one-way; projects converted into Leapfrog Geothermal projects can no longer be opened in Leapfrog Geo. It is recommended that you backup the Geo project before converting it for use in Geothermal. TOUGH2 geometry grid export Previous versions of Geothermal have not been able to export the TOUGH2 geometry file (also known as a Mulgrid geometry file). Geothermal 3.4 now exports two files when exporting a TOUGH2 model: The *.DAT file is the TOUGH2 input file. The *_geometry.dat file is the grid definition file. The geometry file can then be imported into Geothermal, along with the.listing file from TOUGH2. For a description of the geometry file format, users should see the PyTOUGH documentation. TOUGH2, not Tough2 All references to Tough2 have been change to TOUGH2 in Geothermal 3.4 as TOUGH is an acronym for Transport Of Unsaturated Groundwater and Heat. 2

4 Grid Block order when exporting to a TOUGH2.dat file When a TOUGH2 model is exported to a.dat file, the grid block data are now written out in a layer-bylayer order in the ELEME section. Previously (Geothermal 3.3 and earlier) grid blocks were written out in a column order. Grid Block centroid coordinates exported to a TOUGH2.dat file The grid block definitions in the ELEME keyword in the TOUGH2.dat file include the x,y,z of the grid block centroid. Only 10 characters are available for each of the x,y,z values. The format previously used meant that large x and y values, for example, those specified in UTM coordinates, could be rounded up or down with the difference between the rounded value and the true value being greater than the grid block size in X or Y. Grid block centroid x,y,z values are now written in a format that avoids these rounding errors. Importing AUTOUGH2.dat files containing SHORT data AUTOUGH2 is the Geothermal Institute s version of TOUGH2. AUTOUGH2 and TOUGH2 input files are almost completely compatible. However, AUTOUGH2 supports an optional SHORT section towards the end of the input.dat file in which a selection of block, connection and/or generators can be specified to have additional output information written to the listing file by the simulation run. In Geothermal 3.4, an input.dat files containing a SHORT section can now be imported. Any data found after the SHORT keyword are ignored. Note that the standard Berkeley Labs version of TOUGH2 does not support short output. Displaying time-dependent data imported from a TOUGH2 listing file Time-dependent data such as pressure or temperature that has been imported into Leapfrog Geothermal from a TOUGH2 listing file will now be displayed with the correct default minimum/maximum value range. Previously the range defaulted to [0.0,1.0], which for data such as pressure or temperature typically resulted in the grid being displayed in a single colour. The user would then need to open up the Edit Colourmaps dialog and reset the minimum and maximum values. Isosurfacing geophysical data Whereas RBF interpolants are suited to irregularly-spaced sparse data, they cannot be used to isosurface gridded geophysical data. A new type of interpolant has been introduced to Leapfrog Geothermal, the inverse distance weighted (IDW) grid interpolant. An IDW grid interpolant can be created from gridded geophysical data such as Magnetotelluric Resistivity models, UBC grids and Gocad models. Note that magnetotelluric models imported into Leapfrog Geothermal version 3.3 and earlier cannot be used to generate an IDW interpolant and will need to be reimported. Create an IDW interpolant by right-clicking on the Numeric Models folder and selecting New IDW Grid Interpolant. The process is similar but simpler to setting up an RBF interpolant; the values selected cannot be changed once the interpolant has been created, but all other parameters can be adjusted. 3

5 The Exponent setting adjusts the strength of the weighting as distance increases. A higher exponent will result in a weaker weight for the same distance. Importing Magnetotelluric Resistivity Models The menu option in the Geophysical Data folder has been changed to reflect the type of data being imported rather than the type of file. Similar naming changes have been made to the associated dialogs. Applying a threshold is now enabled by default. 4

6 Geophysical point import/export in.csv only The only import/export option available for geophysical point data in the Geophysical Data folder is.csv. Points in.asc,.dxf,.pl3 and.ara formats should be imported into the Points folder. Assign selected intervals to the base lithology When selecting intervals, it is now possible to assign intervals to existing category codes: Previously it was only possible to assign intervals to user-defined codes. 5

7 Filtered wells and points for distance functions When distance functions are created from wells, points, geophysical points, GIS points and imported GIS lines, it is now possible to filter the object used with any query filter defined for that object. Evaluations can now use section extents Previously when evaluating a model on a section there was no option to limit the extents to that of the section, vs. those of the evaluation (layouts had the option of section or evaluation extents but not the section itself). Evaluations on sections When evaluating models or surfaces onto a cross section or serial section an option has been added to allow the evaluation to be limited to the section extents. In the Select Model/Surface to Evaluate dialog a checkbox to Clip evaluations to section extents is available and is selected by default. 6

8 Evaluate wells onto fence sections Wells can now be evaluated onto fence sections. When evaluating wells onto curved sections a projection is made based on the locations of neighbouring segments of the fence section. This is done by using the bisectors of the angles between each segment and its neighbour. These determine the projection point of origin for a given segment of the section. 7

9 If the projection origin for a segment of the section is within the distance filter a dead area occurs relative to that segment. Any portion of a well that falls within the dead area will not be evaluated onto that segment. It may well occur that the well is evaluated on a neighbouring segment. On the inside of a tight corner a single well may be projected multiple times onto the section. Each instance will appear in the well list for evaluation and individual instances can be turned off. 8

10 Distance filtering The filter by minimum distance to section plane uses the distance at 90 degrees from the section. For well segments that are just within this 90 degree distance filter, some may report minimum distances greater than the filter setting when evaluated because the evaluation distance is relative to the projection origin. Updating fence sections If fence sections with a well evaluation are updated and the evaluation location changes as a result then we apply the following rules If all instances of a well evaluation are checked on, then we leave all instances checked on If all instances of a well evaluation are unchecked, then we leave all instances unchecked If only some instances of a well evaluation are checked on, then we revert to having all instances checked on Copying fence section layouts with well evaluations When copying layouts to another section from a fence section, the well evaluation will not be copied and would have to be reapplied. 9

11 Batch export of section layouts relocated Batch export of section layouts was introduced in the last release to make it easier to export large numbers of section layouts from serial sections and alignment serial sections; right-clicking on a serial or alignment section made it possible to export some or all of the section layouts for that section. Batch Export Layouts has been moved to the Cross Sections and Contours folder. This means it is cross section layouts can be exported from all sections in the project at once, rather than having to export layouts from individual sections. Sill renamed to Total Sill in RBF interpolants The Sill parameter in RBF interpolants is technically the total sill. For clarity, this parameter has been renamed to Total Sill. Identify mesh parts in the scene When exporting a mesh that has multiple parts, distinguishing between the different parts that can be exported has previously been a case of trial and error. When exporting a single mesh, it is now possible to identify in the scene what parts of a mesh correspond to the select part in the Export Mesh Parts window. Here, the mesh was added to the scene before opening the Export Mesh Parts window. Clicking on a mesh part in the list selects that part in the scene: 10

12 If the mesh is not in the scene when the Export Mesh Parts window is opened, selecting a part in the list will display it in the scene without reference to the other parts of the mesh. Use the Shift and Ctrl keys to select and view multiple mesh parts in the scene: 11

13 Leapfrog Central UI updates Projects organised by Location When browsing projects on the central projects tab, project are now grouped by Location tags. The location tags are set in the admin portal for a given central server. Local copy tiles When viewing a central project all local copies are now displayed in a Local copies group as a tile. The local copy tile shows a thumbnail with status, a link to the history tree and options to delete or publish to make browsing projects more intuitive. 12

14 Drilling comparison in Leapfrog Browser A new workflow has been introduced to Leapfrog Browser that allows users to compare objects across revisions. To do this, first add the objects you wish to compare to the scene view. For example, you may want to compare drilling data and a surface. Next, click the Compare button: The Compare tab will open. It has two dropdown lists that let you select the versions to compare, along with controls that give you different options for comparing the data objects: 13

15 Double-click on a version to select it. Once you have selected two versions, there will be additional sets of controls for the objects displayed: Use the controls for each object to change its display as you normally would. The controls next to each pair of objects provide different ways of comparing objects: 14

16 The red and green arrows control switches between the display of the two revisions for each object. So clicking the red and green arrows displays first one version, then the other. This is useful for getting a feel for how each version has changed before using the cog to do further comparisons. To display both versions again, click the eye next to the hidden version. How the cog control works depends on the type of object displayed and is not available for some types of objects. If a mesh is displayed, Default settings applies a default set of visibility controls that allows you easily compare two versions of the mesh. One version will be set to display using triangles and the other version to faces. Inverted settings simply swaps these settings. If, however, wells are displayed, the cog control gives you a Fancy wells option that displays the wells at different widths and transparencies. Select Default from the cog turns off Fancy wells. Group projects by location in Leapfrog Browser When an organisations has a large number of Leapfrog Central projects, Leapfrog Browser users may find it difficult to find the project they want. Leapfrog Browser now organises projects by location: 15

17 Projects are automatically grouped in this way, using the project s Location tag in the Admin Portal s Projects tab: Local project display Changes have been made to how local copies of Leapfrog Central projects are displayed in Leapfrog Geothermal. These changes make it easier to determine versions for which local copies have been downloaded. The first change is that there is a new Local copies panel in the project tab. The buttons for each project allow you to: Open the local copy of the project Publish the project to Leapfrog Central, if the project is already open Identify the parent version of the local copy Delete the local copy, if the project is not open The arrangement of these controls may change in a future beta, but this prototype version allows you to experiment with this new way of managing local copies. 16

18 Each local copy is numbered so that it can easily be seen what versions have local copies in the new Local column: The number in the column corresponds to the project in the Local copies panel. 17

19 Issues addressed The following improvements have been made in this release. Well import performance is improved Text columns can now be used in merged tables An issue where some Help button links were broken has been addressed An issue where isosurfacing would fail to complete in some corner cases has been addressed An issue where the mesh backface visibility is incorrect has been addressed An error when reloading or appending wells while a query filter is applied has been addressed An error when deleting the well database in some circumstances has been addressed An error when selecting the trench option in some circumstances has been addressed Upgrade notes Project upgrades Leapfrog Geothermal v3.4 is backwards compatible and supports direct project upgrades from any version of Leapfrog Geothermal since version 2.6. Projects built in earlier versions of the software must be opened using Leapfrog Geothermal v2.6 prior to being opened with v3.4. Backdated versions of the software are available at leapfrog3d.com. 32-bit architectures 32-bit architectures are no longer supported in Leapfrog Geothermal v3.4. All existing 32-bit version users will either need to continue using the previous version, Leapfrog Geothermal v3.4 or upgrade to a 64-bit operating system. 18

20 System Requirements Operating System 1,2 Processor, Supported Windows 7 (64bit) Windows 8 (64bit) Windows 8.1 (64bit) Windows 10 (64bit) Intel Core TM i3,i5 or i7 CPU (2nd generation or later) Intel Xeon TM Recommended Windows 7 (64bit) Windows 8.1 (64bit) Windows 10 (64bit) Intel Core TM i7-6800k Intel Core TM i7-6900k Intel Core TM i Intel Xeon TM E v3 Memory System Free hard disk space Display resolution Graphics 8 4 GB (Minimum) 32 GB RAM Legacy spinning hard disk 250 GB capacity 25 GB free space 1280 x 720 (Minimum) Single display unit Nvidia TM (Desktop hardware) GeForce 700 series 3 GeForce 900 series 3 GeForce 1000 series 3 Quadro 600 series and above Quadro K series 3 Quadro P series 3 Solid state disk drive 1 TB capacity 100 GB free space 2560 x 1440 or better Multiple display setup GeForce GTX 950i 7 GeForce GTX 1050Ti 7 GeForce GTX Nvidia TM (Mobile hardware) GeForce 700M series 3 GeForce 800M series 3 GeForce 900M series 3 GeForce 1000 series 3 Quadro M series 3 Quadro P mobile series GeForce GTX 950M 7 GeForce GTX AMD TM / ATI TM (Desktop hardware) Radeon HD 8000 series 3 Radeon R5 series 3 Radeon R7 series 3 Radeon R9 series 3 Radeon RX series 3 Firepro V series 3 Firepro W series 3 AMD TM / ATI TM (Mobile hardware) Radeon HD 8000 series 3 Radeon R5 series Radeon R7 series Radeon R9 series Radeon RX series Radeon RX Radeon RX Radeon R9 M375 7 Radeon RX FirePro M series Intel TM Integrated Graphics HD Graphics ( Generation 2 or later)l HD Graphics 510 (Generation 6 or later) Notes: 1 Running Leapfrog in virtualised environment is not supported 2 Running Leapfrog via a remote desktop connection or other remote login system is not supported 3 Hardware configuration must include 512MB Video RAM or greater 4 Must be 2nd generation Intel R Core TM i3, i5 or i7 CPU with 512MB Video RAM or greater 5 Must be 3rd generation Intel R Core TM i3, i5 or i7 CPU with 512MB Video RAM or greater 6 Must be 4th generation Intel R Core TM i3, i5 or i7 CPU with 512MB Video RAM or greater 7 Models with peak processing power greater than 600GFLOPS are recommended 8 Touch-screen hardware is not supported 19