Posted by Lieutenant Demil Lis (Chief Science Officer) in Main Sim - Sensor Data - Labs

Posted by Captain Aaron Foley (Commanding Officer) in Main Sim - Sensor Data - Labs

Posted by Lieutenant Demil Lis (Chief Science Officer) in Main Sim - Sensor Data - Labs
Posted by… suppressed (12) by the Post Ghost! 👻
Demil rushed into the labs, barely missing the opening door as he entered. “Report,” he ordered, glancing about to assess the damage himself as he received the cadets’ points of view.

“We need to review the sensor logs for the past half-hour, try to find any gaps or signs of concealment,” he directed any free cadets. “Pull them up and break into teams.”

Lieutenant Demil Lis
Chief Science Officer

The general lab was in decent shape, though some small equipment had ended up on the floor, but thankfully no one was hurt here.

“Aye, Lieutenant,” Cadet Zayin replied, turning back to the console she sat at and pulling the data up on a main screen, as well as several of the single person consoles. She was one of the ones Demil left in charge often, having found she was responsible and a good leader, and she proved it as she started carrying out the CSO’s directions. “Hannah, Sevik, Aaron, can you take teams of 3? Anyone left’s with me.”
As they dug into the records, the power fluctuations proved to be a nuisance, but eventually they noticed a small blip before they were attacked. It was hard to define what the blip was, but it lasted half a second and then was gone. Thirty seconds later, they were attacked.

~Mischief Maker

Demil spotted it, having elected to go over both the raw data and the cadets’ results, and stopped the replay, bringing it back to the blip. “All teams, take a look at this,” he told them, flicking it up to the primary screen. “Any ideas on what this might be?”

“Computer, all available data on this point at this time?” he asked. “Any unusual particle emissions or anomalous readings?”

Lieutenant Demil Lis
Chief Science Officer

There were no strange readings otherwise. Rather than something external being detected, it was almost as if was a blip in the Challenger’s sensor grid, a tiny blind spot that wasn’t able to pick up anything in a range of angles from that one spot on the hull.

~Mischief Maker

crosspost

She toggled the intercom. =^=Lieutenant Lis, any ideas on the sensor anomalies? I’m seeing gaps where there shouldn’t be.=^=

Commander Halcyone
(Executive Officer)

A few moments later, the ship shook hard from three successive strikes. Power flickered in the lab and the sensors array was suddenly patchy.

~Mischief Maker

“Sevik, have your team get the status of those sensor arrays. See if this is a damage problem or something else,” Demil ordered, opening his comm channel. =/\= “Working theory is either the array was damaged or, more likely, jammed somehow.” =/\= He turned back to the rest of the cadets. “I want one team going over every detail in the several seconds immediately preceding the first blip, and another going over the past 30 seconds immediately before the three strikes just now. The last team will go over all of the data from that area of the sensor array over the past day, look for anything that could cause disruption at that point.”

Lieutenant Demil Lis
Chief Science Officer

At first nothing seemed to make sense. There was nothing that seemed to be causing the blip, and it was hard to even say exactly what it was. But the more they dug, the more they could see that there was a difference between the first attack, and the second. With the first, the Challenger had been travelling at warp and the Orions had known exactly where to strike.

With the second attack, the ship had dropped out of warp and was at a stop to deal with the necessary repairs, so they were much easier to find.

In comparing the two, the main difference was that before the first attack, the sensor grid seemed to have a very specific blind spot and the Orions seemed to know about it, because that is where they struck. The second attack was more them just hitting key areas and repeating the attack on power distribution. It was clear they wanted to disable the ship, not destroy it.

~Mischief Maker

=/\= “Bridge, they found a very small blind spot we didn’t even know about, I do not believe this was random,” Demil reported tersely. “They appear to be aiming to disable us, my recommendation is to lock down critical systems and data and prepare for boarding.” =/\= Following his own recommendation, he dispatched cadets to each lab to place all active experiments into locked storage and data into heavier encryption computer storage. “Cadet Zayin, I want you to take 2 others and attempt to rendezvous with Engineering, lock out the main computer core.”

Lieutenant Demil Lis
Chief Science Officer

=^=Plug that blind spot Lieutenant. I don’t want them sneaking up on us again.=^=

Capt Foley - CO (crosspost)

=/\= “Yes sir,” =/\= Demil agreed, taking a terminal and getting to work on patching the gap as best as possible with the damaged systems.

Lieutenant Demil Lis
Chief Science Officer

Strangely, as he worked to bridge the gap in the array, he’d notice that it was a part of the design of the ship. It was tiny, and almost imperceptible, but somehow the Orions had known about it. But more interestingly, it only seemed present (based on the data), when the ship was at warp. This coincided with the Orions attracting while they were at warp.

This complicated the patch because it required integrating systems that were currently not stable due to the power fluctuations radiating from Power Distribution that Engineering was working hard to fix.

~Mischief Maker

=/\= “The vulnerability is only exploitable at warp,” Demil reported. “I’m working to fix it, but I recommend being alert if we return to warp before I finish.” =/\=

Lieutenant Demil Lis
Chief Science Officer

=^=Make it quick Mr. Lis. We’ve only got so many hits left that we can take, and I’d prefer to be a long ways away from here before the Orions come back around again.=^=

Capt Foley - CO (crosspost)

=/\= “Aye, sir,” =/\= Demil replied, turning back into the labs. “Cadet Ashford, come over here. I could use another brain working on this,” he called over to the nearest cadet.
“See if you can do anything about those unstable systems. Talk to Zayin’s team if you need.”

Lieutenant Demil Lis
Chief Science Officer

Ashford quickly turned around to face Lis, as he heard his name called. “Aye, sir,” Ashford replied. He started to move toward the single-person console. He was feeling a mix of emotions ranging from excitement of being able to help the ship, to nervousness, hoping that he wouldn’t mess it all up. Ashford did feel confident, though, having Lis working by his side. He sat at the console and started trying to find ways to fix the sensor blip.

-Cadet Ashford, Science-