Description :
| -THE NEW VERSION
****************
Here is the new version of the toolbox for output only modal analysis
and diagnosis.
This is the 3.0 version. The meaning is not that there is no bugs but
this is a complete version. This is a binary version. Please report any
bug if and only if you got one and you can repeat it.
For the installation you simply have to uncompress the tar file where
you want and then execute the file "modal" in the Scilab window.
For running this toolbox you need the last Scilab version (2.7).
The tarfile contains data for running the demo defined in the given
functions. These data of COST F3 "Structural Dynamics"
have been made available with the courtesy of Jean-Claude Golinval
(see F.J. Molina, R. Pascual, J.-C. Golinval, Description of the
Steelquake Benchmark, Mechanical Systems and Signal Processing (2003)
17(1), 77-82.).
There is no associated man files for this toolbox; this is a button
driven toolbox and the use of the different possibilities is defined
by the "help" button at every stage.
-HOW DOES IT WORK ?
*******************
The basic file is a "Project" containing the parameters of the problem
you want to study.
All the different projects are in the file "list_projects-3.0"
(list_projects-win-3.0 for Windows platforms).
In those files, the first line correspond to the amount of double words
allocated in memory. The number is by default quite low. In case of problem, or
to make the toolbox faster, feel free to increase it, manually or by the
"Memory"
button in the first window of the toolbox. The other lines correspond to the
stored projects and the last line to the current project. A project is stored
if
it has been saved once. A project is the last project if it has been saved
during the last session. If an old project is not found during startup, it is
removed of the list when a save is done (remark applies for all files created
by
the toolbox like detection test files).
In this distribution the demo is in the directory "TOOL_DEMO".
The sub-directory "Files" is simply the directory of the data.
The "geometry_file" defines the finite element structure:
-coordinates (space and euler) and names of the points
-sensors direction (-1 on X means the sensor is in -X direction)
-structural properties (used for localization test) (Young modulus in
Newton/mm/mm, Poisson coefficient, density in T/mm/mm/mm).
-finite element description (list of elements with its structural properties
ID)
The files "project_linux" and "project_windows" contain the parameter
of the procedure.
The geometry file needs to be defined and completed "outside" the
toolbox. The project file can be edited "outside" but a common
procedure is to use the toolbox on new data and to automatically
construct this file while using the toolbox.
Be careful if you want to create a new project file or if you want to
modify a project file created by the toolbox. As soon as you really understand
the inner workings of the toolbox it is better to define those files by hand,
especially if you want to give special names and directions to the structure
points (the automated procedure create Point1, Point2, and so on, all in the X
direction, at [0 0 0] position). Links between elements have to be edited
manually. The project file store path position of the patch. If patch position
are changed or not found, you can affect its selection by the Copy/Replace
option in the Data Menu. A patch selection is noted ok when its fully affected
to the geometry and ready for work.
Some additive files may be created by the toolbox, especially in the detection
procedures. The default directory for files is either the launch directory,
where Scilab has been launched, or the directory where the project file is
(change inside the toolbox Load Menu)
--------------------------------
WARNING: the data are supposed to be in a global directory with
sub-directories corresponding to different experiments and a file
contains the time dta for ONE sensor, collected in a single ASCII
COLUMN file. This is the default case.
You can change this situation and adapt the input procedure to your
case. You simply have to edit and modify the Scilab functions defined
in the directory "Startup":
my_patch_directory.sci : Directory of patchs
my_patch_dir_exist.sci : boolean equal to 1 if the directory is a
data directory of patches
my_list_patches.sci : list of patches in the Data directory
my_list_sensors.sci : sensor list of the experiment directory
my_patch_exist.sci : boolean equal to 1 if the directory is a
directory of an experimentation
my_read_file.sci : your specific reading function
--------------------------------
-STARTING THE DEMO
-launch Scilab-2.7
-exec modal (use File/File Operations button of the Scilab command
window if you launch Scilab in a different directory from the file
"modal")
-click on Project/Load
-validate the slection by clicking on a specific project name (only
2 here)
-validate the data and structure files proposed
-choose Ident./Subspace
-choose Subspace/Start
-choose Visual./Run
-choose Pick mode and click on a point of the stabilization diagram.
and ---------------> discover all the other possibilities
WARNING: LEAVE THE STEPS WITH THE "END" BUTTON OF THE WINDOWS !!
ALL WINDOWS should be closed with its END bouton
MANY windows are interactive. Feel free to click.
GREYED BUTTONS are not available and may be disappear from the menu
bar. They come back when they are necessary.
--------------------------------
Some usual ways to play with the example :
-With the button "First exp" : change the sensor selection, use the
"Time series analysis" to see the data, to filter, to change the
chosen time part for the identification.
-Launch recursive monitoring
-Check all the parameters of the identification procedure
-Select carefully the poles
-Save the signature
At this step you can take you own data and do the identification.
And with these results you can start the detection procedure.
Good Scilabing and eigenstructure manipulation.
*********************************************************************************
AND MORE...............
For the bug report and questions send an email to
laurent.mevelinria.fr and maurice.goursat@inria.fr
You can find the related publications on:
http://www.irisa.fr/sigma2/constructif/
and the website of the research projects SIGMA2 and METALAU from
INRIA-IRISA Rennes and INRIA Rocquencourt.
|
