- EpiData-list - University of Manitoba Mailing Lists

Analysis build 36 released
by epidata-list＠lists.umanitoba.ca 25 Aug '05

25 Aug '05

Analysis build 36 was just released for testing. at http://www.epidata.dk/testing.php Unless users report severe problems, the current build will be released as version 1.0 with some restrictions or removal of commands with problems, see below. Version 0.9 release 5 build 36 * Added or modified o A "select font" on first startup to guide the user for efficient setup of screen o Improved documentation of output formation o Table command can show categories defined as missing o New option controls if more than one instance of the programme can run o Aspects of handling missing value further implemented. o Parsing of strings changed to exclude trailing blanks: e.g "Lion " is the same as "Lion", but not the same as " Lion". o sorting of tables corrected o Tests of homegenity (interaction) in summary stratified 2x2 tables removed until final stable solution is found * Bugs fixed: o "Pointer error" in tables, graphs or describe fixed o Error in table estimates for 2x2 tables o Recnumber now returns number within current select o set listrec was not working Remaining known major issues to settle before v1.0 * Tables must be included in txt formatted log files Known major issues not settled or clarified * Relating files not tested fully * Appending in combination with records marked for deletion * Odds Ratios and RR in tables with Rare data (0 in cells) * Tests of homegenity (interaction) in summary stratified 2x2 tables removed until final stable solution is found Known issues not fixed (put on future list) * Correlate command results in "floating point error" when correlate cannot be calculated * Contents of strings should be converted to UPPER in logical statements to work. e.g. count if upper(v) = "TEST" * Setting format (set number format) is not consistent Kind regards Jens Lauritsen

1 0

match records by field help in verification
by epidata-list＠lists.umanitoba.ca 18 Aug '05

18 Aug '05

[1] I would like to MATCH RECORDS by more than ONE FIELD when preparing double entry verification - is this possible ? And if so, how do I do it ? [2] Once a file is verified, does the corrected data reside in the *.REC or the *_dbl.REC file ? Thank you.

1 0

Re: protecting formulas in check file?
by epidata-list＠lists.umanitoba.ca 12 Aug '05

12 Aug '05

You cannot protect the chk-file completely (e.g. against someone determined to change its contents), but you can protect it from accidental changes it by setting the read-only flag of the file (see "file attributes" of your operating system). Dirk Anthony (epidata-list-request(a)lists.umanitoba.ca) wrote: > I have some coefficient values and equations in my chk file and I wondered > if there was some way to protect them from being changed by another user > down the road? > > In other words, can I structure it so somone in the field can enter the data > into the form but not manipulate, accidentally or otherwise, the chk file > contents?

1 0

protecting formulas in check file?
by epidata-list＠lists.umanitoba.ca 11 Aug '05

11 Aug '05

I have some coefficient values and equations in my chk file and I wondered if there was some way to protect them from being changed by another user down the road? In other words, can I structure it so somone in the field can enter the data into the form but not manipulate, accidentally or otherwise, the chk file contents? Any help would be much appreciated. Thank you! Anthony

1 0

Why does calculation of age at given date not work ?
by epidata-list＠lists.umanitoba.ca 09 Aug '05

09 Aug '05

Question sent to info(a)epidata.dk: I wrote commands as following, which I follow the help commands: dob AFTER ENTRY LET age=round(int(("1997/11/01"-dob)/365.25)) END END But when I change "1997/11/01" into today, as in the following commands, it works! Why so? dob AFTER ENTRY LET age=round(int((today-dob)/365.25)) END END So I just want to ask what is the problem, because I strictly followed your commands in help manual, but age cannot be calculated on a given date. The formulations above are correct, with one exception. THe help file says also: EpiData was made in Europe and here dates are written in the notation dd/mm/yyyy, so to make the statements above work LET age=round(int(("1997/11/01"-dob)/365.25)) should be: LET age=round(int(("01/11/1997"-dob)/365.25)) regardless of which format dob has. It is better to send questions like this to the EpiData list at: epidata-list(a)lists.umanitoba.ca, since the info @ epidata.dk is very often overly filled with spam mails. Jens Lauritsen Coodinator and initiator of EpiData

1 0

Re: EpiData-list Digest, Vol 22, Issue 2
by epidata-list＠lists.umanitoba.ca 08 Aug '05

08 Aug '05

To see value labels you need not (only) the question file (.qes) but the records validation file, as well. One possibility for the different results you obtain is that the validation file (.chk) is not always in the directory EpiData expects it to be - EpiData lets you enter data, create a codebook etc. even if no validation file exists (or if the validation file is in a different directory as the records file .rec). In that case, however, no value labels can be applied. Dirk Cahterine Mathews (epidata-list-request(a)lists.umanitoba.ca) wrote: > Hi > We're using version 3.1, downloaded from the Epi Data site. This is the > first time we've used Epi Data. We are in the process of entering data > into it. Initally, when we created a codebook from the QES file, the > codebook displayed the values together with the value labels. But in > subsequent attempts to create a codebook from the same QES file, we have > found that the codebook won't show the value labels we entered into the > QES file. Sometimes it won't even show the values. Do you have any > ideas about this? ************************************************* Dr. Dirk Enzmann Institute of Criminal Sciences Dept. of Criminology Edmund-Siemers-Allee 1 D-20146 Hamburg Germany phone: +49-040-42838.7498 (office) +49-040-42838.4591 (Billon) fax: +49-040-42838.2344 email: dirk.enzmann(a)jura.uni-hamburg.de www: http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/E… *************************************************

1 0

data labels
by epidata-list＠lists.umanitoba.ca 08 Aug '05

08 Aug '05

Hi We're using version 3.1, downloaded from the Epi Data site. This is the first time we've used Epi Data. We are in the process of entering data into it. Initally, when we created a codebook from the QES file, the codebook displayed the values together with the value labels. But in subsequent attempts to create a codebook from the same QES file, we have found that the codebook won't show the value labels we entered into the QES file. Sometimes it won't even show the values. Do you have any ideas about this? Thanks! Catherine Mathews School of Public Health and Family Medicine University of Cape Town

1 0

Warmning: False Virus sent in name of EpiData
by epidata-list＠lists.umanitoba.ca 01 Aug '05

01 Aug '05

Warning of Virus sent in name of Epidata 1. Aug 2005 Users are warned against the spread of virus assumingly sent by epidata.dk. Known titles of these are IMPORTANT NOTIFICATION You have successfully updated your password Your Account is Suspended For Security Reasons And assumingly these are sent by: support(a)epidata.dk or webmaster(a)epidata.dk or admin(a)epidata.dk There is NO system at EpiData.dk which would send such information. Simply delete the mails without opening. I do not understand why someone are misusing the internet and collaborative efforts by spreading electronic virus. Quite disturbing to all of us. Regards Jens Lauritsen, EpiData Association

1 0

Status of EpiData Analysis development
by epidata-list＠lists.umanitoba.ca 08 Jul '05

08 Jul '05

Since release of first public test build of analysis in october last year good progress has been made. In judging progress it is important to recognize the nature of the EpiData Association, the size of economic contributions for development and the pricing principle - freeware. The latest build is available from http://www.epidata.dk/testing.php The list of what is fixed and remaing by build number is seen at: http://www.epidata.dk/analysisinfo/docs/versioninfo.htm The bug reporting database is shown at: http://asp.epidata.dk/support/default.asp The routine tests now include more than 350 conditions looking at as well overall, stratified and segmented conditions and comparing to external standard estimates. The aim of the complete test suite is to certify all available commands for a chosen number of representative datasets. The definite condition to meet before release is that the quality system certifies as well stability as correctness of estimation. But also that the implemented principles are logical in structure and documented such that decisions and requirements are clear to the end user. An example of this is the latest preparation of a detailed description of the principles of the output implementation of html and style sheets. The number of combinations of font selection, sizes and character sets is very large requiring control at the level of the end-user. This is available now, but for persons with very little or no knowledge in HTML and stylesheet principles the control of output can be a mystery. The status list includes : a. The main design principle of user interface, output formulation, number of commands, principle of missing data is final and most of it working. b.Finalisation of a simple way for users to define interface with local fonts etc. as part of the installation is almost finished. c. A coherent strategy for handling missing values across commands is being implemented. d. Some issues of table estimation exist. E.g. with correct turning of outcome and exposure. Some "Floating point and "Pointer" error messages occurs with some combinations of data e. Some aspects of graphing are giving problems. (Also relates to point b) Re c: e.g. if the user requests frequency tables for say 5 variables: 1. freq a b c d e 2. freq a b c d e /nomissing the first will show all data for all records, whereas the second will demand complete data for all five variables. This principle should be the same across all commands. And the implementation is needed as part of the testing of handling the data correctly. Kind regards -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re:Problems with [-] key for entering missing values
by epidata-list＠lists.umanitoba.ca 05 Jul '05

05 Jul '05

Dirk Enzmann wrote: > Using the following .qes and .chk files with EpiData version 3.1, > EpiData's behavior is strange: > > If I use the [-] numeric key to enter missing values in the field > "schtype", EpiData jumps to the field "male" (i.e. "class" receives no > focus). If I use the [-] key in field "male", EpiData issues the error > message "'-' is not a valid floating point value" although missing > values are defined. > > The problem seems to be the movement to the next field after using the > [-] key, because if I drop field "coder" the problem of field "male" > does not occur. > > Is there a problem in the check file I did overlook or is this a > problem of EpiData version 3.1? Are there any solutions/suggestions? > two problems in above 1. I've noticed that the [-] key sometimes gives this error - the field is not accepted (the missing values are not recognized as legal). This seems to be a random occurrence. Closing the file and starting data entry again has solved the problem for me. 2. The problem of EpiData skipping a field after using [-] to enter a missing value can be addressed for now by checking whether the skipped field is blank before proceeding (see below). This problem only arises when the default missing value has the maximum number of digits in a numeric field. In Dirk's case, missing value is 9997 or 9999 in a #### field. Another solution is to make these special missing value codes negative numbers (e.g. -1) or smaller numbers (e.g. 999), which will be smaller than the field size. Then there is no skipping. This problem does not occur with fields of length one. Jamie Hockin Public Health Agency of Canada --------------------------------- * -- .chk -------------------------------- LABELBLOCK LABEL country * [0.2 ] 430 Austria 320 Belgium 3870 "Bosnia and Herzegovina" 11 Canada 3850 Croatia 3570 Cyprus 4200 "Czech Republic" 450 Denmark 440 "England and Wales" 3720 Estonia 3580 Finland 330 France 490 Germany 360 Hungary 3540 Iceland 3530 Ireland 390 Italy 3710 Latvia 3700 Lithuania 310 Netherlands 442 "Northern Ireland" 470 Norway 480 Poland 70 Russia 441 Scotland 3810 Serbia 3860 Slovenia 460 Sweden 410 Switzerland 10 "United States" 580 Venezuela END LABEL schtype * [0.3 ] 1 "slot1 (lowest grade)" 2 slot2 3 slot3 4 slot4 5 slot5 6 slot6 7 slot7 9998 "other schooltype" 9999 "no answer" END LABEL class * [0.4 ] 9997 "ambiguous answer" 9999 "no answer" END LABEL male * [1.0 ] 1 male 2 female 7 "ambiguous answer" 9 "no answer" END END * ======================================== BEFORE FILE HELP "ISRD2 pilot study nation" END * ======================================== casenum * [0.1 ] KEY Autosearch casenum RANGE 1 9999 MUSTENTER TYPE STATUSBAR "CaseNum = " END country * [0.2 ] * RANGE 1 9996 BEFORE ENTRY IF (ISBLANK(country)) THEN COMMENT LEGAL USE country SHOW ENDIF END COMMENT LEGAL USE country MUSTENTER REPEAT TYPE COMMENT END schtype * [0.3 ] RANGE 1 9996 MISSINGVALUE -1 * COMMENT LEGAL USE schtype MUSTENTER * TYPE COMMENT END class * [0.4 ] RANGE 1 9996 MISSINGVALUE 9997 9999 * COMMENT LEGAL USE class MUSTENTER AFTER ENTRY IF (class = 9997) THEN WRITENOTE "ambiguous answer" ENDIF END * TYPE COMMENT END male * [1.0 ] RANGE 1 2 MISSINGVALUE 7 9 * COMMENT LEGAL USE male * before entry * if (isblank(class)) then * goto class * endif * end MUSTENTER * TYPE COMMENT AFTER ENTRY IF (male = 7) THEN WRITENOTE "ambiguous answer" ENDIF END END coder * [66.0s] BEFORE ENTRY if (isblank(male)) then goto male endif TYPE "(alphanumeric)" GREEN END MUSTENTER WRITENOTE "@coder" END * -- end .chk --------------------------------

1 0