Announce blocks/trials/state transitions in data file
Reported by Christopher Stawarz | October 5th, 2010 @ 12:40 PM
It's difficult to deduce the control flow on an experiment from
a data file. While the state transitions do appear to be recorded
as #announceCurrentState events, it's not obvious
if/how a user can map these announcements onto named paradigm
components in their experiment. (It looks like the mapping is
announced via a code 2, RESERVED_COMPONENT_CODEC_CODE,
event, but it's not clear that that info is meant to be accessed by
the user.)
It'd be nice if blocks, trials, states, etc. were announced more like stimuli, with the name included in the announce data.
Comments and changes to this ticket
-
David Cox October 6th, 2010 @ 11:23 PM
- Assigned user set to “David Cox”
We used to have something like this, but it led to file bloat / network load / realtime failures in cases where users created experiments that spun through many states quickly (probably not good form, but users did so anyways). As you've discovered already, the component codec and announceCurrentState events capture all of this information in as compact a manner as is feasible.
If user-friendliness is the issue, any reason not to build a little bit of genuinely-friendly API on top in the data file reading infrastructure? For instance, in the Python data file module, users don't actually have to worry about finding codec events, or translating event codes. It wouldn't be hard to provide similar "transparent" support for current state events.
-
David Cox October 6th, 2010 @ 11:23 PM
- Assigned user cleared.
-
-
Christopher Stawarz October 17th, 2012 @ 10:47 AM
- State changed from “open” to “hold”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The core framework and supporting libraries for the MWorks Suite
Christopher Stawarz
David Cox