- EpiData-list - University of Manitoba Mailing Lists

��dryangyun��
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

where is your master websites,thank you

1 0

sorting rec file
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

"Is there any possibility to sort the file without exporting the data?" Within EpiData Entry: Define the ID field as a key ID key unique end then after entering all data, export data (#6 in toolbar) to EpiData file and mark "use index as sort order" In EpiData Analysis read myfile sort id savedata newfile copyfile myfile.chk newfile.chk Regards Jens Lauritsen EpiData Association

1 0

Sorting of rec File ?
by epidata-list＠lists.umanitoba.ca 13 Feb '07

13 Feb '07

Dear all, Because of our study design and the randomization procedure in our trial the ID can not be entered in the correct order. Later on it would be more convenient to enter data in the order of the ID. Is there any possibility to sort the file without exporting the data? Thanks in advance, Markus

1 0

QES with two colmns?
by epidata-list＠lists.umanitoba.ca 12 Feb '07

12 Feb '07

Hello all, As times goes by, Im getting the idea that data entry is an art more then a science. Many ptojects have to keep a lot of fields in the paper form and at the end the paper is not big enough to have them all. The consequence is that the QES file should be as similar as possible with paper forms. These last couple weeks Im tryin to make a QES file with tow columns but I cant get to straight up the second column in the REC file. When I make the QES I line up the second by hand, since menu EDIT\line field comand seems to work fine only with one column. But whe the REC file generated the variables, labels and filds of the second column are not align as the QES file (sometimes the labels are uncomplete). Exemple: QES p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 CAUSA MORTIS <A > p75 NECESSITOU INTERNACAO # p76 PROLONGOU A INTERNACAO # p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PARA INDUSTRIA # -- Exemple of resulting REC. p71 RECUPRACAO # p72 SEQUELA # p73 OBITO# p74 AUS<A > p75 NECESSITOU INTERNACAO # p76 PROLON# p77 MEDICAMENTO SUSPENSO # p78 HOUVE MELHORA # p79 POSOLOGIA ALTERADA # p710 NECESSITOU TRATAMENTO ADICIONAL # p711 HOUVE REEXPOSICAO # p712 REACAO REAPARECEU # p713 PRIMEIRA NOTIFICACAO # p714 NOTIFICADO PAR # The most amazing to me is that I´ve worked on some QES files with tow columns before and sometimes it works fine and sometimes it just does not work. At this file for example, a few segments work fine and some dont. Any tip to work around this matter? Thank you, Pedro Emmanuel Brasil Abraço forte e que a força esteja com você, Pedro Emmanuel

1 2

Web Site problem corrected. - new graph command ready v2 b106 analysis
by epidata-list＠lists.umanitoba.ca 08 Feb '07

08 Feb '07

There has been a problem with the website download principle on www.epidata.dk during the last 24 hours. The problem has been resolved, but affected downloads as well as the "Mantis" documentation system. In the latest test build for analysis (b106) a new graph type was included, called "dplot" This will plot a cumulative frequency curve for a given variable. Example of usage: * Show a cumulated frequency percent plot for a variable (here height): dplot height dplot height /yline=50 - the values contained are the same as those showed at : freq height /CP * With option /P: Show a probit plot. * If the data are distributed as Gaussian (Normal) then a probit plot will show data on a straight line. X axis: Midpoints of all data. (e.g. if x = 1 3 ...., then first observation is at x=(1+(3-1)/2)=2 Y axis: The cumulated percentage is converted to probability and graphed as the inverse normal probability dplot height /P There is an unresolved issue with small numbers (incorrect showing) Regards Jens Lauritsen

1 0

How to edit a graph and set further options
by epidata-list＠lists.umanitoba.ca 07 Feb '07

07 Feb '07

Gilles responded correctly on the question of further defining graph options: Try the command: SET GRAPH EDIT = ON which will work in v1 of analysis In the test version v2.0 the "set graph edit" is not allowed. Instead you have to add /edit to any graph command. e.g. scatter v1 v2 /edit But many users will (I assume) use the dialogs from the workprocess toolbar. And in these the /edit is by default added to all graph commands. Regards Jens Lauritsen EpiData Association

1 2

Editing graphs using Epidata analysis
by epidata-list＠lists.umanitoba.ca 06 Feb '07

06 Feb '07

Hallo, I downloaded the test version of the latest Epidata analysis sofware.My problem is;How do I edit a graph so that the percentages appear in each bar or in pie chart. I think I have communicated. Thanks Caleb Ouma Ongong'a +254721-953790, +254733890191 P.O Box 756556-00200 Nairobi-Kenya "Remember that happiness doesn't depend on what you are or on what you possess, but only on how you think." --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar.

1 1

Today autofield
by epidata-list＠lists.umanitoba.ca 05 Feb '07

05 Feb '07

Hello all, I have been reading the epidata list for while but never tryed to send anything so far. It has been a while that I cant get the field <d/m/y-today> work at enter data. I´ve tryed other today autofields but none have worked so far. When I edit chek, this field appears to be working because the today date is there and field is not open for edition. However, when I open the enterdata, the field is always empty and, of course, I cant enter the date in there. My work around, although not as efficient, is to use the <dd/mm/yyyy> with the REPEAT comand in the check file. Is it some sort of bug or Im doing something wrong? Best regards, may the FORCE be with you all, Pedro Brasil Instituto de Pesquisa Clinica Evandro Chagas Fundação Oswaldo Cruz Av. Brasil 4365, Rio de Janeiro, Brasil -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 1

How to get test version of EpiData Analysis v2
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Point your browser to : Http://www.epidata.dk/testing.php and click on: "Complete Setup" or click directly on this link: http://www.epidata.dk/php/downloadc.php?file=setupepidatastattest.exe Notice that test versions should always be used with caution until they are released from the official download page at http://www.epidata.dk/download.php Kind regards Jens Lauritsen EpiData Association

1 0

Re: [EpiData-list] Validation duplicate files
by epidata-list＠lists.umanitoba.ca 02 Feb '07

02 Feb '07

Hi Charity and Lars: There are two ways for duplicate data entry: 1) independent of sequence 2) dependent on sequence 1) If you use a field with unique identifier, you can enter the data independently of sequence twice, and then compare the two files later on that unique identifier. In this instance two data entry groups can enter add the same time part A and part B and then switch for second entry. 2) You can use the "Tools" "Prepare Double Entry Verification". If you do not tick and choose the option "Match records by field" (and choose the Unique identifier), then the second entry will by default follow the record number, and thus sequence matters. If you choose that option, the first data entry group will still have to await completion by the first data entry group. As Charity says, it is critical in any case to have a truly unique identifier which can by assured by KEY UNIQUE. Seemingly, Lars, you did not have that. You must thus identify the records with duplicate identifiers and or missing identifiers in both files, mark them for deletion (but not packing" and then compare. You deal then separately with the problematic records in both files, most simply perhaps by reentering them properly and independently in both files. Regards, Hans Hello Lars, I just did a small test of this to make sure, and the ordering/sequence of IDs in the two files does not make a difference when Validating Duplicate Files. What will cause a problem is if there is a duplicated ID in one of your two files - are you sure that the Case IDs are unique? You should have "KEY UNIQUE 1" included in your .chk file for the ID variable to ensure this. Kind regards, Charity On 2/1/07, epidata-list(a)lists.umanitoba.ca <epidata-list(a)lists.umanitoba.ca> wrote: Dear Epidata_list, I'm a new member of this list and a fairly new user of the Epidata software. In attempting to validate duplicate files not entered in same sequence by two observers I have difficulty in performing the test under documebt/validate duplicate files. Attempting to perfom the test with a selected key field of case-id an error is given; "Duplicate keys found" and the validation is terminated. Is it possible to perform a comparison of the two datasets despite the fact that the registrations are not performed in same sequence with regard to registration of the observations? Siincerely, Lars -- 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