- EpiData-list - University of Manitoba Mailing Lists

Re: EpiData-list Digest, Vol 22, Issue 7 (Out of office)
by epidata-list＠lists.umanitoba.ca 25 Aug '05

25 Aug '05

I will be back at my desk on Monday 5 September 2005 . Until then my access to email will be very limited, and I will address most of it upon my return. If there is anything requiring urgent attention, please contact: Rebecca.Collins(a)lshtm.ac.uk +44 020 7927 22 14 or Rachel.Clarke(a)lshtm.ac.uk +44 020 7927 22 14 Kind regards Kristof >>> epidata-list 08/25/05 18:01 >>> Send EpiData-list mailing list submissions to epidata-list(a)lists.umanitoba.ca To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)lists.umanitoba.ca When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..."

1 0

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 17 Aug '05

17 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