HP ESA-L1500A Spectrum Analyzer Programmer's Guide

Total Page:16

File Type:pdf, Size:1020Kb

HP ESA-L1500A Spectrum Analyzer Programmer's Guide Programmer’s Guide HP ESA-L1500A Spectrum Analyzer HEWLETT@’ r!!a PACKARD HP Part No. E4411-90003 Printed in USA January 1997 0 Copyright Hewlett-Packard Company 1997. All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. 1400 Fountaingrove Parkway, Santa Rosa CA, 95403-1799, USA The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, in- cluding but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, per- formance, or use of this material. The following safety symbols are used throughout this manual. Familiarize your- self with the symbols and their meaning before operating this instrument. CAUTION Caution denotes a hazard. It calls attention to a procedure that, if not correctly performed or adhered to, would result in damage to or destruction of the instrument. Do not proceed beyond a caution until the indicated conditions are fully understood and met. WARNING: Warning denotes a hazard. It calls attention to a procedure which, if not correctly performed or adhered to, could result in injury or loss of life. Do not proceed beyond a warning note until the indicated conditions are fully understood and met. WARNING: This is a Safety Class 1 Product (provided with a protective earthing ground incorporated inthe power cord). The mains plug shall only be inserted in a socket outlet provided with a protective earth contact. Any interruption of the protective conductor inside or outside of the product is likely to make the product dangerous. Intentional interruption is prohibited. 2 Contents 1 Preparing for Use and Printing Connecting Your Spectrum Analyzer 16 Connecting the HP-IB to the Computer 18 Connecting the RS-232 Interface to an HP Vectra or IBM Compati- ble Personal Computer 20 If There Is a Problem 22 Printing 23 What is HP-IB? 27 What is the RS-232 Bus 28 2 Programming Basics What’s In This Chapter 36 Writing Your First Program 37 Modifying the Program 41 Enhancing the Program with Variables 44 Getting Data from the Spectrum Analyzer 46 3 Programming Examples What You’ll Find in This Chapter 50 Reading Trace Data Into a Variable 5 1 Saving Trace Data in a computer 52 3 Contents Loading Trace Data from a Computer Disk 54 Different Formats for Trace Data Transfers 55 Saving and Loading Instrument States 66 Returning the Spectrum Analyzer to its Former State 68 Measuring Harmonic Distortion 69 Monitoring System Operation 72 Using Markers 79 Using Limit Lines 81 Measure Signal Bandwidth 82 Measuring Noise 83 Using Amplitude Correction 84 Examples Using the RS-232 Interface 85 4 Programming Command Cross References Command to Front-Panel 94 Front-Panel to Command 106 Functional Index 113 Command Backwards Compatibility 120 5 Programming Commands 4 Contents Command Syntax Conventions 124 Programming Command Descriptions 13 1 ALIGN Self-alignment Routines 132 AMPCOR Amplitude Correction 135 ANNOT Annotation 138 APB Trace A Plus Trace B 140 AT Attenuation 141 ATC Transfer Trace A to Trace C 143 AUNITS Amplitude Units 144 AUTO Auto Couple 146 AXB Exchange Trace A and Trace B 148 BAUDRATE Baud Rate of Spectrum Analyzer 150 BLANK Blank Trace 152 BML Trace B Minus Display Line 153 BRIGHT Display Brightness 154 BTC Transfer Trace B to Trace C 155 BXC Trace B Exchange Trace C 156 CAT Catalog 15 8 CF Center Frequency 16 1 CLRAVG Clear Average 163 5 Contents CLRW Clear Write 164 CLS Clear Status Byte 165 CMDERRQ Command Error Query 166 CONFIG Configuration 167 CONTRAST Display Contrast 169 CONTS Continuous Sweep 170 CORREK Correction Factors On 171 DATASTAT Data Status 172 DATEMODE Date Mode 174 DEFCONFIG Default Configuration 175 DELETE File 176 DEMOD Demodulation 178 DEMODT Demodulation Time (Dwell Time) 180 DET Detection Mode 182 DL Display Line 184 DN Down 186 DONE Done 187 ERASE Erase 189 EXITSHOWSYS Exit Configbhow System Screen 190 FA Start Frequency 191 Contents FB Stop Frequency 193 FOFFSET Frequency Offset 195 FREF Frequency Reference 197 FS Full Span 198 GETPRNT Get Print 199 GRAT Graticule 202 HD Hold Data Entry 204 ID Identify 205 INVERTLCD Inverse Video 206 INZ Input Impedance 208 IP Instrument Preset 210 LG Logarithmic Scale 213 LIMIDEL Delete limit line Table 215 LIMIDISP Limit Line Display 216 LIMIFAIL Limits Failed 218 LIMIFT Select Frequency or Time Limit Line 220 LIMIHALF Select Upper or Lower Limit Line 221 LIMILINE Limit Lines 223 LIMIREL Relative Limit Lines 226 LIMISEG Enter limit line Segment for Frequency 228 7 Contents LIMISEGT Enter limit line Segment for Sweep Time 23 1 LIMITEST Enable Limit Line Testing 234 LN Linear Scale 236 LOAD Load 237 LSPAN Last Span 239 MDS Measurement Data Size 240 MDU Measurement Data Units 243 MEAN Trace Mean 246 MEANTH Trace Mean Above Threshold 248 MF Marker Frequency Output 250 MINH Minimum Hold 252 MKA Marker Amplitude 253 MKACT Activate Marker 255 MKBW Marker Bandwidth 257 MKCF Marker to Center Frequency 259 MKD Marker Delta 260 MKF Marker Frequency 262 MKFA Marker to Start Frequency 265 MKFB Marker to Stop Frequency 266 MKFC Marker Counter 267 8 Contents MKFCR Marker Counter Resolution 268 MKMIN Marker Minimum 270 MKN Marker Normal 27 1 MKNOISE Marker Noise 273 MKOFF Marker Off 276 MKP Marker Position 277 MKPAUSE Marker Pause 279 MKPK Marker Peak 28 1 MKPP Marker Peak-to-Peak 283 MKPX Marker Peak Excursion 284 MKREAD Marker Readout 286 MKRL Marker to Reference Level 288 MKSP Marker to Span 289 MKSS Marker to Step Size 290 MKTBL Marker Table 292 MKTH Peak Threshold 294 MKTRACE Marker Trace 296 MKTRACK Marker Track 297 ML Mixer Level 299 MOV Move 301 9 Contents MXMH Maximum Hold 304 NDB Number of dB 305 NDBPNT N dB Points 307 NDBPNTR N dB Points Bandwidth 310 NORMLIZE Normalize Trace Data 3 11 NRL Normalized Reference Level 3 13 NRPOS Normalized Reference Position 3 15 OL Output Learn String 317 PCTAM Percent AM 3 19 PCTAMR Percent AM Response 321 PEAKS Peaks 323 POWERON Power-On State 327 PREAMPG External Preamplifier Gain 328 PRINT Print 329 PRNPRT Printer Port 33 1 PRNTADRS Printer Address 332 PRNTMARGB Printer Margin Bottom 333 PRNTMARGT Printer Margin Top 335 PRNTRES Printer Resolution 337 PSTATE Protect State 338 10 Contents PWRBW Power Bandwidth 339 PWRUPTIME Power Up Time 342 RB Resolution Bandwidth 343 REV Revision 345 RFCALIB 50 MHz Signal 347 RL Reference Level 349 RMS Root Mean Square Value 351 ROFFSET Reference Level Offset 353 RQS Service Request Mask 355 SAVE Save File 358 SEGDEL Segment Delete 361 SER Serial Number 363 SETDATE Set Date 364 SETTIME Set Time 365 SHOWSYS Show System 366 SMOOTH Smooth Trace 367 SNGLS Single Sweep 370 SP span 371 SPEARER Speaker 373 SPZOOM Span Zoom 374 11 Contents SQR Square Root 375 SRCAT Source Attenuator 377 SRCPOFS Source Power Offset 379 SRCPSTP Source Power-Level Step Size 381 SRCPSWP Source Power Sweep 383 SRCPWR Source Power 385 SRQ Force Service Request 387 SS Center Frequency Step Size 391 ST Sweep Time 393 SIB Status Byte Query 395 STDEV Standard Deviation of Trace Amplitudes 397 SUM Sum of Trace Amplitudes 399 SUMSQR Sum of Squared Trace Amplitudes 401 SWPCPL Sweep Couple 403 TDF Trace Data Format 404 TH Threshold 411 TIMEBASEC Timebase Coarse Adjustment 413 TIMEBASEF Timebase Fine Adjustment 415 TIMEDATE Time Date 417 TIMEDSP Time Display 4 19 12 Contents TITLE Title 420 TM Trigger Mode 421 TO1 Third-Order Intermodulation Measurement 423 TOIR Third-Order Intermodulation Response 426 TRA/TRB/TRC Trace Data Input and Output 428 TRSTAT Trace Status 432 TS Take Sweep 434 UP Up 436 VARIANCE Variance of Trace Amplitudes 437 VAVG Video Average 439 VB Video Bandwidth 441 VBR Video Bandwidth Ratio 443 VIEW View Trace 444 XCH Exchange 445 6 Error Messages Descriptions 448 Index 455 13 Preparing for Use and Printing 15 Preparing for Use and Printing Connecting Your Spectrum Analyzer Connecting Your Spectrum Analyzer These topics are covered in the following section: l Connecting the Hewlett-Packard Interface Bus (HP-IB) to the computer . Connecting the RS-232 interface to your computer l Connecting your spectrum analyzer to a printer l If there is a problem l Information about HP-IB and RS-232 Connecting Your Spectrum Analyzer to a Computer The spectrum analyzer works with many popular computers. However, the steps required to connect your spectrum analyzer to a specific computer depend on the computer you are using. Before turning to the interconnection instructions for your computer, please read the following general information. Configuring Your Computer System Every computer system has a specific configuration. Your system configuration might include a printer or an external disk drive. Whenever you add another piece of equipment (for example, your spectrum analyzer), you may need to reconfigure your computer system so that the computer knows where and how to send infor- mation to the newly added device. Some computers do not require configuring when a spectrum analyzer is con- nected. Others require a simple modification. The most common modification is changing the configuration information stored on the computer’s operating system disk. A few computers require the insertion of an add-on board, or “card.” Refer to your computer documentation if your system needs these modifications. All of the test programs for HP-IB and RS-232 interfaces are written using the BASIC language. If you have never entered or mn a BASIC program, refer to your computer documentation.
Recommended publications
  • Ecaccess User Guide
    ECaccess User Guide User Support Operations Department Version 3.3.0 May 2009 c Copyright 2009 European Centre for Medium-Range Weather Forecasts Shinfield Park, Reading, RG2 9AX, United Kingdom Literary and scientific copyrights belong to ECMWF and are reserved in all countries. The information within this publication is given in good faith and considered to be true, but ECMWF accepts no liability for error, omission and for loss or damage arising from its use. CONTENTS Contents 1 Introduction 3 2 Ecaccess concepts 4 2.1 ECaccess gateway ......................................... 4 2.2 Using an ECaccess gateway ................................... 5 2.3 Plugins ............................................... 5 3 Security authentication 7 3.1 ECaccess certificate ........................................ 7 3.2 ECcert command ......................................... 7 4 Unattended file transfers initiated from ECMWF 10 4.1 Target location ........................................... 10 4.2 ECtrans command ......................................... 11 4.2.1 Transfer to a Member State host via gateway ....................... 12 4.2.2 Transfer from a Member State host via gateway ...................... 12 5 Shell commands 14 5.1 Environment ............................................ 14 5.2 Access to Shell commands .................................... 15 5.3 General information ........................................ 15 5.4 File management ......................................... 15 5.5 Batch job management .....................................
    [Show full text]
  • Argus Research (July 2020)
    EQUITY RESEARCH REPORT July 13, 2020 MOLECULAR DATA INC. (NCM: MKD) Founded in 2013, China-based Molecular Data operates an e-commerce platform that KEY STATISTICS connects and serves participants of the Chinese chemicals industry across the value chain. Key Stock Statistics COMPANY HIGHLIGHTS Recent price (7/7/20) $2.40 * MKD: Connecting China’s Chemical Industry Value Chain 52 week high/low $11.80/$0.57 ADS Outstanding (M) 115 * In our view, Molecular Data has assembled a comprehensive network that can capture value across multiple previous pain points in China’s fragmented chemicals industry. Market cap (M) $276.0 Dividend Nil * After several years of organically building platform capabilities to include financial services, warehousing, logistics and software as a service (SaaS) offerings, Molecular Yield Nil Data should now be able to diversify its revenue stream beyond its core chemical direct e-commerce sales. This should lead to enhanced profit margins and, ultimately, sustainable Sector Overview profitability. Sector Materials * At the end of 2019, Molecular Data completed an initial public offering that yielded net Sector % of S&P 500 2.5% proceeds of approximately $55 million. As a result, we view the company as well posi- tioned to invest in its integrated e-commerce platform with new higher-margin services, and to pursue the acquisition of new capabilities and services globally. Financials ($M) * Although we expect near-term financial results to be impacted by the COVID-19 outbreak, Cash & Mkt Securities 8.3 which forced many customers and suppliers to halt operations throughout the first half of Debt 2.0 2020, we are encouraged by continued robust traffic on the Molbase platform.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • Supplementary Material for Traditional Agricultural Practices and the Sex Ratio Today Alberto Alesina1,2, Paola Giuliano3,2,*, Nathan Nunn1,2
    Supplementary Material for Traditional agricultural practices and the sex ratio today Alberto Alesina1,2, Paola Giuliano3,2,*, Nathan Nunn1,2 1 Harvard University. 2 NBER. 3 UCLA. *Correspondence to: [email protected] The Supplementary Material provides details on the data sources and the robustness of the analysis for the results derived in the paper. Additional details on the Ethnographic Atlas The Ethnographic Atlas was constructed by George Peter Murdock. It contains ethnographic information for 1,265 ethnic groups worldwide. The period in which the information was collected varies by ethnicity, with the earliest observation dates coming from ethnicities in the Old World (where early written evidence is available) and the most recent information dating around the 20th century, for those parts of the world without a written history and directly observed by anthropologists. All societies are observed prior to industrialization. In total, 23 ethnicities are observed during the 17th century or earlier, 16 during the 18th century, 310 during the 19th century, 876 between 1900 and 1950, and 31 after 1950. For nine ethnicities, an exact year is not provided. The variable v39 classifies each ethnic group as being in one of the following three categories: (1) the plough was absent, (2) the plough existed at the time the group was observed, but it was not aboriginal, and (3) the plough was aboriginal, having existed prior to contact. Using this information, we construct an indicator variable that equals one if the plough was ever adopted during the pre-industrial period (whether aboriginal or not) and zero otherwise. Of the 1,156 ethnicities for which information exists, for 997 the plough was absent, for 141 the plough was adopted (and aboriginal), and for 18 it was adopted, but after European contact.
    [Show full text]
  • Resource Management: Linux Kernel Namespaces and Cgroups
    Resource management: Linux kernel Namespaces and cgroups Rami Rosen [email protected] Haifux, May 2013 www.haifux.org 1/121 http://ramirose.wix.com/ramirosen TOC Network Namespace PID namespaces UTS namespace Mount namespace user namespaces cgroups Mounting cgroups links Note: All code examples are from for_3_10 branch of cgroup git tree (3.9.0-rc1, April 2013) 2/121 http://ramirose.wix.com/ramirosen General The presentation deals with two Linux process resource management solutions: namespaces and cgroups. We will look at: ● Kernel Implementation details. ●what was added/changed in brief. ● User space interface. ● Some working examples. ● Usage of namespaces and cgroups in other projects. ● Is process virtualization indeed lightweight comparing to Os virtualization ? ●Comparing to VMWare/qemu/scaleMP or even to Xen/KVM. 3/121 http://ramirose.wix.com/ramirosen Namespaces ● Namespaces - lightweight process virtualization. – Isolation: Enable a process (or several processes) to have different views of the system than other processes. – 1992: “The Use of Name Spaces in Plan 9” – http://www.cs.bell-labs.com/sys/doc/names.html ● Rob Pike et al, ACM SIGOPS European Workshop 1992. – Much like Zones in Solaris. – No hypervisor layer (as in OS virtualization like KVM, Xen) – Only one system call was added (setns()) – Used in Checkpoint/Restart ● Developers: Eric W. biederman, Pavel Emelyanov, Al Viro, Cyrill Gorcunov, more. – 4/121 http://ramirose.wix.com/ramirosen Namespaces - contd There are currently 6 namespaces: ● mnt (mount points, filesystems) ● pid (processes) ● net (network stack) ● ipc (System V IPC) ● uts (hostname) ● user (UIDs) 5/121 http://ramirose.wix.com/ramirosen Namespaces - contd It was intended that there will be 10 namespaces: the following 4 namespaces are not implemented (yet): ● security namespace ● security keys namespace ● device namespace ● time namespace.
    [Show full text]
  • FTP Plug-In User Guide 2017.1 May 2017 Copyright © 2001-2017 Perforce Software
    FTP Plug-In User Guide 2017.1 May 2017 Copyright © 2001-2017 Perforce Software. All rights reserved. Perforce software and documentation is available from www.perforce.com. You can download and use Perforce programs, but you can not sell or redistribute them. You can download, print, copy, edit, and redistribute the documentation, but you can not sell it, or sell any documentation derived from it. You can not modify or attempt to reverse engineer the programs. This product is subject to U.S. export control laws and regulations including, but not limited to, the U.S. Export Administration Regulations, the International Traffic in Arms Regulation requirements, and all applicable end-use, end-user and destination restrictions. Licensee shall not permit, directly or indirectly, use of any Perforce technology in or by any U.S. embargoed country or otherwise in violation of any U.S. export control laws and regulations. Perforce programs and documents are available from our Web site as is. No warranty or support is provided. Warranties and support, along with higher capacity servers, are sold by Perforce Software. Perforce Software assumes no responsibility or liability for any errors or inaccuracies that might appear in this book. By downloading and using our programs and documents you agree to these terms. Perforce and Inter-File Branching are trademarks of Perforce Software. All other brands or product names are trademarks or registered trademarks of their respective companies or organizations. Any additional software included within Perforce
    [Show full text]
  • How Is Dynamic Symbolic Execution Different from Manual Testing? an Experience Report on KLEE
    How is Dynamic Symbolic Execution Different from Manual Testing? An Experience Report on KLEE Xiaoyin Wang, Lingming Zhang, Philip Tanofsky University of Texas at San Antonio University of Texas at Dallas Outline ๏ Background ๏ Research Goal ๏ Study Setup ๏ Quantitative Analysis ๏ Qualitative Analysis ๏ Summary and Future Work "2 /27 Background ๏ Dynamic Symbolic Execution (DSE) •A promising approach to automated test generation •Aims to explore all/specific paths in a program •Generates and solves path constraints at runtime ๏ KLEE •A state-of-the-art DSE tool for C programs •Specially tuned for Linux Coreutils •Reported higher coverage than manual testing "3 /27 Research Goal ๏ Understand the ability of state-of-art DSE tools ! ๏ Identify proper scenarios to apply DSE tools ! ๏ Discover potential opportunities for enhancement "4 /27 Research Questions ๏ Are KLEE-based test suites comparable with manually developed test suites on test sufciency? ๏ How do KLEE-based test suites compare with manually test suites on harder testing problems? ๏ How much extra value can KLEE-based test suites provide to manually test suites? ๏ What are the characteristics of the code/mutants covered/killed by one type of test suites, but not by the other? "5 /27 Study Process KLEE tests reduced KLEE tests program manual tests coverage bug finding quality metrics "6 /27 Study Setup: Tools ๏ KLEE •Default setting for ๏ GCOV test generation •Statement coverage •Execute each program collection for 20 minutes ๏ MutGen •Generates 100 mutation faults for each program
    [Show full text]
  • IBM I Version 7.2
    IBM i Version 7.2 Networking File Transfer Protocol IBM Note Before using this information and the product it supports, read the information in “Notices” on page 157. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1998, 2013. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents FTP on IBM® i.........................................................................................................1 What's new for IBM i 7.2..............................................................................................................................1 PDF file for File Transfer Protocol................................................................................................................1 Scenarios: FTP..............................................................................................................................................1 Scenario: Transferring a file from a remote host...................................................................................2 Scenario: Securing FTP with SSL............................................................................................................3 Configuration details.........................................................................................................................4 Creating
    [Show full text]
  • RSX - 11 M-PLUS Mini-Reference
    RSX - 11 M-PLUS Mini-Reference Order No. AV-H435F-TC RSX - 11M-PLUS Mini-Reference Order Number. AV-H435F-TC RSX-ll M-PLUS Version 4.2 Digital Equipment Corporation Maynard, Massachusetts First Printing, September 1977 Revised, April 1982 Revised, April 1983 Revised, July 1985 R~vised, .September 1987 Revised, January 1989 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1977, 1982, 1983, 1985, 1987, 1989. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC DIBOL UNIBUS DEC/CMS EduSystem VAX DEC/MMS lAS VAXcluster DECnet MASSBUS VMS DECsystem-lO PDP VT DECSYSTEM-20 PDT DECUS RSTS DECwriter RSX ~U~UIl~DTM ZK5077 Contents Preface vii Conventions ............................................... viii Online Help Files Online Help Files ............................................. 3 Command Line Interpreters Monitor Console Routine (MCR) Commands ......................... 7 Digital Command Language (DCL) ............................... 21 utilities BAD Command Summary ...................................... 67 iii BRU Command Summary ...................................... 69 CMP Command Summary ...................................... 74 DMP Command Summary .....................................
    [Show full text]
  • Electrical Engineering and Computer Science Department
    Electrical Engineering and Computer Science Department Technical Report NWU-EECS-07-02 February 3, 2006 Network-based and Attack-resilient Length Signature Generation for Zero-day Polymorphic Worms Zhichun Li, Lanjia Wang, Yan Chen and Zhi (Judy) Fu Abstract It is crucial to detect zero-day polymorphic worms and to generate signatures at the edge network gateways or honeynets so that we can prevent the worms from propagating at their early phase. However, most existing network-based signatures generated are not vulnerability based and can be easily evaded under attacks. In this paper, we propose to design vulnerability based signatures without any host-level analysis of worm execution or vulnerable programs. As the first step, we design a network-based Length-based Signature Generator (LESG) for worms based on buffer overflow vulnerabilities. The signatures generated are intrinsic to buffer overflows, and are very hard for attackers to evade. We further prove the attack resilience bounds even under worst case attacks with deliberate noise injection. Moreover, LESG is fast, noise-tolerant, and has efficient signature matching. Evaluation based on real-world vulnerabilities of various protocols and real network traffic demonstrates that LESG is promising in achieving these goals. Keywords: zero-day vulnerability; polymorphic worm; worm signature generation; network intrusion detection/prevention system (IDS/IPS); protocol field length based signature Network-based and Attack-resilient Length Signature Generation for Zero-day Polymorphic Worms Zhichun Li, Lanjia Wangy, Yan Chen and Zhi (Judy) Fuz Northwestern University, Evanston, IL, USA yTsinghua University, Beijing, China zMotorola Labs, Schaumburg IL, USA Abstract It is crucial to detect zero-day polymorphic worms and to generate signatures at the edge network gateways or honeynets so that we can prevent the worms from propagating at its early phase.
    [Show full text]
  • Introduction to I N D and Recursive Partitioning
    NASA-CR-191220 Research Institute for Advanced Computer Science NASA Ames Research Center • i _ / / -- , t Introduction to I N D and Recursive Partitioning WRAY BUNTINE Unc 1 -_, 01_!i306 RIACS Technical Report 91.23 September 1991 Introduction to I N D and Recursive Partitioning RIACS TR 91.23 WRAY BUNTINE The Research Institute of Advanced Computer Science is operated by Universities Space Research Association, The American City Building, Suite 212, Columbia, MD 21044, (301)730-2656 Work reported herein was supported in part by Coopertive Agreement NCC2-387 between the National Aeronautics and Space Administration (NASA) and The Universities Space Research Association (USRA) Work was perfomed at the Research Institute for Advanced Computer Science (RIACS), NASA Ames Research Center, Moffett Field, California 94035-1000 Introduction to IND and Recursive Partitioning Wray Buntine, RIACS Rich Caruana, SJSU/NASA NASA Ames Research Center Mail Stop 269-2 Moffet Field, CA 94035 Version 1.0 September 23, 1991 Copyright (_) 1991 Research Institute for Advanced Computer Science. Abstract This manual describes the IND package for learning tree classifiers from data. The package is an integrated C and C shen re-implementation of tree learning routines such as CART, C4, and various MDL and Bayesian variations. The package includes routines for experiment control, interactive operation, and analysis of tree building. The manual introduces the system and its many options, gives a basic review of tree ]earning, contains a guide to the literature and a glossary, lists the manual pages for the routines, and instructions on installation. Contents Preface Getting Started I-I 1.1 About This Manual ..................................
    [Show full text]
  • Description of Knowledge of Mathematical Programs with TEX and XML
    Description of Knowledge of Mathematical Programs with TEX and XML Balázs Vecsei BUTE Mathematical Institute, 5th year student 1111 Budapest, Egry József u. 1, Hungary [email protected] http://www.math.bme.hu/~vecseib Abstract There are many free mathematical programs and databases on the Internet, but use of these pro- grams can be difficult. In this paper I would like to show an XML-based mathematical knowledge description language. In this language I will describe the ability of different kinds of mathematical programs. In my opinion, XML is a useful base for this language, because it is well standardized, and there are tools for handling it. Résumé Il y a une multitude de programmes et bases de données mathématiques sur Internet, mais leur utilisation peut être difficile. Dans cet article nous présentons un langage de description de connais- sance mathématiques basé sur XML. Dans ce langage nous décrivons les fonctionnalités de divers programmes mathématiques. Nous pensons que XML est un fondement utile de ce langage, grâce à sa normalisation et à l’existence d’outils de traitement de celui-ci. Introduction – an interlingua for mathematical communica- tion (OMDoc) I think we need a mechanism to describe the knowledge about free mathematical programs, because more than 50 – a portal for potential users and a discusssion mathematical programs are on the Internet, under the forum for developers GPL or other free licenses. • openmath: OpenMath is an emerging standard for The documentation of the free mathematical pro- representing mathematical objects with their se- grams is often written in a TEX-based language, and we mantics, allowing them to be exchanged between can download it, along with the programs’ source.
    [Show full text]