- EpiData-list - University of Manitoba Mailing Lists

Backup error
by epidata-list＠lists.umanitoba.ca 04 Oct '07

04 Oct '07

I moved my Epidatafiles from a computer running on WinXP to a laptop with Win Vista. Now I cannot do backup. Error message "invalid filename". Epidata incompability with Vista? Nikolai Stenfors

1 0

Epidata Analysis b122 available for testing
by epidata-list＠lists.umanitoba.ca 02 Oct '07

02 Oct '07

These weeks several problems and clarifications have been made on the "road" to release finally EpiData Analysis as v2.0 Some aspects are still insufficiently final, but the level of changes are going into "corner" details from my point of view. As of build 122 some aspects have been fixed: e.g. - EpiDemiological tables (odds ratios, rr and attributable risk) will use highest value of case and exposure variables as default. - A new table dialog has been a success in my personal teaching. Quite clearly beginners adapt much faster when having proper (intuitive) dialogs. - Sorting of frequency tables by numbers - More graph types can now be used with a "group variable", e.g.: box age /by=sex - Many more subtle details have been fixed. Many of these are invisible to the end-user, but clarification makes the whole programme more stable. This will also allow shorter development time for future new commands and additions. Some issues are still creating problems, such as: - internal errors after kruskal-wallis tests. - parts of relate system not working for some files - creating more intuitive dialogs for remaining parts of the system - removing reported bugs (see mantis system). Some users might find it odd that new problems arise, but this is due to the rewriting of core parts. And consequential changes in other parts of the software take some time to find, if they are not pinpointed by the error tracking system. This system is a collection of pgm files doing all verifying results and function in all parts of the programme. Usually when a new error is reported it is due to not being tested for in the error tracking system. The system is now based on 41 pgm files with around 1150 different conditions being tested and verified. Version 2 will not be released before all of the consequences of the rewriting of core parts has taken place. But as could be stated on the www.epidata.dk/testing.php page : "Many of the functions are running and functioning very well, so after each user has verified the function of what he/she uses there is no problem in using the test versions." E.g. the table module has no known errors just now. Kind regards Jens Lauritsen EpiData Association

1 2

A bug of epidata
by epidata-list＠lists.umanitoba.ca 11 Sep '07

11 Sep '07

To any concern, I think that I have found a bug of epidata when I want to export the data from epidata to sas. The content of .qes file: This is a example! The {first} text field: __________ The {second} text field: ________________________________________________________________________________ The {third} text field: ____________ The content of .sas file which is generated by epidata. * EpiData created two files by exporting * D:\statistics\temp\epidata bug\bug.rec * * 1. D:\statistics\temp\epidata bug\bug.sas * is the SAS command file * 2. D:\statistics\temp\epidata bug\bug.txt * is an ASCII text file containing the raw data. * * You may modify the command file before submitting them. ; DATA bug(LABEL="a bug of epidata"); INFILE "D:\statistics\temp\epidata bug\bug.txt"; INPUT FIRST $ 1-10 / SECOND $ 1-80 THIRD $ 1-12; LABEL first="The first text field:" second="The second text field:" third="The third text field:"; run; The conten of .txt file which is also generated by epidata: a b c d e f When I run the .sas file in sas, the log window showed that: NOTE: The infile "D:\statistics\temp\epidata bug\bug.txt" is: File Name=D:\statistics\temp\epidata bug\bug.txt, RECFM=V,LRECL=256 NOTE: LOST CARD. FIRST=f SECOND= THIRD= _ERROR_=1 _N_=4 NOTE: 9 records were read from the infile "D:\statistics\temp\epidata bug\bug.txt". The minimum record length was 10. The maximum record length was 80. NOTE: SAS went to a new line when INPUT statement reached past the end of a line. NOTE: The data set WORK.BUG has 3 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.18 seconds cpu time 0.07 seconds I can get the dataset 'bug' in work library. But it is not what I want. Now I can resolve the problem. I need modify the .sas file. The file which is modifed is listed below: * EpiData created two files by exporting * D:\statistics\temp\epidata bug\bug.rec * * 1. D:\statistics\temp\epidata bug\bug.sas * is the SAS command file * 2. D:\statistics\temp\epidata bug\bug.txt * is an ASCII text file containing the raw data. * * You may modify the command file before submitting them. ; DATA bug(LABEL="a bug of epidata"); INFILE "D:\statistics\temp\epidata bug\bug.txt"; INPUT FIRST $ 1-10 / SECOND $ 1-80 / THIRD $ 1-12; LABEL first="The first text field:" second="The second text field:" third="The third text field:"; run; The 'second' field caused the trouble. The 'second' field's width is 80. I hope someone can fix it. All the files is attached. You can have a try.

1 0

Re- LIST Command
by epidata-list＠lists.umanitoba.ca 03 Sep '07

03 Sep '07

Dear Jens, Thanks for the quick response. I will share my bit on the wiki. Regarding the BROWSE and LIST command message, I was not able to get the output of list command. My programmer found out the solution. We could solve the LIST command problem by SET ECHO=ON. When SET ECHO=OFF, the LIST command is also turned off. If it was supposed to be like that, please include this in the documentation. With regards, Dr. Shavinder Singh

1 0

Issues on EpiData Analysis - list etc.
by epidata-list＠lists.umanitoba.ca 03 Sep '07

03 Sep '07

Shavinder Sing suggested that ..... If each of us writes the documentation of ONE command with example, our command reference can be really exhaustive and useful like EPI6 manual. .... is very appropriate. The idea of a user based documentation centre is exactly the idea of the wiki principles, where everyone can add whatever is possible for them. I expect that a common base wiki will be ready within 6-12 months. Just now the following can be of immense importance: a. Anyone having good examples for distribution consider adding these to the experimental wiki now placed at www.epidata.org/wiki b. Consider writing documents in the form of "how to ...." and make a collection available from a local site, which can then be linked from the main site. c. Make sure that everyone registers for news from EpIData Association, since the number of persons registering there is the only "proof" of usage we have when arguing with authorities that the effort is truly a non-profit international effort. Every so often some discussions come up here in which until now it has been very important to be able to show the large number of registered users. Regarding the "LIST and BROWSE commands are not exactly replaceable." - this is true. I do not understand however why the function of list is not sufficient. There is a deficiency in list not being able to show "value labels", but apart from that I do not see any deficiencies - except that the output window is slow with large amounts of output. Possibly I do not understand the "...kindly preserve the functionality of LIST command as it was in EPI6. " For inspiration of a collaborative effort I suggest everyone to look at the website course developed as part of a number of courses run under the "wings" of IUATLD Union (see www.iuatld.org) by Hans L. Rieder, presented at "http://www.tbrieder.org/epidata/course.htm". The contents have been developed by the "EpiData Promotors" (http://www.tbrieder.org/epidata/epidata_promoters.htm) with some substantive solutions from me. The courses have also influenced the contents of commands and other parts of the Epidata Software. regards Jens Lauritsen EpiData Association

1 0

Thank and LIST command
by epidata-list＠lists.umanitoba.ca 02 Sep '07

02 Sep '07

Dear Jens, Release of build 118 is good news. Thanks you for this wonderful software. In the last few weeks, I had posted 3 queries on the list; a. Command Set replace logfile=on b. Incomplete execution of PGM c. Relational Files Relate error. Problem a could be solved by the erase command. You solved the problem b by suggesting the use of IMIF command along with If then. You solved problem c in the build 118. Jamie had also helped to clarifying the issue. My gratitude to you and Jamie. May I suggest the following? 1. There is a large Epidata Entry and Analysis user base now in many countries. Most of us are past users of EPI6 and have graduated to Epidata thankfully. If each of us writes the documentation of ONE command with example, our command reference can be really exhaustive and useful like EPI6 manual. Of course this will be massive editing job for Epidata team. There are many queries still concerned with the commands. If we were not contributing financially, at least this much effort would save some resources for the Epidata Team. If this idea appeals to you, I am willing to do my bit. 2. LIST and BROWSE commands are not exactly replaceable. BROWSE command is meant for visualizing the data only, while LIST command can actually print the list of records with selected variables in the output file. Build 118 releases LIST command only lists the list of single variables after query. If possible, kindly preserve the functionality of LIST command as it was in EPI6. With regards, Dr. Shavinder Singh

1 0

New test build 118 for EpiData Analysis
by epidata-list＠lists.umanitoba.ca 31 Aug '07

31 Aug '07

Yesterday I uploaded a new test build for analysis, now build 118. Since previous test build many internal parts have been rewritten, such that the source code is the same where possible for analysis, entry and epic. Most of this is invisible to the end-user, but assures that e.g. chk files are read the same way in the systems. A few aspects remain btw. the products. e.g. naming of integer function int() versus integer(). Of particular interest to the end-user is the following: Practical: a. A new table dialog makes it easier (hopefully) to use the possibilities in the new table command without using the command prompt. The table dialog is available from the toolbar or as a command tabdialog. b. Graphs can now be made by a group variable. e.g. box age /by=sex will create two boxes for two values of sex c CHK files are now saved with the data. Including definitions of variable labels and missing values. d When looking at a table or graph in output, rightclicking with the mouse copies that table or graph to clipboard. (for tables sometimes there is a pointer error, but this will be fixed). Technical issues: a. No new functionality will be added before release as public v2.0 except for translation, which is about half way implemented. b. Bugs should be removed before releasing. - some issues are known and will be documented in the Mantis database c. We should decide what to do about text strings in rec files, which are found in the qes files, but not read into analysis. d. Translation for analysis is about half way e. the Mantis system is not completely updated, but this should take place within about a week to reflect what was fixed and what remains. f. There are still some minor estimation problems, such as percentiles not being correct with very small samples (e.g. n<15). Regards to all -- Jens Lauritsen Coordinator and initiator of EpiData Project http://www.epidata.dk

1 0

Re: [EpiData-list] Re: Ranked variable questions
by epidata-list＠lists.umanitoba.ca 26 Aug '07

26 Aug '07

You are right Jamie - a response of 1 was given for most imporant. I will try using your v1=10-v1 and then the method Jens suggests. thank you very much to both you and Jens for your help Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 24/08/2007 1:33 p.m. >>> An important question is whether a response of 1 most important or least important? If 1 is most important, then make the default value 11 and not zero. I would just do: describe v1-v25 and scan the medians to find those with the lowest median (if 1 is most important and default is 11) or highest median (10 is most important and default is 0). Items that are infrequently ranked will have a median equal to the default. Items most frequently ranked will have a median that is based mostly on ranks. I haven't thought about the formal statistical analysis here, but you'll get a pretty good assessment. Jens approach works very well when the most important response is 10. If most important is 1, then you can also do this: v1 = 10-v1 v2 = 10- v2 etc and use aggregate. jamie > Christine wrote: > I have been asked to set up a database for a questionnaire that has > already been written. I was going to set it up in epidata but my > problem is how to deal witha question that asks people to rank > options. The question gives a list of topics and asks the person > filling in the questionnaire to rank them from 1-10 in order of > importance. > Jens wrote: > I suggest to do the following: > For each question (say 25 different themes) enter the priority the > person gave to that issue. > setup the qes: > v1 item1 ..... ## > v2 item2 ..... ## > etc > v25 text for item 25 ## > > in chk make the defaultvalue 0: > before file > DEFAULTVALUE v1-v25 0 > end > > Then in analysis after entering the data: (say you had the 25 variables) > read response > aggregate /sum="v1,v2,v3,v4,v5" > aggregate /sum="v6,v7,v8,v9,v10" etc > > * the tables will show the sum of the variables, that is the overall > ranking sum. > -- 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

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

24 Aug '07

I will be out of the office starting 08/24/2007 and will not return until 08/28/2007. If you require immediate assistance, please contact Stephen Drew at extension 5330.

1 0

Re: Ranked variable questions
by epidata-list＠lists.umanitoba.ca 23 Aug '07

23 Aug '07

Christine wrote: I have been asked to set up a database for a questionnaire that has already been written. I was going to set it up in epidata but my problem is how to deal witha question that asks people to rank options. The question gives a list of topics and asks the person filling in the questionnaire to rank them from 1-10 in order of importance. I suggest to do the following: For each question (say 25 different themes) enter the priority the person gave to that issue. setup the qes: v1 item1 ..... ## v2 item2 ..... ## etc v25 text for item 25 ## in chk make the defaultvalue 0: before file DEFAULTVALUE v1-v25 0 end Then in analysis after entering the data: (say you had the 25 variables) read response aggregate /sum="v1,v2,v3,v4,v5" aggregate /sum="v6,v7,v8,v9,v10" etc * the tables will show the sum of the variables, that is the overall ranking sum. example read bromar // example data set for epidata aggregate /sum="dectime,km,age" which gives the output: N Ndectime SUMdecti1 Nkm SUMkm Nage SUMage 4027 3556 13913.85 3620 381084.00 3786 153740 telling us: 4027 observations in all of these 3556 contributed to dectime, 3620 to km and 3786 to age variables. Sum of the three being 13913.85, 381084.00 and 153740 Obviously here the sum makes no sense, but in your case the sum of the ranking would reflect all of the variables and the responses. regards Jens Lauritsen EpiData Association ps. I tried to locate the user sending spam to the list today/yesterday and may effectively have deleted this person from the list (if not we will see more of the same spam) - terribly annoying.

1 1