00:48.56 |
*** join/#brlcad louipc_
(n=louipc@bas8-toronto63-1177706531.dsl.bell.ca) |
01:37.08 |
*** join/#brlcad
RodGallowGlass
(n=mario_du@bas2-sudbury98-1177871953.dsl.bell.ca) |
01:38.10 |
RodGallowGlass |
winsock.h, unistd.h, shouldn't that be one or
the other? ahh never mind I keep forgetting I'm on a Cygwin system
here :) |
01:47.49 |
*** join/#brlcad
RodGallowGlass
(n=mario_du@bas2-sudbury98-1177871953.dsl.bell.ca) |
02:58.49 |
*** join/#brlcad akreal
(n=ak@87.249.56.198) |
03:07.17 |
CIA-4 |
BRL-CAD: 03brlcad *
10brlcad/src/other/openNURBS/opennurbs_point.cpp: use common.h so
it can work on non-configure platforms too |
03:08.38 |
CIA-4 |
BRL-CAD: 03brlcad *
10brlcad/src/other/openNURBS/opennurbs_system.h: don't need SUNOS
now that he found the right one |
04:38.26 |
*** join/#brlcad bjorkBSD
(n=bjork@ip70-178-214-102.ks.ks.cox.net) |
04:57.27 |
*** join/#brlcad mario
(n=wawio@228-173.126-70.tampabay.res.rr.com) |
05:07.36 |
*** join/#brlcad cad13
(n=467eade4@bz.bzflag.bz) |
05:07.59 |
brlcad |
howdy cad13 |
06:08.18 |
*** join/#brlcad elite01
(n=elite01@195.37.106.60) |
06:28.23 |
*** join/#brlcad Waimea
(i=clock@77-56-111-45.dclient.hispeed.ch) |
07:14.39 |
*** join/#brlcad Elperion
(n=Bary@p54876C43.dip.t-dialin.net) |
07:41.53 |
*** join/#brlcad Waimea
(n=clock@zux221-122-143.adsl.green.ch) |
09:02.37 |
*** join/#brlcad yukonbob
(n=bch@whthyt247-240.northwestel.net) |
09:16.46 |
*** join/#brlcad Waimea
(n=clock@zux221-122-143.adsl.green.ch) |
09:45.10 |
*** join/#brlcad docelic
(n=docelic@212.15.183.71) |
09:50.38 |
yukonbob |
can anybody explain the way to use the dsp
primitive, and any 'gotchas' associated with it (ie: is it
considered experimental (and why), does it incur a large
performance penalty?, etc.) |
10:01.01 |
*** join/#brlcad elite01
(n=elite01@dslc-082-082-067-161.pools.arcor-ip.net) |
11:58.03 |
*** join/#brlcad cad22
(n=d911cafe@bz.bzflag.bz) |
12:13.45 |
*** join/#brlcad elite01_
(n=elite01@dslc-082-082-066-123.pools.arcor-ip.net) |
15:01.08 |
*** join/#brlcad thing0
(i=thing0@124-168-69-106.dyn.iinet.net.au) |
15:02.40 |
thing0 |
hey all |
15:02.44 |
thing0 |
hey brlcad |
15:08.51 |
brlcad |
howdy |
15:09.33 |
thing0 |
I replied to your test email |
15:12.30 |
*** join/#brlcad akreal
(n=ak@87.249.56.198) |
15:13.46 |
*** join/#brlcad ak__
(n=ak@87.249.56.198) |
15:15.58 |
*** join/#brlcad louipc
(n=louipc@bas8-toronto63-1177614168.dsl.bell.ca) |
15:20.58 |
thing0 |
alright |
15:21.01 |
thing0 |
me sleep time |
15:21.08 |
thing0 |
have real work tomorrow |
15:21.09 |
thing0 |
hehe |
15:25.46 |
*** join/#brlcad b0ef
(n=b0ef@062016142179.customer.alfanett.no) |
16:15.17 |
*** join/#brlcad akreal
(n=ak@87.249.56.198) |
18:01.52 |
``Erik |
I WANT MY DMAN TOY CAR@!#~! |
18:07.14 |
*** join/#brlcad poolio
(n=poolio@c-69-251-3-107.hsd1.md.comcast.net) |
18:21.29 |
*** join/#brlcad poolio_
(n=poolio@c-69-251-3-107.hsd1.md.comcast.net) |
19:13.21 |
*** join/#brlcad cadguy
(n=cadguy@trapezewireless121.insecure.utah.edu) |
19:44.04 |
*** join/#brlcad Elperion
(n=Bary@p54876C43.dip.t-dialin.net) |
20:18.31 |
CIA-4 |
BRL-CAD: 03jlowenz *
10brlcad/src/conv/iges/Makefile.am: Remove the standalone pullback
curve impl from compilation (need to delete files later) |
20:20.40 |
CIA-4 |
BRL-CAD: 03jlowenz * 10brlcad/ (6 files in 3
dirs): Debug IGES parsing/handling and openNURBS extensions. Still
not building a simple B-Rep correctly (trim vertices not
agreeing) |
20:50.51 |
*** join/#brlcad PrezKennedy
(n=Matthew@c-69-255-112-97.hsd1.md.comcast.net) |
21:15.43 |
*** join/#brlcad cad64
(n=96a3260a@bz.bzflag.bz) |
21:26.46 |
*** join/#brlcad cad07
(n=96a3260a@bz.bzflag.bz) |
21:27.50 |
yukonbob |
I'll put this out one more time :) |
21:27.57 |
yukonbob |
can anybody explain the way to use the dsp
primitive, and any 'gotchas' associated with it (ie: is it
considered experimental (and why), does it incur a large
performance penalty?, etc.) |
21:29.04 |
*** join/#brlcad poolio
(n=poolio@c-69-251-3-107.hsd1.md.comcast.net) |
21:32.00 |
brlcad |
yukonbob: hm, i missed that question
originally apparently |
21:32.06 |
brlcad |
and yes, I can explain how to use it |
21:32.39 |
brlcad |
there aren't any gotchas that come to mind
immediately, but there probably are some that I just implicitly
don't think about any more -- it's certainly not
experimental |
21:33.48 |
brlcad |
it's actually a rather highly optimized
terrain in-core implementation, one of the fastest you'll find
particularly for ray-tracing massive datasets |
21:34.21 |
brlcad |
basically to create a dsp, you need to prepare
a data file -- this data file needs to be a binary file filled with
unsigned short integer values |
21:34.45 |
brlcad |
there are a variety of ways to get that,
depending on what format you have to start with, but a simple image
can work for example as a starting point |
21:34.57 |
yukonbob |
ah --- I was guessing what the format might
be, and I've been trying arrays of text values with various
seperators ;) |
21:37.36 |
yukonbob |
is Create->dsp the only way to create one,
or is there an mged command-line version as well? |
21:39.06 |
brlcad |
anything you can do in the gui had an mged
command line variant .. *anything* ;) |
21:39.18 |
yukonbob |
!nice -- that's what I like to hear
:) |
21:39.48 |
brlcad |
the gui really just kicks off commands, so
it's all uniform |
21:40.09 |
brlcad |
there are, though, plenty of things you can do
on the command line that you can't do via the gui |
21:46.19 |
yukonbob |
brlcad: when you're talking about using an
image for the shortint values, what do you mean? Is there a special
header required for the dsp data, or can I just use a C prog that
dumps shortints to a file and use that? |
21:48.52 |
brlcad |
yukonbob: heh, if you want to write a C prog
that dumps shortints, then you're golden |
21:49.05 |
brlcad |
but there may already be tools depending on
what data you're starting with |
21:50.53 |
yukonbob |
brlcad: I'm not starting with any data per se,
just exploring brlcad :) -- I _really_ like the precision, and the
flexibility/strength of using Tcl in it, so now I'm exploring the
features I haven't touched yet, and trying to figure out what I can
use it for besides rapid image prototyping... |
21:51.16 |
brlcad |
e.g. if I have a brl-cad .pix file (3-channel,
24 bpp interleaved RGB raw binary image file) -- I can use pix-bw
(1-channel 8 bpp raw b&w binary image file) to get monotonic
values and then use 'cv' to convert to unsigned short
ints |
21:53.12 |
yukonbob |
OK -- that's something I can try... |
21:53.40 |
brlcad |
here's an example that I did a few months back
pretty quickly -- taking data for the puget sound: http://www.cc.gatech.edu/projects/large_models/ps.html |
21:54.12 |
brlcad |
those happen to be 16bit values already
(0-65535) which is what the dsp uses |
21:54.33 |
brlcad |
create a dsp, accentuate the vertical scaling
for effect, and you get http://ftp.brlcad.org/images/puget_mged.png |
21:55.40 |
yukonbob |
OK -- the first site you gave is where you
grabbed the data from, then the ftp.brlcad.org[...] is your
processing of that same data... |
21:55.48 |
brlcad |
right |
21:57.20 |
brlcad |
when you create a dsp, you have two options --
you can keep the data in an external file, or stash the data into
the .g file |
21:57.20 |
brlcad |
use the "in" command to create one |
22:02.30 |
yukonbob |
excellent -- now, before I take too much more
of your time (and you may not have a quick answer for this) -- what
can I do with brlcad besides generate images to screen -- I see
when I render that I can get clues about collisions in 3d space
where object "illegally" intersect, and I can spin/flip/cut-away
objects, etc., but what about what I've read about ballistic
analysis, and radiation, etc... is this stuff done w/ data that
brlcad knows a |
22:07.04 |
*** join/#brlcad louipc_
(n=louipc@bas8-toronto63-1096670012.dsl.bell.ca) |
22:11.06 |
*** join/#brlcad poolio_
(n=poolio@c-69-251-3-107.hsd1.md.comcast.net) |
22:12.12 |
brlcad |
yukonbob: your question was cut-off at "that
brlcad knows a" |
22:12.30 |
yukonbob |
that brlcad knows about, and does it ship with
these tools? Is there a site that scratches the surface of
features like this? (I'm opening up a _huge_ subject area I
realize, and just need a pointer to a site, or we can talk about
this over time at some later date ;) |
22:12.42 |
brlcad |
there are a variety of geometric analyses that
you can run as well as other visualizations |
22:13.22 |
*** join/#brlcad louipc__
(n=louipc@bas8-toronto63-1096667321.dsl.bell.ca) |
22:14.46 |
brlcad |
yukonbob: brl-cad tries to strictly limit
itself to solid modeling, geometric representation, geometric
analysis (answering questions about the physical properties of
something modeled) -- the other analyses that we integrate with are
predominantly external codes with massive efforts of their own into
various methodologies |
22:15.21 |
brlcad |
e.g. the various equations for ballistics
penetration are not something you'll likely find in brl-cad or on
any website for that matter.. |
22:17.26 |
RodGallowGlass |
brlcad: that command line entry in the gui is
quite nice, having the gui up and issuing rot 10 10 10 is nifty,got
it to work in that mingw build I sent you too. |
22:18.02 |
yukonbob |
OK -- I'm not actually interested in
ballistics or radiation, but was curious about what else can be
done w/ brlcad and it's data -- there are references to radiation,
ballistics, etc on various sites, so that's why I brought those
up... I'll have more questions about the "answering questions about
physical properties" later -- for now I'll let you get on with your
day :) |
22:18.52 |
yukonbob |
brlcad: thanks very much for your time... I
appreciate it :) |
22:19.30 |
brlcad |
yukonbob: brl-cad integrated into a lot of
external analysis codes in particular for it's ray-tracing engine
-- it's rather trivial to take a given model and ask brl-cad
questions about a shotline .. where is the geometry on a given
shotline, how thick is it, what material is it, what was the
obliquity, etc -- that in turn can drive other decisions |
22:21.57 |
*** join/#brlcad Laniakea
(i=clock@77-56-108-15.dclient.hispeed.ch) |
22:21.57 |
brlcad |
what brl-cad can do analysis-wise, though, are
geometry analysis questions too -- are there overlapping materials
(rtcheck, g_qa), what's the weight of a given component (rtweight,
g_qa), center of mass, what's the projected presented area of
something (rtarea), what's the bounding box size, etc |
22:22.30 |
brlcad |
on the ray-tracing side, it has tools for
simulating optical energy, multispectral (thermal, xray, infrared)
energy, performing edge detection (rtedge) for hidden line
renderings, and a bit more |
22:23.47 |
*** join/#brlcad louipc
(n=louipc@bas8-toronto63-1096669771.dsl.bell.ca) |
22:29.35 |
yukonbob |
brlcad: I'm pretty excited by BRL-CAD -- seems
like there's lots of space for exploration... I'm glad it's got a
tcl interface for scripting too, which opens up possibilities...
thx again for your insight, and talk soon |
22:31.16 |
brlcad |
yukonbob: no problem, i'm here most of the
time or will answer the log later if i'm not ;) |
22:31.50 |
brlcad |
we're looking for new devs too so you're more
than welcome to jump in -- anything I can do to help you along,
feel free to let me know ;) |
22:33.15 |
yukonbob |
brlcad: thx -- I'm just working on a port of
brlcad to NetBSD (via pkgsrc), and think I noticed some things that
can be improved in the build process --- once I verify, I'll be
sure to pass that info on, and otherwise, look forward to being
part of the BRL-CAD community :) |
22:33.55 |
brlcad |
sweet |
22:37.56 |
PrezKennedy |
hey brlcad, have you ever visited http://thedailywtf.com/ ? |
22:43.28 |
brlcad |
I have now |
23:08.00 |
*** join/#brlcad Twingy
(n=justin@74.92.144.217) |
23:11.24 |
*** join/#brlcad poolio
(n=poolio@c-69-251-3-107.hsd1.md.comcast.net) |