X-Git-Url: https://git.ucc.asn.au/?p=ipdf%2Fdocuments.git;a=blobdiff_plain;f=irc%2F%23ipdf.log;h=8e405bde80633fdee85e74da36572e175f26bbdb;hp=2ceb74e6a92f611b9351e2880ed9db49d1c0d1d5;hb=91215cb6d59e0c89361207f31e3b3a802a56ca46;hpb=eab040bf153d7892f369fbc510eb495f7da6e842 diff --git a/irc/#ipdf.log b/irc/#ipdf.log index 2ceb74e..8e405bd 100644 --- a/irc/#ipdf.log +++ b/irc/#ipdf.log @@ -4176,3 +4176,78 @@ 21:59 < matches> But if you zoom in too far it starts to get classifications totally wrong 22:02 < matches> Yeah I have an abstract due in 2 weeks 22:02 < matches> so screwed +--- Day changed Tue Sep 02 2014 +13:42 < matches> Ok, let's not use floating point values for colours +13:42 < matches> Baad +13:43 < matches> Bad bad +13:43 < matches> Bad sheep +13:43 < matches> The project isn't about precision of representable colours +13:44 < matches> So I'm perfectly OK with using uint8 for colour components +18:53 < matches> Is it too late to change the aim of the project to "render svg-tests/fox.svg but without antialiasing" +18:54 < matches> "Or using the GPU" +18:55 < matches> Well, I understand why shading doesn't usually use flood fill now anyway +18:55 < matches> But I still kind of think flood fill is better at high resolutions +18:56 < matches> Not parallelisable I guess +18:56 < matches> ... Or is it +18:57 < matches> I was going to try and do arbitrary precision stuff but it seems we can no longer compile unless Real == double or float +--- Day changed Wed Sep 03 2014 +17:26 < matches> It would seem Mr Munroe has beaten us... +17:28 < matches> In Javascript +17:28 < matches> We should die of shame +17:29 < matches> Hahaha +17:29 < matches> "// there is no elegance here. only sleep deprivation and regret" +17:31 < matches> On the bright side, we now have a reason to reference xkcd +17:31 < matches> I guess? +17:59 < sulix> I just saw that, and had planned to use that comment as my next commit message. +--- Day changed Thu Sep 04 2014 +10:59 * sulix sulix also engages panic mode. +11:00 * sulix apparently also needs to engage sleep mode. +11:00 * sulix almost engaged sheep mode by mistake. +11:49 < sulix> How sure are you that SolveCubic works? +18:37 < matches> Well, sure within 1e-4 +19:40 < matches> Rational compiles again +19:41 < matches> It just takes... several minutes... to load "The quick brown fox jumps over the lazy dog" +21:04 < matches> I have a new ingenius plan +21:06 < matches> This will probably not work but hopefully it won't take me too long... +21:06 < matches> Oh dear what am I saying +21:06 < matches> It's going to take a month now +22:24 < matches> I really should be integrating one of those two libraries Rowan suggested into the project +22:24 < matches> As opposed to implementing what I like to call the "Paranoid Number" +22:25 < matches> It starts as a float +22:25 < matches> It checks each operation for an exception, and if it does it adds the operation to a linked list instead +22:25 < matches> After trying to simplify the next elements in the list +22:26 < matches> This is going to be awful +22:26 < matches> But it's been a while since I wrote a good linked list +22:32 < matches> ... I think the last linked list I wrote had a nasty tendency to randomly segfault... +22:32 < matches> Nevertheless we shall forge ahead +23:14 < matches> You know you haven't had enough sleep when you start to terminate lines with ':' instead of ';' +23:14 < matches> I blame python +23:14 < matches> Not that it was valid python syntax either +23:15 < matches> But it's a good scapesnake +23:42 < matches> Oh recursive list based functions +23:42 < matches> How I have missed you +23:42 < matches> void Foo() {if (m_next != NULL) m_next->Foo();} +23:42 < matches> <3 +--- Day changed Fri Sep 05 2014 +09:26 < matches> It sort of kind of works +09:26 < matches> Except when it breaks +09:26 < matches> ParanoidNumber::Simplify needs improvement +09:26 < matches> Also operator+= +09:26 < matches> operator-= +09:26 < matches> operator*= +09:26 < matches> and operator/= +09:26 < matches> But it's definitely a number +09:27 < matches> It just occasionally does things in totally the wrong order' +09:28 < matches> So basically the idea is if you have an inexact (or overflow/underflow) operation, you delay it, and then in theory you can rearrange the operations so you have a smaller error... +09:28 < matches> It seems to give better results than floats for tests/paranoidcalculator +09:29 < matches> But that might be because it is initialised off 3/10 and the float starts at 0.3 +09:30 < matches> It could all be totally useless +09:30 < matches> It probably is totally useless +09:31 < matches> I have a hunch that even if it's terrible it might beat true arbitrary precision arithmetic +09:31 < matches> In terms of actually being able to use it +09:31 < matches> Who needs mathematics when you have blind intuition... +--- Day changed Sun Sep 07 2014 +11:37 < sulix> Explicit mentions of hitting floating point precision issues in the xkcd comic: http://chromakode.com/post/notes-on-xkcd-pixels +17:33 -!- unmercifulfish [unmercifulf@motsugo.ucc.gu.uwa.edu.au] has joined #ipdf +17:33 < unmercifulfish> mwahahaha +17:34 < unmercifulfish> you can't escape my stalkerish tendencies now