00:03.17 |
*** join/#brlcad gurwinder
(3b5b70d7@gateway/web/freenode/ip.59.91.112.215) |
00:04.37 |
gurwinder |
brlcad: I have uploaded g-pov.c file. Please
check mail on brlcad developer-mailing list. |
00:04.57 |
gurwinder |
Along with g-pov.1 man page file. |
00:06.59 |
*** join/#brlcad ries_nicked
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
00:37.52 |
brlcad |
gurwinder: yep, I saw it a couple days ago --
outstanding! will respond in more detail soon |
00:41.03 |
*** join/#brlcad Notify
(~notify@66-118-151-70.static.sagonet.net) |
01:18.52 |
gurwinder |
brlcad: ok :) |
01:57.50 |
mihaineacsu |
any updates on my part? I'd like to continue
to push the rest of the changes and then move on to shader
obj |
02:12.18 |
brlcad |
mihaineacsu: I'll have updates for you
tomorrow as I finish getting through your patches, but it's looking
mostly good (few issues) |
02:56.15 |
brlcad |
~gct |
02:56.54 |
brlcad |
starseeker: you're looking into whether P !=
NP now? geometric complexity theory? |
03:02.11 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
03:41.52 |
brlcad |
starseeker: ahhh, never mind .. I see it now
that it's the ball pivot / tess stuff. just a generic misleading
name. :) |
05:46.57 |
brlcad |
I see the gqa bug .. it's related to semaphore
initialization which is supposed to be automatic, but apparently
missed something |
05:47.06 |
brlcad |
fix should be easy, but will tackle that
tomorrow |
06:14.37 |
*** join/#brlcad gurwinder
(caa43575@gateway/web/freenode/ip.202.164.53.117) |
06:20.48 |
gurwinder |
brlcad: I make a case in switch as. if
(sscanf(bu_aptarg, "%g %g %g", &a1, &b1, &c1) {
printf(" %g %g %g", a1, b1, c1);}. else { bu_exit( 1, usage,
argv[0] ;) |
06:21.53 |
gurwinder |
it dosen't give three variable values when if
statements run |
06:25.34 |
*** join/#brlcad gurwinder_
(caa43575@gateway/web/freenode/ip.202.164.53.117) |
06:32.17 |
*** join/#brlcad ries
(~ries@D979EA84.cm-3-2d.dynamic.ziggo.nl) |
06:44.09 |
*** join/#brlcad gurwinder
(caa43575@gateway/web/freenode/ip.202.164.53.117) |
07:03.42 |
*** join/#brlcad ankesh11
(sid8015@gateway/web/irccloud.com/x-vpegbdagfrjigarr) |
11:14.29 |
*** join/#brlcad clock
(~clock@77-58-143-135.dclient.hispeed.ch) |
11:50.09 |
*** join/#brlcad fenn
(~fenn@131.252.130.248) |
12:03.59 |
*** join/#brlcad mihaineacsu
(~mihaineac@92.85.195.16) |
13:19.16 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
13:31.04 |
Notify |
03BRL-CAD Wiki:ColetteWON * 0
/wiki/User:ColetteWON: |
13:40.32 |
Notify |
03BRL-CAD:brlcad * 62511
brlcad/trunk/src/libged/gqa.c: eliminate the static global resource
pointer, since each invocation needs their own |
13:46.09 |
Notify |
03BRL-CAD:brlcad * 62512
brlcad/trunk/src/libged/gqa.c: this fixes the gqa resource bug. now
bu_parallel() gives every thread of execution a unique ID
*including* the parent bu_parallel() thread. this means our index
into a resource structure based on thread ID isn't the same or
correct if #resources == #cpus. need to think about this some to
see if we can index more intelligently into resource
arrays. |
13:58.18 |
Notify |
03BRL-CAD:brlcad * 62513
brlcad/trunk/src/libged/gqa.c: wow, old masked bug.
rt_init_resource only conditionally initializes various lists
within the resource structure, so this assumes that the entire
structure starts out as zero. just declaring the array does not
zero-initialize, so we were getting only partially initialized
resources undoubtedly causing random bad behavior with just the
right start-up memory and |
13:58.20 |
Notify |
cpus. |
14:10.29 |
*** join/#brlcad fenn_
(~fenn@131.252.130.248) |
14:33.30 |
*** join/#brlcad fenn
(~fenn@131.252.130.248) |
14:35.19 |
*** join/#brlcad vladbogo
(~vladbogo@86.127.152.212) |
15:01.53 |
Notify |
03BRL-CAD:carlmoore * 62514
brlcad/trunk/doc/docbook/system/man1/en/plot3-fb.xml: remove
trailing blank |
15:26.09 |
*** join/#brlcad vladbogo
(~vladbogo@86.127.152.212) |
15:33.44 |
*** join/#brlcad Izakey
(~Isaac@195.24.220.134) |
16:14.53 |
*** join/#brlcad kintel
(~kintel@unaffiliated/kintel) |
16:59.34 |
*** join/#brlcad gurwinder
(75dca9c7@gateway/web/freenode/ip.117.220.169.199) |
17:01.32 |
gurwinder |
brlcad: hello, I am trying to get three
arguments from commandline like which we give after option of
tolerence 'a'. I read getopt.h |
17:02.09 |
brlcad |
getopt is very simple |
17:02.09 |
gurwinder |
but using bu_optarg I am able to get only one
argument |
17:05.00 |
gurwinder |
ok, means I can get argument easily by using
getopt? |
17:06.06 |
brlcad |
no, it means that its argument parsing
interface is very simplistic, it's only doing exactly what you tell
it to do |
17:06.16 |
brlcad |
it has no way of knowing you want to read
three arguments |
17:06.31 |
brlcad |
moreover, that's usually an ill-defined usage
statement too |
17:06.43 |
brlcad |
(depending on what arguments and options
follow) |
17:07.00 |
brlcad |
what is this value you're trying to
scan? |
17:08.39 |
gurwinder |
ok, actually I want to get x, y, z coordinates
of camera from command line and write them into pov file |
17:09.14 |
brlcad |
you need more than xyz |
17:09.28 |
brlcad |
that's just a position |
17:09.50 |
brlcad |
you'd also need a direction vector, and some
sort of view frustum defintion |
17:10.35 |
brlcad |
terribly complicated as a set of user
options... nobody thinks in those terms :) |
17:11.36 |
brlcad |
curious, why does pov care? |
17:14.34 |
gurwinder |
hahaha sorry, need some time for understanding
english :P need more practice. Anyway, if I am correct then I think
you want to know why povray need these types of arguments?
right? |
17:15.20 |
brlcad |
yes |
17:15.42 |
brlcad |
it obviously needs a view to render, but not
to convert geometry |
17:17.19 |
gurwinder |
ok, I explain it. As in brlcad if we don't
give any camera view or don't give any light source, it take the
defaults by its own. |
17:18.00 |
gurwinder |
But in povray we have to give camera location
light sources by our own. It has no default one. |
17:18.05 |
brlcad |
for rendering |
17:18.51 |
brlcad |
why is it needed to convert geometry, though
-- because you can't use the converted geometry in pov-ray until a
camera is created? |
17:21.00 |
gurwinder |
yes |
17:24.21 |
*** join/#brlcad albertcoder
(~albertcod@117.219.84.33) |
17:27.25 |
*** join/#brlcad gurwinder
(75dca9c7@gateway/web/freenode/ip.117.220.169.199) |
17:30.46 |
brlcad |
gurwinder: then I suggest you handle the view
like our rendering tools do |
17:33.48 |
*** join/#brlcad Gurwinder
(3b5b7318@gateway/web/freenode/ip.59.91.115.24) |
17:34.04 |
brlcad |
i.e., you'll need -a -e -g -n -w and -p
options |
17:35.12 |
brlcad |
"brlman rt" to see what those all do but
basically they set up azimuth, elevation, grid size, view height,
view width, and perspective angle |
17:35.18 |
brlcad |
and are all single values |
17:35.51 |
Gurwinder |
ok, |
17:35.51 |
brlcad |
that will make your tool consistent with other
tools and is a simple way to specify a view |
17:36.05 |
brlcad |
you can test out those options with the rt
command on some .g file |
17:36.32 |
brlcad |
e.g., rt -a 35 -e 25 share/db/moss.g
all.g |
17:37.05 |
brlcad |
from those aegnwp options, you'll be able to
calculate the exact view parameters that povray wants |
17:38.30 |
Gurwinder |
ok, I will check all these. |
17:41.32 |
brlcad |
Gurwinder: you could also totally just punt
and write out a simple default "front" view |
17:41.45 |
brlcad |
or a default 35/25 view |
17:42.07 |
brlcad |
the emphasis should be on converting the
geometry as best possible |
17:43.14 |
brlcad |
there's a lot of view specification in povray
that they'll probably want to set up and those can just as easily
be done in povray instead of during conversion |
17:44.31 |
brlcad |
we have functions and example code that will
help you calculate a default view |
17:49.15 |
Gurwinder |
yes, exactlly. I am thinking that if we gave
those view points or what we call them as view parameter in default
option and let gave user another options in which s/he can give
camera view, light of his own choice? |
17:51.10 |
Gurwinder |
if I am right, does converting geometry means
converting the view as it is in POV-ray? |
17:53.00 |
brlcad |
I'm saying forget letting the user specify a
camera view of their own choice |
17:53.07 |
brlcad |
just create a default, any default |
17:53.44 |
brlcad |
if they want to change the view, they can do
that in povray or it can be an improvement to the g-pov tool
later |
17:54.30 |
brlcad |
for now, you should focus on converting the
geometry, which will get complicated |
17:54.57 |
*** part/#brlcad clock
(~clock@77-58-143-135.dclient.hispeed.ch) |
17:56.04 |
Gurwinder |
ok, got it. Yes, let it be for later
improvement. |
18:00.35 |
Gurwinder |
okay fine. Now I wiII work on this with aII
zeaI and devotion. Thanks for your precious guidance. :) |
18:08.14 |
*** join/#brlcad gurwinder_
(3b5b7318@gateway/web/freenode/ip.59.91.115.24) |
20:17.03 |
Notify |
03BRL-CAD:n_reed * 62515
brlcad/branches/brep-debug/src/libbrep/boolean.cpp: fix comparison
functions, segment joining, and building of segment
curves |
20:44.28 |
Notify |
03BRL-CAD:n_reed * 62516
brlcad/branches/brep-debug/src/libbrep/boolean.cpp: don't append to
previous events |
21:27.12 |
Notify |
03BRL-CAD:ejno * 62517
(brlcad/trunk/src/conv/3dm/conv3dm-g.cpp
brlcad/trunk/src/libgcv/bot_solidity.c
brlcad/trunk/src/libgcv/bot_solidity.h): prefix libgcv bot tests
with gcv_ and use HIDDEN rather than static; formatting |
22:31.46 |
Notify |
03BRL-CAD:ejno * 62518
brlcad/branches/bullet/src/libged/simulate/simrt.c: remove dead
code |
22:56.56 |
``Erik |
hm, 3d models of 'dreadnoughtus' are "freely
available"... I found some 3d pdf files at
http://figshare.com/articles/Dreadnoughtus_schrani_3D_PDF_images_Lacovara_et_al_2014_A_Gigantic_Exceptionally_Complete_Titanosaurian_Sauropod_Dinosaur_from_Southern_Patagonia_Argentina_Scientific_Reports_/1130885
O.o might be a good freely distributable large BoT for testing and
optimizing? |
23:12.43 |
*** join/#brlcad FreezingCold
(~FreezingC@CPE602ad06bea2a-CM602ad06bea27.cpe.net.cable.rogers.com) |
23:54.59 |
Notify |
03BRL-CAD:n_reed * 62519
brlcad/branches/brep-debug/src/libbrep/boolean.cpp: copy input
loops |