Looks like this holds promise due the efforts of several hard working folks and that the initial tasks are well underway.
So I'll jump ahead to consider what testing of the simulator will be done. As gmat and others of you involved in software development are aware, unit testing, component testing, and integral testing need to be done. From my experience, these seem to go by different names at times depending on the application but I'm sure the comp sci folks must have developed their own nomenclature by now. Someone should probably redefine those for us if the comp sci names are different.
Unit testing is most likely already being due where for example one would make sure the interpolators do what they should.
Component testing should be fairly straight forward in the simulator should be able to reproduce the behavior of the various components, rads for example, based on driving the input and air flow.
Integral testing may be more difficult.
BillA, do you have test results for a system that can be used? Need all components defined plus measurements of system behavior, hopefully with flow rate, cpu (test block) power, etc. varied across a reasonable spectrium. Would be really nice if the states of each component were /measured/available during the testing of each parameter set but I don't know if that is the norm or not.
Anyway, just some initial thoughts on the subject that will need further discussion.
