- EpiData-list - University of Manitoba Mailing Lists

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

SPC Charts
by epidata-list＠lists.umanitoba.ca 20 Oct '08

20 Oct '08

I wonder if someone can give me some advice. I would like to create SPC charts that include data on actual counts and target. I have been playing around and it seems I can only include one field. Is there any way I can create SPC Charts that show actual counts (e.g of MRSA) against targets? Thanks, Shakeel ----------------------------------------- ************************************************************************** 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

Re: Problem with underscore character in variable name
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

"According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). .... However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). " Actually this is a bug in analysis. Will be corrected. Explicitly _ is NOT allowed. Where in the documentation is _ allowed. This is a misrepresentation. The reason is : _ is the representation of a string variable in the qes file, but apparently we made an error in the analysis allowing for this on generate. (e.g. gen i abc_d = 1 or define abc_d # ) regards Jens Lauritsen

1 1

Backup command: make routine snapshots without replacing previous backup (TIME STAMP?)
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

With sufficient patience and testing any name structure can be given for a backup file. Here shown with calling of the external file epic. Some adaptation of the command line is necessary, which is why the backup command was developed. This block will ask whether to create a zip file with the name of todays date using an external application epic.exe - it can be a little (often quite) tedious to work out the parameters to execute, but do so first in a command window outside epidata entry. Include in the chk file this "after file" block, which names the zip file by date, hour and minute: after file help "Create zip file ? 1:yes 2:no" keys="12" type=CONFIRMATION if resultvalue = 1 then define tmpz _________________________________________________ let tmpz = "zip c:\temp\first"+string(day(today)) if month(today) < 10 then tmpz = tmpz + "0" + string(month(today)) + string(year(today)) + string(Num2Time(Now)) + " replace first.*" else tmpz = tmpz + string(month(today))+ string(year(today)) + string(Num2Time(Now)) +" replace first.*" endif help @tmpz execute epic "@tmpz" wait endif END Regards Jens Lauritsen

1 0

Problem with underscore character in variable name
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

According to the documentation, an underscore character is allowed in variable names. And, indeed, I have no problem defining new variable names with an underscore and using them in analysis (v2.1.0.151). However, when the data have been saved and one opens the file for further analysis, the variable has been renamed v1 (or v2, etc). In addition, the original variable name containing the underscore is put into the variable label. For example, I created a variable abc_test. After saving the data and opening the file, I find that the variable now has the name v1 and the label "abc_test abc-test". Annemieke van Middelkoop Pretoria, South Africa

1 1

Backup command: make routine snapshots without replacing previous backup (TIME STAMP?)
by epidata-list＠lists.umanitoba.ca 19 Oct '08

19 Oct '08

Hi EpiData users, I am trying out the backup function in CHK file: .... AFTER FILE BACKUP "D:/backupfolder" ENCRYPT file1 pw123 TODAY END ... What happens is the backup is created each time I close the "ENTER DATA" file in the "D:/backupfolder" as file1_19OCT08.ZKY. This is good. It replaces the previous backed-up ZKY file. I guess if I did this on another date (tomorrow) a new file will be created file1_20OCT08.ZKY, correct? So I would get DAILY snapshots of the data? Is there a way to specify a TIME stamp as well? Thanks S EDIT: Just writing this made me realise, why would one want a more frequent backup? Daily is sufficient. On Sat, Oct 18, 2008 at 7:02 PM, <epidata-list-request(a)lists.umanitoba.ca>wrote: > 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.1 ready (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Oct 2008 01:05:43 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] EpiData Analysis v2.1 ready > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <48F91A47.4000204(a)epidata.dk> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > V2.1 of EpiData Analysis has been placed for general download on the > http://www.epidata.dk/download.php > > All changes since last public release as v2.0 build 129 are documented in: > http://www.epidata.dk/analysisversioninfo.htm > > Main changes are: > 1 new commands: > Lifetable Lifetable and Kaplan-Meier plots, including estimation of > differences and testing of similarity btw. groups. > Stattables : summary reporting > CIplot: Plot of proportions and confidende intervals for strata defined > by other variables > Read /CB: read delimited data from clipboard, e.g. copied from > spreadsheets > 2 rewriting: > many commands and internal structures, including update and browse > 3 enhanced and clarified: > all outcome related estimation commands are synchronised with outcome > variable first. > enhanced options, e.g. /pct giving percentages on bar and histograms > graphs allowing /by > increased number of user "set" specifications including modifiable headers > percentiles for small n table based, see > http://www.epidata.dk/documentation.php > 4 bug removal > all known bugs removed > > Report and discuss on this list please. Definete errors should be > reported to the Mantis database > > More information on credits and funding later > - without this and user involvement in testing the development would not > be possible. > > regards > Jens Lauritsen > > > > > > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 60, Issue 11 > ******************************************** > -- Shuaib Kauchali Department of Paediatrics & Child Health Pietermaritzburg Metropolitan Hospitals Complex & University of KwaZulu-Natal Email: kauchalis(a)gmail.com Cell: +27-84-581-1142 Office: +27-33-897-3221 & -3230 (Secretary) Fax: +27-33-897-3409 No virus detected in this incoming message.

1 0

EpiData Analysis v2.1 ready
by epidata-list＠lists.umanitoba.ca 17 Oct '08

17 Oct '08

V2.1 of EpiData Analysis has been placed for general download on the http://www.epidata.dk/download.php All changes since last public release as v2.0 build 129 are documented in: http://www.epidata.dk/analysisversioninfo.htm Main changes are: 1 new commands: Lifetable Lifetable and Kaplan-Meier plots, including estimation of differences and testing of similarity btw. groups. Stattables : summary reporting CIplot: Plot of proportions and confidende intervals for strata defined by other variables Read /CB: read delimited data from clipboard, e.g. copied from spreadsheets 2 rewriting: many commands and internal structures, including update and browse 3 enhanced and clarified: all outcome related estimation commands are synchronised with outcome variable first. enhanced options, e.g. /pct giving percentages on bar and histograms graphs allowing /by increased number of user "set" specifications including modifiable headers percentiles for small n table based, see http://www.epidata.dk/documentation.php 4 bug removal all known bugs removed Report and discuss on this list please. Definete errors should be reported to the Mantis database More information on credits and funding later - without this and user involvement in testing the development would not be possible. regards Jens Lauritsen

1 0