00:37.11 |
brlcad |
interesting |
00:37.17 |
brlcad |
that's a good model for
demonstration |
00:43.13 |
*** part/#brlcad pinnipedia
(~dgreisen@cheney7.roaming.susx.ac.uk) |
01:25.56 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/include/bu.h: use
generic pointers for the avs min/max ranges |
01:46.59 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/fbserv/fbserv.c: instead of sleeping 5 seconds
indefinately, retry every second up to a minute before giving up on
starting the stand-alone daemon. |
02:24.53 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/ (configure.ac
m4/args.m4): prefix the ARG macro variables with bc_ so that they
do not conflict with potential argument variables being tested
(e.g. with_java was the var and java was an alias, causing an
overwrite of with_java) |
02:29.46 |
*** join/#brlcad polyspin
(~polyspin@pcp0011463358pcs.chrchv01.md.comcast.net) |
02:31.05 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/libbu/malloc.c: |
02:31.05 |
CIA-3 |
BRL-CAD: fix bu_debug memory checking.. if
run-time debugging is enabled, we cannot |
02:31.05 |
CIA-3 |
BRL-CAD: simply call calloc since we need to
allocate the extra space for BU_DEBUG_CHECK |
02:31.05 |
CIA-3 |
BRL-CAD: and BU_DEBUG_MEM_QCHECK. this of
course prevents bu barriercheck corruption and |
02:31.05 |
CIA-3 |
BRL-CAD: false-positives. (this fixes sf bug
1163383 and 1198866) |
02:34.05 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/libbu/avs.c:
make sure we're not trying to free null avs pointers. also set the
counters to zero/null when we're done just in case. |
02:38.06 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/librt/prep.c:
ws |
02:39.20 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db_open.c: no need to embed the scope in the
middle of the function for the argv array.. hope that thing is
getting free'd somewhere |
02:40.12 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db5_scan.c: contrary to popular evidence,
initialize the avs structs to empty anyways. |
02:40.42 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/NEWS: fixed libbu
run-time memory corruption checking (fixes sf bug 1198866 and
1163383) |
02:40.45 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/librt/comb.c:
ws |
02:51.32 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db5_io.c: (log message trimmed) |
02:51.32 |
CIA-3 |
BRL-CAD: rework db5_import_attributes()
hopefully resolving a long-standing (4 years) |
02:51.32 |
CIA-3 |
BRL-CAD: issue with simply referencing the
external representation's memory buffer in the |
02:51.32 |
CIA-3 |
BRL-CAD: ap pointer. this prevents a strdup
otherwise required for _every_ single |
02:51.32 |
CIA-3 |
BRL-CAD: attribute, using up twice as much
memory for attributes. this version also only |
02:51.33 |
CIA-3 |
BRL-CAD: allocates exactly what it needs
without the extra padding, and only as it needs |
02:51.35 |
CIA-3 |
BRL-CAD: it per the rate set in bu_avs_add if
AVS_ADD is defined (otherwise it's all |
03:02.42 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/dg_obj.c: help indentation by using a
preprocessor symbol for the fopen mode |
03:27.45 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/sh/elapsed.sh: if
the start and end times are actually equal, elapsed needs to be
zero seconds not 86400. more likely that we ran elapsed within a
second than it is that it took exactly a day to the
second.. |
03:57.30 |
narnia |
learner, i am shutdown my servers since i am
in court tomorrow, 11 may 2005. be back after court. |
03:57.37 |
*** part/#brlcad narnia
(~terrylr@johann.blauedonau.com) |
04:30.45 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/librt/
(prep.c wdb_obj.c): initialize the attribute value sets to empty
before passing them anywherre, there's too many implicit
assumptions occuring with them without checking their
magic/count.. |
04:34.26 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db5_io.c: |
04:34.26 |
CIA-3 |
BRL-CAD: rework the horrid attribute value
getter func yet again, semi reverting back to |
04:34.26 |
CIA-3 |
BRL-CAD: the version that allocates all of the
memory up front. there's something |
04:34.26 |
CIA-3 |
BRL-CAD: preventing the incremental allocation
from going through cleanly right now that |
04:34.26 |
CIA-3 |
BRL-CAD: should probably be debugged at some
point.. allocating up front probably only |
04:34.27 |
CIA-3 |
BRL-CAD: works because it blows away any
existing contents (whereas the incremental |
04:34.28 |
CIA-3 |
BRL-CAD: wouldn't) implying that something
isn't initialized by the time it gets here. |
04:51.57 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db5_io.c: found it! hopefully the last
uninitialized attribute value set that was preventing incremental
adds/allocations. |
05:12.00 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/db5_io.c: de-c++commentify and commentify on why
we alloc up front. there is indeed some problem with the non
bu_avs_add, but save that for future debugging. |
05:20.37 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/BUGS: |
05:20.37 |
CIA-3 |
BRL-CAD: setting src/librt/db5_io.c's AVS_ADD
off in db5_import_attributes | |
05:20.37 |
CIA-3 |
BRL-CAD: causes bad things to happen and it
really shouldn't. |
05:21.10 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/NEWS: benchmarks
actually take about 15 minutes |
05:38.25 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/librt/dg_obj.c: |
05:38.25 |
CIA-3 |
BRL-CAD: no answer from bob so rerevert the
size arguments to rt and rtcheck so that the |
05:38.25 |
CIA-3 |
BRL-CAD: defaults are used. there was a
problematic case where depending on the |
05:38.26 |
CIA-3 |
BRL-CAD: order/type of your args in mged, you
could not override the default. |
05:38.26 |
CIA-3 |
BRL-CAD: regardless, less overlap sneaks
through the cracks with the more dense grid even |
05:38.26 |
CIA-3 |
BRL-CAD: if at the expense of a little
run-time delay. was there another reason for |
05:38.27 |
CIA-3 |
BRL-CAD: setting the sizes
explicitly? |
05:41.11 |
brlcad |
and on that question, I retire for the
morning |
06:47.47 |
*** join/#brlcad d_rossberg
(~c28bf505@bz.bzflag.bz) |
10:15.31 |
*** join/#brlcad Pimpi
(~frank@p5481927A.dip0.t-ipconnect.de) |
10:21.20 |
*** join/#brlcad cad801
(~c28bf505@bz.bzflag.bz) |
10:28.56 |
archivist |
a small buglet autogen.sh has dos line ends
debian woody didnt like it |
11:31.27 |
brlcad |
oh? |
11:31.31 |
brlcad |
which two? |
11:32.05 |
archivist |
two? |
11:32.45 |
brlcad |
ahh, "DOS", not dos .. |
11:33.11 |
archivist |
hehe yes |
11:34.56 |
brlcad |
wonder how those snuck in |
11:35.34 |
archivist |
the shell gives a "file not found" its the
#!/bin/sh line that fails |
11:36.15 |
archivist |
easy done with editors these days as systems
get better at ignoring line end types |
11:36.17 |
brlcad |
hrm |
11:36.38 |
brlcad |
I just checked a local checkout and there are
no dos line endings |
11:37.21 |
archivist |
i wonder if toitoise cvs that i use added
it? |
11:37.45 |
brlcad |
ahh |
11:37.49 |
brlcad |
you're on windows? |
11:38.12 |
brlcad |
for the checkout |
11:38.25 |
archivist |
I could do with a linux system at work,
yes |
11:43.24 |
archivist |
hmm must find another way of checking out
then |
11:45.01 |
archivist |
ah tortoiseCVS has a unix line end option
:)) |
11:46.03 |
brlcad |
yes, just found that :) |
11:46.04 |
brlcad |
http://www.tortoisecvs.org/faq.html#brokenlineendings |
11:46.59 |
archivist |
I'll delete my download and have another
go |
11:54.20 |
archivist |
I thought of a curve that I dont remember
seeing anywhere yet and that is the involute curve for gear
design |
11:55.57 |
archivist |
and clockmakers need epicycloidal curves for
clock and watch gears |
15:10.41 |
*** join/#brlcad mycr0ft
(~thedoctor@pcp09883071pcs.ewndsr01.nj.comcast.net) |
16:03.38 |
brlcad |
hello mycr0ft |
16:04.41 |
mycr0ft |
hiya |
16:05.08 |
mycr0ft |
was compiling brlcad, had a problem, then
figured out it was an nvidia problem. |
16:05.27 |
mycr0ft |
All before asking anything in here. Mind if I
lurk for a while? |
16:07.57 |
brlcad |
lurk as long as you like :) |
16:40.00 |
mycr0ft |
anybody contribute a gentoo ebuild for
brlcad? |
17:20.22 |
brlcad |
someone was working on it, but they haven't
been around in a while |
17:21.34 |
brlcad |
if you do make one, I'd like to try to
integrate it into cvs so that the ebuild is automatically updated
when we make a release |
17:40.04 |
brlcad |
the biggest problem that we have to address is
the fact that with our dozen libraries and hundreds of
applications, there's a good chance we'll conflict with something
already installed |
17:40.49 |
brlcad |
our traditional solution and preference is an
isolated install root (e.g. /usr/brlcad) like X11 does |
17:41.52 |
brlcad |
the packaging systems discourage that for
consistency's sake so some changes might be warranted in the build
system to put things in different locations |
17:42.14 |
brlcad |
if you know of any other general policy for
resolving conflicting names, I'd be glad to hear about
them |
17:44.21 |
mycr0ft |
hehe, nope |
17:44.43 |
mycr0ft |
at least having an ebuild for local installs
would be useful |
17:45.10 |
mycr0ft |
even if directory placement offends the
sensibilities of the powers that be |
17:45.27 |
mycr0ft |
I had no problem installing into my
/home |
17:45.41 |
brlcad |
:) |
17:45.47 |
mycr0ft |
So a /usr/local or a /usr/brlcad should be
fine too. |
17:47.23 |
mycr0ft |
I'll post to the discussion list if I get one
to work. I sub-ed today |
17:48.18 |
brlcad |
ever used swig? |
17:48.46 |
brlcad |
curious as to how it will wrap a c++
object/method |
17:49.09 |
brlcad |
sorry, completely unrelated topic.. just
muusing |
18:55.40 |
*** join/#brlcad noyb
(~noyb@pool-71-108-66-222.lsanca.dsl-w.verizon.net) |
18:56.35 |
noyb |
brlcad: as I was saying at #bzflag... sorry I
missed you. I fell asleep moments after I called you. |
18:57.07 |
brlcad |
i saw, no problem |
18:57.20 |
noyb |
ok. cool. it's been months. what's
new? |
18:58.22 |
brlcad |
oh, depends what interests you :) |
18:58.29 |
brlcad |
lots of dev'ing |
18:58.36 |
noyb |
did you (or anybody) make a translator thingy
for making maps with brlcad? |
18:58.40 |
brlcad |
build fixes, bug fixes, features |
18:59.00 |
brlcad |
i haven't gotten back to that yet, but it's
still high on my list of things to get working on |
18:59.02 |
noyb |
cool |
18:59.42 |
noyb |
that's ok, I haven't upgraded from 7.0 yet, so
it would have been wasted on me anyway. :-) |
19:01.40 |
noyb |
I just got the 7.2.2 tarball... is there a
sort of "what's new" file in there? |
19:01.55 |
brlcad |
7.2.4 will be released later today |
19:02.16 |
brlcad |
yes, there's a NEWS file that has the list of
changes |
19:02.43 |
noyb |
shucks... ok I'll wait. |
19:04.00 |
noyb |
do you mind putting up a MD5 checksum for the
files? I noticed today that sf.net has some things for download
that do not match their md5 so I trashed 'em. |
19:05.20 |
brlcad |
where are you seeing the md5 on
sf.net? |
19:06.19 |
noyb |
not for brlcad, but for a different package.
sry I didn't clarify that. |
19:07.11 |
brlcad |
ahh |
19:07.37 |
noyb |
it seems that all of the mirrors have the
wrong size file. I had the file already, and it matches the md5
but the ones on the mirrors do not. strange. |
19:08.05 |
noyb |
issues at sf.net or isolated case? |
19:09.47 |
archivist |
they do have their fair share of issues, delay
passing files about is probably a good reason |
19:23.46 |
noyb |
with 99,000+ projects... something's bound to
go wrong... |
19:29.07 |
mycr0ft |
brlcad: sorry. sh I have used swig for python
wrapping of C, not C++. (was away parenting) |
19:55.28 |
brlcad |
mycr0ft: no problem, I never expect an
immediate response from any channel/discussion ;) |
20:25.09 |
*** join/#brlcad disgruntled
(~user@client-82-13-47-32.brhm.adsl.virgin.net) |
20:26.27 |
*** part/#brlcad
disgruntled_goat
(~user@client-82-13-47-32.brhm.adsl.virgin.net) |
20:29.20 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/HACKING:
ChangeLog is autogenerated, so nothing to check prior to
release |
21:40.19 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/ChangeLog:
changelog entries from 7.2.2 to 7.2.4 for release |
21:45.35 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/libpkg/pkg.c:
s/syserr/strerror/ |
21:50.48 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/src/burst/prnt.c:
avoid sys_nerr for solaris |
21:57.05 |
CIA-3 |
BRL-CAD: 03brlcad *
10brlcad/src/util/Makefile.am: ttcp needs socket and nsl (solaris
choked) |
22:52.07 |
*** join/#brlcad narnia
(~terrylr@johann.blauedonau.com) |
22:58.46 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/AUTHORS:
contacted durfee, he was at cmu at the time (as well as bel air
hs). shumaker has been gubbymint for a little while now. |
22:58.49 |
brlcad |
wb narnia |
22:59.34 |
narnia |
brlcad, court sucked. |
22:59.59 |
brlcad |
sorry to hear that |
23:00.07 |
brlcad |
you had better news last time |
23:00.15 |
narnia |
brlcad, i have 30,000+ pages of legal
documents on a cdrom. the opposing lawyers now want me to print
them out. |
23:01.36 |
narnia |
i figure that is 5 cases of paper and at least
two laser jet toners or 12 ink jet cartridges for the hp all-in-one
7100 of my daughter. |
23:02.07 |
noyb |
take the job to Kinko's... get a receipt and
slap it on the other lawyers when you win... :-) |
23:02.11 |
narnia |
the legal documents are e-mail messages in
mbox format. |
23:02.39 |
noyb |
mp can be your friend. nice output of mbox
format. |
23:02.53 |
narnia |
kinko's want $3000.00 usd to print it.
needless to say i do not have $3000.00 usd. |
23:03.36 |
brlcad |
shouldn't your lawyer be dealing with
that? |
23:04.04 |
noyb |
print it in *very* small print... ? (they
probably didn't specify) :) |
23:04.23 |
narnia |
brlcad, my lawyers fought hard to prevent the
opposing lawyers request. |
23:04.44 |
noyb |
3 points should be fine, and with mpage you
could get 9 or 16 "pages" per page... |
23:05.44 |
narnia |
the opposing lawyers won their argument when
they produced reams of paper of e-mail messages in mime format (
base64) not human readbale. |
23:06.35 |
narnia |
it is a stalling tactic. |
23:06.37 |
brlcad |
that would usually imply office
documents |
23:07.52 |
narnia |
i also have my job search data on the cdrom.
6000+ possible job hits which i sent resumes to. those are in
html. |
23:08.41 |
narnia |
there are also pdf and ps (postscript
files). |
23:08.46 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/ChangeLog: add
the last minute solaris fixes |
23:09.43 |
narnia |
the opposing lawyers also spent nearly an hour
questioning me about my never using anything microsoft. |
23:10.35 |
narnia |
i kept telling them i always owned apple macs
or ran linux, one of the bsds. |
23:11.13 |
archivist |
sounds good enough for groklaw |
23:11.19 |
brlcad |
let me guess, the requested evidence that
you've tried to get a job, you gave them a disc of your e-mail,
they printed it out saying "we can't read it", and then got the
judge to put the burden back on you |
23:11.32 |
narnia |
yes |
23:14.10 |
narnia |
their request is a two-edge sword. once those
30000+ pages are submitted as evidence for the opposing lawyers to
get their copies they have to pay $0.50 us cents per page to the
clerk of the court. so they are looking at $15,000.00 usd per
copy. |
23:15.57 |
brlcad |
pennies to them in the big scheme of the
lawsuit though, I'm sure |
23:16.00 |
narnia |
total court records page count would be close
to 100,000 pages. if any side thinks of appealling to higher courts
it will cost roughly $50,000.00 usd for a single copy of all court
records. |
23:19.35 |
narnia |
i feel sorry for the clerk who has to stamp
all those pages with an evidense stamp. |
23:20.57 |
brlcad |
they're either getting paid minimum wage or
they have a machine to do it |
23:21.35 |
narnia |
no they hand stamp each page. |
23:36.26 |
*** join/#brlcad cad285
(~807217a2@bz.bzflag.bz) |
23:37.33 |
cad285 |
Is anyone willing to hear my silly questions
about brlcad? Specifically on the ray-tracer? |
23:37.51 |
brlcad |
ask away silly asking person |
23:38.32 |
cad285 |
I'm interested in hijacking the brlcad
raytrace code to make my own optical design software. |
23:38.52 |
brlcad |
that's what it's designed for |
23:38.55 |
cad285 |
In particular, I would like code that finds
where ray's intersect geometry. |
23:39.02 |
cad285 |
err.. rays. |
23:39.15 |
brlcad |
okay |
23:39.21 |
cad285 |
I'm confused about the difference between
librt and rt |
23:39.30 |
brlcad |
there are at least a dozen examples of that
:) |
23:39.48 |
brlcad |
the difference is mostly design and
separation |
23:40.00 |
cad285 |
Ok, well, this is great news. |
23:40.13 |
brlcad |
much of what is in rt should be in librt, but
for historic reasons it's in the "front end" |
23:40.17 |
cad285 |
Which one provides the lowest level access to
geometrical primitives? |
23:40.29 |
brlcad |
"rt" is the actual BRL-CAD raytracer of 20
years age |
23:41.12 |
brlcad |
brl-cad actually includes several different
kinds of raytracers, all based on the same back-end and library
code |
23:41.53 |
brlcad |
first off, have you read the application
programmer's tutorial? |
23:42.03 |
cad285 |
No. |
23:42.14 |
cad285 |
I should start there I suppose :) |
23:42.15 |
brlcad |
http://brlcad.org |
23:42.20 |
brlcad |
document #5 |
23:42.41 |
brlcad |
you'll probably be particularly interested in
the rtexample.c file |
23:42.59 |
brlcad |
this file is also in the source
distribution |
23:43.03 |
cad285 |
Ok, sweet |
23:43.06 |
brlcad |
along with other kinds of examples |
23:43.11 |
cad285 |
I'll try this out, thank you for your
help. |
23:43.25 |
brlcad |
there's a pdf presentation that was given as
well on that link that explains most of the interface |
23:44.00 |
brlcad |
the basic idea is that you write hook
functions for a hit, a miss, and maybe an overlap as well as a few
other possibilities.. most only care about hit/miss |
23:44.41 |
cad285 |
And brlcad has its own language to feed in a
geometrical model? |
23:45.26 |
brlcad |
the ray setup is up to you to describe since
some fire single rays, some fire grids, some fire volumes, etc --
but the existing raytracers in src/rt/ will give you working code
examples |
23:45.39 |
brlcad |
it's own language? there is a brl-cad .g file
format |
23:46.00 |
brlcad |
there's also a brl-cad ascii .asc file
format |
23:46.29 |
brlcad |
the routines for writing out those geometry
files are also talked about in other places |
23:46.33 |
cad285 |
Ok, I should just start reading. |
23:46.49 |
cad285 |
Thank you for your help. |
23:46.54 |
brlcad |
if all you need to do is "write" geometry..
then libwdb (write database library) is where to start |
23:47.16 |
brlcad |
feel free to hang out here and ask questions
or come back when something comes up |
23:47.26 |
brlcad |
hang out long enough and someone will
answer |
23:47.50 |
cad285 |
Are you a main contributor to
brlcad? |
23:48.05 |
brlcad |
that rtexample.c file also includes example
code that opens a brl-cad .g database |
23:48.47 |
brlcad |
yeah |
23:49.13 |
brlcad |
i'm the open source lead, one of the core
devs |
23:49.16 |
*** join/#brlcad learner
(~brlcad@brlcad.bronze.supporter.pdpc) |
23:49.16 |
*** mode/#brlcad [+o learner]
by ChanServ |
23:49.23 |
brlcad |
yay, learner! |
23:50.03 |
cad285 |
Again, thanks for the help, Ill stick around,
seems interessting. |
23:50.18 |
CIA-3 |
BRL-CAD: 03brlcad * 10brlcad/NEWS: dang it,
they're enchanted enchancements |
23:54.14 |
brlcad |
cad285: cool deal -- what's the "optical
design software" if I might ask? |