User manual VAISALA CP8000

[. . . ] 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. [. . . ] If the percent is greater than 50%, the sensor may have a timing problem. Sites that are located on the edge of the network tend to have higher uncorrelated values because the sensor is seeing information that is beyond the range of other sensors near the edge of the network. Also, consider the location of storms when interpreting the value in the percent uncorrelated field. These statistics may be biased if, during the collection of these statistics, storms were not evenly distributed throughout the network. NOTE LPATS and SAFIR LF sensors report only in the northeast bin since they do not report angle measurements. Percent Recycled The percent recycled statistic indicates how often a sensor was not used by the located process because its information was not consistent with that of any other sensor. In this case, the sensor was correlated in time, but no other measurement, such as angle or signal, was usable in producing a solution. If an IMPACT ALDF sensor reports higher than 10%, it may be acceptable as long as no other problems are present. Sensors with high percentages may have a subtle timing problem, or the configured latitude/longitude of the sensor is incorrect. Angle Deviations Angle deviations should be looked at when troubleshooting IMPACT ALDF sensors. More than 20 flashes is considered a good reading, and the angle deviation should be less than or equal to 3 degrees. As part of the analysis, you can use the intersect process to view angle errors for real-time stroke data (refer to Chapter 9, Analyzing VAISALA ______________________________________________________________________ 109 User's Guide ______________________________________________________________________ Detection Accuracy, on page 117). Large angle errors can be seen, since the vector from the site does not match up with the position of the flash. This may quickly identify configuration problems and rotational errors as opposed to site errors. Site error corrections require the collection of historical data over a significant time period. GPS Time Deviations For each sensor, the time deviation between the stroke time and the sensor's reported time is shown as a histogram. Bins for LF sensors are 1-microsecond bins to a maximum of 10 microseconds. LF sensors with time deviations greater than 5 microseconds should be reviewed. The terrain between the stroke and the sensor may influence sensor timing. Mountainous terrain typically introduces several microseconds of residual error. The sensorqa report includes histograms of large time deviations (20-microsecond bins to a maximum of 200 microseconds) for LF sensors. For LPATS-type sensors there are no large GPS time deviations since timing is the only parameter used in lightning location. Large timing errors for LPATS sensors are indicated by large uncorrelated values. Small timing problems are indicated by a high percentage of recycling. Signal Deviations Signal deviations are reported as the percentage difference between a sensor's range normalized signal strength and the average range normalized signal strength for all sensors that contributed to a stroke location. The signal deviations statistic applies mainly to LPATS and SAFIR LF sensors. A 95th percentile value larger than 30% indicates an antenna gain or noise problem. [. . . ] See sensorqa commands Help key, intersect 120 Hex ID label, displaying sensors 36 hexadecimal, sensor label format 125 -hexterm option. See attach options, setting histograms detection efficiency 107 regionqc 151 reported time 110 sensorqa 101 historical data, reprocessing 97­98 history buffer accessed by intersect process 118 displaying contents 142 function 123 History mode 123, 142 Hold file system archiving to CD-R 84­89 hold area full, troubleshooting 188 operation 83 host name aliases 176 humidity specifications, CP workstation 26 I ifile file, defining URL 52, 53 IMPACT networks, configuring located 72 IMPACT sensor attaching 75 definition 220 supported by CP 12 impactd process CP7000 21 CP8000 24 indexed table file, new 56 Information button 234 __________________________________________________________________M210557EN-A ________________________________________________________________________________ Processes panel 34, 35 Sensors panel 36, 40 Inside Polygon, clipping region 68 Inside Rectangle, clipping region 68 interferometer definition 221 inter-process communication. See IPC intersect base map configuration 136­137 configuring 121­134 enabling time deviation crosses 129 layer settings 138­141 Lightning Viewer 142­143 map controls 129­134 map database directory 138 using the Range Finder 133­134 intersect buffers loading data from a file 124 saving data to a file 123 intersect GUI analyzing detection accuracy with 117­118 configuring operation of 121­122 CP7000 22 CP8000 25 function 22, 25 starting 118 window title 30 intersect window data mode 123 entry fields, Help key 120 example 118 File menu 121 monitoring a sensor 125, 127 selecting sensor label format 125 selecting sensor to monitor 126 sensor timing problems 127 setting units of measure 137 using the mouse 120 IPC CP, sensor communication 171 definition 221 L label command label formats selecting Sensor panel display sensor label, intersect map large GPS time deviation interpreting sensorqa statistic Last button, Lightning Viewer Last Lightning Marker map layer latitude and longitude, clipping region 94 36 125 110 102 143 138 68 Latitude field polygon file 68 sensor realtime database 64 latitude/longitude, setting unit of measure 137 layers converting MIF to MDB 144 setting for map 138­140 LD_LIBRARY_PATH file 176 ldmerged process 24 LF lightning data displayed by intersect 117 reprocessing 98 LF lightning location system 9 LF sensors attaching 41 configuring cloud lightning 154 in an TIS 10 reporting cloud lightning 19 starting sensorqa 100 supported by CP 12 LF stroke data description 10 displaying with intersect 117 LF/VHF TIS 11 LF, definition 221 LF/VHF lightning location calculating 18 system description 11 system type 9 license agreement 4 lightning buffer, allowable size 122 lightning data displaying with intersect 117 displaying with Lightning Viewer 142 format 143 historical (archive) 123 loading from a file 124 real-time 123 saving to a file 123 viewing in ASCII format 142 See also field descriptions Lightning Data map layer 138 lightning marker selecting with mouse 120 setting size 122 Lightning Marker Size field, intersect GUI 122 lightning position calculation 16­19 interpreting chi-square 151 intersect display 142 plotting regardless of quality 122 Lightning to Plot field, intersect GUI 122 Lightning Viewer dialog box 142­143 VAISALA ______________________________________________________________________ 235 User's Guide _____________________________________________________________________ Line Style field, map layer option 140 Linux, definition 221 lnstatd process CP7000 22 CP8000 25 Load menu option, Intersect 124 located process CP7000 21 CP8000 24 definition 221 monitoring with sensorqa utility 99 optimizing lightning position 151 realtime database configuration 71 selecting sensor measurements 71 using as troubleshooting tool 183 using Time (seconds) field 72 viewing output with sensorqa 105 locatevid process CP8000 24 data reprocessing 97, 115 monitoring with sensorqa 99­100 reprocessing VHF historical data 98 troubleshooting 183 Location field, spool device 48 log files compressing for backup 177 error messages 182 naming convention for sensorqa 103 regionqc 150 regionqc, directory for 147 reviewing, troubleshooting 183 sensorqa statistics 103­104, 107 logging in, starting CP 30 Longitude field polygon file 68 sensor realtime database 65 low frequency. See LF LowerLeftLat, regionqc. ksh parameter 148 LowerLeftLng, regionqc. ksh parameter 148 LP Archive Control. [. . . ]