EpiData-list December 2017

epidata-list@lists.umanitoba.ca

1 participants
6 discussions

by EpiData development and support

Dear Jens,I have tested the recent experimental versionEpidataAnalysis0.9.1.5. (Windows version)GOOD PREGRESS -Colour commands for output and command lineis welcome addition. Please add similar commands for Editor also.As mentioned earlier, EpidataAnalysis0.9.1.5. is really fast. It canread files with more than 1,00,000 records easily.ISSUES REQUIRING ATTENTION -MERGE Command was tetsed with following PGM.Patient and visit epx files were used  from course of https://tbrieder.org/epidata/epidata.html//TRY.PGMcd "D:\EpidataAnalysis0.9.1.5\EX";close;read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";merge idpat !fn := "d_ex01_patient" !table;save "combined10.epx" !replace;close;read "combined10.epx";  When this PGM is run it gets stuck at Merge Command. Following outputis obtained..cd "D:\EpidataAnalysis0.9.1.5\EX";D:\EpidataAnalysis0.9.1.5\EX.close;Project Closed!.read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";Loaded file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epxCycle: 10 Datasets: 1 Modified: 10-11-2016 21:34:21.merge idpat !fn := "d_ex01_patient" !table;ERROR: Unable to open the file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patientFile is corrupt or does not exist.Unable to open file "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patient"ERROR: Error loading file:Same problem I was facing with my relational database files.Hence this command needs revision..........................When rec file is read in this software, the variables and data entered do not tally.Conversion from rec file to epx file results in variable with actual data appearingunder other variables..........................Since there is no check file, Hans suggested following commandedit var sex !valuelabel := label_sex              !label := "Examinee's sex";This command (edit) is also not working.It is hard work to write such software. Surely these issues will be addressedin future releases. Keep it up.I wish you and epidata team all success and happy new year 2018.With regards,Dr. Shavinder 

5 years, 9 months

New experimental Analysis for testing released - v0.9.0.15

by EpiData development and support

Dear all users We have released next experimental version for testing, which you may find from the page: Http://www.epidata.dk/testing.php Many issues have been fixed since the latest public test in early december. A complete list is found at the bottom. In particular we have fixed and quality assured the data integrity command: check data, check key, check relate But also many other issues, e.g. colour control. These lines will turn output and command line into yellow on black background. set "COMMANDLINE BG COLOUR" := "#000000"; set "COMMANDLINE FONT COLOUR" := "#FFF000"; set "OUTPUT BG COLOUR" := "#000000"; set "OUTPUT FONT COLOUR" := "#FFF000"; Many other aspects have been fixed, e.g. search and replace in editor in windows. Next in line is the implementation of tables command and a few more issues in relation to data-management, which will then be announced as a pre-public version. Please do some testing in particular of saving files after changes to variables and structures, followed by entry in EntryClient and report to the list of your experiences. Best wishes for the coming end of year festivitas and a merry christmas for those who celebrate the christmas traditions. Jens Lauritsen and Torsten Christiansen EpiData Association Denmark. Complete list: * Removed the result variable $SYSTEMDIR and replaced with the function cwd() * Editor "open file" now opens in current directory * Options may now be a global that holds other options: - new global OPT s := "!cum !d0" - freq sex !OPT // this will effectively act as freq sex !cum !d0 * Fixed a number of bugs in "check relate" and "check key" * Added additional result variables to "check relate" and "check key" * Fixed bugs in relation to names already used in sections/headings * Editor: Inserting history/set-options * "list var" and variable information (F3) now shows variables that are part of key with a "*" * Added sub-command "edit data" with option !del -> marks all record in current select for deletion * Added command "report users" * Added option !del to "browse" and "list data" to show ONLY records marked for deletion * Browser: Added shortcut "CTRL + G" which shows a dialog for jump to observation * Added SET OPTIONS for COLOUR control og OUTPUT, COMMANDLINE and Browser * Added option !output [:= "html | text"] to "save" command. This saves the output buffer to text or html. * And many minor bug fixes.

5 years, 9 months

Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)

by EpiData development and support

Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label := "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder 

5 years, 9 months

Fonts and backgrounds Epidata Analysis ver 0.9.0.0

by EpiData development and support

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

5 years, 9 months

New test release of EpiData Analysis v0.9.0.0 (experimental)

by EpiData development and support

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

5 years, 9 months

Re: [EpiData-list] EpiData-list Digest, Vol 166, Issue 1

by EpiData development and support

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 ********************************************

5 years, 10 months

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list December 2017