Difference between revisions of "Geopsy: Waveform Console"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
The waveform console contains two parts: | The waveform console contains two parts: | ||
| − | * The history attached to each [[Geopsy:Signal Viewer| | + | * The history attached to each [[Geopsy: Signal Viewer|signal viewer]] |
| − | * An editable [[Geopsy:Waveform Scripting Language|script]] that can be executed on the currently active [[Geopsy:Signal Viewer| | + | * An editable [[Geopsy:Waveform Scripting Language|script]] that can be executed on the currently active [[Geopsy: Signal Viewer|signal viewer]] |
| − | All actions performed from [[Geopsy:Waveform Menu|Wavefrom Menu]] are systematically stored in this history and saved in ''Saved steps''. The generated script can be copied in the editable part, modified, and started by ''Run''. They can be also saved in a text file (usually with extension .qs) to be executed from the [[Geopsy: | + | All actions performed from [[Geopsy: Waveform Menu|Wavefrom Menu]] are systematically stored in this history and saved in ''Saved steps''. The generated script can be copied in the editable part, modified, and started by ''Run''. They can be also saved in a text file (usually with extension .qs) to be executed from the [[Geopsy: Waveform Command Line|command line]]. |
| − | ''Saved steps'' are produced by command [[Geopsy: | + | ''Saved steps'' are produced by command [[Geopsy: Waveform Scripting Language#save|save("tag")]] which are always included in menu actions. Those saved steps can be restored at any time by using the graphical combo box or by sending command [[Geopsy: Waveform Scripting Language#restore|restore("tag")]]. |
Latest revision as of 12:26, 8 March 2010
The waveform console contains two parts:
- The history attached to each signal viewer
- An editable script that can be executed on the currently active signal viewer
All actions performed from Wavefrom Menu are systematically stored in this history and saved in Saved steps. The generated script can be copied in the editable part, modified, and started by Run. They can be also saved in a text file (usually with extension .qs) to be executed from the command line.
Saved steps are produced by command save("tag") which are always included in menu actions. Those saved steps can be restored at any time by using the graphical combo box or by sending command restore("tag").
