November 2007 - EpiData-list - University of Manitoba Mailing Lists

Age
by epidata-list＠lists.umanitoba.ca 02 Dec '07

02 Dec '07

Hello, I need some help to figure out an age at a given date. For instance: what is the age of someone born in 15/june/1970 on this date: 31/dec/2006? Thank you, Gaspar L Neto

1 1

set ignore equivalent
by epidata-list＠lists.umanitoba.ca 30 Nov '07

30 Nov '07

Dear members in the group is there an equivalent to epiinfo to SET IGNORE in epidata analysis. I will appreciate your information. Jose Arturo Farfan Mexico ------------------------------------------------------------ Universidad Autónoma de Yucatán http://www.uady.mx/

1 0

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

30 Nov '07

Thank you for your quick answer. Your advice works! Another question. I have a long list of all the countries of the world with only one variable named COUNTRY_NAME , a 25 characters string. Is it possible to use the LEGAL command with a REC file with only one variable? Or do I have to add lable names or numbers for each country to use the COMMENT LEGAL solution? Franco L. Sanavro Epidemiologist Regional Health Centre GGD Zuid-Holland Zuid Dordrecht The Netherlands -----Oorspronkelijk bericht----- Van: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca]Namens epidata-list-request(a)lists.umanitoba.ca Verzonden: zaterdag 24 november 2007 19:03 Aan: epidata-list(a)lists.umanitoba.ca Onderwerp: EpiData-list Digest, Vol 49, Issue 13 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. Re: How to use large amounts of of legal values in chk file (epidata-list(a)lists.umanitoba.ca) 2. Re: Using Comment legal in recfiles (epidata-list(a)lists.umanitoba.ca) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 Nov 2007 23:55:34 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] How to use large amounts of of legal values in chk file To: epidata-list(a)lists.umanitoba.ca Message-ID: <47475A66.5060104(a)tbrieder.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed EpiData Entry most likely does not recognize *.inc. Assume that your POSTCODE.INC file has two fields: name postcode where NAME is the place and POSTCODE its postal code. Make a text file, eg NAMECODE.TXT containing only these two fields, semi-colon delimited. Then make a QES file, e.g., NAMECODE.QES with just two fields: name _________________ postcode #### Then use the import function to import the NAMECODE.TXT file. Now edit the NAMECODE.CHK file so that: name key 1 end postcode key 2 end Go now to your MAINFILE.REC and edit the MAINFILE.CHK in the appropriate place to: postalname COMMENT LEGAL namecode.rec SHOW TYPE COMMENT postalcode END postalcode NOENTER END (assuming you have these two fields). Now the data entry person gets the external file as a label block, with POSTALNAME as the field value that can be found quickly, and the POSTALCODE as the value label, written into the appropriate field. Hans epidata-list(a)lists.umanitoba.ca wrote: > 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). > > 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 > -- 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 ------------------------------ Message: 2 Date: Sat, 24 Nov 2007 01:23:55 +0100 From: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] Re: Using Comment legal in recfiles To: epidata-list(a)lists.umanitoba.ca Message-ID: <47476F1B.6000001(a)epidata.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 49, Issue 13 ********************************************

1 0

EpiData export using filter on dates
by epidata-list＠lists.umanitoba.ca 30 Nov '07

30 Nov '07

Thanks to Hans for his suggestion, but I had already done this. I was just thinking that it should be possible to do it in EpiData Entry, hence my query. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 0

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

EpiData Analysis v2.0 Build 128 available
by epidata-list＠lists.umanitoba.ca 22 Nov '07

22 Nov '07

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

1 0

EpiData Entry: export filter
by epidata-list＠lists.umanitoba.ca 15 Nov '07

15 Nov '07

I am hoping someone knows the answer to the following question: I am trying to export a selection of records from an EpiData rec file using version 3.1 to an Excel file, based on a date field. For instance, to select all records earlier than the 14th of November 2007: dategiven < "14/11/2007" in the filter box, but this yields an error (not a boolean expression) and the field dategiven is a <ddmmyyyy> field. I also tried without quotes and using the date function, with and without the day, month, year functions with the same result. I dare say there is a simple way to do it, but I can't see it, so if anyone can help, I'd be most grateful. Regards, Neville ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

Problems with APPEND in build 126 and 127
by epidata-list＠lists.umanitoba.ca 14 Nov '07

14 Nov '07

In Build 122 the following 3 commands in a pgm-file could be executed correctly. close read "c:\data\tz\test1.rec" append "c:\data\tz\test2.rec" In build 126 and 127 the You get a error "Invalid variable name C:\Data ....." when running the pgm-file. But if You execute each command separately the APPEND command works.as You can se from the following output. . read Loading data C:\Data\TZ\Test1.rec, please wait.. File name : C:\Data\TZ\Test1.rec Fields: 3 Total records: 6 Included: 6 . append Append rewritten - check result Loading data C:\Data\TZ\Test2.rec, please wait.. . list RecNo x y z 1 1 2 3 2 3 2 1 3 4 5 6 4 6 5 4 5 7 8 9 6 9 8 7 7 12 . . 8 13 . . 9 14 . . 10 15 . . Note browse is faster than list . run . close File closed . read "C:\Data\TZ\Test1.rec" Loading data C:\Data\TZ\Test1.rec, please wait.. File name : C:\Data\TZ\Test1.rec Fields: 3 Total records: 6 Included: 6 . append "C:\Data\TZ\test2.rec" invalid variable name C:\Data\TZ\test2.rec Operation aborted ------------------------------------------------------------------------ Stig Uhlin tel 090-786 60 71 Stig.Uhlin(a)umdac.umu.se UMDAC 070-591 03 04 901 87 Umeå fax 090-786 67 62 Jag jobbar numera 1/2 tid enl följande: jämna veckor onsdag-fredag udda veckor måndag-tisdag ------------------------------------------------------------------------

1 1

Alyshia Landry is out of the office.
by epidata-list＠lists.umanitoba.ca 10 Nov '07

10 Nov '07

I will be out of the office starting 11/10/2007 and will not return until 11/13/2007. Regional offices are closed Monday November 12th. I would be happy to respond to your e-mail upon my return. Thank-you, Alyshia

1 0

EpiData Analysis - reported problems solved - build 127 uploaded
by epidata-list＠lists.umanitoba.ca 10 Nov '07

10 Nov '07

The reported problems in relation to b126 have all been solved. In addition the following changes have been implemented: dotplot : Now dots are symmetrical for each group command prompt: At initiation the command prompt is empty (was "read" before". For users wishing to get the "read" command without using a mouse the shortest way is by pressing F4 (goto command prompt) followed by "Up-Arrow" (shows the "read" command), followed by "Enter" (open file dialog). documentation: clarified. Still some of the extended help files could have v1.0 description of options etc. The download page now shows build and version next to the page, as well as there is also a zip file available containing the setup file. Thanks for reporting the problems. Part of the problem of the /SD etc discussed was, that the release build and a former test build had the same build number (b126) (by error), such that users could think they were having the same version, but actually did not. regards Jens Lauritsen EpiData Association

1 0

RE: Sorting of 2x2 tables (Oswego example discussion)
by epidata-list＠lists.umanitoba.ca 09 Nov '07

09 Nov '07

The problem of the /sd option in relation to tab ill cakes vanilla chocolate /oa /sd /ex versus tab ill cakes vanilla chocolate /oa /ex is related to how boolean variables are sorted. Currently in the version 2.0 released there is a bug in sorting of boolean 2x2 variables. The error will be fixed as soon as possible. For numerical variables coded 1/0 or 2/1 there is no problem. The reason I did not catch the boolean Y/N error is, that the tab command gives correct estimates for boolean as well as numerical variables: tab ill cakes vanilla chocolate /oa /ex But if the user adds the sorting (as was needed earlier) : tab ill cakes vanilla chocolate /oa /ex /sd reveals the bug. The way development is done is that before release a number of tests are made, currently around 1250, e.g. after the mentioned tabulation 24 tests were applied for the tabulation of oswego rr values with different options (but not the /sd) option. The oswego rr test has now been extended to cover this issue as well. (18 more tests). A given test can be like this using result variables: tab ill vanilla rolls /o assert samenum(round($OR*100)/100,22.15) assert samenum(round($ORLL*100)/100,5.22) assert samenum(round($ORUL*100)/100,138.39) assert samenum(round($OR1*100)/100,12.26) assert samenum(round($ORLL1*100)/100,1.76) assert samenum(round($ORUL1*100)/100,150.86) assert samenum(round($OR2*100)/100,38.19) assert samenum(round($ORLL2*100)/100,4.06) assert samenum(round($ORUL2*100)/100,1983.85) assert samenum(round($SumOR*100)/100,20.61) assert samenum(round($SumORLL*100)/100,4.93) assert samenum(round($SumORUL*100)/100,126.46) The "hidden" bug arising by the sort option is a good example of why many tests are needed, but I think also that it shows that even with a number of test releases the policy of "silent release" is appropriate. regards -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 1

Congratulations to all epidemiologist and THANKS to Jens
by epidata-list＠lists.umanitoba.ca 08 Nov '07

08 Nov '07

Dear all, The new version is wonderful. I have the oportunity to make a demo at the begining of this year to a cohort of EPIET fellows. They were using Stata and when they saw EPiData Analysis doing the, them a draft version yet, of tables ..... /oa and epicurve. They got completly breath taken I think Jens deserves all our acknowledge Pedro

1 0

Analysis V2 - Congratulations
by epidata-list＠lists.umanitoba.ca 08 Nov '07

08 Nov '07

Although there are a few minor bugs, these will usually be very obvious and only in the unusual situation. My quick testing on favourite troublesome data sets shows this is a great release. If you know anyone working on outbreak investigations who has not seen Analysis, do them a favour and show them how to do the following on the OSWEGO.REC data: tab ill cakes vanilla chocolate /oa /ex gen i onset=(onsettime div 100) + iif(onsetdate = "04/19",24,0) epicurve onset ill You will make someone very happy, I'm sure. Many of us working in the field have been waiting for something as simple as this (I have been waiting over 25 years). Sure, you could almost do this in EPI6, but only with a lot of advanced knowledge - and forget the exact test except as table by table. Many thanks to Jens & team!! Jamie Hockin Public Health Agency of Canada

1 2

Chris Sellers/FHS/ADPH is out of the office.
by epidata-list＠lists.umanitoba.ca 06 Nov '07

06 Nov '07

I will be out of the office starting 11/05/2007 and will not return until 11/13/2007. I will check emails periodically while I am away. If an issue needs immediate attention, please, contact Fred Grady at FredGrady(a)adph.state.al.us or 1-800-338-8374. Otherwise, I will respond to your email when I return.

1 0

Re: EpiData Analysis - first "silent" non-test release
by epidata-list＠lists.umanitoba.ca 05 Nov '07

05 Nov '07

The bugs in Chi Square values in stratified analysis of 2x2 tables and the correlation command error reported today has been solved. Therefore a first version v2.0 for analysis placed on the general download page. The work continues solving minor problems only affecting special situations, such as percentiles with small numbers of observations (n=10-25) or final adaptation of all help documents to the new options. Only the general help file has at this point been uploaded. When all of these points have been settled a general announcement will be made. This is expected to take 1-2 weeks. Thanks to many users for testing and commenting. regards Jens Lauritsen EpiData Association

1 0

CORRELATE command
by epidata-list＠lists.umanitoba.ca 05 Nov '07

05 Nov '07

Dear Jens, After years of hard work you have brought Epi Analysis to the current status. There are almost all the features of EPI6 and much more. Apart from the pending issues you have outlined, I wanted to draw your kind attention to CORRELATE command (build 126). According to the HELP file, correlate var1 var2 [var3 ...], it should work.. When I run this command, the following happens; table design=box . CORRELATE V1 V2 Invalid floating point operation Probably some thing is wrong in the syntax I am attaching a small sample corr.rec file. Please help. Waiting for the release of this marvelous software. With regards, Dr. Shavinder Singh

1 0

EpiData Analysis - status release candidate
by epidata-list＠lists.umanitoba.ca 04 Nov '07

04 Nov '07

Three aspects needs clarification and further exploration : 1 Chi Square values in stratified analysis of 2x2 tables 2 Saving datafiles with "Epi6 naming convention". Only "First Word" works completely. 3 Percentiles have problems with small numbers of observations Except for these three problem areas I think all major issues have now been solved. The table command syntax has been simplified to: tables ........ (default) will do stratified analysis or a n*k table. tables ....... /oa will create a condensed outbreak table with attack rates and rr tables ........ /cc a condensed table with odds ratios tables ....... /fv will do a "first against all other variables", but currently is limited to 2x2 tables It is my intention to release current as a "silent starter" for v2. By silent I mean without a lot of news due to the limitations mentioned above. A warning is given when the analysis commands (tables, describe, stattable) affected by the problems are used. I expect the problems to be solved within about a week or two at most. The reason for the "silent release" is that some courses are due, which do not use these commands. What could change my decision of release as is would be strong disagreement from users on this list. Please discuss, but if no major concerns show up, the release will happen tomorrow. regards Jens Lauritsen EpiData Association

1 0