- EpiData-list - University of Manitoba Mailing Lists

New test versions and a warning on time and memo variables
by EpiData development and support 31 Dec '19

31 Dec '19

Dear all users of EpiData As quite many of you have already experienced, we have placed new test versions of EpiData EntryClient, Manager and Analysis on the http://epidata.dk/testing.php page on December 18th. The changes implemented in the test versions are documented in detail in the "change lists" found under each software on the "public release page, http://epidata.dk/download.php. Current public release versions are 4.6.0 for EntryClient and Manager and 1.4.0 for Analysis. As the the updated test versions are numbered: 4.6.0.2 for EntryClient and Manager and 1.6.0 for Analysis the major changes are in Analysis, where we are preparing for introduction of graphs and other lacking functionality. 1.6.0.0 of analysis * new command: Recode - very strong including formation of labels and other documentation * See Commands.html for details (press F1) of changes to options and the other new commands: keep and version * Variable list, History, Project overview and Command tree have been moved to seperate windows * Revised shortcuts and option names, e.g. unification of label as !l * !h option works for all commands and prints a simple list of supported options for a given command. * Table may be used for only one variable (with options for frequencies) And many Many minor bugfixes, mostly involving statistic calculation and special cases (eg. 0 data) If no major problems are identified the current "test versions" on the testing page will be "public release versions" in early January. Warning: As a side-effect of the new variable types (memo and time) variable, you should notice that if you want to read epx datafiles into classic analysis, then in the new analysis change those variables to another form, e.g. one or more string variables. At this end of our year I wish to express my thanks to all who supported EpiData Software over the years, including anonymous donors in the recent year, but also in particular the core group of Torsten Christiansen, Jamie Hockin and Hans L. Rieder. I wish all a happy new year and do hope that You will welcome the new and coming further structured development. Without all of your support and ideas the project could not continue. Best wishes Jens Lauritsen EpiData Association

1 0

NEUTRALZING A RECORD
by EpiData development and support 19 Dec '19

19 Dec '19

Dear all, How can you neutralize a record in a data set (duplicate or else)? In Epi-Info, you just needed to do F6 on the data sheet It should have a possibility with Epidata Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 18 Dec 2019 22:01:08 +0400 Subject: EpiData-list Digest, Vol 187, 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. 64-bit version / MacOS Catalina (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Dec 2019 07:11:00 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] 64-bit version / MacOS Catalina Message-ID: <trinity-9c54c698-20c3-48e6-a35f-c400c76e47b2-1576563060099@3c-app-webde-bap14> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: <http://lists.umanitoba.ca/pipermail/epidata-list/attachments/20191217/ca53a…> ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 187, Issue 1 ********************************************

1 2

News on software upgrades and EpiData software on Mac Catalina ?
by EpiData development and support 18 Dec '19

18 Dec '19

Dear all Within short time new "pre-public" versions of EpiData Software (Manager, EntryClient and Analysis) will appear on the testing.php page of EpiData. Apart from bug fixes the main upgrading is in Analysis. A dedicated mail will be posted once the updates are placed there. Another issue is that a few users have asked when EpiData software will be available for the MacOS Catalina. This is not to easy to answer since it seems that Apple has applied further special restrictions. In short we can guide you with this (unfortunated) message: Mac users of Epidata software should not upgrade their operating system to MacOS Catalina. Current Mac versions of Epidata will not run under this most recent version of MacOS because of restrictions Apple has put into the operating system. We are working on 64-bit Mac versions of the software that can be installed on MacOS Catalina and will advise users when these are ready. More news on this later when the tests are more extensive and time has permitted the development. Best wishes to all Jens Lauritsen EpiData Association Denmark

1 0

64-bit version / MacOS Catalina
by EpiData development and support 17 Dec '19

17 Dec '19

1 0

Unable to import .qes & .chk in iOS version?
by EpiData development and support 19 Nov '19

19 Nov '19

Dears, I work with local colleagues on TB mortality issues. I imported .rec from Windows version but can't for .chk and .qes Is this "normal", as mentionned in last thread related to iOS version of Epidata or do I miss something ? Thanks ! Gaël Claquin Tél Bénin: +229 99 00 37 17

1 1

Update of EpiData to work with MacOS Catalina
by EpiData development and support 18 Oct '19

18 Oct '19

Hi, When is an update for EpiData Manager and - Entry Client planned for it to work with MacOS Catalina? Current versions are incompatible. Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group ( https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 02 Sep '19

02 Sep '19

Dear, Hans Thank you for this solution, but my goal is not to use R for the statistics. I will be using Python for all my statistics and graphs. The error with the missing values is not a dealbraker as I can recode the values in Python. But I would rather not have to. Kind Regards Henning Langen Stokmo Twitter: @helangen Keybase: @helangen PGP fingerprint: 9C50 5F2D BDB7 F13A

1 0

Re: [EpiData-list] Missing data values when exporting to Stata (EpiData development and support)
by EpiData development and support 27 Aug '19

27 Aug '19

Hi, Exporting the .dta file from Analysis throws the same error in Python as the Stata 14-file from EpiData Manager. Unsure if this is a Python error or Stata-export error. I have used all versions earlier in R so probably something to do with Python Pandas read_stata-function. Kind Regards Henning

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 26 Aug '19

26 Aug '19

Hi, again I tried exporting to Stata v13 and v14 from EpiData Manager (same version av before), but Python throws an error when reading both files. Unsure what the errors are. I can’t find where to export in EpiData Analysis v1.4.0.0. I tried “File -> Save” as .dta, but the file is not a Stata-file. I tried looking in the documentation for an export command, but can’t find one. What am I missing? Kind Regards Henning

1 1

Re: [EpiData-list] Missing data values when exporting to Stata
by EpiData development and support 23 Aug '19

23 Aug '19

I will download the Analysis app and try that. I will also try to export to Stata 14 as the Stata version does not matter with regards to Python. Thanks Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Nuclear Medicine, Oslo University Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group (https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo Sent from Canary (https://canarymail.io/) > On Friday, Aug 23, 2019 at 7:00 PM, <epidata-list-request(a)lists.umanitoba.ca (mailto:epidata-list-request@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. Re: Missing data values when exporting to Stata > (EpiData development and support) > 2. Re: Missing data values when exporting to Stata > (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 22 Aug 2019 23:40:02 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Missing data values when exporting to > Stata > Message-ID: <041A2CAB-A14A-4F26-8389-3410D8489A76(a)gmail.com> > Content-Type: text/plain; charset=utf-8 > > Sorry for not giving any information about the versions and system I use. > > I use EpiData Manager v4.4.2.1 on a MacBook Pro 13? (2018) running Mojave 10.14.6 to export. The exported files are to Stata v12. > The .dta files are opened in Python v3.6.8 via PyCharm IDE CE 2019.2 and imported to a Panda dataframe with the command ?pd.read_stata(<filename>). The empty lines in the Stata-file gets correctly set as ?NaN? in Pandas, but the value label for the missing category is set to ?100.0? instead of ?NaN? as I expect it should be after coding this in EpiData. > > Kind Regards > Henning L. Stokmo > Phd-Student, Oslo University Hospital > > > > On 22 Aug 2019, at 19: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. Re: Missing data values when exporting to Stata > > (EpiData development and support) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Wed, 21 Aug 2019 21:43:41 +0200 > > From: EpiData development and support > > <epidata-list(a)lists.umanitoba.ca> > > To: epidata-list(a)lists.umanitoba.ca > > Subject: Re: [EpiData-list] Missing data values when exporting to > > Stata > > Message-ID: <CE3439F1-72F7-4F8A-90F1-313DF876BD64(a)epidata.dk> > > Content-Type: text/plain; charset=utf-8 > > > > As I remember the Stata value should be > > .a > > But please specify which version of Stata and if you are using Manager export or the new analysis, which may directly save the file in Stata format. > > > > Best wishes > > Jens Lauritsen > > EpiData Association > > Denmark > > > > Den 21. august 2019 14.04.31 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> skrev: > > > Hi, > > > > > > I have some missing data that is encoded as ?9? in the database and in > > > the value label list it is flagged as missing. When exporting to CSV > > > the value is obviously set as ?9? as expected. > > > > > > When I export it as Stata I assume this value ?9? gets encoded to > > > Stata? definition of a missing value, but when I read the data in > > > Python with the ?pd.read_stata?-function it defines the category value > > > ?9? as 100.0 and not as missing data (NaN) like the blanks in EpiData. > > > > > > Eksample > > > One column has 80 values. 19 of these are encoded as ?9? (missing), 58 > > > of these are blank, and 3 are coded as ?1? (Yes) in EpiData. After > > > exporting to Stata and reading in Python I get > > > > > > 19 values in category ?100? > > > 3 values in category ?Yes? > > > 58 values NaN (i.e. missing) > > > > > > Why aren?t the ?9? category correctly coded as missing when exporting > > > to Stata, or am I missing something here? > > > > > > Kind Regards > > > Henning > > > _______________________________________________ > > > EpiData-list mailing list > > > EpiData-list(a)lists.umanitoba.ca > > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > ------------------------------ > > > > ________________________________________ > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > End of EpiData-list Digest, Vol 183, Issue 2 > > ******************************************** > > > > ------------------------------ > > Message: 2 > Date: Fri, 23 Aug 2019 11:21:07 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Missing data values when exporting to > Stata > Message-ID: <C7C018D0-96BA-45C8-8AFF-7F9FC92D31AF(a)epidata.dk> > Content-Type: text/plain; charset=utf-8 > > You spotted an error in export to Stata 12. > > If you export to Stata 14 it works as desired. > > A easier way is to use the new Analysis for export, Analysis has options for choice of Stata version a d works on a Mac. > > Can the python use Stata 14? > > Best wishes > Jens Lauritsen > EpiData Association > Denmark > > > > > Den 22. august 2019 23.40.02 CEST, EpiData development and support <epidata-list(a)lists.umanitoba.ca> skrev: > > Sorry for not giving any information about the versions and system I > > use. > > > > I use EpiData Manager v4.4.2.1 on a MacBook Pro 13? (2018) running > > Mojave 10.14.6 to export. The exported files are to Stata v12. > > The .dta files are opened in Python v3.6.8 via PyCharm IDE CE 2019.2 > > and imported to a Panda dataframe with the command > > ?pd.read_stata(<filename>). The empty lines in the Stata-file gets > > correctly set as ?NaN? in Pandas, but the value label for the missing > > category is set to ?100.0? instead of ?NaN? as I expect it should be > > after coding this in EpiData. > > > > Kind Regards > > Henning L. Stokmo > > Phd-Student, Oslo University Hospital > > > > > > > On 22 Aug 2019, at 19: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. Re: Missing data values when exporting to Stata > > > (EpiData development and support) > > > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Wed, 21 Aug 2019 21:43:41 +0200 > > > From: EpiData development and support > > > <epidata-list(a)lists.umanitoba.ca> > > > To: epidata-list(a)lists.umanitoba.ca > > > Subject: Re: [EpiData-list] Missing data values when exporting to > > > Stata > > > Message-ID: <CE3439F1-72F7-4F8A-90F1-313DF876BD64(a)epidata.dk> > > > Content-Type: text/plain; charset=utf-8 > > > > > > As I remember the Stata value should be > > > .a > > > But please specify which version of Stata and if you are using > > Manager export or the new analysis, which may directly save the file in > > Stata format. > > > > > > Best wishes > > > Jens Lauritsen > > > EpiData Association > > > Denmark > > > > > > Den 21. august 2019 14.04.31 CEST, EpiData development and support > > <epidata-list(a)lists.umanitoba.ca> skrev: > > > > Hi, > > > > > > > > I have some missing data that is encoded as ?9? in the database and > > in > > > > the value label list it is flagged as missing. When exporting to CSV > > > > the value is obviously set as ?9? as expected. > > > > > > > > When I export it as Stata I assume this value ?9? gets encoded to > > > > Stata? definition of a missing value, but when I read the data in > > > > Python with the ?pd.read_stata?-function it defines the category > > value > > > > ?9? as 100.0 and not as missing data (NaN) like the blanks in > > EpiData. > > > > > > > > Eksample > > > > One column has 80 values. 19 of these are encoded as ?9? (missing), > > 58 > > > > of these are blank, and 3 are coded as ?1? (Yes) in EpiData. After > > > > exporting to Stata and reading in Python I get > > > > > > > > 19 values in category ?100? > > > > 3 values in category ?Yes? > > > > 58 values NaN (i.e. missing) > > > > > > > > Why aren?t the ?9? category correctly coded as missing when > > exporting > > > > to Stata, or am I missing something here? > > > > > > > > Kind Regards > > > > Henning > > > > _______________________________________________ > > > > EpiData-list mailing list > > > > EpiData-list(a)lists.umanitoba.ca > > > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > -- > > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > > > ------------------------------ > > > > > > ________________________________________ > > > EpiData-list(a)lists.umanitoba.ca > > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > > > > > > > End of EpiData-list Digest, Vol 183, Issue 2 > > > ******************************************** > > > > _______________________________________________ > > EpiData-list mailing list > > EpiData-list(a)lists.umanitoba.ca > > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 183, Issue 3 > ********************************************

1 0