Archive for the ‘Navy’ Category

Akademy night

August 7th 2008

I just wanted to say hi to everyone going to Akademy. I once again cannot go this year but I figured to compensate I’d regale you with a story from my Officer Candidate School days.

This is a War Spoon

This is a War Spoon

Plate of spaghetti

This is a plate of spaghetti

When I first got to OCS, my eating habits were, uh, modified (to say the least) by the Officer Candidate Regulations manual. Instead of being able to eat food with a knife and a fork, I, as a newly minted worse-than-dirt OC got a spoon to eat with. The spoon was used to eat everything.

It was not sufficient that the spoon was the only utensil you had either. As an Officer-in-training you were not allowed to do anything as barbaric as pick up your food with your fingers. In fact you had a regimented, easy-to-follow 8-step procedure for eating. They called it eating-by-numbers.

So how does spaghetti tie in? Well, at every trip to the chow hall, spaghetti was an option on the menu (except for breakfast). Didn’t like mystery meat with noodles jefferson? Just get spaghetti. Get it every meal if you want. I wasn’t sure why the mess cooks liked spaghetti so much, but I wasn’t complaining. I love spaghetti. I even loved spaghetti by the end of OCS, wasn’t tired of it one bit.

But… how do you eat spaghetti with a war spoon? Well, the secret is that you cannot twirl your spaghetti into a bundle on your spoon and eat it as if you were using a fork. If you were to try to you’d make a mess everywhere (and thereby risk drawing attention to yourself). Even worse, it would be hard to actually eat all of the spaghetti without having to slurp any into your mouth. This definitely draws attention from the roving Class Drill Instructors. Officer Candidates do not like attention from Class Drill Instructors.

Instead learn to use what you have. With a war spoon, you simply have to use the edge of the spoon to cut the spaghetti into bite-sized pieces. Basically you use it like you’d cut a piece of pie out of a pan. It takes less time than you think once you get good at it. After a couple of days of practice you’ll be able to actually eat more spaghetti than you were able to before in a given amount of time.

At about week 4 or so we had our forks given back to us. How did I eat my spaghetti? With a war spoon, of course. Time is still precious, and you can fit more spaghetti onto a war spoon than onto a fork even if you use the pie-cutter technique.

To this day I still eat my spaghetti by the pie-cutter method instead of twirling. I use a fork now though, no reason not to be civilized. ;)

Posted by mpyne under Navy & Personal | 2 Comments »

Go me

July 17th 2008

So I just returned from a trip to Washington, D.C.

The trip was the culmination of about 8 weeks of study for the series of exam and interviews required to graduate the Navy Prospective Nuclear Engineer Officer (PNEO) curriculum. You basically take all the stuff that you already know about the plant from having operated on it, and then go and really dig into how everything really works. It’s not good enough to know that a procedure tells you to do something in the event of a casualty. You have to know why the procedure is written that way (i.e. what do these steps prevent, what could go wrong if you don’t do the procedure right?). It’s not always about operations either, almost more important is learning about the various maintenance responsibilities that way when you’re the guy actually responsible for supervising the entire department’s maintenance schedule you’ll understand what’s coming across your desk.

After passing a comprehensive written exam a student is sent to Washington D.C. to interview with the smart guys at Naval Reactors to judge your worthiness to be the Engineer Officer. If you also pass that screening then you’re done, if not you get to try again (up to a finite number of times).

It sounds demanding (and it is) but most people put in the time and effort required to make it so most people generally pass, even if it takes a second attempt. But it’s nice to have it knocked out of the way early, especially since in my case my command had to get a waiver approved for me to go earlier than normal. Had I not qualified we would only have 1 Engineer-qualified division officer on the boat which we try to avoid. :)

Posted by mpyne under Navy & Personal | 1 Comment »

Usability in interfaces

May 17th 2008

So on Planet KDE there is a bit of discussion regarding usability, discussion brought on by an article on a programming weblog.

The topic of the article was a group that decided to make a copy of Pidgin, the most popular open-source instant messenger. The copy is called Funpidgin and was essentially created because the people making the copy feel the Pidgin development team are not listening to the needs of their users.

Celeste Lyn Paul, one of the KDE team’s usability designers (the group that tries to make the software we make actually usable by the end user) noted that the Funpidgin project needed to be careful with how much they allow the user crowd to drive the direction of the project.

Derek Kite made a comment about the amount of issues that people bring in the name of usability. He then later posted a followup where he says that usability is fine to get inexperienced users acting but tools for more advanced tasks are usable because they work, and that those tools with usability design are usually not useful at all because they are designed by those who don’t use them. i.e. the user would be the best designer.

I don’t disagree but I have an alternate viewpoint based on some of my experience operating two of the most advanced “tools” in the world, nuclear reactor plants:

I first qualified on the S5W nuclear reactor plant. This plant was very old by the time I qualified on it (MTS-626, used to be SSBN-626 U.S.S. Daniel Webster, commissioned April 1964). It was also very well understood, tried and true. The plant I’m currently qualified on, S8G was a quantum leap above. Many things I used to have to verify were done were either not required or performed automatically. The capabilities were more impressive, the plant design was easier to understand. It was better in most every respect, as it should have been, what with all the operational experience the designers were able to integrate from S5W and later plants. Neither of those two plants however, were designed by it users, the nuclear operators and supervisors.

Now, the users of these plants were certainly involved in the design of the follow-on plant. It would be foolish not to get the input and experience of the people who actually use the plant which you design. But the design is still left to the smart guys at Naval Reactors and their contractors. I’m not kidding about smart either. It seems like at least once a week either by looking around or digging in the books that I’ll notice something which had to be designed in to solve or prevent a problem. Even as much as the operators understand the plant, their knowledge is dwarfed by the designers and engineering who designed and maintain (but don’t actually operate) the plant.

Users have only their own experience, however great. By leaving the design to other engineers, who have access to many users and their own expertise, Naval Reactors is able to use that big picture view to develop better designs, which future generations of operators will be able to use. In much the same way, software designers need to use the input of the users of their programs to develop better programs. But completely user-driven design can be hazardous. Different users want different things, sometimes with conflicting demands.

For example, there is a performance issue in KDE (and now in Firefox) due to the fsync() and fdatasync() system calls. Those calls are there to prevent data corruption. Some users aware of the issue disable those system calls (and thereby risk data corruption in the event of a computer crash) in order to increase performance. You can’t make both users who demand performance and users who demand data integrity happy in instances like these. Well, you could perhaps add a checkbox… ;)

You can’t always just add an option though, and sometimes you can’t make everyone happy. That doesn’t mean you shouldn’t base your work off user feedback though! Just as the designer may have the overall big picture view, the users will see things in actual use that the designer would not have thought of, either actual bugs or better ways to do things. This, in my opinion, is the process of usability. The work and value of the actual usability experts shouldn’t be diminished just because of people who make bad suggestions in the name of usability. I’ve seen quite a few programs noticeably improve after a usability review with no loss in functionality. (Edited 18 May to fix spelling)

Posted by mpyne under KDE & Navy & Personal | 3 Comments »

Qualified in submarines

December 18th 2007

So yesterday I completed my submarine officer qualification board. Today I had my dolphins pinned on me by my wife. It’s different having them on, I’m still not really sure what to make of it. For better or for worse you’re looked at differently by submariners if you are qualified in submarines. Unlike many other badges and awards you may encounter this one is still generally awarded only to those who deserve it and have completed all the applicable requirements.

In my case due to circumstances I had a patrol pin with 2 gold stars (indicating 3 alert deterrent patrols) without dolphins. Normally this is the sign of a junior officer who does not have the trust of his captain as you typically get dolphins after your second patrol. In my case the pin and first star were for half patrols, but it’s nice going from dirtbag to experienced junior officer in 15 short minutes this afternoon.

While researching this entry I came across a letter from an SSBN commanding officer briefly describing what it’s like to serve on an SSBN, which I thought was pretty good. You can read it at http://www.news.navy.mil/navydata/cno/n87/usw/issue_5/confessions.html if you’re interested.

Posted by mpyne under Navy & Personal | 10 Comments »

The USS Hampton

October 26th 2007

I’m sure many have seen the news about the nuclear fast attack submarine, USS Hampton, which has had its operations suspended due to failing to perform required inspections, and then trying to fake the required paperwork later.

We had heard inklings of what happened before it hit the news, so I knew that the media coverage of the story was predicably inaccurate but nothing too bad. But then I saw what may have been the stupidest blog post ever about it. Their description? “USS Hampton Submarine Crew Fails To Read Meter, Fakes Logbook, As Fluid That Keeps Reactor From Going Critical Runs Low”.

They then go on to talk about some magical ingredient that submarine nuclear reactors have that keeps the reactor from going critical which must be constantly maintained and which this crew was not doing. Then they accuse the Navy PAO who said that there was never a threat to the public or crew of a “Flat-out fucking lie”.

Unfortunately reality has a funny way of interposing. First off, though this may surprise people, the reactor is pretty much always critical while underway. This may be deduced from the definition of criticality: “2. Physics The point at which a nuclear reaction is self-sustaining.”

Even going by what I assume they mean by critical (i.e. chain reaction going out of control) the chemistry levels couldn’t cause that. Pretty much everything dealing with the actual operation of a naval nuclear power plant is classified CONFIDENTIAL but the fact that we use Pressurized Water Reactors is public knowledge, and Wikipedia has a good article on their operation. I’d like to point out the section dealing with control of reactor power: “Generally, reactor power can be viewed as following steam (turbine) demand”, and “Boron and control rods are used to maintain primary system temperature at the desired point.”. In other words, reactor power depends on the system demand (it automatically rises and falls as necessary), while control rods control temperature. What about boron, you ask? The article answers it in the last sentence of that section: “Due to design and fuel enrichment differences, naval nuclear reactors do not use boric acid.”

Notice nothing of that (besides boron, which I’ve covered) deals with chemicals. We do add chemicals to the water, obviously. But not for control of power. The author of the story I linked to then goes on to say that failure to maintain levels of this magical substance will cause alarms going off, and then “everyone becoming radioactive and the ship sinking.” Which is just so funny that I actually laughed at first until I realized he was serious.

He then says that it’s easy to measure the level, i.e. you just read a meter. That’s unfortunately not the case. It may be on civilian plants but monitoring chemistry levels on the submarine involves (at the very least) drawing a sample of water to perform the analyses on in the first place, which is rather involved due to the fact that the water is radioactive to at least some degree and therefore radiological controls are required during the entire sampling and analysis process.

He then compares adding more chemicals to maintaining the oil levels in your car. I don’t know how his car operates, but with mine I can just unscrew the lid, pour in a quart, and screw the lid back on. You can’t just “unscrew” a cap off of a very highly pressurized primary coolant system and pour some chemicals in. It’s not super hard but it is an involved process.

Next up: “This is in the course, mind you, of a 12 hour daily shift, most of which you spend, in the normal course of activities, bored. Having something to do is good.” To which all I can say is that the author has obviously never been underway. Between training, drills, monitored evolution periods, actual mission operations, cleaning, and qualifying it’s hard enough to find time to sleep. And it’s not a 12-hour shift, it’s (in theory) 6 hours of watch, 6 hours of maintenance/training/other work and 6 hours of off time in an 18-hour day.

Finally the author says that this is the very last bit of maintenance you would want to mess up and then calls the workers in “the reactor room” a bunch of “complete fuckups”. I can think of at least 3 maintenance items right off the top of my head that would be much more horrifying to “gaff off” and I’m sure there’s dozens more that more directly impact reactor safety. And there is no reactor room, and not every nuclear-trained worker was complicit, and the fact of the matter is that we don’t know what happened to cause this (the Commanding Officer has just been relieved of command however).

This is not to try and fluff off what happened (missing chemistry analyses is a *big* deal to Naval Reactors). I would like to think that the whole division did not ignore daily samples for a month (as this would involve not only the RL division in question but also all of the EOOWs and EWSs who had stood watch over that time) but instead had forgotten some sort of non-daily sample. But until more information is released about what exactly the Hampton did wrong it’s way too early to start calling the hardest-working department on a submarine a “complete fuckup”.

Planet KDE readers: I tried to include something relevant to KDE but I have no nifty unfinished work laying around at this time. :-(.

I realize that there is often confusion about how nuclear power works so if anyone has any questions feel free to ask in the comments section but if I’m vague at all (or just refer you to relevant Wikipedia entries) just realize that I have confidentiality standards I have to maintain.

Posted by mpyne under Navy | 12 Comments »

Wheee

July 25th 2007

I’ll be gone for some weeks. (Actually I’ve already been gone by the time you read this :)

Because of this I obviously won’t be responding to emails or phone calls, fixing bugs, releasing new versions of software or anything else I’m normally around for. I normally manually approve of all comments to the weblog and I still get to much spam to change that policy so I apologize but comments will probably be disabled while I’m away.

In the meantime I hope everyone stays safe, and I’ll see you when I return.

Posted by mpyne under Navy & Personal | Comments Off

I can’t think of a good title

May 22nd 2007

But two relatively big events happened over the past week. This past Friday I was promoted to Lieutenant, Junior Grade. And today I finally qualified as Engineering Officer of the Watch and Engineering Duty Officer (on the same board no less). So now I just have like a million more qualifications until I get qualifed as a Submarine Warfare Officer.

On a more humorous note a submarine sailor (currently working as a recruiter) is making a series of animated short videos which are similar to submarine life. A lot of them require some kind of knowledge of the Navy to get the most out of it but then a lot are quite funny on their own as well. He has the videos at his studio site, TubeDaze.

Posted by mpyne under Navy & Personal | 1 Comment »

kdesvn-build 1.4

May 3rd 2007

I’ve released kdesvn-build 1.4 just now. It includes a couple of minor bugfixes, the default options and modules have been revised, and now kdesvn-build supports using the KDE FTP Subversion nightly snapshots when checking out trunk KDE modules. (Thanks to dirk for fixing the FTP mirror script to support kdesvn-build).

In other news I’m back from riding with a different boat to augment my qualifications since I was let off of my last patrol early due to my son being born premature. I ended up going back to work basically as soon as I got back so I’m still catching up on my TODO list (both work and home) but things are progressing.

But anyways, it’s 2 hours past my bedtime so I’m off. :)

Posted by mpyne under KDE & kdesvn-build & Navy | No Comments »

Update update

November 2nd 2006

This has been a really busy two weeks for me. One thing I’ve noticed is that all through the Navy training pipeline, the message has always been, “Oh, it’ll be better at the next command.” But the only time that was true was during OCS (i.e. boot camp).

I went next to Power School, which was hard but was really pretty easy compared with the next stop, Prototype, where I was always busy and being run ragged with studying and trying to get people to sign qualifications off. Now on the boat I am, if anything, even busier. I’m almost looking forward to going to sea because of it. After all, I haven’t been able to do much with my programming, can’t spend time with my wife, and I never get enough sleep. No wonder the Nukes make so much money, because I can’t find any junior officers who are stoked about signing up for more time in the Navy. ;-)

I bought an iPod for the upcoming patrol. The iPod Nano isn’t horribly well supported but the latest gtkpod (with libgpod) program seems to work well enough most of the time. What I need to do when I get back is see if I can hack in iPod support to JuK in some kind of sane fashion. Beyond that though, the iPod itself is as nice as people claim, very easy to use and no detail left unconsidered, not even the packaging.

Adriaan blogged the other day about how he setup a aggregator for the KDE blogs that actually deal mostly with technical talk. I noticed mine’s not on there, and why not? I haven’t published anything that wasn’t whining about politics or how busy I’ve been in a long time. It’s a pity too, as one reason I’d been working so hard on programming during Power School and the beginning of Prototype was so that I could have an alternative to the Navy when it comes time to decide whether to leave the Navy or sign up for another tour. There’s always the off-crew periods where I’ll hopefully be able to focus on getting my hobbies done, but failing that it almost seems as if I won’t have time until my shore duty comes around in a couple of years.

I may not post again for awhile, but rest assured I haven’t left permanently. I’ll just have to find time somehow. :)

Posted by mpyne under Navy & Personal | No Comments »

I lost the power

October 15th 2006

I encountered perhaps the weirdest issues I’ve had with electrical service in my life yesterday.

Yesterday morning I was woken up by the sound of the battery-backed power supply for the computer beeping, indicating that it was running off of battery power. But then it would stop beeping and return to normal. At first I thought that the power supply was failing so I turned off the computer and unplugged the power supply.

Since I was up I went to the bathroom and turned on the light, and noticed that the light was flickering. In fact, every light in the apartment that I tried was flickering. So what was apparently happening to the power supply was that the voltage being supplied to the house was fluctuating, and the power supply was having to rapidly cycle being suppling battery power and using the main apartment power.

The power eventually went out just before I left for work, and when I came back a couple of hours later, things had been restored.

So, OK, just some sort of weird hiccup in the grid, which the power company would repair and that would be that, right? Nope. :-) The same problem kept repeating throughout the day. My wife and I left to run errands and when we came back it looked like the power was out again. Luckily I checked the circuit breaker, because it turned out that another power fluctuation had caused it to trip, but power had already been restored. That was the only other time we lost power, but it continued to fluctuate throughout the day and night.

Today we haven’t had any problems with the power, luckily. I’m hoping the power company has figured out whatever the hiccup was.

I get to leave soon for my first patrol with my ship. I have to say that the engine room (and basically the entire boat) is much much bigger than the one I qualified on at Prototype. :-) On my first patrol I’ll have to qualify for a few watchstations, including the ever-important Engineering Officer of the Watch. Unfortunately those who are not qualified are pretty much expected not to take up too much rest time so I guess I won’t need to pack my computer or any movies.

Posted by mpyne under Navy & Personal | 2 Comments »

« Prev - Next »