- EpiData-list - University of Manitoba Mailing Lists

Convert sting to numeric - Epidata Analysis
by epidata-list＠lists.umanitoba.ca 09 Jun '06

09 Jun '06

Hello How is it possible to convert a string to a numeric value in Epidata Analysis. I have tried all the proposed solutions found on the support list, but the result is always the same 'data type mismach" I have a string variable like var1 = GHXXXXX15 And I want to make statitic(median, means ....) on the last part (15) , I can convert to a numeric value. The function to convert numeric to string exists, but no string to numeric. Thank you very much Yves Yves Dupont Institut of Public Health Rue Juliette Wijtsman 14 1050 Bruxelles Belgium Phone : 32 2 6425785 Fax : 32 2 6425410 ########################################################### Checked as being free of known viruses. Scientific Institute of Public Health, Brussels, Belgium Wetenschappelijk Instituut Volksgezondheid, Brussel, Belgi� Institut scientifique de Sant� publique, Bruxelles, Belgique Visit our website: http://www.iph.fgov.be ###########################################################

1 1

Website now in Spanish also - try www.epidata.dk/sp and other good news
by epidata-list＠lists.umanitoba.ca 05 Jun '06

05 Jun '06

*Website in Spanish (Español) *31. May 06 Due to the work of Pedro Arias and with some assistance from Juan Carlos Merino (Peron) the whole website has been translated to Spanish. Other translations can be placed if someone wishes to translate parts or all. A bit later we will arrange for a news section for the translated version also. ................................................................................................................. Good news - funding received - Financing the conversion plan A first donation of roughly 7000 Euro has been received for the development plan from a Danish Medical research fund. Experimentation with possible principles for implementation of aspects of "audit trail" will start soon based on the funding. I will add a "counter" indicating at all times what percentage of the plan is currently financed. ................................................................................................................ Regards Jens Lauritsen EpiData Association

1 0

Re: Sumfreq and Sumtables
by epidata-list＠lists.umanitoba.ca 03 Jun '06

03 Jun '06

I propose that the principle be established that any appropriate command will eventually allow weights via /w=varname To simplify syntax for many users, /sum=varname can be a synonym for /w=varname on the FREQ command and TABLES command We do not need separate sumfreq and sumtables commands. I never liked this in EpiInfo because you had to learn another command syntax and EpiInfo wasn't know for consistency of syntax. It is good practice to use the variable name COUNT (in English at least) whenever dealing with aggregated data. This becomes self documentation. We do this with an in house system for managing monster national data sets, but still will get people creating frequency tables that do not sum the COUNT variable and they wonder why every category has a frequency of 1 Jamie Hockin Public Health Agency of Canada

1 1

WinGlue menu system
by epidata-list＠lists.umanitoba.ca 03 Jun '06

03 Jun '06

1 0

Sumfreq and Sumtables
by epidata-list＠lists.umanitoba.ca 03 Jun '06

03 Jun '06

1 0

Sumfreq and Sumtables
by epidata-list＠lists.umanitoba.ca 01 Jun '06

01 Jun '06

> Please discuss on the list if the /weight= x principle is what we > want. I have met various > needs for weighting, but assume that the simple frequency weight shown > here is sufficient. > > Regards > Hi everybody, I think there are two different situations where a WEIGTH variable should be necesary: The first situation is when working with data from epidemiologial surveillance. It is very usual that data sent to a upper level (for example National level from a regional level) are sent in an aggregated format. In order to be able to analyze this kind of data a command in the form of sumfreq disease /sum=COUNT (where COUNT is the weigth variable) is essential. The second situation is when working with data comming from a complex sampling design (Not a simple random-sample strategy). In this case it is necesary to specify not only the WEIGHT variable, but the STRATA and Primary Sampling Unit. The sintax for this situation could be something like: CFREQ VAR1 /W=WEIGHTVAR /S=STRATVAR /PSU=PSUVAR Greetings, Pedro Pedro Arias Bohigas John Ericssons gatan, 12 5 tr 112 22 Stockholm Sweden Phone (cell)+46(0)734421130

1 0

Few suggestions about Epi Analysis
by epidata-list＠lists.umanitoba.ca 01 Jun '06

01 Jun '06

Dear Jens, Greetings. I hope Epi Analysis is making good progress. The graphic features are excellent addition.the Epi Ananlysis I tested old PGMs of Epi6 in Epi Analysis. Few more tweakings are further required. You know that long PGMs extendimg into pages are dealt fairly easily by Analysis.exe of Epi6.04. In Epi Analysis, when a particular set of "SELECT" commands do not select any records, the "program aborts the operation" and does not process rest of the commands of the PGM. "RECODE" command does not create e.g. age groups from age data. I strictly adopted the synytax of Epi Analysis. Analysis.exe (323 kb) of Epi info 6.04d could move mountains. It is not appropriate to compare Epi6.04 with Epi Analysis of 1.2. However Epi6 will always remain the inspiration. Long pending requirement of the portability of Epi info has been met by small sized Epidata, Epi-analysis and Flash memmory devices. Kindly keep the work going. Sincerely, Dr. Shavinder Singh

1 0

[Fwd: RE: linux and Epidata]
by epidata-list＠lists.umanitoba.ca 01 Jun '06

01 Jun '06

1 0

Sumfreq and Sumtables
by epidata-list＠lists.umanitoba.ca 01 Jun '06

01 Jun '06

1. Sumfreq / Sumtables (epidata-list(a)lists.umanitoba.ca) >Has anyone an idea on how to replace Sumfreq (or sumtables) with Epidata >analysis? >Thanks! >Gilles / Paris > > > > I understand the sumfreq and sumtables command to be able to do a frequency or crosstable but instead of counting observations the counting would be made with another variable. Example from testdata: read bromar tab agegrp . freq agegrp agegrp Age (10 year intervals) No. % 10 35 0.92 20 489 12.92 30 1198 31.64 40 1337 35.31 50 642 16.96 60 75 1.98 70 9 0.24 80 1 0.03 Total 3786 100% We can now collapse or aggregate the data file like this on agegrp: . agg agegrp /close //"agg" is the same as "aggregate" AGEGRP N 10 35 20 489 30 1198 40 1337 50 642 60 75 70 9 80 1 Now if we do a frequency on agegrp: agegrp Age (10 year intervals) No. % 10 1 12.50 20 1 12.50 30 1 12.50 40 1 12.50 50 1 12.50 60 1 12.50 70 1 12.50 80 1 12.50 Total 8 100% We have one observation for each value of agegrp. 8 records or observations in total. By listing all observations we can see that the variable N tells us how many are in each agegrp: list AGEGRP N 10 35 20 489 30 1198 40 1337 50 642 60 75 70 9 80 1 So in principle we would like a "backwards" aggregate where the weight or counting is by "N":: . freq agegrp /weight=n / Age (10 | year | intervals) | Freq. Percent ------------+-------------------- 10 | 35 0.92 20 | 489 12.92 30 | 1198 31.64 40 | 1337 35.31 50 | 642 16.96 60 | 75 1.98 70 | 9 0.24 80 | 1 0.03 ------------+------------------ Total | 3,786 100.00 Unfortunately the table just shown was made in Stata not in EpiData Analysis, but I have added sumfreq and sumtables to the workplan. Please discuss on the list if the /weight= x principle is what we want. I have met various needs for weighting, but assume that the simple frequency weight shown here is sufficient. Regards Jens Lauritsen EpiData Association

1 1

RE: linux and Epidata
by epidata-list＠lists.umanitoba.ca 31 May '06

31 May '06

At the moment EpiData has been testet on SuSE Linus 9.3 and Fedora Core 4. If you are running KDE or Gnome on Conectiva you should be able to run EpiData using the newest version of wine. Probably you will be able to run Wine(EpiData) in other environments as well, but it has yet not been testet. The Wine HQ homepage: http://www.winehq.com/ The download page: http://www.winehq.com/site/download After installing wine, install EpiData. If wine doesn't start when you try opening EpiData, open the terminal/konsole and type: wine EpiData.exe (in the appropriate folder) Known problems using EpiData in wine: EpiData will sometimes refuse to close Errors ind the chk-file can resolut in "strange" behaviour

1 0