IRC log for #brlcad on 20080410

00:58.56 andrecastelo hi guys
00:58.58 andrecastelo i'm back
00:59.00 andrecastelo hey brlcad
01:00.03 brlcad howdy andrecastelo
01:00.15 brlcad was just going through more applications now
01:00.20 andrecastelo hey, i have something to show you
01:00.33 brlcad I hope you have your pants on
01:00.46 andrecastelo lol hehehe
01:01.27 andrecastelo brlcad: here -> http://pastebin.com/m1cd03a7a
01:01.47 andrecastelo can you give me some feedback ? :)
01:03.27 CIA-20 BRL-CAD: 03johnranderson * r30653 10/brlcad/trunk/src/rt/ (opt.c rt.1 view.c):
01:03.27 CIA-20 BRL-CAD: Added a -k option to rt. Specifies a cutting plane to allow faster computation
01:03.27 CIA-20 BRL-CAD: of cutaway images. Note that this produces an approximation of the image that
01:03.27 CIA-20 BRL-CAD: would be produced by actually subtracting the equivalent halfspace. This may
01:03.27 CIA-20 BRL-CAD: satisfy bug #1812560 Cutaway view 210x slower.
01:05.15 brlcad andrecastelo: nice work
01:06.08 brlcad the only suggestion I'd make would be instead of using that forw linked list pointer, toss in a struct bu_list * instead
01:06.37 brlcad that's our linked list structure (technically a bidirectional linked list, there are a variety of BU_ macros related to it in include/bu.h)
01:06.52 andrecastelo hm ok, like struct point_list { struct bu_list * point_bu_list; point_t pt_cell; }; ?
01:07.12 andrecastelo yeah, i did notice and i first tried something that could be used with those macros
01:07.29 andrecastelo but i didn't know it deeply
01:07.34 andrecastelo i'll change and use the macros
01:07.39 brlcad yeah, that's the basic idea
01:07.47 brlcad maybe a better name :)
01:08.02 brlcad usually hp or head
01:08.17 brlcad or l
01:08.18 *** join/#brlcad DaytonaJohn (n=jra@c-68-55-36-65.hsd1.md.comcast.net)
01:08.23 brlcad usually 'l'
01:09.02 andrecastelo PointListHead ?
01:18.17 brlcad struct bu_list *l;
01:19.34 brlcad doesn't really what you name it though -- you loop via the macros and a ref to whatever you call it
01:23.23 brlcad DaytonaJohn: did you see the message from leslie?
01:28.34 andrecastelo do i have to declare a struct * bu_list or a struct * point_list to iterate through the list ?
01:30.51 andrecastelo nevermind
01:31.58 brlcad due to the good ol' nature of C, you can actually cast between the two so long as the list is the first element
01:32.19 brlcad good ol polymorphism bastardization of C :)
01:32.51 brlcad but in practice, you generally refer to struct point_list *my_list; then use my_list.l
01:34.21 andrecastelo brlcad: http://pastebin.com/d59ab103c
01:42.05 brlcad andrecastelo: looks better, so the last two things would be to fill in the list and print the CPA in the summary
01:43.00 andrecastelo ok.. one thing - i'm having trouble with bu_list - i need a struct point_list * forw in struct point_list ?
01:46.32 brlcad no, bu_list provides it
01:46.37 brlcad you don't worry about forward/next
01:47.32 andrecastelo weird
01:47.43 andrecastelo if i don't put it, i get this error - http://pastebin.com/m2fb6cdb1
01:48.20 brlcad andrecastelo: there's a fairly straight-forward bu_list example in src/libbu/temp.c
01:48.29 andrecastelo ok, i'll take a look
01:49.29 brlcad ah, yes, you need to pass the .l to BU_FOR
01:49.34 brlcad not just area_p->area_points
01:49.52 brlcad so something like area_p->area_points->l
01:50.23 brlcad it's usually not a pointer so you don't have to worry about memory allocation of your head node
01:50.39 andrecastelo ah ok
01:51.12 brlcad if you make it not a pointer, it becomes something like &(area_p->area_points.l)
01:51.41 brlcad interesting, it looks like the initial slot allocations can be roughly characterized as log(#submissions)^2 * 2
01:53.17 andrecastelo where #submissions is ?
01:53.22 andrecastelo ah nvm lol
01:53.59 andrecastelo how many submissions did brl-cad receive ?
01:55.06 brlcad more than enough :)
01:55.37 brlcad DaytonaJohn: sending note out now
01:55.45 andrecastelo ponders a new way to get that information
01:55.55 andrecastelo hehehe
01:56.03 DaytonaJohn brlcad: good, I'll watch for it
02:00.46 andrecastelo hey brlcad : the center point is related to presented area or exposed area ?? (if exposed, just gather the points in ray_hit() ??)
02:00.54 andrecastelo rayhit*
02:10.55 brlcad andrecastelo: technically for either, but exposed is what it usually refers to
02:11.06 brlcad that's the one they care about
02:12.31 andrecastelo hm ok
02:13.56 andrecastelo so, to make it versatile, struct area should have two lists of points ?
02:16.59 CIA-20 BRL-CAD: 03brlcad * r30654 10/brlcad/trunk/NEWS:
02:16.59 CIA-20 BRL-CAD: john added a new -k 'kutaway view' option to rt that allows users to specify a
02:16.59 CIA-20 BRL-CAD: cutting plane for fast(er) computation of cutaway images that approximates the
02:16.59 CIA-20 BRL-CAD: image that would be produced by actually subtracting the equivalent halfspace
02:16.59 CIA-20 BRL-CAD: and potentially satisfies clock's sf bug 1812560 (Cutaway view 210x slower) but
02:17.01 CIA-20 BRL-CAD: still makes this an absurd-yet-fun run-on sentence.
02:18.00 brlcad andrecastelo: yeah, if you wanted to match what that struct does, you'll see it keeps a counter for both presented and exposed
02:19.23 brlcad the faster parellel-smp-safe way would be to utilize a fixed results array for all possible hit points, so all cpus could fill in values for a given cell independently
02:19.39 brlcad as it stands implemented, there's massive lock contention on those counter variables
02:20.01 brlcad that's a bigger change though, for later
02:22.00 CIA-20 BRL-CAD: 03starseeker * r30655 10/brlcad/trunk/src/proc-db/tire.c: No functionality change - just adding some options for printing Maxima style equations for debugging. Committing for now so they're available if I have to throw out subsequent tests.
02:22.10 brlcad heh
02:23.35 starseeker Sorry brlcad, I'll back out the noise later - just playing safe in case I need 'em tomorrow
02:24.27 starseeker finds it makes life easier if he can just cut and paste for confirmation with Maxima's linsolve...
02:31.37 brlcad no skin off my back, it's your proc-db :)
02:31.51 brlcad just funny matching maxima's output :)
02:32.09 brlcad should make some libbn output formatters :)
02:32.35 brlcad pacman87: *ping*
02:33.01 pacman87 brlcad: pong
02:33.23 yukonbob waves in
02:37.55 andrecastelo the second parameter of bu_malloc() is for what exactly?? (genptr bu_malloc(size_t, const char *))
02:41.09 brlcad debugging label
02:41.15 brlcad just but the name of the object
02:41.18 brlcad "foo"
02:41.24 brlcad s/but/put/
02:41.52 brlcad the run-time debugging facilities will hierarchically print out the labels for allocation/deallocation
02:42.24 brlcad so you usually set it as "alloc area_points" during bu_malloc and "free area_points" during bu_free
02:42.55 brlcad so you can match up allocations/deallocations (if that is what you're debugging)
02:43.07 andrecastelo hm ok ok
02:43.30 brlcad ranks andrecastelo's app
02:43.47 andrecastelo shakes
02:44.20 brlcad hmm, I still need more info from several people
02:44.24 pacman87 brlcad: you wanted me?
02:44.55 brlcad heya pacman87
02:45.03 brlcad oh, missed the pong, jeez
02:45.10 brlcad too quick for me :)
02:45.36 pacman87 dorm room, so i'm usually not very far from my computer ;)
02:46.20 brlcad hmm.. what did I want you for, oh yes -- I know we've talked about it, but are you still intending to submit a patch?
02:46.40 pacman87 yes
02:46.53 pacman87 i'm coding now
02:47.05 pacman87 my second test this week was tonight
02:56.51 brlcad okay, cool
02:57.14 brlcad if all you can get done is just one or two of the callback funcs for what you were implementing, that's certainly better than nothing
02:58.27 pacman87 when do you want it by?
03:06.43 brlcad I'd suggest just submitting what you have (presuming "something" works) so it can be reviewed (some of the mentors have only tomorrow to rank, others longer) and then continuing from there if you want through to absolutely no later than the 16th
03:08.02 pacman87 brlcad: i'm not sure how 'testable' it will be without adding it to mged or the other steps
03:08.34 brlcad testable in the sense of being able to add it to the build, get it to compile :)
03:08.40 brlcad we can read code ;)
03:08.52 pacman87 i'm planning on submitting it when i get done tonight
03:08.58 brlcad okay
03:09.01 pacman87 'get done' = wnen i go to bed ;)
03:09.36 pacman87 and keep working on it until it's usable
03:10.49 brlcad cool
03:30.22 andrecastelo well, i'm off to bed now
03:30.33 andrecastelo i'll take care of this tomorrow ;)
03:30.37 andrecastelo cya guys
03:31.13 brlcad cya andrecastelo
03:31.23 andrecastelo cya brlcad
03:32.59 brlcad ~seen mafm
03:33.01 ibot mafm <n=mafm@elnet-111.lip.pt> was last seen on IRC in channel #brlcad, 8h 52m 35s ago, saying: 'heading off, take care'.
03:33.46 brlcad yukonbob & ``Erik: you've got mail
04:03.48 brlcad ~seen jdoliner
04:03.49 ibot jdoliner <n=jdoliner@wireless-239-77.uchicago.edu> was last seen on IRC in channel #brlcad, 8d 9h 53m 2s ago, saying: 'brlcad are you present?'.
04:09.07 pacman87 mergesort for a 4-element list is probably overkill :)
04:10.56 starseeker growls... the solver isn't in agreement with maxima, but the difference is harder to spot this time...
04:15.25 brlcad pacman87: probably :)
04:17.50 pacman87 but i didn't feel like coding a mess of nested if-else blocks
05:32.00 yukonbob brlcad: /me sees he's got mail -- also thinks he's running a misconfigured MTA :P -- gotsta fix so I'm not part of the spam problem...
05:50.02 brlcad yukonbob: hm? misconfigured mta?
06:06.41 *** join/#brlcad clock_ (n=clock@217-162-111-200.dclient.hispeed.ch)
07:02.14 spike_ thinks its time to sleep, night everyone
07:02.56 *** join/#brlcad clock_ (n=clock@zux221-122-143.adsl.green.ch)
07:41.36 pacman87 what are uv_du and uv_dv used for in struct uvcoord?
08:19.25 hippieindamakin8 :( so the patch was useless
08:20.22 pacman87 hippieindamakin8: what patch?
08:21.08 hippieindamakin8 i submitted a patch for nsis script
08:21.35 pacman87 non-english windows %PROGRAM FILES%?
08:21.42 pacman87 or was that a different one
08:22.10 hippieindamakin8 kind of yes :)
08:22.36 pacman87 why is it useless?
08:22.45 hippieindamakin8 it doesnt work :P
08:22.54 hippieindamakin8 as brlcad pointed out
08:23.04 pacman87 you know why not?
08:23.18 hippieindamakin8 and did u submit any ?
08:23.25 pacman87 i'm compiling now
08:23.28 pacman87 to make sure it works
08:23.39 hippieindamakin8 ohh
08:23.51 hippieindamakin8 i dint chk it as i dint have windows with me..
08:24.01 pacman87 cross your fingers :)
08:24.08 hippieindamakin8 which patch are u working on ?
08:24.19 pacman87 adding a hyperboloid of one sheet
08:24.31 pacman87 it's not completely finished yet
08:24.37 hippieindamakin8 :)
08:24.40 hippieindamakin8 naice
08:24.59 pacman87 still needs a few functions implemented, and hooks into mged
08:25.58 hippieindamakin8 so implementing a new primitive
08:26.14 pacman87 an 'easy' primitive
08:26.34 pacman87 since my GSoC proposal is implementing 'hard' primitive(s)
08:34.20 hippieindamakin8 :)
08:34.37 hippieindamakin8 i shall start working on another patch :)
08:34.47 pacman87 got an idea?
08:53.31 pacman87 my computer is embarassingly slow
08:55.25 clock_ pacman87: ZX Spectrum?
08:58.37 pacman87 clock_: not quite :)
09:00.03 pacman87 2.8 GHz P4, 533MHz FSB, 1280MB DDR2700 RAM
09:02.07 hippieindamakin8 i have no idea looking through the bugs and the to do list
09:06.27 pacman87 4:04 - time not found
09:34.22 *** join/#brlcad mafm (n=mafm@elnet-111.lip.pt)
09:35.26 mafm hi
09:35.33 pacman87 hi mafm
09:59.26 *** join/#brlcad Axman6 (n=Axman6@pdpc/supporter/student/Axman6)
10:08.58 pacman87 ~pastebin
10:08.59 ibot [~pastebin] A "pastebin" is a web-based service where you can paste anything over 3 lines without flooding the channel. Here are links to a few : http://www.pastebin.com , http://pastebin.ca , http://channels.debian.net/paste , http://paste.lisp.org , http://www.rafb.net/paste
10:10.12 pacman87 http://pastebin.bzflag.bz/m4039501d
10:10.39 pacman87 if anyone could shed some light on that, i'd be quite grateful
10:14.00 pacman87 i'm holding off on the patch until brlcad actually compiles, but until then, here's the g_hyp.c: https://webspace.utexas.edu/trv82/www/g_hyp.c
11:07.35 *** join/#brlcad d_rossberg (n=rossberg@bz.bzflag.bz)
11:52.10 *** join/#brlcad docelic (n=docelic@78.134.198.227)
12:03.24 *** join/#brlcad docelic (n=docelic@78.134.198.227)
12:35.11 *** join/#brlcad mafm (n=mafm@elnet-111.lip.pt)
12:59.23 *** join/#brlcad mafm (n=mafm@elnet-111.lip.pt)
13:38.30 *** join/#brlcad andrecastelo (n=chatzill@189.71.41.1)
13:38.39 andrecastelo good morning everyone
13:40.20 brlcad good morning andrecastelo
13:41.50 brlcad pacman87: uv coordinates are for uv mapping :) e.g., wrapping a texture
13:45.11 brlcad pacman87: should post up the file to the patches tracker and link it in your app too, but looks good
13:47.59 brlcad andrecastelo: similar for you, don't see a patch link in your app
13:48.23 brlcad ah, found it
13:48.54 andrecastelo brlcad: i'm still brewing my patch :) but i'll link to it once it's ready
13:49.05 brlcad yeah, just remembered
13:49.13 ``Erik *yawn*
13:59.05 andrecastelo hey brlcad, can i use rayhit() (in viewarea.c) to store the points in the areas ? could i use partition->hit->hit_point ?
13:59.47 brlcad you shouldn't modify the partition directly
13:59.57 brlcad other than readin git
14:00.28 brlcad but otherwise, yes -- rayhit is the hit callback, so that's where you know what/where you hit the geometry for a given cell
14:00.51 andrecastelo yeah, i could read the partition->hit->hit_points and store them in the respective areas
14:07.30 brlcad hippieindamakin8: did you not put your irc nick in your proposal? I don't see it (you did read the submission guidelines, right?) .. and you've not done well to answer your app comments
14:08.32 brlcad wanders for a bit
14:09.05 *** join/#brlcad camcorder (n=draco@81.213.157.51)
14:10.06 hippieindamakin8 hey i am answering it rt now
14:15.47 hippieindamakin8 brlcad, i am sorry .. been a bit busy with the end semester exams appraoching ya i am updating them
14:17.15 Axman6 i has my last mid-sem tonight
14:17.20 Axman6 on haskell!
14:22.02 pacman87 brlcad: re; uv mapping, i know what the U and V are, but i'm not sure what du and dv are for. struct uvcoords has 4 members, not just the two
14:23.03 Axman6 change in u and v?
14:23.07 ``Erik dorks with this silly spreadsheet thingiemajigger
14:23.13 Axman6 as in, delta u, delta v
14:23.31 Axman6 or some odd form of derivitive?
14:23.58 Axman6 wow, i've been doing way too much physics, calculus and linear algebra
14:26.13 pacman87 Axman6: that was my guess too, but i'm not sure what it's with respect to (as in dy/dx)
14:26.37 Axman6 du/dv?
14:26.46 Axman6 chain rule stylez
14:27.21 hippieindamakin8 in brlcad if i get it rt.. mged accesses the primitive from librt and that particular file in librt renders it as well
14:28.16 hippieindamakin8 pacman87, it is not dy/dx it is delta u and delta v
14:28.31 hippieindamakin8 its not the gradient it is the difference
14:28.37 Axman6 whoot, i was right
14:28.55 hippieindamakin8 ya Axman6
14:28.55 pacman87 difference between what?
14:30.13 hippieindamakin8 i dont know wat u are dealing with pacman87 :) i am not sure :P
14:31.44 hippieindamakin8 if u and v are the co-ordinated delta u is increment
14:32.59 pacman87 right, but the increment to what? you need two points to get the difference
14:34.21 Axman6 well, it could be used for a matrix...
14:34.30 Axman6 1 0 du
14:34.36 Axman6 0 1 dv
14:34.41 Axman6 0 0 1
14:34.48 hippieindamakin8 pacman87, i really dont know wat u are dealing with :)
14:35.17 hippieindamakin8 pacman87, can u send me if there is some good material for raytracing
14:35.36 Axman6 apply that to a point (u,v,1), and you'll get (u+du,v+dv,1)
14:36.00 Axman6 learnt this today in his linear algebra lecture
14:37.17 andrecastelo suddenly realizes he has to study linear algebra again
14:50.10 pacman87 hippieindamakin8: the book i found is 'an introduction to ray tracing', ed. Glassner, isbn0-12-286160-4
14:51.44 archivist Glassner, thats a name I remember, hes done a few books (Graphics Gems etc)
14:53.50 pacman87 this book is essentially the notes from the siggraph 88 course on ray tracing
14:56.49 archivist we had a user in ##asm saying he was doing ray tracing in assembler yesterday
15:04.02 pacman87 any thoughts on this: http://pastebin.bzflag.bz/m4039501d
15:04.55 pacman87 i'm currently going back and re-applying my changes one by one to see what broke it
15:41.34 *** join/#brlcad Elperion (n=Bary@p54877365.dip.t-dialin.net)
15:51.07 *** join/#brlcad spike_ (i=[U2FsdGV@centaur.acm.jhu.edu)
16:50.09 hippieindamakin8 thanks pacman87
16:51.45 hippieindamakin8 pacman87, do u have an e version of this book ?
16:52.26 andrecastelo pacman87: i'd be interested in that too hehehe
17:02.46 pacman87 hippieindamakin8 & andrecastelo: no, just the hard copy from my uni library
17:02.49 pacman87 sorry
17:03.12 hippieindamakin8 ohh i just looked up the lib database :( it aint in the library
17:06.50 pacman87 http://books.google.com/books?id=YPblYyLqBM4C&dq=%22an+introduction+to+ray+tracing%22+glassner&pg=PP1&ots=yY581FriR9&sig=HyIgo17F5oFn7gfy_NTdKky-En4&hl=en&prev=http://www.google.com/search?hl=en&client=opera&rls=en&hs=eE0&q=%22an+introduction+to+ray+tracing%22+glassner&btnG=Search&sa=X&oi=print&ct=title&cad=one-book-with-thumbnail
17:10.41 hippieindamakin8 tx
17:12.47 pacman87 missing pieces here and there, but that's about as close as you're going to get
17:13.49 pacman87 i found the book by looking at course websites for graphics classes, under the prof's 'suggested reading'
17:13.52 hippieindamakin8 :)
17:13.58 hippieindamakin8 ohh
17:14.13 hippieindamakin8 ill look up MIT's OCW once
17:16.19 pacman87 got a 96 on his tuesday test
17:16.39 hippieindamakin8 :) which subject?
17:16.45 pacman87 circuits
17:17.00 pacman87 second order and AC steady state/phasor analysis
17:17.13 hippieindamakin8 ohh which major are u ?
17:17.25 pacman87 i'm a MechE, but i'm taking EE courses for fun
17:18.08 pacman87 i only need one more ME course, a gov, and 3 electives to graduate
17:18.11 hippieindamakin8 hates Mech Engg.
17:18.17 pacman87 and i've still got two full semesters left
17:18.33 pacman87 what major are you?
17:18.33 hippieindamakin8 sadly i am also enrolled in Mech. Eng
17:18.45 pacman87 why don't you like it?
17:19.13 hippieindamakin8 3rd year Mech.Engg .. i hate Fluids,i hate Manufacturing
17:19.22 hippieindamakin8 i hate material sciences :)
17:19.56 pacman87 once you get navier-stokes, fluids is easy
17:20.02 hippieindamakin8 i am interested in computer vision , CAD and robotics
17:20.13 pacman87 woot, compile worked
17:20.23 pacman87 forgot --enable-all on the configure
17:20.44 pacman87 time to make the patch files
17:20.51 hippieindamakin8 and it is just Navier Stokes equation and why dont u get a computer to solve the equations :P rather than getting it solved by the students in the written exam
17:21.01 hippieindamakin8 congrats
17:25.35 hippieindamakin8 andrecastelo, this can be of some help
17:25.38 hippieindamakin8 http://ocw.mit.edu/OcwWeb/Electrical-Engineering-and-Computer-Science/6-837Fall2003/LectureNotes/index.htm
17:29.18 pacman87 just realized his uv mapping ignores the top/bottom plates :(
17:35.15 brlcad pacman87: that error is because it's using a system tcl/tk 8.4 yet compiling the bundled incrTcl (which requires 8.5) -- so you either have to --enable-all on configure (or at least --enable-tcl and --enable-tk) or you can try installing a system incrTcl for 8.4
17:38.14 pacman87 brlcad: thanks, i realized that this morning, when a vanilla svn co gave the same error
17:38.42 pacman87 everything compiles now on my end
17:38.49 pacman87 and ive got the patch files
17:38.55 pacman87 last thing to do is fix my UV mapping
17:41.32 brlcad cool
17:57.10 andrecastelo hey brlcad.. i'm getting this http://pastebin.com/d47b91c2e when trying to compile this http://pastebin.com/d364f3ce5 ...
17:57.30 andrecastelo the compile error on line 6 is the weirdest
17:58.06 andrecastelo also, the snippet of code is inside rayhit(), in the exposed areas "for()" block
17:59.19 andrecastelo any clues ?
17:59.42 yukonbob waves in
18:06.27 andrecastelo well, i'll have to go now, i'll try this later
18:06.29 andrecastelo cya guys
18:08.55 pacman87 patch is up: http://sourceforge.net/tracker/index.php?func=detail&aid=1939611&group_id=105292&atid=640804
18:10.54 CIA-20 BRL-CAD: 03starseeker * r30656 10/brlcad/trunk/src/proc-db/tire.c: Fix two bugs in matrix solver.
18:17.38 mafm bye
18:17.43 brlcad cya mafm
18:22.06 ``Erik blargh
18:22.44 brlcad hey yukonbob
18:24.35 brlcad pacman87: heh -- for future reference, svn is way better at making patches for you
18:24.38 brlcad svn add src/librt/g_hyp.c
18:24.50 brlcad then svn status to see what files you've changed/added/removed
18:25.00 brlcad then svn diff > your.patch
18:25.08 brlcad and it'll have everything in it (including the new file)
18:25.22 brlcad much easier to apply that way
18:26.31 ``Erik *snicker*
18:26.32 ``Erik During a screening interview, I was asked how I would design a bike fit for someone visually impaired. I responded something to the effect of, "What, like, for blind people?", and she answered yes.
18:26.32 ``Erik I thought for a moment and then I responded, "Well.. a blind person riding a bike doesn't sound like a very safe idea, so I would make the bike stationary, maybe with a fan blowing in the person's face. He probably wouldn't even know the difference."
18:27.08 brlcad hehe
18:31.24 pacman87 brlcad: svn diff kept including all the makefiles and that sort of thing
18:31.40 ``Erik svn should ignore the generated files :/
18:33.54 brlcad it should ignore anything you've not svn added too
18:34.14 pacman87 there's a bunch of .dsp files
18:34.17 ``Erik yeh, don't do "svn add *"
18:34.19 brlcad you probably did edit the src/librt/Makefile.am -- that could go in the patch
18:34.30 brlcad pacman87: ahh.. that would be your editor
18:34.32 pacman87 i did, and it's there
18:34.36 brlcad shame on it :)
18:34.49 brlcad svn status shows files it thinks are modified with an M
18:34.53 brlcad the dsp files shouldn't be modified
18:34.59 brlcad svn revert those files
18:35.11 brlcad svn revert any file you didn't intentionally edit
18:35.19 brlcad then they shouldn't be in the diff
18:35.30 pacman87 well, that's why i just diff'd the files i did edit
18:35.35 brlcad that matters anyways for commit, if you'd svn commit, you'd be commiting those files with changes too
18:36.08 brlcad yeah, you can always svn diff path/to/file.c path/to/file2.c ... > mypatch
18:36.30 brlcad but those files shouldn't be modified -- that's a misconfiguration somewhere along the line
18:39.12 brlcad pacman87: here's the config file I usually use: http://brlcad.org/~sean/subversion.config
18:42.00 pacman87 and that goes in ./.svn/?
18:42.44 brlcad can copy that to ~/.subversion/config
18:46.39 *** join/#brlcad hippieindamakin8 (n=hippiein@210.212.55.3)
18:48.19 ``Erik hum, in g_hyp.c, the import/export functions use ntohd/htond solely instead of using ntohl/htonl on the long ints (like magics) O.o ("shoudl work" on most current os's, but isn' guaranteed)
19:02.21 pacman87 ``Erik: i haven't implemented those yet, what's currently there now is what was in g_xxx.c
19:03.18 pacman87 the patch details lists the functions i've actually done
19:06.23 ``Erik import5/export5 I meant, no one cares about v4 anymore :)
19:06.32 yukonbob ``Erik: re: bike -- LOL
19:07.11 ``Erik hrm? oh, clear? my favorite color :D
19:09.53 ``Erik has been saying that since highschool
19:29.45 pacman87 anyone care to give this a read through? http://brlcad.org/wiki/Revolve_Primitive
19:34.22 CIA-20 BRL-CAD: 03starseeker * r30657 10/brlcad/trunk/src/proc-db/tire.c: Testing new way of specifying top ellipse.
19:50.27 *** join/#brlcad hippieindamakin8 (n=hippiein@210.212.55.3)
19:59.46 yukonbob loads pacman87's post
20:03.53 ``Erik ew, rar
20:08.11 ``Erik thinks this is a menu driven console bank transaction program, looks like it's for a class?
20:11.58 ``Erik ah, yeah, heh, on the page... 'simplify and simulate a bank'
20:57.56 ``Erik wiggles his toes
22:18.35 *** join/#brlcad clock_ (n=clock@77-56-95-49.dclient.hispeed.ch)
22:45.18 *** join/#brlcad clock_ (n=clock@77-56-95-49.dclient.hispeed.ch)
22:49.48 *** join/#brlcad hippieindamakin8 (n=hippiein@210.212.55.3)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.