Welcome to Whisper code’s documentation¶
Whisper project: FP7 ERC Advanced grant 227507 (WHISPER)
Abstract
This project focuses on the use of the seismic ambient noise to monitor slight changes of properties in the solid Earth. The implications are the detection of change of strain at depth with applications in different contexts. A major field of application is the monitoring of potentially dangerous structures like volcanoes or active fault zones. The project includes new methodological developments, massive processing of existing data and field experiments. Applications in regions where changes are induced by human activity are important both for the quantitative refinement of the method and for the important economic and social implications of these problems.
Take a look at the whisper project synopsis.
Codes
Codes are developed for the whisper project. They provide tools for processing a large set of seismograms (traces), for computing correlations and analyse it.
They use the standard python scientific libraries numpy and scipy. The very good useful work made by the obspy library, dedicated to seismology communities, is also used, especially to read seismogram.
These small applications do not provide a lot of functionalities as the libraries already mentioned. They are focus on a main obstacle for the whisper project: the time computing for processing of large sets of datas.
OVERVIEW OF THE PACKAGES¶
General workflow
The packages traces and correlations provides some tools in order to compute all the correlations from a directory.
![digraph structs {
rankdir="TP"
node [shape=Mrecord];
LoadTrace [label="<LoadDirectoryTrace> LoadDirectory |Should contain files with format: \n sac, mseed, wav, etc... "];
ModuleMainTrace [shape=record, label="<ModuleMainTrace> Module \n traces.tracesMain| Extract all traces of seismograms\n and make the processing."];
SaveTrace [label="<SaveDirectoryTrace> SaveDirectoryTrace |Architecture of traces treated: \n Component/Year/JulianDay/Station"];
ModuleMainCorrelation [shape=record, label="<ModuleMainCorrelation> Module \ncorrelations.correlationsMain| Compute all the correlations\n for all the existing couple of traces."];
SaveCorrelations [label="<SaveDirectoryCorrelations> SaveDirectory |Architecture of correlations"];
LoadTrace:LoadDirectoryTrace -> ModuleMainTrace:ModuleMainTrace -> SaveTrace:SaveDirectoryTrace -> ModuleMainCorrelation:ModuleMainCorrelation -> SaveCorrelations:SaveDirectoryCorrelations
}](_images/graphviz-e2277efc04cde065977dccaba34d6e328c9bfb09.png)
Decentralized use
Codes can be run in a decentralized way. The main decentralized options refers to the list of dates and the list of stations which provides a fine granularity:
- List of dates can be divide in a list of sublists of dates.
- List of stations can be divide in a list of sublists of stations.
Note also that codes can be run for each components.
PACKAGES¶
| traces | Package for processing traces from a directory. |
| correlations | Package for computing correlations from the traces package output. |
| goodNumbers | Package for optimize the computation by getting ‘good number’. |