tree failures and accidents in recreation areas

8/8/2019 Tree failures and accidents in recreation areas

1/33


2/33

TREE FAILURES AND ACCIDENTS IN RECREATION AREAS:

A Guide to Data Management for Hazard ControlL e e A . P a i n e J a m e s W . C l a r k e

CONTENTSPage

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Preparing Data Cards ...................... 5 ERRO R CHECK Program . . . . . . . . . . . . . . . . . . 6

ERR OR CHECK Program ControlCard Format . . . . . . . . . . . . . . . . . . . . . . . 6 Notes on ERRO R CHECK Program . . . . . . . . 7 Listing of Blank Check. Num eric Checkand Field Check Cards . . . . . . . . . . . . . . . . 8 Examples of Failure Analysis Tables . . . . . . . . 18 Listing of ER RO R CHECK Test Cards . . . . . . 10 PUNCH Program ......................... 26

WRITE Program . . . . . . . . . . . . . . . . . . . . . . . . . 11 PUNCH Program (C om plete Listing) . . . . . . . 26 WRITE Program Control Card Form at . . . . . . 11 Specifying Form of Output . . . . . . . . . . . . . . 27 Notes on W RITE Program . . . . . . . . . . . . . . . 12

FAILURE Program . . . . . . . . . . . . . . . . . . . . . . . 13 FAILURE Program Control Card Format . . . . 13 Notes on FAILURE Program . . . . . . . . . . . . . 1 3 FAILURE Tables . . . . . . . . . . . . . . . . . . . . . . 14

PageUse of Level Selector Cardsin FAIL URE Program . . . . . . . . . . . . . . . . 14

28 Selector Field Names forFAILUR E Program . . . . . . . . . . . . . . . . 15

Preparing Selector Cards . . . . . . . . . . . . . . 16 Example of Selector Card Sets . . . . . . . . . . 17

Computer S torage Requirements .......... 17

Preparing Stateme nt Cards to SpecifySelector Fields and R estrict Data . . . . . . . . 27

38 Selector Field Names forPUNCH Program . . . . . . . . . . . . . . . . . . . . 28 Examples of I F Statements . . . . . . . . . . . . . . . 3 0

Pacific Southwest Forest and Range Experiment StationP.O. Box 245

Berkeley. California 947011978


3/33

LEE A. PAINE is a forest pathologist, stationed in Berkeley, studyingproblem s in forest tree diseases, particularly in relation t o evaluation andcontrol of public hazard and safety in wooded recreation sites. He came tothe Pacific Southwest Station from t he Canadian Science Service in 195 7.He holds bachelor's (1943 ) and master's (1 947) degrees in forestry fromthe U niversity of Id aho and a do ctor ate (1951 ) from th e Swiss FederalInstitute of Technology. JAMES W. CLARKE is a computer specialist inthe Station's statistical services group. He joined th e Forest Service in 195 3and has been at the Station since 1962.

Paine, Lee A., and James W. Clarke1978. Tree failures and accidents in recreation areas: A guide to datamanagement for hazard control. Gen. Tech. Rep. PSW-24, 30 p.,illus. Pacific Southwest Forest and Range Exp. Stn., Forest Serv.,U.S. De p. Agric., Berke ley, Calif.A data management system has been developed for storage and retrievalof tree failure and hazard data, with provision for computer analyses andpresentation of results in useful tables. This system emphasizes important

relationships betw een tree characteristics, environmental factors, and th eresulting hazard. Th e analysis programs permit easy selection of subsets ofdata for examination of individual species, sites, and other categories ofinformation. Use of this system allows site managers to control hazard atlower cost to bo th the si te and the budget.Oxford: 907.2:416:304(083.7)Retrieval Terms: hazard tree s; hazard re duction; recreation areas; safetystandards; data management; computer programs.


4/33

INTRODUCTION

managers of wooded recreation areas, theT osafety of the public and protection of site andprop erty are major concerns. Injuries, fatalities, andhigh property losses occur each year as a result of treefailures on such sites. Complete prevention of acci-dents is usually not possible without sacrifice of therecreational values of such a site, but an acceptablelevel of safety can be achieved by modifying theexpected losses associated with public occupancy.Hazard reduc tion can limit such losses to prede finedlevels consistent with site values and public welfare.Lack of permanent records, however, combined withmisunderstanding of the influence of hazard compo n-ents, has made effective hazard con trol very costly inthe past. Today we have enough data on tree failuresto permit most individual agencies to control hazardwith p redictable results at lower cost.For a n umb er of years, State and Federal agencieshave been recording the details of failures and acci-den ts within their jurisdiction. Many have used thisinformation in their own planning and management,and have also provided copies of i t for use in anationwide research program undertaken by the U.S.Forest Service. The failure reports on which data havebeen submitted are patterned on U.S. Forest ServiceForm PSW 4600-3 (fig. 1).Generally, tree failures arerepo rted only if the y were large enough t o inflictinjury or property damage. Most of the terms usedhere have been defined previously, ' b ut o ne or twoshould be emphasized.

A tree failure is the uprooting or breakage of anysignificant part of a tree, when the failure was notdirectly caused by logging or construction work.

Hazard, in this con text , is the expected dollar lossthat will result from mechanical failure of a particulartree during a specific time, such as one year. Itdepends, in part, on the probability that the tree willfail during a given period, and on the contingentprobability tha t a target will be struc k by the tree if itfails. Hazard can only exist, then, if there is a targetof value which may be damaged by the failure. Thetargets under consideration are usually people, fixedor movable property, and agency site improvements.

Paine, Lee A. 1971.Acciden t hazard evaluation and c ontroldecisions o n forested recreation sites. USDA Forest Serv.Res. Paper PSW-68, 10 p., illus. Pacific Southwest Forest andRange Exp. Stn., Berkeley, Calif.

Loss from damage t o th e natural si te or t o the treeitself is not considered in this context.Because all trees would fail in time, reduction ofhazard must be effected by (1) removing part or allof the tree before failure, (2) excluding recreationistsor limiting exposure (especially during high-riskperiods), or (3) a reasonable combination of theseactions. Managers have become increasingly aware ofthese con trol option s and of the critical factors not edon the report form. Our analyses by species andlocality have already begun t o concen trate attentionon the m ore dangerous situations. One result has beena consistent annual decrease in the proportion offailures which cause accidents.

In the course of our research on hazard, we havedeveloped a group of co mp uter programs for retrievaland analysis of desired information from the datasubmitted by cooperating agencies. This user's guideto the programs, in conjunction with the programtape, the coding manual, and the user's own data, willprovide a manager with analyses that will greatlyassist in identifying problems and in achieving eco-nomical control of hazard. D uring the past years, wehave been able to prepare only a limited number ofanalyses for cooperating agencies. Now, almost anyadministrator or manager with access to a large com-puter can carry out his own analyses as needed.

Analyses produced with the data managemen t sys-tem described in this manual will provide a managerwith information on the relative frequency of failuresand accidents, by species; the types of accidents anddollar losses; the classes of failure that have occurredmost ofte n; the d efects that have most frequently ledto failure; and the environmental factors that havetriggered failures. In addition, data on diameterclasses, time of day, mo nth , site, elevation, and otherfactors normally recorded can be analyzed to deter-mine their influence. Relations between class of fail-ure, defect, and environmental factors are also avail-able. Because this information can be related to spe-cific areas, th e hazard inspec tor can localize prob lemsand allocate his time and priorities more effectively.The administrator, with a review of statistics for theover-all area, can recommend intensification of ef-forts where needed and can budget fund s to meetdefined goals. The site planner can identify those siteswith high-risk species or size classes and advise man-agers to avoid or modify them before making heavyinvestments on inappropriate locations.


5/33

REPORT OF TREE FAILURE(Mechanical break, collapse, or uprooting)REPORTING AGENCY: UNIT:(A) Tree and stand (E) Time and location of incident

Species: Approximate hour:Approximate dbh of tree: inches Month, year:Approximate age of tree: Yeam County:Forest type: State:Stand age class:- Overmature Site open for public use: Yes__ No.ature (F) Land ownership- Young-growth-All-age -FederalElevation of site: -State-Other public:(B) Class of mechanical failure -Private-Upper bole (top half) -Public utility-Lower bole-Butt (lower 6 feet) (G) Site category-Limb -Established camp or picnic ground-Root, including uprooting -Other established public use site @(C) Tree defect or fault leading to failure @ -Volunteer site @-Marked trail-Rot (trunk, limb, or root) -Special use site @-Sweep -Roadside-Tree dead - snag -Residence site @-Fire wound - Other: a-Leaning -Urban-Lightning wound-Mechanical wound (H) Property or person directly affected-Cracks or splits -Agency-Fork or multiple top -Recreationist-Twin bole or basal fork - Forest industry-Dead top or branch -Permittee-Concessionaire-Widow-maker or hang-up -Other:-Canker, rust -Contractor-Canker, mistletoe - Public utility-Other:-Unknown or none (I) Consequences- Clean-up work required(D ) Contributing factors - Property damaged:-Wind - Stream bank erosion Property loss estimate:$-Snow - Shallow rooting - Injuries (Do not give tree values)Erosion - Tree striking tree - Medical attention required- Soil - saturation - Other: - Fatalities- Unknown or none(J) Name of site: *Comments:

Only failures of a size capable of inflicting some damage or injury should be reported. Minor limb failures should not be reported unless theywere potentially dangerous. Do not report simple death of a beeor part of a beeunless it resulted in mechanical failure. Trees removed prior tofailure should not be reported.

Forest Service Form PSW-4600-3Rev 6/75)Figure 1-For data management, reports of tree failures and accidents are submitted on a formpatterned after the U.S. Forest Service Form PSW4600-3.


6/33

@ A report should be m ade for:(1) each tree failu re involving property damage or bodily injury;(2) each failure adjacent t o perm anent recreation facilities, hom e sites, or other locatio ns where failures are a threa t t o

property, and;(3) each failure on recreation sites and other high use locations during th e season of public use, whether or n ot the

failure causes damage or injury.@ Check only those defects and con tributing factors which lead to t he actual failure.@ Oth er established public use site: Winter sports, beaches, viewpoints, visitor centers, historical buildings, etc.@ Volun teer site: Undeveloped site with concentra ted public use.@ Special use site: Resorts, service facilities, etc.@ Residen ce site: Agency, private, or permittee-lessor.

Other: Wilderness area sites, open forest, etc.@ Published analyses will no t ind icate th e source of specific incidents.

If ma ny failures occur in your area, reports may be limited t o managed sites normally subject to insp ection and hazardcontrol. Where inform ation is available, however, reports from volunteer and oth er noninspected sites will be of value.

NOTE: A SEPAR ATE FORM SH OULD BE COMPLETED FOR EACH INDIV IDUAL FAILURE. Inclusion of morethan on e failure o n a report prevents correlation of dat a unless all details are identical.

Additional forms may be obtained from your headquarters or by w riting to the following address:Return to: Lee A. Paine Commercial Phone: (41 5) 4 86-3158U.S.D.A. F ores t Service FTS Phone: 449-3158

P.O. Box 245Berkeley, California 94701


7/33

Thus, this data control system is a means of plan-ning and mo nitoring hazard management programs. Itdelineates program modifications dictated by prob-lem areas, species, or con ditio ns, assists in selection ofnew recreation sites, and serves as a useful record inlegal actions when accidents occur. Specifically, thedata processing programs facilitate storage, editing,and retrieval of tree failure and accident data (species,class of failure, target, loss, etc.), and execution ofanalyses useful in hazard contro l management.

The programs and instructions are intended forrecreation site managers and administrators with localor remote access to computers. Although a basicunderstanding of data coding and retrieval is assumed,use of the programs does not require specializedknowledge of co mp uter programming or operation.The illustrations of program control cards, sampledata cards, and sample ou tpu t are given as they wouldbe used on a Control Data 660 0 computer2 under aScope operating system. A programmer or systemsanalyst should be able to modify them easily for usewith other available equipment. Once the programsare made compatible with the local data processingsystem, the procedure for management of the dataand use of the programs is essentially as describedhere.Three of the programs in the system are availableon tape; the fourth is listed in this guide and isavailable on cards. To obtain the programs, send amagnetic tape (1200- or 2400-foot reel) to Director,Pacific Southwest Forest and Range Experiment Sta-tion , P.O. Box 2 45, Berkeley, California 947 01, At-tention: Statistical Services. If your agency has pre-viously subm itted data t o this Station, send a secondtape and request a copy of the data.

In addit ion t o the programs and th e already exist-ing data files, t he coding manual3 is needed so thatnew data files from the failure repor t form s can beestablished. Staff members of agencies and organiza-tions which have no t previously received a printo ut ofthe coding manual should request th at i t be includedwith th e program tapes.

' Trade names and commercial enterprises or products arementioned solely for information. No endorsement by theU.S . Department o f Agriculture is implied.Paine, Lee A. Coding hazardous tree failures for a datamanagement system. Gen. Tech. Rep. Pacific SouthwestForest and Range Exp. Stn., Forest Serv., U.S. Dep. Apic.,Berkeley, Calif. Manuscript in preparation.

The basic procedure for use of these programsrequires the following steps:

1. Pertinent data must have been collected (as infig. 1).

2. Data must have been coded and punched onstandard 80-column data cards as indicated in thecoding manual.

3. Cards should be subjected to the ERRORCHECK program for detection of illegal punches.4. Following any necessary corrections, the data

must be added to any earlier data o n a com putertape, using the WRITE program.

5. Accumulated data on the tape can then besubjected to selective analyses using the FAILUREprograms. These programs provide summaries in oneof seven standa rd tables. The FAIL URE programs areflexible; groups of tree failures associated with speci-fied environmental, geographic, organizational, andspecies characteristics may be studied as easily as asingle group encompassing all reported failures for anagency.

6. As an option, data cards or listings of selectedincidents may be re-created from the data tape usingthe PUNCH program. Cards produced by PUNCHmay be used for editing and resubmission t o a datatape, for special analyses, or for tran smittal of data t oother offices.

In this guide to the ERROR CHECK, WRITE,FAIL UR E and PUNCH programs, the basic eleme nt isthe "control card format" for each program. Contr olcard listings not enclosed in brackets give the actualcommand required by the Scope operating system.For use with other computers, an interpretation ofthe command is given. Comments enclosed in brack-ets < > are descriptive or explana tory. They merelyrepresent actual cards which must be prepared with-out brackets or comments. For example, requires a card with a multiple 7-8-9 punch inthe first column; it represents an end of logicalrecord.

Following the control card format, notes are pro-vided which explain the preparation or use of thecards and any necessary cautions or restrictions thatshould be kept in mind. Such matters as computerstorage procedures and estimates of storage require-ments are also discussed. Finally, where appropriate,sample listings of the con trol cards and data cards aregiven.


8/33

PREPARI NG DATA CARDS

Data relating to failures of individual trees are manual. The codes are then punched in specifiedsubmitted on the "Report of Tree Failure" (fig. 1). locations on standard 80-column data processingAs the reports are received at the coding office, each cards. Tw o cards are required to record relevant datais given an accession num ber and entries are inte r- for each failure. A listing of the cards will loo k likepreted an d coded in accordance with the code the following example:

1 6 2 7 2 1 5 0 3 1 0 0 5 0 1 8 2 0 9 3 5 01 8 7 6 5 4 6 3 9 9 0 2 7 6 0 6 0 1 0 1 1 1 1 0 0 0 916 27 22 0 0 O G O W A R N E R CG q1 6 2 7 8 1 8 0 3 4 8 1 2 5 0 9 2 0 0 0 1 0 9 8 7 6 5 4 6 3 1 9 0 9 7 6 0 1 0 3 9 1 B 4 1 0 0 0916 27 8Z 0 0 0 0 0 I N T E P P T RA TL 9l 6 ? 7 9 1 0 0 1 3 6 1 0 0 02 4 0 0 3 3 0 1 0 3 8 7 6 5 4 6 3 2 3 1 0 7 6 0 1 0 08 1 2 1 2 1 0 001 6 2 7 9 2 1 CAMPR 200 0 0 0 0 7000 x x x x x 01 6 2 8 3 1 5 7 2 1 0 q 9 9 0 1 2 0 0 0 3 0 1 0 5 8 7 6 5 0 6 3 9 9 0 9 7 6 0 1 0 2 3 1 2 1 1 0 0 0 91 6 2 8 3 2 0 0 0 0 0 C A M P S I T E 9 1 91 6 2 8 5 1 5 1 0 2 8 9 9 9 0 2 1 0 1 0 3 0 1 8 7 6 5 4 6 3 0 4 1 0 7 6 0 1 0 44 1 2 4 1 1 0 001 6 2 8 5 5 1 F E N C E 9 0 0 0 0 0 9 0 30 F T SW OF SANTA CLARA TREE 0l M R 6 1 5 O S ? 4 0 4 0 2 0 3 000 4 08 09 8 7 6 5 4 6 3 1 8 0 87 6 0 1 0 2 3 1 2 1 1 0 0 0 91 6 2 8 6 2 0 0 0 0 0 W AYSI DE C G S I T E 1 8 91 6 2 8 7 1 8 0 3 6 4 2 0 0 5 0 2 0 2 0 4 0 1 8 7 6 5 4 6 3 9 9 0 9 7 6 0 1 0 42 1 1 1 1 0 0 0 916?R7?0 0 0 0 0 DAVRY BROWN C G 91 6 2 8 8 1 8 2 4 3 7 1 2 0 1 7 2 0 07 5 0 1 8 7 6 5 4 6 3 1 0 1 0 7 6 2 0 0 61 1 1 1 1 0 0 0 91 6 2 8 8 2 0 0 0 0 0 M A R B L E CREEK CG 9162R91820 I P 9 9 9 2 0 2 0 2 6 3 0 1 8 7 6 5 4 6 3 20 1 0 7 6 0 10 1 9 1 1 1 1 0 0 0 916 2 8 9 2 0 0 0 0 0 HO EG EE' S T RA I L CAMP 91 6 2 Q 0 1 3 0 1 1 8 1 2 0 1 3 2 08 0 5 01 8 7 6 5 4 6 3 9 9 0 4 7 6 0 6 0 0 8 2 1 I 1 0 0 0 91 6 2 9 0 2 0 0 0 0 0 O L D F O L K S FLAT CG 9


9/33

ERROR CHECK PROGRAM After data have been punched on cards, followingthe coding manual format, the cards should bechecked to insure that no errors have been introducedduring the process of coding and punching. The ER-

ROR CHECK program detects illegal code numbers(those no t valid for the specific field), lists them , andidentifies the detected errors. (The program cannot,for the mo st part , detect inco rrect assignment of validcode numbers.)By modifying the "standard" error checkparameter cards, which are listed in the next section,the user can change th e range of illegal code numbersas needed for most data fields. Detection of certainoccurrences, such as the illogical com binatio n of fail-ure classes and associated defects, is part of the pro-

gram and is not easily changed. But the range ofillegal species, for example, can easily be restricted orexpanded to accept only those species normally re-ported to a particular agency.Sample error check test cards are provided for usewith the program. Submitting these data to theERROR CHECK program, either separately or aftervalid data cards, yields examples of various potentialerrors. The value of the test cards is to illustrate themanner in which certain errors are indicated by theprogram, and to verify proper operation of the pro-gram should all new data cards be submitted withouterrors. A listing of th e error check test cards is givenat the end of this section.

ERROR CHECK Program Control Card Format

< JOB CARDR UN ( S l Compile programC O P Y C R ( I N P U T , C H E C K E R ) Copy ERROR CHECK cards to file checkerREW I ND ( CHECKER) Rewind the file checkerL I N K (F=LGO, X I Load and execu te the program

7-8-9 CARD > End of record< ERROR CHECK PROGRAM DECK >< 7-8-9 CARD > End of record

< A. BLANK CHECK CARDS ( 2 ) >< 8 . NUM ERI C CHECK CARDS (2) >< C. F I E L D CHECK CARDS (ANY NUMBER) >

< 9 CARD (COLUMN 1 ) End of field check cards< 7-8-9 CARD > End of record< ERROR CHECK TEST CARDS - O P T I O N A L >< DATA CARDS TO BE CHECKED< 6-7-8-9 CARD * End of job


10/33

Notes on ERROR CHECK ProgramThe listing in the following section shows a "stan-dard" set of the three different types of ERRORCHECK co ntr ol cards. These "blank," "numeric,"and "field" che ck cards may be used as show n, maybe lim ited t o p arameters o f a specific agency, or maybe expanded to accommodate additional species.Normally, an agency would restrict the range of allchecks to the limits of agency data. For example, ifno site lies above 3900 feet elevation, the illegalparameters on the appropriate field check card (seeprintout, following location card 12325) would bechanged to three blanks followed by ,040-998$.In t he listing, t he cards with X's are blank checkand numeric check cards. The remainder are fieldcheck cards. If different cards are desired, theyshould be prepared as described here, using the codemanual as needed. Note that the code manual re-quires that the record of each failure begin on onecard and end on another, so that each failure isrepresented by a pair of cards, rather than a singleone.

Blank Check CardsThere are two b lank check cards, one for each datacard o f a pair. For each unused colum n on data cards,a corresponding column on the blank check cardsmust be blank. For each non-blank data column,enter an X in the corresponding column of the blankcheck cards.Numeric Check CardsThere are also two numeric check cards, one foreach data card of a pair. For each non-alpha column(blank or numeric) on data cards, the correspondingcolumns on the numeric check cards must be blank.For all alpha or alpha-plus-numeric fields on data

cards, enter X in the corresponding columns of thenumeric check cards.Field Check Cards

This part of the deck may contain any number offield check cards for identified fields. Each data fieldto be checked requires a location card and one ormore parameter cards.

Location card locates a field as follows: ColumnI-punch the number of the card containing thespecified field (1 or 2 of a two-card data set). Col-umns 2 and 3-punch first column of field, rightjustified. Columns 4 and 5-punch last colum n offield, right justified. (For 1-column fields, columns 4and 5 will be th e same as colum ns 2 and 3.)Parameter cards follow each location card, and

specify values that are illegal for the field defined inthe location card. The number of digits punched foreach value should correspond with the code manualand the defined length of the particular field. Param-eters begin in c olum n 1 with leading zeros as neces-sary to match the defined field length. When blanksare illegal, the parameter card starts with the appro-priate number of blanks followed by a comma or adollar sign.Parameters may be either a single illegal value or aseries of individual values and/or ranges. Individualparameters are separated by commas. For ranges, thefirst and last illegal values are separated by a dash andfollowed by a comma. The last parameter on a card isfollowed by an asterisk. The last parameter on thefinal parameter card for each location card is fol-lowed by a dollar sign in place of an asterisk. Addi-tional sets of location cards and parameter cards areused as necessary to define all fields to be checkedand th e illegal values for such fields.


11/33

Listing of Blank Check,Numeric Check, andField Check Cards

x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x X x X x x X X Xx x x x x x x X x X x x X x x X x X X X x x x x X x x x X x x x x X X X x x x x X x x x x x x x x x X x X x X x x x x x x x x X X x x x X x x xX X X X X x x X X x x x x X X X x x x x x x x xx x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x10709


12/33

Listing of Blank Check,Numeric Check, and

Field Check Cards(con inued)


13/33

Listing of ERROR CHECK Test Cards

000021001 10 300 27 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 090000?20 0 0 0 1 1 F O R E S T T Y P E E R R O R + C L E A N U P000031001 10 300 18 5 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 090000320 0 0 0 1 1 S T AND AGE CL AS S E RROR T I Mf tE U T Y P E 9000041001 10 300 08 1 005 1 1 01101 01 20 0769 01010 1 1 1 1 0 0 090000420 0 0 0 0 1 DE F E CT COL BL ANK 9000051001 10 300 08 1 005 I 05 05 1 01101 01 20 076Q 01010 1 1 1 1 0 0 090000520 0 0 0 2 1 D E FE C T I S R E PE A TE D T W I C E 9000061001 10 300 08 1 005 5 01 0 4 01101 01 20 0769 01010 1 1 1 1 0 0 090000620 0 0 0 3 1 C O N F A C T O R S R E P E A T E D T i N I C E 9000071001 10 300 08 1 005 5 01 2 01101 01 20 0769 01010 1 1 1 1 0 0 090000720 0 0 0 0 1 COL 38 B LA NK ( C O N T R I B U T I N G F A C T O R ) 9000081001 10 300 08 1 005 5 01 1 1 1 01101 01 20 0769 01010 1 1 1 1 0 0 090000R20 0 0 0 1 1 D E F E C T C O N F L I C T W I T H C L A SS OF F A I L 9OOOO'm Ol 10 SO0 08 1 005 4 01 3 01101 01 20 0769 01010 1 1 1 1 0 0 090000920 0 0 0 2 1 C ON . F A C TO R C O N F L I C T C L A S S OF F A I L 9000101001 10 300 08 1 005 1 01 1 05001 01 20 0769 01010 1 1 1 1 0 0 090001020 0 0 0 2 1 AGENCY CODE ERROR q000111001 10 300 08 1 005 1 01 1 01101 01 27 0749 01010 1 1 1 1 0 0 090001 120 0 0 0 3 1 HOUR ERROR 9000121001 10 300 08 1 005 I 01 1 01101 01 20 0769 01010 1 1 9 1 0 0 090001330 0 0 0 1 L A N D O W N E R S H I P E R R O R 9000141001 10 300 08 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 3 1 1 00001431 CAR 5 1 1 0 0 I I N J U R Y - - P E R S O N A F F E C T E D R E C .000161001 10 300 08 1 005 1 17 1 01101 01 20 0769 01010 1 1 1 I 0 0 090001620 0 0 0 0 1 D E F E C T E R RO R ( NO S U C H P E F E C T ) 9000171001 1 300 08 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 090001720 0 0 0 0 1 DBH ERROR COL 12 BL ANK 9000301001 10 300 O R 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 2 0 0000?0?1 CAR 5 0 0 0 0 1 2 I N COL 75000?21888 10 926 82 7 005 6 16 05 02 9 2 3 01101 01 20 1369 51010 1 1 1 2 0 0OOOZ2B? CA R 5 0 0 0 0 1 2 I N COL 75 AND S/7 + M U L T I P L E S 9000331 36 ?50 06 4 055 2 16 1 ? 01517 04 99 0170 01031 2 1 1 1 0 0 090002320 0 0 0 0 1 COLUMN 7-9 ( NO S P E C I E S ) 9000321 88 888 21 0 978 8 20 03 03 ? 1 66 09 0077 09444 322 3 3 3 3 390003230 0 0 0 0 M U L T I P L E E R R O R T E S T E R 0000351001 10 300 08 1 005 2 01 051 1 01101 01 20 0769 01010 1 1 1 1 0 0 09 0003530 0 0 0 0 1 COL 34 SHOULD BE BL ANK 9000371701 10 300 08 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 090003820 0 0 0 0 1 C L A S S OF F A I L F R R OR ( NO S U C H C L A S S ) 9000391001 10 300 08 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 2 1 3 3 0003931 5 2 3 2 0 1 C HE CK OM M U L T I P L E I N J + F A T000401001 10 300 Oft 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 0 OOO/O? 0 0 0 0 1 N O 9 I N COL 80 ON CARDS 1 OR 20 0 0 ~ 1 1 0 0 1 0 300 06 1 005 5 04 01 1 01101 01 ZO 0769 01010 1 1 1 1 0 0 09 0004lSO 0 0 0 0 1 D E F E C T S O U T O F ORDER 9000431001 10 300 08 1 005 1 01 1 01101 01 20 0769 01010 1 1 1 1 0 0 09 000431 0 0 0 0 0 1 3 CARD HAS 1 I N CO L. 6 9


14/33

WRITE PROGRAMUsing the cards that have been checked for errors program also edits and deletes data, and makes addi-

and corrected, the WRITE program creates data tapes tions to existing data o n tape.to be used with the FAILU RE programs. The WRITE

WRITE Program Control Card Format

< JOB CARD >RUN (S )COPYCR( INPUTpTAPE3)REWIND (TAPE 31R E QU E ST ( T A P E 2 1 2 7 6 0 4L I NK (FELGO,X)UNLOAD (TA PES )REQUEST(NEW,W)27605REWIND (TAPE 11COPY(TAPElpNEW1UNLOAD(NEW)REQUEST(BACK,W)10407R E W I N D ( T A P E l 1COPY(TAPE1,BACK)< 7-8-9 CARD >< WRITE PROGRAM DECK >< 7-8-9 CARD

L I S T A < OR L I S T >< I L I N E ( O P T I O N A L ) >

E D I T < OR DATA >< NEW DATA CARDS

END< 6-7 -8 -9 CARD >

Compile ProgramCopy the data deck to th e disk file TAPE3Rewind the file TAPE3Mount the current data tape as file TAPE2Load and execute the programRelease the tape driveMount the new data tapeTAPE1 is a disk file containing the new da taCopy TAPE1 t o the tap e file, NEWRelease the tape driveMount another tape and copy the

contents of TAPE1 to it for aback-up of the reel 27605

End of record

End of recordSee Notes

See Notes

End of data cardsEnd of job


15/33

Notes on WRITE ProgramFor WRITE, the new data cards, or the cards to

edit existing data, or both together, should be put insequential order, with card 1 of each pair immed-iately preceding card 2, before they are added to thedata tape.

The control card format as shown provides for amethod-not required, bu t convenient-wherebythree data tapes, one of which is a backup, are used.During the process of adding or editing data, recordsfrom th e current tape (27604) are copied to the newtape (27605), except that those records to be editedare replaced by the input data cards. When all olddata are copied or edited, any new data sets remain-ing in th e card deck are also added to the new tape(27605). Subsequently, the same file is written to th ebacku p ta pe (1 0407).

In this process, 2 760 5 has become the "new" orcurren t data t ape. In t he next revision, 27605 will becalled first and the edited data will be written backon to 276 04. T hus, the two data tapes are alternatelyassigned as th e new tape. Backup 10 40 7 is always acopy of the most recent of the two data tapes. (Thetape numbers actually assigned to tapes will varydepending o n the applicable tape numbering system.)LISTA

Precedes EDIT or DATA card. LISTA provides alisting of the en tire new tape.LIST

Precedes EDIT or DATA card. May be used inplace of LISTA. LIST provides a listing only fromfirst new or first edited data item to the end of alldata.

1LINEIf one-line printed output without comments and

other non-numeric information is also desired, insert1LINE after LISTA or LIST and before EDIT card.LISTA or LIST may be om itted t o suppress thetwo-c ard image listing.EDIT

Must always be used when one or more datarecords in the old data file are to be replaced withnew data, or new data are being added. The new datacards follow the EDIT card and are followed by anEND card. Revised data cards used with EDIT deletethe old records and replace them with the new databearing the same accession numbers.

Special Note: To delete data for a pair of cardswitho ut an immediate replacement, prepare only card1 of the pair, with an asterisk (*) in column 6 afterthe accession number. Place the card in numericalsequence with the other data cards to be edited oradded to the data tape.DATA

Must be used to build a new data tape the firsttime data for a user's agency or specific unit arerecorded on tape. It is used in place of EDIT. Dataare written from cards to fresh tape. LIST or LISTAcard must precede DATA card.END

Must be the next-to-last card in the deck imme-diately after data cards and is followed only by an"end of job" card.


16/33

FAILURE PROGRAM The FAILURE program provides for retrieval fromthe data tape of selected classes or groups of data asrequired. The selected data are summarized and pre-sented in one of seven tables according to the type ofanalysis and format desired.The seven FAILURE tables are produced by fourprograms. (These originally formed a single program,but turn-around time was excessive. Rather than re-design the program to use overlays, we separated the

table functions by making four copies of the pro-gram. We removed from each copy all but theselected table summaries, thus obtaining four smallerprograms which would use less central memory forany given problem.) Separate programs (FAILS,FAIL6, and FAIL7) produce each of the three largesttables. The remaining program (FAIL1 5) producestables 1, 2, 4, and 5.

FAILURE Program Contro l Card Format

< JOB CARDR EQ UE ST ( F A I L ) 4 0 9 7 2 Mount tape containing appropriate FAIL programR E Q U E S T ( T A P E l ) 2 7 6 0 5 Mount current data tapeL I N K ( F e F A I L , X l Load and execute the FAIL program< 7-8-9 CARD > End of record< TABLES CARD > See notes< LEVEL SELECTOR CARDS * See notes< BLANK CARD > End of level selector cards< 6-7-8-9 CARD > End of job

Notes on FAILURE Program

1. TABLES card shows the word TABLES incolumn 1-6 and the num ber of the table desired (1-7)in column 8.2. For all tables, level selector card sets for speciesmust be last in series if species are to be individuallyidentified and analyzed. Each level must include alldata required from subsequent levels (with higherlevel numbers). (See explanation of level selectorcards below.)

Table 1 always requires a level selector card set f orspecies (even when data for all species are desired).Species card sets mus t be last in series.3. Table 6 will contain fewer data than othertables because on some failure reports, hour or monthinformation is missing. Table 6 does not include"hour=99" or "month=99 " (unknown) data (see cod-ing manual).


17/33

TablesThis summary of the tables indicates their con-tent: they are listed here in order of utility. (Theterms 1-way, 2-way, and 3-way refer to the numberof interrelations analyzed in the table.)

Table 7: 1-way, three partsFailures, accidents, and losses by (A) class of fail-ure, (B) defects, and (C) environmental factor^.^ (N odirect interrelations are shown between A, B, and C.)Table 1: 1-way

Frequency of failures by species code number.Table 5: 2-way, two partsFrequency of failures by (A) class of failure bydefect, and (B) class of failure by environmental fac-tor.Table 4: 3-way , on e table fo r each class of failure

Frequency of failures by class of failure, by defectby environmental factor.Table 6: 3-way, one group of tables for each factor,one tab le fo r each class of failureFrequency of failures by selected environmental

factor (wind, unknown/none, other), by class offailure, by m onth by hour of the day.Table 2: 3-way, one table fo r each defectFrequency of failures by defect, by environmentalfactor b y class of failure.Table 3: 3-way, two parts, one table for each defect,and one table for each factorFrequen cy o f failures (A) by d efec t, by species byclass of failure; and (B) by environmental factor, byspecies by class of failure.

Examples of the tables given in a later sectionillustrate their general for m. (Because of their length,it is not feasible to show complete examples of allformats.)Restriction of the data to produce the desiredtables is accomplished in the programs by means oflevel selector cards. The preparation of these cards,according t o the coding manual, is explained below.Temporary storage file requirements of the variouslevels must be provided for in advance; instructionsfor this are also given in a later section .

Use of Level Selector Cards in FAILURE ProgramTo obtain the desired analysis, once the TABLEScard has specified th e table form at, th e level selectorcard must be entered to specify the part of the data

to be included. There are 28 selector field nameswhich can be used with FAILURE. The list of namesincludes an explanation of t he name and the locationof the entry for that name on the data card (eithercard 1 or card 2 of th e two-card set for each failure' The terms "environmental factor" and "contributing fac-tor" are used interchangeably in the programs.

record). Note: The list includes four names to coverlevels of U.S. Forest Service administration-AGENCY, REGION, FOREST, and DISTRICT.These can be used t o cover similar levels of adminis-tration in other organizations. State or Federal parksare given code numbers under FOREST (see codemanual).


18/33


19/33

Preparing Selector CardsThe selector names chosen for a specific tablemust be nu mbered in sequence; these are the levels ofthe analysis. (The number of levels is limited as ex-plained below.) A s erieso f level selector card sets isprepared, with reference to the code manual, in themanner described here.Card 1of a set

Card 1 defines the data field to be searched. Incolum n 2 of the card, the level number ( the sequencenumber for the field names) is entered. Rep etitions ofa particular selector field name (to cover more thanone range in the field) retain the same level number.(In the example of selector card sets see level"3 FORE ST" an d level "4 YEAR.")In colum ns 4 through 9, th e selector field name isentered in the required form show n in the list.In columns 1 1 through 13, a "total" number isentered (right justified), tha t tells how m any separatecode numbers are to be searched in that repetition ofthe level. (The actual code numbers are given on card2.) However, if the code numbers embrace a continu-ous series with no omissions, no entry is made incolumns 11 to 13.The title of the field starts in column 15 and maybe continued through column 44 a t most, except thatFor table 3 the title must terminate by column 32.Any desired informative title may be used.Card 2 and following o f a setThe second c ard contain s the codes for the desireditems for that repetition within the designatedselector field. T he card begins in column 1, with5-digit fields for each code number. Numbers areentered in sequence, with zeros preceding each asnecessary to make each number 5 digits long. Forexample, if the desired code numbers are 3,7, and 9,they would be writ ten 000030000700009. If morethan 16 individual code numbers are needed forSPECIE, they are entered continuously in fields offive on subsequent cards. If the code numbers forman unbroken series, only the first and final numbersare written. For example, 1 through 9 is written0000100009. (Note, however, that if card 1 shows a2 in column 13, the program would select only code1 and code 9. ignoring 2 through 8.)

Coding of certain items on selector card sets maydiffer from that on data card sets. In the codingmanual and on data cards, code numbers vary inlength from o ne to five digits depending on th e items.On data cards, moreover, most code fields are separ-ated by blanks. Exceptions to this rule are certaingroups of field names: the accession number, cardnumber, and tree species which occur in an unbrokenseries; the mon th and y ear; the state and county; andthe agency, region, and forest. In the last group, onlythe first two digits of the five-digit combination referto the selector AGENCY. The third digit is the codefor REGION, and the last two positions define theselector FOR EST. In the selector card sets, a separatelevel is required for each selector name in a group.For example, on data cards, Los Padres Forest inRegion 5 of the U.S. F orest Service is coded 0 150 7.On t he selector card set, however, to retrieve specificinformation for the Los Padres, the selectorAGENCY is written 00001 on card 2, REGION is00005 , an d FORE ST is 00007. These would be levels1,2, and 3.In FA ILURE , a maximum of 10 levels (10 differ-ent selector names) may be used in one run. A maxi-mum of 10 0 selector title cards (100 levels and repeti-tions combined), may be used in each execution. Foreach repetition of the selector name SPECIE there isa limit of 200 individual specifications within therepetition. For each repetition of any other selector,there is a limit of 10 individual specifications withinthe repetition. For example, within FOREST only 10individual fo rests can be specified for each repe titio n;for DBH only 10 individual inch measurem ents canbe specified for each DBH repetition. A continuousrange is not subject to this restriction, however.For discontinuous code numbers, then, with amaximum of 16 code numbers per card, there can be1 2 % cards for a SPECIE repetition. There can onlybe one card, with a t most 1 0 specifications, withinany single repetition of a selector other than SPECIE.The number of tables that will be produced isequal to the product of th e repetitions per level. Thefollowing example would create 1 X 1 X 2 X 4 X 1 or8 tables.


20/33

Example of SelectorCard Sets

< 7 - 8 - 9 C A R D >T A B L E S 7

1 AGENCY 1 C A L I F O R N I A S T A T E PA RK S + RE C0 0 0 5 2? R E GI O N 1 D I S T R I C T 4

0 0 0 0 43 FOREST ALL PARKS I N D I S T R I C T

0 0 0 0 1 0 0 0 3 53 FOREST 1 BLANK STA TE PARK

0 0 0 0 14 YEAR A L L Y E A R S

0 0 0 3 8 0 0 0 7 64 Y E A R 1 1 9 7 6

0 0 0 7 64 YEAR 1 1 9 7 7

0 0 0 7 74 YEAR 1 1978

0 0 0 7 85 S P E C I E 4 1 M I N O R H AR DW OO DS

0 0 5 0 2 0 0 5 0 4 0 0 5 0 8 0 0 5 0 9 0 0 5 1 1 0 0 5 1 3 U 0 5 1 4 0 0 5 1 5 0 0 5 1 6 0 0 5 1 7 0 0 5 1 8 0 0 5 1 9 0 0 5 2 0 0 0 5 2 1 0 0 5 2 2 0 0 5 2 3005240052500526~05270052800 5290~53000531005320053300534~~5 3S00536005370053800539 0054000541005U?005430054400545005~6005U70054 f i< BL ANK CARD >

6 - 7 - 1 - 9 C A R D >Computer Storage Requirements

The FAIL URE program requires a maximum of 10 space, he will need to make some trials with thetempo rary files on a magnetic disk, or drum. The programs before he can estimate exactly what isfiles, called scratc h files, are used by the program t o necessary.store the subset of data required at each level of the As many as nine levels may be written t o scratchsummary, according t o the table selected by the user, files-one less tha n the numbe r of levels neede d forand the selector field names chosen. The first scratch the job. TAPE1 is the file nam e for the data tapefile contains the data selected at the first level, the itself; the scratch file names are TAPE2 throughsecond scratch file contains the data selected for the TAPE10. (TAPE1 1 is also used, but it is a storage filesecond level, and so on. Thus, the number of files to for a table of species selectors. See coding manual.)be used is predictable. The size of each file is not so Central memory or core requirements are as fol-easily know n, however. T his depends on the degree of lows:restriction represented by the user's choice of tableforma t, selector fields, and selector codes, to fit his File Name Coreparticular problem. The first scratch file may besmall, or ma y be nearly as large as the data set itself.The other scratch files will grade downward at somerate peculiar to the problem. If the user's computersystem requires a special request for scratch storage


21/33

Examples of Failure A nalysis TablesGeneral note : The sample data shown in the tablesgiven here are incomplete, and are drawn from onlyone state. Also, for convenience, parts of long tablesor wide-page tables have been omitted, as indicatedby the jagged lines.

Table 7To produce this example of the output for Table7, the following steps have been taken:1. A data tape has been established in the com-puter through proper coding and punching of datacards and use of the ERROR CHECK and WRITEprograms as described.

2. The proper control card format for the FAILURE program, for table 7, has been followed.

3 . Three levels of selector names have beenchosen: AGENCY, REGION, and CLAIM. Selectorcard sets have been properly prepared, using the cod-ing manual for the information desired at each level,and these have been entered in the program, precededby the TABLES 7 card, and followed by a blank card.The result is a table 7 format analysis of all non-catastrophe failures which have been recorded for thespecified regions of the selected agencies.Other TablesThese tables have been prod uced in a man nersimilar to that used for table 7. Selector card setshave been prepared for the information desired ateach level.

1 . S E L E C T E D A G E N C I E S2. S P E C I F I E D R E GI O NS

3. NONCATASTROPHE7A -A B L E T O T A L MIJMRER OF A C C ID E N T F A I L U R E S

8Y C L A S S OF F A I L U R E FO R AL L S P E C I E S (001-999)

U P P E R B O L E 91 3 3 94 65 3 ,14395 37070 2LOWER BOLE 104 5 S 105 60 1 ,17471 10069 6 5B U T T 95 13 3 100 619 .I6155 69078 11R O O T 197 14 1 1 201 1831 .lo976 133 903 14

* T O T A L * 563 42 23 5 7 8 4015 ,14396 361497 3


22/33

T A B L E 78 - T O T A L N U M B E R O F A C C I D E N T F A I L U R E SB Y D E F E C T S / F A U L T S F O R AL L S P E C IE S ( 0 0 1 - 9 9 9 )ROTSWEEPT RE E DE ADF I R E W O U N DL E A N I N GL I G H T N I N GMECH WOUNDC R A C K / S P L I TFORK TOPT W I N B O L EDE AD T OP /BRWIOOH-MAKERC A N K E R , R U S TC A N K E R p M I S TOTHER


23/33

T ABL E 7 C - OTAL NUMBER OF ACCIDENT FAILURESBY C O N T R I B U T I N G F AC TO R S FO R A L L S P E C I E S ( 0 0 1 - 9 9 9 )

SNOW 1 0 9 1 0 1 0 9 7 3 1 . I 4 9 1 1 5 6 5 4 7 1E R O S I O N 7 0 1 7 5 4 . I 2 9 6 3 3 5 8 0 0S O I L S A T U R 57 3 5 5 7 3 8 3 1 4 8 8 3 5 4 1 7 8 3STREAM EROS 13 5 1 13 1 0 7 ,0 8 8 4 4 8 7 7 5 5SHALLOW ROOT 3 8 0 0 36 316 . 1 2 0 2 5 2 4 8 0 5 0TREE X TREE 3 2 2 3 7 0 . 0 4 2 8 6 2 h U O 2OTHER 11 1 0 11 9 U . I 1 7 0 2 2 5 4 5 0

T ABL E 1TOTAL NUMBER OF TREE FAIL .UR BY I N D I V I D U A L S P E C I F S

1 A L L S P E C I E S 7 8 3 0


24/33

5A -- T O T A L N UM BE R O F T R E E F A I L U R E S B Y D E F E C T / F A U L TAND C O N T R I B U T I N G FA C T OR F O R A LL S P E C I E S

UP H O L E 8 746 185 5 6 2 13 7 [ 3 5 6 5 12 6 451

L O W * O L E 11789 977 29 6 4 88 24 8 1 0 0 1 8 8 6 5 2

A L L R O L F * 1946 1723 481 32 b 6 20 14 1103

M U T T 1319 1194 995 5 8 1 41 720 (( 0 1 1 0 16 167

.........................................................................................................................................C O N T R I B U T I N G F A C T O R S

S T R. SHA - T RE E LINK.C LA SS O F ERO- S O I L E R O - L L O h S T K . 0RF A I L U R E H I N D SNOW S I O N S AT . S I G N R O O T T RE E O T HE R NO NE.........................................................................................................................................UP BO L E 342 440 0 1 0 0 32 12 106

LOW BOLE 374 615 0 0 0 0 24 11 132

A L L B O L E * 716 10-55 0 I 0 0 56 ? 3 238

B U T T 403 745 0 0 0 0 34 10 176

* T O T A L * ?a70 1223 7 3 899 314 240 503 84 712


25/33

T A B L F SB -- P E R CE N T A GE O F T R E F F A I L U R E S B Y O F F E C T / F A H L TAND C O N T R I B U T I N G F A C TO R F OR A L L S P E C I E S

L O N B O L E 1.00 .QO .?.7 .OO .OR . 0 ? .On

A L L B O L E * 1 . 0 0 . . ? S .On .OR .02 .08

L I M P 1 . 0 0 . 9? 1 1 0. . 0 0 .00 . 0 0

R O O T 1.00 . Q O . 3 0 .00 .0a .02 . 1 3

* T O T A L * 1.00 .QO .28 . 0 0 .Oh .OZ .15

T A B L E U -- F R E I J U F N C Y O F A S S U C I A T T O N OF O F F E C T S / l - A U L T SI M T H C O N T K I l i U T I N G F A C T O R S FO R A LL S P EC 1 F. S

C L A S S OF F A I L I I K E -- I I P B O L E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..................... O E F F C f / F A U L r rt I N r.1 S NON FKOt i TUM 11 T HEU U N K / N O N E

. . . . . . . . . . . . . . . . . . . . .

R O T 126 3? 0 48

T R E E D E A D 3 1 ? 0 0 3 0

F I R E WOUND I 1 8 0 0 2

L F A N T N G 28 p. 0 5 19

L I G H T N I N G 2 0 0 0 9


26/33

I

TABLE 11 -- F R E Q U E N C Y OF A S S O C I A T I O N OF O F F E C T S / F A U L T SW I T H C O N T R I B U T I N G F A C T OR S FO R A L L S P E C I E S

CLASS OF F A I L U R E -- * TOTAL *- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - =...................................................

D E F EC r / F A U L T W IN O SNOW EHOSION.......................................................................................................R O T 1 0 0 1 7 9 4

SWEEP 1 6 0 I

T R E E D E A D 1 7 0 1 Q

F I R E WOUND 7 5 18 3

L E A V I N G

L I G H T N I N G 5 1 0 1 TABLE (> A -- TOTAL NUMBER OF TREE FA IL UR ES BY MONTH AND HOUR

DUE TO WIND F O R ALL SPECIESC L A S S O F F A I L U R E - UPPER BOLE

M A R 0 0 1 I 0 0 0 0 00 . 0 . . 1 0 . 1 0 0 . 0 . 0. 0 . 0 .

0 0 1 0 0 1 n 0. 2 0 0 . 0. . 2 0 0. 0 .0

EC 0 1 4 Z 2 4 3 0 0 0 40. - 2 2 . 03 - 3 8 .05 0. 0 . 0 . .(I(

Tables 6B and 6C provide data for "unknown/none"or "other" as environmental factor.


27/33

----------------------------------------------- - - - - - -----------

-- -

T A R L F ?A - - F K E Q I I E N C Y DF A S S O C I A T I O N OF D f - F f eC T S / F A U L T S W I T HC l l M T W I B U T l M G F A C T O R S B Y C L A S S OF F A I L U W t

T O T AL T R E F F A I L U R E S F O G A LL S P E C I F S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F A C T O R S I 0 7 AL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UPPEP H O L E L I M B

k 0 T - r i lhf l 1 0 0 1 3 1 1 1 2 6 1 1 7

Table 2B provides data corresponding to 2A , inpercentages; see table 5B.T P P L F 3A -- T O T A L NUMBER OF T R EE F A I L U R E S

A S S O C I A T E D W I T H R OT

5 CALIF. P I N E S 35 7 1 1 0 6- 1 1 7 8 5 -23906 -35690


28/33

TABLE 38 -- TOTAL NUMBER OF T R E E F A I L U R E SA S S O C I A T E D W I T H W IN D

5 CALIF. PINES 1 1 7 125 2 4 ? .I7206 .I8382

6 8 0


29/33

PUNCH PROGRAM The PUNCH program is designed to create quasi- numbered incident. The other listing shows bothoriginal data cards from a data tape, and also to alpha and numeric data as they would appear on eachprovide subsets of data as listings or tapes. The pro- data card pair, whether or not punched cards aregram allows selection of any desired data card sets actually produced as desired output. The PUNCHfrom the data tape. Selector names for any data fields program can also be used to create a new tape con-

can be specified and the range within fields can be taining a subset of data from an existing tape. Thisrestricted as needed. Using this procedure, one may, new tape can thereafter be treated as an original datafor example, request all data for a given species, for a tape and subjected to FAILURE analyses or even tolimited diameter range, for only certain types of sites subsequent PUNCH programs.within one district of a forest of the U.S.' Forest The control card format for PUNCH, given in theService in the state of Montana. A single run will next section, includes the complete program listing.produce either or both of two forms of data card Because PUNCH is a short program, it has been pro-listing and/or quasi-original punched cards that may vided here rather than on the tape available on re-be treated as originals for subsequent computer quest. Therefore, each time the program is used, theanalyses. One form of listing (1LINE) provides all the program cards shown must be submitted to the com-puter.numeric data available in a single line for each

PUNCH Program (Complete Listing)< J O B C A R D >R U N ( S ) ( C O M P I L E P R O G R A M )R E O U E S T ( T A P E 1 ) 2 7 6 0 4 ( MO UN T C U RR E NT D A T A T A P E )L I N K ( F ZL GO , X ) ( L O A D A ND E X F C U T E T H E P R OG R AM )R E M I N D ( P U M C H) ( R EW I ND P UN CH F I L E )C O P Y S B F fP U N C H , OU T P U T ) ( P R I N T AND D E L E T E P U NC H F I L E )< 7 - 8 - 9 C A R D > (END OF RECORD)PROGRAM D A T A O U T ( P U N C H = ~ ~ ~ ~ ~ O U T P U T S ~ ~ ~ ~ ~ T A P E ~ ~ ~ ~ ~ ~ ~ II N T E G E R S P E C I E , D B H , A GE , T I M B E R , S T A ND , E L E V , C L A S S , O E F E C T ( 3 ) t

$ F A C T O R ( 3 ) , A GE NC Y, R E G I O N , F O R E S T , O I S T R T , HO UR , Y E A R *$ S T A T E , C O U N T Y , S E A S O N , O W N E R , S I T E , T A R G E T , F A T A L , C L A I M ,S C O O L L A R , S E T T L E , S R O L L A R , T R E E S , C L E A NC OM MO N B U F F E R , I D A T AI N T E G E R P UN CH , I O A T A ( 4 5 ) , B U F FE R ( 5 0 0 0 )L O G I C A L R E A D 0E Q U I V A L E N C E$ ( I D A T A ( 1 ) p N U M B E R ) p ( I D A T A ( Z ) , S P E C I E ) t ( I D A T A C 3 ) p D B H 1 ,$ ( I O A T A ( U ) , A G E 1 , ( I D A T A ( 5 ) v T I M B E R 1 , ( I D A T A ( 6 ) p S T A N D 1,S ( I O A T A C 7 ) v E L E V 1 , ( I O A T A ( 8 ) v C L A S S 1 , ( I D A T A ( 9 ) t U E F E C T 1 ,S ( I D A T A ( l ? ) , F A C T O R ), ( I O A T A ( 1 5 ) , A G E N C Y ) , ( I D A T A ( 1 6 ) , R E G I O N 1 ,S ( I O A T A ( 1 7 ) , F O R E S T ) , ( I D A T A ( 1 8 ) p D I S T R T 1 , ( I D A T A ( 1 9 1 , H O U R 1 ,!3 ( I D A T A ( 2 0 ) , M O N T H 1, ( I D A T A 1 2 1 ) , Y E A R 1, t I O A T A ( 2 2 ) * S T A T E S ( I D A T A ( 2 3 ) ,C OU NTY ) ( I D A T A (24),S E A S O N ) , ( I O A T A ( 2 5 ) OWNER 1,S ( I D A T A ( 2 6 ) , S I T E ) , ( T O A T A ( Z 7 ) p T A R G E T ) , ( I O A T A ( B ) , I F P R 1 ,$ ( I D A T A ( 2 9 ) , L O S S ) , ( I D A T A ( 3 0 ) , I N J U R Y ) , ( I D A T A ( 3 1 ) p M E O A T T I >S ( I D A T A ( 3 2 ) p F A T A L 1 , ( I O A T A ( 3 3 ) v C L A I M 1 , ( I O A T A ( ~ U ) , C O O L L A R ) P$ ( I O A T A ( 3 5 ) , S E T T L E ) , ( I O A T A ( 3 6 ) v S D O L L A R ) , ( I D A T A ( 3 7 ) p T R E E S 1 ,$ ( I D A T A ( 3 8 ) v C L E A N 1C A L L F E T ( 5 L T A P E 1 , 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 OO OO B,8*64)M T S lA S S I G N 1 0 0 0 T O NO PU NC HA S S I G N 2 0 0 0 T O P U N C HR E A D 1 0 , L I S T1 0 F O R MA T (A 5 )I F ( L I S T . N E . 5 H l L I N E ) GO T O 1 0 0 0KOUMT = 0P R I N T 9 0 0 0P R I N T 9 0 0 1


30/33

PUNCH Program (Complete Listing)(continued)

1 0 0 0 R E A D C l) I D A TA00 5 0 1 = 1, 38I D A T A ( 1 ) s - I D A T A ( 1 )5 0 C O N T I N U EI F ( I O A T A ( 1 ) . E Q . 5 R E N D 1 STOPI F ( I D A T A ( l ) . E 0 . 5 R O A T A ) GO TO 1 0 0 0

< I N S E R T * I F * S T A T EME N T S E L EC T OR C A RD S HE R E B E F OR E RUN . >2 0 0 0 I F ( L I S T . N E . 5 H l L I N E I GO TO 5 0 2 5I F ( KOUNT .LT. 5 0 GO TO 2 0 2 5P R I N T 9 0 0 2P R I NT 9 0 0 1KOUNT = 02 0 2 5 C O N T I N U E

D O 2 0 2 6 1=1, 3 8I F ( ID A T A (1 ) ,EQ. 0 I D A T A C I ) = 02 0 2 6 C O N T I N U EIF(LIST.EQ.SH1LINE)PRINT 9 0 0 3 , ( I D A T A ( I ) , I = 1 , 3 8 )PUNCH 9OO4,(IDATA(I),I=l,27),IDATA(l),IOATA(28),IDATA(39),1 (IDATA(T),I=29,37),(IOATA(I),I=40,45)pIDATA(38)KOUNT = KOUNT + 1GO TO 1 0 0 09 0 0 0 F O R M A T C I H l p 4 1 X , 3 1 H * * * L I S T I N G OF P UN CH ED D AT A * * * / / 19 0 0 1 F O R M A T ( I X , l l l ( l H = ) / l X , l I l H I D SP OBH AGE T T S E L F D EF ES C T / F C ON T R AG R FO D I HR MO Y R ST CO S 0 S P 0 L OS S I M F C C L A I MS S SAMT MU M C / I X , 1 1 0 ( 1 H = ) / / )9 0 0 2 F O R M A T ( l H 1 , 3 5 X , 4 3 H * * * L I S T I N G OF P UN CH ED D A TA ( C O N T IN U E D ) * * * / / I9 0 0 3 FORMAT(1X~R")I5,13,14~13,~2~I4,12,313,312,13,12,713,512,15,412p16,S 12, IS, 14,1219 0 0 4 FORMAT(R5,lH1,13~13,14,13,12,14,IZ,313,312,13,11,12,313~12,213,4I2

S / R 5 , 1 H 2 , 1 1 , l X , A 5 , 1 5 , 4 1 2 , 1 5 , 1 1 , 1 6 ~ 1 4 , l X , 5 A 6 ~ A 5 ~ 1 X p 1 ~EN D< 7 - 8 - 9 C A R D > (END OF RECORD)I L I N E< 6 - 7 - 8 - 9 C A R D W (END OF J O B )

Specifying Form of OutputThe control card format as shown will produce a To suppress punched card ou tpu t, insert:two-card image listing and a 1 LIN E (numeric d ata) REWINDCpUNCH)listing as well as punched card output. To obtain WRITEFCpUNCH)alternative combinations of output, cards may be afteradded or omitte d as follows: REWIND(PUNCH)To suppress two-card image listing, remove: an dREWINDCpUNCH) COPYSBF (PUNCH,OUTPUT)COPYSBF(PUNCH,OUTPUT) or in place of these two cards if the two-card imageTo suppress ' 1LINE listing, remove after END listing is not ne eded.card:

1LINE Preparing Sta tement Cards to Specify SelectorFields and to Restrict DataStatement cards are inserted in the PUNCH pro- numbers are specified which are either equal to, notgram at the point shown in the program listing. Any equal to , less than, or greater than th e numbe rs repre-field or combination of 38 named selector fields may senting the desired characteristics selected for punch-be searched. R estriction of da ta within a field is made ing. Relationships between fields may be additive orby conventional FORTRAN I F statements. Code restrictive.

7-8-9


31/33

As man y stateme nt cards specifying selectors maybe used as needed. When selector fields are restrictive,there should be only one IF statement for each selec-tor field. The I F statements must be capable of onlytw o possible interpre tations-tru e or false. The com -puter must "know" whether to "punch" or not.Examples of suitable statements are given in a latersection.Statement cards begin in column 7 with IF and (,or open parenthesis. Card must end, or be continuedto another card, with column 72. The first card

remains blank in column 6. When a statement con-tinues on a following card, the following card(s) musthave a character other than a zero punched in column6. The dollar sign ($) has been used in this programfor contin uation. Spaces have no significance in thesestatements. The last statement card must end with aclose parenthesis, followed by either GO TO N0-PUNCH or GO TO PUNCH. If it ends with GO TOPUNCH it must be followed by a separate GO TONOPUNCH card. Unlike the IF statement cards, theseparate GO TO NOPUNCH card is punched starting

in colum n seven. If GO TO NOPUNCH concludes thelast of the state men t cards, omit separate GO TONOPUNCH card.

Note: When DEFECT or FACTOR is a chosenselector, the order of selection desired must be speci-fied (see examples of IF statements). This is becausethe coding manual provides that up to three of eachof these items can be punched, in separate locations.If all occurrences of any one defect or factor are tobe selected, the defect or factor must be searched forin all three locations. Exceptions are the defects"rot" and "unknown," and the factors "wind" and"unknow n," which are always in the first location ofthe appropriate field (see coding manual).When NUMBER is a selector, the desired five-digitaccession numbers must each be preceded by 5R(e.g., 5R12345).Blanks and zeros should be assumed equivalent inall columns which are used for data.Redund ancy-to improve accuracy in coding,columns 75, 77, 79, and 80 on card 1 are duplicatedin columns 7, 20, 2 4, and 8 0 on card 2.

38 Selector Field Names for PUNCH ProgramSee coding manual for related code numbers. data cards. Last column gives abbreviated form s thatNext-to-last column gives location of information on will appear as headings on 1LINE ou tpu t.

Selectorfield nameNUMBERS P EC I ED8HA G ET I M B E RS T A N DELEVC L A S SD E F E C T ( 1 )D E F E C T (2 )D E F E C T ( 3 )F A C T O R ( 1 )F A C T O R (2)F A C T O R ( 3 )A G E N C Y

Card numb er 1LINEMeaning and column TitleAccession or inciden t number (e.g., 5R1 2345) 111-5 (211-5) IDTree species 117-9 SPDiametel at 4.5 feet 111 1-12 DBHAge of tree 1/14-1 6 AGEForest type 1/18-19 TTStand age class 1/21 sElevation divided by 100 1/23-25 ELEClass of failure 1/27 FCausal defe ct 1/29-30 DEFECTIFCausal defect 1/32-33 DEFECTIFCausal defect 1/35-36 DEFECTIFCausal environmen tal factor 1/38 CONTRCausal environmen tal factor 1/4 0 CONTRCausal env ironmental factor 1/42 CONTR1st level agency designation 1144-45 AG


32/33

38 Selector Field Names for PUNCH Program(continued)

REG ION 2nd level agency designation RFOREST 3rd level Fores t or park FOD I S T R T 4th level District DIHOUR Time of failure HRMONTH Month of failure MOYEAR Year of failure YRSTATE State in which failure occurred STCOUNTY County in which failure occurred COSEASON Whether in season for public use sOWNER Land ownership 0S I T E Site category sTARGET Property or person affected PI F P ROP Property accident DLOSS Dollar property loss LOSSI N JURY Number of injuries IMEDATT Number requiring medical attention MFATAL Number of fatalities F

Failure category-normal, catastrop he or urban cCDOLLAR Value of property CLAIMSETTLE Data field open for use sSOOLLAR Total value including injuries, fatalities SAMTTREES Uncoded failures associated with repo rt + 1 NUMCLEAN Cleanup required c


33/33

Examples of IF StatementsSome of the conventions used in IF statements are examples illustrate bo th t he inclusive GO TO PUNCHillustrated below. Only on e of the I F statements directive as well as the exclusive GO TO NOPUNCHshown here would normally be used in any one run of when the directive is part of the IF statement. Whenthe PUNCH program. In these statements, .EQ. is GO TO NOPUNCH is used in the IF statement, all"equal to," .NE. is "not e qua l to," .GT. is "greater othe r tha n the designated items are selected. Multiple

than," .LT. is "less than," .GE. is "greater th an or restrictions are illustrated in the last five statements.equal to," and .LE. is "less tha n or equal to." These Note t hat nesting parentheses are used for clarity.

I F ( SP EC I E .EQ. 0 0 1 ) GO TO PUNCHGO TO NOPUNCH Selects only data for species 001I F ( S P EC IE .NE. 0 0 1 ) GO TO NOPUNCH Selects only d ata for species 001I F (S PE C IE .GT. 0 0 2 ) GO TO NOPUNCH Selects data for species 002 and belowI F ( S P E C I E .LT. 0 0 3 ) G O TO PUNCHGO TO NOPUNCH Selects data for species 002 and belowI F (S PE C IE .GE. 0 0 3 ) GO TO NOPUNCH Selects data for species 002 and belowI F ( S P E C I E .L E. 0 0 2 ) GO TO P UN CHGO TO NOPUNCH Selects data for species 002 and below

I F (AGENCY .EO. 0 1 .AND. RE GIO N .EQ. 5 .AND. FOREST .EQ. 02) G OS T 0 P U N C HGO T O NOPUNCH Selects data for forest, within region,within agency specifiedI F ( S PE CI E .L T. 8 0 0 .OR. SP EC I E .GT. 8 2 6 ) GO TO NOPUNCHSelects data for species 80 0 thru 826I F ( S P E C I E .EQ. 801 .AND. CLEAN .FQ. 9 .AND. C L A IM .EO. 1) GO TO$PUNCHGO TO NOPUNCH Selects only California black oakcatastrophe failures which did notcause accidentsI F ( ( S P E C I E .E Q. 8 0 1 .OR. S P E C I E .EQ. 804) .AND. (Y EA R .EQ. 40))SGO T O PUNCH

GO TO NOPUNCH Selects data for species 801 and 8 04failures which occurred in 194 0I F ( ( D E F E C T ( l 1 .EQ. 0 1 ) .AND. ( DE FE CT ( 2 ) .EQ. 0 3 .OR. DEFECT(3)$.EQ. 0 3 1 1 GO TO PUNCHGO TO NOPUNCH Selects only data for failures whentrees were both dead and decayed

tree failures and accidents in recreation areas

Documents