3. How to use large amounts of of legal values in chk file
> We are building a data-entry system for the registration of medical contact for the youth in our organisation.
> Therefore we need several hundreds of schoolcodes and zipcodes (postcode).
>
>
On the page www.epidata.dk/examples.php there are two examples of using
comment legal based on external files, - see these entitled: "Comment
legal recfile - Birds and tick names" plus "Comment legal recfile -
Bacteria list".
regards
Jens Lauritsen
EpiData Association
We are building a data-entry system for the registration of medical contact for the youth in our organisation.
Therefore we need several hundreds of schoolcodes and zipcodes (postcode).
For the quality of data I want to use this data in the chk file in the following way.
In stead of:
LABELBLOCK
LABEL_POSTCODE
LEGAL
2234
2344
2544
2645
.
ETC
END
POSTCODE
LEGAL USE LABEL_POSTCODE
MUSTENTER
END
I want to use an externel file POSTCODE.INC
whith the data and used the following syntax:
LABELBLOCK
LABEL_POSTCODE
INCLUDE POSTCODE.INC
END
POSTCODE
LEGAL USE LABEL_POSTCODE
MUSTENTER
END
But I only get errors.
Someone has a solution?
Franco L. Sanavro
Epidemiologist
Regional Health Centre
GGD Zuid-Holland Zuid
Postbus 166
3300 AD Dordrecht
The Netherlands
078 6321817
fsanavro(a)ggdzhz.nl
www.ggdzhz.nl
1. Output formation and slow output
To remedy slow output: hit F12 button every so often. This will clear the
screen and output speed goes up.
Explanantion:
Output in EpiData Analysis is created in html format. The same format used
on internet pages. The good feature of this is that formatting is easy
without a lot of programming. E.g. for reporting users can write:
set echo=off
read myfile
count if age > 45 /q
type "Number of persons was @$count" /h3
tab sex
boxplot age /by=sex /ti="Current age structure by sex"
set echo = on
and the sentence with "type" will show the number of counts in a header
type line (/h3) followed by a table of sex and a boxplot.
The problem of html is however that it is a block structured file format.
Therefore each time a line is added the whole output - not just the added
line - has to be written on the screen. Therefore the speed of output
slows down for every additional line you add.
After a certain length of the output the screen clears automatically.
Users cannot control this length (currently).
To remedy slow output: hit F12 button every so often. Then when you have
the complete output you wish, save the commands as a pgm file and run all
again. Or at some point issue "logclose" and read the resulting logfile
(default EAoutput.htm) in a browser.
2: Vista and analysis:
There has been a report that EpiData Analysis cannot run on Windows
Vista.
If anyone are using Vista, please report your experiences with this.
I assume that the specific user had insufficient "writing rights"
to the Vista machine, since the stopping occurred when trying to open
EAoutput.htm as part of the initiation sequence for analysis.
regards
Jens Lauritsen
EpiData Association
Please unsubcribe my name from Epidata, as I cannot do this myself online, having forgotten my password.
With Thanks
I. Riach
________________________________
From: epidata-list-bounces(a)lists.umanitoba.ca on behalf of epidata-list-request(a)lists.umanitoba.ca
Sent: Fri 23/11/2007 5:01 AM
To: epidata-list(a)lists.umanitoba.ca
Subject: EpiData-list Digest, Vol 49, Issue 11
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. EpiData Analysis v2.0 Build 128 available
(epidata-list(a)lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1
Date: Thu, 22 Nov 2007 17:36:44 +0100
From: epidata-list(a)lists.umanitoba.ca
Subject: [EpiData-list] EpiData Analysis v2.0 Build 128 available
To: epidata-list(a)lists.umanitoba.ca
Message-ID: <4745B01C.1090106(a)epidata.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I just uploaded v2.0.1.128 on the page: www.epidata.dk/testing.php
This build remedies as far as we can test here the problems shown since
release of v2.0:
- saving data files with automatic naming
- odds ratios in stratified tables with more than two strata
- memory leaks.
Plan for current testversion:
1. Leave on testing.php page for a few days (3-4 days)
2. Move as current release on the general download page.
The reason for putting on the test page is that the memory leak cleanout
could have introduced problems with menus and screen handling, which
cannot be tested here. Memory demand after running many commands could
before rise to more than e.g. 200Mb is now down to around 15-20 Mb.
Since release of v2.0 the test suite applied has been extended from 1749
tests to 1884 tests. The extension includes aspects such as further
sorting and stratified results for a combination of variables and files.
Please test as indicated and report here if you find problems
Regards
Jens Lauritsen
EpiData Association
------------------------------
________________________________________
EpiData-list(a)lists.umanitoba.ca
http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 49, Issue 11
********************************************
I just uploaded v2.0.1.128 on the page: www.epidata.dk/testing.php
This build remedies as far as we can test here the problems shown since
release of v2.0:
- saving data files with automatic naming
- odds ratios in stratified tables with more than two strata
- memory leaks.
Plan for current testversion:
1. Leave on testing.php page for a few days (3-4 days)
2. Move as current release on the general download page.
The reason for putting on the test page is that the memory leak cleanout
could have introduced problems with menus and screen handling, which
cannot be tested here. Memory demand after running many commands could
before rise to more than e.g. 200Mb is now down to around 15-20 Mb.
Since release of v2.0 the test suite applied has been extended from 1749
tests to 1884 tests. The extension includes aspects such as further
sorting and stratified results for a combination of variables and files.
Please test as indicated and report here if you find problems
Regards
Jens Lauritsen
EpiData Association
I am hoping someone knows the answer to the following question:
I am trying to export a selection of records from an EpiData rec file
using version 3.1 to an Excel file, based on a date field. For instance,
to select all records earlier than the 14th of November 2007:
dategiven < "14/11/2007"
in the filter box, but this yields an error (not a boolean expression)
and the field dategiven is a <ddmmyyyy> field. I also tried without
quotes and using the date function, with and without the day, month,
year functions with the same result. I dare say there is a simple way to
do it, but I can't see it, so if anyone can help, I'd be most grateful.
Regards,
Neville
-----------------------------------------
**************************************************************************
The information contained in the EMail and any attachments is
confidential and intended solely and for the attention and use of
the named addressee(s). It may not be disclosed to any other person
without the express authority of the HPA, or the intended
recipient, or both. If you are not the intended recipient, you must
not disclose, copy, distribute or retain this message or any part
of it. This footnote also confirms that this EMail has been swept
for computer viruses, but please re-sweep any attachments before
opening or saving. HTTP://www.HPA.org.uk
**************************************************************************
In Build 122 the following 3 commands in a
pgm-file could be executed correctly.
close
read "c:\data\tz\test1.rec"
append "c:\data\tz\test2.rec"
In build 126 and 127 the You get a error "Invalid
variable name C:\Data ....." when running the
pgm-file. But if You execute each command
separately the APPEND command works.as You can se from the following output.
. read
Loading data C:\Data\TZ\Test1.rec, please wait..
File name : C:\Data\TZ\Test1.rec
Fields: 3 Total records: 6 Included: 6
. append
Append rewritten - check result
Loading data C:\Data\TZ\Test2.rec, please wait..
. list
RecNo x y z
1 1 2 3
2 3 2 1
3 4 5 6
4 6 5 4
5 7 8 9
6 9 8 7
7 12 . .
8 13 . .
9 14 . .
10 15 . .
Note browse is faster than list
. run
. close
File closed
. read "C:\Data\TZ\Test1.rec"
Loading data C:\Data\TZ\Test1.rec, please wait..
File name : C:\Data\TZ\Test1.rec
Fields: 3 Total records: 6 Included: 6
. append "C:\Data\TZ\test2.rec"
invalid variable name C:\Data\TZ\test2.rec
Operation aborted
------------------------------------------------------------------------
Stig Uhlin tel 090-786 60 71 Stig.Uhlin(a)umdac.umu.se
UMDAC 070-591 03 04
901 87 Umeå fax 090-786 67 62
Jag jobbar numera 1/2 tid enl följande:
jämna veckor onsdag-fredag
udda veckor måndag-tisdag
------------------------------------------------------------------------
I will be out of the office starting 11/10/2007 and will not return until
11/13/2007.
Regional offices are closed Monday November 12th. I would be happy to
respond to your e-mail upon my return.
Thank-you,
Alyshia
The reported problems in relation to b126 have all been solved.
In addition the following changes have been implemented:
dotplot : Now dots are symmetrical for each group
command prompt: At initiation the command prompt is empty (was "read"
before". For users wishing to get the "read" command without using a
mouse the shortest way is by pressing F4 (goto command prompt) followed
by "Up-Arrow" (shows the "read" command), followed by "Enter" (open file
dialog).
documentation: clarified. Still some of the extended help files could
have v1.0 description of options etc.
The download page now shows build and version next to the page, as well
as there is also a zip file available containing the setup file.
Thanks for reporting the problems.
Part of the problem of the /SD etc discussed was, that the release build
and a former test build had the same build number (b126) (by error),
such that users could think they were having the same version, but
actually did not.
regards
Jens Lauritsen
EpiData Association
The problem of the /sd option in relation to
tab ill cakes vanilla chocolate /oa /sd /ex
versus
tab ill cakes vanilla chocolate /oa /ex
is related to how boolean variables are sorted. Currently in the version
2.0 released there is a bug in sorting of boolean 2x2 variables.
The error will be fixed as soon as possible.
For numerical variables coded 1/0 or 2/1 there is no problem. The reason I
did not catch the boolean Y/N error is, that the tab command gives correct
estimates for boolean as well as numerical variables:
tab ill cakes vanilla chocolate /oa /ex
But if the user adds the sorting (as was needed earlier) :
tab ill cakes vanilla chocolate /oa /ex /sd
reveals the bug.
The way development is done is that before release a number of tests are
made, currently around 1250, e.g. after the mentioned tabulation 24 tests
were applied for the tabulation of oswego rr values with different options
(but not the /sd) option. The oswego rr test has now been extended to
cover this issue as well. (18 more tests). A given test can be like this
using result variables:
tab ill vanilla rolls /o
assert samenum(round($OR*100)/100,22.15)
assert samenum(round($ORLL*100)/100,5.22)
assert samenum(round($ORUL*100)/100,138.39)
assert samenum(round($OR1*100)/100,12.26)
assert samenum(round($ORLL1*100)/100,1.76)
assert samenum(round($ORUL1*100)/100,150.86)
assert samenum(round($OR2*100)/100,38.19)
assert samenum(round($ORLL2*100)/100,4.06)
assert samenum(round($ORUL2*100)/100,1983.85)
assert samenum(round($SumOR*100)/100,20.61)
assert samenum(round($SumORLL*100)/100,4.93)
assert samenum(round($SumORUL*100)/100,126.46)
The "hidden" bug arising by the sort option is a good example of why many
tests are needed, but I think also that it shows that even with a number
of test releases the policy of "silent release" is appropriate.
regards
--
Jens Lauritsen
Coordinator and initiator of EpiData Project
http://www.epidata.dk