- EpiData-list - University of Manitoba Mailing Lists

Epidata Analysis 2
by epidata-list＠lists.umanitoba.ca 07 Nov '08

07 Nov '08

Hello, Three suggestions on last version of Epidata Analysis 2.0 (very good on the whole): - a regression line in scatter graph is imperative like EPI 6 and all the statistic softwares ++ - a few "set command" are desirable; for example : * "set statistics = on" instead to write /t for all the commands * "set table percentage = row" instead to write /r for all the "tables" commands - "set freq percentage= column" instead to write /c for all "freq" commands A question about "lifetable" command (very useful and pratical) : - In understand that the method is "actuarial" ou "lifetable" with a range of time for the calculation of probability (1 by default). The result is the same than SPSS with the command "lifetable" and time range = 1. It's not Kaplan-Meier method because the probability is not calculated at each event, (or calculation of remaining number at each censored data). Thank you your observation. B. BRANGER. PS : I modify this week the help on my site www.reseau-naissance.fr <http://www.reseau-naissance.fr/>

1 0

Epidata with lynux
by epidata-list＠lists.umanitoba.ca 04 Nov '08

04 Nov '08

How can I use Epidata with Lynux?

1 1

Options versus set
by epidata-list＠lists.umanitoba.ca 03 Nov '08

03 Nov '08

I am more than just in favor of options, I believe that they are the best possible approach, it makes everything so straight forward and simple. Sometimes we want something to test, then we do it with the option, else we take it out, and it is all in the same command line, rather than a "set xx=on" then the command, then "set xx=off" again. Options are very intuitive. Hans

1 0

Default behaviour of EpiData Analysis
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

There will always be differences as to how users wish to run different commands. Some time ago a discussion was on the list regarding the list. The decision was to move as much as possible to options, since otherwise the users have to issue different commands for changes. As was suggested by B.Branger why not "get back" the "set statistics", "set table percentage" etc. The problem of this is the implementation in the menu system (dialogs), which becomes a bit messy. The suggestion for users is rather to use the following technique: Add to your epidatastat.ini: define tableoption __________ global tableoption = " /t /R /C" // or whatever you prefer or shorter: define t __________ global t = " /t /R /C" // or whatever you prefer Now in your actual pgm file or at the command line, just issue: tab v1 v2 @t You might say "a bit annoying" to add @t, but still less than writing the options. Another aspect of the issue is that the set definitions mentioned are part of the Epi Info v6 specification, but many users who did not do statistical analysis with Epi6 are not aware of this by now. regards Jens Lauritsen Epidata Association

1 0

about: Lifetable in v2.1
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

B.Branger questioned whether the lifetable is "actuarial" or "Kaplan-Meier" principle. The principle is to calculate changes in survival probabilities at each date, where a change happens - either censoring or case status. In actuarial calculations there would be an aggregation to say half year, month or similar. Therefore if you DO NOT use the /i for "Interval" the calculation will be "Kaplan-Meier" technique. If you found an example where this is not the case let us know. regards Jens Lauritsen EpiData Association

1 0

Epidata Analysis 2
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

Hello, Three suggestions on last version of Epidata Analysis 2.0 (very good on the whole): - a regression line in scatter graph is imperative like EPI 6 and all the statistic softwares ++ - a few "set command" are desirable; for example : * "set statistics = on" instead to write /t for all the commands * "set table percentage = row" instead to write /r for all the "tables" commands - "set freq percentage= column" instead to write /c for all "freq" commands A question about "lifetable" command (very useful and pratical) : - In understand that the method is "actuarial" ou "lifetable" with a range of time for the calculation of probability (1 by default). The result is the same than SPSS with the command "lifetable" and time range = 1. It's not Kaplan-Meier method because the probability is not calculated at each event, (or calculation of remaining number at each censored data). Thank you your observation. B. BRANGER. PS : I modify this week the help on my site www.reseau-naissance.fr <http://www.reseau-naissance.fr/>

1 0

Update for EpiData Analysis v2.1 and news on further development.
by epidata-list＠lists.umanitoba.ca 02 Nov '08

02 Nov '08

A new build for EpiData Analysis has been placed for general download. From v2.1.0.154 it is possible to give dates as a parameter to x-axis limits in EpiCurve and Kaplan Meier Survival plots. e.g. Epicurve outcome dayonset /xmin="01/10/1986" /xmax="25/10/1986" Notice the DMY format. A few other bugs have been solved. If you are not using Epicurve there is no reason for updating. A recent seminar in Canada forms part of the intensified development ongoing this year. This collaboration is with the Assocation of Public Health Epidemiologists in Ontario, Canada, see: http://www.apheo.ca/index.php?pid=47 On the testing page (http://www.epidata.dk/testing.php) v2.1.1.154 includes two new commands released for tests and comments: xbar /Range, xbar /Sigma , and ichart /MR - these will perform double charts used in Statistical Process Control analysis and visualisation. An extended user manual is in development and expected ready for general use in about one month. G-charts are expected within 1-2 weeks for testing. Regards Jens Lauritsen EpiData Association

1 0

Re: new install zipfile on web
by epidata-list＠lists.umanitoba.ca 23 Oct '08

23 Oct '08

I am a user who does not have administrative rights so may thanks for the new feature. I like the new version of Epidata Analysis but I have one small issue. When I go file open in the programme editor It always opens up to the test data file directory C:\programme files\epidata\test data and i have to navigate to the directory where I saved my programme. With the old version if I clicked open in editor it would open at the directory of the last programme I used (e.g. F:\programmes\health protection\outbreaks). Is there something I can do to change to make the new version do this? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 23/10/2008 4:52 p.m. >>> A few bugs has been found in the public release the latest week: a. In Epicurve when started from the menu, the time variable could not be date - fixed b. In Epicurve the default Yincrease is now set to one. (/yinc=1) these are fixed, in addition c the reported error with define and gen of variables "_" will be fixed An increasing number of users cannot install files on their own pc. Since Epidata software is not really installed, but only unzipped and copied the zip file for download does not contain an install file, but a zipped copy of an installed version. This means that all users who have problems due to lack of administrative rights should be able to download the "Setup (zip)", unzip and place somewhere, e.g. a subfolder to the desktop. It is then up to the user to edit the ini file found via the edit menu to the correct path/folder name. If you are not using epidemic curves there is no reason to change from build 151 to 152. regards Jens Lauritsen -- 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 0

Corrected Analysis v2.1.0.152 and new install zip file on web
by epidata-list＠lists.umanitoba.ca 22 Oct '08

22 Oct '08

A few bugs has been found in the public release the latest week: a. In Epicurve when started from the menu, the time variable could not be date - fixed b. In Epicurve the default Yincrease is now set to one. (/yinc=1) these are fixed, in addition c the reported error with define and gen of variables "_" will be fixed An increasing number of users cannot install files on their own pc. Since Epidata software is not really installed, but only unzipped and copied the zip file for download does not contain an install file, but a zipped copy of an installed version. This means that all users who have problems due to lack of administrative rights should be able to download the "Setup (zip)", unzip and place somewhere, e.g. a subfolder to the desktop. It is then up to the user to edit the ini file found via the edit menu to the correct path/folder name. If you are not using epidemic curves there is no reason to change from build 151 to 152. regards Jens Lauritsen

1 0

Double entry and unique field
by epidata-list＠lists.umanitoba.ca 22 Oct '08

22 Oct '08

Dear EpiData friends, Im in project about adverse events of a particular kind of patients using some medications. The data entry has a rationale of every adverse event of a single patient has a different questionnaire. This means that a unique number of the patient could be typed in the dataset more than once. So far ... OK But we are plannig a double entry... and than the unique identifier of the patient may couse problmes and errors! So I was thinking about creating a sequence for each adverse event, and than a patient 19230 would have a event A, B,C .... and so on A unique variable could be automaticly created by patientnumber+uniqueevent wich could give something like 19230A, 19230B, 19230C and so on! But this does not seem to me an elegante work around! Does any one else have other suggestions? -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0