THE OMNIGRID MANUAL (GW-BASIC VERSION) PC Version 1.5 April, 1989 PC Versions 1.0 and 1.5 Manual Prepared by Kenneth W. Sewell Department of Psychology University of Kansas Lawrence, KS 66045 (913-864-4919) Original Apple II Versions by John Mitterer and Jack Adams-Webber Department of Psychology Brock University St Catharines, Ontario, L2S 3A1, Canada (416-688-5550) 1 ABOUT THIS MANUAL This manual is intended to allow the full use of the OMNIGRID program on IBM-PC compatible computers via GW-Basic. This manual assumes that the user is familiar with IBM-PC compatible computers and with personal construct psychology and grid theory. If you are not familiar with IBM-PC's, it is recommended that you work through the manuals supplied with your computer. If you are not familiar with personal construct psychology and grid theory, it is recommended that you read the Mitterer and Adams-Webber chapter on OMNIGRID (1988, in J.C. Mancuso & M.L.G. Shaw (Eds.) Cognition and Personal Structure: Computer Access and Analysis. New York: Praeger) as it links the use of this program with the relevant literature. A general introduction to Personal Construct Psychology can be found in Adams-Webber, J.R. (1979) Personal Construct Theory: Concepts and Applications. New York: Wiley. OMNIGRID has been placed in the public domain and as such users are encouraged to share copies with anyone who is interested. If you do make important changes or improvements or you translate OMNIGRID for use on another type of microcomputer, it is requested that you put your version in the public domain as well. Further, it is requested that you contact the original authors and send a copy of your version. ACKNOWLEDGEMENTS Translation of OMNIGRID from the original Apple version was carried out by Doug Heacock of the University of Kansas on funds provided by the Rue L. Cromwell, Ph.D. general research grant #1-2160-60-0002. Kenneth W. Sewell provided the substance of the changes from Apple Version 2.0, tested and debugged preliminary versions of PC Version 1.0, developed and tested PC Version 1.5, and prepared the PC Versions 1.0 and 1.5 Manuals. Correspondence regarding PC Versions should be directed to Kenneth W. Sewell, Department of Psychology, University of Kansas, Lawrence, KS 66045 (913-864-4919). Correspondence regarding Apple versions should be directed to the original authors. 2 USING OMNIGRID The first thing you should do with this disk is to create a back-up copy or two. Since OMNIGRID is not copy protected in any way, any copy program will do. As a general principle, you are encouraged to explore the program as much as possible. Try and set up a grid familiar to you and be your own subject or client by then actually taking the grid and producing analyzed data. Satisfy yourself that the data collection and analyses yield correct results. Explore various options to appreciate the scope of the program and to identify its limits for what you want to do. The authors of OMNIGRID cannot take responsibilty for any faults in this program. If you uncover any bugs, please report them and attempts will be made to repair them. If you are reading this manual, then the disk you have received is in good working order and you have figured out how to print out the manual. In order to actually use OMNIGRID, you need simply boot up your PC with this disk in the default drive. The main OMNIGRID menu will then be displayed. This menu offers four options: (F)ORMAT CONFIGURATION FILE (C)OLLECT DATA (A)NALYSE DATA (Q)UIT On first use, you should select the (F)ORMAT CONFIGURATION FILE option. All menus in OMNIGRID follow the simple convention of allowing choices to be made by typing in the first letter of that option. This is signaled by placing the first letter of the options available in parentheses. Thus, simply pressing the "F" key will be sufficient. Also, all inputs to the program must end with typing the return key. Assuming that this is an unused copy of OMNIGRID, the first question you will be asked is for the name of a "configuration file". Basically, this program is going to ask you from 10 to 30 questions relevant to the design of your grid. The answers you give will determine how the program goes on to administer and analyze your grid. The answers to those questions, which specify the design of a particular grid, are stored by OMNIGRID in a file we call the "configuration file" since it is used to configure the program to your specifications. Having designed a grid and saved that design in a configuration file allows you to to call it up at any time. This way, you can design a particular grid once and have that design available any time in the future without having to re-design it. Also, you can design more than one grid and select the one you desire at any time. Each configuration file which you create requires a name. 3 Following DOS conventions, all file names must begin with a letter and must be between 1 to 8 characters in length. Optionally, the file name may be followed by a period (.) and a 1 to 3 character extension. It is recommended that you select names which describe the particualar grid that each configuration file encodes. At this point, you should type in a name of your choosing (followed by a return). You will now be presented with a second menu, the main menu for the configuration sub-program: (C)REATE A CONFIGURATION FILE (E)DIT A CONFIGURATION FILE (P)RINT A CONFIGURATION FILE (N)EW CONFIGURATION FILE NAME (R)ETURN TO OMNIGRID Again, for your first time through, you should select the (C)REATE A CONFIGURATION FILE option by typing a "C" (followed by a return). This option is the heart of the whole OMNIGRID system. With it, you can design a grid complete with a specification of constructs and elements, method of presentation, and desired data analyses. You will go through a series of questions one at a time. A brief description of all of the questions is given below: 1. NUMBER OF ELEMENTS? Between 4 and 22 elements are accepted. 2. SPECIFY SEX OF ELEMENTS? You can elect to have subjects specify the sex of any elements elicited from them. 3. ELICIT OR SUPPLY ELEMENTS? Element can be elicited from or supplied to subjects, or a combination of both. 4. HOW MANY ELICITED ELEMENTS? 5. RANDOMIZE ELEMENTS? 6. 'SELF' ELEMENT NUMBER? A number of analyses require that one of the elements be the 'self'. if you require those analyses then you will have to specify which element is the 'self'. 7. NUMBER OF CONSTRUCTS? Between 2 and 22 constructs are accepted. 8. BIPOLAR OR UNIPOLAR CONSTRUCTS? 9. ELICIT OR SUPPLY CONSTRUCTS? Constructs can be elicited or supplied (or a combination of both). 10. HOW MANY ELICITED CONSTRUCTS? 11. SUBJECT IDENTIFY POSITIVE POLE OF SUBJECT SUPPLIED CONSTRUCTS? 12. ADAMS-WEBBER FORMAT OR CROMWELL FORMAT? Coding can be aligned with the positive pole of the construct pair (Adams-Webber) or with the subject's original construct/contrast distinction. Since this is a 4 new feature of PC Version 1.5, there is a more detailed discussion of these formats below. 13. RANDOMIZE CONSTRUCTS? 14. SUPPLY OR CREATE TRIADS? 15. CONSTANT ELEMENT IN EVERY TRIAD? 16. WHICH ELEMENT? 17. RANDOMIZE TRIADS? 18. FORM OF ELICITING QUESTION? Two options are given. 19. ROLE CONSTRUCT OR GRID TASK? 20. GRID PRESENTATION FORMAT? You can elect to have subjects rank elements, scale elements, or classify elements on constructs. 21. PRESENT WHICH POLE? 22. (UN)CONSTRAINED ASSIGNMENT? 23. LOWER ANCHOR POINT? 24. UPPER ANCHOR POINT? 25. INCLUDE ZERO? 26. SPEARMAN'S RHO OR KENDAL'S TAU? 27. PRINT AVERAGE CORRELATION? 28. PRINT KENDAL'S CONCORDANCE (W)? 29. PRINT INTENSITY? 30. PRINT VARIANCE IN COMMON? 31. PRINT ELEMENT DEVIANCES? 32. PRINT MATCHING SCORES? 33. PRINT SELF-OTHER DIFFERENTIATION? 34. PRINT SELF-ESTEEM MEASURE? 35. PRINT POSITIVITY BIAS? 36. PRINT UNCERTAINTY (H)? 37. PRINT SALIENCE (S)? 38. PRINT ELEMENT DISTANCES? 39. CENTRE MATRIX? 40. NORMALIZE EACH ROW? 41. PRINT PEARSON'S R? 42. PRINT EXTREMITY MEASURES? 43. PRINT VARIANCE IN COMMON? 44. PRINT ANGULAR DISTANCES? 45. PRINT VARIABILITY OF INTENSITY? This option is available for scaled data. Includes Intensity. 46. PRINT INTER-ELEMENT DISTANCES? 47. PRINT OBSERVED/EXPECTED DISTANCES? 48. PRINT SELF/OTHER DISTANCE? Your answer to some questions will determine which other questions you will be asked. Thus, while the program has a list of 48 questions which it can ask, usually you will only answer 10 to 30 of them to design a particular grid. Please take some time to play with this process by designing a number of grids so that you become comfortable with it. If you are unsure of the meaning of a particular question, simply type "H" for "help". An on-line help file will then present you with some additional information about that question (with the exception of questions 12 which is 5 discussed below). Please note that this help facility is only available in this part of OMNIGRID. NEW FEATURES IN VERSION 1.5 The major thrust of the latest revision of OMNIGRID-PC is the inclusion of an alternative coding format (question 12 above). Earlier versions of OMNIGRID have aligned valence of constructs (when elicited) with a particular coding direction. For example, the two construct pairs of "nice/not nice" and "obnoxious/pleasant" may have valences of +/- and -/+ respectively. In the original coding scheme (referred to here as the "Adams-Webber" format), the positive poles would be aligned on whatever scale is being used (e.g. both 6 on a 1-6 scale; both 1 on binary classification; etc.). This is a useful coding scheme for computing self-esteem, positivity biases, etc. There also exist merits for leaving the construct/contrast order as the subject enters it, i.e. aligning constructs with constructs and contrasts (or opposites) with contrasts, regardless of valence. Earlier verions of OMNIGRID allowed this, but only if construct valences were not elicited. Thus, possible analyses were limited because of no valence information. Version 1.5 includes a "Cromwell" format which leaves the construct/contrast order as the subject enters it, collects valence information on elicited AND SUPPLIED constructs, and prints out the constructs and contrasts in the order of entry along with their valence. All analyses are performed on the "Cromwell" format grid, except for positivity bias, salience, and self-esteem. These latter analyses are performed on a converted "valence grid" which is essentially an "Adams-Webber" format grid (with the lower anchor point adjusted to "1" when using scaled data). The OMNIGRID authors are currently preparing a manuscript describing these coding issues in detail, with special emphasis on their differential clinical interpretation if factor analysis is employed. Additionally, a more sensitive self-esteem measure for scaled data has been added to Version 1.5. The self-esteem measure in Version 1.0 essentially created binary data from the scaled data and then computed self-esteem in the same way as it is computed with binary data. The new measure takes into account the increased sensitivity provided by the scale while yielding a coefficient with the same range of 0 to 1. It is computed by adding the values for the "self" element (from the valence grid if the "Cromwell" format is being used; from a vector adjusted for negative values if the "Adams-Webber" format is being used) 6 and dividing the total by the product of the scale length and the number of constructs. IMPORTANT: Files created using PC Version 1.0 are NOT compatible with Version 1.5. This is because Version 1.5 carries some additional parameters and arrays between the various subprograms. If you have configuration files that you would like to convert to Version 1.5, the easiest method of conversion is to print out the Version 1.0 configuration file and then re-enter it in Version 1.5. Grid data files collected in Version 1.0 need to be analyzed by the Version 1.0 ANALYSE subprogram with the corresponding Version 1.0 configuration file. GENERAL INSTRUCTIONS Please note that if you are planning to have constructs elicited by having the program create triads from a predefined list to be elicited from or supplied to subjects, then there is an important relationship between the number of elements and the number of constructs you specify that you should know about. Specifically, since triads must be built from elements, it must be possible to build a sufficient number of unique triads to elicit all of the constructs required. For example, if you specified 4 elements and 10 constructs, then the program will enter an endless loop since it will try to construct 10 unique triads, while only 4 unique triads can be created with 4 elements. To calculate the appropriate number of triads that can be created from a given number of elements, follow these guidelines: 1) if you have specified m elements, and you do not require that there be a constant element in every triad, then it is only possible to generate m!/(m-3)!3! unique triads, without duplicating some; 2) if you do require a constant element in every triad, then it is only possible to generate (m-1)!/(m-3)!2! unique triads. In keeping with this fact, OMNIGRID will not allow you to request more than the relevant number of constructs to be elicited. This prevents you from having duplicate triads be presented to subjects. To avoid any problems, simply use the appropriate formula to compute how many unique triads you will be able to generate from the set of elements you plan to work with and this will tell you the maximum number of constructs you will be able to have elicited for you. Also, please note that if you elect to have either elements or constructs both elicited and supplied (i.e. if you choose the 'mixed' option for either), then OMNIGRID will not prevent duplication of elements or constructs between elicited and supplied sets. You will be responsible for that. For example, suppose that you have elected to have some elements elicited and some supplied, and that one of those supplied elements happens to be "mother". There is nothing stopping your subject from providing the same element to one of the element descriptions 7 provided during element elicitation. It is recommended that you simply notify your subjects of which elements or constructs you will be supplying and request that they not duplicate those during elicitation. Upon answering the configuration questions, you will then be asked to supply elements or element descriptions, as well as constructs or even triads for construct elicitation, depending on what you have opted for. There are some important limits on the lengths of responses you can give here. Specifically, if you opt for the ranking procedure, the length of elements and constructs which you can supply cannot exceed 18 characters (including spaces). Similarly, if you opted to display both poles of constructs for any of the grid procedures, you will be restricted to 18-character constructs. Under all other circumstances, element descriptions, elements and constructs cannot exceed 38 characters in length. Please note that these restrictions also apply to any elements or constructs which your subjects or clients are required to supply. Finally, please note that comma's (,) cannot be included in construct or element names. If you have chosen to supply the triads for the construct elicitation, the program will ask for each member of each triad. You are to provide the element NUMBER or element description NUMBER corresponding to the element which you wish to include in the triad. Once you have designed your grid, a configuration file with the name you specified will be saved on the disk in the default drive. Configuration or grid files can be on disks in drives other than the default. To do this, specify the drive (A, B, etc.), followed by a colon (:) before the file name. Once a configuration file has been designed, it can be modified by selecting the (E)DIT CONFIGURATION FILE option from the main menu of the configuration sub-program. The editing power given here is rudimentary but useful for creating families of related grids or changing minor errors in the original configuration file specification. It is also useful to print out a copy of a configuration file by selecting the (P)RINT CONFIGURATION FILE option on the main menu of the configuration program. Of course, in order to do this, you will need to have a printer attached to your PC. What you will get when you ask for a print-out is a list of all of the questions you were asked in designing that grid, the answers you gave, the list of element description or elements you supplied, a list of constructs or triads if you supplied them. This useful hard copy makes it easy to recall what each configuration file you have created contains. There are two other commands available from the configuration main menu. One is the (N)EW CONFIGURATION FILE NAME option, which allows you to specify a new configuration file 8 name. This is useful if you wish to create more than one configuration file at a time, or if you wish to create one configuration file and print out another. Finally, you can select the (R)ETURN TO OMNIGRID option to return to the OMNIGRID main menu. Assuming that you have already created a configuration file, you can then collect grid data from a subject or client by selecting (C)OLLECT DATA from the main OMNIGRID menu. It is not necessary for you to do this immediately after creating a configuration file; OMNIGRID was designed to allow you complete flexibility in creating configuration files, collecting data, and analyzing it when you wish. The way this is done can be seen when you choose the (C)OLLECT DATA option. You will first be asked to supply the name of one or two files. One will be the configuration file name desired, the other is for a file called the "grid data file". After the COLLECT program has finished, a subject or client will have completed your grid. The information supplied by that person will be saved in a grid data file with the name you specify here. Again, the file name you choose should cue you as to the identity of the person supplying that grid. Upon supplying the relevant file names, you will be presented the data collection program main menu: (C)OLLECT DATA (N)EW FILE NAMES (R)ETURN TO OMNIGRID You will discover that sometimes there is already a configuration file name and perhaps even a grid data file name printed out when you select this option. Most of the time, this name will be the one you wanted but if it is not, you can change the name of either file to whatever you desire by selecting the (N)EW FILE NAMES option. The collect program requires that you supply both file names for proper operation. The configuration file name tells it where to find information on how to set up this grid and the grid data file name tells it where to store the resulting data. Again, explore the program by completing some grids that you just designed to be sure of what is going to happen when you put subjects or clients on it. As you will see, the operation of the program at this stage is automatically guided by the configuration file, so all you (or the subject or client) need do is follow instructions. Finally, when grid data collection is completed, the grid data file will be saved under the name you supplied previously. Having collected one grid, you can go on to collect others simply by changing the file names as desired. Once data collection is complete, selecting the (R)ETURN TO OMNIGRID option allows the final main choice, namely the (A)NALYSE DATA option. 9 Again, you must supply the data analysis program with a configuration file name and a grid data file name. The configuration file tells the analysis program just which analyses to perform and the grid data file supplies the raw data for analysis. Once you have selected the (A)NALYSE DATA option, the program then automatically loads in the specified configuration file to determine which analyses will be done, loads in the specified grid data file which contains the raw data to be analyzed, and completes the analyses. This program does not store the analyzed data back on disk. Instead, it prints out (on the screen or to a printer as desired) the results for you. This print-out includes a list of elements if they were elicited, a list of constructs if they were elicited, the unanalyzed resulting grid, and the results of all of the analyses you requested. If you specify to route the analysis to a disk file, the program will ask you to name the file, then it will write only the grid data to the specified file. This is to make it convenient to upload the grid to a main-frame computer system if other or more sophisticated analyses are desired. It is important to remember, if you are using the "Cromwell" coding format (described above), the main grid - NOT THE VALENCE GRID - is the information that will be written to the disk file. Once you have gone this far, you will be able to use OMNIGRID to create grid formats, administer them and analyze the data. When you have finished with the program on a given day, it is recommended that you return to the OMNIGRID main menu and choose the (Q)UIT option before turning off the computer. Doing this sets the program up to request new configuration and grid data file names the next time you use it. Good luck! If in exploring OMNIGRID, you encounter difficulties or find limitations which make it less useful for you, please contact the authors. MODIFYING OMNIGRID For a variety of reasons, you may wish to modify OMNIGRID. A "minimalist" stance has been taken in designing the system - an approach which may be most evident in the design of the displays which subjects or clients see. This means that the use of system-specific commands, such as graphics commands, were avoided to minimize the complexity of modifying or transporting the program to other computers. The following information is meant to make it easier to modify the OMNIGRID set of programs. This information, coupled with the listings of the source code which you can print out for yourself should make modification feasible. If you are trying to modify OMNIGRID and are having trouble, let us know. The disk you have includes the following files: COMMAND.COM, the DOS command file that allows the disk to be "bootable." There are also two hidden system files. All 10 three of these are essential for the disk to be used as a system disk. AUTOEXEC.BAT, a batch file that executes OMNIGRID when the disk it booted up. If this file is renamed, typing the name will execute OMNIGRID, but it will not start automatically upon boot up. INQUIRE.EXE, a DOS execution file that is necessary for the proper operation of the PRINTMAN.BAT file explained below. BASICA.EXE, the GW-Basic system upon which OMNIGRID operates. This file cannot be renamed. MANUAL.TXT, a text file which contains the manual which you are now reading. It can be printed using the PRINTMAN batch file (explained next), simply copied to the printer, or transported into a word-processor and printed from there. PRINTMAN.BAT, a batch file which will copy the MANUAL.TXT file to a standard printer. This is done by simply typing "printman" at the DOS prompt. OMNIGRID.BAS, a simple shell program which switches control between the three main programs. CONFIGUR.BAS, COLLECT.BAS, and ANALYSE.BAS, the three main programs which carry out the three main functions of formatting a configuration file, collecting data, and analyzing the data, respectively. CFGHLP.DAT, a data file which contains the help comments associated with any of questions asked by the CONFIGUR program, in the same numerical order as given above. If this file is removed from the disk, the help function in the CONFIGUR program will be disabled. CFGHLP.NDX, an index file that contains codes that point to the proper help comment in the CFGHLP.DAT file when asked for from the CONFIGUR program. If this file is removed from the disk, the help function in the CONFIGUR program will be disabled. FILE.NAM, a random access file used to store the current configuration file and grid data file names as well as the last random number used by OMNIGRID (to be used as a 'seed' for generating the next one. This allows switching between CONFIGUR, COLLECT, and ANALYSE without requiring the user to re-enter the names of those files each time. In addition, each time the users quits OMNIGRID, the names of those files are set to 'Nil' so that upon restart, the system prompts for new file names. 11 PARAM.DSC, a sequential file containing the questions which the configure program prints out when a configuration file is created. CONFIGUR SUBROUTINE STRUCTURE Here is a 'map' of what each of the subroutines in CONFIGURE is designed to do. The numbers are the line numbers at which those subroutines begin. 5 MAIN BODY - CREATE MAIN MENU 20 NAME CONFIGURATION FILE 1000 PARAMETER SPECIFICATION 2000 ELEMENT SPECIFICATION 2200 MIXED ELEMENT ELICITATION 2500 INPUT ELEMENTS 2600 LIST ELEMENTS 2700 EDIT ELEMENTS 3000 CONSTRUCT SPECIFICATION 3500 MIXED CONSTRUCT SPECIFICATION 4000 SUPPLY CONSTRUCTS 4500 SUPPLY CONSTRUCTS 4600 PRINT OUT CONSTRUCTS 4700 EDIT CONSTRUCTS 5000 COLLECT SUPPLIED TRIADS 5500 INPUT TRIADS 5600 PRINT OUT TRIADS 5700 EDIT TRIADS 6000 CREATE TRIADS WITHOUT CONSTRAINT 6500 CREATE TRIADS 5600 PRINT OUT TRIADS 6600 EDIT TRIADS 7000 CREATE TRIADS WITH CONSTRAINT 7500 CREATE TRIADS 5600 PRINT OUT TRIADS 7600 RECREATE TRIADS 8000 LOAD A CONFIGURATION FILE 8100 SAVE A CONFIGURATION FILE 8200 EDIT A CONFIGURATION FILE 2000 ELEMENTS ONLY 3000 CONSTRUCTS ONLY - EVERYTHING 1000,9600,2000,3000 8300 PRINT A CONFIGURATION FILE 8400 PRINT ANSWERS TO QUESTIONS 2600 PRINT ELEMENTS 8500 PRINT CONSTRUCTS 8600 PRINT ALL 9000 HELP SUBROUTINE 9100 YES/NO SUBROUTINE 9200 MOD 16 FOR PAGINATION 12 9300 ITEM CHANGE SUBROUTINE 9400 "HIT RETURN TO CONTINUE" 9600 RE-EDIT QUESTION SPECIFICATION? 9700 ILLEGAL STRING SUBROUTINE 9800 LENGTH TEST 9900 FACTORIAL TEST 16000 CODING FORMAT CHOICE COLLECT SUBROUTINE STRUCTURE Again, here is the subroutine structure for the COLLECT program: 50 MAIN MENU 400 GET NEW FILE NAMES IF NEEDED 1000 COLLECT DATA 2000 ELICIT ELEMENTS IF REQUIRED 2200 CHECK FOR REPETITION 2300 PRINT OUT RESULTS 2400 GET SEX OF ELEMENT IF REQUIRED 2500 EDIT RESULTS 2600 RANDOMIZE ELEMENT DESCRIPTIONS 3000 ELICIT CONSTRUCTS IF REQUIRED 3200 CHECK FOR REPETITION 3300 FIND OUT WHICH POLE IS POSITIVE 3400 SELECT SECOND QUESTION 3500 CREATE TRIADS WITHOUT CONSTRAINT 3600 CREATE TRIADS WITH CONSTRAINT 3700 RANDOMIZE TRIAD PRESENTATION ORDER 4000 COLLECT GRID DATA IF REQUIRED 5000 RANKED DATA 6000 CLASSIFIED DATA 7000 SCALED DATA 600 SAVE GRID DATA 200 GET CURRENT FILE NAMES 250 GET FILE NAMES FROM USER 300 PRINT OUT CURRENT FILE NAMES 700 LOAD CURRENT CONFIGURATION FILE 9100 YES/NO SUBROUTINE 9200 MOD 16 FOR PAGINATION 9300 "WHICH ONE DO YOU WANT TO CHANGE" 9400 HIT RETURN TO CONTINUE 9500 RANDOMIZE ELEMENTS 9600 COUNTERBALANCE POLES 9700 "HIT RETURN WHEN READY FOR NEXT CONSTRUCT" 9800 ILLEGAL STRING SUBROUTINE 9900 LENGTH TEST 11100 ELICIT VALENCE ON SUPPLIED CONSTRUCTS 13 ANALYSE SUBROUTINE STRUCTURE In the same format, the subroutine structure for the ANALYSE program is: 50 MAIN MENU 400 GET NEW FILE NAMES 1000 ANALYSE DATA 2000 RANKED DATA 2500 SPEARMAN RHO 2600 KENDAL'S TAU, VARIANCE IN COMMON, INTENSITY 2700 KENDAL'S W 2800 ELEMENT DEVIANCES 4000 CLASSIFIED DATA 4300 MATCHING AND DEVIATION MATCHING SCORES 4400 POSITIVITY BIAS -- CROMWELL FORMAT 14400 POSITIVITY BIAS -- ADAMS-WEBBER FORMAT 4500 H & S -- CROMWELL FORMAT 14500 H & S -- ADAMS-WEBBER FORMAT 4600 SELF-OTHER DIFFERENTIATION 4700 SELF-ESTEEM -- CROMWELL FORMAT 14700 -- ADAMS-WEBBER FORMAT 4800 INTER-ELEMENT DISTANCES 4900 COMPUTE UNIT OF EXPECTED DISTANCE 6000 SCALED DATA 6100 SELF-ESTEEM -- CROMWELL FORMAT 16100 SELF-ESTEEM -- ADAMS-WEBBER FORMAT 6200 CENTRE MATRIX AND NORMALIZE ROWS 6300 PEARSON, VARIANCE IN COMMON, ANGULAR DISTANCE 6400 EXTREMITY SCORES 6500 INTER-ELEMENT DISTANCES, O/E RATIOS, and SELF/OTHER DISTANCE 200 GET CURRENT FILE NAMES 250 GET FILE NAMES FROM USER 300 PRINT OUT CURRENT FILE NAMES 7000 CREATING CROMWELL FORMAT VALENCE GRID 9200 COMPUTE MOD 16 TO PAGINATE 9400 "HIT RETURN WHEN READY" 9999 WRITE GRID DATA TO DISK IMPORTANT SHARED DATA STRUCTURES While all three main programs use somewhat different variables, there is a great deal of consistency in variable assignment across programs: I,J,& K are always used as index variables A$ is always used to hold temporary inputs 14 N is the number of elements N1 is the number of constructs P indexes which question is being asked in CONFIGURE CC$(50) is an array which holds the contents of PARAM.DSC The contents of the configuration file are loaded into the following files in the order given: P$(52) is an array which holds the answers to questions asked in the CONFIGUR program (we call them parameters) E$(22,2) is an array which holds the elements T$(22,3) is an array which holds the triads C$(22,2) is an array which holds the constructs ED$(22) is an array which holds the element descriptions G(22,22) is an array which holds the grid data. V$(22,2) is an array which holds the construct valences collected in the "Cromwell" format. VG(22,22) is an array which holds the valence grid created in the ANALYSE subprogram which adjusts the "Cromwell" format codes for valence (essentially creating an "Adams-Webber" grid). 15