00:19.22 |
*** join/#brlcad ``Erik
(~erik@pool-74-103-121-45.bltmmd.fios.verizon.net) |
00:21.07 |
brlcad |
caen23_: google just sent me a few pictures of
you and skriptkid receiving your awards :) |
01:54.26 |
*** part/#brlcad Mahi
(~Mahi@ec2-54-234-175-101.compute-1.amazonaws.com) |
03:17.20 |
starseeker |
sweet - glfw is adding support for undecorated
OpenGL windows. May have to try plugging them in behind a generic
OpenGL libdm/libfb layer. |
08:56.36 |
*** join/#brlcad zero_level
(~zero_leve@117.212.25.74) |
10:45.38 |
*** join/#brlcad mpictor_
(~mpictor_@2600:1015:b10e:1110:0:2:7a6a:b901) |
11:59.40 |
*** join/#brlcad d_rossberg
(~rossberg@66-118-151-70.static.sagonet.net) |
12:57.55 |
caen23_ |
brlcad: :D heh, nice |
12:59.36 |
caen23 |
it was a very cool week indeed |
13:39.12 |
starseeker |
growls - n_reed, it looks
like that trick for generating wireframes won't fly after
all |
13:39.19 |
starseeker |
too resource intensive |
13:49.06 |
*** join/#brlcad ``Erik
(~erik@pool-74-103-121-45.bltmmd.fios.verizon.net) |
13:49.07 |
n_reed |
you mean it takes too much longer than the
normal time? |
13:49.23 |
n_reed |
it was worth a try regardless |
14:13.55 |
starseeker |
yeah - I'm looking at anywhere I can trim fat
to try and speed it up, but I doubt it'll be enough |
14:14.05 |
starseeker |
pity - it gives decent results in some
cases |
14:14.44 |
starseeker |
is there any way we can tweak the vds folding
to bias in some way toward original points in the local
neighborhood? |
14:32.04 |
n_reed |
not sure what you mean |
14:35.01 |
Notify |
03BRL-CAD:carlmoore * 55687
(brlcad/trunk/src/sig/f-i.c brlcad/trunk/src/sig/i-f.c): set
scale=1.0 in the declaration, not in a separate statement |
14:35.38 |
n_reed |
avoid folding nodes containing original
triangles which are adjacent to an already folded node? |
14:36.37 |
n_reed |
or when folding a node always use an original
triangle vertex as the proxy? or something else? |
14:54.52 |
Notify |
03BRL-CAD:carlmoore * 55688
(brlcad/trunk/src/sig/bw-d.c brlcad/trunk/src/sig/d-bw.c): changes
(preset of scale =1.0 and implementing -h and -?) for bw-d.c and
d-bw.c |
14:58.09 |
Notify |
03BRL-CAD:carlmoore * 55689
brlcad/trunk/src/sig/bw-d.c: remove math.h reference, which d-bw.c
did not have, and I did make to make sure this didn't break
anything |
15:06.00 |
starseeker |
n_reed: something along those lines... you had
mentioned "losing" the original shape as folding
progressed |
15:25.44 |
Notify |
03BRL-CAD:carlmoore * 55690
(brlcad/trunk/src/sig/d-u.c brlcad/trunk/src/sig/u-d.c): cosmetic
changes for d-u.c/u-d.c file comparison, and in u-d.c implement
'double scale=1.0;' |
15:29.19 |
Notify |
03BRL-CAD:carlmoore * 55691
brlcad/trunk/src/sig/u-f.c: move scale=1.0 into the type
declaration |
15:35.08 |
n_reed |
to reiterate, the primary issue is that
rendering requires too many original triangles to be
present |
15:35.25 |
n_reed |
if you don't have a patch of original
triangles every so often, you end up with holes |
15:35.45 |
n_reed |
if you don't keep any original triangles, you
end up with nothing (disappearing tire syndrome) |
15:37.27 |
n_reed |
this restricts the number of triangles you can
remove to a number that seems too few to be of much use to
us |
16:12.06 |
*** join/#brlcad zero_level
(~zero_leve@117.205.26.141) |
16:35.26 |
*** join/#brlcad mpictor_
(~mpictor_@2600:1015:b10e:1110:0:2:7a6a:b901) |
16:59.43 |
Notify |
03BRL-CAD:phoenixyjll * 55692
brlcad/trunk/src/libbrep/intersect.cpp: Try to add PS support using
get_closest_point(). |
17:00.56 |
Notify |
03BRL-CAD:erikgreenwald * 55693
brlcad/trunk/doc/docbook/system/man1/en/fbclear.xml: rebalance the
XML so it can be parsed |
17:05.04 |
*** join/#brlcad zero_level
(~zero_leve@117.205.20.87) |
17:08.29 |
Notify |
03BRL-CAD Wiki:Phoenix * 5368
/wiki/User:Phoenix/GSoc2013/Reports: /* Community bonding
*/ |
18:01.24 |
*** join/#brlcad caen23
(~caen23@92.81.209.90) |
18:14.51 |
Notify |
03BRL-CAD:carlmoore * 55694
brlcad/trunk/src/sig/i-d.c: add a blank line (cosmetic comparison
with d-i.c) and initialize scale in the type statement |
19:18.55 |
zero_level |
<PROTECTED> |
19:19.31 |
zero_level |
``Erik : Hi |
19:31.16 |
zero_level |
``Erik: I wish to discuss things related to
buffers in the image utilities. Please respond when you see this.
Thanks :-) |
19:32.42 |
Notify |
03BRL-CAD:carlmoore * 55695
brlcad/trunk/src/util/pix-png.c: don't need those 2 case
statements; just use default |
19:42.51 |
*** join/#brlcad mpictor_
(~mpictor_@2600:1015:b10e:1110:0:2:7a6a:b901) |
19:51.05 |
*** join/#brlcad mpictor
(~mpictor_@99-93-104-202.lightspeed.iplsin.sbcglobal.net) |
19:53.58 |
*** join/#brlcad mpictor
(~mpictor_@99-93-104-202.lightspeed.iplsin.sbcglobal.net) |
19:56.23 |
*** join/#brlcad mpictor_
(~mpictor_@99-93-104-202.lightspeed.iplsin.sbcglobal.net) |
20:29.38 |
Notify |
03BRL-CAD:carlmoore * 55696
brlcad/trunk/src/util/pix-ps.c: implement -h and -? (removing old
-h high-res) |
20:35.37 |
``Erik |
zero_level: ask your questions, someone will
answer them eventually... I'm running around preparing for a
preschool graduation at the moment, so I'm not very available, but
other mentors might be |
20:42.23 |
*** join/#brlcad ``Erik
(~erik@pool-74-103-121-45.bltmmd.fios.verizon.net) |
20:54.10 |
zero_level |
``Erik: ok, |
20:54.20 |
zero_level |
I am currently preparing implementation plan
for utilities of group 1-6. I will post it on wiki page. I might
need your review for that. |
20:54.36 |
zero_level |
Also i wish to shuffle components of
development phase in my time-line. |
20:55.25 |
zero_level |
About buffers. |
20:57.13 |
``Erik |
'k, when the changes are committed to the
wiki, mention it in here and at least one mentor will
review/comment |
20:58.34 |
``Erik |
re-ordering is fine, um, there are two review
times, a half-way review and the final review... if the shuffling
moves things between those two halves, just let us know |
20:59.36 |
zero_level |
In the image processing utilities, the image
is not read in full to the memory, rather buffers of varied size
are used. The image is read in parts from one of the raw format
pix/bw to these buffers, processed and written to the output
buffer/file depending upon the utility |
21:00.31 |
zero_level |
this reading --> processing and writting
continues until the complete file is not read. |
21:01.16 |
zero_level |
I require few suggestions here |
21:04.03 |
zero_level |
a) The current work on ICV has a image
container which contains feild for both file pointer and the array
containing the file. The easiest task would be to refactor the code
and let them use the buffers of the varied sizes and read from the
input file pointer |
21:04.43 |
zero_level |
I would welcome implementation suggestion for
this ! |
21:08.46 |
Notify |
03BRL-CAD Wiki:Level zero * 5369
/wiki/User:Level_zero/proposal: /* June 17 - Sep 2 suffling of
components of Development Phase */ |
21:10.21 |
zero_level |
``Erik this notification is for shuffling of
the components. I would now focus on the 11 Groups first and then
the conversion tools |
21:10.57 |
``Erik |
http://youtu.be/vxG1PFHOpI8 they
turbo'd an old golf to break 1000hp (1013bhp, 744kw... I assume at
the flywheel) |
21:15.02 |
``Erik |
zero_level: I don't recall what group 11 is,
but I'd imagine the converters are more important in the long run..
I'd like to see some effort on the converters, even if we decide to
break it up differently... |
21:16.15 |
``Erik |
w00t, got my twirssi back up and I only had to
alter one system perl module |
21:17.07 |
zero_level |
``Erik : i meant all the other image
processing tools(1-11 groups) other than converters |
21:20.06 |
starseeker |
brlcad: anything we can do to assist with
tagging? (I can do another sync, if that would help...) |
22:42.41 |
Notify |
03BRL-CAD:r_weiss * 55697
brlcad/trunk/src/libged/gqa.c: Updates to 'gqa' command to improve
results with default settings and improve user messages/warnings.
More testing is needed. |
23:28.04 |
*** join/#brlcad mpictor
(~mark@99-93-104-202.lightspeed.iplsin.sbcglobal.net) |