Observation on TNG: Peak Performance

[Howedar]

I happened to flip onto Peak Performance about 20min in. Worf (on Hathaway) was planning to send false sensor data over to Enterprise, to suggest an enemy ship was closing. Riker pointed out that they'd see (rather, not see) that the readings were false. Worf replied that the viewscreen would project an image of the fake ship on the viewscreen.

As far as I can see, this has some interesting implications. First of all, it immediately makes suspect any visual information we get from the viewscreen. I'd always assumed it was designed as a camera system with some sweet zoom capabilities, but it is clear that it is in fact CGI. We already know it can be fooled from Worf's idea, so anything we get from the viewscreen view is not very reliable.

You'll all need to bear with me on this second part. I actually have never seen The Die is Cast, so I'm not sure if any of this is valid. The visuals we got of a very non-molten surface - was this from the viewscreen or from an outside view? If it was from the viewscreen, it could be a side effect of the false readings they were getting from the surface, so dialog could in fact be more accurate in this case. If it were an outside view, there could have been an inside view that looked like the properly molten surface. This would not change what actually happened, but would explain some apparent Starfleet stupidity. If we saw a viewscreen as well as an outside view, none of this matters.



Has any of this been considered before?

[Techno_Union]

These are some very interesting points. It very well could be the viewscreen gave misreadings. Also, if the founders were in a liquid state then wouldn't the ripples just be like a wave and not the actual destruction of the planet. We also know that the planet was giving out fake reading about lifeforms so why could they not send out fake destruction readings?

On a side note, how did Worf make the Ferengi ship detect a fed ship when the enterprise did not detect the fake one? How did Worf get into their systems to do that?

[Howedar]

Trekrosoft systems.

[seanrobertson]

You'll all need to bear with me on this second part. I actually have never seen The Die is Cast, so I'm not sure if any of this is valid. The visuals we got of a very non-molten surface - was this from the viewscreen or from an outside view? If it was from the viewscreen, it could be a side effect of the false readings they were getting from the surface, so dialog could in fact be more accurate in this case. If it were an outside view, there could have been an inside view that looked like the properly molten surface. This would not change what actually happened, but would explain some apparent Starfleet stupidity. If we saw a viewscreen as well as an outside view, none of this matters.

Has any of this been considered before?

It's not been mentioned before to my knowledge.

As I recall, we see the fleet open fire in an exterior shot; then, the camera cuts to the viewscreen, and we see the "effects" on the surface.

Since I don't have that episode on hand, though, I can't verify that--sorry *frowns*. We might've seen an exterior shot of stuff hitting the planet immediately before things cut back to Tain's viewscreen (?).

More on this later. Bedtime!

[Gil Hamilton]

The description sounds like what is happening is the the Enterprises telescopes are wired to a computer which chews on the data, interprets it, and puts it on the video screen (rather than having the cameras having a direct feed). What Riker and gang did was exploit this by hacking the Enterprise and convincing it's Visual Data Processor into overlooking a giant starship. This has some interesting implications, if right.

For one, it indicates that the Enterprises computer network can be easily compromised by someone with a little know-how on how the system work and/or isn't paranoid about packets it gets. This is not without other incidents, like Ro tricking the Enterprise to overlook the fact that the Maquis were boarding her, because she knew what the encryption algorithims were. Which is odd, because even someone who designed the system shouldn't be able to get encryption keys simply by knowing how the system works, due to encryption keys being generated randomly. That means that there is a serious flaw in their network security. Or when the Iconian virus waltzed into their system via a video log, and no one noticed the information being transfered to the computer system until things started breaking, indicating that the Enterprise needs get a virus scanner, pronto.

Another thing is that the computer doesn't question discrepancies in data. For instance, if their telescopes are telling them that something (like a giant starship) is floating in front of them, but comes out of the Video Analyzer on the way to the viewscreen as empty space, there is something wrong. It doesn't go "Wait a second, something is definitely out there reflecting light into my cameras... but when I try to look at the data, nothing is there! Shit!" Naturally, a live video feed wouldn't have this problem.

Things to think about.

[Darth Wong]

You know, I always thought it worked that way as well, but now that I think about it, how do we know that the computer automatically does this "false visual projection" thing all the time? How do we know Worf didn't mean that he would hack the computer to make it do this? In which case it would not apply to any situation other than "Peak Performance"?

What benefit would there be to such an automatic false-projection system, particularly one that does not even notify the bridge crew whether it's displaying an optical image or a CGI one?

[Howedar]

No offense Mike, but your theory seems even more outrageous than mine. Either Worf took another system that was capable of perfectly mimicking a Warbird and then remotely wired it into the viewscreen perfectly (and we know it usually takes Starfleet engineers with direct access to systems at least several minutes to do such things), or he magically coded the system on the fly (which is patently absurd). Furthermore, Worf said that the computer would take the sensor data and then match it to a rendering on the viewscreen. He did not say he would undertake each operation independantly (something which would presumably take considerably more time).


As for benefit, I could see using it against obsolete cloaks that are invisible to the naked eye but not to advanced sensors. However I do agree that it is incredibly foolish not to depict CGI ships as such.

[Isolder74]

The thing that bugs me is they were able to pull off this trick on a completely alien ship with no problems at all.

The other is that this "wargame" is supposts to prove what?

That the Enterprise can defeat a ship that so outclasses it that it does not even have a duec of a chance. This was a watse of time. It would be similer to the matchup in the Movie Down Periscope except that was not at all serious! Now if they had whistled up the Galaxy or something similer that would have been worthwhile.

[Darth Wong]

No offense Mike, but your theory seems even more outrageous than mine.

Why? If you have sufficient access to the enemy's computer system to mimic every sensor reading appropriate for an approaching ship, why would it be so much harder to tell the computer to render the thing onscreen too?

Either Worf took another system that was capable of perfectly mimicking a Warbird and then remotely wired it into the viewscreen perfectly (and we know it usually takes Starfleet engineers with direct access to systems at least several minutes to do such things), or he magically coded the system on the fly (which is patently absurd).

Are you saying the computer does not have any built-in visualization capabilities? In case you hadn't noticed, your theory requires such built-in capabilities as well. The only real distinction is that you presume the computer does this automatically and without informing the crew in any way in the event of a mismatch between sensor data and optical data, while I think it more likely that someone has to tell the computer to do this.

Furthermore, Worf said that the computer would take the sensor data and then match it to a rendering on the viewscreen. He did not say he would undertake each operation independantly (something which would presumably take considerably more time).

Why would it take so much more time? How do you even know that the operations required separate instructions? For all you know, there's a built-in routine for combat simulations, so all you have to do is switch it on and tell it what to "draw" in both the sensors and viewscreens. The point is that "Peak Performance" does not mean that the computer must normally generate fake visuals based on sensor data.

As for benefit, I could see using it against obsolete cloaks that are invisible to the naked eye but not to advanced sensors.

Isn't that what the tactical display is for? It's not as if you can actually aim weapons based solely on the viewscreen visuals.

However I do agree that it is incredibly foolish not to depict CGI ships as such.

We should also note that in "The Neutral Zone", they were expecting to see visual distortions if a Romulan cloaking device were present. That would be rather odd if the viewscreen normally displays something other than an optical.

[The Kernel]

You'll all need to bear with me on this second part. I actually have never seen The Die is Cast, so I'm not sure if any of this is valid. The visuals we got of a very non-molten surface - was this from the viewscreen or from an outside view? If it was from the viewscreen, it could be a side effect of the false readings they were getting from the surface, so dialog could in fact be more accurate in this case. If it were an outside view, there could have been an inside view that looked like the properly molten surface. This would not change what actually happened, but would explain some apparent Starfleet stupidity. If we saw a viewscreen as well as an outside view, none of this matters.

We actually see both, there is an outside shot of the initial bombardment, then we see the brown clouds forming, then it switches to the Romulan Warbird's viewscreen which is an exact duplicate of what we saw from the outisde.

[Howedar]

Why? If you have sufficient access to the enemy's computer system to mimic every sensor reading appropriate for an approaching ship, why would it be so much harder to tell the computer to render the thing onscreen too?

Yes, I think it would. The capability would not necessarily be there. I don't see why it would be.

*EDIT* The only alternative I can see would be for simulation only (curse me for not reading your whole post before responding). I address that below.

Are you saying the computer does not have any built-in visualization capabilities? In case you hadn't noticed, your theory requires such built-in capabilities as well. The only real distinction is that you presume the computer does this automatically and without informing the crew in any way in the event of a mismatch between sensor data and optical data, while I think it more likely that someone has to tell the computer to do this.

We need to keep in mind that the people on the bridge did not know that the system was active. Considering that, I think it is more likely that it is built in and working continuously and not obvious instead of being manually activated and not obvious. I'd expect a status light or something to warn when the system was active if it weren't on all the time.

That's probably a bit much to ask from Federation interface designers though.

Why would it take so much more time? How do you even know that the operations required separate instructions? For all you know, there's a built-in routine for combat simulations, so all you have to do is switch it on and tell it what to "draw" in both the sensors and viewscreens. The point is that "Peak Performance" does not mean that the computer must normally generate fake visuals based on sensor data.

If there were a build-in routine for simulations, I would expect them to check that before raising shields and breaking off the simulated engagement with Hathaway. But they didn't, they immediately assumed that the Warbird was a legitimate hostile.

Isn't that what the tactical display is for? It's not as if you can actually aim weapons based solely on the viewscreen visuals.

Yes you can according to ST Bridge Commander

On that logic, I don't see any reason for showing an outside view on the viewscreen at all in combat.

We should also note that in "The Neutral Zone", they were expecting to see visual distortions if a Romulan cloaking device were present. That would be rather odd if the viewscreen normally displays something other than an optical.

I've not seen that episode since I was as tall as your knee and so don't feel qualified to comment on that point.

[Uraniun235]

The thing that bugs me is they were able to pull off this trick on a completely alien ship with no problems at all.

The other is that this "wargame" is supposts to prove what?

That the Enterprise can defeat a ship that so outclasses it that it does not even have a duec of a chance. This was a watse of time. It would be similer to the matchup in the Movie Down Periscope except that was not at all serious! Now if they had whistled up the Galaxy or something similer that would have been worthwhile.

I was under the impression that after the warp-jump, the Ferengi were picking the Hathaway as another Federation starship, not realizing it was the Hathaway. I may need to review the episode again.

The only good explanation I can come up with for the Hathaway exercise is that it's supposed to be helping to groom Riker for his own command, by making it another "test of character" sort of thing. If Starfleet were truly interested in honing the command staff's tactical abilities, they could have just rigged the Main Bridge and Battle Bridge for battle drills and had Picard and Riker go at each other with simulated Galaxys. Or, even better, use the fucking holodecks!

[Howedar]

No, it was another sensor ghost from Worf. It was explicitly stated to be such.

[Uraniun235]

God, what a contrived episode. They couldn't even go for the logical way to fool the Ferengi, no, the writer was so goddamn proud of his little trick that he had to put it in again.

[Howedar]

I agree wholeheartedly.

[Kamakazie Sith]

These are some very interesting points. It very well could be the viewscreen gave misreadings. Also, if the founders were in a liquid state then wouldn't the ripples just be like a wave and not the actual destruction of the planet. We also know that the planet was giving out fake reading about lifeforms so why could they not send out fake destruction readings?

On a side note, how did Worf make the Ferengi ship detect a fed ship when the enterprise did not detect the fake one? How did Worf get into their systems to do that?

He didn't. The Ferengi really did detect another UFP starship, just that there sensors weren't good enough to recognize that it was the same ship that they thought the Enterprise destroyed.

[Howedar]

No, I just watched the episode a few hours ago. It was Worf.

[Kamakazie Sith]

The description sounds like what is happening is the the Enterprises telescopes are wired to a computer which chews on the data, interprets it, and puts it on the video screen (rather than having the cameras having a direct feed). What Riker and gang did was exploit this by hacking the Enterprise and convincing it's Visual Data Processor into overlooking a giant starship. This has some interesting implications, if right.

For one, it indicates that the Enterprises computer network can be easily compromised by someone with a little know-how on how the system work and/or isn't paranoid about packets it gets. This is not without other incidents, like Ro tricking the Enterprise to overlook the fact that the Maquis were boarding her, because she knew what the encryption algorithims were. Which is odd, because even someone who designed the system shouldn't be able to get encryption keys simply by knowing how the system works, due to encryption keys being generated randomly. That means that there is a serious flaw in their network security. Or when the Iconian virus waltzed into their system via a video log, and no one noticed the information being transfered to the computer system until things started breaking, indicating that the Enterprise needs get a virus scanner, pronto.

Actually it's more incompetence on Picards or the security officers part for not changing the access codes. Also, why would you think Worf is someone with a little know how? What if he is someone the knows the very intimate details of that system. Also, Ro sent an imbedded security code so the Enterprise allowed her to take the medical supplies they never actually boarded her.

Another thing is that the computer doesn't question discrepancies in data. For instance, if their telescopes are telling them that something (like a giant starship) is floating in front of them, but comes out of the Video Analyzer on the way to the viewscreen as empty space, there is something wrong. It doesn't go "Wait a second, something is definitely out there reflecting light into my cameras... but when I try to look at the data, nothing is there! Shit!" Naturally, a live video feed wouldn't have this problem.

Things to think about.

You make the assumption that they are actually video cameras and not some other form of advanced technology, it is sci-fi afterall.

[Kamakazie Sith]

No, I just watched the episode a few hours ago. It was Worf.

Then what was the point of faking the destruction of the Hathaway?

[Howedar]

Give the Ferengi no reason to stay, I think.

[Kamakazie Sith]

Give the Ferengi no reason to stay, I think.

Indeed, after they destroy the Enterprise there would be no reason to stay. If that's how it actually went then that was a stupid episode. However, I'm going to double check it just to be sure.

[Howedar]

Just watched it tonight. That's how it went.

[Xon]

Another thing is that the computer doesn't question discrepancies in data.

Actually, Trek computer systems are incredible dumb. Despite their processing ability, there isnt much "smartness" encoded into the system.

This is evident due to the utter lack of workable, smart, safeguards.

Paradoxically, individual subsystems appear to be fairly smart about how they do things. They look to be really really good at symbol manipulation.

Also knowing what the encryption algorithims were would allow you to back trace who used them(since they do have some type of user monitoring), and then use the internal sensor logs to read the encryption keys when someone entered them.

But trek security is just shockingly bad. Makes a win95 machine on the internet with no patches look secure.

[Robert Walper]

Has it been considered that Worf may have utilized a common Trek technology built within starship systems?

For example, the system he may have "hacked" could very well be a system used by Federation ships to communicate with eachother. For example, a Federation starship may have something interesting on it's viewer/sensors that another ship is too far away to view or detect. The first Federation starship sends a signal to the other so it can evaluate what the other one is encountering.

It should be noted that once Picard had Data change the "codes", Worf was no longer able to utilize this deception. This heavily suggests this is a system the Enterprise didn't take into account being used against it...after all, Worf should be familar with it onboard the Enterrpise, and your enemies aren't expected to have Federation codes on hand like that. You do not typically fight enemies who were just onboard your own ship a few hours ago, and who are intimately familar with it's systems and codes.

In reference to Worf playing the trick on the Ferengi, this may merely suggest they have similar a system in place, but it was either unguarded or poorly so. But that would be a weakness of the Ferengi, not Starfleet(which frankly, isn't surprising given the Ferengi's apparent complete lack of any significant power(other than economic))

[CDiehl]

I think the purpose of the exercise was to test how Picard and Riker handle a mismatch. I assume the exercise we saw was to be the first of several between the Enterprise and the Hathaway, with Picard and Riker switching places from time to time. I think the idea of Riker going first and having to repair the Hathaway was a test for him personally, since Starfleet was definitely grooming him for a promotion. That would explain why they gave him that old junker instead of separating the Enterprise or dispatching a better ship.

The choice of the Enterprise for this exercise seems reasonable to me. First, despite Picard's comments in this episode, Stafleet is the Federation military, and should a superior opponent attack the Federation, Galaxy-class ships would be the ones most likely to meet it. Second, the Enterprise's main job is exploration, and it's possible they will encounter a superior, and hostile, ship, so it's practical that they practice for it. Third, if there is a war, and the Enterprise is destroyed, Picard and Riker, if they survive, would probably be given command of smaller ships, and they need some experience commanding small ships against large ones.

Finally, an observation. Starfleet seriously needs to establish an opposing force like the US Army has. They also need to hold their exercises well inside Federation space, so enemy ships can't show up and interfere.