13,525
edits
(New log.) |
No edit summary |
||
Line 23: | Line 23: | ||
{{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #10''' <br>I am now acting as the First Officer of the USS Invicta, as well as the project manager for SCE in this region of space - forgive any extraordinary breaks between log entries. '''[sighs]''' I need some sleep. <br>I've been thinking about the transporter beacons that we're using to sort of 'rush' forward an in-progress transport to reach the secondary transport site. The problem we're facing at the moment is that there isn't enough distance between beacons to not just cover every figurative inch of space in them to be useful. It's not a logical decision if starships are going to have to correct their courses every minute to avoid hitting one. Not to mention that while a beacon path would be the most efficient way to push forward transport, it'd also mess up the computer system and we'd lose people or objects in transport should one beacon's frequency cross with another and make an infinite loop. I want to avoid that. <br>Speaking of which, I may have to reconsider this being an automated system. We're still a long way away before implementing this in any sort of serious manner - the damn thing hasn't even been constructed for real yet, nor will it be until these tests show some proper results - but now that we're rethinking the scope of the system and with the beacons, we may actually have to have each station crewed by at least one person. Which would also mean we'd have to factor in living quarters on top of the power distribution. '''[huff]''' You know what? I'll focus on the tech first and worry about that later. <br>The problem with biological matter hasn't yet been addressed - so we haven't put a person back into the shuttle as of yet until we can figure out what went wrong in that area. I've got a feeling it's got something to do with the energy output - as a technical rule, transporter deconstruct matter to recompose it a way away. People have to be destroyed before they can be put back together. The question is just how much decomposition is the transporter doing to confuse itself when it puts people back together again. I'll have to consult Blueheart. In the meantime, I'm curious to see whether bio-neural gel packs will result in a similar scenario of deconstruction, so we've begun to equip the newest Akeelah with the system. Since we're not testing the system's performance on the shuttle, accuracy according to new SCE designs isn't necessarily needed, but in the event it does spark something out of the blue, I'd rather have it as accurate as possible. None of us are happy with that, but that's how experiments get done, I guess. <br>Oh, before I end this recording, to address why log nine was suddenly cut from recording? Yeah. ''My crew got possessed.'' Remind me to lodge a complaint to Starfleet about our lack of 'anti-possession' technology or something. The fact that we don't have anything of the kind is a huge oversight by SCE and Starfleet Medical. Somebody get on that.{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | {{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #10''' <br>I am now acting as the First Officer of the USS Invicta, as well as the project manager for SCE in this region of space - forgive any extraordinary breaks between log entries. '''[sighs]''' I need some sleep. <br>I've been thinking about the transporter beacons that we're using to sort of 'rush' forward an in-progress transport to reach the secondary transport site. The problem we're facing at the moment is that there isn't enough distance between beacons to not just cover every figurative inch of space in them to be useful. It's not a logical decision if starships are going to have to correct their courses every minute to avoid hitting one. Not to mention that while a beacon path would be the most efficient way to push forward transport, it'd also mess up the computer system and we'd lose people or objects in transport should one beacon's frequency cross with another and make an infinite loop. I want to avoid that. <br>Speaking of which, I may have to reconsider this being an automated system. We're still a long way away before implementing this in any sort of serious manner - the damn thing hasn't even been constructed for real yet, nor will it be until these tests show some proper results - but now that we're rethinking the scope of the system and with the beacons, we may actually have to have each station crewed by at least one person. Which would also mean we'd have to factor in living quarters on top of the power distribution. '''[huff]''' You know what? I'll focus on the tech first and worry about that later. <br>The problem with biological matter hasn't yet been addressed - so we haven't put a person back into the shuttle as of yet until we can figure out what went wrong in that area. I've got a feeling it's got something to do with the energy output - as a technical rule, transporter deconstruct matter to recompose it a way away. People have to be destroyed before they can be put back together. The question is just how much decomposition is the transporter doing to confuse itself when it puts people back together again. I'll have to consult Blueheart. In the meantime, I'm curious to see whether bio-neural gel packs will result in a similar scenario of deconstruction, so we've begun to equip the newest Akeelah with the system. Since we're not testing the system's performance on the shuttle, accuracy according to new SCE designs isn't necessarily needed, but in the event it does spark something out of the blue, I'd rather have it as accurate as possible. None of us are happy with that, but that's how experiments get done, I guess. <br>Oh, before I end this recording, to address why log nine was suddenly cut from recording? Yeah. ''My crew got possessed.'' Remind me to lodge a complaint to Starfleet about our lack of 'anti-possession' technology or something. The fact that we don't have anything of the kind is a huge oversight by SCE and Starfleet Medical. Somebody get on that.{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | ||
{{#if:{{{4|}}}|<br />|<div style="border:1px dotted #666666; padding:0.5em; font-family:Verdana,sans-serif; margin: 1em 1em 1em 3em;">'''MST Development Log #11''' <br>Last log I made for this blasted thing was six months ago. Honestly there hasn't been much for me to report - we're still stuck at the same problems as last log entry. Since then, I failed to consult Blueheart about the humanoid aspect of the transport. I've also gone on long service leave to Rodul were . . . things have been interesting, but no less peaceful than I'd expected, and taken my MST work with me, or what I could bring of it, because the Corps of Engineers allowed it. <br>Which brings me to why I'm making this log entry - to thank one [[Nygeyan-Vale Caeloi]], a non-Starfleet Rodulan engineer, who just broke my MST out of a solar system and into sector space! I'm too tired to get into specifics, and I'll be sure to add it into the files, but for now, know that I am one semi-happy Rodulan!{{#if:{{{2|}}}|<div style='margin-top:.5em'>{{{2}}}</div>}}{{#if:{{{3|}}}|<div style='margin-top:.5em'>{{{3}}}</div>}} ''</div>}} | |||
[[Category:Sky Blake]] | [[Category:Sky Blake]] |
edits