i was at work until 7:00 last night. then i transferred the matlab script to my home computer, and worked on it for another 3 hours here at home, and i will probably finish it up with an hour today. i know, i know. leave work at work.
but i couldn’t. you ever get on a roll? i was on a roll with this crossrange script, and with the weekend coming, i knew if i dropped things for two days, i’d never be able to remember exactly where i was or what i was thinking my next step should be. so i worked on it at home.
the good news is that i added the thing to the script that gavin wanted. the bad news is that in going through the structure of the script (since i wasn’t the one who wrote it), i’m 99% sure that i’ve discovered an error in the way it has been calculating crossrange for the entire 5 weeks since columbia that we’ve been using it. an error that doesn’t cause hugely significant amounts of wrong-ness, but an error that does need to be fixed and will have a slight effect on everything we’ve done up to this point.
ugh. i’m going to have to tell the coder that it is wrong. i don’t really want to, because i’m afraid he’ll think i was second-guessing his ability to do the work.
well, that’s that.
