Fix文件字段简要说明.pdf

Fix Summary File Specification 1 Overview 2 This document provides an overview of fix summary file and its potential usage. 3 Potential Usage of Fix Summary Files 4 We need the fix summary file mainly when we would 5 a) Find the reason why a specific fix failed or does not perform as expected 6 b) Find Serving BS lookup failure 7 c) Get measurement PN lookup failure statistics 8 d) Reason sample measurement PN lookup failure and try to find ways to fix the problem and 9 improve the measurement PN lookup success rate 10 Item a) is mainly concerns when the system performance (esp. accuracy) is validated. Item b) to d) 11 are concerns in BSA optimization and maintenance. 12 How to Get the Fix Summary File 13 TraceFilter2 and Its Usage 14 Fix summary file is one of the output file type from TraceFilter2. Figure 2-1 provides an overview of 15 TraceFilter2 input and output files. 16 TraceFilter2 .BIN Input File (from PDE or Snapper) INPUT: “.CSV” file (formerly .POS) ?Data about individual fixes ?Summary statistics OUTPUTS: “.MLB” file ?Data about individual range measurements “.TXT” file ?Free-form text ?Error messages and other extraneous stuff “.FIX” file ?Details about individual fix record ?BSA lookup statistics 17 Figure 0-1 TraceFilter2 Input and Output Files 18 Overview 2 TraceFilter2 is a command-line program that runs both on Windows and UNIX platform. Following 1 are some instructions for running TraceFilter2 on each platform. 2 ? When using TraceFilter2 on a Windows platform, either mixed- or lower-case letters may be 3 used for the TraceFilter2 command. While on UNIX platform, certain inputs are case-4 sensitive. 5 ? Use “tracefilter2” to get version and help information. 6 ? General command format of TraceFilter2 is as follows: 7 tracefilter2 /f LSL_001.bin [options/switches] 8 ? Wild-card is supported by TraceFilter2. Thus multiple bin trace files could be processed 9 together in one time. 10 Switches/Options Us