- EpiData-list - University of Manitoba Mailing Lists

Complete repeated information
by epidata-list＠lists.umanitoba.ca 29 Nov '07

29 Nov '07

Dear colegues of epidata, Most current data structure for survival analysis have repetitive subjects with differenta dates. That means that the data has more than one (say five) subject number 8 (for example), and each line number 8 has dates showing diffenret periods (say period 1 to 2; 2 to 3 and so on). This structure is necessary for cox models with variables changing over time and more complex marginal models. However some variables remain with the same value over time, such as sex. I would like know if it is possible to implment in epidata entry chek file some comand that would find previous repetitive subject and type in the field this non changing variables over time. That is... suppose Im typing a record with id number 8 which is data from period 4. This command would look for the privous id 8 (just as autosearch) form period 3 or 2 or 1, if it finds any it would sugests ou type the same sex in this record as those found in privious periods of the same id. Is this possible? -- May the force be with you Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Incorrect variable names
by epidata-list＠lists.umanitoba.ca 29 Nov '07

29 Nov '07

Using Epidata v2.0.2.29, the following (intimidating) message appears when entering an incorrect variable name in any command: *Internal error, report to info(a)Epidata.dk (Access violation at address 00404500 in module 'EpiDataStat.exe'. Read of address FFFFFFFC* Much friendlier is the message given in earlier builds: *Field 'varname' not found.* Annemieke van Middelkoop Pretoria, South Africa

1 0

selecting by month
by epidata-list＠lists.umanitoba.ca 28 Nov '07

28 Nov '07

Dear member in the group I would like to select records based on the month value from a date variable with the following format "mm/dd/yyyy". I would like to use something like this: IF DC [1,2]="01" THEN MES="EN" IF DC [1,2]="02" THEN MES="FE" IF DC [1,2]="03" THEN MES="MA" This is in epiinfo 6. DC is the date variable I will appreciate your help. Jose A. Farfan Dr. Jose Arturo Farfan Ale Centro de Investigaciones Regionales "Dr. Hideyo Noguchi" Universidad Autónoma de Yucatán Av. Itzáes por 59, num. 490 Mérida, Yucatán, México 97000 Tel: (999) 923-22-74 (999) 924-57-55 Fax: (999) 923-61-20

1 1

Before public release
by epidata-list＠lists.umanitoba.ca 28 Nov '07

28 Nov '07

One small thing that comes and goes: if you merge two files, some variable names in the merged file come through rudimentary, eg freq sex of patient N Female 226 Male 271 Missing 94 Total 591 but correct with: freq sex /vnl sex of patient N Female 226 Male 271 Missing 94 Total 591 Not a really problem, just a small thing to perhaps look at, and not for all field names. Hans -- 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

Grouping for frequency tables
by epidata-list＠lists.umanitoba.ca 27 Nov '07

27 Nov '07

Hi Jens and colleagues Congratulations on the progress with Epidata analysis. I work with outbreaks so I love the OA function which lets you get the attack rate tables. My question is if it is possible to do something similar - to get a group of symptoms in one table. In our outbreak reports we want tables that show the count and percent of sick people with a range of symptoms - for example (say with 20 people ill) diarrhoea 20 100% Vomiting 10 50% Fever 5 25% At the moment I create a frequency table for each symptom and then cut and paste them into one summary table. I would like to know if there is a quick way to create just one symptoms table thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB **

1 1

EpiData Analysis v2.0 Build 129 available (any objections for release as current public version ?)
by epidata-list＠lists.umanitoba.ca 27 Nov '07

27 Nov '07

A few errors were trapped in v2.0.1.128, but I take the lack of reported errors beyond what I know of as an indication that the current build 129 can be released for general public use. Should this not be the case, please report errors immediately to the list. Notice that build 129 exists as well as v2.0.1.29 and v2.0.2.29, the latter is the one avialable at this point. For means and kwallis the correct syntax is: kwallis v1 /by=group means v1 /by=group but both commands will now accept the old syntax with a warning: kwallis v1 group - or - means v1 group Regards Jens Lauritsen EpiData Association

1 0

Re: Using Comment legal in recfiles
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

3. How to use large amounts of of legal values in chk file > We are building a data-entry system for the registration of medical contact for the youth in our organisation. > Therefore we need several hundreds of schoolcodes and zipcodes (postcode). > > On the page www.epidata.dk/examples.php there are two examples of using comment legal based on external files, - see these entitled: "Comment legal recfile - Birds and tick names" plus "Comment legal recfile - Bacteria list". regards Jens Lauritsen EpiData Association

1 0

How to use large amounts of of legal values in chk file
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

We are building a data-entry system for the registration of medical contact for the youth in our organisation. Therefore we need several hundreds of schoolcodes and zipcodes (postcode). For the quality of data I want to use this data in the chk file in the following way. In stead of: LABELBLOCK LABEL_POSTCODE LEGAL 2234 2344 2544 2645 . ETC END POSTCODE LEGAL USE LABEL_POSTCODE MUSTENTER END I want to use an externel file POSTCODE.INC whith the data and used the following syntax: LABELBLOCK LABEL_POSTCODE INCLUDE POSTCODE.INC END POSTCODE LEGAL USE LABEL_POSTCODE MUSTENTER END But I only get errors. Someone has a solution? Franco L. Sanavro Epidemiologist Regional Health Centre GGD Zuid-Holland Zuid Postbus 166 3300 AD Dordrecht The Netherlands 078 6321817 fsanavro(a)ggdzhz.nl www.ggdzhz.nl

1 1

Slow output when using EpiData Analysis
by epidata-list＠lists.umanitoba.ca 23 Nov '07

23 Nov '07

1. Output formation and slow output To remedy slow output: hit F12 button every so often. This will clear the screen and output speed goes up. Explanantion: Output in EpiData Analysis is created in html format. The same format used on internet pages. The good feature of this is that formatting is easy without a lot of programming. E.g. for reporting users can write: set echo=off read myfile count if age > 45 /q type "Number of persons was @$count" /h3 tab sex boxplot age /by=sex /ti="Current age structure by sex" set echo = on and the sentence with "type" will show the number of counts in a header type line (/h3) followed by a table of sex and a boxplot. The problem of html is however that it is a block structured file format. Therefore each time a line is added the whole output - not just the added line - has to be written on the screen. Therefore the speed of output slows down for every additional line you add. After a certain length of the output the screen clears automatically. Users cannot control this length (currently). To remedy slow output: hit F12 button every so often. Then when you have the complete output you wish, save the commands as a pgm file and run all again. Or at some point issue "logclose" and read the resulting logfile (default EAoutput.htm) in a browser. 2: Vista and analysis: There has been a report that EpiData Analysis cannot run on Windows Vista. If anyone are using Vista, please report your experiences with this. I assume that the specific user had insufficient "writing rights" to the Vista machine, since the stopping occurred when trying to open EAoutput.htm as part of the initiation sequence for analysis. regards Jens Lauritsen EpiData Association

1 0

RE: EpiData-list Digest, Vol 49, Issue 11
by epidata-list＠lists.umanitoba.ca 22 Nov '07

22 Nov '07

Please unsubcribe my name from Epidata, as I cannot do this myself online, having forgotten my password. With Thanks I. Riach ________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca Sent: Fri 23/11/2007 5:01 AM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 49, Issue 11 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 Analysis v2.0 Build 128 available (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Thu, 22 Nov 2007 17:36:44 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] EpiData Analysis v2.0 Build 128 available To: epidata-list(a)lists.umanitoba.ca Message-ID: <4745B01C.1090106(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed I just uploaded v2.0.1.128 on the page: www.epidata.dk/testing.php This build remedies as far as we can test here the problems shown since release of v2.0: - saving data files with automatic naming - odds ratios in stratified tables with more than two strata - memory leaks. Plan for current testversion: 1. Leave on testing.php page for a few days (3-4 days) 2. Move as current release on the general download page. The reason for putting on the test page is that the memory leak cleanout could have introduced problems with menus and screen handling, which cannot be tested here. Memory demand after running many commands could before rise to more than e.g. 200Mb is now down to around 15-20 Mb. Since release of v2.0 the test suite applied has been extended from 1749 tests to 1884 tests. The extension includes aspects such as further sorting and stratified results for a combination of variables and files. Please test as indicated and report here if you find problems Regards Jens Lauritsen EpiData Association ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 49, Issue 11 ********************************************

1 0