July 2017 - EpiData-list - University of Manitoba Mailing Lists

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

2 3

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

I'm studying the copydata example to learn how to extract several variables from a file identified in a COMMENT LEGAL statement. In A3.chk, the statement "TYPE COMMENT atransfer" appears. What is atransfer? I don't see where it has been defined as a variable and I don't find it as a system variable. Further, the program seems to be parsing the string in atransfer according to the position of punctuation. Where is the format of this string defined? Perhaps to be a bit more explicit: I have file with a list of CHWs: District, Village, CHW name and a survey conducted by the CHWs. As the data is entered for the survey, I'd like to present pick lists to facilitate entry. The data is quite strictly hierarchical: Villages occur within Districts, an CHWs live in villages. Thank you,

2 3

Reg Epidata Manager 4.0.2.101
by EpiData development and support 03 Aug '17

03 Aug '17

This is a very basic question. 1) I am not able to automatically calculate the number of hours from the calculate option. I have input date and time and entered it into the calculate option but it is not giving me the correct answer. e.g. I have input date of injury and time of injury; and date of presentation and time of presentation. I need to calculate the number of hours of delay in presentation. I am not able to do that. 2) Is it possible to change the time option and exclude the seconds? Thank you, With regards, Madhurita

1 3

error message
by EpiData development and support 21 Jul '17

21 Jul '17

Dear all When comparing two datasets with Epidata Manager (double entry) I receive the error: "index out of bounds 108". Does somebody know what this means? Thank you very much, Nicole Dr. med. Nicole Bender Senior Research Fellow Evolutionary Morphology and Adaptation Group Institute of Evolutionary Medicine (IEM) University of Zurich Winterthurerstrasse 190 CH-8057 Zurich, Switzerland Office Y42 G86b Phone +41 44 635 05 31, Fax: +41 44 635 57 02 nicole.bender(a)iem.uzh.ch http://www.iem.uzh.ch/en/people/admin/Nicole-Bender.html

1 4

Read and Merge “rec” file commands and few suggestions in New Epidata Analysis (0.7.3.0)
by EpiData development and support 09 Jul '17

09 Jul '17

Dear Jens,                                     It is heartening to see the Epidata Analysis development progressing. Our favourite “qes/chk/rec” file  systm  seems fading  on the horizon. Our old applications are still functional in Classic Epidata Entry. It is comparatively easy to upgrade to the new”epx” file if one is using the FLAT file. However, the relational “rec” files cannot be upgraded to the new  ”epx” file. There was a line written in the mail that  one can read “rec” file but not write it in the new Epidata Analysis. Hence I request you to kindly preserve the read and merge (rec files) commands in the new Epidata Analysis.The Command and Function Reference Guide 2.1 is fairly exhaustive. Command “Merge” is perhaps not introduced in the prototype version, hence not mentioned in the Command and Function Reference Guide.It is possible to generate by the available Graphics in the Epidata Analysis ver 2.2.3 (build 187) by command syntax  generated by using  “Diaglogue boxes”.  Available options in the graphical output are excellent. However some tweaking is still required to get the final graph. PGMs is a wonderful feature with infinite possibilities. Gratitude to Epidata team for the sustained effort .With regards,Dr.  Shavinder Singh 

1 0

Test version of new EpiData Analysis released (v0.7.0.3) - please assist in testing.
by EpiData development and support 08 Jul '17

08 Jul '17

Exciting News Today we have released a test version of the rewritten analysis, which for the first time approaches functionality resembling the final first version to be released later. You may download the test version from http://www.epidata.dk/testing.php Please notice that it is still premature to use the new analysis for production every day use, but we urge users to challenge the new analysis. You could for instance replicate data-management procedures you do with ordinary Classic Analysis v2.2. rel 3 (Build 187) The intention is to release the new analysis for production when the following has been developed: A: all functionality for data management (new projects, new variables, labels and editing of these). B: append and merge. C: basic reporting - e.g. for logfile overview Already now you may test many of these aspects. After download and unzipping (files are provided in zipped archives) you will see the commands and syntax documentation. We attempt to maintain the same syntax that you know, but to allow for the modernization some changes are needed: e.g. read and write epx, csv and dta files ; work on all operating systems (Linux, Mac, Windows) ; accept UTF-8; extend with special functions; sort data; manage encrypted data. You can read rec files, but not write them. Use epx for saving data. We also aim for standardization across commands. E.g. number of decimals in output is always !Dx, where x is the number of decimals 0,1,2 etc. For data analysis these commands are implemented: count , means, freq, Some changes: use := instead of = . Put texts in " " . End all command lines with ;. Selection works on a single block. Options are mentioned with ! instead of /. Some enhancements: A copy of all executed commands is saved (commandlog.pgm). Recent pgm in editor filelist. Multiple pgm sorting ascending and descending and more. See datasets (F2) in a project. Open encrypted files. A frequency table of v17: freq v17 !vl !cum ; // would show labels and values plus cumulative percentage. To do the same table among those younger than 40 with no decimals. select (age < 40) do freq v17 !vl !d0; To remove all observations with age above 68. Use the command drop: select (age> 68) do drop data; A new construct is a loop, e.g. : new global integer i ; for i:=1 to 5 do ? "This is a number counting: " + i ; Which can be used to show means or frequencies for subgroups of another variable: new global integer i ; for i:= 1 to 5 do select (area = i) do means age !by:=sex !t; Please challenge function within WHAT is already implemented. Also notice that output format is still rather crude. Rest assured more will come during autumn. But do remember that you should NOT use production data - work on copies of real data. Please also discuss function and problems on this list. Best wishes for fruitful testing Torsten Christiansen Jens Lauritsen EpiData Association, Denmark

1 1