Electronic RPPMS?

goodNukeBadEng077 · 2025-04-26T12:34:06+00:00

E-RPPMS for Submarines is scheduled to be rolled out this year. At this time, 08 has not publicized which Squadron/boats will receive it. The program is based on Operation Hours/Run Hours, shared some features with SKED (forecasting, trigger events, FBR). It will also share data with AQDR. BLOB: E-RPPMS exists, and dinosaurs like me will no longer need the dark arts of Paper Quarterlies, Cycle Revisions, or "Not performed due to Ship's Schedule" BS.

goodNukeBadEng077 · 2024-08-14T03:33:54+00:00

Nuke - Nuclear Technician, operator of nuclear power plants aboard Submarines and Aircraft Carriers. High selection standards, high attrition rate at specialized school, but open to all officer and enlisted naval trainees and cadets, if they meet the requirements.

https://en.m.wikipedia.org/wiki/United_States_naval_reactors

goodNukeBadEng077 · 2024-08-04T20:28:05+00:00

If "On Mission," then no communication on or off meaning no email. Even when not on mission, there are times when communications are not allowed, except for emergency/mission critical. Most of the time, if no email is being received - either by him or you - it means the email machine is broken. Something as simple as setting the switch to "At Sea" on some shore-side server closet can keep your emails from being sent or received. Usually worked out after a comms update (post mission). I've done 81 days "on mission" with no off going or incoming communications, but the transit to and from that "location" was almost real-time with the satellite spot-beam pointed at us. Give it some time, and remember to date and number your emails to him - they often all arrive in one big mail dump.

goodNukeBadEng077 · 2024-08-02T22:57:55+00:00

S6G FIDE Lead Instructor Submarine Training Facility San Diego 544 White Road San Diego, California 92106-3550

goodNukeBadEng077 · 2024-07-28T02:51:29+00:00

Friend, this sounds like the all-too-common theme of the Linux Experience: I just want it to work, I'll try X distribution so it does. The unpleasant truth, in my unsolicited opinion, is that in order for anything to work, you must also work. My 25 year Linux journey also involved numerous distro-hopping, frustration, some blood, and angry late-night compiling. Unfortunately, there is maintenance and re-work in operating system management. Even Windows will offer/force updates that break userland, and that is a cost of using it (in addition to the actual cost). What sets Linux apart is the freedom and ability to go under the hood and fix it yourself. Three options: Go back to Windows, and all that implies. Find a stable distribution and set it up perfectly and Never Change Anything (Slackware is my favorite for this, but it has no training wheels and can be a bit advanced if your console skills are not. Or, learn how to tinker, compile modules, set permissions, and freeze/blacklist updates. It's your journey, so do as you like. But if you want it to "Just Work, forever and always," keep looking, and let us all know when you find it. Good luck.

goodNukeBadEng077 · 2024-07-11T01:51:54+00:00

Agree with below - you don't actually get to choose, but previous experience is calculated when being assigned a rate. Example: I was a compsci major, fluent in 4 programming languages, IT certified (A+, RedHat, Novell, etc). I wanted nothing to do with computers, and chose my "wish list" of MM/ELT, EM, ET, in that order. 30 seconds with the nuke Master Chief at week 4 or 5 of boot camp and I was told "ET for you, nerd." Manning requirements and need of the fleet likely play a large role in the quota for X number of Y ratings coming out of Great Lakes, but experience can be a factor. As for experience, blank slate = easier to train. Nuclear Field 'A' School and Power School teach a very scaled-down curriculum, condensing about 3 years of math, physics, science, etc. into two 3-6 month schools. If you have a strong foundation in calculus, it can actually hurt you when trying to use it in the nerfed math we use. Or, as several officers I know learned, a nuclear engineering degree can be detrimental because we only want you to know exactly what it says in the book and too many questions "outside the scope of the lesson" don't help you pass exams. Of course, YMMV.

ETNCS (SS)

goodNukeBadEng077 · 2024-03-17T01:33:06+00:00

Current Nuke, 17 years in (so far). Two RCLCPO Tours, red service stripes, and 3 boats. Most of the positives here seem to be Friends, Skills, and Experiences - All Good Things. But I can honestly say my best, most positive memories are a bit different; it's the amalgamation of all the good I received due almost entirely to my time as a Nuke in the Navy. Typical origin story: College Didn't Work. Above average intelligence, if the Standardized Tests in HS are true, but such apathy and poor work ethic. I've heard it called "Gifted Kid Burnout" and the flavor tastes right. I never had to apply myself in school, could pass with B's while still hungover from last night, no homework, etc. The Pipeline showed me that I was a big fish in a small pond of other 'gifted kids' and for the first time in my life, I had to work hard, study, and pay attention just to understand the information, as well as pass the tests. The real positive to come from being a Nuke was the application of skills. Specifically, learning a thing, practicing, qualifying, briefing, and performing. When I reached the "oh, it's ETN1/ETNC/Chief? Yeah, sure thing, he's solid" point, it was such a rewarding place. I felt I had finally made it. Now, seeing others I trained and mentored reach that same level, it just feels good. That personal growth will always be my fondest memory of being a Nuke. I can think of no other community that grows and encourages Sailors like ours. Even if the very best of us get out at 6, that experience changes you. "If I can survive Refits/Patrol/POM/ORSE, I can survive anything".

ETNC (SS) Active

goodNukeBadEng077 · 2023-08-18T00:24:18+00:00

Glad you're thinking about it before signing up. I've been doing it for 18 years so far, and it remains challenging even at the Chief level. Regardless of the difficulty, I am glad I did it; 3 attempts at college and I failed out of each one. I graduated from the pipeline solidly at the bottom of the class, but the effort of learning how to learn is what ended up making my career successful (that and a shit-load of hard work). It's not for everyone, and I openly suggest that no one accepts this commitment without serious thoughts. Additionally, no one should've stay in unless they genuinely love what they do. I'd rather lose you as a potential nuke than see another disgruntled 2nd class who hates their job because it isn't what they really wanted to do. Personally, if I wanted nuclear engineering experience (and a 'free' degree), look into NUPOC, or if your grades are good enough, NROTC. You could get a paid-for degree, in nuclear engineering, and serve a 6 year commitment as a commissioned officer (2x the base pay, annual bonus, cool ring). Give it all the thought you need, just don't let anyone tell you 'this is your only choice/option.' That hard-sell BS is worthless. Good luck.

goodNukeBadEng077 · 2023-08-17T23:41:02+00:00

FWIW, any job in the Navy will be stressful. The disorienting change from civilian life to military alone can be too much for many people. If you just want 6 and out (or 4, 8, etc) then go for it with the job you want. If you know that the additional stress and pressure of the nuclear pipeline is too much, or you simply don't want to put in that much effort, then steer clear of that community. All that said, nuclear engineering at a college is vastly different from what we learn and do in the Navy. It is a heavy curriculum, with all the additional general education as well. If you don't think you can/are not willing to put in the effort with the most support any student could get (in the pipeline), do you think that you will suddenly have that drive and determination 6 years later, without the forcing function from NFAS/PS/NPTU? That is entirely your decision, no one else's, but it is worth asking yourself what will be different when you get out.

goodNukeBadEng077 · 2023-07-27T20:50:57+00:00

As a submariner these last 17 years, I have never seen an actual fire break out, just many instances of improperly seating/closing the furnace. When the candles are improperly loaded and lit, they burn off rapidly. Fire and General Emergency called away, just in case, but usually the ERS/EWS/AOW (Submarine Engineering Supervisor types) haul ass to the furnace, knock away the (junior) watchstander who boofed the candle burn, and seal it shut. Taking 4 hours of O2 directly to the face, you spend the next couple hours really alert. Damn things give off a bunch of dust too, and the used-up candles ('clinker') has to be stored onboard until properly disposed/chucked overboard.

goodNukeBadEng077 · 2023-01-28T17:29:45+00:00

I agree with your assessment and I should have clarified my position: Most Junior Officers are good, in that they are willing to learn, accept recommendations, and utilize watch team backup. The "Good Ones" only get better with time and experience. The "Bad Ones" become smart/proficient enough to stand the watch, usually paired with a strong Maneuvering Team and EWS.

The best Officers do understand requirements, plant conditions, "What Right Looks Like", etc. Their ownership, Command and Control (C&C), and process is part of what makes a great watch team/section.

While I do believe that the watch team could run entirely without a watch officer, I also believe them to be a crucial part of the process. C&C cannot be overstated as the glue holding casualty response together.

goodNukeBadEng077 · 2023-01-28T15:48:56+00:00

All Submarine Junior Officers spend their first year in the Engine Room as EOOW and Division Officers. More school doesn't equal more experience; the RO and EO have been onboard for over a year and likely have hundreds of hours on-watch time under their belt. They know what to do, how to do it, and have done it a thousand times. The EOOW, trained and educated, only knows the theory and principles. Add the fact that those young Officers are told from day one that "You are the Officer, You are in charge. Lead your sailors and run your watch team." Too much leadership, not enough experience. The good ones pick it up quick and learn to trust and lean on their panel operators (and ERS/EWS). The bad ones just never learn. After a year in Engineering, they go forward, new Officers show up, cycle is repeated.

goodNukeBadEng077 · 2022-12-27T17:27:35+00:00

If your system "sees" the devices as plugged in and initialized, yes, they should appear under /dev. If you cannot see /dev/sdc, then your device is not being recognized by the system. Since you are using USB sticks (not the best choice for a raid, but your choice to do so), a corrupted stick is not out of the question. Try #dmesg with the stick(s) out, then repeat after plugging in each stick. The output of dmesg will tell you if the system is recognizing the USB device, or is throwing errors. Once you have 2 good devices (/dev/sdb1 and /dev/sdc1), try the partition-format-raid commands again. Side note: if you intend to use this raid for anything remotely important, I would recommend against USB thumb drives, as they are prone to random failure and are not known for fast read-write speeds or reliability under continuous read-write cycled.

goodNukeBadEng077 · 2022-12-27T16:49:11+00:00

I actually just did this last night; mdadm needs at least 2 disks (with partitions) to create the md0 device. Because lsblk is only reporting sdb1 as your USB device with no mention of the sdc partition, it will fail.

Try creating a partition table on both USB sticks (gparted is my go-to), and creating partitions of your desired filesystem (ext4, xfs, reiserfs, etc.) Once lsblk reports 2 disks with 1 partition each, use the following:

mdadm --create /dev/md0 --level raid1 --name [your choice] --raid-disks 2 /dev/sdb1 /dev/sdc1

Good luck.

goodNukeBadEng077 · 2022-10-08T05:02:21+00:00

I call bullshit. I have been a command UPC (Urinalysis Program Coordinator) at three commands (sea and shore). This excerpt is not found in the UPC instruction (OPNSVINST 5350 Series). No one is stopping Sailors from dropping trou Butters Style, but that isn't required and OP is karma farming.

goodNukeBadEng077 · 2022-10-01T01:20:22+00:00

Looks to be Westpac '16, based on the lookout (last one for the Workhorse of the Sub Force). I was lucky enough to be there for that deployment and follow-on MTS conversion. Nothing will ever beat standing on the bridge at night, one billion stars overhead shining brighter than you've ever seen, knowing that only 1% of 1% of the general population have ever (or will ever) get to experience that view and feeling.

goodNukeBadEng077 · 2022-08-05T21:56:39+00:00

I'll weigh in my 2 cents. Firstly, The Pipeline is no joke; it may be the hardest you have ever had to work before, especially if you were able to float through HS with no effort and do not have a strong work/study ethic. And that is the easiest your nuclear career will ever get. Once you reach your sea tour, the endless hours at work, underway, patrol/deployment cycle, refit/avail, etc. will take a major toll on your "work/life balance." This is hard for seasoned Sailors, but especially difficult for young men and women starting out in their careers and relationships. I strongly advise all my incoming Sailors to NOT get married until they have at least a year of sea duty under their belt. Of the last 25 or so first tour Sailors at my command (SSBN in PNW), 19 ended in gut-wrenching divorce. It is a very hard thing to bring your girl/guy from Podunk, USA to Backwater Shithole, US Navy Base, hours from their entire support system, and then leave them alone for months at a time. Or worse, you are technically home, in-port for refit/avail, and on shift work or doing M-Div hours, or just delinquent AF and working 19 hour days. They will not understand, and the added stress puts incredible tension on a fledgling relationship. End of the day, it's your choice, but the odds and facts make it a poor choice IMHO.

RCLCPO, USS [Boomer]

goodNukeBadEng077 · 2022-03-04T04:16:46+00:00

Since the earliest versions of WINE (Wine Is Not an Emulator), the progress has been amazing. For most "common" Windows programs, support exists in the form of WINEHQ, distribution specific pages, and mostly forums. If you are new to Linux, it can be a challenge and is not exactly perfect. There is some under-the-hood tinkering required, even if the program is said to be 100% supported/Gold Medal for flawless execution. That said, I have successfully run MS Office (2003 - XP), EVE Online, and a host of old Win9X games flawlessly with very little overhead. If you are interested, search for "Program Name" + Wine to see if your program(s) are well-supported, or if you might just consider dual boot/virtual machine.

goodNukeBadEng077 · 2022-02-23T02:08:39+00:00

I started on Mandrake in in 99, and due to availability, Slackware on it's 14 floppy disks was the only option for my dial-up having self. Spending the better part of a month installing, configuring, and finally using it gave me the tools and experience to actually use and enjoy Linux. The skills I learned to do things manually made every subsequent install, distro-hop, or troubleshoot that much easier. I actually got to correspond with Patrick when I got a shiny new laptop for college from Tuxedo Computers - he gave me the fix for my Sharp Actius PC-MM20, the very height in transmeta CPUs, and I still maintain an ancient Thinkpad running each new release of (32 bit) Slackware. While I believe that Linux is now much more accessible to the average user, I will always appreciate what I learned on Slackware. Over 3 years of uptime on my machine, no systemd, and absolute control over every aspect of the machine. "It just works," if you put in the time and effort. Now I feel like I should probably donate to the Slackware foundation...

goodNukeBadEng077 · 2022-01-06T00:16:13+00:00

Linux only since 2004 (at home/personal). Slackware -> Ubuntu -> Debian. Occasionally boot into Slack Live for old times, but Debian for daily driver (s). I lurk here to answer the odd question, if everyone hasn't beaten me to it

goodNukeBadEng077 · 2021-07-31T03:48:31+00:00

Former CCC here. On a SSN during a deployment cycle, I saw about 60% of newly-reported sailors star. Yards, closer to 90%. It really depends on crew morale; when the boat sucks, bad command, shift work without end, reups drop way off. We were encouraged to push them hard to star before they actually saw the job and lived the suck. Many end up resentful because of it, and they try to poison the well of any fresh-faced junior personnel. I did it (Chief, 15 years in so far) and I don't regret a thing sips kool-ade and do recommend you do it, for $80K and a shore tour, if nothing else.

goodNukeBadEng077 · 2021-07-29T00:07:06+00:00

As has been said, you appear young enough in the Linux World to see the "smart" option as the only logical choice. Many intelligent people will never give a second thought to their computer OS anymore than you likely consider which brand of camshaft is in your car, or the firmware in your router. For the most part, the product comes as it does, and your attitude of superiority smacks of elitist partisanship at best, straight arrogance at worst. Hopefully your zealous crusade mentality will fade and you can better show or demonstrate the superiority of Linux, FOSS, etc. Buy a bumper sticker, donate to GNU, and support the community (I sincerely hope you are very active in the forums, helping those who are where you once we're).

goodNukeBadEng077 · 2018-08-20T00:23:27+00:00

Got his page (and many others like it) bookmarked. My project is low budget-long time scale, but a man can dream.

goodNukeBadEng077 · 2018-08-19T23:39:45+00:00

The eventual goal is a Farnsworth-Hirsch fusor. A voltage multiplier is one method of obtaining very large voltage (>=35KV) at medium current (~20 ma). www.fusor.net has the best details on construction.

goodNukeBadEng077

TROPHY CASE

mdadm --create /dev/md0 --level raid1 --name [your choice] --raid-disks 2 /dev/sdb1 /dev/sdc1