• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

Computers are SOO big - V Clunky

Originally posted by Uncle Bob:

>Page 41. A Maneuver program takes one "space". Jump 1 and Navigate each take 1 space.

Obviously, two is not one but I will defend it as "roughly equivalent".

The Generate program to produce a jump flight plan only takes one space. So much for a terabyte database and a supercomputer.<

Here's an example of how the Generate, Maneuver, Navigation and Jump programs are used on a TL 9 jump 1 ship, with a Model 1 computer.
The ship is on the surface, maneuver and generate are in the computer. Generate produces a flight plan once the final destination is input by the pilot. Ship maneuvers to jump-point and stops maneuvering. The jump 1 program replaces the maneuver program, the generate program creates a jump flight plan in conjuction with the jump program. The generate program is removed and navigation program is used along with the jump program to control the jump.

The generate program does not create jump flight plans without the jump program. The actual mathematics involved to write a program to generate a Newtonian physics flight plan may be simple enough for a Commodore 64 to do but the generate program and it's requisite math should not be the standard of what "1 space" is. Same for the maneuver program.

How much data, equations, etc is in the jump program? A lot. As a comparison here's my example.

The library program contains local information. How much is dependent on the referee but I consider it to have as much info, references, pages as the entire internet of today. All of the info stored in those multi-story server farms, etc. condensed into one space. When referenced by a PC the PC has to navigate the immense database to find the desired info. Built in navigator and search engines ease the task somewhat.
The library program also contains information about surrounding systems. The closer and more important the system the more of it's data is included in the library program.

Now the jump program is similar in depth [IMTU]. It has to account for jump physics not only for the system the ship is going to but also surrounding systems [of a radius equal to jump number] as well due to gravitational influences, etc. The jump program has to have derived equations and data for these permutations. Thats a lot of info, much more than the few scores of equations to maneuver a starship around a stellar system.

The derived equations in the jump program are simple but jump physics is difficult. As an example try to use a modern computer and research to derive equations [like basic geometric shapes] simple enough for a elementary student can understand and operate to find the solution of complex calculus and differential equations [about as far as I got]. Condense calculus mathematics down to four equations even a child can use to solve any given calculus problem. That's the difference between jump physics and our present RL physics model.

IMTU the generate, maneuver programs might actually use only 0.2 spaces [or such] but is saved onto a standard [1 space] size "disk" for ease of use in a standard "disk drive" built to handle the intensive jump program.

If we go much further than this then I'll have to resort to the hand wave - and go with option 1, that's the rules, live with it.
 
Originally posted by trader jim:
guess what.....one of my computers is going to blow.....can you find it in time?????...... :eek:
alpha.gif
...jim...
alpha.gif
...i can feel my mind going...
alpha.gif
...jim...
alpha.gif
...would you like to hear a song?...
alpha.gif
...I know a song...
alpha.gif
...row, row, row, your boat....

toast.gif
 
Originally posted by RandyT0001:
Originally posted by Uncle Bob:

The Generate program to produce a jump flight plan only takes one space. So much for a terabyte database and a supercomputer.<
Yet the rest of your post goes on to support my suggestion. I would think that a TL 9 on space Comp would be comparable to a supercomputer and a terabyte database would not take up much space. As a matter of fact, the spaces of a computer program would be more data than program code. Your explanation of the library program backs this up.
 
Colonel, the problem with your argument is that a Generate progeram can be run on a 1940s computer much smaller than Eniac.

This is NOT a supercomputer. Apparently once we figure out how to do it the number crunching should be easy.

And I agree, a 52 cubic meter TL9 computer should be a Teraflop super computer. But the computer-3 is outclassed by a 1975 PDP-12 using Travellers own definitions of computer power.

Nurd-Boy, NASA in the early 70s bought time on the Rice University computer, an IBM 360, which had about the power of a 486 running Linux. And the Apollo on board computer was capable of navigating on its own if radio communication were lost. The reason why they did all the computing on the ground in "Apollo 13" was because the on-board computer was powered down.

Also, "all the other functions of a ships computer" is your fantasy, and I challenge you to find support in the Traveller rules. Remember a Computer 1, a vacuum tube eniac could do everything expected of a ships computer and jump. And if a computer is completely destroyed the other functions are not affected, so they are not controlled by the ship's computer.
 
In my campaign, we have traditionally used what I would now describe as UBT-III (Uncle Bob Type III) comptuers.. slightly modified. Generally, we have been considering the computer tonnage itself to be electronic warfare/sensors/and battle statistics machines, and completely ignoring the Book 2 software rules. The rest of the machine is distributed around the ship here and there.

But then again, I started using TNE rules... which don't have software considerations. Robots (Book 8 IIRC) has guidelines of computing power at various tech levels. So does TNE.

It isn't a perfect solution, but it does let me keep the rules AND avoid the software / tonnage / what should a computer be able to do debate with my players. Pure fluff? Yep... but it works.
 
Just a thought about computers and bridges in CT....I have to agree with earlier posts that the tonnage of a Computer from Mark 1-9 was also including holo tanks, terminals, display panels, wiring, coolant, etc what have you. In addition the bridge tonnage included sensors, antennae, wiring, seats, etc. IIRC the description of the stateroom says that usually only about half of the 4 tons was actually in the room itself. The rest was in common areas. I usually thought that to include the bridge and engineering and computer equipment as well. I think there was also usually 1 ton that needed to be dedicated to fire control per turret. The only thing that I thought needed to be the actual listed tonnage was the fuel tankage. YMMV, these were all approximations.
Also the S/C with its 20 ton bridge spoke to me of a HUGE sensor array, but then it breaks down with the 100 ton free trader, so whadda ya want? I was a liberal arts major!
 
200 ton Free Trader, but yeah. The rules have a lot of ambiguity on how to translate tonnage into deckplans. This is probably a good thing, as it allows the designer to use a little imagination (or at least common sense). It can lead to absurdities, though.

IMHO the megatraveler and FFS rules added complexity and difficulty to the design process without leading to more realistic or even believable designs.

And there is nothing wrong with liberal arts degrees, I have a couple myself. (BS in History, MA in History)
The D.D. doesn't have to be a problen, either. :D
(One of my favorite Referees is now working for his ThD)
 
Originally posted by Uncle Bob:
[QB]
Nurd-Boy, NASA in the early 70s bought time on the Rice University computer, an IBM 360, which had about the power of a 486 running Linux. And the Apollo on board computer was capable of navigating on its own if radio communication were lost. The reason why they did all the computing on the ground in "Apollo 13" was because the on-board computer was powered down.

QB]
first trav. ships DO NOT have a 'houston' to monitor their systems, Those huge control rooms you see on the news footage would have to be on board and automated, meaning alot of computing, either through one massive point or multiple subsystems that are networked to a core for coordination....AAAND........

second, take a standard fusion plant, there IS NO WAY to control one without a massive amount of computer power regulating reaction rate,temperatures, output, etc... that alone means having its own deticated system and massive computing power just to keep it stable, wich in turn has to coordinate with the jump drives computer to regulate power draw, that inturn talks to the nav computer to know how much power is needed for jump-x (unless in your TU a jump-3 is 3, no further, no less, period)that also talks to the life support system to make sure it doesn't loose power....if you think about it, all the components are pretty much computer driven, and those 'peices' need to talk to each other and balance...unless you'd like to do it all by hand?..you know manually...have an engineer stationed 24-7 at each component with the old sound-power-phone strapped around his neck (like in an old war movie) talking to each other?...and the coordination center for all these systems?..hmmm, lets see, is jojo the cybermonkey?...noooo, its the ships computer....

its not 'fantasy'. It's a realistic train of thought and reasonable...a ship isn't an office building, the devices onboard are not copy machines, they are complicated, sensitive needing the kind of control/monitoring only a deticated computer can provide. Then all those devices need to operate in balance to get a vessel to do something other than be a paperwieght all the while making sure the crew stays alive.....

that returns us to my main argument in comparing computers to 486's, ibm uptysquats, SCOPE, SCALE..people think to small and not realize what goes into making a ship work....

sheeeeeeeeeeeez.........
omega.gif
 
QB][/QUOTE]

sheeeeeeeeeeeez.........
omega.gif
[/QB][/QUOTE]

besides, lets not forget the time period the original game game out in....projected sizes BASED on (then) current technology was reasonable assumations.
 
besides, lets not forget the time period the original game game out in....projected sizes BASED on (then) current technology was reasonable assumations.[/QB][/QUOTE]
 
Originally posted by Nurd_boy:

First trav. ships DO NOT have a 'houston' to monitor their systems, Those huge control rooms you see on the news footage would have to be on board and automated, meaning alot of computing, either through one massive point or multiple subsystems that are networked to a core for coordination....AAAND........

My point was that the Houston contriol center was not needed for Apollo navigation. A hat-box sized computer (pre-integrated circuits) and a sextant could do that quite nicely, thank you. Houston Control was the equivalent of dozens of watchstanders staring at single dials. Few had any influence on the mission. That huge center had limited computer power as they were renting time on the Rice University computer there in Houston.

second, take a standard fusion plant, there IS NO WAY to control one without a massive amount of computer power regulating reaction rate,temperatures, output, etc... that alone means having its own deticated system and massive computing power just to keep it stable,

You are making a reasonable assumption about the fusion power plant which is not explicitly supported by cannon. The power plant may use a confined plasma, but if it does it uses local processors because it continue to function if the shps computer is destroyed.

wich in turn has to coordinate with the jump drives computer to regulate power draw, that inturn talks to the nav computer to know how much power is needed for jump-x (unless in your TU a jump-3 is 3, no further, no less, period)that also talks to the life support system to make sure it doesn't loose power....if you think about it, all the components are pretty much computer driven, and those 'peices' need to talk to each other and balance...unless you'd like to do it all by hand?..you know manually...have an engineer stationed 24-7 at each component with the old sound-power-phone strapped around his neck (like in an old war movie) talking to each other?...and the coordination center for all these systems?..hmmm, lets see, is jojo the cybermonkey?...noooo, its the ships computer....

Once again that does not require a central computer. Local processors can tell the power plant what is needed and the power plant's own processors will supply. You don't need a central unit to do that, and the fact that the power supply and life support continue to work when the computer is destoyed proves that the Ship's computer is not involved in these functions.

The its not 'fantasy'. It's a realistic train of thought and reasonable

It is a reasonable train of thought which is not fully supported by canon. As for comparing computer power, canon defines a simple, well understood computer task as taking one "space". All my comparisons are based on this fact in Book 2.
 
In one of my traveler games, there were big problems with a couple of players because they "knew" that computers would be ridiculusly prowerful by this era. When they found computer rooms on their deckplans they were aghast. When I forced them to make piloting rolls etc etc.

At the risk of getting into necromancy I had a little brainwave about this a while ago.

It's better to think of a computer as a whole avionics package including sensors and control infrastructure. Perhaps controlling a jump might require a quantum computer - you can make up any schitck behind this that you want. The nature of quantum computers is such that they're quite large and clunky because they need a substantial cryogenic cooling unit and at least quad redundancy (including the cooling units) for aerospace usage.

Combine this with sensors and their associated antennae, redundant internal network looms within the ship, redundant control interfacing hardware, reserve batteries for a UPS (also quad redundant), milspec consoles and the other gubbins that go with such things - plus maintenance space to get at them - and you can make them up to being quite a substantial complex of hardware. The same thing can apply to bridges.
 
Nice bit on the quantum part.

I took this on in my IMTU thread, basically I explained the LBB2 computer pricing and performance as being extremely fault-tolerant and dreamy support levels, and dropping in prices in orders of magnitude but losing licensing for carrying passengers and ultimately freight, increasing instability under duress and bad/non-existent support for swapping in/out starship hardware.

So ya you can run your ship on a PC equivalent but you'll be running under market/illegal rates and find yourself without a working system at the worst possible times.
 
You could also just rule that integrated circuits and dense memory chips are highly susceptible to the weirdness of jumps, so most of a computer is heavy shielding (lots of metal, plus a giant magnetic bubble).
 
You could also just rule that integrated circuits and dense memory chips are highly susceptible to the weirdness of jumps, so most of a computer is heavy shielding (lots of metal, plus a giant magnetic bubble).

Which opens up SDBs/monitors to the use of far less massive computers, granting them a further tactical advantage.
 
You could also just rule that integrated circuits and dense memory chips are highly susceptible to the weirdness of jumps, so most of a computer is heavy shielding (lots of metal, plus a giant magnetic bubble).

Or that semiconductance differs, so you need to use vacuum tubes.
 
Back
Top