Jump to content
RockWare Support Forum

All Activity

This stream auto-updates     

  1. Last week
  2. It builds the model first and then truncates it, so I don't anticipate you having any problems with the collar elevations not matching the DEM.
  3. I am thinking that it will work better with a smaller number of higher quality points, and including structural data with them. If I put in points along a contact, and constrain the model with the ground surface, will I run into problems if there are small differences in the collar elevation and interpolated ground surface? I m worried that the model might truncate the interval of the borehole that includes the contact, and therefore not see the contact. Or does it build the model first and then clip to the ground surface?
  4. My guess is that tens of thousands of points would be overkill. I would start with a smaller dataset and build up from that. Maybe increase the number of points to 8000 to see how it works first?
  5. I have just run a test with a handful of contacts converted to points/psuedo boreholes, which added about 800 points. Am I going to run into problems if I end up adding tens of thousand such points?
  6. Also, there are fields for strike and dip in the Stratigraphy table. Use the Tab Manager tool to enable the fields. If you populate these fields, then you would want to use the Dip interpolation algorithm during model creation: Unfortunately, other interpolation algorithms don't take strike/dip into account, so you really just need to experiment to see if this approach works for you. Limiting the number of points or applying a cutoff distance seems to help create more realistic surfaces.
  7. You will definitely need to resample the DEM or LIDAR surface to match your project dimensions. This can be done through the Grid|Math|Resample program under the Utilities. In most cases, you can import the DEM as an ArcASCII file (or some other format), but you may not be able to display it. You just need the RwGrd file to be created so that the resample tool can be used to bring it down to a resolution more appropriate for geologic modeling.
  8. Thanks. I am using Rockworks for the first time, and really appreciate the advice. I am making a fairly detailed and accurate geologic map on a lidar base, so I will have plenty of contacts on multiple horizons to include. I assume there is no way to include strike and dip data directly. I was planning on using the lidar as a topographic surface, but Rockworks choked on a 600,000 cell USGS DEM so I can't imagine how it would handle 1m lidar.
  9. I think this is a good approach. Depending on whether you need to model other units as well, you may want to add additional contacts to the database, both above and below ground (perhaps using an average thickness value for each unit). When creating the Stratigraphy model, be sure to use a "Constraining Surface" such as a DEM or grid that is based on borehole elevations. Feel free to send us your project if you are having a problem creating a model that reflects these superficial contacts. Best Regards, Alison
  10. I wanted to add a couple of additional suggestions. 1. An easy way to populate an optional field is to use the File | Locations -> Datasheet tool to transfer data in the Location table of the Borehole Manager Database to the Datasheet. You would want to do this AFTER adding the optional field to the database. You can then populate the optional field, possibly by copying and pasting, and then you can transfer the data back to the Database through the File | Transfer | Locations-> Borehole Manager tool. 2. You might consider creating a playlist that gives you tools for turning on and off groups of boreholes based on SQL Statements. I would recommend that you include one SQL statement that disables all of the boreholes in the database, and you can then include additional items that enable various groups of boreholes based on optional field data. You can check on only the statements you want to use depending on the group of boreholes you want to enable. Here are some examples of SQL statements: a. This statement will disable all of the boreholes UPDATE [Location] SET Enabled = 0 b. This statement would enable only the boreholes with an "x" in an optional field called "HPT" UPDATE [Location] SET Enabled = 1 WHERE ("Location"."HPT" = 'x') c. This statement would enabled only the boreholes with aExample SQL Statements.RwPlaylistn "x" in an optional field called "MIP" UPDATE [Location] SET Enabled = 1 WHERE ("Location"."Mip" = 'x') Obviously, these SQL statements will vary depending on the way you've set up the optional fields. To turn on the MIP boreholes, you would check on just the first and last statement (not the HPT statement), and then run the Playlist. I've attached a playlist with these three items so that you can download it and experiment a bit.
  11. I am trying to combine borehole stratigraphic data with geologic map data. From what I have been able to gather, this is done by creating psuedo boreholes at locations where the map provides stratigraphic data. To convert my contacts, I first converted the polylines to vertex points, then gave each point a collar elevation equal to the ground surface elevation, and then added two stratigraphic intervals. One interval extends from -10 ft to 0 and has the overlying unit, the other goes from 0 to 10 ft and has the underlying unit. Is this the right approach? Is there a simpler way to do it?
  12. Thanks, that did the trick. Tedious to go through and populate the optional field but now I can easily sort.
  13. There are a few ways to group boreholes. One is to add an optional field, then Filter/Select to update the Enabled flag based on the values in that new field. Another is to create a list of borehole names either by just typing them into a text file or from the Edit menu "Save Enabled/Disabled borehole list", then use "Enabled/Disabled boreholes Based on list" from the same menu to update the Enabled flag when you want to switch. If the boreholes are geographically differentiated you can create a sub-site (which sounds like it would not work for what you need).
  14. Is there a way to group boreholes in borehole manager so that you can view subsets of data without having to check and uncheck dozens of boxes in the borehole list. For Example, I have boreholes that include bedrock scattered among many that do not, and I would like to look at the two datasets separately. There are hundreds of boreholes, so toggling between sets by unchecking individual boreholes would be tedious.
  15. Earlier
  16. Gridded surfaces can include use strike and dip information when you create the grid. Choose the ModOps Grid | Create | XYZ & Dips -> Grid menu. Sold models require XY location, Z elevation (ground minus depth), and G (a unique numeric ID) of each node within the item. Regards, Tom B RockWare Inc
  17. Hello everyone, I am very, very happy to be part of this Forum. I am a student in Mining Geology, option Applied Geophysics. I developed a 2D geological model from geological field observations and geophysics (Magnetism and Gravimetrics associated). Since my 2D model is already realized and that I can evaluate through geophysics the depth of the bodies and geological structures constituting the 2D model, how to do or what approach I should use to reconstruct this same model in 3D please. Thank you in advance for your attention.
  18. The Midas.dll error can occur when RockWorks20xx is launched. It is caused by the midas.dll file not being properly registered. To correct that follow the steps below. Close RockWorks. Open up a command prompt by selecting the windows button + R at the same time. Type cmd into the Run window like the screenshot below which will bring up the command prompt window. On the first line after C:\Users\Username type (or copy and paste) in: cd "c:\program files\rockware\rockworks20\" and hit Enter. That should bring up a second command line starting with c:\Program Files\Rockware\Rockworks20\ and after that type (or copy and paste) in: regsvr32 midas.dll and hit Enter. A window should then pop up saying: DllRegisterServer in midas.dll succeeded. Below is a screenshot of what this should roughly look like. If the error persists, users have found that running a registry cleaner solves the problem, presumably by removing conflicting references to the DLL. Molly Mayfield RockWare Inc
  19. Molly

    Export to emf

    Hi Allison, Thanks for your posting.A few questions: Can you specify the revision of RockWorks you are using (e.g. 2020.9.3)? I'm having difficulty recreating this issue in both RockWorks17 (the last posted 2020.5.6) and RockWorks2020 (the current 2020.5.3 build). Does the output file look different if you open it into a different program? Metafiles are tricky because they can look very different when opened into Paint, for example, versus Word or Illustrator or PaintShop or... Do you need to use the EMF/WMF for your desired output? High-res raster output is more predictable. You are welcome to email your RockPlot2D file (.Rw2D) to support at rockware.com and, with the information from above, we can try to recreate the issue. Thanks Molly Mayfield RockWare Support
  20. Allison

    Export to emf

    When I try to export a cross section (Rockplot2D file) to a .emf or.wmf, the cross section gets cut off (see attached). Choosing manual VE of 10 (which is the VE of the section) and a size 11x17 page. This used to work well but now all of a sudden it cuts everything off. Thanks for your help. emf.docx
  21. The issue that was causing this error was that there were boreholes that had dates listed as pre-1900. This is not an issue within RockWorks, but when exporting out to Excel you will receive the OLE error message as Excel's dating options technically do not start until 1/1/1900. Excel will halt the export as it views those dates being exported out pre-1900 as "negative dates." If the dates are updated to show after 1/1/1900 then the export should go through without issues.
  22. Hi Tom The email is on its way. Thank you for looking into this. Regards Vincent
  23. Hi Vincent, Please backup your project with the File | Backup Database, and send the ZIP file to [email protected] We'll take a look to see how to resolve the problem. Regards, Tom B RockWare Inc
  24. Hi all I wanted to create an multiple tables export to an excel file when I stumbled upon following error: So, naturally, I performed a database integrity check and every datatype was verified except the 'Production' as you can see below. Now I'm left with the question on how to solve this problem. Has anyone else encountered this problem before? Kind regards Vincent Verswijvel
  25. A new version of RockWorks2020 was uploaded to the RockWare website today, with many new features, improvements, and bug fixes. And a new video! The RockWorks Revision History has a complete list, by date, of all changes in the program. Video A new button titled "2D & 3D Embellishments" has been added to the "What's New in RockWorks 2020" index. Clicking on this button will display a new video that describes some additional new features within RockWorks 2020.(https://www.screencast.com/t/16pyJx9BJp). New Features A new tab option titled "Lith/Strat Filter" has been added to the following menus: I-Data | Histogram I-Data | Statistics P-Data | Histogram P-Data | Statistics T-Data | Histogram T-Data | Statistics Reports generated by programs that use the new Lith/Strat Filter option now include summaries of the Lith/Strat Filter settings. Users can now specify the number of sides in RockPlot cylindrical entities (cylinder, cones, disk, etc.) in the Preferences dialog on the RockPlot tab. Fewer sides will make drawing faster and exports smaller. The default setting is 12 with a minimum of 3 and a maximum of 24. Changes to this value will affect already created diagrams. The Surface Profile options for sections and profiles now provides for two surfaces (e.g. ground surface and water table). The vertical title position for section and profile annotation can now be manually specified. This is useful when creating multiple sections and profiles in which the title position must be consistent. An option for smoothing the grids has been added to the T-Data | Multiple Solids (TimeMachine) program menu. Added an ability to list the files/entries in the Project Manager. The report labeling options within the Borehole Operations | I-Data | Volumetrics (IDataVolume) and Borehole Operations | T-Data | Volumetrics (TDataVolume) programs now include options for independently specifying the decimals places for the area, g-value, length, mass, and volume results. A new option titled “Format for Readability” has been added to the TXT and RFT sub-menus for programs that create reports. If selected, the output is configured for optimal display using a fixed-width font. The Grid Polygon Clipping program now will take multiple polygons from a RockPlot2D file and apply them to the output grid. The Utilities | 3-D | Perimeter/Wall program (Perimeter3D) now includes an option for plotting a "Cage" around the diagram. Lots of changes to the Histogram programs. "Reset Menu Setting to Defaults" was added to the Settings menu in most program windows. This is similar to the Reset in the main Setup menu except that it applies only to the menu that is open. It opens the project default ini file and updates the menu setting to those values. Improvements The "Show Instructions" checkbox that formerly appeared within the sub-menus listed below has been replaced by a small "Show/Hide" +/- button located near the upper-right corner of the sub-dialog. The status of the small +/- buttons (display/show help embedded messages) at the right edge of the following sub-menus is now shared with all other programs: Time Filter , Strat Rules, 2D Log Design, 3D Log Design, Fence Location, Section Location, Profile Location, ProSect Location, and Location Map. In the Playlist you can multi-select items then Cut, Copy, Paste and Delete multiple items at a time. The popup menu that appears when the user right-clicks on the Playlist now includes the Enable All and Disable All options. The number of Playlist items is now shown within the Playlist title. Vertical and diagonal striplog titles within sections and profiles now properly offset the main title. The Solid Voxel Reveal program has been renamed to Solid Reveal and now works with both Isosurfaces and Voxel models. The stand alone Voxel Reveal program now allows users to set the view direction, zoom, vertical exaggeration, background color and other 3D options. The Solid Reveal program now allows the user to activate up to 12 different changes of direction, with or without a bounce. Deletions from the Faults tab will warn the user with a confirmation dialog for both single fault deletes or the Erase Disabled functions. Reminder warnings have been added to the 2D Striplog Section and Stratigraphy Picker menus to avoid using the Hang and Vertical Clipping at the same time. ModOps Solid | Import changed the menu items to ASCII XYZG Import with and without a header. Reworked the imports to handle other delimiters in addition to a space. The RockWorks Graphics | Images | Digitize program has been redesigned. The textual reports produced by the IDataVolume and TDataVolume programs now include the name of the polygon table used for limiting the resource, the density conversion factor, and the stripping ratio type. They have been reformatted for better readability, and the Geologic Resources/Reserves summary has been moved to the bottom of the report to be more consistent with the sequence of filtering. Other reports have also been reformatted for better readability: Borehole Operations: Striplogs | Datasheet - > Borehole Survey, Striplogs | Borehole Survey, P-Data | Create Predictive Model, P-Data | Histograms by Lithology, I-Data | Statistics, T-Data | Statistics, P-Data | Statistics Utilities: Stats | Univariate, Survey | XYZ, Planes | Beta Intersections, Stats | XYZ Analysis ModOps: Grid | Directional | Trend Surface Report, Grid | Statistics | Stats - Single Grid, Grids | Statistics | Stats - Multiple Grids, Volume | Triangulation Volumetrics, Volume | Ore Grid, Volumetrics | Extract Via Surface Excavation The ModOps | Volumetrics | Extract Via Surface Excavation program now checks to make sure that the surface and the solid models have the same dimensions and issues a meaningful error message if they don’t. You can now import your 2D faults into 3D fault tab (Faults Tab | Import | Fault Table to 3D Faults. On the Fault tab, delete any value in the G-Value field will NULL the field, it will show as a blank, a database NULL value. The frame for importing Faults will now accept a blank value as a null value and not convert it to a '0'. The font dimensions for adding perimeter annotation in Google Earth is no longer shown in scientific notation and the maximum size has been increased to 10,000 meters. The RockPlot2D Annotate Border program now offers the correct options for the type of diagram (maps, sections, diagrams) and has been renamed to Annotate. Bug Fixes The solid modeling Distance filter now works correctly when modeling lithology using either the Lateral Blending or Lateral Extrusion algorithms. The ModOps | Volumetrics | Extract Via Surface Excavation program now generates a 3D diagram. Unchecking the Report option will now eliminate the report. The Stratigraphy Picker now reads numbers with thousands separators and plots formations below a depth of 1,000. The Manual option within the CSV export program now works correctly. Planes | Polylines to Planes, azimuths can represent strike or dip. Tab renamed to Directionality. I-Data Volume and T-Data Volume programs no longer generate errors if the Report option is disabled. Utilities - Stats | Ternary Diagram Titles now honor the Peripherals input values. Also applies to the Durov and Stiff diagrams. Fixed DBF import to the Datasheet, plumbing reconnected so import works. Polylines & Images -> Mult. Curved Image Panels, plumbing reconnected so it works. Also Sample file Images_Vertical_Multiple_Curved updated. Polyline & Image -> Single Curved Image Panel, plumbing reconnected so it works. Added an example file to "Polyline & Image -> Single Curved Image Panel". Sections with grid-based surface profiles no longer generate an error if there are duplicate vertex points. Sections through solids no longer generate an error if there are duplicate vertex points. 3D Shape Exports (Stratigraphy, Lithology, Water Levels, Well Construction Fractures, I-Data, T-Data and P-Data) have been moved out of the Ledger Exports due to an incompatibility of the options and purpose. The Shape exports have their own menu items as they did in RW17. Reports that are sent to Text or RTF files now use the designated Manual file name. The Solids to Animation program now scans all included solid models to find one minimum/maximum value set to fit all models in the animation. This prevents the color scheme from changing for each frame. The Solid | Export | ASCII program permits selection of G value decimal places. We recommend that Network license users install the RockWare Network License Administrator v. 1.15. Contact support at rockware.com for a link to the the latest version. To download this build, use the Help | Updates | Check for Updates menu inside RockWorks2020. Or visit our website and click on the RockWorks Free Trial tab: https://www.rockware.com/product/rockworks/#tab-product_inquire_form_1494_tab 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 September 3, 2020. Contact RockWare Sales or visit our Customer Portal (https://www.rockware.com/customer/) if you would like to update your maintenance. Molly Mayfield RockWare Inc
  26. Looks like a bug to me. I should have a fix by the end of the day.
  27. I mean to the left not the right.
  1. Load more activity
  • Create New...