All Activity

I found the answer to my question in the RockWare video "Creating a Water Level Grid." So no need for any member response.

I'm a neophyte user of RockWorks, employing it for a groundwater assessment. At the moment I'm trying, and failing, to create a map showing about 35 boreholes and the water-table elevations in each, as well as simple interpreted water-table contour lines. I've explored several approaches to create this map but have come up empty. Could someone please suggest at least some initial steps with the software?

An updated version of LogPlot has been loaded to the RockWare website! Improvements: Macro for Date in Static Text is now saved as the current date in the Compiled LogView file. When opening a LogPlot project folder, the user will be prompted to use it if an existing Keyword/Pattern file is in the folder. Bug Fix: Resample a depth column for point or interval data, now behaves as expected. You can refer to the complete LogPlot revision list: https://www.rockware.com/support/logplot-support/logplot-revision-list/ To download this build visit the LogPlot Free Trial tab (https://www.rockware.com/product/logplot/) where you can download the installation program and install the new build. Note that the software will not be automatically licensed if your maintenance has expired before April 2025, so the software will be installed in trial mode. If you would like to renew your maintenance, contact RockWare Sales. Katy Duncan RockWare Inc

Hi Alison, Nailed it. As always, thank you very much! Jack

To me, it looks like you've turned on the Baseplate option during model creation with an elevation of 0. If its convenient for you to recreate your model, you could make the adjustment for the baseplate to be at an elevation of 800. If its not convenient for you to overwrite the entire model, you could recreate the "base" RwGrd file of the lower unit using the Grid | Create | Single Elevation/Dip -> Grid tool. You would just want to overwrite that grid with a Horizontal grid at an elevation of 800. If you continue to have problems, feel free to contact us at tech@rockware.com. Thanks, Alison

Dumb question that I cannot seem to overcome. I'm creating a model-based stratigraphy section but want to limit the y-axis minimum to 800 ft. No matter what settings I try, the output cross section has a y-axis minimum of 0 ft (see attached): z-scale Spatial Filter; Elevation Range in the Annotation menu; editing the Dimensions to set the Z-values. The boreholes don't have any "deep" data to explain it, although there appear to be oddly deep perimeter/outlines to the boreholes in the cross section. The vertical-axis issue persists even when I change boreholes. Any ideas? Thanks for the help.

Hello Customers, Some of you may have seen a notice today about a RockWorks release this week. We have decided to push this back a couple of days for further testing and appreciate your patience. We will get the new version posted as soon as it's ready. Regards, The RockWare Team

A new version of RockWorks was uploaded to the RockWare website with new features, improvements, and bug fixes. The RockWorks Revision History includes complete lists, by date, of all changes in the program. New Features: Borehole Manager | Edit | Update Symbols - Can now update either or both Raster and Vector symbols and other options. "Hydrostratigraphy" has been renamed to "HydroStrat" within the 3D Log Designer. We've added an option to define project dimensions or subsite dimensions from a polygon that is already saved to the polygon table. The polygon table dialog allows importing from another project from a datasheet or a text file. The Vertical Separation and Thickness Cutoff options within the Layered Stratigraphy Model / Diagram sub-menus now show the vertical project units so the user knows what these numbers represent. The user may now import dimensions from a TIFF file without elevation data, as long as the file contains georeferencing data. Improvements: You can now save Peripherals and other sub-menus in Playlists. The Maximize button within the upper-right corner of RockWorks windows is more consistent when toggling between the maximized state and the previous non-maximized state. It is now much easier to resize RockWorks forms because the margins surrounding them have increased. Dragging the edges and corners of RockWorks forms has been significantly improved. The form contents are no longer redisplayed as the mouse is moved. Instead, a faint outline is displayed during the dragging process to show the new dimensions, and the form is re-displayed when the mouse button is released. This eliminates the flicker and the sluggish response. There are improvements to the RockPlot 3D | Wavefront Obj Export for better viewing in external programs. The top of the legends is now calculated similarly for Color, Stratigraphy, and Lithology legends. Bug Fixes: The Borehole Operations / Stratigraphy / 2D Isopach Map / 2D Grid Map / Peripherals / Color Legend no longer lists negative numbers if the Truncate Base option is enabled and the superface grid extends below the subface grid. Changed saving the Wavefront Obj Export file to use the low-level file writing and avoid an integer overflow. RockPlot3D diagrams with legends will export to Sketchfab (OBJ file) and show the legend as intended. The Lateral Blending algorithm no longer omits the interpolations within the upper portion of the model if the Warping option is enabled. The RockPlot2D / File / Export / DXF / Output menu no longer refers to KMZ files. Instead, it now correctly refers to DXF files. Added a "Color" tab to the Utilities | Planes | XYZ & Dips to Profile menu. The program was using the values from this tab without displaying it. Labels for 2D Striplogs were incorrectly plotted when the "Omit Columns with No Data" option was set. BorePlot was changing the downhole calculations to Unwind, overriding the "Plot Vertical"/"Plot using True Vertical Depth" in "2D Striplog Section" | "Striplogs" | "Projection" The Playlist / Add / Set Project Dimensions option now adds the "Set Project Dimensions" title to the Playlist. The previous version would only add the dimensions icon. To download this software build, use the Help | Updates | Check for Updates menu inside RockWorks. Or visit our website and click on the RockWorks Free Trial tab: https://www.rockware.com/product/rockworks/ You can download the installation program and install the new build right over the top of the existing program. (DO NOT uninstall first.) Note that you cannot use this new program build if your maintenance has expired before April 2025. Contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer/) if you would like to update your maintenance. Katy Duncan RockWare Inc

Maciej, I think you may need to send an email directly to the TOUGHREACT developers about this. I am not sure that the chemical reactions are fully coupled with the flow and transport portion for TOUGHREACT EOS5. PetraSim does not currently support EOS5 for TOUGHREACT v4.13, but we would be happy to help you come up with a work flow using a different EOS module (probably EOS3) if you decide to move forward with using it. You can contact me directly about this at alison@rockware.com. Best Regards, Alison

Hello All, Is TOUGHREACT / EOS5 able to simulate the process of serpentization that can lead to the production of natural hydrogen? I know that EOS5 is intended for transporting hydrogen in the aquatic environment, but I wonder if it is possible to simulate hydrogen generation in situ. Kind regards, Maciej P.S. I also posted the same question on the TOUGH forum, but it only had a few views, so I hope I'll get an answer here

A new version of RockWorks was uploaded to the RockWare website with new features, improvements, and bug fixes. The RockWorks Revision History includes complete lists, by date, of all changes in the program. New Feature: When editing Playlist items, if a duplicate item is created because the user changed a variable, duplicate playlist items will be deleted. Improvements: The Scattergram menu from the Utilities / Stats / Scattergram program has been redesigned to accept dates for the x-axis. The Undefined sub-menu settings within the solid-modeling Special Options sub-menu now accept a user-defined value. Added a warning when loading a Project Image that the World file and Manual coordinates must match the Project's Coordinate Reference System. Bug Fixes: Normalizing the P-Data no longer generates an error if a null or zero value is encountered in the chosen data type. RockPlot3D files that contain cutouts will show when loaded into RockPlot3D instead of failing to load. Fixed the function that appends the Project folder to a filename if no folder is specified (i.e. when only a filename is provided). This problem affected loading various file types, including XY data files, RwDat files, XY pair files, and profile data. It also occurred when importing files (Text or Excel) from a playlist. To download this software build, use the Help | Updates | Check for Updates menu inside RockWorks. Or visit our website and click on the RockWorks Free Trial tab: https://www.rockware.com/product/rockworks/ you can download the installation program and install the new build right over the top of the existing program. (DO NOT uninstall first.) Note that you cannot use this new program build if your maintenance has expired before January 2025. Contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer/) if you would like to update your maintenance. Katy Duncan RockWare Inc

Is it possible to export the T-Data or P-Data to a text file with an additional column for the corresponding stratigraphy, so that each T-Data or P-Data log value has its corresponding stratigraphy listed next to it?

I am glad it was an easy fix! Please don't hesitate to reach out if you run into any other issues.

Hi Paul, I'm very embarrassed to admit it but it was an issue with a sneaky superface that was restricting the elevation past a point that I hadn't even realized was enabled. Thank you for the reminder as to what it could be though! You really helped me get past this silly block that had been standing in the way of a project for longer than I'd care to admit.

Good afternoon Kali, It looks like there is an upper constraining surface that is stopping your Lithology data from extrapolating any higher than what it is currently set to. For your Lithologic model are you currently using a Superface to constrain the model, or do you have any of the Spatial Filters turned on that would limit the upper bounds of the model? If you would like to zip up your project and send it to us at tech@rockware.com we would be happy to look at it as well.

I'm currently working with some soil data and I've opted to construct a section to show off the lithology underneath the surface. The problem is that the data that was collected from the boreholes does not extrapolate higher than the lowest borehole in the section. This is a problem when we want to include something like a surface profile, as the areas between the tops of the lower elevation boreholes and higher ones simply does not fill in, not even as a block which could then be trimmed by using a surface profile. Is there some setting that I'm missing here to allow it to do this? Is it that the lithologic data doesn't line up quite right, or is there something else that I'm missing entirely here. Any help would be very appreciated!

A new version of RockWorks was uploaded to the RockWare website, with new features, improvements, and bug fixes. The RockWorks Revision History includes complete lists, by date, of all changes in the program. New Features: A new program titled "Solid Evaluation" has been added for quantifying the "goodness-of-fit" for an interpolated solid model. The new program generates a report with diagrams that depict the accuracy of a solid (block) model relative to the original control points that were used to interpolate the voxel values. Import RockWare's AqQA data file (*.aqq) into the Utilities Datasheet. File | Import | Aq•QA Point-source stochastic flow path simulation program added to RockWorks. ModOps | Grid | Set Grid Fault flag - Takes an input and output RwGrd file name and the program simply checks on/off the Fault flag for the output file. A new program titled "Grid Evaluation" has been added for quantifying the "goodness-of-fit" for an interpolated grid model. It generates a report with diagrams that depict the accuracy of a grid model relative to the original control points used to interpolate the grid values. RockWorks can create a map featuring rose diagrams that depict wind directions at one or more data collection sites. Select the Wind Roses program from the Utilities / Maps pull-down menu. The radii of the petals are proportional to the relative percentages, while the color of the petal bands represents the wind speed. Improvements: The Borehole Manager / Fractures / Stereonet and Stereonet Map programs now provide a means to adjust the great circle color and thickness. RockWorks no longer attempts to use the Window Media Player. The Row-Based (formerly called Multi-Table) Import to the Borehole Manager for both Excel and Text imports can be added to a Playlist and edited from a Playlist. When you rename a file in the Project Manager, it will be sorted alphabetically within the list of files, rather than appearing at the bottom of the list for its file type. The Flow Path (Drainage Net) Map, 3D Flow Diagram, Flow Table, and Upgradient Drainage Area programs within the Utilities / Hydrology menu group have been revamped and updated to compute quicker. Added the option to export a PRJ file from RockWorks that could be used to set the projection in Global Mapper or other GIS programs. Improved the Filter | Remove Disabled Rows tool so that after you select this filter it will result in a smaller file, as one would expect. Maps | Point Symbols - Map Overlays now include the option to plot Boreholes. Bug Fixes: The grid smoothing "size" and "passes" settings are no longer reversed within the modeling code. The Prefix and Suffix settings for the southern label within a radially-labeled point map are no longer reversed. The raster exports (e.g., BMP, JPG, PNG , & PDF) within the RockPlot3D / File / Export menu no longer swap the reds and blues when configured to use the hardware (graphics card) OpenGL driver. The Borehole Operations / I-Data / Section / Hole-to-Hole Interpolation and Projected Section programs no longer skip boreholes with just one I-Data value. This makes the program more useful for scenarios where a single sample represents the geochemistry within a screened interval. To download this software build, use the Help | Updates | Check for Updates menu inside RockWorks. Or visit our website and click on the RockWorks Free Trial tab: https://www.rockware.com/product/rockworks/ where you can download the installation program and install the new build right over the top of the existing program. (DO NOT uninstall first.) Note that you will not be able to use this new build of the program if your maintenance has expired before December 2024. Contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer/) if you would like to update your maintenance. Katy Duncan RockWare Inc

Good morning! Using the samples database I was unable to replicate the error messages that you were running into. When you are going through the work flow of importing your data are all of your bitmaps stored within the RockWorks project folder and not under any sort of subfolders? Below is a screenshot from the Bitmap excel tab of how to format your data prior to importing it into RockWorks. Under the Filename column you can see that it is referencing the image name as it is assumed that all of the images are already in the RockWorks project folder. This may be an issue given file size, but if you would like to zip up your project folder and send it to tech@rockware.com, or provide your excel import table with a few of the bitmap images you are working with we can try to recreate this on our end using your data.

When importing boreholes from Excel with bitmap data I always get the "Bitmap "File name" is bad" error message no matter what I do. When trying to export bitmap data from rockworks as excel table I always get the "invalid index" error. Do you know what could be the problem here?

Simple fix, shut down program and reopen and program operates fine. Maybe there is a refresh button also? Solved but curious why?

Stange problem upon transferring BH database to BH data fields. Data properly charted to correct field. Viewing functionality with pointer or scroll not happening, point to BH 104 and 102 shows. Try to move to 110 and 102 still shows. Must be a simple fix but I have not found it yet Thank you for suggestions

Hi, I would like to know how to do declustering, compositing and how to integrate variographic calculations when estimating resources with Rockworks. Is it possible to process magnetic and gravity data on RockWorks (including doing constrained and unconstrained 3D inversions of these data with RockWorks)? Thanks in advance for your feedback

Thank you Alison for your reply

Vale, Unfortunately, we no longer support PetraSim v2016 and I cannot think of a way to get around this error. It looks like it was resolved in PetraSim v2017 and later versions. If you would like to contact RockWare with your licensing information, we can determine if you are eligible to use a newer version of the software. You can contact us at tech@rockware.com. Best Regards, Alison

Hello, We are experiencing a problem with Petrasim 2016. we are trying to set-up a model in which we would like to assign different temperature gradient to the layers. As soon as we click on Layer > edit layers > initial conditions > temperature > function, the software crashes. the java error we get is the following: PetraSim Version: 2016.2.0523 x64 Date: 16-set-2024 10.16.30 java.lang.NullPointerException at petrasim.value.EditValue$ValueEditorLinear3d.getValues(Unknown Source) at petrasim.value.EditValue$ValueEditorLinear3d.lambda$editValue$43(Unknown Source) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:726) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:109) at java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:184) at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:229) at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:227) at java.security.AccessController.doPrivileged(Native Method) at java.awt.WaitDispatchSupport.enter(WaitDispatchSupport.java:227) at java.awt.Dialog.show(Dialog.java:1084) at java.awt.Component.show(Component.java:1673) at java.awt.Component.setVisible(Component.java:1625) at java.awt.Window.setVisible(Window.java:1014) at java.awt.Dialog.setVisible(Dialog.java:1005) at thunderheadeng.gui.guiDialog.setVisible(Unknown Source) at thunderheadeng.gui.guiDialog.beginShowing(Unknown Source) at thunderheadeng.gui.guiDialog.doModal(Unknown Source) at petrasim.gui.Actions$EditLayerAction.run(Unknown Source) at petrasim.gui.Actions$PetraSimAction$1.run(Unknown Source) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:726) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) We understand this is a Java related problem, but we don't know how to manage it. Java software installed is: Java RE Version 8 Update 401 We need to use the software for an ongoing project. Any solutions? Best Regards, Vale