01:51.16 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
02:19.57 |
*** join/#brlcad nmz787_i
(nmccorkx@nat/intel/x-bbbfsdamexqxgslj) |
02:49.43 |
Notify |
03BRL-CAD:starseeker * 64193
brlcad/trunk/src/util/pixsaturate.c: Don't need this with
bio.h |
03:07.16 |
Notify |
03BRL-CAD:starseeker * 64194
(brlcad/trunk/src/libbrep/shape_recognition.cpp
brlcad/trunk/src/libbrep/shape_recognition.h and 4 others): Start
working on the common sphere case, corner fillets. |
03:34.53 |
*** join/#brlcad YashM
(~YashM@59.88.24.18) |
03:42.15 |
*** join/#brlcad
unicodesnowman (~unicodesn@167.160.164.140) |
03:47.23 |
*** join/#brlcad nmz787_i
(nmccorkx@nat/intel/x-kncpigtibzhzotbl) |
04:39.47 |
*** join/#brlcad starseek1r
(~starseeke@66-118-151-70.static.sagonet.net) |
04:40.17 |
*** join/#brlcad maths22
(~maths22@66-118-151-70.static.sagonet.net) |
05:11.46 |
*** join/#brlcad rohit0143
(~rohit@183.82.106.99) |
05:28.19 |
*** join/#brlcad rohit0143
(~rohit@14.139.82.6) |
05:34.10 |
*** join/#brlcad ignacio
(~ignacio@rev-18-85-44-59.sugarlabs.org) |
08:01.14 |
*** join/#brlcad YashM
(~YashM@59.88.24.18) |
08:17.58 |
*** join/#brlcad merzo
(~merzo@user-94-45-58-141.skif.com.ua) |
09:42.51 |
*** join/#brlcad teepee-
(bc5c2133@gateway/web/freenode/ip.188.92.33.51) |
09:55.29 |
*** join/#brlcad rohit0143
(~rohit@14.139.82.6) |
10:37.15 |
*** join/#brlcad Izakey
(~Izak@41.205.22.13) |
11:21.30 |
*** join/#brlcad Izakey
(~Izak@41.205.22.13) |
11:34.25 |
*** join/#brlcad
unicodesnowman
(~unicodesn@unaffiliated/unicodesnowman) |
11:44.01 |
*** join/#brlcad konrado
(~root@41.244.243.122) |
11:48.44 |
*** join/#brlcad Izakey
(~Izak@41.205.22.13) |
12:03.07 |
*** join/#brlcad Konrado
(~Konrado@41.244.243.122) |
12:10.53 |
*** join/#brlcad rohit0143
(~rohit@14.139.82.6) |
13:33.01 |
*** join/#brlcad balder_
(7d1409f9@gateway/web/freenode/ip.125.20.9.249) |
13:55.22 |
*** join/#brlcad merzo
(~merzo@92.60.189.225) |
14:09.33 |
*** join/#brlcad merzo
(~merzo@92.60.189.225) |
14:22.37 |
balder_ |
hey! where can I get the demo for online
geometry viewer? |
14:35.20 |
brlcad |
hey balder_ |
14:36.26 |
balder_ |
yes! |
14:37.28 |
brlcad |
the code is on github and you can get a
tarball here:
https://www.google-melange.com/gsoc/project/details/google/gsoc2014/ishwerdas/5657382461898752 |
14:38.19 |
brlcad |
balder_: did you get your other questions
answered? |
14:40.05 |
balder_ |
well I have some! |
14:40.54 |
brlcad |
I know you asked several, but you've not
stayed on IRC to get a response |
14:41.16 |
brlcad |
if you're going to ask questions here, you
should be prepared to stay connected until there is an
answer |
14:41.29 |
brlcad |
which can be many hours later due to timezones
and such |
14:42.02 |
balder_ |
ok!! Sure!! |
14:42.05 |
brlcad |
I recommend getting a real IRC client and
reading the usage etiquette guidelines instead of the freenode web
interface |
14:42.43 |
brlcad |
http://brlcad.org/wiki/IRC has a
link to an IRC client list |
14:43.27 |
balder_ |
oh sure! Thanks for this advice! I will sure
use one! Here's my question : why is there a need for 3d display
manager when we have this crossplatform online viewer?? Is this not
sufficient? |
14:44.29 |
brlcad |
1) the online viewer is still in a
prototype-stage of development |
14:44.56 |
brlcad |
2) it's limited to viewing (intentionally,
editing is incredibly complicated to get into online) |
14:45.16 |
brlcad |
3) it will unlikely scale to real production
models (that are often 2-20GB in size) |
14:45.40 |
brlcad |
so while not sufficient, it certainly has an
entire range of tasks it could handle |
14:46.03 |
brlcad |
and the interface will continue to be expanded
and as it mature, we can hone in on productive uses |
14:46.10 |
brlcad |
s/mature/matures/ |
14:48.46 |
brlcad |
make sense? |
14:49.09 |
*** join/#brlcad lemur
(~lemur@host86-191-238-95.range86-191.btcentralplus.com) |
14:49.24 |
lemur |
hey |
14:50.00 |
balder_ |
yes!! |
15:04.30 |
*** join/#brlcad Sricharanized
(~raincrash@116.202.8.62) |
15:18.36 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
15:18.41 |
*** join/#brlcad balder_
(7d1409f9@gateway/web/freenode/ip.125.20.9.249) |
15:19.56 |
balder_ |
hey! why brlcad is not support interactive 3d
rendering? Is this because we are not able to exploit
gpu?? |
15:20.11 |
balder_ |
*supporting!! |
15:20.36 |
brlcad |
balder_: that's a complicated topic that
involves talking about geometry representation formats |
15:20.48 |
brlcad |
and has nothing to do with being able to
exploit gpu |
15:21.10 |
brlcad |
with implicit geometry and csg operations,
there is no explicit boundary surface |
15:22.02 |
brlcad |
so one has to evaluate the surface/geometry
... and either evaluate points (e.g., via interactive ray tracing)
or via format conversion (e.g., to polygons) |
15:22.23 |
brlcad |
we have experimental versions of
both |
15:22.52 |
brlcad |
if you have explicit geometry (e.g., triangle
mesh geometry), you can view it interactively now |
15:23.17 |
balder_ |
ok.. |
15:23.54 |
brlcad |
I also answered this question on the mailing
list, so I'm guessing you still don't understand? :) |
15:26.05 |
balder_ |
uhh! yeah I got the point that .g files need
to be coverted to formats which supports triangle meshes, to make
it possible for 3d rendering. (correct me if i am wrong
:)) |
15:27.00 |
brlcad |
this is not accurate |
15:27.42 |
kintel |
brlcad: Hey, are you guys doing gsoc this
year? |
15:28.16 |
brlcad |
they only need to be converted to triangle
meshes if you want to interactively visualize with a method that
requires triangle meshes (e.g., OpenGL) |
15:28.43 |
brlcad |
you can ray trace interactively without
conversion |
15:29.01 |
brlcad |
kintel: not yet decided but a discussion I
wanted to have with you later this week |
15:29.25 |
kintel |
brlcad: Sounds good - |
15:29.41 |
kintel |
brlcad: ..or catch teepee if Iâm not
around |
15:30.17 |
teepee- |
has some technical problems
though due to the tor gateway being down :( |
15:38.11 |
brlcad |
balder_: the "rtgl" I mentioned is an example
of an interactive ray tracing shaded display approach that is in
brl-cad now but not production-ready |
15:39.38 |
brlcad |
balder_: adrt is another method (using
high-performance triangle ray tracing) used for
visualization |
15:40.14 |
brlcad |
balder_: and there are other experimental
methods involving conversion to triangles that I mentioned on the
mailing list (E, ev, draw -m1) |
15:40.27 |
balder_ |
ok! I need you to tell me more about the
approach used in rtgl! |
15:40.57 |
brlcad |
that's an open-ended question |
15:41.16 |
brlcad |
you should research the code reference I gave
you and ask a specific question |
15:41.38 |
brlcad |
otherwise, I could talk all day and maybe not
provide helpful information, maybe waste both our time |
15:42.07 |
brlcad |
what would you like to know? |
15:42.13 |
*** join/#brlcad raghuram_
(~raghuram@14.139.82.6) |
15:42.29 |
raghuram_ |
hi |
15:42.41 |
balder_ |
ok! I will get back to you soon ! And
seriously thanks for all this stuff!! |
15:44.18 |
raghuram_ |
I'm new. I want to contribute. Can you help
me |
15:44.26 |
brlcad |
probably |
15:45.20 |
raghuram_ |
I like to help on stuff related to
android. |
15:46.07 |
brlcad |
what kind of help, that's very vague |
15:46.30 |
brlcad |
and how does it pertain to brl-cad? |
15:46.49 |
raghuram_ |
Any bugs to start with. That would be of great
help. |
15:48.04 |
brlcad |
we have 142 bugs listed in our BUGS file and
many more listed in our Sourceforge tracker, all easily found with
a simple web search |
15:49.01 |
brlcad |
you should read http://en.flossmanuals.net/contributors-guide-to-brl-cad/ |
16:15.12 |
*** join/#brlcad rohit0143
(~rohit@14.139.82.6) |
16:22.37 |
*** join/#brlcad lemur1
(~lemur@host86-191-238-95.range86-191.btcentralplus.com) |
16:29.32 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
16:30.03 |
Notify |
03BRL-CAD:carlmoore * 64195
brlcad/trunk/src/libbrep/shape_recognition_planar.cpp: remove
trailing blanks/tabs |
16:30.16 |
Notify |
03BRL-CAD:carlmoore * 64196 brlcad/trunk/TODO:
fix spelling |
16:30.29 |
Notify |
03BRL-CAD:carlmoore * 64197
brlcad/trunk/doc/docbook/system/man1/en/mged.xml: add 2 commas and
a space |
16:31.20 |
sofat |
starseek1r, hello |
16:55.31 |
Notify |
03BRL-CAD:carlmoore * 64198
(brlcad/trunk/doc/docbook/system/man1/en/mged.xml
brlcad/trunk/doc/docbook/system/man1/en/tire.xml): fix punctuation
and add 2 missing periods |
16:57.55 |
Notify |
03BRL-CAD:carlmoore * 64199
brlcad/trunk/src/libbrep/shape_recognition_sphere.cpp: fix
spelling |
16:59.02 |
*** join/#brlcad nmz787_i
(~nmccorkx@134.134.139.74) |
17:02.37 |
Notify |
03BRL-CAD:carlmoore * 64200
(brlcad/trunk/doc/docbook/articles/en/oed.xml
brlcad/trunk/doc/docbook/articles/en/tire.xml and 2 others): supply
missing period at end of 'a.k.a.', because that last 'a' stands for
'as' |
17:05.57 |
Notify |
03BRL-CAD:starseeker * 64201
brlcad/trunk/doc/docbook/system/man1/en/gdiff.xml: fix
title |
17:06.20 |
*** join/#brlcad albertcoder
(~quassel@202.164.45.204) |
17:08.29 |
sofat |
starseeker, i found some files in
/trunk/doc/burst/ |
17:08.57 |
sofat |
i want to know about the structure of these
file |
17:09.19 |
sofat |
like .tbl file what is they
represent? |
17:16.11 |
Stragus |
sofat: http://en.wikipedia.org/wiki/Tbl |
17:16.26 |
Stragus |
Probably not something to worry about
:) |
17:16.40 |
sofat |
thanks |
17:17.33 |
Stragus |
This Troff stuff has fallen out of use decades
ago, as far as I know |
17:41.55 |
*** join/#brlcad albertcoder
(~quassel@202.164.45.204) |
17:47.36 |
*** join/#brlcad lemur12
(~lemur@host86-191-238-95.range86-191.btcentralplus.com) |
17:59.27 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:06.13 |
*** join/#brlcad albert_coder
(~quassel@202.164.45.208) |
18:11.23 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:20.41 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:22.49 |
*** join/#brlcad albertcoder
(~quassel@202.164.45.204) |
18:31.56 |
*** join/#brlcad sofat
(~sofat@202.164.45.204) |
18:34.54 |
*** join/#brlcad sprakash
(~sidd_prak@14.139.82.6) |
19:00.02 |
*** join/#brlcad nmz787_i
(nmccorkx@nat/intel/x-bmjtbckmftoinkwv) |
19:27.37 |
*** join/#brlcad lemur1
(~lemur@host86-191-238-95.range86-191.btcentralplus.com) |
19:47.54 |
*** join/#brlcad lemur12
(~lemur@host86-191-238-95.range86-191.btcentralplus.com) |
20:22.58 |
*** join/#brlcad konrado
(~root@41.244.243.119) |
20:32.41 |
*** join/#brlcad sprakash
(~sidd_prak@14.139.82.6) |
20:45.01 |
*** join/#brlcad sprakash
(~sidd_prak@14.139.82.6) |
21:02.03 |
*** join/#brlcad sprakash
(~sidd_prak@14.139.82.6) |
21:57.42 |
*** join/#brlcad sprakash
(~sidd_prak@14.139.82.6) |
22:13.16 |
brlcad |
Stragus: troff is still alive and well (it's
still the foundation for the man page system) |
22:13.56 |
brlcad |
that document is old, but it does need to get
transformed into docbook/xml |
22:15.32 |
brlcad |
it's documentation for our burst tool, which
is in active use |
22:19.39 |
Stragus |
Interesting, I stand corrected |
22:19.56 |
*** join/#brlcad merzo
(~merzo@205-52-133-95.pool.ukrtel.net) |
22:23.33 |
nmz787_i |
brlcad: any idea why I was getting a 'magic'
error when running g-stl? |
22:28.16 |
Notify |
03BRL-CAD:carlmoore * 64202
brlcad/trunk/src/util/pixembed.c: try fixing pixembed.c ; also,
notice that the previous version had yin-border_inset and I
couldn't find it defined |
22:35.18 |
brlcad |
nmz787_i: are you running trunk
sources? |
22:36.37 |
nmz787_i |
i tried that, I believe |
22:36.50 |
nmz787_i |
7.25.0 is what my dev build had in the dir
name |
22:37.00 |
brlcad |
okay, that should be a checkout |
22:37.01 |
Notify |
03BRL-CAD:starseeker * 64203
brlcad/trunk/src/libbrep/shape_recognition_sphere.cpp: Find the 2d
center point of the loop. |
22:37.31 |
nmz787_i |
I thought I pulled and recompiled after I got
the bug the first time, but I can try again tonight |
22:37.54 |
brlcad |
what's the complete error? it should tell you
exactly what is wrong |
22:38.38 |
nmz787_i |
http://paste.pound-python.org/show/WMJU7pu2gADrnxMqdCit/ |
22:38.48 |
nmz787_i |
after running this 2-command tcl script
http://paste.pound-python.org/show/fZ1b52wd43S9ocBeQEXx/ |
22:39.51 |
nmz787_i |
well I guess including setting the title and
units it is 4 commands |
22:54.48 |
brlcad |
nice! |
22:55.28 |
brlcad |
how are you counting four? I see two (in
hilbert... and r hilbert...) |
22:56.20 |
brlcad |
the crash log is perfect, that's actually a
graceful abort because unexpected data was encountered (possibly a
code bug), and it includes the exact line numbers to inspect, so I
can check |
22:57.24 |
nmz787_i |
cool |
22:57.50 |
nmz787_i |
I actually was just working on porting the
hilbert example in python-brlcad to my new project
python-brlcad-tcl :P |
22:58.17 |
nmz787_i |
I got the 3d-hilbert script to convert to use
my backend pretty easily |
22:58.18 |
nmz787_i |
https://github.com/nmz787/python-brlcad-tcl/blob/master/examples/hilbert_3d.py |
22:58.27 |
nmz787_i |
https://github.com/nmz787/python-brlcad-tcl/blob/master/examples/output/hilbert_3d.tcl |
22:58.46 |
nmz787_i |
the .g and the .stl are next to the .tcl in
the repo too |
22:59.03 |
nmz787_i |
so I haven't actually done any of the hard
mathy work at all :) |
23:02.35 |
brlcad |
what does your g-stl line look like? (it
worked here) |
23:04.20 |
nmz787_i |
g-stl -o filename.stl database.g
whatevertheregionis.r |
23:04.31 |
brlcad |
yeah, that's what I did |
23:04.34 |
brlcad |
hrm |
23:04.35 |
nmz787_i |
or possibly: |
23:04.36 |
nmz787_i |
g-stl -o filename.stl -a 0.1 database.g
whatevertheregionis.r |
23:04.43 |
brlcad |
ah, let me try that |
23:05.19 |
brlcad |
hm, nope |
23:05.29 |
brlcad |
2156 triangles written |
23:05.30 |
nmz787_i |
it crashed or no errors? |
23:05.32 |
nmz787_i |
huh |
23:05.48 |
nmz787_i |
hrmm |
23:06.16 |
brlcad |
heh, even 0.001 worked... 71420 triangles
written |
23:06.33 |
nmz787_i |
for the pastebin tcl right, not the 3d one on
my github? |
23:06.50 |
brlcad |
ah, no I used the github one |
23:06.53 |
nmz787_i |
ooh |
23:06.57 |
nmz787_i |
yeah that one works |
23:07.02 |
brlcad |
k, checking |
23:07.26 |
nmz787_i |
the 2d version (pastebin) works in mged's
display |
23:07.42 |
nmz787_i |
and I can even click raytrace there and get a
solid looking render |
23:19.52 |
*** join/#brlcad Konrado
(~Konrado@41.244.243.88) |
23:21.13 |
brlcad |
woot, reproduced |
23:21.31 |
brlcad |
http://brlcad.org/~sean/tmp/hil.png
I recognize that :) |
23:24.56 |
*** join/#brlcad konrado
(~root@41.244.243.88) |
23:25.12 |
konrado |
brlcad: hello |
23:25.23 |
nmz787_i |
brlcad: cool, so you got the STL
error? |
23:29.12 |
brlcad |
nmz787_i: I got to the bomb |
23:29.19 |
brlcad |
konrado: hola |
23:29.54 |
brlcad |
some bug in rt_pipe_tess |
23:31.12 |
konrado |
with the vrml-g convertion ? |
23:39.58 |
nmz787_i |
konrado: I think he's referring to the bug I
came across, when generating an STL |
23:42.13 |
konrado |
nmz787_i: Ok |
23:44.04 |
brlcad |
konrado: sorry, was responding to nmz787_i ...
your vrml work is looking good |
23:44.25 |
brlcad |
what's next / missing from the converter?
anything? |
23:46.17 |
konrado |
Yes support for extrution node,
indexedpointset , proto IS keyword and also
colorpervertex |
23:46.33 |
brlcad |
cool! |
23:46.48 |
brlcad |
we do have extrusions and point
clouds |
23:47.10 |
brlcad |
per vertex coloring is going to be tricky (but
something we want/need too) |
23:48.48 |
konrado |
where do i find code on extrusion and point
cloud within brlcad source |
23:49.20 |
brlcad |
src/librt/primitives has all entity types,
include/rtgeom.h has most of their declarations |
23:49.40 |
brlcad |
the converter would likely use the wdb
interface (include/wdb.h) |
23:51.17 |
brlcad |
there's not a wdb interface for pnts, but you
can see how to create them low-level in
src/libged/make_pnts.c |
23:52.34 |
brlcad |
there is mk_extrusion() for extrudes |
23:55.01 |
konrado |
I would continue updating the code a soon as I
am done with my exams which begins next week |
23:56.52 |
konrado |
Did you see the support I added, for color
with RGB representation ? |