RockWorks/2006 Revision History
(123) COSMETIC (12/28/07/JPR): The Borehole Manager / Striplog-2D submenu has been re-designed such that the I-Data and P-Data track column-selection sub-menus no longer appear whenever the associated tree-item is expanded.
(122) BUG FIX (12/27/07/JPR): The RockPlot/2D / File / Export / KMZ (Google Earth) program now works correctly if the initial map is stored in UTM / Feet units (assuming that the user has selected "Feet" as the input units).
(121) IMPROVEMENT (12/27/07/JPR): The Great Circles / Variable option within the Utilities / Planes / Stereonet program is now more "forgiving". Specifically, the previous version required that the user select a "line-style" column (column styles are defined by right-clicking on a column title and selecting the type of data that is contained within the column). If the user selects a "color" column, the program will now use that data with a solid, single-pixel line thickness.
(120) NEW FEATURE (12/27/07/JPR): The Borehole Manager / Lithology / Section program now generates layer information for all of the diagram entities. This feature is useful when you wish to isolate/highlight selected lithotypes within a profile.
(119) NEW FEATURE (12/27/07/JPR): The Borehole Manager / Lithology / Profile program now generates layer information for all of the diagram entities. This feature is useful when you wish to isolate/highlight selected lithotypes within a profile.
(117) COSMETIC (12/27/07/JPR): The starting point for all pattern fills is now the same for all of the entities within a diagram. This means that contiguous polygons that use the same pattern will not have a discontinuity between the patterns. Notice the contact between the top two units within the following example. In the previous version, the diagonal lines were offset.
(116) BUG FIX (12/24/07/JPR): Diagonal lines within 2D pattern-fills are no longer sporadically omitted within the corners of rectangular regions.
(115) BUG FIX (12/20/07/JCJ): RockWorks now uses the "XP Manifest" which allows the program to change according to the "themes" that are implemented within Windows XP and Vista. These themes determine menu transparency levels, check-box rounding, tree-expansion/collapsing icons, and a whole mess of other useless characteristics.
(114) BUG FIX (12/20/07/MIW): Items within disabled layers may no longer be selected within the ReportWorks program.
(113) NEW FEATURE (12/20/07/MIW): An Undo (Ctrl-Z) feature has been added to the ReportWorks program. The number of undo levels is initially set to 10 and can be changed from the new Configuration dialog. The Undo command can be disabled if disk space is limited or performance is unacceptable.
(112) COSMETIC (12/20/07/MIW): The RockPlot/3D / File / Export / Animation menu now displays the file names with a white background that is much easier to read.
(111) COSMETIC (12/20/07/MIW): The Grafix / 3D-Utilities / Append program now displays an hourglass cursor as the operation is taking place,
(110) BUG FIX (12/20/07/MIW): The Utilities / Widget / Igneous program now displays the correct rock types and constituents.
(109) NEW FEATURE (12/20/07/MIW): It is now possible to select all of the items in a RockPlot/2D layer by right-clicking on the layer name within the layer list.
(108) NEW FEATURE (12/20/07/JPR): The Borehole Manager / Lithology / Volumetrics program report now includes a column that list the statistics for undefined nodes.
(107) BUG FIX (12/20/07/JPR): The Borehole Manager / Lithology / Volumetrics program no longer list an initial layer of empty voxels that is above the top of the model.
(106) IMPROVEMENT (12/19/07/JPR): The Utilities / Map / SpherePlot / SpherePlot/2D program now includes an option for plotting a UTM reference grid within cylindrically projected maps.
(105) IMPROVEMENT (12/19/07/JPR): The Utilities / Map / SpherePlot / SpherePlot/2D program now includes an option for plotting longitude/latitude labels around the perimeter of cylindrically projected maps.
(104) IMPROVEMENT (12/19/07/JPR): Programs that reference UTM zones and hemispheres now link to a consolidated graphic menu. that is activated by pressing the new "UTM Zone" button.
This new configuration eliminates the ugly list of zones and replaces it with an interactive map that is activated by clicking on the UTM Zone button and clicking on the region of interest. This consolidates the separate selection of hemispheres and zones into a single click that will hopefully eliminate problems in which a user might change the zone but forget to change the hemisphere.
(103) IMPROVEMENT (12/18/07/JPR): The Utilities / Map / SpherePlot / SpherePlot/2D program now generates layer information for all of the diagram entities.
(102) IMPROVEMENT (12/18/07/JPR): The Borehole Manager / Fractures / Stereonet Map program now generates layer information for all of the diagram entities.
Unlike the Stereonet program (see Revision #101 - below), the Stereonet Map program does not subdivide the individual diagrams into the detailed entities. Otherwise, the layer listing would be too cumbersome.
(101) IMPROVEMENT (12/18/07/JPR): The Utilities / Planes / Stereonet program now generates layer information for all of the diagram entities.
(100) IMPROVEMENT (12/18/07/JPR): The Utilities / Hydrochemistry / Stiff Map program now generates layer information for all of the diagram entities.
Unlike the Stiff Diagram program (see Revision #99 - below), the Stiff Map program does not subdivide the individual diagrams into the detailed entities. Otherwise, the layer listing would be too cumbersome.
(99) IMPROVEMENT (12/18/07/JPR): The Utilities / Hydrochemistry / Stiff Diagram program now generates layer information for all of the diagram entities.
(98) IMPROVEMENT (12/17/07/MIW): The RockPlot/3D / Export / Animation program now saves all of the menu settings.
(97) IMPROVEMENT (12/17/07/MIW): The RockPlot/3D / Export / Animation program now saves the bitmaps/frames in 24-bit color. The previous version used 8-bit color. This simply means that the output looks much better (the color-blends are more continuous).
(96) IMPROVEMENT (12/17/07/MIW): The RockPlot/3D program now uses a new XML "parsing engine" that speeds up the reading and writing of files.
(95) IMPROVEMENT (12/17/07/MIW): The temporary grid models that are generated by the following programs are now automatically deleted upon completion.
(94) IMPROVEMENT (12/17/07/MIW): All grid data referenced by a RockPlot/3D file is now embedded within the RockPlot/3D input file (i.e. the ".xml" files). There are several implications for this change;
(93) NEW FEATURE (12/17/07/JCJ): A new option titled "" has been added to the Borehole Manager / P-Data / Export menu. This program is used to create CSV files of P-Data that can be directly imported into the Microsoft Excel product.
Once selected, this new program will present the user with the following menu:
Upon completion, the output file will be automatically loaded and displayed within Excel.
(92) NEW FEATURE (12/17/07/JCJ): A new option titled "" has been added to the Borehole Manager / I-Data / Export menu. This program is used to create CSV files that can be directly imported into the Microsoft Excel product.
Once selected, this new program will present the user with the following menu:
Upon completion, the output file will be automatically loaded and displayed within Excel.
(91) COSMETIC (12/17/07/JPR): 100 blank rows are now added to the datasheet when loading at ATD file. This will hopefully imply to the novice user that it is possible to add more data to a datasheet. The previous version would terminate the datasheet display at the last row. As always, additional rows may be added by pressing the down arrow, tabbing, etc.
(89) IMPROVEMENT (12/17/07/JPR): The Borehole Manager / File / Import / LAS program now "remembers" the name of the last LAS file that was imported.
(88) BUG FIX (12/16/07/JPR): The Borehole Manager / Striplogs / 2D programs no longer omit the P-Data background grids if the columns do not contain any data and the user has elected to plot the background grids in the foreground.
(86) NEW FEATURE (12/15/07/JPR): The RockPlot/2D program now list the number of entities within each layer.
(85) IMPROVEMENT (12/15/07/JPR): The RockPlot/2D program no longer lists layers that do not contain any data (i.e. they are automatically deleted from the layer list). This does not apply to the default layer.
(84) BUG FIX (12/13/07/JPR): The title now appears in the output from the Utilities / Grid / Grid -> Profile program.
(83) BUG FIX (12/13/07/JPR): When creating vertical sections in which the vertical scalebars are automatically scaled (as opposed to using the project dimensions), the program no longer extends the vertical scalebars above the top of the highest entity within the diagram.
This change applies to the following applications:
RockWorks Utilities / Grid / Grid -> Profile
RockWorks Utilities / Solid / Profile
RockWorks Utilities / Solid / Section
Borehole Manager / Striplogs / Multi-Log Profile
Borehole Manager / Striplogs / Multi-Log Section
Borehole Manager / Lithology / Profile
Borehole Manager / Lithology / Section
Borehole Manager / Stratigraphy / Profile
Borehole Manager / Stratigraphy / Section / Modeled
Borehole Manager / Stratigraphy / Section / Straight
Borehole Manager / I-Data / Profile
Borehole Manager / I-Data / Section
Borehole Manager / P-Data / Profile
Borehole Manager / P-Data / Section
Borehole Manager / Fractures / Profile
Borehole Manager / Fractures / Section
Borehole Manager / Aquifers / Profile
Borehole Manager / Aquifers / Section
(82) NEW FEATURE (12/12/07/JPR): Many of the programs that create two-dimensional diagrams now save the data in discrete layers that may be activated/deactivated within the RockPlot/2D program.
(81) NEW FEATURE (12/12/07/JPR): The "Cage" option that is used for all 3D diagrams now includes options for manually specifying the number of decimal places within the axis annotation.
(80) IMPROVEMENT (12/12/07/JPR): Operations that require a grid and a solid of equal horizontal dimensions now list the offending dimensions if the models are not properly matched. These changes apply to the following options;
(79) IMPROVEMENT (12/12/07/JPR): Operations that require two solids models of equal dimensions now list the offending dimensions if the models are not properly matched. These changes apply to the following options;
(78) IMPROVEMENT (12/11/07/JPR): Operations that require two grids of equal dimensions now list the offending dimensions if the grids are not properly matched. These changes apply to the following options;
(77) BUG FIX (12/11/07/JPR): The Utilities / Solid / Filter / Grid Filters / One Bounding Grid program now exits gracefully if the grid and solid model dimensions don't match. The previous version would give an error message and then continue to erroneously process the data.
(76) IMPROVEMENT (12/11/07/JPR): The Borehole Manager / Striplogs / Profile program no longer attempts to plot every entity within every log. Instead, the program skips logs that do not extend into the profile buffer zone (i.e. the stippled yellow region within the profile location selection dialog). This means that profiles are generated much more quickly especially when working with databases that include large numbers of boreholes.
(75) BUG FIX (12/11/07/JPR): Two-dimensional diagram with multiple layers now correctly rescale, convert to other formats (e.g. DXF), etc.
(74) NEW FEATURE (12/07/07/JPR): The RockPlot/2D Layers window now includes buttons for automatically checking and un-checking all of the layers.
(73) Bug Fix (12/06/07/JCJ): The automated update installation now works with Vista. The previous version generated a notice that required that the user's privileges be "elevated."
(72) Improvement (12/06/07/JCJ): The automated notice that prompts the user to download a newer version now includes an option to disable the automatic newer-version checking in the future. Note: If you disable the automated updating and call for technical support to report a bug, well ... think about it.
(71) Bug Fix (12/05/07/JPR): The Borehole Manager / Vector / Model program no longer produces bad models that lock-up the RockPlot/3D program. This bug occurred with sparse data sets in which any of the voxels did not have a corresponding line segment that was normal to the voxel. In the process of fixing the bug we managed to make the program somewhat faster.
(70) Improvement (12/03/07/JPR): The RockPlot/2D / File / Open option now defaults to the current project folder.
(69) Improvement (12/03/07/JPR): The "high-fidelity" filtering that is used by all of the solid-modeling routines has been tweaked in such a way that the output solid will never have values that are lower than the lowest control point value or higher than the highest control point value. This means that a geochemical model will never have values less that zero.
(68) Bug Fix (12/03/07/JPR): The RockWorks Utilities / Solid / Filter / Polygon Clip program will now replace the nodes inside/outside the polygon by a user-specified, non-null value. The previous version would always use a null value (-1.0e27) as the node replacement regardless of the settings.
(67) Cosmetic (11/30/07/JPR): The RockWorks_2006_Licensing.exe program file has been renamed to "RockWorks_Licensing.exe".
(66) New Feature (11/29/07/JPR): The RockWorks Utilities / Grid / Filter / Boolean program now allows the user to specify the actual values that are used for the "true" and "false" values. This provides the user with a way to assign null (-1.0e27) values to false nodes.
(65) Bug Fix (11/29/07/JPR): The RockWorks Utilities / Grid / Filter / Range program no longer produces unpredictable results when filtering models that contain null values.
(64) Bug Fix (11/29/07/JPR): The custom contour interval option (i.e. contour intervals defined within a user-defined table) no longer produces unwarranted contours when plotting a grid that has a huge range of z-values (e.g. data that requires logarithmic modeling).
(63) Cosmetic (11/28/07/JPR): The RockWorks Utilities / Grid / Grids->Solid Model menu no longer list the cage options twice.
(62) Bug Fix (11/28/07/JPR): The Borehole Manager / Striplogs / Multi-Log Map program no longer plots two logs for every borehole when the auto-offset option has been enabled.
(61) Improvement (11/28/07/JPR): The Help / About dialog no longer contains a scrolling list of RockWare contact information. Instead, a new button titled "Contacting RockWare" now loads the appropriate page into the default web browser.
(60) Cosmetic (11/28/07/JPR): The revision number that is listed within the following locations now shows the entire year (followed by the month and day).
(59) Bug Fix (11/26/07/MIW): Using units other than Units/Inch in the RockPlot2D Printing dialog now work correctly.
(58) Bug Fix (11/20/07/MIW): The "Hide Thin Sections" option within the Borehole Manager stratigraphy modeling now works correctly. The previous version would only work properly when the difference between the base and the top was zero.
(57) Bug Fix (11/20/07/MIW): The RockPlot/2D print scaling now initializes by using a best-fit method if the x and Y scales are not equal.
(54) Bug Fix (11/16/07/JPR): The RockPlot/2D / File / Print now works correctly with metric-based, vertically exaggerated diagrams. These fixes also address a problem with manually-specified pattern densities.
(53) Improvement (11/16/07/JPR): The printer page orientation (portrait vs landscape) is now saved when using the RockPlot/2D / File / Print option.
(52) Bug Fix (11/14/07/JPR): 3D vector data within Borehole Manager / Striplogs no longer produce doofy-looking 3d-arrows if the Value setting (within the Vectors table) is zero.
(51) New Feature (11/13/07/JPR): A new menu item titled "Model" has been added to the Borehole Manager / Vectors menu.
This program is designed to convert directional downhole data (stored within the Vectors table) into solid models that approximate the extents of the vectors. An example application is the generation of void geometries (cave models) based on downhole laser surveys. Actually, that's the only example that we can think of right now, but we're sure that others will come up for other applications.
How It Works:
This program will perform the following operations in order to generate a model that approximates cave geometries based on the vector data:
For each solid model node ...
For each borehole ...
For each vector ...
Compute the endpoint coordinates.
Define a line connecting the endpoints.
Define a sphere whose center is defined by the line midpoint and whose diameter is equal to the line length.
If the node resides outside of the sphere it's g-value is set to "null" (-1.0E27).
If the node resides inside of the sphere, it's g-value is set to the distance to the closest line.
Note: In order for the node values to increase with distance to the closest line, it is necessary to negate the distance values (i.e. the node values should be multiplied by -1) as allowed within the Vector Modeling Options menu.
This example will assume that we're working with downhole laser data in an attempt to delineate cave extents and produce a surface hazard map.
Enter the downhole laser data into the Borehole Manager "Vector" table for all of the boreholes. The distance data is saved within the "Value" column.
Select the Borehole Manager / Striplogs / Multi-Log 3D option and create a diagram showing the "raw" vector data.
Save this RockPlot/3D diagram as "Boreholes.xml".
Click on the Borehole Manager / Vectors menu and select the "Model" sub-option.
Model Dimensions: This is tricky. If you make the cells too small, the model will look very tubular. If you make them too large, you loose resolution. Experimentation is therefore necessary. In general, a good starting point is to make the cell width equal to half of the average minimum spacing between the boreholes.
Negate Node Values: If left unchecked, the node values will represent the distance to the closest vector. When plotting the output as an isosurface, the cutoff level (and slider bar) will behave in a fashion that is opposite to what you'd expect (i.e. the voxels closer to the vectors will be rendered invisible). The "Negate Node Values" will multiply all of the voxel g-values by -1 such that the g-values become higher with proximity to a vector. This allows the cutoff level to behave as you might expect.
Smooth Solid: This will effectively round-off the edges of the "tubes" and create a more natural appearance. Be careful, however, with too much smoothing. Notice how the 4X smoothing (filter size = 1x1 for all models) within the following diagram has removed some salient features.
Once the modeling process has been completed, an initial diagram will be displayed in which the cave appears as a series of coalescing spheres. Experiment with the isolevel setting. During this process, notice how a highly filtered model will generate tubes around the laser paths. As a consequence, it is necessary that various cutoff levels be applied to achieve the desired diagram (e.g. cutoff = 25 meters).
Note: If the "Negate Node Values" option was activated prior to the generation of the model (which it should have been), you will need to enter the isosurface cutoff value as a negative number.
Change the opacity/transparency level of the isosurface to 50% in order to see into the model and compare the model with the original vector data.
Save this diagram as "Caves.xml".
Convert the distance-to-point model to a boolean model by selecting the RockWorks / Utilities / Solid / Boolean Operations / Boolean Conversion option.
In order to use this program, you must enter the minimum distance as the lower threshold (cutoff) value. Let's say that you specified -20. Any voxels that are less than 20 meters from a vector will be set to a value of 1 (true) while any voxels greater than 20 meters from a vector will be set to zero (false) within the new, boolean model. The net result can be interpreted to mean that nodes with a value of 1 represent voids whereas nodes with a value of 0 represent rock.
Remember that the distances within the model are expressed in negative values (assuming that you chose to "Negate" the values when the model was initially created). The high-cutoff won't be used, so specify something ridiculously high like 9999.
Name the new, output model "Boolean.mod".
A diagram of the boolean model will look very similar to the original, continuous cave model. It's just more block and doesn't have the low values.
Convert the boolean model into a grid model by selecting the RockWorks / Utilities / Solid / Convert / Solid -> Grid option.
Be sure to check the "Sum" option within the Solid->Grid menu. This means that the grid nodes will be defined as the sum of all nodes within the corresponding solid model vertical column. Given that a voxel value of one within the boolean model represents a void, a grid node value of five would mean that five nodes below that cell are void.
The map of this grid shows, in a continuous fashion, the areas that are most dangerous for heavy equipment. Admittedly, it does not take into account the depth of the caverns (e.g. a large, but very deep cavern may be of no concern).
Use the RockPlot/2D \ Export \ RockPlot3D option to create an overlay of the contour map to show in conjunction with the 3D model.
In order to "see through" this layer into the solid model, we recommend that you plot only the contours rather than a color-fill map.
Once the diagram has been displayed within RockPlot/3D, save it as "Contour Overlays.xml".
Use the RockPlot/3D / File / Append option to append the caves diagram (caves.xml) and the boreholes (boreholes.xml).
(51) Cosmetic (11/13/07/JPR): A new menu item titled "Vectors" has been added to the Borehole Manager menu bar. This menu will contain future programs that process data within the Borehole Manager / Vectors data table.
(50) Improvement (11/09/07/JCJ): Programs that export data to Microsoft Excel files (XLS) now generate meaningful error messages.
(49) Bug Fix (11/09/07/JPR): The Borehole Manager / Striplogs / Miscellaneous option now includes an option for specifying the number of subdivisions to use when automatically computing the log resolution. This option disappeared when the graphical menu was introduced.
(48) Bug Fix (11/09/07/JPR): The RockWorks Utilities datasheet no longer generates sporadic error messages when loading and saving large datasets,
(47) Improvement (11/09/07/MIW): The two Surfer import options (ASCII and binary) within the RockWorks Utilities / Grid / Import have been consolidated into a single option. The program now automatically determines the input format and calls the appropriate subroutine.
(46) Bug Fix (11/09/07/MIW): The various "tree-style" menus no longer open the wrong item if the user failed to highlight the new item.
(45) Bug Fix (11/09/07/MIW): The capability for hiding thin zones when using the Borehole Manager / Stratigraphy / Model program has now adjusted such that a cutoff value of zero will hide zones that are equal to zero.
(44) Bug Fix (11/07/07/JPR): The legend option within the RockWorks Utilities / Solid / Model and Fence programs now works correctly.
(43) Improvement (11/07/07/JPR): The Borehole Manager / Lithology / Surface-Map program now generates a friendly error message/warning if the grids and solids have different dimensions. The previous version would produce a cryptic error message.
(42) Improvement (11/05/07/JPR): The RCL option within the Borehole Manager tree menus now saves the P-Data and I-Data variables as column names rather than relative column numbers (which can be screwed-up by moving columns around). This eliminates a step (changing column numbers to column names) when saving menus for subsequent use as RCL scripts.
(41) Improvement (11/05/07/MIW): Trailing spaces are now removed from variables within RCL scripts thereby speeding things up a bit.
(40) Improvement (11/05/07/MIW): If RockPlot3D is launched from RockWorks the initial default folder in the Open Dialog will be the current project folder. If it's launched from a shortcut the initial directory will be the current directory on the main drive.
(39) Improvement (11/04/07/JPR): The RockPlot/2D / Export / RockPlot/3D program no longer generates jagged lines when draping contours over a grid model.
When combined with three-dimensional surfaces, the net effect is somewhat striking ...
Note: For optimal effects, be sure to project the draped contours slightly above the solid surface. It is also useful to decrease the draped contour line opacity to 95%.
(38) Improvement (11/02/07/JPR): The warning message that appears when the user attempts to exceed the 2,500 node limit within the Project Dimensions window now appears after the user has finished specifying the node spacing. The previous version would display the error message dialog box as the user was typing in the node spacing. This was very irritating.
(37) Bug Fix (11/02/07/JPR): The solid modeling programs are now more "stable" with large data sets (e.g. more than one million control points). The previous version would sometimes generate erroneous out-of-memory errors depending upon the machine configuration.
(36) Bug Fix (11/02/07/MIW): The ReportWorks program can now read world files with extra spaces at the beginning or end of each number.
(35) Bug Fix (11/02/07/JCJ): The automatic updating mechanism now works correctly.
(34) Bug Fix (11/02/07/MIW): The programs within the RockWorks Utilities / Planes sub-menu now correctly convert the planes to poles when the input is in dip-direction.
(33) Cosmetic (11/02/07/JPR): The RockWorks Utilities / Grafix / 3-D Utilities / Images / Panels sub-menu has been removed. Instead, the two Panels options have been renamed to "Panels / Vertical" and "Panels / Horizontal" and moved into the Images sub-menu. This eliminates a 4th-level nested menu (just too dang deep).
(32) Bug Fix (10/24/07/MIW): The RockPlot/2D / Export / DXF program no longer swaps the red and blue components.
(31) Bug Fix (10/24/07/JPR): The Borehole Manager / Stratigraphy / Pick Contacts program no longer generates a range-check error. This was a new bug that was introduced within the last update.
(30) Cosmetic (10/19/07/JPR): The main project folder now occupies the entire width of the main RockWorks menu thereby providing a bit more space for listing the current project folder. The previous version sacrificed some "real estate" to the vertical button bars that are used to switch between the Borehole Manager, The RockWork Utilities, etc.
(29) New Feature (10/18/07/MIW): The RockPlot2D / Export / DXF program now uses a look-up table to provide better color matching when using the standard Window's colors provided within the RockWorks dialogs. Non-matched colors will use a best fit method for calculating the DXF Index color.
(28) Bug Fix (10/18/07/MIW): When editing tables (e.g. the polygon table), the program now saves the current file name when the table editor is closed.
(27) Bug Fix (10/18/07/MIW): The Borehole Manager / Stratigraphy / Model program now computes the total volume.
(26) Bug Fix (10/18/07/MIW): The RockWorks Utilities / Linears / Import / DXF Lineations program now increments the datasheet rows when the source file contains polylines.
(25) New Feature (10/18/07/MIW): The RockWorks Utilities / Planes / Beta Pairs program now generates an output column that lists the angle between the planes.
(24) Cosmetic (10/17/07/JPR): The solid modeling distance filter now includes option for expressing the distance in terms of map units or as a percentage of the project size.
(23) Cosmetic (10/17/07/JPR): The "Decluster" option within the Borehole Manager / P-Data / Model menu has relocated as a sub-option under the P-Data Track grouping.
(22) Cosmetic (10/17/07/JPR): The "Decluster" option within the Borehole Manager / I-Data / Model menu has relocated as a sub-option under the I-Data Track grouping.
(21) Cosmetic (10/17/07/JPR): The RockWorks Utilities / Solid / Model menu has been re-organized such that the Spatial FIltering, G-Filtering, Decimation, and Declustering options are now located under a new sub-topic titled "Control Point Filtering".
(20) Cosmetic (10/17/07/JPR): Selected items within the RockWorks menus now display additional information within the "button-bar" at the top of the menu dialog box as the mouse cursor is moved over the item. This new capability is designed to provide more information about menu items without cluttering up the menu.
(19) Cosmetic (10/15/07/JPR): The Upper Surface, Lower Surface, Distance, and Polygon Filtering options within the solid modeling menus have now been grouped under a heading titled "Model Constraints".
(18) New Feature (10/15/07/JPR): The "Upper Surface" and "Lower Surface" grid filters within the solid modeling menus now provide for separate margins. The previous version (when these options were lumped under the "Stratabound" heading) had only one setting that applied to both filters.
(17) Cosmetic (10/15/07/JPR): The "Stratabound" sub-heading has been removed from the solid modeling menus. Instead, the sub-options are now shown with new headings (i.e. "Upper Surface (Grid) Filter" and "Lower Surface (Grid) Filter").
(16) New Feature (10/15/07/JPR): The solid modeling menus now include an option for restricting the modeling to a region that is either inside or outside of a user-defined polygon. This is a "pre-filter" (see item #13 below) which means that it can greatly speed-up the processing time.
(15) Improvement (10/12/07/JPR): The solid modeling has been redesigned in such a way that the Maximum Distance and/or Stratabound Filtering operations are performed as the model is being created as opposed to a post-modeling process. This means that the program doesn't waste time interpolating node values for points that will be eventually removed by the Maximum Distance Filtering. For example, consider the following dataset:
1. Control points distributed within a narrow, diagonal region.
2. Solid model for entire region that encompasses control points.
3. Solid model constrained to region within a user-specified distance (5% of project size) of a control point.
4. Solid model constrained to region below a user-specified surface.
5. Solid mode constrained by user-specified distance as well as user-specified surface.
The following execution speeds describe the advantage of pre-filtering the nodes as opposed to filtering the completed model:
By reversing the order of distance and stratabound filtering, the interpolation process is considerably faster.
Given that the previous version would add additional time at the end, the speed difference is even more dramatic. Given the preceding example, an operation that may have taken 1 hour and 15.9 minutes now requires 16.4 minutes!
(14) Cosmetic Consolidation (10/14/07/JPR): The Stratabound Filtering and Minimum Distance Filtering options within the solid modeling menus no longer include separate sub-options that allow the user to define the g-values for nodes that reside outside the filter boundaries. Instead, the menu now includes a new option titled "Undefined Nodes" in which the user can define a single g-value that is to be used for nodes outside the filter boundaries. This removes an incongruity in which a node can be outside a stratabound filter as well as a distance filter (i.e. Which default value should be assigned to the node?).
(13) Cosmetic (10/13/07/JPR): The RockWorks Utilities / Coords / Rotate XY Data program no longer displays a debugging message ("hi") before the coordinates are rotated.
(12) Improvement (10/12/07/JPR): The Project Dimensions sub-menu now includes special traps that automatically adjust the node spacing in the event that the maximum number of nodes are exceeded in any direction.
(11) Bug Fix (10/11/07/MIW): The RockPlot/2D program now correctly exports rectangles to the RockPlot/3D program.
(10) Improvement (10/11/07/JCJ): 3D striplogs now include a date filter when plotting aquifer data.
(9) Improvement (10/11/07/JCJ): RockWorks will now prompt the user to install a new copy of RockWorks after the automatic download is completed. If the user chooses not to install immediately they will be prompted on closing or opening RockWorks.
(8) Bug Fix (10/11/07/JCJ): Some users were experiencing a problem with the program setting the initial project folder just after installation. The program will now preset the project folder to the default Samples directory if no project folder has been set.
(7) Bug Fix (10/11/07/JCJ): The Tables window now updates the path for the stratigraphy , lithology and well construction tables to reflect changes within the project folder.
(6) Bug Fix (10/11/07/JCJ): The Borehole Manager / Stratigraphy / Consolidate program no longer deletes the last unit in the hole. The program also now executes faster and updates the borehole only if something was changed as a result of the consolidation.
(5) Bug Fix (10/11/07/MIW): The RockWorks Utilities / Stats / Ternary program overlays now work with international number formatting.
(4) New Feature (10/05/07/JPR): The main Tables option (located along the left side of the main RockWorks menu now includes an option for editing the tables that are used by the new 3D-Points program (see item #2 below).
(3) Cosmetic (10/05/07/JPR): The word "scalar" is now spelled correctly within the program menus. The previous version used a misspelling of "scaler". Unfortunately, the RCL (RockWare Command Language) commands must remain misspelled in order to insure backwards compatibility with existing RCL scripts.
(2) New Feature (10/05/07/JPR): A new program titled "3D-Points" has been added to the RockWorks Utilities / Map menu.
The 3D-Points option has two main sub-options titled "Simple" and "Advanced". The "Simple" version will prompt the user for three columns within the datasheet that contain the X (Easting), Y (Northing), and Z (Elevation) for a list of points.
The output from the RockWorks Utilities / Map / 3D-Points / Simple program will be displayed as equally-sized red spheres.
The RockWorks Utilities / Map / 3D-Points / Advanced program requires a bit more explanation. Quite a bit.
Group Name: This is the
diagram title that will be displayed within the RockPlot/3D data tree.
It becomes especially useful when diagrams are combined.
Symbol Type: This setting
defines the type of three-dimensional symbol that will be used when plotting
the data points.
Spheres / Oblates: Plot points as spheres or oblates (stretch or squished spheres).
Spheres, Oblates (Horizontal Radius > Vertical Radius), & Oblates (Vertical Radius > Horizontal Radius)
Cubes / Parallelepipeds: Plot points as cubes or parallelepipeds (stretch or squished cubes).
Cubes, Parallelepipeds (Width > Height), & Parallelepipeds (Height > Width)
Symbol Size & Color: Unlike
the simple version of the 3D point plotting, the advanced version allows the
user to control the symbol dimensions and colors.
Independent: Define the
symbol dimensions and symbol colors separately.
There are two methods for setting the symbol dimensions:
Uniform: All symbols will have the same size.
Uniformly Sized Points
dimensions are expressed as a percentage of the horizontal
diagonal of the project area. In the case of spheres,
this number will define the radius. For cubes, the
size defines the width of the cube.
Variable: If selected, the variable option will scale the symbol based on the minimum and maximum sizes and the magnitude of a user defined data column.
Variably Sized Points
This column contains the parameter that will be used to
determine the size of the symbol. It is especially
useful for showing variations in point attributes (e.g.
earthquake magnitudes, geochemical values, etc.).
The magnitude data (see item above) will be normalized in
such a way that the smallest value will correspond to this
dimension (which is expressed as a percentage of the
horizontal diagonal of the project area).
The magnitude data will be normalized in such a way that the
largest value will correspond to this dimension (which is
expressed as a percentage of the horizontal diagonal of the
Symbol Colors: There
are three methods for defining the symbol color:
Fixed: All symbols will have the same color (monochromatic).
Monochromatic Point Coloring
Color to be used for all symbols.
Column: Colors are defined by a column within the main datasheet along with the other information (x, y, z, magnitude, etc.).
Column-Based Point Coloring
Column within datasheet that contains color setting for each
Automatic: Colors are automatically assigned based on the user-defined magnitude column within the datasheet. These colors will range from the "cold" colors (magenta) through the "hot" colors (red).
Automatically Colored Points With Magnitude Labels. Note how low values are depicted with cold colors while high values are depicted with hot colors.
Column that will be used to define the color. Low
values will have cold colors while high values will have hot
Table-Based: It is possible to standardize the size and colors of symbols based on a special "lookup-table" and a designated column within the main datasheet. For example, notice how values within the following example that have a magnitude between four and five appear as medium-sized yellow spheres.
Lookup Table & Diagram Based On Range Values Within Lookup Table
Table: Name of file
that contains lookup-table. This table may also be accessed
from the Tables tab on the left side of the main RockWorks dialog.
Data column that should be compared with the lookup table to define
the size and color of the symbol.
Vertical Scalar: The
vertical dimensions for the symbols will be multiplied by this number.
It is useful when the vertical exaggeration for the output will be
Labels: Labels can be plotted adjacent to each sample point. In the case of earthquakes, these labels might show the date or the magnitude. In the case of geochemistry, these labels might show the geochemical levels, and so on.
Spherical Symbols With Labels
Label Column: This is
the column within the datasheet that will be depicted by the label.
Font: This setting defines the font style, size, and color for the label.
Small Font (Left) & Large, Goofy Font (Right)
Offset: The offset defines the distance (as a percent of the horizontal diagram diagonal) between the symbol midpoint and the label.
Small (5%), Medium (10%), and Large (20%) Label Offsets
Leader Lines: This
setting will draw a line from the symbol midpoint to the label.
Without Leader Lines (Left) and With Leader Lines (Right)
Connectors: Connectors are
either vertical lines, tubes, or cones that connect a symbol with an set
elevation or a gridded surface. They are used to register points with
their corresponding horizontal location on a surface.
Connector Color: This
setting defines the color that will be used to plot the connector.
Connector Style: Connectors
may be one of three types:
Line: The connector will be displayed as a single-pixel line.
Tube: The connector will
be displayed as a tube whose radius is defined by the user.
Tube Radius: The
radius of the tube is defined as a percentage of the horizontal
Radius = 1 (Left) and Radius = 3 (Right)
Cone: A cone will be
displayed such that the base is a positioned at the specified surface
elevation (see below) while the tip will be positioned at the symbol
Cone Radius: This is
the cone base radius. It is defined as a percentage of the
horizontal project size.
Conical Connectors. Left: Radius = 2, Surface Elevation = 0. Right: Radius = 4, Surface Elevation = -200
Surface Elevation: The
surface elevation defines the starting point for a connector while the
symbol midpoint defines the other endpoint. There are two methods for
defining the surface elevation:
Fixed: The Fixed option
is used to define the surface as a horizontal plane at a user-specified
elevation (see previous cone example).
Elevation for fixed horizontal surface.
Variable: The Variable
elevation option will use a grid model to define the surface from which
the connector will be drawn.
Grid Model Name: The Grid Model Name defines the grid model that will be used as the surface from which the connector will be drawn.
Three-Dimensional Symbols With Connectors Based On Surface Grid Model
(1) Removal (10/03/07/JPR): The RockWorks Utilities / Grafix / 3D-Utilities / Spheres program has been removed. The same functionality is now available from within the new RockWorks Utilities / Map / 3D-Points program (see Item #2 - above).
Previous Quarter (3/07)