All Projects

Currently jumps cannot be defined from Date variables. Sometimes this is relevant.

Add this jump to dates:

Two options for development:
Quick one limited:
* is allowed, that is "after any value"

Jump to: all currently defined options.

an error is created if a vl already exist.

add new option , e.g.
new vl g i (0,"No") (1,"possibly") (2,"Definetely") !replace;

EpiData Manager
Program Version: 2.0.2.28 r1115
Core version: 2.0.0.0 r1126
FPC Version: 2.6.4
Platform: x86_64-Win64

I have a time field on opening a new record and a time field on first save.

1) It is unclear where and how to put the interval calculation, if the second to last field is one that either jumps to save record or goes to the last field
2) In analysis, the two fields are read as floats and have the form 0.852616. It is not clear what this is. Assuming that it could be a fraction of the day (as in EpiData Entry 3.1), I multiply (end-start)*86400 but the result does not make sense, giving something like 22.98 up to 73.01. I doubt that I took that many seconds (should be more like in the order of 10 seconds per record)

v4.0.2.49 (Copy version puts nothing in the clipboard)
This is reproducible and occurred with earlier builds.
Invoke the error: open a project and click Browse data, Find on an empty form
Click OK and the Find window opens with the current field, blank match type, blank match

Invoke the error: open a project, enter one field, cursor in that field; click Browse data, Find
Click OK and the Find window opens with the current field, blank match type, data entered in the field

Workaround:
open project, enter data to match, click Browse data, List records
This only seems to work when nothing else has been done, so I have to close the project and reopen to do another find this way

merged datasets get difficult names:

merge !ds:=ds5;

list ds _m*;

// example _merge_ds1_ds5_1 _merge_ds1_ds5_2 etc

Simplify "_merge_" to: "m-"

Label of the merged dataset is now the same as the first(use) dataset.

- change to: "("+"label of first"+"+"(" + "label of second ds"+")"

Flyspray setup is missing the rich text editor toolbar in new tasks.

<br /> see:
https://www.flyspray.org/manual/editing_task_details/

There has been a few comments on a "Dummyform already exists" error when running graph command.

This is not yet confirmed.

asdfasdfasdfasdfasdfasdf

* EPIDATA ANALYSIS PROGRAM

logopen "H:\Teaching Courses\Outbreak Course\bugTN_06122013\bugTN_06122013.htm" /close /replace

cd "H:\Teaching Courses\Outbreak Course\bugTN_06122013"
read "H:\Teaching Courses\Outbreak Course\bugTN_06122013\wedd" /close

set random simulations=10000

***********************************************
* EpiData Analysis 2.2.1.171
* tables ill redsauce gheerchick /o /nt /nc /ex /t /obs
* Using 2.2.1.171: OR = 1.08 [95% CI 0.22 to 5.66]; p(M-H)=0.916; p(exact)=0.0414

* EpiData Analysis 2.2.2.182
tables ill redsauce gheerchick /o /nt /nc /ex /t /obs /oex
* Using 2.2.2.182: OR(Exact) = 1.08 [95% CI 0.22 to 5.66]; p(M-H)=0.046; p(exact)=0.0414
* Using 2.2.2.182: OR = 1.07 [95% CI 0.11 to 10.06]

* Epi Info for DOS v6.04d
* tables redsauce ill gheerchick
* Using Epi Info for DOS v6.04d: OR (MLE) = 1.08 [95% CI 0.22 to 5.66]; p(M-H uncorrected)=0.91644269; p(M-H corrected)=0.81105112

* Stata/SE 12.1 for Windows (32 bit) Revision 20 Mar 2013
* logit ill redsauce gheerchick
* P-value for coefficient of redsauce = 0.916

* The estimate is close to 1 and the confidence interval is wide, so a test for the adjusted OR being significantly different to 1 should have a p-value close to 1
* Both Epi Info for DOS and Stata give a p-value of 0.916
* So I have a lot of confidence in this being the correct p-value.

* EpiData Analysis (build 171)
* The chi-squared test statistic and the p-value for a M-H weighted odds ratio using the option /t is 0.01 and 0.916
* This p-value using the option /t appears to be correct.
* The p-value using the option /ex appears to be incorrect.
* The chi-squared test statistic and the p-value using the option /ex is 6.147 and 0.0414.
* If the test statistic is correct a comparison to a chi-squared distribution of 1 degree of freedom should give a p-value equal to 0.0132?
* Possibly the correct p-value should be calculated as 1-2*(0.0414) = 0.917?

* EpiData Analysis (build 182)
* The chi-squared test statistic and the p-value for a M-H weighted odds ratio using the option /t is 6.15 and 0.046
* This p-value using the option /t appears to be incorrect.
* The p-value using the option /ex appears to be incorrect.
* The chi-squared test statistic and p-value using the option /ex is 6.147 and 0.0414.
* If the test statistic is correct a comparison to a chi-squared distribution of 1 degree of freedom should give a p-value equal to 0.0132?
* Possibly the correct p-value should be calculated as 1-2*(0.0414) = 0.917?

***********************************************
logclose

Strange problem. When I run this command on the attached data set everything runs fine: "stab komplians tjekind tjekud timeout /stat="sum" /by="yearweek" /n".

However, running this command freezes EpiData: "stab tjekind1 tjekind2 /stat="sum" /by="yearweek" /n" EpiData apparently goes into some kind of infinite loop using up all the cpu power. I can force the program to close by clicking the cross in the window corner.

The problem appears whenenver there are variables with almost similar names, e.g. tjekud1 tjekud2, etc.

Hello:

In the process of installing EpiData Manager or EpiData Entry, I can't find the web link of http://www.epidata.dk/license.htm.

I'm using GNU/Linux (Ubuntu) and I suppose that this problem appears in any Operating System.

Regards,

See attached .epx

Export to Stata (tested with V8 and V12) does not use Stata missing values for declared missing data (i.e. data matching one of the missing value label values).

System missing fields are always exported properly and recognized as system missing in Stata.

In this test file:
missing value of 9 / 99 in a 1 / 2 digit integer has value 100 in Stata, while the value labels include large values as missing
*** 100 is the largest legal number in byte data; first missing value (corresponding to Epidata system missing) is 101
missing value of 999 / 9999 in a 3 / 4 digit integer has value 32740, with the same large values as missing
*** 32740 is the largest legal number in small integer data; first missing value (corresponding to Epidata system missing) is 324701
value labels have the value 132417700 for the missing values of (8 / 88 / 888 / 8888)
and the value 132417701 for the missing values of (9/ 99 / 999 / 9999 )

With larger integers (5+ digits), the value labels for missing also follow this pattern, but at least the data are coded to match the new missing values.

**The bug**: declared missing values in the data should match the value label for that type of missing data.

While the user should be able to adapt to this by deleting the missing data values in analysis, it would make most sense to retain the original values.

**The feature request**: perhaps as an option, transform all declared missing values to Stata's missing values that represent .a, .b, .c, etc.
so for byte data, system missing remains 101, first missing value becomes 102 (.a), next becomes 103 (.b), etc.
for small integers (3-4 digits), system missing remains 32741, first missing becomes 32742 (.a), etc.
for long integers (5 and up), system and declared missing should match the .dta specification:

maximum nonmissing +2,147,483,620 (0x7fffffe4)
code for . +2,147,483,621 (0x7fffffe5)
code for .a +2,147,483,622 (0x7fffffe6)
code for .b +2,147,483,623 (0x7fffffe7)
...
While value labels for floats are not exported, they can also follow the same pattern for missing values (e.g. properties of the field include a range and declared missing values)

----------- Output from Analysis after reading the Stata 8/9 export file -------------
.list v;
Name Type Length Decimal Label Valuelabels Missing
V1 Integer 3 0 1 digit 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V2 Integer 3 0 2 digits 134217700 = N/A
134217701 = Missing
1 = OK
2 = OK too
V3 Integer 5 0 3 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V4 Integer 5 0 4 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V5 Integer 10 0 5 digits 1 = OK
2 = OK too
134217700 = N/A
134217701 = Missing
V6 Float 18 4 float 5.2
V7 Float 18 4 float 12.8
V8 String 207 0 text
V9 Date (DMY) 10 0 date
V10 Float 18 4 time
V11 Integer 3 0 boolean

.list vl;
_V1 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V2 (Integer)
Value Label Missing
134217700 N/A
134217701 Missing
1 OK
2 OK too

_V3 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V4 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

_V5 (Integer)
Value Label Missing
1 OK
2 OK too
134217700 N/A
134217701 Missing

.list data !vl; // data as read into Analysis; this matches exactly data as read into R
Obs. No 1 digit 2 digits 3 digits 4 digits 5 digits float 5.2 float 12.8 text date time boolean
1 1 OK 1 OK 1 OK 1 OK 1 OK 1 1 abcdefg 24/10/2017 43200000 1
2 2 OK too 2 OK too 2 OK too 2 OK too 2 OK too 2 2 ccc 11/10/2017 43200000 0
3 100 100 32740 32740 134217700 N/A 99.99 999.99999999 . . .
4 . . . . 134217701 Missing . . . . .
5 . . . . . . . . . .

A completely new editor is needed. The current is buggy and requires to much rewriting to maintain at a reasonable level.

This is expected to be implemented after the new core principle has been implemented.

The search and find dialog is buggy and requires a rewrite.

This is scheduled to happen after the new core principle has been implemented.

The entire core project requires translation.

At the moment there is no handling of progress event. This should be implemented.

Importing spreadsheets using fpSpreadSheet should be implemented.

Use the already provided fpc routines for writing DBF files instead of own constructed routines.

With these data and this command the output table does not mark test 5 as positive. Tests 4 and 5 should both be positive. The graph looks correct to me.

### command line and data table ###
ichart reghn uge /t4 /t5 /sl

Uge RegHN
2009-15 185
2009-16 272
2009-17 310
2009-18 241
2009-19 197
2009-20 277
2009-21 282
2009-22 316
2009-23 237
2009-24 302
2009-25 277
2009-26 267
2009-27 240
2009-28 261
2009-29 228
2009-30 167
2009-31 183
2009-32 181
2009-33 204
2009-34 215
2009-35 249
2009-36 291
2009-37 332
2009-38 303
2009-39 305
2009-40 292

The use of freq * /m instead of freq * /M troncate the display of results-> the result list is cut.

Ver 2.2.1.171

Helpfile says for the command "!":

dos textexecute any valid MS-DOS command and return to EpiData- dos command will open an MS-DOS window/open : Keep window open after execution
!works only on XP+ Pc's

I interpret this as working with XP or higher, but if it works in some XP versions (perhaps), it does not do so in all: I know of two colleagues in whom the command to open a batch file that directs to open a REC file (in EpiData Entry) opens the REC file in the default text editor.

Vista and Windows 7 no problem, it works perfectly.

Any chance to get this command "!" to work on XP machines? It is a marvelously powerful command. Or is there a workaround? The reason for its usefulness comes with using EpiData Analysis for a menu report, and allowing (or rather directing) people to enter data into a predetermined file only, and then in the same menu allow analysis by button pressing - the whole package including software can be given to people who need to know nothing.

Example is on www.tbrieder.org | EpiData | Part D, Exercise 4 solution

I noticed that the GUI which allows you to create histograms (Graph -> Histogram) does not let you specify a boolean variable as "by" variable.

Example:

. read C:\EpiData\TestData\bromar.rec
. select dectime<>.
. gen b fast=(dectime<3.87)

it is possible to do the following:

. his age /by=fast

but the GUI form does not list "fast" as a "by" variable.

When importing file structure from and .epx file, there could be an option to ignore the field position elements of the .epx XML structure. I suppose that normally these would start at the top of the page. When I broke up an .epx file using a text editor, the different sections start part way down the screen and leave blank space when imported.

Not a big deal for now.

Using sked.rec:

read sked.rec
missingvalue turkey /8
missingvalue chicken /8
tables status beef turkey chicken /ct /oex /t /sa

yields the MLE ORs all equal to 0.00 and CIs 0.00-0.00

Det ville være dejligt hvis man kunne kopiere en enkelt linje fra sin historik til pgm filen.
Tak.
Mvh Anna

using sked.rec:

missingvalue chicken /8
missingvalue turkey /8
* Expected to get odds ratios in the following command (has the output from ct changed from * previous builds? - if so, not listed as a change):
tables status sex beef chicken turkey /sa /ct /t
* Need to specify o option:
tables status sex beef chicken turkey /sa /ct /t /o
* But odds ratios disappear if add /ex (with or without t option):
tables status sex beef chicken turkey /sa /ct /t /o /ex

Linux install of manager:

Menu group created with link to Manager is : Other
Not "EpiData" as expected.

(EntryClient correctly installed in "EpiData")

Linux: Xubuntu 11.04, 32 bit - XFCE desktop

It would be nice to be able to wrap the text in long headings. The heading box has handles that suggest we can reshape the box, but it is constrained to one line. It will be useful to have extended explanatory text for a field that the user can read or refer to on screen.

Also, to facilitate entering long text, it would be VERY useful to allow the user to paste text from the clipboard. Since <ctrl>v or <command>v have another meaning in the field properties dialogue, this could be added to the edit menu (e.g. Paste text)

I think we can use Notes to deal with this, but it is awkward to have to read the explanation in another window. I'll play with window placement to see if this can work OK. Showing notes as a hint does not leave the text on screen long enough.

It is currently NOT possible to paste content into a fields question or a headings text.

This request is to provide CTRL+V/CTRL+C (Command on MAC) to these edits.

It is not possible to drag/drop controls outside the right and bottom border on a MAC, this is possible on both Windows and Linux.

Running reports through the txt-generator needs some additional features, such as

* Specifying/adding lines (dividers) horizontally in tables.
* --- do --- with vertical lines.

Eg:
------------------------------------------------
Main Dataset: Duplicate dataset:
------------------------------------------------
Record no: 4029
Key Fields:
id = .
Record not found in main datafile!
Record no: 4028
Key Fields:
id = .
Record not found in main datafile!
------------------------------------------------

should be:
------------------------------------------------
Record no: 4029
Key Fields:
id = .
Record not found in main datafile!
------------------------------------------------
Record no: 4028
Key Fields:
id = .
Record not found in main datafile!
------------------------------------------------

The value entered when recoding data using the "Recode Data" form is not validated in any way.

This may lead to undesired result and non-validated data.

Create a repport with details on what was done during append.

This report should include possibility to append multiple projects AND multiple datafiles in one go.

Add functionality to append multiple projects in one go!

Define new jump option:

(Save Record and Quit)

Result:
1 Save current record
2 Save current projectfile to disk without confirmation of doing the save
3 Quit EntryClient

Epidata manager and entry 2.0

The option when defining a value to save and exit data form is no longer supperted in version 2.0
the option I would like is:
-> End Dataform flow, stop relate sequence go to current top level.
Meaning "write record and make a break in data flow".

//Frederik

Details
Currently jumps can only be defined based on fields on current dataform

Sometimes the field to reference is on another dataform.

Jumps should therefore be possible such as:

dataform1 fields v1 v2 v3
dataform2 fields v17 v19 v21

From field dataform1.v2 we wish to jump to dataform2.v21 if dataform1.v2 is = 1
From field dataform1.v2 we wish to jump to dataform2.v17 if dataform1.v2 is <> 1

EpiData Manager: (2015/10/16 - 14:44:50)
Program Version: 2.0.7.53 r1213
Core version: 2.0.0.0 r1206
FPC Version: 2.6.4
Platform: i386-Darwin
(same behaviour with EntryClient)

For some fonts (e.g. Menlo on my MacBook - el Capitan OS), Manager imposes bold/italic even though I request regular. I wonder if there is something different about the new fonts (Menlo) in el Capitan.

I cannot find where the font preferences are stored (not in com.company.epidatamanager.plist)

We need a report which can print the content of a single parent record and ALL records in child datasets related to the parent record.

Identified in version 4.2.0.0 and below

I have a field defined with only one digit in the "decimal" part and three digit in the "length" part.

In the epidata entry client, when the user enter "123," a zero is automatically added when "," is entered and the focus is transferred to the next field.

This only occurs when the total number of characters entered by the user is equal to "length"+"decimal" and only for fields with one decimal.

If the user enter "1,2" it's ok.
It's quite disturbing for our users.

Description:
In a Trial we have to compile used substances for Drug-consumption.
Therefore a textfield is appointed. In Statistics we need a categorized numeric field with collected Text as Labels.
(In Stata-> encode , in SPSS-> autorecode)
But incorrect input (for example different shifted input, some uses abbreviations othes not ect.) creates more categories then needed.

Feature Request:
It would be nice, to have an "advanced Textfield" . You enter an item, which is choosable for coming enters, like a dropdownfield or a picklist.
This field should be exportet as an Integer with Labels.

This is a known bug in the Carbon Framework as best I can tell. I was supposed to be fixed 2 or 3 years ago, but seems to still be there.

I think we just need to watch for some resolution, but I don't think Carbon is being updated.

We should have something in release notes like:

In MacOS, the File Open dialog box may not always show files in your working data directory. This is a bug in the underlying framework that has been used to support creation of EpiData for Windows, MacOS and Linux, so we cannot change this behaviour. Mac users can create a shortcut to the data directory in the Finder Sidebar. The Sidebar will appear when you use File, Open or type read; at the command prompt.

Create "engine for graphs" - much like the aggregate/table system. That is a common class for all graphs which may then be inherited by as well SPC as standard graphs, unless SPC need their own class.

Total functionality of graphs defined as in EpiData Classic Analysis

.Append !fn:="Lykke.epx" ;
ERROR: This file is locked by another program!
You can force a read/save by using the option !force

.Append !fn:="Lykke.epx" !force ;
ERROR: Unknown option/variable: force

Two aspects of modifications of value labels are not handled in a user oriented manner.

1 change to "not found": // value label should be forgiving if deleting a value is not found, just like "drop v " .

for S in ["alvorliglbl", "fvgl","janej","henvislbl","koenlbl","plbl"] do

edit vl @{s} !d:=1410065407;

ERROR: Cannot delete - value does not exist!

2 change to "Cannot Assign Missing to undefined Value in: xxxx (here alderlbl)"

// Assigning missing to an undefined value is not handled correctly

edit vl alderlbl !m:=9;

ERROR: Unhandled error during execution:

Access violation

Please contact EpiData (info@epidata.dk) and include a copy of history and if possible example data!

export to stata

sdato,adato,atime

.,25-06-2017,12:12:00

.,20-12-2017,10:38:00

will be exported to Stata 14:

sdato adato atime

2.15e+09 25jun2017 12:12:00

2.15e+09 20dec2017 10:38:00

date is exported as 2.15e+09, not as the Stata "." value

In all versions
Use case:
On new record, enter a text value to match and press f

In creating the comboBox for match criteria, all field types are seen as integer
this means that the search form is created with empty match criteria for text fields
since = is not an option
Find or List fails with Index out of range, since the match criteria is not valid
Because using a new record is the quickest way to set up a search, the user must remove all string criteria and reenter them.

I sketched out a way to trap this in a commit to trunk, but it does not set the proper match criteria