March 2006 - EpiData-list - University of Manitoba Mailing Lists

RE: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File)
by epidata-list＠lists.umanitoba.ca 28 Apr '06

28 Apr '06

Hello! I totally agree with you Max on this question. Cheers, Bellinda -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list(a)lists.umanitoba.ca Sent: Thursday, March 09, 2006 6:35 PM To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How should EpiData Analysis read a CSV (CommaSeparated File) Hello Jens, I would strongly argue that a missing is a missing and a 0 (zero) is a very distinct value - hence never turn missings into zero by default... or in short: Option 2 Bests Max On 10 Mar 2006, at 10:21, epidata-list(a)lists.umanitoba.ca wrote: > A question has come up. > > Please consider how you find reading of a CSV file in analysis > appropriate: > > > In a csv file the following data is found: > id, s, pos, sex, ill > 1,.,.,f,0 > 2...... etc (rest of records) > > The data in line can be interpreted in two ways: > Option 1: > ID= 1 > s= 0.0 > pos=0.0 > SEX = "f" ill = 0 > > Option 2: > ID= 1 > s= . > pos=. > SEX = "f" ill = 0 > > In other words the question is how to read ",.," should it be: > Option 1: as 0.0 (which is current behaviour) > or Option 2: . > > Any comments on desired behaviour appreciated. > > regards > > Jens Lauritsen > EpiData Association > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 3

RE: [EpiData-list] second try: order of missing valuesindocument->codebook
by epidata-list＠lists.umanitoba.ca 30 Mar '06

30 Mar '06

I gave it a try: - When the variable is NUMERIC (as it is the case in your file), missing (.) values appear at the end of the tabulation. When it is STRING, missing (.) values appear at the top of the tabulation as follows: var1S -------------------------------------------------------------------- var1S type: Texte majuscule Libellés des codes: libellé_var1s manquant: 3/7 valeurs uniques: 4 tabulation: Freq. P.100 Valeur Libellé 3 42.9 . 1 14.3 1 1 1 14.3 2 2 2 28.6 3 3 var2N -------------------------------------------------------------------- var2N type: Numérique Libellés des codes: libellé_var1s manquant: 3/7 fourchette: [2 ; 3] valeurs uniques: 3 tabulation: Freq. P.100 Valeur Libellé 3 42.9 2 2 1 14.3 3 3 3 42.9 . Note: as shown in your example, there is a redundancy in the checkblock: the variable is controlled by a list if valid values ('label_ramde7'), AND there a Range command (0-10,98). As it is already controlled by the list, it is not useful to control it twice with 'Range - legal'. Choose either of the 2 control systems, remove the other one, and check again. ______________________________________________ Gilles DELMAS Institut de Veille Sanitaire Dept. Maladies Infectieuses, Unité infections entériques, alimentaires et zoonoses 12 rue du Val d'Osne 94415 Saint-Maurice cedex - France + 33 1 41 79 67 27 g.delmas(a)invs.sante.fr ______________________________________________ -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : mardi 28 mars 2006 00:00 À : epidata-list(a)lists.umanitoba.ca Objet : RE: [EpiData-list] second try: order of missing valuesindocument->codebook That variable is a 2 digit number created with ## in the qes file. Here's the rest of the info about the variable in the codebook: type: Number value labels: label_ramde7 range/legal: 0-10,98 missing: 6/52 range: [3 ; 10] unique values: 8 epidata-list(a)lists.umanitoba.ca wrote: What kind of variable is it? This shouldn't happen id the variable is numeric. -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 24 mars 2006 23:40 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] second try: order of missing values indocument->codebook Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates. _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list --------------------------------- Blab-away for as little as 1¢/min. Make PC-to-Phone Calls using Yahoo! Messenger with Voice.

1 1

RE: [EpiData-list] second try: order of missing values indocument->codebook
by epidata-list＠lists.umanitoba.ca 30 Mar '06

30 Mar '06

What kind of variable is it? This shouldn't happen id the variable is numeric. -----Message d'origine----- De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca] Envoyé : vendredi 24 mars 2006 23:40 À : epidata-list(a)lists.umanitoba.ca Objet : [EpiData-list] second try: order of missing values indocument->codebook Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 4

second try: order of missing values in document->codebook
by epidata-list＠lists.umanitoba.ca 24 Mar '06

24 Mar '06

Didn't hear from anyone, so I'm trying again (sorry). I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution ofvalues for thevariables. I just noticed that the missing values (.) appear at an almost random point in the otherwise ordered list (in this example,between 9 and 10). I compared the codebook with SAS tables and the data appear to be correct. tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 0

re: variable names
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

You can change this by selecting the option to use the first word as the field name (under File, Options, Create data file tab). This is described in the help files. You may have to reset your options when you install a new version. There is a newer version on epidata.dk now (12 March 2006) Jamie ============================= In the latest version of Epidata (12012006) field names is not functioning well. I choose field names to be the first word in the line and the software assigne the name with 10 first characters in the line. I can change field names but it is a lot of work. Is it any other solution? Luciana Petrucci Gigante

1 0

First word versus first 10 characters for field naming in EpiData Entry v3.1 (12012006)
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

We are looking into this problem, which is an error in the installation routine NOT in the actual software once installed. To get the correct behaviour you desire do this: 1. Start epidata.exe 2. Go into the options (see file menu) 3. Choose the "Create data file" part 4. Select either "first word" or "automatic" as you please. The issue in relation to installation will be solved, but until so do as shown in point 1-4. Regards Jens Lauritsen EpiData Association

1 0

Field names
by epidata-list＠lists.umanitoba.ca 23 Mar '06

23 Mar '06

In the latest version of Epidata (12012006) field names is not functioning well. I choose field names to be the first word in the line and the software assigne the name with 10 first characters in the line. I can change field names but it is a lot of work. Is it any other solution? Luciana Petrucci Gigante luciana(a)homemail.com

1 0

tabulation in documentation->codebook
by epidata-list＠lists.umanitoba.ca 22 Mar '06

22 Mar '06

I have been creating a dataset using epidata. I was looking through the documentation->codebook to get a sense of the distribution of values for the variables. I just noticed that the missing values appear at an almost random point in the otherwise ordered list (in this example, between 9 and 10). tabulation: Freq. Pct. Value Label 2 3.8 3 1 1.9 4 2 3.8 5 6 11.5 7 7 13.5 8 7 13.5 9 6 11.5 . 21 40.4 10 Any ideas why this might happen? thanks. Richard Herrell NIH --------------------------------- Yahoo! Messenger with Voice. PC-to-Phone calls for ridiculously low rates.

1 0

RE: EpiData-list Digest, Vol 29, Issue 8
by epidata-list＠lists.umanitoba.ca 22 Mar '06

22 Mar '06

either a) or c)with notification -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Mon 3/20/2006 1:23 PM To: epidata-list(a)lists.umanitoba.ca Cc: Subject: EpiData-list Digest, Vol 29, Issue 8 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

RE: Design decision.... Restricted words
by epidata-list＠lists.umanitoba.ca 21 Mar '06

21 Mar '06

> Should we : > a. Adopt a strategy, where users are warned when creating files where > field names/variables are > given the same names as a restricted word - a warning. > > b. Maintain current where users will find out since either an error or > occur or nothing happens when > they create confusion in this way - a "non-friendly" way towards > users. > > c. A strategy where field names cannot have the same names as functions. > - a restrictive strategy. Hi, I don't fully understand what option a) implies. If an user receives a warning, can (s)he continues working?. And what next?. Will (s)he get an error sometimes?. In my opinion if there is a risk of conflict bettwen a command or funtion name and the name of a field or variable this name should be prohibited. So, i think the most restrictive option should be implemented (whith a very clear message saying "the word XXXXX is a reserved word, choose another for your variable name"). Saludos, Pedro Pedro Arias Bohigas John Ericssons gatan, 12 5 tr 112 22 Stockholm Sweden Phone (cell) 0734421130 Phone (international calls)+46734421130

1 0