Topic Actions

Topic Search

Who is online

Users browsing this forum: No registered users and 34 guests

Oops

Join us in talking discussing all things Honor, including (but not limited to) tactics, favorite characters, and book discussions.
Re: Oops
Post by Weird Harold   » Thu Apr 16, 2015 9:24 am

Weird Harold
Fleet Admiral

Posts: 4478
Joined: Thu Apr 24, 2014 10:25 pm
Location: "Lost Wages", NV

Theemile wrote:
Random statesec ship wrote:...


It's quite easy to enforce lazy behavior...


Yes, but automated system should be in place limiting (or obstructing) communications between subsystems. [/quote]

We have to remember that the ships destroyed were StateSec ships -- of generally the same configuration as all PRN ships in a generally paranoid system. They would have had a backdoor into their self-destruct command loops for StateSec to do exactly what Shannon Forraker did to them -- command self-destruct from an external channel.

The MAlign did something similar to the ships of the PNE that we're explicitly told about, the the combination of institutional paranoia and institutional arrogance of StateSec would virtually guarantee that StateSec would be able to cheat in any battle against the regular Navy or rogue StateSec ships.
.
.
.
Answers! I got lots of answers!

(Now if I could just find the right questions.)
Top
Re: Oops
Post by Kytheros   » Thu Apr 16, 2015 9:31 am

Kytheros
Rear Admiral

Posts: 1407
Joined: Thu Dec 29, 2011 11:34 pm

cthia wrote:Keep in mind, that as Tac officer, Shannon has a lot of command clearance. She has to. Tac officers must be able to coordinate fleet-wide tactical munitions coordination. There were commands given by Honor, I think, to "tie in with CIC on the other ships and coordinate our attack." I'm sure CIC could be bypassed altogether, with the Tac officer clearance Shannon had - together with total systems knowledge. Plus, Shannon is a nerd. She knows the 'puters better than the SOB that designed them!

As far as what she actually did, I personally would not speculate that it had anything to do with the reactors. What Shannon did caused instantaneous destruction. Reactor failure takes time - even when all safeguards are removed - before reactor overload. And they wouldn't go together in a choreographed explosion. And there'd be warnings. And at least one engineer would have been in place to eject the core, saving that ship.

From what I remember of the passage, I don't think the scuttling charges are the answer either. Scuttling charges take a bit of time to destroy a ship as well, compared to the instantaneous, almost simultaneous destruction of all ships.

Theemile speculated commanded-missile explosions. That's a better fit of the evidence.

.

Nope, they were superdreadnoughts. Way too big for ejectable cores. Only the smallest warships can viably have ejectable cores, otherwise, you're leaving your reactors way more exposed and unprotected than they need to be.

Frankly, I'm not sure Rolands are small enough, and lightly armored enough to have ejectable cores, if they are, they're at the upper end of where ejectable cores are viable on warships. As far back as Short Victorious War, a battlecruiser was definitely way too big for ejectable cores. I don't remember if Star Knights had ejectable cores, but I don't think they did.

Also, with the fusion reactors, all you really need to do is screw up the containment field generators, and their backups, and then boom! Remember, the fuel is forced into fusion and held under extreme pressures by a gravity pinch mechanism. Of course, the reactor containment is doubtless something that gets heavily overengineered.
Also, there was a degree of delay between Foraker pushing the execute button and the SS SDs going up beyond transmission lag, exactly how long I'm not sure.


That said ... I think using the missiles is unlikely. I expect that they have failsafes with physical interlocks that would prevent either/both the missile warhead and impeller drives from initiating until they had been launched and were clear of the ship.


And thus ... we're at the self-destruct or blowing the reactors. Either or both is possible. And, frankly, there probably wouldn't be much way to tell, seeing as the self-destruct is probably a large nuke (or more than one, depending), and would blow containment on the reactors as well.
Top
Re: Oops
Post by roseandheather   » Thu Apr 16, 2015 9:46 am

roseandheather
Admiral

Posts: 2056
Joined: Sun Dec 08, 2013 10:39 pm
Location: Republic of Haven

I've always had the impression that Shannon simply caused the fusion bottle containment systems to fail. Voila - insta-vaporised StateSec SDs. Something about the way they went up so suddenly and so brilliantly just struck me as fusion bottles letting go. That's just me, though.
~*~


I serve at the pleasure of President Pritchart.

Javier & Eloise
"You'll remember me when the west wind moves upon the fields of barley..."
Top
Re: Oops
Post by cthia   » Thu Apr 16, 2015 9:56 am

cthia
Fleet Admiral

Posts: 14951
Joined: Thu Jan 23, 2014 1:10 pm

Kytheros wrote:
cthia wrote:Keep in mind, that as Tac officer, Shannon has a lot of command clearance. She has to. Tac officers must be able to coordinate fleet-wide tactical munitions coordination. There were commands given by Honor, I think, to "tie in with CIC on the other ships and coordinate our attack." I'm sure CIC could be bypassed altogether, with the Tac officer clearance Shannon had - together with total systems knowledge. Plus, Shannon is a nerd. She knows the 'puters better than the SOB that designed them!

As far as what she actually did, I personally would not speculate that it had anything to do with the reactors. What Shannon did caused instantaneous destruction. Reactor failure takes time - even when all safeguards are removed - before reactor overload. And they wouldn't go together in a choreographed explosion. And there'd be warnings. And at least one engineer would have been in place to eject the core, saving that ship.

From what I remember of the passage, I don't think the scuttling charges are the answer either. Scuttling charges take a bit of time to destroy a ship as well, compared to the instantaneous, almost simultaneous destruction of all ships.

Theemile speculated commanded-missile explosions. That's a better fit of the evidence.

.

Nope, they were superdreadnoughts. Way too big for ejectable cores. Only the smallest warships can viably have ejectable cores, otherwise, you're leaving your reactors way more exposed and unprotected than they need to be.

Frankly, I'm not sure Rolands are small enough, and lightly armored enough to have ejectable cores, if they are, they're at the upper end of where ejectable cores are viable on warships. As far back as Short Victorious War, a battlecruiser was definitely way too big for ejectable cores. I don't remember if Star Knights had ejectable cores, but I don't think they did.

Also, with the fusion reactors, all you really need to do is screw up the containment field generators, and their backups, and then boom! Remember, the fuel is forced into fusion and held under extreme pressures by a gravity pinch mechanism. Of course, the reactor containment is doubtless something that gets heavily overengineered.
Also, there was a degree of delay between Foraker pushing the execute button and the SS SDs going up beyond transmission lag, exactly how long I'm not sure.


That said ... I think using the missiles is unlikely. I expect that they have failsafes with physical interlocks that would prevent either/both the missile warhead and impeller drives from initiating until they had been launched and were clear of the ship.


And thus ... we're at the self-destruct or blowing the reactors. Either or both is possible. And, frankly, there probably wouldn't be much way to tell, seeing as the self-destruct is probably a large nuke (or more than one, depending), and would blow containment on the reactors as well.

Thanks for the info of a lack of ejectable cores on SDs. Very nice thoughts too.

One thing though. There was a delay between signaling and destruction. But the delay that should be questioned is the delay between ship explosions. Virtually simultaneous.

Although, IIRC, one ship went alone, probably the flagship. It would be reasonable that Shannon bypassed security of the flagship, which probably gave her easy tactical pickings of the other ships. But the one ship exploded, a delay, then all the other ships went almost simultaneously. Which points to some sort of possible cascade effect.

Containment failure eh? I have to concede that the type of resulting destruction has to be something huge. Reactor explosion can certainly fit that bill. I just didn't see how simultaneous explosions could be coaxed out of those systems, but I make the error of basing it on current reactor systems. Doh!

Son, your mother says I have to hang you. Personally I don't think this is a capital offense. But if I don't hang you, she's gonna hang me and frankly, I'm not the one in trouble. —cthia's father. Incident in ? Axiom of Common Sense
Top
Re: Oops
Post by Duckk   » Thu Apr 16, 2015 10:23 am

Duckk
Site Admin

Posts: 4200
Joined: Sat Aug 08, 2009 5:29 pm

But the one ship exploded, a delay, then all the other ships went almost simultaneously. Which points to some sort of possible cascade effect.


Where are you getting that? Nothing in the events point to that.
-------------------------
Shields at 50%, taunting at 100%! - Tom Pope
Top
Re: Oops
Post by cthia   » Thu Apr 16, 2015 10:39 am

cthia
Fleet Admiral

Posts: 14951
Joined: Thu Jan 23, 2014 1:10 pm

Duckk wrote:
But the one ship exploded, a delay, then all the other ships went almost simultaneously. Which points to some sort of possible cascade effect.


Where are you getting that? Nothing in the events point to that.

My apology Duckk. I just found that out myself. *Probably errant data conflicting in my head.

Ashes of Victory - Chapter 48
"Citizen Admiral, I have a com request from Citizen Admiral Heemskerk," Citizen Lieutenant Fraiser announced, and Lester Tourville looked up from the tactical exercise on Shannon Foraker's plot with a sudden chill. His raised hand interrupted his conversation with Foraker and Yuri Bogdanovich, and he turned to his com officer.

"Did the Citizen Admiral say what he wants?" he asked in a voice whose apparent calmness astonished him.

"No, Citizen Admiral," Fraiser said, then cleared his throat. "But a StateSec courier boat did enter the system about forty-five minutes ago," he offered.

"I see. Thank you." Tourville nodded to Fraiser and looked back at Bogdanovich and Foraker. "I'm afraid I'll have to take this call," he said. "We'll get back to this later."

"Of course, Citizen Admiral," Bogdanovich said quietly, and Foraker nodded. But then the tac officer inhaled sharply, and Tourville glanced back at her.

"Alphand's sidewalls just came up, Citizen Admiral," she said. "So did DuChesnois' and Lavalette's. In fact, it looks like Citizen Admiral Heemskerk's entire squadron has just cleared for action."

"I see," Tourville repeated, and managed a smile. "It would seem the Citizen Admiral's message is more urgent than I'd anticipated." He looked across the flag bridge at Everard Honeker, and saw the matching awareness in his people's commissioner's eyes, but Honeker said nothing. There was nothing, after all, that anyone could say.

Foraker was tapping keys at her console, no doubt refining her data, as if it were going to make any difference. Even if Tourville had been tempted to resist the order he knew Heemskerk was about to give, it would have been futile. With Heemskerk's squadron already at full battle readiness, it would have been an act of suicide to even begin bringing up his flagship's own sidewalls or weapon systems.

"I'll take it at my command chair, Harrison," he told the com officer. After all, there was no point trying to conceal the bad news from any of his staff.

"Aye, Citizen Admiral," Fraiser said quietly, and Tourville crossed to the admiral's chair. He settled himself into it, then touched the com stud on its arm. The display before him came alive with the stern, jowly face of Citizen Rear Admiral Alasdair Heemskerk, State Security Naval Forces, and Tourville made himself smile.

"Good afternoon, Citizen Admiral. What can I do for you?" he inquired.

"Citizen Admiral Tourville," Heemskerk replied in a flat, formal voice, "I must request and require you to join me aboard my flagship immediately, pursuant to the orders of Citizen Chairman Saint-Just."

"Are we going somewhere?" Tourville's heart thundered, and he discovered his palms were sweating heavily. Odd. The terror of combat had never hit him this hard.

"We will be returning to Nouveau Paris," Heemskerk told him unflinchingly, "there to consider the degree of your complicity in Citizen Secretary McQ—"

His voice and image cut off, and Tourville blinked. What the—?

"Jesus Christ!" someone yelped, and Tourville spun his chair in the direction of the shout, then froze, staring in disbelief at the main visual display.

Twelve glaring spheres of unendurable brightness spalled the velvety blackness of deep space. They were huge, and so hellishly brilliant it hurt to look at them even with the display's automatic filters. And even as he stared at them, he saw another ripple of glaring light, much further away. It was impossible to make out any details of the second eruption, but it appeared to be on the approximate bearing of Javier Giscard's flagship . . . and the StateSec battle squadron which had been assigned to ride herd on him.

Lester Tourville wrenched his eyes back to the fading balls of plasma which had been the ships of Citizen Rear Admiral Heemskerk's squadron. The silence on his flag bridge was total, like the silence a microphone picked up in hard vacuum, and he swallowed hard.

And then the spell was broken as Shannon Foraker looked up from the console from which she had just sent a perfectly innocent-seeming computer code over the tactical net to one of the countless ops plans she'd downloaded to the units of Twelfth Fleet over the last thirty-two T-months.

"Oops," she said.

It seems Shannon had been infiltrating and setting up these contingency plans over some time. You can't give a scorned, awakened giant of a woman of her means... time.


An aside:
* I'm in burnout mode. I'm scheduled to get married soon. Originally it was supposed to be in May. Then it was moved to June. Then late August. Then back to May. Then back to late August - when most people can get the vacation time. And the cost of this thing is soaring. I pledged to pay for it all myself. And it's approaching a quarter mil in cost - flying everyone to the Canaries, wardrobe, catering. Etc., etc. I don't mind the cost, but are weddings supposed to be this stressful?! Gees!

So, I am a burnout right now. And this time of year in the Civil Engineering business is taxing. Busy, busy busy. Building Projects!

At the end of my days now, I am crawling. Then, I have to help my fiancée with new logistics, a task of which she seems to have endless surges of energy from an unlimited reservoir. So, my apologies for everything.

Any advice from you already married victims other than, bridge - leap? :lol:

Son, your mother says I have to hang you. Personally I don't think this is a capital offense. But if I don't hang you, she's gonna hang me and frankly, I'm not the one in trouble. —cthia's father. Incident in ? Axiom of Common Sense
Top
Re: Oops
Post by Sharp Claw   » Thu Apr 16, 2015 12:10 pm

Sharp Claw
Lieutenant Commander

Posts: 109
Joined: Mon Nov 04, 2013 3:26 pm

Shannon simply sent a routine, slightly modified , fusion reactor maintenance update & executed it.

OOPS

I was supposed to shut down the reactor before I turned off the containment field. Oh well.

If you think automated safety routines should have caught this little error remember this is peep software. :twisted: Also Shannon probably executed the code at a very low level like the driver level for the hardware, bypassing all higher level code and its builtin safety routines.
Top
Re: Oops
Post by cthia   » Thu Apr 16, 2015 12:12 pm

cthia
Fleet Admiral

Posts: 14951
Joined: Thu Jan 23, 2014 1:10 pm

The cutest little 9-month-old baby was sitting in her high chair waiting to be fed. She liked these times. Her high chair afforded her a god-like view of the world. She could see the cat and the puppy playing chase, and all the new targets as goals to reach by crawling. A mode of propulsion she had mastered.

Food! She loves the stuff. Maybe she'll get the good grub today. The applesauce. Yummy! Oh no. It's the green gook. Her mummy cooks and mashes zuchini then stuffs it in jars and feeds it to her. It's horrible. It's only redeeming qualities are it's healthy - no salt added, cost effective and it makes mummy feel good about herself. But baby Shannon hates the stuff. Wait, mummy is distracted by an HD call. Now's my chance. Just a slight nudge ... There! Splash! All over the carpet! Uh oh, mummy is angry.

"Oops."

Baby Shannon's first word. And mama is so pleased by that first spoken word that she forgets all about the mess.

"That's so cute." Mama says.

Baby Shannon forvever connects with that one word.

:lol:

Son, your mother says I have to hang you. Personally I don't think this is a capital offense. But if I don't hang you, she's gonna hang me and frankly, I'm not the one in trouble. —cthia's father. Incident in ? Axiom of Common Sense
Top
Re: Oops
Post by Theemile   » Thu Apr 16, 2015 12:29 pm

Theemile
Fleet Admiral

Posts: 5241
Joined: Sat Feb 27, 2010 5:50 pm
Location: All over the Place - Now Serving Dublin, OH

cthia wrote:An aside:
* I'm in burnout mode. I'm scheduled to get married soon. Originally it was supposed to be in May. Then it was moved to June. Then late August. Then back to May. Then back to late August - when most people can get the vacation time. And the cost of this thing is soaring. I pledged to pay for it all myself. And it's approaching a quarter mil in cost - flying everyone to the Canaries, wardrobe, catering. Etc., etc. I don't mind the cost, but are weddings supposed to be this stressful?! Gees!

So, I am a burnout right now. And this time of year in the Civil Engineering business is taxing. Busy, busy busy. Building Projects!

At the end of my days now, I am crawling. Then, I have to help my fiancée with new logistics, a task of which she seems to have endless surges of energy from an unlimited reservoir. So, my apologies for everything.

Any advice from you already married victims other than, bridge - leap? :lol:


As my best friend said, sobbing, to his soon-to-be wife on the phone a week before their wedding: "I can't take this anymore - I was happy just living in sin!"

After living through my sister's fiasco and the months of family fallout before and after that wedding, my wife and I eloped - we told both families our planned date at the courthouse about 2 weeks prior to the event so they could be there.

All I can say is good luck - I hope it's worth it.
******
RFC said "refitting a Beowulfan SD to Manticoran standards would be just as difficult as refitting a standard SLN SD to those standards. In other words, it would be cheaper and faster to build new ships."
Top
Re: Oops
Post by Jonathan_S   » Thu Apr 16, 2015 12:36 pm

Jonathan_S
Fleet Admiral

Posts: 8791
Joined: Fri Jun 24, 2011 2:01 pm
Location: Virginia, USA

Kytheros wrote:Frankly, I'm not sure Rolands are small enough, and lightly armored enough to have ejectable cores, if they are, they're at the upper end of where ejectable cores are viable on warships. As far back as Short Victorious War, a battlecruiser was definitely way too big for ejectable cores. I don't remember if Star Knights had ejectable cores, but I don't think they did.
I thought HotQ said something about it, but when I went looking it seems I'd be confused and was thinking of the following passage from SVW.
Short Victorious War: Ch6 wrote:As in most merchantmen, fusion rooms in destroyers and light cruisers—and some smaller heavy cruisers—were designed with blow-out bulkheads to permit them to jettison malfunctioning reactors as an emergency last resort. But larger warships couldn't do that, unless their designers deliberately made their power plants more vulnerable than they had to.
I'd guess that as the newest, and biggest, CA in RMN service at the time of that quote that a Star Knight would not be in the group of "some smaller heavy cruisers" with emergency ejection mechanisms for her fusion plants.

But that's far less definitive than what I was originally thinking.
Top

Return to Honorverse