From 744de8a65d665006584c50dc542b5a33c36e2c14 Mon Sep 17 00:00:00 2001 From: C R Onjob Date: Fri, 25 Jul 2014 01:00:04 +0800 Subject: [PATCH] Automatic commit of irc logs You love peace. --- irc/#ipdf.log | 175 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 175 insertions(+) diff --git a/irc/#ipdf.log b/irc/#ipdf.log index 3a9cbd2..77a4282 100644 --- a/irc/#ipdf.log +++ b/irc/#ipdf.log @@ -2946,3 +2946,178 @@ 17:22 < matches> I like that they seem to store the sign as part of the size 17:22 < matches> If something has a negative size it is negative and has |size| digits 17:34 < matches> I guess I will try and write some sort of report about how we implemented Arbitrary Integers but they are terrible compared to existing implementations :P +--- Day changed Thu Jul 24 2014 +14:44 < matches> So I was going to work on the project but existential dread +14:45 < matches> About whether my major exists +14:45 < matches> Do I exist? +14:49 <@sulix> Are you thinking? Because cogito ergo sum. +14:50 < matches> I'm not sure I was thinking when I picked this major... +14:50 <@sulix> I did some project code yesterday and then a bug I thought I'd fixed reappeared so I got distracted failing to fix that. +14:50 < matches> Haha +14:53 < matches> Should I upset everyone and recommend freshers for wheel again... +14:54 <@sulix> I'm all for it, but I think the consensus was that we need to make them actually do wheel-y projects first. +14:55 < matches> That seems kind of hypocritical though +14:55 < matches> Because nearly none of active wheel has actually done wheel-y projects +14:55 < matches> Certainly not before getting on wheel +14:56 <@sulix> My current random guess is that the problem is that people used to fix the desktops and stuff, and now everyone has their own laptops to break. +14:56 < matches> But I'll be quiet or people might decide I need to be removed due to lack of doing useful things +14:56 < matches> Yeah +14:56 < matches> That too +14:57 <@sulix> I'll definitely bring it up at the meeting. +15:02 <@sulix> So which CoderDojo forms do I need to fill out? +15:02 < matches> Ooh! +15:02 < matches> http://coderdojowa.org.au/volunteer +15:02 < matches> This one +15:03 < matches> But now you've said that I'm already adding you to the mailing list... +15:04 < matches> There's a thing on Saturday in 2.01 in CS at 12:00pm +15:04 < matches> I hope people actually show up because we are pretty short on presenters +15:04 <@sulix> Yeah, I've got a programming competition then. I'm trying to work out how much of the schedule for the competitions exists. +15:06 <@sulix> Okay, apparently there are programming competitions every saturday in August, which will be fun. +15:07 <@sulix> Although half of them are "details TBD," which sounds ominous. +15:07 <@sulix> Also there is a round 2 and a round 4 but no round 3. +15:11 <@sulix> Okay: it looks like the only weeks I don't have programming competitions on are the last 3 on the form. +15:13 <@sulix> Also I suspect they're running out of names for the programming competitions, because this Saturday's is called the "South Pacific Winter Programming Carnival". +15:21 < matches> Haha +15:27 <@sulix> Form submitted. Sorry for the snarkiness. +15:40 < matches> Brilliant +15:40 < matches> You can do a C or C++ workshop or something :P +15:40 < matches> Or just talk about Commander Keen that'll work +15:40 < matches> Or "Why Javascript is awful and you should forget all the lessons" +15:42 <@sulix> "Intro to DOS programming." :P +18:38 < matches> I did a sort of half hearted attempt at writing more about Arbints +18:39 < matches> Maybe I'll try put fonts in +18:39 < matches> That seems vaguely like not what I am supposed to be doing right now :P +18:43 < matches> There's that virtual FPU sitting there doing nothing +18:43 < matches> That I promised to do things with in my lit review +18:43 < matches> That Tim is marking +18:43 < matches> When I haven't actually done anything with it and he knows it... +18:44 < matches> I can't help but feel like we need a more impressive thing to zoom in on +18:44 < matches> Or even a way to draw things once we have zoomed in +18:46 < matches> Does "We implemented Arbitrary Precision Integers but GMP did it better" count as research? +19:13 < matches> Do we have a memory leak? +19:13 < matches> I've been running it for a while and things are slowing down +19:25 <@sulix> matches: With GMP or just doubles? +19:27 <@sulix> My quick check has us not leaking memory with doubles. +19:27 <@sulix> Well, X leaks memory and the nVidia driver leaks memory, but we're fine. +19:35 < matches> I was actually running with singles :S +19:35 < matches> See push to documents repo +19:35 < matches> There is a pdf +19:35 < matches> I did a thing +19:38 < matches> I'm basing the assumption that x86-64 is IEEE compliant on the fact that it passed the "paranoia" program +19:39 <@sulix> Yeah, x86_64 is IEEE compliant. +19:39 <@sulix> x86_32 is "mostly" IEEE compliant if I recall. +19:41 < matches> Well a picture tells a thousand words +19:41 < matches> So I think I wrote 8000 words today +19:41 < matches> Progress! +19:43 <@sulix> http://cgit.freedesktop.org/mesa/mesa/tree/src/mesa/drivers/dri/i965/brw_defines.h?id=9d6166880da83887e3246fb4498c3a07d979cc3b#n162 +19:43 <@sulix> I'll see if I can find where they actually set it to non IEEE. +19:43 < matches> Oh I was going to say fglrx did different things to nVidea but as I don't have nVidea that's difficult to do +19:45 <@sulix> Although there's this: http://lists.freedesktop.org/archives/mesa-dev/2013-July/041555.html +19:45 <@sulix> Yeah, nVidia, Intel and fglrx all seem to do different things. +19:45 <@sulix> fglrx does the strangest things. +19:45 <@sulix> nVidia does the most consistant things. +19:45 <@sulix> Intel sits nicely in the middle. +19:46 < matches> If we can get four screenshots of the different things at the same view bounds that might be useful +19:47 < matches> Also working out more about what the jagged edges implies about the precision/rounding might be helpful +19:47 < matches> All I've got is "This is clearly not a circle" +19:48 < matches> So it's still doing that with the quad trees enabled, so I assume the quad trees aren't amazingly quadifying everything yet :P +19:48 <@sulix> The quadtrees are basically doing nothing but occasionally causing bugs. +19:48 <@sulix> http://davidgow.net/stuff/ipdf-nvidia.png +19:48 < matches> That is progress at least +19:49 < matches> Thanks +19:49 < matches> I will update the others to be the same view bounds +19:49 < matches> I *think* we have code to set the view bounds at start? +19:51 <@sulix> http://davidgow.net/stuff/ipdf-intel.png +19:51 < matches> Haha +19:51 < matches> Well it's really obvious that that's different +19:52 < matches> Can you rerun it with -b 0.0869386 0.634194 2.63295e-07 2.63295e-07 +19:52 < matches> Obsessive compulsive... +19:52 < matches> Must all be same view bounds... +19:53 < matches> I'd run it on my other laptop with intel integrated graphics except the keyboard still doesn't work +19:55 < matches> Actually don't bother +19:55 <@sulix> http://davidgow.net/stuff/ipdf-nvidia1.png +19:57 <@sulix> http://davidgow.net/stuff/ipdf-intel1.png +19:59 < matches> oah wierd stuff is happening with the quad tree +19:59 < matches> There is a big circle and a little circle +19:59 < matches> Is that supposed to be here... +20:00 < matches> The distance between them is not constant :S +20:09 <@sulix> Yeah, that doesn't happen on intel and is the bug I've been hitting my head against. +20:09 <@sulix> Pretty certain I'm trying to render one more object than there actually is somewhere, maybe corruping memory in the process. +20:32 < matches> Ok so it turns out the CPU is actually about as terrible as the GPU at those view bounds when you replace the "double" with "float" in the Circle Renderer :S +20:32 <@sulix> That's what I expected. +20:32 <@sulix> It looks like the nVidia one, right? +20:32 < matches> But it does slightly different wrong things! +20:34 < matches> It looks similar-ish +20:35 < matches> It is blocky as opposed to zig zaggy +20:39 < matches> As in it doesn't look as whack as intel +20:43 <@sulix> Hmm... I'm not sure what I'm doing wrong, but I can't see any artefacts at all with CPU rendering w/ those bounds. +20:55 < matches> They are hard coded as doubles +20:55 < matches> Not floats +20:55 < matches> Or reals rather +20:56 <@sulix> Ah. +20:56 <@sulix> This explains much. +21:08 < matches> I have pushed a thing +21:09 < matches> It almost sounds like a real paper +21:09 < matches> Until you realise all it is is "we drew some circles and they look different" +21:09 < matches> Also your screenshots had some kind of crazy blue glowy border +21:10 <@sulix> Yeah, that's the KDE window shadow. +21:10 < matches> Fancy +21:10 <@sulix> It used to make the nVidia driver corrupt screenshots, but it seems to work now. +21:11 < matches> I'm pretty pleased with that 4 way comparison figure... +21:12 < matches> "One of these things is not like the others..." +21:12 < matches> *cough* intel +21:12 <@sulix> The conclusion is brilliant. +21:15 < matches> If we assume the nVidia and x86-64 figures are what things are supposed to look like +21:15 < matches> fglrx tries really hard +21:15 < matches> But doesn't quite make it +21:16 < matches> (I'm pretty sure that's just a particularly good view for it) +21:16 < matches> (If you move it around it goes insane) +21:16 < matches> I can respect the intel shader +21:16 < matches> It isn't afraid to blatantly disregard the rules +21:17 < matches> intel driver rather +21:17 < matches> Not sure why I put "shader" there +21:17 < matches> This has not been as productive as I hoped +21:18 < matches> Still +21:18 < matches> We finally have something written that Tim can pass judgement on +21:18 < matches> He's still in the country right? +21:19 < matches> He might want to finish passing judgement on my literature review first :S +21:21 <@sulix> I think he's still in the country, but don't hold me to that. +21:22 < matches> Ok, so if you translate around with the CPU things don't go insane, but they do on the GPU. That might be caused by something else though. +21:23 < matches> I'll be at University tomorrow +21:24 <@sulix> I might head in, too, then. +21:25 <@sulix> Do things still "go insane" on the GPU with CPU-side coordinate transforms. +21:26 < matches> Yeah +21:26 < matches> It looks like there is a tear +21:27 < matches> So you get this rectangle pattern +21:27 < matches> If you move it around on the CPU it maintains its shape +21:28 <@sulix> I think that fglrx (or maybe just the AMD hardware) calculates the coordinates per-triangle rather than per-vertex or something. +21:28 < matches> Under fglrx the bottom part of it sort of maintains its shape but there is a big diagonal line and the stuff above that changes +21:28 <@sulix> That's pretty weird. +21:29 < matches> Also the bottom part doesn't have concave bits but the top occasionally gets one +21:29 < matches> concave/overhanging whatever +21:29 <@sulix> The whole thing maintains its shape on nvidia (and even intel) +21:29 < matches> Well, the bottom half (and also the CPU/nVidia entire thing) looks kind of like a stair case +21:29 < matches> The top bit gets all these sticky out bits and overhangs +21:30 < matches> Which brings us to our next paper +21:30 < matches> The geology of fglrx +21:30 <@sulix> Intel also does the "staircase" on the other side of the circle. +21:30 < matches> On the other side... +21:30 < matches> Hmm the plot thickens +21:31 < matches> Oh well I need to sleep +21:31 < matches> Why do I feel like I have actually lost sleep over the holidays... +21:32 < matches> I am not ready for semester to start :( +21:32 <@sulix> I know exactly what you mean. +21:33 < matches> I seem to have been roped into unpaid work with physics +21:34 <@sulix> Oh dear. More lab demonstrating or something more interesting? +21:34 < matches> Hopefully if I visit ECM they won't make me do GENG5505 yet +21:34 < matches> Fixing my honours experiment I think... +21:35 <@sulix> Another pipe corroded through? +21:35 < matches> Haha +21:35 < matches> They were wondering where all the electronics went +21:35 < matches> (I have most of it) +21:35 < matches> (Also it's no longer functional) +21:36 < matches> (I may have taken some of it apart...) +21:36 < matches> (Although really the sensible option would have been to burn it with fire) +21:37 < matches> Goodnight anyway +21:37 <@sulix> I'm required to "correct" anything they want to change with this project after submitting it. +21:37 <@sulix> On the morrow, then! -- 2.20.1