View source for RP Log: About that Slipstream Drive

[[Category:RP Logs]][[Category: 2446]]
<div>
{| border="0" class="infobox bordered" style="width:210px; font-size:90%; float: right; clear: right ; border: 1px solid darkgray; background-color: #dee0e3; border-collapse:collapse;margin:1em 1em 1em 1em;"
|-
! style="background-color:#878681;" colspan="2" | <span style="color:white">Roleplay Log</span>
|-
| style="width: 32%;vertical-align:top;padding:0.5em;" | '''Participants:'''
* [[Hauser]]
| style="width: 36%;vertical-align:top;padding:0.5em; " | <br>
* [[Worthington]]
|-
| style="width: 32%;vertical-align:top;padding:0.5em;" colspan="2"| '''Location(s):'''
* Shuttlebay - Saucer -- USS Sao Paulo
* Combat Simulator -- USS Sao Paulo
|-
| style="width: 32%;vertical-align:top;padding:0.5em;" colspan="2"| '''Stardate:'''
* 123791.0
|-
! style="background-color:#878681;" colspan="2" | <span style="color:white">2022-09-25 21:33</span>
|}
</div>
:''Shuttlebay - Saucer <USS Sao Paulo NCC-122004>
:''The largest internal compartment aboard the vessel is the primary shuttlebay of the saucer section. This cavernous expanse is over four decks tall, 125 meters in length, and 110 meters wide. The deck is labelled with a variety of symbols and markings to easily facilitate auxiliary craft procedures. There are 12 landing pads here, spread out evenly and used to refuel and/or provide external support to the auxiliary craft. Six of the landing pads can handle smaller vessels such as shuttlecraft, while the other six are designed for larger craft such as the Delta-Flyer class or Runabout. There are also additional storage racks for auxiliary vessels along both the port and starboard bulkheads, and a conveyor system along the ceiling for storage of up to six workbees.
:''Unlike some other vessels, there is no secondary shuttle storage facility above or below the bay. Massive blast doors can be raised and lowered at the aft of the bay to facilitate landings and takeoffs. A ladder near the fore of the bay leads up several decks to the shuttlebay control room.
<br><br>
Worthington is walking through the ship, heading nowhere in particular, but passing through the shuttlebay, looking at the probe from another universe and setting his eyes upon Huang He.
<br><br>
Hauser pops out of the hatch of the Huang He, tricorder in hand, muttering to it. She doesn't see Worthington meandering as she shuts the runabout up.
<br><br>
Worthington sees hauser however as he passes around the rear of the runabout. He makes his way toward the entry hatch and waves down the ensign. "Anything to report?" he asks.
<br><br>
"Yeah," she says. "One is, I don't think spoofing the computer with a simmed problem's gonna tell us what we need to know sir. I wanted to suggest a holodeck recreation of the problem?"
<br><br>
Worthington considers that. "Could you copy over the subroutines from the Huang He's computer? We could also put them into one of the combat simulators downstairs on deck 23. They have a simulation model for the gryphon-class runabout as well. I want your professional opinion though on the best way to handle this diagnostic issue."
<br><br>
"I've got them here," she says, tapping her tricorder. "I don't have a lot of experience with the combat simulators, but if they have a gryphon-class, we won't have to recreate the thing, and if the sims will let us load our own computer parameters as are, then there we go."
<br><br>
Worthington nodds. "Never had a reason to do so, but that's something you should be able to easily find out," he replies. "Shal we?" he asks.
<br><br>
Hauser says, "After you, sir."
<br><br>
:''Combat Simulator One <Venture>
:''The inside of the simulator is fairly nondescript. There are two console for controlling the system, and a number of display screens. When in operation the lights are slightly dimmed.
<br>
Worthington is settling in, a gryphon-class simulation loaded. He takes a seat at one of the consoles.
<br><br>
Hauser drops into the chair. "Ok, now to isoolate this sim from the mainframe. I don't want the ship's computer taking up these parameters and thinking we want the mainframe to do what we're doing here."
<br><br>
Worthington nodds. "Yes, we don't want to corrupt the stock simulation. That is advisable," he replies. "There are a few default power profiles here for us to work with, but our diagnostic routine will focus on the slipstream drive with the parameters input."
<br><br>
Hauser says, "So you don't want me to load up any of these? Or you do?"
<br><br>
Worthington smiles. "Load the cruise one, kill the ftl drive, and power the slipstream drive. You should be able to do the switch over in these, no department head lockouts that I know of."
<br><br>
Hauser says, "No department head lockouts, sir. No slipstream drive, either."
<br><br>
Worthington smiles. "It's listed under, secondary ftl system. They're cute with labeling in here," he replies with a grin.
<br><br>
Hauser says, "Very much. Ok, got that handled, sir."
<br><br>
Worthington nodds. "Good. How's the isolation protocol going?" he asks.
<br><br>
Hauser looks down at the parameters as they finally stop clicking home. "I think we're set, sir. When I load these parameters," she taps her tricorder, "the sim will, should, do exactly what the Huang He's systems are doing. That's the beauty of a simulator. They can recreate mistakes, too."
<br><br>
Worthington smiles. "Perfect," he replies. "Slipstream requires autopilot, so we're going to ignore the whole neutral zone rule. Sims are good for that too. Setting a course for Eisn. Engage on your mark."
<br><br>
Hauser grins. "You fancy going to Romulus, sir?"
<br><br>
Worthington smiles. "Either romulus, a nebula, or a black hole, so Romulus it is," he replies.
<br><br>
The vessel vibrates as it transitions into slipstream.
<br><br>
Hauser says, "Ok, so far so good. THis problem, it was intermittent? It didn't happen every time?"
<br><br>
Worthington responds. "Once it started happening, it was like every 30 seconds or so," he replies.
<br><br>
Hauser says, "Ok, I have an idea. May I? She starts punching in coordinates. "Just ti give us more time to see the problem in action.""
<br><br>
Worthington nodds. "Anywhere will do," he replies, getting where the ensign is coming from.
<br><br>
Hauser hits the controls and settles back in her chair. About 20 seconds later, the first error message flashes, warning of slipstream integrity failure.
<br><br>
The vessel vibrates as it returns to normal space from subspace.
<br><br>
Worthington watches that message pop up on his display and considers. "You able to trace the subroutines and see what caused that to occur?" he asks.
<br><br>
"That's what I've been up to. Odds say this isn't a drive system issue at all." She punches in a few commands, overriding the error message and getting an electronic curse from the computer as she reengages the drive.
<br><br>
The vessel vibrates as it transitions into slipstream.
<br><br>
Worthington nodds. "That's what I originally thought," he replies in ascent. "I had to override the system to get Huang He back at all, and if it had been a drive problem, well, the runabout should have suffered some internal damage from that trip home."
<br><br>
Hauser says, "Commander, if it'd been a drive problem, overriding the computer and reinnitiating that particular drive in spite of the issue would have scattered your atoms from here to Orion Three, sir. So, honestly, I never counted on s propulsion system malfunction."
<br><br>
Worthington nodds. "Plus, the drive damage initially shown would have been real," he adds. "I don't fancy having any of my atoms on Orion 3, so let's not cause that to happen."
<br><br>
"I'm all for that," Hauser says. "You remember, sir, I was initially guessing some kinf of foul up between the drive and the computer control and monitoring systems? I still think that. I just need to dig and see exactly where the faulty code is. If it's faulty code."
<br><br>
Worthington nodds. "Understood," he replies. "Will diagnostic tracing in here help you find it?" he queries.
<br><br>
"Probably not," Hauser says. "I'll need to dig back through the readings I have from the real Huang He, sir. But these sim gives me an idea of where to start. I'll have to be painstaking about it. No messing around with Slipstream."
<br><br>
Worthington nodds. "Understood. I'm glad we've got a place to start. Anything you need you can have. I'd really like to get Huang He operational as soon as possible. We have nothing to conduct medium to long range trips at the moment."
<br><br>
Hauser says, "Thanks. I'll let you know what I find as soon as I find out. THen, of course, we'll have to fix it."
<br><br>
Worthington nodds. "That we will," he replies. "Before we leave, be sure to reset the code on the sim then link it back to the mainframe. Don't want any issues with the computers here. Once we have a working idea as to what the issue is and how to fix it, we can move forward there," he replies.
<br><br>
Hauser nods. "We'll get it figured out, Commander," she says. SHe enters in a series of codes, disengaging her special parameters. "Ok, it's safe again. But still where we left it, sir."
<br><br>
Worthington smiles. "Oh, that's no worry. The coordinates and parameters automatically reset when reloaded and reset," he replies, disengaging the program.