Difference between revisions of "DSP"

From BRL-CAD
(Creating a DSP object from manual or programmatic generation of data)
(Creating a DSP object from manual or programmatic generation of data)
Line 117: Line 117:
 
== Creating a DSP object from manual or programmatic generation of data ==
 
== Creating a DSP object from manual or programmatic generation of data ==
  
Now let's consider a more practical example and a real test of BRL-CAD.  We can import topological data
+
Now let's consider a more practical example and a real test of BRL-CAD.  We can import topological data and produce a realistic ground surface.  There are many free sources of such data.  See this site for a start:
and produce a realistic ground surface.  There are many sources of such data.   
 
See this site for a start:
 
  
 
http://www.naturalgfx.com/free_topo_gis.htm
 
http://www.naturalgfx.com/free_topo_gis.htm
Line 129: Line 127:
 
We downloaded the zip archive 'ned_19_arc.zip' and unzipped in its own directory:
 
We downloaded the zip archive 'ned_19_arc.zip' and unzipped in its own directory:
  
  $ mkdir ned_19_shapefile
+
  $ mkdir ned_19_usa_arcgis_shapefile
  $ mv ned_19_arc.zip ned_19_shapefile
+
  $ mv ned_19_arc.zip ned_19_usa_arcgis_shapefile
  $ cd ned_19_shapefile
+
  $ cd ned_19_usa_arcgis_shapefile
 
  $ unzip ned_19_arc.zip
 
  $ unzip ned_19_arc.zip
 
  Archive:  ned_19_arc.zip
 
  Archive:  ned_19_arc.zip

Revision as of 19:08, 7 June 2012


Displacement (DSP) map primitive

Creating a DSP object from miscellaneous images

We will use two examples to illustrate the next few sections.

1. A black and white (gray scale) image (png format):

File:Class65-150h.png

with properties:

$ file Class65-150h.png
Class65-150h.png: PNG image, 142 x 150, 8-bit gray+alpha, non-interlaced

2. A color png file:

File:Cs-24-150h.png

with properties:

$ file Cs-24-150h.png
Cs-24-150h.png: PNG image, 152 x 150, 8-bit/color RGBA, non-interlaced

Preparing your height field data

The DSP takes unsigned short (16-bit) integer data. Our various command-line data converters can help bring data in from pretty much any existing format, including image data, via various processing commands. If the data was in png image format, for example (which is basically 3-channel 8-bit integer data), the data could be prepared with a combination of 'png-pix', 'pix-bw', and 'cv'.

If you type the 'in' command, it will prompt you for each parameter individually and that should help some. For the DSP, the main parameters are: the source of the height data, the width (number of points in the Y direction) and length (number of points in the X direction) of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells (0 = do not interpolate, 1 = interpolate).

See the 'dsp_add' tool for combining two existing DSP data files into one.

A DSP primitive is an array of cells initially defined by points in the XY plane as positive heights from Z = 0. The DSP can then be transformed to other orientations and positions. The number of cells is (numX * numY).

The data format for the DSP primitive is network-ordered unsigned short integers (nu16). BRL-CAD has a couple of dozen tools that you can use for converting existing data into that raw format, such as the 'cv' command or the 'bw-d' and 'd-u' commands among other similar tool chains. If you use the cv command, the output format is "nus" for network unsigned shorts.

Using the two examples to convert the data to dsp format.

Example 1.

Convert it to a bw file (one pixel is one unsigned char):

$ png-bw Class65-150h.png > Class65-150h.bw

View the result:

$ bw-fb -w142 -n150 Class65-150h.bw

Convert it to the format required for a dsp file (nu16):

$ cv huc nu16 Class65-150h.bw Class65-150h.dsp

Example 2.

Convert it to a pix file (one pixel is defined by three unsigned chars):

$ png-pix Cs-24-150h.png > Cs-24-150h.pix

View the result:

$ pix-fb -w152 -n150 Cs-24-150h.pix

Convert it to a bw file (one pixel is one unsigned char):

$ pix-bw Cs-24-150h.pix > Cs-24-150h.bw

View the result:

$ bw-fb -w152 -n150 Cs-24-150h.bw

Convert it to the format required for a dsp file:

$ cv huc nu16 Cs-24-150h.bw Cs-24-150h.dsp

Importing DSP data into a .g file

Example 1.

In mged create a dsp object:

mged> in dsp.s dsp f Class65-150h.dsp 142 150 0 ad 1 0.005

Example 2.

In mged create a dsp object:

mged> in dsp2.s dsp f Cs-24-150h.dsp 152 150 0 ad 1 0.005

Rendering your DSP

Example 1.

mged> B dsp.s
mged> ae 45 45
mged> rt

You should see something like this:

Dsp.png

You can play around with the scaling factors (the end pair: 1 - cell width, 0.005 - cell height) to improve the looks of the image.

Example 2.

mged> B dsp2.s
mged> ae 45 45
mged> rt

You should see something like this:

Dsp2.png

Again, you could play with various parameters to get the desired look.

Creating a DSP object from manual or programmatic generation of data

Now let's consider a more practical example and a real test of BRL-CAD. We can import topological data and produce a realistic ground surface. There are many free sources of such data. See this site for a start:

http://www.naturalgfx.com/free_topo_gis.htm

We started with shape file data for the US from:

http://seamless.usgs.gov/data_availability.php?serviceid=Dataset_19

We downloaded the zip archive 'ned_19_arc.zip' and unzipped in its own directory:

$ mkdir ned_19_usa_arcgis_shapefile
$ mv ned_19_arc.zip ned_19_usa_arcgis_shapefile
$ cd ned_19_usa_arcgis_shapefile
$ unzip ned_19_arc.zip
Archive:  ned_19_arc.zip
  inflating: ned_19_arc.dbf          
  inflating: ned_19_arc.pdf          
  inflating: ned_19_arc.prj          
  inflating: ned_19_arc.sbn          
  inflating: ned_19_arc.sbx          
  inflating: ned_19_arc.shp          
  inflating: ned_19_arc.shp.xml      
  inflating: ned_19_arc.shx          
  inflating: ned_19_arc.txt          
  inflating: ned_19_arc.xml          
  inflating: NED_DataDictionary2006.pdf  

[TO BE CONTINUED]