I just growled at my computer. Didn't actually realize I was doing it until I was already growling. Stupid client and his stupid typos and stupid stupid stupid! Gah! How am I supposed to analyze numerical data when it's riddled with typos?
I know Perl, at least the basics. It's entirely unhelpful here. These errors are pretty damn creative, really. It's to the point that I can't farm it out to one of the data processors - most of this stuff is only fixable on a case by case basis. That is, I can look at the data myself and I can generally tell what it's supposed to be, but it's not anything I can think of actual guidelines for. Just a year's worth of experience.
But unfortunately, it's only really practical to look at the data in the right way if I get an error message. Which may or may not come up. Basically, I think I've found most of the implausible errors. But none of the plausible ones. And some of the implausible ones keep coming up...
no subject
Date: 2006-07-25 08:56 pm (UTC)From:But unfortunately, it's only really practical to look at the data in the right way if I get an error message. Which may or may not come up. Basically, I think I've found most of the implausible errors. But none of the plausible ones. And some of the implausible ones keep coming up...