Dear Ziad,
Perhaps it may be better to merge the files to produce one file of
observations (all levels should be included). If you decide to go through
this route, please remember that this can be done in EpiData Analysis using
the MERGE command.
Best wishes
Tieble
2009/10/22 <epidata-list-request(a)lists.umanitoba.ca>
> 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. Re: EpiData-list Digest, Vol 72, Issue 7
> (epidata-list(a)lists.umanitoba.ca)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 22 Oct 2009 08:15:08 +0200
> From: epidata-list(a)lists.umanitoba.ca
> Subject: [EpiData-list] Re: EpiData-list Digest, Vol 72, Issue 7
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID:
> <897a5cf60910212315r4894a4b8t6cd37fa5668cbd6f(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi!
> I have had 2 date related vaiables called "datebase1" and "datebase2"
> in EpiData. When exported them into STATA, they are showing as
> "datebase" and "datebase" and both variables contain the same value
> now which is not correct.
>
> It might be due to the total number of characters for the variable
> name, but my question is how can I fix it?
>
>
> Best regards
> ziad
>
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 72, Issue 8
> *******************************************
>
Correction to last message:
An ampersand (&) does translate to & when it appears in a .qes file /
header of .rec,
but it does not get translated when it appears in DATA, i.e. a text field
that contains "A & B"
--
Jamie Hockin
The module is not correctly handling special characters in creating recxml
files. Two examples I've found so far.
1. " translates to &qout; rather than "
2. & is not translated to &
sample .qes lines are:
a var # 1 = "some text"
b var # Factor A & Factor B
either of these causes failure on reading the recxml
--
Jamie Hockin
Thank you for your prompt reply, however the screen with backup option (i.e.
with the destination) does not appear at all.
The only message that I get from both menus document and export is "file not
found".
I have no problem performing the backup on other computers on which I
installed the Epidata program. However for some reason the message "file
not found" occurs only on the computers where I do not have permission to
install the program. Is there any solution to this problem? Clearly I have
tried to write a short program to backup, unfortunately that did not work
too.
Your help will be appreciated
Kind regards
Tieble
2009/10/16 <epidata-list-request(a)lists.umanitoba.ca>
> 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. Backup data file (epidata-list(a)lists.umanitoba.ca)
> 2. Re: Backup data file (epidata-list(a)lists.umanitoba.ca)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 15 Oct 2009 18:35:14 +0100
> From: epidata-list(a)lists.umanitoba.ca
> Subject: [EpiData-list] Backup data file
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID:
> <bf1bb7700910151035u36e2d874vf7d16b6d04fb56a(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I will appreciate it if anyone could provide me with some advice in
> creating
> a backup in Epidata. Every time, I try to use the menu to backup the
> following message appears "File Not Found".
> Clearly, I did not encounter any problem creating the backup file/data in
> the EpiData programs installed on my PCs (laptop and desktop). But I am
> having difficulty in backing up the rec. file created on a company's
> computer.
>
> Kind regards
>
> Tieble
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 15 Oct 2009 18:52:27 -0400
> From: epidata-list(a)lists.umanitoba.ca
> Subject: Re: [EpiData-list] Backup data file
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID: <4AD7A7AB.6020705(a)sympatico.ca>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Check the Destination directory in the box that opens up with Backup. It
> may point to a directory for which you do not have write access.
> > I will appreciate it if anyone could provide me with some advice in
> creating
> > a backup in Epidata. Every time, I try to use the menu to backup the
> > following message appears "File Not Found".
> > Clearly, I did not encounter any problem creating the backup file/data in
> > the EpiData programs installed on my PCs (laptop and desktop). But I am
> > having difficulty in backing up the rec. file created on a company's
> > computer.
> >
> > Kind regards
> >
> > Tieble
>
>
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 72, Issue 6
> *******************************************
>
I will appreciate it if anyone could provide me with some advice in creating
a backup in Epidata. Every time, I try to use the menu to backup the
following message appears "File Not Found".
Clearly, I did not encounter any problem creating the backup file/data in
the EpiData programs installed on my PCs (laptop and desktop). But I am
having difficulty in backing up the rec. file created on a company's
computer.
Kind regards
Tieble
To: EpiData software development team
EpiData software core module Version 0.2.1 build 99:
Exporting to EpiData REC file and reading exported file in EpiData
Analysis 2.2.1.171:
File:
Num fields = 65
Num data fields = 65
Num records = 37635
1) All field labels are front-truncated
2) CHK file seems correct
--
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
Thanks Jamie
I tried this and it worked well. It was quite easy to copy the Attack rate table into Excel. I just highlighted the data in the htm file and pasted it into a black worksheet. Then I
1. used data/text to columns to separate out the confidence interval colum into two columns (low and high)
2. Used edit replace to take out the brackets
4. Change the order of the columns to LowCI HighCI RR
3. Selected the data to make a chart
4. Chose stock chart
5. I also chose the option to include the data table within the chart
The graph does not look as good as CIplot but does look pretty good.
many thanks
Christine
Christine Roseveare
Analyst
Regional Public Health
570 9194
027 495 9671
>>> <epidata-list(a)lists.umanitoba.ca> 6/10/2009 2:28 a.m. >>>
Hi Christine,
CIPLOT is showing proportions, not RR. I think you will have to create
your own chart in another package. You can import the attack rate table
into excel and with a bit of manipulation, get the columns in the right
order for a "stock chart" - stock chart uses the order Close, High, Low,
where Close will be RR, High will be UCL and Low will be LCL.
However, you will have to do some formatting to do to get the chart
looking as good as CIPLOT.
Jamie Hockin
Christine wrote
> Does anyone have a tip for the best and easiest way to graph the results of the attack rate table for an outbreak analysis including confidence intervals? I have run the outbreak analysis and generated the attack rate table
> (TAB CASE 1 OYSTERS PRAWNS CHICKEN etc OA/ex), This is great. BUT...
>
> Now I have been asked to show all the exposures with relative risks higher than 2 and CIs that don't include 1 (of which there are about 10) on a single graph. The graph must show relative risk, lower confidence interval and higher confidence interval for each exposure. I have looked at the CI graph in Epidata Analysis but
> a) I only want the total and the CIPLOT graph shows Yes and No as well as total
> b) I want to show more than one exposure on the same graph and I don't think I can do this with the CI.
>
--
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 **
Hi
Does anyone have a tip for the best and easiest way to graph the results of the attack rate table for an outbreak analysis including confidence intervals? I have run the outbreak analysis and generated the attack rate table
(TAB CASE 1 OYSTERS PRAWNS CHICKEN etc OA/ex), This is great. BUT...
Now I have been asked to show all the exposures with relative risks higher than 2 and CIs that don't include 1 (of which there are about 10) on a single graph. The graph must show relative risk, lower confidence interval and higher confidence interval for each exposure. I have looked at the CI graph in Epidata Analysis but
a) I only want the total and the CIPLOT graph shows Yes and No as well as total
b) I want to show more than one exposure on the same graph and I don't think I can do this with the CI.
Any help much appreciated.
thanks
Christine
Christine Roseveare
Analyst
Regional Public Health
570 9194
027 495 9671
--
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 **
An exiting phase of development is now ready for general comments and
testing. In june/july of this year the first cross platform experiments
were available published on the testing page
http://www.epidata.dk/testing.php
Crossplatform function must solve aspects such as:
- many different local character sets
- different standards for physical file formats
- the user should not do anything special when sending or receiving
files created on another operating system
On top of this another issue is coming up soon - the development of a
dedicated data entry module also allowing for GCP (Good Clinical
Practice) rules of transaction logging.
Therefore we have now experimented with development and specification of
a file format which contains as well the data as the metadata needed for
understanding the data. By doing so we are moving towards a new structure:
a. Datafile containing datadefinition and data.
(parts of current rec and chk file). Suggested extension: recxml
b. Dataentry definition file containing control during entry
(e.g. relate, range, mustenter etc). Suggested extension: chkxml
- part b not developed yet
The proposed new data format is described here:
http://www.epidata.org/dokuwiki/doku.php/documentation:datafileformat_xml
Just now users are encouraged to test the following:
1. Can the test application read your files ?
2. Can the test application write your files ?
3. In particular test - when possible - whether the data files can be
read on another operating system. E.g. saved by a Linux or Mac and then
read on a windows pc.
Get the test application from: http://www.epidata.dk/testing.php
And report to the epidata-list of failures and success.
Data formats supported are: REC, RECXML, ODF, DBF, XLS
A table of what can be imported and exported is shown here:
http://www.epidata.org/dokuwiki/doku.php/documentation:importexport
Operating systems supported are: Mac (OS X), Linux (32+64bit), Windows.
Mac PowerPC expected soon.
After a few weeks of comments on the format a new test application will
be created. Which will collect some time estimates of reading and
writing data with subsequent reporting to a central database. This
method should allow for future user tests of core modules with
documentation available on the central website.
Regards Jens Lauritsen
EpiData Association
v2.2.1 (Build 171) of EpiData Analysis has been uploaded.
The only changes are:
Fixing mismatch of subfoot and estimates information on SPC charts.
Extending information for RunCharts - telling the number of measurements
and points omitted on median.
regards
Jens Lauritsen
EpiData Association