miyamot0 / datatracker3 Goto Github PK

I have encountered a few issues with the current version of Data Tracker.

The program often quits when reliability is calculated. When the program does not quit, the reliability output generated only reflects scores for the frequency keys (not duration keys). It also appears that data streams are being compared based off the time stamps of recorded keys. It would be helpful if the files were compared based on the start times instead, so a session could be coded from a video at a later time and compared to the primary file.

After collecting data, the program asks if the user would like to discard the data, with the default answer being 'yes'. Could you change the program to ask if the user would like to save the data (to make accidentally deleting files less likely)?

Also, are we able to change the primary save location on Data Tracker from the computer to Dropbox? This would allow us to calculate reliability without having to manually move all files onto one computer.

w/in ReliabilityScoring.h

Data tracker is quitting unexpectedly about half way through data collection. It is happening regardless of "primary" or "reliability." I haven't been able to get through an entire session to determine if any of the problems from prior posts (duration or frequency data are being collected accurately) are occurring.

With two different duration keys, each time I calculate a reliability report between two data collectors, each key has the exact partial interval agreement (for example, if key F denotes one behavior and key L denotes another, Data Tracker is calculating 85.67 PIA for both keys although the behaviors for these two keys are not occurring at similar rates). In addition, after calculating reliability by hand I was not able to get the same agreement- can someone explain to me how Data Tracker is calculating reli?