Need more planning before attempting any major rework of this sort. (svn branch delete)

svn:revision:68259 svn:branch:multiproj svn:account:starseeker
More refactor work.
2016-07-12 16:25:55 +00:00 · 2016-04-19 00:33:15 +00:00 · 2016-04-18 18:02:47 +00:00 · 2016-04-18 17:49:30 +00:00 · 2016-04-18 16:39:10 +00:00 · 2016-04-18 15:17:41 +00:00
3397 changed files with 745382 additions and 156913 deletions
@@ -1,4 +1,3 @@
 /bin
 /lib
 /build
-/testing
@@ -279,7 +279,6 @@ Schueler, Betty J.

 Edwards, Eric
 SURVICE Engineering, Inc.
-Open Source (Doc Camp)

 Kregel, Dwayne
 SURVICE Engineering, Inc.
@@ -335,37 +334,6 @@ Perez, Alex
 2012 November
 Open Source (GCI)

-Singh, Harmanpreet
-nicknames harmanpreet
-2013 October
-Open Source (Doc Camp)
-
-Kamga, Isaac
-nicknames Izak, iiizzzaaakkk
-2013 October
-Open Source (Doc Camp)
-
-Check, Nyah
-nicknames Ch3ck
-2013 October
-Open Source (Doc Camp)
-
-Scott Nesbitt
-2013 October
-Open Source (Doc Camp)
-
-Wood, David
-2013 November
-Open Source (GCI)
-
-Agarwal, Yatharth
-2013 November
-Open Source (GCI)
-
-McDonald, Rob
-2013 November
-Open Source
-
 Tannous, Marc
 2014 December
 Open Source (GCI)
@@ -513,7 +481,6 @@ nicknames mjgillich mgillich
 U.S. Army Research Laboratory

 Howard, Doug
-nicknames dhoward
 SURVICE Engineering, Inc.
 2006 April

@@ -569,7 +536,7 @@ nicknames homovulgaris, madant
 Open Source (GSoC)

 Saunders, Benjamin
-nicknames Ralith, ralith
+nicknames Ralith
 2008 July
 Open Source

@@ -609,10 +576,6 @@ Jain, Sachin
 2011 April
 Open Source

-Gerstner, Nick
-2011 May
-SURVICE Engineering, Inc.
-
 Easterbrook, Zach
 nicknames lainiwakurax
 2011 July
@@ -743,12 +706,12 @@ nicknames avneetkhalsa
 Open Source (GSoC)

 Daga, Mohit
-nicknames zero_level, mohitdaga
+nicknames zero_level
 2013 June
 Open Source (GSoC)

 Kamga, Isaac
-nicknames Izak, iiizzzaaakkk
+nicknames Izak
 2013 July
 Open Source (GSoC)

@@ -777,7 +740,6 @@ Schulte, Johannes
 Open Source (GCI)

 Amidon, Peter
-nicknames peter-sa, Andromeda Galaxy
 2013 November
 Open Source (GCI)

@@ -794,7 +756,7 @@ nicknames huskmate13
 2014 January
 Open Source

-Granroth, Gustave
+Gustave Granroth
 2014 May
 Open Source

@@ -983,7 +945,7 @@ Thomas, Balbir
 Open Source

 Remenak, Daniel T.
-nicknames DTRemenak, Erroneous, dtremenak
+nicknames DTRemenak, Erroneous
 2005 July
 California Institute of Technology
 Open Source
@@ -77,7 +77,7 @@ and with @DEPRECATED in source code comments.  Where users are not
 adversely affected, a run-time DEPRECATION statement may be printed.

 Whenever published functionality is finally removed, move its entry
-from the DEPRECATED section below to the REMOVED section for the
+from the DEPRECATED section below to the OBSOLETE section for the
 version in which it was removed.  Make sure the entry retains a
 reference to the version in which the item was marked as deprecated.

@@ -112,80 +112,32 @@ calls that can be updated must be updated at that time.
 The items listed below are interfaces that are deprecated.  They are
 categorized by the release in which the change was made.  If the
 change involved a removal of a command or function, both the original
-and new names should be listed for reference.  If an item is marked
-with a "'" (single quote), that means it was not documented and may be
-removed at any time.
+and new names should be listed for reference.


 7.26
 ----
-ray tracing tools
-	lgt : functionally replaced by nirt
-	rtcell', rtfrac', rtpp, rtrad', rtrange, rtray, rtregis, rtsil'
-	Removed as part of distillation effort [deprecated 7.26]
-converter tools
-	cy-g, euclid-g, euclid_format', euclid_unformat', g-euclid,
-	g-euclid1', g-tankill, intaval-g.py, viewpoint-g : obsolete formats
-	plot3-X, plot3-hpgl, plot3-tek : obsolete interface, see overlay command
-	plot3debug, xyz-plot3 : see plot3-asc,asc-plot3
-	bot-bldxf', bot_shell-vtk, g-nmg, nmg-bot, nmg-rib, nmg-sgp',
-	poly-bot, rt_bot_faces, : primitive-specific converters
-	Removed as part of distillation effort [deprecated 7.26]
-image tools
-	cmap-fb, fb-cmap, fbcmrot : colormap support obsolete
-	fbed, cell-fb : outside scope
-	fbscanplot, polar-fb, pp-fb, bw-imp, pixinfo.sh : obsolete
-	png_info : incorporating into icv
-	pixpaste : outside scope, license
-	alias-pix' : incorporating into icv
-	asc2pix' : incorporating into icv
-	pix-yuv', yuv-pix' : obsolete non-standard format
-	texturescale : obsolete implementation
-	Removed as part of distillation effort [deprecated 7.26]
-video & animation tools
-	anim_*', fbanim, chan_add', chan_mult, chan_permute,
-	pixflip-fb' : outside scope
-	pixfields', pixfieldsep' : outside scope
-	orbit.sh, rtwalk, scriptsort, script-tab', tabinterp, tabsup,
-	azel, bary
-	Removed as part of distillation effort [deprecated 7.26]
-signal analysis tools
-	a-d', d-a', bw-a', i-a', u-a' : incorporating into cv
-	d-a', d-bw', d-f', d-i', d-u' : incorporating into cv
-	a-d', bw-d', c-d', f-d', i-d', u-d' : incorporating into cv
-	f-d', f-i', d-f', i-f', u-f', u-bw' : incorporating into cv
-	d2-c', double-asc' : incorporating into cv
-	Removed as part of distillation effort [deprecated 7.26]
-infrared & shapefactor tools
-	all_sf', if-X, ifdisp, pictx, showterm, firpass, secpass, shapefact
-	ssamp-bw, ssampview', ssampview.tcl'
-	Removed as part of distillation effort [deprecated 7.26]
-misc tools
-	fix_polysolids' : obsolete primitive
-	remapid : superseded by reid+remat
-	buffer : unnecessary network/stream buffering tool
-	hex : superseded by hexdump
-	Removed as part of distillation effort [deprecated 7.26]
-include/bu/ptbl.h
-        BU_PTBL_BASEADDR, BU_PTBL_LASTADDR, BU_PTBL_END
-        Removed as private implementation detail [deprecated 7.26
 include/bu/hash.h
 	bu_hash_tbl_find, bu_set_hash_value, bu_get_hash_value, bu_get_hash_key,
-	bu_hash_tbl_add, bu_hash_tbl_print, bu_hash_tbl_free, bu_hash_tbl_first,
-	bu_hash_tbl_next, bu_hash_tbl_traverse, public structs bu_hash_entry and
-	bu_hash_tbl will be made private.
-	Replaced with new API [deprecated 7.26]
+        bu_hash_tbl_add, bu_hash_tbl_print, bu_hash_tbl_free, bu_hash_tbl_first,
+        bu_hash_tbl_next, bu_hash_tbl_traverse, public structs bu_hash_entry and
+        bu_hash_tbl will be made private.
+        Replaced with new API [deprecated 7.26]
+rtrad, bot_shell-vtk, rt_bot_faces, g-nmg, nmg-bot, nmg-rib, nmg-sgp, plot3-hpgl,
+plot3-tk, plot3-X, fix_polysolids, terrain, pixinfo.sh, png_info, dbcp, buffer,
+hex, bw-d, c-d, d-bw, d-f, d-i, d-u, f-d, f-i, i-d, -if, u-bw, u-d, u-f
+	remove obsolete commands [deprecated 7.26]
 include/bu/cmd.h
 	remove struct bu_cmdhist and struct bu_cmdhist_obj [deprecated 7.26]
 	BU_CMDHIST_NULL, BU_CMDHIST_OBJ_NULL, bu_cmdhist_histor, bu_cmdhist_add,
 	bu_cmdhist_curr, bu_cmdhist_nest, bu_cmdhist_prev [deprecated 7.26]
 fb-rle, rle-fb, bw-rle, pix-rle, rle-pix
-	All tools focused specifically on the RLE image format. [deprecated 7.26]
+        All tools focused specifically on the RLE image format. [deprecated 7.26]
 nirt
 	-T - use LIBRT_BOT_MINTIE environment variable instead [deprecated 7.26]
 all global variables
 	global variables are no longer considered published public API [deprecated 7.26]
-	bn_mat_identity -> MAT_INIT_IDN or MAT_IDN() or NULL
+        bn_mat_identity -> MAT_INIT_IDN or MAT_IDN() or NULL
 include/bn.h
 	tp_setup, no longer needs to be public API [deprecated 7.26]
 include/raytrace.h
@@ -195,48 +147,31 @@ include/raytrace.h
 	tcl_list_to_fastf_array *_tcl_*, removal of all tcl-specific
 	API functions [deprecated 7.26]
 	db_regexp_match_all() -> db_ls() [deprecated 7.26]
-include/rt/solid.h
-	shouldn't be public API - this level of detail belongs inside the display
-        manager [deprecated 7.26]
-include/ged/defines.h
-	remove struct ged_drawable -  shouldn't be public API [deprecated 7.26]
-	remove freesolid from struct ged - exposes struct solid [deprecated 7.26]
-include/ged/view.h
-	remove current forms of dl_erasePathFromDisplay and invent_solid - they
-	expose the struct solid type [deprecated 7.26]
 include/tclcad.h
 	tclcad_bn_mat_print tclcad_rt_parse_ray tclcad_rt_pr_cutter
 	tclcad_rt_pr_hit tclcad_rt_rt tclcad_rt_import_from_path, removal of all
-	tcl-specific API functions [deprecated 7.26]
+        tcl-specific API functions [deprecated 7.26]
 pixcut, pixpaste
-	copyright cleanup [deprecated 7.26]
+        copyright cleanup [deprecated 7.26]
 librt, fast4-g
 	removal of CLINE entity support [deprecated 7.26]
-mged
-	kill, killtree, killall, killrefs - replaced with rm command [deprecated 7.26]
-
-	rm comb obj1 obj2 comb1 ... -> new behavior: remove objects and empty combs from .g
-	original functionality replaced with rm comb/obj* comb/comb1 ... syntax [deprecated 7.26]
-
-	expand -> replaced by search -name <pattern> (previous docs indicating matching of
-	expand was regex were wrong - uses bu_fnmatch.) [deprecated 7.26]
-
-	pathlist, paths -> replaced by search [deprecated 7.26]
-burst
-	remove termlib-based interactive menu interface [deprecated 7.26]
+kill, killtree, killall, killrefs
+        replaced with rm command [deprecated 7.26]
+rm comb obj1 obj2 comb1 ... -> new behavior: remove objects and empty combs from .g
+        original functionality replaced with rm comb/obj* comb/comb1 ... syntax [deprecated 7.26]

 7.24
 ----
 fbed, pp-fb
-	removes termcap use, no known users [deprecated 7.24]
+        removes termcap use, no known users [deprecated 7.24]
 include/raytrace librt
-	db_full_path_list_add(), db_free_full_path_list() [deprecated 7.24]
-	db_search_formplan(), db_search_freeplan(), db_search_full_paths() [deprecated 7.24]
-	db_search_unique_objects(), struct db_full_path_list [deprecated 7.24]
+        db_full_path_list_add(), db_free_full_path_list() [deprecated 7.24]
+        db_search_formplan(), db_search_freeplan(), db_search_full_paths() [deprecated 7.24]
+        db_search_unique_objects(), struct db_full_path_list [deprecated 7.24]
 src/irprep
-	all_sf, firpass, ir-X, irdisp, pictx, secpass, shapefact, showterm [deprecated 7.24]
+        all_sf, firpass, ir-X, irdisp, pictx, secpass, shapefact, showterm [deprecated 7.24]
 include/raytrace.h librt
-	RT_DBHASH and RT_DBNHASH [deprecated 7.24]
+        RT_DBHASH and RT_DBNHASH [deprecated 7.24]

 7.22
 ----
@@ -245,7 +180,9 @@ include/raytrace.h librt
 	RT_GET_TREE -> BU_GET [deprecation 7.22]
 	RT_FREE_TREE -> BU_PUT [deprecation 7.22]
 include/bu.h
-	bu_parse_mm() [deprecated 7.22]
+        bu_parse_mm() [deprecated 7.22]
+librtserver
+        becoming stand-alone project, removes optional java dependency [deprecated 7.22]
 mged
 	em, e_muves, l_muves, lm, read_muves, and t_muves MUVES-specific commands [deprecated 7.22]

@@ -285,6 +222,8 @@ db.h
 	rt_fastf_float() -> ntohf() [deprecated 7.18]
 	rt_mat_dbmat() -> htonf() [deprecated 7.18]
 	rt_dbmat_mat() -> ntohf() [deprecated 7.18]
+dbcp
+	dbcp -> dd [deprecated 7.18]
 mged
 	?(*) -> ? -(*) [deprecated 7.18]
 	apropos(*) -> apropos -(*) [deprecated 7.18]
@@ -353,46 +292,31 @@ include/raytrace.h
 	struct hit.hit_normal -> RT_HIT_NORMAL [deprecated pre-7.0]


-***********
-* REMOVED *
-***********
+************
+* OBSOLETE *
+************

-Below are the interfaces that have followed deprecation policy or were
-deemed minimally impacting and, regardless, are now no longer a part
-of BRL-CAD.
+Below are the interfaces that have followed deprecation policy and are
+now no longer a part of BRL-CAD.

 7.26.0
 ------
-dbcp
-	dbcp -> dd [deprecated 7.18]
-pov (mged)
-	removed, undocumented command with many alternatives [minimally impacting]
-polybinout (mged)
-	removed, undocumented command, use plot [minimally impacting]
-pl (mged)
-	removed, use plot [minimally impacting]
 conf.h
 	removed - replaced with common.h [deprecated 7.0]
-UtahRLE image tools
-	no longer installed by default with BRL-CAD - not used directly by
-	BRL-CAD tools [minimally impacting]
-Tcl in libbu and libbn
-	no longer utilize or require Tcl [dependency eliminated]
-Tcl/Tk man pages
-	no longer installed by default with BRL-CAD when the bundled Tcl/Tk is used
-	to build [minimally impacting]
+libbu, libbn
+        no longer utilize or require Tcl [7.26 architecture change]
 include/dg.h
-	implementation detail no longer being exposed, use libged [deprecated 7.22]
+        implementation detail no longer being exposed, use libged [deprecated 7.22]
 autogen.sh && configure
 	GNU Autotools build system -> CMake build system [deprecated 7.20]
 Dunn camera and Canon printer tools
-	dunncolor [deprecated 7.16]
-	dunnsnap [deprecated 7.16]
-	canonize [deprecated 7.16]
+	dunncolor [ deprecated 7.16 ]
+	dunnsnap [ deprecated 7.16 ]
+	canonize [ deprecated 7.16 ]
 genptr_t/GENPTR_NULL
 	genptr_t -> void* [deprecated 7.16]
 include/bu.h
-	bu_argv0() -> bu_basename(bu_argv0_full_path(), NULL) [deprecated 7.16]
+	bu_argv0() -> bu_basename(bu_argv0_full_path()); [deprecated 7.16]
 include/dm_color.h
 	dm_color.h -> dm.h [deprecated 7.14]
 include/fb.h
@@ -420,9 +344,9 @@ mged
 	-n option -> -c option [deprecated 7.14]
 	per_line [deprecated 7.14]
 SGI-specific tools
-	pl-sgi -> pl-fb [deprecated 7.16]
+	pl-sgi -> pl-fb [ deprecated 7.16 ]
 src/gtools
-	g_diff, g_lint, g_qa, g_transfer -> gdiff, glint, gqa, gtransfer [deprecated 7.14]
+	g_[toolname] -> g[toolname] [deprecated 7.14]
 src/librt/cmd.c
 	rt_split_cmd() -> bu_argv_from_string() [deprecated 7.12]
 any-png.sh
@@ -437,9 +361,6 @@ pixread.sh
 	obsolete hardware [deprecated 7.16]
 sgisnap.sh
 	obsolete hardware [deprecated 7.16]
-librtserver and Java Native Interface (JNI) bindings
-	removed, unused and undocumented, modern approach would be to
-	use a tool such as swig to generate bindings [minimally impacting]

 7.24.2
 ------
@@ -1073,23 +994,23 @@ s/bu_count_path(.*)\);/bu_dir_list\1, NULL);/g
 	made bu_dir_list() return the number of entries [7.21]
 s/bu_strcmpm\((.*),([^,]*)\)/bu_strcmp(\1)/g
 	no use for label parameter, convert to bu_strcmp() [7.21]
-	bu_set_realtime() [deprecated 7.22]
+        bu_set_realtime() [deprecated 7.22]

 7.24
 ----
 s/bu_set_realtime\([[:space:]]\);//g
-	didn't do anything [7.23]
+        didn't do anything [7.23]
 s/.*bu_cpulimit_[sg]et\([[:space:]]\);//g
-	didn't do anything [7.23]
+        didn't do anything [7.23]
 s/rt_g\./RTG\./g
-	renamed rt_g global to RTG so it doesn't match the struct name [7.24]
+        renamed rt_g global to RTG so it doesn't match the struct name [7.24]
 s/rt_functab\[/OBJ\[/g
-	renamed rt_functab global to OBJ so it doesn't match the struct name [7.24]
+        renamed rt_functab global to OBJ so it doesn't match the struct name [7.24]
 s/redraw_vlist/draw/g
-	removed redraw_vlist mged command, just call draw or refresh [7.24]
+        removed redraw_vlist mged command, just call draw or refresh [7.24]
 s/RT_BADNUM/INVALID/g
 s/RT_BADVAL/VINVALID/g
-	moved RT_BADNUM and RT_BADVEC to vmath.h as INVALID and VINVALID [7.24]
+        moved RT_BADNUM and RT_BADVEC to vmath.h as INVALID and VINVALID [7.24]
 s/bu_create_hash_tbl/bu_hash_tbl_create/g
 s/bu_find_hash_entry/bu_hash_tbl_find/g
 s/bu_hash_add_entry/bu_hash_tbl_add/g
@@ -1098,7 +1019,7 @@ s/bu_hash_tbl_pr/bu_hash_tbl_print/g
 s/dm_applicationfocus\([[:space:]]*\);//g
 	only useful in older os x versions, users can now do the same thing via XQuartz preferences [7.24]
 s/bu_vls_trunc2/bu_vls_trunc/g
-	removed duplicitous function in favor of more general version [7.24]
+        removed duplicitous function in favor of more general version [7.24]
 s/bn_pi/M_PI/g
 s/bn_twopi/M_2PI/g
 s/bn_halfpi/M_PI_2/g
@@ -1110,34 +1031,34 @@ s/bn_inv255/(1.0 \/ 255.0)/g
 s/bn_degtorad/DEG2RAD/g
 s/bn_radtodeg/RAD2DEG/g
 s/bn_sin_scale/(BN_SINTABSIZE \/ M_2PI)/g
-	eliminated a number of libbn globals in favor of existing constants [7.24]
+        eliminated a number of libbn globals in favor of existing constants [7.24]
 s/(#[[:space:]]*include[[:space:]]+["<])vfont-if\.h/\1bu\/vfont.h/g
 s/(#[[:space:]]*include[[:space:]]+["<])cmd\.h/\1bu\/cmd.h/g
 s/(#[[:space:]]*include[[:space:]]+["<])hist\.h/\1bu\/hist.h/g
 s/(#[[:space:]]*include[[:space:]]+["<])magic\.h/\1bu\/magic.h/g
-	library-specific public headers moved into a subdir [7.24]
+        library-specific public headers moved into a subdir [7.24]
 s/([^_])([nh]to[hn][fd])/\1bu_cv_\2/g
-	ntohf, ntohd, htonf, htond renamed with bu_cv_ prefix [7.24]
+        ntohf, ntohd, htonf, htond renamed with bu_cv_ prefix [7.24]

 7.26
 ----
 s/bu_kill_parallel\([[:space:]]*\);//g
-	didn't do anything unless called from forked process, use bu_terminate() [7.25]
+        didn't do anything unless called from forked process, use bu_terminate() [7.25]
 s/bu_jmpbuf/bu_jmpbuf[0]/g
 s/bu_setjmp_valid/bu_setjmp_valid[0]/g
-	can replace 0 with bu_parallel_id() to get thread-safe jumping [7.25]
+        can replace 0 with bu_parallel_id() to get thread-safe jumping [7.25]
 s/bu_semaphore_reinit/bu_semaphore_init/g
-	no longer need to manually reinitialize (or initialize) semaphores [7.25]
+        no longer need to manually reinitialize (or initialize) semaphores [7.25]
 s/(#[[:space:]]*include[[:space:]]+["<])fbio\.h/\1bu\/fb.h/g
-	fbio.h is now part of fb.h [7.25]
+        fbio.h is now part of fb.h [7.25]
 s/UNION/'u'/g
 s/SUBTRACT/'-'/g
 s/INTERSECT/'+'/g
-	old db.h db4 preprocessor symbols removed, use char or DB_OP_* [7.25]
+        old db.h db4 preprocessor symbols removed, use char or DB_OP_* [7.25]
 s/(#[[:space:]]*include[[:space:]]+["<])bselect\.h/\1bsocket.h/g
 s/(#[[:space:]]*include[[:space:]]+["<])bin\.h/\1bnetwork.h/g
-	rename bselect.h and bin.h public headers to be more declaratively named [7.25]
-s/db5_enc_len\[(.*)\]/DB5_ENC_LEN(\1)/g
+        rename bselect.h and bin.h public headers to be more declaratively named [7.25]
+s/db5_enc_len[(.*)]/DB5_ENC_LEN(\1)/g
 	replaced db5_enc_len[] global array with DB5_ENC_LEN() macro [7.25]
 s/db_normalize/bu_normalize/g
 	move the path normalization routine to libbu [7.25]
@@ -1186,34 +1107,13 @@ s/rt_ck_vlist/bn_ck_vlist/g
 s/rt_vlist_export/bn_vlist_export/g
 s/rt_vlblock_free/bn_vlblock_free/g
 s/rt_vlblock_find/bn_vlblock_find/g
-	move vlist functions from librt to libbn [7.25]
+        move vlist functions from librt to libbn [7.25]
 s/([[:space:],\(,"])bn_tcl/\1tclcad_bn/g
 s/([[:space:],\(,"])rt_tcl_rt/\1tclcad_rt/g
 s/([[:space:],\(,"])rt_tcl/\1tclcad_rt/g
 	tcl library registrations moved to libtclcad [7.25]
 s/rt_grow_boolstack/rt_bool_growstack/g
-	rename with consistent prefixes [7.25]
+	 rename with consistent prefixes [7.25]
 s/(#[[:space:]]*include[[:space:]]+["<])obj\.h/\1dm\/bview.h/g
 s/GED_VIEW_OBJ_NULL/VIEW_OBJ_NULL/g
 	move view_obj to dm/bview.h [7.25]
-s/BU_PTBL_CLEAR_I\((.*)\)/BU_PTBL_SET(\1, (long*)0)/g
-	replace BU_PTBL_CLEAR_I into the BU_PTBL_SET command [7.25]
-s/BU_PTBL_END\(([^\)]*)\)/(\1)->end/g
-        replace BU_PTBL_END with direct ptbl peek or BU_PTBL_LEN [7.25]
-s/bu_free_argv/bu_argv_free/g
-s/bu_dup_argv/bu_argv_dup/g
-s/bu_dupinsert_argv/bu_argv_dupinsert/g
-	bu_*_argv -> bu_argv_* [7.25]
-s/bu_dir_list/bu_file_list/g
-	bu_dir_list -> bu_file_list [7.25]
-s/BU_FNMATCH_NOMATCH/1/g
-	don't use an explicit define for the non-matching case [7.25]
-s/bu_basename\(([^\)]*)\)/bu_basename(\1, NULL)/g
-	pass NULL argument to get a dynamically allocated buffer back [7.25]
-
-7.28
----
-s/bu_free_array/bu_free_args/g
-        fixed misleading name [7.26]
-s/(#[[:space:]]*include[[:space:]]+["<])bu\/rb\.h/\1bu\/redblack.h/g
-	clearer header name [7.26]
@@ -247,22 +247,12 @@ for memory allocation, threading, string handling, argument support,
 linked lists, and more.
 	Depends on: (threading) (malloc)

-libbg: The BRL-CAD Geometry library implements generic algorithms
-widely used in computational geometry, such as convex hull and
-triangle/triangle intersection calculations.
-	Depends on: libbn libbu
-
 libbn: The BRL-CAD Numerics library provides many floating-point math
 manipulation routines for vector and matrix math, a polynomial
 equation solver, noise functions, random number generators, complex
 number support, and more as well.
 	Depends on: libbu libm

-libbrep: The BRL-CAD Boundary Representation library implements
-routines needed for the manipulation and analysis of Non-Uniform
-Rational BSpline based boundary representations.
-	Depends on: libbg libbn libbu OpenNURBS
-
 libcursor: The cursor library is a lightweight cursor manipulation
 library similar to curses but with less overhead.
 	Depends on: termlib
@@ -304,6 +294,14 @@ messages across stream connections.  The library supports a
 client-server communication model.
 	Depends on: libbu

+librtserver: The ray-trace server library is a thin interface over
+librt that simplifies the process of applying individual ray
+intersection tests against a given set of geometry.  The library
+supports communication with a BRL-CAD geometry repository and
+multithreaded ray dispatch.
+	Depends on: librt libbn libbu libtcl
+	Includes dependent libraries as part of this library
+
 libtclcad: The Tcl-CAD library is a thin interface that assists in the
 binding of an image to a Tk graphics context.
 	Depends on: libbn libbu libfb libtcl libtk
@@ -424,15 +422,14 @@ compiler conformance with the ANSI C standard (c89).
 There is currently no C++ interface to the core BRL-CAD libraries.
 There are a few tools and enhancements to libraries that are
 implemented in C++ (the new BREP object type in librt, for example),
-and C++ is used underneath quite a number of libraries, but there is
-presently no public C++ API in use outside of OpenNURBS.
-
-While C++ as an implementation language of new tools and new library
-interfaces is not prohibited, the mixing of C++ semantics and C++ code
-(including simple // style comments) in the existing C files is not
-allowed.  As new interfaces are developed, new contributors become
-involved, and C++ code integration becomes more prevalent, the
-contributor guidelines will become reinforced with more details.
+but there are presently no C++ bindings available beyond experimental
+developments.  While C++ as an implementation language of new tools
+and new library interfaces is not prohibited, the mixing of C++
+semantics and C++ code (including simple // style comments) in the
+existing C files is not allowed.  As new interfaces are developed, new
+contributors become involved, and C++ code integration becomes more
+prevalent, the contributor guidelines will become reinforced with more
+details.


 CODING STYLE & STANDARDS
@@ -875,10 +872,6 @@ Note that changes to publicly documented tools and library APIs must
 adhere to BRL-CAD's change policy.  This means changes to any tests
 may require thoughtful deployment.  See the CHANGES file for details.

-These tests are run nightly on BRL-CAD's server to catch problems
-quickly - developers should be aware of the status of BRL-CAD's tests
-as seen at http://brlcad.org/CDash
-
 To add new regression tests, look at regress/weight.sh for an
 integration test example and src/libbu/tests/bu_vls_vprintf.c for an
 API unit test example.  See their corresponding CMakeLists.txt build
@@ -1275,7 +1268,7 @@ Release steps are as follows:

    # Manually check rt, mged, and archer.
    bin/rt        # should report usage with correct library versions
-    bin/mged -c test.g "make sph sph ; draw sph ; rt"   # pops up a sphere
+    bin/mged -c test.g "make sph sph ; rt"   # pops up a sphere
    bin/mged      # displays gui, run: opendb test.g ; draw sph ; rt
    bin/archer    # displays gui, run: opendb test.g ; draw sph ; rt

@@ -1401,32 +1394,32 @@ Release steps are as follows:
    SFUSERNAME=`ls ~/.subversion/auth/svn.simple/* | xargs -n 1 grep -A4 sourceforge | tail -1`
    echo "SFUSERNAME=$SFUSERNAME MAJOR=$MAJOR MINOR=$MINOR PATCH=$PATCH"
    ssh -v $SFUSERNAME,brlcad@shell.sf.net create
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH"

    # create binary dirs (as needed)
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH"
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH"
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH"
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH"
-    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH"
+    ssh -v $SFUSERNAME,brlcad@shell.sf.net mkdir "/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH"

    # upload source dist and any binaries
-    scp brlcad-$MAJOR.$MINOR.$PATCH* "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/."
+    scp brlcad-$MAJOR.$MINOR.$PATCH* "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/."

    # extract and upload release notes to source dir
-    cat ../NEWS | tr '\n' '@' | perl -p -e "s/.*?(@---[[:space:]@-]*[0-9]{4}-[0-9]{2}-[0-9]{2}[[:space:]]*Release[[:space:]]*${MAJOR}\.${MINOR}\.${PATCH}[[:space:]@-]*.*?)@---.*/\1/" | tr '@' '\n' > README-${MAJOR}-${MINOR}-${PATCH}.txt
+    cat ../NEWS | tr '\n' '@' | perl -pi -e "s/.*?(@---[[:space:]@-]*[0-9]{4}-[0-9]{2}-[0-9]{2}[[:space:]]*Release[[:space:]]*${MAJOR}\.${MINOR}\.${PATCH}[[:space:]@-]*.*?)@---.*/\1/" | tr '@' '\n' > README-${MAJOR}-${MINOR}-${PATCH}.txt
    echo "Release notes for $MAJOR.$MINOR.$PATCH" && echo "==="
    cat README-$MAJOR-$MINOR-$PATCH.txt && echo "==="
-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ Source/$MAJOR.$MINOR.$PATCH/."

    # NON-AUTO: Following the NAMING A BINARY RELEASE convention,
    # upload any release binaries and platform-specific release notes.

-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH/."
-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH/."
-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH/."
-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH/."
-    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ Runtime\ Libraries/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ BSD/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Linux/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Mac\ OS\ X/$MAJOR.$MINOR.$PATCH/."
+    scp README-$MAJOR-$MINOR-$PATCH.txt "$SFUSERNAME,brlcad@shell.sf.net:/home/frs/project/b/br/brlcad/BRL-CAD\ for\ Windows/$MAJOR.$MINOR.$PATCH/."

    # NON-AUTO: Be sure to mark binaries as default download, then
    # close shell session
@@ -1456,9 +1449,6 @@ Release steps are as follows:
    Slackware maintainer
 	http://slackbuilds.org/result/?search=brlcad

-    Fedora maintainer
- 	https://fedoraproject.org/wiki/User:Germano#Contact
-
 #####################################################################
 # 18: Announce the new release.

@@ -1476,6 +1466,10 @@ audience.  Always notify the following when a release is made:
    BRL-CAD SourceForge NEWS  (authorized can submit)
 	https://sourceforge.net/p/brlcad/news/new

+    Freshmeat  (anyone can submit update)
+	http://freecode.com/projects/BRL-CAD/
+	short summary without news details (sentence format)
+
    BRL-CAD on Facebook  (authorized can submit)
 	http://www.facebook.com/pages/BRL-CAD/387112738872
 	short summary without news details (sentence format)
@@ -347,18 +347,6 @@ respectively.
 CONFIGURATION OPTIONS
 ---------------------

--- BRLCAD_BUNDLED_LIBS ---
-
-Enables compilation of all 3rd party sources that are provided within a BRL-CAD
-source distribution.  If used this option sets all other 3rd party library
-build flags to ON by default.  However, that setting can be overridden by
-manually setting individual variables. Default is "AUTO" - 3rd party sources
-are compiled only if they are not detected as being available and functioning
-as expected.
-
-Aliases:  ENABLE_ALL
-
-
 --- BRLCAD_ENABLE_OPENGL ---

 Enable support for OpenGL based Display Managers in BRL-CAD.
@@ -450,6 +438,18 @@ permissions).
 Aliases:  ENABLE_DOCS, ENABLE_EXTRA_DOCS, ENABLE_DOCBOOK


+--- BRLCAD_BUNDLED_LIBS ---
+
+Enables compilation of all 3rd party sources that are provided within a BRL-CAD
+source distribution.  If used this option sets all other 3rd party library
+build flags to ON by default.  However, that setting can be overridden by
+manually setting individual variables. Default is "AUTO" - 3rd party sources
+are compiled only if they are not detected as being available and functioning
+as expected.
+
+Aliases:  ENABLE_ALL
+
+
 --- BRLCAD_LEMON ---

 Option for enabling and disabling compilation of the lemon parser
@@ -546,6 +546,16 @@ first for a system version if BRLCAD_BUNDLED_LIBS is also AUTO.
 Aliases:  ENABLE_TINYCTHREAD


+--- BRLCAD_FREETYPE ---
+
+Option for enabling and disabling compilation of the FreeType
+libraries provided with BRL-CAD's source code.  Default is AUTO, responsive to
+the toplevel BRLCAD_BUNDLED_LIBS option and testing first for a system
+version if BRLCAD_BUNDLED_LIBS is also AUTO.
+
+Aliases:  ENABLE_FREETYPE
+
+
 --- BRLCAD_TERMLIB ---

 Option for enabling and disabling compilation of the termlib library
@@ -9,119 +9,14 @@ first and are grouped by release.  Each release also includes optional
 descriptive text that emphasizes or further describes significant
 changes made.  See document footer for additional details.

----------------------------------------------------------------------
--- 2016-07-XX  Release 7.26.2                                     ---
----------------------------------------------------------------------
-
-* fixed rt support for lights created prior to rel 6.0 - Sean Morrison
-* fixed infinite loop bug in when using shadow lights - Sean Morrison
-* removed man pages: erase_all, export_body, vrmgr, dall - Cliff Yapp
-* added manual pages for the 'brlman' and 'man' commands - Cliff Yapp
-* improved gdiff default grid spacing and tolerancing - Cliff Yapp
-* updated brlman to support browsing all page categories - Cliff Yapp
-* added support for .rtwizardrc configuration file - Cliff Yapp
-* renamed MGED gdiff grid spacing -t option to -g - Cliff Yapp
-* updated MGED gdiff default drawing options to -l -r - Cliff Yapp
-* removed MGED gdiff -R option, now default behavior - Cliff Yapp
-* replaced obsolete 'g_diff' manual page with 'gdiff' - Cliff Yapp
-* improved 'keep' error message when file is not created - Cliff Yapp
-* improved rtwizard window sizing and "RtWizard" titling - Cliff Yapp
-* brep command attaches .brep suffix instead of _brep - Sean Morrison
-* changed ogl & wgl framebuffer delayed write behavior - Sean Morrison
-* upgraded libpng to version 1.6.23 - Cliff Yapp
-* upgraded freetype to version 2.6.5 - Cliff Yapp
-* upgraded zlib to version 1.2.8 - Cliff Yapp
-* fix rtedge foreground/background color options - Jon Engbert
-* support rt -C colors specified as 0-255 or 0.0-1.0 - Jon Engbert
-

 ----------------------------------------------------------------------
--- 2016-08-08  Release 7.26.0                                     ---
+--- 2014-XX-XX  Release 7.26.XX                                    ---
 ----------------------------------------------------------------------

-This major release of BRL-CAD culminates several years of development
-effort to provide robust explicit boundary representation (BREP)
-Non-uniform Rational Basis Spline (NURBS) import and ray tracing
-analysis support.  Compared to previous polygonal mesh (BoT) methods,
-NURBS offer superior interoperability with other CAD systems, faithful
-shape-preserving import, and significantly reduced model sizes.  NURBS
-may be imported from the ISO STEP (AP203) and Rhino 3DM file formats,
-both with improved hierarchy preservation and entity support.
-
-Unprecedented in BRL-CAD's history, this release initiates steps to
-significantly reduce complexity and improve usability.  Many features
-are being consolidated, reorganized, and removed via BRL-CAD's
-deprecation process.  There are widespread documentation system
-enhancements including new manual pages, improved command usage,
-better help facilities, and more.
-
-This release introduces the 'gcv' and 'icv' tools for geometry and
-image conversion respectively.  These plugin-architecture tools are
-intended to eventually consolidate and replace all of BRL-CAD's
-conversion and processing functionality into an easy universal
-interface for users and application developers.  GCV currently
-supports import and export of STL, 3DM, OBJ, VRML, and FASTGEN
-geometry as well as mesh decimation, facetization, and solidity
-testing.  The new FASTGEN exporter implements extensive compatibility
-feature mapping for round-trip geometry conversion.
-
-Ray tracing performance on Windows is vastly improved on symmetric
-multiprocessing (SMP) multicore and multiple CPU systems.  Implemented
-as 'datum' objects, BRL-CAD provides new modeling support for
-reference points, lines (axes), and planes.  Major features still
-under experimental development include NURBS Boolean evaluation, a new
-marching cubes method for polygonal mesh export, rigging joints for
-constrained geometry articulation, and an OpenCL-accelerated high
-performance ray tracing pipeline.
-
-* mass-deprecation of 121 command-line utilities - BRL-CAD Developers
-* fixed bad args crash in metaball 'in' command - Cliff Yapp
-* added manual page for lt comb child listing command - Cliff Yapp
-* added lt -c option for specifying separation character - Bob Parker
-* improved hierarchy preservation in 3dm-g importer - Jon Engbert
-* fixed upside down 'screengrab' images on some platforms - Nick Reed
-* updated wireframe drawing to respect primitive colors - Cliff Yapp
-* updated pixdiff & pixcmp to only compare same sizes - Cliff Yapp
-* fixed running archer from read-only filesystems - Cliff Yapp
-* fixed patch-g tool and E command infinite loop bug - Sean Morrison
-* improved NMG ray tracing fault tolerance - Sean Morrison
-* added 3dm-g support for layers and names - Keith Bowman
-* fixed color/shader preservation issue with 3dm-g importer - Jon Engbert
-* added 3dm-g support for mesh objects - Jon Engbert
-* added csg implicit hierarchy conversion to brep command - Cliff Yapp
-* fixed crash in clone when told to make zero copies - Cliff Yapp
-* fixed crash in search when using -above option - Cliff Yapp
-* extended nirt to list current and available formats - Sean Morrison
-* fixed NURBS wireframe drawing crash - Cliff Yapp
-* fixed firing of single rays using the rtshot tool - Sean Morrision
-* removed pixread.sh, pixwrite.sh; obsolete hardware - Sean Morrison
-* removed cray.sh and sgisnap.sh; obsolete hardware - Sean Morrison
-* removed cadbug.sh - use sourceforge tracker - Sean Morrison
-* removed any-png.sh - use pix tools - Sean Morrison
-* removed librtserver interface - Cliff Yapp
-* removed MGED per_line command - Sean Morrison
-* updated MGED tops command: default to -g -u behavior- Sean Morrison
-* removed MGED -n option; use -c instead - Sean Morrison
-* removed MGED commands pl, pov and polybinout - Sean Morrison
-* removed UtahRLE image tools - Cliff Yapp
-* improved rcodes command feedback in the no changes case - Cliff Yapp
-* added brlman -S option to specify man page section  - Cliff Yapp
-* modified rtg3 to avoid outputting excessive LOS - Nick Gerstner
-* extended burst and rtg3 to output 5 digit ID numbers - Nick Gerstner
-* improved draw command manual page documenation - Cliff Yapp
-* added lc -m option to report multi-material/los regions - Cliff Yapp
-* added new 'icv' image conversion tool w/ pix, bw, dpix, png, ppm
-	- Mohit Daga, Cliff Yapp, Sean Morrison, Erik Greenwald
-* ported 'burst' tool (batch mode only) to Windows - Cliff Yapp
-* removed mged pl command, use plot command instead - Sean Morrison
-* improved datum wireframes (yellow) and fixed arrowheads - Cliff Yapp
-* added initial manual page for 'burst' ray dispatch tool - Cliff Yapp
-* improved wireframe display list performance - Keith Bowman
-* added draw -S for simplied wireframes, no subtractions - Cliff Yapp
-* added draw -L# to draw bounding boxes for large objects - Cliff Yapp
-* added 3dm-g instance reference and definition import - Jon Engbert
+* added -M draw cmd option to skip subtraction solids - Cliff Yapp
+* added -L draw cmd option to draw bboxes for large bots - Cliff Yapp
 * minor rtwizard graphical user interface reorganization - Cliff Yapp
-* fixed rtwizard edge and ghosted image bug on Windows - Bob Parker
 * ported 'brlman' manual page viewer with GUI to Windows - Cliff Yapp
 * added gdiff -h help command-line option - Cliff Yapp
 * added facetize -m marching cubes option - Erik Greenwald
@@ -129,11 +24,8 @@ performance ray tracing pipeline.
 * improved pix-bw intensity averaging to closest integer - Cliff Yapp
 * removed pix-bw3 & bw3-pix tools, see pix-bw & bw-pix - Cliff Yapp
 * fixed pix-ppm to write out all image data - Sean Morrision
-* added libnetpbm for ppm image format support in icv - Cliff Yapp
 * added new algorithm to bot_decimate (via -f option) - Jon Engbert
 * fixed benchmark bug running from paths with spaces - Sean Morrison
-* fixed adjust command crash when working with BoTs - Daniel Roßberg
-* removed fb-orle, orle-fb, orle-pix, and pix-orle tools - Cliff Yapp
 * removed support for RLE v1 and v2 ('orle') image format - Cliff Yapp
 * fixed datum type 'in' command unit conversion bug - Cliff Yapp
 * fixed rpatch / patch-g line handling on Windows - Daniel Roßberg
@@ -144,41 +36,25 @@ performance ray tracing pipeline.
 	- Jon Engbert, Vasco Costa
 * improved point cloud plot visualization - Sean Morrison
 * fixed program freezing bug in MGED grouper command - Bob Parker
-* added 'rhc' reporting to analyze command - Kalpit Thakkar
-* improved command option and manual page consistency - Carl Moore
+* improved help option consistency across numerous tools - Carl Moore
 * added prefatory FASTGEN4 geometry export support - Jon Engbert
-* added FASTGEN4 illegal thickness CCONE1 entity import - Cliff Yapp
-* improved help message for 'tire' command - Cliff Yapp, Carl Moore
 * improved option parsing and output options for gencolor - Carl Moore
-* fixed saveview usage help string and running from archer - Nick Reed
-* fixed and improved killtree man page - Nick Reed
 * fixed composition bugs in pixmatte and pixmerge - Carl Moore
 * fixed definition of "light year" in unit conversions - Cliff Yapp
-* fixed duplicate name errors in dbconcat - Daniel Roßberg
-* modernized documents and improved infrastructure - Hitesh Sofat
 * added mirroring support for hrt primitive objects - Isaac Kamga
-* added manual page documenting the STEP geometry format - Cliff Yapp
 * ported the mged Overlap Tool to Windows - Sean Morrison
 * improved NURBS prep performance for UV-remapped surfaces - Nick Reed
 * fixed dbconcat -c crash when color table does not exist - Nick Reed
 * swapped meanings of search's -above/-below options - Sean Morrison
-* upgraded freetype to version 2.5.5 - Cliff Yapp
-* updated libregex to apply a fix for CVE-2015-2305 - Cliff Yapp
 * upgraded libpng to version 1.6.20 - Cliff Yapp
 * added command window option for pasting tree view paths - Nick Reed
-* improved 'bb' command digits and units output - Keith Bowman
-* improved robustness of bb command oriented box option - Peter Amidon
-* added example NURBS B-Rep geometry files from NIST - Cliff Yapp
 * removed "high resolution" options from all commands - Carl Moore
 * improved performance of archer loading large BoT models - Nick Reed
 * added evaluated shaded drawing preference mode and menu - Nick Reed
 * extensive improvements to NURBS Boolean evaluation - Nick Reed
 * added 'bot chull' for creating convex hull envelopes - Cliff Yapp
 * new manual page for the g-voxel exporter - Mandarj
-* improved performance of lc command - Peter Amidon
-* updated manual page for MGED's brep command - Peter Amidon
 * new manual page for the g-dot exporter - Shardul Chiplunkar
-* added sketch centroid support the analyze command - Peter Amidon
 * new Think. Invent. Create. splash screen for archer - Marc Tannous
 * improved pix-bw to support dual output streams - Carl Moore
 * added list option to attr command - Cliff Yapp
@@ -189,23 +65,15 @@ performance ray tracing pipeline.
 * gqa respects LIBRT_BOT_MINTIE environment variable - Ștefan Mirea
 * improved behavior of mged's draw command - Ștefan Mirea
 * fixed handling of extra whitespace in nirt commands - Ștefan Mirea
-* renamed 'make_bb' mged command name to 'bb' - Cliff Yapp
-* added g-ply exporter for Stanford PLY geometry format - Rishub Jain
-* added ply-g importer for Stanford PLY geometry format - Rishub Jain
-* improved rtedge help option output - Carl Moore
 * fixed texture mapping crash with bad image dimensions - Ștefan Mirea
 * fixed g2asc and asc2g handling of dsp primitive - Cliff Yapp
 * rewrote gdiff with improved output & reporting options - Cliff Yapp
 * fixed pix-ps -S -W -N output size options being ignored - Carl Moore
 * fixed crash exporting mixed mode merged BoT meshes - Sean Morrison
 * fixed submodel primitive crash - Cliff Yapp, Sean Morrison
-* added fbclear command to archer - Bob Parker
-* improved rtwizard command-line mode manual page docs - Cliff Yapp
 * support non-.g file import in Archer's file open dialog - Cliff Yapp
 * added brep support to g2asc and asc2g - Cliff Yapp
 * fixed a CPU affinity locking bug on Linux platforms - Sean Morrison
-* renamed g_diff/g_lint/g_qa/g_transfer sans underscore - Cliff Yapp
-* removed mged -n option, use mged -c for classic mode - Cliff Yapp
 * fixed mged -c crash running view-modifying commands - Sean Morrison
 * improved kill, killall, killtree documentation - Sean Morrison
 * added killtree -f force flag to kill unconditionally - Sean Morrison
@@ -215,36 +83,23 @@ performance ray tracing pipeline.
 	- Wu Jianbang, Nick Reed, Cliff Yapp
 * improved step-g assembly hierarchy import support - Keith Bowman
 * fixed rtweight when using the -G grid spacing option - Sean Morrison
-* fixed memory leaks in a number of pix utilities - Cezar Elnazli
+* fixed memory leaks in a number of pix utilities - Cezar Elnazi
 * improved NURBS ray tracing & tessellation robustness - Keith Bowman
 * improved step-g NURBS geometry import robustness - Keith Bowman
-* added -f vertex fuse option to obj-g importer - Jon Engbert
 * added -v verbose output option to mged 'search' command - Cliff Yapp
 * fixed g_lint and pixcount red-black tree memory leaks - Tom Browder
-* added conversion time reporting to step-g importer - Keith Bowman
 * fixed crash of extrude with special case bezier curves - huskmate13
 * improved performance of 'terrain' & numerous shaders - Sean Morrison
 * new manual pages for rtexample and brep_simple - Shardul Chiplunkar
 * added key binding to reopen/focus mged command window - Emory Huff
 * added menu option to restore mged command window - Cezar Elnazli
-* improved DocBook documentation output formatting
-	- David Wood, Yatharth Agarwal
-* added 'search' -params option for geometric parameters - Cliff Yapp
 * search command now recognizes hyp and metaball types - Cliff Yapp
-* improved spec formatting, added v5 timestamp proposal - Tom Browder
-* improved search command documentation examples - Cliff Yapp
-* improved archer interface's behavior on start-up - Nick Reed
 * added -depth option to mged 'search' command - Cliff Yapp
-* initial support for rigging joints and constrained articulation
-	- Nick Reed, Keith Bowman, Cliff Yapp, Sean Morrison
 * improved 'search' with 'flat' search path modifier - Cliff Yapp
 * improved 'search' with above/equal/below depth limits - Cliff Yapp
-* improved support for sub-millimeter (tiny) meshes - Keith Bowman
 * added comb -S option to stop when object already exists - Cliff Yapp
 * improved comb command documentation with many examples - Cliff Yapp
 * implemented new 'hrt' heart-shaped primitive object - Isaac Kamga
-* added support for multicore / SMP ray tracing on Windows
-	- Adrián Calle, Arjun Govindjee, Daniel Roßberg, Sean Morrison


 ----------------------------------------------------------------------
@@ -520,7 +375,7 @@ received corrections and improvements.  The introductory article
 * "About BRL-CAD" article translation to Armenian - Karen Mgebrova
 * "About BRL-CAD" article translation to Italian
 	- Unknown Contributor, Tom Browder
-* improved 'adjust' command rgb/color attribute handling - Cliff Yapp
+* improved handling of rgb/color attributes by adjust cmd - Cliff Yapp
 * added initial support for step-g import of assemblies - Keith Bowman
 * added a basic SWIG spec file - Erik Greenwald
 * fixed referenced object highlighting in archer treeview - Bob Parker
@@ -551,7 +406,7 @@ received corrections and improvements.  The introductory article
 * improved tessellation of pipe bends for conversion - Richard Weiss
 * fixed keypoint vertex bug when editing extrude objects - Nick Reed
 * fixed eto error converting hyp objects with asc2g tool - Nick Reed
-* fixed mged bug processing edcodes command arguments - Bob Parker
+# fixed mged bug processing edcodes command arguments - Bob Parker
 * various improvements to NMG polygonal mesh processing robustness
 	- Nick Reed, Sean Morrison, Richard Weiss
 * improved bad face handling within the obj-g importer - Nick Reed
@@ -1262,7 +1117,7 @@ invalid geometry is now more robust.
 * added new -c character option to the loop command - Dawn Thomas
 * tire now checks for files instead of overwriting - Cliff Yapp
 * add new nirt formatting options, -L listing option - C. Yapp
-* fixed nirt 'dest' command file name string handling - Cliff Yapp
+* fixed nirt's dest cmd's handling of file name string - Cliff Yapp
 * modified mged nirt command to include air in results - Bob Parker


@@ -1854,7 +1709,7 @@ The rtarea command was added to MGED as well, along with rtweight.
 * added a -noleaf option to the mged pathlist command - Bob Parker
 * fixed potential infinite loop bug in BoT primitive - Bob Parker
 * no longer install tclsh/wish, use btclsh/bwish - Sean Morrison
-* added 'bot_merge' mged command (combine 2 bots into 1) - Lee Butler
+* added bot_merge mged cmd (combine 2 bots into 1) - Lee Butler

 ----------------------------------------------------------------------
 --- 2005-06-07  Release 7.2.6                                      ---
@@ -1,5 +1,5 @@
 			    BRL-CAD
-			 Release 7.26.2
+			 Release 7.26.0
 		       http://brlcad.org/

 BRL-CAD is a powerful cross-platform open source combinatorial
@@ -18,117 +18,56 @@ tasks as they are completed.
 THESE TASKS SHOULD HAPPEN BEFORE THE NEXT RELEASE
 -------------------------------------------------

-* add regression test for directional light sources
+* sync tgc/rec shot() behavior, sort results for proper normal.
+  inspect t62 grazing with r653,r735 (tgc on an arb8) looking at ae0,0
+  and z=1524 (was hit/overlap, now misses).

-* update astyle
+* fix regressions in step-g

-* bundle primary rays in rt front end into postage stamps, shoot via
-  rt_shootrays(), modify to pass all rays down through the spatial
-  partitioning simultaneously
+* figure out why the following is crashing:

-* create a catalog of all possible entity types.  including distinct
-  parameterizations with sufficient variety that conveys the object's
-  parameterization options (e.g. ell as sphere, flat disc, long spike,
-  etc.).  this is necessarily defined per object type and possibly
-  programmable.  see src/proc-db/csgbrep.cpp for a basic start.
+  bin/rtshot -R 1 -p 0 0 0 -d 1 0 0 share/db/havoc.g havoc

-  create a BRL-CAD .g with all possible object types embedded.
-  integrate into testing.
+  is it related to using bu_hash in some fashion?  This test worked
+  as of r65575

-* create a catalog of all possible/distinct/useful shader settings.
-  see regress/shaders.sh for a basic start.
+* quick rtg3 with -c option.  was failing when run without -c "set
+  ray_data_file=..." with this: "RTG3: Invalid argument" and "Cannot
+  open ray data output file"

-* readd support for vrml v1 to g-vrml so that users can select whether
-  they want v2 (default) or previous v1 output format via a
-  command-line switch.  see http://brlcad.svn.sf.net/viewvc/brlcad/brlcad/trunk/conv/g-vrml.c?view=diff&pathrev=22798&r1=16900&r2=16901
+* rtwizard command line ghost image specification isn't working
+  reliably

-* reinstate 'stat' and search -size, see r67636 through r67646
+* drawing datums far from origin result in huge arrowheads


 THESE TASKS SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
 -------------------------------------------------------

+* reinstate 'stat' and search -size, see r67636 through r67646
+
 * turn on Bullet code (simulate command) unconditionally

-* metaball in command input needs sanity checks and better
-  validation.
+* create a BRL-CAD .g with all possible object types embedded.  The
+  csgbrep command is a good starting point, but only about half of
+  them.

-* integrate gen-registered-attributes-html output into website
+* bundle primary rays in rt front end into postage stamps, shoot via
+  rt_shootrays(), modify to pass all rays down through the spatial
+  partitioning simultaneously

-* brlcad-config build helper script is not working (not reporting
-  -llibs, reporting semicolon list for 'brlcad' lib).  Example working output:
-  $ /usr/brlcad/rel-7.18.0/bin/brlcad-config brlcad
-  -L/usr/brlcad/rel-7.18.0/lib -m64 -L/usr/local/lib64 -L/usr/local/lib -pipe -fno-strict-aliasing -fno-common -fexceptions -ggdb3 -D_FORTIFY_SOURCE=2 -O3 -w -L/usr/brlcad/rel-7.18.0/lib -lbrlcad -lged -lwdb -lrt -lbn -lbu -ltcl8.5 -ldl -lm -lpng14 -lz -lc -lpthread -lregex -lsysv -lopenNURBS -lanalyze  
+* resolve bot bin sort optimization crash, disabled during release

-  $ /usr/brlcad/rel-7.18.0/bin/brlcad-config rt
-  -L/usr/brlcad/rel-7.18.0/lib -m64 -L/usr/local/lib64 -L/usr/local/lib -pipe -fno-strict-aliasing -fno-common -fexceptions -ggdb3 -D_FORTIFY_SOURCE=2 -O3 -w -L/usr/brlcad/rel-7.18.0/lib -lrt -lbn -lbu -ltcl8.5 -ldl -lm -lpng14 -lz -lc -lpthread -lregex -lsysv -lopenNURBS
-
-* OpenCL for enhanced performance boolweave sorting
-
-* create boolweave+boolfinal unit tests to validate weaving behavior
-  and performance.
-
-* make sure we can run db_dirbuild() multiple times without creating
-  duplicate entries.
-
-* heap unit test needs to actually compare performance against system
-  allocation, not just do some work
-
-
-THESE ARE UNSCHEDULED BACKLOG TASKS
-----------------------------------
-
-* define geometry URL and VFS behavior
-
-* change _mged_ command prefix to a simple '.' prefix to hide/protect
-  the built-in commands.
-
-* sync tgc/rec shot() behavior, sort results for proper normal.
-  inspect t62 grazing with r653,r735 (tgc on an arb8) looking at ae0,0
-  and z=1524 (was hit/overlap, now misses).
+* closing the graphics window brings down X11 on Mac due to a bad
+  context.  fix or revert recent close window behavior.

 * havoc.g s.nos5g reliably exhibits the grazing edge bug where only
  one hit point is being returned.  to reproduce:
  e s.nos5g ; ae 35 25 ; units mm ; center 26912.4 7089.08 7168.96 ; nirt

-* obsd stack crashers

-* closing the graphics window brings down X11 on Mac due to a bad
-  context.  fix or revert recent close window behavior.
-
-* resolve bot bin sort optimization crash, disabled during release
-
-* rt moss.g facetize rt bot bug
-
-* evaluate OpenMesh (http://www.openmesh.org) and OpenFlipper
-  (http://www.openflipper.org) for smoothing, decimation, and
-  additional GCV conversion formats.
-
-* GCT decimation assumes no edge is shared by two triangles except
-  once in the reversed order (AB, BA).  Needs basic check to avoid
-  failures/crashing.
-
-* V&V bwcrop, pixembed are behaving correctly, as documented
-
-* need routine that returns a color given a path, similar to
-  rt_comb_get_color() but full path so that inheritance is taken into
-  account and colors set correctly.
-
-* implement unit tests for bu dirent / stat API
-
-* convert src/util/terrain.c to src/shapes/terrain.c writing out the
-  datafile to a binunif along with a referencing dsp.  perhaps add
-  command line option to skip .g to retain prior datafile capability.
-  need to review command line options to simplify complexity and
-  control randomization better.
-
-* implement quasi-random unbiased iterative spherical ray sampling.
-  requires devising an algorithm whereby we obtain a set of points on
-  a sphere with rays randomly going through those points, so we sample
-  the volume evenly.  we need to be able to add additional sets of
-  points/rays (incrementally or step-wise) in order to evaluate
-  convergence and estimate error.  this feature is useful for checking
-  overlaps, surface area, volume, and moments of inertia.
+THESE ARE UNSCHEDULED BACKLOG TASKS
+-----------------------------------

 * get_eyemodel returns an eye_pt entry, but feeding the results to
  archer's eye_pt command results in get_eyemodel returning a different
@@ -136,15 +75,33 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  intuitively, I would expected feeding the results of get_eyemodel to
  eye_pt to result in no change, modulo unit conversions.

-* make rt -b accept a pixel index in addition to x,y pixel coordinates
+* teach pixdiff, rt, and other tools that can/should support the
+  capability to read/write (as appropriate) pixel index values and
+  reproduce the ray fired to create that pixel.  rt's -j option can
+  specify a sub-rectangle, but the key point (whatever the details of
+  implementation) is to be able to easily identify and reproduce the
+  ray that produces a given pixel when debugging.  For example,
+  pixdiff's -l option will report differing pixels by index - rt
+  should support those index specifications as an input option.
+  Another possibility would be to have rt support accepting an input
+  image as a "control" image and generating a file with nirt or rtshot
+  commands for each pixel that reports different from the control.

-* teach pixdiff and other tools that can/should support the capability
-  to read/write (as appropriate) pixel index values or x,y coordinates
-  and reproduce the ray fired to create that pixel. currently does -l
-  index but not xy coordinates.
+* pull work on rm command out of history (commit r67394 reverted it)
+  and take it to a production ready stage.
+
+* Extract bounding box code from both autoview.c and get_autoview.c
+  into a general bounding rpp function in librt and use accordingly
+  (particularly in libged).  Should combine autoview.c with
+  get_autoview.c (perhaps as a flag) and utilize the general function
+  in lots of places (e.g., the ged_arb() function).

 * make mged work without a batch script

+* make archer work without a batch script
+
+* make isst work without a batch script
+
 * Need to rethink libbu hash API - ideally should be much simpler and
  expose much less to the user.

@@ -211,6 +168,9 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  fixes some concerns but breaks if an application changes its notion of
  the current working directory after initialization, for example.

+* make the idents command not list subtracted objects by default,
+  optionally list everything
+
 * start making use of the CMakePushCheckState macros - we are doing
  this manually in several places

@@ -290,12 +250,27 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * import CTRI material information in fast4-g as per-face data.

+* improve performance of these commands that seem to have exponential
+  cost: bot_split, killtree
+
+* translate lc command to libged (discovered in Feb. 2015 to have already
+  been done -- need information regarding when this was done and committed).
+
 * Integrate ADRT into Archer as a visualization mode.

 * Document a GUI feature list (prioritized).

 * Document a CLI feature list (prioritized).

+* create a catalog of all possible entity types.  including distinct
+  parameterizations with sufficient variety that conveys the object's
+  parameterization options (e.g. ell as sphere, flat disc, long spike,
+  etc.).  this is necessarily defined per object type and possibly
+  programmable.  see src/proc-db/csgbrep.cpp for a basic start.
+
+* create a catalog of all possible/distinct/useful shader settings.
+  see regress/shaders.sh for a basic start.
+
 * high-performance VOL for medical data visualization.  consider
  leveraging OpenVDB, PCL, Paraview/VTK, etc.

@@ -306,6 +281,13 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  propagated up into separate region hits.  the prior is probably
  easier and less error-prone.

+* BoT mesh editing command.  Subtasks:
+
+  - enumerate functions desirable
+  - catalog features of other mesh manipulation tools
+  - investigate mesh editing libraries and/or relying on NMG editing
+  - bind GUI editing to the BoT mesh editing command
+
 * establish the Basic Application Runtime (BAR), only consisting of
  libbu and libbn, as a stand-alone self-contained project.  provide
  an API that supports most C/C++ application development and
@@ -329,11 +311,15 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  functions until it provides some clear advantage (e.g., portability,
  performance, and/or maintainability).

-* rename the "joint2" articulation command (possibly also rename the
-  "joint" command) worked on when joint objects were implemented.
-  joint2 interfaces with the old text-file based articulation
-  interface, but conceivably should get updated when joint objects can
-  describe everything in the old text files.
+* object error heuristic.  implement a function/command to report how
+  big of an error a given geometry object has.  the intent is to help
+  prioritize geometry modeling errors based on their spatial impact.
+  this is particularly relevant for nurbs/brep and nmg geometry where
+  there may be solidity gaps in the topology that need to be sealed or
+  dangling faces/surfaces of different sizes.  this is meant to be a
+  relative heuristic applicable across all geometry, not necessary an
+  exact measure.  this may make more sense added as an output option
+  to glint or as a warning category for a geometry debugger.

 * create a joint articulation (manually is good, automatic is better)
  for the tin woodsman so he can move his arms, legs, neck, and head.
@@ -365,6 +351,12 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 * convert all calls to BU_SETJUMP/BU_UNSETJUMP into familiar try/catch
  logic layout using if/else.

+* heap unit test needs to actually compare performance against system
+  allocation, not just do some work
+
+* make sure we can run db_dirbuild() multiple times without creating
+  duplicate entries.
+
 * re-do the sh/enumerate.sh script for CMake

 * get bu_extern out of bu/parse.h into its own header file.
@@ -373,6 +365,17 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * investigate INFINITY spatial partitioning issue.

+* implement a region anointment feature where the user can turn an
+  assembly into a region and change all lower or higher regions into
+  combinations.  basically consolidate or distribute region flags.
+  this is partially covered by the 'comb' command but it tries hard to
+  ensure geometry isn't left in a broken state.  needs to be a way to
+  do the simple consolidate/distribute operation regardless of
+  resulting state.
+
+* update search depth options (above + below) to make sure the logic
+  supports depth=0 / above=0 / below=0 meaning the current node.
+
 * kill material_head static global in src/librt/mater.c

 * add an mk_extrude() routine to libwdb.
@@ -381,7 +384,6 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  other options supplied at the command line and in environment
  variables.  See whether we can pass a variable into CMAKE_C_FLAGS
  that will allow specification of build flags at make time.
-  Relevant link: https://cmake.org/Bug/view.php?id=12928

 * investigate the possibility of allowing functions to define
  their own custom filters for some version of the db_search API.
@@ -391,6 +393,9 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  as the functions satisfy the API templates used by the db_plan
  structures, wouldn't custom functions work?

+* merge get_eyemodel's functionality  as a "view eyemodel"
+  sub-command in MGED/Archer.
+
 * document gqa centroid and moments of inertia options

 * add support for custom and random views to gqa.  provide an option
@@ -550,21 +555,36 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 * decouple libwdb from librt, particularly the headers and relevant
  structures that cross over to both such as the rtgeom.h types.

-* Translate logic from clipper polygon clipping library
-  (http://www.angusj.com/delphi/clipper.php) into libbg and use it
-  as a pre-processing step for poly2tri's algorithm along the lines
-  of what bitfighter did:  https://github.com/raptor/clip2tri
-  Some useful notes here: http://stackoverflow.com/a/16115775
-
-* Translate the poly2tri routines into libbg C code
+* Translate the poly2tri routines into libbn C code

 * Implement Shamos-Hoey test for checking whether a polygon is simple
-  in libbg: http://geomalgorithms.com/a09-_intersect-3.html
+  in libbn: http://geomalgorithms.com/a09-_intersect-3.html

 * figure out what in f_matpick (or possibly some other related function)
  is causing ipathpos to get incremented to a number larger than the
  number of objects in the full path it's supposed to be referencing.

+* change _mged_ command prefix to a simple '.' prefix to hide/protect
+  the built-in commands.
+
+* the 'comb' command both updates and creates combinations.  this is a
+  problem because it's not possible to infer an intended result from
+  the command string alone.  it should either append to an existing
+  combination and fail if it doesn't exist (with flag to create) OR it
+  should create a combination and fail if there is an existing
+  combination (with flag to append).
+
+* Update the comb "region lift" capability to handle automatic duplication
+  and substitution of the duplicate into the tree of combs who can't have
+  their definitions changed without impacting other geometry in the .g file.
+
+* change 'mirror' command offset to be prior to mirror instead of
+  after, so that you can mirror intuitively over a specified point
+  along a given axis.
+
+* add option to 'mirror' command to delete the source object.  support
+  specification of a plane as the view plane, 3 points, XY, YZ, XZ.
+
 * refactor rt_mirror (src/librt/primitives/mirror.c) into the functab

 * refactor rt_functab accessors to go through an api call or calls so
@@ -597,9 +617,6 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 * investigate integrating Pixar's OpenSubdiv for subdivision surfaces:
  http://graphics.pixar.com/opensubdiv/

-* investigate the possibility of using Appleseed (http://appleseedhq.net/)
-  to perform visual image rendering using librt shotline data for input.
-
 * the scale structure in bn_cmd_noise_slice (bn_tcl.c) was never
  initialized. it looks like somebody has planned to extend the
  function but never carried out
@@ -629,6 +646,10 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  as API instead of expecting callers to use RT_DBNHASH and
  RT_DBHASH() manually.  consider using bu_hash or other container.

+* rename chan_add, chan_mult, chan_permute and look into possibly
+  merging them into one tool in the util directory.  similar to the
+  'join' command, but arguably easier to use.
+
 * temp colors and temp matrices during ray tracing, rt, rtwizard.
  need a command-line and mged method to override parameters.

@@ -651,6 +672,11 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * convert teapot to use nurbs surfaces instead of bspline

+* add an option to the bb command for calculating a bounding box that
+  encompasses subtracted objects and trimmed surfaces and default to
+  calculating a tight-fitting fbounding box once we have a robust path
+  from geom->NURBS+CSG->NURBS.
+
 * create a FASTGEN sample geometry with all entities defined and a
  corresponding regression test to make sure outputs don't change.

@@ -735,14 +761,42 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * fix the "(type)(size_t)val" hacks (using ints like ptrs, etc.)

+* Mac OS X mouse input binding problem seems to be back with rotations
+  stalling during interactive use.
+
+* killall command reports db_lookup failures if the target object
+  doesn't exist (maybe we only care about refs).  should keep quiet.
+
 * pixdiff reports bytes, but reports incorrect (off-by-one) bytes for
  .bw input files.  cause is due to tool assuming input is rgb triplets
  (even though output is bytes, wtf?).  should probably report pixels
  and/or have a -b option for handling byte/bw input.

+* the new "exists" command is a beautiful corollary to the unix 'test'
+  command.  make the usage match, remove options that make no sense
+  after you've replaced instances of 'file' with 'object', and add
+  options specific to testing geometry (like whether two objects
+  overlap, whether an object's volume is greater than some value or
+  equal to zero, whether two objects are actually the same object
+  (geometrically), etc.).
+
 * investigate why epa primitive is so sensitive to coarse absolute
  value changes (run csgbrep, tol abs=1, facetize and get 321k poly)

+* implement a new "simulate" command for applying physics deformations
+  to geometry.  Each timestep (default steps==1) would get recorded as
+  new geometry unless updating the existing is requested.  Usage might
+  be something like this:
+
+     simulate [-k] [-g|-G] [-f x y z N] <time> [steps]
+
+  Examples:
+     simulate 10.5  # simulate 10.5s of time (default gravity)
+     simulate 3 10  # simulate 30s of time, 10s per timestep
+     simulate -f 0 0 -1.0 9.807 3.0  # earth's gravity for 3s
+     simulate -k 1.0  # simulate 1s of gravity, overwriting original
+     simulate -G -f 1 2 3 .4 5  # no gravity, custom force, 5s
+
 * implement http network transfer tool for crash reports and benchmark
  analyses (via libfetch)

@@ -765,6 +819,8 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  framebuffer is enabled and the window is resized.  initialize and
  refresh the new memory and zap the framebuffer.

+* merge sed and oed commands
+
 * make the right-hand path to oed optional

 * deprecate dbcp and merge functionality (and improved
@@ -775,6 +831,8 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * update g-xxx_facets to use libgcv

+* make sure 'preview' works, particularly the 'tree' subcommand.
+
 * make nreed's new bot cleanup interface update interactively without
  resorting to calls to Tcl_DoOneEvent() down in librt.

@@ -787,6 +845,9 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * investigate OpenEXR (BSD licensed HDE image format)

+* add support for a custom unit conversion factor to the units command
+  (e.g. 'units 9.3120223' or 'units metertons 9.3120223')
+
 * usage statistics.  similar to the eclipse Usage Data Collector, keep
  track of which BRL-CAD command-line commands and MGED/libged
  commands are run.  Give the user the option of uploading those
@@ -827,6 +888,10 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  obtain a bu_log()-style callback function returned from a
  logger registration function.

+* deprecate dbfind - ensure functionality is fully captured by the
+  search command, make it report a deprecation statement on use and
+  utilize search under the hood.
+
 * investigate impact of using lookup tables for root solving.
  implement lookup tables for a range of linear, quadratic, cubic, and
  quartic polynomial coefficients.  compare performance to root
@@ -868,6 +933,9 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  intersected with them) since, while bad practice, are valid
  geometrically.

+* implement some sort of archive/backup command in mged in order to
+  save the currently open database out to a file.
+
 * make sure there are no getenv() non-NULL assumptions within the
  code.  might want to see if there's a pattern of variables being
  checked such that a libbu interface would be warranted (e.g.,
@@ -915,6 +983,19 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 * refactor mged's signal handling to make it possible to safely
  interrupt long-running commands

+* add a -color option to all mged commands that draw geometry (B, eid,
+  and E come to mind)
+
+* have mged record a timestamped command history by default
+
+* implement -exec support for 'search' command
+
+* implement -param support for 'search' command
+
+* readd support for vrml v1 to g-vrml so that users can select whether
+  they want v2 (default) or previous v1 output format via a
+  command-line switch.  see http://brlcad.svn.sf.net/viewvc/brlcad/brlcad/trunk/conv/g-vrml.c?view=diff&pathrev=22798&r1=16900&r2=16901
+
 * make Mac OS X universal binaries actually work.

 * fully implement analyze for all primitives
@@ -934,6 +1015,8 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * calculate radii of gyration in 'analyze' and/or gqa output

+* implement 'analyze' command option to write output to a file
+
 * implement make, ted, edsol, mirror, and analyze for revolve
  primitive.  implement tess() too.

@@ -948,6 +1031,13 @@ THESE ARE UNSCHEDULED BACKLOG TASKS

 * give bot-bldxf the axe (reconcile and merge with bot_dump)

+* implement mged object name globbing similar to tclsh's globbing
+  (i.e. via a globbing command and quoting globs that use []).  testing
+  shows db_glob doesn't seem to behave correctly, at least not like
+  glob.  hook globbing into all commands so glob_compat_mode
+  statefulness can go away.  a db_glob expression that doesn't match
+  anything should not return the expression.
+
 * come up with a new tool that automatically generates "inside"
  regions for a given model as a way to automatically model air.
  particularly useful for bot models where the inside air compartment
@@ -1082,6 +1172,8 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
 * libfb + font rendering (perhaps through libbn's plot interface) for
  a posix terminal.

+* OpenCL for enhanced performance boolweave sorting
+
 * getexecname, "/proc/self/cmdline", program_invocation_short_name.
  separate out into new file.

@@ -1122,6 +1214,15 @@ THESE ARE UNSCHEDULED BACKLOG TASKS
  combinations of these primitives, provided their continuity at the
  ends ensures continuity all along "seams" - something to consider.

+* incorporate some variety of spatial partitioning into the facetize
+  command (may involve just rewriting it) to try and realize MUCH
+  faster tessellation of CSG geometry.  Current routines are doing a
+  lot of unnecessary work that tends to result in explosive completion
+  times for worst-case scenarios - try to get closer to the "only do
+  the work we need to" ideal.  Once a new idea is proven in that
+  command, it should be made into a libgcv routine and
+  converters/other commands retargeted to use it.
+
 * look into embedding both rgb[3] and complex[n] data types in a union
  to allow unification of libmultispectral and liboptical APIs to a
  single more general liboptical.  Need to be careful about
@@ -1262,16 +1363,6 @@ LIBGED

 * See src/libged/TODO for new command and subcommand ideas.

-* the lt [-c] obj command looks like it should be replaceable with
-  a search command (search obj -depth 1) and a more powerful -print
-  option that can do things like mimic tcl style output and create
-  lists with user specified character separation.  Enhance search
-  to do more powerful printing, then make lt an alias to a search
-  call.
-
-* pull work on rm command out of history (commit r67394 reverted it)
-  and take it to a production ready stage.
-
 * libged needs to support "temporary" objects that are in-memory only
  and will disappear when the ged instance is destroyed, yet is
  otherwise considered real objects in a given database.  this
@@ -1313,155 +1404,6 @@ LIBGED
  common code in src/libanalyze (there may be more candidates around
  the tree)

-* Extract bounding box code from both autoview.c and get_autoview.c
-  into a general bounding rpp function in librt and use accordingly
-  (particularly in libged).  Should combine autoview.c with
-  get_autoview.c (perhaps as a flag) and utilize the general function
-  in lots of places (e.g., the ged_arb() function).
-
-* Explore possibility of expanding dm command to accept object names
-  as a way of tweaking display manager specific properties (wireframe
-  vs solid drawing, shading on normals, etc.) that are currently
-  controlled only via the draw command.  Many of the undocumented (or
-  poorly documented) draw options are very specific and there are many
-  more possible similar options that aren't defined.  Initial thought
-  is to allow passing "dm" subcommands to draw (maybe --dm key=val or
-  some such) and using the dm command to offer display type aware
-  hooks (for example, solid drawing isn't a valid option in text mode
-  display, so options about how to shade normals don't make much
-  sense.  On the other hand, a full scene graph could have many
-  per-object display options the user (or application) would want to
-  tweak on a per object basis, e.g. dm obj.r transparency 0.3. Hard
-  wiring draw options isn't going to be flexible or user friendly;
-  need something similar to the new dm ability to supply dm-backend
-  specific options to the user.
-
-* use the globbing work needed for proper rm support to enhance the
-  ls command.  dbfind's behavior can be emulated by search, but the
-  speed of dbfind is not practical in search due to the potential
-  generality of search's filters.  search would have to pre-process
-  its plan and prove it needed to examine only a subset of the full
-  hierarchy in advance.  ls */objname is a better match for what
-  dbfind is actually doing, and if need be we could add a
-  --print-parent option or some such to precisely mimic dbfind's
-  output.
-
-* make the idents command not list subtracted objects by default,
-  optionally list everything
-
-* improve performance of these commands that seem to have exponential
-  cost: bot_split, killtree, and
-  make s sph; make a arb8; sed a; e a; tra 0 0 500; r hemi u s - a; tol norm 1 ; facetize hemi.bot hemi
-  # compared to tol norm 2, # triangles is up ~20% but facetize is >200%
-
-* translate lc command to libged (discovered in Feb. 2015 to have already
-  been done -- need information regarding when this was done and committed).
-
-* BoT mesh editing command.  Subtasks:
-
-  - enumerate functions desirable
-  - catalog features of other mesh manipulation tools
-  - investigate mesh editing libraries and/or relying on NMG editing
-  - bind GUI editing to the BoT mesh editing command
-
-* object error heuristic.  implement a function/command to report how
-  big of an error a given geometry object has.  the intent is to help
-  prioritize geometry modeling errors based on their spatial impact.
-  this is particularly relevant for nurbs/brep and nmg geometry where
-  there may be solidity gaps in the topology that need to be sealed or
-  dangling faces/surfaces of different sizes.  this is meant to be a
-  relative heuristic applicable across all geometry, not necessary an
-  exact measure.  this may make more sense added as an output option
-  to glint or as a warning category for a geometry debugger.
-
-* implement a region anointment feature where the user can turn an
-  assembly into a region and change all lower or higher regions into
-  combinations.  basically consolidate or distribute region flags.
-  this is partially covered by the 'comb' command but it tries hard to
-  ensure geometry isn't left in a broken state.  needs to be a way to
-  do the simple consolidate/distribute operation regardless of
-  resulting state.
-
-* update search depth options (above + below) to make sure the logic
-  supports depth=0 / above=0 / below=0 meaning the current node.
-
-* the 'comb' command both updates and creates combinations.  this is a
-  problem because it's not possible to infer an intended result from
-  the command string alone.  it should either append to an existing
-  combination and fail if it doesn't exist (with flag to create) OR it
-  should create a combination and fail if there is an existing
-  combination (with flag to append).
-
-* Update the comb "region lift" capability to handle automatic duplication
-  and substitution of the duplicate into the tree of combs who can't have
-  their definitions changed without impacting other geometry in the .g file.
-
-* change 'mirror' command offset to be prior to mirror instead of
-  after, so that you can mirror intuitively over a specified point
-  along a given axis.
-
-* add option to 'mirror' command to delete the source object.  support
-  specification of a plane as the view plane, 3 points, XY, YZ, XZ.
-
-* add an option to the bb command for calculating a bounding box that
-  encompasses subtracted objects and trimmed surfaces and default to
-  calculating a tight-fitting fbounding box once we have a robust path
-  from geom->NURBS+CSG->NURBS.
-
-* killall command reports db_lookup failures if the target object
-  doesn't exist (maybe we only care about refs).  should keep quiet.
-
-* the new "exists" command is a beautiful corollary to the unix 'test'
-  command.  make the usage match, remove options that make no sense
-  after you've replaced instances of 'file' with 'object', and add
-  options specific to testing geometry (like whether two objects
-  overlap, whether an object's volume is greater than some value or
-  equal to zero, whether two objects are actually the same object
-  (geometrically), etc.).
-
-* replace sed and oed commands: functionality provided by new 'edit'
-  command, but requires testing (unit tests) to make sure it's working
-  correctly.
-
-* make sure 'preview' works, particularly the 'tree' subcommand.
-
-* add support for a custom unit conversion factor to the units command
-  (e.g. 'units 9.3120223' or 'units metertons 9.3120223')
-
-* deprecate dbfind - ensure functionality is fully captured by the
-  search and ls commands, make it report a deprecation statement on
-  use and utilize ls under the hood.
-
-* implement some sort of archive/backup command in mged in order to
-  save the currently open database out to a file.
-
-* add a -color option to all mged commands that draw geometry (B, eid,
-  and E come to mind)
-
-* have mged record a timestamped command history by default
-
-* implement -exec support for 'search' command
-
-* implement -param support for 'search' command
-
-* implement 'analyze' command option to write output to a file
-
-* implement mged object name globbing similar to tclsh's globbing
-  (i.e. via a globbing command and quoting globs that use []).  testing
-  shows db_glob doesn't seem to behave correctly, at least not like
-  glob.  hook globbing into all commands so glob_compat_mode
-  statefulness can go away.  a db_glob expression that doesn't match
-  anything should not return the expression.
-
-* incorporate some variety of spatial partitioning into the facetize
-  command (may involve just rewriting it) to try and realize MUCH
-  faster tessellation of CSG geometry.  Current routines are doing a
-  lot of unnecessary work that tends to result in explosive completion
-  times for worst-case scenarios - try to get closer to the "only do
-  the work we need to" ideal.  Once a new idea is proven in that
-  command, it should be made into a libgcv routine and
-  converters/other commands retargeted to use it.
-

 SHADED DISPLAYS
 ---------------
@@ -1478,9 +1420,6 @@ ARCHER
 ATTRIBUTES
 ----------

-* See src/libbu/TODO.binary_attributes for more info about
-  bson based binary attribute work.
-
 * attr command option to output to a file

 * attr command change to only output non-standard attributes
@@ -1687,13 +1626,6 @@ NEW OBJECTS
  view (i.e., a grid of primary rays), and 3) rtgl point samples
  (which is a variant of 2 but potentially view independent).

-  Considerations:
-    fast dictionary with expiration by time? (eviction during writes)
-    cache rate read/write / sec > 10k @ 500bytes
-    remain fast with millions of entries
-    immediate retrieval (consistency)
-    provide for concurrent access (concurrency), perhaps via sharding (N locks)
-
 * alias objects.  this is an object handle in a geometry database that
  refers to another geometry database object.  in effect, it
  encapsulates the idea of a symbolic reference for database objects.
@@ -1824,6 +1756,7 @@ The following binaries are not yet available on Windows.  The reason
 is identified in parentheses.

 bombardier (possibly just a problem with the build logic)
+burst      (TERMLIB)
 enigma     (not ported)
 fbcolor    (TERMLIB)
 fbed       (TERMLIB)
@@ -1850,9 +1783,6 @@ missing on Windows due to needing lex.
 CONVERTERS
 ----------

-* add gcv support for the Microstation file format (DGN), probably
-  leveraging http://dgnlib.maptools.org/ (MIT-licensed)
-
 * integrate the submitted x3d-g (Web3D, VRML successor) importer
  (pending patch on sf)

@@ -2258,80 +2188,152 @@ DOCUMENTATION

 * add missing manual pages (tbrowder2 generated list 2013-08):

+    3dm-g
+    a-d
+    alias-pix
+    all_sf
+    anim_cascade
+    anim_fly
+    anim_hardtrack
+    anim_keyread
+    anim_lookat
+    anim_offset
+    anim_orient
    archer
+    asc2pix
+    bolt
    bombardier
+    bot-bldxf
+    brep_cube
+    brep_simple
+    brepintersect
+    breplicator
+    brickwall
+    brlman
+    burst
+    bw-a
+    bw-d
+    bwish
+    c-d
+    chan_add
+    check-express
+    clutter
+    contours
+    csgbrep
+    d-a
+    d-bw
+    d-f
+    d-i
+    d-u
+    d2-c
    damdf
    dauto
    dauto2
    dconv
    ddisp
+    dem-g
    dfft
    dmod
+    double-asc
    dpeak
    dsel
+    dsp_add
    dstats
    dwin
-    ihist
-    imod
-    isst
-    istats
-    lowp
-    pix3filter
-    pixcount
-    pixelswap
-    pixembed
-    plot3stat
-    rtsrv
-    smod
-    umod
-    ustats
-
-* these are matured shape tools that get installed with simple
-  usability but should still have basic docs and better names.  plan
-  to absorb them into ged as external plugins, but they'll still need
-  docs:
-
-    bolt
+    euclid_format
+    euclid_unformat
+    f-d
+    f-i
+    fbgammamod
    fence
-    gastank
-    handle
-    human
-    picket_fence
-    window
-    window_frame
-    wire
-
-* misc / 3rd party tools we control / bundle, but need docs if anyone
-  else is to use them or contribute:
-
-    perplex
-    re2c
-
-* needs his own repo:
-
-    ttcp
-
-* need to revisit utility of spherical mapping, used by sh_spm and
-  sh_points, used for environment mapping (e.g., stars):
-
-    pix-spm
-    spm-fb
-
-* these eventually get put into gcv (hopefully not needing docs):
-
-    3dm-g
-    dem-g
+    fhor
+    fix_polysolids
    g-dot
+    g-euclid1
    g-jack
    g-off
    g-step
    g-voxel
+    gastank
+    globe
+    handle
+    human
+    i-a
+    i-d
+    i-f
+    ihist
+    imod
+    isst
+    istats
    jack-g
+    kurt
+    lens
+    lowp
+    masonry
+    menger
+    metaball
+    mkbuilding
+    molecule
+    nmg-sgp
+    nmgmodel
    off-g
+    pdb-g
+    perplex
+    picket_fence
+    pipe
+    pix-spm
+    pix-yuv
+    pix2g
+    pix3filter
+    pixcount
+    pixelswap
+    pixembed
+    pixfields
+    pixfieldsep
+    pixflip-fb
+    pixpaste
+    plot3-dm
+    plot3stat
+    pyramid
    raw-g
+    rawbot
+    re2c
+    ringworld
+    room
+    rtcell
+    rtfrac
+    rtrad
+    rtsil
+    rtsrv
+    script-tab
    shp-g
+    sketch
+    smod
+    sphflake
+    spm-fb
+    ssampview
    step-g
+    surfaceintersec
+    tea
+    tea_nmg
+    texturescale
    tgf-g
+    torii
+    ttcp
+    tube
+    u-a
+    u-bw
+    u-d
+    u-f
+    umod
+    ustats
+    vegetation
+    wavy
+    window
+    window_frame
+    wire
+    xyz-plot3
+    yuv-pix

 * DocBook: create a DB index.xml to generate a doc listing (with
  hot links) for the html and pdf collection
@@ -2356,8 +2358,9 @@ DOCUMENTATION
  CMake supports other generators, wouldn't hurt to detail how to
  trigger builds in them (MSVC is partially covered, make sure to
  coverage is complete - others include Eclipse, XCode once we get the
-  kinks ironed out there, CodeBlocks.  Ninja build tool and its
-  CMake support are worth documenting too.
+  kinks ironed out there, CodeBlocks.  New experimental ninja build
+  tool and its (also experimental) CMake support are promising -
+  if/when CMake support goes mainstream, document that too.)

 * all of the rt* tracers share common code and common options, but do
  not share common documentation.  refactor documentation to use
@@ -10,10 +10,6 @@ while [ "$1" != "" ]
 do
   case $1
   in
-     --enable-all)                options="$options -DBRLCAD_BUNDLED_LIBS=ON";
-                                  shift;;
-     --disable-all)                options="$options -DBRLCAD_BUNDLED_LIBS=OFF";
-                                  shift;;
     --enable-opengl)                options="$options -DBRLCAD_ENABLE_OPENGL=ON";
                                  shift;;
     --disable-opengl)                options="$options -DBRLCAD_ENABLE_OPENGL=OFF";
@@ -90,6 +86,10 @@ do
                                  shift;;
     --disable-docbook)                options="$options -DBRLCAD_EXTRADOCS=OFF";
                                  shift;;
+     --enable-all)                options="$options -DBRLCAD_BUNDLED_LIBS=ON";
+                                  shift;;
+     --disable-all)                options="$options -DBRLCAD_BUNDLED_LIBS=OFF";
+                                  shift;;
     --enable-lemon)                options="$options -DBRLCAD_LEMON=BUNDLED";
                                  shift;;
     --disable-lemon)                options="$options -DBRLCAD_LEMON=SYSTEM";
@@ -130,6 +130,10 @@ do
                                  shift;;
     --disable-tinycthread)                options="$options -DBRLCAD_TINYCTHREAD=SYSTEM";
                                  shift;;
+     --enable-freetype)                options="$options -DBRLCAD_FREETYPE=BUNDLED";
+                                  shift;;
+     --disable-freetype)                options="$options -DBRLCAD_FREETYPE=SYSTEM";
+                                  shift;;
     --enable-termlib)                options="$options -DBRLCAD_TERMLIB=BUNDLED";
                                  shift;;
     --disable-termlib)                options="$options -DBRLCAD_TERMLIB=SYSTEM";
@@ -8,7 +8,6 @@ set(G_BENCHMARK_MODELS
 )

 set(G_SAMPLE_MODELS
-  aet.asc
  axis.asc
  boolean-ops.asc
  castle.asc
@@ -1,68 +0,0 @@
-title {Untitled BRL-CAD Database}
-units mm
-put {xyzringtrc.s} tgc V {0.31168735027313232421875 0.31356084346771240234375 0.2343517243862152099609375}  H {-0.02296111360192298889160156 -0.02476786263287067413330078 0.03948847576975822448730469}  A {-0.003937630914151668548583984 -0.02411045134067535400390625 -0.01741208322346210479736328}  B {0.02662250958383083343505859 -0.01068659685552120208740234 0.008777192793786525726318359}  C {-3.937628207495436072349548E-05 -0.0002411044843029230833053589 -0.0001741207961458712816238403}  D {0.0002662249607965350151062012 -0.0001068659257725812494754791 8.77717902767471969127655E-05} 
-put {viewdirtrc.s} tgc V {0.08660250157117843627929688 0.08660250157117843627929688 0.08660250157117843627929688}  H {-0.07794228941202163696289062 -0.07794228941202163696289062 -0.07794228941202163696289062}  A {0 0.02828427031636238098144531 -0.02828427031636238098144531}  B {0.03265986219048500061035156 -0.01632993109524250030517578 -0.01632993109524250030517578}  C {0 0.000212132028536871075630188 -0.000212132028536871075630188}  D {0.0002449489838909357786178589 -0.0001224744919454678893089294 -0.0001224744919454678893089294} 
-put {twistpanel.r} comb region yes tree {l twistpanel.c}
-attr set {twistpanel.r} {color} {232/198/232} {shader} {glass {tr 0.6}} {region} {R} {region_id} {1000} {material_id} {1} {los} {100}
-put {xyzringcut.c} comb region no tree {- {- {- {- {- {- {- {- {- {- {l ringxyztor.s} {l cut0.s}} {l cut1.s}} {l cut2.s}} {l cut4.s}} {l xrcc.s}} {l yrcc.s}} {l zrcc.s}} {l viewdirrcc.s}} {l xyzcutrcc.s}} {l xyzringtrc.s}}
-put {viewdirrcc.s} tgc V {0.779421329498291015625 0.779421329498291015625 0.779421329498291015625}  H {-0.6928203105926513671875 -0.6928203105926513671875 -0.6928203105926513671875}  A {0 0.007071067579090595245361328 -0.007071067579090595245361328}  B {0.008164965547621250152587891 -0.004082482773810625076293945 -0.004082482773810625076293945}  C {0 0.007071067579090595245361328 -0.007071067579090595245361328}  D {0.008164965547621250152587891 -0.004082482773810625076293945 -0.004082482773810625076293945} 
-put {twistpanel.c} comb region no tree {- {- {- {l twistrcc.s} {l twisttor.s}} {l twisttrc.s}} {l viewdirrcc.s}}
-put {ringxytor.s} tor V {0 0 0}  H {0 0 1}  r_a 0.5 r_h 0.009999999776482582092285156
-put {twistring.r} comb region yes tree {l twistring.c}
-attr set {twistring.r} {color} {232/198/232} {shader} {mirror {tr .1 re 0.4}} {region} {R} {region_id} {1000} {material_id} {1} {los} {100}
-put {xyringtrc.s} tgc V {0.3913685381412506103515625 0.3006020486354827880859375 -0.0009004921885207295417785645}  H {-0.03143119439482688903808594 0.04401883110404014587402344 -0.0006720747915096580982208252}  A {0.02089671231806278228759766 0.01464617997407913208007812 -0.01800444535911083221435547}  B {-0.01446941774338483810424805 -0.01072130445390939712524414 -0.02551533468067646026611328}  C {0.0002089670742861926555633545 0.0001464617671445012092590332 -0.0001800443860702216625213623}  D {-0.0001446941751055419445037842 -0.0001072130180546082556247711 -0.0002551533398218452930450439} 
-put {xyzcutrcc.s} arb8 V1 {0.285196959972381591796875 0.223926544189453125 0.2792418301105499267578125}  V2 {0.3270788453519344329833984 0.2655878327786922454833984 0.2198253460228443145751953}  V3 {0.3691307827830314636230469 0.3075636327266693115234375 0.2788994473521597683429718}  V4 {0.3272488489747047424316406 0.2659022919833660125732422 0.3383159413933753967285156}  V5 {0.2260562554001808166503906 0.2832767628133296966552734 0.2791691728780278936028481}  V6 {0.2679381202906370162963867 0.3249380290508270263671875 0.2197526805102825164794922}  V7 {0.3099901042878627777099609 0.366913974285125732421875 0.2788267984578851610422134}  V8 {0.2681080885231494903564453 0.3252525255084037780761719 0.3382433503866195678710938} 
-put {xyringcut.c} comb region no tree {- {- {- {- {- {- {- {- {- {l ringxytor.s} {l cut0.s}} {l cut1.s}} {l cut3.s}} {l xrcc.s}} {l yrcc.s}} {l zrcc.s}} {l ringxyztor.s}} {l xycutrcc.s}} {l xyringtrc.s}}
-put {testdisks.c} comb region no tree {u {- {- {- {l xyzrcc.s} {l cut0.s}} {l cut1.s}} {l cut2.s}} {- {- {- {- {- {l xyrcc.s} {l cut0.s}} {l cut1.s}} {l cut2.s}} {l cut3.s}} {l cut0.s}}}
-put {twistring.c} comb region no tree {u {- {- {l twisttor.s} {l twistcut.s}} {l twisttrc.s}} {l twisttrc.s}}
-put {halfplane.s} half N {0 0 1}  d -0.536277353763580322265625
-put {halfplane.r} comb region yes tree {l halfplane.s}
-attr set {halfplane.r} {color} {255/255/255} {shader} {stack {{phong   {sp 0.05 di 0.95}} }} {region} {R} {region_id} {1002} {material_id} {1} {los} {100}
-put {twisttor.s} tor V {0.449999988079071044921875 0.449999988079071044921875 0.449999988079071044921875}  H {-0.577350269189625731058868 -0.577350269189625731058868 -0.577350269189625731058868}  r_a 0.1500000016475442066177237 r_h 0.01000000030444709100962974
-put {twistcut.s} part V {0.3950000000000000177635684 0.3850000000000000088817842 0.5649999999999999467092948}  H {0.0003640000000000000114804 -0.0003699999999999999946917462 -0.0005000000000000000104083409}  r_v 0.02800000000000000058286709 r_h 0.02800000000000000058286709
-put {twisttrc.s} tgc V {0.37255561351776123046875 0.40711653232574462890625 0.57051956653594970703125}  H {0.03641721233725547790527344 -0.03706122934818267822265625 -0.0005011741304770112037658691}  A {0.01779515855014324188232422 0.01750466972589492797851562 -0.001385415205731987953186035}  B {0.001156966434791684150695801 0.0007993413601070642471313477 0.02496042102575302124023438}  C {0.0001779512967914342880249023 0.0001750463998178020119667053 -1.385413543175673112273216E-05}  D {1.156978123617591336369514E-05 7.993325198185630142688751E-06 0.0002496042288839817047119141} 
-put {xyzpanel.r} comb region yes tree {l xyzcut.c}
-attr set {xyzpanel.r} {color} {205/253/172} {shader} {glass {tr 0.6}} {region} {R} {region_id} {1003} {material_id} {1} {los} {100}
-put {twistrcc.s} tgc V {0.4472982883453369140625 0.4472982883453369140625 0.4472982883453369140625}  H {0.005773502867668867111206055 0.005773502867668867111206055 0.005773502867668867111206055}  A {0 -0.1060660183429718017578125 0.1060660183429718017578125}  B {0.1224744841456413269042969 -0.06123724207282066345214844 -0.06123724207282066345214844}  C {0 -0.1060660183429718017578125 0.1060660183429718017578125}  D {0.1224744841456413269042969 -0.06123724207282066345214844 -0.06123724207282066345214844} 
-put {xycutrcc.s} arb8 V1 {0.4098457992076873779296875 0.330240428447723388671875 -0.03679068386554718017578125}  V2 {0.3675903864204883575439453 0.3863152638077735900878906 -0.03679068386160150305741467}  V3 {0.3675903864204883575439453 0.3863152638077735900878906 0.03342260420322418212890625}  V4 {0.4098457992100617008901509 0.3302404284445723536833839 0.03342260420322418212890625}  V5 {0.3537709638476371765136719 0.2879850156605243682861328 -0.03679068386554718017578125}  V6 {0.3115155547857284545898438 0.3440598426386713981628418 -0.03679068386160150305741467}  V7 {0.3115155547857284545898438 0.3440598426386713981628418 0.03342260420322418212890625}  V8 {0.3537709638476371765136719 0.2879850156605243682861328 0.03342260420322418212890625} 
-put {cutdisks.c} comb region no tree {- {- {- {- {- {l disks.c} {l cut0.s}} {l cut1.s}} {l cut2.s}} {l cut3.s}} {l cut4.s}}
-put {twistcut.s.backu} ell V {0.3945335447788238525390625 0.383843958377838134765625 0.5655720233917236328125}  A {0.03095294535160064697265625 -0.0002858481311704963445663452 -0.0002035317302215844392776489}  B {0.0002871743054129183292388916 0.03095294535160064697265625 0.0002016565413214266300201416}  C {0.0002016565558733418583869934 -0.0002035317156696692109107971 0.03095364384353160858154297} 
-put {xyzring.r} comb region yes tree {u {l xyzringcut.c} {l xyzringtrc.s}}
-attr set {xyzring.r} {color} {230/253/215} {shader} {mirror {tr .1 re 0.4}} {region} {R} {region_id} {1005} {material_id} {1} {los} {100}
-put {viewdir.r} comb region yes tree {l viewdir.c}
-attr set {viewdir.r} {color} {253/227/198} {shader} {phong   {tr .1 ri 1.5 sh 2}} {region} {R} {region_id} {1001} {material_id} {1} {los} {100}
-put {xypanel.r} comb region yes tree {l xycut.c}
-attr set {xypanel.r} {color} {178/221/243} {shader} {glass {tr 0.6}} {region} {R} {region_id} {1002} {material_id} {1} {los} {100}
-put {diagram.r} comb region no tree {u {u {u {l arrows.r} {l twistpanel.r}} {u {l twistring.r} {l xypanel.r}}} {u {u {l xyring.r} {l xyzpanel.r}} {u {l xyzring.r} {l viewdir.r}}}}
-put {viewdir.c} comb region no tree {u {l viewdirrcc.s} {- {- {- {l viewdirtrc.s} {l xrcc.s}} {l yrcc.s}} {l zrcc.s}}}
-put {arrows.r} comb region yes tree {l coordinates.c}
-attr set {arrows.r} {color} {217/217/254} {shader} {mirror {tr .1 re 0.4}} {region} {R} {region_id} {1001} {material_id} {1} {los} {100}
-put {xyring.r} comb region yes tree {u {l xyringcut.c} {l xyringtrc.s}}
-attr set {xyring.r} {color} {206/230/242} {shader} {mirror {tr .1 re 0.4}} {region} {R} {region_id} {1004} {material_id} {1} {los} {100}
-put {ground.s} ell V {0 0 -10000.08984375}  A {10000 0 0}  B {0 6.12303176911188629105709E-13 10000}  C {0 -10000 6.12303176911188629105709E-13} 
-put {xyzcut.c} comb region no tree {- {- {- {- {- {- {- {- {- {- {- {l xyzrcc.s} {l cut0.s}} {l cut1.s}} {l cut2.s}} {l cut4.s}} {l xrcc.s}} {l yrcc.s}} {l zrcc.s}} {l viewdirtrc.s}} {l viewdirrcc.s}} {l ringxyztor.s}} {l xyzringtrc.s}}
-put {ground.r} comb region yes tree {l ground.c}
-attr set {ground.r} {color} {255/255/255} {shader} {stack {{checker {b  {192 192 192} s 8192.0}} {phong   {sp 0.8 sh 4 em .5}} }} {region} {R} {region_id} {1001} {material_id} {1} {los} {100}
-put {xyzrcc.s} tgc V {0.005014000460505485534667969 -0.004998999647796154022216797 7.123547086408665851564592E-19}  H {-0.009999999776482582092285156 0.009999999776482582092285156 0}  A {-0.356000006198883056640625 -0.356000006198883056640625 0}  B {0 0 0.5}  C {-0.356000006198883056640625 -0.356000006198883056640625 0}  D {0 0 0.5} 
-put {ground.c} comb region no tree {l ground.s}
-put {disks2.c} comb region no tree {u {- {- {- {- {l xyzrcc.s} {l cut0.s}} {l cut1.s}} {l cut2.s}} {l xyrcc.s}} {- {- {- {l xyrcc.s} {l cut0.s}} {l cut1.s}} {l cut2.s}}}
-put {light.s} ell V {-98.451141357421875 103.03456878662109375 200.0417633056640625}  A {14 0 0}  B {0 14 0}  C {0 0 14} 
-put {light.r} comb region yes tree {l light.s}
-attr set {light.r} {color} {255/255/255} {shader} {light {a 270 d  {1 0 0} s 16 v 0}} {region} {R} {region_id} {1002} {material_id} {1} {los} {100}
-put {xyrcc.s} tgc V {0 0 -0.004999999888241291046142578}  H {0 0 0.009999999776482582092285156}  A {0 -0.5 0}  B {0.5 0 0}  C {0 -0.5 0}  D {0.5 0 0} 
-put {xycut.c} comb region no tree {- {- {- {- {- {- {- {- {- {- {- {l xyrcc.s} {l cut0.s}} {l cut1.s}} {l cut3.s}} {l xrcc.s}} {l yrcc.s}} {l zrcc.s}} {l xyzrcc.s}} {l ringxytor.s}} {l viewdirtrc.s}} {l xyringtrc.s}} {l viewdirrcc.s}}
-put {disks.c} comb region no tree {u {- {l xyzrcc.s} {l xyrcc.s}} {l xyrcc.s}}
-put {rings.c} comb region no tree {u {l ringxytor.s} {l ringxyztor.s}}
-put {ztec.s} tgc V {0 0 1}  H {0 0 0.1000000014901161193847656}  A {0.02999999932944774627685547 0 0}  B {0 0.02999999932944774627685547 0}  C {0.0003000000142492353916168213 0 0}  D {0 0.0003000000142492353916168213 0} 
-put {ytec.s} tgc V {0 1 0}  H {0 0.1000000014901161193847656 0}  A {0.02999999932944774627685547 0 0}  B {0 0 0.02999999932944774627685547}  C {0.0003000000142492353916168213 0 0}  D {0 0 0.0003000000142492353916168213} 
-put {xtec.s} tgc V {1 0 0}  H {0.1000000014901161193847656 0 0}  A {0 0.02999999932944774627685547 0}  B {0 0 0.02999999932944774627685547}  C {0 0.0003000000142492353916168213 0}  D {0 0 0.0003000000142492353916168213} 
-put {zrcc.s} tgc V {0 0 0}  H {0 0 1}  A {0 -0.009999999776482582092285156 0}  B {0.009999999776482582092285156 0 0}  C {0 -0.009999999776482582092285156 0}  D {0.009999999776482582092285156 0 0} 
-put {yrcc.s} tgc V {0 0 0}  H {0 1 0}  A {0 0 0.009999999776482582092285156}  B {0.009999999776482582092285156 0 0}  C {0 0 0.009999999776482582092285156}  D {0.009999999776482582092285156 0 0} 
-put {xrcc.s} tgc V {0 0 0}  H {1 0 0}  A {0 0 -0.009999999776482582092285156}  B {0 0.009999999776482582092285156 0}  C {0 0 -0.009999999776482582092285156}  D {0 0.009999999776482582092285156 0} 
-put {cut4.s} arb8 V1 {1 1 1}  V2 {1 -1 1}  V3 {-1 -1 1}  V4 {-1 1 1}  V5 {-1 -1 -1}  V6 {-1 -1 -1}  V7 {-1 -1 -1}  V8 {-1 -1 -1} 
-put {cut3.s} arb8 V1 {1.010072231292724609375 1.0000178813934326171875 1.010089874267578125}  V2 {1.010072231292724831419605 1.0000178813934326171875 -1.0000002384185791015625}  V3 {-1.0000178813934326171875 -1.010072231292724609375 -1.0000002384185791015625}  V4 {-1.0000178813934326171875 -1.010072231292724609375 1.01008987426757901317842}  V5 {-1.0000178813934326171875 1.0000178813934326171875 -1.0000002384185791015625}  V6 {-1.0000178813934326171875 1.0000178813934326171875 -1.0000002384185791015625}  V7 {-1.0000178813934326171875 1.0000178813934326171875 -1.0000002384185791015625}  V8 {-1.0000178813934326171875 1.0000178813934326171875 -1.0000002384185791015625} 
-put {cut2.s} arb8 V1 {1 -1 -1.0051000118255615234375}  V2 {1 1 -1.0051000118255615234375}  V3 {1 1 -0.0051000118255615234375}  V4 {1 -1 -0.0051000118255615234375}  V5 {-1 -1 -1.0051000118255615234375}  V6 {-1 1 -1.0051000118255615234375}  V7 {-1 1 -0.0051000118255615234375}  V8 {-1 -1 -0.0051000118255615234375} 
-put {cut1.s} arb8 V1 {0 -1 -1}  V2 {0 1 -1}  V3 {0 1 1}  V4 {0 -1 1}  V5 {-1 -1 -1}  V6 {-1 1 -1}  V7 {-1 1 1}  V8 {-1 -1 1} 
-put {cut0.s} arb8 V1 {1 -1 -1}  V2 {1 0 -1}  V3 {1 0 1}  V4 {1 -1 1}  V5 {-1 -1 -1}  V6 {-1 0 -1}  V7 {-1 0 1}  V8 {-1 -1 1} 
-put {coordinates.c} comb region no tree {u {u {u {u {u {- {- {l xrcc.s} {l yrcc.s}} {l zrcc.s}} {- {- {l yrcc.s} {l xrcc.s}} {l zrcc.s}}} {- {- {l zrcc.s} {l xrcc.s}} {l yrcc.s}}} {l xtec.s}} {l ytec.s}} {l ztec.s}}
-put {ringxyztor.s} tor V {0 0 0}  H {-0.7071067811865475727373109 0.7071067811865475727373109 0}  r_a 0.4999999914428644998132256 r_h 0.009999999670806607177109271
@@ -33,41 +33,13 @@ macro(ADD_NIST_STEP_TARGET step_model folder)
  DISTCLEAN(${log_file})
 endmacro(ADD_NIST_STEP_TARGET step_model folder)

-# Get our root path
-if(CMAKE_CONFIGURATION_TYPES)
-  set(bin_root "${CMAKE_BINARY_DIR}/${CMAKE_CFG_INTDIR}")
-else(CMAKE_CONFIGURATION_TYPES)
-  set(bin_root "${CMAKE_BINARY_DIR}")
-endif(CMAKE_CONFIGURATION_TYPES)
-
-# The general pattern of the BRL-CAD build is to use CMAKE_CFG_INTDIR when
-# multi-configuration builds complicate the location of binaries.  In this
-# case, however, we are using a generated script with a different mechanism
-# for handling this situation, and we need to update the executable paths
-# accordingly if they are configuration dependent.
-if(CMAKE_CONFIGURATION_TYPES)
-  string(REPLACE "${CMAKE_CFG_INTDIR}" "\${BUILD_TYPE}" rbin_root "${bin_root}")
-else(CMAKE_CONFIGURATION_TYPES)
-  set(rbin_root "${bin_root}")
-endif(CMAKE_CONFIGURATION_TYPES)
-
-# Use the CMake executable to figure out if we need an extension
-get_filename_component(EXE_EXT "${CMAKE_COMMAND}" EXT)
-
-
 macro(ADD_NIST_3DM_TARGET rhino_model folder)
-  set(CMD_EXEC ${rbin_root}/${BIN_DIR}/3dm-g${EXE_EXT})
  string(REGEX REPLACE "([0-9a-z]*).3dm" "\\1" rhino_model_root "${rhino_model}")
-  set(output_file ${rbin_root}/${DATA_DIR}/db/${rhino_model_root}.g)
-  set(log_file ${CMAKE_CURRENT_BINARY_DIR}/${rhino_model_root}.log)
-  set(STDOUT_LOG "${log_file}")
-  set(STDERR_LOG "${log_file}")
-  set(CMD_ARGS "-o \"${output_file}\" \"${CMAKE_CURRENT_SOURCE_DIR}/${rhino_model}\"")
-  configure_file(${BRLCAD_CMAKE_DIR}/builddir_cmd.cmake.in ${CMAKE_CURRENT_BINARY_DIR}/3dm-g.cmake @ONLY)
  set(output_file ${bin_root}/${DATA_DIR}/db/${rhino_model_root}.g)
+  set(log_file ${CMAKE_CURRENT_BINARY_DIR}/${rhino_model_root}.log)
  add_custom_command(
    OUTPUT ${output_file}
-    COMMAND ${CMAKE_COMMAND} -P ${CMAKE_CURRENT_BINARY_DIR}/3dm-g.cmake
+    COMMAND 3dm-g -o ${output_file} ${CMAKE_CURRENT_SOURCE_DIR}/${rhino_model} > ${log_file} 2>&1
    DEPENDS 3dm-g ${CMAKE_CURRENT_SOURCE_DIR}/${rhino_model}
  )
  add_custom_target(${rhino_model_root}.g ALL DEPENDS ${output_file})
@@ -225,6 +225,7 @@ CMAKEFILES(
  README.OSCON-2014
  STARTERS
  STRATEGY
+  burst
  csv_to_comgeom.txt
  implicit_constraints.txt
  pad_file.xml.in
@@ -15,7 +15,7 @@ familiar with the project.

 * Render some pictures using rt and rtedge

-* Perform basic geometric analysis using rtarea, rtweight, and gqa
+* Perform basic geometric analysis using rtarea, rtweight, and g_qa

 * Write a procedural geometry tool (see examples in src/proc-db)

@@ -29,17 +29,6 @@ familiar with the project.

 * Implement one of the items listed on the request for enhancements tracker

--
-There are lots of possible non-coding tasks:
-
-* Write documentation
-* Improve the website
-* Offer to help with art and design
-* Engage in discussions
-* Write design docs
-* Update roadmap
-* Answer questions, be helpful
-* Give a presentation on some topic

 ---
 There may be more tasks and ideas available in the Tasks section of
@@ -98,7 +98,7 @@ libXext-devel
 libXi-devel
 freetype-devel
 fontconfig-devel
-mesa-libGL-devel
+

 To determine what particular version of Redhat or Fedora you are
 using, check these files:
@@ -65,201 +65,172 @@ bolster those areas, and identifies specific actionable objectives.
  strategic areas devising measurable tasks that support the
  particular objective.

+** PROJECT: Deploy Archer

-** PROJECT: Deploy Archer/MGED Beta (14)
-
-*** interactivity / blocking indicators - ALPHA (3)
-**** TODO multithreaded command execution (2)
-**** TODO interface busy indicator (1)
-
-*** command cleanup - ALPHA (3)
-**** TODO inventory + mapping + time (1)
-**** TODO design UI / commands (2)
-**** TODO sit with users to discuss command migration (0)
-
-*** feature parity - ALPHA (2)
-**** TODO review/finish edit keypointing (oed parity) (1)
-**** TODO GUI matrix editing (1)
+*** command cleanup - ALPHA+
+**** TODO inventory + mapping + time
+**** TODO design UI / commands
+**** TODO QA acceptance from users
+**** TODO announce / share / sit with users
    
-*** announcements + migration plan - BETA+ (4)
-**** TODO write + publish strategy map and migration plan (1)
-**** TODO preliminary discussion with users, discuss tcl scripts (0)
-**** TODO archer manual page (1)
-**** TODO install basic version of new website (1)
-**** TODO sit down review with users (1)
-
-*** searchable docs - ALPHA (2)
-**** TODO command line searching of doc content, apropos (2)
+*** interactivity / blocking indicators - ALPHA
+**** TODO multithreaded command execution
+**** TODO interface busy indicator
+**** TODO drawing indicator
+     
+*** feature parity - ALPHA
+**** TODO classic console mode
+**** TODO review/finish edit keypointing (oed parity)
+**** TODO summarize features
+**** TODO create mapping from old to new
+**** TODO GUI matrix editing
+**** TODO reverse tempfile
+**** TODO query ray control GUI
+    
+*** undo - BETA
+**** TODO implement libbu filesystem info
+**** TODO re-enable undo with fs awareness
+    
+*** bug reporting / feedback / metrics - BETA
+**** TODO reliable backtrace
+**** TODO hook/enable bombardier
+**** TODO in-app feedback dialog
+**** TODO track metrics (archer commands, tips, docs)
+    
+*** QA acceptance - BETA
+**** TODO run regression w/ archer
+**** TODO sit down reviews (discuss scripts)
+**** TODO define acceptance tasks
+**** TODO run with procedural web scripts
+    
+*** announcements + migration plan - BETA+
+**** TODO write + publish strategy map
+**** TODO write + publish migration plan
+**** TODO review + update tutorials (docs)
+**** TODO create + give presentation
+**** TODO install new website (basic version)
+**** TODO discussion with core stakeholders
+    
+*** searchable docs - FINAL
+**** TODO command line searching of doc content
+**** TODO apropos reading from docbook
+**** TODO web publishing + searching of docs


-** PROJECT: Deploy Merged Archer/MGED Final (16)
+** PROJECT: Concentration

-*** usability parity - BETA (4)
-**** TODO classic console mode (1)
-**** TODO map from old to new, publish summary (1)
-**** TODO reverse .g tempfile backup, edit live (1)
-**** TODO graphical query ray (1)
+*** revisit scope (vision, mission)
+**** TODO communicate intent and updates
+**** TODO develop high-level project roadmap
+**** TODO connect features to markets

-*** undo - BETA (2)
-**** TODO implement libbu filesystem info (1)
-**** TODO re-enable undo with fs awareness (1)
+*** develop command roadmap
+**** TODO inventory of command-line commands, decide keep/refactor/kill
+**** TODO communicate command-line changes
+**** TODO take inventory of ged commands, decide keep/refactor/kill
+**** TODO communicate ged command changes
+**** TODO assess and mitigate deployment risks

-*** bug reporting / feedback / metrics - BETA (3)
-**** TODO reliable backtrace (1)
-**** TODO hook/enable bombardier (1)
-**** TODO track metrics (archer commands, tips, docs) (1)
-
-*** QA acceptance - BETA (3)
-**** TODO define acceptance tasks (1)
-**** TODO run regression w/ archer (1)
-**** TODO make wiki procedural web scripts work (1)
-
-*** announcements + migration plan - BETA+ (3)
-**** TODO review + update tutorials and docs (2)
-**** TODO create + give presentation (1)
-
-*** searchable docs - FINAL (1)
-**** TODO web publishing + searching of docs (1)
+*** unify docs
+**** TODO convert/integrate/kill html+troff docs
+**** TODO consolidate docs, one guide per interface
+**** TODO stub new docs where missing


-** PROJECT: Distilling BRL-CAD (11)
+** PROJECT: Webulgation

-*** revisit scope (vision, mission) (3)
-**** TODO communicate intent and updates (1)
-**** TODO develop high-level project roadmap (1)
-**** TODO connect features to markets (1)
+   FIXME these need to be sorted and ranked

-*** develop command roadmap (4)
-**** TODO inventory of command-line commands, decide keep/refactor/kill (1)
-**** TODO communicate command-line changes (0)
-**** TODO develop command categorization (1)
-**** TODO take inventory of ged commands, decide keep/refactor/kill (1)
-**** TODO communicate ged command changes (0)
-**** TODO assess and mitigate deployment risks (1)
+*** publish docbook docs
+**** TODO instantiate / set up sofat's doc interface
+**** TODO design pdf stylesheet
+**** TODO integrate docs onto website (html+pdf)

-*** integrate docs (4)
-**** TODO plan what to do with html+troff docs (0)
-**** TODO stub new docs where missing (1)
-**** TODO consolidate docs, one guide per interface (2)
-**** TODO kill obsolete docs (0)
-**** TODO migrate e-mail and release notes to web (1)
+*** online doc editing
+**** TODO review sofat edit interface
+**** TODO apply website theme to edit interface
+
+*** publish use cases
+**** TODO post 3+ customer profiles
+**** TODO post top-10 feature highlights
+**** TODO identify alternatives and their highlight mappings
+**** TODO post comparison table with 2+ alternatives
+
+*** set up developer corner
+**** TODO publish doxygen output to website
+**** TODO update doxygen stylesheet to fit theme
+**** TODO ensure buildbot is setup and running handsfree
+**** TODO update buildbot stylesheet to fit theme
+**** TODO post nightly builds
+**** TODO set up cron job to maintain CI and doc updates
+**** TODO announce dev corner to brlcad-devel/brlcad-news
+
+*** improve website usability
+**** TODO set up platform-detected downloads on main page
+**** TODO publish project vitality/stats (ohloh integration)


-** PROJECT: Website Renovation (10)
+** PROJECT: Deploy GCV

-*** improve website usability (1)
-**** TODO set up platform-detected downloads on main page (0)
-**** TODO publish project vitality/stats (openhub integration) (0)
-**** TODO restore search interface (1)
+*** 3dm "round-tripping"
+**** TODO integrate existing importer
+**** TODO NURBS export support
+**** TODO document entity support

-*** publish docbook docs (3)
-**** TODO instantiate / set up sofat's doc interface (1)
-**** TODO design pdf stylesheet (1)
-**** TODO integrate docs onto website (html+pdf) (1)
+*** documentation
+**** TODO convert jon's write-up to docbook
+**** TODO integrate jon's plugin examples
+**** TODO write and publish plugin API policy
+**** TODO write and publish GCV feature profile on website

-*** publish use cases (3)
-**** TODO post 3+ customer profiles (1)
-**** TODO post top-10 feature highlights (1)
-**** TODO identify alternatives and their highlight mappings (1)
-**** TODO post comparison table with 2+ alternatives (0)
+*** CLI usability
+**** TODO design usage / synopsis
+**** TODO provide logging/debugging interface

-*** set up developer corner (3)
-**** TODO ensure buildbot is setup and running handsfree (1)
-**** TODO update buildbot stylesheet to fit theme (0)
-**** TODO post nightly builds (0)
-**** TODO set up cron job to maintain CI and doc updates (1)
-**** TODO announce dev corner to brlcad-devel/brlcad-news (0)
-**** TODO buildbot <-> cdash/lcov/coverity/gccfarm/swamp integration (1)
+*** robust deployment
+**** TODO convert tlib via automated testing
+**** TODO automate extraction of sources from checkout
+**** TODO integrate gcv into mged/archer
+**** TODO troubleshoot JASP export memory issue
+**** TODO integrate bot_dump into gcv


-** PROJECT: Deploy GCV (9)

-*** 3dm "round-tripping" (2)
-**** TODO integrate existing importer (0)
-**** TODO NURBS export support (1)
-**** TODO document entity support (1)
+** PROJECT: Performant Pipeline
+*** bundled ray dispatch
+**** TODO define ray bundling API
+**** TODO audit librt API for performance
+**** TODO convert RT to new bundled API

-*** documentation (3)
-**** TODO convert jon's write-up to docbook (0)
-**** TODO integrate jon's plugin examples (1)
-**** TODO write and publish plugin API policy (1)
-**** TODO write and publish GCV feature profile on website (1)
-
-*** CLI usability (2)
-**** TODO design usage / synopsis (1)
-**** TODO provide logging/debugging interface (0)
-**** TODO integrate bot_dump into gcv (1)
-
-*** robust deployment (2)
-**** TODO convert tlib via automated testing (1)
-**** TODO automate extraction of sources from checkout (0)
-**** TODO integrate gcv into mged/archer (0)
-**** TODO troubleshoot JASP export memory issue (1)
-
-
-** PROJECT: Performant Pipeline (15)
-
-*** coherent Boolean evaluation (3)
-**** TODO preliminary OpenCL conversion (1)
-**** TODO eliminate branching (1)
-**** TODO V&V with specific test cases (1)
-
-*** audit ray dispatching (3)
-**** TODO define ray bundling API (1)
-**** TODO audit librt ray API, consolidate (1)
-
-*** implement bundled ray dispatch (2)
-**** TODO integrate Costa's GSoC work (1)
-**** TODO propagate bundle through spatial partition (1)
-**** TODO convert rt* to new bundled API (1)
-
-*** on-demand NURBS tree-build (4)
-**** TODO formulate a design / approach (1)
-**** TODO dynamic tree build with minimal malloc (2)
-**** TODO profile and validate results (1)
-
-*** coherent NURBS evaluation (1)
-**** TODO review 2006 paper (0)
-**** TODO convert openNURBS surface evaluation to OpenCL (1)
-
-*** performant raytrace image display (2)
-**** TODO optimize libdb/libfb to remove bottleneck (1)
-**** TODO update archer for interactive tracing display (1)
-
-
-** PROJECT: Raytrace Prep Caching (10)
-
-*** implement LIBBU data caching (3)
-**** TODO document libbu data caching API (1)
-**** TODO create data caching test cases (1)
-**** TODO implement libbu data caching (1)
-
-*** implment LIBRT object caching (4)
-**** TODO serialize BoT prep data to cache (1)
-**** TODO serialize NURBS prep data to cache (1)
-**** TODO serialize tess/plot data to cache (2)
-
-*** update tools to utilize the cache (3)
-**** TODO update rt* to use prep cache (1)
-**** TODO update mged/archer to use tess/plot cache (1)
+*** raytrace prep caching
+**** TODO implement libbu data caching API (3)
+**** TODO implement librt object prep caching (5)
+**** TODO update tools to utilize the prep cache (1+2)
 **** TODO document the prep cache interface (1)

+*** on-demand NURBS tree-building
+**** TODO dynamic tree build with minimal malloc
+**** TODO profile and validate results
+**** TODO formulate a design / approach

-** PROJECT: Progressive Geometry Display (11)
+*** coherent Boolean evaluation
+**** TODO OpenCL conversion
+**** TODO handle bundles of ray, eliminate branching
+**** TODO review and integrate Costa's GSoC work
+**** TODO V&V with specific test cases

-*** asynchronous geometry display (4)
-**** TODO modify display loop to run in separate thread (2)
-**** TODO update draw command to dispatch (2)
+*** coherent NURBS evaluation
+**** TODO review 2006 paper
+**** TODO convert openNURBS surface evaluation to OpenCL

-*** ray trace display manager (4)
-**** TODO review rtgl code (1)
-**** TODO design incremental loading architecture (1)
-**** TODO implement incremental ray tracing (2)
+*** performant raytrace image display
+**** TODO optimize libdb/libfb to remove bottleneck
+**** TODO update archer for interactive tracing display

-*** point cloud hashing (3)
-**** TODO design LoD point cloud storage approach (1)
-**** TODO calculate LoD point cloud utility metric (1)
-**** TODO implement LoD point cloud loading (3)
+
+** PROJECT: Merge Archer/MGED
+
+*** do more good stuff


 ** TEMPLATE: Project Title
@@ -283,41 +254,6 @@ bolster those areas, and identifies specific actionable objectives.
     0 for tasks less than 2 days.


-* Strategic Strengths
-** project
-*** open source
-*** cross-platform
-*** free software
-*** 30-years of development
-*** massive investment
-*** extensive API
-*** extensive documentation
-** code
-*** extensively modular
-*** scalability
-*** embeddable
-*** efficient workflow
-*** flexible workflow
-*** DoD-accreddited
-*** integrated into MUVES, AJEM, COVART
-** modeling
-*** hybrid representation system
-*** wide variety of supported entities
-*** csg, nurbs, triangles, volumes, point clouds
-*** scriptable geometry
-*** procedural geometry
-*** geometry conversion
-*** geometry editing
-** analysis
-*** geometry v&v
-*** geometry preparation
-*** joint articulation system
-*** physics simulation system
-*** ray tracing performance
-*** analytic ray tracing
-*** solid ray tracing
-*** geometry visualization
-
 # Local Variables:
 # mode: org
 # End:
@@ -0,0 +1,30 @@
+tbl()	{
+	case $# in
+	0) rsh vmb.brl.mil 'PATH=/usr/5bin:$PATH export PATH; tbl';;
+	*) cat $1 | rsh vmb.brl.mil 'PATH=/usr/5bin:$PATH export PATH; tbl';;
+	esac;
+	}
+typeset()
+	{
+	case $# in
+	0)
+	rsh vmb.brl.mil 'PATH=/usr/5bin:$PATH export PATH; troff -mm -Ti300 | dimp -t | ipr -J -Pim124';;
+	*) cat $1 |
+	rsh vmb.brl.mil 'PATH=/usr/5bin:$PATH export PATH; troff -mm -Ti300 | dimp -t | ipr -J -Pim124';;
+	esac;
+	}
+laser()
+	{
+	OPTS=
+	case $# in
+	0)	;;
+	*)	case $1 in
+		-h)	OPTS=$1; shift;;
+		esac
+		case $# in
+		1)	FILE=$1;;
+		esac;;
+	esac
+	pix-bw -ntsc ${FILE} | bw-imp ${OPTS} | rsh vmb.brl.mil 'PATH=/usr/5bin:$PATH export PATH; ipr -J -Pim124'
+	unset OPTS FILE;
+	}
@@ -0,0 +1,11 @@
+#!/bin/sh
+
+#OPTS='-V'
+OPTS='-b'
+
+groff $OPTS -mm -Tps burst.mm   > burst.ps
+ps2pdf burst.ps
+
+#groff $OPTS -mm
+
+#groff -mm -Thtml burst.mm > burst.html
@@ -0,0 +1,22 @@
+#!/bin/sh
+
+tables="\
+bpl \
+cmap \
+commands \
+fb \
+hmkeys \
+ids \
+overlap \
+plot \
+screen \
+scrollmenu \
+shotlines \
+submenu \
+topmenu\
+"
+
+for table in $tables ; do
+  tbl $table.tbl > $table.mm
+done
+
@@ -0,0 +1,27 @@
+# these macros (mm files) are generated by tclsh script "Make-tables.sh"
+TABLE_MM := bpl.mm
+TABLE_MM += cmap.mm
+TABLE_MM += commands.mm
+TABLE_MM += fb.mm
+TABLE_MM += hmkeys.mm
+TABLE_MM += ids.mm
+TABLE_MM += overlap.mm
+TABLE_MM += plot.mm
+TABLE_MM += screen.mm
+TABLE_MM += scrollmenu.mm
+TABLE_MM += shotlines.mm
+TABLE_MM += submenu.mm
+TABLE_MM += topmenu.mm
+
+PRODS := burst.ps burst.pdf burst.html
+
+docs:
+	@echo "Making burst tables for groff..."
+	./Make-tables.sh
+	@echo "Making burst docs..."
+	./Make-docs.sh
+
+clean: distclean
+
+distclean:
+	-rm $(TABLE_MM) $(PRODS) *~ t tt
@@ -0,0 +1,64 @@
+Documentation for the BRL-CAD program 'burst'.
+
+Debian requires packages groff and groff-base.
+
+The original source file ('burst.mm') has been modified slightly to
+ensure correct handling by Eric Raymond's doclifter
+(http://www.catb.org/~esr/doclifter/).  From an e-mail from Eric:
+
+from:	   Eric S. Raymond <esr@thyrsus.com>
+reply-to:  esr@thyrsus.com
+to:	   Tom Browder <tom.browder@gmail.com>
+date:	   Tue, Aug 20, 2013 at 8:48 AM
+subject:   Re: doclifter (master) failing on troff mm source
+mailed-by: thyrsus.com
+
+<quote>
+Tom Browder <tom.browder@gmail.com>:
+> I have checked all macros and they are valid mm macros so I  can't
+> figure out why doclifter is failing.  I can send you the whole source
+> zipped if you're interested.
+
+What you sent is sufficient.  The problem is that your mm file
+contains none of the three trigger macros doclifter is looking for as
+a way to recognize that it's dealing with mm - .MT, .SA, or .COVER.
+The relevant table looks like this:
+
+# This is how we autodetect the right macro set:
+
+interpreter_dispatch = {
+    "pp": MeInterpreter,
+    "Dt": MdocInterpreter,
+    "Dd": MdocInterpreter,
+    "Nm": MdocInterpreter,
+    "AU": MsInterpreter,
+    "NH": MsInterpreter,
+    "TH": ManInterpreter,
+    "MT": MmInterpreter,
+    "SA": MmInterpreter,
+    "COVER": MmInterpreter,
+    # Extension macro sets
+    "supplemental macros used in Tcl/Tk": TkManInterpreter,
+    "BS": TkManInterpreter,
+    "the F register is turned on": Pod2ManInterpreter,
+    "ZN": XManInterpreter,
+    "Pn": XManInterpreter,
+    "ny0": XManInterpreter,
+    "reStructuredText": reStructuredTextInterpreter,
+    "reStructeredText": reStructuredTextInterpreter,
+    "DocBook XSL Stylesheets" : DocBookInterpreter,
+    "pdfdest" : FoojzsInterpreter,
+    "H0": ASTInterpreter,
+    # These are all of the supported Mwww tags
+    "URL": MwwwInterpreter,
+    "FTP": MwwwInterpreter,
+    "MTO": MwwwInterpreter,
+    "PIMG": MwwwInterpreter,
+    "IMG": MwwwInterpreter,
+    "TAG": MwwwInterpreter,
+    }
+
+Inserting a dummy .MT 0 call should fix your problem.
+</quote>
+
+
@@ -0,0 +1,15 @@
+.TL
+``burst''; Air Force Vulnerability Analyses from BRL-CAD Models
+.AF "U. S. A. Ballistic Research Laboratory"
+.ds ZZ Aberdeen Proving Ground
+.AU "Gary S.\& Moss" GSM ZZ
+.AS
+.so introduction.mm
+'\"The presentation will not dwell on the details of usage as much as the paper
+'\"but will focus on the available features of the \*(b) program
+'\"as well as its flexibility in supporting analyses of varied threat
+'\"mechanisms on \*(m) targets.
+.AE
+.MT 4
+.rm ZZ
+.SA 1
@@ -0,0 +1,37 @@
+.TS
+allbox,center,tab(@);
+lb lb lb
+_ _ _
+l l l.
+record description@field format@field description
+run header@'1'@record number 1
+@1x,f9.4@attack azimuth (degrees)
+@1x,f8.4@attack elevation (degrees)
+@1x,f5.2@burst distance
+@1x,f10.2@projected area associated with burst point
+@1x,6a@units (mm,cm,inches,feet,meters)
+@1x,f9.6@ray solid angle (steradians)
+shotline header@'2'@record number 2
+@1x,f8.3@Y' coordinate of shotline
+@1x,f8.3@Z' coordinate of shotline
+shotline intersections@'3'@record number 3
+@1x,f8.2@X' coordinate of component intersection
+@1x,f8.2@line-of-sight thickness of component
+@1x,i4@component code number
+@1x,i2@space code
+@1x,f7.3@sine of fallback angle of exit normal
+@1x,f7.2@rotation angle of exit normal (degrees)
+@1x,f7.3@cosine of obliquity angle at entry
+@1x,a1@burst flag ('1' for yes, '0' for no)
+burst ray header@'4'@record number 4
+@1x,f8.3@azimuth angle WRT shotline (radians)
+@1x,f8.3@sine of elevation angle WRT shotline
+@1x,i6@sequential ray number for this burst point
+burst ray intersections@'5'@record number 5
+@1x,f10.3@distance to first contact with component
+@1x,f9.3@line-of-sight thickness of component
+@1x,f9.3@normal thickness of component
+@1x,i4@space code
+@1x,i4@component code number
+@1x,f6.3@cosine of obliquity angle at entry
+.TE
@@ -0,0 +1,995 @@
+.\" ASI Note: PP was changed to P in this file; CS was commented out
+.\" Note the following line was added per Eric Raymond's advice for
+.\"  use by doclifter:
+.MT 0
+.PH ""
+.PF "''\\\\nP''"
+.so defs.mm
+.so abstract.mm
+.so macros.mm
+.H 1 "User Interface"
+.H 2 "Program Invocation"
+In the examples below,
+the `$' symbol represents the \*(U)
+shell prompt.
+The general usage for the \*(b) program is as follows:
+.Ex "burst [-b]\fR"
+.P
+When \*(b) is used in the default mode,
+a full-screen, interactive, menu-driven interface is provided:
+.Ex burst
+In the interactive mode,
+commands are formatted by the menu system (see \fBHierarchical Menus\fR).
+The optional
+.I -b\^
+argument will suppress the full-screen terminal display in favor of a
+batch-oriented interface;
+when coupled with \*(U) file redirection and background processing,
+the user can submit the job and go on to other tasks.
+.Ex "burst \|\-b \|< \|input_file \|&"
+The user will typically want to redirect any diagnostics to a log file
+(see \fBError Log\fR).
+In either batch or interactive mode,
+the program will read commands (see \fBCommand Input\fR) from the standard
+input until an end of file is encountered.
+In batch mode,
+the program will exit after the last command is processed,
+but when run interactively the menu system will take over after the last
+command.
+The user must \fIquit\fR the program by exiting the top-level menu
+(see Table 2).
+It is recommended that the reader begin by running the \*(b)
+program interactively.
+The hierarchical menu system generates key word commands for the user by
+prompting him to make choices or enter values without prior knowledge of
+the commands and their syntax.
+As commands are generated,
+they are printed in the scrolling region so that the user can learn
+the syntax of the alternative mode of input without affecting his productivity.
+The more advanced user can circumvent the menu system by using a
+text editor to prepare input files.
+.sp
+.H 2 "Command Input"
+All commands to \*(b) are composed of one or more words connected by hyphens
+and each command may require one or more arguments that must be separated by
+either spaces or tabs.
+A line that begins with the `#' symbol is considered a comment and will be
+ignored.
+Each command must be on a separate line and may be supplied to the \*(b)
+program's standard input (i.e. using \*(U)
+.Ud sh 1
+file redirection) or can be generated from the hierarchical menus.
+In Table 1 below is a brief description of these commands; \fIflag\fR
+arguments have \fIyes\fR or \fIno\fR values, an \fIangle\fR is expressed in
+degrees as a floating-point quantity,
+\fIdistances\fR and coordinates such as \fIX, Y, Z, left, right\fR, etc.
+are also floating-point numbers,
+and \fIcount\fR represents an integer.
+Square brackets delimit optional arguments.
+For a detailed description of each command,
+refer to sections 2 through 7.
+.DF
+.sp
+.TB "Key Word Commands"
+.so commands.mm
+.sp
+.DE
+.H 2 "Screen Layout"
+In interactive mode,
+the screen is divided into sections of one or more rows (lines) of text.
+.DF
+.so screen.mm
+.FG "Screen Layout"
+.sp
+.DE
+The top line,
+referred to as line 1,
+is reserved for
+CPU
+usage statistics.
+Starting on line 2,
+the hierarchical menu region spans 12 lines of the screen.
+Below the menu region is a line used for user input related errors and
+help messages that are generated by typing an `h' (see Table 2).
+Below that is a line used to prompt the user for input and to inform him
+of ongoing processing.
+The next line contains the program name and version number,
+and is intended as a divider between the scrolling window below it and the
+non-scrolling portion of the screen.
+Once ray tracing has begun,
+grid index ranges will appear inside square brackets to the right of the
+version number.
+The first number is the current horizontal index,
+and this is separated by a colon from the right-most index for the grid.
+After the comma,
+is the current vertical index,
+followed by the top-most index for the grid.
+As ray tracing commences,
+the current grid indices will reflect the current shotline being calculated
+as the grid is traversed in a left-to-right,
+bottom-to-top fashion.
+The scrolling window region takes up the remainder of the screen for the
+display of processed commands and processing-related errors (i.e. from the
+ray tracer).
+Figure 1 shows what the various sections of the screen are used for,
+however in practice,
+the status information,
+help message,
+and prompt would not be displayed concurrently.
+The screen-oriented interface is terminal independent;
+it doesn't use graphics per se
+but uses the terminal capabilities information database to control the
+manipulation of text characters.
+.sp
+.H 2 "Hierarchical Menus"
+Table 2 shows the key strokes used to manipulate the menus.
+.DF
+.sp
+.TB "Hierarchical Menu Commands"
+.so hmkeys.mm
+.sp
+.DE
+The top-level menu looks like Figure 2.
+.DF
+.so topmenu.mm
+.FG "Top-Level Hierarchical Menu"
+.sp
+.DE
+Note that the \fIcurrent\fR entry will be highlighted.
+The `v' symbols at the bottom corners of the menu show that
+there are more entries below.
+Attempting to move the cursor past the bottom entry will cause the
+menu to scroll upwards as illustrated in Figure 3.
+.DF
+.so scrollmenu.mm
+.FG "Scrolled Menu"
+.sp
+.DE
+Note the `^' symbols at the top corners of the menu.
+These signify that there are now hidden entries above that can be
+scrolled down by advancing the cursor upwards past the top visible
+entry.
+If no scrolling is possible,
+that is,
+if no further entries exist,
+a `+' symbol will mark the corner of the menu.
+If a menu item is selected that has a sub-menu,
+the sub-menu will be drawn to the right of its parent menu as shown
+in Figure 4.
+.DF
+.so submenu.mm
+.FG "Sub-Menu Display"
+.sp
+.DE
+The menu system \fIremembers\fR the last item selected in a given
+menu;
+entering a menu that has been used before will cause
+the \fIcurrent\fR item to be the same as it was when that menu was last exited.
+If a menu has never been used,
+the top item will initially be \fIcurrent\fR.
+.H 2 "Scrolling Region"
+When running the \*(b) program interactively,
+all diagnostic output is, by default, printed in a scrolling text window
+at the bottom of the display.
+If the batch option (\fI\-b\fR) is used,
+these diagnostics will be printed on the standard error output of the
+program.
+If there is enough output the user may find it difficult
+to read it all before it scrolls out of sight.
+Also, the user may wish to save these diagnostics for later reference;
+overlap diagnostics from the ray tracer are useful in fixing errors in
+the geometry of the target description.
+The \*(b) program has a command called
+.Co error-file
+that will divert this output to a file (see \fBError Log\fR).
+Figure 5 shows three such overlap diagnostics.
+.DS
+.sp
+.so overlap.mm
+.FG "Overlap Diagnostics"
+.sp
+.DE
+The full path name of both regions is printed, the zero enclosed in double
+curly brackets is intended to discriminate between \fIinstances\fR\*F.
+.FS
+An \fIinstance\fR is a type of group in the \*(m) data base that has
+a \fIprototype\fR object as a member.
+Several \fIinstances\fR may reference the same \fIprototype\fR
+yet have different transformation matrices.
+Although these objects represent distinct geometric entities,
+they share the same path name,
+therefore the additional discriminant is necessary.
+.FE
+Theoretically,
+\fIisol\fR and \fIosol\fR are the names of the starting and ending solids
+associated with the boolean operations on the overlapping partition.
+In practice,
+these solid names are typically not helpful in diagnosing the problem,
+but the region names should be sufficient.
+The \fIdepth\fR is the line-of-sight thickness of the overlapping partition
+in millimeters.
+In parentheses,
+are printed the target coordinates of the intersection of the ray
+with the overlap.
+The \fIx-2\fR and \fIy1\fR reveal that the grid indices of the shotline are
+\fI-2, 1\fR; this means that the shotline was 2 cells to the left,
+and one cell above the grid origin.
+If \fIlvl\fR (meaning ray tracing recursion level) is \fIzero\fR,
+then the overlap resulted from a shotline,
+but if it is \fIone\fR,
+it could represent either a burst ray intersection or a probe to
+calculate the normal thickness of a component intersected by the shotline.
+The real purpose of the ray is stated last.
+.H 1 "Executing a Run"
+.Cs "/execute"
+The \*(b) program is designed to allow many options to be configured before
+any outputs are calculated.
+Unless otherwise stated in the individual command descriptions in this report,
+a given command will nullify any previous occurrence of the same directive
+until an
+.Co execute
+command is given.
+For instance, the command
+.Co "target-file"
+\ \fItank1\fR followed by
+.Co "target-file"
+\ \fItank2\fR will nullify the reference to \fItank1\fR.
+Once the input parameters are specified,
+the
+.Co execute
+command will start a \fIrun\fR.
+Many \fIruns\fR may occur during an instance of the \*(b) program.
+One such instance is referred to as a \fIsession\fR.
+Below are descriptions of commands for configuring the behavior of the
+\*(b) program.
+.Ce
+.H 1 "User Preferences"
+.H 2 "Units of Measure"
+.Cs /units
+The
+.Co units
+command will set the linear units for input and output.
+This command should be used before any scalar quantities such as coordinates,
+distances,
+or sizes are input.
+The units may be changed to accommodate input files of differing units,
+but the output from a particular run will reflect whatever the units were
+set to when the
+.Co execute
+command was given.
+One argument is expected out of the following list and must be spelled
+correctly:
+\fImillimeters\fR,
+\fIcentimeters\fR,
+\fImeters\fR,
+\fIinches\fR and \fIfeet\fR.
+The default units are \fImillimeters\fR.
+Angles are always expressed in degrees, not radians.
+.Ce
+.H 2 "Region Overlap Reporting"
+.Cs "/preferences/report-overlaps"
+It is considered an error if two \fIregions\fR in an \*(m) file occupy
+the same space; we call this an \fIoverlap\fR.
+The ray tracing library (\*(l)) will report \fIoverlapping regions\fR that are
+intersected by shotlines or burst rays to the \*(b) application and
+the program will,
+by default,
+print out any that have a line of sight thickness of at least 0.25 millimeters
+(see \fBError Log\fR).
+Although a target may only have several \fIoverlaps\fR,
+an error will be reported for each ray that intersects one of them,
+so the messages will typically be repetitious.
+Although these diagnostics are important for fixing problems in the geometric
+description of the target,
+the user may wish to proceed with a production run and the printing of these
+errors can slow the execution time considerably.
+A \fIyes\fR or \fIno\fR argument to this command will turn the diagnostics
+on or off.
+Regardless of whether or not individual \fIoverlaps\fR are reported,
+the total number detected will be logged.
+.Ce
+.H 1 "Shotlining Options"
+.Cs /shotlines
+\fIShotlining\fR is a technique whereby lines are described in the target
+coordinate system and information is requested about the geometry that
+intersects those lines in 3-space.
+This technique is useful for analysis programs that must simulate
+threat/target interactions,
+and therefore must sample the geometry along the threat path.
+Typically the lines are specified discretely,
+by a point and a direction,
+or a \fIgrid\fR of lines is generated that is
+oriented perpendicular to the direction of attack.
+A \fIgrid\fR is rectangular,
+but is subdivided along its height and width uniformly resulting in square
+cells.
+\fIGridding\fR techniques include passing a line called a \fIshotline\fR through
+the center of each cell,
+or alternatively,
+\fIdithering\fR each shotline's position within its respective cell's
+boundaries (see \fBDithering Shotlines\fR).
+.Ce
+.H 2 "Attack Direction"
+.Cs "/shotlines/attack-direction"
+The orientation of shotlines with respect to the coordinate system of the
+target are described by \fIazimuth\fR and \fIelevation\fR angles.
+These angles must be specified in degrees as floating-point numbers
+(see \fBGridding\fR).
+.Ce
+.H 2 "Gridding"
+.Cs "/shotlines/shotline location"
+The user is faced with several choices for generating shotlines;
+full-target envelope, partial envelopes, or discrete shots.
+No matter what shotlining method is used,
+a grid always exists as a frame of reference for specifying 2-dimensional
+coordinates in the plane normal to the direction of attack.
+This 2-dimensional coordinate system is a projection of the shotline
+coordinate system (also referred to as the \fIprimed\fR coordinate system).
+For the simple case of a zero azimuth, zero elevation attack,
+the
+.Ax \*(x) \*(y) \*(z)
+in the shotline coordinate system coincide
+with the
+.Ax \*(X) \*(Y) \*(Z)
+of the target coordinate system and the shotline direction is parallel to
+the \*(x)\*(A) and headed toward decreasing coordinates.
+Other orientations are described by rotating the
+.Ax \*(x) \*(y) \*(z)
+to keep the shotline direction always down the \*(x)\*(A).
+This transformation involves two rotations;
+first a rotation of the \fIprimed\fR coordinate system about the coincident
+\*(Z) and \*(z)\*(a) by the specified azimuthal angle,
+followed by a rotation about the new \*(y)\*(A) by the specified elevation
+angle.
+Since the grid is a 2-d projection of the shotline coordinate system,
+it has no \*(X) coordinate;
+if the user's viewpoint is from the direction of attack,
+the \*(y)\*(A) can be thought of as horizontal with increasing coordinates
+to the right,
+and the \*(z)\*(A) as vertical and increasing in the upward direction.
+.Ce
+.Cs "/shotlines/shotline location/envelope"
+An \fIenvelope\fR refers to a grid that is dimensioned such that its
+rectangular area,
+projected normal to the grid,
+will cover optionally all or part of the target.
+.Ce
+.Cs "/shotlines/shotline location/envelope/enclose-target"
+This option will generate a grid that is guaranteed to cover the entire
+target.
+Since the \*(m) modeler uses combinatorial solid geometry,
+the dimensions of the target are not known,
+therefore a worst case bounding rectangular parallel piped (RPP)
+is the only information available to the program and
+the grid may be larger than necessary.
+In addition,
+depending on the attack aspect,
+the presented area of some targets may not fill up a rectangular grid well.
+This should not be a problem since ray tracing outside the target
+boundaries is cheap, but if desired,
+the grid can be trimmed down with the partial envelope option described
+below.
+The grid origin is always aligned with the target origin.
+.Ce
+.Cs "/shotlines/shotline location/envelope/enclose-portion"
+This option allows the user to generate a \fIsub-grid\fR by specifying the
+distances from the grid origin to the \fIsub-grid's\fR left, right, top,
+and bottom boundaries.
+.Ce
+.H 2 "Cell Size"
+.Cs "/shotlines/cell-size"
+The dimensions of a grid cell are input as floating-point values that
+represent the distances between the centers of adjacent cells.
+\fICell size\fR also expresses the projected area of influence
+associated with a shotline or burst ray.
+Therefore,
+\fIcell size\fR must be specified even when a grid will not be generated,
+such as with discrete shot or discrete burst point selection
+(see \fBInput Discrete Shots\fR and \fBInput Discrete Burst Points\fR).
+.Ce
+.H 2 "Dithering Shotlines"
+.Cs "/shotlines/dither-cells"
+When gridding,
+shotlines normally pass through the center of each cell,
+however,
+they may be also be \fIdithered\fR.
+If the user chooses the latter,
+2 random numbers are selected for each
+cell that are used to offset the shotline in both parametric
+directions of the grid plane,
+but within the respective cell's boundaries.
+.Ce
+.H 2 "Input Discrete Shots"
+.Cs "/shotlines/shotline location/discrete shots"
+The following options describe different ways to input explicit shot locations
+as an alternative to generating a grid.
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/target coordinate system"
+If the user wants to fire at a known point on the target,
+he may wish to describe the shotline location in target coordinates.
+When coupled with the attack direction,
+each 3-dimensional coordinate uniquely specifies a shotline.
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/target coordinate system/input-3d-shot"
+This option allows the user to type in a single shot location as an
+\*(X), \*(Y), and \*(Z) coordinate.
+When the
+.Co execute
+command is given,
+that one shot will be run.
+No queueing of shots occurs in this mode;
+the last set of coordinates entered will be used.
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/target coordinate system/read-3d-shot-file"
+A number of shots can be input from a file;
+this option will,
+after submission of an
+.Co execute
+directive,
+loop through every set of target coordinates in the named file.
+The file should contain three floating-point numbers on each line separated by
+white space (blanks or tabs).
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/shotline coordinate system"
+Another way to describe a shot location is in the shotline coordinate
+system.
+Since the \*(x) location of the shot is irrelevant (the shotline is
+parallel to the \*(x)\*(A)) a shot may be specified as a
+\*(y) and \*(z) coordinate.
+These coordinates can also be referred to as horizontal and vertical grid
+offsets.
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/shotline coordinate system/input-2d-shot"
+This option allows the user to type in a single shot location as a
+\*(y), and \*(z) coordinate.
+When the
+.Co execute
+command is given,
+that one shot will be run.
+No queueing of shots occurs in this mode,
+the last set of grid offsets entered will be used.
+.Ce
+.Cs "/shotlines/shotline location/discrete shots/shotline coordinate system/read-2d-shot-file"
+A number of shots can be input from a file;
+this option will,
+after submission of an
+.Co execute
+directive,
+loop through every set of grid offsets in the named file.
+The file should contain three floating-point numbers on each line separated by
+white space (blanks or tabs).
+.Ce
+.H 1 "Bursting Options"
+.Cs "/burst points"
+\fIBursting\fR is a technique for sampling a target's geometry with the use
+of ray tracing.
+As opposed to \fIshotlining\fR involving parallel rays,
+\fIbursting\fR employs a distribution of rays that emanate from a single
+point.
+The \*(b) program generates rays that approximate a uniform distribution
+over a user-specified solid angle (see \fBSampling Cone Half Angle\fR)
+and having a density (see \fBNumber of Sampling Rays\fR) that is also under
+control of the user.
+The user also has a choice between several mechanisms for setting up
+burst point locations depending on the particular threat he is attempting
+to emulate.
+.Ce
+.H 2 "Method of Locating Burst Point"
+.Cs "/burst points/bursting method"
+Depending on threat type,
+burst points may be located using two basic techniques.
+The first technique is simply to input the burst point coordinates.
+This method can be used to compare vulnerability analysis results with
+empirical results from the firing range or combat field.
+The second technique available to the user is to burst along a shotline.
+This option is used more for predicting the burst point location based
+on target geometry,
+given certain parameters that describe the target/threat interactions.
+.Ce
+.H 3 "Input Discrete Burst Points"
+.Cs "/burst points/bursting method/burst point coordinates"
+The input of explicit burst point coordinates can be accomplished
+either by typing them in one at a time or by reading a file
+of target \*(X), \*(Y), and \*(Z) coordinates.
+.Ce
+.Cs "/burst points/bursting method/burst point coordinates/burst-coordinates"
+This option allows the user to type in a single burst point location as an
+\*(X), \*(Y), and \*(Z) coordinate.
+When the
+.Co execute
+command is given,
+that one burst point will be run.
+No queueing of burst points occurs in this mode,
+the last set of coordinates entered will be used.
+.Ce
+.Cs "/burst points/bursting method/burst point coordinates/read-burst-file"
+A number of burst points can be input from a file;
+this option will,
+after submission of an
+.Co execute
+directive,
+loop through every set of target coordinates in the named file.
+The file should contain three numbers on each line separated by
+white space (blanks or tabs).
+.Ce
+.H 3 "Burst on Contact"
+.Cs "/burst points/bursting method/burst point coordinates/shotline-burst"
+The
+.Co shotline-burst
+directive can be given a \fIyes\fR or \fIno\fR argument to either enable
+or disable this method of generating burst points.
+When a \fIyes\fR argument is given,
+a second \fIyes\fR or \fIno\fR argument is also required
+(see \fBBurst on Armor\fR).
+Bursting along a shotline can be done different ways depending on the
+combination of several options.
+The location of the burst point is based on the triggering
+mechanism that is selected with the \fIburst distance\fR parameter.
+.Ce
+.H 4 "Burst on Armor"
+.sp
+If the \fIburst distance\fR parameter is set to a negative or zero value,
+then interior burst points will be generated (see \fBBurst Distance\fR).
+This method of bursting requires the input of \fIburst armor\fR idents and,
+by default, \fIburst air\fR idents are also required.
+If the user does not want to require that certain air be present to trigger
+a burst point,
+the
+.Co shotline-burst
+command has a second argument.
+When this second argument is set to \fIno\fR,
+bursting will occur as long as
+\fIburst armor\fR is followed by any air or void (empty space),
+and the \fIburst air\fR file is not required.
+For more information see \fBBurst Armor File\fR and \fBBurst Air File\fR.
+.Ce
+.H 4 "Ground Plane Bursting"
+.Cs "/burst points/bursting method/burst point coordinates/ground-plane"
+Ground plane bursting is a vehicle for evaluating the effect of
+fragmenting warheads on light-armored vehicles when they strike the ground
+in close proximity to the target.
+The
+.Co ground-plane
+command is only relevant when bursting along a shotline is selected.
+The ground is modeled as a rectangle lying in a plane parallel
+to the target \fIX-Y\fR plane with edges parallel to the \*(X) and \*(Y)
+axes.
+The grid will be enlarged to include the ground plane;
+it is important for efficiency to limit the size of the ground plane to
+match the range of the fragments that may be generated by the particular
+threat being modeled.
+When enabling this option,
+the
+.Co ground-plane
+command is given a \fIyes\fR argument
+followed by the height of the target above the ground,
+and the distances that the ground rectangle extends out positive \*(X),
+negative \*(X),
+positive \*(Y),
+and negative \*(Y) axes.
+.Ce
+.H 2 "Bursting Parameters"
+.Cs "/burst points/bursting parameters"
+The following parameters influence both the triggering mechanism for burst
+points,
+as well as the characteristics of the cone of rays generated from each
+point.
+.Ce
+.H 3 "Burst Distance"
+.Cs "/burst points/bursting parameters/burst-distance"
+The \fIburst distance\fR parameter is modeled after the \fBBDIST\fR parameter
+used by the Air Force's \*(G)\*F code.
+.FS
+The Air Force currently uses \*(G) to produce burst point libraries
+for \*(P) from \*(F) descriptions.
+.FE
+The role of this parameter is overloaded,
+however it was retained to aid \*(G) users in transitioning to the \*(b)
+program.
+If it is zero or negative,
+then \fIinterior bursting\fR is enabled,
+otherwise,
+if it is greater than zero, \fIexterior bursting\fR will occur,
+subject to certain conditions (see below).
+The magnitude of this parameter is used to offset the burst point location
+along the shotline relative to the geometry that triggered the burst.
+.Ce
+.H 4 "Interior Bursting"
+.sp
+\fIBurst armor\fR refers to a component whose ident code is found in
+the list input by the
+.Co burst-armor-file
+command.
+Similarly,
+\fIburst air\fR refers to a component whose ident code is found in the
+list input by the
+.Co burst-air-file
+directive.
+If \fIinterior bursting\fR is enabled
+and a \fIburst armor\fR component is encountered along a shotline
+that is immediately followed by \fIburst air\fR,
+then a burst point will be located the absolute value of \fIburst distance\fR
+beyond the exit of the shotline from the component.
+This means that if \fIburst distance\fR is zero,
+the burst point will lie at the \fIburst armor/air\fR interface,
+and if it's -5.5,
+the burst point will lie 5.5 units inside the air compartment from the
+back surface of the armor.
+.Ce
+.H 4 "Exterior Bursting"
+.sp
+If \fIburst distance\fR is greater than zero,
+the first component encountered along the shotline will trigger a
+burst point,
+regardless of its ident code,
+that will be located \fIburst distance\fR
+in front of the shotline \fIentry\fR point.
+This technique simulates the behavior of a fragmenting munition with
+a \fIstandoff\fR fuzing such that detonation is triggered before
+the collision of the warhead with the target.
+The \fIburst distance\fR is set to imitate the built in \fIstandoff\fR
+of the warhead.
+When employing \fIexterior bursting\fR methods,
+\fIburst armor\fR and \fIburst air\fR are not used.
+.sp
+.H 3 "Sampling Cone Half Angle"
+.Cs "/burst points/bursting parameters/cone-half-angle"
+To limit the solid angle within which burst rays will be generated,
+the user may specify a \fIcone half angle\fR.
+This angle represents the degrees (in floating point) from the \fIaxis\fR of
+the cone to its limiting surface.
+The default value for the \fIcone half angle\fR is 45 degrees.
+.Ce
+.H 3 "Deflected Sampling Cone"
+.Cs "/burst points/bursting parameters/deflect-spall-cone"
+The spall cone axis is,
+by default,
+aligned with the shotline.
+In reality,
+the center of mass of the spall cloud would be between the shotline direction
+and the exit normal of the shotline from the spalling component.
+By aligning the spall cone axis with a vector halfway between the shotline
+and the exit normal,
+a narrower cone half angle can be used and still sample within the solid
+angle of interest.
+This technique can therefore be used to cut down on the number of rays
+calculated without lowering the sampling density.
+The
+.Co deflect-spall-cone
+command takes a \fIyes\fR or \fIno\fR argument about whether or not
+to divert the cone axis.
+.Ce
+.H 3 "Number of Sampling Rays"
+.Cs "/burst points/bursting parameters/max-spall-rays"
+The sampling ray density within the spall cone is controlled by specifying
+the maximum number of rays desired.
+Due to the uniform distribution algorithm employed,
+the number of rays calculated will be slightly less.
+.Ce
+.H 3 "Maximum Barriers"
+.Cs "/burst points/bursting parameters/max-barriers"
+For munitions known to have limited penetration capability,
+the user may set a limit on the number of burst ray intersections reported.
+The effect of setting this parameter is to reduce the size of the
+burst point library (see \fBBurst Point Library\fR) by limiting the
+number of components that will be reported per burst ray.
+By default,
+up to 100 components are reported,
+as it is not expected that this number will be reached under normal
+circumstances.
+.Ce
+.H 1 "Input File Options"
+.H 2 "Target-Related Input Files"
+.Cs "/target files"
+This group of commands is for specification of target-specific input files.
+.Ce
+.H 3 "Target Data Base File"
+.Cs "/target files/target-file"
+The input of the target's \*(m) file is accomplished with this command.
+Note that only one data base may be read in during a given \fIsession\fR.
+If the user wishes to change the target once the
+.Co execute
+command has been given,
+he must exit the \*(b) program and start a new \fIsession\fR.
+.Ce
+.Cs "/target files/target-objects"
+After specifying the \*(m) file,
+the user must list all of the objects in the \*(m) hierarchy that he
+wishes to be included in his analysis.
+The objects must be listed as arguments to one
+.Co target-objects
+command with spaces or tabs as separators.
+Note that only one list of objects may be loaded per \fIsession\fR,
+however,
+they do not get loaded until the
+.Co execute
+command is given.
+.Ce
+.H 3 "Ident List Input Files"
+.sp
+\fIIdents\fR refer to the \fIregion ident\fR code from the \*(m) file.
+Lists of \fIidents\fR may be specified singly or as ranges.
+Individual \fIidents\fR must appear as one per line,
+but ranges are specified by two numbers on a line that are
+separated by one or more of the following characters: comma, hyphen, colon,
+semicolon, space, or tab.
+Figure 6 shows an example of such a file.
+.DS
+.sp
+.so ids.mm
+.FG "Ident List File Format"
+.sp
+.DE
+.Ce
+.H 4 "Burst-Armor and Burst-Air Ident Files"
+.sp
+.Cs "/target files/burst-armor-file"
+.Cs "/target files/burst-air-file"
+When interior burst points are to be generated along a shotline
+(see \fBInterior Bursting\fR) a file of \fIburst armor\fR idents and
+\fIburst air\fR idents must be input.
+If a shotline intersects a component whose \fIident\fR has been input
+as a \fIburst armor\fR and it is immediately followed by \fIburst air\fR
+a burst point will be triggered.
+.Ce
+.H 4 "Critical Component Idents"
+.Cs "/target files/critical-comp-file"
+Whether interior or exterior bursting is being employed,
+information about components hit by burst rays will only be output
+for rays that hit \fIcritical components\fR.
+The file name containing a list of \fIcritical component\fR idents must
+therefore be input by this command if burst points are to be generated.
+.Ce
+.H 3 "Color Mapping Input File"
+.Cs "/target files/color-file"
+This command allows users to assign colors to component idents for graphics
+options,
+in particular,
+the
+.Co image-file
+and
+.Co plot-file
+commands.
+The format of this file is 5 numbers per line separated by blanks or tabs.
+The first number is the low end of an ident range and the second number is
+the high end of the range (both numbers are inclusive).
+This range is mapped to the color specified by the last 3 numbers on the
+line that are red, green, and blue components of the color (values for
+these components must be between 0 and 255 inclusive).
+Figure 7 shows an example of such a file.
+.DS
+.sp
+.so cmap.mm
+.FG "Color Mapping File Format"
+.sp
+.DE
+.Ce
+.H 2 "Project-Related Input Files"
+.H 3 "Reading Session Files"
+.Cs "/project files/read-input-file"
+This command reads an \fIinput\fR file of commands.
+These files can be generated manually by using a text editor or
+saved from a \fIsession\fR file with the
+.Co write-input-file
+command.
+See the section called \fBCommand Input\fR for the format of this
+file.
+.Ce
+.H 3 "Shotline and Burst Point Input Files"
+.sp
+For an explanation of commands for reading in files of shotline or burst
+point coordinates,
+see the sections called \fBInput Discrete Shots\fR and
+\fBInput Discrete Burst Points\fR.
+.Ce
+.H 1 "Output File Options"
+.Cs "/project files"
+The following commands will turn on optional output.
+By default,
+no output is produced except error logging (see \fBError Log\fR),
+unless an output file is specified with the appropriate command.
+Any combination of output options may be specified for a particular run.
+Note that specifying an output file will cause an existing file with that
+name to be truncated to zero length.
+Therefore,
+only one such command should be entered per \fIsession\fR for a particular file
+name.
+Multiple runs during a \fIsession\fR will append to the same files if
+intervening commands to change the output file name are not given,
+except for the graphics files as explained below.
+Note that there is no way to append to a file created by a previous
+\fIsession\fR of the \*(b) program,
+but these files may be concatenated after the fact by using the
+\*(U)
+.Ud cat 1
+utility.
+.Ce
+.H 2 "Burst Point Library File"
+.Cs "/project files/burst-file"
+This command will open the named file for creating a burst point library.
+If the file exists,
+it will be truncated by this command.
+\fBAppendix A\fR describes the format for these files.
+.Ce
+.H 2 "Shotline File"
+.Cs "/project files/shotline-file"
+This command will open the named file for creating a shotline file.
+If the file exists,
+it will be truncated by this command.
+\fBAppendix B\fR describes the format for these files.
+.Ce
+.H 2 "\*(U) Plot File"
+.Cs "/project files/plot-file"
+This command generates a \*(U) plot file,
+using \*(B) extensions to the standard format.
+This option is useful for examining the shotline and burst ray information
+graphically as a three-dimensional vector plot.
+Due to constraints inherent in the \*(U) plot format,
+these plots must be displayed as a post-process step by using
+a \*(B) plotting utility such as \fBpl-sgi\fR or \fBpl-fb\fR.
+Because some of these display programs do not support multiple plots
+per file,
+the file name should be changed between runs.
+Table 3 describes the color mapping associated with these plots.
+.DF
+.sp
+.TB "Color Key for \s-1UNIX\s0 \*(Tm Plots"
+.so plot.mm
+.sp
+.DE
+.P
+If the user has specified a color mapping file with the
+.Co color-file
+command,
+then those colors will be used rather than the above colors for
+all shotline/ray intersections.
+.Ce
+.H 2 "Frame Buffer Image"
+.Cs "/project files/image-file"
+This option will generate a color image that provides the user with
+immediate feedback about a run.
+The grid is displayed graphically and each cell location is dynamically
+color coded to show its current status.
+Table 4 describes the color mapping associated with the grid.
+.DF
+.sp
+.TB "Color Key for Frame Buffer Image"
+.so fb.mm
+.sp
+.DE
+.P
+In addition to the above cell colors, hits on critical components by burst
+rays are depicted as a colored pixel projected into grid
+space from the intersection point where the ray enters the component.
+Colors for the components are mapped from ident numbers according to the
+table specified by the user with the
+.Co "/target files/color-file"
+directive and shaded using a lighting model illuminated from the viewing
+direction.
+.H 2 "Grid File"
+.Cs "/project files/grid-file"
+This command will store each shotline coordinate generated during the run
+as grid offsets.
+These files can later be read in to replicate a previous run's grid or discrete
+shots by using the
+.Co read-2d-shot-file
+command.
+This capability is especially useful when \fIdithered\fR shotlines have been
+used and it is desired that the same shotlines be used in another run.
+Note that the shotline intersection information is not saved,
+just the grid offsets for each shotline.
+.Ce
+.H 2 "Script File"
+.Cs "/project files/write-input-file"
+During a \fIsession\fR,
+all commands are saved in a temporary file.
+The
+.Co write-input-file
+command will create a \fIsnapshot\fR of this \fIsession\fR file,
+that can later be used to recreate the current \fIsession\fR
+up to the point when the file was written.
+The \fIsession\fR or \fIinput\fR files
+can later be used in one of two ways: either read in with the
+.Co read-input-file
+command,
+or supplied on the standard input of the \*(b) program.
+Note that the
+.Co write-input-file
+and
+.Co read-input-file
+commands will not be included in the \fIinput\fR files,
+but the commands read in by the latter \fIwill\fR.
+.Ce
+.H 2 "Error Log"
+.Cs "/project files/error-file"
+This command is useful to save errors in a log file and prevent copious
+ray tracer diagnostics from scrolling by on the screen.
+This option is especially useful if using the batch mode of execution
+so that the terminal is not tied up by program output.
+If no error log is specified,
+diagnostic messages will appear in the scrolling window or,
+if in batch mode,
+on the \*(b) program's standard error output.
+.Ce
+.H 2 "Histogram File"
+.Cs "/project files/histogram-file"
+This command generates a frequency histogram to the named file.
+The file format is simply one number per line; each number is a count
+of critical components hit by an individual burst ray.
+This file can easily be post-processed to display a histogram,
+for instance,
+how many rays hit zero, one, two, three, etc. components.
+.Ce
+.H 1 Conclusion
+There is a large, and rapidly growing, collection of highly detailed \*(m)
+models due to the widespread use of the highly portable \*(B) package.
+The \*(b) program gives the \*(F) community the option of analyzing \*(m)
+models.
+This, along with the \*(F) to \*(m) translator will permit an easy transition
+of the Air Force to the \*(B) system.
+Then,
+productivity in the target description arena,
+that has long been a bottleneck to the vulnerability and lethality analyst,
+will increase dramatically.
+Another benefit will be increased accuracy of results due to the superior
+detail and accuracy afforded by a true combinatorial solid geometry modeler.
+.H 1 Acknowledgments
+The author would like to thank Leonard E. Bruenning, Jr. of Sverdrup
+Technology, Inc. for his thorough, concise and well-illustrated
+documentation\*F of the requirements to be met by the \*(b) program
+and for his courteous and professional manner in fielding related questions.
+.FS
+Leonard E. Bruenning,
+"Interface Control Document for BURST Ray Generator Computer Program",
+\fBTechnical Report\fR,
+prepared for: Department of the Air Force,
+Armament Division,
+Eglin AFB,
+FL 32542-5000,
+14 December 1988.
+.FE
+.H 1 Appendices
+Both burst point library files and shotline files are composed
+of single-line records.
+Each line begins with a digit that identifies the type of record it represents.
+Both file formats are composed of one or more \fIruns\fR that begin with a
+\fIrun header\fR.
+Each shotline that intersects the target will result in a
+\fIshotline header\fR that is followed by one or
+more \fIshotline intersection\fR records.
+These record types exist for both file formats,
+but they do not contain the same information.
+Burst point library files have two additional record types,
+\fIburst ray headers\fR and \fIburst ray intersections\fR.
+If a burst point occurs along a shotline,
+the \fIburst ray header\fR will immediately follow that shotline's last
+intersection record.
+Each \fIburst ray header\fR records will be immediately followed by
+\fIburst ray intersection\fR records,
+one for each ray that strikes a \fIcritical component\fR.
+.bp
+.H 2 "Appendix A:  Burst Point Library File Format"
+Below is a description of the format of the burst point library files that
+are generated if the
+.Co burst-file
+command is used.
+.DS
+.so bpl.mm
+.DE
+.bp
+.H 2 "Appendix B:  Shotline File Format"
+Below is a description of the format of the shotline files that are
+generated if the
+.Co shotline-file
+command is used.
+.DS
+.so shotlines.mm
+.DE
+.de TX
+.ce
+TABLE OF CONTENTS       \" define header for TOC page
+..
+.de TY          \" suppress default TOC header
+..
+.TC
+.\" .CS
@@ -0,0 +1,12 @@
+.TS
+center,box;
+l.
+4001 4003       255 255 0       # Fuel
+4050 4050       255 255 0       # Fuel
+8000 8001       255 100 255     # Ammo
+100 165         150 255 100     # Hull armor
+610 619         220 150 100     # Commander
+720 729         220 150 100     # Gunner
+830 839         220 150 100     # Loader
+940 949         220 150 100     # Driver
+.TE
@@ -0,0 +1,55 @@
+.so defs.mm
+.ps -2
+.vs -2
+.TS
+center,allbox,tab(@);
+cb cb cb
+_ _ _
+cb ci c.
+COMMAND@ARGUMENTS@DESCRIPTION
+attack-direction@azim_angle elev_angle@specify azimuth and elevation of attack relative to target
+burst-air-file@file@input burst air idents from \fIfile\fR
+burst-armor-file@file@input burst armor idents from \fIfile\fR
+burst-coordinates@X  Y  Z@input single burst point location in target coordinates
+burst-distance@distance@offset burst point along shotline (see \fBBurst Distance\fR)
+burst-file@file@output burst point library to \fIfile\fR
+cell-size@distance@specify shotline separation (equidistant horizontal and vertical)
+color-file@file@input ident to color mapping from \fIfile\fR (for graphics)
+cone-half-angle@angle@specify limiting angle for spall ray generation
+critical-comp-file@file@input critical component idents from \fIfile\fR
+deflect-spall-cone@flag@deflect axis of spall cone half way towards exit normal
+dither-cells@flag@if \fIyes\fR, randomly offset shotline within grid cell
+enclose-target@@generate rectangular grid of shotlines for full target envelope
+enclose-portion@left right bottom top@T{
+generate partial envelope by specifying grid boundaries
+T}
+error-file@file@divert all diagnostics to \fIfile\fR
+execute@@initiate a run (no output produced without this command)
+grid-file@file@save shotline locations (Y' Z') in \fIfile\fR
+ground-plane@flag [Z  +X  -X  +Y  -Y]@T{
+if \fIyes\fR, burst on ground (see \fBGround Plane Bursting\fR).
+T}
+histogram-file@file@write hit frequency histogram to \fIfile\fR
+image-file@file@generate frame buffer image on specified \fIfile\fR or device
+input-2d-shot@Y'  Z'@input single shotline location as grid offsets
+input-3d-shot@X  Y  Z@input single shotline location in target coordinates
+max-barriers@count@specify the maximum number of components to report along spall ray
+max-spall-rays@count@specify the desired number of spall rays generated per burst point
+plot-file@file@generate \*(U) plot in \fIfile\fR
+read-2d-shot-file@file@read shot locations from \fIfile\fR as grid offsets (see \fBinput-2d-shot\fR)
+read-3d-shot-file@file@read shot locations from \fIfile\fR in target coords. (see \fBinput-3d-shot\fR)
+read-burst-file@file@read burst point locations from \fIfile\fR (see \fBburst-coordinates\fR)
+read-input-file@file@read key word commands from \fIfile\fR
+report-overlaps@flag@if \fIyes\fR, log overlap diagnostics
+shotline-burst@flag [flag]@T{
+if \fIyes\fR, generate burst points along shotlines (see \fBBurst on Contact\fR).
+T}
+shotline-file@file@output shot line data to \fIfile\fR
+target-file@file@read \*(m) data base from \fIfile\fR
+target-objects@object0 [object1 object2 ...]@list objects from \*(m) data base to interrogate
+units@name@linear units (\fIinches,feet,millimeters,centimeters,meters\fR)
+write-input-file@file@save script of commands in \fIfile\fR
+#@@any line beginning with the `\fB#\fR' character is a comment
+.TE
+.ps +2
+.vs +2
@@ -0,0 +1,21 @@
+.ds A) \fI axis\fR
+.ds a) \fI axes\fR
+.ds B) \fB\s-1BRL-CAD\s0\fR
+.ds b) \fBburst\fR
+.ds f) \fBlibfb\fR
+.ds F) \fB\s-1FASTGEN\s0\fR
+.ds G) \fB\s-1PGEN\s0\fR
+.ds l) \fBlibrt\fR
+.ds m) \fBmged\fR
+.ds p) \fBlibplot3\fR
+.ds P) \fB\s-1PDAM\s0\fR
+.ds S) \fB\s-1SHOTGEN\s0\fR
+.ds U) \s-1UNIX\s0 \*(Tm
+.ds X) \fIX\fR
+.ds Y) \fIY\fR
+.ds Z) \fIZ\fR
+.ds x) \fIX'\fR
+.ds y) \fIY'\fR
+.ds z) \fIZ'\fR
+.ds HF 3 3 3 3 3 3 3
+.ds HP +2 +2 +2 +2 +2 +2 +2
@@ -0,0 +1,15 @@
+.TS
+center,allbox,tab(@);
+cb cb cb cb cb
+_ _ _ _ _
+lb ci ci ci l.
+COLOR@R@G@B@REPRESENTATION
+red@255@0@0@axis of grid
+black@0@0@0@grid cell boundaries
+blue@150@100@255@outside of grid
+lt grey@200@200@200@shot missed target
+white@255@255@255@shot hit target
+lt green@200@255@200@burst occurred but hit no critical components
+pink@255@200@200@burst occurred and hit some critical components
+purple@255@0@255@a ground burst occurred
+.TE
@@ -0,0 +1,12 @@
+.TS
+center,allbox;
+cb cb
+_ _
+ci c.
+KEY	FUNCTION
+u or ^P	move cursor to item above the current item
+d or ^N	move cursor to item below the current item
+h or ?	print help message about the current item
+q	exit the current menu without making a selection
+space	select the current item
+.TE
@@ -0,0 +1,11 @@
+.TS
+center,box;
+l.
+600-999
+1011
+4002-4050
+8000
+9001
+9004
+9005
+.TE
@@ -0,0 +1,53 @@
+A joint-services sponsored program is currently establishing a Ballistic
+Research Laboratory-Computer Aided Design (\*(B))
+modeling capability at Eglin Air Force Base, Florida.
+Currently, the Air Force uses \*(F) to model target geometries using
+polygonal facets, two-dimensional plates, and some solid primitives.
+They also maintain compatibility with \*(S), a precursor to \*(F).
+These modelers are cumbersome to use by today's standards and the resultant
+descriptions,
+while taking an extremely long time to build,
+fall far short of the accuracy and information content of true
+combinatorial solid geometry models such as produced by
+the \fBM\fRultiple-device \fBG\fRraphics \fBED\fRitor (\*(m)),
+the \*(B) modeler.
+Along with this capability comes several key requirements,
+one of which will be addressed in this paper;
+an interface to Eglin AFB's Point Burst Damage Assessment Model (\*(P))
+from \*(B) solid models.
+.P
+The \*(b) program enables the user to direct ray tracing
+of the \*(m) models to prepare inputs to the
+\*(P) code in the form of shotline files and burst point library files.
+The program is capable of supporting analyses of varied threat
+mechanisms on \*(m) targets.
+The shotline and burst point library files are written in
+.SM ASCII
+and are supplemented with both shaded, color images
+and 3-d vector plots using the \*(B) frame buffer (\*(f)) and extended
+\*(U)
+.FS \*(Tm
+UNIX is a registered trademark of AT&T.
+.FE
+plot (\*(p)) libraries for portability to virtually all hardware
+platforms running the \*(U) operating system.
+The terminal-independent user interface employs hierarchical menus
+coupled with optional graphics displays facilitating ease of use and
+maximizing information feed back to the operator while permitting full
+featured use from any video terminal or window system.
+The menu-driven interface is coupled with an interpreter that
+accepts key word commands for batch input if the user wishes to
+detach the job to run unattended.
+These key word command files can either be prepared automatically from
+the user-selected parameters orchestrated by the menu system,
+typed in by hand with an editor,
+or perhaps generated from another process in a pipeline configuration.
+.P
+This paper is intended to serve a dual function,
+both as a technical memorandum,
+and as a user manual.
+Hopefully,
+not only will it help one appreciate why \*(b) was developed in the first place
+but will help readers decide whether they need to acquire it,
+and if so,
+how to use it.
@@ -0,0 +1,28 @@
+'\" define macro for program usage examples
+.de Ex
+.sp
+.in +0.5i
+\fI$\ \\$1\fR
+.in -0.5i
+.sp
+..
+'\" define macro for naming coordinate axes
+.de Ax
+\\$1, \\$2, and \\$3\fI axes\fR
+..
+'\" define macro for naming commands
+.de Co
+\fB\\$1\fR
+..
+'\" define macros for command descriptions.
+.de Cs                  \" Start command description.
+.br
+\s-1\fB[menu reference:\\$1]\fR\s0
+.P
+..
+.de Ce                  \" End command description.
+.sp
+..
+.de Ud
+.BI \\$1 (\\$2)\^
+..
@@ -0,0 +1,48 @@
+.so defs.mm
+.H 1 Introduction
+.H 1 "User Interface"
+.H 2 "Program Invocation"
+.H 2 "Command Input"
+.H 2 "Screen Layout"
+.H 2 "Hierarchical Menus"
+.H 2 "Scrolling Region"
+.H 1 "Shotlining Options"
+.H 2 "Attack Direction"
+.H 2 "Cell Size"
+.H 2 "Dithering"
+.H 2 "Gridding"
+.H 3 "Envelope"
+.H 4 "Enclose target"
+.H 4 "Enclose portion of target"
+.H 3 "Input shot coordinates"
+.H 4 "Target coordinate system"
+.H 5 "Type in 3-D coordinates"
+.H 5 "Read file of 3-D coordinates"
+.H 4 "Shotline coordinate system"
+.H 5 "Type in 2-D coordinates"
+.H 5 "Read file of 2-D coordinates"
+.H 1 "Bursting Options"
+.H 2 "Method of Locating Burst Point"
+.H 3 "Input burst point coordinates"
+.H 4 "Type in 3-D coordinates"
+.H 4 "Read file of 3-D coordinates"
+.H 3 "Burst on contact"
+.H 4 "Ground plane bursting"
+.H 4 "Burst on armor"
+.H 2 "Bursting Parameters"
+.H 3 "Burst distance"
+.H 3 "Sampling cone half angle"
+.H 3 "Deflected sampling cone"
+.H 3 "Number of sampling rays"
+.H 3 "Maximum barriers"
+.H 1 "Output Options"
+.H 2 "UNIX Plot File"
+.H 2 "Frame Buffer Image"
+.H 2 "Burst Point Library"
+.H 2 "Shotline File"
+.H 2 "Grid File"
+.H 2 "Script File"
+.H 2 "Error Log"
+.H 1 Conclusion
+
+
@@ -0,0 +1,18 @@
+.TS
+center,box,tab(@);
+l.
+OVERLAP:
+reg=/component/turret/tur.ext/tur.armor/tur.bot{{0}} isol=s2,
+reg=/component/hull/hull.ext/hull.armor/r1.top{{0}} osol=ss4,
+depth 544.21mm at (-471.784,812.8,0) x-2 y1 lvl0 purpose=shotline
+_
+OVERLAP:
+reg=/component/turret/tur.ext/tur.ring{{0}} isol=ss2,
+reg=/component/turret/tur.ext/tur.armor/tur.bot{{0}} osol=s2,
+depth 25.39mm at (-418.907,812.8,0) x-2 y1 lvl1 purpose=normal thickness
+_
+OVERLAP:
+reg=/component/turret/tur.ext/tur.ring{{0}} isol=ss2,
+reg=/component/turret/tur.ext/tur.armor/tur.bot{{0}} osol=s2,
+depth 52.88mm at (-418.907,-812.8,0) x-2 y1 lvl1 purpose=spall ray
+.TE
@@ -0,0 +1,13 @@
+.TS
+center,allbox,tab(@);
+cb cb cb cb cb
+_ _ _ _ _
+lb ci ci ci l.
+COLOR@R@G@B@REPRESENTATION
+yellow@255@255@0@grid cell centers
+red@255@0@0@burst cone
+blue@0@0@255@default component intersection
+lt blue@100@100@255@default outside air intersection
+lt green@100@255@100@default inside air intersection
+purple@255@0@255@default critical component intersection
+.TE
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+MASTER=burst
+#MASTER=debug
+
+doclifter -h hints.txt -x -vvvv $MASTER.mm #2>t
+
+STATUS=$?
+
+echo "doclifter return value for '$MASTER' was '$STATUS'"
@@ -0,0 +1,54 @@
+.TS
+center,box,tab(@);
+c0 l s s s.
+@0.97 user + 1.21 sys in 6 elapsed secs (16.1667%)
+.T&
+c0   c   c   c   c
+c0 | c | c | c | c
+c0 | c | c | c | c
+c0 | c | _ | c | c
+c0 | c | c | c | c
+c0 | c | c | c | c
+c0 | c | c   _   c
+c0 | c | c   c   c .
+@_@_@_@
+@units@bursting method@burst-distance
+@project files@\fBbursting parameters\fR@\fBcone-half-angle\fR
+@target files@@deflect-spall-cone
+@shotlines@@max-spall-rays
+@\fBburst points\fR@@max-barriers
+@comment
+@execute
+@preferences
+@_@
+.sp 2
+.T&
+c0 lb s s c
+c0 lb s s c
+c0 l  s s s .
+@degrees from spall cone axis to limit burst rays
+@Cone angle ? (degrees)[45.000000]
+@___BURST (2.2)_______________________________________________
+.T&
+c0 l l.
+@error-file@tfiles/ktank.log
+@plot-file@tfiles/ktank.plot
+@image-file@/dev/sgi
+@units@inches
+@shotline-file@tfiles/ktank.shotlines
+@burst-file@tfiles/ktank.burst
+@burst-air-file@tfiles/ktank,air.ids
+@burst-armor-file@tfiles/ktank,armor.ids
+@critical-comp-file@tfiles/ktank,crit.ids
+@color-file@tfiles/ktank,colors
+@burst-distance@0
+@cell-size@16
+@attack-direction@0 0
+@max-spall-rays@50
+@cone-half-angle@45
+@target-file@/vld/moss/g/ktank.g
+@target-objects@component
+@report-overlaps@no
+@shotline-burst@yes yes
+@#ground-plane@yes 66 200 200 200 200
+.TE
@@ -0,0 +1,12 @@
+.TS
+center;
+c c c.
+\d\s+6\s+4^\s-4\s-6\u	_	\d\s+6\s+4^\s-4\s-6\u
+|	target files	|
+|	shotlines	|
+|	burst points	|
+|	comment	|
+|	\fBexecute\fR	|
+|	preferences	|
+\s+2+\s0	_	\s+2+\s0
+.TE
@@ -0,0 +1,29 @@
+.TS
+center,allbox,tab(@);
+lb lb lb
+_ _ _
+l l l.
+record description@field format@field description
+run header@'1'@record number 1
+@1x,f9.4@attack azimuth in degrees
+@1x,f8.4@attack elevation in degrees
+@1x,f7.2@shotline separation
+@1x,f7.2@maximum Y' coordinate of target
+@1x,f7.2@minimum Y' coordinate of target
+@1x,f7.2@maximum Z' coordinate of target
+@1x,f7.2@minimum Z' coordinate of target
+@1x,6a@units (\fImm,cm,inches,feet,meters\fR)
+shotline header@'2'@record number 2
+@1x,f8.3@Y' coordinate of shotline
+@1x,f8.3@Z' coordinate of shotline
+shotline intersections@'3'@record number 3
+@1x,f8.2@X' coordinate of intersection
+@1x,f7.3@sine of fallback angle of exit normal
+@1x,f7.2@rotation angle of exit normal in degrees
+@1x,i4@component code number
+@1x,f8.2@normal thickness of component
+@1x,f8.2@line-of-sight thickness of component
+@1x,i2@space code following component
+@1x,f7.2@obliquity angle at entry to component in degrees
+@1x,f7.2@obliquity angle at exit from component in degrees
+.TE
@@ -0,0 +1,12 @@
+.TS
+center,tab(@);
+c c c c c.
+\s+2+\s0@_@\s+2+\s0@_@\s+2+\s0
+|@units@|@\fBtarget-file\fR@|
+|@project files@|@target-objects@|
+|@\fBtarget files\fR@|@burst-air-file@|
+|@shotlines@|@burst-armor-file@|
+|@burst points@|@critical-comp-file@|
+|@comment@|@color-file@|
+\s+2v\s0@_@\s+2+\s0@_@\s+2+\s0
+.TE
@@ -0,0 +1,10 @@
+.ce
+\fB``burst''; Air Force Vulnerability Analyses from BRL-CAD Models\fR
+.ce
+"\fIGary S. Moss"
+.sp
+.ce 4
+"\fRBRL-CAD Open Source"
+.sp
+.ce
+"moss@vmb.brl.mil"
@@ -0,0 +1,12 @@
+.TS
+center;
+c c c.
+\s+2+\s0	_	\s+2+\s0
+|	\fBunits\fR	|
+|	project files	|
+|	target files	|
+|	shotlines	|
+|	burst points	|
+|	comment	|
+\s+2v\s0	_	\s+2v\s0
+.TE
@@ -3386,6 +3386,11 @@
        <link xlink:href="../../man1/en/g-var.php">G-var</link>
      </para>
    </listitem>
+    <listitem>
+      <para>
+        <link xlink:href="../../man1/en/g-vrml.php">G-vrml</link>
+      </para>
+    </listitem>
    <listitem>
      <para>
        <link xlink:href="../../man1/en/g-x3d.php">G x3d</link>
@@ -4323,6 +4328,11 @@
        <link xlink:href="../../mann/en/d.php">D</link>
      </para>
    </listitem>
+    <listitem>
+      <para>
+        <link xlink:href="../../mann/en/dall.php">Dall</link>
+      </para>
+    </listitem>
    <listitem>
      <para>
        <link xlink:href="../../mann/en/db.php">DB</link>
@@ -4468,6 +4478,11 @@
        <link xlink:href="../../mann/en/erase.php">Erase</link>
      </para>
    </listitem>
+    <listitem>
+      <para>
+        <link xlink:href="../../mann/en/erase_all.php">Erase All</link>
+      </para>
+    </listitem>
    <listitem>
      <para>
        <link xlink:href="../../mann/en/ev.php">EV</link>
@@ -4488,6 +4503,11 @@
        <link xlink:href="../../mann/en/expand.php">Expand</link>
      </para>
    </listitem>
+    <listitem>
+      <para>
+        <link xlink:href="../../mann/en/export_body.php">Export Body</link>
+      </para>
+    </listitem>
    <listitem>
      <para>
        <link xlink:href="../../mann/en/extrude.php">Extrude</link>
@@ -5213,6 +5233,11 @@
        <link xlink:href="../../mann/en/vquery_ray.php">Vquery Ray</link>
      </para>
    </listitem>
+    <listitem>
+      <para>
+        <link xlink:href="../../mann/en/vrmgr.php">Vrmgr</link>
+      </para>
+    </listitem>
    <listitem>
      <para>
        <link xlink:href="../../mann/en/vrot.php">vrot</link>
@@ -5162,6 +5162,9 @@ x 					delete character
  <entry>
    <link linkend="d">d</link>
  </entry>
+  <entry>
+    <link linkend="dall">dall</link>
+  </entry>
  <entry>
    <link linkend="db">db</link>
  </entry>
@@ -5244,6 +5247,9 @@ x 					delete character
  <entry>
    <link linkend="erase">erase</link>
  </entry>
+  <entry>
+    <link linkend="erase_all">erase_all</link>
+  </entry>
  <entry>
    <link linkend="ev">ev</link>
  </entry>
@@ -5255,6 +5261,9 @@ x 					delete character
  <entry>
    <link linkend="expand">expand</link>
  </entry>
+  <entry>
+    <link linkend="export_body">export_body</link>
+  </entry>
  <entry>
    <link linkend="expand_comb">expand_comb</link>
  </entry>
@@ -5456,11 +5465,20 @@ x 					delete character
  <entry>
    <link linkend="permute">permute</link>
  </entry>
+  <entry>
+    <link linkend="pl">pl</link>
+  </entry>
  <entry>
    <link linkend="plot">plot</link>
  </entry>
+  <entry>
+    <link linkend="polybinout">polybinout</link>
+  </entry>
  </row>
 <row>
+  <entry>
+    <link linkend="pov">pov</link>
+  </entry>
  <entry>
    <link linkend="prcolor">prcolor</link>
  </entry>
@@ -5705,6 +5723,9 @@ x 					delete character
  <entry>
    <link linkend="vquery_ray">vquery_ray</link>
  </entry>
+  <entry>
+    <link linkend="vrmgr">vrmgr</link>
+  </entry>
  <entry>
    <link linkend="vrot">vrot</link>
  </entry>
@@ -7906,7 +7927,8 @@ x 					delete character
          explicitly displayed objects). Objects that are displayed as
          members of explicitly displayed combinations cannot be deleted
          from the display with this command (see
-          <link linkend="erase">erase -r</link>). Note that this
+          <link linkend="dall">dall</link> or
+          <link linkend="erase_all">erase_all</link>). Note that this
          has no effect on the <emphasis>BRL-CAD</emphasis> database
          itself. To actually remove objects from the database, use the
          <link linkend="kill">kill</link> command.
@@ -7932,6 +7954,36 @@ x 					delete character
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <variablelist xml:id="dall">
+    <varlistentry>
+      <term>
+        dall <emphasis>&lt;objects</emphasis>&gt;
+      </term>
+      <listitem>
+        <para>
+          The <quote>dall</quote> command deletes the specified list of
+          objects from the <emphasis>mged</emphasis> display. This is a
+          synonym for the <link linkend="erase_all">erase_all</link>
+          command. This command will allow the user to delete objects
+          that have not been explicitly displayed (unlike the
+          <link linkend="d">d</link> command). Note that this has no
+          effect on the <emphasis>BRL-CAD</emphasis> database itself. To
+          actually remove objects from the database, use the
+          <link linkend="kill">kill</link> command.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        Examples:
+      </term>
+      <listitem>
+        <para>
+          mged&gt; dall region1 shapea
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
  <para>
    – Delete <emphasis>region1</emphasis> and
    <emphasis>shapea</emphasis> from the <emphasis>mged</emphasis>
@@ -9258,7 +9310,8 @@ x 					delete character
          explicitly displayed objects). Objects that are displayed as
          members of explicitly displayed combinations cannot be deleted
          from the display with this command (see
-          <link linkend="erase">erase -r</link>). Note that this
+          <link linkend="dall">dall</link> or
+          <link linkend="erase_all">erase_all</link>). Note that this
          has no effect on the <emphasis>BRL-CAD</emphasis> database
          itself. To actually remove objects from the database, use the
          <link linkend="kill">kill</link> command.
@@ -9283,6 +9336,36 @@ x 					delete character
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <variablelist xml:id="erase_all">
+    <varlistentry>
+      <term>
+        erase_all <emphasis>&lt;objects</emphasis>&gt;
+      </term>
+      <listitem>
+        <para>
+          The <quote>erase_all</quote> command deletes the specified
+          list of objects from the MGED display. This is a synonym for
+          the <link linkend="dall">dall</link> command. This command
+          will allow the user to delete objects that have not been
+          explicitly displayed (unlike the <link linkend="d">d</link> or
+          <link linkend="erase">erase</link> commands). Note that this
+          has no effect on the <emphasis>BRL-CAD</emphasis> database
+          itself. To actually remove objects from the database, use the
+          <link linkend="kill">kill</link> command.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        Examples:
+      </term>
+      <listitem>
+        <para>
+          mged&gt; erase_all region1 shapea
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
  <para>
    – Delete <emphasis>region1</emphasis> and
    <emphasis>shapea</emphasis> from the MGED display.
@@ -9462,6 +9545,28 @@ x 					delete character
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <para xml:id="export_body">
+    export_body object file
+  </para>
+  <para>
+    The <quote>export_body</quote> command is used to copy the contents
+    of the specified binary <emphasis>object</emphasis> into the
+    specified <emphasis>file</emphasis>. Currently, only binary objects
+    containing a uniform array of simple objects is supported.
+  </para>
+  <para>
+    Examples:
+  </para>
+  <para>
+    <literal></literal>
+  </para>
+  <para>
+    mged&gt; export_body bin_chars /home/fred/chars
+  </para>
+  <para>
+    – Copy the contents of <quote>bin_chars</quote> into the file
+    <quote>/home/fred/chars</quote>
+  </para>
  <para xml:id="expand_comb">
    expand_comb <emphasis>prefix comb …</emphasis>
  </para>
@@ -11626,12 +11731,12 @@ foo.r_xpand/R
    </listitem>
    <listitem>
      <para>
-        extrude
+        extrude – experimental.
      </para>
    </listitem>
    <listitem>
      <para>
-        sketch
+        sketch – experimental.
      </para>
    </listitem>
  </itemizedlist>
@@ -12585,6 +12690,53 @@ foo.r_xpand/R
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <variablelist xml:id="pl">
+    <varlistentry>
+      <term>
+        pl [<emphasis>-float</emphasis>] [<emphasis>-zclip</emphasis>]
+        [<emphasis>-2d</emphasis>] [<emphasis>-grid</emphasis>]
+        <emphasis>out_file</emphasis> | <quote>|</quote> filter
+      </term>
+      <listitem>
+        <para>
+          The <quote>pl</quote> command creates a UNIX plot of the
+          current MGED display. If an <emphasis>output_file</emphasis>
+          is specified, the plot is stored in that file. If a
+          <emphasis>filter</emphasis> is specified, the output is sent
+          to that <emphasis>filter</emphasis>. The
+          <emphasis>-float</emphasis> option requests a plot file with
+          real numbers rather than integers. The
+          <emphasis>-zclip</emphasis> option requests that the plot be
+          clipped to the viewing cube in the Z-direction. The
+          <emphasis>-2d</emphasis> option requests a two-dimensional
+          plot (the default is 3D). The <emphasis>-grid</emphasis>
+          option is intended to include a grid in the plot, but is
+          currently not implemented. This command uses the
+          <emphasis>dm-plot</emphasis> display manager. The
+          <link linkend="plot">plot</link> command performs the same
+          function, but does not use the <emphasis>dm-plot</emphasis>
+          display manager.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        Examples:
+      </term>
+      <listitem>
+        <para>
+          mged&gt; pl -float | pldebug
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
+    – Create a UNIX plot of the current MGED display and pipe the
+    results to the <emphasis>pldebug</emphasis> command.
+  </para>
+  <para>
+    <emphasis role="strong"></emphasis>
+  </para>
  <variablelist xml:id="plot">
    <varlistentry>
      <term>
@@ -12606,7 +12758,11 @@ foo.r_xpand/R
          <emphasis>-2d</emphasis> option requests a two-dimensional
          plot (the default is 3D). The <emphasis>-grid</emphasis>
          option is intended to include a grid in the plot, but is
-          currently not implemented.
+          currently not implemented. This command does not use the
+          <emphasis>dm-plot</emphasis> display manager. The
+          <link linkend="pl">pl</link> command performs the same
+          function, but does use the <emphasis>dm-plot</emphasis>
+          display manager.
        </para>
      </listitem>
    </varlistentry>
@@ -12628,6 +12784,36 @@ foo.r_xpand/R
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <variablelist>
+    <varlistentry>
+      <term xml:id="polybinout">
+        polybinout file
+      </term>
+      <listitem>
+        <para>
+          Store vlist polygons into polygon file (experimental).
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
+    <emphasis role="strong"></emphasis>
+  </para>
+  <variablelist>
+    <varlistentry>
+      <term xml:id="pov">
+        pov args
+      </term>
+      <listitem>
+        <para>
+          Set the point-of-view (experimental).
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
+    <emphasis role="strong"></emphasis>
+  </para>
  <variablelist xml:id="prcolor">
    <varlistentry>
      <term>
@@ -16639,6 +16825,50 @@ EOF
  <para>
    <emphasis role="strong"></emphasis>
  </para>
+  <variablelist xml:id="vrmgr">
+    <varlistentry>
+      <term>
+        vrmgr <emphasis>host</emphasis> {<emphasis>master</emphasis> |
+        <emphasis>slave</emphasis> | <emphasis>overview</emphasis>}
+      </term>
+      <listitem>
+        <para>
+          The <quote>vrmgr</quote> command establishes a link between
+          the current MGED display and a <emphasis>vrmgr</emphasis>
+          process running on the specified <emphasis>host</emphasis>.
+          The <emphasis>vrmgr</emphasis> program is a manager for
+          virtual reality displays using MGED. The
+          <emphasis>vrmgr</emphasis> process must be started on
+          <emphasis>host</emphasis> prior to executing the
+          <emphasis>vrmgr</emphasis> command in MGED. The second command
+          line argument to the <emphasis>vrmgr</emphasis> command is the
+          role of the current MGED display. The
+          <emphasis>master</emphasis> display controls the viewing
+          parameters of itself and all the <emphasis>slave</emphasis>
+          displays. The <emphasis>overview</emphasis> display acts as an
+          observer of the entire virtual reality process.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>
+        Examples:
+      </term>
+      <listitem>
+        <para>
+          mged&gt; vrmgr host1.brlcad.org master
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
+    – Set the current MGED display as the <emphasis>master</emphasis>
+    for the <emphasis>vrmgr</emphasis> process running on the host named
+    <emphasis>host1.brlcad.org.</emphasis>
+  </para>
+  <para>
+    <emphasis role="strong"></emphasis>
+  </para>
  <variablelist xml:id="vrot">
    <varlistentry>
      <term>
@@ -2963,7 +2963,7 @@ comb comb_name u a - b + c
    <para>
      There are several ways to evaluate BRL-CAD geometry. These include
      (1) rendering the image using rt, (2) checking for overlaps using rtcheck
-      (or the lesser-known/used glint or MGED's overlap tool), and (3) checking
+      (or the lesser-known/used g_lint or MGED's overlap tool), and (3) checking
      for faulty material composition (e.g., densities) using rtweight.
    </para>
    <para>
@@ -2977,7 +2977,7 @@ comb comb_name u a - b + c
    </para>
    <para>
      As subcomponents are organized into assemblies and the complexity of the
-      geometry increases, it is then a good practice to use rtcheck (or glint
+      geometry increases, it is then a good practice to use rtcheck (or g_lint
      or the overlap tool) to help find any errors in the geometry and isolate
      any problems.
    </para>
@@ -904,7 +904,7 @@ Engineering Company, 2002):</para>
 	  <para><option>-R refset_name</option> - specifies a desired reference set (which Unigraphics uses to provide additional control over assembly components), overriding the reference set specified in the Unigraphics model.</para>
 	</listitem>
 	<listitem>
-	  <para><option>-f</option> - facetizes all the geometry. If this option is not specified, the converter will attempt to create CSG equivalent geometry wherever possible.</para>
+	  <para><option>-f</option> - facetizes all the geometry. If this option is not specified, the converter will attempt to create CSG equivalent geometry wherever possible. (Note that this option is experimental.)</para>
 	</listitem>
 	<listitem>
 	  <para><option>-s</option> - lists all features that were attempted to convert to CSG. (This option and the <option>-f</option> option are mutually exclusive.)</para>
@@ -92,8 +92,8 @@
      are combined using boolean operations to form regions of homogeneous material.
    </para>
    <para>
-      The database is organized as a <emphasis>directed acyclic graph</emphasis> (DAG), which is
-      comprised of:
+      The database is organized as a <emphasis>directed acyclic graph</emphasis> (DAG), which
+      comprises

      <itemizedlist>
 	<listitem>
@@ -107,7 +107,7 @@
 	  </para>
 	</listitem>
 	<listitem>
-	  <para><emphasis>arcs</emphasis> - containing boolean operators and 4x4 homogeneous transformation matrices.</para>
+	  <para><emphasis>arcs</emphasis> - contain boolean operators and 4x4 homogeneous transformation matrices.</para>
 	</listitem>
      </itemizedlist>
    </para>
@@ -1600,6 +1600,14 @@
 	place of anameN+1 signals the end of the ASCII attribute data.
      </para>

+      <para>
+	PROPOSED: A second type of attribute has an ASCII key but a binary value.
+        Such attributes follow the ASCII-valued ones after the double NULLs:
+	<literallayout class="normal">anameN+1 NULL uintN &lt;uintN  binary bytes&gt; [...0 or more binary attribute pairs]</literallayout>
+        where, for each binary attribute pair, the uintN is of size AWid and is
+        the length of the binary value for its ASCII key.
+      </para>
+
      <para>
 	Every object in the database may have zero or more attributes
 	attached to it; the meaning of these attributes will vary
@@ -3,8 +3,6 @@ set(specifications_EN
  )
 ADD_DOCBOOK("HTML;PHP;PDF" specifications_EN specifications/en "")

-CMAKEFILES(BRL_CAD_g_format_V6.xml)
-
 # Local Variables:
 # tab-width: 8
 # mode: cmake
@@ -5,7 +5,6 @@ set(man1_EN
  anim_track.xml
  anim_turn.xml
  ap-pix.xml
-  alias-pix.xml
  asc-nmg.xml
  asc-plot3.xml
  asc2dsp.xml
@@ -13,14 +12,12 @@ set(man1_EN
  azel.xml
  bary.xml
  benchmark.xml
-  brlman.xml
  bot_dump.xml
  bot_shell-vtk.xml
  brep_simple.xml
  brlcad-config.xml
  brlcad.xml
  buffer.xml
-  burst.xml
  bw-fb.xml
  bw-imp.xml
  bw-pix.xml
@@ -89,7 +86,6 @@ set(man1_EN
  fbzoom.xml
  firpass.xml
  g-acad.xml
-  g-dot.xml
  g-dxf.xml
  g-egg.xml
  g-euclid.xml
@@ -97,7 +93,6 @@ set(man1_EN
  g-nff.xml
  g-nmg.xml
  g-obj.xml
-  g-ply.xml
  g-raw.xml
  g-shell-rect.xml
  g-step.xml
@@ -107,18 +102,17 @@ set(man1_EN
  g-voxel.xml
  g-vrml.xml
  g-x3d.xml
+  g-dot.xml
  g2asc.xml
-  gastank.xml
+  g_diff.xml
+  g_lint.xml
  gdiff.xml
  gencolor.xml
  gif-fb.xml
  gif2fb.xml
-  glint.xml
  gqa.xml
  halftone.xml
-  handle.xml
  hex.xml
-  icv.xml
  iges-g.xml
  imgdims.xml
  ir-X.xml
@@ -135,7 +129,6 @@ set(man1_EN
  obj-g.xml
  patch-g.xml
  pictx.xml
-  picket_fence.xml
  pix-alias.xml
  pix-bw.xml
  pix-fb.xml
@@ -241,9 +234,6 @@ set(man1_EN
  vdeck.xml
  viewpoint-g.xml
  wavelet.xml
-  window.xml
-  window_frame.xml
-  wire.xml
  wdb_example.xml
  )

@@ -284,6 +284,23 @@ are, by convention, lower case for file information,
 and upper case for screen information.
 Here's a list of some of the common options you may encounter:</para>
 <variablelist remap='TP'>
+  <varlistentry>
+  <term><option>-h</option></term>
+  <listitem>
+<para>The "high resolution" flag, increasing the default screen and file
+size of 512x512
+to 1024x1024.  Has same effect as
+<option>-s</option> 1024 (or <option>-S</option> 1024)
+but exists as a convenient shorthand held over from the simple days
+when framebuffers were square, and only came in two resolutions.
+This historical usage unfortunately preempts this letter from use
+as a height specifier, forcing that function to relocate under
+protest to
+<option>-n</option>,
+which can be thought of as "number of scanlines", which isn't
+too bad a mnemonic.</para>
+  </listitem>
+  </varlistentry>
  <varlistentry>
  <term><option>-i</option></term>
  <listitem>
@@ -1,109 +0,0 @@
-<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="brlman1">
-
-  <refmeta>
-    <refentrytitle>BRLMAN</refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
-    <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
-  </refmeta>
-
-  <refnamediv xml:id="name">
-    <refname>brlman</refname>
-    <refpurpose>
-      a manual page viewer for BRL-CAD
-    </refpurpose>
-  </refnamediv>
-
-  <!-- body begins here -->
-  <refsynopsisdiv xml:id="synopsis">
-    <cmdsynopsis sepchar=" ">
-      <command>brlman</command>
-      <arg choice="opt" rep="repeat"><replaceable>options</replaceable></arg>
-      <arg choice="opt"><replaceable>manpage</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-  <refsection xml:id="description"><title>DESCRIPTION</title>
-
-    <para>
-      <command>brlman</command> provides manual page viewing capabilities for
-      BRL-CAD's programs, commands, libraries, and conventions (such as file
-      formats and attribute standards.)  On Unix-type systems, its default
-      behavior is to wrap the system <command>man</command> command with the appropriate path
-      information to allow man to find and display BRL-CAD's man pages.  On
-      systems without a <command>man</command> command, <command>brlman</command>
-      will instead launch a Tcl/Tk based graphical view that displays html
-      versions of the manual pages.  Both versions are generated from the same
-      DocBook source files and contain the same information.
-    </para>
-
-  </refsection>
-
-  <refsection xml:id="brlman_options"><title>OPTIONS</title>
-
-    <variablelist remap="TP">
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-h</emphasis></term>
-	<listitem>
-	  <para>
-	    Prints help.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-g</emphasis></term>
-	<listitem>
-	  <para>
-	    Instructs <command>brlman</command> to use its graphical man page viewer.
-	  </para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-L</emphasis></term>
-	<listitem>
-	  <para>
-	    Specify a language to use when selecting man pages.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-S [1 3 5 n]</emphasis></term>
-	<listitem>
-	  <para>
-	    Specify a particular section to use when searching for a man page.  Useful when there are programs and MGED commands with the same names - the default man page returned will be that of the program, so <option>-S</option> can be used to specify the MGED page instead.  Allowed sections are 1 (programs), 3 (libraries), 5 (conventions), and n (MGED).
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">--no-gui</emphasis></term>
-	<listitem>
-	  <para>
-	    Instructs <command>brlman</command> <emphasis>not</emphasis> to use its graphical man page viewer, even in situations where there is no command line option.  Primarily useful in scripting situations.
-	  </para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-  </refsection>
-
-  <refsection xml:id="author"><title>AUTHOR</title>
-    <para>Clifford Yapp</para>
-  </refsection>
-
-  <refsection xml:id="copyright"><title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 2016 United States Government as
-      represented by the U.S. Army Rebrlman Laboratory.
-    </para>
-  </refsection>
-
-  <refsection xml:id="bug_reports"><title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
-    </para>
-  </refsection>
-</refentry>
-
-<!-- vim: set shiftwidth=2 : -->
@@ -97,7 +97,7 @@ to avoid having to create a font converter.</para>
 </refsection>

 <refsection xml:id="example"><title>EXAMPLE</title>
-<para>fblabel -f "oldenglish.14" `fbpoint -H` "Hello"</para>
+<para>fblabel -f "oldenglish.14" `fbpoint -h` "Hello"</para>
 </refsection>

 <refsection xml:id="see_also"><title>SEE ALSO</title>
@@ -1,143 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='gstl1'>
-  <refmeta>
-    <refentrytitle>G-PLY
-    </refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo class='source'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='software'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='manual'>User Commands</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname>g-ply</refname>
-    <refpurpose> Stanford PLY exporter (BRL-CAD to PLY)</refpurpose>
-  </refnamediv>
-  <!-- body begins here -->
-  <refsynopsisdiv xml:id='synopsis'>
-    <cmdsynopsis>
-      <command>g-ply</command>
-      <arg choice='opt'>-v</arg>
-      <arg choice='opt'>-xX <replaceable>lvl</replaceable></arg>
-      <arg choice='opt'>-a <replaceable>abs_tess_tol</replaceable></arg>
-      <arg choice='opt'>-r <replaceable>rel_tess_tol</replaceable></arg>
-      <arg choice='opt'>-n <replaceable>norm_tess_tol</replaceable></arg>
-      <arg choice='opt'>-t <replaceable>type</replaceable></arg>
-      <arg choice='opt'>-s</arg>
-      <arg choice='opt'>-D <replaceable>dist_calc_tol</replaceable></arg>
-      <arg choice='plain'>-o <replaceable>output_file_name</replaceable></arg>
-      <arg choice='plain'><replaceable>database.g</replaceable></arg>
-      <arg choice='plain' rep='repeat'><replaceable>object(s)</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-
-  <refsect1 xml:id='description'><title>DESCRIPTION</title>
-  <para>
-    <command>g-ply</command> converts the specified<emphasis remap='I'>object(s)</emphasis>
-    from a BRL-CAD <emphasis remap='I'>database.g</emphasis> file to the
-    <emphasis remap='I'>Stanfort PLY</emphasis> file format.
-  </para>
-
-  <para>The following options are recognized.</para>
-  <variablelist remap='TP'>
-    
-    <varlistentry>
-      <term><option>-o filename</option></term>
-      <listitem><para>Specify output file name.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-	<para>
-	  Write out one object per file, instead of merging individual objects into a single ply file.
-	</para>
-      </listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-t</option> type (asc: ascii), (le: little endian), (be: big endian)</term>
-      <listitem>
-	<para>
-	  Specify the type of PLY file to write.
-	</para>
-      </listitem>
-    </varlistentry>
-    
-    
-    <varlistentry>
-      <term><option>-D#</option></term>
-      <listitem>
-	<para>Specify a calculational distance tolerance (mm). Any two vertices that are
-	less than this distance apart will be treated as the same vertex.</para>
-      </listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-a#</option></term>
-      <listitem><para>Specify the absolute tesselation tolerance.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-r#</option></term>
-      <listitem><para>Specify the relative tesselation tolerance.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-n#</option></term>
-      <listitem><para>Specify the surface-normal tesselation tolerance.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-x#</option></term>
-      <listitem><para>Specify an RT debug flag.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-X#</option></term>
-      <listitem><para>Specify an NMG debug flag.</para></listitem>
-    </varlistentry>
-    
-    <varlistentry>
-      <term><option>-v</option></term>
-      <listitem><para>Enable verbose output.</para></listitem>
-    </varlistentry>
-    
-  </variablelist>
-  </refsect1>
-
-  <refsect1 xml:id='example'>
-    <title>EXAMPLE</title>
-    <synopsis>
-      $ g-ply -o <emphasis remap='I'>sample.ply sample.g sample_object</emphasis>
-    </synopsis>
-  </refsect1>
-
-  <refsect1 xml:id='diagnostics'>
-    <title>DIAGNOSTICS</title>
-    <para>Error messages are intended to be self-explanatory.</para>
-  </refsect1>
-
-  <refsect1 xml:id='author'>
-    <title>AUTHOR</title>
-    <para>BRL-CAD Team</para>
-  </refsect1>
-
-  <refsect1 xml:id='copyright'>
-    <title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 2003-2016 by the United States
-      Government as represented by U.S. Army Research Laboratory.
-    </para>
-  </refsect1>
-
-  <refsect1 xml:id='bug_reports'>
-    <title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;.
-    </para>
-  </refsect1>
-</refentry>
-
@@ -0,0 +1,91 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- lifted from troff+man by doclifter -->
+<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='g_diff1'>
+<refmeta>
+    <refentrytitle>G_DIFF
+</refentrytitle>
+<manvolnum>1</manvolnum>
+<refmiscinfo class='source'>BRL-CAD</refmiscinfo>
+<refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
+</refmeta>
+
+<refnamediv>
+<refname>g_diff</refname>
+<refpurpose>a BRL-CAD differential geometry comparator</refpurpose>
+</refnamediv>
+<!-- body begins here -->
+<refsynopsisdiv xml:id='synopsis'>
+<cmdsynopsis>
+  <command>g_diff</command><arg choice='opt'>-m </arg>
+    <arg choice='opt'>-f </arg>
+    <arg choice='opt'>-v </arg>
+    <arg choice='plain'><replaceable>model1.g</replaceable></arg>
+    <arg choice='plain'><replaceable>model2.g</replaceable></arg>
+</cmdsynopsis>
+</refsynopsisdiv>
+
+
+<refsect1 xml:id='description'><title>DESCRIPTION</title>
+<para><command>g_diff</command>
+compares the two BRL-CAD models specified on the command line. The results of this comparison
+are written to standard out in a human readable form describing the changes from model1 to model2.
+If the
+<option>-m</option>
+option is exercised, the output will be a script, readable by <command>mged(1)</command>, that will perform the
+necessary changes to model1 to make it a copy of model2. The produced script makes extensive use
+of the
+<emphasis remap='I'>db get</emphasis>,
+<emphasis remap='I'>db put</emphasis>,
+and
+<emphasis remap='I'>db adjust</emphasis>
+commands in <command>mged(1)</command>. A few solid types are not supported by these commands, and changes involving these
+solids are merely noted (the script will not actually be capable of performing all the changes in this case).
+The
+<option>-e</option>
+option selections evolutionary mode, which attempts to guess if a change in a region is due to an evolutionary change or a reworking.
+The output is similar to -m, but it is NOT mged readable.
+The
+<option>-f</option>
+option requests that all floating point numerical comparisons be done in single precision rather
+than the default double precision. This may be useful when comparing different format databases.
+The
+<option>-v</option>
+option requests that the default attributes of each region in both files be checked for
+consistency. Any inconsistencies are written to stderr.</para>
+
+<para>The program returns 0 if the files being compared have no differences and non-zero otherwise.</para>
+</refsect1>
+
+<refsect1 xml:id='example'><title>EXAMPLE</title>
+<para>The command</para>
+
+<!-- .in +5 -->
+<para>g_diff -m uncle.g aunt.g &gt; mged.script</para>
+<!-- .in &bsol;-5 -->
+
+<para>will create a file named "mged.script" that may be sourced in <command>mged(1)</command> to change
+uncle.g into aunt.g .</para>
+</refsect1>
+
+<refsect1 xml:id='see_also'><title>SEE ALSO</title>
+<para><citerefentry><refentrytitle>mged</refentrytitle><manvolnum>1</manvolnum></citerefentry></para>
+
+</refsect1>
+
+<refsect1 xml:id='author'><title>AUTHOR</title>
+<para>BRL-CAD Team</para>
+
+</refsect1>
+
+<refsect1 xml:id='copyright'><title>COPYRIGHT</title>
+<para>This software is Copyright (c) 1999-2016 by the United States
+Government as represented by U.S. Army Research Laboratory.</para>
+
+</refsect1>
+
+<refsect1 xml:id='bug_reports'><title>BUG REPORTS</title>
+<para>Reports of bugs or problems should be submitted via electronic
+mail to &lt;devs@brlcad.org&gt;.</para>
+</refsect1>
+</refentry>
+
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <!-- lifted from troff+man by doclifter -->
-<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='glint1'>
+<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='g_lint1'>
 <refmeta>
    <refentrytitle>G_LINT
 </refentrytitle>
@@ -10,13 +10,13 @@
 </refmeta>

 <refnamediv>
-<refname>glint</refname>
+<refname>g_lint</refname>
 <refpurpose>a BRL-CAD geometry checker</refpurpose>
 </refnamediv>
 <!-- body begins here -->
 <refsynopsisdiv xml:id='synopsis'>
 <cmdsynopsis>
-  <command>glint</command>    <arg choice='opt'><replaceable>options</replaceable></arg>
+  <command>g_lint</command>    <arg choice='opt'><replaceable>options</replaceable></arg>
    <arg choice='plain'><replaceable>model.g</replaceable></arg>
    <arg choice='plain' rep='repeat'><replaceable>objects</replaceable></arg>

@@ -25,7 +25,7 @@


 <refsect1 xml:id='description'><title>DESCRIPTION</title>
-<para><command>glint</command>
+<para><command>g_lint</command>
 uses
 <citerefentry><refentrytitle>librt</refentrytitle><manvolnum>3</manvolnum></citerefentry>
 to fire an array of parallel rays
@@ -144,7 +144,7 @@ The default is 0.</para>
  <listitem>
 <para>Specifies that one ray should be fired from the center of each grid cell.
 By default,
-<command>glint</command>
+<command>g_lint</command>
 fires a ray from one random point in each cell.</para>
  </listitem>
  </varlistentry>
@@ -170,7 +170,7 @@ The default is 100 mm.</para>
  <term><option>-o</option></term>
  <listitem>
 <para>Causes
-<command>glint</command>
+<command>g_lint</command>
 to include in each report
 the model coordinates of the ray origination point.
 These appear between the tag and the rest of the data.</para>
@@ -180,7 +180,7 @@ These appear between the tag and the rest of the data.</para>
  <term><option>-p</option></term>
  <listitem>
 <para>Causes
-<command>glint</command>
+<command>g_lint</command>
 to produce its reports as
 <emphasis remap='I'>plot3(5)</emphasis>
 drawing commands instead of ASCII text.
@@ -238,14 +238,14 @@ The default is 1.</para>
  <term><option>-s</option></term>
  <listitem>
 <para>Causes
-<command>glint</command>
+<command>g_lint</command>
 to collect all the overlap reports and sort them before printing them.
 The reports for a given pair of regions
 are printed contiguously,
 and the clusters of reports for the various pairs of regions
 appear in order of decreasing cumulative overlap length.
 By default,
-<command>glint</command>
+<command>g_lint</command>
 reports overlaps immediately and in the order of their discovery.</para>
  </listitem>
  </varlistentry>
@@ -281,7 +281,7 @@ ignores air regions.</para>
  <term><option>-x</option><replaceable> bits</replaceable></term>
  <listitem>
 <para>Sets the
-<command>glint</command>
+<command>g_lint</command>
 debug flags to
 <emphasis remap='I'>bits</emphasis>.
 See the
@@ -299,7 +299,7 @@ Note that some of the report types have no corresponding diagnostics.</para>
 <para>The command</para>

 <!-- .in +5 -->
-<para>glint -a 35 -e 25 -c -g 1 -r 31 -t 0.01 <emphasis remap='I'>kitchen.g appliances</emphasis></para>
+<para>g_lint -a 35 -e 25 -c -g 1 -r 31 -t 0.01 <emphasis remap='I'>kitchen.g appliances</emphasis></para>
 <!-- .in &bsol;-5 -->

 <para>fires a ray every millimeter and produces overlap reports
@@ -1,100 +1,100 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 <refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='gdiff1'>
-  <refmeta>
-    <refentrytitle>GDIFF
-    </refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo class='source'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
-  </refmeta>
+	<refmeta>
+		<refentrytitle>GDIFF
+		</refentrytitle>
+		<manvolnum>1</manvolnum>
+		<refmiscinfo class='source'>BRL-CAD</refmiscinfo>
+		<refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
+	</refmeta>

-  <refnamediv>
-    <refname>gdiff</refname>
-    <refpurpose>a BRL-CAD differential geometry comparator</refpurpose>
-  </refnamediv>
-  <!-- body begins here -->
-  <refsynopsisdiv xml:id='synopsis'>
-    <cmdsynopsis>
-      <command>gdiff</command>
-      <arg choice="opt" rep="repeat"><replaceable>options</replaceable></arg>
-      <arg choice='plain'><replaceable>left_model.g</replaceable></arg>
-      <arg choice='opt'><replaceable>ancestor_model.g</replaceable></arg>
-      <arg choice='plain'><replaceable>right_model.g</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
+	<refnamediv>
+		<refname>gdiff</refname>
+		<refpurpose>a BRL-CAD differential geometry comparator</refpurpose>
+	</refnamediv>
+	<!-- body begins here -->
+	<refsynopsisdiv xml:id='synopsis'>
+		<cmdsynopsis>
+			<command>gdiff</command>
+			<arg choice="opt" rep="repeat"><replaceable>options</replaceable></arg>
+			<arg choice='plain'><replaceable>left_model.g</replaceable></arg>
+			<arg choice='opt'><replaceable>ancestor_model.g</replaceable></arg>
+			<arg choice='plain'><replaceable>right_model.g</replaceable></arg>
+		</cmdsynopsis>
+	</refsynopsisdiv>


-  <refsect1 xml:id='description'><title>DESCRIPTION</title>
-  <para>
-    <command>gdiff</command> compares BRL-CAD models
-    specified on the command line, reporting differences according to the
-    specified options.  It supports a plain "diff" comparison between two
-    files, as well as a "3-way" comparison that accepts a third file with
-    "ancestral" information that provides a context for the left and right
-    files.
-  </para>
-  <para>The following options are recognized:</para>
-  <variablelist remap="TP">
-    <varlistentry>
-      <term><option>-a</option></term>
-      <listitem>
-        <para>(two-way diff) Report objects added in right_model.g</para>
-	<para>(three-way diff) Report objects added in left_model.g and/or right_model.g</para>
-      </listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-d</option></term>
-      <listitem>
-        <para>(two-way diff) Report objects deleted in right_model.g</para>
-	<para>(three-way diff) Report objects deleted in left_model.g and/or right_model.g</para>
-      </listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-m</option></term>
-      <listitem>
-        <para>(two-way diff) Report objects modified in right_model.g</para>
-	<para>(three-way diff) Report objects that are different in left_model.g and/or right_model.g relative to ancestor.g</para>
-      </listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-u</option></term>
-      <listitem>
-        <para>(two-way diff) Report objects that are identical in left_model.g and right_model.g</para>
-        <para>(three-way diff) Report objects that are identical in ancestor_model.g, left_model.g and right_model.g</para>
-      </listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-v #</option></term>
-      <listitem><para>Control the verbosity of the output.  Zero will suppress all reporting and only the return value of the program will contain information, one will provide categorized lists of objects but no details on what changed, two will list each changed object preceded by a modifier, three will print more details for changed objects, and four will print all available information.  All settings for this option will respect other constraints applied to the reporting output.</para></listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-t #</option></term>
-      <listitem><para>Set a numerical comparison tolerance used to compare numerical properties.  Default value is RT_LEN_TOL, but be aware that this comparison is not aware of units.</para></listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-F "filter_string"</option></term>
-      <listitem><para>Apply filters to the diff output, using the same set of filters available in the <command>search</command> command's search.  See the <command>search</command> manual page for more details.</para></listitem>
-    </varlistentry>
-    <varlistentry>
-      <term><option>-M merged_file.g</option></term>
-      <listitem><para>Merge the files being diffed into one output file.</para></listitem>
-    </varlistentry>
-  </variablelist>
+	<refsect1 xml:id='description'><title>DESCRIPTION</title>
+		<para>
+			<command>gdiff</command> compares BRL-CAD models
+			specified on the command line, reporting differences according to the
+			specified options.  It supports a plain "diff" comparison between two
+			files, as well as a "3-way" comparison that accepts a third file with
+			"ancestral" information that provides a context for the left and right
+			files.
+		</para>
+		<para>The following options are recognized:</para>
+		<variablelist remap="TP">
+			<varlistentry>
+				<term><option>-a</option></term>
+				<listitem>
+                                    <para>(two-way diff) Report objects added in right_model.g</para>
+				    <para>(three-way diff) Report objects added in left_model.g and/or right_model.g</para>
+                                </listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-d</option></term>
+	                        <listitem>
+                                    <para>(two-way diff) Report objects deleted in right_model.g</para>
+				    <para>(three-way diff) Report objects deleted in left_model.g and/or right_model.g</para>
+                                </listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-m</option></term>
+	                        <listitem>
+                                    <para>(two-way diff) Report objects modified in right_model.g</para>
+				    <para>(three-way diff) Report objects that are different in left_model.g and/or right_model.g relative to ancestor.g</para>
+                                </listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-u</option></term>
+	                        <listitem>
+                                    <para>(two-way diff) Report objects that are identical in left_model.g and right_model.g</para>
+                                    <para>(three-way diff) Report objects that are identical in ancestor_model.g, left_model.g and right_model.g</para>
+                                </listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-v #</option></term>
+				<listitem><para>Control the verbosity of the output.  Zero will suppress all reporting and only the return value of the program will contain information, one will provide categorized lists of objects but no details on what changed, two will list each changed object preceded by a modifier, three will print more details for changed objects, and four will print all available information.  All settings for this option will respect other constraints applied to the reporting output.</para></listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-t #</option></term>
+				<listitem><para>Set the length tolerance used to compare numerical properties.  Units are millimeters.  Default value is RT_LEN_TOL.</para></listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-F "filter_string"</option></term>
+				<listitem><para>Apply filters to the diff output, using the same set of filters available in the <command>search</command> command's search.  See the <command>search</command> manual page for more details.</para></listitem>
+			</varlistentry>
+			<varlistentry>
+				<term><option>-M merged_file.g</option></term>
+				<listitem><para>Merge the files being diffed into one output file.</para></listitem>
+			</varlistentry>
+		</variablelist>

-  <para>
-    The program returns 0 if the files being compared have no differences that satisfy
-    the user-supplied options, otherwise it returns the total number of differing objects that do
-    satisfy the supplied options.  Default is to report all differences that rise above RT_LEN_TOL.
-  </para>
-  </refsect1>
+		<para>
+			The program returns 0 if the files being compared have no differences that satisfy
+			the user-supplied options, otherwise it returns the total number of differing objects that do
+			satisfy the supplied options.  Default is to report all differences that rise above RT_LEN_TOL.
+		</para>
+	</refsect1>

-  <refsect1 xml:id='example'><title>EXAMPLES</title>
+	<refsect1 xml:id='example'><title>EXAMPLES</title>

  <example><title>Default Diffing Results</title>
-  <para>
-    Running the default options on two pre-prepared examples of Moss World gives us a summary of the status of various objects:
-    <literallayout>
-      <computeroutput>
+        <para>
+          Running the default options on two pre-prepared examples of Moss World gives us a summary of the status of various objects:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff moss.g moss2.g</userinput>
 M platform.r
 M ellipse.s
@@ -107,29 +107,29 @@ M tor.r
 D LIGHT
 A tgc_new.s
 A eto.s
-      </computeroutput>
-    </literallayout>
-    'M' denotes an object that was modified, 'D' is an object that was deleted, and 'A' is an object that was added.
-  </para>
-  </example>
+		</computeroutput>
+          </literallayout>
+          'M' denotes an object that was modified, 'D' is an object that was deleted, and 'A' is an object that was added.
+        </para>
+   </example>

-  <example><title>Alternate Diffing Result Outputs</title>
-  <para>
-    The <option>v</option> provides various styles of output, as follows:
-  </para>
-  <para>
-    <option>-v 0</option> (no output except the return code):
-    <literallayout>
-      <computeroutput>
-	<prompt>~:</prompt><userinput> gdiff -v 0 moss.g moss2.g</userinput>
-      </computeroutput>
-    </literallayout>
-  </para>
+   <example><title>Alternate Diffing Result Outputs</title>
+	   <para>
+		   The <option>v</option> provides various styles of output, as follows:
+	   </para>
+	   <para>
+		   <option>-v 0</option> (no output except the return code):
+		   <literallayout>
+			   <computeroutput>
+<prompt>~:</prompt><userinput> gdiff -v 0 moss.g moss2.g</userinput>
+			   </computeroutput>
+		   </literallayout>
+	   </para>

-  <para>
-    <option>-v 1</option>:
-    <literallayout>
-      <computeroutput>
+	   <para>
+		   <option>-v 1</option>:
+		   <literallayout>
+			   <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 1 moss.g moss2.g</userinput>
 Added:
 tgc_new.s, eto.s
@@ -139,15 +139,15 @@ LIGHT

 Changed:
 platform.r, ellipse.s, light.r, _GLOBAL, cone.s, cone.r, box.s, tor.r
-      </computeroutput>
-    </literallayout>
-    Objects are reported in lists, categorized by their status.
-  </para>
+			   </computeroutput>
+		   </literallayout>
+		   Objects are reported in lists, categorized by their status.
+	   </para>

-  <para>
-    <option>-v 2</option> (default):
-    <literallayout>
-      <computeroutput>
+	   <para>
+		   <option>-v 2</option> (default):
+		   <literallayout>
+			   <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 2 moss.g moss2.g</userinput>
 M platform.r
 M ellipse.s
@@ -160,15 +160,15 @@ M tor.r
 D LIGHT
 A tgc_new.s
 A eto.s
-      </computeroutput>
-    </literallayout>
-    If verbosity is not specified, this is the default output.
-  </para>
+			   </computeroutput>
+		   </literallayout>
+		   If verbosity is not specified, this is the default output.
+	   </para>

-  <para>
-    <option>-v 3</option>:
-    <literallayout>
-      <computeroutput>
+	   <para>
+		   <option>-v 3</option>:
+		   <literallayout>
+			   <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 3 moss.g moss2.g</userinput>
 - "platform.r" tree(p): l platform.s
 + "platform.r" tree(p): - {l platform.s} {l cone.s}
@@ -199,17 +199,17 @@ A eto.s
 D LIGHT
 A tgc_new.s
 A eto.s
-      </computeroutput>
-    </literallayout>
-    Verbosity 3 is a more detailed version of the previous setting, with each parameter in the modified objects reported in detail.  '-' lines
-    show what was removed for a given attribute or parameter, and '+' lines contain the data that replaced them.
-  </para>
+			   </computeroutput>
+		   </literallayout>
+		   Verbosity 3 is a more detailed version of the previous setting, with each parameter in the modified objects reported in detail.  '-' lines
+                   show what was removed for a given attribute or parameter, and '+' lines contain the data that replaced them.
+	   </para>


-  <para>
-    <option>-v 4</option>:
-    <literallayout>
-      <computeroutput>
+	   <para>
+		   <option>-v 4</option>:
+		   <literallayout>
+			   <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 4 moss.g moss2.g</userinput>
 - "platform.r" tree(p): l platform.s
 + "platform.r" tree(p): - {l platform.s} {l cone.s}
@@ -255,70 +255,70 @@ A "eto.s" C(p): 3.448298656000062134552309 0 3.448298656000062134552309
 A "eto.s" N(p): 0 0 0.01724149328000028000285049
 A "eto.s" V(p): 8.533195938359670051909234 -11.04524849332910996224655 -1.403988582132086548881489
 A "eto.s" DB5_MINORTYPE(p): eto
-      </computeroutput>
-    </literallayout>
-    Verbosity 4 is a fully detailed diff that contains all information added or removed.
-  </para>
+			   </computeroutput>
+		   </literallayout>
+		   Verbosity 4 is a fully detailed diff that contains all information added or removed.
+	   </para>

-</example>
+   </example>


-<example><title>Filtering Based on Difference Type</title>
-<para>
-  The options <option>a</option>, <option>d</option>, <option>m</option>, and <option>u</option> control
-  which categories of diff results (added, deleted, modified, and unchanged) are reported. By default
-  added, deleted and modified items are reported, but once one of these four options is specified only
-  those specified are reported:
-</para>
-<para>
-  Report only objects added:
-  <literallayout>
-    <computeroutput>
+  <example><title>Filtering Based on Difference Type</title>
+        <para>
+          The options <option>a</option>, <option>d</option>, <option>m</option>, and <option>u</option> control
+          which categories of diff results (added, deleted, modified, and unchanged) are reported. By default
+          added, deleted and modified items are reported, but once one of these four options is specified only
+          those specified are reported:
+        </para>
+        <para>
+          Report only objects added:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -a moss.g moss2.g</userinput>
 A tgc_new.s
 A eto.s
-    </computeroutput>
-  </literallayout>
-</para>
-<para>
-  Report only objects deleted:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+        </para>
+        <para>
+          Report only objects deleted:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -d moss.g moss2.g</userinput>
 D LIGHT
-    </computeroutput>
-  </literallayout>
-</para>
-<para>
-  Report both added and deleted objects, but not modified objects:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+        </para>
+        <para>
+          Report both added and deleted objects, but not modified objects:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -a -d moss.g moss2.g</userinput>
 D LIGHT
 A tgc_new.s
 A eto.s
-    </computeroutput>
-  </literallayout>
-</para>
-<para>
-  Report unmodified objects:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+        </para>
+        <para>
+          Report unmodified objects:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -u moss.g moss2.g</userinput>
-ellipse.r
-box.r
-all.g
-    </computeroutput>
-  </literallayout>
-</para>
-</example>
+  ellipse.r
+  box.r
+  all.g
+                </computeroutput>
+          </literallayout>
+        </para>
+  </example>

-<example><title>Filtering Results With Tolerance</title>
-<para>
-  To eliminate differences in modifications that are too small to be of interest, the <option>t</option> is used.  What
-  difference constitutes "too small" is up to the user - in this example, we will use 30 millimeters:
-  <literallayout>
-    <computeroutput>
+  <example><title>Filtering Results With Tolerance</title>
+        <para>
+          To eliminate differences in modifications that are too small to be of interest, the <option>t</option> is used.  What
+          difference constitutes "too small" is up to the user - in this example, we will use 30 millimeters:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 3 -t 30.0 moss.g moss2.g</userinput>
 - "platform.r" tree(p): l platform.s
 + "platform.r" tree(p): - {l platform.s} {l cone.s}
@@ -335,30 +335,30 @@ all.g
 D LIGHT
 A tgc_new.s
 A eto.s
-    </computeroutput>
-  </literallayout>
-  Notice that ellipse.s, which was on earlier lists, is now filtered out.  cone.s has a difference in the x coordinates
-  of the parameter V that is large enough to satisfy the tolerance filter, so that parameter stays in.  Parameters that
-  are not strictly numerical comparisons, or those that are part of added or deleted objects, remain in the report.
-</para>
-</example>
+		</computeroutput>
+	</literallayout>
+	Notice that ellipse.s, which was on earlier lists, is now filtered out.  cone.s has a difference in the x coordinates
+	of the parameter V that is large enough to satisfy the tolerance filter, so that parameter stays in.  Parameters that
+	are not strictly numerical comparisons, or those that are part of added or deleted objects, remain in the report.
+        </para>
+  </example>


-<example><title>Filtering Results With Search Filters</title>
-<para>
-  The <emphasis>search</emphasis> filtering technique can be used to select specific subsets of the database to see
-  in reports, using the <option>F</option> option.  For example, limiting the diff report to only objects of type elliptical torus:
-  <literallayout>
-    <computeroutput>
+  <example><title>Filtering Results With Search Filters</title>
+        <para>
+          The <emphasis>search</emphasis> filtering technique can be used to select specific subsets of the database to see
+          in reports, using the <option>F</option> option.  For example, limiting the diff report to only objects of type elliptical torus:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -F "-type eto" moss.g moss2.g</userinput>
 A eto.s
-    </computeroutput>
-  </literallayout>
-</para>
-<para>
-  Note that this option will work at all levels of verbosity:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+        </para>
+        <para>
+          Note that this option will work at all levels of verbosity:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 4 -F "-type eto" moss.g moss2.g</userinput>
 A "eto.s" r_d(p): 1.724149328000026404339451
 A "eto.s" r(p): 13.79319462400021123471561
@@ -366,17 +366,17 @@ A "eto.s" C(p): 3.448298656000062134552309 0 3.448298656000062134552309
 A "eto.s" N(p): 0 0 0.01724149328000028000285049
 A "eto.s" V(p): 8.533195938359670051909234 -11.04524849332910996224655 -1.403988582132086548881489
 A "eto.s" DB5_MINORTYPE(p): eto
-    </computeroutput>
-  </literallayout>
-</para>
-</example>
+                </computeroutput>
+          </literallayout>
+        </para>
+  </example>

-<example><title>Combining Multiple Filters</title>
-<para>
-  The various diff filters can be used together.  For example, repeating the search
-  filter with ell types added to the accepted list produces the following:
-  <literallayout>
-    <computeroutput>
+  <example><title>Combining Multiple Filters</title>
+        <para>
+          The various diff filters can be used together.  For example, repeating the search
+          filter with ell types added to the accepted list produces the following:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 4 -F "-type eto -or -type ell" moss.g moss2.g</userinput>
 - "ellipse.s" C(p): 0 8.980256080627000869753829 8.980256080627000869753829
 + "ellipse.s" C(p): 0 1.561016355403846755933728 1.561016355403846755933728
@@ -393,13 +393,13 @@ A "eto.s" C(p): 3.448298656000062134552309 0 3.448298656000062134552309
 A "eto.s" N(p): 0 0 0.01724149328000028000285049
 A "eto.s" V(p): 8.533195938359670051909234 -11.04524849332910996224655 -1.403988582132086548881489
 A "eto.s" DB5_MINORTYPE(p): eto
-    </computeroutput>
-  </literallayout>
-</para>
-<para>
-  If we now add the tolerance filter, we see ellipse.s is filtered out:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+        </para>
+        <para>
+          If we now add the tolerance filter, we see ellipse.s is filtered out:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 4 -t 30.0 -F "-type eto -or -type ell" moss.g moss2.g</userinput>
 D "LIGHT" C(p): 0 0 2.539999961852999810218989
 D "LIGHT" B(p): 0 2.539999961852999810218989 0
@@ -412,23 +412,23 @@ A "eto.s" C(p): 3.448298656000062134552309 0 3.448298656000062134552309
 A "eto.s" N(p): 0 0 0.01724149328000028000285049
 A "eto.s" V(p): 8.533195938359670051909234 -11.04524849332910996224655 -1.403988582132086548881489
 A "eto.s" DB5_MINORTYPE(p): eto
-    </computeroutput>
-  </literallayout>
-  ellipse.s satisfies the search filter, but is filtered by virtue of having no differences larger than 30 in its parameters.
-</para>
+                </computeroutput>
+          </literallayout>
+          ellipse.s satisfies the search filter, but is filtered by virtue of having no differences larger than 30 in its parameters.
+        </para>

-</example>
+  </example>

-<example><title>Three Way Differences</title>
-<para>
-  A "3-way" diff uses an ancestor file as a basis for evaluating the differences between two
-  other files.  This ancestor provides a "context" in which it is possible to tell whether a
-  difference between two files is a) the product of a change in one but not the other in
-  comparison to the original or b) whether both have (incompatibly) changed in comparison
-  to the original.  For example, if we compare moss2.g from the previous examples to a new
-  file moss3.g:
-  <literallayout>
-    <computeroutput>
+  <example><title>Three Way Differences</title>
+        <para>
+          A "3-way" diff uses an ancestor file as a basis for evaluating the differences between two
+	  other files.  This ancestor provides a "context" in which it is possible to tell whether a
+          difference between two files is a) the product of a change in one but not the other in
+          comparison to the original or b) whether both have (incompatibly) changed in comparison
+          to the original.  For example, if we compare moss2.g from the previous examples to a new
+          file moss3.g:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff moss2.g moss3.g</userinput>
 M platform.r
 M ellipse.s
@@ -444,12 +444,12 @@ M all.g
 M tor
 A ellipse2.r
 A LIGHT
-    </computeroutput>
-  </literallayout>
-  All we can tell is that these objects differ from each other.  If, however, we add moss.g
-  to the comparison as an ancestor file:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+          All we can tell is that these objects differ from each other.  If, however, we add moss.g
+          to the comparison as an ancestor file:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff moss2.g moss.g moss3.g</userinput>
 M platform.r
 M ellipse.s
@@ -466,17 +466,17 @@ M tor
 A(B) tgc_new.s
 C eto.s
 A(R) ellipse2.r
-    </computeroutput>
-  </literallayout>
-  We can now see that ellipse.r was deleted only from the right file (moss3.g) and was unchanged in moss2.g.
-  Similarly, we can tell that LIGHT wsa deleted from moss2.g, ellipse2.r was added in moss3.g, tgc_new.s was
-  added identically in both moss2.g and moss3.g, and eto.s is different in moss2.g and moss3.g in some fashion
-  that the ancestor file moss.g cannot help gdiff resolve (a conflict, denoted by 'C'.)
-</para>
-<para>
-  To delve deeper into the nature of the changes, we increase the verbosity with the <option>v</option> option:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+          We can now see that ellipse.r was deleted only from the right file (moss3.g) and was unchanged in moss2.g.
+          Similarly, we can tell that LIGHT wsa deleted from moss2.g, ellipse2.r was added in moss3.g, tgc_new.s was
+          added identically in both moss2.g and moss3.g, and eto.s is different in moss2.g and moss3.g in some fashion
+          that the ancestor file moss.g cannot help gdiff resolve (a conflict, denoted by 'C'.)
+        </para>
+        <para>
+          To delve deeper into the nature of the changes, we increase the verbosity with the <option>v</option> option:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v 3 moss2.g moss.g moss3.g</userinput>
 M(L) "platform.r" tree(p): - {l platform.s} {l cone.s}
 M(L) "ellipse.s" C(p): 0 1.561016355403846755933728 1.561016355403846755933728
@@ -502,64 +502,64 @@ M(R) "tor" r_a(p): 30.18139425891995841766402
 A(B) tgc_new.s
 C(LA!=RA) eto.s
 A(R) ellipse2.r
-    </computeroutput>
-  </literallayout>
-  At this level of verbosity, we can now see that most of the modifications are from the left (moss2.g) file.  M(L) denotes
-  a change that is present only in the left file - the right (moss3.g) agrees with the ancestor.  Similarly, we can now see
-  that the deletion of ellipse.r, the addition of ellipse2.r and the change to all.g come from moss3.g.  The conflict
-  on eto.s is that two add operations (one in moss2.g, one in moss3.g) produced different eto.s primitives - there is no
-  ancestor for eto.s in moss.g, so there is no way to identify one of the eto.s primitives as "correct" - they have equal
-  standing, and manual intervention is needed to determine which eto.s is the "correct" version.
-</para>
-</example>
+                </computeroutput>
+          </literallayout>
+          At this level of verbosity, we can now see that most of the modifications are from the left (moss2.g) file.  M(L) denotes
+          a change that is present only in the left file - the right (moss3.g) agrees with the ancestor.  Similarly, we can now see
+          that the deletion of ellipse.r, the addition of ellipse2.r and the change to all.g come from moss3.g.  The conflict
+          on eto.s is that two add operations (one in moss2.g, one in moss3.g) produced different eto.s primitives - there is no
+          ancestor for eto.s in moss.g, so there is no way to identify one of the eto.s primitives as "correct" - they have equal
+          standing, and manual intervention is needed to determine which eto.s is the "correct" version.
+        </para>
+  </example>


-<example><title>Complex Three Way Differences</title>
-<para>
-  Conflicts can arise from situations other than incompatible additions - an incompatible modification
-  is also enough to trigger a conflict.  Consider three ellipsoids, one of which is an ancestor, one of
-  which has had its A and B vectors modified, and the other of which has had its B and C vectors modified.
-  A three-way diff of these files reports a conflict:
-  <literallayout>
-    <computeroutput>
+  <example><title>Complex Three Way Differences</title>
+        <para>
+          Conflicts can arise from situations other than incompatible additions - an incompatible modification
+          is also enough to trigger a conflict.  Consider three ellipsoids, one of which is an ancestor, one of
+          which has had its A and B vectors modified, and the other of which has had its B and C vectors modified.
+          A three-way diff of these files reports a conflict:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff ell_1.g ell_0.g ell_2.g</userinput>
 C ell.s
-    </computeroutput>
-  </literallayout>
+                </computeroutput>
+          </literallayout>

-  However, closer inspection reveals that this conflict is different than the one reported above for the eto.s object:
-  <literallayout>
-    <computeroutput>
+          However, closer inspection reveals that this conflict is different than the one reported above for the eto.s object:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v3 ell_1.g ell_0.g ell_2.g</userinput>
 C(LM!=RM) ell.s
-    </computeroutput>
-  </literallayout>
-  This notation indicates that a modification in the left side (ell_1.g) does not match a modification made in ell_2.g.
-  Unlike the eto.s, which reported an add conflict, this is a modification conflict triggered by incompatible, different
-  parameters.  Indeed a full verbosity inspection:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+          This notation indicates that a modification in the left side (ell_1.g) does not match a modification made in ell_2.g.
+          Unlike the eto.s, which reported an add conflict, this is a modification conflict triggered by incompatible, different
+          parameters.  Indeed a full verbosity inspection:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -v4 ell_1.g ell_0.g ell_2.g</userinput>
 M(R) "ell.s" C(p): 0 0 300
 C(A) "ell.s" B(p): 0 500 0
 C(L) "ell.s" B(p): 0 510 0
 C(R) "ell.s" B(p): 0 300 0
 M(L) "ell.s" A(p): 1100 0 0
-    </computeroutput>
-  </literallayout>
-  reveals that the changes to the A and C parameters are <emphasis>not</emphasis> in conflict - it is the B parameter that
-  is causing the problem.
-</para>
-</example>
+                </computeroutput>
+          </literallayout>
+          reveals that the changes to the A and C parameters are <emphasis>not</emphasis> in conflict - it is the B parameter that
+          is causing the problem.
+        </para>
+  </example>

-<example><title>Merging Files</title>
-<para>
-  The last and most powerful feature of <command>gdiff</command> is to <emphasis>merge</emphasis> two or three different
-  geometry files into a single output file.  This is most useful when an ancestor is available and a three way merge can
-  be performed - in the two way case, the "ancestor" is an empty file and the results will tend to include many more
-  conflicts.  For example, the three way merge of the moss examples earlier:
-  <literallayout>
-    <computeroutput>
+  <example><title>Merging Files</title>
+        <para>
+          The last and most powerful feature of <command>gdiff</command> is to <emphasis>merge</emphasis> two or three different
+          geometry files into a single output file.  This is most useful when an ancestor is available and a three way merge can
+          be performed - in the two way case, the "ancestor" is an empty file and the results will tend to include many more
+          conflicts.  For example, the three way merge of the moss examples earlier:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -M moss_merged.g moss2.g moss0.g moss3.g</userinput>
 M platform.r
 M ellipse.s
@@ -583,12 +583,12 @@ CONFLICT(eto.s).right    cone.s                   platform.s
 all.g/                   ellipse.s                tgc_new.s
 box.r/R                  ellipse2.r/R             tor
 box.s                    light.r/R                tor.r/R
-    </computeroutput>
-  </literallayout>
-  The resulting file has only two conflict objects present - the same eto.s issue that was discussed earlier.  Trying to
-  do the same merge <emphasis>without</emphasis> the ancestor file:
-  <literallayout>
-    <computeroutput>
+                </computeroutput>
+          </literallayout>
+          The resulting file has only two conflict objects present - the same eto.s issue that was discussed earlier.  Trying to
+          do the same merge <emphasis>without</emphasis> the ancestor file:
+          <literallayout>
+                <computeroutput>
 <prompt>~:</prompt><userinput> gdiff -M moss_2way_merge.g moss2.g moss3.g</userinput>
 M platform.r
 M ellipse.s
@@ -619,36 +619,36 @@ CONFLICT(ellipse.s).right     ellipse.r/R
 CONFLICT(eto.s).left          ellipse2.r/R
 CONFLICT(eto.s).right         platform.s
 CONFLICT(light.r).left/R      tgc_new.s
-    </computeroutput>
-  </literallayout>
-  The result is far less clean, although the merge was still performed - in this latter case, the end user will have to
-  resolve many more conflicting object states manually.
-</para>
-</example>
+                </computeroutput>
+          </literallayout>
+          The result is far less clean, although the merge was still performed - in this latter case, the end user will have to
+          resolve many more conflicting object states manually.
+        </para>
+  </example>



-</refsect1>
+	</refsect1>

-<refsect1 xml:id='see_also'><title>SEE ALSO</title>
-<para><citerefentry><refentrytitle>search</refentrytitle><manvolnum>n</manvolnum></citerefentry></para>
+	<refsect1 xml:id='see_also'><title>SEE ALSO</title>
+		<para><citerefentry><refentrytitle>search</refentrytitle><manvolnum>n</manvolnum></citerefentry></para>

-</refsect1>
+	</refsect1>

-<refsect1 xml:id='author'><title>AUTHOR</title>
-<para>BRL-CAD Team</para>
+	<refsect1 xml:id='author'><title>AUTHOR</title>
+		<para>BRL-CAD Team</para>

-</refsect1>
+	</refsect1>

-<refsect1 xml:id='copyright'><title>COPYRIGHT</title>
-<para>This software is Copyright (c) 2014-2016 by the United States
-Government as represented by U.S. Army Research Laboratory.</para>
+	<refsect1 xml:id='copyright'><title>COPYRIGHT</title>
+		<para>This software is Copyright (c) 2014-2016 by the United States
+			Government as represented by U.S. Army Research Laboratory.</para>

-</refsect1>
+	</refsect1>

-<refsect1 xml:id='bug_reports'><title>BUG REPORTS</title>
-<para>Reports of bugs or problems should be submitted via electronic
-mail to &lt;devs@brlcad.org&gt;.</para>
-</refsect1>
+	<refsect1 xml:id='bug_reports'><title>BUG REPORTS</title>
+		<para>Reports of bugs or problems should be submitted via electronic
+			mail to &lt;devs@brlcad.org&gt;.</para>
+	</refsect1>
 </refentry>

@@ -1,187 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='icv1'>
-  <refmeta>
-    <refentrytitle>ICV</refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo class='source'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname>icv</refname>
-    <refpurpose>Convert images to and from various formats</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv xml:id='synopsis'>
-    <cmdsynopsis>
-      <command>icv</command>
-      <arg choice='opt'>-h</arg>
-      <arg choice='opt'>-i <replaceable>file</replaceable></arg>
-      <arg choice='opt'>--input-format <replaceable>fmt</replaceable></arg>
-      <arg choice='opt'>-o <replaceable>file</replaceable></arg>
-      <arg choice='opt'>--output-format <replaceable>fmt</replaceable></arg>
-      <arg choice='opt'>-w <replaceable>width</replaceable></arg>
-      <arg choice='opt'><replaceable>input_file</replaceable></arg>
-      <arg choice='opt'><replaceable>output_file</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-
-  <refsection xml:id='description'>
-    <title>DESCRIPTION</title>
-    <para>
-      <command>icv</command> is a tool to convert images to and from a variety of
-      image formats.  Currently support formats include:
-
-      <table>
-	<title>Supported ICV Image Formats</title>
-	<tgroup cols="2">
-	  <thead>
-	    <row>
-	      <entry>Format</entry>
-	      <entry>Extension</entry>
-	    </row>
-	  </thead>
-	  <tbody>
-	    <row>
-	      <entry>PIX - pixel sequence of R/G/B values stored as unsigned chars.</entry>
-	      <entry>pix</entry>
-	    </row>
-	    <row>
-	      <entry>Double PIX - double precision pixel sequence</entry>
-	      <entry>dpix</entry>
-	    </row>
-	    <row>
-	      <entry>Portable Network Graphics</entry>
-	      <entry>png</entry>
-	    </row>
-	    <row>
-	      <entry>PPM - "lowest common denominator" Netbpm color iamge format</entry>
-	      <entry>ppm</entry>
-	    </row>
-	    <row>
-	      <entry>BW - black and white image data</entry>
-	      <entry>bw</entry>
-	    </row>
-	    <row>
-	      <entry>(TODO) Utah Raster Toolkit Run-Length Encoded (RLE)</entry>
-	      <entry>rle</entry>
-	    </row>
-	  </tbody>
-	</tgroup>
-      </table>
-    </para>
-  </refsection>
-
-  <refsection xml:id='options'>
-    <title>OPTIONS</title>
-    <para>
-      File types will be deduced unless explicitly specfied with the <option>input-format</option>
-      and/or <option>output-format</option> options.
-
-      For file types like PIX that do not encode dimensional information, <command>icv</command>
-      will attempt to guess the image size based on various assumptions (a square image, known sizes
-      for image displays, paper sizes at various dots-per-inch, etc.).  If the users does know
-      the correct image width and height, they may be specified with the <option>w</option> and
-      <option>n</option> options.
-    </para>
-
-    <variablelist remap='TP'>
-      <varlistentry>
-	<term><option>-h</option>, <option>--help</option></term>
-	<listitem>
-	  <para>
-	    Print help and exit.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>-i</option> <replaceable>file</replaceable>, <option>--input</option> <replaceable>file</replaceable></term>
-	<listitem>
-	  <para>
-	    Specify an input file.  If none is specified, the first non-option-related argument will be used as the input file name.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>-o</option> <replaceable>file</replaceable>, <option>--output</option> <replaceable>file</replaceable></term>
-	<listitem>
-	  <para>
-	    Specify an input file.  If none is specified, the second non-option-related argument will be used as the output file name.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>-w</option> <replaceable>#</replaceable>, <option>--width</option> <replaceable>#</replaceable></term>
-	<listitem>
-	  <para>
-	    Specify the width of the input image.  Useful for file types such as PIX that do not encode explicit size information.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>-n</option> <replaceable>#</replaceable>, <option>--height</option> <replaceable>#</replaceable></term>
-	<listitem>
-	  <para>
-	    Specify the height of the input image.  Useful for file types such as PIX that do not encode explicit size information.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>--input-format</option> <replaceable>fmt</replaceable></term>
-	<listitem>
-	  <para>
-	    Explicitly specify input file format.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><option>--output-format</option> <replaceable>fmt</replaceable></term>
-	<listitem>
-	  <para>
-	    Explicitly specify output file format.
-	  </para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-  </refsection>
-
-  <refsection xml:id='example'>
-    <title>EXAMPLE</title>
-    <literallayout remap='RS'>
-      icv -w 1024 -n 512 tank.pix tank.png
-    </literallayout>
-  </refsection>
-
-  <refsection xml:id='see_also'>
-    <title>SEE ALSO</title>
-    <para>
-      <citerefentry><refentrytitle>pix</refentrytitle><manvolnum>5</manvolnum></citerefentry>
-      <citerefentry><refentrytitle>bw</refentrytitle><manvolnum>5</manvolnum></citerefentry>
-    </para>
-  </refsection>
-
-  <refsection xml:id='author'>
-    <title>AUTHOR</title>
-    <para>
-      Clifford Yapp
-    </para>
-  </refsection>
-
-  <refsection xml:id='copyright'>
-    <title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 1989-2016 by the United States
-      Government as represented by U.S. Army Research Laboratory.
-    </para>
-  </refsection>
-
-  <refsection xml:id='bug_reports'>
-    <title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;.
-    </para>
-  </refsection>
-</refentry>
-
@@ -290,6 +290,7 @@
 	  The
 	  <citerefentry><refentrytitle>pix-fb</refentrytitle><manvolnum>1</manvolnum></citerefentry>
 	  utility can be used later to display ".pix" files.
+	  Note that using -o disables parallel processing.
 	  </para>
 	</listitem>
      </varlistentry>
@@ -364,13 +365,6 @@
 	</listitem>
      </varlistentry>

-      <varlistentry>
-	<term><option>-z</option></term>
-	<listitem>
-	  <para>Enables OpenCL accelerated raytracing (OpenCL must be enabled at compilation time for this option to be present.)</para>
-	</listitem>
-      </varlistentry>
-
      <varlistentry>
 	<term><option>-A #</option></term>
 	<listitem>
@@ -393,7 +387,7 @@
 	<term><option>-C #/#/#</option></term>
 	<listitem>
 	  <para>sets the background color to the RGB value #/#/#, where each #
-	  is in the range of 0 to 255 or 0.0 to 1.0.
+	  is in the range of 0 to 255.
 	  All non-background colors will be dithered away from this value.</para>
 	</listitem>
      </varlistentry>
@@ -61,7 +61,7 @@
 	<term><option>-. #</option></term>
 	<listitem>
 	  <para>
-	    selects the factor used in NUgrid algorithm. Default is 1.5 .
+            selects the factor used in NUgrid algorithm. Default is 1.5 .
 	  </para>
 	</listitem>
      </varlistentry>
@@ -70,7 +70,7 @@
 	<term><option>-, #</option></term>
 	<listitem>
 	  <para>
-	   selects which space partitioning algorithm to use
+           selects which space partitioning algorithm to use
 	  </para>
 	</listitem>
      </varlistentry>
@@ -106,7 +106,7 @@
 	<term><option>-d #</option></term>
 	<listitem>
 	  <para>sets flag for reporting of pixel distances: 1 for on, 0 (default) for off.
-	  (Each pixel is represented by 3 bytes of color information followed by 8 bytes
+          (Each pixel is represented by 3 bytes of color information followed by 8 bytes
 	  for a double, in IEEE format, which gives the distance to the ray's first hit.
 	  If the ray doesn't hit, a zero distance is reported by default
 	  which causes <citerefentry><refentrytitle>rt</refentrytitle><manvolnum>1</manvolnum></citerefentry>
@@ -379,7 +379,7 @@
 	<term><option>-C #/#/#</option></term>
 	<listitem>
 	  <para>sets the background color to the RGB value #/#/#, where each #
-	  is in the range of 0 to 255 or 0.0 to 1.0.
+	  is in the range of 0 to 255.
 	  All non-background colors will be dithered away from this value.</para>
 	</listitem>
      </varlistentry>
@@ -388,7 +388,7 @@
 	<term><option>-D #</option></term>
 	<listitem>
 	  <para>This is the "desired frame" flag, specifying the frame number to start with.
-	   Used with animation scripts; specify the desired ending (kill-after) frame with
+           Used with animation scripts; specify the desired ending (kill-after) frame with
 	  <option>-K #</option> .</para>
 	</listitem>
      </varlistentry>
@@ -397,7 +397,7 @@
 	<term><option>-E #</option></term>
 	<listitem>
 	  <para>sets the distance from the eye point to the center of the model RPP; default is
-	  the square root of 2.
+          the square root of 2.
 	  Only useful with auto-sizing, and conflicts with
 	  <option>-M</option> .</para>
 	</listitem>
@@ -425,10 +425,10 @@
      <varlistentry>
 	<term><option>-H #</option></term>
 	<listitem>
-	  <para>This is the "hypersample" flag, specifying number of extra rays to fire for each pixel to
-	  obtain more accurate results without needing to store the extra pixels. Automatically invokes
+          <para>This is the "hypersample" flag, specifying number of extra rays to fire for each pixel to
+          obtain more accurate results without needing to store the extra pixels. Automatically invokes
 	  <option>-J 1</option>. The final colors of all rays are averaged together. Better results can be
-	 obtained by simply increasing the resolution, and decimating the results with a filter such as
+         obtained by simply increasing the resolution, and decimating the results with a filter such as
 	  <citerefentry><refentrytitle>pixhalve</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
 	</listitem>
      </varlistentry>
@@ -621,7 +621,7 @@
 	<term><option>-+ #</option></term>
 	<listitem>
 	  <para>specifies (setting argument to "t") that output is NOT binary (default is that it is).
-	  <option>-+</option> is otherwise not implemented.
+          <option>-+</option> is otherwise not implemented.
 	  </para>
 	</listitem>
      </varlistentry>
@@ -672,8 +672,8 @@
 	<listitem>
 	  <para>
 	    set the color of the foreground (edges) to the
-	    given  r,g,b triple, where each of r,g,b, is in the range 0 to 255 or 0.0 to 1.0.
-	    The default is white (255/255/255).
+	    given  r,g,b triple. The default is white
+	    (255,255,255).
 	  </para>
 	</listitem>
      </varlistentry>
@@ -688,8 +688,7 @@
 	<listitem>
 	  <para>
 	    set the color of the background to the r,g,b
-	    triple, where each of r,g,b is in the range 0 to 255 or 0.0 to 1.0.
-	    The default is near-black (0,0,1).
+	    triple. The default is near-black (0,0,1).
 	  </para>
 	</listitem>
      </varlistentry>
@@ -944,7 +943,7 @@

      <para>
 	The command
-	<userinput>rtedge -s1024 -o new.pix -c"set fg=0/255/0 bg=255/0/0" havoc.g havoc</userinput>
+	<userinput>rtedge -s1024 -o new.pix -c"set fg=0,255,0 bg=255,0,0" havoc.g havoc</userinput>
 	changes the edge color to be green and the background color to be red.
      </para>

@@ -348,7 +348,8 @@ as a region.
 "matname" is either a NULL pointer, or a pointer to a string
 containing the material property name.
 "matparm" is either a NULL pointer, or a pointer to a string
-containing the material property parameter information specific to that material.
+containing the material property parameter information,
+which is material-specific (and still experimental).
 Color is passed as an array of three unsigned chars in "rgb".
 Color "inherit" is a boolean, and if true, the color and material
 properties will be passed from upper-level objects to lower-level
@@ -22,8 +22,6 @@ set_target_properties(attr_std_list_xml PROPERTIES FOLDER "DocBook")
 set(man5_EN
  dsp.xml
  ${CMAKE_CURRENT_BINARY_DIR}/attributes.xml
-  burst_point_library.xml
-  burst_shotline_files.xml
  bw.xml
  cmap.xml
  pix.xml
@@ -1,251 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='burst_point_library'>
-  <refmeta>
-    <refentrytitle>Burst Point Library File Format</refentrytitle>
-    <manvolnum>5</manvolnum>
-    <refmiscinfo class='source'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname>burst_point_library</refname>
-    <refpurpose>Data output by the <command>burst-file</command> command from the burst tool.</refpurpose>
-  </refnamediv>
-
-  <refsection xml:id='format'>
-    <title>FORMAT</title>
-    <para>
-
-      Burst point library files are composed of single-line records. Each line begins with a
-      digit that identifies the type of record it represents. The file is composed of one or more runs that
-      begin with a run header. Each shotline that intersects the target will result in a shotline header that is
-      followed by one or more shotline intersection records. If a burst point occurs along a shotline, the burst ray header will
-      immediately follow that shotline's last intersection record. Each burst ray header records will be
-      immediately followed by burst ray intersection records, one for each ray that strikes a critical component.
-
-      <table>
-	<title>Burst Point Library File Format</title>
-	<tgroup cols="3">
-	  <thead>
-	    <row>
-	      <entry>Record Description</entry>
-	      <entry>Field Format</entry>
-	      <entry>Field Description</entry>
-	    </row>
-	  </thead>
-	  <tbody>
-
-	    <row>
-	      <entry>run header</entry>
-	      <entry>'1'</entry>
-	      <entry>record number 1</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f9.4</entry>
-	      <entry>attack azimuth (degrees)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.4</entry>
-	      <entry>attack elevation (degrees)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f5.2</entry>
-	      <entry>burst distance</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f10.2</entry>
-	      <entry>projected area associated with burst point</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,6a</entry>
-	      <entry>units (mm,cm,inches,feet,meters)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f9.6</entry>
-	      <entry>ray solid angle (steradians)</entry>
-	    </row>
-
-	    <row>
-	      <entry>shotline header</entry>
-	      <entry>'2'</entry>
-	      <entry>record number 2</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>Y' coordinate of shotline</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>Z' coordinate of shotline</entry>
-	    </row>
-
-	    <row>
-	      <entry>shotline intersections</entry>
-	      <entry>'3'</entry>
-	      <entry>record number 3</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.2</entry>
-	      <entry>X' coordinate of component intersection</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.2</entry>
-	      <entry>line-of-sight thickness of component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i4</entry>
-	      <entry>component code number</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i2</entry>
-	      <entry>space code</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.3</entry>
-	      <entry>sine of fallback angle of exit normal</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>rotation angle of exit normal (degrees)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.3</entry>
-	      <entry>cosine of obliquity angle at entry</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,a1</entry>
-	      <entry>burst flag ('1' for yes, '0' for no)</entry>
-	    </row>
-
-	    <row>
-	      <entry>burst ray header</entry>
-	      <entry>'4'</entry>
-	      <entry>record number 4</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>azimuth angle WRT shotline (radians)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>sine of elevation angle WRT shotline</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i6</entry>
-	      <entry>sequential ray number for this burst point</entry>
-	    </row>
-
-	    <row>
-	      <entry>burst ray intersections</entry>
-	      <entry>'5'</entry>
-	      <entry>record number 5</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f10.3</entry>
-	      <entry>distance to first contact with component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f9.3</entry>
-	      <entry>line-of-sight thickness of component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f9.3</entry>
-	      <entry>normal thickness of component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i4</entry>
-	      <entry>space code</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>ix,i4</entry>
-	      <entry>component code number</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>ix,f6.3</entry>
-	      <entry>cosine of obliquity angle at entry</entry>
-	    </row>
-
-	  </tbody>
-	</tgroup>
-      </table>
-    </para>
-  </refsection>
-  <refsection xml:id='see_also'>
-    <title>SEE ALSO</title>
-    <para>
-      <citerefentry><refentrytitle>burst</refentrytitle><manvolnum>1</manvolnum></citerefentry>
-    </para>
-  </refsection>
-
-  <refsection xml:id='author'>
-    <title>AUTHOR</title>
-    <para>BRL-CAD Team</para>
-  </refsection>
-
-  <refsection xml:id='copyright'>
-    <title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 1989-2016 by the United States
-      Government as represented by U.S. Army Research Laboratory.
-    </para>
-
-  </refsection>
-
-  <refsection xml:id='bug_reports'>
-    <title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;.
-    </para>
-  </refsection>
-</refentry>
@@ -1,198 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<refentry xmlns='http://docbook.org/ns/docbook' version='5.0' xml:lang='en' xml:id='burst_shotline_5'>
-  <refmeta>
-    <refentrytitle>Burst Shotline File Format</refentrytitle>
-    <manvolnum>5</manvolnum>
-    <refmiscinfo class='source'>BRL-CAD</refmiscinfo>
-    <refmiscinfo class='manual'>BRL-CAD</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname>burst_shotline_files</refname>
-    <refpurpose>Data output by the <command>shotline-file</command> command from the burst tool.</refpurpose>
-  </refnamediv>
-
-  <refsection xml:id='format'>
-    <title>FORMAT</title>
-    <para>
-
-      Burst shotline files are composed of single-line records. Each line begins with a
-      digit that identifies the type of record it represents. The file is composed of one or more runs that
-      begin with a run header. Each shotline that intersects the target will result in a shotline header that is
-      followed by one or more shotline intersection records.
-
-      <table>
-	<title>Shotline File Format</title>
-	<tgroup cols="3">
-	  <thead>
-	    <row>
-	      <entry>Record Description</entry>
-	      <entry>Field Format</entry>
-	      <entry>Field Description</entry>
-	    </row>
-	  </thead>
-	  <tbody>
-
-	    <row>
-	      <entry>run header</entry>
-	      <entry>'1'</entry>
-	      <entry>record number 1</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f9.4</entry>
-	      <entry>attack azimuth (degrees)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.4</entry>
-	      <entry>attack elevation (degrees)</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>shotline separation</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>maximum Y' coordinate of target</entry>
-	    </row>
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>minimum Y' coordinate of target</entry>
-	    </row>
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>maximum Z' coordinate of target</entry>
-	    </row>
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>minimum Z' coordinate of target</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,6a</entry>
-	      <entry>units (mm,cm,inches,feet,meters)</entry>
-	    </row>
-
-	    <row>
-	      <entry>shotline header</entry>
-	      <entry>'2'</entry>
-	      <entry>record number 2</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>Y' coordinate of shotline</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.3</entry>
-	      <entry>Z' coordinate of shotline</entry>
-	    </row>
-
-	    <row>
-	      <entry>shotline intersections</entry>
-	      <entry>'3'</entry>
-	      <entry>record number 3</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.2</entry>
-	      <entry>X' coordinate of component intersection</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.3</entry>
-	      <entry>sine of fallback angle of exit normal</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>rotation angle of exit normal in degrees</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i4</entry>
-	      <entry>component code number</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.2</entry>
-	      <entry>normal thickness of component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f8.2</entry>
-	      <entry>line-of-sight thickness of component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,i2</entry>
-	      <entry>space code following component</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>obliquity angle at entry to component in degrees</entry>
-	    </row>
-
-	    <row>
-	      <entry></entry>
-	      <entry>1x,f7.2</entry>
-	      <entry>obliquity angle at exit from component in degrees</entry>
-	    </row>
-
-	  </tbody>
-	</tgroup>
-      </table>
-    </para>
-  </refsection>
-  <refsection xml:id='see_also'>
-    <title>SEE ALSO</title>
-    <para>
-      <citerefentry><refentrytitle>burst</refentrytitle><manvolnum>1</manvolnum></citerefentry>
-    </para>
-  </refsection>
-
-  <refsection xml:id='author'>
-    <title>AUTHOR</title>
-    <para>BRL-CAD Team</para>
-  </refsection>
-
-  <refsection xml:id='copyright'>
-    <title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 1989-2016 by the United States
-      Government as represented by U.S. Army Research Laboratory.
-    </para>
-
-  </refsection>
-
-  <refsection xml:id='bug_reports'>
-    <title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;.
-    </para>
-  </refsection>
-</refentry>
@@ -6,6 +6,7 @@ set(mann_EN
  Z.xml
  adc.xml
  ae.xml
+  alias-pix.xml
  all_sf.xml
  analyze.xml
  anim_cascade.xml
@@ -52,6 +53,7 @@ set(mann_EN
  cp.xml
  cpi.xml
  d.xml
+  dall.xml
  db.xml
  db_glob.xml
  dbconcat.xml
@@ -80,10 +82,12 @@ set(mann_EN
  em.xml
  eqn.xml
  erase.xml
+  erase_all.xml
  ev.xml
  exists.xml
  exit.xml
  expand.xml
+  export_body.xml
  extrude.xml
  eye_pt.xml
  facedef.xml
@@ -92,11 +96,12 @@ set(mann_EN
  fracture.xml
  g.xml
  garbage_collect.xml
-  gdiff.xml
+  gastank.xml
  gqa.xml
  gr.xml
  graph.xml
  gui.xml
+  handle.xml
  help.xml
  helpdevel.xml
  helplib.xml
@@ -125,10 +130,8 @@ set(mann_EN
  loadtk.xml
  lookat.xml
  ls.xml
-  lt.xml
  make.xml
  make_pnts.xml
-  man.xml
  mater.xml
  matpick.xml
  memprint.xml
@@ -149,6 +152,7 @@ set(mann_EN
  pathlist.xml
  paths.xml
  permute.xml
+  picket_fence.xml
  plot.xml
  prcolor.xml
  prefix.xml
@@ -199,7 +203,7 @@ set(mann_EN
  sed.xml
  setview.xml
  shader.xml
-  shells.xml
+  shell.xml
  showmats.xml
  size.xml
  solids.xml
@@ -227,6 +231,7 @@ set(mann_EN
  vnirt.xml
  voxelize.xml
  vquery_ray.xml
+  vrmgr.xml
  vrot.xml
  wcodes.xml
  whatid.xml
@@ -234,6 +239,9 @@ set(mann_EN
  whichair.xml
  whichid.xml
  who.xml
+  window.xml
+  window_frame.xml
+  wire.xml
  wmater.xml
  x.xml
  xpush.xml
@@ -1,20 +1,13 @@
 <article xmlns="http://docbook.org/ns/docbook" version="5.0">
-  <title>BRL-CAD Manual Pages</title>
+  <title>MGED Commands - Manual Pages</title>



   <para>
-      This is BRL-CAD's tool for viewing manual pages for commands. To bring up
-      the manual page for a specific command select it from the list to the
-      left of this welcome message.
-  </para>
-  <para>
-      By default, the list will itemize GED commands if the man viewer is
-      launched from MGED or Archer, and command line commands if the brlman
-      program is run directly from the command line.  To specify a specific
-      section of manual pages to list with brlman, use the -S option on the
-      command line to specify 1, 3, 5 or n (with n being GED commands.)
-  </para>
+      This is MGED's help system for commands available at the MGED
+      prompt.  To bring up the manual page for a specific command
+      select it from the list to the left of this welcome message.
+    </para>
   <para>
      These manual pages are written in Docbook format and displayed
      as HTML.
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>ALIAS-PIX</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -683,21 +683,6 @@
        </listitem>
      </varlistentry>
    </variablelist>
-    <variablelist>
-      <cmdsynopsis>
-        <command>csg</command>
-      </cmdsynopsis>
-      <varlistentry>
-        <term></term>
-        <listitem>
-          <para>
-            Take the specified B-Rep and attempt to generate a CSG
-	    implicit boolean tree that will define the same solid
-	    shape.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
  </refsection>

  <refsection xml:id='examples'>
@@ -31,7 +31,7 @@
      <command>d</command> command (use the <command>who</command> command to see
      a list of explicitly displayed objects). Objects that are displayed as members
      of explicitly displayed combinations cannot be deleted from the display with
-      this command (see <command>erase -r</command>).
+      this command (see <command>dall</command> or <command>erase_all</command>).
      Note that this has no effect on the <emphasis>BRL-CAD</emphasis> database
      itself. To actually remove objects from the database, use the
      <command>kill</command> command.
@@ -0,0 +1,62 @@
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="dall">
+
+  <refmeta>
+    <refentrytitle>DALL</refentrytitle>
+    <manvolnum>nged</manvolnum>
+    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
+    <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
+  </refmeta>
+
+  <refnamediv xml:id="name">
+    <refname>dall</refname>
+    <refpurpose>Deletes the specified list of objects from the <emphasis>mged</emphasis>
+    display. This is a synonym for the <command>erase_all</command>command.
+    </refpurpose>
+  </refnamediv>
+
+  <!-- body begins here -->
+  <refsynopsisdiv xml:id="synopsis">
+    <cmdsynopsis sepchar=" ">
+      <command>dall</command>
+      <arg choice="req" rep="norepeat"><replaceable>objects</replaceable></arg>
+    </cmdsynopsis>
+  </refsynopsisdiv>
+
+  <refsection xml:id="description"><title>DESCRIPTION</title>
+
+    <para>
+      Deletes the specified list of objects from the <emphasis>mged</emphasis>
+      display. This is a synonym for the <command>erase_all</command> command.
+      This command will allow the user to delete objects that have not been explicitly
+      displayed (unlike the <command>d</command> command). Note that this has no effect on the
+      <emphasis>BRL-CAD</emphasis> database itself. To actually remove objects from the database,
+      use the <command>kill</command>command.
+    </para>
+  </refsection>
+
+  <refsection xml:id="examples"><title>EXAMPLES</title>
+
+    <para>
+      The example shows the use of the <command>dall</command> command to delete a
+      region and a shape from the <emphasis>mged</emphasis> display, even if they
+      have not been explicitly displayed.
+    </para>
+    <example><title>Delete a region and a shape from the <emphasis>mged</emphasis> display,
+      even if they have not been explicitly displayed.</title>
+
+      <para><prompt>mged&gt;</prompt> <userinput>dall region1 shapea</userinput></para>
+      <para>Deletes <emphasis>region1</emphasis> and <emphasis>shapea</emphasis> from
+      the <emphasis>mged</emphasis> display.</para>
+    </example>
+  </refsection>
+
+  <refsection xml:id="author"><title>AUTHOR</title><para>BRL-CAD Team</para></refsection>
+
+  <refsection xml:id="bug_reports"><title>BUG REPORTS</title>
+
+    <para>
+      Reports of bugs or problems should be submitted via electronic
+      mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+    </para>
+  </refsection>
+</refentry>
@@ -1,157 +1,134 @@
 <refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="draw">

-  <refmeta>
-    <refentrytitle>DRAW</refentrytitle>
-    <manvolnum>nged</manvolnum>
-    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
-    <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
-  </refmeta>
+<refmeta>
+  <refentrytitle>DRAW</refentrytitle>
+  <manvolnum>nged</manvolnum>
+  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
+  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
+</refmeta>

-  <refnamediv xml:id="name">
-    <refname>draw</refname>
-    <refpurpose>Adds <emphasis>objects</emphasis>&gt; to the display list so that they will appear on the
-    <emphasis>MGED</emphasis> display. The <command>e</command> command is a synonym for <command>draw</command>.
-    </refpurpose>
-  </refnamediv>
+<refnamediv xml:id="name">
+  <refname>draw</refname>
+  <refpurpose>Adds <emphasis>objects</emphasis>&gt; to the display list so that they will appear on the
+ <emphasis>MGED</emphasis> display. The <command>e</command> command is a synonym for <command>draw</command>.
+   </refpurpose>
+</refnamediv>

-  <!-- body begins here -->
-  <refsynopsisdiv xml:id="synopsis">
-    <cmdsynopsis sepchar=" ">
-      <command>draw</command>
+<!-- body begins here -->
+<refsynopsisdiv xml:id="synopsis">
+  <cmdsynopsis sepchar=" ">
+    <command>draw</command>

-      <arg choice="opt" rep="norepeat">-A <replaceable>attribute name/value pairs</replaceable></arg>
-      <arg choice="opt" rep="norepeat">-s</arg>
-      <arg choice="opt" rep="norepeat">-A -o<replaceable>attribute name/value pairs</replaceable></arg>
-      <arg choice="opt" rep="norepeat">-C#/#/#</arg>
-      <arg choice="opt" rep="norepeat">-L #</arg>
-      <arg choice="opt" rep="norepeat">-R</arg>
-      <arg choice="opt" rep="norepeat">-S</arg>
-      <arg choice="opt" rep="norepeat"><replaceable>-m1</replaceable></arg>
-      <arg choice="req" rep="norepeat"><replaceable>objects</replaceable></arg>
+    <arg choice="opt" rep="norepeat">-A <replaceable>attribute name/value pairs</replaceable></arg>
+    <arg choice="opt" rep="norepeat">-s</arg>
+    <arg choice="opt" rep="norepeat">-A -o<replaceable>attribute name/value pairs</replaceable></arg>
+    <arg choice="opt" rep="norepeat">-C#/#/#</arg>
+    <arg choice="opt" rep="norepeat">-L #</arg>
+    <arg choice="opt" rep="norepeat"><replaceable>-m1</replaceable></arg>
+    <arg choice="req" rep="norepeat"><replaceable>objects</replaceable></arg>

-    </cmdsynopsis>
-  </refsynopsisdiv>
+  </cmdsynopsis>
+</refsynopsisdiv>

-  <refsection xml:id="description"><title>DESCRIPTION</title>
+<refsection xml:id="description"><title>DESCRIPTION</title>

-  <para>
-    Adds <emphasis>objects</emphasis> to the display list so that they will appear on the
-    MGED display. The <command>e</command> command is a synonym for draw.
+  <para>Adds <emphasis>objects</emphasis>&gt; to the display list so that they will appear on the MGED display. The <command>e</command> command is a synonym for draw.
  </para>
-  <itemizedlist mark="bullet">
-    <listitem>
-      <para>
+<itemizedlist mark="bullet">
+<listitem>
+<para>
 	The <emphasis>-C</emphasis> option provides the user a way to specify a color that overrides all other
 	color specifications including combination colors and region-id-based colors.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
+</para>
+</listitem>
+<listitem>
+<para>
 	The <emphasis>-s</emphasis> option specifies that subtracted and intersected objects should be drawn
 	with shape lines rather than dot-dash lines.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
+</para>
+</listitem>
+<listitem>
+<para>
 	The <emphasis>-A</emphasis> option specifies that the arguments provided to this command are attribute
 	name/value pairs, and only objects having the specified attributes and values are
 	to be displayed. The default (without <emphasis>-o</emphasis>) is that only objects having all the
 	specified attribute name/value pairs will be displayed.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
-	The <emphasis>-m1</emphasis> option will display BOTs shaded if the display manager is OpenGL and the
-	zbuffer and lighting is enabled. To enable these settings, from the MGED GUI, choose
-	"Modes/Display Manager/OpenGL", "Misc/Z-buffer" and "Misc/Lighting". If the zbuffer and lighting is
-	already enabled, toggle them off then back on to ensure they are enabled.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
+</para>
+</listitem>
+<listitem>
+<para>
+	 The <emphasis>-m1</emphasis> option will display BOTs shaded if the display manager is OpenGL and the
+	 zbuffer and lighting is enabled. To enable these settings, from the MGED GUI, choose
+	 "Modes/Display Manager/OpenGL", "Misc/Z-buffer" and "Misc/Lighting". If the zbuffer and lighting is
+	 already enabled, toggle them off then back on to ensure they are enabled.
+</para>
+</listitem>
+<listitem>
+<para>
 	The <emphasis>-L</emphasis> option allows the user to specify a face count.  BoT primitives with more
 	faces than the user set threshold will be represented in wireframe drawing by their bounding boxes rather
 	than the full BoT wireframe.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
-	The <emphasis>-R</emphasis> option tells draw to not change the view size when drawing new objects.
-	Without this flag, <command>draw</command> will automatically size the view to make the new object(s)
-	visible when the view was previously empty.
-      </para>
-    </listitem>
-    <listitem>
-      <para>
-	The <emphasis>-S</emphasis> option tells draw to be
-	"simplified" by skipping subtraction objects when drawing, not
-	drawing NMG interior surfaces, and potentially more. Skipping
-	subtractions is useful in situations where an object has many
-	large objects subtracted from it but those objects have
-	relatively minimal impact on the shape.  This results in the
-	default wireframe bearing little resemablance to the evaluated
-	shape.
-      </para>
-    </listitem>
+</para>
+</listitem>
+<listitem>
+<para>
+	The <emphasis>-M</emphasis> option tells draw to be "minimalist" by skipping subtraction objects when drawing.
+	This is useful in situations where an object has many large objects subtracted from it but those objects have
+	relatively minimal impact on the shape - this results in the wireframe bearing little resemablance to the
+       	evaluated shape.
+</para>
+</listitem>

+</itemizedlist>
+</refsection>

-  </itemizedlist>
-  </refsection>
+<refsection xml:id="examples"><title>EXAMPLES</title>

-  <refsection xml:id="examples">
-    <title>EXAMPLES</title>
+  <para>The following examples show the use of the <command>draw</command> command to draw particular objects,
+	to specify color, to draw with shape lines rather than dot-dash lines, and to limit the objects to be drawn
+ to those having specific attribute names and value pairs.
+  </para>
+  <example><title>Draw specific objects in the <emphasis>MGED</emphasis> display.</title>
+
+    <variablelist>
+      <varlistentry>
+	   <term><prompt>mged&gt;</prompt> <userinput>draw object1 object2</userinput></term>
+	   <listitem>
+	     <para><emphasis>Object1</emphasis> and <emphasis>object2</emphasis> are drawn in the <emphasis>MGED</emphasis> display.
+	     </para>
+	   </listitem>
+      </varlistentry>
+    </variablelist>
+  </example>
+
+  <example><title>Specify the color used to draw the object.</title>

    <para>
-      The following examples show the use of the <command>draw</command> command to draw
-      particular objects,
-      to specify color, to draw with shape lines rather than dot-dash lines, and to limit the objects to be drawn
-      to those having specific attribute names and value pairs.
+      <prompt>mged&gt;</prompt><userinput>draw -C 255/255/255 object2</userinput>
    </para>
+    <para>Object2 is drawn in white.
+    </para>
+  </example>

-    <example>
-      <title>Draw specific objects in the <emphasis>MGED</emphasis> display.</title>
-      <variablelist>
-	<varlistentry>
-	  <term><prompt>mged&gt;</prompt> <userinput>draw object1 object2</userinput></term>
-	  <listitem>
-	    <para><emphasis>Object1</emphasis> and <emphasis>object2</emphasis> are drawn in the <emphasis>MGED</emphasis> display.
-	    </para>
-	  </listitem>
-	</varlistentry>
-      </variablelist>
-    </example>
+ <example><title>Limit the objects to be drawn to those having specific attribute names and value pairs.
+ </title>

-    <example>
-      <title>Specify the color used to draw the object.</title>
-      <para>
-	<prompt>mged&gt;</prompt><userinput>draw -C 255/255/255 object2</userinput>
-      </para>
-      <para>Object2 is drawn in white.
-      </para>
-    </example>
-
-    <example>
-      <title>Limit the objects to be drawn to those having specific attribute names and value pairs.</title>
-      <para>
-	<prompt>mged&gt;</prompt><userinput>draw -A -o Comment {First comment} Comment {Second comment}</userinput>
-      </para>
-      <para>
-	Objects having a Comment attribute with a value of either "First comment" or "Second comment" are drawn.
-      </para>
-    </example>
-
-  </refsection>
-
-  <refsection xml:id="author">
-    <title>AUTHOR</title>
-    <para>BRL-CAD Team</para>
-  </refsection>
-
-  <refsection xml:id="bug_reports">
-    <title>BUG REPORTS</title>
    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+      <prompt>mged&gt;</prompt><userinput>draw -A -o Comment {First comment} Comment {Second comment}</userinput>
    </para>
-  </refsection>
+    <para>Objects having a Comment attribute with a value of either "First comment" or "Second comment" are drawn.
+    </para>
+  </example>
+
+</refsection>
+
+<refsection xml:id="author"><title>AUTHOR</title><para>BRL-CAD Team</para></refsection>
+
+<refsection xml:id="bug_reports"><title>BUG REPORTS</title>
+
+  <para>
+    Reports of bugs or problems should be submitted via electronic
+    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+  </para>
+</refsection>
 </refentry>
@@ -0,0 +1,60 @@
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="erase_all">
+
+<refmeta>
+  <refentrytitle>ERASE_ALL</refentrytitle>
+  <manvolnum>nged</manvolnum>
+  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
+  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
+</refmeta>
+
+<refnamediv xml:id="name">
+  <refname>erase_all</refname>
+  <refpurpose>Deletes the specified list of objects from the MGED display.
+   </refpurpose>
+</refnamediv>
+
+<!-- body begins here -->
+<refsynopsisdiv xml:id="synopsis">
+  <cmdsynopsis sepchar=" ">
+    <command>erase_all</command>
+
+    <arg choice="req" rep="norepeat"><replaceable>objects</replaceable></arg>
+    <arg choice="opt" rep="norepeat"/>
+  </cmdsynopsis>
+</refsynopsisdiv>
+
+<refsection xml:id="description"><title>DESCRIPTION</title>
+
+  <para>Deletes the specified list of objects from the MGED display. It is a synonym for the <command>dall</command> 	command. It allows the user to delete objects that have not been explicitly displayed (unlike the <command>d	</command> or <command>erase</command> commands). Note that this has no effect on the BRL-CAD database itself. To 	actually remove objects from the database, use the <command>kill</command> command.
+   </para>
+</refsection>
+
+<refsection xml:id="examples"><title>EXAMPLES</title>
+
+  <para>The example shows the use of the <command>erase_all</command> command to delete two objects from the MGED 	display.
+   </para>
+  <example><title>Delete objects from the MGED display.</title>
+
+    <variablelist>
+      <varlistentry>
+	   <term><prompt>mged&gt;</prompt> <userinput>erase_all region1 shapea</userinput></term>
+	   <listitem>
+	     <para>Two objects, <emphasis>region1</emphasis> and <emphasis>shapea</emphasis>, are deleted from the MGED 				display.
+	     </para>
+	   </listitem>
+      </varlistentry>
+    </variablelist>
+  </example>
+
+ </refsection>
+
+<refsection xml:id="author"><title>AUTHOR</title><para>BRL-CAD Team</para></refsection>
+
+<refsection xml:id="bug_reports"><title>BUG REPORTS</title>
+
+  <para>
+    Reports of bugs or problems should be submitted via electronic
+    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+  </para>
+</refsection>
+</refentry>
@@ -9,7 +9,7 @@

 <refnamediv xml:id="name">
  <refname>expand</refname>
-  <refpurpose>Performs matching of the <emphasis>shell globbing pattern</emphasis> with the names
+  <refpurpose>Performs matching of the <emphasis>regular_expression</emphasis> with the names
 of all the objects in the database. It returns all those that successfully match.
   </refpurpose>
 </refnamediv>
@@ -19,14 +19,14 @@ of all the objects in the database. It returns all those that successfully match
  <cmdsynopsis sepchar=" ">
    <command>expand</command>

-    <arg choice="req" rep="norepeat"><replaceable>globbing_expression</replaceable></arg>
+    <arg choice="req" rep="norepeat"><replaceable>regular_expression</replaceable></arg>

  </cmdsynopsis>
 </refsynopsisdiv>

 <refsection xml:id="description"><title>DESCRIPTION</title>

-  <para>Performs matching of the <emphasis>globbing_expression</emphasis> with the names
+  <para>Performs matching of the <emphasis>regular_expression</emphasis> with the names
 of all the objects in the database. It returns all those that successfully match.
  </para>
 </refsection>
@@ -0,0 +1,59 @@
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="export_body">
+
+<refmeta>
+  <refentrytitle>EXPORT_BODY</refentrytitle>
+  <manvolnum>nged</manvolnum>
+  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
+  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
+</refmeta>
+
+<refnamediv xml:id="name">
+  <refname>export_body</refname>
+  <refpurpose>Copies the contents of the specified binary <emphasis>object</emphasis> into the 	specified <emphasis>file</emphasis>.
+   </refpurpose>
+</refnamediv>
+
+<!-- body begins here -->
+<refsynopsisdiv xml:id="synopsis">
+  <cmdsynopsis sepchar=" ">
+    <command>export_body</command>
+    <arg choice="req" rep="norepeat"><replaceable>object file</replaceable></arg>
+  </cmdsynopsis>
+</refsynopsisdiv>
+
+<refsection xml:id="description"><title>DESCRIPTION</title>
+
+  <para>Copies the contents of the specified binary <emphasis>object</emphasis> into the 	specified <emphasis>file</emphasis>. Currently, only binary objects containing a uniform
+	array of simple objects are supported.
+  </para>
+</refsection>
+
+<refsection xml:id="examples"><title>EXAMPLES</title>
+
+  <para>The example shows the use of the <command>export_body</command> command to copy the contents of a particular binary <emphasis>object</emphasis> into a specified <emphasis>file</emphasis>.
+  </para>
+  <example><title>Copy the contents of a binary object into a file.</title>
+
+    <variablelist>
+      <varlistentry>
+	   <term><prompt>mged&gt;</prompt> <userinput>export_body bin_chars /home/fred/chars				</userinput></term>
+	   <listitem>
+	     <para>Copies the contents of bin_chars into the file /home/fred/chars.
+		     </para>
+	   </listitem>
+      </varlistentry>
+    </variablelist>
+  </example>
+
+ </refsection>
+
+<refsection xml:id="author"><title>AUTHOR</title><para>BRL-CAD Team</para></refsection>
+
+<refsection xml:id="bug_reports"><title>BUG REPORTS</title>
+
+  <para>
+    Reports of bugs or problems should be submitted via electronic
+    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+  </para>
+</refsection>
+</refentry>
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>GASTANK</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -1,129 +0,0 @@
-<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="gdiffn">
-
-  <refmeta>
-    <refentrytitle>GDIFF</refentrytitle>
-    <manvolnum>nged</manvolnum>
-    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
-    <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
-  </refmeta>
-
-  <refnamediv xml:id="name">
-    <refname>gdiff</refname>
-    <refpurpose>
-      a BRL-CAD differential geometry comparator
-    </refpurpose>
-  </refnamediv>
-
-  <!-- body begins here -->
-  <refsynopsisdiv xml:id="synopsis">
-    <cmdsynopsis sepchar=" ">
-      <command>gdiff</command>
-      <arg choice="opt" rep="repeat"><replaceable>options</replaceable></arg>
-      <arg choice="plain"><replaceable>left_object</replaceable></arg>
-      <arg choice="plain"><replaceable>right_object</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-  <refsection xml:id="description"><title>DESCRIPTION</title>
-
-    <para>
-      <command>gdiff</command> compares BRL-CAD geometry objects using
-      LIBRT's solid raytracing capabilities and visualizes differences in
-      the display manager.
-    </para>
-
-    <para>
-      Red segments are those generated only from intersections with the <emphasis>left_obj</emphasis>
-      object while blue segments represent intersections unique to the <emphasis>right_obj</emphasis>
-      object.  White segments represent intersections common to both objects. By default, only segments
-      unique to the left and/or right objects are displayed.
-    </para>
-
-    <para>
-      Users will want to pay careful attention to grid size.  By default gdiff
-      will try to guess a reasonable grid spacing using the bounding boxes of the
-      objects in question, but depending on the visual quality of the result users
-      may want to adjust the spacing up or down.  Be careful of specifying tolerances
-      that are too fine - performance will drop off rapidly as grid spacing becomes
-      very small.
-    </para>
-
-  </refsection>
-
-  <refsection xml:id="gdiff_mged_options"><title>OPTIONS</title>
-
-    <variablelist remap="TP">
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-h</emphasis></term>
-	<listitem>
-	  <para>
-	    Prints help.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-g #</emphasis></term>
-	<listitem>
-	  <para>
-	    Controls grid spacing.  Units are mm.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-l</emphasis></term>
-	<listitem>
-	  <para>
-	    Visualize solid segments occurring only in the left object.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-r</emphasis></term>
-	<listitem>
-	  <para>
-	    Visualize solid segments occurring only in the right object.
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-b</emphasis></term>
-	<listitem>
-	  <para>
-	    Visualize solid segments occurring in both the left and right object (i.e. common or shared volume).
-	  </para>
-	</listitem>
-      </varlistentry>
-      <varlistentry>
-	<term><emphasis remap="B" role="bold">-G</emphasis></term>
-	<listitem>
-	  <para>
-	    Report differences in grazing hits.  By default, differences are reported only when they can be
-	    verified by shooting parallel rays offset around the original shotline reporting a difference.
-	    This options disables that filter.
-	  </para>
-	</listitem>
-      </varlistentry>
-    </variablelist>
-
-  </refsection>
-
-  <refsection xml:id="author"><title>AUTHOR</title>
-    <para>Clifford Yapp</para>
-  </refsection>
-
-  <refsection xml:id="copyright"><title>COPYRIGHT</title>
-    <para>
-      This software is Copyright (c) 2016 United States Government as
-      represented by the U.S. Army Research Laboratory.
-    </para>
-  </refsection>
-
-  <refsection xml:id="bug_reports"><title>BUG REPORTS</title>
-    <para>
-      Reports of bugs or problems should be submitted via electronic
-      mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
-    </para>
-  </refsection>
-</refentry>
-
-<!-- vim: set shiftwidth=2 : -->
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>HANDLE</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -19,7 +19,6 @@
    <command>lc</command>
       <group choice="opt" rep="norepeat">
 	 <arg choice="plain" rep="norepeat">-d</arg>
-	 <arg choice="plain" rep="norepeat">-m</arg>
 	 <arg choice="plain" rep="norepeat">-s</arg>
       </group>
       <arg choice="opt" rep="norepeat">-r</arg>
@@ -70,18 +69,6 @@
 	</para>
      </listitem>
    </varlistentry>
-    <varlistentry>
-      <term><option>-m</option></term>
-      <listitem>
-	<para>
-	  Specifies to list only regions with shared 'region_id' values where one
-	  or more of the objects in the set of objects defined by shared 'region_id'
-	  value reports a different 'material_id' and/or 'los'.  Essentially, this
-	  allows users to quickly find and resolve inconsistent 'material_id' and
-	  'los' settings within a 'region_id' group.
-	</para>
-      </listitem>
-    </varlistentry>
    <varlistentry>
      <term><option>-r</option></term>
      <listitem>
@@ -1,63 +0,0 @@
-<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="lt">
-
-  <refmeta>
-    <refentrytitle>LT</refentrytitle>
-    <manvolnum>nged</manvolnum>
-    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
-    <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
-  </refmeta>
-
-  <refnamediv xml:id="name">
-    <refname>lt</refname>
-    <refpurpose>Generates a list of the child objects of a combination.</refpurpose>
-  </refnamediv>
-
-  <!-- body begins here -->
-  <refsynopsisdiv xml:id="synopsis">
-    <cmdsynopsis sepchar=" ">
-      <command>lt</command>
-      <arg choice="opt" rep="norepeat"><replaceable>char</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-  <refsection xml:id="description"><title>DESCRIPTION</title>
-
-  <para>
-    The <command>lt</command> command generates a list of the children found
-    in a combination object specified by the user.  By default it will print
-    a curly bracket bound set of objects and their boolean flags.  If the <option>-c</option>
-    option is specified, it will instead use the character supplied to the <option>-c</option>
-    option as the separator in the list of objects.  In the latter mode the
-    boolean flags will not be printed.
-  </para>
-  </refsection>
-
-  <refsection xml:id="examples"><title>EXAMPLES</title>
-
-  <example><title>Tcl Output</title>
-  <literallayout class="normal">
-mged&gt; lt component
-{u bed} {u frame} {u cab} {u suspension} {u misc} {u power.train}
-  </literallayout>
-  </example>
-
-  <example><title>CSV Output</title>
-  <literallayout class="normal">
-mged&gt; lt -c , component
-bed,frame,cab,suspension,misc,power.train
-  </literallayout>
-  </example>
-  </refsection>
-
-  <refsection xml:id="author"><title>AUTHOR</title>
-  <para>BRL-CAD Team</para>
-  </refsection>
-
-  <refsection xml:id="bug_reports"><title>BUG REPORTS</title>
-
-  <para>
-    Reports of bugs or problems should be submitted via electronic
-    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
-  </para>
-  </refsection>
-</refentry>
@@ -1,51 +0,0 @@
-<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="man_MGED">
-
-  <refmeta>
-    <refentrytitle>MAN</refentrytitle>
-    <manvolnum>nged</manvolnum>
-    <refmiscinfo class="source">BRL-CAD</refmiscinfo>
-    <refmiscinfo class="manual">BRL-CAD MGED Commands</refmiscinfo>
-  </refmeta>
-
-  <refnamediv xml:id="name">
-    <refname>man</refname>
-    <refpurpose>View manual pages.</refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv xml:id="synopsis">
-    <cmdsynopsis sepchar=" ">
-      <command>man</command>
-      <arg choice="req" rep="norepeat"><replaceable>cmdname</replaceable></arg>
-    </cmdsynopsis>
-  </refsynopsisdiv>
-
-  <refsection xml:id="description"><title>DESCRIPTION</title>
-
-  <para>
-    Launches the <command>brlman</command> graphical man page viewer with
-    the man page documenting the specified MGED command name.
-  </para>
-  </refsection>
-
-  <refsection xml:id="author"><title>AUTHOR</title>
-    <para>
-      BRL-CAD Team
-    </para>
-  </refsection>
-
-  <refsection xml:id="copyright"><title>COPYRIGHT</title>
-  <para>
-    This software is Copyright (c) 2016 United States Government as
-    represented by the U.S. Army Rebrlman Laboratory.
-  </para>
-  </refsection>
-
-  <refsection xml:id="bug_reports"><title>BUG REPORTS</title>
-  <para>
-    Reports of bugs or problems should be submitted via electronic
-    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
-  </para>
-  </refsection>
-</refentry>
-
-<!-- vim: set shiftwidth=2 : -->
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>PICKET_FENCE</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -550,10 +550,14 @@
 	<listitem>
 	  <para>
 	    The below operator applies the expression to every
-	    object below the matching object in the tree
-	    hierarchy.  E.g. searching with -below -name start\*
-	    on /component/region.r/start_comb.c/prim1.s would
-	    return prim1.s, as the object below start_comb.c
+	    object above the current full path to that object,
+	    and returns TRUE if one or more of them satisfies
+	    the expression.  E.g., searching with -below -name
+	    s\* on /component/region.r/start_comb.c/prim1.s
+	    would return TRUE for /component and
+	    /component/region.r as start_comb.c is below both of
+	    them, but would return FALSE for any deeper objects
+	    (i.e., prim1.s in this example).
 	  </para>
 	  <para>
 	    Optionally, inequality and equality constraints on
@@ -577,14 +581,12 @@
 	<listitem>
 	  <para>
 	    The above operator applies the expression to every
-	    object above the current full path to that object,
-	    and returns TRUE if one or more of them satisfies
-	    the expression.  E.g., searching with -above -name
-	    s\* on /component/region.r/start_comb.c/prim1.s
-	    would return TRUE for /component and
-	    /component/region.r as start_comb.c is below both of
-	    them, but would return FALSE for any deeper objects
-	    (i.e., prim1.s in this example).
+	    object below the current object in the tree
+	    hierarchy.  It finds objects that are above a given
+	    expression.  In effect, it does a "mini-search" up
+	    the tree using the current object path as a starting
+	    point and returns TRUE if the expression is
+	    satisfied by one or more objects in the sub-tree.
 	  </para>
 	  <para>
 	    Optionally, inequality and equality constraints on
@@ -848,17 +850,6 @@
      </para>
    </example>

-    <example><title>Find All Combs Containing At Least One of Two Objects (dbfind)</title>
-
-      <para>
-	<userinput>search |. ( -depth 0 -above=1 -name obj1 ) -or ( -depth 0 -above=1 -name obj2 ) </userinput>
-      </para>
-      <para>
-	Prints all combs immediately above either obj1 or obj2.  This more or less mimics the results of
-	the dbfind command, although it will be somewhat slower (noticably so on large databases.)
-      </para>
-    </example>
-
    <example><title>Finding all Plate-Mode BoT Objects</title>

      <para>
@@ -1,4 +1,4 @@
-<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="shells">
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="shell">

 <refmeta>
  <refentrytitle>SHELL</refentrytitle>
@@ -8,7 +8,7 @@
 </refmeta>

 <refnamediv xml:id="name">
-  <refname>shells</refname>
+  <refname>shell</refname>
  <refpurpose>Separates the specified NMG shape into its constituent shells.
   </refpurpose>
 </refnamediv>
@@ -0,0 +1,67 @@
+<refentry xmlns="http://docbook.org/ns/docbook" version="5.0" xml:id="vrmgr">
+
+<refmeta>
+  <refentrytitle>VRMGR</refentrytitle>
+  <manvolnum>nged</manvolnum>
+  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
+  <refmiscinfo class="manual">BRL-CAD MGED Commands</refmiscinfo>
+</refmeta>
+
+<refnamediv xml:id="name">
+  <refname>vrmgr</refname>
+  <refpurpose>Establishes a link between the current MGED display and a
+<emphasis>vrmgr</emphasis> process running on the specified <emphasis>host</emphasis>.
+   </refpurpose>
+</refnamediv>
+
+<!-- body begins here -->
+<refsynopsisdiv xml:id="synopsis">
+  <cmdsynopsis sepchar=" ">
+    <command>vrmgr</command>
+
+    <arg choice="req" rep="norepeat"><replaceable>host</replaceable></arg>
+<group choice="opt" rep="norepeat">
+	<arg choice="req" rep="norepeat">master</arg>
+	<arg choice="req" rep="norepeat">slave</arg>
+	<arg choice="req" rep="norepeat">overview</arg>
+</group>
+
+  </cmdsynopsis>
+</refsynopsisdiv>
+
+<refsection xml:id="description"><title>DESCRIPTION</title>
+
+  <para>Establishes a link between the current MGED display and a
+<emphasis>vrmgr</emphasis> process running on the specified <emphasis>host</emphasis>. The <emphasis>vrmgr</emphasis> program is a manager for virtual reality displays using MGED.  The <emphasis>vrmgr</emphasis> process must be started on <emphasis>host</emphasis> prior to executing the <command>vrmgr</command> command in MGED. The second command line argument to the <command>vrmgr</command> command is the role of the current MGED display. The <emphasis>master</emphasis> display controls the viewing parameters of itself and all the <emphasis>slave</emphasis> displays. The <emphasis>overview</emphasis> display acts as an observer of the entire virtual reality process.
+
+  </para>
+</refsection>
+
+<refsection xml:id="examples"><title>EXAMPLES</title>
+
+  <para>The example shows the use of the <command>vrmgr</command> command to set the current MGED display as the master for the <emphasis>vrmgr</emphasis> process running on the host.
+
+   </para>
+
+  <example><title>Set the current MGED display as the master for the <emphasis>vrmgr</emphasis> process running on the host.
+</title>
+
+    <para>
+      <prompt>mged&gt;</prompt><userinput>vrmgr host1.arl.army.mil master</userinput>
+    </para>
+    <para>Sets the current MGED display as the <emphasis>master</emphasis> for the <emphasis>vrmgr</emphasis> process running on the host named <emphasis>host1.arl.army.mil</emphasis>.
+    </para>
+  </example>
+
+</refsection>
+
+<refsection xml:id="author"><title>AUTHOR</title><para>BRL-CAD Team</para></refsection>
+
+<refsection xml:id="bug_reports"><title>BUG REPORTS</title>
+
+  <para>
+    Reports of bugs or problems should be submitted via electronic
+    mail to &lt;devs@brlcad.org&gt;, or via the "cadbug.sh" script.
+  </para>
+</refsection>
+</refentry>
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>WINDOW</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>WINDOW_FRAME</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -2,7 +2,7 @@

 <refmeta>
  <refentrytitle>WIRE</refentrytitle>
-  <manvolnum>1</manvolnum>
+  <manvolnum>nged</manvolnum>
  <refmiscinfo class="source">BRL-CAD</refmiscinfo>
  <refmiscinfo class="manual">BRL-CAD User Commands</refmiscinfo>
 </refmeta>
@@ -80,7 +80,7 @@ tops tree whatid whichair whichid</B>
 Methods associated with
 <A HREF="../librt/dg_obj.html#sect9">LIBRT's drawable geometry object</A>:<BR>
 <DL>
-<DD><B>assoc blast clear draw erase ev get_autoview
+<DD><B>assoc blast clear draw erase erase_all ev get_autoview
 illum label observer overlay report rt rtcheck vdraw who zap</B>
 </DD>
 </DL>
@@ -56,7 +56,7 @@ The following commands are possible for drawable objects:
 Methods associated with
 <A HREF="../librt/dg_obj.html#sect9">LIBRT's drawable geometry object</A>:<BR>
 <DL>
-<DD><B>assoc blast clear draw erase ev get_autoview
+<DD><B>assoc blast clear draw erase erase_all ev get_autoview
 illum label observer overlay report rt rtcheck vdraw who zap</B>
 </DD>
 </DL>
@@ -146,7 +146,7 @@ title tol tops tree whatid whichair whichid</B>
 <P>
 Methods associated with <A HREF="../librt/dg_obj.html#sect9">LIBRT's drawable geometry object</A>:<BR>
 <DL>
-<DD><B>blast clear draw erase ev
+<DD><B>blast clear draw erase erase_all ev
 get_autoview get_dgname illum label overlay
 report rt rtcheck vdraw who zap</B>
 </DD>
@@ -80,13 +80,13 @@ region id based colors.
 may be deleted with the ``erase'' command (use the <a href="#who">who</a>
 command to see a list of explicitly displayed objects). Objects that are
 displayed as members of explicitly displayed combinations cannot be
-deleted from the display with this command (see <a href="#erase -r">erase -r</a>).
+deleted from the display with this command (see <a href="#erase_all">erase_all</a>).
 Note that this has no effect on the
 <I>BRL&#173CAD</I> database itself. To actually remove objects from the
 database, use the <a href="#kill">kill</a> command.
 </DD>
 <P>
-<DT><I>dgName</I> <A NAME="erase -r"><B>erase -r</B></A> <I>&lt;objects&gt</I></DT>
+<DT><I>dgName</I> <A NAME="erase_all"><B>erase_all</B></A> <I>&lt;objects&gt</I></DT>
 <DD>Delete the specified list of objects from the display list.
 This command will allow the user to delete objects
 that have not been explicitly displayed (unlike the <a href="#erase">erase</a> command).
@@ -129,6 +129,9 @@ on the command line.
 to view coordinates with perspective.
 </DD>
 <P>
+<DT><I>viewName</I> <A NAME="pov"><B>pov</B></A></DT>
+<DD>Set the point of view (experimental).</DD>
+<P>
 <DT><I>viewName</I> <A NAME="rmat"><B>rmat</B></A> [<I>matrix</I>]</DT>
 <DD>Set/get the rotation matrix.</DD>
 <P>
@@ -110,6 +110,8 @@
 <FONT SIZE=2><P></FONT><A HREF="#cpi"><FONT SIZE=2>cpi</FONT></A></TD>
 <TD WIDTH="20%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#d"><FONT SIZE=2>d</FONT></A></TD>
+<TD WIDTH="22%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#dall"><FONT SIZE=2>dall</FONT></A></TD>
 <TD WIDTH="21%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#db"><FONT SIZE=2>db</FONT></A></TD>
 </TR>
@@ -163,6 +165,8 @@
 <FONT SIZE=2><P></FONT><A HREF="#em"><FONT SIZE=2>em</FONT></A></TD>
 <TD WIDTH="20%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#erase"><FONT SIZE=2>erase</FONT></A></TD>
+<TD WIDTH="22%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#erase_all"><FONT SIZE=2>erase_all</FONT></A></TD>
 <TD WIDTH="21%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#ev"><FONT SIZE=2>ev</FONT></A></TD>
 </TR>
@@ -170,6 +174,8 @@
 <FONT SIZE=2><P></FONT><A HREF="#exit"><FONT SIZE=2>exit</FONT></A></TD>
 <TD WIDTH="19%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#expand"><FONT SIZE=2>expand</FONT></A></TD>
+<TD WIDTH="20%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#export_body"><FONT SIZE=2>export_body</FONT></A></TD>
 <TD WIDTH="22%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#expand_comb"><FONT SIZE=2>expand_comb</FONT></A></TD>
 <TD WIDTH="21%" VALIGN="MIDDLE">
@@ -301,9 +307,15 @@
 <TD WIDTH="19%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#permute"><FONT SIZE=2>permute</FONT></A></TD>
 <TD WIDTH="20%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#pl"><FONT SIZE=2>pl</FONT></A></TD>
+<TD WIDTH="22%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#plot"><FONT SIZE=2>plot</FONT></A></TD>
+<TD WIDTH="21%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#polybinout"><FONT SIZE=2>polybinout</FONT></A></TD>
 </TR>
-<TR><TD WIDTH="19%" VALIGN="MIDDLE">
+<TR><TD WIDTH="18%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#pov"><FONT SIZE=2>pov</FONT></A></TD>
+<TD WIDTH="19%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#prcolor"><FONT SIZE=2>prcolor</FONT></A></TD>
 <TD WIDTH="20%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#prefix"><FONT SIZE=2>prefix</FONT></A></TD>
@@ -461,6 +473,9 @@
 <FONT SIZE=2><P></FONT><A HREF="#vnirt"><FONT SIZE=2>vnirt</FONT></A></TD>
 <TD WIDTH="20%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#vquery_ray"><FONT SIZE=2>vquery_ray</FONT></A></TD>
+<TD WIDTH="22%" VALIGN="MIDDLE">
+<FONT SIZE=2><P></FONT><A HREF="#vrmgr"><FONT SIZE=2>vrmgr</FONT></A></TD>
+<TD WIDTH="21%" VALIGN="MIDDLE">
 <FONT SIZE=2><P></FONT><A HREF="#vrot"><FONT SIZE=2>vrot</FONT></A></TD>
 </TR>
 <TR><TD WIDTH="18%" VALIGN="MIDDLE">
@@ -1083,12 +1098,20 @@
 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
 <DT><A NAME="d"></A>d</B> <I>&lt;objects</I>&gt;</DT>
-<DD>The &quot;d&quot; command deletes the specified list of objects from the <I>mged</I> display.  This is a synonym for the <A HREF="#erase">erase</A> command.  Only objects that have been explicitly displayed may be deleted with the &quot;d&quot; command (use the <A HREF="#who">who</A> command to see a list of explicitly displayed objects).  Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see <A HREF="#erase">erase -r</A>).  Note that this has no effect on the <I>BRL-CAD</I> database itself. To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
+<DD>The &quot;d&quot; command deletes the specified list of objects from the <I>mged</I> display.  This is a synonym for the <A HREF="#erase">erase</A> command.  Only objects that have been explicitly displayed may be deleted with the &quot;d&quot; command (use the <A HREF="#who">who</A> command to see a list of explicitly displayed objects).  Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see <A HREF="#dall">dall</A> or <A HREF="#erase_all">erase_all</A>).  Note that this has no effect on the <I>BRL-CAD</I> database itself. To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
 <FONT SIZE=4><DT>Examples:</DT>
 </FONT><TT><DD>mged&gt;</TT> <B>d region1 shapea</DD>
 </DL>
 </B><FONT SIZE=2><P>-- Delete <I>region1</I> and <I>shapea</I> from the <I>mged</I> display. </P>

+<P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
+<DT><A NAME="dall"></A>dall</B> <I>&lt;objects</I>&gt;</DT>
+<DD>The &quot;dall&quot; command deletes the specified list of objects from the <I>mged</I> display.  This is a synonym for the <A HREF="#erase_all">erase_all</A> command.  This command will allow the user to delete objects that have not been explicitly displayed (unlike the <A HREF="#d">d</A> command).  Note that this has no effect on the <I>BRL-CAD</I> database itself.  To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
+<FONT SIZE=4><DT>Examples:</DT>
+</FONT><TT><DD>mged&gt;</TT> <B>dall region1 shapea</DD>
+</DL>
+</B><FONT SIZE=2><P>-- Delete <I>region1</I> and <I>shapea</I> from the <I>mged</I> display. </P>
 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
 <DT><A NAME="db"></A>db</B> <I>command</I> [<I>args...</I>]</DT>
@@ -1449,13 +1472,21 @@ l r230 r231 r232 r233 r234 r235 r236 r237 r238 r239 <BR>
 <DD><HR ALIGN="RIGHT"></DD></DIR>

 <B><DT>erase</B> <I>&lt;objects</I>&gt;</DT>
-<DD>The &quot;erase&quot; command deletes the specified list of objects from the MGED<I> </I>display.  This is a synonym for the <A HREF="#d">d</A> command.  Only objects that have been explicitly displayed may be deleted with the &quot;erase&quot; command (use the <A HREF="#who">who</A> command to see a list of explicitly displayed objects).  Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see <A HREF="#erase">erase -r</A>).  Note that this has no effect on the <I>BRL-CAD</I> database itself.  To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
+<DD>The &quot;erase&quot; command deletes the specified list of objects from the MGED<I> </I>display.  This is a synonym for the <A HREF="#d">d</A> command.  Only objects that have been explicitly displayed may be deleted with the &quot;erase&quot; command (use the <A HREF="#who">who</A> command to see a list of explicitly displayed objects).  Objects that are displayed as members of explicitly displayed combinations cannot be deleted from the display with this command (see <A HREF="#dall">dall</A> or <A HREF="#erase_all">erase_all</A>).  Note that this has no effect on the <I>BRL-CAD</I> database itself.  To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
 <FONT SIZE=4><DT>Examples:</DT>
 </FONT><TT><DD>mged&gt;</TT> <B>erase region1 shapea</DD>
 </DL>
 </B><FONT SIZE=2><P>-- Delete <I>region1</I> and <I>shapea</I> from the MGED display. </P>
 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
+<DT><A NAME="erase_all"></A>erase_all</B> <I>&lt;objects</I>&gt;</DT>
+<DD>The &quot;erase_all&quot; command deletes the specified list of objects from the MGED display. This is a synonym for the <A HREF="#dall">dall</A> command.  This command will allow the user to delete objects that have not been explicitly displayed (unlike the <A HREF="#d">d</A> or <A HREF="#erase">erase</A> commands).  Note that this has no effect on the <I>BRL-CAD</I> database itself. To actually remove objects from the database, use the <A HREF="#kill">kill</A> command.</DD>
+<FONT SIZE=4><DT>Examples:</DT>
+</FONT><TT><DD>mged&gt;</TT> <B>erase_all region1 shapea</DD>
+</DL>
+</B><FONT SIZE=2><P>-- Delete <I>region1</I> and <I>shapea</I> from the MGED display. </P>
+<P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
 <DT><A NAME="ev"></A>ev</B> [<I>-dfnrstuvwST</I>] [<I>-P#</I>] [-C#/#/#] &lt;<I>objects</I>&gt;</DT>
 <DD>The &quot;ev&quot; command evaluates the <I>objects</I> specified by tessellating all <A HREF="#SOLID">primitive shapes</A> in the objects and then performing any <A HREF="#BOOLEAN">Boolean operations</A> specified in the <I>objects</I>. The result is then displayed in the MGED display according to the specified options:</DD>
 </DL>
@@ -1503,6 +1534,13 @@ l r230 r231 r232 r233 r234 r235 r236 r237 r238 r239 <BR>
 </B><FONT SIZE=2><P>-- Display a list of all database object names that end in &quot;.r&quot;. </P>
 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
+<DT><A NAME="export_body"></A>export_body <I>object file </DT>
+</B></I><DD>The &quot;export_body&quot; command is used to copy the contents of the specified binary <I>object</I> into the specified <I>file</I>.  Currently, only binary objects containing a uniform array of simple objects is supported. </DD>
+<DT></DT>
+<FONT SIZE=4><DD>Examples: </DD>
+</FONT><TT><DD>mged&gt;</TT> <B>export_body bin_chars /home/fred/chars</DD>
+</B><DD>-- Copy the contents of &quot;bin_chars&quot; into the file &quot;/home/fred/chars&quot;</DD>
+<DT><HR ALIGN="RIGHT"></DT>
 <DT><b><a name="expand_comb"></a>expand_comb <i>prefix comb ...</i></DT>
 <DD>The <i>expand_comb</i> will create a new combination object <i>prefix</i>.
 For each Boolean node in the original tree of the combination a new
@@ -2347,6 +2385,16 @@ foo.r_xpand/R

 </B><FONT SIZE=2><P>-- Rearrange the vertices of the currently edited <I>ARB</I> such that vertex #3 becomes vertex #1, vertex #2 remains #2, and vertex #1 becomes #3. </P></DIR>

+<P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
+<DT><A NAME="pl"></A>pl</B> [<I>-float</I>] [<I>-zclip</I>] [<I>-2d</I>] [<I>-grid</I>] <I>out_file</I> | &quot;|&quot; <I>filter</DT>
+</I><DD>The &quot;pl&quot; command creates a UNIX plot of the current MGED display.  If an <I>output_file</I> is specified, the plot is stored in that file.  If a <I>filter</I> is specified, the output is sent to that <I>filter</I>.  The <I>-float</I> option requests a plot file with real numbers rather than integers.  The <I>-zclip</I> option requests that the plot be clipped to the viewing cube in the Z-direction.  The <I>-2d</I> option requests a two-dimensional plot (the default is 3D). The <I>-grid</I> option is intended to include a grid in the plot, but is currently not implemented.  This command uses the <I>dm-plot</I> display manager.  The <A HREF="#plot">plot</A> command performs the same function, but does not use the <I>dm-plot</I> display manager.</DD>
+<FONT SIZE=4><DT>Examples:</DT>
+</FONT><TT><DD>mged&gt;</TT> <B>pl -float | pldebug</DD>
+</DL><DIR>
+
+</B><FONT SIZE=2><P>-- Create a UNIX plot of the current MGED display and pipe the results to the <I>pldebug</I> command.</P></DIR>
+
 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
 <DT><A NAME="plot"></A>plot</B> [<I>-float</I>] [<I>-zclip</I>] [<I>-2d</I>] [<I>-grid</I>] <I>out_file</I> | &quot;|&quot; <I>filter</DT>
@@ -2357,6 +2405,15 @@ foo.r_xpand/R

 </B><FONT SIZE=2><P>-- Create a UNIX plot of the current MGED display and pipe the results to the <I>pldebug</I> command. </P></DIR>

+<P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
+<DT><A NAME="polybinout"></A>polybinout</B> <I>file</DT>
+</I><DD>Store vlist polygons into polygon file (experimental).</DD>
+</DL>
+<FONT SIZE=2><P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
+<DT><A NAME="pov"></A>pov</B> <I>args</DT>
+</I><DD>Set the point-of-view (experimental).</DD>
 </DL>
 <FONT SIZE=2><P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
@@ -3478,6 +3535,15 @@ All textual arguments may be abbreviated by their first letter. </P>
 <DT><A NAME="vquery_ray"></A>vquery_ray</B> <I>x y</DT>
 </I><DD>Same as <A HREF="#vnirt">vnirt</A>.</DD>
 </DL>
+<FONT SIZE=2><P><HR ALIGN="RIGHT"></P>
+</FONT><B><DL>
+<DT><A NAME="vrmgr"></A>vrmgr</B> <I>host</I> {<I>master</I> | <I>slave</I> | <I>overview</I>}</DT>
+<DD>The &quot;vrmgr&quot; command establishes a link between the current MGED display and a <I>vrmgr</I> process running on the specified <I>host</I>.  The <I>vrmgr</I> program is a manager for virtual reality displays using MGED.  The <I>vrmgr</I> process must be started on <I>host</I> prior to executing the <I>vrmgr</I> command in MGED.  The second command line argument to the <I>vrmgr</I> command is the role of the current MGED display.  The <I>master</I> display controls the viewing parameters of itself and all the <I>slave</I> displays.  The <I>overview</I> display acts as an observer of the entire virtual reality process.</DD>
+<FONT SIZE=4><DT>Examples:</DT>
+</FONT><TT><DD>mged&gt;</TT> <B>vrmgr host1.brlcad.org master</DD>
+</DL><DIR>
+
+</B><FONT SIZE=2><P>-- Set the current MGED display as the <I>master</I> for the <I>vrmgr</I> process running on the host named <I>host1.brlcad.org.</I> </P></DIR>

 <P><HR ALIGN="RIGHT"></P>
 </FONT><B><DL>
@@ -1,2 +1,4 @@
 joint
+polybinout
+pov
 solids_on_ray
@@ -1007,6 +1007,7 @@
 ****** [[file:../doc/docbook/system/mann/en/facedef.xml][facedef.xml]]
 ****** [[file:../doc/docbook/system/mann/en/rcc-cap.xml][rcc-cap.xml]]
 ****** [[file:../doc/docbook/system/mann/en/quit.xml][quit.xml]]
+****** [[file:../doc/docbook/system/mann/en/vrmgr.xml][vrmgr.xml]]
 ****** [[file:../doc/docbook/system/mann/en/make.xml][make.xml]]
 ****** [[file:../doc/docbook/system/mann/en/whichair.xml][whichair.xml]]
 ****** [[file:../doc/docbook/system/mann/en/viewsize.xml][viewsize.xml]]
@@ -1036,6 +1037,7 @@
 ****** [[file:../doc/docbook/system/mann/en/attr.xml][attr.xml]]
 ****** [[file:../doc/docbook/system/mann/en/dup.xml][dup.xml]]
 ****** [[file:../doc/docbook/system/mann/en/eye_pt.xml][eye_pt.xml]]
+****** [[file:../doc/docbook/system/mann/en/dall.xml][dall.xml]]
 ****** [[file:../doc/docbook/system/mann/en/bot_split.xml][bot_split.xml]]
 ****** [[file:../doc/docbook/system/mann/en/copymat.xml][copymat.xml]]
 ****** [[file:../doc/docbook/system/mann/en/read_muves.xml][read_muves.xml]]
@@ -1072,7 +1074,7 @@
 ****** [[file:../doc/docbook/system/mann/en/preview.xml][preview.xml]]
 ****** [[file:../doc/docbook/system/mann/en/search.xml][search.xml]]
 ****** [[file:../doc/docbook/system/mann/en/brep.xml][brep.xml]]
-****** [[file:../doc/docbook/system/mann/en/erase.xml][erase.xml]]
+****** [[file:../doc/docbook/system/mann/en/erase_all.xml][erase_all.xml]]
 ****** [[file:../doc/docbook/system/mann/en/expand.xml][expand.xml]]
 ****** [[file:../doc/docbook/system/mann/en/xpush.xml][xpush.xml]]
 ****** [[file:../doc/docbook/system/mann/en/pull.xml][pull.xml]]
@@ -1081,6 +1083,7 @@
 ****** [[file:../doc/docbook/system/mann/en/l.xml][l.xml]]
 ****** [[file:../doc/docbook/system/mann/en/handle.xml][handle.xml]]
 ****** [[file:../doc/docbook/system/mann/en/edmater.xml][edmater.xml]]
+****** [[file:../doc/docbook/system/mann/en/export_body.xml][export_body.xml]]
 ****** [[file:../doc/docbook/system/mann/en/tol.xml][tol.xml]]
 ****** [[file:../doc/docbook/system/mann/en/exists.xml][exists.xml]]
 ****** [[file:../doc/docbook/system/mann/en/title.xml][title.xml]]
@@ -3824,6 +3827,7 @@
 *** [[file:../src/libged/comb_std.c][comb_std.c]]
 *** [[file:../src/libged/mater.c][mater.c]]
 *** [[file:../src/libged/prcolor.c][prcolor.c]]
+*** [[file:../src/libged/pov.c][pov.c]]
 *** [[file:../src/libged/inside.c][inside.c]]
 *** [[file:../src/libged/rot.c][rot.c]]
 *** [[file:../src/libged/bot_face_sort.c][bot_face_sort.c]]
@@ -4093,6 +4097,7 @@
 *** [[file:../src/libged/nmg_mm.c][nmg_mm.c]]
 *** [[file:../src/libged/red.c][red.c]]
 *** [[file:../src/libged/nmg_kill_f.c][nmg_kill_f.c]]
+*** [[file:../src/libged/polybinout.c][polybinout.c]]
 *** [[file:../src/libged/zoom][zoom]]
 **** [[file:../src/libged/zoom/zoom.c][zoom.c]]
 *** [[file:../src/libged/pmodel2view.c][pmodel2view.c]]
@@ -12811,6 +12816,7 @@
 *** [[file:../regress/mged/rotobj.mged][rotobj.mged]]
 *** [[file:../regress/mged/i.mged][i.mged]]
 *** [[file:../regress/mged/run_test][run_test]]
+*** [[file:../regress/mged/dall.mged][dall.mged]]
 *** [[file:../regress/mged/mvall.mged][mvall.mged]]
 *** [[file:../regress/mged/center.mged][center.mged]]
 *** [[file:../regress/mged/push.mged][push.mged]]
@@ -44,8 +44,8 @@
 /** @file bg.h */
 /** @} */

-#ifndef BG_H
-#define BG_H
+#ifndef GM_H
+#define GM_H

 #include "common.h"

@@ -56,7 +56,7 @@
 #include "bg/tri_ray.h"
 #include "bg/tri_tri.h"

-#endif /* BG_H */
+#endif /* GM_H */

 /*
 * Local Variables:
@@ -18,8 +18,8 @@
 * information.
 */

-#ifndef BN_DVEC_H
-#define BN_DVEC_H
+#ifndef DVEC_H
+#define DVEC_H

 #include "common.h"

@@ -207,7 +207,7 @@ extern "C++" {

 /** @} */

-#endif /* BN_DVEC_H */
+#endif /* DVEC_H */

 /*
 * Local Variables:
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
Clifford Yapp	06c791b764	Need more planning before attempting any major rework of this sort. (svn branch delete) svn:revision:68259 svn:branch:multiproj svn:account:starseeker	2016-07-12 16:25:55 +00:00
Clifford Yapp	76ed837546	More refactor work. svn:revision:67656 svn:branch:multiproj svn:account:starseeker	2016-04-19 00:33:15 +00:00
Clifford Yapp	1cad8fcbe3	random includes of CMake functionality... svn:revision:67655 svn:branch:multiproj svn:account:starseeker	2016-04-18 18:02:47 +00:00
Clifford Yapp	f21f329b16	Factor out more individual pieces. svn:revision:67654 svn:branch:multiproj svn:account:starseeker	2016-04-18 17:49:30 +00:00
Clifford Yapp	69297ea941	Don't need the liblib override in the general add_library override. svn:revision:67653 svn:branch:multiproj svn:account:starseeker	2016-04-18 16:39:10 +00:00
Clifford Yapp	46f742eb84	Start modularizing the top level CMakeLists.txt file into discreet functionality chunks. svn:revision:67652 svn:branch:multiproj svn:account:starseeker	2016-04-18 15:17:41 +00:00
Clifford Yapp	7572914650	Make a branch to do some fairly invasive experiments with the CMake logic. svn:revision:67651 svn:branch:multiproj svn:account:starseeker	2016-04-18 13:38:50 +00:00