I will be out of the office from the afternoon of December 23 until the
morning of January 3.
elaine
>>> epidata-list 12/31/05 12:00 >>>
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. V1.1 of EpiData Analysis ready (?)
(epidata-list(a)lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1
Date: Sat, 31 Dec 2005 12:23:58 +0100
From: epidata-list(a)lists.umanitoba.ca
Subject: [EpiData-list] V1.1 of EpiData Analysis ready (?)
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <43B66A4E.8060909(a)epidata.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Unless someone finds serious bugs in the testversion of EpiData Analysis
v1.1 build 61 available from:
the testing page: Http://www.epidata.dk/testing.php will be released for
general usage about one week from today.
Translation procedures have started and a preliminary partial
installation procedure in Spanish can be tested.
Many aspects are updated and enhanced. See:
Http://www.epidata.dk/testing.php for a complete list. The major issue
is a new focused help system, an aggregation (collapse) command and
extensions such as a cumulative column in frequency tables.
Work on revision of the stratified table analysis module will be made
within the first quarter of 2006, in particular due to a recent donation
from Health Canada and the Statistical Process Charts will be extended
due to the collaboration with Gruk Norway.
Regards and happy new-year to all
Jens Lauritsen
EpiData Association
------------------------------
________________________________________
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 26, Issue 15
********************************************
Unless someone finds serious bugs in the testversion of EpiData Analysis
v1.1 build 61 available from:
the testing page: Http://www.epidata.dk/testing.php will be released for
general usage about one week from today.
Translation procedures have started and a preliminary partial
installation procedure in Spanish can be tested.
Many aspects are updated and enhanced. See:
Http://www.epidata.dk/testing.php for a complete list. The major issue
is a new focused help system, an aggregation (collapse) command and
extensions such as a cumulative column in frequency tables.
Work on revision of the stratified table analysis module will be made
within the first quarter of 2006, in particular due to a recent donation
from Health Canada and the Statistical Process Charts will be extended
due to the collaboration with Gruk Norway.
Regards and happy new-year to all
Jens Lauritsen
EpiData Association
The reported problems of EpiData Entry when verifying double entry has
been solved.
The problem was that when the file to compare with was missing, then a
mysterious error message was given.
The principle has now been changed such that if the comparison file is
not existing, then the verify procedure stops completely. The path
information in the ...dbc file is no longer placed there. Therefore if
the user wishes to compare to a first entry file residing in a different
folder than where the ...dbl.rec file resides, then manually edit the
....dbc file.
Analysis is advancing
A lot of work has been put into finding a managable help file structure,
which also accomodates translation. If you see on the
http://www.epidata.dk/testing.php page, you will see that there is now a
partial translation to Spanish and the English version. Some issues of
always showing the correct file is still lacking, but is expected to be
fixed within a few weeks.
The test versions are placed on: http://www.epidata.dk/testing.php
The upgraded EpiData Entry (build 18dec2005) is on the
http://www.epidata.dk/download.php
Version information for
entry: http://www.epidata.dk/revision.htm
analysis: http://www.epidata.dk/versioninfo.htm
Kind regards
Jens Lauritsen
EpiData Association
It's more simple to to it step by step:
1- Your qes file has to contain a variable (string, length = 4. I call it YV1)) to store the year of the date entered in V1.
2- In the chk file, edit checkblock for V1, and add the line:
YV1 = year(V1)
3- Then, it is possible to enter the check lines that will calculate the categories:
If YV1 = "xxx" then
CATEGORY = "xxx"
Endif
If YV1 = "yyy" then
CATEGORY = "yyy"
Endif
(...)
End
(assuming there is a variable called Category!)
That's it.
It's better (although you can do without) to add NOENTER to YV1 checkblock, so that it will be impossible to enter another value by accident.
Gilles Delmas
-----Message d'origine-----
De : epidata-list(a)lists.umanitoba.ca [mailto:epidata-list@lists.umanitoba.ca]
Envoyé : mardi 13 décembre 2005 18:57
À : epidata-list(a)lists.umanitoba.ca
Objet : [EpiData-list] Date variable
I am having some difficulties playing around with a date variable (named v1, form dd/mm/yyyy). I wish to create a new variable with categories based upon different years within the original variable and I have tried copying the examples provided in the help section, but I'm not having any luck. Any direction would be greatly appreciated. Thanks, Kate
* Example pgm file to group a date variable V1
* created by: Jens Lauritsen, EpiData Association
set show info=off
generate 50 // generate 50 empty observations for testing
define v1 <dd/mm/yyyy>
define y ####
y = 1900 + recnumber // could also be 1900 + _n
v1 = dmy(1,7,y)
* so now we have a date variable with dates from 1900 to 1950
* three different strategies to group.
* Strategy 1: extract year from the date and recode to a string:
define y1 ####
define ys ________________________
y1 = year(v1)
recode y1 to ys by 10
tab ys
* Strategy 2: round the number into 10 year groups
define y2 ####
y2 = year(v1)
y2 = trunc(y2/10)*10 // creates groups by 10 years
tab y2
* If you use 5 instead of 10 you get 5 year groups
* y2 = trunc(y2/5)*5 // creates groups by 5 years
* strategy 3: split on specific dates:
define y3 #
let y3 = 0
if (v1 < dmy(1,10,1930) ) then y3 = 1
if (v1 >= dmy(1,10,1930)) and (v1 < dmy(1,10,1939) ) then y3 = 2
if (v1 >= dmy(1,10,1939)) and (v1 < dmy(1,10,1960) ) then y3 = 3
tab y3
* run the above to get the tabulations.
----------------------------------------------------------------------------------
Output:
E.g. for strategy 1:
No. % Cum %
1900 - 1909 9 18.00 18.00
1910 - 1919 10 20.00 38.00
1920 - 1929 10 20.00 58.00
1930 - 1939 10 20.00 78.00
1940 - 1949 10 20.00 98.00
1950 - 1959 1 2.00 100.00
Total 50 100%
* strategy 2:
No. % Cum %
1900 9 18.00 18.00
1910 10 20.00 38.00
1920 10 20.00 58.00
1930 10 20.00 78.00
1940 10 20.00 98.00
1950 1 2.00 100.00
Total 50 100%
* strategy 3
No. % Cum %
1 30 60.00 60.00
2 9 18.00 78.00
3 11 22.00 100.00
Total 50 100%
----------------------------------------------------------------------------------
Regards Jens Lauritsen
EpiData Association
A new build (dec 13th) is almost ready which fixes some of the other issues of double entry mentioned earlier.
Before releasing the new one we will find the cause of the error reported by Yali Zhang.
If anyone else have issues of double entry please submit files to info @ epidata.dk
Best Regards
Jens Lauritsen
EpiData Association
I am having some difficulties playing around with a date variable (named v1,
form dd/mm/yyyy). I wish to create a new variable with categories based
upon different years within the original variable and I have tried copying
the examples provided in the help section, but I'm not having any luck. Any
direction would be greatly appreciated. Thanks, Kate
Hi,
When I opened the T3_dbl.REC file for double entry, the system suggested
that "DOUBLE ENTRY VERIFICATION MODE Error". I could open the T3_dbl.REC
file, but I couldn't verify the entry. Why? How to solve it?
There are some Chinese characters in the REC file.
Thank you,
Yali Zhang
Department of Clinical Epidemiology
Beijing Hui Long Guan Hospital
Beijing Suicide Research and Prevention Center
Beijing 10096 P.R.C
Fax: 86-10-82951150
E-mail:zhang_bsrpc@hotmail.com
zhangyali(a)crisis.org.cn
_________________________________________________________________
免费下载 MSN Explorer: http://explorer.msn.com/lccn/
In the help file users can find information on this:
color data black yellow aqua
color background white
But not further information on how to use these check file commands.
One example is:
BEFORE FILE
color data black yellow aqua
color background white
end
Which will give yellow fields and aqua current entry fields. The background will be white and the colour of texts black.
Backup as check file command
The backup command documentation is incorrect in the help file. The help file says:
AFTER FILE
BACKUP F:\backup\distinationdirectory ZIP myzipfile.zip [DATE]
END
This should be: (to create a zip file with the date appended to the zip file name)
AFTER FILE
BACKUP F:\backup\distinationdirectory ZIP myzipfile [DATE]
END
It is always good practice to search the help file for a given word and if the examples are insufficient - then suggest to the list how it could be formulated. If users are not using the help system and this is due to faulty help system, then criticise the help system. But sometimes it appears that questions are asked without the user spending time on:
1. Looking in the help system
2. Searching old messages in the epidata-list on the topic
3. Looking in the further documentation supplied at the web page.
http://www.epidata.dk/documentation.php
We are now experimenting with solutions to translate analysis and create focused help. Users knowing of funding resources for translation please contact me at:
info"at"epidata.dk (replace "at" with @)
Best Regards
Jens Lauritsen
EpiData Association