User manual VAISALA CP7000

[. . . ] CP SeriesTM CP7000TM, CP8000TM USER'S GUIDE M210557EN-A April 2004 PUBLISHED BY Vaisala Oyj P. O. Fax +358 9 8949 1 +358 9 8949 2227 Visit our Internet pages at http://www. vaisala. com/ FOR TECHNICAL INFORMATION Vaisala Inc. +011 520 806 7300 Fax: +011 520 741 2848 Toll free (US) 1 888 424 9899 © Vaisala 2004 No part of this manual may be reproduced in any form or by any means, electronic or mechanical (including photocopying), nor may its contents be communicated to a third party without prior written permission of the copyright holder. The contents are subject to change without prior notice. Please observe that this manual does not create any legally binding obligations for Vaisala towards the customer or end user. [. . . ] Figure 41 on page 113 identifies the fields for correlated sensor data. 2003/04/13 14:07:51. 186568210 38 . 187546610 146 . 187764048 237 . 187769600 235 . 187913500 219 . 188319900 151 . 188322424 180 . 188331100 224 . 188461800 233 . 188465100 228 . 188610000 43 . 188611507 126 . 188626646 178 . 188773600 181 . 188823800 148 . 188871741 131 . 188881278 244 . 189259200 225 . 189362000 44 . 189368963 118 . 189402103 36. 2263 -102. 7928 -3. 2 3. 2 339. 5 5. 4 4. 0 113. 6 -2. 8 3. 2 0. 0 -4. 4 2. 2 0. 0 -2. 4 3. 4 0. 0 3. 4 3. 8 264. 8 -0. 2 4. 4 0. 0 -4. 4 2. 8 0. 0 0. 6 3. 6 0. 0 1. 1 2. 6 0. 0 -1. 3 2. 6 312. 7 -2. 8 2. 8 30. 8 -3. 3 3. 0 0. 0 2. 5 3. 6 0. 0 -3. 4 21. 8 167. 2 0. 7 2. 6 50. 8 2. 6 4. 0 0. 0 -1. 2 2. 8 0. 0 3. 3 2. 2 308. 1 -0. 4 2. 8 212. 4 0 -172. 7 0 341. 3 -1. 2 116. 1 -0. 2 0. 0 _. _ 0. 0 _. _ 0. 0 _. _ 262. 8 2. 7 0. 0 _. _ 0. 0 _. _ 0. 0 _. _ 0. 0 _. _ 317. 7 0. 3 28. 3 2. 3 0. 0 _. _ 0. 0 _. _ 166. 2 0. 8 50. 6 0. 8 0. 0 _. _ 0. 0 _. _ 306. 0 2. 9 216. 4 -1. 8 0. 2 0. 1 2. 0 14. 8 -50. 3 -170. 6 -5. 8 -54. 5 -230. 1 -19. 2 -37. 2 -158. 7 -2. 0 -35. 6 -173. 2 -4. 7 -24. 9 -163. 2 -2. 1 -32. 7 -213. 6 -9. 8 -21. 1 -138. 6 +1. 6 -20. 9 -149. 6 +0. 1 -23. 1 -164. 9 -2. 1 -20. 7 -161. 0 -1. 4 -21. 5 -167. 6 -2. 2 -18. 8 -147. 9 +0. 3 -17. 3 -146. 7 +0. 3 -14. 8 -128. 9 +2. 3 -21. 3 -189. 8 -4. 6 -16. 2 -145. 5 +0. 5 -13. 0 -138. 4 +1. 1 -10. 0 -111. 1 +3. 5 -14. 7 -163. 9 -1. 3 -15. 6 -176. 7 -2. 4 5. 0 26 G HA*T OK 2 294. 3 AST A_T ___ 2 356. 9 AST A_T ___ 1 360. 3 _ST __T ___ 1 404. 0 _ST __T ___ 1 525. 1 _ST __T ___ 2 524. 9 AST A_T ___ 1 527. 8 __T __T ___ 1 568. 5 _ST __T ___ 1 567. 9 _ST __T ___ 1 611. 2 _ST __T ___ 1 612. 5 AST A_T ___ 1 617. 4 AST A_T ___ 1 661. 4 __T __T ___ 1 674. 8 __T __T ___ 1 690. 7 AST A_T ___ 1 692. 7 AST A_T ___ 1 805. 5 _ST __T ___ 1 837. 3 __T __T ___ 1 838. 4 AST A_T ___ 1 848. 9 AST A_T ___ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ _G__S_ Figure 40 Sample of Correlated Sensor Data 112 __________________________________________________________________M210557EN-A Chapter 8 _______________________________________________ Monitoring Sensor Performance Figure 41 Fields for Correlated Sensor Data Uncorrelated or Rejected Sensor Data The following example shows uncorrelated or rejected LF sensor data displayed by the sensorqa report. Figure 42 on page 114 describes the data fields. UNCORR 06 06/18/2003 01:40:02. 956412672 8 29. 3 +15. 3 8. 6 16. 4 IMPCT VAISALA _______________________________________________________________________113 User's Guide ______________________________________________________________________ Figure 42 Fields for Uncorrelated or Rejected Data Reprocessing with sensorqa The sensorqa utility operates in a reprocessing mode compatible with the reprocessing modes available in other processes such as located, locatevid, fcalcd, fcalcvd, and amond. Reprocessing LF Data To perform sensor quality assurance on reprocessed located data: - Type the following after the apa:{~}> prompt: cat *. raw | located -reprocess | sensorqa -reprocess Statistics are written to the $HOME/log/R. yyyy. mm. dd. hh. mm. qa directory. 114 __________________________________________________________________M210557EN-A Chapter 8 _______________________________________________ Monitoring Sensor Performance Reprocessing VHF Data To perform sensor quality assurance on reprocessed locatevid data: - Type the following after the apa:{~}> prompt: cat *. raw | locatevid -reprocess | sensorqa -vhf -reprocess Statistics are written to the $HOME/log/R. yyyy. mm. dd. hh. mm. vhf. qa directory. VAISALA _______________________________________________________________________115 User's Guide ______________________________________________________________________ This page intentionally left blank. 116 __________________________________________________________________M210557EN-A Chapter 9 _________________________________________________Analyzing Detection Accuracy CHAPTER 9 ANALYZING DETECTION ACCURACY This chapter applies to all CP models. Overview The utility for analyzing the detection accuracy of sensors is the intersect process. This process maps the lightning positions from the CP in two dimensions, and in a manner that displays which sensors are accurately locating lightning (see Figure 43 on page 119). The position data displayed by intersect includes: - LF stroke data from LF sensors: cloud strokes and cloud-to-ground (CG) return strokes - Total lightning data from VHF and LF sensors: VHF flashes and LF flashes - LF flashes The intersect process requires access to the appropriate lightning data queue, and may require bridged to be running if the data is not currently available on the local workstation. Access to cdbd is also required in order to obtain sensor configuration data (refer to section Starting Core Processes on page 31). Sensor designations are displayed on the map, if this information is available from cdbd. You can display either the two-character abbreviation for each sensor, the hex ID of the sensor, or the decimal ID of the sensor. VAISALA _______________________________________________________________________117 User's Guide ______________________________________________________________________ The intersect process displays data from either of two lightning buffers: real-time or history. The real-time buffer stores data received from a real-time lightning queue, while the history buffer contains historical (archive) data files loaded from disk. You can save either buffer to a file, or load a buffer with the contents of a file. When a real-time connection is enabled, lightning data that is received is added to the end of the real-time buffer. If the real-time buffer exceeds its maximum size, the oldest data is removed from the start of the buffer. As each real-time lightning occurs, various graphic information (such as angle vectors and time circles) may be added to the map on separate layers. The map layers selected for display control the information plotted on the map. The intersect process can be configured to display lightning reported by a particular sensor in a color different from that of lightning not seen by that sensor. Color can be used to better differentiate the types of lightning as well. The intersect process can receive all lightning data generated by the CP, LF stroke or total lightning, along with any time-correlated sensor data that did not produce a position. You can configure intersect to display all correlated events or only events that produced a position. Figure 43 on page 119 illustrates a typical intersect window. The following sections describe how to use and configure intersect. Using intersect The intersect process displays either LF stroke data or total lightning data in two dimensions. The LF stroke data includes cloud strokes and CG return strokes from LF sensors. Total lightning data includes VHF flashes and LF flashes from VHF and LF sensors, respectively. Starting intersect Using the GUI Icon To start the intersect process from the CDE control panel: 1. If the intersect GUI icon is visible on the desktop, double-click it to start the intersect process. 118 __________________________________________________________________M210557EN-A Chapter 9 _________________________________________________Analyzing Detection Accuracy Figure 43 2. Typical intersect Window If the intersect GUI icon is not visible on the desktop, open the Apa Apps pop-up menu and click the icon next to Intersect (see Figure 44 on page 120). [. . . ] See LF LowerLeftLat, regionqc. ksh parameter 148 LowerLeftLng, regionqc. ksh parameter 148 LP Archive Control. See LpaControl GUI LpaControl GUI archiving to CD-R 84­89 archiving to tape 89 configuring spool and storage devices 47 CP7000 22 CP8000 25 functions 81 monitoring data archiving 47­49 troubleshooting CD-R 188 viewing spooling space available 47 LPATS IV DSP field, cloud lightning 154 LPATS networks, configuring located 72 LPATS sensors attaching definition supported by CP lpbridged process CP7000 CP8000 lpmon process CP7000 CP8000 lpstart commands lpstart process CP7000 CP8000 lpterm process, troubleshooting tool LS5000 sensor CP support definition LS7000 sensor CP support definition LS7200 CP support LS7200 sensor definition LS7500 CP support LS7500 sensor definition LS8000 sensor CP support definition LTraX display LTraX, definition M magneto-optical disk archiving procedure troubleshooting man pages, file path managebydir command managebyfile command MANPATH file manual control of spool device manuals, conventions used map configuring base configuring layers displaying views replotting setting colors setting plot mode setting units of measure using Range Finder 78 221 12 22 25 22 25 31­33 21 24 184 12 221 12 221 12 221 12 221 12 221 12, 14 222 90­95 188 176 163 164 176 47 2 133, 136­137 138 132 132 137 137 137 133­134 236 __________________________________________________________________M210557EN-A ________________________________________________________________________________ zooming 130 map database binary format (MDB) 144 map database, directory 138 map layers associated with intersect display 118 configuring 138­140 disabling display 141 displaying time information 127 enabling display 141 Time Deviation Crosses 128, 139 World 138 map text file (MTX), ASCII 144 MapInfo Data Interchange Format (MIF) 144 MapInfo files, conversion to MDB 145 MAPPATH environment variable 145 Max Latitude, clipping region 68 Max Longitude, clipping region 68 MDB 144 MDB, map conversion 145 measurements required, located process 71 median semi-major axis, regionqc 151 merging LF and VHF flashes 15 messages CD verification 85 viewing 183 See also error messages microsecond trigger point, setting 128 MIF, conversion to MDB 145 miftomdb utility process 144 Min Latitude, clipping region 68 Min Longitude, clipping region 68 MinUsableAngles, cloud lightning 194 MinUsableTimes, cloud lightning 193 mixed sensor networks configuring located 72 maximizing cloud lightning efficiency 193 mode History 123, 142 Real-Time 123, 142 Mode field, clipping region 68 mode for plotting, base map attribute 136 Model field, sensor table 62 monitoring CP system 181­183 hard disk space 46 sensors 126­127 mount command 94 mount point, removable media 90 mounting archive media 82, 83 archive media after overflow switch 92 CD media 87 hold media 83 new disk as /archive directory 94 overflow media 83 removable media, ApaControl GUI 90 spool media 83 mouse button functions 120 MTX 144 multicasting 169­170 multiplicity definition 222 flash and stroke data 16 Multiplicity field, UALF record 168 N National Lightning Detection Network (NLDN), definition 222 NDS display 12 Network Data Archive process. See pandad process network detection efficiency, regionqc 152 network folder, configuring 60 Network ID configuring 60 configuring transport 64 network process interconnections CP7000 20 CP8000 22 network relative detection efficiency function 103 sensorqa statistic 152 Network Time Protocol (NTP) monitoring GPS synchronization 182 troubleshooting GPS 186 newfs command 94 Next button, Lightning Viewer 143 Next, map view 132 NLDN region boundaries, regionqc. ksh file 148 no sensor reports, troubleshooting 190 normalized signal strength calculation 207 definition 222 deviation 110 NRDE. See network relative detection efficiency ntpd process 182 ntpq command 182 ntpq process 182 O Objects In field, map layer option 140 ofile file, defining URL 53 -online option. [. . . ]