“You have CIC,” Levy responded. He then turned in the direction of the nearest CIC omni sound pickup and announced, “Computer, log that the Officer of the Deck transferred CIC Con to the CO at 00:46.”
“CIC Con transfer to Commanding Officer logged at zero hours, forty-six minutes,” announced the Computer, its voice sounding perversely like a cross between an inhuman mechanism and a nymphomaniac sex kitten. The regulations were clear: only one man was in charge in CIC at any given time, and there was never, ever the slightest doubt as to who that was. Every change was announced and the time logged. After all, the joke went, if anything happened to the ship, and the man who had the con survived, he would be shot. And the Navy wanted to be sure to shoot the right man.
“Status.”
“Sir, course is zero-four-three mark two-five-eight, speed eight hundred c,” Levy reported. “Still awaiting report from Sensors on data acquired from course change. Ship is at Condition Blue. All systems nominal.” Condition Blue was the second lowest readiness state. The lowest was Green. Max never set Condition Green unless the ship was in a well-guarded rear area, preferably in the vicinity of at least a Carrier and a couple of Battleships, and even then only if he really trusted the Captains of the Carrier and the Battleships. When you command a warship, the question is never whether you are being paranoid, but whether you are being paranoid enough.
“Very well.” Now, Max was in a quandary. Because of his orders regarding the “Sweet Seventeen,” every department in the ship other than CIC was working without the benefit of its best men. Not only that, under the Watch rotation system, Second Watch on Day Two of the cycle was stood by the White Watch, the weakest of the three. Max could solve both problems by going to General Quarters, which would bring the Sweet Seventeen out of hibernation and would put everyone at Battle Stations, meaning that every position would be stood by its best man, usually with the second best right at his elbow. But, that would defeat the whole purpose. These men, even the least skilled of them, would have to be brought up to a standard of reasonable proficiency. They would have to start walking without crutches.
They would have to start walking right now.
Levy started to move toward his accustomed post at Intel to relieve Rhinelander.
“And where do you think you are going, Mister Levy?”
“Um, the Intel station, Captain.”
“Mais, non. I’m not letting you off the hook that easily, young man. You’re the Officer of the Deck, which means for the duration of this watch you are a Command Level Officer for this vessel. Unless and until I summon Mister DeCosta to CIC, you are my acting XO. Now, take your station, Mister.”
“Aye, sir.” Levy stepped over to the XO’s station, sat down, and fired up the console which had been left on STAND BY, his hands moving deftly over the controls. Apparently, Mister Levy had spent some time on the Command Console Simulator preparing for his big night in the Big Chair. Good man.
Max cast a glance over at Hobbs at Sensors. He was deep in a discussion with his Back Room, rapidly pulling up graphs that looked like various computer generated hypotheses of the target’s motion and the compression readings that would result, trying to find a fit. This was typically done by the computer without much human intervention. If Mr. Kasparov were sitting in that chair and Mr. Harbaugh running the Back Room, Max wouldn’t even think of intervening, but with Kasparov off watch and Harbaugh sequestered with the Sweet Seventeen, anything could happen. Max should have heard some sort of call from Sensors by now—at least a bearing to the target and a recommendation of what to do to localize it. He looked over at Hobbs again. Nothing.
So, Max did something he had not done since he assumed command of the Cumberland. He eavesdropped. The CO’s station had the capability of monitoring every data and voice channel on the ship. Max’s predecessor apparently spent most of his time doing just that, either from the CO’s station or from the work station in his Day Cabin, and had configured both consoles to do it easily and efficiently. Max hated micromanagement, but he had a feeling that that his sensors guys might be stuck on something.
He pulled up the data channels that the Sensors’ Back Room was sharing with Hobbs. He could see that they were digging into the raw data rather than looking at what the computer was doing with it. The raw data, and even the partially processed raw data, was too complex and too full of random variations for human beings to interpret. It took lots and lots of computer processing to tease out the patterns. This made no sense. Then he looked at what the computer was generating and saw why the Sensors people were having trouble.
The computer was putting out nonsense. Pure garbage. One minute, it was hypothesizing that the target was impossibly wide--272.53 kilometers wide, the size of a not inconsiderable moon--and the next postulating that it was following a zig zag course at unheard of velocities, making course changes that would tear any ship into ragged shreds, with the points of the zigs on one side and of the zags on the other forming two parallel lines 272.53 kilometers apart that tracked the Cumberland’s former course. This was crap. The computer has gotten confused.
No. That’s wrong. Computers don’t “get confused.” People confuse them. The oldest adage of computer use, probably articulated about twelve minutes and nineteen seconds after the first computer was turned on, is: GIGO—garbage in, garbage out. OK. Find the garbage. He pulled up some diagnostic screens. The sensors that read the compressed space/normal space boundary checked out. But that data went lots of places before it hit the computer. He quickly ran the signal path and the intermediate processors—they all checked out. He was missing something. The computer’s conclusions were derived from what? There was the data from the sensors. That had to be good. There was the algorithm that processed the data. That had been checked by NAVCOMPSYSCOM half a million times under every conceivable data state. That had to be good, as well. That left the comparatively trivial few bits of data and limiting assumptions that sometimes got input by the operator. That had to be it. But what did the operator input? It had been four years since Max had worked in Sensors and this version of the system was newer than that. He didn’t know.
Time to fess up. “Hobbs. I could see you were having problems, so I was looking over your shoulder. Trying to help out.” He shrugged slightly, to acknowledge that he was admitting a kind of transgression, if even a minor one. Just because the skipper was the closest thing to God on his ship didn’t mean he should be high-handed. Hobbs nodded quickly, as if to admit that he was a bit over his head and was glad to have the help. “Look, I see what you guys are doing, but you’re on the wrong track. The problem isn’t in the data. It’s got to be something wrong with an operator input. I’m not familiar with this thing. What gets supplied by the operator?”
Max read the blank look on the man’s face before he could work up the courage to say that he didn’t know. Max saved him the trouble. At least he knew that the man would never even dream of bullshitting him.
“OK. You can’t know everything Hobbs.” Max punched himself into the circuit to the Sensors Back Room. “This is the skipper. Who’s on the compression detector?”
“Greenlee here, sir.”
“Greenlee? Oh, right. You’re the only one of my three James Smiths who’s not James Edwin Smith—you’re from Greenlee something or other. OK, Mister Greenlee, we’ve got to figure this thing out before this target gets out from under us. What are the operator inputs on this thing? That’s got to be where the problem lies.”
“Sir, I can’t see where. There’s not much to input. The system mainly relies on the data from the sensors. I input the calibration values from the last diagnostic. I triple checked those. Our speed gets read in automatically. I checked it anyway. It was one thousand nine hundred sixty c, now it’s eight hundred c. For some reason it makes me manually input the compression field gradient. I checked that twice and had Chief Klesh verify it. It’s right. The only other thing is number of contacts.”
Bingo. “It makes yo
u input the number of contacts manually?” Max heard his voice rising in pitch and volume. He was starting to get a bad feeling about this. It was starting to make sense. A very bad kind of sense. “You mean, it doesn’t try to get a fit for different numbers of contacts? It just assumes the truth of the number of contacts you give it and tries to get a fit on bearing and range with the data it has?”
“That’s right, sir.”
“And you assumed one contact,” Max said. “Of course you did. It was inconceivable to you that there would be two contacts out there in interstellar space that somehow were on a constant bearing with us. It could never happen by chance.”
“That’s right, sir.”
“It didn’t happen by chance. Have the computer assume that there are two contacts.”
“Two, sir?”
“Two. Yes. Now.”
“Aye, sir.”
Max watched the Sensors console’s SSR ATTN data channel that he had earlier pulled up for display on his own console. In a few seconds, the nonsensical conclusions reached by the computer resolved itself into usable data. Yep. Two contacts. Solid bearings, ranges, speeds.
“Contact,” said Hobbs, nearly shouting. Max turned to him sharply and made a downward patting motion with his right hand to signal him to lower his voice. Hobbs got the point, rattling off his designation of the contacts as Uniform One and Uniform Two, their speeds, bearings, and ranges, in something approaching a normal tone of voice.
“Maneuvering, get us back on our former course and speed. Match our former course track exactly and put us at the point in space we would be if we had not changed course. As fast as possible without compromising stealth.” Lugatsch acknowledged the order. “Hobbs, keep a close eye on those two contacts. Don’t blink. Don’t even fantasize about blinking. If they so much as swerve to run over a rattlesnake, I want to know. Understood?”
“Understood.” Max could hear the compression drive increasing the ship’s speed and the cooling system for the fusion reactor working harder as the power plant increased its output to supply the staggering amount of energy needed to trick the space time continuum into propelling the ship at more than two thousand times the speed of light. About ten minutes later, he heard the notes of both power plant and cooling plant drop as the speed dropped to 1960 c. Lugatsch announced that the ship was back on its former track at his former speed, where it would have been had nothing happened.
There was a Mid posted in CIC to assist the Captain. Max waved him over to get him some coffee, pointed at the pot and raised an inquiring eyebrow at Levy who nodded. Getting coffee was part of the job description, and the boy who happened to have that duty for this watch—a nine year old named Gilbertson, one of the second or third youngest class of squeakers--almost skipped over to the coffee pot to fetch for both officers. Oh, to have that kind of energy at about one in the morning.
While he was doing that, Max punched in the voice loop for the Sensors Back Room. The USS Cumberland College of Advanced Space Warfare and Keeping Your Ass from Being Nuked by Some Rat-Faced Krag Bastard was now, once again, in session.
“Gentlemen, this is the skipper. I want to thank you for your hard work just now. I know that because of the new training schedule you are short a few people who might have made things run a little smoother and I understand that. I’m on your loop to remind you that just because you are constantly hearing that Mr. Krag doesn’t do very well at thinking outside the box is no excuse to keep your thinking inside the box. Why? Because we’re talking two different boxes, people. Don’t make limiting assumptions. Always know what your assumptions are and if, when you apply them, you turn up nonsense, go back to them and try a different set. Keep trying until you get something that explains the data. Men, never forget, the job of the Sensors section is to find truthful interpretations that fit the sensor data, not to find data that fits your interpretations. It’s likely to be an exciting watch, folks, so stay alert. Keep your eyes peeled and your minds open. Skipper out.”
The coffee arrived. Both men took a few sips.
School wasn’t over. He had dismissed the big lecture class of Freshmen and Sophomores. Now for the Senior Seminar. “Well, Mr. Levy, a good weapons officer doesn’t have his head stuck in the Fire Control Console. He needs to know something about what is going on with the targets he’s shooting at. So what’s going on here?” Seeing a bit of a blank look, Max prompted, “Start with the basics and work up from there.”
Max could almost hear him gulp. “Well, sir, there are two targets, Uniform One and Uniform Two, currently unidentified. Uniform One is right on our six, matching our velocity at nineteen hundred and sixty c at a range of one-point-one-one-six AU. Uniform Two is two hundred seventy two kills off his port beam. I don’t think they know we’ve spotted them back there.”
“Why do you think that?”
“We just got an upgrade to our local compression detection system. That gave us about a forty percent increase in its range. As far as we can tell, the Krag are still at their old level of technology. There’s no way they just blundered into us way out here in interstellar space dozens of light years from the FEBA. The only theory that makes sense is that they somehow knew we were coming through, lay in wait along our flight path, picked us up, and then fell in behind us, beyond what they thought was our detection radius. When we did our localization maneuver, we never entered their detection radius, so they should be ignorant of what we did. They aren’t really interested in tracking us. They’re acting like they know where we’re going. They just want to get there right behind us.”
“Exactly what I had concluded. All right. Now, who are they?”
“Well, sir, we’ve got to presume they’re Krag. That’s who we’re at war with.”
“Can we do more than that? Do we have any evidence of who they are?”
“No, sir. At this range and at superluminal velocities, all we can do is to detect bearing, range, and speed. We don’t have any of the phenomenologies that give us an identification.”
“Don’t we? What’s the range to Uniform One again?”
“One-point-one-one-six AU.”
“Anything about that number sound familiar to you?”
“Come to think of it, it does ring a bell, but I can’t remember what it is.”
“That’s because the contexts are too different for your brain to make the connection easily. Fortunately, you’ve got a memory aid.” He pointed at the keyboard.
“Riiiiight. Sir.” Levy typed in a query, asking the computer to find other distances, ranges, and sizes that were 1.116 AU. There were fourteen matches. He started down the list: the mean diameter of the Hoffman Nebula, the periastron of a periodic comet in the Alphacen system, the length of the first experimental compression drive flight undertaken by the Pfelung, and . . . “That’s the mean distance of the Krag home world from their sun. It’s basically their AU.”
“You got it. That’s a nice comfy distance for them. When they want to stand off a safe distance from something, that’s a distance they often pick. Not always, not even most of the time, but often enough that when you see something at that range you know it’s a Krag ship. In some ways, they’re a lot like us. Haven’t you heard skippers say, ‘Maneuvering, put us one AU behind Hotel Three”—things like that?”
“Yes, sir.”
“And, there’s a clincher. What’s the range between the two ships?”
“Two hundred seventy-two, no, two hundred and seventy-three kills.”
“No. The exact distance. Take it to two decimal points. I’m betting that it’s exactly two hundred seventy-two point five three kills.”
Levy input the query. “That’s right, sir. How did you know?”
“The fundamental Krag unit of linear measurement is point-two-seven-two-five-three meters. Lots of the things they do come out to a nice round power of ten of that distance. Like the maximum range of their Foxhound missile which is?”
“Twenty-seven thousand, two hundred, and fift
y-three kills. I get it.”
“Again, they’re a lot like us that way. Can’t you just hear the big cheese back there telling the smaller cheese ‘position yourself a thousand Kragometers,’ or whatever they call their unit, ‘off my port beam’? That’s just the sort of thing we’d do. That’s why I often give orders to stand off at odd ranges.”
“So, sir, that pretty much makes them Krag.”
“I wouldn’t bet against it, Levy. Not even if I was betting with your money. Now, let’s get a little speculative. What does that mean for us?”
“Well, skipper, I suppose it would have to mean that the Krag had in their possession sufficient information for an intercept.”
“Which is?”
“It’s what you need to determine a velocity vector in time and space. Departure point, departure time, either course or destination, and speed.”
“Right, Levy. Now, if they had our departure point and time, course or destination, and speed, what does that imply?”
“There has to be some sort of leak, or spy, or Krag ability to intercept and decrypt at least certain critical tactical communications, or that they somehow observed our departure.”
“Observation wouldn’t have helped them. You weren’t on watch so you wouldn’t know this. I departed the system nearly ninety degrees off the lubber line on two axes and ran at 1580 c for an hour and a half, then turned toward the rendezvous point and increased speed to 1960 c. So anyone taking a read on our departure or tracking us for the first ninety minutes would have been completely misled as to direction and velocity. So, we’re back to the first set of possibilities. How do we narrow that down? Any ideas?”
“Sir, I’m not much on Intel. Too much guessing. I’m better at concrete stuff, like what my warhead is going to do against a Krag deflector.”
“Bullshit, Levy. I’ve been a Weapons Officer and I’ve worked in Intel and I can tell you that the two have more in common than you suppose. A great deal of Intel is just as precise and concrete and logical as the data you deal with as a Weapons Officer. There’s lots of hard data involved in both. It’s something you need to get a handle on. To be a well-rounded officer you’ve got to understand at least the fundamentals of every one of the Warship Combat Disciplines: Tactical, Weapons, Sensors, Intel, Countermeasures, and Stealth. And it doesn’t hurt to know a thing or two about Logistics, Engineering, Damage Control, Environmental Systems, and Personnel, either. If you want to rise to command rank, you’ve got to be a well-rounded officer.”
For Honor We Stand Page 25