F.D.+E. Experimental HTML Fatigue Database

Fatigue Design and Evaluation Committee
Web Page: https://fde.uwaterloo.ca/Fde/Materials/dindex.html


A Note on the Fitted Curves and Calculator files in database
Plot compare fatigue datafiles (plotStrainLife.txt) using gnuplot.

An Analysis Routine (also Open Source) to use this data
There are a number of more "sophisticated" ways to organize such a database structure, and the author has created several such versions in the past, but although its fun programing, it was basically a waste of effort. Experience shows that what 99% of the fatigue/durability users want is a data file/plot for the material name that they have, and, if there is no direct match, a nearest or "best" fit. No one ever uses the search options for values of Su (ultimate Stress), Sy(yield) etc. This is from an observation of hundreds of verbal requests by engineers over a period of more than 25 years at Ford Motor Co. The best policy in a fatigue related database is to keep things very simple. The following list structure lets a user achieve the same search objective. When no exact match can be found for the requirements, the subsequent search for "next best or equivalent material" can be fairly difficult to solve without expert help.

Database Structure:

A very simple form of fatigue material property database can be constructed by linking from an index file, such as this one, to a tree of other folders and files. You are welcome to submit a list of your own posted files, hopefully in the same format, for addition to the links posted above.
Here is how the "folder" or directory/file structure is organized:
(uses the "tree" command)  Abridged version:

|-- Steel-|
|         |-- SAE1045
|                   |-- sae1045.html
|                   |-- SAE1045_203BHN_OL.png
|                   |-- overload_disc.html
|                   |-- sae1045_187BHN.html
|                   |-- sae1045_203BHN.html
|                   |-- sae1045_203BHN_CA_Bonnen-Chern.html
|                   |-- sae1045_203BHN_OL_Bonnen.html
|                   |-- sae1045_277BHN.html
|-- Alumcast
|         |-- A356
|         |          |-- a356-T6_sae_sp760.html
|         |          `-- a356.html
|         `-- alumcast.html
|-- PM
|         |-- f488
|         `-- pm.html
|                    |-- f488.html
|                    |-- lqq1-1.html
|                    |-- lqq1-2.html
|                    |-- lqq1-3.html
|                    |-- lqq2-3.html
|                    |-- lqq2-4.html
|                    |-- lqq2-5.html
|                    |-- lqq3-3.html
|                    |-- lqq3-3_1_1000.gif
|                    |-- lqq3-4.html
|                    |-- pmqq500x.gif
|                    |-- pmqq500xb.gif
|                    |-- pmqqsample.gif
|                    `-- std488life.html
|-- SSteel
          |-- AISI_304_stainless
          |          |-- aisi304.html
          |          |-- aisi304ss_hard.html
          |          |-- aisi304ss_soft.html
          |-- AISI_310_stainless
          |          |-- aisi310.html
          |          |-- aisi310ss_soft.html


In each folder above, such as "PM" or "Steel" there is at least one viewable html file that points to the other folders or files below it in the tree structure.
For example in the folder "Materials" there is the file that you are presently reading (dindex.html) and the sub-directories or folders "PM", "Steel", and "Alum" etc. In the "PM" folder there is an index type file called pm.html and a folder for each data set (e.g. f488).
In each data set folder there is an index file (I have used the strain_life file itself to "point" to the other files) and all the stress-strain loop, micrographs, tensile curves, etc. for that fatigue test set. Because the files are all html compliant it is easy to incorporate "different" data formats, as might occur if one were to save fatigue information about composite material fatigue or wanted to add crack propagation data, for example.

If you wish to make a copy of all the files in your own database, to get a start, the Linux program "wget" is very helpful. with the -r option you can get recursively the complete directory tree. At this point you can then expand the html files to insert your own. There are many options to the wget command. Check the "man wget" pages on a Linux machine. The typical wget variation you will probably use is:

   wget -rv --random-wait -p -np -nH https://fde.uwaterloo.ca

#  where
#          -rv    recursive(down all directories)  v= verbose
#          -p     load all files that make a given page displayable
#          -np    no parent directories.  While following the tree
#                 limbs do not ascend into the parent directory
#          -nH    no host name in the directories

Note: The "end-of-line" character(s) are different in a Windows and a Linux/Unix system. This can cause problems if you are running the software on your own machine. The files on this site are in Linux/Unix format. You may wish to learn a bit about the dos2unix and unix2dos commands, or use a text editor that is less sensitive about the line terminators, like "vim" or "gvim" available for both Linux and MSWindows.