[joey.hsu]

Thanks Andy, just shared via dropbox.

[joey.hsu]

Just looking to follow up on this, thanks!

Joey

[joey.hsu]

Hi Andy,

Thanks for your response!

I commented those lines out and they resolved the specific error that was in my post, but unfortunately does not fix the general issue of the electrodes for the manually entered localization not showing up.

I believe the larger issue has to do with the assignment of the “coords_mm” and “trajectory” variables at the top of the ea_showelectrode function.

When using lead group, the “coords_mm” and “trajectory” fields of the “elstruct” input variable are empty for the subject with the manually entered localization.

However, when using lead dbs to do the visualization, these fields are populated (seemingly automatically by lead dbs since I originally only entered the head and tail information for the subject) and thus the variable assignment works. In addition, it seems a final necessary piece is the “name” field, which is present again when running using lead dbs but not when using lead group.

If I run the lead group visualization while in debugging mode for the ea_showelectrode function, and then manually assign in the coords_mm, trajectory, and name fields of elstruct saved from using lead dbs visualization, I am able to get the lead group visualization to run successfully.

I believe solving this discrepancy is perhaps the key issue?

Thanks!
Joey

[joey.hsu]

Hello,

Looking to follow up on this old thread.

I am attempting to do a similar procedure as Martijn has described above but to be able to visualize the manually entered localization alongside an actual localization done with lead dbs through lead group.

I’ve followed Ningfei’s advice of setting up the reco variable for the manual entered localization and putting that into a blank subject folder, and that loads OK with the 3D visualization through lead dbs.

However, when I try to visualize the two localizations together in lead group, I get the following error:

_________________________________________________________________________________________
Cell contents reference from a non-cell array object.

Error in ea_showelectrode (line 34)
trajvector=mean(diff(trajectory{side}));

Error in ea_trajectory>update_trajectory (line 242)
[obj.elpatch,obj.ellabel,obj.eltype]=ea_showelectrode(obj.plotFigureH,obj.elstruct,obj.pt,poptions);

Error in ea_trajectory (line 159)
update_trajectory(obj);

Error in ea_elvis (line 164)
el_render(end+1)=ea_trajectory(pobj);

Error in lead_group>vizbutton_Callback (line 545)
resultfig=ea_elvis(options,M.elstruct(ptidx));

Error in gui_mainfcn (line 95)
feval(varargin{:});

Error in lead_group (line 42)
gui_mainfcn(gui_State, varargin{:});

Error in
matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)lead_group(‘vizbutton_Callback’,hObject,eventdata,guidata(hObject))
Error while evaluating UIControl Callback.

_______________________________________________________________________________________

It seems to do specifically with the manually entered localization as the lead group 3d visualization works fine if I just select the subject localized with lead dbs. I suspect it has to do with the fact that there is no further imaging/trajectory information available for the manually entered localization subject for the lead group script to use.

I am running matlab 2017b and lead suite 2.1.8.1

Thank you!
Joey

[Author]

Posts