00:29.34 |
*** join/#brlcad Notify
(~notify@66-118-151-70.static.sagonet.net) |
00:58.12 |
*** join/#brlcad hoiji
(671b082c@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.44) |
01:42.51 |
*** join/#brlcad KimK
(~Kim__@ip24-255-223-153.ks.ks.cox.net) |
01:54.34 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
02:09.25 |
*** join/#brlcad ries_nicked
(~ries@190.9.171.121) |
02:43.13 |
*** join/#brlcad teepee
(~teepee@gateway/tor-sasl/teepee) |
03:21.50 |
*** join/#brlcad hcurtis
(b82d2a0d@gateway/web/freenode/ip.184.45.42.13) |
03:39.13 |
*** join/#brlcad ries_nicked
(~ries@190.9.171.121) |
04:17.23 |
*** join/#brlcad ries_nicked
(~ries@190.9.171.121) |
04:40.29 |
*** join/#brlcad hcurtis
(b82d2a0d@gateway/web/freenode/ip.184.45.42.13) |
06:29.47 |
*** join/#brlcad drv_
(~smuxi@dynamic-78-8-101-9.ssp.dialog.net.pl) |
06:57.31 |
*** join/#brlcad KimK
(~Kim__@ip68-102-30-143.ks.ok.cox.net) |
08:11.29 |
*** join/#brlcad KimK
(~Kim__@ip68-102-30-143.ks.ok.cox.net) |
09:49.46 |
*** join/#brlcad Zhao_Anqing
(~clouddrif@2001:da8:e000:1a08:6d34:9345:fc98:266b) |
10:01.55 |
*** join/#brlcad KimK
(~Kim__@ip68-102-30-143.ks.ok.cox.net) |
11:52.17 |
*** join/#brlcad drv_
(~smuxi@dynamic-78-8-155-21.ssp.dialog.net.pl) |
12:30.28 |
drv_ |
Hi :) If I will start to work on raytracing I
should use OpenCL branch instead main trunk? I have some problems
with it... For example CL kernel have syntax errors (?). Was this
branch tested? |
12:34.05 |
*** join/#brlcad ries
(~ries@190.9.171.121) |
12:56.00 |
*** join/#brlcad hoiji
(671b082c@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.44) |
13:02.15 |
teepee |
drv_: maybe also post the error, I guess that
increases the chances someone can help |
13:10.04 |
drv_ |
Will I post error as bug ticket on
sourceforge? |
13:13.15 |
teepee |
drv_: if it's a compile problem which might be
on your system, you could post it on something like fpaste.org and
post the link here |
13:17.16 |
*** join/#brlcad Zhao_Anqing
(~clouddrif@2001:da8:e000:1a08:6d34:9345:fc98:266b) |
13:20.03 |
*** join/#brlcad kesha
(~kesha@14.139.122.114) |
13:20.42 |
*** join/#brlcad hoiji
(671b082c@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.44) |
13:29.02 |
drv_ |
Ok. And do you know how to copy mged output?
In help is written that "ButtonPress-2" will begin "text
operation". It's about copying? I've tried it with C, Ctrl-C,
Ctrl+Shift+C... I misunderstand something? |
13:48.00 |
teepee |
drv_: sorry, no idea |
13:51.31 |
drv_ |
So maybe you know how to raytrace a file from
command line? |
13:52.17 |
teepee |
not really, I'm hanging around here mostly
because of GSoC |
13:52.32 |
teepee |
my BRL-CAD knowledge is very much limited
right now |
13:52.52 |
drv_ |
ok, thanks a lot ;) |
14:15.08 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
14:16.10 |
*** join/#brlcad luca79
(~luca@host161-108-dynamic.15-87-r.retail.telecomitalia.it) |
14:45.49 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
15:20.35 |
*** join/#brlcad Zhao_Anqing
(~clouddrif@2001:da8:e000:1a08:6d34:9345:fc98:266b) |
16:12.27 |
*** join/#brlcad gaganjyot__
(~gagan@27.255.243.151) |
17:20.50 |
Notify |
03BRL-CAD:bob1961 * 60429
brlcad/trunk/src/tclscripts/lib/Ged.tcl: Lighten up the rgb for
Grey. |
17:39.29 |
*** join/#brlcad Zhao_Anqing
(~clouddrif@2001:da8:e000:1a08:6d34:9345:fc98:266b) |
17:42.49 |
*** join/#brlcad ishwerdas
(~ishwerdas@117.220.149.59) |
17:58.57 |
*** part/#brlcad caen23
(~caen23@109.97.108.82) |
18:27.12 |
*** join/#brlcad FreezingCold
(~FreezingC@135.0.41.14) |
18:34.20 |
*** join/#brlcad dli_
(~dli@fw.tamaggo.isp.ip4b.net) |
18:35.19 |
dli_ |
brlcad, do we have to attend this meeting?
Friday, 18 April at 19:00 UTC in #gsoc |
18:59.58 |
*** join/#brlcad javampire
(~ncsaba@p4FF72B1F.dip0.t-ipconnect.de) |
19:02.14 |
*** join/#brlcad cstirk
(~charlie@c-107-2-138-11.hsd1.co.comcast.net) |
19:08.08 |
*** join/#brlcad teepee
(~teepee@gateway/tor-sasl/teepee) |
19:44.45 |
javampire |
hi all, anybody knows by heart where I find
the BRL-CAD primitive parameters explained on an image ? I'm
playing with ASCII-art versions of that, which possibly can be
included directly in the source code, like this one: |
19:44.51 |
javampire |
http://codepad.org/QDcJR7J3 |
19:52.28 |
teepee |
javampire: that
http://brlcad.org/~gcibhlegm/piwigo/_data/i/galleries/diagrams/primitives-me.png
? |
19:53.57 |
javampire |
teepee: nope, I think there were somewhere
images for example with the order of the points of an
ARB8 |
19:54.10 |
javampire |
or the meaning of the parameters of a
torus |
19:54.12 |
javampire |
and similar |
19:56.09 |
teepee |
ahh, that I don't know |
20:20.50 |
Notify |
03BRL-CAD:starseeker * 60430
brlcad/trunk/src/tclscripts/tkcon.tcl: trim tkcon down a bit
more... |
20:44.49 |
*** join/#brlcad kesha
(~kesha@14.139.122.114) |
21:39.47 |
javampire |
this the kind of thing I had in
mind: |
21:39.48 |
javampire |
http://codepad.org/1lNAzM17 |
21:40.23 |
javampire |
the advantage against images is that it can be
pasted directly in the source code too |
21:40.46 |
javampire |
so whoever does anything on the primitive's
code, can see what it looks like |
21:42.25 |
javampire |
if it's marked appropriately, the same can be
included in any other kind of documentation, ASCII-art is something
which can be displayed anywhere a fixed size font is
available... |
21:48.17 |
Notify |
03BRL-CAD:starseeker * 60431
(brlcad/trunk/include/bu/cv.h brlcad/trunk/src/libbu/CMakeLists.txt
brlcad/trunk/src/libbu/tests/CMakeLists.txt): Add base64 encoding
and decoding to libbu, based on the public domain libb64
implementation at sourceforge. |
21:49.05 |
starseeker |
javampire: nice! |
21:49.47 |
starseeker |
are you doing that by hand? |
21:50.03 |
javampire |
starseeker: I use jave for the basic shape
then fix by hand |
21:50.29 |
``Erik |
I always used the ascii when needing that
info... there might be some buried in various reports, but I don't
think there's a canonical graphical repo of that :/ |
21:50.50 |
javampire |
well why not including in the code ? |
21:50.54 |
javampire |
in some way |
21:51.13 |
javampire |
so that it can be automatically included in
the man page too perhaps |
21:51.46 |
starseeker |
javampire: my first guess as to where to put
those would be include/rtgeom.h |
21:52.24 |
javampire |
ok, will have a look |
21:54.15 |
javampire |
hmm, rtgeom.h is indeed a good place, but I
would like to do it in a way which allows a man page of all
primitives explained |
21:54.38 |
javampire |
and that generated by a script if
possible |
21:54.46 |
starseeker |
javampire: you'll want to wrap them so they
show up in the doxygen output - see, for example,
src/libbrep/libbrep_brep_tools.h |
21:55.31 |
javampire |
yep, that looks good ! |
21:56.21 |
starseeker |
javampire: um. We've looked a little bit a
generating such pages from the source code - see the attributes man
page in doc/docbook/system/man5/en - but for now we aren't ready
with the infrastructure that would let us generate such a page
properly |
21:57.02 |
starseeker |
I'd put them in rtgeom.h for now (which *is*
where the canonical internal structures live) and we'll figure out
how to generate DocBook from it later |
21:57.28 |
starseeker |
in the meantime, the doxygen page for rtgeom.h
will be a decent start on a "primitives explanation" page |
21:59.54 |
javampire |
yes, it sounds like a good plan |
22:00.50 |
javampire |
but I would still like to find again the work
already done in this area, at least to be consistent with
it... |
22:01.01 |
*** join/#brlcad chick_
(~chick_@195.24.209.20) |
22:01.07 |
javampire |
anybody remember where those pictures live ?
I'm sure I have seen something already |
22:01.39 |
javampire |
but can't find it now on google or brlcad
site |
22:05.13 |
javampire |
starseeker: OK, there is one small problem
with the rtgeom -> for example the arb4-7 are all mapped to
arb8, but they need the most an explanation of how that mapping is
done... |
22:06.21 |
javampire |
so basically that would mean that all that
info is put to ARB8 in rtgeom.h, I don't think there's any other
good solution |
22:06.49 |
javampire |
but the actual code of mapping is in
wdb.c |
22:07.01 |
*** join/#brlcad dli_
(~dli@dsl-173-248-248-88.acanac.net) |
22:11.10 |
*** join/#brlcad chick_
(~chick_@195.24.209.21) |
22:41.57 |
brlcad |
javampire: there's an appendix at the end of
the mged tutorial (on the website, under documentation) .. it has
most of the common ones |
22:42.22 |
brlcad |
there are also several gci tasks that visually
documented the parameters for most primitives, but they're not
organized or easily accessible right now |
22:42.36 |
javampire |
brlcad: thanks, will have a look |
22:43.03 |
javampire |
would it be possible to publish those gci
results somewhere ? |
22:43.21 |
brlcad |
the source files actually often have a diagram
or description too, in src/librt/primitives/[obj]/[obj].c |
22:43.38 |
javampire |
ok, will look there too |
22:43.51 |
brlcad |
yeah, the intent IS to make them part of our
docs as a "primitive overview" document |
22:44.10 |
brlcad |
but they're not easily accessible right
now |
22:44.49 |
brlcad |
(the gci site won't let us get to our list of
completed tasks, so have to do a google site: search) |
22:45.45 |
brlcad |
http://www.google.com/search?q=primitives+diagram+site:google-melange.com |
22:48.17 |
javampire |
OK, that works too, found some of
them |
22:48.58 |
javampire |
brlcad: what do you think about ASCII art
instead of images ? |
23:00.44 |
ries |
ping brlcad |
23:39.44 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |