00:00.55 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
01:21.58 |
*** join/#brlcad crdueck
(~cdk@24.212.219.10) |
01:28.16 |
Notify |
03BRL-CAD Wiki:BiogiegoPah * 0
/wiki/User:BiogiegoPah: |
02:31.49 |
*** join/#brlcad ddg80
(~IceChat77@c-76-30-172-184.hsd1.tx.comcast.net) |
03:01.26 |
Notify |
03BRL-CAD:brlcad * 55152 brlcad/trunk/NEWS:
GCI participant chris dueck implemented and exposed support for
reporting ETO surface areas to the mged/archer analyze
command |
03:02.43 |
Notify |
03BRL-CAD:brlcad * 55153 brlcad/trunk/NEWS:
GCI participant chris dueck implemented and exposed support for
reporting ETO surface areas and volume to the mged/archer analyze
command |
03:03.31 |
Notify |
03BRL-CAD:brlcad * 55154 brlcad/trunk/NEWS:
GCI participant chris dueck implemented and exposed support for
reporting ARBN surface areas and volume to the mged/archer analyze
command |
03:07.50 |
Notify |
03BRL-CAD:brlcad * 55155 brlcad/trunk/NEWS:
GCI participant chris dueck implemented and exposed support for
reporting EPA surface areas, centroid, and volume to the
mged/archer analyze command |
03:10.58 |
Notify |
03BRL-CAD:brlcad * 55156
(brlcad/trunk/src/libged/Makefile.am
brlcad/trunk/src/libged/dag.cpp and 3 others): ws |
03:14.10 |
Notify |
03BRL-CAD:brlcad * 55157 brlcad/trunk/NEWS:
GCI participant chris dueck implemented and exposed support for
reporting EPA surface areas and volume to the mged/archer analyze
command |
03:35.32 |
Notify |
03BRL-CAD:brlcad * 55158
brlcad/trunk/src/librt/primitives/brep/brep.cpp: remove dead code,
the original utah-baed ray tracing method is now no longer
used. |
03:36.42 |
*** join/#brlcad dcd
(4c1eacb8@gateway/web/freenode/ip.76.30.172.184) |
03:36.52 |
*** part/#brlcad dcd
(4c1eacb8@gateway/web/freenode/ip.76.30.172.184) |
05:05.07 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
07:23.59 |
*** join/#brlcad brlcad
(~sean@66-118-151-70.static.sagonet.net) |
10:39.05 |
``Erik |
ddg80: non-vacuum gravity simulator? cool!
developing in windows should not be a problem, but we treat it as a
second class platform so there may occasionally be a commit that
breaks the windows build. the first step is to check out a copy of
the source code and compile it (you'll need an svn client like
tortoise, cmake and a compiler) |
10:51.40 |
*** join/#brlcad viku
(uid11086@gateway/web/irccloud.com/x-oimuaweddorfxhlk) |
11:32.03 |
*** join/#brlcad Daniel
(5123dc25@gateway/web/freenode/ip.81.35.220.37) |
13:04.13 |
starseeker |
woo hoo! https://github.com/stepcode/stepcode/pull/227 |
13:58.50 |
brlcad |
that is fantastic |
13:58.54 |
brlcad |
news-worthy even |
14:05.12 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
14:10.31 |
*** join/#brlcad rays2pix
(~deepak@110.234.229.2) |
14:13.02 |
brlcad |
starseeker: if you would, hold off on
switching to external stepcode until after release :) |
15:27.23 |
kanzure |
"Based on testing to date, it looks like the
merge branch merging in the BRL-CAD version of SCL to stepcode is
ready to go live." |
15:27.32 |
kanzure |
that's a tremendously huge merge |
15:27.35 |
kanzure |
wow |
18:07.53 |
``Erik |
ten ton pull request, I'm kinda surprised they
didn't ask you to close it and do a rebase |
18:08.26 |
``Erik |
awesome stuff, gratz O.o |
19:02.22 |
*** join/#brlcad hsrai
(~hsrai@202.164.53.116) |
20:08.17 |
starseeker |
brlcad: yeah, I've had enough bad luck with
that here lately |
20:08.42 |
starseeker |
I'm just doing a build test to see what issues
remain |
20:09.50 |
starseeker |
``Erik: actually, Mark was the one who asked
for the pull request |
20:25.19 |
starseeker |
brlcad: anyway, step-g builds but doesn't
function, so there's more clean-up to do before we're all the way
there |
20:25.46 |
kanzure |
does this massive merge include unit
tests? |
20:25.52 |
starseeker |
our converter must exercise stuff the existing
stepcode tests doesn't... |
20:25.54 |
kanzure |
were there ever any step-g unit
tests? |
20:26.00 |
kanzure |
*ever any |
20:26.10 |
starseeker |
kanzure: not to my knowledge - the stepcode
guys have added a lot of test code |
20:26.21 |
kanzure |
ah good, at least some exists then. |
20:26.34 |
starseeker |
but I don't know if they're unit
tests |
20:26.48 |
kanzure |
i am really bad at calling tests the right
things. i think i call all tests unit tests :). |
20:26.48 |
starseeker |
eventually we'll have step-g regression tests
too, but we aren't there yet |
20:27.00 |
starseeker |
heh |
20:27.07 |
kanzure |
i also tend to call regression tests and unit
tests the same thing, because nobody ever yelled at me about
it |
20:27.21 |
starseeker |
kanzure: if you check out the default stepcode
tree you'll see it doing a lot of test work |
20:27.24 |
kanzure |
also because the libraries for writing both
style of tests tend to be called "unitwhatever" and "unit"...
hrm. |
20:27.27 |
kanzure |
okay cool |
20:27.35 |
kanzure |
*TestUnit |
20:30.03 |
starseeker |
hmm: http://www.steptools.com/support/stdev_docs/stpfiles/ap203/ |
20:30.14 |
starseeker |
wonders what the NIST DPPA
repository is? |
20:30.18 |
kanzure |
btw have you met charlie stirk? |
20:35.18 |
starseeker |
never met him in person, no |
20:35.28 |
starseeker |
ah ha! http://edge.cs.drexel.edu/repository/ |
20:37.10 |
starseeker |
confound it, why don't they have copyright and
license info at the toplevel directory?? |
21:03.50 |
``Erik |
I think the pedantic interpretation of a unit
test is that every object/method/function used by the
method/function being tested is mocked out, so the only
interactions not guaranteed are in the function/method itself...
which can get a bit insane :D |
21:17.59 |
kanzure |
i tend to only partially mock things out.. so
i think the conclusion is that i am terrible at calling my tests
the right things ;) |
21:21.50 |
``Erik |
that you mock bits at all probably puts you
well ahead of the curve |
23:07.49 |
*** join/#brlcad gdh
(~quassel@pool-71-177-13-144.lsanca.dsl-w.verizon.net) |