This contains attempts to create BEAM FEM model.

I have started a <a href="https://c3.nasa.gov/dashlink/projects/47/blog/">Blog</a> to discuss this... please put your comments there and I will attempt to keep everything updated.  <a href="https://c3.nasa.gov/dashlink/static/media/dataset/Emails_AB_CDW.pdf">Correspondence between A.B. and CDW is provided to assist in developing NASTRAN Beam FEM  <br>
(through July 1)(PDF)</a>

The original data provided by Alexander is shown in
<a href="https://c3.nasa.gov/dashlink/static/media/dataset/model_input-extract.txt">model_input-extract.txt
</a>

Additional files loaded July 21, 2011:<br>
<LI><a href="https://c3.nasa.gov/dashlink/static/media/dataset/WingMassLength_Comparisons.xls">Comparison of Wing Masses, and Lengths, and Mass calculated from provided densities, and lengths</a>
<LI><a href="https://c3.nasa.gov/dashlink/static/media/dataset/Compare_W_eig_20110720.xlsx.pdf">Comparison of Model Masses and frequencies</a>
<LI><a href="https://c3.nasa.gov/dashlink/static/media/dataset/LP_CDW_emails.pdf">Emails dealing with offsets for bending and center of mass (between Proctor and Wieseman)</a>
<LI><a href="https://c3.nasa.gov/dashlink/static/media/dataset/BeamProperties_modrho.xlsx">Spreadsheet that contains element beam properties</a> used for debugging
<LI><a href="https://c3.nasa.gov/dashlink/static/media/dataset/OneElement_TipLoad.bdf">One element beam model to check beam stiffnesses</a>
<LI><a  href="https://c3.nasa.gov/dashlink/static/media/dataset/Emails_20110728.pdf"> Email correspondence as of July 28, 2011</a> - includes a cursory check of the bending and center of mass locations.  
<P>
<TABLE BORDER = 1>
<TR>
<TD>X1,X2,X3</TD>
<TD>Inertias/Kappa</TD>
<TD>Mode 1 Freq, Hz</TD>
<TD>Mode 2 Freq, Hz</TD>
<TD>File name (ms103_beam_)</TD>
</TR><TR>
<TD>1,0,0</TD>
<TD>modified*</TD>
<TD>26.37854</TD><TD>83.69360</TD>
<TD><a href="https://c3.nasa.gov/dashlink/static/media/dataset/ms103_beam_100_modi_ccs_o1_k_nsm1_nm1.bdf"> 100_modi_ccs_o1_k_nsm1_nm1</a> 
</TD></TR><TR>
<TD>1,0,0</TD>
<TD>modified*/Beam properties modified</TD>
<TD>26.37855</TD><TD>83.69344</TD>
<TD><a href="https://c3.nasa.gov/dashlink/static/media/dataset/ms103_beam_100_modi_ccs_o1_k2_nsm1_nm1.bdf"> 100_modi_ccs_o1_k2_nsm1_nm1</a> 
</TD></TR><TR>
<TD>cosa,0,-sina</TD>
<TD>as provided</TD>
<TD>26.37949</TD><TD>83.69533</TD>
<TD><a href="https://c3.nasa.gov/dashlink/static/media/dataset/ms103_beam_ca_0_nsa_ccs_o1_k_nsm1_nm1.bdf"> ca_0_nsa_ccs_o1_k_nsm1_nm1</a> 
</TD></TR><TR>
<TD>cosa,0,-sina</TD>
<TD>as provided</TD>
<TD>26.37949</TD><TD>83.69533</TD>
<TD><a href="https://c3.nasa.gov/dashlink/static/media/dataset/ms103_beam_ca_0_nsa_ccs_o1_k_nsm1_nm1.bdf"> ca_0_nsa_ccs_o1_k_nsm1_nm1</a> 
</TD></TR>
</TABLE>
<BR>
<P>
<P>
Below are frequencies with different permutations of 
<LI> X1,X2,X3 definitions on CBEAM card <br>A) - 1,0,0 or <br>B) ca_0_nsa = cos(alpha),0,-sin(alpha) or <br> C)nca_0_sa = -cos(alpha),0,sin(alpha) on the beam card <br>
<LI> coordinate system (CCS) is converted from original
<LI> O1 indicates that offsets W1-W3 were included between the node and the shear center
<LI> nsm1 = beam density is unchanged and includes the non-structural mass
<LI> nsm2 = non-structural mass is separated from the beam mass density
<LI> nm = calculation of offset N1,N2 for beginning and end of each beam segment is performed - different ways depending on the index
<LI> modi = inertias provided by Boucke were modified by the alpha.  
<LI> _k_ = kappa(K1,K2) were included in the model - values provided by Boucke (A.B.)
<LI> _k2_ = kappa(K1/K2) modified along with beam properties per equations provided by A.B.
<P>


<TABLE BORDER = 1>
<TR>Description<TD></TD>
<TD>1st mode</TD><TD>2nd mode</TD></TR>
<TR><TD>Boucke provided frequencies</TD><TD>25.33879547</TD><TD>78.63642299</TD></TR>
<TR><TD>100_modi_ccs_o1_k2_nsm1_nm1</TD><TD>26.37855</TD><TD>83.69344</TD></TR>
<TR><TD>100_modi_ccs_o1_k_nsm1_nm1</TD><TD>	26.37854</TD><TD>83.6936</TD></TR>
<TR><TD>ca_0_nsa_ccs_o1_k_nsm1_nm1</TD><TD>	26.37949</TD><TD>83.69533</TD></TR>
<TR><TD>ca_0_nsa_modi_ccs_o1_k2_nsm1_nm1</TD><TD>26.3795</TD><TD>83.69762</TD></TR>
<TR><TD>ca_0_nsa_modi_ccs_o1_k_nsm1_nm1</TD><TD>26.37949</TD<TD>83.69778</TD></TR>
<TR><TD>nca_0_sa_ccs_o1_k	</TD><TD>26.37466</TD<TD>83.62444</TD></TR><TR>
<TD>nca_0_sa_ccs_o1_k_nsm1_nm1</TD><TD>26.33955</TD><TD>82.98219</TD>
</TR><TR><TD>nca_0_sa_ccs_o1_k_nsm1_nm2</TD><TD>26.3778</TD<TD>83.67184</TD>
</TR><TR>
<TD>nca_0_sa_ccs_o1_k_nsm2_nm1</TD><TD>26.3452</TD<TD>83.07531</TD></TR>
<TR>
<TD>nca_0_sa_ccs_o1_k_nsm2_nm2</TD><TD>26.37785</TD<TD>83.6722</TD>
</TR><TR><TD>nca_0_sa_modi_ccs_o1_k_nsm1_nm1</TD>
<TD>26.33953</TD<TD>82.98429</TD></TR></TABLE>
<P>


Matlab code has been requested that reads the input deck.  This code also does some debugging and calculation.  The disclaimer is that it isn't easy to read.  If you find a coding error please let me know.  There are two codes - one for reading that also does some distance calculations and then a code that writes the BDF file.