"observing"

So I'm still waiting for my code to crash. This is mostly a good sign, as it is mostly working for this set of data, but I really trying to get it to work on another set of data. But I'm running it on the data it should already run on to try to figure out why it isn't running on the new data. But there is a lot of old data . . . .

I'm actually on the mountain "observing." Well, not observing yet but commissioning the instruments so that in the near future someone can observe. But I'm not really doing that either. While I might do some "observing," I've learned that an "observing run" is code for getting you to work a lot because you are there for 16 hours/day with no home to go to. I thought having dinner at 8 pm was odd until I realized that was still at least 4 hours until bedtime. So after midnight sometime we stop, go back to our room to sleep, and then come back in the morning to start all over again.

While the hours are long, it is also rather productive to be around the other people involved in the project, because they are experts in various parts of it all--including the code I am trying to debug. Or at least a similar piece of code that they were tasked with debugging. So I think that is most of the idea behind the "observing" run.