comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Variable is undefined: Actually a function
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Variable is undefined: Actually a function [message #76824] Wed, 06 July 2011 13:17 Go to next message
Maegereg is currently offline  Maegereg
Messages: 10
Registered: June 2011
Junior Member
Still working on the same project as when I last posted an inquiry (the
relevant detail would be that I did not write this code). I'm getting
the following error at runtime:

% Variable is undefined: CALCULATE_DECAY_RATE.
% Execution halted at: PHYSIOLOGY::MTT
% ESTIMATE_AIF_MRTM 283 ~/Developer/DCE-MRI
ABC/MRTM/estimate_aif_mrtm.pro
% ANALYZE_ROI_DATA_EVENT 582 ~/Developer/DCE-MRI
ABC/ANALYSIS/analyze_roi_data.pro
% WIDGET_PROCESS_EVENTS
% $MAIN$

I've checked through PHYSIOLOGY::MTT, and it does call the function
CALCULATE DECAY RATE. The function is defined in
calculate_decay_rate.pro, is the last function in that file, and the
file is in ~/Developer/DCE-MRI ABC/OTHER_AIF/Bayesian, which is a
subfolder of the project directory (~/Developer/DCE-MRI ABC/). I've also
tried adding a forward function declaration to PHYSIOLOGY::MTT to no
avail. As you might expect, manually compiling calculate_decay_rate.pro,
and then manually compiling Physiology__Define.pro before running the
project will make the error go away, but whenever I do a full build on
the project the error returns. I've checked the project build order, and
calculate_decay_rate.pro should be built before Physiology__Define.pro.
Any help would be greatly appreciated.
Re: Variable is undefined: Actually a function [message #76894 is a reply to message #76824] Fri, 08 July 2011 09:44 Go to previous message
Maegereg is currently offline  Maegereg
Messages: 10
Registered: June 2011
Junior Member
Paulo Penteado wrote:
> Is the right file found with
>
> print,file_which('calculate_decay_rate.pro')
> print,file_which('calculate_decay_rate.pro',/include_current _dir)
>
> ?
>
> Also, what happens if you do
>
> resolve_routine,'calculate_decay_rate',/is_function
>
> ?

IDL> print, file_which('calculate_decay_rate.pro')
% Compiled module: FILE_WHICH.
~/Developer/DCE_MRI_ABC/OTHER_AIF/Bayesian/calculate_decay_r ate.pro
IDL> print, file_which('calculate_decay_rate.pro',/include_current_dir)
~/Developer/DCE_MRI_ABC/OTHER_AIF/Bayesian/calculate_decay_r ate.pro
IDL> resolve_routine, 'calculate_decay_rate', /is_function
% Compiled module: CALCULATE_DECAY_RATE.

That's the right files in those first two queries.
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: MIP from BMP Images
Next Topic: Re: TOTAL gives totally different result on identical array

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 11:43:36 PDT 2025

Total time taken to generate the page: 0.00465 seconds