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

Home » Public Forums » archive » Re: Variable is undefined: Actually a function
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Variable is undefined: Actually a function [message #76822 is a reply to message #76819] Wed, 06 July 2011 16:22 Go to previous messageGo to previous message
penteado is currently offline  penteado
Messages: 866
Registered: February 2018
Senior Member
Administrator
On Jul 6, 5:17 pm, Maegereg <maege...@uchicago.edu> wrote:
> 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.

If ESTIMATE_AIF_MRTM makes no use of () for array indexing, a
'compile_opt strictarr' in it would solve the problem.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: mgunit 1.2 release
Next Topic: TOTAL gives totally different result on identical array

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

Current Time: Fri Oct 10 02:49:27 PDT 2025

Total time taken to generate the page: 1.03707 seconds