Setup
Setup
Windows95/Windows98/WindowsNT/Windows2000/WindowsXP/WindowsVista
version. (Compaq Visual FORTRAN 6.6B compiler version)
1. These versions of Ruaumoko2D and Ruaumoko3D run directly under the Windows95,
Windows98, WindowsNT or WindowsXP operating systems. The plot save file
Ruaumoko.tmp is created in the users current directory and the scratch data-base file
Ruaumoko.scr is created in the directory defined by the 'temp' environment variable set
in the Autoexec.bat file in the users operating system. If the 'temp' variable is not
defined then the file is created in the users current working directory. This is of no
consequence on a single PC but if the program is being run from a server on a network
then the scratch file should be on the local hard disk and NOT on the server as the
network traffic will be very large and program speed will be greatly reduced. Both files
are deleted by Ruaumoko2D or Ruaumoko3D at the end of the analysis, but if they are
left in the directories because of an abnormal program termination this is of no
consequence as they will be over-written in the next analysis. However, as both
programs use the same file names do not run more that one version of the programs at
any one time. In the latest versions of the programs the scratch file is largely emulated
in memory, greatly speeding up the execution of the programs and though the scratch
file will be created, it it may not, in fact, be used unless the memory buffer defined is
exceeded in a very large analysis.
2. This version of Ruaumoko2D has a memory limitation set at 10000000 integers and
Ruaumoko3D has a memory limitation set at 63000000 integers. If greater
requirements are needed please let me know and I will arrange a version with more
memory. (Note: With the current Fortran Compilers 63000000 integers appears to be as
large a dimension that we can use without getting addressing errors from the compiler)
These amounts of memory appear to be adequate for all current users. The amount of
memory used in the analysis is shown in the statistics information at the end of the output
file as is the memory available. If the user wants to know the "wall clock" time taken for
the analysis this is available by subtracting the analysis start time output at the beginning
1
of the output file from the finish time output in the statistical information at the end of
the output file.
3. The versions of Dynaplot and Combplot have a memory limitation of 5000000 integers.
This should be ample for any plotting. For n lines there is a requirement of (n+1)*2
integers per plot point. The number of points is equal to the number of data saves to the
.res file and this is a function of the step interval KPA (or KPOST) and the total number
of time-steps in the Ruaumoko2D or Ruaumoko3D analysis.
4. The post-processor (.res) files created by Ruaumoko2D and Ruaumoko3D are binary
files as files created in an ASCII mode (and hence viewable on the screen) would be, at
least, twice the size of the binary files. However, there is an option to generate ASCII
post-processor files for Dynaplot, please see the file ASCII.pdf in the manuals
directory.
6. Programs Dynaplot, and Combplot are the same for both Ruaumoko and Ruaumoko3D.
8. Comments about ease of use and usefulness of the program are appreciated. Suggestions
for improvements to the programs or additional features are welcome. Similarly,
suggestions for improvements, additions or corrections to the manuals are greatly
appreciated.
===================
2
SETUP for Full License version
1. Copy the .pdf files from the root directory on the cdrom to get
It is suggested that these text files may be located in the same directory that will be used for
the executable files. It is suggested that the release notes (if present) be printed off and made
available to all program users or else copies be attached to the appropriate manuals.
Alternatively, the updated manuals could be printed from the Manuals directory.
The Fqwin.hlp file MUST be in the PATH for any of the programs to run.
It is suggested that the directory with these executable files be added to the system Path in the
Autoexec.bat file (or else to the users Path in the WindowsNT or Windows2000 operating
systems).
3
Notes:
1. The Ruaumoko2N and Ruaumoko2E etc. versions are not always provided.
2. The Ruaumoko2N and Ruaumoko3N versions are compiled with no graphics
routines and as such are more efficient for running in "Batch" mode as there is no
risk of a graphics call terminating the batch process. The data is unchanged from
that of the normal versions of Ruaumoko2D or Ruaumoko3D respectively.
3. Microsoft Windows does not check for arithmetic exceptions such as underflow
and it is possible to get problems with, in particular, underflow where the result of a
multiplcation or subtraction resulting in a number smaller than that which can be
represented by the precision of the computer. In this case the exponents are
modified as in the normal numerical operation but the number cannot now be
represented and results in a NaN (Not a Number). Once a Nan occurs in the
arithmetic they tend to propagate right through the solution making results useless.
The programs attempt to trap for NaN, and assumming that they are resulting from
an underflow where they can be found at no significant operational cost, they are
replaced by 0.0.
There are parts of the program where they would be expensive to trap for and there
may be cases where they may not be from an underflow, so the user should check
the output files for undeflows. The Ruaumoko2E and Ruaumoko3E versions
have exceptrions checking on, resulting in considerably slower execution but
avoiding the risk of NaNs occuring. If problems with NaNs do occur with
Ruaumoko2D and Ruaumoko3D then the problem could be tried with
Ruaumoko2E and Ruaumoko3E.
Most other computing operating systems automatically check for arithmetic
exceptions.
4. As a user, I prefer to run my analyses from the directory where I have my data sets
and where my output and post-processor files are generated. This is my working
directory. I keep all my executable files in one executable directory which is in the
system or user path. When I have finished with the analyses of a given structure and
I have plotted all the results I need, I delete output and post-processor files and
move the data files to a separate data directory from where they can be retrieved if
necessary at a later time.
4
SETUP for Student version
1. Copy the .pdf files from the root directory on the cdrom to get
It is suggested that these text files may be located in the same directory that will be used for the
executable files. It is suggested that the release notes (if present) be printed off and made
available to all program users or else copies be attached to the appropriate manuals.
Alternatively, the updated manuals could be printed from the Manuals directory.
The Fqwin.hlp file MUST be in the PATH for any of the programs to run.
It is suggested that the directory with these executable files be added to the system Path in the
Autoexec.bat file (or else to the users Path in the WindowsNT or Windows2000 operating
systems).
For the Stident version of Ruaumoko2D the memory limit is set at 30,000 integers and the
maximum number of joints, or nodes, in the structure is limited to 25 joints.
5
Notes:
1. The Ruaumoko2N version is not generally provided.
2. The Ruaumoko2N version is compiled with no graphics routines and as such are
more efficient for running in "Batch" mode as there is no risk of a graphics call
terminating the batch process. The data is unchanged from that of the normal
versions of Ruaumoko2D.
3. Microsoft Windows does not check for arithmetic exceptions such as underflow and
it is possible to get problems with, in particular, underflow where the result of a
multiplcation or subtraction resulting in a number smaller than that which can be
represented by the precision of the computer. In this case the exponents are
modified as in the normal numerical operation but the number cannot now be
represented and results in a NaN (Not a Number). Once a Nan occurs in the
arithmetic they tend to propagate right through the solution making results useless.
The programs attempt to trap for NaN, and assumming that they are resulting from
an underflow where they can be found at no significant operational cost, they are
replaced by 0.0.
There are parts of the program where they would be expensive to trap for and there
may be cases where they may not be from an underflow, so the user should check
the output files for undeflows. Most other computing operating systems
automatically check for arithmetic exceptions.
4.. As a user, I prefer to run my analyses from the directory where I have my data sets
and where my output and post-processor files are generated. This is my working
directory. I keep all my executable files in one executable directory which is in the
system or user path. When I have finished with the analyses of a given structure and
I have plotted all the results I need, I delete output and post-processor files and
move the data files to a separate data directory from where they can be retrieved if
necessary at a later time.
6
3. Copy the directory Quake to get the following earthquake accelerograms. It is suggested
that these be kept in a separate directory, i.e. C:\Quake to keep the path short as these
names will be required to be input each time Ruaumoko2D, Ruaumoko3D, Inspect or
Spectra are run and the longer the path name the more characters that have to be typed
with increased chance of error.
7
4. Copy the directory Examples to get the following example data sets. It is suggested that
these files be kept in a separate directory. These data files may be edited with Notepad
Example.dat (Ruaumoko2D)
Pushover.dat (Ruaumoko2D)
Frame12e.dat (Ruaumoko2D)
Frame12a.dat (Ruaumoko2D)
Frame12d.dat (Ruaumoko2D)
Frame12l.dat (Ruaumoko2D)
Frame12p.dat (Ruaumoko2D)
Frame12p.dat (Ruaumoko2D)
Frame12m.dat (Ruaumoko2D)
Pounding.dat (Ruaumoko2D)
Isolated.dat (Ruaumoko2D)
GraceKao.dat (Ruaumoko2D)
Exampl3D.dat (Ruaumoko3D)
Pushov3D.dat (Ruaumoko3D)
Frame3Di.dat (Ruaumoko3D)
Frame3Dm.dat (Ruaumoko3D)
Frame3De.dat (Ruaumoko3D)
Frame3Da.dat (Ruaumoko3D)
Sac3D.dat (Ruaumoko3D)
H2b.dat (Ruaumoko3D)
H3b.dat (Ruaumoko3D)
Wpe1x.dat (Ground displacement history for H2b.dat & H3b.dat)
Dz4203eq.dat (Simqke)
ReadData.txt (Description of example files)
5. Copy the RESULTS directory to get the following example results sets. It is suggested
that these be kept in a separate directory. These files may be deleted from this directory
once your use for them is finished. They may be re-copied from the cdrom at a later date
if desired.
8
6. Copy the ICONS directory to get the following icons that may be used to create shortcuts
to the programs on the desktop. It is suggested that the files themselves be kept in a
separate directory or in the same directory as the executable files.
Ruaumoko2D.ico
Ruaumoko3D.ico
Dynaplot.ico
Combplot.ico
Hysteres.ico
Spectra.ico
Inspect.ico
Simqke.ico
Pquake.ico
Fprint.ico
Rui.ico
ReadIcon.pdf
7. If desired you may copy the directory Source to get the following sample hysteresis
source file as an example if you wish to have your own hysteresis rule incorporated into
Ruaumoko2D, Ruaumoko3D, Inspect and Hysteres. You could write the subroutine
following the programming rules implied in the sample program, send it to me to integrate
into the programs and send you back the updated programs. It is suggested that these files
be in a separate directory.
(usage:
Condedit Sample.for Sample.f
then call compiler e.g.
F90 Sample.f
then delete system specific source file
Del Sample.f
you are left with compiled code and original non-system specific source file,
In my case, all done with a Fortran.bat file i.e.
Fortran Sample )
8. Copy the files from the directory Rui and then run Setup.exe to set up the Ruaumoko
User Interface program. See the ReadRui.pdf file in the Rui directory. It is suggested
that these files be kept in a separate directory. (This is only for Ruaumoko and not
Ruaumoko3D) This version of the user interface will be not be continued as the
performance and the ease of upgrading the program in Visual Basic has not been a
success. Work is underway to find an alternative means of creating a better user interface
program. It has also been found that the Visual Basic graphics has an unpredictable
behaviour on some laptop displays.
9
9. The updated manuals are in the directory Manuals as .pdf files. These may be
printed if required.
10
Release Notes
This contains features not covered in the user manuals for Ruaumoko etc. Copies should
be distributed to all users or appended to the user manuals
Dynaplot has always had the option of not actually plotting the graphs that it generates,
though they may still be saved for spreadsheet use with the Keep option.
To turn the graphics off follow the name of the post-processor file (the .res or .ras file)
with the word no in upper or lower case (or mixed case).
The user can also run the program using the $add option of the command processor of
having responses already prepared for production analyses. These are most easily
generated using the $log option of the command processor whilst running Dynaplot in the
conventional interactive mode. The resulting file can then be edited, with any text editor
such as Notepad etc. to form the input for later runs. Please see the example
Dynaplot.txt file in the Results directory on the cdrom.
Dynaplot now has an option to be run in batch mode. This is useful for researchers
running large numbers of parameter studies and who wish to use some features of the
post-processing. In the batch mode the graphics is automatically turned off.
To run the Dynaplot in batch mode the command Dynaplot must be followed by at least
3 arguments, i.e.
where
Output.wri is the name of the output file. This file contains the maximum and
minimum values of every line drawn in every plot drawn by Dynaplot. Any
extension may be used, i.e. .wri or .txt etc. This file MUST NOT exist or the
program will terminate.
Example is the name of the postprocessor file. This file MUST exist. The file will
have the extension .res or .ras depending on whether it is binary or ASCII post-
processor file. The extension is NOT supplied with the name.
Input.txt is the name of the data file containing all the command input for Dynaplot,
which is very similar to the example file Dynaplot.txt in the Results directory on
the cdrom. This file MUST exist.
The input data file is probably best generated during a conventional interactive use of
Dynaplot saving a copy of all the commands and data with the $log option of the
command processor. The only difference is that in the batch mode there is only one
output file and the Open option in Dynaplot works in a different manner. In the
interactive mode in Dynaplot when the Open option is used, the existing output file (if
not screen) is closed and the user is prompted for a new output file name. The user is
then prompted for a new post-processor file name. In the batch mode there is only one
output file, that given in the command line. If the Open option is invoked, the command
Open must be followed (on the same line) by the name of the new post-processor file.
11
The file name has the .res or .ras implied and the extension therefore MUST NOT be
applied.
12
RUAUMOKO and WindowsXP
There have been some difficulties with the graphics when running the Ruaumoko suite of
programs in the WindowsXP operating system. The programs run without any problems in
Windows95, Windows98, WindowsME, WindowsNT 4.0 and Windows2000. The causes of
these difficulties have been isolated during the past week and this note is being sent out to all
licence holders so that they can remove the problems. I am still investigating if there are
simpler fixes and also what to do where the files are located on Windows2000 servers with
WindowsXP clients.
This will remove the superimposed WindowsXP windows from the graphics. If the changes
to the properties is also done for the other executable files, such as Spectra.exe etc. it will
have no effect apart from, apparently, speeding up the execution of the programs.
The other graphics problem detected with all the programs in the Ruaumoko suite is that the
small font appears very faint grey, being very hard to see, and the printed graphs are no
better. On each computer running the programs the following needs to be done the fix the
problem.
• Go to Control Panel.
• Select System. You may have to change the View option to Show Details to find the
System option.
• Select Advanced.
• Select Performance.
• Select Settings.
• Un-check Smooth Edges of Screen Fonts.
• Click ok all the way back to Control Panel.
The small font is now back to full black characters to match the large font.
For more information, go to Help, topic Screen Fonts, then Making them more readable.
Another solution, used in many of the computer laboratories in the University of Canterbury
is to change the Screen Properties to use Windows Classic. This problem may be
appropriate where the executable files are held on a Windows2000 Server, where the
13
Compatiblity Properties options do not exist. We are awaiting to see the installation of
Windows2003 Server to see if these advanced properties options exist.
I am not aware, as yet of any difficulties with the WindowsVista operating system.
This section lists changes to the program since the last version of the manuals was printed in
October 2004.
14
noticeable effect will be if a spring, with noticeable length is attached to a beam then the
moment at the end of the beam may not be the same as the moment in the spring as the
tranverse shear in the spring member will also have a contribution to the moment. The
parameter SL enables the user to move the location of the transverse component from mid-
length. SL = -0.5 moves the transverse components to End 1 of the member and SL = + 0.5
moves the transverse components to End 2. In the Compound Spring members the data item
SL existed in the earlier editions of the manuals but was not used. If the data item is not
supplied, or old data sets are used then SL is taken as 0.0 and the default location at mid-
length is used.
Ruaumoko2D:
8. The Spring members now have a Quadratic Axial Force- Bending Moment interaction
Ruaumoko3D:
9. The line 19b to provide the material specific damping coefficients for ICTYPE = 5 or 7 is
missing from the manual for the Quadrilateral elements. This data is identical to that
required for the Beam, Spring or Foundation elements. This is the second line of data for
these elements and should make up page 74 in the manual.
10. The Contact element has a new option ITYPE = 3 which allows for the modelling of
spherical isolation bearings. These bearings are assumed to carry no tension force and any
lateral movement of the contact implies a shortening of the contact member, increasing the
compressive force and hence, maintaining equilibrium, lifting the structure. The friction
coefficient may vary with velocity.
11. There is a new External member type. This member type enables the user to use
Ruaumoko3D in psuedo-dynamic experiments were some of the members are part of a
displacement controlled experiment or where the member (or its' hysteresis properties) are
modelled in an external program using MatLab or Visual Basic. The external program
controlling the experiment or modelling the members must be running when Ruaumoko3D
is started so that the pipe between the programs is active. At each iteration within each
time-step, including that static analysis, Ruaumnoko sends the incremental displacements
for each specified action in each External member to the external program, then processes
all other elements on the structure than waits for the pipe to return the member actions etc.
Once the data is returned, the member stiffnesses are updated and the program proceeds to
the next time-step.
The advantage of operating in this way is that the program is no different for other users,
the program does not need re-compiling for user written hystersis models or for
experimental control. The external features are all controlled by the external program.
Sample external programs will be supplied to illustrate how the system operates.
12. Both Frame and Spring members have a new Type 4 Reinforced Concrete Beam-Column
Interaction.
Inspect
13. There is an alternative damping model available, The original model set up the damping
coefficient for the specified fraction of critical damping for the elastic oscillator. This
damping coefficient remained constant irrespective of the change in stiffness in the
oscillator as the earthquake excitation progressed. The new option, follow the fraction of
critical damping with the word NO, adjusts the damping coefficient to retain the same
fraction of critical damping at all times using the tangent stiffness of the oscillator.
Dynaplot
14. The options in Dynaplot have been adjusted to allow for the extra features of the 3D Contact
member. This means that if earlier results had 3D Contact elements in the structure the new
15
Dynaplot will not work. For this reason, keep the old Dymnaplot in a separate directory or
renamed so that it can be used for the old post-processor files.
16