1. Moti Abu & Roee Ben Halevi Supervisors: Prof. Mark Last, Mr. Hanan Friedman 12 December 2010

2. Telemetry Velocities Vibrations Pressures ……………..

3. SNR (dB) Bit Errors

5. Solutions Best Source Selector Selects the best source based on received signal level. Best Data Selector Selects the best data based on SNR and received signal level. Correlated Source Selector Selects the best data bits based on best data fit. Smart Source Selector Combination of all the above.

6. Solutions

8. Survey 12 December 2010

9. Requirements SymbolRequirementDescriptionPriority [R1]Quality of outputBER in output should be reduced by at least 90% in all simulations Critical [R3]Halt and resumeThe system should support halting and resuming master generation Critical [R5]User interfaceThe system should include an ergonomic GUI and command line API for configuration. GUI should be in English Critical [R8]Late integration of sources The system should be able to integrate more inputs to the master output without re-reading of early sources High [R9]real-time progress notifications The system should include real- time progress notifications on GUI and command line interface High [R10]Built-in data-mining algorithms The system should offer built-in data-mining algorithms for optimizing the quality of output Medium 12 December 2010

10. Requirements SymbolRequirementDescriptionPriority [R11]Statistical reportsThe system should provide a user-defined statistical reports regarding the quality of output and sources Medium [R12]Configuration filesThe system should allow saving and loading current configuration status to and from configuration files Medium [R13]User overrideThe system should allow user to override algorithm decisions Medium [R15]API for user-defined plugins and extensions The system should support user- defined plugins and extensions by providing a user-friendly API Medium [R16]WizardThe system should allow users to create new jobs by a user- friendly wizard Medium [R20]Integrated probability models The system should include integrated probability models for bit-error prediction Low 12 December 2010

11. Requirements SymbolRequirementDescriptionPriority [R22]SpeedMaster output should be generated at a rate of 1Mb/sec for 5 sources with BER of 2% Critical [R23]ReliabilityThe system cannot crash at any circumstances Critical [R24]UsabilityGUI should be user-friendly and simple to manage for the common user. Not overwhelming the user with redundant messages. Every option should be up to 3 clicks away High [R25]ModularityThe system should enable replacing the provided data selection algorithms and formats by user-defined algorithms and formats Medium [R26]PortabilityThe system should work perfectly on Windows environment. Linux version is optional Low 12 December 2010

12. Requirements SymbolRequirementDescriptionPriority [R30]TestingThe system should be tested with artificial benchmarks Critical [R31]DemoFirst prototype of the system will include only core components Critical [R32]Quality measurements Quality of output will be measured with pre-defined quality measurements like similarity value and bias. Critical 12 December 2010 The quest for the best similarity value…

13. Use Cases 12 December 2010

14. Use Cases Use Case 2 [UC2]: generate master Primary Actor: Telemetry technician (or common user). Interests: The technician wants to generate a master output from source inputs. Pre-conditions: User opened a new job, loaded sources and defined a configuration. Post-conditions: The master is generated and saved in the job directory with metadata information. Main success scenario: 1. User clicks on "play" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. After confirmation, master output and metadata information are generated according to user configuration and saved in job directory. Main fail scenario: 1. User clicks on "play" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. User cancels master generation. 12 December 2010

15. Use Cases Use Case 3 [UC3]: Integrate input Primary Actor: Telemetry technician. Interests: The technician wants to integrate input source to master output. Pre-conditions: Configuration file, master output and metadata information are present in the job directory. User loaded inputs. Post-conditions: The new master is generated and saved in the job directory with new metadata information. Main success scenario: 1. User clicks on "integrate sources" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. After confirmation, new master output and metadata information are generated according to user configuration and saved in job directory. Main fail scenario: 1. User clicks on "integrate sources" icon. 2. An estimate for the execution time is displayed for the user and he is asked to confirm. 3. User cancels integration 12 December 2010

16. Proposed Solution 12 December 2010

17. Dataflow in Solution Experimental Aircraft Experimental aircraft transmits data to ground receivers Ground Receivers Several ground receivers record the data Preprocess unit (XXX-Telemetry records creator) The raw data that was recorded in each receiver is formatted and metadata files are created Smart Data Selector (SDS) Integrates all inputs to one master record that is as close as possible to the original data Analysis tools and QuickView Master record is used for analysis of flight and plotting 12 December 2010

18. Software Context 12 December 2010 Minor Major Minor Major Minor Major Minor

19. Survey 12 December 2010

20. Software Context 12 December 2010 Master Unit Best record Pack Slave Unit Best raw data Best metadata Master Readers Scheduler Master Builder Output to GUI Slave Reader Selecting Algorithm

21. 12 December 2010 Master Reader Master Unit – Part A Meta Data Raw Data Top Rated Record Master Reader 1 Master Reader N/2]] Master Reader N Part I Part [N/2] Part N Read Meta Data Threads

22. Master Record Builder 12 December 2010 Master Readers Good Minors Queue Minor Raw Minor Meta Minor Have Sync? Yes Have CRC? Yes Pack as Good Minor! Bad Minors Queue Raw Minor Meta Minor Have Bad Sync? OR Have Bad CRC? Pack as Bad Minor! Bad Minor

23. 12 December 2010 Good Minors Queue Bad Minors Entry Queue Bad signature Scheduler Task Queue Task Queue Task Queue Task Queue Slave Packet Apply Algorithm Apply Algorithm Good Minor Good Minor

24. Slave Minor Signature Slave Reader Raw Data Records Raw Data Records Meta Data Records Meta Data Records Find Good Minor In Others Records?  Yes!  Send Location to Builder All Records have bad minor??  Apply algorithm. Algorithm Machine Algorithm Machine Algorithms can be added and/or changed by user (Support Reflection mechanism )

25. Algorithm examples: - BitVoting. -Pattern recognition. -User Algorithm. 11010101101010 10010101001010 10010001001000 10010101001010 10010101001010 Origin data Station A Station B Station C BitVote

26. Master Record Builder Good Minors Queue Good Minor Good Minor To GUI

27. Block Diagram 12 December 2010