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.
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
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
Hi,
How can i have an Epidata Analysis V2.0 for make some testing?
Thanks
___________________________________________
Dr Jean-Paul DIBY-KONAN
Médecin Santé Publique
MCM Santé de la Reproduction
Institut Médecine Tropicale
Kapucinessenstraat 8 B-2000 Anvers
Belgique
----- Message d'origine ----
De : "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca>
À : epidata-list(a)lists.umanitoba.ca
Envoyé le : Jeudi, 1 Février 2007, 19h15mn 13s
Objet : EpiData-list Digest, Vol 40, Issue 1
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. Tables in 2.0 R. 1 Build 104 of Epidata Analysis
(epidata-list(a)lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1
Date: Thu, 1 Feb 2007 08:04:10 -0800 (PST)
From: epidata-list(a)lists.umanitoba.ca
Subject: [EpiData-list] Tables in 2.0 R. 1 Build 104 of Epidata
Analysis
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <398980.61861.qm(a)web32105.mail.mud.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Hi,
Thank you for introducing the test version of Epidata
Analysis V2.0.
I tried to do some tables using it but no infrential
statistics is performed. Just an r*c table is shown.
Even for "Means" command, just descriptive statistics
is shown.
Thanks
Reza
____________________________________________________________________________________
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
------------------------------
________________________________________
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 40, Issue 1
*******************************************
___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
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
As announced a short while back the module is now available for testing.
A short example should help users getting started on the test.
1. Expect that some/many set commands have changed. E.g.
Obsolete ones in version 2: Set statistics, set percentages, set table
reverse etc
2. You only get what you ask for. e.g.:
tables v1 v2 // will only give the counts
tables v1 v2 /R // will give row percentages (column:/C,
total: /T)
tables v1 v2 /T /EX // will give a chi square test and
with /EX also exact tests for 2x2 tables
tables v1 v2 v3 /T /EX // will do a stratified analysis with
overall exact testing as well.
tables v1 v2 v3 v4 /OA //will make a condensed outbreak analysis table
tables v1 v2 /SD // will sort descending instead of the default
ascending sort on row and column
tables v1 v2 /SRAT // will sort ascending on the row total
/SRDT would be descending
3. replacement for epitables or etab will be typically (to have highest
value as case and exposure):
tables v1 v2 v3 /sd /t
Many aspects are not final yet - notice it is a test build, e.g. some
issues remain on medians in SPC graphs.
Therefore the front page also states:
Notice - this is a premature test build - only for experienced test
persons !
regards
Jens Lauritsen
EpiData Association
Public testing of version 2 of EpiData Analysis can now begin.
A lot of work has been done to reshape internal parts of EpiData
Analysis. All users are now encouraged to participate in the testing.
A system of comparing estimates, counting with results of Stata or Epi6
is applied. Currently the system contains around 1000 different tests.
But maybe the system is not taking care of all problems, therefore user
tests are also important.
A complete list of changes is shown at
http://www.epidata.dk/analysisversioninfo.htm.
Main points are:
Output is simplified. You only get what you ask for. To get more add
options (e.g. /T) to the command
Tables Extended (sorting, percentages, weights, outbreak)
Metadata commands: missingvalue, labelvalue, rename
Outbreak analysis: "tab outcome exposure variables /oa" "epicurve
datevar outcome group"
The test version is placed at: Http://www.epidata.dk/testing.php
Please discuss the new version on this list.
If you find definite bugs report to http://www.epidata.dk/php/mantis,
where all development is documented.
..............................................................
Regarding the discussion last week of differences btw. open-source and
free software.
As announced earlier a "master plan" for rewriting all EpiData Software
to Open-Source as well as platform independence is part of the general
development plan for EpiData. Releasing software as open-source makes no
sense if the structure and content of the product is not sufficiently
modular to allow for several independent development lines.
Someone might disagree with me on this, but knowing how fragile software
development is and seing the increased requirements for documentation
and quality assurance I am assured that a controlled situation is
preferable at this point in time. For almost all end users having a
stable, quality assured software line is more important than having
access to independent and possibly confusing development. But there
should be no doubt that the aim is at an appropriate time to release the
product source-code as open-source.
Should anyone have a lot of energy or time to add to the project there
are many issues needing assistance, e.g. answering questions on the
epidata-list, assisting in sorting incoming mails to the help line,
releasing mails for the epidata-list coming from un-subscribed persons,
creating a FAQ collection such as that running for Stata at
http://www.stata.com/support/faqs/ or joining a group running a wiki for
EpiData, which could contain the FAQ. A start of this can be seen at
www.epidata.org/wiki, but will not be announced before such a group has
been established (A coordinator has been found). Notice also that for
EpiData Entry users can develop their own CHK file commands. Modules for
doing so (source code and examples) are found on
http://www.epidata.dk/documentation.php
..............................................................
Kind regards
Jens Lauritsen
EpiData Association
Hi,
Thank you for introducing the test version of Epidata
Analysis V2.0.
I tried to do some tables using it but no infrential
statistics is performed. Just an r*c table is shown.
Even for "Means" command, just descriptive statistics
is shown.
Thanks
Reza
____________________________________________________________________________________
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/