Jump to content
RockWare Support Forum


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Golden, CO
  • Interests
    Geology, Geochemistry, Programming

Recent Profile Visitors

1444 profile views

Brianna's Achievements

Advanced Member

Advanced Member (3/3)



  1. Msayed, What program are you using and what kind of format are you in need of? Why would the center of the voxels be sufficient? Since the RockWorks model is regularly spaced and uniform, wouldn't the center of the nodes be the "same" as the corners? I would think it would only be different if the discretization of the grid was variable?
  2. Thanks for this question Chris. If you want to have uniform thickness across faults, you have to add in some control. RockWorks needs to create a grid across the entire project area. This includes above ground where the units may have eroded away. You need to approach your project with a couple of things in mind: your geology is a result of multiple events and you will need to construct the stratigraphy model in the same way. I would recommend creating a grid surface of your alluvium on its own first. This gives you a known thickness of alluvium across the site. The bottom of the alluvium will then be the constraining surface to the underlying layers. You can save the alluvium for later as it's modeled by turning off that unit in the stratigraphy list so it's not re-interpolated. The stratigraphy model is then constructed below including layers that would have intersected the alluvium prior to erosion. Do this by adding stratigraphy above the ground (you can have strat units with negative values indicating that they are above the ground). This gives RockWorks the ability to interpolate the grids across the entire site. When you model this, use the alluvium base as the constraining surface so it cuts the units above that grid surface. You may also need to get your units below your data to extend the beds that may not have been seen in the deeper holes. Ideally, if you run the stratigraphy model without onlap or overlap (using none) you shouldn't see any overlapping layers because you are forcing an average thickness of the units where you don't have the data. We are working on an update to RockWorks that will give you the ability to truncate your striplogs in the sections so it doesn't show the data above 0 and below your TD so all of the inferred units in your logs will not display. This allows you to keep single boreholes and not duplicate holes with the extra data. If you have any more questions please contact me directly.
  3. Hi Abby, I'm not exactly sure what it is you're looking to do. Could you draw out what you want to do and send it to support@rockware.com Then I'll be able to come up with some suggestions if it's possible to do.
  4. You can plot up stereonets and a variety of maps showing strucutral data, but we do not have anything pertaining to safety factors and failure prediction. Here are the options in the "Planes" category.
  5. The Single table import was broken since the last build because of some internal changes to the program. We have a fix and we should be releasing this fixed version later today. Sorry for any inconvenience.
  6. Jeremy, I can help you out with this if you send your project data to support@rockware.com. Without seeing what's happening it is hard to say specifically what the issue is. Cheers, Brian
  7. Chris, Unfortunately in LogPlot7 this is not possible. Look for this feature in the next version of LogPlot coming soon.
  8. You can assign the vertical units to meters or feet when you create your project. You may not have switched that to feet when you created the project. You can reassign the units from the Settings/Coordinates/Reassign coordinate system and/or units without changing actual data
  9. Josh, The legend text is directly proportional to the size of the legend itself so by making the legend larger the text will get larger. Otherwise there is no direct way to change the size. Another indirect way would be to change the other dimensions in the legend to make more space for the text... so change the margins or the cell width.
  10. Craig, All boreholes that are input to the borehole manager need to have at least the following data fields: Easting Northing Z Elevation Collar Elevation Total Depth The Z elevation is the ground surface elevation. The collar elevation is an alternative elevation, typically above or below the ground surface, that might be used as a measuring point for water levels. If you don't have this information, you can use the Z Elevation. If you are having trouble importing from Excel, you can paste your values into the Utilities data sheet and transfer the values to the borehole manager using the File -> transfer -> Locations->Borehole Manager function Be sure to assign units to the column headers before transferring.
  11. Craig, Check to see if your project dimensions are set properly so that your boreholes are within the project bounds. Generally, if the project dimensions are outside the borehole locations, it may appear that your boreholes are not showing up.
  12. Josh, Unfortunately we don't have any 3D clipping tools. What I would suggest is using either ARC 3D or AutoCad to clip it prior to importing it. I'm going to put this feature on the list for the developers for a future version.
  13. Josch, The method you are using to produce your grid surface will dictate how long it will take. More complex calculations will add time. When I generated a map from your data I used triangulation because it was a large set. I just ran Easy Map (which uses triangulation) and it took about 4 minutes. You can certainly do what you are wanting to do but you will need to think about your resolution of the model. A model space that is 200km2 is vary large. It's certainly fine, it's all about scaling. If you want to use your 50m DEM you would need to make your model in 50m spacing and that would be much too large. Depending on the spacing of your boreholes, I would consider a smaller number like 500m grid spacing. I say to go this large because it's a good way to make a faster model that you can get a sense of what's happening before you go into the detailed and more time consuming models at smaller increments. Use the Borehole manager for storing all of your data except for the grids. It's much more powerful than using the DataSheet. The datasheet has many uses, but the borehole manager will allow you do do things much more efficiently. There is a very 'loose' connection between the BH Manager and the DataSheet. The DataSheet doesn't save to the BH manager except for Stratigraphy and Locations ad those are manual commands. You will typically go back to do things in the Utilities but the Borehole manager is where you want to store all the XYZ data for your boreholes. Tips on your DEM: you can use the 50M DEM for cross sections and profiles for the surface, but for doing anything that involves grid math, the surface grid needs to be exactly the same size and dimensions as your model. So if you were going to make a 500m model, make a 500m spacing DEM. While you're at it, make some other resampled ones, maybe at 250, 200, and 100. You can use those later on when you refine your model. Brian
  14. This is a pretty large data set so you will want to load the file to make the grid instead of using the data sheet. I would stay away from using Local Coordinates, The maps you make here are small scale and UTM is much better for that. Here's what I did to make a map from your data: Be sure you make your project in UTM zone 32 (I used x/y and z meters) load your data to the datasheet convert the Lat/lon to UTM zone 32 You can scan the datasheet to get your model dimensions at this point based on the UTM export the data to a text file Load the text file using Map-> Gridbased map-> based on xyz Because you have such a huge data set I used triangulation and got a good result
  15. It seems that the issue was coming from data issues. I think you have it worked out now.
  • Create New...