RockWorks/15 Revision History
(102) New Feature (03/31/10/JCJ/CIF): The Google Icon is now an available Utilities column type.
(101) New Feature (03/31/10/JCJ/CIF): The Google Icon is now available from within tree-style menus.
(100) Improvement (03/31/10/JCJ/CIF): The ASCII and Excel imports/exports now include the Google Icon field within the location table.
(99) New Feature (03/31/10/JCJ/CIF): Add a new type of table, called an XYZ-Comment table has been added to the project database. This table will be used within later versions of the product.
(98) New Feature (03/31/10/JCJ): Added a new location field for the collar offset representing the distance down to the ground level for when the elevation represents a platform or collar height.
(97) Improvement (03/31/10/JCJ): The RESTORE command in RCL file will now only restore the project settings to default and not the global settings. (The user is logged out at the end of the RCL script if using network licensing)
(96) Improvement (03/31/10/JCJ): Two new RCL commands to adjust the project dimensions:
SCAN_BOREHOLES to scan all boreholes and
SCAN_ENABLED to scan enabled boreholes.
(95) Cosmetic (03/31/10/JCJ): Changed 'Log' to 'Borehole' on Borehole Manager File menu.
(94) Improvement (03/31/10/JCJ): Added error handling for blank data in Misc Table import (ASCII and Excel). Also added reporting of which line of input data is bad if there is an error.
(93) Improvement (03/31/10/JCJ/CIF): Symbol editors now appear with a single mouse click (versus a double mouse click).
(92) New Feature (03/31/10/JCJ): Added an import (ASCII and Excel) for Stratigraphy Tops. This will allow the import of bases or calculate the bases from the top of the next Stratigraphy layer.
(91) Improvement (03/31/10/JCJ): Added row numbers to the grid type reports and moved column units to the header for Lithology and Stratigraphy volumetric reports. Data-grid reports will now be cleared each time before being rewritten.
(90) Improvement (03/31/10/JCJ): Multiple profiles can now be saved in the database. This is similar to how Fences and Sections work. (Refactored the classes for improved cohesion)
(89) Improvement (03/26/10/MIW): RockWorks now saves polygons vertices in counterclockwise order when creating KML and KMZ files for Google Earth. This fixes sporadic problems when viewing exported files within Google Earth in which the polygons are displayed in "Absolute" or "Relative" elevation modes.
(88) New Feature (03/16/10/JCJ): A new program has been added for importing stratigraphy tops (and optionally bases) from a Comma Separated Values (CSV) file or Excel Spreadsheet. This importer follows along the line used for imports or I-Data, P-Data, etc. The Tops can be expressed as Elevations or Depths from the top of the borehole. If you are importing Tops the program can optionally calculate the Bases based on the next formationís Top. This new option is available from the Stratigraphy / Import sub-menu as well as the Stratigraphy Import button on the Stratigraphy tab. Note: This importer assumes vertical boreholes if you are importing elevations.
(87) New Feature (03/16/10/JPR): The Model, Profile, Section, Fence, and Plan Map programs within the Borehole Manager / Aquifers menu now provide an option for overriding the automatic grid naming convention by specifying a "root name". The suffixes of "_top.grd", "_base.grd", and "_isopach.grd" will be added to this root name when creating aquifer grids.
(86) Removal (03/16/10/JPR): All references to "Tessellation" within the Google Earth related programs have been removed. Instead, the program always tessellates polylines and polygons when creating Google Earth files. The tessellation is only used by Google Earth when diagrams are "clamped" to the ground.
(85) New Feature (03/12/10/MIW/JCJ/JPR/CIF): The Borehole Manager / Location tab now includes a special "Google Earth" icon that will be used when creating borehole location maps within Google Earth (see item #21 within the next quarters' [4/1/10-6/31/10] revision list).
Clicking on the Google Earth icon will present the user with a menu of available icons. Double-click on one of these icons to select it.
(84) Improvement (03/11/10/MIW): The Kriging algorithm's performance has been substantially improved for large data sets and dense grids by using multi-threading and quad trees to calculate the grid. In addition the Lag Stream performance has been increased by 1,000% by only performing calculations on distance qualified pairs. The following table shows some sample times (in milliseconds). Very small data sets will actually run slower (due to the quad-tree/tread management), but large data sets are radically improved.
|2-Treads (Dual Core Processor)|
(83) Removal (03/10/10/JPR): The "Decimals" option within the Borehole Manager / Map / Adjust Coordinates / Longitude/Latitude -> Easting/Northing option has been removed.
(82) Bug Fix (03/10/10/JPR): The UTM zone selection menu no longer hangs up with selected video cards (e.g. triple-monitors).
(81) Bug Fix (03/09/10/MIW): Blank file names in the tree-style menus now allow users to select a file for input or output.
(80) Enhancement (03/09/10/MIW): The mouse wheel (if you have one) may now be used to zoom in or out of an image within the Image Rectification Calibration window.
(79) Bug Fix (03/09/10/MIW): The Image Rectification program now rotates images in the proper direction.
(78) New Feature (03/09/10/MIW): Lithology, Stratigraphy, I-Data, T-Data, P-Data, Fractures, Water Levels and Well Construction can now be exported as ESRI 3D Shape files with data attributes for display and analysis in ArcScene. This new capability is accessed via the new Borehole Manager / Striplogs / Exports / 3D Shape Files menu.
Interval based data can be exported as PolylineZ or PointZ files.
Point data is calculated as the midpoint of an interval.
Missing Tops or Bases will be exported with a user specified null value.
Point based data only exports as PointZ files.
Once shape files have been added to ArcScene, the data can be queried and classified.
Example of stratigraphy segments displayed within ArcScene.
Example of color-coded gamma point data within ArcScene.
(77) Improvement (03/04/10/MIW): The RockPlot2D / Export / KML (Google Earth) program now includes an option for adjusting the overall opacity of all items within the overlay.
(76) Bug Fix (03/01/10/MIW): The RockPlot2D Clipping Utility now clips bitmaps to the size specified by the user.
(75) Bug Fix (02/25/10/MIW): Loading grids that only contain null values in RockPlot3D no longer give an Invalid Floating Point error.
(74) Bug Fix (02/24/10/MIW): Plotting I-Data in a 3D Borehole with the size based on a table now assigns the correct hot to cold colors based on the data range in the project.
(73) Improvement (02/23/10/MIW): Solid Resampling can now be done with a 2x2x2, 3x3x3 or 4x4x4 filter. The smaller filter is faster while the larger filters provide more smoothing. Filter based resampling is much faster than sector based resampling but may show some edge effects.
(72) New Feature (02/22/10/JCJ): The endpoint coordinates of profiles are now saved within the project database so that their names can be saved/remembered easily for use later and during subsequent exporting. This allows for repetitive profile creation, instead of having to export the menu settings of every profile or create an RCL script. The profiles (Profile Table) are saved similarly to how Fences (XY Pair Table) and Sections (XY Coordinate Table) are saved. The saved data includes the coordinates X1, Y1, X2, Y2, and Swath size and is limited to one row of data. The current profile data being used is still saved in the ini file. The user then uses the import and export menu to read from or save to alternate profiles.
(71) Improvement (02/22/10/MIW): The Grid Resampling can now be done using a 2x2, 3x3, or 4x4 filter. The smaller filter is faster while the larger filters provide more smoothing. Filter-based resampling is now significantly faster than sector-based resampling but may show some edge effects.
(70) Improvement (02/21/10/MIW): The Lithologic Closest Point solid modeling algorithm is now significantly faster thanks to a new point-searching method.
(69) Improvement (02/20/10/MIW): The Closest Point solid modeling algorithm is now significantly faster thanks to a new point-searching method.
(68) Improvement (02/19/10/MIW): The Closest Point solid modeling algorithm is now significantly faster thanks to a new point-searching method.
(67) Improvement (02/18/10/MIW): A new point searching algorithm has been added to the Closest-Point (Polyhedral) gridding algorithm thereby significantly improving the processing speed.
(66) Improvement (02/17/10/MIW): It is now possible to create a stratigraphic profile if a stratigraphic contact grid is missing. The previous version required that a grid exist for every stratigraphic top and bottom.
(65) Cosmetic (02/09/10/JCJ): The hint for the color column in the Striplog 2D designer now says Colors instead of Vector Text.
(64) Bug Fix (02/09/10/JCJ): Menus that created a report in a grid form were previously not clearing the grid if the report was recreated. The grid will now be cleared each time the Process button is clicked.
(63) New Feature (02/09/10/JCJ): The menu for the Color / Import / Comments -> Colors program has an additional option to choose a replacement color if the comment is blank or has no match in the Color Names table. The user can also choose to do nothing to the current color in this case.
(62) Bug Fix (02/09/10/JCJ): When the user imports project menu settings, the new settings are now being written back to the disk.
(61) Improvement (02/09/10/JCJ): The Land Grid table is now saved in within the system database. The import options for the Land Grid table have been adjusted to import into this table and added to the editor for this table.
(60) Bug Fix (02/09/10/JCJ): The download of the RockWare Landbase files no longer prompts the user to open it.
(59) Cosmetic (02/09/10/JCJ): The Widgets Menu is now expanded to allow selection of the Widgetís page. This makes the Widget menu item more consistent with the other top-level menu items.
(58) New Feature (02/09/10/JCJ): If RockWorks was closed with the Project Manager hidden, when RockWorks was restarted the user could not open it. The Project Manager now has a menu item on the Project menu to open/close it.
(57) Improvement (02/09/10/JCJ): In the Color System Filter dialog a warning was added that filter will be ignored if no Color System is selected for the filter.
(56) Improvement (02/09/10/JCJ): P-Text and I-Text imports from LogPlot no longer include the terminator (^) on the end of the line.
(55) Improvement (02/09/10/JCJ): The Color | Import | Raster Imagery -> Colors program (bitmaps_to_colors) now adjusts for the Header Base and Footer Top, as well as bad stored dimensions.
(54) Bug Fix (02/09/10/JCJ): When opening a RockWorks 14 project in RockWorks15 some users received a warning the Project Tables were missing even though they were created as RockWorks upgraded the project.
(53) Bug Fix (02/07/10/MIW): The Circle spacing for Rose diagrams with petals sized by cumulative length are now dynamically calculated.
(52) Bug Fix (02/07/10/MIW): The circle labels on the east and west limbs of the rose diagrams are now rotated 90 degrees.
(51) Bug Fix (02/07/10/MIW):
The P-Data Statistics Map and Export using the highest
value now finds the actual high value.
(50) Bug Fix (02/07/10/MIW): The 3-Point Calibration for Raster Images now appears correctly.
(49) Cosmetic (02/07/10/MIW): The status bar within the 3-Point Raster Image calibration now shows the global coordinates of the calibration point to be digitized.
∑ (48) Bug Fix (02/07/10/MIW): TSolid Models in RockPlot3D are no longer exported to a raster image when run in "stand-alone" mode.
(47) Cosmetic (02/06/10/JCJ): The hint for the color column in the Striplog 2D designer now says "Colors" instead of "Vector Text".
(46) Improvement (02/05/10/JCJ): When the user imported project menu settings, the new settings are now being written back to the disk.
(45) Improvement (02/04/10/JCJ): The Land Grid table is now saved in the system database. The import options for the Land Grid table have been adjusted to import into this table and added to the editor for this table.
(44) Cosmetic (02/03/10/JCJ): The download of the RockWare Landbase files no longer prompts the user to open it.
(43) Cosmetic (02/02/10/JCJ): Widgets Menu was expanded to allow selection of the Widgetís page. This makes the Widget menu item more consistent with the other top-level menu items.
(42) Improvement (02/01/10/JCJ): If RockWorks was closed with the Project Manager hidden, when RockWorks was restarted the user could not open it. The Project Manager now has a menu item on the Project menu to open/close it.
(41) Improvement (01/31/10/JCJ): The LogPlot importer P-Text and I-Text import no longer the terminates the line when a "^" is encountered.
(40) Improvement (01/30/10/JCJ): The Color / Import / Raster Imagery / Bitmaps->Colors program now adjusts for the Header Base and Footer Top, as well as bad stored dimensions.
(39) Bug Fix (01/29/10/JCJ): When opening a RockWorks 14 project in RockWorks15 some users received a warning the Project Tables were missing even though they were created as RockWorks upgraded the project.
(38) Improvement (01/28/10:MIW): The Delaunay Triangulation has been optimized for faster processing. Delaunay Triangulation is used by EZ-Map and the Triangulation gridding method.
(37) Bug Fix (01/28/10:MIW): Very large distances (sparse datasets) no longer cause some Inverse/Distance algorithms to assign null or 0 values incorrectly.
(36) New Feature (01/27/10:MIW): A new utility for creating animations (AVI files) of increasing and decreasing iso-level values within a block model has been added to the RockPlot3D program.
This option is available from the Scene Tree popup menu.
If the user selects a start or end value outside the models minimum and maximum value the start or end will be adjusted.
(35) New Feature (01/25/10:JCJ): The user can now specify how the boreholes are sorted. The user could add a field for the Operator of a well and then sort first by the operator and then the borehole name. Menu item is View | Change Sort of Boreholes.
(34) Bug Fix (01/25/10:JCJ): File / Import / Excel: When editing the location table from the Tab Manager, an exception no longer occurs when exiting the dialog.
(33) New Feature (01/25/10:JCJ): File / Import / Excel: A filtering ability for color systems in the Color Names table dialog was added. This allows the dialog to display only the color systems the user is working with. This filter is saved from session to session.
(32) Bug Fix (01/25/10:JCJ): File / Import / Excel: RockColors were not importing, now they do.
(31) New Feature (01/25/10:JCJ): An Import button was added to Color table tab.
(30) Bug Fix (01/25/10:JCJ): Utilities Map | Land Grid | Section Map used wrong columns (Easting and Northing were reversed).
(29) Bug Fix (01/25/10:JCJ): Bitmap and Aquifer tables were being left out of the recalc of XYZ values.
(28) New Feature (01/22/10:MIW): The Borehole Manager / Map / Borehole Locations program now includes a set of options that can be used to plot the borehole symbol at the base of the deviated and inclined boreholes.
Notice the symbols that are used to designate the TD's within the following example.
(27) New Feature (01/21/10:MIW): The Solid Model Export -> ASCII XYZG program now allows users to omit or replace null values within the model.
(26) Improvement (01/21/10:MIW): The Inverse Distance gridding (simple and sector-based) now uses "multi-threading" for faster processing. Improvements will only be noticeable on computers with multiple CPU's or multi-core technology. The more physical CPU cores that are available, the faster the modeling will go.
(25) Cosmetic (01/14/10:JPR): Tree menus are now initially displayed such that the menu is scrolled horizontally to the left. A handful of menus in previous versions would be slightly scrolled to the right (thereby hiding the expand/collapse buttons on the left) if the very first line extended beyond the right side of the tree window.
(24) Improvement (01/13/10:JPR): The sample database now includes downhole color data that corresponds to the lithology data. The diagram below depicts a color model based on this data.
(23) Improvement (01/12/10:JPR): The Borehole Manager / Colors / Comments-to-Color program no longer asks for the type of conversion (i.e. Munsell vs. RockWare Color Names). Instead, the program can now tell the difference and automatically pick the proper color.
(22) New Feature (01/05/10:MIW): A voxel-style option has been added to the Color Model menu.
(21) New Feature (01/05/10:MIW): A color model display option has been added to the Project Manager.
(20) New Feature (01/04/10:JPR): A new program titled "Raster Imagery -> Colors" has been added to the new Borehole Manager / Colors / Import submenu.
This program scans the raster images that are stored within the bitmap table and averages the colors for each depth interval into a single number.
Sampling Intervals: There are two ways to sample and convert the raster information to color information;
All Data (Highest Resolution): The "All Data" option will compute the height represented by each row of pixels within the raster image. The average color for each row will then be stored within the Colors table.
User-Specified Intervals: The "User-Specified Intervals" option will compute the average color within rectangular regions (as specified by the designated sampling interval) and store the results within the Colors table. For example, if the "Sampling Interval" is set to 5.0, the program will start by sampling all the pixels that fill within a depth range from zero to five meters. The average color will be stored as Depth-1 = 0, Depth-2 = 4, Color = Average For Interval.
Apply to ...
All Boreholes: The color data (stored within the Colors table) for all boreholes will be erased and replaced by the averaged colors from the associated raster images (as defined within the Bitmaps table).
Currently Highlighted Borehole: The color data (stored within the Colors table) for the currently selected borehole will be erased and replaced by the averaged colors from the associated raster images (as defined within the Bitmaps table).
Images should be cropped such that only the uniformly illuminated regions will be scanned. For example, core images are commonly shadowed along the margins because the light source (flash) is typically located directly above the lens., Limiting the image to the most uniformly illuminated region will result in optimal color interpretation.
As the sampling interval is increased, the data becomes less useful, depending upon the vertical color variability.
(19) New Feature (01/04/10:JPR): A new option titled "Comments -> Color" has been added to the Borehole Manager / Colors / Import sub-menu.
This program is used to read text within the new Color table and convert these comments from either Munsell or color names to Windows colors. These colors are then added to the "Color" column within the Color table.
The "Munsell Soil Codes" option will use the new Munsell "looup table" to convert any comments that contain Munsell codes into the corresponding color as shown by the following example;
The "RockWare Color Names" option will use the new RockWare color "lookup table" to convert any comments that contain RockWare color names into the corresponding color as shown by the following example;
(18) New Feature (01/04/10:JPR): A new program titled "Vertical Images -> Color Model" has been added to the new Imagery menu (see item #58 below).
The usefulness of this new capability is best illustrated by a case-study involving GPR data.
Creating a Solid Model From GPR (Ground Penetrating Radar) Profile Images
We start with five bitmaps that represent GPR profiles as shown below. These profiles were interpreted (aka "doctored") within a paint program to highlight salient features (e.g. a zone of stratigraphic disturbance associated with a buried object).
The image names and corner-point coordinates were then stored with the RockWare Utilities datasheet as shown below.
The Imagery / Vertical Images -> 3-D Panels program was then used to display the images in three-dimensions.
The Imagery / Vertical Images -> X/Y/Z/Color program was then used to converted selected pixels within the GPR images to control points (see diagram below). This program also plots the extracted control points as color-coded spheres. Note: This step is typically unnecessary when creating a model (since the modeling also performs the necessary image-to-control-point extraction). It has been included here in order to illustrate the relationship between the control points and the original imagery.
Next, the Imagery / Vertical Images -> Color Model program was used to create a solid model by using a anisotropic inverse-distance algorithm.
The next step was to set the model filter to the color of interest (yellow) and view the disturbed region (below). Note the volume (19 million cubic meters) represented by the yellow region.
The next step was to append the original GPR profiles with the filtered model. In the diagram below, the western panel has been hidden and the panel transparency has been set to 40%.
The diagram below depicts the northern GPR image and the "disturbed" portion of the model at a 3x vertical exaggeration.
(17) New Feature (01/04/10:JPR): A new program titled "Vertical Images -> X/Y/Z/Color" has been added to the new Imagery menu (see item #58 below).
This program creates a table of X/Y/Z/Color points based on images within the RockWare Utilities datasheet. The input is identical to that used for the Vertical Imagery -> 3D Panels program. In addition to creating the X/Y/Z/Color table, the program may also be used to create a diagram depicting the selected pixels as color-coded spheres as shown below;
The purpose of this program is to create X/Y/Z/Color tables that can be used as control points for subsequent modeling. The menu options are described as follows;
Pixel Sampling Intervals: Converting every pixel to a control point will typically result in a control point array that is huge thereby creating memory and/or execution speed problems. The Point Sampling Intervals allow the user to create a reasonable sized data set.
X (Horizontal) Sampling Frequency: This setting determines how often, on a horizontal/column basis, the image pixels will be sampled. For example, a setting of 1 will sample every pixel whereas a setting of 5 will cause the program to sample every fifth pixel.
Y (Vertical) Sampling Frequency: This setting determines how often, on a vertical/row basis, the image pixels will be sampled. For example, a setting of 1 will sample every row of pixels whereas a setting of 5 will cause the program to sample every fifth row.
Ignore Specified Color: It may be desirable that certain colors be ignored when converting image pixels to control points. For example, the black borders and patterns within the example above will create undesirable effects within the final model. This filter allows the user to ignore any pixels that fall within a specified color range.
Color: This is the color that will be ignored.
Tolerance: In the example above, black is the color that is to be ignored, but there may be pixels that are nearly black (e.g. dark gray). The tolerance setting provides a means for expanding the range of the filter to include colors that are similar to the desired color.
Decimal Places: The number of decimal places within the X/Y and Z coordinates that are shown within the output report are specified within the following sub-options.
X/Y Coordinates: Number of decimal places to show within the X and Y coordinates in the output report.
Z Coordinates: Number of decimal places to show within the Z coordinates in the output report.
Create Diagram: If you want to create a diagram depicting the X/Y/Z/Color data as color-coded spheres (see example above), check this box.
Sphere Radius: The radii of the color spheres are specified as a percentage of the project dimensions (i.e. the distance from the southwestern corner of the project to the upper northeast corner).
(16) New Feature (01/04/10:JPR): A new option titled "Color Plan" has been added to the Borehole Manager / Colors menu.
This new program is used to create a 2-dimensional plan view map at a specified elevation within a color model.
Note: The color-converter program will copy the currently selected Windows 32-bit color number to the Windows clipboard so that selected colors can be copied back to other applications. In other words, we're figuring that you're using this program to look up a color for some other RockWorks application.
(15) New Feature (01/04/10:JPR): A new option titled "Surface Map" has been added to the Borehole Manager / Colors menu.
This new program is used to display the predicted color at any point on a designated surface model.
(14) New Feature (01/04/10:JPR): A new option titled "Fence" has been added to the Borehole Manager / Colors menu.
This program us used to create fence diagrams based on the new color models. The menu options for the Color Fence program are identical to the other Fence Diagram menus within RockWorks.
The Colors / Fence menu is very similar to the other fence diagram menus within RockWorks with exception of the "Color Range Filter". This option will render all colors outside of the user-specified range to be transparent.
(13) New Feature (01/04/10:JPR): A new option titled "Section" has been added to the Borehole Manager / Colors menu.
This program will create color sections based on the new downhole color data. The menu options for the modeling are identical to those for the new color modeling (see Revision #47 below) while the other menu items are identical to those used by other sectioning programs (e.g. I-Data / Profile, P-Data / Profile, etc.).
Note: When creating a color section with colored intervals, be sure to set the Color Scheme to "Direct". Otherwise, the colors will look something like the diagram below.
(12) New Feature (01/04/10:JPR): A new option titled "Profile" has been added to the Borehole Manager / Colors menu.
This program will create color profiles based on the new downhole color data. The menu options for the modeling are identical to those for the new color modeling (see Revision #47 below) while the other menu items are identical to those used by other profiling programs (e.g. I-Data / Profile, P-Data / Profile, etc.).
Note: When creating a color profile with colored intervals, be sure to set the Color Scheme to "Direct". Otherwise, the colors will look something like the diagram below.
(11) New Feature (01/04/10:JPR): The Borehole Manager / Colors / Model program now includes options for filtering the model such that nodes outside of a color range will be assigned a null value (-1.0e27) and therefore rendered invisible.
To use this filter, check the box labeled "Color Range Filter", click on the "Desired Color" button, select the color that you're interested in, and then specify the "Tolerance". Tolerance, is expressed as a percentage whereby 100 corresponds to all possible colors while zero would limit the visible voxels to only those that have exactly the same color value. Notice how a 20% tolerance within the example results in a diagram that shows tan/gray regions within the model.
In addition, the volume of non-null nodes is listed within the RockPlot3D data tree as shown below.
The new color capabilities within RockWorks are designed for color-sensitive applications such as clay mining, dimension-stone mining (e.g. limestone facing), and geochemical color alteration exploration. As far as we know, RockWorks is the only product with this capability, but we're sure to see these techniques proliferate throughout the marketplace as our competitors continue to brazenly steal our ideas just like they've been unabashedly doing during the last 27 years. Some people have no shame.
(10) Case Study (01/04/10:JPR): Creating a Color Model From Outcrop Images
This case study shows how images can be used to create a color model. The study area is an excavation in Nicosia, Cyprus where a series of digital photographs were made from the inside of a rectangular excavation. Pseudo-boreholes were created by cutting out strips from these images and saving the strips within the Bitmaps table. These strips were then converted to colors (see Revision #45 below) and modeled with the new color-modeling algorithm option (see Revision #36 below).
A series of digital photographs of the interior walls were taken from inside the excavation. These images were then stitched together into four panoramas. Twelve 200 pixel-wide pseudo-logs were then extracted from the panoramas and saved within the RockWorks Borehole Manager bitmap table as summarized within the following diagram.
The four panoramas were then plotted in 3D using the RockWorks Grafix / 3D-Utilities / Images / Vertical Panels program. The borehole bitmaps were then converted to color intervals via the new Raster Imagery -> Colors program (see Revision #45 below) and plotted as 3D striplogs. Finally, a color model was created based on the data within the color table. The results are shown within the following diagram.
(9) New Feature (01/04/10:JPR): A new option titled "Model" has been added to the new Color menu category within the Borehole Manager.
The new color modeling option will read the data from the new Colors table (see Revision #38 below) and generate a block model in which the interpolated node values represent color (see Revision #36 below).
Note: The "G = Color" setting within the Spatial Filtering Options submenu will be automatically set to "True" when creating a color model. In other words, it's not a problem if you forget to set the "G = Color" option within the Spatial Filtering Options sub-menu because the program will automatically do it when creating a color model.
Note: The tire required to create a color model will be three times longer than conventional modeling due to the fact that three separate iterations are required for the red, green, and blue components.
(8) Cosmetic (01/04/10:JPR): A new category titled "Color" has been added to the main menu bar within the Borehole Manager.
This menu category will be used for applications that process data within the new Colors table (see Revision #38 below).
(7) New Feature (01/04/10:MIW): A new type of entity, called a "Color Model" has been added to the RockPlot/3D program. This new capability has been added for displaying solid models that contain color data as described within Revision #36 (see below).
The display options for color-based block models are limited to voxels and points (no isosurfaces).
(6) New Feature (01/04/10:JPR): The Solid Modeling Options menu now includes an option titled "G = Color".
This new option is used to create solid models in which the node values represent color. These color numbers used the WDC (Windows Decimal Color) scheme. WDC colors range from zero (black) to 16,777,216 (white).
Note: Displaying a solid model that is based on WDC colors requires that the user set the new "color scheme" to the new "Direct (Node Value = Color)" setting (see Revision #37 above).
Note: Color-based modeling should not be used in conjunction with the "distance-to-point" algorithm.
Note: The time required to create a color model will be three times longer than conventional modeling due to the fact that three separate iterations are required for the red, green, and blue components.
(5) New Feature (01/04/10:JPR): The Color Scheme menu now includes an option titled "Direct (Node Value = Color)".
This new option is specially designed to plot grid models that represent color models as described within Revision #33 (below).
Note: When plotting color maps based on color grids, be sure to turn off the legend plotting. It just doesn't make any sense (i.e. the colors represent the colors rather than colors representing numbers such as geochemical values or elevations).
(4) New Feature (01/04/10:JPR): The Gridding Options menu now includes an option titled "Z = Color".
This new option is used to create grid models in which the node values represent color. Here's how it works; Typically, colors are expressed as three values such as red/green/blue, or hue/chroma/saturation. Using three numbers to represent a color obviously too cumbersome from a user-interface standpoint. Instead, RockWorks uses the Microsoft Windows scheme whereby colors are stored as a single WDC (Windows Decimal Color) number that can be converted to RGB (Red, Green, Blue) via a somewhat convoluted process. The WDC colors range from zero (black) to 16,777,216 (white). This is the scheme that is used when saving color data within the RockWorks datasheet. For example, if you change a color column to text, you'll see the WDC color numbers. Unfortunately, creating a grid of color values is not possible using a single number such as the WDC code. To circumnavigate this problem, RockWorks converts the WDC colors into their red/green/blue constituents as part of a special color-only gridding process that works in conjunction with the selected gridding algorithm. The net result is a special grid model in which the node values represent the WDC number.
Note: Color-contouring a grid that has been generated with the "Z=Color" option turned on requires that the user set the new "color scheme" to the new "Direct (Node Value = Color)" setting (see Revision #34 above).
Note: Color-gridding makes no sense when used in conjunction with the "distance-to-point", "cumulative", and "sample-density" algorithms. So don't do it.
Note: The time required to create a color model will be three times longer than conventional modeling due to the fact that three separate iterations are required for the red, green, and blue components.
(03) New Feature (01/04/10/JPR): Two-dimensional striplogs now include options for plotting borehole titles at the top and/or bottom of the striplogs.
Notice how the labels are automatically rotated (i.e. not upside down) for boreholes that are drilled upwards (i.e. underground drilling).
(02) New Feature (01/03/10/JPR): Two-dimensional striplogs now include an option for plotting borehole symbols at the top and/or bottom of the striplogs.
This new capability provides a way to know, at a glance, what type of borehole is being depicted (e.g. blast holes, injection wells, dry holes, recovery wells, monitor wells, etc.).
Borehole symbols may be plotted at the tops and/or bottoms of the boreholes.
Note: If borehole symbols are being plotted at the top of the logs, the title offset will be relative to the center of the borehole symbol rather than the top of the log.
(01) New Feature (01/02/10/JPR): Programs that generate profiles that include striplogs now include an option for showing the distance from the borehole collar to the profile along the top of the diagram.
The collar distance options include the following options:
The three label orientation options are depicted within the following diagram:
This new capability applies to the following programs:
Striplogs / Profile
Aquifers / Profile
Color / Profile
Fractures / Profile
Grid / Profile
I-Data / Profile
Lithology / Profile
P-Data / Profile
Solid / Profile
Stratigraphy / Profile
T-Data / Profile
Previous Quarter (4/09)