I will be out of the office starting 04/30/2008 and will not return until
05/01/2008.
If you require immediate assistance, please contact Celina Sousa at
extension 5300.
Thanks and have a great day,
Alyshia
Hi,
all the answers that you have received are right.
There is still one more reason why you can loose the data when trying to
change the QES file.
If you have used the option in EpiData to modify the name of the variables
directly in the REC file (tools-->rename fields), then when you make a
modification in the QES file no matter which way you use you will loose
your data as the names of the variables in the REC file do not match the
name of the variables in the QES.
Hope it helps
Pedro
> -----Message d'origine-----
> De : epidata-list(a)lists.umanitoba.ca
> [mailto:epidata-list@lists.umanitoba.ca] Envoyé : lundi 28 avril 2008
> 13:13
> À : epidata-list(a)lists.umanitoba.ca
> Objet : [EpiData-list] How to keep data when modifying questionnaire
>
> Hi,
> i started data entry and now need to add 2 new variables to the QES
> file, when i transfer the QES file into REC file, the old data
> disappeared, any tips how to avoid it?
>
> Thank you in advance and best regards
> ziad
>
>
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 54, Issue 13
> ********************************************
Hi,
i started data entry and now need to add 2 new variables to the QES
file, when i transfer the QES file into REC file, the old data
disappeared, any tips how to avoid it?
Thank you in advance and best regards
ziad
Hi, Ziad
I think you can do it with menu TOOLS > REVISE DATA FILE
You will have to enter values for these new variables on the yet entered questionaires, for sure.
Hope it helps,
Fúlvio
Grups de Recerca d'Amèrica i Àfrica Llatines - UAB (Barcelona, Spain)
Porto Alegre, Brazil
----- Mensagem original ----
De: "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca>
Para: epidata-list(a)lists.umanitoba.ca
Enviadas: Segunda-feira, 28 de Abril de 2008 19:09:21
Assunto: EpiData-list Digest, Vol 54, Issue 12
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. How to keep data when modifying questionnaire
(epidata-list(a)lists.umanitoba.ca)
Hi,
i started data entry and now need to add 2 new variables to the QES
file, when i transfer the QES file into REC file, the old data
disappeared, any tips how to avoid it?
Thank you in advance and best regards
ziad
________________________________________
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/
EpiData Analysis build 134
I found problems with the internal definitions of variable names after
running a browse in combination of running part of a pgm file in the
editor in a block (F8).
If you get strange "variable not found ....." or similar error and that
variable is no longer in your dataset, unfortunetely you have to close
analysis and start over.
The error is either part of the editor NOT parsing lines correctly to
analysis (e.g. the block is sent for analysis in a different size than
shown on the screen) or the browser not cleaning up memory correctly after
a browse.
The error will be further documented, tracked and removed. I have NOT been
able to create the error without using browse. - for safe mode showing of
data in this build then use list command instead.
(This underlines the necessity of always having a test period before final
release).
regards
Jens Lauritsen
Coordinator and initiator of EpiData Project
http://www.epidata.dk
For a medication study we wish to test the hypothesis of no diffence in
use of additional morphine for patients given two different pain regimens.
The data collected for each patient is the date and time of additional
medication from day one until day seven. The number of additional
medication given varies from 0 to many. Therefore we record the data as:
id : patient id
d : date of medication
m : Dosage of the medication
Basic data are saved for each patient
grp : treatment group, A vs. B
dayop : Date of surgery
For the analysis we also need:
variable m : sum of additional morphica given
varable d : day of treatment
This would seem easy:
read medication
* add day of surgery etc.:
merge id /table=basicdata
gen i day = d - dayop
* now aggregate on day of medication
aggregate id day grp /sum=m
* save for later:
savedata daymedication /replace
* this creates the summary variable summ for m
* summ contains the sum of medication on each day for each patient
means summ /by=grp /t : overall
means summ /by=grp / t if day = 1 : example comparison on day one.
But this will give a wrong result, since only persons given medication are
recorded in the medication file.
We therefore need to restructure the analysis:
A. Create a complete file for all patients:
* generate file of patient id' numbers
* (here 22 patients on day one and two):
generate 44
gen i idn = recnumber +1
* we need two lines for each patient:
gen i id = (idn div 2)
gen i grp = 1
* our dataset is such that first 11 patients are group 1 and remaining
group 2:
if id > 11 then grp = 2
gen i day = 1
if (id = id[recnumber-1]) then day = 2
drop idn
labeldata "Key file for all patients"
savedata key /replace
* this file now contains exactly one record for all patients on each of
day one and two.
B now we can analyse the data again:
(notice the daymedication file created above)
* get the complete file:
Read key /close
* add medication information:
merge id day /table=daymedication
* add basic information on
merge id /table=basicdata
* for patients with no medication summ is equal to . (missing)
recode summ .=0
* now summ contains the sum of medication on each day for each patient
* show the observations for all days:
* generate indicator variable based on day and group
gen i g = 10*(grp-1) + day
labelvalue g /1="Case Day 1" /2="Day 2" /11="Control day 1" /12="Day 2"
* verify distribution of summ as a probit plot
cdfplot summ /p
* for aggregation in the cdfplot the variable must be integer:
gen i mx = integer(summ*1000)
cdfplot mx /p /agg
* for my specific data showing a straight line
* (with a slight "too many at zero" problem)
* show as box and dotplot:
box summ /by=g /n /out
dotplot summ /by=g /sizex=600 /xa /di=0.25 /ti="Amount given - patient level"
* finally test the hypothesis
means summ /by=grp /t : overall
means summ /by=grp if day = 1 : comparison on day one.
means summ /by=grp if day = 2 : comparison on day two.
Jens Lauritsen
Coordinator and initiator of EpiData Project
http://www.epidata.dk
Many minor problems have now (hopefully) been solved in build 134 of
EpiData Analysis. Which is available from the usual testing page:
www.epidata.dk/testing.php
Some issues remain:
- small data / zero cell inaccuracies (Most likely not solved, but
better information should be developed)
- update had to be disabled in this build
- a major rewrite is needed before stable function
use EpiData Entry for changes to data instead.
- some wishes reported to Mantis database
- The user base seems divided in where to put some aspects in the menu
system:
- should logfiles be in file menu or results
- should edit setup ini be in file menu or edit
Issues solved: Version 2.0.0 build 134
* Extended or adapted function
* CIPLOT: adapted to changed order of variables and defaults
new plot with confidence intervals for proportions
(e.g. cases in subgroups of other variables)
* BAR and Histogram: Y axis can be scaled as percent: Option /PCT
* Weight variables can be non-integer in tables
* merge accepts comparing upper string with string key
* Update disabled this build (inconsistent behaviour must be
rewritten)
* Documentation
* Command reference updated (F1)
* added quick guide (see F1)
* Bugs
* Upper string variables written as standard string
* Various bugs removed
For those wishing to test or comment on the adapted menu system, please see
www.epidata.dk/testing.php to get the updated build.
Following testing we are approaching release as v2.1 with first
translations in Spanish and French.
I do acknowledge in particular Gilles Desve for the adaptation of the
multinational translation module and
Jamie Hockin, Pedro Arias, Peron (Juan Carlos Merino), Bjørnar Nyen,
Hans L. Rieder and Neville Verlander for discussions and inputs. But
also the EpiData-list discussants in general.
In the previous year the Association of Public Health Epidemiologists in
Ontario have established an important expert panel, which have been very
active in the specification of the CIplot command and other recent
aspects. More on this latter collaboration will be announced later.
Update is not permanently disabled, but has shown many problems.
Therefore I am considering NOT to wait a full rewrite of update, but
instead disabling update, to be able to release v2.1 with translation.
Comments welcomed on this aspect also.
Regards Jens Lauritsen
EpiData Association
I will be out of the office starting 04/19/2008 and will not return until
04/23/2008.
If you require immediate assistance, please contact Celina Sousa at
extension 5300.
Thanks and have a great day,
Alyshia