Fixmat references are irritating when non-fixation data is stored in fixmats

Question

Fixmat references are irritating when non-fixation data is stored in fixmats

nwilming opened this issue 13 years ago · 4 comments

The fixmat data structure is quite useful for many other applications (read: normal psychopyhsical experiments). The frequent reference to 'fixmat' is annoying. It can probably be replaced by talking about 'events' or so.

Answer 1 · 2012-01-24T08:30:23.000Z

What about blocks of data stored in a BlockData

Answer 2 · 2012-01-24T08:38:30.000Z

I think I like datamat better than blockdata. Block doesn't quite reflect what you can do with a fixmat. Maybe we should just call it 'DataTable'?

Answer 3 · 2012-01-24T09:35:23.000Z

But the primary value of the representation here (over and above an array or lists of lists) is that it is blocked according to whatever is of interest to you in the analysis (trials/experiments/heartbeats/fixations/hits-on-the-head) and this defines the smallest unit of data. That and the ability to index the entire structure (datamat[].fixations) but I can't think of a name that captures that (SliceData?)

Answer 4 · 2012-05-15T08:33:37.000Z

I have refactored fixmat.py into fixmat.py and datamat.py. Datamat contains fixation unspecifc stuff (i.e. the datamat structure) and fixmat.py contains some fixation related things.