EpiData-list July 2006

epidata-list@lists.umanitoba.ca

1 participants
11 discussions

RE: EpiData 3.1 - Viewing value label in data entry window?

by epidata-list＠lists.umanitoba.ca

Thanks, I've worked it out... I needed to add this code to the start of the check file: BEFORE FILE TYPE COMMENT ALLFIELDS BLUE END cheers leanne. -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca]On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Saturday, 29 July 2006 3:06 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 33, 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..." EpiData-list mailing list ___________________________________ Today's Topics: 1. EpiData 3.1 - Viewing value label in data entry window? (epidata-list(a)lists.umanitoba.ca) 2. Re: EpiData 3.1 - Viewing value label in data entry window? (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Fri, 28 Jul 2006 11:22:52 +1000 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData 3.1 - Viewing value label in data entry window? To: <epidata-list(a)lists.umanitoba.ca> Message-ID: <0FE7A7717D7DB745B5097135D3892EFD01CB09FC(a)accvnt71.accv.org.au> Content-Type: text/plain; charset=iso-8859-1 Hi there all! I have a question regarding viewing value labels when I'm in the data entry window of EpiData 3.1. In the booklet called "Introduction to EpiData" it said that 'blue explanatory text' based on labels in the check file is added to the right of the field by EpiData after data entry ... this is not happening in my file. Can anyone suggest why this might be? All of my files for the data are located in the same subfolder (ie. the qes, rec and chk files for the dataset are in the one folder). many thanks in advance, Leanne. ------------------------------ Message: 2 Date: Fri, 28 Jul 2006 09:46:12 -0400 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] EpiData 3.1 - Viewing value label in data entry window? To: epidata-list(a)lists.umanitoba.ca Message-ID: <44CA1524.4010402(a)binghamton.edu> Content-Type: text/plain; charset=ISO-8859-1 What sort of statement pertaining to the problematic variable(s) do you have in your check file? I've also noticed that in my version of EpiData, the blue text appears only after I tab or enter out of a variable, to the next one. Even if a record already has all its variables filled in, the blue text won't appear until I move to a variable and then tab/enter away from it. --Chris -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton and Wilson Family Practice Residency, Johnson City, NY cryanatbinghamtondotedu GnuPG and PGP public keys available at http://pgp.mit.edu "If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea." [Antoine de St. Exupery] epidata-list(a)lists.umanitoba.ca wrote: > Hi there all! > I have a question regarding viewing value labels when I'm in the data entry window of EpiData 3.1. In the booklet called "Introduction to EpiData" it said that 'blue explanatory text' based on labels in the check file is added to the right of the field by EpiData after data entry ... this is not happening in my file. Can anyone suggest why this might be? All of my files for the data are located in the same subfolder (ie. the qes, rec and chk files for the dataset are in the one folder). > many thanks in advance, > Leanne. > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 33, Issue 8 *******************************************

17 years, 8 months

EpiData 3.1 - Viewing value label in data entry window?

by epidata-list＠lists.umanitoba.ca

Hi there all! I have a question regarding viewing value labels when I'm in the data entry window of EpiData 3.1. In the booklet called "Introduction to EpiData" it said that 'blue explanatory text' based on labels in the check file is added to the right of the field by EpiData after data entry ... this is not happening in my file. Can anyone suggest why this might be? All of my files for the data are located in the same subfolder (ie. the qes, rec and chk files for the dataset are in the one folder). many thanks in advance, Leanne.

17 years, 9 months

Please help: Analysis

by epidata-list＠lists.umanitoba.ca

Hi there I am currently analysing my first survey using Epidata Analysis instead of DOS Epi Info (I hated Windows EpiInfo) and have been using Epidata quite a lot for data entry, so now I am giving Analysis a go! In the DOS EpiInfo I have been able to use the "COMBINE" command to do a freq on a question where more than 1 option can be selected. Eg. Question: In which province do you primarily work? (You may choose more than 1 option) The provinces are then all listed and the respondents just tick In my Epidata REC file I have numbered all the options from 1-10. I repeated the question 4 times in the REC file, so that 4 options could be ticked (my data does not have more than 4 options ticked for this Question - I checked!) I have a dataset with 148 respondents. I know that my denominater will increase with the "combine" command, but I am interested in the percentages only. What command in Analysis will assist me with this analysis problem? Warm regards, Elize Webb School of Health Systems and Public Health University of Pretoria **************************************************************************** ******** This message and attachments are subject to a disclaimer. Please refer to www.it.up.ac.za/documentation/governance/disclaimer/ for full details. / Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar. **************************************************************************** *******

17 years, 9 months

EpiData alignment problem

by epidata-list＠lists.umanitoba.ca

I cannot get past info(a)epidata.com filter no matter what subject I use so I am posting this to the group DEAR Jens and Michael , I have delayed composing this letter for quite some time because I so much appreciate the efforts and accomplishments of the Epidata(ED) team over the years. I was one of the early users and continue to use ED extensively in our very many projects here at the hospital. My problem is that what I see in the QES file is not translated, as it appears, to the data entry screens in the REC file. In other words, the form is not WYSIWIG; in fact, what you see is NOT what you get. What you sometimes get in data entry screens are fields that are scattered all over and the allignment between the lines is comletely lost. This does not happen in EpiInfo(EI). This problem is not apparent in the sample files because they only have one item on a line. To see the misalignment, the QES file must have multiple lines and fields that use the brackets, such as date and boolean fields. I examined the header portion of the REC file generated by both EI and ED and they are essentially identical. The brackets and their conversion are the problem! Consider the following very simple QES file: A<mm/dd/yyyy>B<Y>C___ D___________ E___ F___ Note: the font may be changed by you email client. To see the point being made, letter D should be right under letter A, E should be right under B and F under C using a fixed-width font, such as 'courier new' with no spaces between the fields. I have six fields(A-F) and have intentionally placed B right after A and C right after B. If this file is converted to a REC file in EI, everything is aligned exactly as it appears above. If it is converted in ED, it is not. What EI does is remove the left bracket in field A and shift the REST OF THE LINE one space to the left. It then removes the right bracket from A and again shifts the REST OF THE LINE one space to the left. It then does exactly the same thing for field B. Everything would now be out of alignment with the next line, except that EI then adds two spaces IMMEDIATELY to the right of EACH field from which the brackets have been removed. In fact, if you look at the data entry screen in EI, you will notice that after shifting to the left as described above, two spaces now appear right after field A and two space appear right after field B, and this maintains the alignment with the lines below. ED does exactly the same shifting as EI, but fails to add two spaces to the right of each of these bracketed fields. Changing the font in ED data entry screens to fixed-width does not help. I develop QES files with hundreds of fields of all types, and bracketed fields hopelessly mess up the alignment in both the screen version and in printed forms. While I can now(since I figured it out) make these adjustments in the QES file to maintain alignment, I cannot recommmend ED to any of my less experienced colleagues because the entry screens and printed reports will look disorganized, resulting in a less aesthetic experience and more data entry errors. I must therefore either personally design every form (which I do not have time for), or have them use something horrible like Excel. EpiData is a splendid product and is indeed legacy EpiInfo because it maintains the elegant features of the latter, while adding many new and really useful ones. The loss of alignment between lines, however, sort of ruins things for me although it probably does not affect most users. If my analysis is correct, I hope the program can be modified relatively easily. If I am wrong, maybe you can’t do anything. Either way, thanks again for all you have done for the rest of us EpiInfo lovers. Sincerely Steve Blum, PhD Associate Professor Albert Einstein College of Medicine Dept of Epidemiology and Population Health

17 years, 9 months

RE: [EpiData-list] Four files

by epidata-list＠lists.umanitoba.ca

Hi you four different file (subject) or the same subject ? thanks __________________________ Ibrahim Hussaini Afghanistan Independent human rights commission Phone: (020)2500676- 2500197 Mobile: 0093(0)799155445 Fax: 0093(020)2500677 E_mail: ibrahim_hussaini(a)hotmail.com > To: epidata-list(a)lists.umanitoba.ca> Date: Thu, 13 Jul 2006 13:49:22 -0300> From: epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Four files> > Hi,> > suppose that I have four files. How can I put all in one file???> > Thanks,> > ---------------------------------------------------------------> Silvano Cesar da Costa> Departamento de Estatística e Matemática Aplicada> Centro de Ciências Exatas> Universidade Estadual de Londrina> Campus Universitário> Cx. Postal 6001> CEP 86051-990> Londrina - PR> Fones: (43) 3371 4848 (direto)> (43) 3371 4346 (Secretaria)> > http://www.uel.br/pessoal/silvano> ---------------------------------------------------------------> > _______________________________________________> EpiData-list mailing list> EpiData-list(a)lists.umanitoba.ca> http://lists.umanitoba.ca/mailman/listinfo/epidata-list _________________________________________________________________ Express yourself: design your homepage the way you want it with Live.com. http://www.live.com/getstarted

17 years, 9 months

RE: [EpiData-list] Four files

by epidata-list＠lists.umanitoba.ca

Hi you said you have four different file to put in one file are same file? best regards Ibrahim Hussaini Database Assistant Afghanistan Independent Human Rights Commission Phone: (020) 2500676 - 2500197 Mobile: 0093 (0) 799155445 Fax: 0093(020)2500677 E-mail: ibrahim_hussaini(a)hotmail.com > To: epidata-list(a)lists.umanitoba.ca> Date: Thu, 13 Jul 2006 13:49:22 -0300> From: epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Four files> > Hi,> > suppose that I have four files. How can I put all in one file???> > Thanks,> > ---------------------------------------------------------------> Silvano Cesar da Costa> Departamento de Estatística e Matemática Aplicada> Centro de Ciências Exatas> Universidade Estadual de Londrina> Campus Universitário> Cx. Postal 6001> CEP 86051-990> Londrina - PR> Fones: (43) 3371 4848 (direto)> (43) 3371 4346 (Secretaria)> > http://www.uel.br/pessoal/silvano> ---------------------------------------------------------------> > _______________________________________________> EpiData-list mailing list> EpiData-list(a)lists.umanitoba.ca> http://lists.umanitoba.ca/mailman/listinfo/epidata-list _________________________________________________________________ Express yourself: design your homepage the way you want it with Live.com. http://www.live.com/getstarted

17 years, 9 months

Four files

by epidata-list＠lists.umanitoba.ca

Hi, suppose that I have four files. How can I put all in one file??? Thanks, --------------------------------------------------------------- Silvano Cesar da Costa Departamento de Estatística e Matemática Aplicada Centro de Ciências Exatas Universidade Estadual de Londrina Campus Universitário Cx. Postal 6001 CEP 86051-990 Londrina - PR Fones: (43) 3371 4848 (direto) (43) 3371 4346 (Secretaria) http://www.uel.br/pessoal/silvano ---------------------------------------------------------------

17 years, 9 months

Definition of GCP guidelines and tools

by epidata-list＠lists.umanitoba.ca

Tim C. Responded: Which set(s) of GCP guidelines is Epidata using as the goal? GCP is an abbreviation of "Good Clinical Practice". The whole issue of GCP guidelines is a difficult one. The preparation in itself involves reading a lot of " heavy legal text". The major issue is that the principles are described in lengthy documents, but there is no strict definition as of what it really implies in terms of specific implementation (apart from the principles). I will add a summary of the main documents later. In the most recent time I have been experimenting with various software tools for the task: - bug tracking - developmental documentation of tasks resolved. - documentation in general - testing and verifying software behaviour - how to accomplish solutions which are operating system independent. ........ To develop all the details of this is going to be a lot of work, which is why collaborative efforts are crucial. One of the issues is persontime and funding and another is testing. As soon as I can reveal more details of the work plan and steps of this process the list will be informed. And interested persons invited to participate. Regards Jens Lauritsen

17 years, 9 months

stattables error and test principles.

by epidata-list＠lists.umanitoba.ca

Susanne Widmar pointed out an "estimation" error in a command: > As you can see the missing values are included in the calculation for > the 90th percentile. It's obviously a bug. However you may not detect > the bug if you're interested in the interquartile range: I quickly ran the same analysis with the most recent build available on the test page which does not show the problems. . version Current version: 1.1 Release 8 (Build 68) Latest public release 1.1 Release 1 (Build 62) . stattables sex /idr=km SEX N NKM P10KM P90KM Kvinde 490 423 18.00 265.00 Mand 3537 3197 0.00 265.00 . stattables sex /iqr=km SEX N NKM P25KM P75KM Kvinde 490 423 42.00 237.00 Mand 3537 3197 36.00 192.00 . describe km if sex = 1 Variable N=490 Sum Mean (95% cfi) Min p5 p10 p25 Median p75 p90 p95 Max KM 423 50288.0 118.88 109.42 128.35 0.0 0.0 18.00 42.00 73.00 237.00 265.00 277.00 286.00 . describe km if sex = 2 Variable N=3537 Sum Mean (95% cfi) Min p5 p10 p25 Median p75 p90 p95 Max KM 3197 330796.0 103.47 100.23 106.71 0.0 0.0 0.0 36.00 71.00 192.00 265.00 265.00 286.00 Apparently the bug shown has been corrected in build 68. - To avoid such errors a comprehensive test suite has been developed for analysis. Currently the test involves testing of around 650 different conditions and a test for the problem above has been added. I will update to a later build very soon to remedy the problem. Known other problems are: Estimation of OR in sparse tables The aggregate (stattables) command can create variable names longer than 10 characters Apart from that I am not aware of current problems of estimation. If other definitive bugs are known (not requests for new functions) please report to the new bug database, found at Http://www.epidata.dk/php/mantis Currently development is focused on "long term plans" including rewriting the software for further documentation and testing, experimentation with collaborative editing of documentation and other aspects of the development plan for 2006-2010. The "in-house" build of analysis has come to 85 now, where build 68 is the latest for public testing. When the current aspects are completely finalised a new build will be placed for testing. One of the many new aspects are more user control over the interface, a completely rewritten table command, which includes exact testing of stratified tables, calculation of gamma coefficient for ordinal data and extensive sorting. Working with summarised data is next in line. Other new aspects are further documentation tools within analysis (value labels, missing value assignment), renaming variables and enhanced control over graphics, e.g. axis and ranges. Kind regards Jens Lauritsen EpiData Association

17 years, 9 months

Bug in EpiData Analysis

by epidata-list＠lists.umanitoba.ca

This is an email to the folk at EpiData. In my examples below I'm using the data file bromar.rec, one of the example data files that come with EpiData. The variable km has some missing data (.). This data seems to be correctly treated as missing values for some commands but not for all. One example is the StatTables command. Below is an example of the command I typed into EpiData and the resulting output: . StatTables sex /idr=km SEX N NKM P10KM P90KM Female 490 423 42.00 . Male 3537 3197 32.00 . As you can see the missing values are included in the calculation for the 90th percentile. It's obviously a bug. However you may not detect the bug if you're interested in the interquartile range: . StatTables sex /iqr=km SEX N NKM P25KM P75KM Female 490 423 67.00 265.00 Male 3537 3197 42.00 265.00 If you do a "describe" you can see that 265 is definitely not the 75th percentile. Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit Royal Children's Hospital Flemington Rd Parkville Victoria 3052 telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000

17 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list July 2006