- EpiData-list - University of Manitoba Mailing Lists

Field Length Issue
by epidata-list＠lists.umanitoba.ca 17 Jul '13

17 Jul '13

Hello, I am currently working to try to import data into SPSS. I created the .dat file with StatTransfer from the Stata-formatted file. Looking at the .sps file, it appears that one of my variables which should be 70 characters (and is specified as such in the EpiData Manager) contains only 1 character. I noticed this issue while rewriting the syntax to pull the data into SPSS. Our variables are embedded within the string variables (e.g., EPIVAR = 56 -> VAR1 = 5 VAR2 = 6). We used spaces as missing data. Could it be an issue with missing data? It shouldn't be, if the field is specified as 70 characters! How can this be? It is making me very anxious.

1 2

Scripting in Manager
by epidata-list＠lists.umanitoba.ca 15 Jul '13

15 Jul '13

Using: Test version EpiData Manager: v1.5.0.10 3 NOENTER fields: id1, length 5, integer id2, length 5, integer id3, length 5, string 1 MUSTENTER field serno, length 4, integer In the field serno I type in SCRIPT, AFTER ENTRY: id1 := serno; DEFINE id2Temp: integer; id2Temp := serno+1000; id2 := id2Temp; id3 := string(serno); Result in EpiData Entry Client: id1: correctly done id2: correctly done id3: nothing done (except a "." written into the field) I cannot get strings working, neither from string to string nor (as above) trying to transform an integer to a string. I tried different ways, nothing worked. Consulting the Wiki was not revelatory. Dates constructed from date components (with 1 or more components set to missing, and then making approximations) also work impeccably. Floats not yet tested. -- 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

1 0

Can I "tell" RELATE how many children records to create for a specific household
by epidata-list＠lists.umanitoba.ca 14 Jul '13

14 Jul '13

I have a household survey that asks the head of the household several general questions and then also interviews all women of reproductive age within that household. The number of eligible women can thus range from 0 to several. Is there a way in Epi Data to essentially tell the program that there will be 2 women's records for household A and 3 womens records in household B, and so on. I remember in Epi Info (dos) we could specify the number of "children" records in the KEY UNIQUE field (if I put a "2" on that line then after 2 "childrens' records were created then Epi would bounce back to the main rec file. Thanks for any suggestions. Conrad

1 1

PS to: Experimental Manager and Entry Client version with before/after entry scripts available
by epidata-list＠lists.umanitoba.ca 10 Jul '13

10 Jul '13

Excuses, I managed to send the former mail too early: The EntryClient should be version: Program Version: 1.5.0.10 r292 But there are as well versions for Linux, Mac and Windows. Please experiment with these new principles and report. The release of the experimental script version and the former announced public version release: 1.4.2 also indicates a break in development from now until beginning of September 2013. But please keep discussing and asking questions on this list as they will be collected and handled - if serious also fixed before September. The script language is explained here: Wiki: http://epidata.info/dokuwiki/doku.php?id=techdocs:scripting:start A few aspects are still not on the wiki, but will come within some days, e.g. the function now() returns the time at the point of invoking the function. Could be used e.g. to record the starting time of entering data into a new record. Other functions are also on the way such as IsNewRecord() - which will test if the current record has been saved. But please note that this in the experimental section, such that for specific names of functions always look in the wiki if a given function does not work or is not found. Regards Jens Lauritsen EpiData Association

1 2

SV: Re: [EpiData-list] PS to: Experimental Manager and Entry Client version with before/after entry scripts available
by epidata-list＠lists.umanitoba.ca 06 Jul '13

06 Jul '13

Dear Jean-Marie. We have deliberately chosen to make the programs behave the way it does, concerning the mouse. The reason behind this, is that in most scenarios a user creates a database, based on a questionnaire. This questionnaire has a well defined flow (usually top-left to bottom-right), perhaps with some diversion, eg. skipping some fields if it makes no sense to enter based on previous values. This flow is the same we wish to keep in Manager and EntryClient. And if a user the have to use the mouse, this is typically because an error has been made. Hence the use needs to exit the current field, without any validation is done and script is run. This was actually a flaw in the old EpiData Entry program, where the flow was not well defined. That is, if a user clicked with the mouse the behaviour could lead to an error or even worse some undefined state. Kind regards, Torsten Bonde Christiansen. EpiData Association. Sendt fra min Xperia™-tablet-pc epidata-list(a)lists.umanitoba.ca skrev: >Hello, > >THANKS, This new functionnality is really very exciting! >I made some tests and it's very easy to use. > >A great improvment would be the activation of "before entry" and "after >entry" action when the next field is directly selected using the mouse. > >In modern UI, users tend to navigate from field to field using the mouse >instead using the keyboard. Thus scripts are not fired if users use the >mouse and it breaks the logic behind the scripts. > >Best regards > >Jean-Marie Chrétien >CHU d'Angers - DRCI >Cellule Méthodo/Biostat/Data >Maison de la Recherche >4 rue Larrey >49933 ANGERS Cedex 9 > > > >2013/7/5 <epidata-list(a)lists.umanitoba.ca> > >> Excuses, I managed to send the former mail too early: >> >> The EntryClient should be version: Program Version: 1.5.0.10 r292 >> But there are as well versions for Linux, Mac and Windows. >> >> Please experiment with these new principles and report. >> >> The release of the experimental script version and the former announced >> public version release: 1.4.2 also indicates a break in development from >> now until beginning of September 2013. >> >> But please keep discussing and asking questions on this list as they will >> be collected and handled - if serious also fixed before September. >> >> The script language is explained here: >> >> Wiki: >> http://epidata.info/dokuwiki/**doku.php?id=techdocs:**scripting:start<http://epidata.info/dokuwiki/doku.php?id=techdocs:scripting:start> >> >> A few aspects are still not on the wiki, but will come within some days, >> e.g. the function now() returns the time at the point of invoking the >> function. Could be used e.g. to record the starting time of entering data >> into a new record. Other functions are also on the way such as >> IsNewRecord() - which will test if the current record has been saved. But >> please note that this in the experimental section, such that for specific >> names of functions always look in the wiki if a given function does not >> work or is not found. >> >> Regards >> >> Jens Lauritsen >> EpiData Association >> >> >> ______________________________**_________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.**ca <EpiData-list(a)lists.umanitoba.ca> >> http://lists.umanitoba.ca/**mailman/listinfo/epidata-list<http://lists.umanitoba.ca/mailman/listinfo/epidata-list> >> >_______________________________________________ >EpiData-list mailing list >EpiData-list(a)lists.umanitoba.ca >http://lists.umanitoba.ca/mailman/listinfo/epidata-list

1 2

Epidata Analysis
by epidata-list＠lists.umanitoba.ca 06 Jul '13

06 Jul '13

Hello, For the last version of EPIDATA ANALYSIS (24 May 2013) : - the first veiwer screen is black (it changes after le first commands..) : why ? - in Help, I don't find for the tables command : /t, /c, /o, /r.. Why ? Ok I seen "set statistics="OR CHI...", but I have a message error. - Idem for epitables or etab command, I have a message error. Thank you for your help. Bernard BRANGER, Nantes, France PS : the new link for "Course Materials in Franch" is : http://www.reseau-naissance.fr/module-pagesetter-viewpub-tid-2-pid-28.html Thank you

1 4

Experimental Manager and Entry Client version with before/after entry scripts available
by epidata-list＠lists.umanitoba.ca 05 Jul '13

05 Jul '13

Whereas the former mail concerned the public production version, this mail is an exciting additional feature to be tested by users. Assume you have a special situation where you need to do a particular calculation to show the entry person, e.g. calculation of BMI or the summation of 10 items for an index. With the experimental version now available from: http://www.epidata.dk/testing.php You can create such scripts. Attached is an example file using integers. Example script is: if V1 = 4 then goto V3 missing else if V1 = 3 then goto V3 clear; Another example: V4 := V1 + V2 + V3 ; V5 := V1*V2*V3; Notice that the way the syntax is written resembles pascal, which is a deliberate choice. We have tried a few other variants, including R, but too many problems were created at the implementation. The syntax is intended to be implemented in exactly the same way later in Analysis, once this software has also been rewritten. Quite many functions are already implemented. These are explained on the wiki page: Users are encouraged to work over the next months challenging the scripting engine. And discuss on this list if the new scripting engine is too experimental or of actual use. To write a script: 1 add a field in Manager version : Program Version: 1.5.0.10 r684 2 hightligh that field and hit Enter button 3 on the tab pages of the properties of the field you will see a tab page next to "notes" saying script. this is where you write your scripts. 4 then save the file and open in EntryClient which MUST be the experimental version as well: EpiData Entry Client Program Version: 1.5.0.10 r292 Core version: 1.5 r767 FPC Version: 2.6.2 Platform: x86_64-Linux

1 0

EpiData Manager and EntryClient updated to v1.4.2
by epidata-list＠lists.umanitoba.ca 05 Jul '13

05 Jul '13

The following has been updated: New functionality in Manager: Expand current Dataform, - shown on the toolbar with two triangles pointing downwards. This will add blank space at the bottom of the dataform- A tecx indicator is shown. When you save the file the indicator is NOT saved. EntryClient and Manager: * Added commandline options -i, -r, -h and -v * Added commandline options -i, -r, -h and -v Which allows to specify inifile, recentfile, help and version. One use of this would be to use separate recentfiles for experimental and runtime latest public version. A bug in Manager in relation to copy structure for double entry and another in relation to copy/paste has been fixed. Users should be aware that on export to SPSS, SAS etc there can be difficulties in creating systemfiles in these softwares, since EpiData Manager and EntryClient now base all text on the UTF-8 principles. Later some recipies will be added on "how-to" manage this. The version mentioned above is available from the general "production" page: Http://www.epidata.dk/download.php A separate mail will follow regarding a new experimental version - which can run scripts before and or after entry. regards Jens Lauritsen Torsten Christiansen EpiData Association

1 0

Copy Structure (EpiData 3.02)
by epidata-list＠lists.umanitoba.ca 26 Jun '13

26 Jun '13

Dear users, As I attempted to copy structure on an existing file in the dialogue box "Copy file structure" the options check box for "copy *c*heck file" is not accessible. What could be the problem? Omala

1 0

Copy Structure(EpiData 3.02).
by epidata-list＠lists.umanitoba.ca 26 Jun '13

26 Jun '13

Dear users, As I attempted to copy structure on an existing file in the dialogue box "Copy file structure" the options check box for "copy *c*heck file" is not accessible. What could be the problem? Omala On 13 June 2013 20:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Bug on import in Manager (public release 1.4.1.0) > (epidata-list(a)lists.umanitoba.ca) > 2. How to count the number of missing values in an > observation/record/row (epidata-list(a)lists.umanitoba.ca) > 3. Re: How to count the number of missing values in an > observation/record/row (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 13 Jun 2013 08:05:33 GMT > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Bug on import in Manager (public release > 1.4.1.0) > To: <epidata-list(a)lists.umanitoba.ca> > Message-ID: <1371110733382.14178.2158@webmail02> > Content-Type: text/plain; charset=UTF-8 > > We have found a bug in the most recent public release version of EpiData > Manager 1.4.1.0. > > With the bug import of epx and other files into a project with "renaming" > of value label sets gives an error. This will be fixed and a new version > uploaded within short time. (days) > > This is only relevant for the situation where you add files depending on > naming of value label sets. > > If other bugs have been identified please report, such that we can fix > these as well. > > regards > > Jens Lauritsen > EpiData Association > > > > ------------------------------ > > Message: 2 > Date: Thu, 13 Jun 2013 14:39:48 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] How to count the number of missing values in > an observation/record/row > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAPLSYrXc_P9+LsC0wDO0Yvm1WCAfpYuLhOP+5c1O-JkfNSNtKA(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear sirs/madams, > > My name is Anh. I am a student from Vietnam. I would like to calculate the > number of missing values/entered values in a record. > > I had a look at Epidata manual but I could not find any relevant > instructions. Could you please help me with this problem? > > Thank you so much, > > Anh Dang > > ........................................................ > > Details of my problem: > > My checklist contains 5 variables. Each variable is given a score (0,1,2), > but in some records, a few variables are left blank because they are not > relevant. The final score is calculated by dividing the sum of score of > each variable (don't take the missing into account) by the 'total number of > entered variables'. > id var1 var2 var3 var4 var5 > 1 2 1 1 0 final score = > (2+1+1+0)/4 ( I use the command 'ignoremissing' to get the sum) > 2 2 2 2 1 1 final score = > (2+2+2+1+1)/5 > 3 1 1 final score=(1+1)/2 > > > ------------------------------ > > Message: 3 > Date: Thu, 13 Jun 2013 08:44:26 -0400 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] How to count the number of missing values > in an observation/record/row > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <BLU0-SMTP795C0548F993B63377ADD1FD870(a)phx.gbl> > Content-Type: text/plain; charset="us-ascii" > > I assume you are doing this in Analysis. The solution is similar for a > .chk file, but the syntax is different. It is also a bit tricky doing this > in a .chk file because values can be changed after the calculation is done > if you are not careful. > > * c is count of non-missing variables > * s is sum of non-missing variables > * score is final score (average of non-missing variables) > > gen c=0 > gen s=0 > if var1 <> . then c=c+1 > if var1 <> . then s=s+var1 > if var2 <> . then c=c+1 > if var2 <> . then s=s+var2 > if var3 <> . then c=c+1 > if var3 <> . then s=s+var3 > if var4 <> . then c=c+1 > if var4 <> . then s=s+var4 > if var5 <> . then c=c+1 > if var5 <> . then s=s+var5 > gen score = s/c > > if you do not have any defined missing values, you can also calculate c > this way: > > c = 5-mv(var1)-mv(var2)-mv(var3)-mv(var4)-mv(var5) > > and you can also calculate s this way: > > s=iif(var1<>. , var1,0)+iif(var2<>. , var2,0)+iif(var3<>. , > var3,0)+iif(var4<>. , var4,0)+iif(var5<>. , var5,0) > > Check the help for these functions to see how they work: mv() and iif() > > Jamie > > On 2013-06-13, at 3:39 AM, epidata-list(a)lists.umanitoba.ca wrote: > > > > > Details of my problem: > > > > My checklist contains 5 variables. Each variable is given a score > (0,1,2), > > but in some records, a few variables are left blank because they are not > > relevant. The final score is calculated by dividing the sum of score of > > each variable (don't take the missing into account) by the 'total number > of > > entered variables'. > > id var1 var2 var3 var4 var5 > > 1 2 1 1 0 final score = > > (2+1+1+0)/4 ( I use the command 'ignoremissing' to get the sum) > > 2 2 2 2 1 1 final score = > > (2+2+2+1+1)/5 > > 3 1 1 final > score=(1+1)/2 > > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 116, Issue 3 > ******************************************** >

1 0