Talk:PROSE modeling language: Difference between revisions

Content deleted Content added
I am a PROSE & FortranCalculus user for over 39 years!
Added usage examples from my experience
Line 23:
It also reads very promotionally, and all of the references appear to lead back to a single website (www.metacalculus.com), and I'm concerned that even meets the standards for notability. This appears to have been a minor language/system in the seventies, which is being used to promote a new commercial(?) product along similar lines. [[User:Rwessel|Rwessel]] ([[User talk:Rwessel|talk]]) 00:09, 14 January 2014 (UTC)
 
== Comments from a user of 39 years ==
I'm also involved in PROSE & FortranCalculus (FC) education. We have a website, http://fortrancalculus.info, for a textbook of applications that were solved via PROSE or FC. Many of these applications could NOT be solved without these calculus level languages ... especially those that use nested solvers. It is nice to have Joe's history notes as stated here even if they are above most of our heads. Some day these comments may help others make great strides in furthering computer software in the future. Just keep future software simple to work with as the goal. [[User:OptimalDesigns|OptimalDesigns]] ([[User talk:OptimalDesigns|talk]]) 17:23, 16 January 2014 (UTC)
 
I'm also involved in PROSE & FortranCalculus (FC) education. We have a website, http://fortrancalculus.info, for a textbook of applications that were solved via PROSE or FC. Many of these applications could NOT be solved without these calculus level languages ... especially those that use nested solvers. It is nice to have Joe's history notes as stated here even if they are above most of our heads. Some day these comments may help othersfuture developers make great strides in furthering computer software in the future. Just keep future software simple to work with as the goal. [[User:OptimalDesigns|OptimalDesigns]] ([[User talk:OptimalDesigns|talk]]) 17:23, 16 January 2014 (UTC)
 
A little history ...
 
From 1975 to 79, I taught PROSE to Engineers & Scientists that were time-sharing customers in the San Francisco Bay Area. The following cases are results from customers using PROSE:
1. Aertech had a thermistor problem: they build black boxes (for space) that need a thermistor that fits 3 data points. Each black box has unique data points. In order to solve the problem, Aertech allowed a technician up to 16 hours to solve for one set of data points using a (Basic or Fortran) software program. If not solved, the problem was pasted on to an Engineer. The Engineer had up to 2 hours to solve the problem. If still not resolved, the black box with hard to fit data points was dismantled and part of it was switched with another unit awaiting assembly.
 
A PROSE program was written to find the best solution. 5 thermistor problems were submitted as a remote-job-entry on our time-sharing system. The results took less than one minute to solve all 5 problems and all solutions used the fewest number of thermistors! A huge time-savings for Aertech!!!
 
2. Watkins-Johnson (WJ) had a similar problem: 2 Engineers were trying to fit a straight line to a curve and getting no where fast. I met these Engineers and couldn't get them to slow down and explain their problem to me. Finally, after a month, one sat down an explained their problem. Within 2 hours we wrote PROSE code to solve their problem. WJ won the government project do to the PROSE solution! (No other competitor was able to solve the problem!)
 
3. Memorex attended my class and hired me to write a PROSE program to build a Matched Filter for their disc drives. This required solving a generalized transfer function, H(s), that would take an asymmetric input signal and convert it into a symmetric output signal. PROSE coding was done in the first day (8 hours) of work. It was tweaked/modified over the next 2 years. Solutions were always optimal for the given PROSE code.
 
Here is ware I became aware of problems with having the right equations. This was solved in the frequency ___domain but with time it became apparent that the problem needed to be solved in the time ___domain. Without PROSE we probably would never have seem this ___domain problem. PROSE gave instant solutions to each modification thus got our efforts off coding and got us focusing on our math equations. This work was published in an 1981 IEEE journal and a copy is on my web site at http://fortrancalculus.info/example/pulse-slimming.html . The problem was put into an application for all to use ... see http://fortrancalculus.info/apps/match-n-freq.html
-----
 
PROSE and soon FortranCalculus are for Engineers & Scientists ... when they have some equations to solve. Write their (10 or 10,000) equations in Fortran code then add a FIND statement (and INTEGATE stmt. for Differential Equ.s) and add some begin & end statements and you have a the basic code for a PROSE program. Can't get much simpler! Perfect for Engineers & Scientists.
 
I trust this gives a better picture of what Calculus-level compilers can do for us non programmers. [[User:OptimalDesigns|OptimalDesigns]] ([[User talk:OptimalDesigns|talk]]) 18:03, 17 January 2014 (UTC)