A brief respite to wish a happy birthday
Before the day is totally gone, I wanted to take a moment to catch my breath and wish a Happy Birthday to kasheesty I hope you had a wonderful day and the year to follow is full of the best that Life has to offer.
Other than that, it has been another week of fun filled Carnival Cruise adventures. I had a course that was supposed to be three hour long sessions onboard for incident investigations. However, I missed the second session of the "TOP SET Incident Investigation" course because my hour long teleconference took nearly 2 hours instead. That has pretty much been the story of my week, everything has taken about twice as long as it should have. I also got to have a telephone conversation with my boss about a personnel issue among members of my team on the opposite rotation from me. (I am still trying to get my head around how to manage a team remotely that I may get to see for a couple of hours every 5 weeks.) I may get to call into another teleconference on Wednesday about that, but won't know if it is considered a good idea by the HR people in Houston until tomorrow. In addition, I should be preparing a shipment, sorting out whether I have to go to the Rio office after crew change, along with about 42 other reports which need writing (or at least starting in one case).
On top of all that, the techno-geek software issue I mentioned recently has turned out to be a combination of hardware and software issue. Much of today was a case of letting the computer run down until we could bring it down and then have a hardware guy remotely double the amount of swap space available on each of the blades. As it turns out, doubling the swap space was not enough for optimum efficiency for the processing step in question, but at least it helps some for other jobs which can now be run on the same blade. *knocking seriously on the wood of my desk!*
Also during the week, we had a serious "Oh Shit!" crop up with some data I had already shipped to the client. Even though the processing step had been checked onboard, in the office and even by the client before I started production processing for the data tapes I sent off, it wasn't until after the supervisor onshore had told the shipping guy in the office to send the data to the client that he thought about how we were writing some header words to the tapes we sent. As it turns out, the same header information was overlooked by myself, the supervisor and even the client who had come to the office to review the data format. What are the odds, that all three of us would have tunnel vision over the same issue???
So now besides having to redo all of that data which had already been run, we are having a continuous battle with the amount of data to be processed versus the amount of diskspace upon which to keep the processed data. This has been such an issue that the qc chief geo even sent a mail to some of the corporate heavy weights that even though we have sacrificed 4 terabytes of our disk system to the data that they are writing for our follow on processing, we were causing delays in their production! Of course of the acquisition plan was more in keeping with what we need for the processing, we would not be running at 80-90% of our capacity all of the time and having to remove data to make room for new acquisition and then have to restore what was removed once we have enough coverage to go on to our next step in the processing. Oh well, I guess if this job were easy anybody could do it!
Oh well, time to get back to fire fighting, or head off to bed, I am not sure which has the higher priority at the moment.
Other than that, it has been another week of fun filled Carnival Cruise adventures. I had a course that was supposed to be three hour long sessions onboard for incident investigations. However, I missed the second session of the "TOP SET Incident Investigation" course because my hour long teleconference took nearly 2 hours instead. That has pretty much been the story of my week, everything has taken about twice as long as it should have. I also got to have a telephone conversation with my boss about a personnel issue among members of my team on the opposite rotation from me. (I am still trying to get my head around how to manage a team remotely that I may get to see for a couple of hours every 5 weeks.) I may get to call into another teleconference on Wednesday about that, but won't know if it is considered a good idea by the HR people in Houston until tomorrow. In addition, I should be preparing a shipment, sorting out whether I have to go to the Rio office after crew change, along with about 42 other reports which need writing (or at least starting in one case).
On top of all that, the techno-geek software issue I mentioned recently has turned out to be a combination of hardware and software issue. Much of today was a case of letting the computer run down until we could bring it down and then have a hardware guy remotely double the amount of swap space available on each of the blades. As it turns out, doubling the swap space was not enough for optimum efficiency for the processing step in question, but at least it helps some for other jobs which can now be run on the same blade. *knocking seriously on the wood of my desk!*
Also during the week, we had a serious "Oh Shit!" crop up with some data I had already shipped to the client. Even though the processing step had been checked onboard, in the office and even by the client before I started production processing for the data tapes I sent off, it wasn't until after the supervisor onshore had told the shipping guy in the office to send the data to the client that he thought about how we were writing some header words to the tapes we sent. As it turns out, the same header information was overlooked by myself, the supervisor and even the client who had come to the office to review the data format. What are the odds, that all three of us would have tunnel vision over the same issue???
So now besides having to redo all of that data which had already been run, we are having a continuous battle with the amount of data to be processed versus the amount of diskspace upon which to keep the processed data. This has been such an issue that the qc chief geo even sent a mail to some of the corporate heavy weights that even though we have sacrificed 4 terabytes of our disk system to the data that they are writing for our follow on processing, we were causing delays in their production! Of course of the acquisition plan was more in keeping with what we need for the processing, we would not be running at 80-90% of our capacity all of the time and having to remove data to make room for new acquisition and then have to restore what was removed once we have enough coverage to go on to our next step in the processing. Oh well, I guess if this job were easy anybody could do it!
Oh well, time to get back to fire fighting, or head off to bed, I am not sure which has the higher priority at the moment.