Specifying Syntax Components of a Grammar 1

Total Page:16

File Type:pdf, Size:1020Kb

Specifying Syntax Components of a Grammar 1 Specifying Syntax Components of a Grammar 1. Terminal symbols or terminals, Σ Language Specification 2. Nonterminal symbols or syntactic Syntax categories, N Form of phrases Vocabulary = Σ ∪ N Physical arrangement of symbols Semantics 3. Productions or rules, α ::= β, Meaning of phrases where α,β∈ (Σ ∪ N)* Result of executing a program 4 .Start Symbol (a nonterminal) Pragmatics Usage of the language Features of implementations Chapter 1 1 Chapter 1 2 Types of Grammars An English Grammar Type 0: Unrestricted grammars <sentence> ::= <noun phrase> <verb phrase> . α ::= β α <noun phrase> ::= <determiner> <noun> where contains a nonterminal | <determiner> <noun> <prepositional phrase> <verb phrase> ::= <verb> | <verb> <noun phrase> Type 1: Context-sensitive grammars | <verb> <noun phrase> <prepositional phrase> αBγ ::= αβγ <prepositional phrase> ::= <preposition> <noun phrase> Type 2: Context-free grammars <noun> ::= boy | girl | cat | telescope A ::= string of vocabulary symbols | song | feather <determiner> ::= a | the Type 3: Regular grammars A ::= a or A ::= aB <verb> ::= saw | touched | surprised | sang <preposition> ::= by | with Chapter 1 3 Chapter 1 4 A Derivation (for Figure 1.4) Concrete Syntax for Wren <sentence> ⇒ <noun phrase> <verb phrase> . ⇒ <determiner> <noun> <verb phrase> . Phrase-structure syntax: ⇒ the <noun> <verb phrase> . ⇒ the girl <verb phrase> . <program> ::= program <ident> is <block> ⇒ the girl <verb> <noun phrase> . <block> ::= <declaration seq> begin <cmd seq> end ⇒ the girl touched <noun phrase> . ε ⇒ the girl touched <determiner> <declaration seq> ::= | <declaration> <declaration seq> <noun> <prep phrase> . ⇒ the girl touched the <noun> <prep phrase> . <declaration> ::= var <var list> : <type> ; ⇒ the girl touched the cat <prep phrase> . <type> ::= integer | boolean ⇒ the girl touched the cat <preposition> <var list> ::= <var> | <var> , <var list> <noun phrase> . <cmd seq> ::= <cmd> | <cmd> ; <cmd seq> ⇒ the girl touched the cat with <noun phrase> . <cmd> ::= <var> := <expr> | skip ⇒ the girl touched the cat with <determiner> <noun> . | read <var> | write <int expr> ⇒ the girl touched the cat with a <noun> . | while <bool expr> do <cmd seq> end while ⇒ the girl touched the cat with a feather . | if <bool expr> then <cmd seq> end if | if <bool expr> then <cmd seq> Note example of a context-sensitive grammar. else <cmd seq> end if Chapter 1 5 Chapter 1 6 Lexical syntax: <expr> ::= <int expr> | <bool expr> <relation> ::= <= | < | = | > | >= | <> <integer expr> ::= <term> <weak op> ::= + | – <strong op> ::= * | / | <int expr> <weak op> <term> <ident> ::= <letter> | <ident> <letter> <term> ::= <element> | <ident> <digit> | <term> <strong op> <element> <letter> ::= a | b | c | d | e | f | g | h | i | j | k | l | m <element> ::= <numeral> | <var> | n | o | p | q | r | s | t | u | v | w | x | y | z | ( <int expr> ) | – <element> <numeral> ::= <digit> | <digit> <numeral> <bool expr> ::= <bool term> | <bool expr> or <bool term> <digit> ::= 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 <bool term> ::= <bool element> | <bool term> and <bool element> <bool element> ::= true | false | <var> Tokens: | <comparison> | not ( <bool expr> ) | ( <bool expr> ) <token> ::= <identifier> | <numeral> <comparison> ::= <int expr> <relation> <int expr> | <reserved word> | <relation> | <weak op> | <strong op> <var> ::= <ident> | := | ( | ) | , | ; | : <reserved word> ::= program | is | begin | end | var | integer | boolean | read | write | skip | while | do | if | then | else | and | or | true | false | not Chapter 1 7 Chapter 1 8 Sample Wren Program Ambiguity program prime is var num,divisor : integer; One phrase has two different derivation trees, thus two different syntactic structures. var done : boolean; begin Ambiguous structure may lead to ambiguous read num; semantics. while num>0 do Dangling “else” divisor := 2; done := false; Associativity of expressions (ex 2, page 16) while divisor<= num/2 and not(done) do Ada: done := num = divisor*(num/divisor); Is “a(2)” a subscripted variable divisor := divisor+1 or a function call? end while; if done then write 0 Classifying Errors in Wren else write num Context-free syntax end if; — specified by concrete syntax read num • lexical syntax end while • phrase-structure syntax end Context-sensitive syntax (context constraints) • also called “static semantics” Semantic or dynamic errors Chapter 1 9 Chapter 1 10 Context Constraints in Wren Syntax of Wren 1. The program name identifier may not be declared elsewhere in the program. <token>* — abitrary strings of tokens 2. All identifiers that appear in a block must be <program> — strings derived from declared in that block. the context-free grammar 3. No identifier may be declared more than once Syntactically well formed in a block. Wren programs derived from <program> and also satisfying the context constraints 4. The identifier on the left side of an assignment command must be declared as a variable, and the expression on the right must be of the same type. 5. An identifier occurring as an (integer) Semantic Errors in Wren element must be an integer variable. 1. An attempt is made to divide by zero. 6. An identifier occurring as a Boolean element 2. A variable that has not been initialized is must be a Boolean variable. accessed. 3. A read command is executed when input file 7. An identifier occurring in a read command empty. must be an integer variable. 4. An iteration command (while) does not terminate. Chapter 1 11 Chapter 1 12 Regular Expressions Denote Languages Nonessential Ambiguity ∅ Command Sequences: ε <cmd seq> ::= <command> a for each a∈Σ | <command> ; <cmd seq> (E | F) union (E • F) concatenation <cmd seq> ::= <command> | <cmd seq> ; <command> (E*) Kleene closure May omit some parentheses following the <cmd seq> ::= <command> ( ; <command> )* precedence rules Or include command sequences with Abbreviations commands: E1 E2 = E1 • E2 <command> ::= <command> ; <command> | skip | read <var> | … E+ = E • E* En = E • E • … • E, repeated n times E? = ε | E Language Processing: scan : Character* → Token* → Note: E* = ε | E1 | E2 | E3 | … parse : Token* ???? Chapter 1 13 Chapter 1 14 Concrete Syntax (BNF) read m; if m=-9 then m:=0 end if; write 22*m Derivation Tree • Specifies the physical form of programs. <cmd seq> • Guides the parser in determining the phrase structure of a program. <command> ; <cmd seq> read <variable> • Should not be ambiguous. <command> ; <cmd seq> var(m) <command> • A derivation proceeds by replacing one if <bool expr> then <cmd seq> end if nonterminal at a time by its corresponding write <int expr> right-hand side in some production for that <bool term> <command> nonterminal. <term> <bool elem> <variable> := <expr> <term> <str op> <elem> • A derivation following a BNF definition of a <comparison> var(m) <int expr> language can be summarized in a derivation <element> * var(m) (parse) tree. <int expr> <rel> <int expr> <term> num(22) <term> <term> • Although a parser may not produce a = <element> derivation tree, the structure of the tree is <element> <element> num(0) embodied in the parsing process. var(m) - <element> num(9) Chapter 1 15 Chapter 1 16 Abstract Syntax read m; if m=-9 then m:=0 end if; write 22*m • Representation of the structure of language constructs as determined by the parser. Abstract Syntax Tree: commands • The hierarchical structure of language constructs can be represented as abstract syntax trees. read if write var(m) times equal • The goal of abstract syntax is to reduce commands num(22) var(m) language constructs to their “essential” assign var(m) minus properties. num(9) var(m) num(0) • Specifying the abstract syntax of a language means providing the possible templates for the OR various constructs of the language. if write expr • Abstract syntax generally allows ambiguity expr since parsing has already been done. timesvar(m) num(22) equal var(m) minus • Semantic specifications based on abstract num(9) syntax are much simpler. Chapter 1 17 Chapter 1 18 Assume we only have to deal with programs that Designing Abstract Syntax are syntactically correct. What basic forms can an expression take? Consider concrete syntax for expressions: <int expr> <weak op> <term> <expr> ::= <int expr> | <bool expr> <term> <strong op> <element> <integer expr> ::= <term> <numeral> <variable> | <int expr> <weak op> <term> – <element> <term> ::= <element> | <term> <strong op> <element> <bool expr> or <bool term> <element> ::= <numeral> | <var> <bool term> and <bool element> | ( <int expr> ) | – <element> true false <bool expr> ::= <bool term> not ( <bool expr> ) | <bool expr> or <bool term> <int expr> <relation> <int expr> <bool term> ::= <bool element> | <bool term> and <bool element> Abstract Syntax: <bool element> ::= true | false | <var> Expression ::= Numeral | Identifier | true | false | <comparison> | ( <bool expr> ) | Expression Operator Expression | not ( <bool expr> ) | – Expression | not(Expression) <comparison> ::= Operator ::= + | – | * | / | or | and <int expr> <relation> <int expr> | <= | < | = | > | >= | <> Chapter 1 19 Chapter 1 20 Abstract Syntax Abstract Syntactic Categories Alternative Abstract Syntax Program Type Operator Block Command Numeral Abstract Production Rules Declaration Expression Identifier Program ::= prog (Identifier, Block) Abstract Production Rules Block ::= block (Declaration*, Command+) Program ::= program Identifier is Block Declaration ::= dec (Identifier+, Type) Block ::= Declaration* begin Command+ end Type ::= integer | boolean Declaration ::= var Identifier+ :
Recommended publications
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • DC Console Using DC Console Application Design Software
    DC Console Using DC Console Application Design Software DC Console is easy-to-use, application design software developed specifically to work in conjunction with AML’s DC Suite. Create. Distribute. Collect. Every LDX10 handheld computer comes with DC Suite, which includes seven (7) pre-developed applications for common data collection tasks. Now LDX10 users can use DC Console to modify these applications, or create their own from scratch. AML 800.648.4452 Made in USA www.amltd.com Introduction This document briefly covers how to use DC Console and the features and settings. Be sure to read this document in its entirety before attempting to use AML’s DC Console with a DC Suite compatible device. What is the difference between an “App” and a “Suite”? “Apps” are single applications running on the device used to collect and store data. In most cases, multiple apps would be utilized to handle various operations. For example, the ‘Item_Quantity’ app is one of the most widely used apps and the most direct means to take a basic inventory count, it produces a data file showing what items are in stock, the relative quantities, and requires minimal input from the mobile worker(s). Other operations will require additional input, for example, if you also need to know the specific location for each item in inventory, the ‘Item_Lot_Quantity’ app would be a better fit. Apps can be used in a variety of ways and provide the LDX10 the flexibility to handle virtually any data collection operation. “Suite” files are simply collections of individual apps. Suite files allow you to easily manage and edit multiple apps from within a single ‘store-house’ file and provide an effortless means for device deployment.
    [Show full text]
  • Windows Command Prompt Cheatsheet
    Windows Command Prompt Cheatsheet - Command line interface (as opposed to a GUI - graphical user interface) - Used to execute programs - Commands are small programs that do something useful - There are many commands already included with Windows, but we will use a few. - A filepath is where you are in the filesystem • C: is the C drive • C:\user\Documents is the Documents folder • C:\user\Documents\hello.c is a file in the Documents folder Command What it Does Usage dir Displays a list of a folder’s files dir (shows current folder) and subfolders dir myfolder cd Displays the name of the current cd filepath chdir directory or changes the current chdir filepath folder. cd .. (goes one directory up) md Creates a folder (directory) md folder-name mkdir mkdir folder-name rm Deletes a folder (directory) rm folder-name rmdir rmdir folder-name rm /s folder-name rmdir /s folder-name Note: if the folder isn’t empty, you must add the /s. copy Copies a file from one location to copy filepath-from filepath-to another move Moves file from one folder to move folder1\file.txt folder2\ another ren Changes the name of a file ren file1 file2 rename del Deletes one or more files del filename exit Exits batch script or current exit command control echo Used to display a message or to echo message turn off/on messages in batch scripts type Displays contents of a text file type myfile.txt fc Compares two files and displays fc file1 file2 the difference between them cls Clears the screen cls help Provides more details about help (lists all commands) DOS/Command Prompt help command commands Source: https://technet.microsoft.com/en-us/library/cc754340.aspx.
    [Show full text]
  • GNU Grep: Print Lines That Match Patterns Version 3.7, 8 August 2021
    GNU Grep: Print lines that match patterns version 3.7, 8 August 2021 Alain Magloire et al. This manual is for grep, a pattern matching engine. Copyright c 1999{2002, 2005, 2008{2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 2 Invoking grep :::::::::::::::::::::::::::::::::::: 2 2.1 Command-line Options ::::::::::::::::::::::::::::::::::::::::: 2 2.1.1 Generic Program Information :::::::::::::::::::::::::::::: 2 2.1.2 Matching Control :::::::::::::::::::::::::::::::::::::::::: 2 2.1.3 General Output Control ::::::::::::::::::::::::::::::::::: 3 2.1.4 Output Line Prefix Control :::::::::::::::::::::::::::::::: 5 2.1.5 Context Line Control :::::::::::::::::::::::::::::::::::::: 6 2.1.6 File and Directory Selection:::::::::::::::::::::::::::::::: 7 2.1.7 Other Options ::::::::::::::::::::::::::::::::::::::::::::: 9 2.2 Environment Variables:::::::::::::::::::::::::::::::::::::::::: 9 2.3 Exit Status :::::::::::::::::::::::::::::::::::::::::::::::::::: 12 2.4 grep Programs :::::::::::::::::::::::::::::::::::::::::::::::: 13 3 Regular Expressions ::::::::::::::::::::::::::: 14 3.1 Fundamental Structure ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Your Performance Task Summary Explanation
    Lab Report: 11.2.5 Manage Files Your Performance Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 6 seconds Required Score: 100% Task Summary Actions you were required to perform: In Compress the D:\Graphics folderHide Details Set the Compressed attribute Apply the changes to all folders and files In Hide the D:\Finances folder In Set Read-only on filesHide Details Set read-only on 2017report.xlsx Set read-only on 2018report.xlsx Do not set read-only for the 2019report.xlsx file Explanation In this lab, your task is to complete the following: Compress the D:\Graphics folder and all of its contents. Hide the D:\Finances folder. Make the following files Read-only: D:\Finances\2017report.xlsx D:\Finances\2018report.xlsx Complete this lab as follows: 1. Compress a folder as follows: a. From the taskbar, open File Explorer. b. Maximize the window for easier viewing. c. In the left pane, expand This PC. d. Select Data (D:). e. Right-click Graphics and select Properties. f. On the General tab, select Advanced. g. Select Compress contents to save disk space. h. Click OK. i. Click OK. j. Make sure Apply changes to this folder, subfolders and files is selected. k. Click OK. 2. Hide a folder as follows: a. Right-click Finances and select Properties. b. Select Hidden. c. Click OK. 3. Set files to Read-only as follows: a. Double-click Finances to view its contents. b. Right-click 2017report.xlsx and select Properties. c. Select Read-only. d. Click OK. e.
    [Show full text]
  • Text Editing in UNIX: an Introduction to Vi and Editing
    Text Editing in UNIX A short introduction to vi, pico, and gedit Copyright 20062009 Stewart Weiss About UNIX editors There are two types of text editors in UNIX: those that run in terminal windows, called text mode editors, and those that are graphical, with menus and mouse pointers. The latter require a windowing system, usually X Windows, to run. If you are remotely logged into UNIX, say through SSH, then you should use a text mode editor. It is possible to use a graphical editor, but it will be much slower to use. I will explain more about that later. 2 CSci 132 Practical UNIX with Perl Text mode editors The three text mode editors of choice in UNIX are vi, emacs, and pico (really nano, to be explained later.) vi is the original editor; it is very fast, easy to use, and available on virtually every UNIX system. The vi commands are the same as those of the sed filter as well as several other common UNIX tools. emacs is a very powerful editor, but it takes more effort to learn how to use it. pico is the easiest editor to learn, and the least powerful. pico was part of the Pine email client; nano is a clone of pico. 3 CSci 132 Practical UNIX with Perl What these slides contain These slides concentrate on vi because it is very fast and always available. Although the set of commands is very cryptic, by learning a small subset of the commands, you can edit text very quickly. What follows is an outline of the basic concepts that define vi.
    [Show full text]
  • Shells and Shell Scripting
    Shells and Shell scripting What is a Shell? • A shell is a command line interpreter that is the interface between the user and the OS. • A “program launcher” of sorts. • The shell: o analyzes each command o determines what actions are to be performed o performs the actions • Example: wc –l file1 > file2 Which shell? • sh – Bourne shell o Most common, other shells are a superset o Good for programming • csh or tcsh – default for command line on CDF o C-like syntax o Best for interactive use. Not good for programming. • bash – default on Linux (Bourne again shell) o Based on sh, with some csh features. • korn – written by David Korn o Based on sh – Some claim best for programming. o Commercial product. Common shell facilities Shell startup When a shell is invoked, it does the following: 1. Read a special startup file (usually in home directory) 2. display prompt and wait for command 3. Ctrl-D on its own line terminates shell, otherwise, goto step 2. Shell startup files used to set shell options, set up environment variables, alias sh – executes .profile if it’s there. ksh – executes .profile if in interactive mode. Executes $ENV (usually $HOME/.kshrc) csh – executes .cshrc if it exists. If a login shell, executes .login bash – executes .bashrc, if a login shell, executes .bash_profile instead Executables vs. built-in commands Most commands you run are other compiled programs. Found in /bin Example: ls – shell locates ls binary in /bin directory and launches it Some are not compiled programs, but built into the shell: cd, echo Input-output redirection prog < infile > outfile ls > outfile 2>&1 # sh stdout and stderr Pipelining commands send the output from one command to the input of the next: ls -l | wc ps –aux | grep reid | sort Before a program is executed, the shell recognizes the special characters such as <, >, |, and rewires the standard input, output, or error file descriptors of the program about to be executed to point to the right files (or the standard input of another program).
    [Show full text]
  • UNIX X Command Tips and Tricks David B
    SESUG Paper 122-2019 UNIX X Command Tips and Tricks David B. Horvath, MS, CCP ABSTRACT SAS® provides the ability to execute operating system level commands from within your SAS code – generically known as the “X Command”. This session explores the various commands, the advantages and disadvantages of each, and their alternatives. The focus is on UNIX/Linux but much of the same applies to Windows as well. Under SAS EG, any issued commands execute on the SAS engine, not necessarily on the PC. X %sysexec Call system Systask command Filename pipe &SYSRC Waitfor Alternatives will also be addressed – how to handle when NOXCMD is the default for your installation, saving results, and error checking. INTRODUCTION In this paper I will be covering some of the basics of the functionality within SAS that allows you to execute operating system commands from within your program. There are multiple ways you can do so – external to data steps, within data steps, and within macros. All of these, along with error checking, will be covered. RELEVANT OPTIONS Execution of any of the SAS System command execution commands depends on one option's setting: XCMD Enables the X command in SAS. Which can only be set at startup: options xcmd; ____ 30 WARNING 30-12: SAS option XCMD is valid only at startup of the SAS System. The SAS option is ignored. Unfortunately, ff NOXCMD is set at startup time, you're out of luck. Sorry! You might want to have a conversation with your system administrators to determine why and if you can get it changed.
    [Show full text]
  • Useful Commands in Linux and Other Tools for Quality Control
    Useful commands in Linux and other tools for quality control Ignacio Aguilar INIA Uruguay 05-2018 Unix Basic Commands pwd show working directory ls list files in working directory ll as before but with more information mkdir d make a directory d cd d change to directory d Copy and moving commands To copy file cp /home/user/is . To copy file directory cp –r /home/folder . to move file aa into bb in folder test mv aa ./test/bb To delete rm yy delete the file yy rm –r xx delete the folder xx Redirections & pipe Redirection useful to read/write from file !! aa < bb program aa reads from file bb blupf90 < in aa > bb program aa write in file bb blupf90 < in > log Redirections & pipe “|” similar to redirection but instead to write to a file, passes content as input to other command tee copy standard input to standard output and save in a file echo copy stream to standard output Example: program blupf90 reads name of parameter file and writes output in terminal and in file log echo par.b90 | blupf90 | tee blup.log Other popular commands head file print first 10 lines list file page-by-page tail file print last 10 lines less file list file line-by-line or page-by-page wc –l file count lines grep text file find lines that contains text cat file1 fiel2 concatenate files sort sort file cut cuts specific columns join join lines of two files on specific columns paste paste lines of two file expand replace TAB with spaces uniq retain unique lines on a sorted file head / tail $ head pedigree.txt 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10
    [Show full text]
  • 5 Command Line Functions by Barbara C
    ADAPS: Chapter 5. Command Line Functions 5 Command Line Functions by Barbara C. Hoopes and James F. Cornwall This chapter describes ADAPS command line functions. These are functions that are executed from the UNIX command line instead of from ADAPS menus, and that may be run manually or by automated means such as “cron” jobs. Most of these functions are NOT accessible from the ADAPS menus. These command line functions are described in detail below. 5.1 Hydra Although Hydra is available from ADAPS at the PR sub-menu, Edit Time Series Data using Hydra (TS_EDIT), it can also be started from the command line. However, to start Hydra outside of ADAPS, a DV or UV RDB file needs to be available to edit. The command is “hydra rdb_file_name.” For a complete description of using Hydra, refer to Section 4.5.2 Edit Time-Series Data using Hydra (TS_EDIT). 5.2 nwrt2rdb This command is used to output rating information in RDB format. It writes RDB files with a table containing the rating equation parameters or the rating point pairs, with all other information contained in the RDB comments. The following arguments can be used with this command: nwrt2rdb -ooutfile -zdbnum -aagency -nstation -dddid -trating_type -irating_id -e (indicates to output ratings in expanded form; it is ignored for equation ratings.) -l loctzcd (time zone code or local time code "LOC") -m (indicates multiple output files.) -r (rounding suppression) Rules • If -o is omitted, nwrt2rdb writes to stdout; AND arguments -n, -d, -t, and -i must be present. • If -o is present, no other arguments are required, and the program will use ADAPS routines to prompt for them.
    [Show full text]
  • DC Load Application Note
    DC Electronic Load Applications and Examples Application Note V 3032009 22820 Savi Ranch Parkway Yorba Linda CA, 92887-4610 www.bkprecision.com Table of Contents INTRODUCTION.........................................................................................................................3 Overview of software examples........................................................................................................3 POWER SUPPLY TESTING.......................................................................................................4 Load Transient Response.................................................................................................................4 Load Regulation................................................................................................................................5 Current Limiting................................................................................................................................6 BATTERY TESTING...................................................................................................................7 Battery Discharge Curves.................................................................................................................7 Battery Internal Resistances.............................................................................................................8 PERFORMANCE TESTING OF DC LOADS...........................................................................10 Slew Rate.......................................................................................................................................10
    [Show full text]
  • Mv-409S (8-14)
    MV-409S (8-14) www.dmv.state.pa.us SUPPLEMENTAL CERTIFICATION APPLICATION FOR THE ENHANCED VEHICLE SAFETY For Department Use Only INSPECTION PROGRAM Bureau of Motor Vehicles • Vehicle Inspection Division • P.O. Box 68697 (TO BE USED FOR CATEGORY 4 TESTING ONLY) Harrisburg, PA 17106-8697 PRINT OR TYPE ALL INFORMATION - MUST BE SUBMITTED BY AN APPROVED EDUCATIONAL FACILITY Upon successful completion of testing, applicants who currently hold an inspection mechanic certification will receive an updated mechanic certification card; applicants who do not hold an inspection mechanic certification will receive a Certificate of Completion. All applicants must be 18 years of age and have a valid operator’s license. A APPLICANT INFORMATION Last Name First Name Middle Name Driver’s License/Photo ID# State Issued From Street Address City State Zip Code County Work Telephone Number Home Telephone Number Date Of Birth Applicant Gender ( ) ( ) r Male r Female Do you currently hold a valid out-of-state driver’s license? (If yes, attach a copy) . r Yes r No *Contact PennDOT’s Vehicle Inspection Division at 717-787-2895 to establish an out-of-state mechanic record prior to completion of this class. Do you currently hold a PA inspection mechanic certification? . r Yes r No If yes, enter the classes listed on your mechanic certification card: ________________________________________ List any restrictions on your driver’s license (if applicable): __________________________________________________ Do you currently hold a valid Pennsylvania driver's license?. r Yes r No If no, enter the operator number on your safety inspection certification card: Have you held a Pennsylvania driver's license in the past? .
    [Show full text]