FD&E Public Software Proposal

--To: All members of the SAE Fatigue Design & Evaluation Committee If you find the proposal below interesting please send me (aconle@ford.com) a reply expressing your opinion and any suggestions. I will condense & summarize any suggestions and return it to all in a couple of weeks.

Please do NOT attach this whole note itself to your reply, but only the bits you are interested in. (I'll just have to edit it out when composing the summary :-)
Al Conle

> Proposal:   Create an F.D.& E. Public Software (Task Force? Repository?)
>             (Acronym: FDE_PS ? )
> Objective: To create and test new fatigue analysis software and to make it
>            available to anyone who wishes to try it, or improve it. 
>    Step 1 :
>      Create or elicit from members initial "seed" software.
>      Place these routines on a FD&E website, along with source code and
>      GNU general public license (See below)
>      Allow members (and anyone else) to test & modify & re-post, if they 
>      wish, the routines with source code.
>    Step 2 :
>      When several variants of some software type have been created,
>      test, analyse, and evaluate for F.D.& E. re-posting, the best
>      variations, or recommend & sponsor further work to merge two or
>      more concepts into one routine. 
>    Step 3 : 
>      Go out and have a beer.
> Initial Seed Software Requests:
>   Note: all source files must be compilable, and presumably executable,
>         on a typical Linux operating system computer.
>   Also Note: Typical Linux setups include an Apache Web Server. The sites
>         are presently considered more secure than NT and many Unix
>         machines. 
>   We have:
>     *  RPC (MTS Corp. trademark) file binary to ascii conversion 
>        routine: 
>         rpc2ascii.f.txt 
>     *  RPC single channel extraction routine:  rpc_getch.f.txt 
>     *  RPC channel max/min extraction routine:  rpc_hilo.f.txt 
>     *  Standard FD&E Rainflow data file display routine
>     *  A sample program for converting a typical company data
>        format into an SAE Fatigue standard data file.
>         x2sae.f.txt   (Adapt it to convert your own)
>     *  An SAE standard file format for transfer of stress-strain 
>        hysteresis loops (
>         proposal  ).
>   We need:
>     1. Standard FD&E fatigue data file analysis routine for the 
>        calculation of the "strain-life" fatigue parameters.
>     2. Standard FD&E fatigue data file graphic display routine.
>     3. Standard FD&E Rainflow data file analysis routine.
>     4. Standard file format for "cyclic" stress-strain curves.
>     5. Conversion of Fatigue Parameters to a "digital" strain-life 
>        curve and a stress-strain curve.
>     6. Fatigue crack propagation analysis routine.
>     7. Routine to convert a Nominal or FEA elastic history to a local 
>        stress-strain history (uniaxial version). Some call it Neuber.
>     8. A multiaxial stress-strain cyclic deformation model to convert 
>        a rosette strain history to a multiaxial stress-strain history.
>     9. RPC time history display routine
>    10. Simple ascii file time-based point graphic display routine.
>    11. Fatigue history editing software.
>    12. A RT (Real-Time) Linux servo hydraulic test control routine.
>        (and a standard format for storing stress-strain loops).
>    13. A database for raw strain life fatigue data, with I/O links 
>        to standard FD&E file formats.
>    14. A sample conversion routine to translate fatigue data from a 
>        typical spread sheet to a standard SAE fatigue data file.
>    15. An FTP site for submission and distribution of SAE standard
>        fatigue data sets.  Could also be a site of "links" to such
>        data, thereby leaving the data in the hands of the original
>        contributor (and making less work for the rest of us :-)
>    16. Routines to calculate spot weld fatigue, post FEA.
>    17. Routines to calculate fusion weld fatigue, post FEA.
>    18. A standard format to describe proving ground test surfaces.
>        Other Suggestions:__________________________________________
>        ____________________________________________________________
>        ____________________________________________________________
> Distribution Synopsis: 
> Software should be made available to anyone who requests it under the 
> conditions of the GNU General Public License, sometimes called GPL or 
> "Copyleft". The license was developed by the Free Software Foundation. 
> By "free" it refers to freedom, not just cost.
>  * Original authors are allowed to retain the software's copyright
>  * Anyone can take the software and modify it or even base other
>    programs on it.
>  * Others are allowed to redistribute or resell the software, or 
>    modified versions of the software.  The software can even be resold
>    for profit, but in redistributing or reselling the software, however,
>    you cannot restrict any of these rights from the party you are selling
>      it to.
> Note: when one redistributes or sells the software, one must also provide,
>     at no cost, the full source code so that others can modify the
>     software and resell it if they so desire. One cannot hold back the
>     source of one's modifications.
>For more and exact information on the License system check:
>      http://www.gnu.org/copyleft/gpl.html
>and more about the Gnu project itself see: http://www.gnu.org