The 200 branch go to: Many years ago,/in the days of punch cards and mainframes,/ I wrote, /in FORTRAN/ a complex radar system modeling/simulation tool to evaluate radar system designs in a variety of environments. The program used a large variety of signal generation and signal processing modules to predict how designs and design changes would change performance.. The program generated simulated radar returns from simple and complex targets (things we might want to see), clutter (the things in the environment we didn't want to see) and jamming (signals the enemy might generate to make things difficult) for radar configurations, and dynamics. (What comes out of radar antennas is dependent on the relative dynamics of anything that might be reflecting radar energy as well as antenna design and pointing. )
There were modules to generate the various radar returns for various conditions and designs. There were also modules to model the various signal processing elements in radar receivers, etc. The program flow was controlled by an integer array telling it what to do next after if finished each step using a 200 branch go to statement. It required a good understanding of radar systems and signal processing to run this program. It was used to aid the design of a number of radar and sonar systems. Thirty years after I left that company somebody told me they just found a bug in the program. They were still using it. Craig ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
