Re: Re: Stress calculation

>Problem #1: finding the software, if it exists. It neednt be a piping
>program; just one with a compatible I/O, database, processing format.
This is the easiest thing. Plenty of simple FEA programs around. That can handle piping

>Problem #2: finding members who have the time to commit and the
>patience to wait for a usable solution.
Harder, because the members who have the time may not have the necessary expertise.

>Problem #3: Finding a coordinator to decide the architecture, split
>it up,farm it out and then pull it all together again .
Hardest. Deciding on architecture and needed features, especially people who don't know about programming, is a nightmare. Everyone wants everything and they want it now. You'll need to take a general

>I am quite sure some clients would be absolutely
>horrified to see the amount of absolutely erroneous crap such
>programs can produce.

The program produces what it's told. Crap production isn't limited to computer software. The best crap production comes from people trying to sell stuff. Nothing like combined ignorance and greed to provide super crap. You're right of course, but you deal with computerized crap like a chicken deals with a cow pie--sort the edible stuff out and enjoy... ;->

>I was quite frankly appalled. Beautiful printouts, however. Apart
>from the spikes, which apparently dont matter.
So what do you do when you see spikes or static in instrumentation. You sort out what made tham, and why then you decide whether you ignore them or pay attention. Same for software ;->

Christopher Wright P.E.    |"They couldn't hit an elephant at
chrisw@skypoint.com        | this distance"   (last words of Gen.
___________________________| John Sedgwick, Spotsylvania 1864)