Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

splitTD doesn't yet deal with multi-dimensional linked fields #9

Open
raeedcho opened this issue Feb 23, 2019 · 1 comment
Open

splitTD doesn't yet deal with multi-dimensional linked fields #9

raeedcho opened this issue Feb 23, 2019 · 1 comment

Comments

@raeedcho
Copy link
Collaborator

Example: In random target task, each trial has multiple targets, and thus multiple target locations. I'm not sure how exactly splitTD or TrialData in general should deal with splitting or storing that, but it's a potential issue nonetheless.

@mattperich
Copy link
Collaborator

I hadn't considered that use case, as splitTD was originally designed to split each target/movement into its own trial. However, if you want to preserve the sequence it should be possible. Right now linked fields explicitly assumes every field is linked to the split idx_ field. One possible solution could be to make the linked fields input 2-dimensional, so you match each parameter to any arbitrary field. Example: split on idx_trial_start. There are multiple go cues per trial. Linked_fields input is something like {'reward','idx_trial_start'; 'target_location','idx_go_cue'}. With this solution, Reward can get matched to idx_trial_start, but Target Location can get matched to idx_go_cue. So no matter how the code splits up idx_go_cue, there will be a corresponding target_location that makes it into the trial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants