Hmmmmm.
Of course this whole thing vexed me even in the early 80s.
I'm thinking universal computing maker for ship computers to personal comps.
Space Opera really had the workable system with the complexity scale, and the T4 CSC had that computer problem-solving vs. time chart as well.
I'm thinking the following variables-
- Complexity-Model Number
- Capacity=Complexity squared
- Reliability (4 grades, Consumer/Business/Avionic/Critical)
- Speed/time for solving X complexity, realtime solutions like autopiloting and gunnery solutions are .1s, analysis may take hours or weeks, and something like jump requires 10m
- Volume/weight, 2000kg per dton
- TL gives miniaturization/cost/power reduction
Each variable increases or lowers cost by a factor of 10. Base Cr10xC
2 per kg, Speed 1 is 100s per even complexity number. Base 10x Model# dton size.
So example for reliability, a TL6 Model/1 Consumer computer is Cr20000, each level up is Cr200000/MCr2/MCr20, no change to size for reliability
Usually somewhere along the line from TL6 to TL9, the typical starship Model/1 avionic level gets TL advantage sized down to 1 dton and gets specced to Speed 3, one advantage per TL. Cost remains the same unless it is the advantaged one- so a TL9 Model/1 Speed 2 avionic level could be dropped from MCr2 to Cr200000 instead.
Speed maximum is model number or model +1 per next TL. So Model/1 can get Speed 3 at TL9, Speed 4 at TL10 etc. Speed increments in .0001s, .001s, .01s, .1s, 1s, 10s, 100s, 1000s, 1h, 10h, 1D, 10D, 1 M, 10M, 1Y. Roll (3d6/10) x increment value for randomization of time cost.
EP=C
2xSx.01. C is complexity S is speed. Speed baseline is 1m at Speed 1 at equal Complexity. I'm not happy with this formula, going to revisit. I'm making this up as of an hour ago.
Baseline system is TL9 Model/1 capable of Jump-1, I'm going with CT models to TL15/Model 9 starting at TL6 just cause. The CT/HG Model/1 put onboard most of the cheap freighters would be 1dton/2000kg (distributed inside the hull with a workstation or central hosted room), speed 3 so complexity 1 problems like a +0 gunnery shot is .1s resolution time, and no EP.
I think the original CT computers were predicated on the original USN shipboard computers and didn't have Moore's Law built in. In any event if we are doing TL6 USN computers we'll make those a business level computer and that gets us 1 dton at likely their reliability rate.
Each jump we'll rate at complexity 5 per Jn. Throwing a high complexity problem at a computer CAN be solved, but it will take large amounts of time, increment one time level per difference in model number vs. complexity problem.
So a complexity 5 J-1 at the postulated Speed 3 Model/1 is four levels of complexity above the computers rating. Figuring the basic complexity-1 Model/1 is at Speed 3 so .1s base speed, it increments up 4 levels 1s/10s/100s/1000s. The average CT turn is 1000s, so this works out.
For every level of complexity less the problem is then the model number, decrement by a level. So a Complexity-0 problem would be .01s.
So a big deal is figuring out how complex a problem is and then how much time involved. Really could amp up science/exploration games, or feeling the crunch of not having enough computer available Out There.
Advantaged gunnery and evade programs incur speed increment cost. Regular gunnery costs 1 speed increment which is within the complexity level, a +1 to hit gunnery program would cost complexity 2 and thus take our example Model/1 .1s computer to 1s per solution.
I would probably charge off that time to that character 'hogging the bandwidth', the computer frees up for other use and they likely would get away with no ill effect. If however the gunner used a +2 program it would cost 10s and maybe in that time an enemy fired at the pilot didn't have evasion control to use evade tasks/programs.
Reliability in CT terms is consumer takes 4 hits on the CT computer fail roll per single hit, business takes 2 hits, avionic takes 1 hit, critical takes hit only on 3- on 1d6. Model number reduction on the same schedule for HG.
I don't know how far I'd go with all this, just spitballing a way to define/make computers that makes sense.