Compare commits

..
2 Commits
3786 changed files with 97802 additions and 550819 deletions
+2 -2
View File
@@ -26,13 +26,13 @@ _$*
*.ln
core
# CVS default ignores end
.cvsignore
.deps
Makefile
Makefile.in
aclocal.m4
autom4te.cache
brlcad.spec
config.*
configure
libtool
ltmain.sh
so_locations
+105 -179
View File
@@ -1,4 +1,3 @@
-*- coding: utf-8 -*-
BRL-CAD Contributors
====================
@@ -42,38 +41,28 @@ then in the will, then in reality."
- Mike Muuss
PROJECT ADMINISTRATORS
----------------------
Open Source Point of Contact
Morrison, Christopher Sean <morrison@brlcad.org>
U.S. Army Research Laboratory Point of Contact
Butler, Lee <butler@arl.army.mil>
DEVELOPERS
----------
Muuss, Michael John
U.S. Army Research Laboratory
Weaver, Earl P.
Weaver, Earl P
U.S. Army Ballistic Research Laboratory
Moss, Gary S.
Moss, Gary S
U.S. Army Research Laboratory
Dykstra, Phillip
U.S. Army Research Laboratory
Applin, Keith A.
Applin, Keith A
U.S. Army Research Laboratory
Kennedy, Charles Michael <kermit@brlcad.org> **
U.S. Army Research Laboratory
Gwyn, Douglas A.
Gwyn, Douglas A
U.S. Army Research Laboratory
Stay, Paul Randall
@@ -82,31 +71,27 @@ U.S. Army Research Laboratory
Hanes, Jeff
U.S. Army Research Laboratory
Butler, Lee A. <butler@arl.army.mil> **
Butler, Lee A <butler@arl.army.mil> **
U.S. Army Research Laboratory
Johnson, Christopher T. <cjohnson@cyberpaladin.com>
Cray Research, Inc.
Johnson, Christopher T <cjohnson@cyberpaladin.com> **
Geometric Solutions, Inc.
Paladin Software
JRMTech, Inc.
Paladin Software, Inc.
Ross, Adam
Geometric Solutions, Inc.
Markowski, Michael J
U.S. Army Research Laboratory (??? brl only)
Markowski, Michael J. <michael.markowski@arl.army.mil>
U.S. Army Ballistic Research Laboratory
Anderson, John R. <jra@arl.army.mil> **
Anderson, John R <jra@arl.army.mil> **
U.S. Army Research Laboratory
Tanenbaum, Paul J.
Tanenbaum, Paul J
U.S. Army Research Laboratory
Durfee, Glenn
ARL Student Hire / Carnegie Mellon University
ARL Student Hire / Stanford University (??? carnegie-mellon)
Parker, Robert G. **
Parker, Robert G **
U.S. Army Research Laboratory
Survice Engineering, Inc.
@@ -114,7 +99,7 @@ Morrison, Christopher Sean <morrison@brlcad.org> **
ARL Student Hire / Johns Hopkins University
Quantum Research International, Inc.
Bowers, Ronald A.
Bowers, Ronald A
U.S. Army Research Laboratory
Hartley, Robert <hartley@vt.edu>
@@ -125,70 +110,50 @@ U.S. Army Research Laboratory
Shumaker, Justin **
Quantum Research International, Inc.
U.S. Army Research Laboratory
Greenwald, Erik <erikg@arl.army.mil> **
Greenwald, Erik **
U.S. Army Research Laboratory
MATHEMATICAL, ALGORITHMIC, AND GEOMETRIC SUPPORT
------------------------------------------------
Davisson, Edwin **
Davisson, Edwin
U.S. Army Research Laboratory
Rodgers, David
U.S. Naval Academy
Reed, Harry
Reed, Jr., Harry
Geometric Solutions, Inc.
U.S. Army Ballistic Research Laboratory
Applin, Keith A.
Applin, Keith A
U.S. Army Research Laboratory
Kregel, Dwayne **
Kregel, Dwayne
Survice Engineering, Inc.
CODE CONTRIBUTIONS
------------------
Hartwig, Jr., George W.
Pistritto, Joseph C
U.S. Army Ballistic Research Laboratory
Pistritto, Joseph C.
U.S. Army Ballistic Research Laboratory
Natalie, Ronald B.
U.S. Army Ballistic Research Laboratory
Toth, George E.
Natalie, Ronald B
U.S. Army Ballistic Research Laboratory
Mermagen, Jr., William
U.S. Army Research Laboratory
Barker, Natalie L.
Barker, Natalie L
U.S. Army Research Laboratory
Becker, David
Cray Research
Hunt, Jim <jhunt@ara.com>
Applied Research Associates, Inc.
U.S. Army Research Laboratory
Dender, Daniel C
U.S. Army Research Laboratory
Survice Engineering, Inc.
Coates, Sue
U.S. Army Research Laboratory (??? only brl)
Ross, Brant A
General Motors, Inc.
Lindemann, William
Sun Microsystems, Inc.
@@ -201,28 +166,22 @@ Sun Microsystems, Inc.
Fiori, James D.
Sun Microsystems, Inc.
DiGiacinto, Tom
U.S. Army Ballistic Research Laboratory
Bowden, Mark Huston
University of Alabama
Suckling, Bob
U.S. Army Ballistic Research Laboratory
Reschly, Jr., Robert J.
Reschly, Jr., Robert J
U.S. Army Ballistic Research Laboratory
Gigante, Mike
Royal Melbourne Institute of Technology
Melbourne Institute of Technology
Muuss, Susanne L.
Muuss, Susanne L
U.S. Army Research Laboratory
Dray, Adam
Geometric Solutions, Inc.
Nuzman, Carl J.
Nuzman, Carl J
ARL Student Hire / Princeton University
Laut, Bill
@@ -248,97 +207,18 @@ Survice Engineering, Inc.
Anderson, David
SGI
Ro§berg, Daniel
Industrieanlagen-Betriebsgesellschaft mbH (IABG)
SPECIAL THANKS
--------------
Henrikson, Bruce
U.S. Army Ballistic Research Laboratory
Wolff, Stephen
U.S. Army Ballistic Research Laboratory
Stanley, Charles
U.S. Army Ballistic Research Laboratory
Deitz, Paul
U.S. Army Ballistic Research Laboratory
Miles, Robert S.
U.S. Army Ballistic Research Laboratory
Martin, Glenn E.
Northrup Research and Technology Center
Willson, Stephen Hunter
Northrup Research and Technology Center
Merrit, Don
U.S. Army Research Laboratory
zum Brunnen, Rick
U.S. Army Research Laboratory
Smith, Jill
U.S. Army Research Laboratory
Monk, Mary
U.S. Army Research Laboratory
Spencer, Thomas W.
University of Utah
McKie, Jim
Davies, Steve
Turkowski, Ken
Woods, James A.
Orost, Joseph
Lorenzo, Max
CECOM Night Vision & Electronic Sensors Directorate
Dome, John
CECOM Night Vision & Electronic Sensors Directorate
Florek, David
CECOM Night Vision & Electronic Sensors Directorate
Stoudenmire, Eugene A.
CECOM Night Vision & Electronic Sensors Directorate
Kekesi, Alex
CECOM Night Vision & Electronic Sensors Directorate
Pronk, Sander
TNO Prins Maurits Laboratory
Moulton, Jr., Russ
EOSoft, Inc. (CECOM)
Reed, Jr., Harry
U.S. Army Ballistic Research Laboratory
Satterfield, Steve
U.S. Naval Academy
Johnson, Joe
U.S. Naval Academy
Woo, Alex
University of Illinois
Musgrave, F. Kenton
Skinner, Robert
Sebok, William L.
Monk, Mary
U.S. Army Reserach Laboratory
Haywood, Heather
U.S. Army Research Laboratory
@@ -351,21 +231,6 @@ Survice Engineering, Inc.
Bokkers, Wim
TNO Prins Maurits Laboratory
Yapp, Cliff
Giffuni, Pedro
Thomas, Balbir
Remenak, Daniel T.
California Institute of Technology
Caruso, Mike
Qryon LLC
Arunaogun, Razak
Qryon LLC
CORPORATE AND ORGANIZATION SUPPORT
----------------------------------
@@ -406,36 +271,97 @@ Industrieanlagen-Betriebsgesellschaft mbH (IABG)
TNO Prins Maurits Laboratory
Free Software Foundation
Open Source Technology Group
SourceForge.net, freshmeat.net
TO BE FILED
-----------
Qryon LLC
Becker, David
Davies, Steve
NEWS ARTICLES
-------------
Dender, Dan
U.S. Army Research Laboratory (chuck)
Survice Engineering, Inc.
Muuss, Mike
"The BRL-CAD Package." Ray Tracing News. Vol 2, No 2. 1989/02/20
DiGiacinto, Tom
U.S. Army Ballistic Research Laboratory
"Designing with BRL-CAD." ITWorld.com, Linux Desktop Applications. 2000/12/14
Dome, John
CECOM Night Vision & Electronic Sensors Directorate
Wasmund, Thomas L.
"New Model to Evaluate Weapon Effects and Platform Vulnerability: AJEM." WSTIAC NEWSLETTER. Vol 2, No 4. 2001/09
Florek, David
CECOM Night Vision & Electronic Sensors Directorate
Jackson, Joab
"Open for business." Government Computer News. Vol 24, No 13. 2005/06/06
Hartwig, George W
U.S. Army Ballistic Research Laboratory
Henrikson, Bruce
U.S. Army Ballistic Research Laboratory
---
Johnson, Joe
U.S. Naval Academy
Kekesi, Alex
CECOM Night Vision & Electronic Sensors Directorate
Martin, Glenn E
Northrup Research and Technology Center
McKie, Jim
Merrit, Don
U.S. Army Research Laboratory
Miles, Robert S
U.S. Army Ballistic Research Laboratory (???NRTC)
Moulton, Jr., Russ
EOSoft, Inc.
Musgrave, F Kenton
Reed, Harry
U.S. Army Ballistic Research Laboratory
Ross, Brant A
General Motors, Inc.
Satterfield, Steve
U.S. Naval Academy
Sebok, William L
Skinner, Robert
Stoudenmire, Eugene A
CECOM Night Vision & Electronic Sensors Directorate
Toth, George E
Turkowski, Ken
Willson, Stephen Hunter
Northrup Research and Technology Center
Wolff, Stephen
U.S. Army Ballistic Research Laboratory
Woo, Alex
University of Illinois
zum Brunnen, Rick
U.S. Army Research Laboratory
Stanley, Charles
U.S. Army Ballistic Research Laboratory (??? maybe maybe didn't contribute)
---
* The U.S. Army Research Laboratory (ARL) was formerly named the
U.S. Army Ballistic Research Laboratory (BRL). Persons who
contributed entirely before the name change reflect the original name,
whereas persons who continued or began contributions after the name
change reflect the new name.
whereas persons who continued contributions or began contributions
after the name change reflect the new name.
** The contributor is an active developer, meaning that they have been
actively involved with the BRL-CAD development within the past 12 months.
+12 -115
View File
@@ -1,139 +1,36 @@
BRL-CAD Bugs
============
Bugs should be reported to the bug tracker on the project website at
http://sourceforge.net/tracker/?atid=640802&group_id=105292
The bugs and issues listed in here may or may not be the same as or
related to the bugs reported to the bug tracker. In general, users
should not look to this file for information regarding the status of
bugs. Informal bug-related information that is intended for
developers will generally be found here. This may include short term
issues that are in active development as well as long term and
developers will generally be found herein. This may include short
term issues that are in active development as well as long term and
on-going issues.
Recent Bugs
-----------
* wavelet isn't working correctly on a simple image decomposition &
reconstruction.
* query_ray can't find nirt if not installed
* fbed is looking for /usr/lib/vfont/nonie.r.12
* mged doesn't check if html_dir does not exist when searching for
docs/browser.
* permute then translate doesn't refresh the graphics window
permute 4378
translate menus
p 0 0 0
p 0 0 0
* constrained axis translation bindings on OS X don't work
object/matrix edit
shift-alt mouse (left/mid/right for x/y/z respectively) should work
* mged documentation doesn't open on OS X
* the findfont directive in gv postscript is reporting font not found
* concave arbs give correct wireframe but do not raytrace correctly.
* rtwizard/rtedge creates incorrect "fuzzy" edge overlay when creating
a "Ghost Image with Insert and Lines" that includes a light source
and object close to surface (e.g. moss.g; select plane, light, and
cone for ghost; select cone for insert and lines.)
* rtwizard doesn't work with perspective
* mged's solid illuminate doesn't work when Lighting is turned on
* raytrace of -s64 and remote -F/dev/Xl crashes inside an empty memcpy
* g2asc exports attr lines but will not grok them on asc2g
* mged's matrix selection does not modify the correct matrix if there
are multiply referenced non-unique paths (e.g. referencing the same
object N times in a combination).
* facetize -t doesn't work (tnurb support)
* on os x, the -fast option results in an odd optimization/aliasing
bug where rtip contents are lost in rt after returning from
rt_gettrees().
* report of rtwizard hanging at 40% on Debian (from binary distro)
* make extrude crashes
* tra in console mode outputs a warning about mged_players
* mged primitive editor doesn't accept/apply values to disk for
certain primitives (e.g. sph)
* photon map cache file doesn't work (seems to crash rt on use)
* enabling perspective mode horks shaded mode, also Z clipping
shouldn't be required to get the shading.
* an underlay framebuffer does not underlay with shaded mode
* bu_malloc() function and company take an unsigned int argument and
will overflow without notification (since it is unsigned) resulting
in less memory allocated than one requested.
* rtweight chokes on a .density file that has less than 3 values per
line (infinite loop). also gives infinite areas when presented with
an empty .density file.
* libfb and libdm have hardcoded XMAXSCREEN and YMAXSCREEN values that
are easily being surpassed on certain systems..
* setting src/librt/db5_io.c's AVS_ADD off in db5_import_attributes
causes bad things to happen and it really shouldn't.
* vrml exporter (and probably others) doesn't export primitives
directly as one might expect like the ray-tracers, only regions.
* if you turn off compilation of tcl/itcl, btclsh/mged fail to find
their scripts.
* sketches extruded with non-square AB vectors results in inner sketch
components not getting scaled properly.
* rtcheck is ignoring fastgen tagged geometry since no multioverlap
handler is set.
* bot-bldxf fails in db_walk_tree(), interface may have changed
* bwmod gives a divide by zero error whenever you use the "-d" option
* mged help seems to be busted
* you can't run a make benchmark unless you're compiling in place
* reflected light energy seems to be accumulating too much
* benchmark may report environment garbage into the summary file if
the benchmark run is aborted.
* X11 framebuffer often fails to display on certain middle bit depth
displays. (e.g. 15 or 16 bit depth)
Older Bugs
----------
* several manpages are missing or out of date for various tools
* X11 framebuffer often fails to display on certain middle bit depth
displays. (e.g. 15 or 16 bit depth)
Annoyances
----------
* matrix edits on objects in mged require you to select a primitive
for a coordinate system reference. this can be counterintuitive and
confusing.
* there are frequently modality errors when entering edit mode as
control and middle mouse rebind to model edit instead of view edit.
---
Bugs should be reported to the bug tracker on the project website at
http://sourceforge.net/tracker/?atid=640802&group_id=105292
BUGS items should be formated to column 70 (M-q in emacs), no tabs
+50 -69
View File
@@ -1,78 +1,60 @@
BRL-CAD Copying and Distribution
================================
BRL-CAD Distribution
====================
BRL-CAD is open source software controlled and maintained by the
designated project developers and the US Army Research Laboratory.
BRL-CAD developers. BRL-CAD is made available under the terms of the
BRL-CAD License Agreement, provided via doc/legal/brlcad.txt in the
source distribution. The BRL-CAD License Agreement should be referred
to for exact details and clarification of how BRL-CAD may be used,
incorporated into, or otherwise redistributed.
BRL-CAD is made available under the terms of the GNU General Public
License (GPL) as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
BRL-CAD is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with this file. If you did not, please contact one of the
BRL-CAD project admins listed at http://sf.net/projects/brlcad/ or in
the AUTHORS file included as part of the distribution.
You should have received a copy of the BRL-CAD License Agreement along
with this distribution; if not, please write to the Advanced Computer
Systems Team Leader, U.S. Army Research Laboratory, AMSRD-ARL-SL-BE,
Bldg 238, APG, MD 21005-5168 USA.
Overview
--------
BRL-CAD consists primarily of libraries, applications, scripts,
documentation, geometric models, images, and build infrastructure.
The BRL-CAD libraries include the headers in the include/ directory as
well as all of the directories that begin with the prefix "lib" in the
src/ directory (e.g. src/librt/). All of BRL-CAD's libraries are
covered by the terms of the GNU Lesser General Public License (LGPL)
as published by the Free Software Foundation unless noted otherwise in
the source files.
Most of BRL-CAD's build infrastructure (i.e. files required by the GNU
Build System such as the configure.ac and all Makefile.am files), a
variety of scripts located in the misc/ and sh/ directories, and the
testing infrastructure (scripts and resources) are provided either
under the BSD license or are in the public domain. Refer to each
individual file for specific terms.
BRL-CAD consists primarily of libraries, applications, documentation,
and build infrastructure. The BRL-CAD libraries include the headers
in the include/ directory as well as all of the directories that begin
with the prefix "lib" in the src/ directory (e.g. src/librt/). All of
BRL-CAD's libraries are covered by the terms of the BRL-CAD License
Agreement.
BRL-CAD's documentation consists of manual pages located throughout
the package, most of the files in the doc/ directory, and the
the package, the majority of files in the doc/ directory, and the
top-level administrative project text files (e.g. README & AUTHORS).
Unless otherwise denoted, all of BRL-CAD's documentation is made
available under the terms of the GNU Free Documentation License (GFDL)
or, at your option, under the terms of the GNU General Public License
(GPL) as published by the Free Software Foundation. Several older
documents (e.g. published by the U.S. Government prior to being
released as Open Source) are in the public domain. Refer to each
document and the original author(s) individually for specific terms.
All of BRL-CAD's build infrastructure (i.e. files required by the GNU
Autotools), a variety of scripts located in the misc/ and sh/
directories, and the testing infrastructure are provided either under
a rather unrestrictive BSD-style license or said files are in the
public domain. Refer to each individual file for specific terms.
Unless previously described or otherwise already covered by another
license, the BRL-CAD package is covered under the terms of the GNU
General Public License (GPL) as published by the Free Software
Foundation. This includes but is not limited to the applications,
geometric models, images, and other resource data included in the
BRL-CAD distribution.
license, the BRL-CAD package is covered under the terms of the BRL-CAD
License Agreement.
The full text of the GPL, LGPL, GFDL, and BSD license should be
included in the source distribution of BRL-CAD in the doc/legal/
directory. Refer to the full license text for more details,
information, and implications of each license.
3rd-Party Components
3rd Party Components
--------------------
BRL-CAD includes software code and files that are covered by other
licenses including but not limited to the Berkeley Software
Distribution (BSD) license and the GNU Free Documentation License.
The specific terms of BRL-CAD's licenses should be included in the
doc/legal/ directory of the source code distribution and should be
consulted for more details, information, and implications of each
license.
The BRL-CAD package utilizes and redistributes copies of several 3rd
party source code, libraries, and/or applications. Said 3rd party
source code, libraries, and/or applications all retain their
respective agreements, licenses, and copyrights and should be referred
to individually for their specific terms. For purposes of
redistribution and legal compatibility, external component libraries
should not be under the terms of the GPL or any other license with
similar legal implications.
to individually for their specific terms.
When referring to BRL-CAD, its source code, documentation, and/or
When referring to BRL-CAD source code, documentation, and/or
libraries, this is not meant to include or imply 3rd party source
code, libraries, and/or applications unless specifically stated
otherwise. The majority of the 3rd party source code, libraries, and
@@ -82,27 +64,26 @@ directory of the source code distribution.
Copyright
---------
All contributions to BRL-CAD have been provided under agreement. By
requiring all contributions be given back to the BRL-CAD developers,
this agreement allows the BRL-CAD project to continue to grow
unhindered. As such, a majority of the source code is copyright by
the United States Government as represented by the United States Army
Research Laboratory.
All contributions to BRL-CAD have been provided under agreement. This
agreement allows the BRL-CAD project to continue to grow unhindered by
requiring all contributions be given back to the BRL-CAD developers.
As such, a majority of the source code is copyright by the United
States government in all countries except the United States. In the
United States, the terms of the BRL-CAD License Agreement do still
apply regardless of copyright.
Authors and other BRL-CAD contributors must comply with the copyright
terms for their respective contributions unless otherwise noted or
arranged. The following notice should be prominent in the BRL-CAD
sources:
Copyright (c) 2005-2006 United States Government as represented by
the U.S. Army Research Laboratory. All Rights Reserved.
Copyright 2004, United States Government as represented by the
Director of the U.S. Army Research Laboratory. No copyright is
claimed in the United States under Title 17, U.S.Code. All Other
Rights Reserved.
Trademark
---------
The word mark "BRL-CAD" and the "BRL-CAD Eagle" image are registered
trademarks of the Department of the Army, United States Government.
All rights are reserved.
---
$Revision$
The mark "BRL-CAD" and the "BRL-CAD Eagle" are registered trademarks
of the United States Army. All rights are reserved.
-605
View File
File diff suppressed because one or more lines are too long
+77 -315
View File
@@ -1,4 +1,4 @@
The Hacker's Guide to BRL-CAD
The Hacker's Guide to BRL-CAD
=============================
Please read this document if you are contributing to BRL-CAD.
@@ -7,7 +7,7 @@ BRL-CAD is a relatively large package with a long history and
heritage. Many people have contributed over the years, and there
continues to be room for involvement and improvement in just about
every aspect of the package. As such, contributions to BRL-CAD are
very welcome and appreciated.
very welcome and appreciated.
For the sake of code consistency and long-term evolution of BRL-CAD,
there are guidelines for getting involved. Developers are strongly
@@ -15,15 +15,6 @@ encouraged to follow these guidelines. There are simply too many
religious wars over what usually come down to personal preferences and
familiarity that are distractions from making productive progress.
Although BRL-CAD was originally developed and supported primarily by
the U.S. Army Research Laboratory and its affiliates, it is now a
true Open Source project with source code contributions coming from
around the world. The U.S. Army Research Laboratory continues to
support and contribute to BRL-CAD, but now the source code is
primarily driven by a team of core developers and the BRL-CAD open
source community. Contact the BRL-CAD developers for more
information.
TABLE OF CONTENTS
-----------------
@@ -47,71 +38,23 @@ TABLE OF CONTENTS
GETTING STARTED
---------------
As there are many ways to get started with BRL-CAD, one of the most
important steps for new developers to do is get involved in the
discussions and communicate with the BRL-CAD developers. There are
mailing lists, on-line forums, and an IRC channel dedicated to BRL-CAD
developer communication. Developers are encouraged to participate in
all of them.
* E-mail Mailing Lists
Go to http://sourceforge.net/mail/?group_id=105292 and join the
"brlcad-devel" mailing list. More involved developers will also
want to join the "brlcad-commits" and "brlcad-tracker" lists.
* On-line Forums
Discussion forums are available on the project site at
http://sourceforge.net/forum/?group_id=105292 for both developers
and users. Of particular interest to developers is, of course, the
"Developers" forum.
* Internet Relay Chat
The primary and generally preferred mechanism for interactive
developer discussions is via IRC. Several of the core developers
and users of BRL-CAD hang out in #brlcad on the Freenode network.
With most any IRC client you should be able to join #brlcad on
irc.freenode.net, port 6667. See http://freenode.net and
http://irchelp.org for more information
To contribute source code to BRL-CAD, begin by submitting source code
patches to the patches section at http://sf.net/projects/brlcad/.
Patches in the universal diff format (diff -u) are preferred.
HOW TO CONTRIBUTE
-----------------
BRL-CAD's open source developer management structure is best described
as a meritocracy. Roughly stated, this basically means that the power
to make decisions lies directly with the individuals that have ability
or merit with respect to BRL-CAD. An individual's ability and merit
is basically a function of their past and present contributions to the
project. Those who constructively contribute and are involved have
more say than those who don't.
As BRL-CAD is comprised of a rather large code base, there are many
many places where one may begin to get involved. More than likely,
there is some new goal you already have in mind, be it a new geometry
converter, support for a different image type, a fix to some bug, or
something else entirely. Regardless of the goal or contribution, it's
highly encouraged that you interact with the developers and discuss
your intentions if you would like to see your modification added to
BRL-CAD. When in doubt, working on resolving existing bugs, improving
performance, documentation, and writing tests are perfect places to
begin.
your intentions. When in doubt, working on resolving existing bugs,
improving performance, documentation, and writing tests are perfect
places to begin.
For many, at first, it can be overwhelming at just how much there is.
To a certain extent, you will need to familiarize yourself with the
basic existing facilities before adding a completely new feature.
There is documentation available at in the source distribution's doc/
directory, throughout the source hierarchy in manpages, and at
http://sourceforge.net/docman/?group_id=105292 covering a variety of
topics.
It is not uncommon that some particular piece of code that you are
basic existing facilities before adding a completely new feature. It
is not uncommmon that some particular piece of code that you are
either working on or thinking about writing is in fact already
written. Again, working with the other developers and reading the
source code itself is a great place to begin.
@@ -120,12 +63,12 @@ source code itself is a great place to begin.
SYSTEM ARCHITECTURE
-------------------
At a glance, BRL-CAD consists of about a dozen libraries and over 400
At a glance, BRL-CAD consists of about a dozen libraries and about 400
executable binaries. The package has been designed from the ground up
adopting a UNIX methodology, providing many tools that may often be
used in harmony in order to complete a task at hand. These tools
include geometry and image converters, image and signal processing
tools, various raytrace applications, and geometry manipulators.
adopting a UNIX methodology, providing many tools that may be used in
harmony in order to complete a task at hand. These tools include
geometry and image converters, image and signal processing tools,
various raytrace applications, and geometry manipulators.
One of the firm designs of the architecture is to be as cross-platform
as is realistically possible. As such, BRL-CAD maintains support for
@@ -182,7 +125,7 @@ the wireframe in the geometry editor).
libfb: The framebuffer library is an interface for managing a graphics
context that consists of pixel data. This library supports multiple
devices directly, providing a generic device-independent method of
devices directly, providing a generic device-independant method of
using a frame buffer or files containing frame buffer images.
libfft: The Fast-Fourier Transform library is a signal processing
@@ -191,7 +134,7 @@ library for performing FFTs or inverse FFTs efficiently.
libmultispectral: The multispectral optics library is a separate
compilation mode of the raytrace library where support for additional
bands of energy is added. By providing a defined spectrum of energy,
the raytrace library will produce different signal analyses for a given
the raytrace library will produce different signal analyses of a given
set of geometry.
liboptical: The optical library is the basis for BRL-CAD's shaders.
@@ -200,11 +143,10 @@ models, as well as various visual effects such as texturing, marble,
wood graining, air, gravel, grass, clouds, fire, and more.
liborle: The "old" run-length encoding library that will decode and
encode University of Utah Raster Toolkit format Run-Length Encoded
data.
encode University of Utah Raster Toolkit format Run-Length Encoded data.
libpkg: The "Package" library is a network communications library that
supports multiplexing and demultiplexing synchronous and asynchronous
supports multiplexing and demultiplexing syncronous and asynchronous
messages across stream connections. The library supports a
client-server communication model.
@@ -219,14 +161,14 @@ systems that lack functionality required by BRL-CAD. This library is
deprecated and should not be used for new development.
libtclcad: The Tcl-CAD library is a thin interface that assists in the
binding of an image to a Tk graphics context.
binding of an image to a Tk graphcs context.
libtermio: The terminal I/O library is a TTY control library for
managing a terminal interface.
libwdb: The "write database" library provides a simple interface for
the generation of BRL-CAD geometry files supporting a majority of the
various primitives available as well as combination/region support.
various primitives available as well as combintaion/region support.
The library is a write-only interface (librt is necessary to read &
write) and is useful for procedural geometry.
@@ -240,8 +182,8 @@ Tcl/Tk. The BRL-CAD Benchmark, build system, and utility scripts are
written in Bourne Shell Script. An initial implementation of a
BRL-CAD Geometry Server is written in PHP.
With release 7.0, BRL-CAD has moved forward and worked toward making
all of BRL-CAD C code conform with the ANSI/ISO standard for C
With release 7.0, BRL-CAD has moved forward and worked towards making
all of BRL-CAD C code conformant with the ANSI/ISO standard for C
language compilation (ISO/IEC 9899:1990). Support for older compilers
and older K&R-based system facilities is being migrated to the build
system declarations and preprocessor defines.
@@ -250,75 +192,55 @@ system declarations and preprocessor defines.
FILESYSTEM ORGANIZATION
-----------------------
Included below is a sample (not comprehensive) of how some of the
sources are organized in the source distribution. For the directories
under src/, see the src/README file for more details on subdirectories
not covered here.
Here is a sample (not comprehensive) of how some of the sources are
organized in the source distribution:
bench/
The BRL-CAD Benchmark Suite
db/
Example geometry databases
Geometry databases
doc/
Documentation
include/
Public headers
m4/
Autoconf compilation resource files
misc/
Anything not categorized or is sufficently en masse
Everything else
pix/
Sample raytrace images, includes benchmark reference images
regress/
Scripts and resources for regression testing
Sample raytrace images
sh/
Utility scripts, used primarily by the build system
Utility scripts
src/
Sources, see src/README for more details
Sources
src/anim/
Animation utilities
src/conv/
Various geometry converters
src/conv/iges/
IGES converter
Geometry converters (most, but not all)
src/fb/
Tools for displaying data to or reading from framebuffers
Framebuffer services
src/fbserv/
Framebuffer server
src/java/
Java geometry server interface to librt
src/libbn/
BRL-CAD numerics library
src/libbu
BRL-CAD utility library
src/libfb/
BRL-CAD Framebuffer library
src/libfft/
Fast Fourier transform library
src/libpkg/
Network "package" library
src/librt/
BRL-CAD Ray-trace library
src/libwdb/
Write database library
src/lib/
BRL-CAD libraries
src/mged/
Multi-device geometry editor
Geometry Editor
src/other/
External frameworks (Tcl/Tk, libpng, zlib, etc)
src/proc-db/
Procedural geometry tools, create models programmatically
Procedural geometry generators
src/remrt/
Distributed raytrace support
src/rt/
Raytracers, various
Raytracers
src/util/
Various image processing utilities
Various data processing utilities
CODING STYLE
------------
For anyone who plans on contributing code, the following conventions
should be followed. Contributions that do not conform are likely to
be ridiculed and rejected until they do.
should be followed. Contributions that do not conform will be
rediculed and rejected until they do.
Code Organization:
@@ -340,21 +262,12 @@ standard header files, available libraries, and data types. No
assumptions should be made regarding the availability of any
particular header, function, datatype, or other resource. After
running the configure script, there will be an autogenerated
include/brlcad_config.h file that contains many preprocessor
directives and type declarations that may be used where needed.
include/config.h file that contains many preprocessor directives and
type declarations that may be used where needed.
Generic platform checks (e.g. #ifdef unix, #ifdef _WIN32) are highly
discouraged and should not be used. Replace those checks with tests
for the actual facility being utilized instead.
The Windows platform utilizes its own manually-generated configure
results header (include/config_win.h) that has to be manually updated
if new tests are added to the configure.ac template.
The BRL-CAD sources as well as packages linking to BRL-CAD should
include the common.h header. They should not include brlcad_config.h
or config_win.h directly. The common.h header should be listed before
any other headers.
Generic platform checks (e.g. ifdef unix) are highly discouraged and
should not be used. Replace those checks with tests for the actual
facility being utilized instead.
Coding Standards:
@@ -363,9 +276,9 @@ are generally the baseline for strict language conformance.
Particulars of the usage of the language calls special attention to
the following:
Globals variables, structures, and other data types are discouraged -
globals are often the easy way around a hard coding problem, try to
find another solution unless there is a good reason.
globals are discouraged - globals are often the easy way around a hard
coding problem, try to find another solution unless there is a good
reason.
"//" style comments are not allowed. This is mainly to cause less
grief when porting to the older systems where such support is
@@ -380,26 +293,21 @@ of being consistent.
1) Whitespace
Indents are 4 characters, tabs are 8 characters. There should be an
emacs and vi local variables block setting at the end of each file to
adopt, enforce, and otherwise remind this convention. The following
lines should be in all C source and header files at the end of the
file:
Indents are 2 characters, tabs are 8 characters. There should be an
emacs and vi setting at the end of each file to adopt, enforce, and
remind this convention. The following lines should be in all source
and header files at the end of the file:
/*
* Local Variables:
* mode: C
* tab-width: 8
* c-basic-offset: 4
* indent-tabs-mode: t
* End:
* ex: shiftwidth=4 tabstop=8
* Local Variables: ***
* mode:C++ ***
* tab-width: 2 ***
* c-basic-offset: 2 ***
* indent-tabs-mode: t ***
* End: ***
* ex: shiftwidth=2 tabstop=8
*/
A similar block can be used on source and script files in other
languages (such as Tcl, Shell, Perl, etc). See the local variable
footer script in sh/footer.sh to automatically set/update files.
Space around operators.
a = (b + c) * d; /* ok */
@@ -421,11 +329,11 @@ braces should line up with that same statement.
j -= 1;
}
}
3) Names
Prefer mixed-case names over underscore-separated ones. (this one is
less important, as there are vast quantities of both in the code)
less important, as there are vast majorities of both in the code)
Variable names should start with a lowercase letter.
double localVariable; /* ok */
double LocalVariable; /* bad (looks like class or constructor) */
@@ -456,7 +364,7 @@ Compilation preprocessor defines should never change the size of structures.
};
Use libbu's memory allocation and logging routines. Use bu_malloc(),
bu_free(), and bu_log() instead of malloc(), free(), and printf().
bu_free(), bu_log() instead of malloc(), free(), printf(), etc.
---
@@ -479,13 +387,13 @@ and add documentation accordingly.
All public library functions and most private or application functions
should be appropriately documented using Doxygen style comments.
Without getting into the advanced details, this minimally means that
you need to add an additional asterisk to a comment that precedes your
you need to add an additional asterisk to a comment that preceeds your
functions:
/** Computes the answer to the meaning of life, the universe, and
* everything.
*/
int the_answer() { return 42; };
int everything() { return 42; };
TESTING
@@ -516,10 +424,6 @@ To perform a run of the benchmark suite to validate raytrace behavior:
make benchmark
To perform a run of the test suite:
make test
PATCH SUBMISSION GUIDELINES
---------------------------
@@ -538,25 +442,16 @@ belong (or what should be removed). If CVS cannot be used, please
provide the complete release and build number of the sources you
worked with.
Any source code that is provided must not modify or conflict with the
existing COPYING file distribution requirements. This means that
library modifications must be LGPL-compatible and changes to
applications must be GPL-compatible. Similarly, GPL libraries may not
be used or otherwised linked to BRL-CAD. Contributors are asked to
only provide patches that may legally be incorporated into BRL-CAD
under the existing distribution provisions described in the COPYING
file.
Patches that are difficult to apply are difficult to accept.
BUGS
----
When a bug or unexpected behavior is encountered that cannot be
quickly fixed, it needs to be documented. If you are already a
BRL-CAD developer, this means either making a comment in the BUGS file
or by making a formal report to the SourceForge bug tracker at:
When a bug or unexpected behavior is encountered, it needs to be
documented. If you are a BRL-CAD developer, this means either making
a comment in the BUGS file or by making a formal report to the
SourceForge bug tracker at:
http://sourceforge.net/tracker/?atid=640802&group_id=105292&func=browse
@@ -564,8 +459,8 @@ If the bug is complicated, will require discussion, cannot be fixed
any time soon, or if you do not have CVS commit access, the issue
should be reported to the SourceForge bug tracker. The issues listed
in BUGS are not necessarily listed in bug tracker, and vice-versa.
The BUGS file is merely maintained as a convenience notepad of long
and short term issues for the developers only.
The BUGS files is merely maintained as a convenience notepad of long
and short term issues for the developers.
COMMIT ACCESS
@@ -574,7 +469,7 @@ COMMIT ACCESS
Details on the particulars of how to interact with CVS are described
in the doc/cvspolicy.txt document. In brief, BRL-CAD has a STABLE
branch in CVS that should always compile and run with expected
behavior on all supported platforms. On the contrary, while the CVS
behavior on all supported platforms. On the contrary, while the CVS
HEAD is generally always expected to compile, more flexibility is
allowed for resolution of cross-platform build issues. Read the CVS
policy document for more details.
@@ -582,16 +477,16 @@ policy document for more details.
CVS commit access is evaluated on a person-to-person basis at the
discretion of the existing developers. If you'd like to have commit
access, there is usually no need to ask. Getting involved with the
other developers and making patches will generally result in automatic
consideration for CVS commit access. If you have to ask for it, you
probably won't get it.
other developers and making patches will generally result in
consideration to grant CVS access over time. If you have to ask for
it, you probably won't get it.
Those with CVS commit access have a responsibility to ensure that
other developers are following the guidelines that have been described
herein within reason. A basic rule of thumb is: don't break anything.
While the testing process will strive to ensure consistent behavior as
changes are made, the responsibility still remains with the individual
changes are made, the responsilibity still remains with the individual
developer to ensure that everything still compiles and runs as it
should. At any given time, BRL-CAD should compile on all of the
primary platforms and (minimally) pass the BRL-CAD Benchmark
@@ -625,11 +520,10 @@ considered compatible with each other.
The MINOR_VERSION is updated more frequently and serves the dual role
as previously mentioned of easily identifying a build as a public
release. A minor version update is generally issued after significant
development activity (generally several months of activity) has been
development activity (generally a month or more of activity) has been
tested and deemed sufficiently stable. When a stable release is made,
it may (but not necessarily) be tagged as a maintenance branch in CVS
(see doc/cvspolicy.txt) with patch releases being performed on that
branch.
it is tagged as a maintenance branch in cvs (see doc/cvspolicy.txt)
and patch releases are performed on that branch.
The PATCH_VERSION may and should be updated as frequently as is
necessary. Every public maintenance release should increment the
@@ -637,135 +531,3 @@ patch version. Every development version modification that is
backwards incompatible in some manner should increment the patch
version number.
MAKING A RELEASE
----------------
BRL-CAD uses a monthly iteration development cycle. If there have
been significant changes since the previous iteration, the developers
are expected to "settle down" around the last couple days of the month
so that the source code may be verified, tested, and released. Major
changes to the source code should not occur during these last couple
days of the iteration, only minor bug and build fixes. A release
should then be made within the first couple days of the next month's
iteration. Repeat, rinse, recycle.
In addition to the monthly iteration release, additional releases may
be made on an as-needed basis. This is particularly relevant for
emergency bug-fix releases and in response to security issues. The
December/January timeframe is considered a single iteration with only
one iteration release necessarily being made in that timeframe.
When making a release, certain public repositories, mailing lists, and
news outlets require updating and notification. Especially when the
major or minor version of BRL-CAD is going to be updated, it is very
important to follow and ensure that the following steps have been
successfully performed:
0) All code is committed to CVS.
1) Verify that the NEWS file includes a comment for all relevant and
significant items added since the previous release.
2) All existing manual pages and the TODO file are updated with the
latest changes.
3) Update or verify the version numbers minimally in configure.ac,
NEWS, README, and include/config_win.h (see VERSION NUMBERS &
COMPATIBILITY section) and commit the changes to the source
repository.
4) Update the ChangeLog with entries since the last release; commit
the updated ChangeLog. Use the YYYY-MM-DD of the previous release.
Get the date from the NEWS file.
rcs2log -h users.sourceforge.net -r "-d>YYYY-MM-DD" > ChangeLog
5) A "./configure && make" completes successfully on all platforms.
6) Perform a "make distcheck" successfully. This will ensure that a
proper source distribution tarball may be generated and that a build
should compile properly regardless of the existence of the GNU Build
System tools (autoconf, automake, etc).
7) Tag the release using the format "rel-MAJOR-MINOR-PATCH". See the
doc/cvspolicy.txt document for details. e.g. cvs tag rel-7-2-4
8) Export a tagged version of the sources (required so that RCS ids
are correct): cvs export -r rel-MAJOR-MINOR-PATCH brlcad
9) Perform another "make distcheck" on the exported/updated sources
(preferably on Mac OS X) to generate the distributable compressed
source tarballs.
10) Verify that the source distribution tarballs may be expanded; and
that they build, run, and that the file permissions are correct.
11) Use one of the source distribution tarballs to generate
platform-specific builds. Test the build: make test && make bench
12) Post the source and platform-specific binary distributions to
SourceForge (i.e. upload them via ftp to upload.sf.net's incoming
directory and select them on the sf.net File Release System).
13) Increment and commit the next BRL-CAD release numbers to CVS;
update the configure.ac, README, include/config_win.h, and NEWS
immediately to a developer version (odd minor or patch version number,
e.g. 7.4.1).
14) If appropriate, notify and/or update the following information
outlets with the details of the new release:
News on the BRL-CAD website
http://brlcad.org/
with news details
SourceForge Project News
http://sf.net/projects/brlcad/
with news details
BRL-CAD News & Users mailing lists
brlcad-news@lists.sourceforge.net
brlcad-users@lists.sourceforge.net
with news details
CAD on Linux mailing list
cad-linux@freelists.org
with news details
Freshmeat
http://freshmeat.net/projects/BRL-CAD/
short without news details
upFront.ezine (if major)
Ralph Grabowski
ralphg@upfrontezine.com
with news details
CADinfo.NET (if major)
copyboy@cadinfo.net
with news details
TenLinks Daily (if major)
http://www.tenlinks.com/NEWS/tl_daily/submit_news.htm
news@tenlinks.com
with news details
Slashdot (if major)
http://slashdot.org
short without news details
Government Computer News (if major)
Joab Jackson
jjackson@gcn.com
short without news details
15) Sit back and enjoy a beverage for a job well done.
GETTING HELP
------------
See the GETTING STARTED section above. Basically, communicate with
the existing developers. There is an IRC channel, e-mail mailing
lists, and on-line forums.
+224 -309
View File
@@ -1,321 +1,236 @@
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.MacOSX -- Apple Mac OS X
doc/README.IRIX -- SGI IRIX and IRIX64
TABLE OF CONTENTS
-----------------
Introduction
Table of Contents
Quick Installation
Installing from Source
Installing from Binary
Configuration Options
Compilation Options
Installation Options
Post-Installation
Testing an Install
Reporting Problems
QUICK INSTALLATION
------------------
For the impatient or simplistic, the following should compile, test,
and install BRL-CAD quickly into the /usr/brlcad directory. If you
have a configure script, run the following:
./configure
make
make benchmark
make install # as root, e.g. sudo make install
make test
If you don't have a configure script, run the following to generate
the script then proceed with the steps above:
sh autogen.sh
If any of the listed steps fail, then something unexpected happened.
See the reporting problems section of this document to report the
problem.
Once installed, add /usr/brlcad/bin to your path, and you should be
able to run one of the 400+ applications that constitute BRL-CAD. For
example, to run the MGED solid modeler:
PATH=/usr/brlcad/bin:$PATH ; export PATH
mged
If you use tcsh or another C-shell based command shell, use this
instead:
set path=( /usr/brlcad/bin $path ) ; rehash
mged
INSTALLING FROM SOURCE
----------------------
There are a couple means to obtain the BRL-CAD sources, via either a
CVS checkout/export or a source distribution tarball. Using the
latest CVS sources is recommended where possible, since it will have
the latest changes.
Starting From a CVS Checkout/Export:
If you have obtained the BRL-CAD sources from the CVS revision control
system, you will need to prepare the build for configuration:
sh autogen.sh
This step requires that you have the GNU Build System (GBS) installed,
which includes a sufficiently recent version of Autoconf, Automake,
and Libtool. Running autogen.sh will verify that the versions of each
are sufficient and will generate the `configure' script. If you do
not have sufficient versions of the GBS components installed, you will
either need to install/ugrade them, run autogen.sh on another system
and them copy the files over, or start with a source tarball
distribution (where autogen.sh is automatically run for you).
Once autogen.sh is sucessfully run somewhere, you can continue with
the steps shown next for starting from a source distribution.
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
for installation into the /usr/brlcad directory (the --prefix option
may be used to change that). This tradition goes back a couple
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 the `configure' script:
./configure
By default, an unoptimized debug build of BRL-CAD will be configured
for compilation. To obtain an optimized build (for example, for
BRL-CAD Benchmark performance testing), use the --enable-optimized
configure option:
./configure --enable-optimized
By default, all components and functionality will be built except
jove. However, 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. You can force any one of those components
on or off via --enable-FEATURE and --disable-FEATURE arguments to
configure:
./configure --enable-termlib --disable-png
See the Configuration Options below for more details on all of the
possible settings.
Once configured, you should be able to succesfully build BRL-CAD via
make:
make
See the Compilation Options section in this document for more details
on compile-time options including options for parallel build support.
Testing a Compilation:
Once the compilation is complete, you can test it before and after
installation. To test a compilation of 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
See the Testing An Install section of this document for more details
on testing your BRL-CAD distribution.
Installing a 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 or sudo commands:
sudo make install
See the Installation Options section of this document for more details
on BRL-CAD installation options and post-install environment
preparations.
INSTALLING FROM BINARY
----------------------
There are a variety of different kinds of BRL-CAD binary
distributions. Some of the binary disributions are sufficiently
generic and are simply a binary commpressed tarball distribution.
Others are specific to a particular platform such as Debian, Mac OS X,
FreeBSD, 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. That is to say that they
contain /usr/brlcad in it's entirety so that if you decompress, you
will have a `usr' directory that contains a single `brlcad' directory:
gunzip brlcad-7.2.4_linux_ia64.tar.gz
tar -xvf brlcad-7.2.4_linux_ia64.tar
sudo mv usr/brlcad /usr/.
Of course, there are other compression options possible including zip
and bzip2. By default, BRL-CAD expects to be installed into
/usr/brlcad and MGED is not relocateable by default. It's recommended
that you start from a source distribution if you would like to install
into an alternate installation location.
However, if you do desire to install and run BRL-CAD from a different
location, give it a try.. ;) The only problems encountered should be
with running the MGED solid modeler where you will need to set the
BRLCAD_ROOT environment variable to your different install location
(e.g. /usr/local). If this doesn't work (some platforms are more
problematic than others), you will need to compile and install from a
source distribution.
Mac OS X Disk Mounting Image:
Mount the .dmg and run the Installer .pkg contained therein. This
will install into /usr/brlcad and will only require confirming that
your environment is set up properly (i.e. add /usr/brlcad/bin to your
path) as described in this document's Installation Options section.
CONFIGURATION OPTIONS
---------------------
By default, BRL-CAD is configured to build the entire package and will
install completely isolated into the /usr/brlcad directory.
Configuration will prepare the build for an unoptimized compilation by
default and will attempt to utilize required system libraries if they
are available, otherwise compiling the required library dependencies
as needed. Run `./configure --help' for a list of all of the possible
configuration options.
Variables can be set in the environment passed to `configure'.
However, the build may run configure again during the build, and the
customized values of these variables may be lost. In order to avoid
this problem, you should set them in the `configure' command line,
using `VAR=value'. For example:
./configure CC=/usr/ucb/bin/cc
will cause the specified executable program to be used as the C
compiler.
COMPILATION OPTIONS
-------------------
If you are on a multiprocessor machine, you can compile in parallel
depending on the version of `make' being used. For the GNU and BSD
make, you can use the -j argument. For example, to use 4 CPUs:
make -j4
With the IRIX compiler, the -P option enables parallel build mode and
the PARALLEL environment variable sets the number of CPUs (default is
two):
PARALLEL=4 make -P
INSTALLATION OPTIONS
--------------------
By default, `make install' will install BRL-CAD's files into
`/usr/brlcad/bin', `/usr/brlcad/man', etc. You can specify an
installation prefix other than `/usr/brlcad' by giving `configure' the
Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
Setting Up the Path:
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
Once installed, you will need to add /usr/brlcad/bin to your system
PATH. For Bourne shell users, you can run the following:
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
PATH=/usr/brlcad/bin:$PATH ; export PATH
Optional Features
=================
For C shell users, this should do the same thing:
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
set path=( /usr/brlcad/bin $path ) ; rehash
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
If you would like to provide BRL-CAD to multiple users, your shell
environment scripts should be edited so that /usr/brlcad/bin is added
to the system path. This usually entails editing /etc/profile,
/etc/csh.login, /etc/bashrc, and possibly other files depending on
your platform.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
`configure' recognizes the following options to control how it
operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
Setting Up the Manual Pages Path:
It may be useful to add /usr/brlcad/man to your MANPATH in the same
manner as shown above for PATH. Conversely, you could use the
`brlman' command that is already preconfigured to locate the BRL-CAD
manpages.
On IRIX
./configure CC=cc CFLAGS=-64 LDFLAGS=-64 --enable-64bit-build
or
./configure CC=cc
TESTING AN INSTALL
------------------
After BRL-CAD is installed, you can test the installation via:
make test
This will run a series of tests on the installed sources to make sure
that they behave as they should. Similarly, simply running `rt'
and/or `mged' are good tests of basic functionality. Running `rt'
without any options should display version information and a usage
message. Running `mged' without any options will start the GUI-based
solid modeler applicaation.
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.
---
$Revision$
+46 -339
View File
@@ -1,42 +1,6 @@
# M A K E F I L E . A M
# BRL-CAD
#
# Copyright (c) 2005-2006 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
#
# 3. The name of the author may not be used to endorse or promote
# products derived from this software without specific prior written
# permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
# OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
# GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
###
# $Id$
AUTOMAKE_OPTIONS = 1.6 dist-zip dist-bzip2
ACLOCAL_AMFLAGS = -I m4
AUTOMAKE_OPTIONS = 1.6
required_dirs = \
include \
@@ -49,7 +13,6 @@ bench_dirs = \
other_dirs = \
doc \
m4 \
misc \
regress \
sh
@@ -83,303 +46,52 @@ DIST_SUBDIRS = \
$(bench_dirs) \
$(other_dirs)
documentationdir = $(BRLCAD_DATA)
documentation_DATA = \
EXTRA_DIST = \
AUTHORS \
BUGS \
COPYING \
ChangeLog \
HACKING \
INSTALL \
NEWS \
README
EXTRA_DIST = \
$(documentation_DATA) \
BUGS \
ChangeLog \
README \
TODO \
autogen.sh \
brlcad.spec.in \
libtool
DISTCLEANFILES = \
$(CONFIG_CACHE) \
aclocal.m4 \
brlcad.spec \
config.log \
config.status \
configure \
install.$(host_triplet).log \
libtool \
so_locations
MAINTAINERCLEANFILES = Makefile.in
##########################
# packaged distributions #
##########################
$(PACKAGE)-$(VERSION).tar.gz: dist
# Build a Mac OS X Installer .pkg -- make sure the package resources
# reflect the correct version. we specifically do not use an autoconf
# template so that the file may be edited without doing a configure
# (which would also cause a need to regenerate the template to keep in
# sync every time it's edited).
$(PACKAGE_NAME)-$(VERSION).pkg:
@if ! test -f "install.$(host_triplet).log" ; then \
$(ECHO) ; \
$(ECHO) "}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}" ; \
$(ECHO) " WARNING: It seems as though you might not have" ; \
$(ECHO) " installed BRL-CAD yet?" ; \
$(ECHO) ; \
$(ECHO) " You should run 'make install' before creating a" ; \
$(ECHO) " binary distribution package. Trying regardless." ; \
$(ECHO) "{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{" ; \
$(ECHO) ; \
fi
@$(ECHO) "Building an Installer package for Mac OS X"
@$(ECHO)
@$(ECHO) "Warning: this package target presently assumes that the install directory"
@$(ECHO) " does not contain extra files and comprises a full clean install."
@$(ECHO)
@if test -f "$(top_srcdir)/misc/macosx/Resources/ReadMe.rtfd/TXT.rtf" ; then \
perl -pi -e "s/BRL-CAD [0-9]*\.[0-9]*\.[0-9]/BRL-CAD $(VERSION)/g" $(top_srcdir)/misc/macosx/Resources/ReadMe.rtfd/TXT.rtf ; \
fi
@if test -f "$(top_srcdir)/misc/macosx/Resources/Welcome.rtfd/TXT.rtf" ; then \
perl -pi -e "s/BRL-CAD [0-9]*\.[0-9]*\.[0-9]/BRL-CAD $(VERSION)/g" $(top_srcdir)/misc/macosx/Resources/Welcome.rtfd/TXT.rtf ; \
fi
@${SH} $(top_srcdir)/sh/make_pkg.sh "$(PACKAGE_NAME)" "$(MAJOR_VERSION)" "$(MINOR_VERSION)" "$(PATCH_VERSION)" "$(DESTDIR)$(prefix)" "$(top_srcdir)/misc/macosx/Resources"
openUp:
cd misc/macosx && make openUp
$(PACKAGE_NAME)-$(VERSION).dmg: $(PACKAGE_NAME)-$(VERSION).pkg openUp
@$(ECHO) "Building a Disk Image for Mac OS X"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_dmg.sh "$(PACKAGE_NAME)" "$(MAJOR_VERSION)" "$(MINOR_VERSION)" "$(PATCH_VERSION)" "$(top_srcdir)/misc/macosx/background.png"
##############
# the rules #
##############
# using home is probably not a great choice..
$(PACKAGE)-$(VERSION).rpm: $(PACKAGE)-$(VERSION).tar.gz
@$(ECHO) "Building binary RPM for RedHat Linux"
@$(ECHO)
.PHONY : rpm
rpm: dist
@CP@ $(PACKAGE)-$(VERSION).tar.gz ${HOME}/rpm/SOURCES/
rpmbuild -ba $(top_builddir)/misc/brlcad.spec
rpmbuild -ba $(PACKAGE).spec
@CP@ ${HOME}/rpm/RPMS/i386/$(PACKAGE)-$(VERSION)-*.i386.rpm .
@touch $(PACKAGE)-$(VERSION).rpm
@$(ECHO) "WARNING: Fake make placeholder created as $(PACKAGE)-$(VERSION).rpm"
@$(ECHO)
# using home is probably not a great choice..
$(PACKAGE)-$(VERSION).src.rpm: $(PACKAGE)-$(VERSION).tar.gz
@$(ECHO) "Building source RPM for RedHat Linux"
@CP@ $(PACKAGE)-$(VERSION).tar.gz ${HOME}/rpm/SOURCES/
rpmbuild -ba $(top_builddir)/misc/brlcad.spec
@CP@ ${HOME}/rpm/SRPMS/$(PACKAGE)-$(VERSION)-*.src.rpm .
@touch $(PACKAGE)-$(VERSION).src.rpm
@$(ECHO) "WARNING: Fake make placeholder created as $(PACKAGE)-$(VERSION).src.rpm"
@$(ECHO)
$(PACKAGE)-$(VERSION).deb:
@$(ECHO) "Building a package for Debian Linux"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_deb.sh "$(PACKAGE_NAME)-$(VERSION)"
$(PACKAGE)-$(VERSION).bin.zip:
@if ! test -f "install.$(host_triplet).log" ; then \
$(ECHO) ; \
$(ECHO) "}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}" ; \
$(ECHO) " WARNING: It seems as though you might not have" ; \
$(ECHO) " installed BRL-CAD yet?" ; \
$(ECHO) ; \
$(ECHO) " You should run 'make install' before creating a" ; \
$(ECHO) " binary distribution package. Trying regardless." ; \
$(ECHO) "{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{" ; \
$(ECHO) ; \
fi
@$(ECHO) "Building a zip-compressed file archive"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_zip.sh "$(PACKAGE_NAME)-$(VERSION)"
@$(ECHO)
@$(ECHO) "Built $(PACKAGE_NAME)-$(VERSION).bin.zip for $(host_triplet)"
$(PACKAGE)-$(VERSION).bin.tar.gz: $(PACKAGE)-$(VERSION).bin.tar
@$(ECHO) "Building a gzip-compressed tape archive"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_tgz.sh "$(PACKAGE_NAME)-$(VERSION)"
@$(ECHO)
@$(ECHO) "Built $(PACKAGE_NAME)-$(VERSION).bin.tar.gz for $(host_triplet)"
$(PACKAGE)-$(VERSION).bin.tar.bz2: $(PACKAGE)-$(VERSION).bin.tar
@$(ECHO) "Building a bzip2-compressed tape archive"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_bz2.sh "$(PACKAGE_NAME)-$(VERSION)"
@$(ECHO)
@$(ECHO) "Built $(PACKAGE_NAME)-$(VERSION).bin.tar.bz2 for $(host_triplet)"
$(PACKAGE)-$(VERSION).bin.tar:
@if ! test -f "install.$(host_triplet).log" ; then \
$(ECHO) ; \
$(ECHO) "}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}" ; \
$(ECHO) " WARNING: It seems as though you might not have" ; \
$(ECHO) " installed BRL-CAD yet?" ; \
$(ECHO) ; \
$(ECHO) " You should run 'make install' before creating a" ; \
$(ECHO) " binary distribution package. Trying regardless." ; \
$(ECHO) "{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{" ; \
$(ECHO) ; \
fi
@$(ECHO) "Building an uncompressed tape archive"
@$(ECHO)
@${SH} $(top_srcdir)/sh/make_tar.sh "$(PACKAGE_NAME)" "$(MAJOR_VERSION)" "$(MINOR_VERSION)" "$(PATCH_VERSION)" "$(DESTDIR)$(prefix)"
@$(ECHO)
@$(ECHO) "Built $(PACKAGE_NAME)-$(VERSION).bin.tar for $(host_triplet)"
#############
# the rules #
#############
.PHONY : benchmark bench regression regress test pkg dmg rpm deb zip tgz tbz
packages: rpm
benchmark: all
${SH} $(top_srcdir)/bench/run.sh
@SH@ $(top_srcdir)/bench/run.sh
bench: benchmark
regression: all
@cd regress && make regression
regress: regression
test: regression
pkg: $(PACKAGE_NAME)-$(VERSION).pkg
@$(ECHO) "Done."
dmg: pkg $(PACKAGE_NAME)-$(VERSION).dmg
@$(ECHO) "Done."
rpm: $(PACKAGE)-$(VERSION).rpm $(PACKAGE)-$(VERSION).src.rpm
@$(ECHO) "Done."
deb: $(PACKAGE)-$(VERSION).deb
@$(ECHO) "Done."
zip: $(PACKAGE)-$(VERSION).bin.zip
@$(ECHO) "Done."
tgz: $(PACKAGE)-$(VERSION).bin.tar.gz
@$(ECHO) "Done."
bz2: $(PACKAGE)-$(VERSION).bin.tar.bz2
@$(ECHO) "Done."
tar: $(PACKAGE)-$(VERSION).bin.tar
@$(ECHO) "Done."
package:
@$(ECHO)
@$(ECHO) "To build a BRL-CAD package for distribution, there are various make"
@$(ECHO) "targets available for various platforms:"
@$(ECHO)
@$(ECHO) " make pkg - Builds an Installer package for Mac OS X"
@$(ECHO) " make dmg - Builds a Disk Image for Mac OS X"
@$(ECHO) " make rpm - Builds source and binary RPM for RedHat Linux"
@$(ECHO) " make deb - Builds a package for Debian Linux"
@$(ECHO) " make zip - Builds a zip-compressed file archive"
@$(ECHO) " make tgz - Builds a gzip-compressed tape archive"
@$(ECHO) " make bz2 - Builds a bzip2-compressed tape archive"
@$(ECHO) " make tar - Builds a uncompressed tape archive"
@$(ECHO)
# delete files that should not be in the distribution
dist-hook:
rm -f $(distdir)/include/brlcad_config.h
rm -rf `find $(distdir) -type d -name CVS`
##########################
# summaries and warnings #
##########################
# make sure a dangerous umask will not prevent others from using an
# installed version by checking to make sure the exec mode is set.
# We minimally check only the binary and prefix directories.
install-data-local:
@warn_umask=no ; \
case `ls -ld $(DESTDIR)$(prefix)` in \
d????????-*) warn_umask=yes ;; \
d?????-???*) warn_umask=yes ;; \
d??-??????*) warn_umask=yes ;; \
esac ; \
if test "x$$warn_umask" = "xno" ; then \
case `ls -ld $(DESTDIR)$(bindir)` in \
d????????-*) warn_umask=yes ;; \
d?????-???*) warn_umask=yes ;; \
d??-??????*) warn_umask=yes ;; \
esac ; \
fi ; \
if test "x$$warn_umask" = "xyes" ; then \
$(ECHO) ; \
$(ECHO) "}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}" ; \
$(ECHO) " WARNING: There is no execute permission on the" ; \
$(ECHO) " install directory." ; \
$(ECHO) ; \
$(ECHO) " Consider running \"umask 022\" before installing" ; \
$(ECHO) " next time. You should be able to repair this"; \
$(ECHO) " installation's directory permissions with: " ; \
$(ECHO) ; \
$(ECHO) " find $(DESTDIR)$(prefix)/. -type d -exec chmod go+x {} \;" ; \
if test -d "$(DESTDIR)$(bindir)" ; then \
if test "x$(DESTDIR)$(exec_prefix)/bin" != "x$(DESTDIR)$(bindir)" ; then \
$(ECHO) " find $(DESTDIR)$(bindir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(sbindir)" ; then \
if test "x$(DESTDIR)$(exec_prefix)/sbin" != "x$(DESTDIR)$(sbindir)" ; then \
$(ECHO) " find $(DESTDIR)$(sbindir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(libexecdir)" ; then \
if test "x$(DESTDIR)$(exec_prefix)/libexec" != "x$(DESTDIR)$(libexecdir)" ; then \
$(ECHO) " find $(DESTDIR)$(libexecdir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(datadir)" ; then \
if test "x$(DESTDIR)$(prefix)/share" != "x$(DESTDIR)$(datadir)" ; then \
$(ECHO) " find $(DESTDIR)$(prefix)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(libdir)" ; then \
if test "x$(DESTDIR)$(exec_prefix)/lib" != "x$(DESTDIR)$(libdir)" ; then \
$(ECHO) " find $(DESTDIR)$(libdir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(mandir)" ; then \
if test "x$(DESTDIR)$(prefix)/man" != "x$(DESTDIR)$(mandir)" ; then \
$(ECHO) " find $(DESTDIR)$(mandir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
if test -d "$(DESTDIR)$(includedir)" ; then \
if test "x$(DESTDIR)$(prefix)/include" != "x$(DESTDIR)$(includedir)" ; then \
$(ECHO) " find $(DESTDIR)$(includedir)/. -type d -exec chmod go+x {} \;" ; \
fi ; \
fi ; \
$(ECHO) ; \
$(ECHO) " Do not presume the find example is all that is" ; \
$(ECHO) " needed. VERIFY THE PERMISSIONS." ; \
$(ECHO) "{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{" ; \
$(ECHO) ; \
fi ; \
touch install.$(host_triplet).log ; \
if test -w install.$(host_triplet).log ; then \
LC_ALL=C ; \
if test "x$USER" = "x" ; then \
USER="unknown" ; \
fi ; \
$(ECHO) "Installed BRL-CAD Release @BRLCAD_VERSION@ Build @CONFIG_DATE@ by ${USER} to $(DESTDIR)$(prefix) on `date`" >> install.$(host_triplet).log ; \
fi
# Print out an informative summary. As just about everything seems to
# end up calling the all-am hook, which in turns calls the all-local
@@ -390,50 +102,45 @@ install-data-local:
# to emphasize the achievement.
#
all-local:
@$(ECHO) "Done."
@$(ECHO)
@$(ECHO) "BRL-CAD Release @BRLCAD_VERSION@, Build @CONFIG_DATE@"
@$(ECHO)
@if test "x$(MAKECMDGOALS)" = "xall-am" -o "x$(.TARGETS)" = "xall-am" -o "x$(MAKECMDGOALS)" = "xfast" -o "x$(.TARGETS)" = "xfast" ; then \
$(ECHO) $(ECHO_N) "Elapsed compilation time: " ;\
@@ECHO@ "Done."
@@ECHO@
@@ECHO@ "BRL-CAD Release @BRLCAD_VERSION@, Build @CONFIG_DATE@"
@@ECHO@
@if test "x$(MAKECMDGOALS)" = "xall-am" -o "x$(.TARGETS)" = "xall-am" ; then \
@ECHO@ @ECHO_N@ "Elapsed compilation time: " ;\
sh $(top_srcdir)/sh/elapsed.sh `cat $(top_builddir)/include/brlcad_version.h | grep Compilation` ;\
$(ECHO) $(ECHO_N) "Elapsed time since configuration: " ;\
@ECHO@ @ECHO_N@ "Elapsed time since configuration: " ;\
sh $(top_srcdir)/sh/elapsed.sh @CONFIG_TIME@ ;\
$(ECHO) "---" ;\
$(ECHO) "Run 'make install' to begin installation into $(prefix)" ;\
$(ECHO) "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
@ECHO@ "---" ;\
@ECHO@ "Run 'make install' to begin installation into $(prefix)" ;\
@ECHO@ "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
elif test "x$(MAKECMDGOALS)" = "xinstall-am" -o "x$(.TARGETS)" = "xinstall-am" ; then \
$(ECHO) $(ECHO_N) "Elapsed installation time: " ;\
@ECHO@ @ECHO_N@ "Elapsed installation time: " ;\
sh $(top_srcdir)/sh/elapsed.sh `cat $(top_builddir)/include/brlcad_version.h | grep Compilation` ;\
$(ECHO) $(ECHO_N) "Elapsed time since configuration: " ;\
@ECHO@ @ECHO_N@ "Elapsed time since configuration: " ;\
sh $(top_srcdir)/sh/elapsed.sh @CONFIG_TIME@ ;\
$(ECHO) "---" ;\
$(ECHO) "Run 'make test' to run the BRL-CAD Test Suite" ;\
$(ECHO) "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
$(ECHO) ;\
@ECHO@ "---" ;\
@ECHO@ "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
@ECHO@ ;\
line1=" BRL-CAD @BRLCAD_VERSION@ is now installed into $(prefix)" ;\
line2=" Be sure to add $(prefix)/bin to your PATH" ;\
separator="`$(ECHO) $$line1 | tr '[a-zA-Z0-9.\-/ ]' '*'`" ;\
$(ECHO) "$${separator}****" ;\
$(ECHO) "$$line1" ;\
$(ECHO) "$$line2" ;\
$(ECHO) "$${separator}****" ;\
length="`@ECHO@ $(prefix)@BRLCAD_VERSION@ | wc -c`" ;\
length="`expr $$length + 34`" ;\
separator="" ;\
while test $$length -gt 0 ; do \
separator="$${separator}***" ;\
length="`expr $$length - 3`" ;\
done ;\
@ECHO@ "$$separator" ;\
@ECHO@ "$$line1" ;\
@ECHO@ "$$line2" ;\
@ECHO@ "$$separator" ;\
elif test "x$(MAKECMDGOALS)" = "x" -a "x$(.TARGETS)" = "x" ; then \
$(ECHO) $(ECHO_N) "Elapsed time: " ;\
@ECHO@ @ECHO_N@ "Elapsed time: " ;\
sh $(top_srcdir)/sh/elapsed.sh `cat $(top_builddir)/include/brlcad_version.h | grep Compilation` ;\
$(ECHO) $(ECHO_N) "Elapsed time since configuration: " ;\
@ECHO@ @ECHO_N@ "Elapsed time since configuration: " ;\
sh $(top_srcdir)/sh/elapsed.sh @CONFIG_TIME@ ;\
$(ECHO) "---" ;\
$(ECHO) "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
@ECHO@ "---" ;\
@ECHO@ "Run 'make benchmark' to run the BRL-CAD Benchmark Suite" ;\
fi
@$(ECHO)
include $(top_srcdir)/misc/Makefile.defs
# Local Variables:
# mode: Makefile
# tab-width: 8
# indent-tabs-mode: t
# End:
# ex: shiftwidth=8 tabstop=8
@@ECHO@
+13 -377
View File
@@ -1,385 +1,23 @@
-*- coding: utf-8 -*-
BRL-CAD Release Notes
=====================
Included below is the latest news pertaining to BRL-CAD releases. The
history or BRL-CAD prior to release 5.0 is covered in doc/history.txt,
see that file and the CVS log for more historic information. The
entire history of the project is available through CVS.
----------------------------------------------------------------------
--- 2006-02-XX Release 7.7.0 ---
----------------------------------------------------------------------
This release marks the one year anniversary of BRL-CAD being released
as Open Source software. Thank you to everyone for your support and
contributions.
* added manual page for benchmark tool - Sean Morrison
* fixed g-dxf export compatibility issue - John Anderson
* smoother sketch primitive spline drawing - Sean Morrison
* fixed read bug in giftorle - Sean Morrison
* fixed multiply referenced object illumination bug - Sean Morrison
* improved nmg tesselation support reliability - Sean Morrison
* new tpkg ttcp-style example application using libpkg - Sean Morrison
* new roots_example root solving sample application - Sean Morrison
* prevent several g-nmg segfaults during tesselation - Sean Morrison
* fixed brlman/awf `./"' unsupported or unknown issue - Sean Morrison
* new g_transfer in-memory geometry example program - Sean Morrison
* new reshoot program to reshoot rays & compare results - Lee Butler
* added support for -F framebuffer option to fb-bw - Sean Morrison
* reid mged command, recursively assign region IDs - Sean Morrison
* remat mged command, recursively assign a material ID - Sean Morrison
* get_regions mged command, list assembly regions - Sean Morrison
* extensive Windows build support enhancements - Bob Parker
* new Archer modeling and visualization tool - Bob Parker, Doug Howard
* raytracers use image size for default aspect ratio - Sean Morrison
* fixed benchmark sqrt of negative numbers error - Sean Morrison
* raytracer performance enhancements - Sean Morrison
see that file for more historic information.
----------------------------------------------------------------------
--- 2005-12-15 Release 7.6.6 ---
--- 2004-11-01 Release 7.1.0 ---
----------------------------------------------------------------------
Continuing with the newly added point collection and reverse modeling
techniques provide in the previous release, this iteration improves
upon that support fixing several issues and refining the modeling
techniques. Additionally, after more than a year of passively
researching and investigating, this release now accounts for the
majority of known contributors to BRL-CAD over the project's
existence. This is part of an on-going effort to document the history
of BRL-CAD over the past 20 years.
* improved mged resource searching when not installed - Sean Morrison
* significant AUTHORS file updates, all names filed - Sean Morrison
* fixed sketch primitive bezier path computation bug - Sean Morrison
* cleaned up erroneous rtedge end of line output - Sean Morrison
* configure --enable/disable-everything option - Sean Morrison
* updated g_qa manual page documentation - Lee Butler
* early termination grid spacing limit bug in g_qa fixed - Lee Butler
* fixed Jove sandbox installation issue - Sean Morrison
* fixed adrt/isst client crash bug - Mike Caruso, Razak Arunaugun
* fixed modified env(PATH) startup issue in mged - Sean Morrison
* fixed benchmark tool default resource location bug - Sean Morrison
* added another text alignment handler to dxf-g - John Anderson
* clamped integer value printing of primitives in mged - Sean Morrison
* removed gratuitous nmg debug printing from mged - Sean Morrison
* fixed grouping bug, mged point importer - Jason Owens, Sean Morrison
* improved mged point import support - Lee Butler, Sean Morrison
* fixed bug in plate orientation of mged point importer - Lee Butler
----------------------------------------------------------------------
--- 2005-11-12 Release 7.6.4 ---
----------------------------------------------------------------------
This release adds a new geometry creation interface to mged that
supports reverse modeling geometry of existing objects. New geometry
creation commands read point data sets in a simple text file format,
recognizing categories and collections of points. Using
point-acquisition devices such as X-Station Vulcan advanced surveying
systems from Arc Second Inc., points may be collected and used in mged
to factilitate the generation of geometry models. Collection
techniques are recognized for polygonal plates, cylinders, spheres,
point clouds, and more.
* auto-locate mged external apps regardless of PATH - Sean Morrison
* mged utilizes a local display if unspecified/unset - Sean Morrison
* set default mged Escape key binding to reject - Sean Morrison
* fixed 'benchmark' tool resource searching - Sean Morrison
* added -u option to mged "make_bb" to allow air - Lee Butler
* fixed IBM AIX compiler support issues - Sean Morrison
* head/tail -n usage posix compliance - Stefan Fiedler, Sean Morrison
* fixed jove compilation issues - Sean Morrison, Daniel Remenak
* fixed conversion bug in the dxf-g converter - John Anderson
* point parsing/import interface to mged - Sean Morrison, Lee Butler
* fixed bug in export of NMG primitives - John Anderson
* fixed itcl configuration issue - Stefan Fiedler, Sean Morrison
* fixed g_qa tolerance option parsing inconsistency - Sean Morrison
* improved mged 'tol' command tolerance value checks - Sean Morrison
* fixed tgc absolute tesselation tolerance issue - Sean Morrison
* optional build support checks for X11 and OpenGL - Sean Morrison
* improved Windows build support - Bob Parker, Daniel Ro§berg
* isst observer 2x screen magnification - Justin Shumaker
* added los and material name support to librtserver - John Anderson
* improved 64bit support for ADRT - Justin Shumaker
* updated manual page documentation - Sean Morrison
* added support for text handling to dxf-g - John Anderson
----------------------------------------------------------------------
--- 2005-09-29 Release 7.6.2 ---
----------------------------------------------------------------------
In order to resolve an integration issue with the MUVES-S2
vulnerability analysis code, this special release of BRL-CAD was put
together providing updated tclscripts that work correctly when
embedded into MUVES-S2. This release also facilitates BRL-CAD's
integration with AJEM as well for their corresponding release.
* fixed 'embedded mged' tclscript files - Karen Murray, Sean Morrison
----------------------------------------------------------------------
--- 2005-09-08 Release 7.6.0 ---
----------------------------------------------------------------------
This release includes the addition of a new geometry "Quantitative
Analysis" tool called g_qa. This tool is a new tool that combines
some of the features of rtweight, rtcheck and g_lint, providing a
robust means for computing the weight and volume of objects while also
allowing a means to report overlaps, air gaps, external air regions,
bounding box dimensions, and more.
* configuration build fixes for Tk/Iwidgets - Michal Slonina
* fixed bug in mged overlay command handling of EOF - Lee Butler
* renamed g-wave converter to g-obj - Sean Morrison
* mged will now work without being installed - Sean Morrison
* improved ADRT build support - Sean Morrison
* improved build support detection for OpenGL and X11 - Sean Morrison
* performance enhancements to ADRT - Justin Shumaker
* enabled SGI knobs and button box support for IRIX - Sean Morrison
* fixed mged startup resource bug - Enrique Perez-Terron
* Enhancements to g_qa for stability and performance. - Lee Butler
* 'make test' now runs against an uninstalled build tree - Lee Butler
* new nightly regression test framework - Lee Butler
* g_qa now has option to report interfaces/connections - Lee Butler
* mged relocation support - Sean Morrison
* Doxygen changes to source code comments - Lee Butler, Sean Duvall
----------------------------------------------------------------------
--- 2005-08-10 Release 7.4.2 ---
----------------------------------------------------------------------
Continuing with the impressive ADRT tool suite being provided by
Justin Shumaker is the addition of the Interactive Shot Selection Tool
(ISST). Using ISST, you can spin large facetized models around in
real-time, slice through them with rays, and examine the geometric
components along a given path. The tool will take advantage of
clusters and SMP hardware similar to RISE, providing a master job
manager, a slave compute daemon for network distributed processing,
and a client for interacting with and viewing the models.
* fixed ray-trace unique hits evaluation bug - John Anderson
* added manual page for remapid - John Anderson
* fixed quick memory debugging bug - Jim Hunt
* improved brlman relocation - Sean Morrison
* added g_qa geometry quality analysis tool (beta) - Lee Butler
* added adrt interactive shot selection tool - Justin Shumaker
* simultaneous -o and -F options to rt, rtedge, rtxray - Sean Morrison
----------------------------------------------------------------------
--- 2005-07-12 Release 7.4.0 ---
----------------------------------------------------------------------
This update includes several enhancements and new additions including
the impressive addition of the Realistic Image Synthesis Engine (RISE)
path-tracer. RISE is part of the Advanced Distributed Ray-Trace
(ADRT) tool and library suite, which provides a high-performance
triangle ray-trace engine. This engine serves as the basis for
several tools, RISE being the first toolset to be released. This
toolset includes a master job manager, a slave compute daemon for
network distributed processing, and a client for observing job
progress.
Driven by user requests, the 'rtarea' command now reports signifcantly
more information than before including area details for all assemblies
and regions being rendered. Both the presented and exposed areas are
now computed too, including details on how many regions/assemblies are
hit. The exposed area is the potentially occluded 2D projection
whereas the presented area is calculated without consideration for
occlusions. That is to say that if an object is in front covering a
regions or assemblies from a particular view, the exposed area of the
covered geometry would be reduced but the presented area would not.
The rtarea command was added to mged as well, along with rtweight.
* improved mged initialization failure reporting - Sean Morrison
* applied zlib vulnerability patch (CAN-2005-2096) - Sean Morrison
* added the adrt rise path-tracer - Justin Shumaker
* increased mged shadow ray selection max to 64 - Sean Morrison
* added rtarea and rtweight commands to mged - Sean Morrison
* added sorting and hierarchy support to rtarea - Sean Morrison
* rewrote rtarea for region and assemblies support - Sean Morrison
* fixed .density file parser bug in rtweight - Daniel Rossberg
* improve detection and handling of cyclic geometry - Sean Morrison
* 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 cmd (combine 2 bots into 1) - Lee Butler
----------------------------------------------------------------------
--- 2005-06-07 Release 7.2.6 ---
----------------------------------------------------------------------
Additional modifications were made to the benchmark suite including
the addition of iterative frames that compare the stability of the
performance results being observed. The benchmark will continue to
render frames of a designated time-complexity until the numbers are
either stable or a maximum time window is reached. The benchmark
output now describes what the results mean and provides reference
numbers for comparison. The benchmark suite is also now included in
the default installation as a command-line tool named 'benchmark'.
In conjunction with the benchmark suite's requirements, some example
geometry databases are now provided as part of the default install as
are the corresponding reference benchmark images and logs. They are
intended to provide new users with sample geometry models to work
with; and custom configurations may disable the installation of the
additional geometry databases if so desired.
* documented the rtcheck -g and -G options - Sean Morrison
* fixed units bug in mged typein of bot and arbn - Daniel Ro§berg
* added -W option to raytracers for white background - Sean Morrison
* synchronized mged startup message with gui creation - Sean Morrison
* added -f option to mged to prevent backgrounding - Sean Morrison
* install example geometry databases - Sean Morrison
* added 'benchmark' tool and install benchmark suite - Sean Morrison
* improved installation instructions - Sean Morrison
* fixed various typos in top level documents - Chuck Kennedy
* added summary and explanation of benchmark results - Sean Morrison
* fixed dimension conversion bug in dxf-g - John Anderson
* added deviation stability checks to benchmark suite - Sean Morrison
----------------------------------------------------------------------
--- 2005-05-11 Release 7.2.4 ---
----------------------------------------------------------------------
The release marks the beginning of a series of benchmark suite
enhancements. The benchmark suite will now iteratively increase the
number of rays being shot until a minimum amount of time has elapsed
per render. The resulting computations provide a more stable
ray-trace figure of merit (rtfm) and allows the benchmark tests to
scale more effectively to increasingly higher-performance machines
without requiring intervention. The current default testing time
window minimum of 60 seconds elapsed wallclock time implies that the
benchmark suite will now take about 15 minutes to complete.
* fixed libbu run-time memory corruption checking - Sean Morrison
* prevent indirect OpenGL framebuffers from crashing - Sean Morrison
* throttle cpu usage on lingering OpenGL framebuffers - Sean Morrison
* uniform binary objects from partial file data - Sean morrison
* added libwdb interface to uniform binary objects - Sean Morrison
* fixed mged help for whichid, whatid, and whichair - Sean Morrison
* fixed dsp primitive bug when using binary objects - Sean Morrison
* fixed tabsub 64bit filesystem file read bug - Sean Morrison
* vrml-g now writes out DEF names for exported shapes - Sean Morrison
* updated manual pages with new contact details - Sean Morrison
* iterative scalable benchmark computations - Sean Morrison
* added logging of ray details when root solver fails - Sean Morrison
* added logging of solid name when root solver fails - Lee Butler
* build now includes a termlib library - Sean Morrison
* fixed smp linux rtarea calculation bug - Sean Morrison
* fixed rtweight centimeter units computation bug - Lee Butler
* fixed asc2g double-free warnings bug - Sean Morrison
* added rtarea manpage documentation - Sean Morrison
* fixed compilation support for Solaris - Sean Morrison
* removed redirection usage examples in g2asc docs - Sean Morrison
----------------------------------------------------------------------
--- 2005-04-03 Release 7.2.2 ---
----------------------------------------------------------------------
* fixed rtedge/rtwizard background render failure bug - Sean Morrison
* fixed rttherm previous results interference bug - Sean Morrison
* fixed aborted benchmark summary bug - Sean Morrison
* renamed the irprep 'display' tool to 'showtherm' - Sean Morrison
* quelled XInputExtension warning on mged startup - Sean Morrison
* fixed non-square window mged illumination selection - Sean Morrison
----------------------------------------------------------------------
--- 2005-03-05 Release 7.2.0 ---
----------------------------------------------------------------------
* fixed libpng link bug on Irix64bit - Lee Butler
* fixed locale build bug - Thierry Thomas & Pedro Giffuni
* fixed g-iges stdout header bug - Manfred Spraul
* fixed minimal BoT disappearance bug - Lee Butler
* Sketch Editor now starts with an empty sketch - Sean Morrison
* fixed need for brlcad_root on default configure - Sean Morrison
* update to zlib 1.2.2 - Sean Morrison
----------------------------------------------------------------------
--- 2005-01-25 Release 7.0.4 ---
----------------------------------------------------------------------
This patch release update fixes several build issues experienced on
various platforms including Gentoo, Debian, and Mac OS X.
* provided libutahrle (urt) vulnerability patch - Pedro Giffuni
* fixed missing vgr results when missing dc - Sean Morrison
* update of Utah Raster Toolkit from 3.0 to 3.1b1 - Sean Morrison
* update of libpng from 1.2.5 to 1.2.8 - Sean Morrison
* gentoo build fixes - Cliff Yapp
----------------------------------------------------------------------
--- 2005-01-07 Release 7.0.2 ---
----------------------------------------------------------------------
This release marks the first source and binary distribution of BRL-CAD
as an Open Source project. With the exception of a few minor bug
fixes, the majority of changes made available through this release
that separate it from 7.0.0 are source code style adoptions and
clarifications of the developer documentation. All files have adopted
an emacs/vi local variables block for style conformance and the source
code headers are modified to denote the new distribution and copyright
status of the project.
----------------------------------------------------------------------
--- 2004-12-21 Release 7.0.1 ---
----------------------------------------------------------------------
While with the new release numbering scheme it will be rare to see a
release with an odd minor patch number, in many ways this is a major
BRL-CAD release with the package entering the realm of Open Source
software. Likewise, the project moves a new public website as well as
adopts a SourceForge project site. With the migration of the project
to SourceForge, new forums, mailing lists, bug tracking, feature
requests, support mechanisms, task management, and news announcement
channels all become instantly available.
OPEN SOURCE
This marks the first release of BRL-CAD as Open Source software. It
has taken several years and much hard work by many people to actually
make this happen. Special thanks goes out to the U.S. Army Research
Laboratory for giving back to the community by allowing BRL-CAD to be
released as Open Source software under the Open Source Initiative
(OSI) approved NASA Open Source Agreement (NOSA). The "release"
solely exists in CVS -- binary and source distributions will remain
unprepared.
The majority of BRL-CAD is covered by the GNU General Public License.
The BRL-CAD libraries (src/lib*) are all provided under the GNU Lesser
General Public License. The documentation is provided under the terms
of the GNU Free Documentation License. The build infrastructure and
supporting scripts are covered by the Berkeley Software Distribution
license or are in the public domain. Given the vast size, complexity,
and varied usage needs of BRL-CAD's source code and supporting data,
all of the aforementioned licenses allow for a greater degree of
flexibility in how they may be used.
See the individual files in question and the COPYING file for more
details. The licenses are intended to foster and encourage
improvements to BRL-CAD and the Open Source community as a whole
without taking away from the package's heritage and history. See the
COPYING file for more details and information.
----------------------------------------------------------------------
--- 2004-11-01 Release 7.0.0 ---
----------------------------------------------------------------------
BRL-CAD's source code has undergone major restructuring with a
complete replacement of the build system and conversion of the sources
toward standards compliance.
complete replacement of the build sytem and conversion of the sources
towards standards compliance.
SOURCES REORGANIZED
@@ -425,7 +63,7 @@ g-nff converter for exporting to the NFF file format. There is
experimental initial support for a new super ellipsoid primitive type
for advanced curvature shapes. There are a few new procedural
database generators including one for creating geometry of an image as
well as generic vegetation.
well as generic vegitation.
WINDOWS SUPPORT
@@ -434,7 +72,7 @@ This release marks the first release with initial support for the
Windows operating system platform. All of the core BRL-CAD libraries
as well as several tools (including mged, rt, nirt, asc2g, and more)
have completed the conversion. While not yet a holistic port, all of
the libraries and the core utilities have been ported and the rest will
the libraries and the core utilites have been ported and the rest will
soon follow.
@@ -462,14 +100,14 @@ This is probably the most significant change in this release. It
introduces a large number of new capabilities in BRL-CAD, including:
* Machine-Independent Data
The geometry in the new file format is stored in an
architecture-independent fashion. This removes the need to convert
the geometry file to ASCII representation and back to binary when
moving between machines of different architectures (e.g., between
Big-Endian and Little-Endian machines).
* Unlimited-Length Object Names
* Unlimited-Length Object Names
Names of objects in the geometry database were previously limited to
16 characters. This restriction was burdensome when constructing
@@ -567,7 +205,7 @@ there have been numerous improvements. These include:
These allows user to automatically generate more complex primitives
from existing ones. For example, rcc-cap creates an ellipsoidal top
for a right circular cylinder. The list of accelerators includes:
for a right circular cylinder. The list of accellerators includes:
rcc-blend, rcc-cap, rcc-tgc, rpp-arch, rpp-cap, rpp-arch, tor-rcc,
and sph-part.
@@ -669,7 +307,7 @@ OTHER ENHANCEMENTS
achieve a substantial speedup during raytracing.
* ASCII Representation for ebm and vol Primitives
These two primitives did not have an ASCII representation in
previous releases. This omission has been corrected.
@@ -763,11 +401,11 @@ DEPRECATED FEATURES
remove the ability to run g2asc and asc2g on streaming data.
SPECIAL ACKNOWLEDGMENT
SPECIAL ACKNOWLEGEMENT
This release is the last to introduce new features developed by Mike
Muuss. Mike embodied a unique blend of unparalleled intellect,
unquenchable curiosity, and unending enthusiasm to advance the
unquenchable cur iosity, and unending enthusiasm to advance the
capabilities and performance of everything and everyone he touched. He
was the original architect of BRL-CAD and for 20 years guided its
development and emergence as one of the most advanced physically based
@@ -852,7 +490,7 @@ NEW UTILITIES
There is new conversion tools available now for converting BRL-CAD to
ACAD (General Dynamics) for XPATCH, Alias|Wavefront, Compaq (Digital
Equipment) OFF, and VRML. Likewise, there are tools for converting
Cyberware digitization, NASTRAN, and 3D systems stereolithography
Cyberware digitizations, NASTRAN, and 3D systems stereolithography
(stl) formats into BRL-CAD geometry.
Using the g_diff command, you can compare .g files and report
@@ -954,5 +592,3 @@ further, and thus may not be present in subsequent releases.
See doc/history.txt for more historic information on BRL-CAD. There
is contained information on releases that predate 1999 and the 5.0
release.
NEWS items should be formated to column 70 (M-q in emacs), no tabs
+56 -212
View File
@@ -1,70 +1,35 @@
BRL-CAD
Release 7.8.0
Release 7.1.0
http://brlcad.org/
BRL-CAD is a powerful Combinatorial/Constructive Solid Geometry (CSG)
solid modeling system that includes an interactive geometry editor,
ray-tracing support for rendering and geometric analysis,
network-distributed framebuffer support, image and signal-processing
tools, realistic image synthesis path-tracing, a benchmark performance
analysis suite, and an embedded scripting language.
The package is a collection of over 400 tools and utilities across
over 750,000 lines of source code. Included is support for various
geometric data format conversions, image and signal processing
capabilities, sophisticated ray-tracing based lighting models, network
distributed ray-tracing, massively parallel ray-tracing,
high-performance path-tracing, animation capabilities, data
compression, image handling, and interactive 3-D geometric editing.
Included is an implementation of Weiler's n-Manifold Geometry (NMG)
data structures for surface-based solid models and photon mapping.
Since 1979, the U.S. Army Research Laboratory has been developing and
distributing the BRL-CAD solid modeling package for a wide range of
military and industrial applications. The package is primarily used
for the design and analysis of vehicles, mechanical parts,
architecture, and various signature analysis work. BRL-CAD is also used in
radiation dose planning and education where it's used to to aid
teaching fundamental computer graphics and CSG modeling concepts to
primary, secondary, and higher education students.
BRL-CAD was released as open source in December 2004 with portions
licensed under the GPL, LGPL, GFDL, and BSD license. See the COPYING
file for more details.
BRL-CAD is a comprehensive solid modeling system based on the
Combinatorial/Constructive Solid Geometry (CSG) technique. The
package is Primarily used for design and analysis of vehicles,
mechanical parts, and architecture. Also used in radiation dose
planning and education.
The distribution includes an interactive 3-D geometry editor,
ray-tracing library, sophisticated ray-tracing based lighting models,
a network-distributed ray-tracer, animation capabilities, a
network-distributed image-processing capability, image-handling, and
data-compression utilities. Also included is an implementation of
Weiler's n-Manifold Geometry (NMG) data structures for surface-based
solid models and photon mapping.
CONTENTS
--------
Introduction
Contents
Getting Started
Compile and Install
Benchmark
Communication
Bug Reports/Feature Requests
Distribution Details
Background Material
Future Events
Getting Help
GETTING STARTED
----------------
This README file exists only to provide you a brief roadmap to the
contents of the BRL-CAD distribution.
contents of the BRL-CAD distribution.
The information on how to install and operate the software, to become
involved with the development of the package, or to run the benchmark
performance test suite have each become sufficiently large that their
details are covered in more detail in standalone documents. For more
details on what BRL-CAD provides, see the documentation provided on
the website at http://brlcad.org/.
Information relevant to those interested in the source code is
contained in the HACKING and COPYING files. See doc/benchmark.tr file
for benchmark suite information. There is a variety of other
documentation and information also available in the doc/ directory.
the website. Information relevant to those interested in the source
code is contained in the HACKING and COPYING files. See
doc/benchmark.tr file for benchmark suite information. There is a
variety of other information also available in the doc/ directory.
Please note that this distribution package does not include the
various military-specific model analysis tools such as MUVES, GIFT,
@@ -72,137 +37,39 @@ SAR, SLAVE, VAST, etc., nor does it include any military geometry
databases. If you desire to have access to this material, please
contact one of the BRL-CAD developers.
INSTALLATION
COMPILE AND INSTALL
-------------------
See the INSTALL file for details on configuring, compiling, and
installing BRL-CAD. In order to compile and install BRL-CAD from a
source distribution, the following steps may be taken for a full
default install:
./configure
make
make install
If you do not have a configure script in your source tree (at the same
level as this README file), you will need a relatively up-to-date
version of the GNU Build System (autoconf, automake, & libtool)
installed. The autogen.sh script will need to be run successfully in
order to generate the configure script first:
sh autogen.sh
./configure
make
make install
There are various options available to both configure and make. Run
"./configure --help" for a list of available configuration options.
Users on multiprocessor systems will be able to speed up their builds
by passing the -j option to make (e.g. make -j4, assuming GNU make).
Once the build completes and assuming you have proper filesystem
permissions, you should be able to begin the installation by running
the "make install" . By default, the package is configured to install
entirely into /usr/brlcad/.
You will need to add /usr/brlcad/bin to your path (or whatever was
used as a --prefix during configure) in order for the BRL-CAD binaries
to be in your path.
./autogen.sh
./configure
make
make install
BENCHMARK
---------
After the build successfully completes, you will be able to verify
basic functionality by running the BRL-CAD Benchmark. Running the
benchmark suite is integrated into the build system such that any time
after configure, you may run:
See the paper in doc/benchmark.doc for information on analyzing the
results of the benchmark tests. Comparisons between various different
computers are listed.
make benchmark
If the build is successful, you will see "CORRECT" numbers and a
performance summary at the end. The "vgr" line effectively shows you
approximately how much faster your machine is to a VAX 11/780. After
installing BRL-CAD, you may run the 'benchmark' tool as well to run
the BRL-CAD Benchmark.
See the paper in doc/benchmark.tr for information on analyzing and
comparing the results of the benchmark tests in more detail.
COMMUNICATION
-------------
You are invited to participate in the InterNet (aka "ARPANET")
electronic mailing list on the BRL-CAD software. There are various
BRL-CAD mailing lists available on the project website at
http://sourceforge.net/mail/?group_id=105292 including three
developer-oriented lists, a user list, and a read-only news
announcement list. See the posted archives to get a feel for the
volume of list traffic for each list and to read/search past
discussions.
On-line web forums are likewise available on the project site at
http://sourceforge.net/forum/?group_id=105292
A variety of information on BRL-CAD is available via the
World-Wide-Web. Papers, documentation, and the software repository
may be found at:
http://brlcad.org
In addition to the above, there is an official BRL-CAD IRC channel on
the Freenode network that may be reached by joining #brlcad on
irc.freenode.net connecting via port 6667. For first-time users,
there is a web-based IRC client available for certain browsers at:
http://irc.brlcad.org
IRC is the preferred method of communication to interact with the
BRL-CAD developers, to get involved with the project, obtain support,
or provide direct feedback.
BUG REPORTS AND FEATURE REQUESTS
--------------------------------
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
request to http://sourceforge.net/tracker/?group_id=105292&atid=640805
and http://sourceforge.net/tracker/?group_id=105292&atid=640803
respectively.
BACKGROUND MATERIAL
For overview information on the whole package, consult the overview
paper in the filepapers/overview, and the brlcad(1) manual page in the
file util/brlcad.1. For a discussion of the significance of this
software, read the paper "Understanding the Preparation and Analysis
of Solid Models".
DISTRIBUTION DETAILS
--------------------
BRL-CAD is freely available and distributed in both binary and source
code form through the BRL-CAD project website on Sourceforge:
http://sf.net/projects/brlcad/
The package is similarly available via the Concurrent Versions System
(CVS) software version control repository. To obtain the latest,
follow the directions for anonymous checkout at:
http://sourceforge.net/cvs/?group_id=105292
There is also a paid-for full-service support distribution available
for those interested through the Survivability/Vulnerability
Information Analysis Center (SURVIAC).
SURVIAC administers the supported BRL-CAD distributions and
information exchange programs for the U.S. Army Research Laboratory.
Full service distributions include a copy of the full distribution
materials on your choice of magnetic or tape media. One printed set
of BRL-CAD documentation will be mailed to you. Software upgrades
will also be provided at no additional charge, and you will have
access to full technical assistance by phone, FAX, letter, or E-mail.
Agencies of the Federal Government may acquire the full service
distribution with a simple MIPR or OGA funds transfer.
Full service distribution: The Survivability/Vulnerability Information
Analysis Center (SURVIAC) administers the supported BRL-CAD
distributions and information exchange programs for ARL. Full service
distributions a copy of the full distribution materials on your choice
of magnetic tape media, or you may elect to obtain your copy via FTP.
One printed set of BRL-CAD documentation will be mailed to you.
Software upgrades will be provided at no additional charge, and you
will have access to full technical assistance by phone, FAX, letter,
or E-mail. Agencies of the Federal Government may acquire the full
service distribution with a simple MIPR or OGA funds transfer.
For further details, contact:
@@ -215,49 +82,26 @@ or call USA telephone (410) 273-7794, send E-mail to
<cad-dist@arl.army.mil>, FAX your letter to USA (410) 272-6763, or
write to the above address.
COMMUNICATION
BACKGROUND MATERIAL
-------------------
You are invited to participate in the InterNet (aka "ARPANET")
electronic mailing list on the BRL-CAD software, which is called
<brlcad-users@lists.sourceforge.net>. If you are a developer, there
is also a separate list called <brlcad-devel@lists.sourceforge.net>.
Bug reports and discussions of new features are the main topics; the
volume of messages fluctuates over time.
For overview information on the whole package, consult the website at
http://brlcad.org/ and the brlcad(1) manual page in the file
src/util/brlcad.1. For a discussion of the significance of this
software, read the paper "Understanding the Preparation and Analysis
of Solid Models".
A variety of information on BRL-CAD is available via the
World-Wide-Web. Papers, documentation, and the software repository
may be found at:
http://brlcad.org
FUTURE EVENTS
-------------
It is expected that new releases of BRL-CAD will be issued
approximately once a month. A new release is scheduled for
distribution at the beginning of every month, usually being posted
sometime within the first week of every month.
Depending on need, demand, and activity, additional releases may also
be made. The additional releases will be heavily dependant upon the
level of user involvement and contributions in particular.
Information about new releases will be routinely provided by
electronic mail to recipients of this software as well as to the
BRL-CAD NEWS mailing list:
http://sourceforge.net/mail/?group_id=105292
Periodically, training and user group meetings are provided with
announcements similarly posted to the BRL-CAD NEWS mailing list.
Several BRL-CAD developers also regularly attend the ACM Siggraph
conference, the ACM Solid and Physical Modeling conference, and other
similar conferences, conventions, and symposiums as well.
GETTING HELP
------------
Feel free to direct any unanswered questions relating to BRL-CAD via
e-mail to 'devs@brlcad.org' or to any of the other contact means
described above in the communications section of this document.
It is expected that new releases of this software will be issued
between once and twice a year. Information about new releases will be
routinely provided by electronic mail to recipients of this software.
Best Wishes,
The BRL-CAD Development Team
devs@brlcad.org
+34 -139
View File
@@ -1,173 +1,68 @@
BRL-CAD to do list
==================
Included below is a list of things that are scheduled or desirable to
be done at some point. Most recently added items are on top, older
topics are on the bottom. This is not an official list, it's more a
scratch pad for the developers to use for tracking development ideas
and informal plans.
Included below is a list of things that are scheduled or desireable to
be done at some point. More important, easy, and most recently added
items are on top, older topics are on the bottom.
The items listed for release should not ever hinder, stop, or
otherwise delay a release from being made. The items listed are
merely to give an estimate of what was expected to be done. See the
project task tracker for more to do items and future planning efforts.
http://sf.net/pm/?group_id=105292
THESE SHOULD HAPPEN BEFORE SOURCEFORGE UPLOAD
* write up initial README
* remove license speak for an immediate preliminary release
THESE SHOULD HAPPEN BEFORE THE NEXT RELEASE
-------------------------------------------
* restore functionality to tests and benchmark
* modify file headers to add license info
* Update libpng to address CERT Technical Cyber Security Alert
TA04-217A
http://www.us-cert.gov/cas/techalerts/TA04-217A.html
THESE SHOULD HAPPEN WITHIN TWO RELEASE ITERATIONS
-------------------------------------------------
* get archer working
* clone and tracker
* ensure successful build on mingw
* Mac OS X SGI dial knobs support
* add geometry examples for toy jeep and building
* test pic/nonpic build problems with librtms/libmultispectral
* run-time path identification of mged resources was never completed,
complete it.
* use environ for run-time path tracing lookups
* add support to restore the backups when an autogen.sh step aborts
* support variable overrides for autogen.sh
THESE ARE LOWER PRIORITY OR FOR FUTURE RELEASES
-----------------------------------------------
* short introductory documentation on using various BRL-CAD command
line tools such as rt, mged, nirt, fbserv, converters, etc.
* short introductory documentation on using mged, covering a majority
of the various commands.
* reference sheet of useful BRL-CAD command-line tools grouped
categorically.
* reference sheet of common mged commands, keybindings, gui elements
and scripting facilities.
* support to the raytracers for multiple image file formats,
recognizing an option and/or the file suffix of the -o filename.
* libfb + font rendering (perhaps through libbn's plot interface) for
a posix terminal.
* gpgpu for enhanced performance boolweave sorting
* getexecname, "/proc/self/cmdline", program_invocation_short_name.
separate out into new file.
* write an introduction to brl-cad document that overviews the primary
tools and how they can be used together.
* test out -Wfloat-equal
* geometry viewing commands/visualizations of exploded levels
* add command line help options to 'benchmark' tool
* default mged text editor invokes ed, should invoke jove or system
gui editor like TextEdit on OS X if it's known.
* mirror around an arbitrary plane (maybe point+vector) in mged
* mirror around point/distance along axis operation in mged
* librt-based path tracer
* system identifier application with sysctl-style information
database, with some back-end functionality placed into libbu.
* write scripts that parse the sf.net tracker data and generate
automatic reports for release.
* add callback data parameters to libpkg hook functions
* test intel compiler performance on Altix, add performance options
* pix-png should make sure output is not to a terminal
* investigate performance impact of using sched_setaffinity and/or
pthread_attr_setaffinity_np for linux threading affinity in librt.
* rtedge-style tracer that outputs tool paths (splines/segments, etc)
for CNC/CAM style toolpath cutting descriptions (g-code files).
* rt annotation support
* support for fillets and chamfers as object/combination operations
* M-x indent-region scripts
* provide installation and post configuration support scripts
* make the DSP primitive use less memory when data is coming from
a binunif. allocating 160 times binunif size is a bit extravagant
(which comes from sizeof(struct dsp_bb)).
* add dynamic geometry support. i.e. the ability to modify the parsed
in-memory geometry tree on the fly via api calls (e.g. to add holes)
* convert the documentation to docbook and integrate their generation
with the build system.
* investigate why g-iges followed by iges-g on a single box results in
permuted vertex lists
* fix reference to a "Create Solid" submenu on pdf page 18 (page 6) of
volume II
* ensure successful build on windows
* write up the history of brlcad
* revise cvs policy document to reflect desired and practical public
use
* ensure successful build on solaris with gcc and sunwpro compiler
* handle multiple threading models (irix) via configure
* obliterate compilation warnings
* clean up code comments, add more of them, and doxygenify them
(minimally, use /** */ in major comment blocks)
* add checks for system libs and optionally build our libs only if
they don't have suitable system libs (namely, libtcl)
THESE ARE LOWER PRIORITY
* add support for subgeometry support to the geometry syndicator
* add xml, nff, bzw, pov, blend geometry import and export support
* add xml geometry import and export support
* add support for filesystem-based geometry collections
* add support for levels of detail
* make benchmarks scale over time by performing multi-resolution
raytrace iterations of increasing size
ODDITIES
--------
* the scale structure in bn_cmd_noise_slice (bn_tcl.c) was never
initialized. it looks like somebody has planned to extend the
function but never carried out
* add nfs support and ability to safely interrupt benchmark
THESE BREAK PROTOCOL OR ARE BACKWARDS-INCOMPATIBLE
--------------------------------------------------
* support for features either as primitives or operations or both
e.g. chamfer, fillet, round, etc
THESE BREAK PROTOCOL AND ARE BACKWARDS INCOMPATIBLE
* fix the database I/O writing to properly support the addition of new
primitive types. this includes modifying the major/minor code or
combinations/regions and binary objects
* add database support for constraints, expressions, parametric
values, construction history, and timestamping.
---
See the project task tracker for more to do items and future planning
efforts. http://sf.net/pm/?group_id=105292
TODO items should be formated to column 70 (M-q in emacs), no tabs
+202 -683
View File
File diff suppressed because it is too large Load Diff
+1 -2
View File
@@ -2,5 +2,4 @@
*.log.*
*.pix
*.pix.*
benchmark
pixcmp
.cvsignore
+6 -29
View File
@@ -4,38 +4,15 @@ bin_PROGRAMS = pixcmp
pixcmp_SOURCES = pixcmp.c
clobber:
@$(ECHO) "About to wipe out all pictures and binary files in this directory"
@$(ECHO) "Send SIGINT (type ^C) within 3 seconds to abort"
@echo "About to wipe out all pictures and binary files in this directory"
@echo "Send SIGINT (typ. ^C) within 3 seconds to abort"
@sleep 3
rm -f *.log.* *.pix.* # old versions
rm -f *.log *.pix # last try
dist_bin_SCRIPTS = \
benchmark
EXTRA_DIST = lgt.sh perf.sh pretty.sh recheck.sh run.sh try.sh
man_MANS = \
benchmark.1
EXTRA_DIST = \
$(man_MANS) \
${dist_bin_SCRIPTS} \
lgt.sh \
run.sh \
try.sh \
viewdiff.sh
benchmark: run.sh
cp $(top_srcdir)/bench/run.sh benchmark
.PHONY : run bench
run: all
${SH} run.sh
bench: run
CLEANFILES = \
benchmark
include $(top_srcdir)/misc/Makefile.defs
benchmark: all
sh run.sh
bench: benchmark
-130
View File
@@ -1,130 +0,0 @@
.TH BENCHMARK 1 BRL-CAD
.\" B E N C H M A R K . 1
.\" BRL-CAD
.\"
.\" Copyright (c) 2006 United States Government as represented by
.\" the U.S. Army Research Laboratory.
.\"
.\" This document is made available under the terms of the GNU Free
.\" Documentation License or, at your option, under the terms of the
.\" GNU General Public License as published by the Free Software
.\" Foundation. Permission is granted to copy, distribute and/or
.\" modify this document under the terms of the GNU Free Documentation
.\" License, Version 1.2 or any later version published by the Free
.\" Software Foundation; with no Invariant Sections, no Front-Cover
.\" Texts, and no Back-Cover Texts. Permission is also granted to
.\" redistribute this document under the terms of the GNU General
.\" Public License; either version 2 of the License, or (at your
.\" option) any later version.
.\"
.\" You should have received a copy of the GNU Free Documentation
.\" License and/or the GNU General Public License along with this
.\" document; see the file named COPYING for more information.
.\"
.\".\".\"
.SH NAME
benchmark \- runs the BRL-CAD benchmark
.SH SYNOPSIS
.B benchmark
.SH DESCRIPTION
.PP
The benchmark suite will test the performance of a given system by
iteratively rendering several well-known datasets into 512x512 images
where performance metrics are documented and fairly well understood.
The local machine's performance is compared to the base system (called
VGR) and a numeric "VGR" mulitplier of performance is computed. This
number is a simplified metric from which one may qualitatively compare
cpu and cache performance, versions of BRL-CAD, and different compiler
characteristics.
.PP
There are several environment variables that will modify how the
BRL-CAD benchmark behaves so that it may be run in a stand-alone
environment:
.PP
\&
.B RT
\- the rt binary (e.g. ../src/rt/rt or /usr/brlcad/bin/rt)
.br
\&
.B DB
\- the directory containing the reference geometry (e.g. ../db)
.br
\&
.B PIX
\- the directory containing the reference images (e.g. ../pix)
.br
\&
.B LOG
\- the directory containing the reference logs (e.g. ../pix)
.br
\&
.B CMP
\- the name of a pixcmp tool (e.g. ./pixcmp)
.br
\&
.B ELP
\- the name of an elapsed time tool (e.g. ../sh/elapsed.sh)
.br
\&
.B TIMEFRAME
\- the minimum number of seconds each trace needs to take
.br
\&
.B MAXTIME
\- the maximum number of seconds to spend on any test
.br
\&
.B DEVIATION
\- the minimum sufficient % deviation from the average
.br
\&
.B AVERAGE
\- how many frames to average together
.br
\&
.B DEBUG
\- turn on extra debug output for testing/development
.PP
The \fITIMEFRAME\fR, \fIMAXTIME\fR, \fIDEVIATION\fR, and \fIAVERAGE\fR options control how the
benchmark will proceed including how long it should take. Each
individual benchmark run will consume at least a minimum \fITIMEFRAME\fR of
wallclock time so that the results can stabilize. After consuming at
least the minimum \fITIMEFRAME\fR, additional frames may be computed until
the standard deviation from the last \fIAVERAGE\fR count of frames is below
the specified \fIDEVIATION\fR. When a test is run and it completes in less
than \fITIMEFRAME\fR, the raytrace is restarted using double the number of
rays from the previous run. If the machine is fast enough, the
benchmark may accelerate the number or rays being fired. These
additional rays are hypersampled but without any jitter, so it's
effectively performing a multiplier amount of work over the initial
frame.
.PP
Plese send your BRL-CAD Benchmark results to the developers along with
detailed system information to <devs@brlcad.org>. Include at least:
.PP
0) Operating system type and version (e.g. uname -a)
1) Compiler name and version (e.g. gcc --version)
2) CPU configuration (e.g. cat /proc/cpuinfo or hinv or sysctl -a)
3) Cache (data and/or instruction) details for L1/L2/L3 and system
(e.g. cat /proc/cpuinfo or hinv or sysctl -a)
4) Output from this script (e.g. ./run.sh > run.sh.log 2>&1)
5) All generated log files (e.g. *.log* after running run.sh)
6) Anything else you think might be relevant to performance
.SH "SEE ALSO"
brlcad(1), rt(1), pix-fb(1), librt(3), pix(5).
.SH AUTHOR
Michael John Muuss
.br
Susan Muuss
.br
Christopher Sean Morrison
.SH SOURCE
BRL-CAD Open Source
.SH COPYRIGHT
This software is Copyright (c) 2006 United States Government as
represented by the U.S. Army Research Laboratory. All rights reserved.
.SH BUGS
None known.
.SH "BUG REPORTS"
Reports of bugs or problems should be submitted via electronic
mail to <devs@brlcad.org>.
+14 -52
View File
@@ -1,39 +1,4 @@
#!/bin/sh
# L G T . S H
# BRL-CAD
#
# Copyright (c) 2004-2006 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
#
# 3. The name of the author may not be used to endorse or promote
# products derived from this software without specific prior written
# permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
# OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
# GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
###
# A Shell script to test LGT
# @(#)$Header$ (BRL)
@@ -47,9 +12,6 @@ if ! test -f "$expected" ; then
exit 1
fi
# force locale setting to C so things like date output as expected
LC_ALL=C
LGT="$expected"
DB="$path_to_lgt_sh/../db"
@@ -94,7 +56,7 @@ G 64 0 0 0.0
p 0
# change background to mauve
b 111 66 66
# read key frame
# read key frame
j ../db/lgt-test.key
# display view #3
R
@@ -153,7 +115,7 @@ o
# bye
q
EOF
if test $? = 0 ; then
if test $? = 0 ; then
:
else
echo "Abnormal lgt exit"
@@ -167,16 +129,16 @@ fi
FAIL=0
for i in 1 2 3 ; do
if ${CMP} "$path_to_lgt_sh/../pix/lgt${i}.pix" lgt${i}a.pix ; then
if ${CMP} "$path_to_lgt_sh/../pix/lgt${i}.pix" lgt${i}a.pix ; then
:
else
else
echo "Test $i A failed."
FAIL=1
fi
if ${CMP} "$path_to_lgt_sh/../pix/lgt${i}.pix" lgt${i}b.pix
then
then
:
else
else
echo "Test $i B failed."
FAIL=1
fi
@@ -188,11 +150,11 @@ fi
echo "*** LGT does NOT work on this platform ***"
exit 2
# Local Variables:
# mode: sh
# tab-width: 8
# sh-indentation: 4
# sh-basic-offset: 4
# indent-tabs-mode: t
# End:
# ex: shiftwidth=4 tabstop=8
# Local Variables: ***
# mode: sh ***
# tab-width: 8 ***
# sh-indentation: 2 ***
# sh-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
Executable
+93
View File
@@ -0,0 +1,93 @@
#!/bin/sh
# A Shell script to extract the benchmark statistics, and build an
# entry suitable for the tables in doc/benchmark.doc.
# Note well that the command-line args may have embedded spaces.
# Mike Muuss & Susan Muuss, 11-Sept-88.
# @(#)$Header$ (BRL)
# Ensure /bin/sh
export PATH || (sh $0 $*; kill $$)
path_to_perf_sh=`dirname $0`
NAME=$0
if test "x$1" = x ; then
echo "Usage: $NAME hostname [note1] [note2]"
exit 1
fi
# Save three args, because arg list will be reused below.
# They may have embedded spaces in them.
HOST="$1"
NOTE1="$2"
NOTE2="$3"
NEW_FILES=" \
moss.log \
world.log \
star.log \
bldg391.log \
m35.log \
sphflake.log \
"
REF_FILES=" \
$path_to_perf_sh/../pix/moss.log \
$path_to_perf_sh/../pix/world.log \
$path_to_perf_sh/../pix/star.log \
$path_to_perf_sh/../pix/bldg391.log \
$path_to_perf_sh/../pix/m35.log \
$path_to_perf_sh/../pix/sphflake.log \
"
for i in $NEW_FILES $REF_FILES ; do
if test ! -f $i ; then
echo "${NAME}: file $i does not exist, aborting"
exit 1
fi
done
# Use TR to convert newlines to tabs.
VGRREF=`grep RTFM $REF_FILES | \
sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | \
tr '\012' '\011' `
CURVALS=`grep RTFM $NEW_FILES | \
sed -n -e 's/^.*= *//' -e 's/ rays.*//p' | \
tr '\012' '\011' `
RATIO_LIST=""
# Trick: Force args $1 through $6 to the numbers in $CURVALS
# This should be "set -- $CURVALS", but 4.2BSD /bin/sh can't handle it,
# and CURVALS are all positive (ie, no leading dashes), so this is safe.
set $CURVALS
while test $# -lt 6 ; do
echo "${NAME}: Warning, only $# times found, adding a zero."
CURVALS="${CURVALS}0 "
set $CURVALS
done
for ref in $VGRREF ; do
cur=$1
shift
RATIO=`echo "2k $cur $ref / p" | dc`
# Note: append new value and a trail TAB to existing list.
RATIO_LIST="${RATIO_LIST}$RATIO "
done
# The number of plus signs must be one less than the number of elements.
MEAN_ABS=`echo 2k $CURVALS +++++ 6/ p | dc`
MEAN_REL=`echo 2k $RATIO_LIST +++++ 6/ p | dc`
# Note: Both RATIO_LIST and CURVALS have an extra trailing tab.
# The question mark is for the mean field
echo "Abs ${HOST} ${CURVALS}${MEAN_ABS} $NOTE1"
echo "*vgr ${HOST} ${RATIO_LIST}${MEAN_REL} $NOTE2"
# Local Variables: ***
# mode: sh ***
# tab-width: 8 ***
# sh-indentation: 2 ***
# sh-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
+13 -32
View File
@@ -1,25 +1,5 @@
/* P I X C M P . C
* BRL-CAD
*
* Copyright (c) 2004-2006 United States Government as represented by
* the U.S. Army Research Laboratory.
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this file; see the file named COPYING for more
* information.
*
*/
/** @file pixcmp.c
/*
* P I X C M P . C
*
* Compute the difference between two .pix files.
* To establish context, a monochrome image is produced when there
@@ -36,14 +16,25 @@
* Source -
* SECAD/VLD Computing Consortium, Bldg 394
* The U. S. Army Ballistic Research Laboratory
* Aberdeen Proving Ground, Maryland 21005
*
* Copyright Notice -
* This software is Copyright (C) 1988-2004 by the United States Army.
* All rights reserved.
*/
#ifndef lint
static const char RCSid[] = "@(#)$Header$ (BRL)";
#endif
#include "common.h"
#include <stdio.h>
#include <stdlib.h>
#ifdef HAVE_STRING_H
#include <string.h>
#endif
long matching;
long off1;
long offmany;
@@ -141,13 +132,3 @@ main(int argc, char **argv)
/* Success! */
exit(0);
}
/*
* Local Variables:
* mode: C
* tab-width: 8
* c-basic-offset: 4
* indent-tabs-mode: t
* End:
* ex: shiftwidth=4 tabstop=8
*/
+49
View File
@@ -0,0 +1,49 @@
#!/bin/sh
export PATH || (echo "This isn't sh."; sh $0 $*; kill $$)
eval `machinetype.sh -b` # sets MACHINE, UNIXTYPE, HAS_TCP
if test -f ../.rt.$MACHINE/rt ; then
RT=../.rt.$MACHINE/rt
DB=../.db.$MACHINE
LD_LIBRARY_PATH=../.libbu.$MACHINE:../.libbn.$MACHINE:../.librt.$MACHINE:../.libfb.$MACHINE:../.libpkg.$MACHINE:../.libsysv.$MACHINE:$LD_LIBRARY_PATH
else
if test ! -f ../rt/rt ; then
echo "Can't find RT"
exit 1
fi
RT=../rt/rt
DB=../db
LD_LIBRARY_PATH=../libbu:../libbn:../librt:../libfb:../libpkg:../libsysv:$LD_LIBRARY_PATH
fi
export LD_LIBRARY_PATH
# Alliant NFS hack
if test x${MACHINE} = xfx ; then
cp ${RT} /tmp/rt
RT=/tmp/rt
fi
# WARNING THIS IS A REAL CPU HOG
if test -f cube.pix; then mv -f cube.pix cube.pix.$$; fi
if test -f cube.log; then mv -f cube.log cube.log.$$; fi
$RT -p90 -f1024 -H3 -M $*\
-o cube.pix\
$DB/cube.g\
'all.g' \
2> cube.log\
<<EOF
6.847580140e+03
3.699276190e+03 3.032924070e+03 3.658674860e+03
-5.735762590e-01 8.191521640e-01 0.000000000e+00 0.000000000e+00
-3.461885920e-01 -2.424037690e-01 9.063078880e-01 0.000000000e+00
7.424040310e-01 5.198366640e-01 4.226181980e-01 0.000000000e+00
0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00
EOF
# Local Variables: ***
# mode: sh ***
# tab-width: 8 ***
# sh-indentation: 2 ***
# sh-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
+58
View File
@@ -0,0 +1,58 @@
#!/bin/sh
# A Shell script to re-check the most recent results of the benchmark
# @(#)$Header$ (BRL)
# Ensure /bin/sh
export PATH || (echo "This isn't sh."; sh $0 $*; kill $$)
eval `machinetype.sh -b` # sets MACHINE, UNIXTYPE, HAS_TCP
if test -f ../.util.$MACHINE/pixdiff ; then
PIXDIFF=../.util.$MACHINE/pixdiff
PIX_FB=../.fb.$MACHINE/pix-fb
LD_LIBRARY_PATH=../.libbu.$MACHINE:../.libbn.$MACHINE:../.librt.$MACHINE:../.libfb.$MACHINE:../.libpkg.$MACHINE:../.libsysv.$MACHINE:$LD_LIBRARY_PATH
else
if test -f ../util/pixdiff ; then
PIXDIFF=../util/pixdiff
PIX_FB=../fb/pix-fb
else
echo "Can't find pixdiff"
exit 1
fi
LD_LIBRARY_PATH=../libbu:../libbn:../librt:../libfb:../libpkg:../libsysv:$LD_LIBRARY_PATH
fi
export LD_LIBRARY_PATH
# Alliant NFS hack
if test x${MACHINE} = xfx ; then
cp ${PIXDIFF} /tmp/pixdiff
cp ${PIX_FB} /tmp/pix-fb
PIXDIFF=/tmp/pixdiff
PIX_FB=/tmp/pix-fb
fi
echo +++++ moss.pix
${PIXDIFF} ../pix/moss.pix moss.pix | ${PIX_FB}
echo +++++ world.pix
${PIXDIFF} ../pix/world.pix world.pix | ${PIX_FB}
echo +++++ star.pix
${PIXDIFF} ../pix/star.pix star.pix | ${PIX_FB}
echo +++++ bldg391.pix
${PIXDIFF} ../pix/bldg391.pix bldg391.pix | ${PIX_FB}
echo +++++ m35.pix
${PIXDIFF} ../pix/m35.pix m35.pix | ${PIX_FB}
echo +++++ sphflake.pix
${PIXDIFF} ../pix/sphflake.pix sphflake.pix | ${PIX_FB}
# Local Variables: ***
# mode: sh ***
# tab-width: 8 ***
# sh-indentation: 2 ***
# sh-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
+226 -1020
View File
File diff suppressed because it is too large Load Diff
+204 -64
View File
@@ -1,74 +1,214 @@
#!/bin/sh
# T R Y . S H
# BRL-CAD
#
# Copyright (c) 2004-2006 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
#
# 3. The name of the author may not be used to endorse or promote
# products derived from this software without specific prior written
# permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
# OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
# GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
###
# A Shell script to run the BRL-CAD Benchmark, with output going to
# a framebuffer rather than to a file.
#
# Authors -
# Mike Muuss
# Christopher Sean Morrison
#
# A Shell script to run the BRL-CAD Benchmark Test,
# with output going to the current framebuffer, rather than a file.
# @(#)$Header$ (BRL)
# Ensure /bin/sh
export PATH || (echo "This isn't sh."; sh $0 $*; kill $$)
path_to_this=`dirname $0`
path_to_run_sh=`dirname $0`
# force locale setting to C so things like date output as expected
LC_ALL=C
# sets MACHINE, UNIXTYPE, HAS_TCP
eval `machinetype.sh -b 2> /dev/null`
TIMEFRAME=1 ; export TIMEFRAME
MAXTIME=1 ; export MAXTIME
ARGS="-F/dev/Xl $*"
if test -f "$path_to_this/run.sh" ; then
$path_to_this/run.sh $ARGS
elif test -f "$path_to_this/benchmark" ; then
$path_to_this/benchmark $ARGS
elif test -f "/usr/brlcad/bin/benchmark" ; then
/usr/brlcad/bin/benchmark $ARGS
if test "x$MACHINE" = "x" ; then
echo Looking for machinetype.sh...
eval `$path_to_run_sh/../sh/machinetype.sh -b 2> /dev/null`
if test "x$MACHINE" = "x" ; then
echo WARNING: could not find machinetype.sh
# try _something_, linux is pretty popular
MACHINE="li"
else
echo ...found local machinetype.sh
fi
fi
echo Looking for RT...
# find the raytracer
# RT environment variable overrides
if test "x${RT}" = "x" ; then
# see if we find the rt binary
if test -x "$path_to_run_sh/../src/rt" ; then
echo ...found $path_to_run_sh/../src/rt/rt
RT="$path_to_run_sh/../src/rt/rt"
LD_LIBRARY_PATH="$path_to_run_sh/../src/rt:$LD_LIBRARY_PATH"
fi
else
echo ...using $RT from RT environment variable setting
fi
# Local Variables:
# mode: sh
# tab-width: 8
# sh-indentation: 4
# sh-basic-offset: 4
# indent-tabs-mode: t
# End:
# ex: shiftwidth=4 tabstop=8
echo Looking for geometry database directory...
# find geometry database directory if we do not already know where it is
# DB environment variable overrides
if test "x${DB}" = "x" ; then
if test -f "$path_to_run_sh/../db/sphflake.g" ; then
echo ...found $path_to_run_sh/../db
DB="$path_to_run_sh/../db"
fi
else
echo ...using $DB from DB environment variable setting
fi
echo Checking for pixel comparison utility...
# find pixel comparison utility
# CMP environment variable overrides
if test "x${CMP}" = "x" ; then
if test -x $path_to_run_sh/pixcmp ; then
echo ...found $path_to_run_sh/pixcmp
CMP="$path_to_run_sh/pixcmp"
else
if test -f "$path_to_run_sh/pixcmp.c" ; then
echo ...need to build pixcmp
for compiler in $CC gcc cc ; do
CC=$compiler
$CC "$path_to_run_sh/pixcmp.c" >& /dev/null
if $? = 0 ; then
break
fi
if test -f "$path_to_run_sh/pixcmp" ; then
break;
fi
done
if test -f "$path_to_run_sh/pixcmp" ; then
echo ...built pixcmp with $CC
CMP="$path_to_run_sh/pixcmp"
fi
fi
fi
else
echo ...using $CMP from CMP environment variable setting
fi
# Alliant NFS hack
if test "x${MACHINE}" = "xfx" ; then
cp ${RT} /tmp/rt
cp ${CMP} /tmp/pixcmp
RT=/tmp/rt
CMP=/tmp/pixcmp
fi
# print results or choke
if test "x${RT}" = "x" ; then
echo "ERROR: Could not find the BRL-CAD raytracer"
exit 1
else
echo "Using [$RT] for RT"
fi
if test "x${DB}" = "x" ; then
echo "ERROR: Could not find the BRL-CAD database directory"
exit 1
else
echo "Using [$DB] for DB"
fi
if test "x${CMP}" = "x" ; then
echo "ERROR: Could not find the BRL-CAD pixel comparison utility"
exit 1
else
echo "Using [$CMP] for CMP"
fi
export LD_LIBRARY_PATH
echo
# Run the tests
echo +++++ moss
time $RT -B -M -s512 $* \
$DB/moss.g all.g \
<< 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 -3.461886346e-01 -2.424038798e-01 9.063078165e-01
0.000000000e+00 7.424039245e-01 5.198368430e-01 4.226182699e-01
0.000000000e+00 0.000000000e+00 0.000000000e+00 0.000000000e+00
1.000000000e+00 ;
start 0;
end;
EOF
echo +++++ world
time $RT -B -M -s512 $* \
$DB/world.g all.g \
<< 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 -3.461886346e-01 -2.424038798e-01 9.063078165e-01
0.000000000e+00 7.424039245e-01 5.198368430e-01 4.226182699e-01
0.000000000e+00 0.000000000e+00 0.000000000e+00 0.000000000e+00
1.000000000e+00 ;
start 0;
end;
EOF
echo +++++ star
time $RT -B -M -s512 $* \
$DB/star.g all \
<<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
5.539599410e-01 4.823888300e-02 8.311441420e-01 0.000000000e+00
4.896120540e-01 7.885590550e-01 -3.720948210e-01 0.000000000e+00
0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 ;
start 0;
end;
EOF
echo +++++ bldg391
time $RT -B -M -s512 $* \
$DB/bldg391.g all.g \
<<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 -3.461886346e-01 -2.424038798e-01 9.063078165e-01
0.000000000e+00 7.424039245e-01 5.198368430e-01 4.226182699e-01
0.000000000e+00 0.000000000e+00 0.000000000e+00 0.000000000e+00
1.000000000e+00 ;
start 0;
end;
EOF
echo +++++ m35
time $RT -B -M -s512 $* \
$DB/m35.g all.g \
<< 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
-4.815587087e-01 -3.308784486e-01 8.115544728e-01 0.000000000e+00
6.800964482e-01 4.429747496e-01 5.841593895e-01 0.000000000e+00
0.000000000e+00 0.000000000e+00 0.000000000e+00 1.000000000e+00 ;
start 0;
end;
EOF
echo +++++ sphflake
time $RT -B -M -s512 $* \
$DB/sphflake.g scene.r \
<< 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;
start 0;
end;
EOF
# Local Variables: ***
# mode: sh ***
# tab-width: 8 ***
# sh-indentation: 2 ***
# sh-basic-offset: 2 ***
# indent-tabs-mode: t ***
# End: ***
# ex: shiftwidth=2 tabstop=8
-183
View File
@@ -1,183 +0,0 @@
#!/bin/sh
# R E C H E C K . S H
# BRL-CAD
#
# Copyright (c) 2004-2006 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
#
# 3. The name of the author may not be used to endorse or promote
# products derived from this software without specific prior written
# permission.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
# OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
# GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
###
# A Shell script to view the differences of a benchmark run,
# displaying the results in a framebuffer window.
#
# The following environment variables will modify how the view diff
# behaves (in case you're not running from a source distribution, for
# example):
#
# PIX - the directory containing the pix files to be compare
# PIXDIFF - the name of a pix diff tool
# PIXFB - the name of a pix to framebuffer tool (e.g. pix-fb)
#
# Authors -
# Mike Muuss
# Christopher Sean Morrison
#
# @(#)$Header$
# Ensure /bin/sh
export PATH || (echo "This isn't sh."; sh $0 $*; kill $$)
path_to_this="`dirname $0`"
echo Looking for benchmark images ...
# find pix reference image directory if we do not already know where
# it is. PIX environment variable overrides
if test "x${PIX}" = "x" ; then
if test -f "$path_to_this/../pix/sphflake.pix" ; then
echo ...found .pix image files in $path_to_this/../pix
PIX="$path_to_this/../pix"
elif test -f "$path_to_this/sphflake.pix" ; then
echo ...found .pix image files in $path_to_this
PIX="$path_to_this"
elif test -f "$path_to_this/../share/brlcad/pix/sphflake.pix" ; then
echo ...found .pix image files in $path_to_this/../share/brlcad/pix
PIX="$path_to_this/../share/brlcad/pix"
fi
else
echo ...using $PIX from PIX environment variable setting
fi
echo Checking for pixel diff utility...
# find pixel diff utility
# PIXDIFF environment variable overrides
if test "x${PIXDIFF}" = "x" ; then
if test -x $path_to_this/pixdiff ; then
echo ...found $path_to_this/pixdiff
PIXDIFF="$path_to_this/pixdiff"
elif test -x $path_to_this/../src/util/pixdiff ; then
echo ...found $path_to_this/../src/util/pixdiff
PIXDIFF="$path_to_this/../src/util/pixdiff"
else
if test -f "$path_to_this/../src/util/pixdiff.c" ; then
echo ...need to build pixdiff
for compiler in $CC gcc cc ; do
COMPILE="$compiler"
if test "x$COMPILE" = "x" ; then
continue
fi
$COMPILE -o pixdiff "$path_to_this/../src/util/pixdiff.c"
if test "x$?" = "x0" ; then
break
fi
if test -f "pixdiff" ; then
break;
fi
done
if test -f "pixdiff" ; then
echo ...built pixdiff with $COMPILE -o pixdiff pixdiff.c
PIXDIFF="./pixdiff"
fi
fi
fi
else
echo ...using $PIXDIFF from PIXDIFF environment variable setting
fi
echo Checking for pix to framebuffer utility...
# find pix to framebuffer utility
# PIXFB environment variable overrides
if test "x${PIXFB}" = "x" ; then
if test -x $path_to_this/pix-fb ; then
echo ...found $path_to_this/pix-fb
PIXFB="$path_to_this/pix-fb"
elif test -x $path_to_this/../src/fb/pix-fb ; then
echo ...found $path_to_this/../src/fb/pix-fb
PIXFB="$path_to_this/../src/fb/pix-fb"
else
if test -f "$path_to_this/../src/fb/pix-fb.c" ; then
echo ...need to build pix-fb
for compiler in $CC gcc cc ; do
COMPILE="$compiler"
if test "x$COMPILE" = "x" ; then
continue
fi
$COMPILE -o pix-fb "$path_to_this/../src/fb/pix-fb.c"
if test "x$?" = "x0" ; then
break
fi
if test -f "pix-fb" ; then
break;
fi
done
if test -f "pix-fb" ; then
echo ...built pix-fb with $COMPILE -o pix-fb pix-fb.c
PIXFB="./pix-fb"
fi
fi
fi
else
echo ...using $PIXFB from PIXFB environment variable setting
fi
echo +++++ moss.pix
${PIXDIFF} ${PIX}/moss.pix moss.pix | ${PIXFB}
echo +++++ world.pix
${PIXDIFF} ${PIX}/world.pix world.pix | ${PIXFB}
echo +++++ star.pix
${PIXDIFF} ${PIX}/star.pix star.pix | ${PIXFB}
echo +++++ bldg391.pix
${PIXDIFF} ${PIX}/bldg391.pix bldg391.pix | ${PIXFB}
echo +++++ m35.pix
${PIXDIFF} ${PIX}/m35.pix m35.pix | ${PIXFB}
echo +++++ sphflake.pix
${PIXDIFF} ${PIX}/sphflake.pix sphflake.pix | ${PIXFB}
# Local Variables:
# mode: sh
# tab-width: 8
# sh-indentation: 4
# sh-basic-offset: 4
# indent-tabs-mode: t
# End:
# ex: shiftwidth=4 tabstop=8
+6 -16
View File
@@ -1,25 +1,15 @@
# BRL-CAD
# Copyright (c) 2004 BRL-CAD Developers
# $Id$
#
# Copyright (C) 2004-2005 United States Government as represented by
# the U.S. Army Research Laboratory.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as
# published by the Free Software Foundation; either version 2 of the
# License, or (at your option) any later version.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the appropriate license described in the file
# named COPYING that should have accompanied this file.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
#
# You should have received a copy of the GNU General Public License
# along with this file; see the file named COPYING for more
# information.
#
#
# $Id$
Summary: BRLCAD
Name: @PACKAGE@
+1094 -2378
View File
File diff suppressed because it is too large Load Diff
+1
View File
@@ -1,3 +1,4 @@
.cvsignore
Makefile
Makefile.in
axis.g
+9 -25
View File
@@ -12,20 +12,12 @@ G2A=$(top_builddir)/src/conv/g2asc
echo $(A2G) $< $@ ; \
$(A2G) `if test -e $< ; then echo $< ; else echo $(top_srcdir)/db/$< ; fi` $@ ; \
else \
echo "$(A2G) does not exist" ; \
echo "$(A2G) does not exist" ; touch $@ ; \
fi
BENCHMARK_MODELS = \
bldg391.asc \
m35.asc \
moss.asc \
sphflake.asc \
star.asc \
world.asc
MODELS = \
$(BENCHMARK_MODELS) \
axis.asc \
bldg391.asc \
boolean-ops.asc \
castle.asc \
cornell.asc \
@@ -38,36 +30,28 @@ MODELS = \
kman.asc \
ktank.asc \
lgt-test.asc \
m35.asc \
moss.asc \
pic.asc \
prim.asc \
sphflake.asc \
star.asc \
tank_car.asc \
terra.asc \
truck.asc \
wave.asc \
woodsman.asc \
world.asc \
xmp.asc
EXTRA_DIST = \
${MODELS:asc=g} \
${MODELS} \
db.php
dbdir = $(BRLCAD_DATA)/db
if INSTALL_MODELS
db_DATA = ${MODELS:asc=g}
EXTRA_DATA = ${MODELS:asc=g}
BUILT_SOURCES = ${MODELS:asc=g}
else !INSTALL_MODELS
db_DATA = ${BENCHMARK_MODELS:asc=g}
BUILT_SOURCES = ${BENCHMARK_MODELS:asc=g}
endif
# end INSTALL_MODELS
MOSTLYCLEANFILES = ${MODELS:asc=g}
MAINTAINERCLEANFILES = Makefile.in
include $(top_srcdir)/misc/Makefile.defs
+14 -25
View File
@@ -1,29 +1,9 @@
<?php
/* D B . P H P
* BRL-CAD
*
* Copyright (c) 2004-2006 United States Government as represented by
* the U.S. Army Research Laboratory.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public License
* as published by the Free Software Foundation; either version 2 of
* the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Library General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this file; see the file named COPYING for more
* information.
*
**//** @file db.php
/* d b . p h p
*
* Really Simple Syndication of BRL-CAD Geometry Databases
*
* Description -
* Description -
* This script will publish an rss feed of BRL-CAD geometry
* databases. For convenience, a path alias should be set up for
* the * script with a web server. For Apache, adding something
@@ -34,10 +14,19 @@
*
* Author -
* Sean Morrison
*
*
* Source -
* The U.S. Army Research Laboratory
* Aberdeen Proving Ground, Maryland 21005-5068 USA
*
* Distribution Notice -
* Re-distribution of this software is restricted, as described in
* your "Statement of Terms and Conditions for the Release of
* The BRL-CAD Package" agreement.
*
* Copyright Notice -
* This software is Copyright (C) 2004 by the United States Army
* in all countries except the USA. All rights reserved.
*/
/* --SETTINGS-- */
@@ -196,7 +185,7 @@ if ($mimeType) {
/* just return the file if it exists */
if ($physicalFile) {
/* sanity check */
if (isset($_SERVER['PATH_INFO'])) {
$fileWithPath = $PATH_TO_DB . "/" . $_SERVER['PATH_INFO'];
@@ -211,7 +200,7 @@ if ($physicalFile) {
header("Content-Length: " . filesize($fileWithPath));
readfile($fileWithPath);
} else {
debug("ERROR: $fileWithPath does not exist\n");
die("ERROR: File $fileWithPath not found.");
-3
View File
@@ -5,6 +5,3 @@ EXTRA_DIST = \
debug.inc
MAINTAINERCLEANFILES = Makefile.in
include $(top_srcdir)/misc/Makefile.defs
-56
View File
@@ -1,56 +0,0 @@
Ideas for new BRL-CAD contributors
==================================
If someone is interested in contributing to BRL-CAD and doesn't have
an idea of where to begin, included below is a list of ideas of
interest for people to work on. Each idea has been given a value
between 0 and 9 as a broad indicator of the difficulty and a rough
relative estimate of the expected time involved.
D
i
f
f
i
c
u T
l i
t m
y e
----------------------------------------------------------------------
0 0 Install and setup BRL-CAD
0 2 Go through the modeling tutorials
0 1 Render pictures
2 2 Model something real
3 1 Make an animation
0 1 Run and collect BRL-CAD Benchmark results
1 4 Run, document, and categorize commands
2 5 Work on the Materials Database
2 5 Work on the Geometry Repository
2 5 Work on the Benchmark Results Database
3 3 Create a Java-based 3D geometry viewer
4 3 Write a SWIG interface to the modeling commands
2 6 Convert documentation to Docbook
1 5 Translate documentation to other languages
2 2 Add Griffen knob support to MGED
3 2 Add SGI knob and button box support to MGED on MacOSX
4 4 Write a new geometry converter
3 3 Write a new image converter
3 3 Write a new data processing utility
4 3 Write a new shader to RT
4 4 Implement a new primitive
2 6 Work on the BRL-CAD website
1 2 Make an overview diagram of BRL-CAD
1 2 Write a BRL-CAD tutorial
2 2 Write a new manual page
3 4 Write a system information tool for the benchmark
* * Fix one of the bugs listed in the BUGS file
* * Fix one of the bugs listed in the bug tracker
* * Implement one of the items listed in the TODO file
* * Implement a requested feature from the RFE tracker
---
There may be more tasks and ideas available in the Tasks section of
the project website at
http://sourceforge.net/pm/task.php?group_project_id=35563&group_id=105292
+2 -14
View File
@@ -4,18 +4,9 @@ SUBDIRS = \
html \
legal
documentationdir = $(BRLCAD_DATA)/doc
documentation_DATA = \
README.AIX \
README.BSD \
README.IRIX \
README.Linux \
data_DATA = \
README.MacOSX \
README.Solaris \
README.Windows \
anim.txt \
archer_ack.txt \
benchmark.tr \
cvs.txt \
description.txt \
@@ -42,10 +33,7 @@ man_MANS = \
plot3.5
EXTRA_DIST = \
$(documentation_DATA) \
$(data_DATA) \
$(man_MANS)
MAINTAINERCLEANFILES = Makefile.in
include $(top_srcdir)/misc/Makefile.defs
View File
-18
View File
@@ -1,18 +0,0 @@
The only issue that comes to mind, is that newer versions of libtool
have a bug where they do not install the .la files causing libtool to
report warnings. If you see messages in the output during install
such as:
libtool: install: warning: `../../src/libfb/libfb.la' has not been installed in `/usr/brlcad/lib'
libtool: install: warning: `../../src/libbu/libbu.la' has not been installed in `/usr/brlcad/lib'
Those warnings are not cause for concern. The install is complete if
that is all that is being reported. Regardless, a simple workaround
to quell the warnings is to manually copy all the .la files in one
step to the install library directory:
find . -name \*.la -exec cp {} /usr/brlcad/lib/. \;
After that, a 'sudo make install' (or whatever means you use to go
root) should work just fine and the warnings should go away.
-25
View File
@@ -1,25 +0,0 @@
BRL-CAD on IRIX README
======================
Note by setting the compiler flags, configure seems to skip the check
for maximum shell command line length is skipped. Be careful not to
place the source in a directory too deep. The libtool script wrapper
which runs bwish builds a command line that is too long for the shell
to handle. So for example, placing the source in:
/vld/butler/BRLCAD/mips64_brlcad-7.2.0
is known to cause a build failure. On the other hand, the following:
/vld/butler/BRLCAD/m6_72
resulted in a successful build.
For IRIX 64bit build:
export SGI_ABI=-64
./configure CC=cc CFLAGS=-64 LDFLAGS=-64 --enable-64bit-build
For IRIX 32bit build:
export SGI_ABI=-n32
./configure CC=cc
-4
View File
@@ -1,4 +0,0 @@
If you happen to be installing on a ppc64 Linux system, the binaries
will not correctly resolve without being installed first. Be sure to
install before testing applications.
+9 -20
View File
@@ -9,6 +9,7 @@ same as the UNIX, BSD, and Linux platforms.
X11 Window Server
-----------------
You'll need to install an X11 server if you would like to build Tk and
have a graphical user interface. Apple's X11 is the recommended X
Window Server, though XDarwin should work suitably as well. Be sure
@@ -18,30 +19,17 @@ package.
Supported Versions
------------------
BRL-CAD is generally only "extensively" tested by the developers on
the latest released version of Mac OS X only. That is to say that
although the BRL-CAD package should build on prior versions of the Mac
OS X operating system, they are generally and eventually not
maintained and will require additional effort to obtain a build.
Compiling on 10.3 or 10.4 should complete successfully. Due to a
variety of significant application programming interface issues in
early releases of Mac OS X, versions prior to 10.2 are unsupported.
Mac OS X 10.2
-------------
Compiling directly on Mac OS X 10.2 requires additional effort. When
compiling from source, a libtool script is generated after running
autogen.sh that gets used during compilation. The version of
glibtoolize shipped with 10.2 is non-functional with respect to
convenience libraries, a feature that BRL-CAD requires. That means
that you will need to obtain the generated libtool script from other
means. You can either run autogen.sh on a different machine that has
a newer version of libtool installed or you can download a source
disribution where autogen.sh has already been run for you on a
relatively new system.
BRL-CAD is generally extensively tested by the developers on the
latest released version of Mac OS X only. That is to say that
although the package should build on prior versions of the operating
system, they are generally unmaintained. Due to a variety of
significant application programming interface issues in early releases
of Mac OS X, versions prior to 10.2 are unsupported.
Parallel Builds
---------------
As many workstation and server systems shipped by Apple are
multiprocessor systems, you can enjoy the benefits of decreased
compile times by utilizing the "-j" option to make. After running
@@ -49,6 +37,7 @@ configure, run "make -j2" to build on a 2-processor system.
Bugs
----
The only known bugs specific to Mac OS X are limitations of Tk or the
X11 event handler that our generally outside of BRL-CAD's domain.
Refer to BUGS for more general details on known bugs and reporting
-10
View File
@@ -1,10 +0,0 @@
If while compiling you encounter an error "Text relocation remains
against symbol" along with some number of lines following, it usually
means that the build has attempted to link a static system library
into a shared library being compiled (e.g. attempting to link a system
libz.a into the png library distributed in src/other/libpng being
compiled as libpng.so).
The fix/workaround is pretty simple. Either install a shared verison
of the system library (e.g. libz.so) or run configure with the
-mimpure-text linker option: ./configure LDFLAGS=-mimpure-text
-8
View File
@@ -1,8 +0,0 @@
The Windows build of MGED does not currently have a functioning
display manager so raytracing directly into the Graphics Window is not
possible. To raytrace, users should either render directly to a
window by utilizing the 'rt' command, or by launching a framebuffer
server via 'fbserv' on the command-line. The framebuffer can be "set
default" by adding a -F# (e.g. -F0) to the "Other Options" field of
the "Advanced Settings..." panel of the Raytrace Control Panel,
selected via File->Raytrace.
-1
View File
@@ -1 +0,0 @@
␍Archer was developed by SURVICE Engineering under the Phase II Small Business Innovative Research (SBIR) grant AF03-141 (reference contract FA8651-04-C-0137) under the supervision of Lt. Edwin Rodriquez (AFRL/MNAL).␍␍Archer is built upon BRL-CAD. SURVICE would like to acknowledge the contribution and support from the Army Research Laboratory (ARL) BRL-CAD Development Team, without which Archer would not be possible.␍␍The following is the Archer Development Team:␍- Bob Parker: Principal programmer␍- Doug Howard: Original coding and plug-in interface design␍- Keith Bowman: Architecture ␍- Steve Phillips: Website and Software Change Request (SCR) tracking system␍- Mark Butkiewicz: Project Management␍
+19 -19
View File
@@ -186,11 +186,11 @@ l l.
System Name Configuration
_ _
axposf DEC Alpha 4000/710, 256M, OSF/1 V3.0 \(dg
ex-art Pentium-P90, 16MB, 256K cache, BSD/OS 2.0,
ex-art Pentium-P90, 16MB, 256K cache, BSD/OS 2.0,
hawks 486DX/33, 24MB, 256K cache, BSD/OS 2.0
orac 486/100, 20MB, No cache, BSD/OS 2.0 (laptop)
pk Cray C90, C916/161024, UNICOS 8.0.2.4
vapor SGI, 18* 75 MHz R8000 IP21, 1024M RAM 8-way, Irix 6.0
vapor SGI, 18* 75 MHz R8000 IP21, 1024G RAM 8-way, Irix 6.0
vblt 66 MHz 486DX2/66, 16M RAM, Linux 1.1.73
vgr DEC VAX-11/780 w/FPA, 64M RAM, 4.3 BSD
vision Sun-3/280 w/68881 FPA, 16M RAM, SunOS 4.1.1
@@ -198,8 +198,8 @@ voyage SGI, 4* 25 MHz R3000 IP7, 56M RAM, Irix 4.0.1
whiz SGI Ingido**2, 100 MHz IP22, 96M RAM, Irix 5.2
waffle SGI, 4* 25 MHz R3000 IP7, 64M RAM, Irix 4.0.5 (heavy network use)
warp Sun SPARCstation 5, 32M RAM, SunOS 4.1.4
wax SGI, 24* 150 MHz R4400 IP19, 1024M RAM 4-way, Irix 5.2
wilson SGI, 8* 100 MHz R4400 IP19, 1024M RAM 8-way, Irix 5.2
wax SGI, 24* 150 MHz R4400 IP19, 1024G RAM 4-way, Irix 5.2
wilson SGI, 8* 100 MHz R4400 IP19, 1024G RAM 8-way, Irix 5.2
wilted Sun-4/25 ELC, 16M RAM, SunOS 4.1.1
wimp 33 MHz 386DX/33 w/387, 256k cache, 16M RAM, BSDI 2.0beta2
wimpy Sun SS10BSX-GX, 2* 50 MHz SuperSPARC, 64M RAM, SunOS 5.4
@@ -218,7 +218,7 @@ between different runs on the \fIsame\fR database; it is not
meaningful to compare RTFM numbers between different databases. The
Rays/sec number for a multi-processor machine is for "aggregate CPU
cluster seconds", rather than rays/total CPU seconds (which remains
fairly constant on good parallel machines).
fairly constant on good parallel machines).
.PP
The statistics are recorded in an easily understood format, with all
results for a particular configuration listed on a single line. The
@@ -312,11 +312,11 @@ wilson 41.16 39.54 45.98 42.93 34.82 40.88 -P1
whiz 36.25 31.08 37.21 39.62 36.98 36.22
warp 19.88 21.33 23.71 24.19 22.60 22.34
ex-art 16.89 18.54 22.98 26.97 25.57 22.19
orac 7.57 8.23 10.72 12.43 11.30 10.05
orac 7.57 8.23 10.72 12.43 11.30 10.05
wilted 9.58 9.53 10.66 10.53 9.87 10.03
hawks 3.64 4.17 5.71 6.90 6.23 5.33
vblt 4.85 4.89 5.29 5.24 4.90 5.03
wimp 1.16 1.34 1.82 2.25 2.06 1.72
hawks 3.64 4.17 5.71 6.90 6.23 5.33
vblt 4.85 4.89 5.29 5.24 4.90 5.03
wimp 1.16 1.34 1.82 2.25 2.06 1.72
vision 1.07 1.23 1.23 1.31 1.26 1.22 -P1
vgr 1.0 1.0 1.0 1.0 1.0 1.0
.TE
@@ -351,7 +351,7 @@ virus Sun-3/50, 15 Mhz clock, 12 Mhz 68881, Sun UNIX 3.2
vista SGI 3030, w/FP chip, UNIX release 3.5
vmb Gould PN 9080, no MACCs, UTX 2.0, 12x1Mb mem boards
vhs Silicon Graphics 4D/60T, 12.5 Mhz clock 16 MB memory
ovoyage Silicon Graphics 4D/120, 16.7 Mhz clock 16 MB memory
ovoyage Silicon Graphics 4D/120, 16.7 Mhz clock 16 MB memory
taylor Silicon Graphics 4D/220, 25 Mhz clock 16 MB memory
crim Silicon Graphics 4DCRIMS 50Mhz clock 128 MB memory
wiltse Silicon Graphics 4D R4000 50Mhz clock
@@ -640,7 +640,7 @@ _
Abs video 940.33 469.30 399.21 367.64 544.12 UNIX 2.0
*vgr video 6.77 6.98 7.32 7.48 7.13 -O2
_
Abs vhs 954.81 471.90 409.78 392.55 557.26 IRix 3.1
Abs vhs 954.81 471.90 409.78 392.55 557.26 IRix 3.1
*vgr vhs 6.87 7.02 7.52 7.99 7.45 Parallel, -P1
_
Abs bob 2602.68 1078.25 712.39 642.42 1258.93 UNICOS 4.0, /bin/cc
@@ -693,40 +693,40 @@ A/* H/W Moss World Star Bldg M35 Mean CPU
_
.TH
Abs vgr 128.64 54.47 45.17 40.35 49.02 63.53 1
*vgr vgr 1.00 1.00 1.00 1.00 1.00 1.00
*vgr vgr 1.00 1.00 1.00 1.00 1.00 1.00
_
Abs rh2 1704.56 791.31 599.81 549.74 589.01 846.88 1
*vgr rh2 13.25 14.52 13.27 13.62 12.01 13.33
_
Abs spark 435.69 208.59 176.76 177.69 174.67 234.68 1
*vgr spark 3.53 3.61 4.17 4.29 3.40 3.80
*vgr spark 3.53 3.61 4.17 4.29 3.40 3.80
_
Abs vhs 973.11 475.00 384.62 351.12 343.44 505.45 1
*vgr vhs 7.56 8.72 8.51 8.70 7.00 8.09
*vgr vhs 7.56 8.72 8.51 8.70 7.00 8.09
_
Abs whisper 1118.35 561.81 473.52 439.76 509.26 620.54 1
*vgr whisper 8.69 10.31 10.48 10.89 10.38 10.15
*vgr whisper 8.69 10.31 10.48 10.89 10.38 10.15
_
Abs nova 2024.80 976.01 790.17 732.35 ? 1130.83 1
*vgr nova 15.74 17.92 17.49 18.15 ? 17.32
_
Abs ovoyage 1969.57 1001.21 862.77 809.61 786.11 1085.85 2
*vgr ovoyage 15.31 18.38 19.10 20.06 16.03 17.77
*vgr ovoyage 15.31 18.38 19.10 20.06 16.03 17.77
_
Abs taylor 2446.98 1076.24 912.03 837.56 799.58 1214.47 1
*vgr taylor 19.02 19.75 20.19 20.75 16.31 19.20
*vgr taylor 19.02 19.75 20.19 20.75 16.31 19.20
_
Abs worm 2671.46 1218.49 966.76 859.61 932.18 1329.70 1
*vgr worm 20.76 22.36 21.40 21.30 19.01 20.96
_
Abs viper 3255.73 1368.96 1102.71 1039.37 1008.15 1554.98 8
*vgr viper 25.30 25.13 24.41 25.75 20.56 24.23
*vgr viper 25.30 25.13 24.41 25.75 20.56 24.23
_
Abs vector 3956.86 1625.23 1234.03 1137.36 1121.41 1814.97 8
*vgr vector 30.75 29.83 27.31 28.18 22.87 27.78
_
Abs taylor 4730.05 2225.56 1742.09 1590.57 1551.78 2368.01 2
*vgr taylor 36.76 40.85 38.56 39.41 31.65 37.44
*vgr taylor 36.76 40.85 38.56 39.41 31.65 37.44
_
Abs worm 5017.85 2309.86 1894.92 1708.27 1791.11 2544.40 2
*vgr worm 39.00 42.40 41.95 42.33 36.53 40.44
+1 -24
View File
@@ -1,27 +1,4 @@
.TH BW 5 BRL-CAD
.\" B W . 5
.\" BRL-CAD
.\"
.\" Copyright (c) 2005-2006 United States Government as represented by
.\" the U.S. Army Research Laboratory.
.\"
.\" This document is made available under the terms of the GNU Free
.\" Documentation License or, at your option, under the terms of the
.\" GNU General Public License as published by the Free Software
.\" Foundation. Permission is granted to copy, distribute and/or
.\" modify this document under the terms of the GNU Free Documentation
.\" License, Version 1.2 or any later version published by the Free
.\" Software Foundation; with no Invariant Sections, no Front-Cover
.\" Texts, and no Back-Cover Texts. Permission is also granted to
.\" redistribute this document under the terms of the GNU General
.\" Public License; either version 2 of the License, or (at your
.\" option) any later version.
.\"
.\" You should have received a copy of the GNU Free Documentation
.\" License and/or the GNU General Public License along with this
.\" document; see the file named COPYING for more information.
.\"
.\".\".\"
.TH BW 5 BRL/CAD
.SH NAME
bw \- Black and White image file format and utilities
.SH FORMAT
+1 -24
View File
@@ -1,27 +1,4 @@
.TH CMAP 5 BRL-CAD
.\" C M A P . 5
.\" BRL-CAD
.\"
.\" Copyright (c) 2005-2006 United States Government as represented by
.\" the U.S. Army Research Laboratory.
.\"
.\" This document is made available under the terms of the GNU Free
.\" Documentation License or, at your option, under the terms of the
.\" GNU General Public License as published by the Free Software
.\" Foundation. Permission is granted to copy, distribute and/or
.\" modify this document under the terms of the GNU Free Documentation
.\" License, Version 1.2 or any later version published by the Free
.\" Software Foundation; with no Invariant Sections, no Front-Cover
.\" Texts, and no Back-Cover Texts. Permission is also granted to
.\" redistribute this document under the terms of the GNU General
.\" Public License; either version 2 of the License, or (at your
.\" option) any later version.
.\"
.\" You should have received a copy of the GNU Free Documentation
.\" License and/or the GNU General Public License along with this
.\" document; see the file named COPYING for more information.
.\"
.\".\".\"
.TH CMAP 5 BRL/CAD
.SH NAME
cmap \- Framebuffer colormap file format and utilities
.SH FORMAT
+14 -14
View File
@@ -5,7 +5,7 @@ The document includes a set of requirements and recommended procedures
for how to effectively use CVS with this project. Included are
details on checking code in and out, effective use of commit messages,
tag naming conventions, branch management, making releases, and more.
Basic knowledge of CVS, its capabilities, and to a lesser extent its
Basic knowledge of CVS, it's capabilities, and to a lesser extent it's
limitations are beyond the scope of this document. See the CVS
website and the "References" section for more information. That said,
the following general rules should always be adhered to:
@@ -134,7 +134,7 @@ CHECKING OUT SOURCES
will checkout using the default implicit :ext: method and will
need to provide an authorized username. Be sure to use the "-P"
checkout option to remove (prune) empty directories. The "-z9"
global CVS option is encouraged to minimze network utilization.
global CVS option is encouranged to minimze network utilization.
FROM HEAD:
@@ -163,7 +163,7 @@ CHECKING OUT SOURCES
The process for checking out a given revision number is pretty
much a matter of knowing which revision tag name is desired, and
then checking out with that symbolic tag name:
As anonymous:
cvs -z9 -d :pserver:anonymous@cvs.sf.net:/cvsroot/brlcad checkout -P -r <tagname> brlcad
@@ -196,7 +196,7 @@ CHECKING IN SOURCES
developers.
If you are given commit access, you are expected to
read and follow this policy and its guidelines as well as the
read and follow this policy and it's guidelines as well as the
developer's guide.
@@ -234,8 +234,8 @@ CHECKING IN SOURCES
message, e.g. "moved from librt/bool.c to src/librt/bool.c".
TO HEAD:
TO HEAD:
It's very important that the main CVS HEAD revision be a "mostly"
stable code base so that at any given time users may download the
latest source, get it to compile with minimal effort, and have the
@@ -339,14 +339,14 @@ TAG NAMING CONVENTIONS
compatible.
<date> := YYYYMMDD (e.g., 20021231)
When creating tags, the date a tag is made is sometimes noted
and useful or even recommended. The format of the date is
YYYYMMDD and should correspond to tag creation dates. Branch
and release tags should not include a date in the tag name.
<comment>
For branches the comment is "branch". For releases, it is
left blank. For other miscellaneous tags, the comment is up
to the person tagging.
@@ -412,7 +412,7 @@ TAG NAMING CONVENTIONS
postmerge[-<revision>][-<date>]-<comment>
Example: postmerge-20040315-windows
Example: postmerge-20040315-windows
The <comment> should be a simple identifying keyword. The
branch keyword being merged suffices quite well. A date is
@@ -431,7 +431,7 @@ TAG NAMING CONVENTIONS
<keyword>[-<revision>][-<date>]-pre
<keyword>[-<revision>][-<date>]-post
Examples: hartley-6-0-pre ctj-4-5-post offsite-5-3-pre
@@ -442,7 +442,7 @@ TAG NAMING CONVENTIONS
informative tag names should be used. Dates are highly
recommended as CVS tags are not associated by date, but rather
to the individual revision of a file.
<keyword>[-<revision>][-<date>][-<comment>]
When in doubt, tag. It's easy to remove or rename tags, but it
@@ -583,7 +583,7 @@ MERGING A BRANCH
cause CVS to not expand the CVS variables such as \$Revision\$ and
\$Id\$. If those keyword variables are expanded, you're likely to
have many conflicts depending on time-stamps.
If the branch being checked in an extensive set of changes,
testing is essential. It is also a good idea to warn other
developers of what you are planning to do. You should indicate
@@ -781,7 +781,7 @@ XFree86 Direct Rendering Infrastructure CvsPolicy
http://dri.sourceforge.net/cgi-bin/moin.cgi/CvsPolicy
http://dri.sourceforge.net/doc/cvspolicy.txt
Zope
Zope
http://dev.zope.org/CVS/ZopeReleasePolicy
FreeBSD
@@ -791,6 +791,6 @@ AT&T SML/NJ
http://www.smlnj.org/DEV/policy.html
http://cm.bell-labs.com/cm/cs/what/smlnj/DEV/policy.html
---
---
This document was initially written in 2002 and later almost
completely rewritten in 2004 by Christopher Sean Morrison.
+27 -27
View File
@@ -981,18 +981,18 @@ Hence, the GENERAL ARB menu is a list of edges to move:
.sp
.ce 13
GENERAL ARB MENU
move edge 12
move edge 23
move edge 34
move edge 14
move edge 15
move edge 26
move edge 56
move edge 67
move edge 78
move edge 58
move edge 37
move edge 48
move edge 12
move edge 23
move edge 34
move edge 14
move edge 15
move edge 26
move edge 56
move edge 67
move edge 78
move edge 58
move edge 37
move edge 48
.sp
The edge to be moved is selected from this menu and is then moved
using the data tablet and pen. When the pen is pressed, the line
@@ -1005,7 +1005,7 @@ for edge 58 are planes 4378 and 1265 (see Figure 6).
The information printed on the bottom of the screen is the x, y, z
coordinates of the eight vertices:
.ce 5
vertex coordinates
vertex coordinates
1,2 x1 y1 z1 x2 y2 y3
3,4 x3 y3 z3 x4 y4 z4
5,6 x5 y5 z5 x6 y6 z6
@@ -1074,13 +1074,13 @@ During solid editing, the parameters of the TGC are constantly updated
on the bottom of the screen:
.ce 7
V x y z
V x y z
H x y z |H| a b g rot fb
A x y z |A|
B x y z |B|
c |c|
d |d|
AxB a b g rot fb
A x y z |A|
B x y z |B|
c |c|
d |d|
AxB a b g rot fb
where "a", "b", "g" are the direction cosines and "rot" and "fb" are
the rotation and fallback angles of the listed vector.
@@ -1103,9 +1103,9 @@ the menu:
.ce 4
ELLG MENU
scale A
scale B
scale C
scale A
scale B
scale C
The scaling of these vectors is done using the data tablet and pen in
exactly the same manner as in object scaling. The "p" keyboard
@@ -1115,7 +1115,7 @@ The parameters of the ELLG are continually updated on the bottom of
the screen during solid editing:
.ce 4
V x y z
V x y z
A x y z |A| a b g rot fb
B x y z |B| a b g rot fb
C x y z |C| a b g rot fb
@@ -1141,7 +1141,7 @@ The parameter editing of the TOR consists of scaling the radii, hence
the menu contains only two members:
.ce 3
TORUS MENU
TORUS MENU
scale radius 1
scale radius 2
@@ -1153,9 +1153,9 @@ The parameters of the TOR are continually updated on the bottom of the
screen during solid editing:
.ce 4
V x y z
r1 |r1|
r2 |r2|
V x y z
r1 |r1|
r2 |r2|
N x y z a b g rot fb
where "a", "b", "g" are the direction cosines and "rot" and "fb" are
+5 -5
View File
@@ -1,9 +1,9 @@
The History of BRL-CAD
======================
The BRL-CAD PACKAGE
The BRL CAD PACKAGE
Short Summary
In FY87 two major releases of the BRL-CAD Package software were
In FY87 two major releases of the BRL CAD Package software were
made (Feb-87, July-87), along with two editions of the associated
400 page manual. The package includes a powerful solid modeling
capability and a network-distributed image-processing capability.
@@ -43,7 +43,7 @@ In terms of geometrical representation of data, BRL-CAD supports:
base which has been used to model > 150 target descriptions,
domestic and foreign
extensions to include both a Naval Academy spline
extensions to include both a Naval Academy spline
(Uniform B-Spline Surface) as well as a U. of
Utah spline (Non-Uniform Rational B-Spline [NURB] Surface)
developed under NSF and DARPA sponsorship
@@ -100,7 +100,7 @@ BRL-CAD environment is the leading candidate for that role.
----
To obtain a copy of the BRL-CAD Package distribution, you must send
To obtain a copy of the BRL CAD Package distribution, you must send
enough magnetic tape for 20 Mbytes of data. Standard nine-track
half-inch magtape is the strongly preferred format, and can be written
at either 1600 or 6250 bpi, in TAR format with 10k byte records. For
@@ -109,7 +109,7 @@ cartridges can also be accommodated. With your tape, you must also
enclose a letter indicating
(a) who you are,
(b) what the BRL-CAD package is to be used for,
(b) what the BRL CAD package is to be used for,
(c) the equipment and operating system(s) you plan on using,
(d) that you agree to the conditions listed below.
-3
View File
@@ -1,5 +1,2 @@
# $Id$
SUBDIRS = ReleaseNotes manuals
include $(top_srcdir)/misc/Makefile.defs
+3 -5
View File
@@ -2,8 +2,6 @@
SUBDIRS = Rel5.0 Rel6.0
htmldocsdir = $(BRLCAD_DATA)/html/ReleaseNotes
htmldocs_DATA = email2.0.html email3.0.html email3.1.html email4.0.html email4.4.html email5.0.html index.html
EXTRA_DIST = $(htmldocs_DATA)
include $(top_srcdir)/misc/Makefile.defs
stuffdir = $(prefix)/html/ReleaseNotes
stuff_DATA = email2.0.html email3.0.html email3.1.html email4.0.html email4.4.html email5.0.html index.html
EXTRA_DIST = $(stuff_DATA)
+4 -7
View File
@@ -1,10 +1,7 @@
# $Id$
SUBDIRS = Summary
htmldocsdir = $(BRLCAD_DATA)/html/ReleaseNotes/Rel5.0
htmldocs_DATA = deprecated.html index.html new_cmds.html new_libs.html
EXTRA_DIST = $(htmldocs_DATA)
include $(top_srcdir)/misc/Makefile.defs
stuffdir = $(prefix)/html/ReleaseNotes/Rel5.0
stuff_DATA = deprecated.html index.html new_cmds.html new_libs.html
EXTRA_DIST = $(stuff_DATA)
@@ -1,81 +1,7 @@
# $Id$
htmldocsdir = $(BRLCAD_DATA)/html/ReleaseNotes/Rel5.0/Summary
htmldocs_DATA = \
activem.gif \
activep.gif \
collapse.gif \
expand.gif \
first.gif \
home.gif \
ielogo.gif \
img001.jpg \
img002.jpg \
img003.jpg \
img004.jpg \
img005.jpg \
img006.jpg \
img007.jpg \
img008.jpg \
img009.jpg \
img010.jpg \
img011.jpg \
img012.jpg \
img013.jpg \
img014.jpg \
img015.jpg \
img016.jpg \
img017.jpg \
img018.jpg \
img019.jpg \
index.html \
info.gif \
last.gif \
next.gif \
pptani.gif \
prev.gif \
sld001.htm \
sld002.htm \
sld003.htm \
sld004.htm \
sld005.htm \
sld006.htm \
sld007.htm \
sld008.htm \
sld009.htm \
sld010.htm \
sld011.htm \
sld012.htm \
sld013.htm \
sld014.htm \
sld015.htm \
sld016.htm \
sld017.htm \
sld018.htm \
sld019.htm \
space.gif \
text.gif \
tsld001.htm \
tsld002.htm \
tsld003.htm \
tsld004.htm \
tsld005.htm \
tsld006.htm \
tsld007.htm \
tsld008.htm \
tsld009.htm \
tsld010.htm \
tsld011.htm \
tsld012.htm \
tsld013.htm \
tsld014.htm \
tsld015.htm \
tsld016.htm \
tsld017.htm \
tsld018.htm \
tsld019.htm
EXTRA_DIST = $(htmldocs_DATA)
include $(top_srcdir)/misc/Makefile.defs
stuffdir = $(prefix)/html/ReleaseNotes/Rel5.0/Summary
stuff_DATA = activem.gif activep.gif collapse.gif expand.gif first.gif home.gif ielogo.gif img001.jpg img002.jpg img003.jpg img004.jpg img005.jpg img006.jpg img007.jpg img008.jpg img009.jpg img010.jpg img011.jpg img012.jpg img013.jpg img014.jpg img015.jpg img016.jpg img017.jpg img018.jpg img019.jpg index.htm index.html info.gif last.gif next.gif pptani.gif prev.gif sld001.htm sld002.htm sld003.htm sld004.htm sld005.htm sld006.htm sld007.htm sld008.htm sld009.htm sld010.htm sld011.htm sld012.htm sld013.htm sld014.htm sld015.htm sld016.htm sld017.htm sld018.htm sld019.htm space.gif text.gif tsld001.htm tsld002.htm tsld003.htm tsld004.htm tsld005.htm tsld006.htm tsld007.htm tsld008.htm tsld009.htm tsld010.htm tsld011.htm tsld012.htm tsld013.htm tsld014.htm tsld015.htm tsld016.htm tsld017.htm tsld018.htm tsld019.htm
EXTRA_DIST = $(stuff_DATA)
+60
View File
@@ -0,0 +1,60 @@
<html>
<head>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<title>What’s New in BRL-CAD™ Release 5.0?</title>
</head>
<BODY >
<CENTER>
<h1>What’s New in BRL-CAD™ Release 5.0?</h1>
<h4>5/4/99</h4>
<br><h2> <A HREF="sld001.htm">Click here to start</A>
</h2><br>
</center>
<center>
<table width=90%>
<tr>
<td valign=top align=left width=50%>
<h3><u>Table of Contents</u></h3>
<P ALIGN=LEFT><A HREF="sld001.htm">What’s New in BRL-CAD™ Release 5.0?</A></P>
<P ALIGN=LEFT><A HREF="sld002.htm">Major New Features of BRL-CAD™ 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld003.htm">Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld004.htm">Benefits of Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld005.htm">Tclifying BRL-CAD? Applications</A></P>
<P ALIGN=LEFT><A HREF="sld006.htm">Tcl/Tk-based GUI for MGED</A></P>
<P ALIGN=LEFT><A HREF="sld007.htm">Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</A></P>
<P ALIGN=LEFT><A HREF="sld008.htm">New Utilities</A></P>
<P ALIGN=LEFT><A HREF="sld009.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld010.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld011.htm">Libraries</A></P>
<P ALIGN=LEFT><A HREF="sld012.htm">Major New Features of MGED for 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld013.htm">Major New Features of MGED for 5.0, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld014.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld015.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld016.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld017.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld018.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld019.htm">BRL-CAD™ Projection Shader</A></P>
</td>
<td valign=top width=50%>
<strong>Author: </strong>Paul J. Tanenbaum
<P> <strong>Email: </strong> <A HREF="MAILTO:pjt@arl.mil">pjt@arl.mil</A> </P>
</td>
</tr>
</table>
</center>
<br>
<a href="../index.html"> BRL-CAD Release 5.0 Release Notes </a>
</body>
</html>
+58 -54
View File
@@ -1,56 +1,60 @@
<html>
<head>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<title>What's New in BRL-CAD Release 5.0?</title>
</head>
<BODY >
<CENTER>
<h1>What's New in BRL-CAD Release 5.0?</h1>
<h4>5/4/99</h4>
<br><h2> <A HREF="sld001.htm">Click here to start</A>
</h2><br>
</center>
<center>
<table width=90%>
<tr>
<td valign=top align=left width=50%>
<h3><u>Table of Contents</u></h3>
<P ALIGN=LEFT><A HREF="sld001.htm">What's New in BRL-CAD Release 5.0?</A></P>
<P ALIGN=LEFT><A HREF="sld002.htm">Major New Features of BRL-CAD 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld003.htm">Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld004.htm">Benefits of Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld005.htm">Tclifying BRL-CAD? Applications</A></P>
<P ALIGN=LEFT><A HREF="sld006.htm">Tcl/Tk-based GUI for MGED</A></P>
<P ALIGN=LEFT><A HREF="sld007.htm">Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</A></P>
<P ALIGN=LEFT><A HREF="sld008.htm">New Utilities</A></P>
<P ALIGN=LEFT><A HREF="sld009.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld010.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld011.htm">Libraries</A></P>
<P ALIGN=LEFT><A HREF="sld012.htm">Major New Features of MGED for 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld013.htm">Major New Features of MGED for 5.0, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld014.htm">BRL-CAD Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld015.htm">BRL-CAD Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld016.htm">BRL-CAD Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld017.htm">BRL-CAD Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld018.htm">BRL-CAD Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld019.htm">BRL-CAD Projection Shader</A></P>
</td>
<td valign=top width=50%>
<strong>Author: </strong>BRL-CAD Developers (Paul J. Tanenbaum)
<P> <strong>Email: </strong> <A HREF="MAILTO:devs@brlcad.org">devs@brlcad.org</A> </P>
</td>
</tr>
</table>
</center>
<html>
<head>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<title>What’s New in BRL-CAD™ Release 5.0?</title>
</head>
<BODY >
<CENTER>
<h1>What’s New in BRL-CAD™ Release 5.0?</h1>
<h4>5/4/99</h4>
<br><h2> <A HREF="sld001.htm">Click here to start</A>
</h2><br>
</center>
<center>
<table width=90%>
<tr>
<td valign=top align=left width=50%>
<h3><u>Table of Contents</u></h3>
<P ALIGN=LEFT><A HREF="sld001.htm">What’s New in BRL-CAD™ Release 5.0?</A></P>
<P ALIGN=LEFT><A HREF="sld002.htm">Major New Features of BRL-CAD™ 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld003.htm">Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld004.htm">Benefits of Tcl/Tk</A></P>
<P ALIGN=LEFT><A HREF="sld005.htm">Tclifying BRL-CAD? Applications</A></P>
<P ALIGN=LEFT><A HREF="sld006.htm">Tcl/Tk-based GUI for MGED</A></P>
<P ALIGN=LEFT><A HREF="sld007.htm">Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</A></P>
<P ALIGN=LEFT><A HREF="sld008.htm">New Utilities</A></P>
<P ALIGN=LEFT><A HREF="sld009.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld010.htm">New Utilities, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld011.htm">Libraries</A></P>
<P ALIGN=LEFT><A HREF="sld012.htm">Major New Features of MGED for 5.0</A></P>
<P ALIGN=LEFT><A HREF="sld013.htm">Major New Features of MGED for 5.0, cont.</A></P>
<P ALIGN=LEFT><A HREF="sld014.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld015.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld016.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld017.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld018.htm">BRL-CAD™ Projection Shader</A></P>
<P ALIGN=LEFT><A HREF="sld019.htm">BRL-CAD™ Projection Shader</A></P>
</td>
<td valign=top width=50%>
<strong>Author: </strong>Paul J. Tanenbaum
<P> <strong>Email: </strong> <A HREF="MAILTO:pjt@arl.mil">pjt@arl.mil</A> </P>
</td>
</tr>
</table>
</center>
<br>
<a href="../index.html"> BRL-CAD Release 5.0 Release Notes </a>
</body>
</html>
</body>
</html>
+49 -49
View File
@@ -1,49 +1,49 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>What’s New</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img001.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="first.gif" BORDER=0>
<IMG SRC="prev.gif" BORDER=0>
<A HREF="sld002.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld001.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 1 of 19</P>
</CENTER>
<!-- <UL>
ARMY RESEARCH LABORATORY</UL></P>
<P><UL>
<H2>What’s New in BRL-CAD™ Release 5.0?</H2>
</UL></P>
<P><UL>
<H2>
</H2>
</UL><UL>
<H2>Paul J. Tanenbaum
</H2>
</UL><UL>
<H2>
</H2>
</UL><UL>
<H2>4 May 1999</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>What’s New</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img001.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="first.gif" BORDER=0>
<IMG SRC="prev.gif" BORDER=0>
<A HREF="sld002.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld001.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 1 of 19</P>
</CENTER>
<!-- <UL>
ARMY RESEARCH LABORATORY</UL></P>
<P><UL>
<H2>What’s New in BRL-CAD™ Release 5.0?</H2>
</UL></P>
<P><UL>
<H2>
</H2>
</UL><UL>
<H2>Paul J. Tanenbaum
</H2>
</UL><UL>
<H2>
</H2>
</UL><UL>
<H2>4 May 1999</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+66 -66
View File
@@ -1,66 +1,66 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img002.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld001.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld003.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld002.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 2 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of BRL-CAD™ 5.0</H2>
</UL></P>
<P><UL>
<LI><H2>Modern graphical user interface (GUI)
</H2>
</UL><UL>
<LI><H2>Integrated software development medium
</H2>
</UL><UL>
<LI><H2>Controllability from other applications
</H2>
</UL><UL>
<LI><H2>Dynamic geometry
</H2>
</UL><UL>
<LI><H2>Dozens of new utilities (stand-alone programs)
</H2>
</UL><UL>
<LI><H2>New application development libraries and reorganization of existing libraries
</H2>
</UL><UL>
<LI><H2>HTML documentation
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img002.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld001.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld003.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld002.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 2 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of BRL-CAD™ 5.0</H2>
</UL></P>
<P><UL>
<LI><H2>Modern graphical user interface (GUI)
</H2>
</UL><UL>
<LI><H2>Integrated software development medium
</H2>
</UL><UL>
<LI><H2>Controllability from other applications
</H2>
</UL><UL>
<LI><H2>Dynamic geometry
</H2>
</UL><UL>
<LI><H2>Dozens of new utilities (stand-alone programs)
</H2>
</UL><UL>
<LI><H2>New application development libraries and reorganization of existing libraries
</H2>
</UL><UL>
<LI><H2>HTML documentation
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+45 -45
View File
@@ -1,45 +1,45 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tcl/Tk</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img003.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld002.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld004.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld003.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 3 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tcl/Tk</H2>
</UL></P>
<P><UL>
<LI>Tcl is an embeddable, full-function interpreted command language
</UL><UL>
<LI>Tk is a toolkit, based on Tcl, for building user interfaces, etc.
</UL><UL>
<LI> Created by John Ousterhout
</UL><UL>
&#060john.ousterhout@scriptics.com&#062
</UL><UL>
<LI> Available from ftp://ftp.scriptics.com/pub/tcl</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tcl/Tk</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img003.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld002.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld004.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld003.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 3 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tcl/Tk</H2>
</UL></P>
<P><UL>
<LI>Tcl is an embeddable, full-function interpreted command language
</UL><UL>
<LI>Tk is a toolkit, based on Tcl, for building user interfaces, etc.
</UL><UL>
<LI> Created by John Ousterhout
</UL><UL>
&#060john.ousterhout@scriptics.com&#062
</UL><UL>
<LI> Available from ftp://ftp.scriptics.com/pub/tcl</UL></P>
<P> -->
</Body>
</HTML>
+43 -43
View File
@@ -1,43 +1,43 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Benefits of Tcl/Tk</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img004.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld003.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld005.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld004.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 4 of 19</P>
</CENTER>
<!-- <UL>
<H2>Benefits of Tcl/Tk</H2>
</UL></P>
<P><UL>
<LI> Rapid development
</UL><UL>
<LI> Ease of providing applications a powerful scripting language
</UL><UL>
<LI> An excellent “glue language”
</UL><UL>
<LI> User convenience</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Benefits of Tcl/Tk</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img004.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld003.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld005.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld004.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 4 of 19</P>
</CENTER>
<!-- <UL>
<H2>Benefits of Tcl/Tk</H2>
</UL></P>
<P><UL>
<LI> Rapid development
</UL><UL>
<LI> Ease of providing applications a powerful scripting language
</UL><UL>
<LI> An excellent “glue language”
</UL><UL>
<LI> User convenience</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tclifying BRL-CAD? Applications</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img005.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld004.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld006.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld005.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 5 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tclifying BRL-CAD? Applications</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tclifying BRL-CAD? Applications</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img005.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld004.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld006.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld005.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 5 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tclifying BRL-CAD? Applications</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tcl/Tk-based GUI for MGED</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img006.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld005.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld007.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld006.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 6 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tcl/Tk-based GUI for MGED</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Tcl/Tk-based GUI for MGED</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img006.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld005.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld007.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld006.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 6 of 19</P>
</CENTER>
<!-- <UL>
<H2>Tcl/Tk-based GUI for MGED</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Example of Gluing Applications Together:</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img007.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld006.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld008.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld007.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 7 of 19</P>
</CENTER>
<!-- <UL>
<H2>Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Example of Gluing Applications Together:</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img007.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld006.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld008.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld007.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 7 of 19</P>
</CENTER>
<!-- <UL>
<H2>Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+48 -48
View File
@@ -1,48 +1,48 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img008.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld007.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld009.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld008.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 8 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities</H2>
</UL></P>
<P><UL>
<LI><H2>Geometry Conversion
</H2>
<UL>
<LI>From BRL-CAD to...
<BR> ACAD (General Dynamics) for XPATCH
<BR> Alias|Wavefront
<BR> Compaq (Digital Equipment) OFF
<BR> VRML
<LI>To BRL-CAD from...
<BR> Cyberware digitization
<BR> NASTRAN
<BR> 3D Systems stereolithography </UL></UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img008.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld007.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld009.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld008.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 8 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities</H2>
</UL></P>
<P><UL>
<LI><H2>Geometry Conversion
</H2>
<UL>
<LI>From BRL-CAD to...
<BR> ACAD (General Dynamics) for XPATCH
<BR> Alias|Wavefront
<BR> Compaq (Digital Equipment) OFF
<BR> VRML
<LI>To BRL-CAD from...
<BR> Cyberware digitization
<BR> NASTRAN
<BR> 3D Systems stereolithography </UL></UL></P>
<P> -->
</Body>
</HTML>
+48 -48
View File
@@ -1,48 +1,48 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img009.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld008.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld010.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld009.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 9 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Database Maintenance
</H2>
<UL>
<LI>Compare .g files and report differences
<LI>Reorganize region IDs
<LI>Convert NMGs to simpler solids
</UL></UL><UL>
<LI><H2>Image Support
</H2>
<UL>
<LI> PNG tools (conversion, display, etc.)
<LI>YUV color model</UL></UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img009.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld008.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld010.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld009.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 9 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Database Maintenance
</H2>
<UL>
<LI>Compare .g files and report differences
<LI>Reorganize region IDs
<LI>Convert NMGs to simpler solids
</UL></UL><UL>
<LI><H2>Image Support
</H2>
<UL>
<LI> PNG tools (conversion, display, etc.)
<LI>YUV color model</UL></UL></P>
<P> -->
</Body>
</HTML>
+45 -45
View File
@@ -1,45 +1,45 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img010.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld009.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld011.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld010.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 10 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Miscellaneous
</H2>
<UL>
<LI>Tcl/Tk windowing shell providing interface to BRL-CAD library routines
<LI>Cascading and time estimation added to animation capabilities
<LI>Haar wavelet decomposition & reconstruction
<LI>Barycentric combination
<LI>
</UL></UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img010.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld009.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld011.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld010.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 10 of 19</P>
</CENTER>
<!-- <UL>
<H2>New Utilities, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Miscellaneous
</H2>
<UL>
<LI>Tcl/Tk windowing shell providing interface to BRL-CAD library routines
<LI>Cascading and time estimation added to animation capabilities
<LI>Haar wavelet decomposition & reconstruction
<LI>Barycentric combination
<LI>
</UL></UL></P>
<P> -->
</Body>
</HTML>
+62 -62
View File
@@ -1,62 +1,62 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Libraries</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img011.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld010.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld012.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld011.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 11 of 19</P>
</CENTER>
<!-- <UL>
<H2>Libraries</H2>
</UL></P>
<P><UL>
<LI><H2>libbn
</H2>
</UL><UL>
<H2> Numerical computation, quaternions, wavelets, ...
</H2>
</UL><UL>
<LI><H2>libbu
</H2>
</UL><UL>
<H2> Utilities: memory mgmt, parallel processing, ...
</H2>
</UL><UL>
<LI><H2>libdm
</H2>
</UL><UL>
<H2> Display manager: X, Open GL, PostScript, ...
</H2>
</UL><UL>
<LI><H2>librt Ray tracing
</H2>
</UL><UL>
<LI><H2>libpng PNG
</H2>
</UL><UL>
<LI><H2>libz Data compression</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Libraries</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img011.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld010.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld012.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld011.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 11 of 19</P>
</CENTER>
<!-- <UL>
<H2>Libraries</H2>
</UL></P>
<P><UL>
<LI><H2>libbn
</H2>
</UL><UL>
<H2> Numerical computation, quaternions, wavelets, ...
</H2>
</UL><UL>
<LI><H2>libbu
</H2>
</UL><UL>
<H2> Utilities: memory mgmt, parallel processing, ...
</H2>
</UL><UL>
<LI><H2>libdm
</H2>
</UL><UL>
<H2> Display manager: X, Open GL, PostScript, ...
</H2>
</UL><UL>
<LI><H2>librt Ray tracing
</H2>
</UL><UL>
<LI><H2>libpng PNG
</H2>
</UL><UL>
<LI><H2>libz Data compression</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+56 -56
View File
@@ -1,56 +1,56 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img012.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld011.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld013.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld012.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 12 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of MGED for 5.0</H2>
</UL></P>
<P><UL>
<LI><H2>Integration of frame buffer
</H2>
<UL>
<LI>render geometry for disambiguation/debugging
<LI>register geometry with imported imagery
</UL></UL><UL>
<LI><H2>Integration of ray tracing
</H2>
<UL>
<LI>query rays
<LI>click to edit, click to render
</UL></UL><UL>
<LI><H2>Multipane mode
</H2>
</UL><UL>
<LI><H2>Snap-to-grid mode
</H2>
</UL><UL>
<LI><H2>Networked collaboration, multiple display managers</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img012.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld011.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld013.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld012.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 12 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of MGED for 5.0</H2>
</UL></P>
<P><UL>
<LI><H2>Integration of frame buffer
</H2>
<UL>
<LI>render geometry for disambiguation/debugging
<LI>register geometry with imported imagery
</UL></UL><UL>
<LI><H2>Integration of ray tracing
</H2>
<UL>
<LI>query rays
<LI>click to edit, click to render
</UL></UL><UL>
<LI><H2>Multipane mode
</H2>
</UL><UL>
<LI><H2>Snap-to-grid mode
</H2>
</UL><UL>
<LI><H2>Networked collaboration, multiple display managers</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+54 -54
View File
@@ -1,54 +1,54 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img013.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld012.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld014.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld013.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 13 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of MGED for 5.0, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Uniform mouse-based manipulation of
</H2>
</UL><UL>
<H2> geometry and view
</H2>
</UL><UL>
<LI><H2>GUI control panels…
</H2>
<UL>
<LI>ray-traced rendering
<LI>animation
<LI>color editing
<LI>snap to grid
<LI>angle/distance cursor
<LI>shaders (glass, camo, projection, …)
</UL></UL><UL>
<LI><H2>Command history and command-line editing</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img013.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld012.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld014.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld013.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 13 of 19</P>
</CENTER>
<!-- <UL>
<H2>Major New Features of MGED for 5.0, cont.</H2>
</UL></P>
<P><UL>
<LI><H2>Uniform mouse-based manipulation of
</H2>
</UL><UL>
<H2> geometry and view
</H2>
</UL><UL>
<LI><H2>GUI control panels…
</H2>
<UL>
<LI>ray-traced rendering
<LI>animation
<LI>color editing
<LI>snap to grid
<LI>angle/distance cursor
<LI>shaders (glass, camo, projection, …)
</UL></UL><UL>
<LI><H2>Command history and command-line editing</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img014.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld013.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld015.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld014.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 14 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img014.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld013.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld015.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld014.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 14 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img015.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld014.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld016.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld015.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 15 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img015.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld014.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld016.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld015.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 15 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img016.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld015.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld017.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld016.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 16 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img016.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld015.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld017.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld016.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 16 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img017.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld016.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld018.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld017.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 17 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img017.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld016.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld018.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld017.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 17 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img018.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld017.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld019.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld018.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 18 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img018.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld017.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<A HREF="sld019.htm"><IMG SRC="next.gif" BORDER=0 ALT="Next"></A>
<A HREF="sld019.htm"><IMG SRC="last.gif" BORDER=0 ALT="Last"></A>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld018.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 18 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
+35 -35
View File
@@ -1,35 +1,35 @@
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img019.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld018.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<IMG SRC="next.gif" BORDER=0>
<IMG SRC="last.gif" BORDER=0>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.html"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld019.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 19 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
<!-- Presentation generated by Internet Assistant for Microsoft PowerPoint 97 -->
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for Microsoft PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<CENTER>
<TABLE WIDTH=100%>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<IMG SRC="img019.jpg" usemap="#Objmap" WIDTH=320 HEIGHT=240 BORDER=0>
</TD> </TR>
<TR> <TD WIDTH=100% ALIGN=CENTER>
<A HREF="sld001.htm"><IMG SRC="first.gif" BORDER=0 ALT="First"></A>
<A HREF="sld018.htm"><IMG SRC="prev.gif" BORDER=0 ALT="Previous"></A>
<IMG SRC="next.gif" BORDER=0>
<IMG SRC="last.gif" BORDER=0>
<IMG SRC="space.gif" BORDER=0>
<A HREF="index.htm"><IMG SRC="info.gif" BORDER=0 ALT="Index"></A>
<A HREF="tsld019.htm"><IMG SRC="text.gif" BORDER=0 ALT="Text"></A>
</TD> </TR>
</TABLE>
<P>Slide 19 of 19</P>
</CENTER>
<!-- <UL>
<H2>BRL-CAD™ Projection Shader</H2>
</UL></P>
<P> -->
</Body>
</HTML>
@@ -1,41 +1,41 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>What’s New</TITLE>
</HEAD>
<BODY >
<H1>What’s New in BRL-CAD™ Release 5.0?</H1>
<P><UL>
ARMY RESEARCH LABORATORY</UL></P>
<P><UL>
<H2>
</H2>
</UL><UL>
<H2>Paul J. Tanenbaum
</H2>
</UL><UL>
<H2>
</H2>
</UL><UL>
<H2>4 May 1999</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100></TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld002.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld001.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>What’s New</TITLE>
</HEAD>
<BODY >
<H1>What’s New in BRL-CAD™ Release 5.0?</H1>
<P><UL>
ARMY RESEARCH LABORATORY</UL></P>
<P><UL>
<H2>
</H2>
</UL><UL>
<H2>Paul J. Tanenbaum
</H2>
</UL><UL>
<H2>
</H2>
</UL><UL>
<H2>4 May 1999</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100></TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld002.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld001.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,58 +1,58 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of BRL-CAD™ 5.0</H1>
<P><UL>
<LI><H2>Modern graphical user interface (GUI)
</H2>
</UL><UL>
<LI><H2>Integrated software development medium
</H2>
</UL><UL>
<LI><H2>Controllability from other applications
</H2>
</UL><UL>
<LI><H2>Dynamic geometry
</H2>
</UL><UL>
<LI><H2>Dozens of new utilities (stand-alone programs)
</H2>
</UL><UL>
<LI><H2>New application development libraries and reorganization of existing libraries
</H2>
</UL><UL>
<LI><H2>HTML documentation
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld001.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld003.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld002.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of BRL-CAD™ 5.0</H1>
<P><UL>
<LI><H2>Modern graphical user interface (GUI)
</H2>
</UL><UL>
<LI><H2>Integrated software development medium
</H2>
</UL><UL>
<LI><H2>Controllability from other applications
</H2>
</UL><UL>
<LI><H2>Dynamic geometry
</H2>
</UL><UL>
<LI><H2>Dozens of new utilities (stand-alone programs)
</H2>
</UL><UL>
<LI><H2>New application development libraries and reorganization of existing libraries
</H2>
</UL><UL>
<LI><H2>HTML documentation
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL><UL>
<LI><H2>
</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld001.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld003.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld002.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,37 +1,37 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tcl/Tk</TITLE>
</HEAD>
<BODY >
<H1>Tcl/Tk</H1>
<P><UL>
<LI>Tcl is an embeddable, full-function interpreted command language
</UL><UL>
<LI>Tk is a toolkit, based on Tcl, for building user interfaces, etc.
</UL><UL>
<LI> Created by John Ousterhout
</UL><UL>
&#060john.ousterhout@scriptics.com&#062
</UL><UL>
<LI> Available from ftp://ftp.scriptics.com/pub/tcl</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld002.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld004.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld003.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tcl/Tk</TITLE>
</HEAD>
<BODY >
<H1>Tcl/Tk</H1>
<P><UL>
<LI>Tcl is an embeddable, full-function interpreted command language
</UL><UL>
<LI>Tk is a toolkit, based on Tcl, for building user interfaces, etc.
</UL><UL>
<LI> Created by John Ousterhout
</UL><UL>
&#060john.ousterhout@scriptics.com&#062
</UL><UL>
<LI> Available from ftp://ftp.scriptics.com/pub/tcl</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld002.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld004.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld003.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,35 +1,35 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Benefits of Tcl/Tk</TITLE>
</HEAD>
<BODY >
<H1>Benefits of Tcl/Tk</H1>
<P><UL>
<LI> Rapid development
</UL><UL>
<LI> Ease of providing applications a powerful scripting language
</UL><UL>
<LI> An excellent “glue language”
</UL><UL>
<LI> User convenience</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld003.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld005.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld004.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Benefits of Tcl/Tk</TITLE>
</HEAD>
<BODY >
<H1>Benefits of Tcl/Tk</H1>
<P><UL>
<LI> Rapid development
</UL><UL>
<LI> Ease of providing applications a powerful scripting language
</UL><UL>
<LI> An excellent “glue language”
</UL><UL>
<LI> User convenience</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld003.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld005.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld004.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tclifying BRL-CAD? Applications</TITLE>
</HEAD>
<BODY >
<H1>Tclifying BRL-CAD? Applications</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld004.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld006.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld005.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tclifying BRL-CAD? Applications</TITLE>
</HEAD>
<BODY >
<H1>Tclifying BRL-CAD? Applications</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld004.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld006.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld005.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tcl/Tk-based GUI for MGED</TITLE>
</HEAD>
<BODY >
<H1>Tcl/Tk-based GUI for MGED</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld005.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld007.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld006.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Tcl/Tk-based GUI for MGED</TITLE>
</HEAD>
<BODY >
<H1>Tcl/Tk-based GUI for MGED</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld005.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld007.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld006.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Example of Gluing Applications Together:</TITLE>
</HEAD>
<BODY >
<H1>Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld006.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld008.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld007.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Example of Gluing Applications Together:</TITLE>
</HEAD>
<BODY >
<H1>Example of Gluing Applications Together: Interfacing BRL-CAD and MUVES</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld006.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld008.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld007.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,40 +1,40 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities</TITLE>
</HEAD>
<BODY >
<H1>New Utilities</H1>
<P><UL>
<LI><H2>Geometry Conversion
</H2>
<UL>
<LI>From BRL-CAD to...
<BR> ACAD (General Dynamics) for XPATCH
<BR> Alias|Wavefront
<BR> Compaq (Digital Equipment) OFF
<BR> VRML
<LI>To BRL-CAD from...
<BR> Cyberware digitization
<BR> NASTRAN
<BR> 3D Systems stereolithography </UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld007.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld009.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld008.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities</TITLE>
</HEAD>
<BODY >
<H1>New Utilities</H1>
<P><UL>
<LI><H2>Geometry Conversion
</H2>
<UL>
<LI>From BRL-CAD to...
<BR> ACAD (General Dynamics) for XPATCH
<BR> Alias|Wavefront
<BR> Compaq (Digital Equipment) OFF
<BR> VRML
<LI>To BRL-CAD from...
<BR> Cyberware digitization
<BR> NASTRAN
<BR> 3D Systems stereolithography </UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld007.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld009.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld008.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,40 +1,40 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<H1>New Utilities, cont.</H1>
<P><UL>
<LI><H2>Database Maintenance
</H2>
<UL>
<LI>Compare .g files and report differences
<LI>Reorganize region IDs
<LI>Convert NMGs to simpler solids
</UL></UL><UL>
<LI><H2>Image Support
</H2>
<UL>
<LI> PNG tools (conversion, display, etc.)
<LI>YUV color model</UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld008.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld010.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld009.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<H1>New Utilities, cont.</H1>
<P><UL>
<LI><H2>Database Maintenance
</H2>
<UL>
<LI>Compare .g files and report differences
<LI>Reorganize region IDs
<LI>Convert NMGs to simpler solids
</UL></UL><UL>
<LI><H2>Image Support
</H2>
<UL>
<LI> PNG tools (conversion, display, etc.)
<LI>YUV color model</UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld008.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld010.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld009.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,37 +1,37 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<H1>New Utilities, cont.</H1>
<P><UL>
<LI><H2>Miscellaneous
</H2>
<UL>
<LI>Tcl/Tk windowing shell providing interface to BRL-CAD library routines
<LI>Cascading and time estimation added to animation capabilities
<LI>Haar wavelet decomposition & reconstruction
<LI>Barycentric combination
<LI>
</UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld009.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld011.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld010.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>New Utilities, cont.</TITLE>
</HEAD>
<BODY >
<H1>New Utilities, cont.</H1>
<P><UL>
<LI><H2>Miscellaneous
</H2>
<UL>
<LI>Tcl/Tk windowing shell providing interface to BRL-CAD library routines
<LI>Cascading and time estimation added to animation capabilities
<LI>Haar wavelet decomposition & reconstruction
<LI>Barycentric combination
<LI>
</UL></UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld009.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld011.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld010.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,54 +1,54 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Libraries</TITLE>
</HEAD>
<BODY >
<H1>Libraries</H1>
<P><UL>
<LI><H2>libbn
</H2>
</UL><UL>
<H2> Numerical computation, quaternions, wavelets, ...
</H2>
</UL><UL>
<LI><H2>libbu
</H2>
</UL><UL>
<H2> Utilities: memory mgmt, parallel processing, ...
</H2>
</UL><UL>
<LI><H2>libdm
</H2>
</UL><UL>
<H2> Display manager: X, Open GL, PostScript, ...
</H2>
</UL><UL>
<LI><H2>librt Ray tracing
</H2>
</UL><UL>
<LI><H2>libpng PNG
</H2>
</UL><UL>
<LI><H2>libz Data compression</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld010.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld012.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld011.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Libraries</TITLE>
</HEAD>
<BODY >
<H1>Libraries</H1>
<P><UL>
<LI><H2>libbn
</H2>
</UL><UL>
<H2> Numerical computation, quaternions, wavelets, ...
</H2>
</UL><UL>
<LI><H2>libbu
</H2>
</UL><UL>
<H2> Utilities: memory mgmt, parallel processing, ...
</H2>
</UL><UL>
<LI><H2>libdm
</H2>
</UL><UL>
<H2> Display manager: X, Open GL, PostScript, ...
</H2>
</UL><UL>
<LI><H2>librt Ray tracing
</H2>
</UL><UL>
<LI><H2>libpng PNG
</H2>
</UL><UL>
<LI><H2>libz Data compression</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld010.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld012.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld011.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,48 +1,48 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of MGED for 5.0</H1>
<P><UL>
<LI><H2>Integration of frame buffer
</H2>
<UL>
<LI>render geometry for disambiguation/debugging
<LI>register geometry with imported imagery
</UL></UL><UL>
<LI><H2>Integration of ray tracing
</H2>
<UL>
<LI>query rays
<LI>click to edit, click to render
</UL></UL><UL>
<LI><H2>Multipane mode
</H2>
</UL><UL>
<LI><H2>Snap-to-grid mode
</H2>
</UL><UL>
<LI><H2>Networked collaboration, multiple display managers</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld011.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld013.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld012.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of MGED for 5.0</H1>
<P><UL>
<LI><H2>Integration of frame buffer
</H2>
<UL>
<LI>render geometry for disambiguation/debugging
<LI>register geometry with imported imagery
</UL></UL><UL>
<LI><H2>Integration of ray tracing
</H2>
<UL>
<LI>query rays
<LI>click to edit, click to render
</UL></UL><UL>
<LI><H2>Multipane mode
</H2>
</UL><UL>
<LI><H2>Snap-to-grid mode
</H2>
</UL><UL>
<LI><H2>Networked collaboration, multiple display managers</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld011.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld013.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld012.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,46 +1,46 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of MGED for 5.0, cont.</H1>
<P><UL>
<LI><H2>Uniform mouse-based manipulation of
</H2>
</UL><UL>
<H2> geometry and view
</H2>
</UL><UL>
<LI><H2>GUI control panels…
</H2>
<UL>
<LI>ray-traced rendering
<LI>animation
<LI>color editing
<LI>snap to grid
<LI>angle/distance cursor
<LI>shaders (glass, camo, projection, …)
</UL></UL><UL>
<LI><H2>Command history and command-line editing</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld012.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld014.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld013.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>Major New Features of</TITLE>
</HEAD>
<BODY >
<H1>Major New Features of MGED for 5.0, cont.</H1>
<P><UL>
<LI><H2>Uniform mouse-based manipulation of
</H2>
</UL><UL>
<H2> geometry and view
</H2>
</UL><UL>
<LI><H2>GUI control panels…
</H2>
<UL>
<LI>ray-traced rendering
<LI>animation
<LI>color editing
<LI>snap to grid
<LI>angle/distance cursor
<LI>shaders (glass, camo, projection, …)
</UL></UL><UL>
<LI><H2>Command history and command-line editing</H2>
</UL></P>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld012.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld014.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld013.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld013.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld015.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld014.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld013.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld015.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld014.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld014.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld016.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld015.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld014.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld016.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld015.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld015.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld017.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld016.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld015.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld017.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld016.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld016.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld018.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld017.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld016.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld018.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld017.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld017.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld019.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld018.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld017.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld019.htm">Next slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld018.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
@@ -1,27 +1,27 @@
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld018.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100></TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld019.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
<HTML>
<HEAD>
<meta name="GENERATOR" content="Microsoft Internet Assistant for PowerPoint 97">
<TITLE>BRL-CAD™ Projection Shader</TITLE>
</HEAD>
<BODY >
<H1>BRL-CAD™ Projection Shader</H1>
<P></P>
<P>
<TABLE>
<TD HEIGHT=100 WIDTH=100> <A HREF="tsld018.htm">Previous slide</A> </TD>
<TD HEIGHT=100 WIDTH=100></TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="tsld001.htm">Back to first slide</A> </TD>
<TD HEIGHT=100 WIDTH=150> <A HREF="sld019.htm">View graphic version</A> </TD>
</TABLE>
<BR>
</P>
</Body>
</HTML>
+3 -1
View File
@@ -36,6 +36,8 @@ and thus may not be present in subsequent releases.
</li>
</ul>
<a href="mailto:devs@brlcad.org">&lt;<code>devs@brlcad.org</code>&gt;</a>
<a href="mailto:pjt@arl.mil">
&lt;<code>pjt@arl.mil</code>&gt;
</a>
<br>
<a href="index.html"> BRL-CAD Release 5.0 Release Notes </a>
+3 -2
View File
@@ -10,8 +10,9 @@
<li><a href="deprecated.html">Deprecated features</a></li>
</ul>
<a href="mailto:devs@brlcad.org">&lt;<code>devs@brlcad.org</code>&gt;</a>
<!---<a href="mailto:pjt@arl.army.mil">&lt;<code>pjt@arl.army.mil</code>&gt;</a>--->
<a href="mailto:cad@arl.army.mil">&lt;<code>cad@arl.army.mil</code>&gt;</a>
<br>
<a href="../index.html"> Release Notes for other versions of BRL-CAD </a>
</body>
</html>
</html>
+2 -2
View File
@@ -140,8 +140,8 @@
</li>
</ul>
<a href="mailto:devs@brlcad.org">
&lt;<code>devs@brlcad.org</code>&gt;
<a href="mailto:pjt@arl.mil">
&lt;<code>pjt@arl.mil</code>&gt;
</a>
<br>
<a href="index.html"> BRL-CAD Release 5.0 Release Notes </a>
+3 -3
View File
@@ -5,7 +5,7 @@
<h1>BRL-CAD Release 5.0 New Libraries</strong></h1>
In addition to many capabilities that are new to release 5.0,
a substantial portion of the functionality
previously existing in <code>mged</code>(1) and <code>librt</code>(3)
previously existing in <code>mged</code>(1) and <code>librt</code>(3)
has been broken out
and reorganized into various of the new libraries,
which are summarized below.
@@ -66,8 +66,8 @@ which are summarized below.
</li>
</ul>
<a href="mailto:devs@brlcad.org">
&lt;<code>devs@brlcad.org</code>&gt;
<a href="mailto:pjt@arl.mil">
&lt;<code>pjt@arl.mil</code>&gt;
</a>
<br>
<a href="index.html"> BRL-CAD Release 5.0 Release Notes </a>
+3 -5
View File
@@ -1,9 +1,7 @@
# $Id$
htmldocsdir = $(BRLCAD_DATA)/html/ReleaseNotes/Rel6.0
htmldocs_DATA = index.html
EXTRA_DIST = $(htmldocs_DATA)
include $(top_srcdir)/misc/Makefile.defs
stuffdir = $(prefix)/html/ReleaseNotes/Rel6.0
stuff_DATA = index.html
EXTRA_DIST = $(stuff_DATA)
+33 -33
View File
@@ -17,33 +17,33 @@ It introduces a large number of new capabilities in BRL-CAD, including:
<dl>
<dt><b>Machine-Independent Data</b></dt>
<dd>The geometry in the new file format is stored in an
<dd>The geometry in the new file format is stored in an
architecture-independent fashion. This removes the need to convert
the geometry file to ASCII representation and back to binary when
moving between machines of different architectures (e.g., between
the geometry file to ASCII representation and back to binary when
moving between machines of different architectures (e.g., between
Big-Endian and Little-Endian machines).</dd>
<dt><b>Unlimited-Length Object Names</b></dt>
<dd>Names of objects in the geometry database were previously limited
to 16 characters. This restriction was burdensome when constructing
complex systems. The new database format (and MGED/rt) allows for
unlimited-length names for objects. The only limits remaining are
usability/human factors (i.e., the user may wish to think twice before using
unlimited-length names for objects. The only limits remaining are
usability/human factors (i.e., the user may wish to think twice before using
1024-character names for all objects).</dd>
<dt><b>Object Attributes</b></dt>
<dd>All geometry file objects can now carry arbitrary text data.
This information is stored as a series of name-value pairs. For example, it is
possible to store an attribute called "modeler", which could indicate
the name and organization of the person who created that portion of
the name and organization of the person who created that portion of
the geometry. Another attribute might be "density", whose value would
be the density of the material from which the object was constructed.
Analysis codes can store application-specific data in these attributes
and retrieve them at run time. MGED has a GUI control panel for
and retrieve them at run time. MGED has a GUI control panel for
creating and editing object attributes.</dd>
<dt><b>Opaque Binary Objects</b></dt>
<dd>It is now possible to store arbitrary data in a BRL-CAD geometry
<dd>It is now possible to store arbitrary data in a BRL-CAD geometry
database object. For example, the entire description from an
external CAD system could be stored for reference. Several features
of BRL-CAD geometry that require ancillary data can now use these
@@ -53,9 +53,9 @@ It introduces a large number of new capabilities in BRL-CAD, including:
<dt><b>Reduced Disk Space Requirements</b></dt>
<dd>The new file format is more aggressive about space utilization.
Many primitives now occupy significantly less disk space.</dd>
<dt><b>New <b>dbupgrade</b> Utility for Easy Migration</b></dt>
<dd>The <b>dbupgrade</b> command has been created to bring old
<dd>The <b>dbupgrade</b> command has been created to bring old
databases up to the most current version of the file format.</dd>
<dt><b>Hidden Objects</b></dt>
@@ -66,19 +66,19 @@ It introduces a large number of new capabilities in BRL-CAD, including:
<dt><b>Deprecation of Obsolete <i>hf</i> and <i>poly</i> primitives</b></dt>
<dd>The <i>dsp</i>(Displacement Map) primitive is functionally equivalent to the <i>hf</i>
and offers substantial performance advantages. The <i>bot</i> (bag of triangles) primitive
is likewise a substantial improvement over the
existing <i>poly</i> primitive. The <b>dbupgrade</b> utility converts existing
<i>hf</i> and <i>poly</i> primitives into <i>dsp</i> and <i>bot</i> primitives, respectively.
and offers substantial performance advantages. The <i>bot</i> (bag of triangles) primitive
is likewise a substantial improvement over the
existing <i>poly</i> primitive. The <b>dbupgrade</b> utility converts existing
<i>hf</i> and <i>poly</i> primitives into <i>dsp</i> and <i>bot</i> primitives, respectively.
Both <i>hf</i> and <i>poly</i> primitives are deprecated.</dd>
<dt><b>Introduction of 2D <i>sketch</i> primitive</b></dt>
<dd>The <i>sketch</i> primitive consists of straight lines, circular arcs,
<dd>The <i>sketch</i> primitive consists of straight lines, circular arcs,
and Bezier curves. There is a drawing utility in MGED for creating
them.</dd>
<dt><b>Introduction of <i>extrude</i> primitive</b></dt>
<dd>The <i>extrude</i> primitive supports linear extrusion of
<dd>The <i>extrude</i> primitive supports linear extrusion of
closed-boundary <i>sketch</i> primitive drawings to create 3D objects.
</dd>
@@ -98,7 +98,7 @@ have been numerous improvements. These include:
<dl>
<dt><b>New User's Manual</b></dt>
<dd>This is a completely updated tutorial introduction to MGED and modeling
with BRL-CAD. Delivered in PDF format and suitable for both online
with BRL-CAD. Delivered in PDF format and suitable for both online
browsing and printing. It includes a complete command reference. Look
for it in the MGED menus at:<br>"Help->Manual->PDF MGED Tutorial" &nbsp;&nbsp; or<br>
"/usr/brlcad/html/manuals/mged/VolumeII-Introduction_to_MGED.pdf"
@@ -106,17 +106,17 @@ have been numerous improvements. These include:
<dt><b>Dual-Format Capability</b></dt>
<dd>MGED and other BRL-CAD utilities retain the ability to work
with geometry files constructed
with geometry files constructed
in previous versions of BRL-CAD as well as the new one.
Users can upgrade geometry to the new format
when they choose. New features implemented in the geometry
file may not be available under the old format.</dd>
<dt><b>Accelerators for Complex Shape Construction</b></dt>
<dd>These allows user to automatically generate more complex
primitives from existing ones. For example, <b>rcc-cap</b>
<dd>These allows user to automatically generate more complex
primitives from existing ones. For example, <b>rcc-cap</b>
creates an ellipsoidal top for a right circular cylinder.
The list of accellerators includes: <b>rcc-blend, rcc-cap, rcc-tgc,
The list of accellerators includes: <b>rcc-blend, rcc-cap, rcc-tgc,
rpp-arch, rpp-cap, rpp-arch, tor-rcc,</b> and <b>sph-part.</b></dd>
<dt><b>Improved Menu and Interface Layout</b></dt>
@@ -135,7 +135,7 @@ have been numerous improvements. These include:
</dd>
<dt><b>Extended Primitive Auto Generation</b></dt>
<dd>Several primitive types can now be auto generated using the
<dd>Several primitive types can now be auto generated using the
<b>make</b> command from within MGED. These include:<ul>
<li>rectangular parallelepipeds (rpp)</li>
<li>arbitrary faceted (ars)</li>
@@ -170,7 +170,7 @@ have been numerous improvements. These include:
<dt><b>Build Pattern Tool</b></dt>
<dd>This tool facilitates the construction of replicated objects
in various rectangular grid and circular patterns. For example:
in various rectangular grid and circular patterns. For example:
lines of rivet heads, bolt holes, railroad ties, tire tread patterns.
</dd>
@@ -182,7 +182,7 @@ have been numerous improvements. These include:
<dd>
<dl>
<dt><b>Opaque Binary Object Support for <i>dsp</i> Primitive and <i>Texture</i> Shaders</b></dt>
<dd>The <i>dsp</i> primitive can accept an opaque binary object as the source for its elevation data. Likewise, <i>texture</i> shaders
<dd>The <i>dsp</i> primitive can accept an opaque binary object as the source for its elevation data. Likewise, <i>texture</i> shaders
can now accept opaque binary objects as the source for their image data.
</dd>
@@ -197,7 +197,7 @@ can now accept opaque binary objects as the source for their image data.
<dd>These two primitives did not have an ASCII representation in previous releases. This omission has been corrected.</dd>
<dt><b>Support for MacOS X</b></dt>
<dd>BRL-CAD again supports the MacOS platform. It requires that the
<dd>BRL-CAD again supports the MacOS platform. It requires that the
XDarwin or other X11 server be installed for correct operation.
</dd>
@@ -218,7 +218,7 @@ XDarwin or other X11 server be installed for correct operation.
<dd>A C implementation of the Tcl/Tk dual-ported object type is included.</dd>
<dt><b>New Shaders</b></dt>
<dd>Two new shaders <i>flat</i> and <i>invisible</i> are included.
<dd>Two new shaders <i>flat</i> and <i>invisible</i> are included.
The <i>flat</i> shader support per-channel alpha blending.</dd>
</dl>
</dl>
@@ -229,18 +229,18 @@ The <i>flat</i> shader support per-channel alpha blending.</dd>
<dd>The following are new to release 6.0:
<dl>
<dt><b>pixcmp</b></dt>
<dd>This program Compares two <b>pix</b> format images.
Although not technically new
(it was formerly included in source distributions), <b>pixcmp</b> is now
<dd>This program Compares two <b>pix</b> format images.
Although not technically new
(it was formerly included in source distributions), <b>pixcmp</b> is now
installed.</dd>
<dt><b>rtedge</b></dt>
<dd>This program raytraces models, detects edges,
<dd>This program raytraces models, detects edges,
and writes BRL-CAD color image (.pix) files.</dd>
<dt><b>g_diff</b></dt>
<dd>This program compares two geometry database files and reports differences
<dd>This program compares two geometry database files and reports differences
between the two.
This allows databases that contain the same objects in different orders to
be recognized as being the same.</dd>
@@ -248,7 +248,7 @@ The <i>flat</i> shader support per-channel alpha blending.</dd>
<dt><b>dbupgrade</b></dt>
<dd>This program upgrades an old BRL-CAD database to the current BRL-CAD release
file format.
This allows older geometry to take advantage of space savings and new functionality
This allows older geometry to take advantage of space savings and new functionality
only available with the newer database formats
(e.g., convert a database created with BRL-CAD rel4.5 to one that is fully functional
in BRL-CAD rel6.0).</dd>
@@ -293,7 +293,7 @@ unquenchable cur iosity, and unending enthusiasm to advance the
capabilities and performance of everything and everyone he touched.
He was the original architect of BRL-CAD and for 20 years guided its
development and emergence as one of the most advanced physically based
computer-aided design packages in the world. His presence and his
computer-aided design packages in the world. His presence and his
abilities will be missed.
</dd>
+16 -13
View File
@@ -59,7 +59,7 @@ Here are MGED commands as requested:
&lt; create a region named 'second' which is the intersection (+?)
&lt; of 'my_2' and 'my_1'
r second + my_1 + my_2
&lt; assign a different item, material, color, air to each of the three
&lt; assign a different item, material, color, air to each of the three
&lt; regions
edcodes both first second
&lt; combine 'prims', 'both', 'first', and 'second' into an object named
@@ -80,11 +80,11 @@ Usage: press button_label
(emulate button press)
mged&gt; press ?
?: no match
top, bottom, right, left, front,
rear, restore, save, adc, reset,
45,45, 35,25, oill, sill, oscale,
oxscale, oyscale, ozscale, ox, oy,
oxy, orot, accept, reject, slice,
top, bottom, right, left, front,
rear, restore, save, adc, reset,
45,45, 35,25, oill, sill, oscale,
oxscale, oyscale, ozscale, ox, oy,
oxy, orot, accept, reject, slice,
sedit, srot, sxy, sscale, mged&gt;
<p>
@@ -105,7 +105,7 @@ object state. I use either a Tektronix 4014 emulator on the Macintosh or a
real honest to goodness Tektronix 4207 which emulates a 4109. Attachment to
the Tek 4109 is done properly, pictures are drawn, etc. Solid edit state can
be entered using 'sed', etc. I can't seem to find an object analogy to 'sed'
other than 'press oill' which opens up the door to the pick, path, states,
other than 'press oill' which opens up the door to the pick, path, states,
etc. from which I can't seem to do anything except 'press reject'. I am not
using a tablet or a pen (is a pen required or can this also be emulated with
key presses?). The only cursor that ever comes up on the screen is the
@@ -113,7 +113,7 @@ angle/distance cursor when I toggle it on with 'press adc'.
<p>
Could you please give me some advice? Even better, could you send me,
or us on the network, a (very simple) script of mged commands which would
or us on the network, a (very simple) script of mged commands which would
lead us through an editing session. For example:
<p>
@@ -131,7 +131,7 @@ lead us through an editing session. For example:
create a region named 'first' which subtracts 'my_2' from 'my_1' (1-2?)
create a region named 'second' which is the intersection (+?)
of 'my_2' and 'my_1'
assign a different item, material, color, air to each of the three
assign a different item, material, color, air to each of the three
regions
combine 'prims', 'both', 'first', and 'second' into an object named
'obj2'
@@ -139,7 +139,7 @@ lead us through an editing session. For example:
quit mged
<p>
Such an example would illustrate most of what is required to create
Such an example would illustrate most of what is required to create
a model, and would help me immeasurably. Thank you for your time and, again,
thank you for the software.
@@ -384,7 +384,7 @@ It was thought that perhaps by defing a sub-group to define the union
may give the correct answer, but alas it doesn't.
<p>
Using a sub-region, not only fails to give the correct answer, but
Using a sub-region, not only fails to give the correct answer, but
gives an obviously bug-related bogus answer.
<p>
@@ -404,7 +404,7 @@ complicated model, it could cause a high overhead.
<p>
So, please tell me what is wrong here It is obvious that the solution
is out there as I cannot believe that those complicated models in the
sample pixel files were built in this (clumbsy) way.
sample pixel files were built in this (clumbsy) way.
<p>
The crux of the matter appears to me to be how to (easily) define
@@ -443,7 +443,10 @@ and then subtracting the cylinder didn't work....I believe they should.
<p>
<hr>
<em>mike</em>
<a href="mailto:mike@arl.mil">
&lt;<em> mike@arl.mil </em>&gt;
</a>
<br>
<a href="index.html"> Release notes for other versions of BRL-CAD </a>
+33 -33
View File
@@ -109,7 +109,7 @@ Phil has been making good progress with pl-X, the UNIX-plot to X-windows
display program, the precursor to having X-windows support for MGED.
<p>
Best,
Best,
-Mike
<hr>
Date: Sat, 21 Nov 87 2:46:22 EST
@@ -145,7 +145,7 @@ We plan on having this capability by springtime.
<p>
Sorry I sound like a vendor, but we have limited manpower, and have to
schedule carefully. Would be wonderful to be able to do everything
schedule carefully. Would be wonderful to be able to do everything
immediately.
(I don't even get to do my own research immediately, so there).
@@ -369,8 +369,8 @@ To use mged on this machine
<p>
2. Mged files which have been created on an Iris, Sun, or Alliant
all use the same floating point format as the 4d.
3. type
3. type
vacuum.brl.mil&gt; mged file.g
with sgi as the display type.
@@ -404,7 +404,7 @@ The frame buffer is a bit different.
<p>
lingering windows will stay around until you log off the system
or you kill the window. A menu button to exit the window is provided
via the right most button on the mouse just attach to the window
via the right most button on the mouse just attach to the window
first....
<p>
@@ -550,10 +550,10 @@ I agree entirely with Doug:
after the last component. But, if for instance I come from the side and
hit, say, road wheel, space, hull side, I'd like to have that space show
up (automatically) as outside air.
+ The option of paint as implemented in shotray(1V) should serve our
purposes admirably.
+ I don't see why we would need both regionid and aircode, IF we could get
by with the convention that non-positive regionid were air. I don't even
see why the sign of the regionid need be the characteristic to use in
@@ -1004,7 +1004,7 @@ offending section:
<p>
<p>
denom = ( (E*G) - (F*F) );
denom = ( (E*G) - (F*F) );
<p>
a11 = (( f * F ) - (e * G) ) / denom;
@@ -1045,7 +1045,7 @@ and curvatures produced by eigen2x2 above are not correct???
<p>
Please let me know if these comments are in left field, but it would be
fairly easy to compute the curvatures and principle directions from the
fairly easy to compute the curvatures and principle directions from the
a11,a12,a21,a22 above.
<p>
@@ -1153,7 +1153,7 @@ discussions with Mike.
<p>
Probably more than Mike, I have attempted to carry the flag into
some classic meeting grounds which typically advertise an interest in
some classic meeting grounds which typically advertise an interest in
CAD, CAE and sometimes CAM and CIM. In thinking about this experience
I found the following dates from my back electronic calendars in which
I have presented papers to groups with direct industry representation.
@@ -1178,7 +1178,7 @@ Wed 05/11/88 - - ADPA Mtg: San Diego: Day #2
<p>
Back in the 83-84 time frame, I also had extensive interaction with
the DARCOM Office of Manufacturing Technology (OMT) and Rock Island
Industrial Based Engineering Activity (IBEA).
Industrial Based Engineering Activity (IBEA).
<p>
Let me summarize briefly.
@@ -1215,7 +1215,7 @@ o On the other hand, BRL-CAD has found a very large market which is growing
who are interested in performing item-level analyses of military equipment.
That includes all kinds of topics from vulnerability to signatures, to
weights, neutron transport, high-power microwave damage, . . . The fact
that the BRL-CAD software distribution has now reached 350 sites is
that the BRL-CAD software distribution has now reached 350 sites is
testament to that need.
<p>
@@ -1459,27 +1459,27 @@ Y 0.3420 0.5880 0.0640
Z 0.0480 0.1240 0.7850
<p>
X Y Z
X Y Z
R 2.2708 -1.0772 -0.3490 multiply the XYZ values of the color you want
G -1.3285 2.3607 0.0631 by this matrix for the RGB (not normalized)
B 0.0710 -0.3070 1.2853 values for the 4D/60T monitor.
G -1.3285 2.3607 0.0631 by this matrix for the RGB (not normalized)
B 0.0710 -0.3070 1.2853 values for the 4D/60T monitor.
<p>
Have a colorful experience today,
<p>
Michael Mascagni mascagni@nyu.edu
mascagni@ncifcrf.gov
mascagni@ncifcrf.gov
<hr>
Date: Mon, 25 Jan 88 9:24:41 EST
From: Charlie Arnold (ERIM - Davisson) &lt;carnold@BRL.ARPA&gt;
<p>
There are some people here looking into ground clutter.
The following references will give an idea of what models they
are considering.
1. M. Borgeaud, R.T. Shin, and J.A. Kong, "Theoretical
Models for Polarimetric Radar Clutter", Journal of
E.M. Waves and App., pp73-89, Jan 1987.
@@ -1491,11 +1491,11 @@ From: Charlie Arnold (ERIM - Davisson) &lt;carnold@BRL.ARPA&gt;
4. G.R. Valenzuela, "Depolarization of EM waves by Slightly
Rough Surfaces", IEEE Trans. Ant. and Prop., pp. 552-557,
July 1967.
I am working on sending you some internal memos on finite impedance
surfaces. I need to clear this with the author's first so it may take
a few more days.
Charlie Arnold
<hr>
Date: Wed, 3 Feb 88 2:18:42 EST
@@ -1606,7 +1606,7 @@ mged&gt; ill &lt;name&gt;
Its much easier to use the mouse to select the pull down menus,
then select &lt;object illuminate&gt; or press the &lt;object illuminate&gt; button
on your button box, then move the mouse vertically on the pad to select
the object. The keyboard &lt;press&gt; command and &lt;ill&gt; are there mainly for
the object. The keyboard &lt;press&gt; command and &lt;ill&gt; are there mainly for
Tektronix or other less brain-damaged hardware that don't happen to have
button boxes or mouses (*most* button functions can be done with the
mouse).
@@ -1717,7 +1717,7 @@ copies of the CAD software:
INSTALLED versions of the software (ie, that software which was
installed by saying "make install" or "cake install").
3) The tree spark:/m/cad, which is the development area. The sources for
the very latest software live here, and are under RCS (source code
the very latest software live here, and are under RCS (source code
Revision Control System) archival control. This is the "R&D" copy
of the software, and is where all changes are made.
@@ -1839,7 +1839,7 @@ for it to change. Whoever brought that up inserted a moby red herring
into the disucssion. I assure all of you that I consider database format
changes to be a "really big deal", and they will be done only for good
cause, and with lots of trumpet tooting in advance, so that we can enjoy
our usual vigorous debate before actually doing anything.
our usual vigorous debate before actually doing anything.
<p>
The electronic discussion of this topic is now closed.
@@ -1850,18 +1850,18 @@ From: "Gary S. Moss" (VLD/VMB) &lt;moss@BRL.ARPA&gt;
<p>
Ian writes:
&gt;
&gt;
&gt; I sent this letter two weeks ago,I am not sure whether it got to you
&gt; or if it got lost in the pipeline;anyway here goes again!
We got it, I was just hoping someone else would answer it since I only know
some of the answers, but here goes...
&gt; 1. When trying to use the ARS command I get the reply
&gt; "not implemented yet",
&gt; we have version 2.1 (Jul 87) on our 3130 IRIS. How can we implement
&gt; 1. When trying to use the ARS command I get the reply
&gt; "not implemented yet",
&gt; we have version 2.1 (Jul 87) on our 3130 IRIS. How can we implement
&gt; the ARS's function and what commands are used to create them?
There is no ARS editing capability. The ones that we have were described
by typing in coordinates before MGED was ever written.
&gt; 2. What are the commands to create "Rendered Splines" as shown on
&gt; 2. What are the commands to create "Rendered Splines" as shown on
&gt; plate caption 1.2 in your manual (i.e. how can we add a spline
&gt; surface to a mged model)?
MGED does not edit splines either. We get our splines from the U. of Utah
@@ -2030,7 +2030,7 @@ Or you can write a code which should look alot like this using libwdb:
#include &lt;math.h&gt;
#include "machine.h"
#include "db.h"
#include "vmath.h"
#include "vmath.h"
<p>
main(argc,argv)
@@ -2038,7 +2038,7 @@ main(argc,argv)
<p>
int argc;
char *argv[];
point_t min, max;
point_t min, max;
char *name;
{
argc--,argv++;
@@ -2053,7 +2053,7 @@ char *name;
/* Read command line arguments */
<p>
while (argc &gt; 0 && argv[0][0] == '-') {
while (argc &gt; 0 && argv[0][0] == '-') {
switch (argv[0][1]) {
<p>
@@ -2067,7 +2067,7 @@ char *name;
debug = 1;
argc--,argv++;
break;
default:
fprintf(stderr,
"usage: conman [ -n ][ filename ]\n");
@@ -2126,7 +2126,7 @@ Received: from spark.brl.mil by SEM.BRL.MIL id aa09866; 19 Sep 88 6:14 EDT
Date: Mon, 19 Sep 88 6:14:08 EDT
From: Mike Muuss &lt;mike@BRL.MIL&gt;
To: ACST@BRL.MIL
cc: Moss@BRL.MIL, Gwyn@BRL.MIL, CJohnson@BRL.MIL, PHD@BRL.MIL,
cc: Moss@BRL.MIL, Gwyn@BRL.MIL, CJohnson@BRL.MIL, PHD@BRL.MIL,
Davisson@BRL.MIL
Subject: New rle-fb
Message-ID: &lt;8809190614.aa09313@SPARK.BRL.MIL&gt;
+108 -108
View File
@@ -375,7 +375,7 @@ colourimetry began to flourish in 1931, when the CIE standardized a
statistical entity called the "standard observer". This includes a
standard spectral luminance response defined numerically as a function of
wavelength. It is from this data that the factors which are used in
colour television are derived: .587 for green, .299 for red, and
colour television are derived: .587 for green, .299 for red, and
.114 for blue.
<p>
@@ -390,7 +390,7 @@ green are unquestionably the best values to use, unless you know your
phoshphors intimately.
<p>
The second article continues,
The second article continues,
&gt; The formula is from
&gt; the (1954) NTSC standard for compatible color TV, and it has built
&gt; into it a lot of compromises to accommodate old technology and
@@ -440,10 +440,10 @@ YUV REPRESENTATION (3 wires)
<p>
Studio equipment typically processes colour signals in three components
YUV, which are easily derived from RGB. The Y channel contains the
luminance (black-and-white) content of the image, and is computed as:
luminance (black-and-white) content of the image, and is computed as:
<p>
Y' = 0.299 R' + 0.587 G' + 0.114 B'
Y' = 0.299 R' + 0.587 G' + 0.114 B'
<p>
"Colour difference" signals U and V are scaled versions of B'-Y' and R'-Y'
@@ -531,7 +531,7 @@ Subject: Re: Bug Report on 3.0
<p>
&lt; 3) Running LGT with pop-up menus, no keyboard input is accepted unless
&lt; prompted for as the result of a pop-up menu selection. (Running without
&lt; prompted for as the result of a pop-up menu selection. (Running without
&lt; pop-up menus in favor of the curses style menus gives correct behavior.)
&lt;
&lt; Dan Dender
@@ -604,10 +604,10 @@ To: cad@BRL.MIL
<p>
SUBJECT Standards (was : How to model coil spring)
sent TO : cad@brl.mil
sent TO : cad@brl.mil
<p>
There is a group on standards (comp.std.internat) and so I do
not want start an 'std' debate here - but perhaps a short endorsement
(support/vote) of Phil's view and a recollection of as what IGES
@@ -621,36 +621,36 @@ ISO STEP. (and thus in the future go the ISO route).]
<p>
and Re:
The bottom line is that I predict that ISO STEP (or PDES) models
useful to us won't be available from U.S. defense contractors until
AT LEAST five years and we'd best put our money, at this stage,
into IGES. And some (if not most) of the tools we'd develop for
The bottom line is that I predict that ISO STEP (or PDES) models
useful to us won't be available from U.S. defense contractors until
AT LEAST five years and we'd best put our money, at this stage,
into IGES. And some (if not most) of the tools we'd develop for
IGES should be usable for developing ISO STEP translators
Earl Weaver &lt;earl@brl.mil&gt;
IGES started as a reaction to an overly complicated and
too slowly evolving draft of an ANSI standard (which looked
too slowly evolving draft of an ANSI standard (which looked
rather like a badly written textbook on topology & differential
geometry). IGES was a fast, engineering common sense, quick and
dirty 'fix, for now' , not intented as a base of anything.
geometry). IGES was a fast, engineering common sense, quick and
dirty 'fix, for now' , not intented as a base of anything.
Then 'as a compromise' the two drafts were merged and so on ...
<p>
Fact remains that IGES has insufficient theoretical basis and to
Fact remains that IGES has insufficient theoretical basis and to
build more above it's present function would be mostly a waste
(I agree with Earl: practical and justifiable - but still waste)
of resources.
What is needed is a formal language (probably B-N specified)
with hirrearchical structure (as e.g. PHIGS) which is nD, super-set
of graphics and drafting, and of inputs to Finite Elements models
of graphics and drafting, and of inputs to Finite Elements models
with ability to describe materials, etc etc. It is not simple or
easy - but it needs to be done. One reason for present mess was
easy - but it needs to be done. One reason for present mess was
our inability to make 'reasonable run' goals. {IGES was 'short run',
the previous draft was 'too long run' and so we are in the same dilema
again!). It is possible to set a 'two years goal' and evolve consensus
on something a draft, which is workable. Alternative is to always
work with improvisations and fixes. Since we (US) missed our ANSI
opportunity already - we should now contribute our resources to the
opportunity already - we should now contribute our resources to the
ISO work (and fort short time - just improvise. That may include an
CAD interface - but still quick and dirty;) We'd best put most of
'our money' into developing a draft of a standard which has potential
@@ -806,9 +806,9 @@ their formula for intensity is a severe compromise.
<p>
--
Dick St.Peters
Dick St.Peters
GE Corporate R&D, Schenectady, NY
stpeters@ge-crd.arpa
stpeters@ge-crd.arpa
uunet!steinmetz!stpeters
<hr>
Date: 18 Nov 88 04:48:40 GMT
@@ -838,7 +838,7 @@ To: info-iris@BRL.MIL
of 640 by 480 pixels is displayed on the full RS170 monitor screen.
<p>
An option board may be purchased from Silicon Graphics for Iris 4D
An option board may be purchased from Silicon Graphics for Iris 4D
systems which takes the three RGB outputs and color encodes them
into a composite video signal. This signal is appropriate for
connecting directly to any television, or to a VCR. The composite
@@ -855,12 +855,12 @@ To: info-iris@BRL.MIL
either high res 60hz or NTSC modes).
<p>
So option one for video taping on an Iris 4D is to buy a CG2/3.
So option one for video taping on an Iris 4D is to buy a CG2/3.
The bottom left quarter of the screen may be recorded directly into
any recording device that accepts NTSC composite video.
<p>
Option two allows you to video tape the full picture on your 1280 by
Option two allows you to video tape the full picture on your 1280 by
1024 high resolution display. Pixel averaging is done to reduce
4 pixels down to one giving the appropriate number of pixels (640 - 480)
for NTSC. Pixel averaging provides better images over simply drawing
@@ -1130,7 +1130,7 @@ still there. DBX indicates a bad pointer in the PIX_COLOR call
} else {
color = PIX_COLOR(mp-&gt;mt_dm_int); &lt;----- culprit
}
The rest of his problems occur only on a Sun 4 with SunOS 4.0, with
*no* graphics processor:
@@ -1258,12 +1258,12 @@ it will.
just complained a lot, but I was thinking of the last CAD release). The
output is black (0,0,0) or sometimes *very* dark. I don't know what surface
normals would be output, but at least the thickness is correct when raytraced
with rtshot. I need this for a current government contract (within two
with rtshot. I need this for a current government contract (within two
months?).
<p>
3) Running LGT with pop-up menus, no keyboard input is accepted unless
prompted for as the result of a pop-up menu selection. (Running without
prompted for as the result of a pop-up menu selection. (Running without
pop-up menus in favor of the curses style menus gives correct behavior.)
<p>
@@ -1413,7 +1413,7 @@ to), but there are some practicalities that need to be considered.
<p>
I don't want to spend a lot of time and LOTS of words here describing
the relationships among ANSI, IGES, STEP (and more properly called
PDES/STEP in the U.S.), but I think I should share a few short words
PDES/STEP in the U.S.), but I think I should share a few short words
with those who have an interest in this subject.
<p>
@@ -1467,7 +1467,7 @@ PDES and STEP, in the U.S. are converging to the same thing insomuch
as they are commonly called "PDES/STEP." However, the real use
of PDES/STEP will not be seen for some time yet. PDES has great
interest to the Air Force and the AF would like to see PDES utilized
in the ATF (advanced tactical fighter) project, but...
in the ATF (advanced tactical fighter) project, but...
<p>
OK, now to the practicalities... Currently the major use of IGES is
@@ -1485,10 +1485,10 @@ require much less work to convert than a native format file,
especially if there are lots of different CAD systems involved.
<p>
The bottom line is that I predict that ISO STEP (or PDES) models
useful to us won't be available from U.S. defense contractors until
AT LEAST five years and we'd best put our money, at this stage,
into IGES. And some (if not most) of the tools we'd develop for
The bottom line is that I predict that ISO STEP (or PDES) models
useful to us won't be available from U.S. defense contractors until
AT LEAST five years and we'd best put our money, at this stage,
into IGES. And some (if not most) of the tools we'd develop for
IGES should be usable for developing ISO STEP translators
<p>
@@ -1524,7 +1524,7 @@ the capability to exploit the current base of IGES-available product
definition data and that which would be available for the near future
until a better mousetrap comes along. To me the situation is analogous
to waiting for the perfect dental solution that prevents all tooth/gum
problems rather then submitting to the current picks and drill. I'm
problems rather then submitting to the current picks and drill. I'm
not suggesting that the other outfits on this list have the same need.
<p>
@@ -1534,7 +1534,7 @@ proposal) methodology will come to light, and then should we wait
for that, too, rather than implement ISO STEP?
<p>
And finally, let me make it absolutely clear that I am NOT opposed to
And finally, let me make it absolutely clear that I am NOT opposed to
the new approaches in the works (PDES/STEP, or whatever), but I think
the benefits, to BRL, in using IGES exceed the cost of developing at
least the "import" (to BRLCAD) CSG translator.
@@ -1572,7 +1572,7 @@ in SIGGRAPH '87 pp. 263-272). The work has direct application in image warping.
Proceedings, Graphics Interface '86,
Canadian Information Processing Society,
Vancouver, pp 77-81.
Shearing (i.e. no image stretching or scaling) yields a very efficient inner-
loop despite the extra pass, but leaves the technique rotation-specific.
It also allows for 90-degree rotation (which 2-pass techniques do not): here
@@ -1593,14 +1593,14 @@ shed light on how and why the following oft-cited bit of CS lore works:
<p>
Y' = -eps*X'+ Y; /* carry down __X'__, not X for best results! */
As proposed by Newman and Sproull (vol I only), ascribed to I.E. Sutherland,
and mentioned recently in Jim Blinn's Corner (Algorithm 6 in ``How Many Ways
Can You Draw A Circle, IEEE CG&A, August, 1987). Adding a third line:
<p>
X'' = X' + eps*Y'; /* carry down some more! */
corresponding to the third shearing pass (plus some one-time-only trig to find
eps in statement two, because eps[1]=eps[3]&lt;&gt;eps[2]) now gives rise to a circle
drawer in which "eps" can be large enough to draw closed n-gons with impunity.
@@ -1628,7 +1628,7 @@ From: pom%and.s1.gov@mordor.s1.gov
To: cad@BRL.MIL
<p>
I (pom) opined that time may be right to move beyond IGES; I said:
pom: "It is possible to set a 'two years goal' and evolve consensus
on something, a draft, which is workable. Alternative is to always
@@ -1640,21 +1640,21 @@ To: cad@BRL.MIL
the capability to exploit the current base of IGES-available product.."
<p>
pom: No contest.
pom: No contest.
Mine was a technical comment on the state of the art(less
standard) not on BRL needs. When IGES was developed, the
interactive 3D graphics and Finite Elements (FE) were expensive
interactive 3D graphics and Finite Elements (FE) were expensive
exotic frills. IGES is fine for archiving and transmitting
drawings but todays interactive environment and simulation
has many more aspects. E.g, there are many locations developing
grid editors for FE models ; without some standard 'we'
are likely to that same work 20 times and spend rest of the
time on writing translators. (BRL is just one of the 'we').
grid editors for FE models ; without some standard 'we'
are likely to that same work 20 times and spend rest of the
time on writing translators. (BRL is just one of the 'we').
Earl:
And finally, let me make it absolutely clear that I am NOT opposed to
And finally, let me make it absolutely clear that I am NOT opposed to
the new approaches in the works (PDES/STEP, or whatever),...
.......[BUT]... by the time ISO STEP is developed,
validated, and accepted by the masses, a new, better ... methodology will
validated, and accepted by the masses, a new, better ... methodology will
come to light, and then should we waitfor that, too, rather than implement
ISO STEP?
pom: I do not think that you are
@@ -1663,36 +1663,36 @@ the new approaches in the works (PDES/STEP, or whatever),...
when and what is expected return on which investment of resources.
<p>
Earl: However, you'd best pick less than two people to arrive
Earl: However, you'd best pick less than two people to arrive
at a concensus on this subject within two years..
I suggest you contact ..."
<p>
pom: Agreed. I have been on the ANSI committee, which adopted IGES
and know it takes time. Lot of that consensus reaching time is
and know it takes time. Lot of that consensus reaching time is
consumed in the mail read&comment cycles - particularly in the
later phases. I would not want to do THAT again. The agreement
later phases. I would not want to do THAT again. The agreement
on the ISO forum will undoubtedly be even more slow and difficult.
BUT !!!! reference to ISO or ( PDES/STEP)
DOES NOT mean that one has to wait for THAT. IGES /for example/ was
developed by a small working group and only later brought to the
developed by a small working group and only later brought to the
party. Such a kernel may be in use long before it is formalised.
And use of e-mail should make the whole process much faster . To review current ISO proposals would be a good starting point.
Are you saying it is impossible to collate a wish-list and have
group ON THE NET which would agree on a specification of a
[small but extensible] language kernel in two years?
Something not perfect but much more versatile and readable then IGES?
group ON THE NET which would agree on a specification of a
[small but extensible] language kernel in two years?
Something not perfect but much more versatile and readable then IGES?
<p>
If you are not, then we TWO have already reached a consensus on a
rather important point. Peter (415) 422-7328
<p>
pom@under.s1.gov |or| pom@s1-under.UUCP
pom@under.s1.gov |or| pom@s1-under.UUCP
<p>
mail cad@brl.mil &lt; IGES_J
mail cad@brl.mil &lt; IGES_J
<hr>
From: Jim Walsh &lt;jimw@microsoft.uucp&gt;
Newsgroups: comp.graphics
@@ -1730,9 +1730,9 @@ shows sections on viewer perspectives and appropriate transformations,
various ways to speed image generation, etc.
<p>
--
--
Jim Walsh jimw@microsof.beaver.cs.washington.EDU
Microsoft Corporation jimw@microsof@uw-beaver.ARPA
Microsoft Corporation jimw@microsof@uw-beaver.ARPA
jimw@microsof.UUCP
The views expressed herein are not necessarily mine, let alone Microsoft's...
<hr>
@@ -1756,7 +1756,7 @@ RJ&gt; 7220?" replies. I have looked at these and other, newer chips and they
RJ&gt; do not interest me.]
<p>
You are going to have a challange here. Usually, a controller chip
You are going to have a challange here. Usually, a controller chip
provides atleast two sets of controls:
<p>
@@ -1787,12 +1787,12 @@ RJ&gt; display capable of displaying more lines if you run it at only 30 Hz.?
I think that once a monitor is set at 30 Hz or 60 Hz, your stuck.
What can be changed is the way you feed the monitor. You can opt
to feed it ONE image every frame, or two interlaced images every
two frames.
two frames.
<p>
RJ&gt; Can you up the pixel clock and feed more pixels per scan line? Does all
RJ&gt; this require surgery on the display's sweep circuitry or is there such a
RJ&gt; thing as a magic, self compensating circuit?
RJ&gt; thing as a magic, self compensating circuit?
<p>
If you have a fancy controller, I don't see why not, but the pain may not
@@ -1852,7 +1852,7 @@ cc: cad@BRL.MIL
Peter,
<p>
It looks like we're in agreement on philosophical principles. But on the
It looks like we're in agreement on philosophical principles. But on the
practical side of the issue, we may still have differences of opinion.
<p>
@@ -1863,7 +1863,7 @@ and emphasized the usefulness of IGES to BRL here and now.
<p>
You responded by agreeing with Phil that waiting until ISO STEP was the
better choice ("I agree with Earl: [BRL using IGES is] practical and
better choice ("I agree with Earl: [BRL using IGES is] practical and
justifiable - but still a waste of resources"), but then proposed the
development and implementation of better mousetrap (by reaching a consensus
among knowledgeable participants within a two-year period).
@@ -1873,13 +1873,13 @@ I answered by clarifying my position and again restating the reason why BRL
would benefit here and now with IGES [V 4.0].
<p>
All along my point has been that IGES has not only been accepted by many US
vendors, but that it was being used. I don't care if IGES is a poor substitute
for better methodology; until US industry actually accepts and implements a
better mousetrap, we [BRL] would gain nothing by either waiting for ISO STEP
or developing a better near-term mousetrap UNLESS we could gain immediate
participation by Sikorsky, McDonnell Douglas, Bell, Boeing, Northrup, General
Dynamics, Lockheed, Grumman, Martin Marietta, etc., etc., which, in my opinion,
All along my point has been that IGES has not only been accepted by many US
vendors, but that it was being used. I don't care if IGES is a poor substitute
for better methodology; until US industry actually accepts and implements a
better mousetrap, we [BRL] would gain nothing by either waiting for ISO STEP
or developing a better near-term mousetrap UNLESS we could gain immediate
participation by Sikorsky, McDonnell Douglas, Bell, Boeing, Northrup, General
Dynamics, Lockheed, Grumman, Martin Marietta, etc., etc., which, in my opinion,
is unlikely to happen in spite of the nobleness of the cause.
<p>
@@ -1887,9 +1887,9 @@ I'm glad you are aware of the trials and tribulations of the ANSI process.
(For the record, after the ANSI exercise of adopting IGES V 2.0 in which
you participated [I have most of the original paperwork of THAT exercise and
am really glad you folks were the ones that broke the ice, because that
experience made the follow-up task(s) much easier], that ANSI subcommittee
went into hibernation. When it reactivated, I was asked to help out and
subsequently got stuck with the job resolving the ballot comments when IGES
experience made the follow-up task(s) much easier], that ANSI subcommittee
went into hibernation. When it reactivated, I was asked to help out and
subsequently got stuck with the job resolving the ballot comments when IGES
V 3.0 was balloted. We're currently in the process of bringing up V 4.0
to ballot [and will most likely be involved in PDES/STEP when it matures].)
I hope you'll agree that V 4.0 bears little resemblance to V 2.0, although
@@ -1903,10 +1903,10 @@ ultimately ISO STEP) work.
<p>
Since you agree that your concerns are not in the BRL/IGES mutual
benefits area and I agree that the industry need something more complete
than the current IGES, let's drop this discussion from this cad list
and continue privately and with other folks who have an interest. That poor
soul who asked how to model a coil spring will be afraid to ask
benefits area and I agree that the industry need something more complete
than the current IGES, let's drop this discussion from this cad list
and continue privately and with other folks who have an interest. That poor
soul who asked how to model a coil spring will be afraid to ask
another question!
<hr>
Date: Tue, 24 Jan 89 6:14:26 EST
@@ -1951,13 +1951,13 @@ To: brl-comp-graphics@smoke.brl.mil
<p>
In article &lt;65@sdcc10.ucsd.EDU&gt;, cs161agc@sdcc10.ucsd.EDU (John Schultz) writes:
&gt;
&gt;
&gt;
&gt;
&gt; Problem: Need to rotate an instance of an object from a database,
&gt; then rotate the rotated instance by the previous rotated instance:
&gt;
&gt;
&gt; [currentinstance] = [currentinstance][newinstance]
&gt;
&gt;
&gt; Where the above are each matrices. One of the problems is decay,
&gt; as rotations iterate, decay increases and the object falls apart,
@@ -1995,7 +1995,7 @@ Jerry Kallaus {pyramid.arpa,ucbvax!sun!suncal}leadsv!kallaus
(408)742-4569
"Funny, how just when you think life can't possibly get
any worse, it suddenly does." - Douglas Adams
--
--
Jerry Kallaus {pyramid.arpa,ucbvax!sun!suncal}leadsv!kallaus
(408)742-4569
"Funny, how just when you think life can't possibly get
@@ -2011,7 +2011,7 @@ To: brl-comp-graphics@smoke.brl.mil
<p>
In article &lt;0XryqWy00Uo1875Ud-@andrew.cmu.edu&gt;, po0o+@andrew.cmu.edu (Paul Andrew Olbrich) writes:
&gt; Hi-ho,
&gt;
&gt;
&gt; I'm trying to add refraction to a ray tracing program I'm writing in C. Could
&gt; someone help me out a bit?
@@ -2028,7 +2028,7 @@ incoming ray-&gt; \ | &lt;- surface normal
\ |
\ |
\ |
\ | &lt;material with index of refraction n1&gt;
\ | &lt;material with index of refraction n1&gt;
\ |
\ |
\|
@@ -2056,25 +2056,25 @@ sin(theta1) sin(theta2)
(theta1 and theta2 are angles)
<p>
If n1 is 1 (like for a vacuum) and n2 is bigger than 1 (like glass) then
If n1 is 1 (like for a vacuum) and n2 is bigger than 1 (like glass) then
theta2 is smaller than theta1. Note that if it is the other way around,
that is, the ray goes from an optically dense material to an optically
less dense material, (like a ray coming out of glass), then theta2 is
less dense material, (like a ray coming out of glass), then theta2 is
bigger than theta1. (Maybe this is where you are screwing up?)
<p>
Also, if you are solving for sin(theta2) and you get a number bigger than 1,
it means that the ray should be totally internally reflected. This is why
when you look up from the bottom of a pool, everything above the water looks
it means that the ray should be totally internally reflected. This is why
when you look up from the bottom of a pool, everything above the water looks
like it is in a round window above your head.
<p>
There are other considerations. The ratio of light reflected to
There are other considerations. The ratio of light reflected to
transmitted is dependent on the angle but I can't remember that stuff.
<p>
Also, reflected and transmitted light is polarized (also dependent on the
angle). Pelicans have polarized filters in their eyes to see fish in the
Also, reflected and transmitted light is polarized (also dependent on the
angle). Pelicans have polarized filters in their eyes to see fish in the
water better. Bees have polarized eyes to navigate with sunlight on cloudy
days.
@@ -2099,13 +2099,13 @@ To: brl-comp-graphics@smoke.brl.mil
<p>
In article &lt;1104@nic.MR.NET&gt; jjc@sun1.UUCP (Jon Camp) writes:
&gt;
&gt;1) As Benie Cosell posted, 3-D perception is much more than stereopsis. It
&gt;involves parallax, focus, accomodation, obscuration, perspective, memory, a
&gt;great many other functions which I am not aware of and most likely some
&gt;that no one has ever measured. In our everyday lives, stereopsis is not
&gt;even the primary means of depth perception. Stereopsis IS, however,
&gt;relatively inexpensive to simulate, and is therefore the only contact
&gt;most people have with "3-D display".
&gt;1) As Benie Cosell posted, 3-D perception is much more than stereopsis. It
&gt;involves parallax, focus, accomodation, obscuration, perspective, memory, a
&gt;great many other functions which I am not aware of and most likely some
&gt;that no one has ever measured. In our everyday lives, stereopsis is not
&gt;even the primary means of depth perception. Stereopsis IS, however,
&gt;relatively inexpensive to simulate, and is therefore the only contact
&gt;most people have with "3-D display".
<p>
This subject has been studied in some detail by developers of flight
@@ -2116,8 +2116,8 @@ give here. I do recommend this book to anyone involved in the generation
of realistic imagery.
<p>
&gt;3) The common wisdom is that stereopsis is most effective within the reach
&gt;of our hands.
&gt;3) The common wisdom is that stereopsis is most effective within the reach
&gt;of our hands.
<p>
"Flight Simulation" references T. Gold, 1972, "The Limits of Stereopsis
@@ -2131,10 +2131,10 @@ and in fact stereo vision systems have been built for in-flight refueling
simulators.
<p>
&gt;4) As one who has experience viewing stereo and other 3-D representations,
&gt;I wish to report that stereopsis alone gives me a sensation of "viewing
&gt;fatigue", possibly because stereo so vividly presents SOME depth cues
&gt;while perversely witholding others. This is a personal experience, NOT a
&gt;4) As one who has experience viewing stereo and other 3-D representations,
&gt;I wish to report that stereopsis alone gives me a sensation of "viewing
&gt;fatigue", possibly because stereo so vividly presents SOME depth cues
&gt;while perversely witholding others. This is a personal experience, NOT a
&gt;rigorous criticism of stereoptic display.
<p>
@@ -2147,7 +2147,7 @@ don't have the paper around, but it was by someone in Hollywood who provides
3D gear to filmmakers. One useful gadget they offer is a pocket calculator
preprogrammed with the calculations needed to set up a shot for 3D. For
close-ups, this is non-trivial. They also offer a special leader for 3D
films that allows the projectionist to align the system properly. Failure
films that allows the projectionist to align the system properly. Failure
to do this correctly will induce headaches in some of the audience.
<p>
@@ -2186,7 +2186,7 @@ where, n = m e { 1 + sqrt[ 1 + square( L s / 2 pi c e) ] } / 2
<p>
m = Relative permeability of the material
r
e = Ralative permittivity of the material
r
L = wavelength of light
@@ -2476,7 +2476,7 @@ Subject: rle files in BRLCAD 3.0
<p>
With the new release of BRLCAD 3.0 the following has changed
with reference to rle images.
with reference to rle images.
<p>
There are three different types of rle images: versions 1, 2, and 3
@@ -2491,7 +2491,7 @@ through the /demo directory and converted all version 1 files to version
3.
<p>
I was unable to go through each individuals directories and change
I was unable to go through each individuals directories and change
the rle files which were located outside the demo directory. To test
your rle files and convert them you can to the following...
+83 -83
View File
@@ -36,11 +36,11 @@ system understands. I'm told that MEDUSSA knows how to translate from
its own internal representation format into IGES, but apparently the
BRL-CAD system does not know how to read in a file in IGES format. I'm
new to the BRL-CAD system and to CAD systems in general, so I'm hoping
that I'm just not looking in the right place.
that I'm just not looking in the right place.
I also know people who wish to take PATRAN output and be able
to take advantage of the rendering capabilities of the BRL-CAD system,
but here again, it would seem that some sort of conversion utility
either has to be written or acquired.
either has to be written or acquired.
I can't believe I'm the first person to be in this situation,
so I thought posting to the net would be a good idea before I think in
terms of developing my own utilities. Is there another newsgroup
@@ -168,7 +168,7 @@ Title: BRL-CAD Symposium '89
<p>
<p>
The US Army Ballistic Research Laboratory (BRL) sponsored the BRL-CAD
The US Army Ballistic Research Laboratory (BRL) sponsored the BRL-CAD
Symposium '89 at the Aberdeen Proving Ground on October 24-25.
This was the second of these annual events and was supported by the American
Defense Preparedness Association.
@@ -634,7 +634,7 @@ Please note that this change applies only to the development version so far.
Date: Sat, 30 Dec 89 5:19:36 EST
From: Mike Muuss &lt;mike@BRL.MIL&gt;
Subject: raytrace.h
BCC:
BCC:
<p>
Gary -
@@ -859,7 +859,7 @@ internal reflection inside glass, and refractive index tracking) to be
computed much more efficiently, using a_onehit=3 (IN, OUT, IN hits).
<p>
2. What are the inflip and outflip variables in the partition structure used
2. What are the inflip and outflip variables in the partition structure used
for?
<p>
@@ -926,7 +926,7 @@ a solid, or entirely outside; all partition/solid crossings have
been resolved by splitting the partition into two at the crossing point.
<p>
3. I don't quite understand your overlap handler. Does this refer to a
3. I don't quite understand your overlap handler. Does this refer to a
partition that lies in two or more regions? Why would you want to
eliminate such a partition?
@@ -1173,7 +1173,7 @@ for a response.
Plese rely to vince@atc.boeing.com
<p>
Thanks,
Thanks,
Steve Pirollo
Boeing Helicopters
Date: Fri, 23 Mar 90 14:45:30 EST
@@ -1233,8 +1233,8 @@ Subject: BRL-CAD on a Mac II
<p>
I was looking through Cakefile.defs when I noticed that it supported
a Mac II running AUX. I would like to know whether mged runs well
in this environment.
a Mac II running AUX. I would like to know whether mged runs well
in this environment.
<p>
Also, what hardware is required and/or supported.
@@ -1242,7 +1242,7 @@ Also, what hardware is required and/or supported.
<p>
Will a Mac II with an Apple color screen handle the colors of a rendered
image? Does BRL-CAD support 24 or 32 bit color boards available for the
Mac? If I add a huge hard disk and a 19 inch color monitor to a Mac II,
Mac? If I add a huge hard disk and a 19 inch color monitor to a Mac II,
can I get something close to the modelling capabilities of an Iris?
<p>
@@ -1279,7 +1279,7 @@ Subject: Re: BRL-CAD on a Mac II
Luke,
I ported BRLCAD 3.x to a MacII running AUX 1.0. The rt parts and the utilities
worked well. MGED worked poorly and required a good understanding of BRLCAD
and AUX and MacOS.
and AUX and MacOS.
<p>
Also under A/UX 1.0 there was no color support and no gray level support. BW only.
@@ -1314,7 +1314,7 @@ not as usable an Iris 4D, then we won't waste out efforts.
Also, any idea when the next release will be coming out? I've had problems
compiling 3.7 on a personal iris running IRIX 3.2.1. I circumvented the
problem by compiling everything on an Iris 4D with an older operating system
and copying the binaries to the Personal Iris.
and copying the binaries to the Personal Iris.
<p>
Thanks.
@@ -1954,7 +1954,7 @@ In terms of geometrical representation of data, BRL-CAD supports:
The original Constructive Solid Geometry (CSG) BRL database.
<p>
Extensions to include solids made from collections of
Extensions to include solids made from collections of
Uniform B-Spline Surfaces as well as
Non-Uniform Rational B-Spline [NURB] Surfaces.
@@ -2316,20 +2316,20 @@ Subject: Choosing Workstations for Use with BRL-CAD
<p>
We are considering the purchase of several workstations for use by
individual engineers. One of the uses of these workstations will be
modeling with the BRL-CAD package. Since we want to keep costs low
(under $25K each) and performance good, the workstations which we are
individual engineers. One of the uses of these workstations will be
modeling with the BRL-CAD package. Since we want to keep costs low
(under $25K each) and performance good, the workstations which we are
currently considering are
<p>
Personal Iris
Sparcstation
Decstation
We would be interested in hearing any comments about the above machines
as they relate to the BRL-CAD package (or general performance) and any
other machines which the BRL-CAD community deems worthy of examination.
Also, since X is available on all of these machines, we are interested in
whether or not color for X-windows will be available in the next release of
the CAD Package and when that release might be expected. Thanks.
@@ -2499,20 +2499,20 @@ Subject: Choosing Workstations for Use with BRL-CAD
<p>
We are considering the purchase of several workstations for use by
individual engineers. One of the uses of these workstations will be
modeling with the BRL-CAD package. Since we want to keep costs low
(under $25K each) and performance good, the workstations which we are
individual engineers. One of the uses of these workstations will be
modeling with the BRL-CAD package. Since we want to keep costs low
(under $25K each) and performance good, the workstations which we are
currently considering are
<p>
Personal Iris
Sparcstation
Decstation
We would be interested in hearing any comments about the above machines
as they relate to the BRL-CAD package (or general performance) and any
other machines which the BRL-CAD community deems worthy of examination.
Also, since X is available on all of these machines, we are interested in
whether or not color for X-windows will be available in the next release of
the CAD Package and when that release might be expected. Thanks.
@@ -2685,7 +2685,7 @@ CLUT (gif format) is not at all simple. Paul Heckbert (sp) wrote the
definitive paper on 24 to 8CLUT. His method produces some very nice
output.
1) Cut from 24 to 15bits by chopping the low 3 bits of each color.
2) With the reduced color space, count the number of hits for
2) With the reduced color space, count the number of hits for
each color. (Generate a histogram)
3) In color space,
a) cut at median point along the longest axis of largest box.
@@ -2699,7 +2699,7 @@ bit image into an 8bit image of CLUT look ups.
<p>
I have not (yet) implimented a color dither program but the theary is the
same as for doing black and white dithering. I will try and describe
same as for doing black and white dithering. I will try and describe
a Floyd-Steinburg color dither.
<p>
@@ -2775,7 +2775,7 @@ Subject: re:Spline Solids
<p>
The teapot program is good example for creating a b-spline solid
using the libspl library, the fact that its from IEEE CG&A, is
just a side light. Other splines solids and surfaces should be created
just a side light. Other splines solids and surfaces should be created
in a similar manner. But to answer your questions.
<p>
@@ -2783,9 +2783,9 @@ in a similar manner. But to answer your questions.
2. What determines the # granules of ctls?
<p>
A granule is the size of a database record as defined in
A granule is the size of a database record as defined in
h/db.h and usually is a solid description. In a few instances
such as ARS solids and Spline solids a granule can contain
such as ARS solids and Spline solids a granule can contain
floating point values of either knots or control points.
<p>
@@ -2810,13 +2810,13 @@ Thus a spline solid database record consists
<p>
The geom type is whether the b-spline surface control points
consist of Rational 3 space points (X,Y,Z,W) or
consist of Rational 3 space points (X,Y,Z,W) or
Non Rational 3 Space points (X,y,Z).
<p>
-Paul
Date: Tue, 18 Sep 90 9:28:55 EDT
From: Robert Shnidman (VLD/VMB) &lt;robert@BRL.MIL&gt;
Subject: Re: [J. Terrence Klopcic: [J. Terrence Klopcic: Ullyatt]]
@@ -2838,14 +2838,14 @@ From: "John R. Anderson" (VLD/ASB) &lt;jra@BRL.MIL&gt;
Subject: BRLCAD on a Sparcstation 1+
<p>
Out of curiosity I installed BRLCAD on my new SParcstation 1+.
Out of curiosity I installed BRLCAD on my new SParcstation 1+.
I have included the bechmark results below. Everything compiled fine
with the exceptions of LGT and FBED. MGED seems to work nicely under
SUNVIEW. The operating system is SunOS 4.1.
<p>
Abs whisper.brl.mil 1118.35 561.81 473.52 439.76 509.26 620.54 Tue Oct 23 18:18:24 EDT 1990
*vgr whisper.brl.mil 8.69 10.31 10.48 10.89 10.38 10.15
*vgr whisper.brl.mil 8.69 10.31 10.48 10.89 10.38 10.15
Date: Sat, 3 Nov 90 16:13:48 EST
From: Mike Muuss &lt;mike@BRL.MIL&gt;
Subject: Minor additions
@@ -3233,7 +3233,7 @@ Subject: Re: lgt on Sun3
<p>
Mike,
I fixed the warnings generated on vision (under SunOS 4 Sun fixed
I fixed the warnings generated on vision (under SunOS 4 Sun fixed
the signal() declaration). Since there is no preprocessor define specific
to SunOS 4, warnings will now occur under older releases unless the user
compiles with -DSunOS4=0. Correct code will be produced either way, but
@@ -3598,25 +3598,25 @@ Try this procedure to see what you actually have.
2) Keep the group "hepro" into a separate file, and kill it in this database.
3) Exit mged, and then start it up again. This allows mged to build its
directory anew and thus pick up the directory entry it ignored previously.
4) You should see a group called "hepro" still in your database. If so, then
4) You should see a group called "hepro" still in your database. If so, then
somehow there were two objects in the old .vg database called "hepro".
I don't really know how that would have happened, but there was a lot
less error checking back then.
5) Assuming you find that you still have an object "hepro", compare it
to the one in the separate file. (You can bring the other file into
to the one in the separate file. (You can bring the other file into
the database with some prefix just for comparison.)
6) If, by chance, you still receive the same error message, then you will
have to repeat this procedure until everthing in your database is
singly defined.
singly defined.
<p>
One duplicate entry message is printed for each object name found
duplicated. If you see the same object name appearing multiple times
then you have some serious work cut out for you.
then you have some serious work cut out for you.
<p>
You get rid of the extra definitions by 'keep'ing the duplicated object
into a separate file. Then you kill the object in your database, and exit
into a separate file. Then you kill the object in your database, and exit
mged. Now start mged up again, kill the object again (to get rid of the
entry that was being ignored), and 'concat' the object back in from your
separate file.
@@ -3637,8 +3637,8 @@ Subject: Multiple Processors
<p>
I have written an application that uses raytracing and I
am interested in utilizing multiple processors. What do
I need to do to implement something similar to the -P
am interested in utilizing multiple processors. What do
I need to do to implement something similar to the -P
option on rt?
<p>
@@ -3716,8 +3716,8 @@ Subject: Re: Multiple Processors
<p>
&gt; I have written an application that uses raytracing and I
&gt; am interested in utilizing multiple processors. What do
&gt; I need to do to implement something similar to the -P
&gt; am interested in utilizing multiple processors. What do
&gt; I need to do to implement something similar to the -P
&gt; option on rt?
<p>
@@ -3787,7 +3787,7 @@ do_run( a, b )
<p>
/*
* W O R K E R
*
*
* Compute one pixel, and store it.
*/
void
@@ -3848,7 +3848,7 @@ used:
<p>
/*
* V I E W _ P I X E L
*
*
* Arrange to have the pixel output.
*/
void
@@ -4321,7 +4321,7 @@ through verious prospectives.
<p>
Originally the perspective key toggled between 90% perspective and
orthagonal. This would simulate the -p90 and -p0 (or nothing) option
orthagonal. This would simulate the -p90 and -p0 (or nothing) option
to rt.
<p>
@@ -4557,7 +4557,7 @@ it is important? Is there any way to bypass this?
BRL-CAD Release 3.5 Graphics Editor (MGED) Compilation 1
Mon Feb 18 22:10:03 MET 1991
root@itnsg1:/home/brl/mged
attach (nu|tek|tek4109|ps|plot|sgi)[nu]? sgi
ERROR #104 dbtext: ERR_NODIALDAEMON
ATTACHING sgi (SGI 4d)
@@ -4569,7 +4569,7 @@ But the major problem is that "fbed" core dumps with:
Segmentation fault (core dumped)
<p>
And this seems a big problem to solve,
And this seems a big problem to solve,
any experience?
<p>
@@ -4581,7 +4581,7 @@ p.s.:
I made the kernel mods that you suggested.
<p>
--
--
<p>
---------------------------------------------------------------------------
@@ -4729,7 +4729,7 @@ In terms of geometrical representation of data, BRL-CAD supports:
The original Constructive Solid Geometry (CSG) BRL database.
<p>
Extensions to include solids made from collections of
Extensions to include solids made from collections of
Uniform B-Spline Surfaces as well as
Non-Uniform Rational B-Spline [NURB] Surfaces.
@@ -4979,7 +4979,7 @@ Date: 6 Mar 91 16:09:55 GMT
&gt;In comp.graphics, pdbourke@ccu1.aukuni.ac.nz (Bourke) writes:
&gt;
&gt; Could someone please supply me with information on the IGES graphics
&gt; file format. Like, who developed it, what are its strong points,
&gt; file format. Like, who developed it, what are its strong points,
&gt; what are its problems. How successful is it...etc...
<p>
@@ -5207,7 +5207,7 @@ their advanced animation package. That is as follows:
o square ! object name : Not used in the advanced animation package [optional]
<p>
mtllib my.mtl your.mtl project.mtl ... ! material library search
mtllib my.mtl your.mtl project.mtl ... ! material library search
! path [optional]
maplib my.map your.map ... ! map library search path
![optional]
@@ -5240,14 +5240,14 @@ s 1 ! smoothing group : average vertex normals for shared verticies
s off ! turn smoothing off
<p>
v 0.0 0.0 0.0 ! vertex position
v 0.0 0.0 0.0 ! vertex position
v 1.0 0.0 0.0
v 1.0 1.0 0.0
v 0.0 1.0 0.0
<p>
vt 0.0 0.0 0.0 ! texture vertex position
vt 0.0 1.0 0.0
vt 0.0 1.0 0.0
vt 1.0 1.0 0.0
vt 1.0 0.0 0.0
@@ -5261,7 +5261,7 @@ vn -1.0 1.0 1.0
<p>
p 1 2 3 4 ! a series of four points made up of four index
! references to verticies ( 1 base )
l 1 2 3 4 ! a line made up of four points with the
!topology of vertex 1 to 2 to 3 to 4
@@ -5442,19 +5442,19 @@ under SunOS 4.1.1 or on a Sparc, just 4.0.3 on a 3/80 where it compiles
cleanly.
<p>
|&gt; I have run into a couple of problems installing BRL-CAD on out SPARCserver
|&gt; I have run into a couple of problems installing BRL/CAD on out SPARCserver
|&gt; 490 under SunOS v4.1.1.
|&gt;
|&gt;
|&gt; The major one comes from the following definitions in the include file
|&gt; /usr/include/sys/sysmacros.h:
|&gt;
|&gt;
|&gt; * Major/minor device constructing/busting macros.
|&gt; /* minor part of a device */
|&gt; #define minor(x) ((int)((x)&0377))
|&gt;
|&gt;
|&gt; /* major part of a device */
|&gt; #define major(x) ((int)(((unsigned)(x)&gt;&gt;8)&0377))
|&gt;
|&gt;
|&gt; which conflict with the variables major and minor in fbed.c. We get them
|&gt; because fbed.c includes fcntl.h, which includes sys/fcntlcom.h, which
|&gt; includes sys/stat.h, which includes sys/sysmacros.h.
@@ -5464,7 +5464,7 @@ I have changed the name of the variables "minor" and "major" in fbed.c to
<p>
|&gt; The other problem is that the following statements in fbed/std.h are
|&gt; causing the compiler to give 'illegal type combination' messages:
|&gt;
|&gt;
|&gt; typedef unsigned char u_char; /* unsigned integer types */
|&gt; typedef unsigned short u_short;
|&gt; #ifdef pdp11
@@ -5472,7 +5472,7 @@ I have changed the name of the variables "minor" and "major" in fbed.c to
|&gt; #else
|&gt; typedef unsigned long u_long;
|&gt; #endif
|&gt;
|&gt;
|&gt; These occur in fbed/fbed.c and fbed/execshell.c.
The following is from the current std.h:
@@ -5549,7 +5549,7 @@ int sig;
<p>
|&gt; Enjoy,
|&gt;
|&gt;
|&gt; Dick
I already have. :-{
Thanks for the detailed bug reports.
@@ -5706,19 +5706,19 @@ Symposium will be included in the upcoming release 4.0. Here
is a brief description of its capabilities:
<p>
Iges-g converts IGES files (ASCII format) to BRL-CAD
Iges-g converts IGES files (ASCII format) to BRL/CAD
database format. The IGES file is expected to conform to
the ANSI standard, ASME Y14.26M-1989, which is esentially
IGES 4.0. All IGES CSG objects are converted to BRLCAD
equivalents. Most conversions are exact, with the exceptions
of the solid of revolution and the solid of linear extru-
sion. These solids do not exist in BRL-CAD and are therefore
sion. These solids do not exist in BRL/CAD and are therefore
approximated. The solid of revolution is built from a series
of truncated right cones developed by approximating the
curve to be revolved with a series of straight line sege-
ments. The extrusion is similarly handled by approximating
the curve to be extruded with straight line segments and
using that to build a BRL-CAD polysolid.
using that to build a BRL/CAD polysolid.
<p>
IGES non-uniform rational B-spline surfaces (NURBS) are
@@ -5810,7 +5810,7 @@ the radiative exchange taking place in an engine compartment.
<p>
IRPREP will be released in the upcoming 4.0 Release of the BRL-CAD package.
POC: Edwin Davisson, Ext. 6711
POC: Edwin Davisson, Ext. 6711
<p>
@@ -5841,7 +5841,7 @@ Subject: Cell Plot overlays
<p>
I am pleased to announce that BRL-CAD now has the ability to do quick cell-plot
overlays. Cell-fb now has a logging option which prints out information
overlays. Cell-fb now has a logging option which prints out information
which is used by rtregis (a program that constructs a registration matrix
for use by plrot) to register an RT produced hidden line removed plot file
with the cell-plot.
@@ -5891,7 +5891,7 @@ My file is on /n/walrus/s/scoates/IR.prep.stick.
rt_bomb
rt_identify_magic
rt_units_conversion
$
$
$ cc stick.c /usr/brlcad/lib/libwdb.a.bak -lm -o stick
$
@@ -5918,7 +5918,7 @@ Sue-
<p>
The problem is that you need to include two more libraries with the
libwdb now. libwdb now depends on routines that
libwdb now. libwdb now depends on routines that
are found in librt, another system library must also be included on
the SGI machines -lmpc. The following command worked fine.
@@ -6121,22 +6121,22 @@ POC: Dr Donald Haskell (301)-278-2032.
THE AIR SYSTEMS BRANCH TRAINS WEST POINT CADET IN RESEARCH
<p>
West Point Cadet Frank DeGeorge continued a tradition of
association and exchange between West Point and the BRL - Air Systems
Branch (ASB). A participant in the United States Military Academy
West Point Cadet Frank DeGeorge continued a tradition of
association and exchange between West Point and the BRL - Air Systems
Branch (ASB). A participant in the United States Military Academy
Summer Research Program, from 3 to 28 June, 1991, Cadet DeGeorge
assisted in development of Height-Velocity damage curves for the HIND-F
helicopter following complete loss of power to one of two engines and
two of two engines. Cadet DeGeorge was responsible for gathering
helicopter configuration data, calculation of steady level flight trim
two of two engines. Cadet DeGeorge was responsible for gathering
helicopter configuration data, calculation of steady level flight trim
states (from hover to maximum forward speed), and determination of
optimal autorotation and landing "flare" states. In support of the
vulnerability/lethality analysis for Live Fire Test of the M830E1 HEAT
Multi-Purpose Cartridge, Cadet DeGeorge's assistance was essential
Multi-Purpose Cartridge, Cadet DeGeorge's assistance was essential
to the timely completion of the analysis. For the past two years the
ASB received West Point Cadets under The United States Military Academy
Summer Research Program. The ASB will continue to participate in this
important research program. POC: Dr Donald Haskell (301)-278-2032.
important research program. POC: Dr Donald Haskell (301)-278-2032.
<p>
@@ -6160,7 +6160,7 @@ the final spline shape probably more accurately approaches the
theoretical NACA shape than can be effected in metal fabrication by
airframe manufacturers. The spline shape is then cast into the BRL-CAD
spline solid and thus is compatible with both current BRL-CAD models as
well as new models. POC is Dr. Donald Haskell, (301) 278-2608.
well as new models. POC is Dr. Donald Haskell, (301) 278-2608.
Date: Tue, 16 Jul 91 1:56:08 EDT
From: Mike Muuss &lt;mike@BRL.MIL&gt;
Subject: MGED window size
@@ -6495,11 +6495,11 @@ In your message, you indicated:
&gt;&gt; some problem with the include file for this function. I
&gt;&gt; statically declare the 'struct application ' variable I
&gt;&gt; use and assign it specific values.
&gt;&gt;
&gt;&gt;
&gt;&gt; Could someone please elaborate on the problems
&gt;&gt; and provide me a list of possible solutions or at least
&gt;&gt; some explainations???
&gt;&gt;
&gt;&gt;
<p>
I am not aware of any problems with the header file raytrace.h,
@@ -6629,7 +6629,7 @@ Many of us have noticed that BRLCAD 4.0beta requires substantially more disk
space than 3.7. In some cases, utilities have more than doubled in size.
I went looking for the reasons for this today. It would appear that the
greatest difference comes from the fact that the SGI now links with the X11
libarary. This is somewhat compounded by the fact that we are not currently
libarary. This is somewhat compounded by the fact that we are not currently
using a shared library for X11.
<p>
@@ -6663,11 +6663,11 @@ In your note of Mon, 29 Jul, you mentioned an interesting problem:
&gt;&gt; e r.b*. This is really nice. However, there is still a limit on
&gt;&gt; the number of regions that rt can handle. The following lines show
&gt;&gt; what I typed and the errors I got.
&gt;&gt;
&gt;&gt;
&gt;&gt; e r.b* (This displays approximately 1610 regions.)
&gt;&gt; rt -s 1024 -P 4
&gt;&gt; rt: Arg list too long Abnormal exit x 1000, return (exit) code=16
&gt;&gt;
&gt;&gt;
&gt;&gt; I got around this by grouping all my regions into one group (g cylinders
&gt;&gt; r.b*).
File diff suppressed because it is too large Load Diff

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