IMRTP subscript error

15 views
Skip to first unread message

David Craft

unread,
Jan 25, 2012, 12:09:17 PM1/25/12
to CERR FORUM
Does anyone know what causes this error when doing a QIB IMRT beamlet
calculation:
The IndexLow vector has some negative entries, which causes the crash,
but I'm wondering why this is and how to get around it.


...
Get ray trace for beam 179.
Elapsed time is 0.956717 seconds.
Get ray trace for beam 180.
Elapsed time is 0.335994 seconds.
Compute doses to structure number 11 for beam 1.
numPBs = 90
??? Subscript indices must either be real positive integers or
logicals.

Error in ==> GetPBConsts at 49
DepthLow=DepthTableV(IndexLow);

Error in ==> updateQIBInfluence at 151
[A_zV, a_zV, B_zV, b_zV] = GetPBConsts(radDepthV,
IM.beams(j).beamEnergy, QIBDataS, 'nearest');

Error in ==> updateIMRTP at 88
IM = updateQIBInfluence(IM, structROIV, sampleRateV, updateM);

Error in ==> IMRTPGui at 1171
IMDosimetry = updateIMRTP(ud.IM);

49 DepthLow=DepthTableV(IndexLow);

Joseph Deasy

unread,
Jan 25, 2012, 12:33:20 PM1/25/12
to cerr-...@googlegroups.com
David -

I would put in a

if IndexLow < 0
dbstop
end

type of commands, where indexLow is created and walk through the variable set, as a start.

- Joe


--
You received this message because you are subscribed to the Google Groups "CERR FORUM" group.
To post to this group, send email to cerr-...@googlegroups.com.
To unsubscribe from this group, send email to cerr-forum+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cerr-forum?hl=en.


David Craft

unread,
Jan 25, 2012, 1:17:29 PM1/25/12
to CERR FORUM
Thanks Joe.

Turns out the error is due to the fact that I was using CERR4 but the
IMRTP module from CERR3, and they don't play well together.

David
Reply all
Reply to author
Forward
0 new messages