Last updated 19 Nov 97
STGFAC computes co-performance factors for any stage in a cluster solution (case or task). These factors are written on a Case or Task Factor file, where each factor is given the name of 'STxxxx/COP', where xxxx is the stage number. It also creates an 'MBR' factor for each specified stage.
Program Invocation
The specific syntax for program invocation varies between operating systems. This document diplays the code for the AIX version.
opt: C Forces all tasks which are not members of the selected stage to be removed (set to BADVAL) from the output task factor. ssss: The study number OM6: Input Overlap Matrix file from task clustering CS6: Input Cluster file from task clustering TF6: Output Task/Case Factor file for task clustering results
STGFAC Control Card
STGFAC: cc 01-06 The literal 'STGFAC' study: cc 08-11 The study number for this run pseq: cc 13-18 The presentation sequence ID title: cc 20-79 Optional report title
Factor Request Card(s)
There is no limit on the number of request cards which can be used in a single run. Each co-performance factor requested must have a valid stage in the cluster solution. The new co-performance factors produced will be added to the Task Factor file. Any blank fields on the card are ignored.
STG: cc 01-03 The literal 'STG' stg1: cc 05-08 The next stage to compute d1: cc 09 The literal '-' or blank stg2: cc 10-13 The next stage to compute d2: cc 14 The literal '-' or blank stg3: cc 15-18 The next stage to compute d3: cc 19 The literal '-' or blank stg4: cc 20-23 The next stage to compute d4: cc 24 The literal '-' or blank stg5: cc 25-28 The next stage to compute d5: cc 29 The literal '-' or blank stg6: cc 30-33 The next stage to compute d6: cc 34 The literal '-' or blank stg7: cc 35-38 The next stage to compute d7: cc 39 The literal '-' or blank stg8: cc 40-43 The next stage to compute d8: cc 44 The literal '-' or blank stg9: cc 45-48 The next stage to compute d9: cc 49 The literal '-' or blank stg10: cc 50-53 The next stage to compute d10: cc 54 The literal '-' or blank stg11: cc 55-58 The next stage to compute d11: cc 59 The literal '-' or blank stg12: cc 60-63 The next stage to compute d12: cc 64 The literal '-' or blank stg13: cc 65-68 The next stage to compute d13: cc 69 The literal '-' or blank stg14: cc 70-73 The next stage to compute d14: cc 74 The literal '-' or blank stg15: cc 75-78 The next stage to compute
By including a '-' character between stages, multiple co-performance factors may be computed. For example, if stg1 had the value 3, stg2 had the value 10, and d1 was blank, the COP factors for stages 3 and 10 would be computed. If the d1 field contained a '-', the COP factors for each stage 3 through 10 inclusive would be computed.
These cards are terminated by an end-of-file or an '@eof' image.
@codap stgfac - ssss om600 cs600 tf600 STGFAC ssss PS0001 Sample title for the Task Stage Co-performance report STG 0001-0008 0121 0012 0148-0150 @EOF
This example computes the co-performance factors for stages 1-8,121,12, and 148-150 and adds them to Task Factor file tf600 (stages based on presentation sequence PS0001). To make the factors NTASK in length, this example uses the OVRLAP matrix file obtained by clustering a transposed (Task Data) file.