I have wanted to do this for ages, but most of what's back there belongs to the tall one...so I couldn't easily just go through and toss everything.
We cleaned about half, and there's actual floor space? Not used to that. The trash guys are going to hate us on Thursday.
Next up, the second half of the back porch, relocation of the litterbox, and demo can begin. He has aspirations, I just hope we can figure it out well enough to succeed in doing a decent job.
Hoping to be out in a year. Fingers crossed.
I left the project half-finished last night, intending to fill the radiator with the water that had been lost in pulling out the water temperature sensor. This morning I got up, intending to drive the Spitfire over to the Annual Little British Car Show, poured a bunch of water in, and watched it cascade out of the sensor recess. Tightening the nutbolt (a bolt with a hole through the center that the sensor lives in) down didn't help. I drove my normal car over, checked out some pretty cars, and drove back, and then removed the sensor and started poking at it. Halfway up the bulb that lives in the water, there's a tapered ring of metal. I thought it was a precision tapered ring, that sealed against the matching taper inside the water pump. But this is automotive: there is nothing precision outside of the innards of the engine and transmission. Instead there was secretly a rubber gasket that, when I removed the old sensor, had stayed inside the water pump housing. It was totally shot, and no amount of trying to carefully put it back in was going to save it. I ended up getting an o-ring from my collection of high temperature water-resistant o-rings and using that instead, but because it was smaller, the nutbolt no longer managed to press the sensor down well enough to seal. I had to cut a little collet on the lathe, like a thick washer but sawed in half so it could be put in two pieces around the sensor line. With that, everything sealed correctly, as far as I can tell, and the car is ready to go again. A quick jaunt around the block shows the water temperature gauge indicating roughly the right numbers. I'll check tonight to see if the radiator is full of water.
Yesterday I spent about five hours painting the house, getting a layer or two of exterior paint on all the sun-facing wood on the first floor, and getting a good start on the non-sun-facing wood. Today I'll get the small amount of wood on the second floor. Man this is sore work, all above my head, a lot of it from a ladder, but it should last several years and more importantly prevent the wood being damaged by being exposed, as it was. Looks a lot better, too, than all the flaking and peeling paint that had been there since we moved in.
There are two low blips where we stopped for stoplights, and a high point where my heart got up to 185 or so, but the rest is a nice solid consistent 160-ish, the rate I can maintain for an hour without throwing up.
It was also quite warm today, just about body temp.
The result was that when we got back, everyone showered and ate and then we had a staff meeting and at the end of the staff meeting, when the department manager stood up and said "thanks, everyone", and the rest of us all stood up, I promptly put my back against a wall and slid down it to a seated position, my manager fell over and landed halfway in a chair, and the other manager, who had been drafting me, just had to sit right back down and put his head down on the table.
So it's not just me.
Department manager was all "what are you guys DOING out there?"
Afterwards my coworker came in and nearly melted down, because he is unusually averse to change, and I'm putting vast quantities of change on the table: new software, new hardware interface, new instrumentation, new system for extracting data and manipulating it, I'm using parallel processing and calling modules I've precompiled in a different language. A lot of that I'm doing A: to see if it works and B: to see if it's worth the bother, not because I have to, but he sees this as an onslaught.
Aside: labview is a whackadoodle language. To call a subroutine, you drag the subroutine icon into your work window. There is a C-style header, with C-style parameters, that you can go find in a header file if you want to, but the way you actually handle that is you draw lines from the main program's output terminals on the main program box to the input terminals on your subroutine. If you're passing an array, it's a dotted green line. If you're passing a double, it's a pink line. If you're passing a signed/unsigned 8 or 16 bit integer it's a blue line. Terminals have to match lines, have to match terminals on the other end. You can t them, as well. Some parts are really obscure. A while loop is a box, with a terminal into which you feed an unsigned integer, to determine the number of iterations, and another terminal into which you feed whatever it is that the while loop is supposed to do. But you can also click on the point at which that line enters the while box, and hey presto suddenly it's a shift register instead of a while loop. ??!? Coz that makes sense, and is really easy to debug when you're looking at the program later.
And, excitingly, everything is pass-by-reference, so it's really easy to completely muck up a datastream if you're trying to just, say, increment a value every time you get a good reading, and inject a bunch of trash into your data. But it does let you return an arbitrary number of values from a function call without having to use pointers to structs, so that's kinda nice, I guess.
So today we went on a bike ride at lunch and when we got back my manager sent out a meeting invite to pretty much everyone in the building, with ten minutes of notice, to look at my project.
Luckily I hadn't broken it down.
But man that's not a lot of time to prepare for a raft of technical questions. It's a good thing I'm a loudmouth.
It went really well. I managed to field all the questions successfully. One coworker wanted to know if he could integrate what I was doing into matlab. Another had a bunch of questions about hardware parallelizing. I could see my poor coworker, the one averse to change, winding himself up into enough tension that he was bouncing both legs up and down uncontrollably, his stress tell. Afterwards he had *pages* of questions about the questions other people were asking. He really needs a more deterministic job.
Everybody liked it.
They're going to like it a lot more when I have a demo system ready to talk to new silicon the moment it comes through the door, while our applications software guy gets called off on other emergencies and won't have even a cursory interface ready for two weeks after we get new silicon, as happened the last two times. I'm trying to get our digital designer to give me a (FPGA-based) hardware simulator for the chip, so I can actually try out some more complex stuff before the new chip's anywhere close to coming back, but apparently his hardware simulation doesn't actually work like that.