VAT problem: Ref. to non-existent field ‘vatsettings_horn_removeElectrode’

[tsieger]

Hi,
when attempting to visualize VAT for St.Jude directed 6172 (short) electrodes from within the Stimulation window, I encountered the following problem:

...
Region 40 captured by insulating material.
8 components with 362278 tetraeders total assigned to tissue type 1.
1 components with 444030 tetraeders total assigned to tissue type 2.
9 components with 56653 tetraeders total assigned to tissue type 3.
22 components with 303205 tetraeders total assigned to tissue type 4.
 Done. (30.8912 s)
Creating volume conductor...
 Completed percentage of this task indicated by dots
 0---10---20---30---40---50---60---70---80---90--100
  Done. (12.4489 s)
Calculating voltage distribution...
 Done. (9.7689 s)
Calculating E-Field...
 Done. (0.5443 s)
Calculating quiver field of gradient for display purposes...
Reference to non-existent field 'vatsettings_horn_removeElectrode'.

Error in ea_genvat_horn (line 400)
if options.prefs.machine.vatsettings_horn_removeElectrode

Error in ea_stimparams>stimulate_Callback (line 993)
            [stimparams(1,side).VAT(el).VAT,volume]=feval(ea_genvat,elstruct(el).coords_mm,getappdata(handles.stimfig,'S'),side,options,stimname,options.prefs.machine.vatsettings.horn_ethresh,handles.stimfig);

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

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

Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)ea_stimparams('stimulate_Callback',hObject,eventdata,guidata(hObject))
 
Error while evaluating UIControl Callback.

I’m running LeadDBS 2.3 with the default settings.

Any ideas, please?

cheers,
Tomas

[ningfei]

Hi Tomas,

This is an known issue which has been fixed in the development version. You can download the hotfix from http://www.lead-dbs.org/release/download.php?id=hotfix which is updated several times everyday. Just extract the hotfix and overwrite into your leaddbs installation folder. You can also do it from the leaddbs “Install” menu via “install development version of leaddbs”. Let me know if you still have problem with VTA calculation. Btw, if you see error about intersection when you calculate VTA, you can try to uncheck the “use atlas” optin in teh vta setting window.

Cheers,
Ningfei

[tsieger]

Hi Ningfei,
thanks for your quick help.
Yes, the hotfix resolved the issue (when downloaded and applied manually). VTA then could be computed w/o problems.
BTW: installing the hotfix from the Install menu did not work: http://neuro.felk.cvut.cz/data/uploads/images/misc/leaddbs2.3-update.png

• This reply was modified 4 years, 9 months ago by tsieger.

[tsieger]

I’m encountering problems posting replies to this thread. I’ll try to start another topic.
Tomas

[tsieger]

I can’t even start a new topic. I’ll try to continue here:

I’m curious why the E-field deviates quite a lot from my electrode:
http://neuro.felk.cvut.cz/data/uploads/images/misc/leaddbs-vat.png

–tbc–

[tsieger]

even though it seems that the electrode is not that much bent:
http://neuro.felk.cvut.cz/data/uploads/images/misc/leaddbs-left-electrode.png
–tbc–

[tsieger]

Is the E-field “tube” expected to follow the electrode artifact?
Also, I realized there is the “Auto-segment electrode from postoperative acquisition” button in the 3D view, but it seems it does nothing for my data (postop CT).

Cheers,
Tomas

[andreashorn]

Hi Thomas,

since, v2.3, by default, VTAs are calculated in native space and warped to MNI. Thus, what you see as the deviation is the nonlinearity in the warp. Instead, the electrodes are modeled as a line always (at least currently). Thus, fit around the contacts is nice but not throughout the whole lead.

You should not see such a deviation in native space.

Re new topics, I guess the forum is a bit buggy and also much more buzz is in the Slack channel. Use that one instead, there are also way more people there to provide help.

Best, Andy

[Author]

Posts