User Tools

Site Tools


analysis:course-w16:week10

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
analysis:course-w16:week10 [2016/02/15 10:18]
mvdm [Estimating tuning curves]
analysis:course-w16:week10 [2016/02/16 14:01]
mvdm [Quantifying decoding accuracy]
Line 481: Line 481:
 % get trial id for each sample % get trial id for each sample
 trial_id = zeros(size(Q_tvec_centers));​ trial_id = zeros(size(Q_tvec_centers));​
-trial_idx = nearest_idx3(run_start,​Q_tvec_centers);​ % NOTE: on non-Windows,​ use nearest_idx.m+trial_idx = nearest_idx3(metadata.taskvars.trial_iv.tstart,​Q_tvec_centers);​ % NOTE: on non-Windows,​ use nearest_idx.m
 trial_id(trial_idx) = 1; trial_id(trial_idx) = 1;
 trial_id = cumsum(trial_id);​ trial_id = cumsum(trial_id);​
Line 497: Line 497:
  
 {{ :​analysis:​course-w16:​dec_err.png?​nolink&​600 |}} {{ :​analysis:​course-w16:​dec_err.png?​nolink&​600 |}}
 +
 +(Note, your plot might look a little different.)
  
 Thus, on average our estimate is 2.14 pixels away from the true position. Earlier laps seem to have some more outliers of bins where our estimate is bad (large distance) but there is no obvious trend across laps visible. Thus, on average our estimate is 2.14 pixels away from the true position. Earlier laps seem to have some more outliers of bins where our estimate is bad (large distance) but there is no obvious trend across laps visible.
analysis/course-w16/week10.txt ยท Last modified: 2018/07/07 10:19 (external edit)