Difference between revisions of "DSP"

From BRL-CAD
(stub in some initial infor for the dsp primitive, pulled from content written elsewhere)
 
(mini outline stub)
Line 1: Line 1:
 +
[[category:tutorials]]
 +
 +
= Displacement (DSP) primitive=
 +
 +
== Creating a DSP object ==
 +
 +
== Preparing your height field data ==
 +
 
The data format for the DSP primitive is network-ordered unsigned short integers.  BRL-CAD has a couple 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.
 
The data format for the DSP primitive is network-ordered unsigned short integers.  BRL-CAD has a couple 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.
  
Line 4: Line 12:
  
 
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 width/length of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells.
 
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 width/length of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells.
 +
 +
See the dsp_add tool for combining two existing DSP data files into one.
 +
 +
== Importing DSP data into a .g file ==
 +
 +
== Rendering your DSP ==

Revision as of 01:57, 22 January 2012


Displacement (DSP) primitive

Creating a DSP object

Preparing your height field data

The data format for the DSP primitive is network-ordered unsigned short integers. BRL-CAD has a couple 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.

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 width/length of the input data, width/length/height scaling factors, and whether to smoothly interpolate between cells.

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

Importing DSP data into a .g file

Rendering your DSP