00:25.10 |
*** join/#brlcad starseeker
(~starseeke@66-118-151-70.static.sagonet.net) |
00:25.40 |
starseeker |
returns |
00:25.49 |
*** join/#brlcad gdh
(~quassel@174-126-28-176.cpe.cableone.net) |
00:27.37 |
*** join/#brlcad filipt
(~filip@89.205.42.139) |
00:41.50 |
*** join/#brlcad billa_
(b6131049@gateway/web/freenode/ip.182.19.16.73) |
00:53.38 |
*** join/#brlcad hilnius_bnc
(~hilnius_b@client-resel-2.enst-bretagne.fr) |
02:52.56 |
*** join/#brlcad brlcad
(~sean@66-118-151-70.static.sagonet.net) |
02:55.09 |
*** join/#brlcad jordisayol
(~jordisayo@unaffiliated/jordisayol) |
02:57.23 |
*** join/#brlcad peerless
(~deepak@14.139.226.34) |
03:21.41 |
*** join/#brlcad brlcad
(~sean@66-118-151-70.static.sagonet.net) |
04:23.56 |
*** join/#brlcad n_reed
(~molto_cre@66-118-151-70.static.sagonet.net) |
04:29.36 |
*** join/#brlcad brlcad
(~sean@66-118-151-70.static.sagonet.net) |
04:40.46 |
*** join/#brlcad rays2pix
(~deepak@14.139.226.34) |
04:48.08 |
rays2pix |
Hi All..This is Deepak. Planning to take up
code refactoring projects for gsoc |
04:56.52 |
gdh |
rays2pix, don't worry if the developers are
not answering |
04:57.02 |
gdh |
sometimes, they are away for awhile |
04:57.10 |
gdh |
(and I'm not a developer, sorry) |
04:58.24 |
rays2pix |
gdh: thanks anyways hi ! |
04:59.03 |
gdh |
it's funny, I thought the refactoring projects
wouldn't be popular, but they are |
05:00.19 |
rays2pix |
gdh: I want to first come up with a working
proposal for image processing., I would like to try my hand at
"Density functions" idea too |
05:00.29 |
gdh |
good idea |
05:00.30 |
rays2pix |
gdh: refactoring - teaches you a
lot:)! |
05:00.38 |
gdh |
that's what I was thinking |
05:01.05 |
rays2pix |
gdh: may I know how are you associated with
brlcad..user or beginner like me? |
05:01.14 |
gdh |
beginner |
05:01.22 |
gdh |
I was looking into doing GSoC |
05:01.36 |
rays2pix |
gdh: thats nice!which one have you picked
up? |
05:02.17 |
gdh |
well, I haven't picked one up for sure, but
code reduction and the Archer API are both possible |
05:02.35 |
gdh |
It all depends on what project I can possibly
get |
05:09.19 |
rays2pix |
gdh: Good luck |
05:09.26 |
gdh |
thanks |
05:10.38 |
rays2pix |
gdh: are you running brlcad ? |
05:10.53 |
gdh |
do you mean have I compiled it? |
05:10.54 |
gdh |
yes |
05:10.59 |
gdh |
at the moment, no |
05:14.42 |
rays2pix |
gdh: okay. I compiled it from source
ball,there seems to be some more recent changes.So heading to
SVN |
05:15.38 |
gdh |
sometimes, there's a Notify bot on this
channel that lets us know when there was a new commit |
05:49.48 |
brlcad |
note that it's night for many of the devs, so
some responses might not come for 7-8 hours |
05:55.18 |
rays2pix |
brlcad:its okay ..Will check back and also
will slowly learn about the time lines ! |
06:07.20 |
*** join/#brlcad sbongir
(~chatzilla@59.160.74.254) |
06:42.15 |
*** join/#brlcad akdroid
(~IceChat77@117.222.37.76) |
06:42.35 |
akdroid |
hello |
06:42.48 |
akdroid |
my name is Akhil |
06:43.42 |
akdroid |
I'm interested in the networking project
LIBPKG extensions |
06:43.51 |
akdroid |
for GSoC |
06:44.32 |
akdroid |
What should I read up on for the same
? |
08:11.21 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
08:12.31 |
*** join/#brlcad caen23_
(~cezar@92.81.221.65) |
08:42.36 |
*** join/#brlcad d_rossberg
(~rossberg@66-118-151-70.static.sagonet.net) |
10:08.25 |
*** join/#brlcad Shabbir
(6e5dc80a@gateway/web/freenode/ip.110.93.200.10) |
11:17.14 |
*** join/#brlcad rays2pix
(~deepak@14.139.226.34) |
11:45.17 |
*** join/#brlcad Notify
(~notify@66-118-151-70.static.sagonet.net) |
12:43.30 |
Notify |
03BRL-CAD:bob1961 * 55119
(brlcad/trunk/src/mged/dm-ogl.c brlcad/trunk/src/mged/dm-wgl.c):
This fixes zclipping in MGED. |
12:57.56 |
*** join/#brlcad jordisayol
(~jordisayo@unaffiliated/jordisayol) |
13:09.46 |
Notify |
03BRL-CAD:indianlarry * 55120
brlcad/trunk/src/other/poly2tri/CMakeLists.txt: Cleaned up poly2tri
cmake to remove unneeded variables, build static library based off
of BUILD_STATIC_LIBS, no longer need util.h installed
public. |
13:27.20 |
*** join/#brlcad caen23
(~cezar@92.83.169.52) |
13:30.20 |
Notify |
03BRL-CAD:starseeker * 55121
brlcad/trunk/NEWS: Bob fixed a z-clipping bug introduced a while
ago, related to changes made for more elaborate clipping support in
Archer. Fixed in commit r55119 |
13:32.04 |
*** join/#brlcad celeschus
(c8373a72@gateway/web/freenode/ip.200.55.58.114) |
13:32.48 |
celeschus |
Hi! I'm Celeste, a systems engineering student
from Argentina. I'm interested in your project for GSoC. I have
some questions. |
13:34.03 |
gdh |
celeschus, don't worry if the developers
aren't answering |
13:34.14 |
gdh |
sometimes they are away from their
computers |
13:34.19 |
gdh |
but they will answer |
13:34.33 |
gdh |
I'm a hopeful GSoC student like
yourself |
13:34.49 |
celeschus |
where are you from? |
13:35.04 |
gdh |
Idaho, USA |
13:35.06 |
celeschus |
This program is amazing, there are so many
interesting projects to work with |
13:35.15 |
gdh |
yes, it is |
13:36.08 |
celeschus |
First, I would like to ask If the application
it's for one task in particular or you can express interest in more
than one |
13:36.11 |
``Erik |
celeschus: ask the questions, then just hang
out and wait for someone to answer them :) |
13:37.18 |
``Erik |
you can do several applications, and several
people can apply for a task... |
13:37.36 |
celeschus |
Erik, i'm interested in one task that you
mentor, Astronomical Units |
13:37.48 |
celeschus |
Sorry for my english |
13:37.51 |
celeschus |
=) |
13:37.52 |
``Erik |
cool, big stuff is neat |
13:37.57 |
``Erik |
english seems great so far |
13:40.20 |
celeschus |
If I apply for that task, what do you suggest
me to do before that? In every site of the participating
organizations talks about "preparing you appplication with
mentors" |
13:49.47 |
``Erik |
http://brlcad.org/wiki/Google_Summer_of_Code
has a checklist you should go over |
13:53.27 |
celeschus |
Yes I saw it but i was wondering if there is
something else to do |
14:07.06 |
*** join/#brlcad yiyus
(1242712427@je.je.je) |
14:18.38 |
celeschus |
I mean if I can install something on my laptop
or something like that |
14:19.05 |
*** join/#brlcad jordisayol
(~jordisayo@unaffiliated/jordisayol) |
14:19.05 |
*** join/#brlcad d_rossberg
(~rossberg@66-118-151-70.static.sagonet.net) |
14:19.05 |
*** join/#brlcad starseeker
(~starseeke@66-118-151-70.static.sagonet.net) |
14:19.28 |
gdh |
celeschus, the main thing is to compile it and
perhaps submit a patch or two |
14:19.42 |
gdh |
``Erik, correct me if I'm wrong |
14:24.05 |
``Erik |
you are correct, we like to see proof that you
can work with subversion, compile, follow the style guidelines in
the HACKING file, have competency in the programming language you
intend to use, etc |
14:26.10 |
``Erik |
otherwise, we have to try to guess at the
applicants competence when grading the applications |
14:31.31 |
celeschus |
thanks! |
14:33.20 |
``Erik |
np, good luck on getting a trunk checkout
compiled and running (once it's build, you can do "make test",
"make benchmark" and "make regress" to verify everything worked, as
well as the make install to get it into place) |
14:38.38 |
celeschus |
Ok =) i'll come back in these days |
14:38.52 |
celeschus |
*this |
15:46.05 |
*** join/#brlcad filipt
(~filip@89.205.42.139) |
15:50.47 |
Notify |
03BRL-CAD:indianlarry * 55122
brlcad/trunk/src/other/poly2tri/Makefile.am: Added additional
header files to install and nested header directory structure in
include directory. |
16:07.41 |
*** part/#brlcad filipt
(~filip@89.205.42.139) |
16:15.04 |
*** join/#brlcad KimK
(~Kim__@wsip-184-176-200-171.ks.ks.cox.net) |
16:45.02 |
*** join/#brlcad filipt
(~filip@89.205.42.139) |
16:45.15 |
filipt |
hi |
18:02.14 |
*** join/#brlcad Ch3ck
(~Ch3ck@41.205.13.163) |
18:02.21 |
Ch3ck |
Hi there |
18:02.24 |
Ch3ck |
I am Nyah Check |
18:02.49 |
Ch3ck |
a student from the department of computer
Engineering from the University of Buea. and a good C
programmer |
18:03.04 |
Ch3ck |
i wish to work on the Code refactoring
projects this summer |
18:03.25 |
Ch3ck |
i just wish to know what is required to in
order to write a proposal |
18:21.59 |
*** join/#brlcad caen23
(~cezar@92.83.168.216) |
18:22.58 |
brlcad |
hi Ch3ck |
18:23.49 |
Ch3ck |
Hi |
18:24.03 |
Ch3ck |
I am an engineering Student from
Cameroon |
18:24.08 |
brlcad |
what is required is to figure out what you'd
like to refactor |
18:24.18 |
Ch3ck |
ok |
18:24.38 |
Ch3ck |
so what skill level of C programming is
required.. for work on the projects |
18:24.41 |
brlcad |
the more specific you can be, the
better |
18:24.54 |
brlcad |
especially if you can tie the refactoring to
some tangible gain |
18:25.13 |
brlcad |
any skill level is acceptable, it's more about
passion and intent |
18:25.25 |
brlcad |
propoerly scoping and planning a
project |
18:25.45 |
Ch3ck |
ok |
18:25.50 |
brlcad |
being easy to talk to and work with,
independent in solving problems but not to a fault |
18:26.00 |
Ch3ck |
so how do i get access to some of the projects
so i can determine what to do.. |
18:26.29 |
brlcad |
i'm not sure what your question
means |
18:26.48 |
brlcad |
you don't get access to any projects, you
propose the project |
18:27.12 |
Ch3ck |
ok |
18:27.12 |
brlcad |
you have access to our source code
already |
18:27.26 |
Ch3ck |
ok |
18:27.36 |
Ch3ck |
yeah thats what i am talking about
.. |
18:27.44 |
Ch3ck |
how do i get the source code |
18:27.52 |
Ch3ck |
so i can figure out what to
contribute |
18:27.58 |
Ch3ck |
on my proposal.. |
18:28.20 |
brlcad |
you should be able to figure that
out... |
18:28.35 |
brlcad |
if you wan't find our source code, that's a
big warning sign :) |
18:28.50 |
brlcad |
s/wan't/can't/ |
18:30.17 |
brlcad |
find it yet? |
18:31.23 |
Ch3ck |
yeah ... |
18:31.28 |
Ch3ck |
seen it |
18:31.28 |
Ch3ck |
thanks |
18:31.41 |
brlcad |
you'll want to use our latest subversion
sources from a checkout |
18:31.50 |
brlcad |
do you know where *that* is? |
18:33.32 |
Ch3ck |
no |
18:33.36 |
Ch3ck |
Sir. |
18:33.48 |
brlcad |
~cadsvn |
18:33.49 |
ibot |
To obtain BRL-CAD from Subversion: svn
checkout https://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk
brlcad |
18:34.22 |
``Erik |
Ch3ck: take a few moments to read through the
webpage in the topic, particularly the checklist link |
18:34.52 |
Ch3ck |
ok |
18:34.56 |
Ch3ck |
thanks.. |
18:56.33 |
Ch3ck |
So brlcad is the company that produces
CAD?? |
18:56.58 |
Ch3ck |
wow i'll be so glad to work on a project with
you this Summer.. |
19:01.09 |
brlcad |
BRL-CAD is an open source community |
19:01.46 |
brlcad |
we focus on implementing and improving our CAD
software |
19:01.58 |
Ch3ck |
yeah i will be glad to work with you this
summer |
19:02.20 |
brlcad |
open source participation is entirely
voluntary, though many have day jobs that support their
participation |
19:02.27 |
Ch3ck |
My other buddies use CAD for their
designs |
19:02.36 |
brlcad |
well, hopefully you can write an excellent
proposal ;) |
19:03.18 |
brlcad |
just be sure to keep communicating and start
exploring the code, find something to work on, make a useful patch
or three so we get a sense of your abilities, etc |
19:03.44 |
Ch3ck |
ok thanks |
19:03.51 |
Ch3ck |
i'll start working on it.. |
19:05.26 |
*** join/#brlcad ncsaba
(~ncsaba@p5498328F.dip.t-dialin.net) |
19:05.36 |
ncsaba |
Hi there |
19:06.00 |
Ch3ck |
Hi |
19:06.22 |
brlcad |
howdy ncsaba |
19:06.27 |
brlcad |
how's the calculations coming? |
19:06.33 |
ncsaba |
volume is ready :-) |
19:06.39 |
brlcad |
really? |
19:06.41 |
ncsaba |
surface is real tricky |
19:07.02 |
ncsaba |
I will give you a test pipe, tell me what's
it's surface ;-) |
19:07.15 |
brlcad |
ok |
19:07.24 |
ncsaba |
db put tp5.s pipe V0 { 0 0 -4 } O0 2 I0 1.5 R0
4 V1 { 0 -4 -4 } O1 0.5 I1 0 R1 4 V2 { 0 -4 4 } O2 2 I2 1.5 R2 4 V3
{ 0 4 4 } O3 2 I3 1.5 R3 4 V4 { 0 4 -4 } O4 2 I4 1.5 R4 4 V5 { 0 0
-4 } O5 2 I5 1.5 R5 4 |
19:07.59 |
ncsaba |
turn it with the thin part pointing to you,
and ray-trace... |
19:10.52 |
ncsaba |
the problem is basically that pipes as they
are currently implemented can have either disconnected parts (as in
this example), or segments which are partially connected (with some
jumps in the pipe diameter) |
19:12.28 |
ncsaba |
some of that is not visible if you ray-trace
it - but I like to have things done right, so it will need more
work... |
19:13.12 |
ncsaba |
the volume is actually easy, I just calculate
it for each segment and sum it up |
19:13.34 |
ncsaba |
verified with gqa, it seems to work
OK... |
19:14.04 |
brlcad |
hah, that's really cool |
19:14.19 |
brlcad |
i bet there's a way to break some
assumptions |
19:14.23 |
ncsaba |
but for surface the segments can have
connected parts, where the surface should not be counting |
19:15.11 |
ncsaba |
what is cool ? (sorry I talk a lot and then I
don't know what you answered :-) ) |
19:15.55 |
brlcad |
sorry, I'm still on the db put line |
19:15.59 |
ncsaba |
ah ok |
19:16.08 |
ncsaba |
so you like that pipe ? :-) |
19:16.08 |
brlcad |
just thinking about a pipe that spirals into
itself |
19:16.24 |
ncsaba |
that could work too :-) |
19:16.27 |
brlcad |
I don't think that's a case that has been
considered |
19:16.43 |
brlcad |
might even work they way it processes segments
at a time, but dunno |
19:16.58 |
ncsaba |
well I'm not after total perfection, but the
main cases should work correctly... |
19:18.03 |
ncsaba |
in any case, I think it is possible to have an
algorithm which calculates the surface correctly for most
cases |
19:18.22 |
ncsaba |
just needs more work than simply adding up the
individual surfaces :-) |
19:18.48 |
brlcad |
well, so SA is similar ... |
19:18.55 |
brlcad |
you're still just summing up the
segments |
19:19.12 |
brlcad |
it's just that you have to be aware of your
previous and next segments to get the ends right |
19:19.20 |
ncsaba |
yes |
19:19.27 |
brlcad |
so you ignore the end-cap segments for
starters |
19:19.40 |
ncsaba |
but what about first and last segments
touching each other ? |
19:19.47 |
brlcad |
then it really is just an iteration over each
segment, sum the interior and exterior surface |
19:20.04 |
ncsaba |
you can create a perfect torus with
pipe |
19:20.17 |
ncsaba |
and no, that#s not enough |
19:20.27 |
brlcad |
how so? |
19:21.10 |
brlcad |
by end-cap segments, I mean all those
perpendicular surfaces |
19:21.15 |
brlcad |
not just the first and last |
19:21.31 |
ncsaba |
db put tp2.s pipe V0 { 0 -6 0 } O0 2 I0 0 R0 4
V1 { 0 -4 4 } O1 1 I1 0 R1 4 V2 { 0 4 4 } O2 2 I2 0 R2 4 V3 { 0 4
12 } O3 1 I3 0 R3 4 V4 { 0 10 12 } O4 2 I4 0 R4 4 |
19:21.40 |
ncsaba |
ah ok |
19:22.07 |
ncsaba |
see the jump in this pipe (ray-traced is
visible) |
19:22.25 |
brlcad |
sure |
19:22.39 |
ncsaba |
that jump has a lateral surface which depends
on the touching inner/outer diameters of both ends |
19:23.14 |
brlcad |
yeah, so but ignoring those surfaces I trust
you see how the rest is just a summation of cylinders |
19:23.38 |
brlcad |
(mathematical cylinders, not
geometric) |
19:24.29 |
brlcad |
so the only hard part is what you identified,
calculating the various ellipsoidal areas |
19:24.30 |
ncsaba |
yes, that I have ready |
19:24.38 |
ncsaba |
that's the easy part |
19:24.40 |
brlcad |
er, ellipse areas |
19:24.58 |
ncsaba |
they are truncated cones and torus
segments |
19:25.14 |
brlcad |
right |
19:25.30 |
ncsaba |
that part is done |
19:26.09 |
brlcad |
so then you just need a lil book-keeping to
add up any remaining ellipse areas |
19:26.35 |
ncsaba |
BTW, there is a bug in the bounding box
calculation, the min and max are not initialized to +-infinity - I
will provide a patch for that too |
19:26.35 |
brlcad |
four cases I think |
19:27.56 |
brlcad |
prev to next is solid to solid, solid to
hollow, hollow to solid, hollow to hollow, oh and null to solid,
null to hollow, hollow to null, and solid to null |
19:28.16 |
ncsaba |
well basically I only need to know the
previous/next inner/outer diameters, it really doesn't matter if it
was hollow, bent, etc. |
19:28.36 |
ncsaba |
and must check if the first and last point are
the same |
19:31.10 |
ncsaba |
for the centroid I guess I will need to sum
the individual centroids weighted by volume ? |
19:31.28 |
brlcad |
nowing inner/outer and handling them case-wise
is going to be paramount to handling the 8 cases I
mentioned |
19:32.02 |
brlcad |
"hollow" was just a shorthand for non-zero
inner |
19:32.19 |
Notify |
03BRL-CAD:carlmoore * 55123
brlcad/trunk/src/conv/stl/stl-g.c: Provide 'Usage:'; arrange
explanations in the order the options appear in Usage line; add
comment that -h and -? are not needed ('default' takes care of
them) |
19:32.45 |
ncsaba |
the inner/outer diameters are known for each
segment end, and the only thing to figure out is how much of that
overlaps |
19:33.05 |
ncsaba |
non-overlapping is added, the rest
ignored |
19:33.31 |
brlcad |
pretty sure you're saying the exact same
thing |
19:33.42 |
ncsaba |
ok :-) |
19:34.28 |
ncsaba |
should I upload new patches as soon as I have
something, or better in one go for all 3 methods ? |
19:34.41 |
ncsaba |
right now I would have the volume
done |
19:35.00 |
ncsaba |
but it depends on the former refactoring patch
of course... |
19:35.17 |
brlcad |
I just broke it down into cases that would
result (which could be processed as such with a switch/ifthenelse)
or find some general solution (but I'm pretty sure that'll be a
variation on ifthenelse ultimately) |
19:35.38 |
brlcad |
new patches are good |
19:35.55 |
brlcad |
just way whether they apply independently or
should be applied in order |
19:36.27 |
ncsaba |
yes, if then else - but I prefer to have the
ifs depend on inner/outer diameter only, not other knowledge about
the segment (bent, hollow, null, etc) |
19:37.01 |
ncsaba |
so I can have the initial/end segments be
processed the same as the rest |
19:37.41 |
ncsaba |
ok, I have to go now - will upload patches as
soon as I have some ready |
19:37.56 |
brlcad |
the 8 have no other knowledge, that's just the
possible ways the ellipse/torus ends will combine |
19:37.57 |
ncsaba |
thanks for the talk ! |
19:38.04 |
ncsaba |
see you :-) |
19:38.09 |
brlcad |
cya :) |
20:05.07 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
20:32.11 |
*** join/#brlcad ColloquyUser
(~caen23@92.83.168.216) |
20:32.25 |
Notify |
03BRL-CAD:carlmoore * 55124
brlcad/trunk/src/shapes/coil.c: use av[0]; provide for no-argument
case (program continues running) and -?; shift 'make sure..'
comment; reverse sense of '!bu_file_exists (looked stupid before
the change |
20:45.49 |
Notify |
03BRL-CAD:carlmoore * 55125
brlcad/trunk/src/shapes/coil.c: use the defaults if no arguments at
all or if there is ONLY the -? argument |
21:09.09 |
*** join/#brlcad maths22
(~gcimaths@66-118-151-70.static.sagonet.net) |
22:03.59 |
*** join/#brlcad gdh
(~quassel@174-126-28-176.cpe.cableone.net) |
22:07.40 |
*** join/#brlcad caen23_
(~cezar@92.81.211.227) |
22:54.04 |
*** join/#brlcad filipt
(~filip@89.205.42.139) |
23:00.41 |
Notify |
03BRL-CAD:brlcad * 55126
(brlcad/trunk/src/mged/dm-X.c brlcad/trunk/src/mged/dm-rtgl.c
brlcad/trunk/src/mged/dm-tk.c): shouldn't the others need the same
change too? |
23:01.14 |
brlcad |
starseeker: when was the zclipping bug
introduced? ... |
23:05.31 |
Notify |
03BRL-CAD:brlcad * 55127 brlcad/trunk/NEWS:
Bob fixed a z-clipping bug introduced a while ago, related to
changes made for more elaborate clipping support in Archer. Fixed
in commit r55119. (aiming to consistently lowercase mged (and other
tools) in bullets and uppercase them in the prose
write-ups.) |
23:08.23 |
Notify |
03BRL-CAD:brlcad * 55128
brlcad/trunk/src/shapes/coil.c: ws indent cleanup. want space after
commas in function argument lists. |
23:10.26 |
Notify |
03BRL-CAD:brlcad * 55129
brlcad/trunk/src/shapes/coil.c: ws |
23:11.15 |
brlcad |
(if it was introduced within the last
9-months, it might not be user-visible) |
23:27.56 |
*** join/#brlcad nestor_souler
(~Souler@76.6.60.213.dynamic.mundo-r.com) |
23:32.49 |
brlcad |
hello nestor_souler |
23:35.01 |
nestor_souler |
hi :) |
23:36.08 |
nestor_souler |
i've been reading about ur proposals for
soc13 |
23:36.17 |
nestor_souler |
might stick here for a while :p |