This problem is a lot trickier than it sounds at first.
Just checking simple distance formula's won't do the trick.... not even close!
If your starting goal is to learn fortran, you might experiment with less difficult geometry problems. The difficulty in this problem has only to do with...
I see no error codes.
You posted only a small piece of code with no useful information about the code.
There's not even a hint as to what kind of errors you are getting.
Errors while attempting to compile the code?
Errors while attempting to run code which has successfully been compiled?
We...
This is not actually a "code" question. YOU, the engineer, have to know what the term means in the context in which it is being used. If someone tells you that "The span length is xxx....", and you aren't sure exactly what dimension they are referring to, then, it is your responsibility...
Regarding your second option you were considering:
Model the footing as a continuous beam (assumes that simple beam theory is 'close enough').
Apply an Axial Load, Bending Moment and Shear loads to the footing at the "assumed" location where a column connects to the footing (middle of the...
You need to give a lot more information:
Is this a simple house type of structure, or a medium to large building or a bridge or what? What materials are used? What type of connections are used between columns and beams? What are the relative spacings of members relative to each other...
There's plenty of stuff on the internet concerning Large Deflection Theory.
If your project "actually" requires this type of analysis, you might want to find someone else to work with you on it. It's not something that you can just read about for a few hours and then expect to use in a...
Hmmmm. Maybe I'll apply for a PE license in Texas. Just to be safe, I can send them a large urin sample to go with the prints. You know... just get it out of the way now rather than wait for the regulations to be updated.
"Fingerprints" just to practice engineering??? Kind of reminds...
Try Debugging your model....
Delete or Cancel out ALL of the loads in your model (as I'm guessing you have all member self weights, etc, and probably other loads applied also).
Then... place a single concentrated point load on your model at some location, such that it will be incredibly easy...
There are LOTS and LOTS of online Fortran tutorials, for beginners and even for non-beginners.
As for management of variables, I HIGHLY suggest that you place an "Implicit None" statement at the top of each of your routines. Then, you must explicity declare every variable that your...
Pretty much what IRstuff said is the best I think. Or... rather, just have your fortran code print the data to a simple ascii text output file in a clean format ( ie. spaces between the numeric entries on each line of data ).
You can then very, very easily copy/paste that data into Excel...
For very fast continous beam analysis, you might want to check out DTBeam ( www.dtware.com ). It handles all kinds of supports, including springs, and it handles most load types, including axial loads. Non-prismatic beams are very easy to handle also as are hinges and all sorts of member...
I agree with Toog. To be safe... you may even want to develop a more standard/generic way of doing this ( ie, less subject to simple errors and easy to implement over and over again ).
Character*80 tmpchar
Real*8 tmpreal
: : : : : :
tmpchar = Liden(4:7)
Read(tmpchar,'(f80.0)')...
I did a web search. It seems that what you are referring to is McCaulay Notation. It appears at a glance to be just a way to referring to the differential equations that can describe the load/deflection of an element. If I'm not mistaken... it merely allows you to write one equation that is...
You can derive such formulas "relatively easily" yourself ( as long as your beams cross section is prismatic ). I've done several myself assuming that varying loads vary in a linear fashion. You can also do this for non-linearly varying loads. The algebra is just a bit stickier...
It sounds a bit like you may be attempting to use a C/C++ logic style for fortran. I don't think Polymorphic is necessarily what you want. In any case... I'm pretty sure you can create simpler code using a different style.
Consider developing a Type for each of your different particles...
