- EpiData-list - University of Manitoba Mailing Lists

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

23 Aug '19

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

1 1

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

21 Aug '19

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

1 1

New versions available as pre-release. (Manager V4.6.0.0 , Entryclient V4.6.0.0, Analysis V1.4.0.0)
by EpiData development and support 16 May '19

16 May '19

Dear users New versions have been placed as "pre-release" on: http://epidata.dk/testing.php (Manager V4.6.0.0 , Entryclient V4.6.0.0, Analysis V1.4.0.0) You will find new commands e.g. compact tables in analysis and bugs removed. The major changes are in analysis. All changes will be documented in a few days - and at that point a new mail will be sent to all on this list. Please remember, that as long as the software is placed on the testing.php page DO NOT use on routine data. Make a copy of your data and test function with the new software. Best wishes Torsten Bonde Christiansen and Jens Lauritsen EpiData Association Denmark

1 2

Re: [EpiData-list] EpiData-list Digest, Vol 181, Issue 7
by EpiData development and support 28 Apr '19

28 Apr '19

THANK YOUUUU!!!!!!! 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: Sun, 28 Apr 2019 21:00:14 +0400 Subject: EpiData-list Digest, Vol 181, Issue 7 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: HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC? (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 27 Apr 2019 20:40:13 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC? Message-ID: <5c7a4cb2-0714-13d8-5b23-bfbbb9f03ca4(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Pierre-Yves: Explicitly, you would have - example - a data set that you read and manipulate in EpiData Analysis [classic] as follows: cls close read "original.rec" * Contains variables VAR01, VAR02, .... , VAR19, VAR20 * Has 1200 records * 1) Reduce number of variables * => keep only some variables to your choice: keep var01 var03 var05 var10 var11 var16 * if the converse gives less to write, use: * drop var02 var04 var06 var07 etc * 2) Reduce number of records [assuming sorted by your preference] * Select only the first 500 records: select recnumber<501 * Save the new data set: savedata "reduced_set.rec" /replace * Use the new set: cls close read "reduced_set.rec" * All this is in the superb help file which you get with F1 in EpiData Analysis V2.2.3.187 Best regards, Hans On Apr 26, 2019, at 01:55, EpiData development and support <epidata-list(a)lists.umanitoba.ca> wrote: >> Dear all, >> >> I need to create a smallest datafile to work on it for logistic regression >> In EPIINFO6 it was very easy. the command was: >> >> >> route c:\data\preclog.rec >> >> write recfile chgt multi capot diaf foam withdraw cream depo rythm pil iud \ >> >> precl \ >> >> >> >> For epidata it is logopen "c:\data\preclog.rec" >> >> but after, write recfile does nor work in Epidata >> >> What is the process please? >> >> Thanks >> >> Dr Pierre-Yves Robillard -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 181, Issue 7 ********************************************

1 0

HELP! HOW DO WE CREATE A SMALLEST DATAFIL.REC?
by EpiData development and support 27 Apr '19

27 Apr '19

Dear all, I need to create a smallest datafile to work on it for logistic regression In EPIINFO6 it was very easy. the command was: route c:\data\preclog.rec write recfile chgt multi capot diaf foam withdraw cream depo rythm pil iud \ precl \ For epidata it is logopen "c:\data\preclog.rec" but after, write recfile does nor work in Epidata What is the process please? 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: Fri, 12 Apr 2019 21:00:30 +0400 Subject: EpiData-list Digest, Vol 181, Issue 4 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: Problems appending files (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Apr 2019 19:09:30 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] Problems appending files Message-ID: <1c40e7a2-df66-7ec2-3a02-ec373ce19e14(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Omar Bautista: In the new analysis, this would be the grammar if you would wish to append the four files a.epx, b.epx, c.epx, d.epx and to sa ve them to a new file abcd.epx that you can then use henceforth: cls; read "a.epx"; append !fn := "b.epx"; append !fn := "c.epx"; append !fn := "d.epx"; save "abcd.epx" !replace; Best regards, Hans On 10-Apr-19 20:20, EpiData development and support wrote: > ?Thanks! Very well explained. > > I'm now exporting the data from EpiData using STATA format, on > separate files. And then handling some merge-append functions within > R. I will record the commands to run them as a little R script to make > it more automatic. At least, this is working. But it would be great, > in a near future, to learn how to solve this automatic id problem > within EpiData. > > Cheers, -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 181, Issue 4 ********************************************

1 3

Problems appending files
by EpiData development and support 11 Apr '19

11 Apr '19

Hello Jens and EpiData users! I trying to append some EpiData files. But I'm having a problem... I tried the same steps that are illustrated in this video: https://www.youtube.com/watch?v=BY6nZ0-k2Bs But I'm having an error that is shown in the attached file. Please, help me! -- Omar Bautista González Colaborador en autogestión comunitaria desde República Dominicana Docente de la Universidad Autónoma de Santo Domingo

1 7

Thank you for answer to: Is there a Road Map for the test version (V4.4.2.1) and other questions
by EpiData development and support 21 Mar '19

21 Mar '19

Dear Jens Lauritsen, I just want to thank you for your answers to all of our questions. We really appreciate it! Best regards, Leticia Grize Leticia Grize PhD Biostatistics Unit Department of Epidemiology and Public Health Swiss Tropical and Public Health Institute Office address: Eulerstrasse 77, Basel Phone: +41-(0)61-284-87-12 Fax: +41-(0)61-284-81-01 Email: leticia.grize(a)swisstph.ch Postal address: Swiss TPH / P.O. Box / CH-4002 Basel / Switzerland STPH website: http://www.Swisstph.ch -------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately by reply e-mail and delete this message from your system. --------------------------------------------------------------------------

1 0

Is there a Road Map for the test version (V4.4.2.1) and other questions
by EpiData development and support 20 Mar '19

20 Mar '19

Dear EpiData Association team / epidata-list, I work at a non-profit organization conducting studies in different parts of the world. Several of these studies at our institute are still using EpiData v3.1. At the moment all collaborators of our institute are being migrated from Windows 7 to Windows 10. Our IT department has included EpiData Manager V4.4.2.1 in the software package being installed in our new computers since it is the 'newest' version (a test version but not the current version!) . Since several studies are in the process of entering data using V3.1 we encountered the fact that the entry mask does not work on the newer version (as expected). Using V4.4.2.1 means for us the re-design of the masks, which we have tried but encounter difficulties with the part of the '.chk' e.g no conditional jumps can be applied and calculations can be cumbersome, etc... We would rather work with V3.1 but out IT department would like to know the following to go back to EpiData V3.1: 1.) Which is your 'Road Map' for the development of V4.4.2.1 from 'test' to a 'current' version? Would you have an estimate of the date of availability of the V4.4.2.1 as a current version? 2.) They asked if V3.1 was designed for Win 10, but I rather ask: are there known errors in the use of V3.1 when running under Win10? 3.) Would you have 'security' updates for V3.1? Since it is an old software, the IT team is refusing to install V3.1 because if could introduce 'insecurity' in the Institute's system. - If we were forced to use the test version, is there an easy way to implement the check files from V3.1? - Would you have a manual for the users? We are in the middle of several studies going on and we would like to have reassurance that things are done properly. I would really appreciate your help! Best regards and thank you, Leticia Grize Leticia Grize PhD Biostatistics Unit Department of Epidemiology and Public Health Swiss Tropical and Public Health Institute Office address: Eulerstrasse 77, Basel Phone: +41-(0)61-284-87-12 Fax: +41-(0)61-284-81-01 Email: leticia.grize(a)swisstph.ch Postal address: Swiss TPH / P.O. Box / CH-4002 Basel / Switzerland STPH website: http://www.Swisstph.ch -------------------------------------------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately by reply e-mail and delete this message from your system. --------------------------------------------------------------------------

1 1

RE - A question on size of downloads - what is acceptable for EpiData Software ?
by EpiData development and support 11 Feb '19

11 Feb '19

 Dear Jens,All in one" bundle is suitable and time saving in Windows software. Classical EpidataEntry and Analysis are still popular and stable. Please retain these as long aspossible. It will require time and effort to preserve the range of functionalities of  Classical Epidata Entry and Analysis in the new versions as well as add new features.Keep up this good contribution  for public health.With regards,Dr. Shavinder Singh  

1 0

A question on size of downloads - what is acceptable for EpiData Software ?
by EpiData development and support 08 Feb '19

08 Feb '19

Please consider if a change in download principles is acceptable. All maintained software could be released in two forms: 1 As an installation "all in one" bundle for (4 different bundles): a1: Linux 32 bit (Manager, EntryClient, New Analysis) b1: Linux 64 bit (Manager, EntryClient, New Analysis) c1: Mac OS (Standard Intel) : (Manager, EntryClient, New Analysis) d1: Windows (common routine for 32 and 64 bit): (Manager, EntryClient, New Analysis, Analysis Classic) 2 As zipped packages with all software in one zip file (4 different bundles): a2: Linux 32 bit (Manager, EntryClient, New Analysis) b2: Linux 64 bit (Manager, EntryClient, New Analysis) c2: Mac OS (Standard Intel) : (Manager, EntryClient, New Analysis) d2: Windows (all in one for 32 and 64 bit): (Manager, EntryClient, New Analysis, Analysis Classic) The download size will be up to about 10 Mb per package/bundle. With the above we add Analysis Classic to the current windows packages. The reason is that it will take quite a while before remaining functionality (graphs, survival analysis etc) will be added to the rewritten Analysis. Analysis Classic will remain as it is in the latest version (v2.2 rel 3, build 187). The webpage will also provide access to the current Classic Entry v3.1. Please comment here or by mail to info (at) epidata.dk Best wishes Jens Lauritsen EpiData Association Denmark

1 0