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

Analysis: graph creating GUI bug?
by epidata-list＠lists.umanitoba.ca 30 Mar '11

30 Mar '11

Hello all, I noticed that the GUI which allows you to create histograms (Graph -> Histogram) does not let you specify a boolean variable as "by" variable. Example: . read C:\EpiData\TestData\bromar.rec . select dectime<>. . gen b fast=(dectime<3.87) it is possible to do the following: . his age /by=fast but the GUI form does not list "fast" as a "by" variable. Kind regards, Simon PS: I tried to report this on flyspray, but I get a "Error #23: User or group not enabled for login." when I try to log in.

1 2

New EpiData EntryClient version release for test
by epidata-list＠lists.umanitoba.ca 29 Mar '11

29 Mar '11

Dear List A new version of the EpiData EntryClient program have been release for testing today. Due to a significant bug in jumps, where the program would end up in an infinite loop, we have decided to release a new version where this problem is no longer present. Since the sample file contains a contruct that could activate this bug, we strongly recommend all using the old version of EpiData EntryClient (0.3.2.0) to update to the new version. With kind regards, Torsten Bonde Christiansen EpiData Association.

1 1

Clarification of how to work from now on
by epidata-list＠lists.umanitoba.ca 23 Mar '11

23 Mar '11

Dear all Many of the messages I have added to the list recently are rather technical in nature. This is just a short notice on how mode of work will be from now on: Until now - since 1999 and 2003/4 we have: Data definition, docuemtation and Entry: Epidata Entry Analysis: EpiData Analysis From now on: The manager: The project manager creates data entry forms and structures data collection using the software "EpiData (data) Manager". This can be used in a "point and click" manner visually including adding checks, jumps and ranges. Once the database is structured and ready. The file, e.g. outbreak.epx can be given to those entering data. The one "physical" file contains all information including definition of fields, range, value labels, jumps etc. The data entry person would then acquire the "EpiData EntryClient", which can be used to enter actual data into the file. Adding records just as in the current EpiData Entry software. In other words we separated current functionality into: Project management, data definition and documentation: EpiData Manager Data Entry: Epidata EntryClient Analysis: EpiData Analysis All of these are available from the testing page: Http://www.epidata.dk/testing.php We are now (struggling) to implement all decided functionality, such that a public release will be available as soon as possible. There is still some adaptations and developments to do, but we are approaching the public release. It is therefore welcomed that you look at the new software and join the commenting on the EpiData List - just as many of you have already done. Regards Jens Lauritsen EpiData Association

1 3

BoxPlot with 3 variables
by epidata-list＠lists.umanitoba.ca 23 Mar '11

23 Mar '11

Dear EpiData users, How to make a Boxplot when I have one quantitative variable and two qualitatives variablesThanks __________________________________ Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Info. Médicale UFR Sciences Médicale, U. Abidjan-Cocody 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 493 334 GSM: (+225) 08 167 578 / 02 724 162 skype's: dibykonanjp

1 1

Updated EpiData Manager
by epidata-list＠lists.umanitoba.ca 22 Mar '11

22 Mar '11

Dear EpiData users. Due to a significant bug in the previous version (0.7.1) of EpiData Manager, posted on the testing page last week, a new version has been upload today already. The bug impacted the use of "Import Structure" which could cause problem with saving the project, fields could be missing the field name and other strange problems could follow. Please be advised to download the new version uploaded today to avoid any of these problems. With kind regards, Torsten Bonde Christiansen EpiData Association.

1 1

WRITENOTE command
by epidata-list＠lists.umanitoba.ca 21 Mar '11

21 Mar '11

When writing a comment into a .NOT file, I can display the ID number by @<field name>, e.g. where the field name is babyid: * WRITENOTE "Comments or additional information for baby ID @babyid" SHOW I tried doing this with 2 fields (the combination of babyid and wksdate is unique): * WRITENOTE "Comments or additional information for baby ID @babyid and Week Starting date @wksdate" SHOW However only the value of wksdate is displayed. How can I display the values of both fields? My work around is to create a variable that's a combination of babyid and wksdate, but I'm wondering if there's a more straightforward way to do it. Cheers, Suzanna Vidmar Senior Research Officer Clinical Epidemiology and Biostatistics Unit Murdoch Childrens Research Institute Royal Children's Hospital Flemington Road Parkville Victoria 3052 Australia telephone: +61 3 9345 6372 facsimile: +61 3 9345 6000 email: suzanna.vidmar(a)mcri.edu.au www.mcri.edu.au <http://www.mcri.edu.au/> ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

1 0

Can I start translating the spanish wiki?
by epidata-list＠lists.umanitoba.ca 21 Mar '11

21 Mar '11

Hello: Maybe is very soon to do this but I offer my help editing the spanish version of the wiki on my free time. Regards, -- Omar Bautista González - Colaborador en autogestión comunitaria desde República Dominicana

1 0

epx versus EPX , analysis and problems in test release
by epidata-list＠lists.umanitoba.ca 19 Mar '11

19 Mar '11

When working with files in windows there is no difference btw. "chk" and "CHK" as extension for a file, however in Linux (possibly also in MAC) there is a difference. This is also relevant for EPX versus epx. It turns out that apparently the new batch processor "epidatacmd" can give problems when creating files due to problems of "EPX" versus "epx" extensions. WHen using these files on a Linux pc a file with the name myfile.EPX will not show up on the "supported files", list in manager or client. Other issues when working with the latest released Manager and EntryClient I have found are: a. Sometimes "access violation" occurs when I change the setting in Manager of "showing variable names" or not. b. Sometimes single files created from templates with the epidatacmd processor and subsequently combined in the Manager with "import structure" cannot be read by EpiDataClient. These errors will be fixed - these are examples of why testing is important on the path to the first public release. An updated Analysis (build 175) has been placed on the http://epidata.dk/testing.php. The only change is adaptation of reading epx files with the most recent changes to the epx structure. regards Jens Lauritsen EpiData Association .....................................................................................

1 0

RE: [EpiData-list] Re: EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 17 Mar '11

17 Mar '11

Dear Sam: You have your unique identifier for the parent file that is "inherited" by the child file. In the child file your create a unique identifier for that (simple is a construct of the parent identifier plus the date, if each child event happens on a different date). For validation, you compare the two parent files and the two child files, and that's it. Best regards, Hans Hi, The only problem with this solution is that I then cannot use the double entry method that compares responses as they are keyed in. As far as I know, it is not possible to do that with relational files. Thanks, Sam -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

Re: EpiData Entry Program Exceeding 999 Lines
by epidata-list＠lists.umanitoba.ca 17 Mar '11

17 Mar '11

Hi Sam, To add on Jens's suggestion, you could also give very short name to your variables without much description and fit all within required lines. Otherwise I would recommend relational rec.files (with full description of each var to avoid suffering at the data cleaning stage) and merge them at the end. Best wishes Tieble <http://www.mgavm.ru/>

1 2