Compare commits

..
2 Commits
Author SHA1 Message Date
Clifford Yapp fe2508606b Fully merged - deleting bullet branch, since from here it should be practical to complete the simulate work and Windows bullet building in trunk. (svn branch delete)
svn:revision:62698
svn:branch:bullet
svn:account:starseeker
2014-09-12 15:22:01 +00:00
Clifford Yapp 7b78a19da1 Sync with trunk thru r62694
svn:revision:62696
svn:branch:bullet
svn:account:starseeker
2014-09-12 14:51:54 +00:00
7312 changed files with 211835 additions and 1423350 deletions
+7 -89
View File
@@ -37,7 +37,7 @@ contributor credits are organized into the following general
categories depending on the level and type of involvement:
* Mathematical, Algorithmic, and Geometric Support
* Documentation, Artwork, and Website Contributors
* Documentation and Website Contributors
* Code Contributors
* Special Thanks
@@ -268,8 +268,8 @@ Weaver, Stephanie 'Rain' **
ARL Student Hire / Bridgewater College
DOCUMENTATION, ARTWORK, AND WEBSITE CONTRIBUTORS
------------------------------------------------
DOCUMENTATION AND WEBSITE CONTRIBUTORS
--------------------------------------
Weaver, Earl P.
1980
@@ -334,25 +334,6 @@ Perez, Alex
2012 November
Open Source (GCI)
Tannous, Marc
2014 December
Open Source (GCI)
Chiplunkar, Shardul
nicknames microchip, shardulc
2014 December
Open Source (GCI)
Juvekar, Mandar
nicknames mandarj
2014 December
Open Source (GCI)
Sofat, Hitesh
nicknames sofat
2015 June
Open Source (GSoC)
CODE CONTRIBUTIONS
------------------
@@ -481,9 +462,7 @@ nicknames mjgillich mgillich
U.S. Army Research Laboratory
Howard, Doug
nicknames dhoward
SURVICE Engineering, Inc.
2006 April
Silva, Prasad Prometheus
nicknames prasad_silva
@@ -537,7 +516,7 @@ nicknames homovulgaris, madant
Open Source (GSoC)
Saunders, Benjamin
nicknames Ralith, ralith
nicknames Ralith
2008 July
Open Source
@@ -577,10 +556,6 @@ Jain, Sachin
2011 April
Open Source
Gerstner, Nick
2011 May
SURVICE Engineering, Inc.
Easterbrook, Zach
nicknames lainiwakurax
2011 July
@@ -711,12 +686,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)
@@ -745,7 +720,6 @@ Schulte, Johannes
Open Source (GCI)
Amidon, Peter
nicknames peter-sa, Andromeda Galaxy
2013 November
Open Source (GCI)
@@ -779,47 +753,6 @@ nicknames klinger4077
2014 July
ARL Student Hire / University of Maryland College Park
Mirea, Ștefan-Gabriel
2014 October
Open Source
Krishna
2015 January
Open Source (GCI)
Konrad, Djimeli
2015 February
Open Source
Alexandre da Silva Costa, Vasco
nicknames vasco_costa
2015 April
Open Source (GSoC)
Thakkar, Kalpit
nicknames dracarys983
2015 May
Open Source (GSoC)
Ilinca, Andrei
nicknames andrei_il
2015 June
Open Source (GSoC)
Sofat, Hitesh
nicknames sofat
2015 June
Open Source (GSoC)
Hollister, Brad
nicknames bhollister
2015 July
Open Source (GSoC)
Hanji, Param
2016 March
Open Source (GSoC)
SPECIAL THANKS
--------------
@@ -951,7 +884,7 @@ Thomas, Balbir
Open Source
Remenak, Daniel T.
nicknames DTRemenak, Erroneous, dtremenak
nicknames DTRemenak, Erroneous
2005 July
California Institute of Technology
Open Source
@@ -1111,21 +1044,6 @@ nicknames dhyams
2014 February
Open Source
Reddy, Raj
nicknames raj12lnm
2014 May
Open Source
Malhotra, Shivoam
nicknames shiv05
2015 March
Open Source
Chepkwony, Benson
nicknames bchepkwny
2015 December
Open Source
CORPORATE AND ORGANIZATION SUPPORT
----------------------------------
+23 -37
View File
@@ -15,47 +15,28 @@ on-going issues.
Recent Bugs
-----------
* rtedge's overlay mode appears to be generating different results on
Windows and Linux for the m35 steering wheel (rtwizard rendering
mode D.)
* pixdiff on Windows is reporting no differences with a pair of files
that pixcmp can see differences in.
* fblabel seems quite busted, at least talking to a /dev/X fbserv, in
that it only draws the first character and eventually displays
rem_read() failures when run in -d debug mode.
* rtedge doesn't refresh a /dev/X fbserv (presumably double-buffered)
after doing an overlay render. it does draw, though, as confirmed
by a forced fb-fb refresh.
* pixborder doesn't account for an edge case where the right edge of
an image is expected to be colored (except for one pixel on the top
edge). Example:
pixborder -b "255 0 0" -t "255 255 255" < pix/moss.pix | pix-fb
* report that attempting to change units on a read-only file in MGED
will not change the units in the file but changes them in MGED,
resulting in problems with nirt missing geometry it shouldn't miss.
* typing 'comb -f -r assembly_name' shuts down mged with the error:
ERROR: bad pointer 0000000000B4CA50: s/b bu_external(x768dbbd0), was bu_vls(x89333bbb), file ..\..\..\brlcad_src\src\libbu\parse.c, line 2443"
And on the mged command line:
rt_db_cvt_to_external5 expecting non-NULL name parameter
wdb_export((null)): solid export failure
* report of mged command history not working with the down arrow key
in 7.25.0 (on Windows, unknown on other platforms). Up arrow works
fine.
* wgl framebuffer is not lingering on windows (regardless of using
wgll or default) when it should
* sh_text.c: texture mapping crashes (in txt_render() near line 318)
if you specify image dimensions larger than the texture file. it
gets back a mapped file, but indexes directly based on the provided
sizes without bounds checking.
* count_non_union_ops() in g-iges crashes with simple conversion case
* gqa bypasses rt_dirbuild() so it never sets rt_bot_mintie nor uses
TIE when the environment variable is set.
* nirt -e "xyz val val val" doesn't work due to the space after the -e
and how the nirt/rt commands parse quoted args.
* probably related, there is a big parsing difference between nirt
with "xyz 1.0 2.0 3.0; dir 0 -1 0;" and "xyz 1. 2. 3. ; dir 0 -1
0;". note the intentional space. problem observed is that center
point ended up being "0.0 2.0 0.0" with there clearly being a
parsing error depending on where the semicolon was positioned.
* calling "attr set obj key value" should always result in key getting
set to value, no matter what, as it is the lowest-level attribute
management interface and what the command (correctly) documents.
@@ -113,6 +94,11 @@ Recent Bugs
* idents command is reporting a bogus region count in the region
output table listing (first column).
* yacc 1.9 will not output a header if a path is given to the -o
option. yacc should be run from the binary directory instead of the
source directory so that the command may be simply yacc -d -o
points_parse.c ${CMAKE_SOURCE_DIRECTORY}/points_parse.y
* src/librt/primitives/bot/g_bot_include.c:rt_bot_bbox() routine isn't
calculating the bbox correctly
@@ -146,8 +132,8 @@ Recent Bugs
* bu_log() with a width specifier does not align like printf().
Example: bu_log("%24s", str);
* report that "keep" sometimes results in a .g file with unknown units;
dbconcat also is reported to set the units to unknown if concatting
* report that keep sometimes results in a .g file with unknown units
dbconcat also is reported to set the units to unknown if concating
a file with unknown units.
* infinite loop in rt_find_backing_dist() raytracing a BoT (without
+44 -244
View File
@@ -50,7 +50,7 @@ DEPRECATION POLICY
If a change will intentionally alter, replace, or remove functionality
that has been documented and published in at least TWO releases, it
must first be announced as DEPRECATED. Otherwise, changes to
should mut first be announced as DEPRECATED. Otherwise, changes to
interfaces that have not been publicly announced or are not publicly
documented for at least two releases may be changed without notice.
@@ -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,131 +112,33 @@ 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 : unnecesary 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]
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]
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
include/bn.h
tp_setup, no longer needs to be public API [deprecated 7.26]
include/raytrace.h
curve_to_tcl_list
db_full_path_appendresult tcl_obj_to_int_array
tcl_obj_to_fastf_array tcl_list_to_int_array
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]
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]
7.24
----
include/bu
hist.h bu_hist bu_hist_t BU_HIST_NULL BU_HIST_INIT_ZERO [deprecated 7.24]
BU_HIST_IS_INITIALIZED BU_HIST_TALLY BU_HIST_TALLY_MULTIPLE [deprecated 7.24]
bu_hist_free bu_hist_init bu_hist_range bu_hist_pr [deprecated 7.24]
functions, macros, and header will be renamed for clarity [deprecated 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,9 +147,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]
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]
@@ -287,6 +189,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]
@@ -355,42 +259,23 @@ 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]
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
@@ -422,7 +307,7 @@ 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_[toolname] -> g[toolname] [deprecated 7.14]
src/librt/cmd.c
@@ -439,9 +324,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
------
@@ -617,8 +499,6 @@ may need adjustment (particularly quoting of '(', ')', and '|'
characters) for other environments. Most expressions will apply with:
perl -0777 -pi -e 'EXPRESSION' FILE
To apply them to an entire SVN checkout, the following pattern is useful:
find . -type f -not -path "*.svn/*" -regex '.*\(c\|cpp\|cxx\|h\|hpp\)$' -exec perl -0777 -pi -e 'EXPRESSION' {} \;
6.0 (sed lines)
---
@@ -1075,23 +955,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
@@ -1100,7 +980,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
@@ -1112,101 +992,21 @@ 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]
s/(#[[:space:]]*include[[:space:]]+["<])fbio\.h/\1bu\/fb.h/g
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]
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
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]
s/(#[[:space:]]*include[[:space:]]+["<])bot\.h/\1rt\/primitives\/bot.h/g
consolidate bot header contents [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])anim\.h/\1bn\/anim.h/g
consolidate anim header contents [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])plot3\.h/\1bn.h/g
plot3 implementation is in libbn, move header and replace plot3.h with bn.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])vectfont\.h/#define LAST -128\n\1bn\/vectfont.h/g
consolidate vectfont.h files [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])spm\.h/\1bn\/spm.h/g
move spm.h into bn subheader directory [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])dvec\.h/\1bn\/dvec.h/g
s/(#[[:space:]]*include[[:space:]]+["<])vector_fpu\.h/\1bn\/vector_fpu.h/g
s/(#[[:space:]]*include[[:space:]]+["<])vector_x86\.h/\1bn\/vector_x86.h/g
move dvec.h and friends into bn subheader directory [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])db\.h/\1rt\/db4.h/g
move db.h to rt/db4.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])db5\.h/\1rt\/db5.h/g
move db5.h to rt/db5.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])mater\.h/\1raytrace.h/g
merge mater.h with rt/mater.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])nurb\.h/#include "raytrace.h"\n\1rt\/nurb.h/g
move nurb.h to rt/nurb.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])rtfunc\.h/#include "raytrace.h"\n\1rt\/func.h/g
move rtfunc.h to rt/func.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])tol\.h/#include "bn.h"\n#include "raytrace.h"\n\1rt\/tol.h/g
consolidate tol.h and rt/tol.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])tie\.h/\1rt\/tie.h/g
move tie.h to rt/tie.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])solid\.h/#include "raytrace.h"\n\1rt\/solid.h/g
move solid.h to rt/solid.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])shadework\.h/\1optical\/shadework.h/g
move shadework.h to optical/shadework.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])shadefuncs\.h/\1optical.h/g
move shadefuncs.h to optical/shadefuncs.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])light\.h/#include "bn.h"\n#include "raytrace.h"\n\1optical\/light.h/g
move light.h to optical/light.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])plastic\.h/\1optical\/plastic.h/g
move plastic.h to optical/plastic.h [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])rtgeom\.h/\1rt\/geom.h/g
move rtgeom.h to rt/geom.h [7.25]
s/rt_vlist_get_cmd_description/bn_vlist_get_cmd_description/g
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]
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]
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]
no longer need to manually reinitialize (or initialize) semaphores [7.25]
s/(#[[:space:]]*include[[:space:]]+["<])fbio\.h/\1bu\/fb.h/g [7.25]
+324 -600
View File
File diff suppressed because it is too large Load Diff
+1 -1
View File
@@ -101,7 +101,7 @@ arranged. This includes an implicit assignment of copyright for any
and all contributions being made. The following notice should be
prominent in the BRL-CAD sources:
Copyright (c) 1984-2016 United States Government as represented by
Copyright (c) 1984-2014 United States Government as represented by
the U.S. Army Research Laboratory.
Contact
-15
View File
@@ -1,15 +0,0 @@
## This file should be placed in the root directory of your project.
## Then modify the CMakeLists.txt file in the root directory of your
## project to incorporate the testing dashboard.
##
## # The following are required to submit to the CDash dashboard:
## ENABLE_TESTING()
## INCLUDE(CTest)
set(CTEST_PROJECT_NAME "BRL-CAD")
set(CTEST_NIGHTLY_START_TIME "06:00:00 UTC")
set(CTEST_DROP_METHOD "http")
set(CTEST_DROP_SITE "brlcad.org")
set(CTEST_DROP_LOCATION "/CDash/submit.php?project=BRL-CAD")
set(CTEST_DROP_SITE_CDASH TRUE)
+11185 -41809
View File
File diff suppressed because it is too large Load Diff
+40 -34
View File
@@ -240,28 +240,18 @@ accuracy-oriented ray intersection, geometric analysis, and geometry
representation library that supports a wide variety of geometric
forms. Geometry can be grouped into combinations and regions using
CSG boolean operations.
Depends on: libbn libbu libregex libm (openNURBS)
Depends on: libbn libbu libtcl libregex libm (openNURBS)
libbu: The BRL-CAD Utility library contains a wide variety of routines
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
Depends on: libtcl (threading) (malloc)
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
Depends on: libbu libtcl libm
libcursor: The cursor library is a lightweight cursor manipulation
library similar to curses but with less overhead.
@@ -298,12 +288,30 @@ models, as well as various visual effects such as texturing, marble,
wood graining, air, gravel, grass, clouds, fire, and more.
Depends on: librt libbn libbu libtcl
liborle: The "old" run-length encoding library that will decode and
encode University of Utah Raster Toolkit format Run-Length Encoded
data.
Depends on nothing
libpkg: The "Package" library is a network communications library that
supports multiplexing and demultiplexing synchronous and asynchronous
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
libsysv: The System 5 compatibility library exists to support legacy
systems that lack functionality required by BRL-CAD. This library is
deprecated and should generally not be used for new development.
Depends on nothing
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 +432,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
@@ -580,7 +587,6 @@ variables should be utilized instead of the standard C facility:
bu_optind instead of optind
bu_optopt instead of optopt
bu_optarg instead of optarg
bu_strdup() instead of strdup()
bu_strlcat() instead of strcat(), strncat(), and strlcat()
bu_strlcpy() instead of strcpy(), strncpy(), and strlcpy()
bu_strcmp() and BU_STR_EQUAL() instead of strcmp()
@@ -875,10 +881,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
@@ -979,11 +981,11 @@ granted after a contributor demonstrates strong competency with our
developer guidelines and an existing developer with commit access
vouches for the new developer.
If you would like to have commit access, do not ask for it. Getting
involved with the other contributors and making patches will result in
automatic consideration for commit access. That said, the following
steps represent a minimum that needs to occur in order for commit
access to be granted:
If you would like to have commit access, there is no need to ask.
Getting involved with the other contributors and making patches will
result in automatic consideration for commit access. That said, the
following steps represent a minimum that needs to occur in order for
commit access to be granted:
1) Read this file completely.
@@ -993,7 +995,7 @@ access to be granted:
4) Create a SourceForge account, submit at least two patches that
demonstrate competency with our coding style, apply flawlessly, and
provide some significant improvement.
provide some signficant improvement.
5) Get to know the other developers. One of them will need to vouch
for your commit access.
@@ -1275,7 +1277,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
@@ -1473,6 +1475,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)
-406
View File
@@ -1,349 +1,3 @@
The Installation Guide to BRL-CAD
=================================
Please read this document if you are interested in installing BRL-CAD.
This document covers the basics of installing BRL-CAD from either a
source or binary distribution. Please see the 'Reporting Problems'
section if you run into any trouble installing BRL-CAD.
Some platforms have additional platform-specific documentation
provided in the doc/ directory of the source distribution that should
be consulted if that is the platform you are installing on. This
presently includes the following:
doc/README.AIX -- IBM's Advanced Interactive eXecutive OS
doc/README.BSD -- FreeBSD, NetBSD, OpenBSD, etc.
doc/README.IRIX -- SGI IRIX and IRIX64
doc/README.Linux -- Various Linux distributions
doc/README.MacOSX -- Apple Mac OS X
doc/README.Solaris -- Oracle Solaris, OpenIndiana (Illumos), etc.
doc/README.Windows -- Microsoft Windows
doc/README.VAX -- Virtual Address eXtension architecture from DEC.
One of the original BRL-CAD platforms. These
days, re-created using the simh simulator.
TABLE OF CONTENTS
-----------------
Introduction
Table of Contents
Quick Installation
Installing from Binary
Installing from Source
Testing Functionality
Post-Installation
Reporting Problems
Configuration Options
QUICK INSTALLATION
------------------
Note that the downloaded files have two check sums calculated
automatically by the Source Forge file release system. The values are
used to verify the integrity of the files as distributed. Get those
data by clicking on the 'i' button at the end of each file's name.
You should ensure those data are retained and kept with the files if
you re-distribute them.
If you downloaded a binary distribution of BRL-CAD for your system,
please read the INSTALLING FROM BINARY section of this document down
below. The rest of this quick installation section is only relevant
to source code distributions of BRL-CAD.
For the impatient or simplistic, the following steps should compile,
test, and install an optimized BRL-CAD quickly into the /usr/brlcad/rel-X.Y.Z
directory if CMake is installed on your system:
gunzip brlcad-X.Y.Z.tar.gz
tar -xvf brlcad-X.Y.Z.tar
mkdir brlcad-build
cd brlcad-build
cmake ../brlcad-X.Y.Z -DBRLCAD_BUNDLED_LIBS=ON -DCMAKE_BUILD_TYPE=Release
make
make benchmark
make regress
make install # as root, e.g. sudo make install
If any of the listed steps fail, then something unexpected happened.
See the REPORTING PROBLEMS section of this document to report the
problem or the INSTALLING FROM SOURCE section for more comprehensive
instructions.
Once installed, add /usr/brlcad/rel-X.Y.Z/bin to your path, and you should be
able to run any of the 400+ applications that constitute BRL-CAD. For
example, to run the MGED solid modeler:
PATH=/usr/brlcad/rel-X.Y.Z/bin:$PATH ; export PATH
mged
If you use tcsh or another C-shell based command shell, use this
instead:
set path=( /usr/brlcad/rel-X.Y.Z/bin $path ) ; rehash
mged
INSTALLING FROM BINARY
----------------------
There are a variety of different kinds of binary distributions of
BRL-CAD. Some of the binary distributions are sufficiently generic and
are simply a binary compressed tarball distribution. Others are
specific to a particular platform such as Debian, Mac OS X, FreeBSD,
and Windows etc.
Generic Binary Distributions:
For the unspecialized binary distributions that are basically
compressed tarballs of the installation root, they should contain the
entire hierarchy of the distribution. To put that hierarchy in its
"installed" location, you just create the directory and move the
expanded tarball contents:
gunzip BRL-CAD_7.2.4_Linux_ia64.tar.gz
tar -xvf BRL-CAD_7.2.4_Linux_ia64.tar
sudo mkdir /usr/brlcad/rel-7.2.4
sudo mv BRL-CAD_7.2.4_Linux_ia64/* /usr/brlcad/rel-7.2.4/
Of course, there are other compression options possible including zip
and bzip2. By default, BRL-CAD expects to be installed into
/usr/brlcad/rel-7.2.4. On some platforms the binary may be relocatable,
but this is not guaranteed. It's recommended that you start from a source
distribution if you would like to install into an alternate installation
location. That said, if you do desire to install and/or run BRL-CAD from
a different location, give it a try...on some platforms it will work.
Something to be aware of, even if a binary distribution IS relocatable:
it will use its local copies of things like libraries only so long as the
"final" installed target directory that the build was compiled for
does not contain a BRL-CAD installation. Due to the way path logic
is set, an installed copy of a library in the correct location will
always be loaded first, regardless of the presence of a "local" copy.
Mac OS X Disk Mounting Image:
Mount the .dmg and run the Installer .pkg contained therein. This
will install into /usr/brlcad/rel-X.Y.Z and will only require confirming that
your environment is set up properly (i.e. add /usr/brlcad/rel-X.Y.Z/bin to your
path) as described in the Quick Installation section.
INSTALLING FROM SOURCE
----------------------
There are a couple of ways to obtain the BRL-CAD sources, usually via
one of the following starting points:
1) from a SVN checkout/export, or
2) from a source distribution tarball
Using the latest SVN sources is recommended where possible since it
will have the latest changes. See the corresponding section below for
details on how to install from either starting point.
Starting From a SVN Checkout/Export:
With CMake, there is no longer any difference between building from
a subversion checkout and a tarball--follow the Source Distribution
instructions below.
Starting From a Source Distribution:
There are many different ways to build BRL-CAD and depending on what
you need/want will determine which configuration options you should
use. See the CONFIGURATION OPTIONS section below for details on how
to go about selecting which options are appropriate for you.
By default, the default configuration will prepare the build system
to perform a Debug build and install into the /usr/brlcad/dev-X.Y.Z
directory. The CMAKE_INSTALL_PREFIX option may be used to change
that directory, or a Release build type may be specified to install to
/usr/brlcad/rel-X.Y.Z - more on this below. The
tradition of non-system installation paths goes back a couple of decades
and is a convenient means to isolate the BRL-CAD solid modeling
system from your system, resolves conflicts, facilitates uninstalls,
and simplifies upgrades. The default configuration is performed by
running `cmake'. It is not required to do the build in a directory
different from your source directory, but it is much cleaner and
*highly* recommended - this guide will illustrate the build process
with the assumption that the BRL-CAD source code is in the directory
brlcad-7.2.4 and the directory intended to hold the build output is
brlcad-build, located in the same parent directory as brlcad-7.2.4:
.
./brlcad-7.2.4
./brlcad-build
To start the build process, cd into brlcad-build and run CMake,
pointing it to the source directory:
cd brlcad-build
cmake ../brlcad-7.2.4
As mentioned earlier, CMake uses two "build types", controlled by
the CMAKE_BUILD_TYPE variable, that are useful for specific purposes:
* Debug (-DCMAKE_BUILD_TYPE=Debug) - Debug is the configuration that most
developers will want to use when working on BRL-CAD. It will add
debug flags to the compile, and sets the default install directory to
be /usr/brlcad/dev-X.Y.Z - in order to run the resulting installed
binaries, the developer should ensure that the dev-X.Y.Z path is
first in his or her PATH environment variable.
* Release (-DCMAKE_BUILD_TYPE=Release) - A release build is intended for
final consumption by end users and as such has optimizations enabled.
It also sets the install path to /usr/brlcad/rel-X.Y.Z - best practice
for release installation is to set up symbolic links in /usr/brlcad to
point to the most current BRL-CAD release, while allowing older versions
to remain installed on the system in case they are needed.
In both of these cases any individual variable may be overridden - for
example, setting -DCMAKE_INSTALL_PREFIX=/usr/brlcad in a Debug build will
override the ../brlcad-install default. Build types are a convenient way
to bundle sets of settings, but they do not prevent overrides if a more
custom setup is needed.
By default, all components and functionality will be built.
Note that BRL-CAD does require and include several 3rd party
components. If your system does not include a sufficient version of
those required 3rd party components, they will be automatically
configured for compilation.
If the autodetection mechanisms fail to produce a working configuration,
the next simplest approach is typically to enable ALL the third party
components - this is typically a well tested configuration, but will
increase both the build time and final install size of BRL-CAD on
the system. To set this variable on the command line, use -D to
define BRLCAD_BUNDLED_LIBS for CMake:
-DBRLCAD_BUNDLED_LIBS=Bundled
If the graphical interface (cmake-gui) is in use, it will list this
and other common options by default, allowing the user change them
graphically. This is often quicker and more convenient than
defining options on the command line, but both will work.
You can also force on or off any individual 3rd party library by
setting the BRL-CAD variable for that feature to either on or off:
-DBRLCAD_<LIBRARY>=ON
Other variables control BRL-CAD features. For example, to NOT
enable functionality using OpenGL, set
-DBRLCAD_ENABLE_OPENGL=OFF
To obtain an optimized build (for example, for BRL-CAD Benchmark
performance evaluation), enable BRLCAD_FLAGS_OPTIMIZATION:
-DBRLCAD_FLAGS_OPTIMIZATION=ON
See the CONFIGURATION OPTIONS below for more details on all of the
possible settings.
You can specify options or preferences you want to always use by
default. For example, to always enable all local libs the following
line can be added to your own configuration file:
set(BRLCAD_BUNDLED_LIBS "Bundled" CACHE STRING "Enable all local libs")
You can define your own configuration file in one of three ways. The
build system will search for the file in this order:
${BRLCAD_SOURCE_DIR}/../BRL-CAD_CONFIG.GLOBAL
${BRLCAD_SOURCE_DIR}/BRL-CAD_CONFIG.GLOBAL
the file defined in the environment variable "BRLCAD_USER_GLOBAL_CONFIG_FILE"
The build system will use the first file defined that exists.
Once configured, you should be able to successfully build BRL-CAD via
make:
make
(On multicore systems, adding the -j flag (e.g. -j6) is recommended)
Installing the Compilation:
After the build successfully completes and assuming the benchmark also
produces correct results, installation may begin. Like any package,
you must have sufficient filesystem permissions to install. To
install into a system location, you can generally either become a
super user via the su command and run
make install
or on operating systems set up to use sudo:
sudo make install
TESTING FUNCTIONALITY
---------------------
To test BRL-CAD before installation, you can run the BRL-CAD benchmark.
The benchmark will report if the results are correct, testing a
majority of the core functionality of BRL-CAD in addition to testing
your system's performance:
make benchmark
Note that the benchmark target will build ONLY the pieces required for
the benchmark tests, unless a general make has already been performed.
For more testing, you can run the regression test suite:
make regress
POST-INSTALLATION
-----------------
Permissions:
Something to be aware of with CMake installations is that umask settings
are ignored by current versions of CMake. It is a common situation in
Unix environments to want "group" members to have read/write access -
to achieve this, after installation the following find command can be
run (of course, substituting the actual BRL-CAD version for X.Y.Z):
find /usr/brlcad/rel-X.Y.Z -type d -exec chmod ug+rwx {} \; -exec chmod o+rx {} \; -o -type f -exec chmod ug+rw {} \; -exec chmod o+r {} \;
The above 'find' line will set up permissions across a /usr/brlcad
rooted installation such that 'user' and 'group' will have read-write
access and 'other' will have read access consistently across all
files.
System PATH:
Normally, BRL-CAD's install directories are not in system PATH lists and
consequently BRL-CAD's executables will not be invokable without specifying
their full path. This is normally handled in Unix environments by adding
the desired BRL-CAD installation's binary directory to the user's local path:
In the bash shell: export PATH=/usr/brlcad/rel-X.Y.Z:$PATH
In the csh shell: setenv PATH /usr/brlcad/rel-X.Y.Z:$PATH
REPORTING PROBLEMS
------------------
Please report any bugs encountered to the project bug tracker at
http://sourceforge.net/tracker/?group_id=105292&atid=640802
Similarly, please post any request for feature enhancements or support
to http://sourceforge.net/tracker/?group_id=105292&atid=640805 and
http://sourceforge.net/tracker/?group_id=105292&atid=640803
respectively.
CONFIGURATION OPTIONS
---------------------
@@ -536,26 +190,6 @@ first for a system version if BRLCAD_BUNDLED_LIBS is also AUTO.
Aliases: ENABLE_ZLIB, ENABLE_LIBZ
--- BRLCAD_TINYCTHREAD ---
Option for enabling and disabling compilation of the tinycthread library
provided with BRL-CAD's source distribution. 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_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
@@ -568,16 +202,6 @@ disabled. Windows does not support the termlib API.)
Aliases: ENABLE_TERMLIB
--- BRLCAD_NETPBM ---
Option for enabling and disabling compilation of the netpbm library
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_NETPBM
--- BRLCAD_PNG ---
Option for enabling and disabling compilation of the Portable Network
@@ -712,16 +336,6 @@ version if BRLCAD_BUNDLED_LIBS is also AUTO.
Aliases: ENABLE_OPENNURBS
--- BRLCAD_SPR ---
Option for enabling and disabling compilation of the PoissonRecon library
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_SPR
--- BRLCAD_SC ---
Option for enabling and disabling compilation of the NIST Step Class
@@ -732,16 +346,6 @@ first for a system version if BRLCAD_BUNDLED_LIBS is also AUTO.
Aliases: ENABLE_SCL, ENABLE_STEP, ENABLE_STEP_CLASS_LIBRARIES
--- BRLCAD_GECODE ---
Option for enabling and disabling compilation of the Gecode Constraint
Solving 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_GECODE
--- BRLCAD_VDS ---
Option for enabling and disabling compilation of the libvds triangle
@@ -753,16 +357,6 @@ AUTO.
Aliases: ENABLE_VDS
--- BRLCAD_OSG ---
Option for enabling and disabling compilation of the OpenSceneGraph
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_OPENSCENEGRAPH
--- BRLCAD_GDIAM ---
Option for enabling and disabling compilation of the libgdiam approximate
+9 -135
View File
@@ -9,125 +9,11 @@ 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 ---
----------------------------------------------------------------------
----------------------------------------------------------------------
--- 2016-06-XX Release 7.26.0 ---
--- 2014-XX-XX Release 7.26.XX ---
----------------------------------------------------------------------
This major release update of BRL-CAD culminates several years of
development efforts to provide robust boundary representation (BREP)
NURBS import and ray tracing support. Our NURBS capability gets us a
step closer to full hybrid representation modeling, supporting
seamless transitioning and mixing of boundary representation geometry
(e.g., NURBS or polygonal meshes) with implicit representation
geometry (e.g., primitives with CSG).
* added manual page for lt comb child listing command - Cliff Yapp
* added lt -c option for specifying separation character - Bob Parker
* mass-deprecation of 121 command-line utilities - BRL-CAD Developers
* 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
* 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
* minor rtwizard graphical user interface reorganization - Cliff Yapp
* 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
* removed -I interactive option from rt/rtedge/remrt - Sean Morrison
* 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 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
* added 'arb8' surface area value to analyze command - Kalpit Thakkar
* added 'part' centroid reporting to analyze command - Brad Hollister
* added new pixcrop utility for cropping pix images - Carl Moore
* preliminary OpenCL-accelerated coherent 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 help option consistency across numerous tools - Carl Moore
* added prefatory FASTGEN4 geometry export support - Jon Engbert
* 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
* modernized documents and improved infrastructure - Hitesh Sofat
* added mirroring support for hrt primitive objects - Isaac Kamga
* 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 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
* added globbing support to attr command - Cliff Yapp
* added lc -0 option to return objects in tree order - Sean Morrison
* fixed crash in iges-g importer due to parsing error - Ștefan Mirea
* fixed corrupt output generated by iges-g importer - Ștefan Mirea
* 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
* 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
@@ -136,8 +22,6 @@ geometry (e.g., primitives with CSG).
* 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
@@ -147,10 +31,10 @@ geometry (e.g., primitives with CSG).
- 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 -v verbose output option to mged 'search' command - Cliff Yapp
* added -v verbose output option to MGED 'search' command - Cliff Yapp
* fixed g_lint and pixcount red-black tree memory leaks - Tom Browder
* fixed crash of extrude with special case bezier curves - huskmate13
* improved performance of 'terrain' & numerous shaders - Sean Morrison
@@ -158,21 +42,11 @@ geometry (e.g., primitives with CSG).
* added key binding to reopen/focus mged command window - Emory Huff
* added menu option to restore mged command window - Cezar Elnazli
* search command now recognizes hyp and metaball types - Cliff Yapp
* 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
* added -depth option to MGED 'search' command - Cliff Yapp
* improved 'search' with 'flat' search path modifier - Cliff Yapp
* improved 'search' with above/equal/below depth limits - Cliff Yapp
* 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
----------------------------------------------------------------------
--- 2015-08-31 Release 7.24.4 ---
----------------------------------------------------------------------
* initial support for datum points, lines, and planes - Sean Morrison
----------------------------------------------------------------------
@@ -202,7 +76,7 @@ improved geometry interchange with other CAD systems.
* improved pipe ray tracing grazing hit behavior - Keith Bowman
* upgraded libpng, now at version 1.6.10 - Erik Greenwald, Cliff Yapp
* improved solid NURBS geometry ray tracing behavior - Keith Bowman
* fix z-clipping bug in mged's X display manager - Cliff Yapp
* fix z-clipping bug in MGED's X display manager - Cliff Yapp
* added attribute sorting option to the 'attr' command - Tom Browder
* changed 'bwfilter' tool offset option from -o to -O - Mohit Daga
* gattributes section 5 man page renamed to attributes - Tom Browder
@@ -441,7 +315,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
@@ -472,7 +346,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
@@ -1183,7 +1057,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
@@ -1775,7 +1649,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 -1
View File
@@ -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
+424 -786
View File
File diff suppressed because it is too large Load Diff
+22 -37
View File
@@ -6,55 +6,40 @@ add_definitions(
-DHAVE_CONFIG_H
-DBRLCADBUILD
-DCONSOLE
)
)
BRLCAD_ADDEXEC(pixcmp pixcmp.c libbu)
configure_file(run.sh "${CMAKE_CURRENT_BINARY_DIR}/benchmark" COPYONLY)
install(PROGRAMS "${CMAKE_CURRENT_BINARY_DIR}/benchmark" DESTINATION ${BIN_DIR})
configure_file(run.sh ${CMAKE_CURRENT_BINARY_DIR}/benchmark COPYONLY)
install(PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/benchmark DESTINATION ${BIN_DIR})
if(CMAKE_CONFIGURATION_TYPES)
foreach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
string(TOUPPER "${CFG_TYPE}" CFG_TYPE_UPPER)
configure_file(run.sh ${CMAKE_BINARY_DIR_${CFG_TYPE_UPPER}}/bin/benchmark COPYONLY)
endforeach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
foreach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
string(TOUPPER "${CFG_TYPE}" CFG_TYPE_UPPER)
configure_file(run.sh ${CMAKE_BINARY_DIR_${CFG_TYPE_UPPER}}/bin/benchmark COPYONLY)
endforeach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
else(CMAKE_CONFIGURATION_TYPES)
configure_file(run.sh ${CMAKE_BINARY_DIR}/bin/benchmark COPYONLY)
endif(CMAKE_CONFIGURATION_TYPES)
file(WRITE "${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake" "message(\"---\")\n")
file(APPEND "${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake" "message(\"Run 'make benchmark-clean' in the bench directory to delete the logic\")\n")
file(APPEND "${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake" "message(\"and image files generated during the benchmark analysis.\")\n")
file(WRITE ${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake "message(\"---\")\n")
file(APPEND ${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake "message(\"Run 'make benchmark-clean' in the bench directory to delete the logic\")\n")
file(APPEND ${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake "message(\"and image files generated during the benchmark analysis.\")\n")
CMAKEFILES(lgt.sh run.sh try.sh viewdiff.sh)
if(SH_EXEC)
# CTest enabled short run of the benchmark suite
add_test(NAME benchmark COMMAND ${SH_EXEC} "${CMAKE_BINARY_DIR}/bin/benchmark" run TIMEFRAME=1)
set_tests_properties(benchmark PROPERTIES LABELS "Benchmark")
add_custom_target(benchmark-check
COMMAND ${CMAKE_CTEST_COMMAND} -L Benchmark --output-on-failure
DEPENDS rt pixcmp BENCHMARK_PIX_cp PIX_LOG_cp
)
add_dependencies(benchmark-check bldg391.g m35.g moss.g sphflake.g star.g world.g)
if(TARGET check)
add_dependencies(check benchmark-check)
endif(TARGET check)
# Full run of the benchmark suite
add_custom_target(benchmark
COMMAND ${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark run
COMMAND ${CMAKE_COMMAND} -P "${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake"
DEPENDS rt pixcmp BENCHMARK_PIX_cp PIX_LOG_cp
)
add_dependencies(benchmark bldg391.g m35.g moss.g sphflake.g star.g world.g)
# benchmark cleanup targets
add_custom_target(benchmark-clean
${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark clean
)
add_custom_target(benchmark-clobber
${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark clobber
)
add_custom_target(benchmark
COMMAND ${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark run
COMMAND ${CMAKE_COMMAND} -P ${CMAKE_BINARY_DIR}/CMakeTmp/benchmsg.cmake
DEPENDS rt pixcmp BENCHMARK_PIX_cp PIX_LOG_cp
)
add_dependencies(benchmark bldg391.g m35.g moss.g sphflake.g star.g world.g)
add_custom_target(benchmark-clean
${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark clean
)
add_custom_target(benchmark-clobber
${SH_EXEC} ${CMAKE_BINARY_DIR}/bin/benchmark clobber
)
endif(SH_EXEC)
# Local Variables:
+1 -1
View File
@@ -2,7 +2,7 @@
# L G T . S H
# BRL-CAD
#
# Copyright (c) 2004-2016 United States Government as represented by
# Copyright (c) 2004-2014 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
+5 -15
View File
@@ -1,7 +1,7 @@
/* P I X C M P . C
* BRL-CAD
*
* Copyright (c) 2004-2016 United States Government as represented by
* Copyright (c) 2004-2014 United States Government as represented by
* the U.S. Army Research Laboratory.
*
* This program is free software; you can redistribute it and/or
@@ -31,15 +31,13 @@
#include <stdlib.h>
#include <string.h>
#ifdef HAVE_SYS_STAT_H
# include <sys/stat.h>
#ifdef HAVE_UNISTD_H
# include <unistd.h>
#endif
#include "bio.h"
#include "bu/getopt.h"
#include "bu/log.h"
#include "bu/file.h"
#include "bu/str.h"
#include "bu.h"
/* exit codes for argument processing errors */
#define OPTS_ERROR 127
@@ -120,7 +118,6 @@ main(int argc, char *argv[])
{
FILE *f1 = NULL;
FILE *f2 = NULL;
struct stat sf1, sf2;
long matching = 0;
long off1 = 0;
@@ -202,13 +199,6 @@ main(int argc, char *argv[])
exit(FILE_ERROR);
}
stat(argv[0], &sf1);
stat(argv[1], &sf2);
if (sf1.st_size != sf2.st_size) {
bu_exit(FILE_ERROR, "Different file sizes found: %s(%d) and %s(%d). Cannot perform pixcmp.\n", argv[0], sf1.st_size, argv[1], sf2.st_size);
}
if (!print_bytes) {
f1_skip *= 3;
f2_skip *= 3;
+98 -94
View File
@@ -2,7 +2,7 @@
# R U N . S H
# BRL-CAD
#
# Copyright (c) 2004-2016 United States Government as represented by
# Copyright (c) 2004-2014 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
@@ -51,7 +51,7 @@
export PATH || (echo "This isn't sh."; sh $0 $*; kill $$)
# save the precious args
ARGS="$@"
ARGS="$*"
NAME_OF_THIS="`basename \"$0\"`"
PATH_TO_THIS="`dirname \"$0\"`"
THIS="$PATH_TO_THIS/$NAME_OF_THIS"
@@ -159,59 +159,66 @@ booleanize ( ) {
}
# any unrecognized args are assumed to be RT args (e.g., -P4)
RTARGS=""
# process the argument list for commands
while test $# -gt 0 ; do
arg="$1"
shift
NEWARGS=""
for arg in $ARGS ; do
case "x$arg" in
x*[cC][lL][eE][aA][nN])
CLEAN=1
shift
;;
x*[cC][lL][oO][bB][bB][eE][rR])
CLEAN=1
CLOBBER=1
shift
;;
x*[hH])
HELP=1
shift
;;
x*[hH][eE][lL][pP])
HELP=1
shift
;;
x*[iI][nN][sS][tT][rR][uU][cC][tT]*)
INSTRUCTIONS=1
shift
;;
x*[sS][tT][aA][rR][tT])
shift
;;
x*[qQ][uU][iI][eE][tT])
QUIET=1
shift
;;
x*[vV][eE][rR][bB][oO][sS][eE])
VERBOSE=1
shift
;;
x*[rR][uU][nN])
RUN=1
shift
;;
x*=*)
VAR=`echo $arg | sed 's/=.*//g'`
if test ! "x$VAR" = "x" ; then
VAL=`echo $arg | sed 's/.*=//g'`
CMD="$VAR=\"$VAL\""
CMD="$VAR=$VAL"
eval $CMD
export $VAR
fi
shift
;;
x*)
echo "WARNING: Passing unknown option [$arg] to RT"
RTARGS="$RTARGS $arg"
echo "WARNING: Passing unknown option [$1] to RT"
NEWARGS="$NEWARGS $arg"
;;
esac
done
# reload post-shifting
ARGS="$NEWARGS"
# validate and clean up options (all default to 0)
booleanize CLOBBER HELP INSTRUCTIONS QUIET VERBOSE RUN
@@ -424,13 +431,13 @@ $ECHO
########################
look_for ( ) {
# utility function to search for a certain filesystem object in a
# list of paths.
look_for_type="$1" ; shift
look_for_label="$1" ; shift
look_for_var="$1" ; shift
look_for_dirs="$*"
if test "x$look_for_label" != "x" ; then
$VERBOSE_ECHO "Looking for $look_for_label"
@@ -438,11 +445,11 @@ look_for ( ) {
# get the value of the variable
look_for_var_var="echo \"\$$look_for_var\""
look_for_var_val="`eval \"${look_for_var_var}\"`"
look_for_var_val="`eval ${look_for_var_var}`"
if test "x${look_for_var_val}" = "x" ; then
for look_for_dir in "$@" ; do
shift
for look_for_dir in $look_for_dirs ; do
opts="-r"
case "x$look_for_type" in
xfile)
@@ -453,10 +460,10 @@ look_for ( ) {
opts="-d -x"
;;
xexe*)
opts="$opts -f -x"
opts="$opts -f -r -x"
;;
xscr*)
opts="$opts -f -x"
opts="$opts -f -r -x"
;;
esac
look_for_failed=no
@@ -484,61 +491,61 @@ look_for ( ) {
}
look_for executable "the BRL-CAD raytracer" RT \
"${PATH_TO_THIS}/rt" \
"${PATH_TO_THIS}/../bin/rt" \
"${PATH_TO_THIS}/../src/rt/rt" \
"${PATH_TO_THIS}/src/rt/rt" \
${PATH_TO_THIS}/rt \
${PATH_TO_THIS}/../bin/rt \
${PATH_TO_THIS}/../src/rt/rt \
${PATH_TO_THIS}/src/rt/rt \
./rt \
../brlcadInstall/bin/rt.exe \
../src/rt/rt
look_for file "a benchmark geometry directory" DB \
"${PATH_TO_THIS}/../share/brlcad/*.*.*/db/moss.g" \
"${PATH_TO_THIS}/share/brlcad/*.*.*/db/moss.g" \
"${PATH_TO_THIS}/../share/brlcad/db/moss.g" \
"${PATH_TO_THIS}/share/brlcad/db/moss.g" \
"${PATH_TO_THIS}/../share/db/moss.g" \
"${PATH_TO_THIS}/share/db/moss.g" \
"${PATH_TO_THIS}/../db/moss.g" \
"${PATH_TO_THIS}/db/moss.g" \
${PATH_TO_THIS}/../share/brlcad/*.*.*/db/moss.g \
${PATH_TO_THIS}/share/brlcad/*.*.*/db/moss.g \
${PATH_TO_THIS}/../share/brlcad/db/moss.g \
${PATH_TO_THIS}/share/brlcad/db/moss.g \
${PATH_TO_THIS}/../share/db/moss.g \
${PATH_TO_THIS}/share/db/moss.g \
${PATH_TO_THIS}/../db/moss.g \
${PATH_TO_THIS}/db/moss.g \
./db/moss.g \
../brlcadInstall/share/brlcad/*.*.*/db/moss.g \
../db/moss.g
DB="`echo $DB | sed 's,/moss.g$,,'`"
DB=`echo $DB | sed 's,/moss.g$,,'`
look_for directory "a benchmark reference image directory" PIX \
"${PATH_TO_THIS}/../share/brlcad/*.*.*/pix" \
"${PATH_TO_THIS}/share/brlcad/*.*.*/pix" \
"${PATH_TO_THIS}/../share/brlcad/pix" \
"${PATH_TO_THIS}/share/brlcad/pix" \
"${PATH_TO_THIS}/../share/pix" \
"${PATH_TO_THIS}/share/pix" \
"${PATH_TO_THIS}/ref" \
${PATH_TO_THIS}/../share/brlcad/*.*.*/pix \
${PATH_TO_THIS}/share/brlcad/*.*.*/pix \
${PATH_TO_THIS}/../share/brlcad/pix \
${PATH_TO_THIS}/share/brlcad/pix \
${PATH_TO_THIS}/../share/pix \
${PATH_TO_THIS}/share/pix \
${PATH_TO_THIS}/ref \
./ref
look_for directory "a benchmark reference log directory" LOG \
"$PIX" \
"${PATH_TO_THIS}/../share/brlcad/*.*.*/pix" \
"${PATH_TO_THIS}/share/brlcad/*.*.*/pix" \
"${PATH_TO_THIS}/../share/brlcad/pix" \
"${PATH_TO_THIS}/share/brlcad/pix" \
"${PATH_TO_THIS}/../share/pix" \
"${PATH_TO_THIS}/share/pix" \
"${PATH_TO_THIS}/ref" \
$PIX \
${PATH_TO_THIS}/../share/brlcad/*.*.*/pix \
${PATH_TO_THIS}/share/brlcad/*.*.*/pix \
${PATH_TO_THIS}/../share/brlcad/pix \
${PATH_TO_THIS}/share/brlcad/pix \
${PATH_TO_THIS}/../share/pix \
${PATH_TO_THIS}/share/pix \
${PATH_TO_THIS}/ref \
./ref
look_for executable "a pixel comparison utility" CMP \
"${PATH_TO_THIS}/pixcmp" \
"${PATH_TO_THIS}/../bin/pixcmp" \
"${PATH_TO_THIS}/../bench/pixcmp" \
${PATH_TO_THIS}/pixcmp \
${PATH_TO_THIS}/../bin/pixcmp \
${PATH_TO_THIS}/../bench/pixcmp \
../brlcadInstall/bin/pixcmp.exe \
./pixcmp
look_for script "a time elapsed utility" ELP \
"${PATH_TO_THIS}/elapsed.sh" \
"${PATH_TO_THIS}/../bin/elapsed.sh" \
"${PATH_TO_THIS}/sh/elapsed.sh" \
"${PATH_TO_THIS}/../sh/elapsed.sh" \
${PATH_TO_THIS}/elapsed.sh \
${PATH_TO_THIS}/../bin/elapsed.sh \
${PATH_TO_THIS}/sh/elapsed.sh \
${PATH_TO_THIS}/../sh/elapsed.sh \
./elapsed.sh
@@ -585,12 +592,9 @@ else
fi
# more sanity checks, make sure the binaries and scripts run
eval \"$RT\" -s1 -F/dev/debug \"${DB}/moss.g\" LIGHT > /dev/null 2>&1
$RT -s1 -F/dev/debug ${DB}/moss.g LIGHT > /dev/null 2>&1
ret=$?
if test ! "x${ret}" = "x0" ; then
$ECHO
$ECHO "Running \"$RT\":"
"$RT"
$ECHO
$ECHO "ERROR: RT does not seem to work as expected"
exit 2
@@ -599,7 +603,7 @@ fi
# create a temporary file named "null", fopen("/dev/null") does not work on
# windows (using cygwin), so punt.
> null
eval \"$CMP\" null null >/dev/null 2>&1
$CMP null null >/dev/null 2>&1
rm -f null
ret=$?
@@ -608,7 +612,7 @@ if test ! "x${ret}" = "x0" ; then
$ECHO "ERROR: CMP does not seem to work as expected"
exit 2
fi
eval \"$ELP\" 0 > /dev/null 2>&1
$ELP 0 > /dev/null 2>&1
if test ! "x${ret}" = "x0" ; then
$ECHO
$ECHO "ERROR: ELP does not seem to work as expected"
@@ -676,12 +680,12 @@ if test "x`expr 1 - 1 2>/dev/null`" = "x0" ; then
if test $mintime -lt 1 ; then
mintime=0 # zero is okay
fi
$ECHO "Minimum run time is `\"$ELP\" $mintime`"
$ECHO "Minimum run time is `$ELP $mintime`"
maxtime="`expr 6 \* $MAXTIME`"
if test $maxtime -lt 1 ; then
maxtime=1 # zero would be misleading
fi
$ECHO "Maximum run time is `\"$ELP\" $maxtime`"
$ECHO "Maximum run time is `$ELP $maxtime`"
estimate="`expr 3 \* $mintime`"
if test $estimate -lt 1 ; then
estimate=1 # zero would be misleading
@@ -689,7 +693,7 @@ if test "x`expr 1 - 1 2>/dev/null`" = "x0" ; then
if test $estimate -gt $maxtime ; then
estimate="$maxtime"
fi
$ECHO "Estimated time is `eval \\\"$ELP\\\" $estimate`"
$ECHO "Estimated time is `$ELP $estimate`"
$ECHO
else
$ECHO "WARNING: expr is unavailable, unable to compute statistics"
@@ -719,9 +723,9 @@ run ( ) {
$VERBOSE_ECHO "DEBUG: Running $RT -B -M -s512 -H${run_hypersample} -J0 ${run_args} -o ${run_geomname}.pix ${DB}/${run_geomname}.g ${run_geometry}"
eval \"$RT\" -B -M -s512 -H${run_hypersample} -J0 ${run_args} \
$RT -B -M -s512 -H${run_hypersample} -J0 ${run_args} \
-o ${run_geomname}.pix \
\"${DB}/${run_geomname}.g\" ${run_geometry} 1>&2 <<EOF
${DB}/${run_geomname}.g ${run_geometry} 1>&2 <<EOF
$run_view
EOF
retval=$?
@@ -995,7 +999,7 @@ EOF
# compute how long we took, rounding up to at least one
# second to prevent division by zero.
bench_elapsed="`eval \\\"$ELP\\\" --seconds $bench_frame_start_time`"
bench_elapsed="`$ELP --seconds $bench_frame_start_time`"
if test "x$bench_elapsed" = "x" ; then
bench_elapsed=1
fi
@@ -1063,7 +1067,7 @@ EOF
fi
# see if we need to break out early
bench_overall_elapsed="`eval \\\"$ELP\\\" --seconds $bench_start_time`"
bench_overall_elapsed="`$ELP --seconds $bench_start_time`"
if test $bench_overall_elapsed -ge $MAXTIME ; then
break;
fi
@@ -1101,7 +1105,7 @@ EOF
break
fi
bench_overall_elapsed="`eval \\\"$ELP\\\" --seconds $bench_start_time`"
bench_overall_elapsed="`$ELP --seconds $bench_start_time`"
# undo the hypersample increase back one step
bench_hypersample="`expr \( \( $bench_hypersample + 1 \) / 2 \) - 1`"
@@ -1122,7 +1126,7 @@ EOF
ls -la *.pix*
fi
$VERBOSE_ECHO "DEBUG: $CMP $PIX/${bench_testname}.pix ${bench_testname}.pix"
cmp_result="`eval \\\"${CMP}\\\" \\\"${PIX}/${bench_testname}.pix\\\" ${bench_testname}.pix 2>&1`"
cmp_result="`${CMP} ${PIX}/${bench_testname}.pix ${bench_testname}.pix 2>&1`"
ret=$?
$ECHO "$cmp_result"
@@ -1177,8 +1181,8 @@ perf ( ) {
perf_ref_files=""
perf_cur_files=""
for perf_test in $perf_tests ; do
perf_ref_log="${LOG}/${perf_test}.log"
perf_cur_log="${perf_test}.log"
perf_ref_log=${LOG}/${perf_test}.log
perf_cur_log=${perf_test}.log
for perf_log in "$perf_cur_log" "$perf_ref_log" ; do
if test ! "x$perf_log" = "x" ; then
if test ! -f "$perf_log" ; then
@@ -1186,7 +1190,7 @@ perf ( ) {
fi
fi
done
perf_ref_files="$perf_ref_files \"$perf_ref_log\""
perf_ref_files="$perf_ref_files $perf_ref_log"
perf_cur_files="$perf_cur_files $perf_cur_log"
done
@@ -1196,8 +1200,8 @@ perf ( ) {
#
# FIXME: should really iterate one file at a time so we don't
# just zero-pad at the end
perf_VGRREF="`eval grep RTFM $perf_ref_files | sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | tr '\012' '\011' `"
perf_CURVALS="`eval grep RTFM $perf_cur_files | sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | tr '\012' '\011' `"
perf_VGRREF=`grep RTFM $perf_ref_files | sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | tr '\012' '\011' `
perf_CURVALS=`grep RTFM $perf_cur_files | sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | tr '\012' '\011' `
# if there were no reference values, we cannot compute timings
if test "x$perf_VGRREF" = "x" ; then
@@ -1292,7 +1296,7 @@ $ECHO "Running the BRL-CAD Benchmark tests... please wait ..."
$ECHO
ret=0
bench moss all.g $RTARGS << EOF
bench moss all.g $ARGS << EOF
viewsize 1.572026215e+02;
eye_pt 6.379990387e+01 3.271768951e+01 3.366661453e+01;
viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
@@ -1302,7 +1306,7 @@ viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
EOF
ret=`expr $ret + $?`
bench world all.g $RTARGS << EOF
bench world all.g $ARGS << EOF
viewsize 1.572026215e+02;
eye_pt 6.379990387e+01 3.271768951e+01 3.366661453e+01;
viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
@@ -1312,7 +1316,7 @@ viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
EOF
ret=`expr $ret + $?`
bench star all $RTARGS << EOF
bench star all $ARGS << EOF
viewsize 2.500000000e+05;
eye_pt 2.102677960e+05 8.455500000e+04 2.934714650e+04;
viewrot -6.733560560e-01 6.130643360e-01 4.132114880e-01 0.000000000e+00
@@ -1322,7 +1326,7 @@ viewrot -6.733560560e-01 6.130643360e-01 4.132114880e-01 0.000000000e+00
EOF
ret=`expr $ret + $?`
bench bldg391 all.g $RTARGS << EOF
bench bldg391 all.g $ARGS << EOF
viewsize 1.800000000e+03;
eye_pt 6.345012207e+02 8.633251343e+02 8.310771484e+02;
viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
@@ -1332,7 +1336,7 @@ viewrot -5.735764503e-01 8.191520572e-01 0.000000000e+00 0.000000000e+00
EOF
ret=`expr $ret + $?`
bench m35 all.g $RTARGS <<EOF
bench m35 all.g $ARGS <<EOF
viewsize 6.787387985e+03;
eye_pt 3.974533127e+03 1.503320754e+03 2.874633221e+03;
viewrot -5.527838919e-01 8.332423558e-01 1.171090926e-02 0.000000000e+00
@@ -1342,7 +1346,7 @@ viewrot -5.527838919e-01 8.332423558e-01 1.171090926e-02 0.000000000e+00
EOF
ret=`expr $ret + $?`
bench sphflake scene.r $RTARGS <<EOF
bench sphflake scene.r $ARGS <<EOF
viewsize 2.556283261452611e+04;
orientation 4.406810841785839e-01 4.005093234738861e-01 5.226451688385938e-01 6.101102288499644e-01;
eye_pt 2.418500583758302e+04 -3.328563644344796e+03 8.489926952850350e+03;
@@ -1352,7 +1356,7 @@ ret=`expr $ret + $?`
$ECHO
$ECHO "... Done."
$ECHO
$ECHO "Total testing time elapsed: `eval \\\"$ELP\\\" $start`"
$ECHO "Total testing time elapsed: `$ELP $start`"
# see if we fail
if test ! "x$ret" = "x0" ; then
@@ -1361,7 +1365,7 @@ if test ! "x$ret" = "x0" ; then
$ECHO
$ECHO "A benchmark failure means this is not a viable install of BRL-CAD. This may be"
$ECHO "a new bug or (more likely) is a compilation configuration error. Ensure your"
$ECHO "compiler has strict aliasing disabled, compilation is optimized, and you have"
$ECHO "compiler has strict aliasing disabled, compilation is unoptimized, and you have"
$ECHO "installed BRL-CAD (some platforms require this). If you still get a failure,"
$ECHO "please report your configuration information to benchmark@brlcad.org"
$ECHO
@@ -1376,8 +1380,8 @@ fi
# compute and output results #
##############################
performance="`perf 'moss world star bldg391 m35 sphflake' $RTARGS 2>&1`"
performance="`perf 'moss world star bldg391 m35 sphflake' $ARGS`"
if test $? = 0 ; then
cat >> summary <<EOF
$performance
@@ -1493,7 +1497,7 @@ else
blankit=no
# BSD+
look_for executable "a sysctl command" SYSCTL_CMD `echo "$PATH" | tr ":" "\n" | tr " " "\ " | sed 's/$/\/sysctl/g'`
look_for executable "a sysctl command" SYSCTL_CMD `echo "$PATH" | tr ":" "\n" | sed 's/$/\/sysctl/g'`
if test ! "x$SYSCTL_CMD" = "x" ; then
$ECHO "Collecting system state information (via $SYSCTL_CMD)"
preQUIET="$QUIET"
@@ -1508,7 +1512,7 @@ else
fi
# Solaris
look_for executable "a prtdiag command" PRTDIAG_CMD `echo "$PATH" | tr ":" "\n" | tr " " "\ " | sed 's/$/\/prtdiag/g'`
look_for executable "a prtdiag command" PRTDIAG_CMD `echo "$PATH" | tr ":" "\n" | sed 's/$/\/prtdiag/g'`
if test ! "x$PRTDIAG_CMD" = "x" ; then
$ECHO "Collecting system diagnostics information (via $PRTDIAG_CMD)"
preQUIET="$QUIET"
@@ -1521,7 +1525,7 @@ else
fi
# AIX
look_for executable "a prtconf command" PRTCONF_CMD `echo "$PATH" | tr ":" "\n" | tr " " "\ " | sed 's/$/\/prtconf/g'`
look_for executable "a prtconf command" PRTCONF_CMD `echo "$PATH" | tr ":" "\n" | sed 's/$/\/prtconf/g'`
if test ! "x$PRTCONF_CMD" = "x" ; then
$ECHO "Collecting system configuration information (via $PRTCONF_CMD)"
preQUIET="$QUIET"
@@ -1534,7 +1538,7 @@ else
fi
# SGI
look_for executable "an hinv command" HINV_CMD `echo "$PATH" | tr ":" "\n" | tr " " "\ " | sed 's/$/\/hinv/g'`
look_for executable "an hinv command" HINV_CMD `echo "$PATH" | tr ":" "\n" | sed 's/$/\/hinv/g'`
if test ! "x$HINV_CMD" = "x" ; then
$ECHO "Collecting system configuration information (via $HINV_CMD)"
preQUIET="$QUIET"
@@ -1560,7 +1564,7 @@ else
fi
# Linux+
look_for executable "an lscpu command" LSCPU_CMD `echo "$PATH" | tr ":" "\n" | tr " " "\ " | sed 's/$/\/lscpu/g'`
look_for executable "an lscpu command" LSCPU_CMD `echo $PATH | tr ":" "\n" | sed 's/$/\/lscpu/g'`
if test ! "x$LSCPU_CMD" = "x" ; then
$ECHO "Collecting system CPU information (via $LSCPU_CMD)"
preQUIET="$QUIET"
@@ -1579,12 +1583,12 @@ fi
# tell about the benchmark document
look_for file "" BENCHMARK_TR \
"${PATH_TO_THIS}/../share/brlcad/*.*.*/doc/benchmark.tr" \
"${PATH_TO_THIS}/share/brlcad/*.*.*/doc/benchmark.tr" \
"${PATH_TO_THIS}/share/brlcad/doc/benchmark.tr" \
"${PATH_TO_THIS}/share/doc/benchmark.tr" \
"${PATH_TO_THIS}/doc/benchmark.tr" \
"${PATH_TO_THIS}/../doc/benchmark.tr" \
${PATH_TO_THIS}/../share/brlcad/*.*.*/doc/benchmark.tr \
${PATH_TO_THIS}/share/brlcad/*.*.*/doc/benchmark.tr \
${PATH_TO_THIS}/share/brlcad/doc/benchmark.tr \
${PATH_TO_THIS}/share/doc/benchmark.tr \
${PATH_TO_THIS}/doc/benchmark.tr \
${PATH_TO_THIS}/../doc/benchmark.tr \
./benchmark.tr
$ECHO "Read the benchmark.tr document for more details on the BRL-CAD Benchmark."
+1 -1
View File
@@ -2,7 +2,7 @@
# T R Y . S H
# BRL-CAD
#
# Copyright (c) 2004-2016 United States Government as represented by
# Copyright (c) 2004-2014 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
+1 -1
View File
@@ -2,7 +2,7 @@
# V I E W D I F F . S H
# BRL-CAD
#
# Copyright (c) 2004-2016 United States Government as represented by
# Copyright (c) 2004-2014 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
Vendored
-24
View File
@@ -126,22 +126,10 @@ do
shift;;
--disable-libz) options="$options -DBRLCAD_ZLIB=SYSTEM";
shift;;
--enable-tinycthread) options="$options -DBRLCAD_TINYCTHREAD=BUNDLED";
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";
shift;;
--enable-netpbm) options="$options -DBRLCAD_NETPBM=BUNDLED";
shift;;
--disable-netpbm) options="$options -DBRLCAD_NETPBM=SYSTEM";
shift;;
--enable-png) options="$options -DBRLCAD_PNG=BUNDLED";
shift;;
--disable-png) options="$options -DBRLCAD_PNG=SYSTEM";
@@ -186,10 +174,6 @@ do
shift;;
--disable-opennurbs) options="$options -DBRLCAD_OPENNURBS=SYSTEM";
shift;;
--enable-spr) options="$options -DBRLCAD_SPR=BUNDLED";
shift;;
--disable-spr) options="$options -DBRLCAD_SPR=SYSTEM";
shift;;
--enable-scl) options="$options -DBRLCAD_SC=BUNDLED";
shift;;
--disable-scl) options="$options -DBRLCAD_SC=SYSTEM";
@@ -202,18 +186,10 @@ do
shift;;
--disable-step-class-libraries) options="$options -DBRLCAD_SC=SYSTEM";
shift;;
--enable-gecode) options="$options -DBRLCAD_GECODE=BUNDLED";
shift;;
--disable-gecode) options="$options -DBRLCAD_GECODE=SYSTEM";
shift;;
--enable-vds) options="$options -DBRLCAD_VDS=BUNDLED";
shift;;
--disable-vds) options="$options -DBRLCAD_VDS=SYSTEM";
shift;;
--enable-openscenegraph) options="$options -DBRLCAD_OSG=BUNDLED";
shift;;
--disable-openscenegraph) options="$options -DBRLCAD_OSG=SYSTEM";
shift;;
--enable-gdiam) options="$options -DBRLCAD_GDIAM=BUNDLED";
shift;;
--disable-gdiam) options="$options -DBRLCAD_GDIAM=SYSTEM";
+4 -8
View File
@@ -41,8 +41,8 @@ macro(ADD_G_TARGET g_model folder)
set(output_file ${bin_root}/${DATA_DIR}/db/${g_model_root}.g)
add_custom_command(
OUTPUT ${output_file}
COMMAND asc2g "${CMAKE_CURRENT_SOURCE_DIR}/${g_model}" ${output_file}
DEPENDS asc2g "${CMAKE_CURRENT_SOURCE_DIR}/${g_model}"
COMMAND asc2g ${CMAKE_CURRENT_SOURCE_DIR}/${g_model} ${output_file}
DEPENDS asc2g ${CMAKE_CURRENT_SOURCE_DIR}/${g_model}
)
add_custom_target(${g_model_root}.g ALL DEPENDS ${output_file})
set_target_properties(${g_model_root}.g PROPERTIES FOLDER "${folder}")
@@ -66,16 +66,12 @@ endif(CMAKE_CONFIGURATION_TYPES)
# Make sure the db directories are there
if(CMAKE_CONFIGURATION_TYPES)
foreach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
file(MAKE_DIRECTORY "${CMAKE_BINARY_DIR}/${CFG_TYPE}/${DATA_DIR}/db")
file(MAKE_DIRECTORY ${CMAKE_BINARY_DIR}/${CFG_TYPE}/${DATA_DIR}/db)
endforeach(CFG_TYPE ${CMAKE_CONFIGURATION_TYPES})
else(CMAKE_CONFIGURATION_TYPES)
file(MAKE_DIRECTORY "${CMAKE_BINARY_DIR}/${DATA_DIR}/db")
file(MAKE_DIRECTORY ${CMAKE_BINARY_DIR}/${DATA_DIR}/db)
endif(CMAKE_CONFIGURATION_TYPES)
add_subdirectory(comgeom)
add_subdirectory(nist)
add_subdirectory(faa)
foreach(g_input ${G_BENCHMARK_MODELS})
ADD_G_TARGET(${g_input} "BRL-CAD Geometry Models/Benchmark")
endforeach(g_input ${G_BENCHMARK_MODELS})
File diff suppressed because it is too large Load Diff
Binary file not shown.
-46
View File
@@ -1,46 +0,0 @@
set(COMGEOM_V5_MODELS
ADA073408.comgeom
)
macro(ADD_COMGEOM_V5_G_TARGET comgeom_model folder)
string(REGEX REPLACE "([0-9a-z]*).comgeom" "\\1" comgeom_model_root "${comgeom_model}")
set(output_file ${bin_root}/${DATA_DIR}/db/${comgeom_model_root}.g)
set(log_file ${CMAKE_CURRENT_BINARY_DIR}/${comgeom_model_root}.log)
add_custom_command(
OUTPUT ${output_file}
COMMAND ${CMAKE_COMMAND} -E remove ${output_file}
COMMAND comgeom-g -v 5 ${CMAKE_CURRENT_SOURCE_DIR}/${comgeom_model} ${output_file} > ${log_file} 2>&1
DEPENDS comgeom-g ${CMAKE_CURRENT_SOURCE_DIR}/${comgeom_model}
)
add_custom_target(${comgeom_model_root}.g ALL DEPENDS ${output_file})
set_target_properties(${comgeom_model_root}.g PROPERTIES FOLDER "${folder}")
if(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
if(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
string(REPLACE "${CMAKE_CFG_INTDIR}" "\${BUILD_TYPE}" output_file "${output_file}")
endif(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
install(FILES ${output_file} DESTINATION ${DATA_DIR}/db)
endif(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
set(BUILT_MODELS "${BUILT_MODELS};${output_file}")
set(LOG_FILES "${LOG_FILES};${log_file}")
DISTCLEAN(${log_file})
endmacro(ADD_COMGEOM_V5_G_TARGET comgeom_model folder)
foreach(comgeom_input ${COMGEOM_V5_MODELS})
ADD_COMGEOM_V5_G_TARGET(${comgeom_input} "BRL-CAD Geometry Models/Sample")
endforeach(comgeom_input ${COMGEOM_V5_MODELS})
CMAKEFILES(${COMGEOM_V5_MODELS})
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${BUILT_MODELS}")
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${LOG_FILES}")
CMAKEFILES(
README_ADA073408
ADA073408_inputs.tar.gz
)
# Local Variables:
# tab-width: 8
# mode: cmake
# indent-tabs-mode: t
# End:
# ex: shiftwidth=2 tabstop=8
-17
View File
@@ -1,17 +0,0 @@
Model ADA073408.comgeom is a transcription of the model documented in
the 1979 public release report:
A Combinatorial Geometry Computer Description of the MEP-021A Generator Set
http://www.dtic.mil/docs/citations/ADA073408
A series of Google GCI tasks worked to transcribe the ASCII COMGEOM
description from the original report to text, and post-processed it
into a form that the comgeom-g importer can handle:
http://www.google-melange.com/gci/task/view/google/gci2013/5597236545191936
http://www.google-melange.com/gci/task/view/google/gci2014/5293529710460928
http://www.google-melange.com/gci/task/view/google/gci2014/5792678377684992
The file ADA073408_inputs.tar.gz contains the original transcribed
files and the script used to create the comgeom file.
+1 -1
View File
@@ -2,7 +2,7 @@
# C U B E . R T
# BRL-CAD
#
# Copyright (c) 2004-2016 United States Government as represented by
# Copyright (c) 2004-2014 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
+9 -11
View File
@@ -2,7 +2,7 @@
/* D B . P H P
* BRL-CAD
*
* Copyright (c) 2004-2016 United States Government as represented by
* Copyright (c) 2004-2014 United States Government as represented by
* the U.S. Army Research Laboratory.
*
* This library is free software; you can redistribute it and/or
@@ -275,14 +275,12 @@ if ($physicalFile) {
debug("END http request");
?>
<!--
Local Variables:
tab-width: 8
mode: php
c-basic-offset: 4
indent-tabs-mode: t
End:
ex: shiftwidth=4 tabstop=8
-->
# Local Variables: ***
# mode: C ***
# tab-width: 8 ***
# c-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
?>
-856
View File
@@ -1,856 +0,0 @@
$COMMENT Generic Business Jet Rotor Burst Model
$COMMENT Todd Horelica
$COMMENT 28 Jan 2000
$COMMENT
$COMMENT The generic aircraft models were developed in support of the Federal
$COMMENT Aviation Administration's Aircraft Catastrophic Failure Prevention
$COMMENT Program. The models are used to demonstrate the Uncontained Engine
$COMMENT Debris Damage Assessment Model (UEDDAM) tool which evaluates the risk
$COMMENT to the aircraft from uncontained engine failures. This analysis
$COMMENT supports certification to Title 14 Code of Federal Regulations,
$COMMENT Part 25.903. The models are for demonstration purposes and do not
$COMMENT depict actual aircraft and /or Aircraft systems in service. The models
$COMMENT are available for public release.
$COMMENT
$COMMENT Note: Right and left are with respect to looking forward from the tail;
$COMMENT i.e. the pilot's perspective
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT
$NAME 0 1 Right Engine Nacelle
SECTION 0 1 1 1
GRID 1 -375.96 -64.08 145.47
GRID 2 -491.31 -64.08 145.47
CCONE1 1 8 1 2 0.04 19.010000001
10000001 19.0 1 1
$NAME 0 11 Left Engine Nacelle
SECTION 0 11 1 1
GRID 3 -375.96 64.08 145.47
GRID 4 -491.31 64.08 145.47
CCONE1 2 8 3 4 0.04 19.010000002
10000002 19.0 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Pylons
$NAME 0 2 Left Pylon
SECTION 0 2 1 5
GRID 5 -392.28 45.24 142.98
GRID 6 -392.17 32.83 139.44
GRID 7 -494.47 45.24 142.98
GRID 8 -505.76 25.48 137.36
GRID 9 -392.28 46.75 137.69
GRID 10 -392.17 34.33 134.15
GRID 11 -494.47 46.75 137.69
GRID 12 -505.76 26.99 132.07
CQUAD 51 8 5 9 11 7 0.032 1
CQUAD 52 8 5 6 10 9 0.032 1
CQUAD 53 8 6 8 12 10 0.032 1
CQUAD 54 8 7 8 12 11 0.032 1
CQUAD 55 8 5 6 8 7 0.032 1
CQUAD 56 8 9 10 12 11 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 0 3 Right Pylon
SECTION 0 3 1 5
GRID 13 -392.28 -45.24 142.98
GRID 14 -392.17 -32.83 139.44
GRID 15 -494.47 -45.24 142.98
GRID 16 -505.76 -25.48 137.36
GRID 17 -392.28 -46.75 137.69
GRID 18 -392.17 -34.33 134.15
GRID 19 -494.47 -46.75 137.69
GRID 20 -505.76 -26.99 132.07
CQUAD 61 8 13 17 19 15 0.032 1
CQUAD 62 8 13 14 18 17 0.032 1
CQUAD 63 8 14 16 20 18 0.032 1
CQUAD 64 8 15 16 20 19 0.032 1
CQUAD 65 8 13 14 16 15 0.032 1
CQUAD 66 8 17 18 20 19 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 0 4 Aft Fuselage
SECTION 0 4 1 1
GRID 21 -373.75 -0.00 127.25
GRID 22 -512.50 -0.00 127.25
CCONE1 3 8 21 22 0.032 36.2510000003
10000003 26.96 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 0 101 Fairing
SECTION 0 101 1 1
GRID 223 -512.50 -0.00 100.27
GRID 224 -373.75 33.49 75.73
GRID 225 -373.75 -33.49 75.73
GRID 226 -373.75 33.49 127.25
GRID 227 -373.75 -33.49 127.25
CQUAD 87 8 224 225 227 226 0.032 1
CTRI 88 8 223 224 226 0.032 1
CTRI 89 8 223 224 225 0.032 1
CTRI 90 8 223 225 227 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Rotors
$NAME 1 1 Right Engine Fan
SECTION 1 1 2
GRID 294 -408.33 -64.08 145.47
GRID 295 -411.58 -64.08 145.47
CCONE2 1 7 294 295 13.609C90
C90 13.609 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 2 Right LPC1
SECTION 1 2 2
GRID 296 -416.62 -64.08 145.47
GRID 297 -418.62 -64.08 145.47
CCONE2 2 4 296 297 8.543C905
C905 8.543 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 3 Right HPC1
SECTION 1 3 2
GRID 298 -427.25 -64.08 145.47
GRID 299 -429.00 -64.08 145.47
CCONE2 3 4 298 299 5.09C91
C91 5.09 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 4 Right HPC2
SECTION 1 4 2
GRID 300 -431.36 -64.08 145.47
GRID 301 -432.61 -64.08 145.47
CCONE2 4 4 300 301 4.898C92
C92 4.898 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 5 Right HPC3
SECTION 1 5 2
GRID 302 -436.69 -64.08 145.47
GRID 303 -439.69 -64.08 145.47
CCONE2 5 4 302 303 6.644C93
C93 6.644 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 6 Right HPT1
SECTION 1 6 2
GRID 304 -443.53 -64.08 145.47
GRID 305 -445.28 -64.08 145.47
CCONE2 6 4 304 305 5.784C94
C94 5.784 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 7 Right LPT1
SECTION 1 7 2
GRID 306 -447.46 -64.08 145.47
GRID 307 -448.21 -64.08 145.47
CCONE2 7 4 306 307 7.286C95
C95 7.286 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 8 Right LPT2
SECTION 1 8 2
GRID 308 -450.10 -64.08 145.47
GRID 309 -450.98 -64.08 145.47
CCONE2 8 4 308 309 8.63C96
C96 8.63 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 9 Right LPT3
SECTION 1 9 2
GRID 310 -453.05 -64.08 145.47
GRID 311 -454.05 -64.08 145.47
CCONE2 9 4 310 311 8.985C97
C97 8.985 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 21 Right Engine Case
SECTION 1 21 1
GRID 332 -407.83 -64.08 145.47
GRID 333 -454.55 -64.08 145.47
CCONE1 21 4 332 333 0.1 14.109C332
C332 14.109 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 11 Left Engine Fan
SECTION 1 11 2
GRID 312 -408.33 64.08 145.47
GRID 313 -411.58 64.08 145.47
CCONE2 10 7 312 313 13.609C98
C98 13.609 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 12 Left LPC2
SECTION 1 12 2
GRID 314 -416.62 64.08 145.47
GRID 315 -418.62 64.08 145.47
CCONE2 19 4 314 315 8.543C985
C985 8.543 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 13 Left HPC1
SECTION 1 13 2
GRID 316 -427.25 64.08 145.47
GRID 317 -429.00 64.08 145.47
CCONE2 11 4 316 317 5.09C99
C99 5.09 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 14 Left HPC2
SECTION 1 14 2
GRID 318 -431.36 64.08 145.47
GRID 319 -432.61 64.08 145.47
CCONE2 12 4 318 319 4.898C100
C100 4.898 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 15 Left HPC3
SECTION 1 15 2
GRID 320 -436.69 64.08 145.47
GRID 321 -439.69 64.08 145.47
CCONE2 13 4 320 321 6.644C101
C101 6.644 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 16 Left HPT1
SECTION 1 16 2
GRID 322 -443.53 64.08 145.47
GRID 323 -445.28 64.08 145.47
CCONE2 14 4 322 323 5.784C102
C102 5.784 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 17 Left LPT1
SECTION 1 17 2
GRID 324 -447.46 64.08 145.47
GRID 325 -448.21 64.08 145.47
CCONE2 15 4 324 325 7.286C103
C103 7.286 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 18 Left LPT2
SECTION 1 18 2
GRID 326 -450.10 64.08 145.47
GRID 327 -450.98 64.08 145.47
CCONE2 16 4 326 327 8.63C104
C104 8.63 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 19 Left LPT3
SECTION 1 19 2
GRID 328 -453.05 64.08 145.47
GRID 329 -454.05 64.08 145.47
CCONE2 17 4 328 329 8.985C105
C105 8.985 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 1 22 Left Engine Case
SECTION 1 22 1
GRID 334 -407.83 64.08 145.47
GRID 335 -454.55 64.08 145.47
CCONE1 22 4 334 335 0.1 14.109C333
C333 14.109 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Control Cables
$NAME 3 1 Elevator Control Cables
SECTION 3 1 1
GRID 256 -373.75 13.97 90.17
GRID 257 -446.98 -2.25 95.25
GRID 258 -512.50 -1.03 104.95
GRID 259 -373.75 6.07 88.65
GRID 260 -446.96 -2.70 95.40
GRID 261 -512.50 -1.63 105.02
CLINE 1 4 256 257 0.063 0.063
CLINE 2 4 257 258 0.063 0.063
CLINE 3 4 259 260 0.063 0.063
CLINE 4 4 260 261 0.063 0.063
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 3 2 Elevator Trim Cables
SECTION 3 2 1
GRID 262 -373.75 -26.11 99.49
GRID 263 -388.77 -26.11 99.49
GRID 264 -385.59 -5.80 160.33
GRID 265 -512.50 -5.80 150.95
GRID 266 -375.75 -25.70 99.35
GRID 267 -388.78 -25.70 99.35
GRID 268 -385.59 -5.80 159.88
GRID 269 -512.50 -5.80 150.50
CLINE 5 4 262 263 0.063 0.063
CLINE 6 4 263 264 0.063 0.063
CLINE 7 4 264 265 0.063 0.063
CLINE 8 4 266 267 0.063 0.063
CLINE 9 4 267 268 0.063 0.063
CLINE 10 4 268 269 0.063 0.063
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 3 101 Rudder-Upper
SECTION 3 101 1
GRID 270 -373.75 -3.72 90.59
GRID 271 -384.74 -3.78 90.59
GRID 272 -391.84 -5.80 158.00
GRID 273 -512.50 -5.80 149.08
GRID 274 -373.75 -9.62 91.68
GRID 275 -383.88 -9.54 91.68
GRID 276 -392.62 -7.04 157.94
GRID 277 -512.50 -7.04 149.08
CLINE 11 4 270 271 0.063 0.063
CLINE 12 4 271 272 0.063 0.063
CLINE 13 4 272 273 0.063 0.063
CLINE 14 4 274 275 0.063 0.063
CLINE 15 4 275 276 0.063 0.063
CLINE 16 4 276 277 0.063 0.063
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 3 102 Rudder-Lower
SECTION 3 102 1
GRID 278 -373.75 -3.85 89.54
GRID 279 -448.81 -3.15 95.48
GRID 280 -512.50 -5.55 106.78
GRID 281 -373.75 -11.73 90.18
GRID 282 -448.78 -3.68 95.40
GRID 283 -512.50 -6.18 107.18
CLINE 17 4 278 279 0.063 0.063
CLINE 18 4 279 280 0.063 0.063
CLINE 19 4 281 282 0.063 0.063
CLINE 20 4 282 283 0.063 0.063
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 3 103 Rudder Trim
SECTION 3 103 1
GRID 284 -375.75 25.28 99.20
GRID 285 -388.78 25.28 99.20
GRID 286 -385.54 5.55 159.17
GRID 287 -406.34 -5.80 157.47
GRID 288 -512.50 -5.80 149.62
GRID 289 -373.75 26.53 99.63
GRID 290 -388.76 26.53 99.63
GRID 291 -385.75 5.95 159.27
GRID 292 -406.37 -5.80 157.91
GRID 293 -512.50 -5.80 150.06
CLINE 21 4 284 285 0.063 0.063
CLINE 22 4 285 286 0.063 0.063
CLINE 23 4 286 287 0.063 0.063
CLINE 24 4 287 288 0.063 0.063
CLINE 25 4 289 290 0.063 0.063
CLINE 26 4 290 291 0.063 0.063
CLINE 27 4 291 292 0.063 0.063
CLINE 28 4 292 293 0.063 0.063
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Fuel Lines
$NAME 4 1 Fuel Supply Line (Right Side)
SECTION 4 1 1 1
GRID 23 -378.88 -23.20 99.85
GRID 24 -380.84 -28.57 144.05
GRID 25 -428.13 -21.15 144.62
GRID 26 -428.85 -24.92 136.29
GRID 27 -427.79 -45.94 140.51
CLINE 1 12 23 24 0.035 0.5
CLINE 2 12 24 25 0.035 0.5
CLINE 3 12 25 26 0.035 0.5
CLINE 4 12 26 27 0.035 0.5
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 4 2 Fuel Supply Line (Left Side)
SECTION 4 2 1 1
GRID 28 -378.88 23.20 99.85
GRID 29 -380.84 28.57 144.05
GRID 30 -428.13 21.15 144.62
GRID 31 -428.85 24.92 136.29
GRID 32 -427.79 45.94 140.51
CLINE 5 12 28 29 0.035 0.5
CLINE 6 12 29 30 0.035 0.5
CLINE 7 12 30 31 0.035 0.5
CLINE 8 12 31 32 0.035 0.5
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 4 3 Fuel Motive Flow Line (Right Side)
SECTION 4 3 1 1
GRID 33 -378.82 -21.40 98.41
GRID 34 -380.84 -26.92 143.90
GRID 35 -428.20 -19.50 144.48
GRID 36 -428.89 -24.34 133.86
GRID 37 -427.77 -46.57 138.33
CLINE 9 12 33 34 0.035 0.25
CLINE 10 12 34 35 0.035 0.25
CLINE 11 12 35 36 0.035 0.25
CLINE 12 12 36 37 0.035 0.25
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 4 4 Fuel Motive Flow Line (Left Side)
SECTION 4 4 1 1
GRID 38 -378.82 21.40 98.41
GRID 39 -380.84 26.92 143.90
GRID 40 -428.20 19.50 144.48
GRID 41 -428.89 24.34 133.86
GRID 42 -427.77 46.57 138.33
CLINE 13 12 38 39 0.035 0.25
CLINE 14 12 39 40 0.035 0.25
CLINE 15 12 40 41 0.035 0.25
CLINE 16 12 41 42 0.035 0.25
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Structure
$NAME 7 1 Left Forward Engine Beam (1st 2 outboard; 2nd 2 inboard)
SECTION 7 1 1 1
GRID 43 -421.50 45.35 142.87
GRID 44 -421.50 46.64 137.80
GRID 45 -421.50 31.04 138.79
GRID 46 -421.50 32.33 133.72
$COMMENT Forward Engine Beam, Back Side (1st 2 outboard; 2nd 2 inboard)
GRID 47 -424.50 45.35 142.87
GRID 48 -424.50 46.64 137.80
GRID 49 -424.50 30.85 138.74
GRID 50 -424.50 32.13 133.67
CQUAD 1 8 49 45 43 47 0.190 1
CQUAD 2 8 49 47 48 50 0.100 1
CQUAD 3 8 44 46 50 48 0.190 1
CQUAD 4 8 44 46 45 43 0.100 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 2 Forward Beam through fuselage
SECTION 7 2 1 1
GRID 45 -421.50 31.04 138.79
GRID 46 -421.50 32.33 133.72
GRID 61 -421.50 -31.04 138.79
GRID 62 -421.50 -32.33 133.72
GRID 49 -424.50 30.85 138.74
GRID 50 -424.50 32.13 133.67
GRID 65 -424.50 -30.85 138.74
GRID 66 -424.50 -32.13 133.67
CQUAD 17 8 45 46 62 61 0.100 1
CQUAD 18 8 49 50 66 65 0.100 1
CQUAD 19 8 45 49 65 61 0.190 1
CQUAD 20 8 46 50 66 62 0.190 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 3 Right Forward Engine Beam (1st 2 outboard; 2nd 2 inboard)
SECTION 7 3 1 1
GRID 59 -421.50 -45.35 142.87
GRID 60 -421.50 -46.64 137.80
GRID 61 -421.50 -31.04 138.79
GRID 62 -421.50 -32.33 133.72
$COMMENT Forward Engine Beam, Back Side (1st 2 outboard; 2nd 2 inboard)
GRID 63 -424.50 -45.35 142.87
GRID 64 -424.50 -46.64 137.80
GRID 65 -424.50 -30.85 138.74
GRID 66 -424.50 -32.13 133.67
CQUAD 9 8 65 61 59 63 0.190 1
CQUAD 10 8 65 63 64 66 0.100 1
CQUAD 11 8 60 62 66 64 0.190 1
CQUAD 12 8 60 62 61 59 0.100 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 11 Left Aft Engine Beam (1st 2 outboard; 2nd 2 inboard)
SECTION 7 11 1 1
GRID 51 -460.50 45.14 142.88
GRID 52 -460.50 46.68 137.76
GRID 53 -460.50 28.51 138.09
GRID 54 -460.50 29.85 132.97
$COMMENT Left Aft Engine Beam Back Side (1st 2 outboard; 2nd 2 inboard)
GRID 55 -462.50 45.14 142.88
GRID 56 -462.50 46.68 137.76
GRID 57 -462.50 28.38 138.05
GRID 58 -462.50 29.72 132.93
CQUAD 5 8 57 53 51 55 0.160 1
CQUAD 6 8 57 55 56 58 0.064 1
CQUAD 7 8 52 54 58 56 0.100 1
CQUAD 8 8 52 54 53 51 0.064 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 12 Aft Engine Beam through fuselage
SECTION 7 12 1 1
GRID 53 -460.50 28.51 138.09
GRID 54 -460.50 29.85 132.97
GRID 57 -462.50 28.38 138.05
GRID 58 -462.50 29.72 132.93
GRID 69 -460.50 -28.51 138.09
GRID 70 -460.50 -29.85 132.97
GRID 73 -462.50 -28.38 138.05
GRID 74 -462.50 -29.72 132.93
CQUAD 21 8 53 54 70 69 0.064 1
CQUAD 22 8 57 58 74 73 0.064 1
CQUAD 23 8 53 57 73 69 0.160 1
CQUAD 24 8 54 58 74 70 0.100 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 13 Right Aft Engine Beam (1st 2 outboard; 2nd 2 inboard)
SECTION 7 13 1 1
GRID 67 -460.50 -45.14 142.88
GRID 68 -460.50 -46.68 137.76
GRID 69 -460.50 -28.51 138.09
GRID 70 -460.50 -29.85 132.97
$COMMENT Aft Engine Beam Back Side (1st 2 outboard; 2nd 2 inboard)
GRID 71 -462.50 -45.14 142.88
GRID 72 -462.50 -46.68 137.76
GRID 73 -462.50 -28.38 138.05
GRID 74 -462.50 -29.72 132.93
CQUAD 13 8 73 69 67 71 0.160 1
CQUAD 16 8 68 70 69 67 0.064 1
CQUAD 14 8 73 71 72 74 0.064 1
CQUAD 15 8 68 70 74 72 0.100 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$Frames
$COMMENT The number in parenthesis () is the actual location relative to the origin.
$COMMENT The other numbers are the numbers provided by the original source.
$NAME 7 51 Frame at FS 389.5
SECTION 7 51 1 1
GRID 75 -389.50 -0.00 127.25
GRID 76 -390.25 -0.00 127.25
CCONE1 5 8 75 76 0.032 35.163C1
C1 35.113 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 52 Frame at FS 405.5
SECTION 7 52 1 1
GRID 77 -405.50 -0.00 127.25
GRID 78 -406.25 -0.00 127.25
CCONE1 6 8 77 78 0.032 34.092C2
C2 34.042 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 53 Frame at FS 479.5
SECTION 7 53 1 1
GRID 79 -479.50 -0.00 127.25
GRID 80 -480.25 -0.00 127.25
CCONE1 7 8 79 80 0.032 29.138C3
C3 29.087 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 54 Frame at FS 496.5
SECTION 7 54 1 1
GRID 81 -496.50 -0.00 127.25
GRID 82 -497.25 -0.00 127.25
CCONE1 8 8 81 82 0.032 28.00C4
C4 27.95 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 55 Frame at FS 512.5
SECTION 7 55 1 1
GRID 83 -512.50 -0.00 127.25
GRID 84 -513.25 -0.00 127.25
CCONE1 9 8 83 84 0.032 26.928C5
C5 26.846 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Engine Beam Frames
$NAME 7 61 Frame at FS 420.75
SECTION 7 61 1 1
GRID 85 -420.75 -0.00 127.25
GRID 86 -421.50 -0.00 127.25
CCONE1 10 8 85 86 0.032 33.07C6
C6 33.021 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 62 Frame at FS 424.5
SECTION 7 62 1 1
GRID 87 -424.50 -0.00 127.25
GRID 88 -425.25 -0.00 127.25
CCONE1 11 8 87 88 0.032 32.82C7
C7 32.77 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 63 Frame at FS 459.75
SECTION 7 63 1 1
GRID 89 -459.75 -0.00 127.25
GRID 90 -460.50 -0.00 127.25
CCONE1 12 8 89 90 0.032 30.46C8
C8 30.41 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 64 Frame at FS 462.5
SECTION 7 64 1 1
GRID 91 -462.50 -0.00 127.25
GRID 92 -463.25 -0.00 127.25
CCONE1 13 8 91 92 0.032 30.28C9
C9 30.23 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 65 Frame at FS 442.5
$COMMENT (Missing frame--goes between the two engine beam frames)
SECTION 7 65 1 1
GRID 93 -442.50 -0.00 127.25
GRID 94 -443.25 -0.00 127.25
CCONE1 14 8 93 94 0.032 31.615C10
C10 31.565 1 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$COMMENT Stringers
$NAME 7 101 Stringer 1
SECTION 7 101 1 1
GRID 95 -373.75 0.75 91.13
GRID 96 -373.75 -0.75 91.13
GRID 97 -512.50 0.75 100.42
GRID 98 -512.50 -0.75 100.42
CQUAD 15 13 95 96 98 97 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 102 Stringer 2
SECTION 7 102 1 1
GRID 99 -373.75 0.75 163.38
GRID 100 -373.75 -0.75 163.38
GRID 101 -512.50 0.75 154.09
GRID 102 -512.50 -0.75 154.09
CQUAD 16 13 99 100 102 101 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 103 Stringer 3
SECTION 7 103 1 1
GRID 103 -373.75 6.00 162.51
GRID 104 -373.75 7.49 162.24
GRID 105 -512.50 4.25 153.47
GRID 106 -512.50 5.72 153.17
CQUAD 17 13 103 104 106 105 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 104 Stringer 4
SECTION 7 104 1 1
GRID 107 -373.75 -6.00 162.51
GRID 108 -373.75 -7.49 162.24
GRID 109 -512.50 -4.25 153.47
GRID 110 -512.50 -5.72 153.17
CQUAD 18 13 107 108 110 109 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 105 Stringer 5
SECTION 7 105 1 1
GRID 111 -373.75 12.78 160.63
GRID 112 -373.75 14.11 160.05
GRID 113 -512.50 9.22 152.04
GRID 114 -512.50 10.61 151.47
CQUAD 19 13 111 112 114 113 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 106 Stringer 6
SECTION 7 106 1 1
GRID 115 -373.75 -12.78 160.63
GRID 116 -373.75 -14.11 160.05
GRID 117 -512.50 -9.22 152.04
GRID 118 -512.50 -10.61 151.47
CQUAD 20 13 115 116 118 117 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 107 Stringer 7
SECTION 7 107 1 1
GRID 119 -373.75 19.11 157.41
GRID 120 -373.75 20.36 156.57
GRID 121 -512.50 13.95 149.68
GRID 122 -512.50 15.20 148.85
CQUAD 21 13 119 120 122 121 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 108 Stringer 8
SECTION 7 108 1 1
GRID 123 -373.75 -19.12 157.41
GRID 124 -373.75 -20.36 156.57
GRID 125 -512.50 -13.95 149.68
GRID 126 -512.50 -15.20 148.85
CQUAD 22 13 123 124 126 125 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 109 Stringer 9
SECTION 7 109 1 1
GRID 127 -373.75 24.70 153.01
GRID 128 -373.75 25.76 151.95
GRID 129 -512.50 18.13 146.44
GRID 130 -512.50 19.19 145.38
CQUAD 23 13 127 128 130 129 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 110 Stringer 10
SECTION 7 110 1 1
GRID 131 -373.75 -24.70 153.01
GRID 132 -373.75 -25.76 151.95
GRID 133 -512.75 -18.13 146.44
GRID 134 -512.75 -19.19 145.38
CQUAD 24 13 131 132 134 133 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 111 Stringer 11
SECTION 7 111 1 1
GRID 135 -373.75 29.32 147.61
GRID 136 -373.75 30.16 146.37
GRID 137 -512.50 21.60 142.45
GRID 138 -512.50 22.43 141.20
CQUAD 25 13 135 136 138 137 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 112 Stringer 12
SECTION 7 112 1 1
GRID 139 -373.75 -29.32 147.61
GRID 140 -373.75 -30.16 146.37
GRID 141 -512.50 -21.60 142.45
GRID 142 -512.50 -22.43 141.20
CQUAD 26 13 139 140 142 141 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 113 Stringer 13
SECTION 7 113 1 1
GRID 143 -373.75 32.80 141.41
GRID 144 -373.75 33.38 140.03
GRID 145 -512.50 24.22 137.86
GRID 146 -512.50 24.79 136.47
CQUAD 27 13 143 144 146 145 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 114 Stringer 14
SECTION 7 114 1 1
GRID 147 -373.75 -32.80 141.41
GRID 148 -373.75 -33.38 140.03
GRID 149 -512.50 -24.22 137.86
GRID 150 -512.50 -24.80 136.47
CQUAD 28 13 147 148 150 149 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 115 Stringer 15
SECTION 7 115 1 1
GRID 151 -373.75 35.01 134.66
GRID 152 -373.75 35.30 133.19
GRID 153 -512.50 25.90 132.85
GRID 154 -512.50 26.19 131.37
CQUAD 29 13 151 152 154 153 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 116 Stringer 16
SECTION 7 116 1 1
GRID 155 -373.75 -35.01 134.66
GRID 156 -373.75 -35.30 133.19
GRID 157 -512.50 -25.90 132.85
GRID 158 -512.50 -26.19 131.37
CQUAD 30 13 155 156 158 157 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 117 Stringer 17
SECTION 7 117 1 1
GRID 159 -373.75 35.85 127.60
GRID 160 -373.75 35.85 126.10
GRID 161 -512.50 26.56 127.60
GRID 162 -512.50 26.56 126.10
CQUAD 31 13 159 160 162 161 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 118 Stringer 18
SECTION 7 118 1 1
GRID 163 -373.75 -35.85 127.60
GRID 164 -373.75 -35.85 126.10
GRID 165 -512.50 -26.56 127.60
GRID 166 -512.50 -26.56 126.10
CQUAD 32 13 163 164 166 165 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 119 Stringer 19
SECTION 7 119 1 1
GRID 167 -373.75 35.30 121.31
GRID 168 -373.75 35.01 119.84
GRID 169 -512.50 26.19 123.13
GRID 170 -512.50 25.90 121.65
CQUAD 33 13 167 168 170 169 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 120 Stringer 20
SECTION 7 120 1 1
GRID 171 -373.75 -35.30 121.31
GRID 172 -373.75 -35.01 119.84
GRID 173 -512.50 -26.19 123.13
GRID 174 -512.50 -25.90 121.65
CQUAD 34 13 171 172 174 173 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 121 Stringer 21
SECTION 7 121 1 1
GRID 171 -373.75 -35.30 121.31
GRID 172 -373.75 -35.01 119.84
GRID 173 -512.50 -26.19 123.13
GRID 174 -512.50 -25.90 121.65
CQUAD 34 13 171 172 174 173 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 122 Stringer 22
SECTION 7 122 1 1
GRID 175 -373.75 33.38 114.47
GRID 176 -373.75 32.80 113.08
GRID 177 -512.50 24.79 118.03
GRID 178 -512.50 24.22 116.64
CQUAD 35 13 175 176 178 177 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 123 Stringer 23
SECTION 7 123 1 1
GRID 179 -373.75 -33.38 114.47
GRID 180 -373.75 -32.80 113.08
GRID 181 -512.50 -24.80 118.03
GRID 182 -512.50 -24.22 116.64
CQUAD 36 13 179 180 182 181 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 124 Stringer 24
SECTION 7 124 1 1
GRID 183 -373.75 30.16 108.14
GRID 184 -373.75 29.32 106.89
GRID 185 -512.50 22.43 113.30
GRID 186 -512.50 21.60 112.05
CQUAD 37 13 183 184 186 185 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 125 Stringer 25
SECTION 7 125 1 1
GRID 187 -373.75 -30.16 108.14
GRID 188 -373.75 -29.32 106.89
GRID 189 -512.50 -22.43 113.30
GRID 190 -512.50 -21.60 112.05
CQUAD 38 13 187 188 190 189 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 126 Stringer 26
SECTION 7 126 1 1
GRID 191 -373.75 25.76 102.55
GRID 192 -373.75 24.70 101.49
GRID 193 -512.50 19.19 109.12
GRID 194 -512.50 18.13 108.06
CQUAD 39 13 191 192 194 193 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 127 Stringer 27
SECTION 7 127 1 1
GRID 195 -373.75 -25.76 102.55
GRID 196 -373.75 -24.70 101.49
GRID 197 -512.50 -19.19 109.12
GRID 198 -512.50 -18.13 108.06
CQUAD 40 13 195 196 198 197 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 128 Stringer 28
SECTION 7 128 1 1
GRID 199 -373.75 20.36 97.93
GRID 200 -373.75 19.11 97.09
GRID 201 -512.50 15.20 105.65
GRID 202 -512.50 13.95 104.82
CQUAD 41 13 199 200 202 201 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 129 Stringer 29
SECTION 7 129 1 1
GRID 203 -373.75 -20.36 97.93
GRID 204 -373.75 -19.12 97.09
GRID 205 -512.50 -15.20 105.65
GRID 206 -512.50 -13.95 104.82
CQUAD 42 13 203 204 206 205 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 130 Stringer 30
SECTION 7 130 1 1
GRID 207 -373.75 14.16 94.45
GRID 208 -373.75 12.78 93.87
GRID 209 -512.50 10.61 103.03
GRID 210 -512.50 9.22 102.46
CQUAD 43 13 207 208 210 209 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 131 Stringer 31
SECTION 7 131 1 1
GRID 211 -373.75 -14.17 94.45
GRID 212 -373.75 -12.78 93.87
GRID 213 -512.50 -10.61 103.03
GRID 214 -512.50 -9.22 102.46
CQUAD 44 13 211 212 214 213 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 132 Stringer 32
SECTION 7 132 1 1
GRID 215 -373.75 7.41 92.24
GRID 216 -373.75 5.94 91.95
GRID 217 -512.50 5.59 101.35
GRID 218 -512.50 4.13 101.06
CQUAD 45 13 215 216 218 217 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 133 Stringer 33
SECTION 7 133 1 1
GRID 219 -373.75 -7.41 92.24
GRID 220 -373.75 -5.94 91.95
GRID 221 -512.50 -5.59 101.35
GRID 222 -512.50 -4.13 101.06
CQUAD 46 13 219 220 222 221 0.045 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 201 Fairing Structure 1
SECTION 7 201 1 1
GRID 228 -389.50 29.69 78.52
GRID 229 -389.50 -29.69 78.52
GRID 230 -389.50 29.69 108.35
GRID 231 -389.50 -29.69 108.35
CQUAD 11 8 228 229 231 230 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 202 Fairing Structure 2
SECTION 7 202 1 1
GRID 232 -405.50 25.83 81.35
GRID 233 -405.50 -25.83 81.35
GRID 234 -405.50 25.83 104.95
GRID 235 -405.50 -25.83 104.95
CQUAD 12 8 232 233 235 234 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 203 Fairing Structure 3
SECTION 7 203 1 1
GRID 236 -423.00 21.61 84.44
GRID 237 -423.00 -21.61 84.44
GRID 238 -423.00 21.61 102.37
GRID 239 -423.00 -21.61 102.37
CQUAD 13 8 236 237 239 238 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 204 Fairing Structure 4
SECTION 7 204 1 1
GRID 240 -442.50 16.90 87.89
GRID 241 -442.50 -16.90 87.89
GRID 242 -442.50 16.90 100.49
GRID 243 -442.50 -16.90 100.49
CQUAD 14 8 240 241 243 242 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 205 Fairing Structure 5
SECTION 7 205 1 1
GRID 244 -461.50 12.31 91.25
GRID 245 -461.50 -12.31 91.25
GRID 246 -461.50 12.31 99.48
GRID 247 -461.50 -12.31 99.48
CQUAD 15 8 244 245 247 246 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 206 Fairing Structure 6
SECTION 7 206 1 1
GRID 248 -479.50 7.97 94.43
GRID 249 -479.50 -7.97 94.43
GRID 250 -479.50 7.97 99.19
GRID 251 -479.50 -7.97 99.19
CQUAD 16 8 248 249 251 250 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 207 Fairing Structure 7
SECTION 7 207 1 1
GRID 252 -496.50 3.86 97.44
GRID 253 -496.50 -3.86 97.44
GRID 254 -496.50 3.86 99.49
GRID 255 -496.50 -3.86 99.49
CQUAD 17 8 252 253 255 254 0.032 1
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
$NAME 7 501 Pressure Bulkhead
SECTION 7 501 2
GRID 330 -373.25 -0.00 127.25
GRID 331 -373.75 -0.00 127.25
CCONE2 18 8 330 331 36.25C106
C106 36.25 0 0
$COMMENT123456781234567812345678123456781234567812345678123456781234567812345678
ENDDATA
-44
View File
@@ -1,44 +0,0 @@
set(FAA_SAMPLE_MODELS
Business_Jet.fg4
Generic_Twin.fg4
)
macro(ADD_FAA_G_TARGET faa_model folder)
string(REGEX REPLACE "([0-9a-z]*).fg4" "\\1" faa_model_root "${faa_model}")
set(output_file ${bin_root}/${DATA_DIR}/db/${faa_model_root}.g)
set(log_file ${CMAKE_CURRENT_BINARY_DIR}/${faa_model_root}.log)
add_custom_command(
OUTPUT ${output_file}
COMMAND fast4-g ${CMAKE_CURRENT_SOURCE_DIR}/${faa_model} ${output_file} > ${log_file} 2>&1
DEPENDS fast4-g ${CMAKE_CURRENT_SOURCE_DIR}/${faa_model}
)
add_custom_target(${faa_model_root}.g ALL DEPENDS ${output_file})
set_target_properties(${faa_model_root}.g PROPERTIES FOLDER "${folder}")
if(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
if(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
string(REPLACE "${CMAKE_CFG_INTDIR}" "\${BUILD_TYPE}" output_file "${output_file}")
endif(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
install(FILES ${output_file} DESTINATION ${DATA_DIR}/db)
endif(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
set(BUILT_MODELS "${BUILT_MODELS};${output_file}")
set(LOG_FILES "${LOG_FILES};${log_file}")
DISTCLEAN(${log_file})
endmacro(ADD_FAA_G_TARGET faa_model folder)
foreach(faa_input ${FAA_SAMPLE_MODELS})
ADD_FAA_G_TARGET(${faa_input} "BRL-CAD Geometry Models/Sample")
endforeach(faa_input ${FAA_SAMPLE_MODELS})
CMAKEFILES(
${FAA_SAMPLE_MODELS}
README
)
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${BUILT_MODELS}")
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${LOG_FILES}")
# Local Variables:
# tab-width: 8
# mode: cmake
# indent-tabs-mode: t
# End:
# ex: shiftwidth=2 tabstop=8
File diff suppressed because it is too large Load Diff
-8
View File
@@ -1,8 +0,0 @@
For example images of these models, see the report:
Uncontained Engine Debris Analysis Using the Uncontained
Engine Debris Damage Assessment Model
DOT/FAA/AR-04/16
Office of Aviation Research
Washington, D.C. 20591
http://www.tc.faa.gov/its/worldpac/techrpt/AR04-16.pdf
-111
View File
@@ -1,111 +0,0 @@
set(NIST_SAMPLE_STEP_MODELS
NIST_MBE_PMI_1.stp
NIST_MBE_PMI_2.stp
NIST_MBE_PMI_3.stp
NIST_MBE_PMI_4.stp
NIST_MBE_PMI_5.stp
NIST_MBE_PMI_6.stp
NIST_MBE_PMI_11.stp
)
set(NIST_SAMPLE_3DM_MODELS
NIST_MBE_PMI_7-10.3dm
)
macro(ADD_NIST_STEP_TARGET step_model folder)
string(REGEX REPLACE "([0-9a-z]*).stp" "\\1" step_model_root "${step_model}")
set(output_file ${bin_root}/${DATA_DIR}/db/${step_model_root}.g)
set(log_file ${CMAKE_CURRENT_BINARY_DIR}/${step_model_root}.log)
add_custom_command(
OUTPUT ${output_file}
COMMAND step-g -O ${output_file} ${CMAKE_CURRENT_SOURCE_DIR}/${step_model} > ${log_file} 2>&1
DEPENDS step-g ${CMAKE_CURRENT_SOURCE_DIR}/${step_model}
)
add_custom_target(${step_model_root}.g ALL DEPENDS ${output_file})
set_target_properties(${step_model_root}.g PROPERTIES FOLDER "${folder}")
if(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
if(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
string(REPLACE "${CMAKE_CFG_INTDIR}" "\${BUILD_TYPE}" output_file "${output_file}")
endif(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
install(FILES ${output_file} DESTINATION ${DATA_DIR}/db)
endif(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
set(BUILT_MODELS "${BUILT_MODELS};${output_file}")
set(LOG_FILES "${LOG_FILES};${log_file}")
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)
add_custom_command(
OUTPUT ${output_file}
COMMAND ${CMAKE_COMMAND} -P ${CMAKE_CURRENT_BINARY_DIR}/3dm-g.cmake
DEPENDS 3dm-g ${CMAKE_CURRENT_SOURCE_DIR}/${rhino_model}
)
add_custom_target(${rhino_model_root}.g ALL DEPENDS ${output_file})
set_target_properties(${rhino_model_root}.g PROPERTIES FOLDER "${folder}")
if(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
if(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
string(REPLACE "${CMAKE_CFG_INTDIR}" "\${BUILD_TYPE}" output_file "${output_file}")
endif(NOT "${CMAKE_CFG_INTDIR}" STREQUAL "." AND CMAKE_CONFIGURATION_FILES)
install(FILES ${output_file} DESTINATION ${DATA_DIR}/db)
endif(BRLCAD_INSTALL_EXAMPLE_GEOMETRY)
set(BUILT_MODELS "${BUILT_MODELS};${output_file}")
set(LOG_FILES "${LOG_FILES};${log_file}")
DISTCLEAN(${log_file})
endmacro(ADD_NIST_3DM_TARGET rhino_model folder)
foreach(step_input ${NIST_SAMPLE_STEP_MODELS})
ADD_NIST_STEP_TARGET(${step_input} "BRL-CAD Geometry Models/Sample")
endforeach(step_input ${NIST_SAMPLE_STEP_MODELS})
CMAKEFILES(${NIST_SAMPLE_STEP_MODELS})
foreach(rhino_input ${NIST_SAMPLE_3DM_MODELS})
ADD_NIST_3DM_TARGET(${rhino_input} "BRL-CAD Geometry Models/Sample")
endforeach(rhino_input ${NIST_SAMPLE_3DM_MODELS})
CMAKEFILES(${NIST_SAMPLE_3DM_MODELS})
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${BUILT_MODELS}")
set_property(DIRECTORY APPEND PROPERTY ADDITIONAL_MAKE_CLEAN_FILES "${LOG_FILES}")
CMAKEFILES(
README
pdf
)
# Local Variables:
# tab-width: 8
# mode: cmake
# indent-tabs-mode: t
# End:
# ex: shiftwidth=2 tabstop=8
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
File diff suppressed because it is too large Load Diff
Binary file not shown.
-37
View File
@@ -1,37 +0,0 @@
December 2014:
The files in this directory are conversions of the NIST MBE PMI test models
into the AP203 file format. These conversions are also in the public domain.
Originals are from http://www.nist.gov/el/msid/infotest/mbe-pmi-validation.cfm
Models 7 through 10 have been assembled into a single file, guided by the example
PDF provided with the original NIST data set.
MBE PMI Validation and Conformance Testing Models
NIST has created a Test System to measure conformance of Computer-Aided Design
(CAD) to American Society of Mechanical Engineers (ASME) standards for Product
and Manufacturing Information (PMI), specifically geometric dimensioning and
tolerancing (GD&T) information.
As part of this Test System, CAD Models were prepared.
For problems or questions about the MBE PMI CAD Models, contact: Robert Lipman
Dataset 1 First Release: December 2013
Dataset 1 Update Release: December 2014 (Note: Dataset 1 files currently in
BRL-CAD repo are based off of the
2013 version.)
Dataset 2 First Release: June 2015
These files were developed at the National Institute of Standards and
Technology by employees of the Federal Government in the course of their
official duties. Pursuant to Title 17 Section 105 of the United States Code
these files are not subject to copyright protection and are in the public
domain. These files are an experimental system. NIST assumes no responsibility
whatsoever for their use by other parties, and makes no guarantees, expressed
or implied, about their quality, reliability, or any other characteristic.
Any mention of commercial products is for information only; it does not imply
recommendation or endorsement by NIST.
BIN
View File
Binary file not shown.
Binary file not shown.
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
BIN
View File
Binary file not shown.
+13 -196
View File
@@ -2,6 +2,9 @@
%
% This file contains bibliographic information pertaining to BRL-CAD.
%
% To be added:
% http://www.arl.army.mil/arlreports/2001/ARL-TR-2396.pdf
%
%%%
@@ -55,7 +58,6 @@
number = {V5S10A04},
pages = {pp. 1-12},
address = {Aberdeen Proving Ground, Maryland 21005-5066},
note = {Reprinted by ARL in 2013 as ARL-RP-429.}
owner = {cyapp},
timestamp = {2008.02.05}
}
@@ -348,9 +350,8 @@
pages = {pp. 1-5},
address = {Aberdeen Proving Ground, Maryland 21005-5066},
month = {November},
note = {Reprinted by ARL in 2013 as ARL-RP-428.}
owner = {morrison},
timestamp = {2015.11.19}
owner = {cyapp},
timestamp = {2008.02.05}
}
@INCOLLECTION{Stiller88a,
@@ -639,20 +640,6 @@
timestamp = {2008.02.05}
}
@PROCEEDING{doi:10.1117/12.960423,
author = {Jones, J. and Gonda, T.},
title = {A Thermal Model Preprocessor For Graphics And Material Database Generation},
journal = {Proc. SPIE},
volume = {1098},
number = {},
pages = {42-54},
abstract = {The process of developing a physical description of a target for thermal models is a time consuming and tedious task. The problem is one of data collection, data manipulation, and data storage. Information on targets can come from many sources and therefore could be in any form (2-D drawings, 3-D wireframe or solid model representations, etc.). TACOM has developed a preprocessor that decreases the time involved in creating a faceted target representation. This program allows the user to create the graphics for the vehicle and to assign the material properties to the graphics. The vehicle description file is then automatically generated by the preprocessor. By containing all the information in one database, the modeling process is made more accurate and data tracing can be done easily. A bridge to convert other graphics packages (such as BRL-CAD) to a faceted representation is being developed. When the bridge is finished, this preprocessor will be used to manipulate the converted data.},
year = {1989},
doi = {10.1117/12.960423},
URL = { http://dx.doi.org/10.1117/12.960423},
eprint = {}
}
@INCOLLECTION{Deitz90b,
author = {Deitz, Paul H.},
title = {High-Resolution, Item-Level Weapons Modeling},
@@ -884,9 +871,8 @@ eprint = {}
number = {V1S03A00},
pages = {pp. 1-9},
address = {Aberdeen Proving Ground, Maryland 21005-5066},
note = {Reprinted by ARL in 2013 as ARL-RP-432.}
owner = {morrison},
timestamp = {2015.11.19}
owner = {cyapp},
timestamp = {2008.02.05}
}
@INPROCEEDINGS{Eberius91a,
@@ -1639,19 +1625,6 @@ eprint = {}
timestamp = {2010.02.23}
}
@TECHREPORT{Kunkel01,
author = {Kunkel, Robert W., Jr. and Anderson, John R.},
title = {Conversion Process of a Ballistic Research Laboratory Computer-Aided Design (BRL-CAD) Model to a Panelized Surface Model (PSM)},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2001},
month = {February},
number = {ARL-TR-2396},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release; Distribution is Unlimited.},
owner = {morrison},
timestamp = {2015.11.19}
}
@INPROCEEDINGS{Keyser02a,
author = {Keyser, John and Culver, Tim and Foskey, Mark and Krishnan, Shankar
and Manocha, Dinesh},
@@ -1811,7 +1784,8 @@ eprint = {}
author = {Tabary, Joachim and Hugonnard, Patrick and Mathy, Francoise},
title = {SINDBAD : a realistic multi-purpose and scalable X-ray simulation
tool for NDT applications},
booktitle = {Proceedings DIR 2007 - International Symposium on Digital industrial Radiology and Computed Tomography},
booktitle = {Proceedings DIR 2007 - International Symposium on Digital industrial
Radiology and Computed Tomography},
year = {2007},
month = {June},
note = {http://www.ndt.net/article/dir2007/papers/s4.pdf},
@@ -1819,23 +1793,11 @@ eprint = {}
timestamp = {2008.02.08}
}
@TECHREPORT{Mallory07,
author = {Mallory, Timothy},
title = {A 3-D Scanning Technique for Determining Fragment Shape Factor},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2007},
month = {July},
number = {ARL-TR-4183},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Distribution authorized to the Department of Defense and U.S. DOD contractors only; critical technology (July 2007). Other requests for this document shall be referred to Director, U.S. Army Research Laboratory, ATTN: AMSRD-ARL-SL-BM, Aberdeen Proving Ground, MD 21005-5068.},
owner = {morrison},
timestamp = {2015.12.16}
}
@TECHREPORT{Yapp09a,
author = {Yapp, Clifford},
title = {Interactive Raytracing: The nirt Command},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality
Analysis Directorate},
year = {2009},
month = {April},
number = {ARL-CR-624},
@@ -1848,7 +1810,8 @@ eprint = {}
@TECHREPORT{Yapp09b,
author = {Yapp, Clifford},
title = {Vehicle Tire and Wheel Creation in BRL-CAD},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality
Analysis Directorate},
year = {2009},
month = {April},
number = {ARL-CR-625},
@@ -1887,152 +1850,6 @@ eprint = {}
timestamp = {2010.02.23}
}
@TECHREPORT{Yapp12,
author = {Yapp, Clifford},
title = {Generating Coils in BRL-CAD},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2012},
month = {April},
number = {ARL-CR-691},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2012/ARL-CR-691.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Muuss13,
author = {Muuss, Michael John},
title = {RT \& REMRT Shared Memory Parallel and Network Distributed Ray-Tracing Programs},
institution = {United States Army, Army Research Laboratory},
year = {2013},
month = {April},
number = {ARL-RP-429},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2013/ARL-RP-429.pdf},
owner = {morrison},
timestamp = {2015.11.19}
note = {This is a reprint from the Fourth USENIX Computer Graphics Workshop, Cambridge, MA, 9 Oct 1987.}
}
@TECHREPORT{Stay13,
author = {Stay, Paul R.},
title = {The Definition and Ray-Tracing of B-Spline Objects in a Combinatorial Solid Geometric Modeling System},
institution = {United States Army, Army Research Laboratory},
year = {2013},
month = {April},
number = {ARL-RP-428},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2013/ARL-RP-428.pdf},
owner = {morrison},
timestamp = {2015.11.19}
note = {This is a reprint from the Fourth USENIX Computer Graphics Workshop, Cambridge, MA, 9 Oct 1987.}
}
@TECHREPORT{Dykstra13,
author = {Dykstra, Phillip C.},
title = {The BRL-CAD Package - An Overview},
institution = {United States Army, Army Research Laboratory},
year = {2013},
month = {April},
number = {ARL-RP-432},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2013/ARL-RP-432.pdf},
owner = {morrison},
timestamp = {2015.11.19}
note = {This is a reprint from the Fourth USENIX Computer Graphics Workshop, Cambridge, MA, 9 Oct 1987.}
}
@TECHREPORT{Yapp13,
author = {Yapp, Clifford W.},
title = {The BRL-CAD CMake Build System - An Overview},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2013},
month = {June},
number = {ARL-TR-6475},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2013/ARL-TR-6475.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Ranawake15,
author = {Ranawake, Charith},
title = {The Verification and Validation of the Ray-tracing of Bag of Triangles (BoTs)},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {February},
number = {ARL-CR-0761},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2015/ARL-CR-0761.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Jain15,
author = {Jain, Rishub},
title = {Converting Between PLY and Ballistic Research Laboratory Computer-Aided Design (BRL-CAD) Formats},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {February},
number = {ARL-CR-0760},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited.. Available online: http://www.arl.army.mil/arlreports/2015/ARL-CR-0760.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Roberts15,
author = {Roberts, Mitchell},
title = {Comprehensive BRL-CAD Primitive Database},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {March},
number = {ARL-CR-0764},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2015/ARL-CR-0764.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Nichols15,
author = {Nichols, Steven J.},
title = {Uniform Tests of File Converters Using Unit Cubes},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {March},
number = {ARL-CR-0770},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2015/ARL-CR-0770.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Butler15,
author = {Butler, Lee A. and Yapp, Clifford},
title = {Adaptive Geometry Shader Tessellation for Massive Geometry Display},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {March},
number = {ARL-SR-0312},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2015/ARL-SR-0312.pdf},
owner = {morrison},
timestamp = {2015.11.19}
}
@TECHREPORT{Yapp15,
author = {Yapp, Clifford},
title = {An Investigation into Conversion from Non-Uniform Rational B-Spline Boundary Representation Geometry to Constructive Solid Geometry},
institution = {United States Army, Army Research Laboratory, Survivability/Lethality Analysis Directorate},
year = {2015},
month = {December},
number = {ARL-SR-0347},
address = {Army Research Laboratory, Aberdeen Proving Ground, MD 21005-5068},
note = {Approved for Public Release, distribution unlimited. Available online: http://www.arl.army.mil/arlreports/2015/ARL-SR-0347.pdf},
owner = {morrison},
timestamp = {2015.12.01}
}
@comment{jabref-meta: selector_journal:}
@comment{jabref-meta: selector_author:}
+3 -6
View File
@@ -27,10 +27,8 @@ set(documentation_DATA
benchmark.tr
brep.txt
BRL-CAD.bib
code_review.txt
cvs.txt
description.txt
editors.txt
ged.tr
history.txt
hypot.txt
@@ -218,17 +216,16 @@ set(documentation_mged_old_DATA
)
ADD_DOC(documentation_mged_old_DATA mged_old)
configure_file(pad_file.xml.in "${CMAKE_CURRENT_BINARY_DIR}/pad_file.xml" @ONLY)
install(FILES "${CMAKE_CURRENT_BINARY_DIR}/pad_file.xml" DESTINATION ${DOC_DIR})
configure_file(pad_file.xml.in ${CMAKE_CURRENT_BINARY_DIR}/pad_file.xml @ONLY)
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/pad_file.xml DESTINATION ${DOC_DIR})
CMAKEFILES(
README.OSCON-2014
STARTERS
STRATEGY
burst
csv_to_comgeom.txt
implicit_constraints.txt
pad_file.xml.in
trunk_hierarchy.org
)
# Local Variables:
-11
View File
@@ -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
+2 -2
View File
@@ -56,7 +56,7 @@ Following the build instructions in the INSTALL file. You will need:
gcc (3+, e.g. 4.0.3)
g++ (3+, e.g. 4.0.3)
make (e.g. gnu make 3.8.0)
cmake (2.8.8 or newer)
cmake (2.8.3 or newer)
All three of those have implicit dependencies on other packages.
@@ -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:
+1 -8
View File
@@ -85,13 +85,6 @@ non-parallel build will still succeed. Another workaround is to build
just subdirectories (e.g. src/other, doc, etc.) individually and then
do a toplevel make in non-parallel mode to finalize the build.
OpenSceneGraph and OSX
----------------------
For 32bit OSX builds of an X11+OpenSceneGraph BRL-CAD:
cmake .. -DBRLCAD_BUNDLED_LIBS=BUNDLED -DBRLCAD_ENABLE_OSG=ON
-DBRLCAD_REGEX=SYSTEM -DBRLCAD_WORD_SIZE=32BIT -DOSG_WINDOWING_SYSTEM=X11
Tips
----
@@ -104,6 +97,6 @@ uname -a
Bugs
----
The only known bugs specific to Mac OS X are limitations of Tk or the
X11 event handler that are generally outside of BRL-CAD's domain.
X11 event handler that our generally outside of BRL-CAD's domain.
Refer to BUGS for more general details on known bugs and reporting
mechanisms.
+2 -24
View File
@@ -3,17 +3,14 @@ BRL-CAD on Windows README
The usual way to build BRL-CAD for Windows is to use the CMake build
system generator and the Microsoft Visual Studio C++ (MSVC) compiler.
Recent versions of both (as of this writing, MSVC 2013 and CMake
2.8.12+) are recommended. If generating an installer, the Nullsoft
Recent versions of both (as of this writing, MSVC 2010 and CMake
2.8.6+) are recommended. If generating an installer, the Nullsoft
Scriptable Install System (NSIS) tool is also required.
In principle, BRL-CAD can be built using CMake and environments like
Cygwin and/or Mingw/Msys, but the is largely untested and infrequently
supported. Enhancements or bug reports are welcome.
Visual Studio
-------------
To build with CMake and Visual Studio, the first step is to obtain the
BRL-CAD sources and create a build directory. In principle, it is not
*required* to have a separate build directory, but with Windows and
@@ -46,22 +43,3 @@ ALL_BUILD. Start compiling that target.
Once compilation is successfully complete, you may want to produce an
NSIS installer. If so, locate a target named PACKAGE and run it. The
end result should be an .exe file capable of installing BRL-CAD.
MINGW (WORK IN PROGRESS - THIS DOES NOT YET WORK!!!)
-----
After installing the MINGW system, set up as follows:
set path=%path%;"C:\Program Files (x86)\CMake\bin"
set path=%path%;C:\MinGW\bin
now make a build directory, and run CMake:
cmake ..\brlcad -G "MinGW Makefiles" -DBRLCAD_BUNDLED_LIBS=BUNDLED
mingw32-make
Note that you don't want to do this from an msys prompt that has
sh in the path. (ConEmu can make using the standard Windows command
prompt a bit more tolerable: http://conemu.github.io)
-323
View File
@@ -1,323 +0,0 @@
# -*- mode: org; coding: utf-8; -*- #
# This is an Emacs org-mode file. Keybindings: http://orgmode.org/orgcard.txt
# +TAGS: { UX : U u } { Complex : C c }
# +TAGS: { Comms : P p } { Market : M m }
BRL-CAD Development Strategy
This is a living document that defines and aims to help maintain a
consistent develpment strategy for addressing BRL-CAD requirements.
It recognizes areas of strategic importance, outlines projects to
bolster those areas, and identifies specific actionable objectives.
* Strategic Areas
This section itemizes areas of strategic importance which coincide
closely with areas of categoric deficiency. For each area, we
outline general activities that could strengthen them. From these
areas, we conceive strategic projects and their associated tasks.
** AREA 1: UX :UX:
*** deploying Archer/MGED -cns :p:C:
*** UI simplification -s :C:
*** undo / fault tolerance -n
*** prototype Qt -c :p:
*** UI design / clarification -j :P:C:
*** interaction / integration -j :M:
*** editing constraints, snapping, reuse existing coordinates
*** bug reporting / feature requests :P:
*** portability :p:
** AREA 2: Complexity :Complex:
*** command / tool reduction -cjns :U:
*** API code reduce / simplification / modularity -cjs :U:
*** searchability / info -n :U:p:
*** discoverability / documentation (UP) :U:P:
*** UI design / clarity (UP)
*** restructure of file hierarchy
*** continuous integration
** AREA 3: Communications :Comms:
*** website -cjns :C:
*** doc integration, website -cjns :C:
*** new content (audience / customer profiles), website :C:
*** comms (meeting / promoting our successes / PRB / announcements) :U:C:M:
*** CRM / IRC :U:C:
*** leverage existing capability
** AREA 4: Marketability :Market:
FIXME: these need to be sorted and ranked
*** conversion: import, processing, export -s :P:U:
*** geometry analysis performance (interactive ray tracing / opencl) :U:
*** 3D printing / polygonal export / gcode -s :P:U:
*** industrial design: blueprinting, dimensioning, annotations :P:U:
*** geometry preparation (killing overlaps, hierarchy, V&V) :U:C:
*** visuals: advanced rendering, animation, simulation :P:U:
* Strategic Projects
This section itemizes projects conceived to address BRL-CAD's
principal strategic areas. Each project focuses on one or more
strategic areas devising measurable tasks that support the
particular objective.
** 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)
*** 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)
** PROJECT: Deploy Merged Archer/MGED Final (16)
*** 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)
*** undo - BETA (2)
**** TODO implement libbu filesystem info (1)
**** TODO re-enable undo with fs awareness (1)
*** 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)
** PROJECT: Distilling BRL-CAD (11)
*** revisit scope (vision, mission) (3)
**** TODO communicate intent and updates (1)
**** TODO develop high-level project roadmap (1)
**** TODO connect features to markets (1)
*** 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)
*** 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)
** PROJECT: Website Renovation (10)
*** 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)
*** 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)
*** 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)
*** 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)
** PROJECT: Deploy GCV (9)
*** 3dm "round-tripping" (2)
**** TODO integrate existing importer (0)
**** TODO NURBS export support (1)
**** TODO document entity support (1)
*** 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)
**** TODO document the prep cache interface (1)
** PROJECT: Progressive Geometry Display (11)
*** asynchronous geometry display (4)
**** TODO modify display loop to run in separate thread (2)
**** TODO update draw command to dispatch (2)
*** ray trace display manager (4)
**** TODO review rtgl code (1)
**** TODO design incremental loading architecture (1)
**** TODO implement incremental ray tracing (2)
*** 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)
** TEMPLATE: Project Title
Here is an example project that summarizes the taxonomy and
structure of a strategic project. A project should be scoped to
less than 4 months of full-time uninterrupted effort. A project
must have at least 1 objective.
*** objective
Objectives should be simple with identifiable completion criteria.
An objective should be achievable in 4 weeks or less with larger
objectives divided into separate smaller chunks. Each objective
must have at least 1 task.
**** TODO task
A task is actionable work that should take someone 4 weeks or
less of full-time uninterrupted effort, estimated in weeks, with
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:
+30
View File
@@ -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;
}
+11
View 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
+22
View File
@@ -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
+27
View File
@@ -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
+64
View File
@@ -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>
+15
View File
@@ -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
+37
View File
@@ -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
+995
View File
@@ -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
+12
View File
@@ -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
+55
View File
@@ -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
+21
View File
@@ -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
+15
View File
@@ -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
+12
View File
@@ -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
+11
View File
@@ -0,0 +1,11 @@
.TS
center,box;
l.
600-999
1011
4002-4050
8000
9001
9004
9005
.TE
+53
View File
@@ -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.
+28
View File
@@ -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)\^
..
+48
View File
@@ -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
+18
View File
@@ -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
+13
View File
@@ -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
+10
View File
@@ -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'"
+54
View File
@@ -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
+12
View File
@@ -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
+29
View File
@@ -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
+12
View File
@@ -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
+10
View File
@@ -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"
+12
View File
@@ -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
-48
View File
@@ -1,48 +0,0 @@
BRL-CAD Code Review
===================
...what to look for during a review...
Legal:
* proper copyright statement and compatible license?
* any indication contribution disagrees with copyright assignment?
* if incorporating 3rd party code, prefer bsd/mit-style options
Architecture:
* proper location in hierarchy?
* proper file name(s)?
* is a dependency being introduced?
* is a cyclic dependency being introduced?
* are any global variables being introduced?
Design:
* is public API minimized?
* is a platform symbol being used?
* does the change reduce or violate modularity?
* is the approach being taken reasonable?
* is the code easy to understand?
Testing:
* compiles cleanly?
* are warnings handled cleanly?
* any blatant logic errors?
* are all data inputs checked properly, sanitized?
* if fixing a bug more than once, is there a test?
* is a unit test warranted?
* are there major robustness issues?
Documentation:
* if publicly visible, is NEWS updated?
* if public API changed, is CHANGES updated?
* if public API introduced, does every symbol have a comment?
* if interface changed, are man page or other docs updated?
* are numeric constants documented?
* is suspicious, complex, risky code commented?
Code:
* conforms with style and coding standards?
* proper indentation, formatting, whitespace?
* are symbol names consistent?
* is duplication being introduced, refactoring warranted?
* is there undocumented dead / commented-out code?
* can any code be replaced with library calls?
+27 -5
View File
@@ -11,16 +11,13 @@ string(REPLACE " " "%20" DOCBOOK_BINARY_DIR "${CMAKE_BINARY_DIR}")
string(REPLACE " " "%20" DOCBOOK_SOURCE_DIR "${CMAKE_SOURCE_DIR}")
# Common stylesheets for all DocBook sources
if(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_PDF OR BRLCAD_EXTRADOCS_MAN OR BRLCAD_EXTRADOCS_PHP OR BRLCAD_EXTRADOCS_PPT)
if(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_PDF OR BRLCAD_EXTRADOCS_MAN)
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/resources/brlcad/brlcad-common.xsl.in
${CMAKE_CURRENT_BINARY_DIR}/resources/brlcad/brlcad-common.xsl)
# Fonts definition
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/resources/brlcad/brlcad-fonts.xsl.in
${CMAKE_CURRENT_BINARY_DIR}/resources/brlcad/brlcad-fonts.xsl)
# Wordpress
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/resources/brlcad/wordpress.xsl.in
${CMAKE_CURRENT_BINARY_DIR}/resources/brlcad/wordpress.xsl)
endif(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_PDF OR BRLCAD_EXTRADOCS_MAN OR BRLCAD_EXTRADOCS_PHP OR BRLCAD_EXTRADOCS_PPT)
endif(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_PDF OR BRLCAD_EXTRADOCS_MAN)
# Files for PDF products
if(BRLCAD_EXTRADOCS_PDF)
@@ -50,6 +47,31 @@ add_subdirectory(presentations)
add_subdirectory(specifications)
add_subdirectory(system)
# Now that we have all the individual targets listed by the DocBook.cmake
# macros, define convenience targets
if(BRLCAD_EXTRADOCS_HTML)
get_property(BRLCAD_EXTRADOCS_HTML_TARGETS GLOBAL PROPERTY BRLCAD_EXTRADOCS_HTML_TARGETS)
add_custom_target(doc_html DEPENDS ${BRLCAD_EXTRADOCS_HTML_TARGETS})
set_target_properties(doc_html PROPERTIES FOLDER "DocBook")
endif(BRLCAD_EXTRADOCS_HTML)
if(BRLCAD_EXTRADOCS_MAN)
get_property(BRLCAD_EXTRADOCS_MAN_TARGETS GLOBAL PROPERTY BRLCAD_EXTRADOCS_MAN_TARGETS)
add_custom_target(doc_man DEPENDS ${BRLCAD_EXTRADOCS_MAN_TARGETS})
set_target_properties(doc_man PROPERTIES FOLDER "DocBook")
endif(BRLCAD_EXTRADOCS_MAN)
if(BRLCAD_EXTRADOCS_PDF)
get_property(BRLCAD_EXTRADOCS_PDF_TARGETS GLOBAL PROPERTY BRLCAD_EXTRADOCS_PDF_TARGETS)
add_custom_target(doc_pdf DEPENDS ${BRLCAD_EXTRADOCS_PDF_TARGETS})
set_target_properties(doc_pdf PROPERTIES FOLDER "DocBook")
endif(BRLCAD_EXTRADOCS_PDF)
if(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_MAN OR BRLCAD_EXTRADOCS_PDF)
add_custom_target(doc_all DEPENDS
${BRLCAD_EXTRADOCS_HTML_TARGETS}
${BRLCAD_EXTRADOCS_MAN_TARGETS}
${BRLCAD_EXTRADOCS_PDF_TARGETS})
set_target_properties(doc_all PROPERTIES FOLDER "DocBook")
endif(BRLCAD_EXTRADOCS_HTML OR BRLCAD_EXTRADOCS_MAN OR BRLCAD_EXTRADOCS_PDF)
CMAKEFILES(README fop.xconf.in log4j.properties resources)
CMAKEFILES(README.DB_authors_notes)
CMAKEFILES(css/brlcad.css)
+1 -7
View File
@@ -4,11 +4,6 @@ if(BRLCAD_EXTRADOCS_HTML)
${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/brlcad-article-xhtml-stylesheet.xsl)
endif(BRLCAD_EXTRADOCS_HTML)
if(BRLCAD_EXTRADOCS_PHP)
configure_file(${CMAKE_CURRENT_SOURCE_DIR}/../resources/brlcad/brlcad-article-xhtml-stylesheet.xsl.in
${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/brlcad-article-xhtml-stylesheet.xsl)
endif(BRLCAD_EXTRADOCS_PHP)
# Files for PDF products
if(BRLCAD_EXTRADOCS_PDF)
# Style sheet for XSLT transformation to PDF
@@ -19,8 +14,7 @@ endif(BRLCAD_EXTRADOCS_PDF)
# For HTML and FO (FO is an intermediate file used in the
# XML->PDF transformation) we use variables to hold the full
# stylesheet path.
set(XSL_PHP_STYLESHEET "${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/wordpress.xsl")
set(XSL_HTML_STYLESHEET "${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/brlcad-article-xhtml-stylesheet.xsl")
set(XSL_XHTML_STYLESHEET "${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/brlcad-article-xhtml-stylesheet.xsl")
set(XSL_FO_STYLESHEET "${CMAKE_CURRENT_BINARY_DIR}/../resources/brlcad/brlcad-article-fo-stylesheet.xsl")
add_subdirectory(en)
+8 -59
View File
@@ -1,26 +1,18 @@
set(articles_EN
set(docbook_articles_EN
TEMPLATE.xml
about.xml
animation_tutorial.xml
build_pattern.xml
build_region.xml
camo_shader.xml
ebm_primitive.xml
gcv.xml
ged.xml
mgedrc.xml
nirt.xml
oed.xml
pipes.xml
projection_shader.xml
tire.xml
mged.xml
main_menu.xml
)
set(articles_EN_IMAGES
images/Lee_tux.gif
images/animtbl.gif
set(docbook_articles_EN_IMAGES
images/build_pattern_fig01.png
images/build_pattern_fig02.png
images/build_pattern_fig03.png
@@ -32,26 +24,12 @@ set(articles_EN_IMAGES
images/build_region_fig02.png
images/build_region_fig03.png
images/build_region_fig04.png
images/dagtbl.gif
images/ebm_primitive_fig01.png
images/ebm_primitive_fig02.png
images/ebm_primitive_fig03.png
images/ell.mpg
images/ell_sm.gif
images/ell_ssm.gif
images/equation.gif
images/film.gif
images/fn.gif
images/gcv_architecture.png
images/gcv_unsupported_tessellation.png
images/gcv_using_gdiff.png
images/matrix.gif
images/mgedrc_fig01.png
images/mgedrc_fig02.png
images/mgedrc_fig03.png
images/moss.mpg
images/moss_sm.gif
images/moss_ssm.gif
images/nirt_fig01.png
images/nirt_fig02.png
images/nirt_fig03.png
@@ -123,43 +101,14 @@ set(articles_EN_IMAGES
images/tire_fig12.png
images/tire_fig13.png
images/tire_fig14.png
images/trans.gif
images/transboth.gif
images/transboth_sm.gif
images/v_eqn1.gif
images/v_eqn2.gif
images/azel.jpg
images/az_el.gif
images/az_el.jpg
images/az_el_sm.gif
images/base.gif
images/base.jpg
images/bool.gif
images/coord-axes.gif
images/cup_and_mug.gif
images/cup_and_mug_small.gif
images/cup_out+in.gif
images/cup_outside.gif
images/cup_w_handle.gif
images/faceplate.gif
images/faceplate_menu.gif
images/faceplate_menu_sm.gif
images/faceplate_sm.gif
images/fillet.gif
images/fillet.jpg
images/handle.gif
images/handle.jpg
images/mug_camo.gif
images/mug_camo.jpg
images/mug_green.gif
images/mug_green.jpg
images/prims.gif
images/rim.gif
images/rim.jpg
)
ADD_DOC(articles_EN_IMAGES html/articles/en/images)
ADD_DOC(docbook_articles_EN_IMAGES html/articles/en/images)
ADD_DOCBOOK("HTML;PHP;PDF" articles_EN articles/en articles_EN_IMAGES_cp)
DOCBOOK_TO_HTML(article docbook_articles_EN html/articles/en docbook_articles_EN_IMAGES_cp)
if(BRLCAD_EXTRADOCS_PDF)
DOCBOOK_TO_PDF(article docbook_articles_EN pdf/articles/en docbook_articles_EN_IMAGES_cp)
endif(BRLCAD_EXTRADOCS_PDF)
CMAKEFILES(images/tire_fig12.svg images/tire_fig13.svg)
+3 -3
View File
@@ -84,14 +84,14 @@
NOTE: fileref will normally be something like
"../../articles/en/images/nirt_fig02.png" NOT http: URL
-->
<imagedata align="center" fileref="http://brlcad.org/images/logo/BRL-CAD_gear_logo_w_name_256.png" format="PNG" width="256"/>
<imagedata align="center" fileref="http://brlcad.org/images/logo/BRL-CAD_256x256.png" format="PNG" width="64"/>
</imageobject>
<imageobject role="fo">
<!--
NOTE: fileref will normally be something like
"../../articles/en/images/nirt_fig02.png" NOT http: URL
-->
<imagedata align="center" fileref="http://brlcad.org/images/logo/BRL-CAD_gear_logo_w_name_256.png" format="PNG" width="256"/>
<imagedata align="center" fileref="http://brlcad.org/images/logo/BRL-CAD_256x256.png" format="PNG" width="64"/>
</imageobject>
<caption>
<para>
@@ -103,7 +103,7 @@
<para>
Another image, but rendered inline
<inlinemediaobject><imageobject role="html"><imagedata fileref="http://brlcad.org/images/logo/BRL-CAD_gear_logo_64x64.png" format="PNG" width="64"/></imageobject><imageobject role="fo"><imagedata fileref="http://brlcad.org/images/logo/BRL-CAD_gear_logo_64x64.png" format="PNG" width="64"/></imageobject></inlinemediaobject>
<inlinemediaobject><imageobject role="html"><imagedata fileref="http://brlcad.org/images/logo/BRL-CAD_64x64.png" format="PNG" width="64"/></imageobject><imageobject role="fo"><imagedata fileref="http://brlcad.org/images/logo/BRL-CAD_64x64.png" format="PNG" width="64"/></imageobject></inlinemediaobject>
with the paragraph text.
</para>
File diff suppressed because it is too large Load Diff
-144
View File
@@ -1,144 +0,0 @@
<article xmlns="http://docbook.org/ns/docbook" version="5.0">
<info>
<title>Camouflage shader</title>
</info>
<section xml:id="Introduction">
<title>Introduction</title>
<para>The "camo" shader creates a pseudo-random tri-color camouflage pattern on the object using a fractal noise pattern. This is a procedural shader based upon a fractal noise function known as fractional brownian motion or fBm.
</para>
<para>
The fractal noise function produces a pseudo- random number in the range [-1.0 ... 1.0] from the 3-space coordinates of a point in the bounding volume of the region. This noise value is used to determine the color of the object at the given location.
</para>
<para>
<table frame='all'>
<title>Table 1</title>
<tgroup cols='2' align='left' colsep='1' rowsep='1'>
<thead>
<row>
<entry>Noise Value</entry>
<entry>Object Color</entry>
</row>
</thead>
<tbody>
<row>
<entry>nv &#60; thresh1 </entry> <entry>color 1</entry>
</row>
<row>
<entry>nv &#60; thresh1
and nv &#60; thresh2</entry>
<entry>color 2</entry>
</row>
<row>
<entry>nv > thresh2</entry>
<entry>color 3</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
<para>
The fractal pattern has infinite resolution. As a result, the borders of the color splashes never become pixelated, no mater how close the eyepoint is to the surface.
</para>
<para>
<table frame='all'>
<title>Table 2</title>
<tgroup cols='3' align='left' colsep='1' rowsep='1'>
<colspec colname='c1' />
<colspec colname='c2' />
<colspec colname='c3' />
<colspec colnum='3' colname='c3'/>
<spanspec spanname='hspan' namest='c1' nameend='c3' align='center'/>
<thead>
<row>
<entry>parameter</entry>
<entry>Abbreviation</entry>
<entry>Default Value</entry>
</row>
<row>
<entry spanname='hspan'>Noise Parameters</entry>
</row>
</thead>
<tbody>
<row>
<entry>lacunarity</entry>
<entry>l</entry>
<entry>2.1753974</entry>
</row>
<row>
<entry>H</entry>
<entry>H</entry>
<entry>1.0</entry>
</row>
<row>
<entry>octaves</entry>
<entry>o</entry>
<entry>4.0</entry>
</row>
<row>
<entry>size</entry>
<entry>s</entry>
<entry>1.0</entry>
</row>
<row>
<entry>vscale</entry>
<entry>v</entry>
<entry>1.0/1.0/1.0</entry>
</row>
<row>
<entry>delta</entry>
<entry>d</entry>
<entry>1000/1000/1000</entry>
</row>
<row>
<entry spanname='hspan'><emphasis role='bold'>Shader Specific Parameters</emphasis></entry>
</row>
<row>
<entry>thresh1</entry>
<entry>t1</entry>
<entry>-0.25</entry>
</row>
<row>
<entry>thresh2</entry>
<entry>t2</entry>
<entry>0.25</entry>
</row>
<row>
<entry>color1</entry>
<entry>c1</entry>
<entry>97/74/41</entry>
</row>
<row>
<entry>color2</entry>
<entry>c2</entry>
<entry>26/77/10</entry>
</row>
<row>
<entry>color3</entry>
<entry>c3</entry>
<entry>38/38/38</entry>
</row>
</tbody>
</tgroup>
</table>
</para>
<para><emphasis role='bold'>Lacunarity</emphasis></para>
<para>The grid on which the noise function is built is scaled by this value for each successive octave of noise which will be combined to produce the final result.</para>
<para><emphasis role='bold'>Octaves</emphasis></para>
<para>The number of times the noise grid will be scaled and recombined to produce the final noise function</para>
<para><emphasis role='bold'>Size, Vscale</emphasis></para>
<para>If <emphasis role='bold'>size</emphasis> is set it is used as a scalar which defines the size of the noise grid on the object. So if t2=0.5 and size=5mm then splotches of color3 would tend to be no larger than 5-10mm. If non-uniform scaling is required, Vscale can specify the grid size in X, Y and Z.</para>
<para><emphasis role='bold'>Delta</emphasis></para>
<para>This specifies a translation in noise space for the origin of region space. Since the origin of noise space is reflected 8 ways, it is undesirable to have that portion of noise space overlap with region space.</para>
</section>
<section xml:id="Limitations">
<title>Limitations</title>
<para>Because of the continuous nature of the fractal noise space, it is impossible to get a splash of color1 directly adjacent to a splash of color3. </para>
</section>
</article>
-767
View File
@@ -1,767 +0,0 @@
<article xmlns="http://docbook.org/ns/docbook" version="5.0">
<info>
<title>The Geometry Conversion Library</title>
<author>
<personname>
<firstname>Jon</firstname>
<surname>Engbert</surname>
</personname>
<affiliation>
<orgname>BRL-CAD Open Source</orgname>
</affiliation>
</author>
</info>
<section>
<title>Introduction</title>
<para>
The Geometry Conversion Library (GCV or libgcv) provides a unified API for geometry conversion capabilities under a plugin-based architecture.
</para>
<para>
The GCV public API is declared in C headers located within <literal>include/gcv/</literal>. The single <literal>include/gcv.h</literal> header includes the entire GCV public API.
</para>
</section>
<section>
<title>Architecture</title>
<para>
The Geometry Conversion Library consists of a stream-based API for geometry conversion and associated operations. Input and output are provided by "reader" and "writer" converters (provided by plugins). Intermediate operations are provided by "filters". Readers and writers are types of filters that provide input and output support for model formats, while basic filters apply transformations to models and geometry.
</para>
<para>
Geometry is stored in an in-memory BRL-CAD database (<code>struct db_i</code> in <literal>include/rt/db_instance.h</literal>) during the intermediate steps of conversion. For writer filters, this database is marked read-only and its geometry should not be modified. All names within a BRL-CAD database must be unique.
</para>
<figure>
<title>GCV architecture</title>
<mediaobject>
<imageobject>
<imagedata fileref="../../articles/en/images/gcv_architecture.png"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section>
<title>Building GCV</title>
<para>
GCV can be built in a similar manner as other BRL-CAD libraries. After configuring with CMake, building the <literal>libgcv</literal> target will produce a dynamic library. For Unix-based systems, the procedure should be similar to the following:
<screen>
$ cd brlcad
$ mkdir build
$ cd build
$ cmake ..
$ make libgcv
</screen>
</para>
<para>
Plugins can be built under <literal>gcv_<replaceable>plugin_name</replaceable></literal> targets, or collectively under the <literal>gcv_plugins</literal> target.
</para>
<para>
The command-line utility can be built under the <literal>gcv</literal> target. At this time, the <literal>gcv</literal> program is not installed automatically; the binary will be placed into <literal>build/src/conv/gcv/</literal>.
</para>
</section>
<section>
<title>Example: Using GCV in an application</title>
<para>
The following code illustrates a basic use of GCV from within an application. Note that there may be multiple filters providing import/export capabilities for a given format; the below code simply selects the first matching filter encountered.
</para>
<example>
<title>gcv_app.c</title>
<para>
TODO: embedded code
</para>
</example>
</section>
<section>
<title>GCV Public API</title>
<para>
The public API for interacting with GCV filter plugins is summarized below.
</para>
<table frame='none'>
<title>GCV public filter API</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>struct gcv_context</code></entry>
<entry>Stores the conversion state. Plugins may store messages in the <code>bu_avs_t</code> member <code>messages</code>.</entry>
</row>
<row>
<entry><code>gcv_context_init()</code></entry>
<entry>Initialize a <code>struct gcv_context</code>. Creates an in-memory <code>struct db_i</code> for conversion data.</entry>
</row>
<row>
<entry><code>gcv_context_destroy()</code></entry>
<entry>Frees memory associated with a <code>struct gcv_context</code>.</entry>
</row>
<row>
<entry><code>struct gcv_filter</code></entry>
<entry>Stores characteristics of a filter.</entry>
</row>
<row>
<entry><code>struct gcv_opts</code></entry>
<entry>Store generic options applying to all filters.</entry>
</row>
<row>
<entry><code>gcv_opts_default()</code></entry>
<entry>Initialize a <code>struct gcv_opts</code> with default values.</entry>
</row>
<row>
<entry><code>gcv_list_filters()</code></entry>
<entry>Returns a pointer to a <code>const struct bu_ptbl</code> containing all registered filters as <code>const struct gcv_filter</code> pointers.</entry>
</row>
<row>
<entry><code>gcv_execute()</code></entry>
<entry>Perform a filter operation on a <code>struct gcv_context</code>. Returns <code>1</code> on success and <code>0</code> on failure. If <code>gcv_options</code> is <code>NULL</code>, the defaults will be used as set by <code>gcv_opts_default()</code>. The parameters <code>argc</code> and <code>argv</code> are used for option parsing as specified by the struct gcv_filter.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>The Internal Plugin API</title>
<para>
The GCV plugin API is declared in <code>include/gcv/api.h</code>. Plugins provide an externally-visible <code>const struct gcv_plugin</code> defining their filters, which are described by <code>struct gcv_filter</code>.
</para>
<table frame='none'>
<title>The gcv_filter struct</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>name</code></entry>
<entry>Specifies a unique name for the filter, allowing it to be identified by application code.</entry>
</row>
<row>
<entry><code>filter_type</code></entry>
<entry>Specifies the type of filter.</entry>
</row>
<row>
<entry><code>create_opts_fn</code></entry>
<entry>Optional pointer to a function that allocates and initializes <code>struct bu_opt_desc</code> data and an opaque pointer for storing the option data. If non-<code>NULL</code>, <code>free_opts_fn</code> must also be specified. This member is private for use by libgcv and the associated plugin.
</entry>
</row>
<row>
<entry><code>free_opts_fn</code></entry>
<entry>Optional pointer to a function that frees any opaque pointer allocated by <code>create_opts_fn</code>. This member is private for use by libgcv and the associated plugin.</entry>
</row>
<row>
<entry><code>filter_fn</code></entry>
<entry>Pointer to a function which performs the filter operation. The <code>db_i</code> passed to a writer function within a <code>gcv_context</code> is marked read-only (the pointer is to a non-<code>const</code> struct due to in-memory data that may be modified). Filters of type <code>GCV_FILTER_FILTER</code> receive a <code>NULL</code> value for <code>target</code>. Must return <code>1</code> on success and <code>0</code> on failure. This member is private for use by libgcv and the associated plugin.
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
As shown in the above table, filters may initialize data structures for processing command-line style option strings via <code>bu_opt</code>. Please refer to <code>include/bu/opt.h</code> for full documentation on the <code>bu_opt</code> API.
</para>
<section>
<title>Utility Functions</title>
<para>
In addition to availability of the rest of the BRL-CAD API, the Geometry Conversion Library provides a number of utility functions that may be useful during plugin development.
</para>
<table frame='none'>
<title>GCV utility functions</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>gcv_bot_is_solid()</code>, <code>gcv_bot_is_closed()</code>, <code>gcv_bot_is_orientable()</code></entry>
<entry>Performs topological tests for determining whether a given triangular mesh is a manifold, orientable, closed fan satisfying requisite conditions for object solidity. <code>gcv_bot_is_solid()</code> is equivalent to <code>gcv_bot_is_closed &amp;&amp; gcv_bot_is_orientable()</code></entry>
</row>
<row>
<entry><code>gcv_facetize()</code></entry>
<entry>Produces a triangular mesh tessellation of the object at the given database path using the specified tolerances. Note that if the object at the given path is a combination, a single mesh will be produced from all objects within its tree, and so calling gcv_facetize() on a tree unnecessarily high in the hierarchy and containing many objects is more likely to fail during Boolean evaluation.
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
There are also many relevant functions provided by the BRL-CAD API, including a new mesh decimation function.
</para>
<table frame='none'>
<title>BRL-CAD mesh decimation API</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>rt_bot_decimate_gct()</code></entry>
<entry>Fast implementation of an iterative mesh decimation algorithm.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
<section>
<title>Developing a Minimal Plugin</title>
<section>
<title>Basic Code</title>
<para>
The following steps will implement a minimal plugin providing a reader filter.
</para>
<orderedlist>
<listitem>
<para>
Add the following line to <literal>misc/mime_cad.types</literal>. This file is used to generate <literal>include/bu/mime.h</literal>:
</para>
<programlisting>
model/foo bar
</programlisting>
<para>
This will associate the file extension <literal>.bar</literal> with a new <code>BU_MIME_MODEL_FOO</code> value of <code>bu_mime_model_t</code>.
</para>
</listitem>
<listitem>
<para>
Create the following file at <literal>src/libgcv/plugins/foo/CMakeLists.txt</literal>:
</para>
<example>
<title>CMakeLists.txt</title>
<programlisting>
LIBGCV_ADD_PLUGIN(foo "foo_read.c" "librt;libbu")
</programlisting>
</example>
</listitem>
<listitem>
<para>
Create the following file at <literal>src/libgcv/plugins/foo/foo_read.c</literal>:
</para>
<example>
<title>foo_read.c</title>
<para>
TODO: embedded code
</para>
</example>
</listitem>
</orderedlist>
</section>
<section>
<title>Traversing the Database</title>
<para>
BRL-CAD provides the <code>db_walk_tree()</code> function for traversing the database in hierarchical order. You can specify your own visitor callbacks as documented in <literal>include/rt/tree.h</literal>, or use the region-end functions provided by GCV (<literal>include/gcv/util.h</literal>) to tessellate geometry at the region level.
</para>
<table frame='none'>
<title>GCV region-end tessellation callbacks</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>gcv_region_end()</code></entry>
<entry>Apply Boolean evaluation to region-level tessellated meshes using the default NMG Boolean evaluator, replacing each region-level node and its subtree of tessellated leaf meshes with a single BoT structure that is then passed to the specified callback. The <code>client_data</code> pointer should point to a <code>struct gcv_region_end_data</code>. The individual leaf nodes must already be tessellated into BoTs. This can be done by specifying a <code>leaf_func</code> such as <code>nmg_booltree_leaf_tess()</code>. In the case of failure, an error message is emitted via <code>bu_log()</code> and the callback is not invoked. Any use of <code>bu_bomb()</code> produced by the callback is trapped and an error message is displayed while continuing the tree walk.</entry>
</row>
<row>
<entry><code>gcv_bottess_region_end()</code></entry>
<entry>Boolean evaluator roughly based on UnBBoolean's j3dbool (and associated papers). Does not take a callback.</entry>
</row>
<row>
<entry><code>gcv_region_end_mc()</code></entry>
<entry>Experimental variant of <code>gcv_region_end()</code> based on the marching-cubes algorithm. Tessellates leaves internally and does not require a <code>leaf_func</code>.
</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
The following example implements a filter that tessellates all geometry into BoT mesh objects and counts the total number of faces.
</para>
<example>
<title>tessellation_statistics.c</title>
<para>
TODO: embedded code
</para>
</example>
</section>
<section>
<title>Converting Unsupported Entities</title>
<para>
Although BRL-CAD supports a wide array of common geometric primitives, you may encounter objects that can't be directly imported or exported into an analogous entity. In these cases, conversion filters usually tessellate the incompatible geometry (typically during export) or convert it into an approximation or a composite of several other primitives (often during import).
</para>
<figure>
<title>Tessellation of incompatible entities</title>
<mediaobject>
<imageobject>
<imagedata fileref="../../articles/en/images/gcv_unsupported_tessellation.png"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section>
<title>Comparing Geometry</title>
<para>
When developing a filter, it is often useful to be able to compare different models during testing. This capability is provided by the <literal>gdiff</literal> tool. There are two versions of <literal>gdiff</literal>: the standalone command-line version and the <literal>gdiff</literal> provided within the MGED interface.
</para>
<para>
The command-line <literal>gdiff</literal> quickly produces a textual summary for a two- or three- way diff of several BRL-CAD databases. Documentation for this utility is available under <code>brlman gdiff</code>.
</para>
<para>
The <literal>gdiff</literal> command available within the MGED interface provides a different capability. It uses BRL-CAD's ray tracer to produce a visual display of the differences between two objects within the same database. To compare geometry from separate databases, you can first merge the databases using the <literal>dbconcat</literal> command from within MGED. See <code>brlman dbconcat</code> for full documentation.
</para>
<table frame='none'>
<title>Usage of MGED's gdiff utility</title>
<tgroup cols='2' align='left'>
<thead>
<row>
<entry>Usage:</entry>
<entry><code>gdiff [OPTION]... obj1 obj2</code></entry>
</row>
</thead>
<tbody>
<row>
<entry><literal>--tol=#</literal>, <literal>-t#</literal></entry>
<entry>Tolerance in millimeters.</entry>
</row>
<row>
<entry><literal>--ray-diff</literal>, <literal>-R</literal></entry>
<entry>Test for differences with raytracing.</entry>
</row>
<row>
<entry><literal>--view-left</literal>, <literal>-l</literal></entry>
<entry>Visualize volumes added only by left object.</entry>
</row>
<row>
<entry><literal>--view-both</literal>, <literal>-b</literal></entry>
<entry>Visualize volumes common to both objects.</entry>
</row>
<row>
<entry><literal>--view-right</literal>, <literal>-r</literal></entry>
<entry>Visualize volumes added only by right object.</entry>
</row>
<row>
<entry><literal>--grazing</literal>, <literal>-G</literal></entry>
<entry>Report differences in grazing hits (raytracing mode).</entry>
</row>
</tbody>
</tgroup>
</table>
<figure>
<title>Using MGED's gdiff utility</title>
<mediaobject>
<imageobject>
<imagedata fileref="../../articles/en/images/gcv_using_gdiff.png"/>
</imageobject>
</mediaobject>
</figure>
</section>
<section>
<title>Creating Unit Tests</title>
<para>
BRL-CAD provides a library of standard models that may be used for unit tests, located under <literal>$BRLCAD_ROOT/share/db/</literal> (note that these files are generated during the build process). Unit tests can be integrated into the build system using the <code>add_test</code> CMake command.
</para>
</section>
</section>
<section>
<title>Example: Extending an Application</title>
<para>
The following example will leverage the filter in the above plugin example, <literal>tessellation_statistics.c</literal>, to implement a function that counts the number of faces in a model after tessellation.
</para>
<example>
<title>gcv_embedded.c</title>
<para>
TODO: embedded code
</para>
</example>
</section>
<section>
<title>The GCV Frontend</title>
<para>
GCV includes a command-line front-end utility, <literal>gcv</literal>, implemented in <literal>src/conv/gcv/gcv.c</literal>. Full documentation is available under <code>brlman gcv</code> and <code>gcv --help</code>.
</para>
<example>
<title>Basic usage of the gcv utility</title>
<screen>
$ <userinput>gcv --input=a.stl --output=b.fg4</userinput>
Input file format: BU_MIME_MODEL_STL
Output file format: BU_MIME_MODEL_VND_FASTGEN
Input file path: a.stl
Output file path: b.fg4
Converting Part: all_cpu_cpw6_cw_cpubox_cpubox.a
Using solid name: s.all_cpu_cpw6_cw_cpubox_cpubox.a
Making region (all_cpu_cpw6_cw_cpubox_cpubox.a)
...
</screen>
</example>
<example>
<title>Generic options</title>
<screen>
$ <userinput>gcv --input=a.fg4 --output=b.vrml --input-and-output-opts --verbosity=1 --output-only-opts --objects=comp_0001.r</userinput>
</screen>
</example>
<example>
<title>Filter-specific options</title>
<screen>
$ <userinput>gcv --input=a.fg4 --output=b.obj --input-only-opts --colors=a.fg4.colors --output-only-opts --vertex-normals</userinput>
</screen>
</example>
<example>
<title>Specifying conversion formats</title>
<screen>
$ <userinput>gcv --input=infile.txt --output=outfile.obj --input-format=stl</userinput>
</screen>
</example>
</section>
<section>
<title>Conversion Filters</title>
<para>
GCV currently contains support for import and export into five model formats, detailed below.
</para>
<table frame='none'>
<title>Conversion formats supported by GCV</title>
<tgroup cols='2' align='left'>
<thead>
<row>
<entry>Format</entry>
<entry>File Extension</entry>
</row>
</thead>
<tbody>
<row>
<entry>BRL-CAD</entry>
<entry><literal>.g</literal></entry>
</row>
<row>
<entry>FASTGEN4</entry>
<entry><literal>.fg4</literal></entry>
</row>
<row>
<entry>WaveFront Object</entry>
<entry><literal>.obj</literal></entry>
</row>
<row>
<entry>StereoLithography</entry>
<entry><literal>.stl</literal></entry>
</row>
<row>
<entry>Virtual Reality Modeling Language</entry>
<entry><literal>.vrml</literal></entry>
</row>
</tbody>
</tgroup>
</table>
<section>
<title>Common Conversion Options</title>
<para>
The <code>gcv_opts</code> struct stores generic options applying to many filters, detailed below. Not all options may be applicable to or respected by every filter.
</para>
<table frame='none'>
<title>Conversion formats supported by GCV</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><code>debug_mode</code></entry>
<entry>Print debugging info if set to <code>1</code>. Default is <code>0</code>.</entry>
</row>
<row>
<entry><code>verbosity_level</code></entry>
<entry>Verbosity level. The default, level <code>0</code>, is "quiet" (only error messages are produced).</entry>
</row>
<row>
<entry><code>scale_factor</code></entry>
<entry>Specify the scale factor to be applied during import or export, as units per mm. Default is <code>1.0</code>.</entry>
</row>
<row>
<entry><code>calculational_tolerance</code></entry>
<entry>Calculational tolerance. Defaults to the RT defaults. If you use a non-default value, you should set the ray tracer tolerance to match it when using the resulting model.</entry>
</row>
<row>
<entry><code>tessellation_tolerance</code></entry>
<entry>
Tessellation tolerance. The default value is:
<para>
<literal>abs = 0.0</literal>
</para>
<para>
<literal>rel = 1.0e-2</literal>
</para>
<para>
<literal>norm = 0.0</literal>
</para>
</entry>
</row>
<row>
<entry><code>tessellation_algorithm</code></entry>
<entry>Specify use of either the default, marching-cubes, or bottess-based tessellation algorithm.</entry>
</row>
<row>
<entry><code>max_cpus</code></entry>
<entry>Maximum number of processors to utilize where possible. Default is <code>0</code>, specifying the maximum available during execution.</entry>
</row>
<row>
<entry><code>num_objects</code></entry>
<entry>Number of objects to convert. If <code>0</code> (the default), all top-level objects will be converted.</entry>
</row>
<row>
<entry><code>object_names</code></entry>
<entry>Names of objects to convert (must have <code>num_objects</code> elements). Default is <code>NULL</code>.</entry>
</row>
<row>
<entry><code>default_name</code></entry>
<entry>Name assigned to objects without names. Defaults to "<code>unnamed</code>".</entry>
</row>
<row>
<entry><code>bu_debug_flag</code></entry>
<entry>Debug flag for libbu (see <code>include/bu/debug.h</code>), applied via bitwise-OR with the original value. The original debug flag will be restored after conversion. Defaults to <code>0</code>.</entry>
</row>
<row>
<entry><code>rt_debug_flag</code></entry>
<entry>Debug flag for librt (see <code>include/rt/debug.h</code>), applied via bitwise-OR with the original value. The original debug flag will be restored after conversion. Defaults to <code>0</code>.</entry>
</row>
<row>
<entry><code>nmg_debug_flag</code></entry>
<entry>Debug flag for libnmg (see <code>include/nmg.h</code>), applied via bitwise-OR with the original value. The original debug flag will be restored after conversion. Defaults to <code>0</code>.</entry>
</row>
</tbody>
</tgroup>
</table>
<example>
<title>Using struct gcv_opts</title>
<programlisting>
static int
apply_filter_with_options(struct gcv_context *context, const struct gcv_filter *filter, const char *target)
{
struct gcv_opts options;
const char *argv[] = { "--colors=colors.dat", "--continue" };
const size_t argc = sizeof(argv) / sizeof(argv[0]);
gcv_opts_default(&amp;options);
options->debug_mode = 1;
return gcv_execute(context, filter, &amp;options, argc, argv, target);
}
</programlisting>
</example>
</section>
<section>
<title>FASTGEN4 Reader</title>
<table frame='none'>
<title>FASTGEN4 reader options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--colors=<replaceable>path</replaceable></literal></entry>
<entry>Path to a file specifying component colors.</entry>
</row>
<row>
<entry><literal>--muves=<replaceable>path</replaceable></literal></entry>
<entry>Create a MUVES input file containing any CHGCOMP and CBACKING components.</entry>
</row>
<row>
<entry><literal>--plot=<replaceable>path</replaceable></literal></entry>
<entry>Create a libplot3 plot file of all CTRI and CQUAD elements processed.</entry>
</row>
<row>
<entry><literal>--sections=<replaceable>list</replaceable></literal></entry>
<entry>Process only a list ("<literal>3001, 4082, 5347</literal>") or a range ("<literal>2315 - 3527</literal>") of section IDs.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>FASTGEN4 Writer</title>
<para>
At this time, the FASTGEN4 writer plugin does not make use of any filter-specific options.
</para>
</section>
<section>
<title>OBJ Reader</title>
<table frame='none'>
<title>OBJ reader options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--continue</literal></entry>
<entry>Continue processing on nmg-bomb. Conversion will fall back to native BoT mode if a fatal error occurs when using the nmg or BoT-via-nmg modes.</entry>
</row>
<row>
<entry><literal>--fuse-vertices</literal></entry>
<entry>Fuse vertices that are near enough to be considered identical. Can make the solidity detection more reliable, but may significantly increase processing time during the conversion.</entry>
</row>
<row>
<entry><literal>--grouping=<replaceable>mode</replaceable></literal></entry>
<entry>
Select which OBJ face grouping is used to create BRL-CAD primitives.
<para>
<literal>group</literal> = group (default)
</para>
<para>
<literal>material</literal> = material
</para>
<para>
<literal>none</literal> = none
</para>
<para>
<literal>object</literal> = object
</para>
<para>
<literal>texture</literal> = texture
</para>
</entry>
</row>
<row>
<entry><literal>--conversion-mode=<replaceable>mode</replaceable></literal></entry>
<entry>
Select the conversion mode.
<para>
<literal>bot</literal> = native BoT (default)
</para>
<para>
<literal>nmg</literal> = NMG
</para>
<para>
<literal>nmgbot</literal> = BoT via NMG
</para>
</entry>
</row>
<row>
<entry><literal>--bot-plate-thickness=<replaceable>thickness</replaceable></literal></entry>
<entry>Thickness (mm) used when a BoT is not a closed volume and it's converted as a plate or plate-nocos BoT.</entry>
</row>
<row>
<entry><literal>--bot-ignore-normals</literal></entry>
<entry>Ignore the normals defined in the input file when using native BoT conversion mode.</entry>
</row>
<row>
<entry><literal>--bot-open-type=<replaceable>type</replaceable></literal></entry>
<entry>
Select the type used for BoTs that aren't closed volumes.
<para>
<literal>surface</literal> = surface (default)
</para>
<para>
<literal>plate</literal> = plate
</para>
<para>
<literal>nocos</literal> = plate-nocos
</para>
</entry>
</row>
<row>
<entry><literal>--bot-plot</literal></entry>
<entry>Creates a plot/overlay (<literal>.plot3</literal>) file of open edges for BoTs that aren't closed volumes. <literal><replaceable>bot_name</replaceable>.plot3</literal> will be created in the current directory and will overwrite any existing file with the same name.</entry>
</row>
<row>
<entry><literal>--bot-orientation=<replaceable>mode</replaceable></literal></entry>
<entry>
Select the BoT orientation mode.
<para>
<literal>unoriented</literal> = unoriented (default)
</para>
<para>
<literal>ccw</literal> = counterclockwise
</para>
<para>
<literal>cw</literal> = clockwise
</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>OBJ Writer</title>
<table frame='none'>
<title>OBJ writer options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--vertex-normals</literal></entry>
<entry>Output vertex normals.</entry>
</row>
<row>
<entry><literal>--usemtl</literal></entry>
<entry>Place <literal>usemtl</literal> statements in the output file. These statements are fictional (they do not refer to any material database). The materials named provide information about the material codes assigned to the objects in the BRL-CAD database. The material names will be of the form "<literal><replaceable>aircode</replaceable>_<replaceable>los</replaceable>_<replaceable>material</replaceable></literal>", where <replaceable>aircode</replaceable> is the code number for the air represented by that region, if it does represent air; otherwise, this will be <literal>0</literal>. The <replaceable>los</replaceable> is the Line Of Sight thickness (<literal>0</literal> to <literal>100</literal>) assigned to the region, and <replaceable>material</replaceable> is the material code number assigned.
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>STL Reader</title>
<table frame='none'>
<title>STL reader options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--binary</literal></entry>
<entry>Specify that the input file is in binary STL format (the default assumes ASCII).</entry>
</row>
<row>
<entry><literal>--starting-ident=<replaceable>number</replaceable></literal></entry>
<entry>Specify the starting ident for the regions created. The default is <literal>1000</literal>. This number will be incremented for each region, unless <literal>--constant-ident</literal> is specified.</entry>
</row>
<row>
<entry><literal>--constant-ident</literal></entry>
<entry>Specify that the starting ident should remain constant.</entry>
</row>
<row>
<entry><literal>--material=<replaceable>code</replaceable></literal></entry>
<entry>Specify the material code that will be assigned to all created regions (the default is <literal>1</literal>).</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>STL Writer</title>
<table frame='none'>
<title>STL writer options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--binary</literal></entry>
<entry>Write output as a binary STL file. The default is ASCII. In the case of ASCII output, the region name is specified on the "solid" line of the STL file. In the case of binary output, all the regions are output as a single STL part.</entry>
</row>
<row>
<entry><literal>--output-dir</literal></entry>
<entry>Specify that the output path should be a directory. Each region converted is written to a separate file. File names are constructed from the full path names of each region (the path from the specified object to the region). Any "<literal>/</literal>" characters in the path name are replaced by "<literal>@</literal>" characters and "<literal>.</literal>" and white space are replaced by "<literal>_</literal>" characters.
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section>
<title>VRML Reader</title>
<para>
At this time, the VRML reader plugin does not make use of any filter-specific options.
</para>
</section>
<section>
<title>VRML Writer</title>
<table frame='none'>
<title>VRML writer options</title>
<tgroup cols='2' align='left'>
<tbody>
<row>
<entry><literal>--bot-dump</literal></entry>
<entry>BoT dump. Mutually exclusive with <literal>--evaluate-all</literal>.</entry>
</row>
<row>
<entry><literal>--evaluate-all</literal></entry>
<entry>Evaluate all, CSG and BoTs. Mutually exclusive with <literal>--bot-dump</literal>.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
</article>
File diff suppressed because it is too large Load Diff
Binary file not shown.

Before

Width:  |  Height:  |  Size: 145 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 2.6 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.0 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

Some files were not shown because too many files have changed in this diff Show More