Search results for query: *

AeroAero, Probably a dumb question, but are you using double precision in your Fortran code? Single precision FEM codes lose all significant digits for about 30+ degrees of freedom which seems to be about where you get to.

For existing buildings, use FEMA 356. There are guidelines for the evaluation of slab-column moment frames.

The floating point field width is 4, not 8, and so I think you need to change your format from f8.3 to f4.3. Acutally, I think for input the number of decimal places is subject to over-ride by the decimal point so f4.0 should also work.

I don't think the Fortran standard had a function for date and time until Fortran90 (DATE_AND_TIME intrinsic). Some suppliers of Fortran77 had extensions for the date and time but you'll need to find it in your compiler documentation.

mjs84, WRITE (ans, '(a, i3.3)') chr1, val1

Thanks, onlyadrafter, that is helpful advice. This is the sort of tip that it would be much better to know before starting all the dialogs and coding the macros!

I don't know of a fix for this, I use a workaround by calling GetOpenFile for a single file select within a DO construct. I add the filename to an array each time the user presses OPEN, and continue the DO until the user presses cancel. This is okay for a small number of files, not great if...

Sometimes our complex workbooks become corrupt and the size increases enormously. The only solution seems to be to select all sheets and copy to a new workbook, same with macros. This is painless except for dialog type sheets where the identification number of all objects changes, for example...

dilukshi, Probably a lot more than you need to know but you can download Base Isolation Design Guidelines from this site: www.holmesgroup.com/designguide Section 9.3 has some formulas for compressive stiffnes.

Thanks for the response, DanTex. I don't want to spend time on a very infrequent occurrence. I just recalled the memory models on old compilers required that words started on a segment boundary and wondered whether something similar, but undocumented, occurred with F95. The fact it allocates...

I'm using Lahey F95 v5.6. I have an allocate statement: ALLOCATE (xyzo (nface, 4, 3, 2)) which has never given a problem except when the value of nface is 43656. When it is this value, the program terminates. Changing the final dimension from 2 to 3 fixes the problem, a clumsy fix. Anyone...

You can download a base isolation design guide at www.holmesgroup.com/designguide.html which has a section on ETABS modelling.