Geopsy: Waveform Command Line - Revision history

Marc: /* Setting header information of ascii files */

2022-09-06T08:57:55Z

Setting header information of ascii files

Marc at 13:01, 1 March 2012

2012-03-01T13:01:30Z

Marc at 12:56, 1 March 2012

2012-03-01T12:56:44Z

Marc: /* Setting header information of ascii files */

2011-10-05T08:19:37Z

Setting header information of ascii files

Marc: /* Setting header information of ascii files */

2011-10-05T08:19:07Z

Setting header information of ascii files

Admin: /* Setting header information of ascii files */

2010-03-08T12:30:37Z

Setting header information of ascii files

Admin at 12:29, 8 March 2010

2010-03-08T12:29:57Z

Admin: Geopsy:Waveform Command Line moved to Geopsy: Waveform Command Line

2010-03-08T12:28:49Z

Geopsy:Waveform Command Line moved to Geopsy: Waveform Command Line

Marc: /* Setting header information of ascii files */

2010-02-12T17:58:07Z

Setting header information of ascii files

Marc: /* Setting header information of ascii files */

2009-07-01T07:44:23Z

Setting header information of ascii files

@@ Line 23: / Line 23: @@
 == Setting header information of ascii files ==
-Ascii files does not refer to a particular format. It describes the encoding of each character, other option can be: ASCII, UNICODE, UTF8, UTF16,... Hence, text files might have arbitrary format. This is particularly true for organizing header information where absolutely no standard exists. For the signal samples this is less the case. They are usually organized in various columns or in several bunch of data separated by special characters (see [[Geopsy:Supported file formats|supported file formats]] for details.
+Ascii files does not refer to a particular format. It describes the encoding of each character, other option can be: ASCII, UNICODE, UTF8, UTF16,... Hence, text files might have arbitrary format. This is particularly true for organizing header information where absolutely no standard exists. For the signal samples this is less the case. They are usually organized in various columns or in several bunch of data separated by special characters (see [[Geopsy:Supported file formats|supported file formats]] for details).
 The annoying thing with this kind of file is that you cannot automatically convert or process them in a script. This can be solved by using a script for setting the basic header information upon loading the files.
@@ Line 31: / Line 31: @@
 "setheader.qs' might contain these commands for a text file with three components to set sampling frequency to 100 Hz (see [[Geopsy: Waveform Scripting Language|waveform scripting language]] for details):
-   setHeader(0, "DeltaT", 0, 0.01);
+   for(i=0; i<3; i++) {
-  setHeader(1, "DeltaT", 0, 0.01);
+    setHeader(i, "SamplingFrequency", 100);
-  setHeader(2, "DeltaT", 0, 0.01);
+    setHeader(i, "StartTime", "2000-01-01");
    exportFile("output.mseed", "MiniSeed");
-   $ geopsy tmp/text_file -waveform setheader.qs
+   $ geopsy your_input_text_file -waveform setheader.qs
    -----INFO----- Loading ASCII Columns----
-   The ASCII format without header imply that you fill in the correct information yourself
+   The ASCII format without header implies that you fill in the correct information yourself
-   in a table. Choose menu "view/new table" and change the DeltaT (inverse of the sampling
+   in a table. Choose menu "view/new table" and change the SamplingPeriod (or SamplingFrequency)
-   frequency) to allow correct plotting in a graphic
+   to allow correct plotting in a graphic
-Once converted to miniseed, the sampling frequency is properly set and the files can be handled in a much easier way. A better script should adapt itself to the number of input signals:
+Once converted to miniseed, the starting time and the sampling frequency are properly set and the files can be handled in a much easier way. A better script should adapt itself to the number of input signals:
    n=signalCount();
    for(i=0;i<n;i++) {
-     setHeader(i, "DeltaT", 0, 0.01);
+     setHeader(i, "SamplingFrequency", 100);
+   }
    exportFile("output.mseed", "MiniSeed");

@@ Line 7: / Line 7: @@
 * Execute all actions listed in "scriptfile.qs"
-To save the results, the script must end with an [[Geopsy: Waveform Scripting Language#ExportFile|'''exportFile''']] command:
+To save the results, the script must end with an [[Geopsy: Waveform Scripting Language#exportFile|'''exportFile''']] command:
    [...] // Some processings come here

@@ Line 7: / Line 7: @@
 * Execute all actions listed in "scriptfile.qs"
-To save the results, the script must end with an '''export'' command:
+To save the results, the script must end with an [[Geopsy: Waveform Scripting Language#ExportFile|'''exportFile''']] command:
    [...] // Some processings come here
-   exportFile("output_file.sac", "SAC");
+   exportFile("output_file.sac", false, "SAC");
 Input and output formats for signal files are of course any of the supported file formats for input and output.

@@ Line 50: / Line 50: @@
      setHeader(i, "DeltaT", 0, 0.01);
+   }
-   exportFile("output_file.sac", "SAC");
+   exportFile("output.mseed", "MiniSeed");

@@ Line 34: / Line 34: @@
    setHeader(1, "DeltaT", 0, 0.01);
    setHeader(2, "DeltaT", 0, 0.01);
-   exportFile("output_file.sac", "SAC");
+   exportFile("output.mseed", "MiniSeed");
    $ geopsy tmp/text_file -waveform setheader.qs
    -----INFO----- Loading ASCII Columns----
-   The ASCII format without header imply that you fill in the correct information yourself in a table. Choose menu "view/new table" and change the DeltaT (inverse of the sampling frequency) to allow correct plotting in a graphic
+   The ASCII format without header imply that you fill in the correct information yourself
    tmp/text_file
    File tmp/output.mseed already exists, saving to /home/mwathele/tmp/output.mseed

@@ Line 29: / Line 29: @@
    geopsy -waveform setheader.qs input_file.txt
-"setheader.qs' might contain these commands for a text file with three components to set sampling frequency to 100 Hz (see [[Geopsy: Waveform Scripting Language]] for details):
+"setheader.qs' might contain these commands for a text file with three components to set sampling frequency to 100 Hz (see [[Geopsy: Waveform Scripting Language|waveform scripting language]] for details):
    setHeader(0, "DeltaT", 0, 0.01);

@@ Line 1: / Line 1: @@
-All the scripts that can be executed in [[Geopsy:Waveform Console]] can be also processed through the command line interface.
+All the scripts that can be executed in [[Geopsy: Waveform Console|waveform console]] can be also processed through the command line interface.
    geopsy -waveform scriptfile.qs input_file.mseed
@@ Line 19: / Line 19: @@
 These two commands list the supported file formats on input and output.
-"scriptfile.qs" can contain any series of command specified in [[Geopsy:Waveform Scripting Language]].
+"scriptfile.qs" can contain any series of command specified in [[Geopsy: Waveform Scripting Language|waveform scripting language]].
 == Setting header information of ascii files ==
@@ Line 29: / Line 29: @@
    geopsy -waveform setheader.qs input_file.txt
-"setheader.qs' might contain these commands for a text file with three components to set sampling frequency to 100 Hz (see [[Geopsy:Waveform Scripting Language]] for details):
+"setheader.qs' might contain these commands for a text file with three components to set sampling frequency to 100 Hz (see [[Geopsy: Waveform Scripting Language]] for details):
    setHeader(0, "DeltaT", 0, 0.01);

← Older revision	Revision as of 12:28, 8 March 2010
(No difference)