- EpiData-list - University of Manitoba Mailing Lists

Fonts and backgrounds Epidata Analysis ver 0.9.0.0
by EpiData development and support 13 Dec '17

13 Dec '17

Dear Jens,Separate selection of Fonts in the Output, Command line and Editor isvery good feature. One can read rec file but cannot relate with other rec file.Merge command is not working with parent child rec files.Please retain the feature of choosing the background as black and white(as it was in Classical Epidata Analysis). Otherwise this feaure should change with  Windows colour scheme selection. Only white background results in lot of glare.Startup.pgm could not be located. It is faster than classical epidata analysis.It can read large data sets (more than 35,000) easily. Keep it up.With regards,Dr. Shavinder

1 2

New test release of EpiData Analysis v0.9.0.0 (experimental)
by EpiData development and support 11 Dec '17

11 Dec '17

Dear all users A test version of the new EpiData Analysis was released today. Get it from: Http://www.epidata.dk/testing.php All data management and check of data should now be ready and work similarly in EntryClient, Manager and New Analysis, e.g. help menu. Data management includes: Reading of files (rec, epx, stata, csv, clipboard), creation of new variables, labels, browsing, check data command, saving data in files (epx, stata, csv, copy to clipboard from browser), but also running pgm files with comprehensive loops etc. But since it is in development: MAKE SURE YOU WORK ON COPIES OF REAL DATA Extract the appropriate files (depending on Windows, Linux, Mac version) and make sure you maintain the folder structure. Then start epidataanalysis. The main changes since October 13th (v0.8.4.0) are: * Now all three Operating Systems are supported (Linux, Mac, Windows). * Hit F1 to get automatic search based on content (command line or editor) * observation identifier may be used, e.g. : new var id i := _n; * observations can be checked with the [_n] reference, e.g.: v1:= v1[_n-2] ; (add [_n] with alt+n in the editor or command line) * Browser shows a snapshot of data and you may open several browsers (after browse - use right click to copy or adapt data). * Complex formulations of command syntax allowed (References to variables, loops, expansions of variable names) * Font control (all windows) and custom startup.pgm for preferences * More set options to change aspects of the interface. Faster output. * Recent files are shared with Manager and EntryClient. * More commands, functions and options are added (Hit F1 to see these) example: erase "tempfile.epx" If you have not used the new analysis before, please start the software and look in the help menu (Tutorials local), where you find more explanatory files, including how to adapt old pgm files for the new syntax. To see more aspects, please see the mail from announcement of version (0.8.4.0) (http://lists.umanitoba.ca/pipermail/epidata-list/2017q4/002815.html) If problems arise please report to this list. But make sure you WORK on COPIES OF DATA until we have the first public release. It is of particular interest for us if you can challenge creation and modification of projects (epx files) with subsequent addition of data in EntryClient and view or change of structure in Manager. Our internal standard is about 500 automatic tests, but we cannot test how saved epx files work in EntryClient and Manager automatically. Best wishes Jens Lauritsen and Torsten Christiansen EpiData Association, Denmark The main changes to the command syntax are: 1. use ; at the end of each command in a pgm file 2. use := to give variables a new content . e.g. v1 := 10; 3. options are indicated with ! instead of /, e.g. freq v1 !cum ; means age !t; 4. filenames must contain extension, and enclosed in "projectmain.epx". 5. Similar aspects are grouped, e.g. list data; list variables; list datasets 6. Defining and editing variables have a common structure: new var; edit var; drop var; 7. Many additions allow comprehensive programming

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 166, Issue 1
by EpiData development and support 03 Dec '17

03 Dec '17

Dear Jens and team This is fantastic news Awaiting the stable version soon! sincerely Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca <epidata-list-bounces(a)lists.umanitoba.ca> on behalf of epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Sent: Saturday, December 2, 2017 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 166, 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. New test release of EpiData Analysis v0.9.0.0 (experimental) (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 2 Dec 2017 01:01:18 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] New test release of EpiData Analysis v0.9.0.0 (experimental) Message-ID: <6dd70abc-84a1-bf22-aee6-104f0694f7c1(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Dear all users A test version of the new EpiData Analysis was released today. Get it from:? Http://www.epidata.dk/testing.php All data management and check of data should now be ready and work similarly in EntryClient, Manager and New Analysis, e.g. help menu. Data management includes: Reading of files (rec, epx, stata, csv, clipboard), creation of new variables, labels, browsing, check data command, saving data in files (epx, stata, csv, copy to clipboard from browser), but also running pgm files with comprehensive loops etc. But since it is in development: MAKE SURE YOU WORK ON COPIES OF REAL DATA Extract the appropriate files (depending on Windows, Linux, Mac version) and make sure you maintain the folder structure. Then start epidataanalysis. The main changes since October 13th (v0.8.4.0) are: * Now all three Operating Systems are supported (Linux, Mac, Windows). * Hit F1 to get automatic search based on content (command line or editor) * observation identifier may be used, e.g. : new var id i := _n; * observations can be checked with the [_n] reference, e.g.: v1:= v1[_n-2] ; ?? (add [_n] with alt+n in the editor or command line) * Browser shows a snapshot of data and you may open several browsers ??? (after browse - use right click to copy or adapt data). * Complex formulations of command syntax allowed (References to variables, loops, expansions of variable names) * Font control (all windows) and custom startup.pgm for preferences * More set options to change aspects of the interface. Faster output. * Recent files are shared with Manager and EntryClient. * More commands, functions and options are added (Hit F1 to see these) ?? example: erase "tempfile.epx" If you have not used the new analysis before, please start the software and look in the help menu (Tutorials local), where you find more explanatory files, including how to adapt old pgm files for the new syntax. To see more aspects, please see the mail from announcement of version (0.8.4.0) (http://lists.umanitoba.ca/pipermail/epidata-list/2017q4/002815.html) If problems arise please report to this list. But make sure you WORK on COPIES OF DATA until we have the first public release. It is of particular interest for us if you can challenge creation and modification of projects (epx files) with subsequent addition of data in EntryClient and view or change of structure in Manager. Our internal standard is about 500 automatic tests, but we cannot test how saved epx files work in EntryClient and Manager automatically. Best wishes Jens Lauritsen and Torsten Christiansen EpiData Association, Denmark The main changes to the command syntax are: ? 1. use ; at the end of each command in a pgm file ? 2. use := to give variables a new content????? . e.g. v1 := 10; ? 3. options are indicated with ! instead of /,? e.g. freq v1 !cum ; means age !t; ? 4. filenames must contain extension, and enclosed in "projectmain.epx". ? 5. Similar aspects are grouped, e.g. list data; list variables; list datasets ? 6. Defining and editing variables have a common structure: new var; edit var; drop var; ? 7. Many additions allow comprehensive programming ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 166, Issue 1 ********************************************

1 0

Mulitple Diagnosis
by EpiData development and support 26 Nov '17

26 Nov '17

Dear Jens and Jammy ,First example quantifies the total number of diagnosis which can besorted in descending order to see the magnitude.Second example actually adds all diagnosis in one defined variable (AllDiag).This can again be sorted in descending order (to see the magnitude) anddiagnosis grouping by sorting alphabetical. This data was actually entered inExcell sheet as numerically coded diagnosis. AllDiagnosis___________ resulted in sum of all the numberic data.Hence these codes were converted to actual diagnosis. This resulted inexcellent pattern of diagnostic combinations of all patients. Epidata Analysisis a marvellous software.Thank you for your prompt response and sustained effort to develop Epidata.Much appriciated.Dr Shavinder Singh

1 0

Multiple Diagnosis
by EpiData development and support 25 Nov '17

25 Nov '17

Dear Epidata Team,                   We have a patient's database. A patient can have multiplediagnosis. Hence these are the numerically coded variables defined for dataentry of ;Diag, Diag2, Diag3, Diag4, Diag5, Diag6. Of course one can FREQ theIndividual "diag" and see the individual diagnosis pattern. However if onewants to see the pattern of common diagnostic combinations observed inall the patients, is there any way out?  Dr. Shavinder Singh

1 3

Sorry for these extra characters in the post
by EpiData development and support 25 Nov '17

25 Nov '17

Dear Epidata Team,I aplogize for these strange extra characters appearing in the text file.This has been happening since last four posts to the list. I have sent thetext file this time. I cannot pin point the reason why this is happening.Please ignore these characters.Dr. Shavinder

1 0

EpiData EntryClient and Manager error: Control `DataviewerFrame’ has no parent window
by EpiData development and support 06 Nov '17

06 Nov '17

Hello: We (my admin and I) created a data base in EpiData Manager. Data has been entered. When I press Ctrl D, I can see the data entered nicely in column. I wanted to show my admin this functionality so that she can see how the data looks when entered. When we press Ctrl D (browse data) or use the menu on her computer we get this error (see below). Do you know how we could resolve this error: Control `DataviewerFrame’ has no parent window? IT has already uninstalled and installed both the Manager and the EntryClient. Any advice would be very much appreciated. [cid:image001.jpg@01D356DD.ADAB9260] Thanks, Renate

1 0

Re: [EpiData-list] Error in exporting .epx file to .dta
by EpiData development and support 24 Oct '17

24 Oct '17

The Stata versions we tried were 8, 9, 11 and 12 and SPSS version was 22. With regards to the query on whether to export the original missing values or as .a/.b, I feel it would be preferable to keep the original value. Thanks and Regards Dr. Divya Nair Assistant Professor | Dept. of Community Medicine Sri Venkateshwaraa Medical College Hospital & Research Centre Ariyur | Pondicherry 605 102. Mob: 8056748342 | Alternate email: divs87_nair(a)yahoo.co.in

1 0

Error in exporting .epx file to .dta
by EpiData development and support 23 Oct '17

23 Oct '17

Dear team members, I had entered data in an .epx file created using EpiData Manager v4.2.0.0 with jumps set for certain variables using the last defined and second last defined missing values. A unique identifier was also created for each record by combining two integer fields. On importing the data to stata for analysis, the following issues have been noted: 1. The unique id field remains empty in the stata file 2. Wherever, missing values were indicated in the .epx file, they appear as large random numbers in the stata file and not as the actual value that was entered. For example, age entered as 999 (missing) in the .epx file shows up as "32740" in the stata file. This happens only when the "missing" box is ticked while assigning value labels for categorical or continuous variables. This issue has been noted in the previous versions of epidata manager as well as while exporting to newer versions of stata and SPSS. I have attached the sample .epx file and the .dta file for your reference. Thanks and Regards Dr. Divya Nair

1 3

Re: [EpiData-list] EpiData-list Digest, Vol 164, Issue 2
by EpiData development and support 23 Oct '17

23 Oct '17

Thank you for the new version (0.804.0) od Epidata Analysis Two questions : - Is the command "Tables var1 var2" available ? - In the command "freq", spontaneously I would say that the percentages are in column (!c), and not in row (!r) Thanks for your activity. Bernard BRANGER 11 bis, rue Gabriel LUNEAU 44000 NANTES - FRANCE Mobile 06 32 70 33 80 Courriel : branger-bono(a)wanadoo.fr

1 0