Skip to content

Month: January 2024

link example ln -s

Published by admin-joel on 2024-01-18

Here is a successful example of linking a file that really exists in subdir of PersArmNoIntarm,
up to a phake one in main PersArmNoIntarm.  Note I am doing it FROM desired location of
phake.  I say to ln -s the original, down in subdir, to “dot” which is current (main) dir:

PersArmNoIntArm> ln -s OutputFromLocBoots/PersNoIntArmvsLocSlopes.20240717_S.Summ.eps .

print idl’s path and see if it can find a file within it and note capitalization conventions

Published by admin-joel on 2024-01-02

IDL> print, file_which(‘chjuldaytolmstGALFA.pro’)
/usr/share/astro/idlshare/locallib/chjuldaytolmstGALFA.pro

 

and more specifically:

from https://stackoverflow.com/questions/29986130/idl-procedure-wont-compile

IDL procedure won’t compile

But when I try to find the procedure using “Findpro” I get

Procedure CHLOADCT found in directory  /data/clh93/colortables/CH/

So my paths are right. I don’t understand why it won’t find my procedure, does anyone know what’s going on?

Answers:

Things to check in situations like this:

  1. you are consistent about whether the routine is a function or procedure, i.e., routine is procedure and you are calling it as a procedure
  2. routine you are calling is either compiled already or the last routine in a file named the same as it with a .pro extension; the case of the filename and routine call must match or the filename must be all lowercase (just use all lowercase in filenames!)
  3. quick check to see if my_routine.pro is in your !path: 
    IDL> print, file_which('my_routine.pro')

    It will return an empty string if it can’t find it.

  4. make sure the file is not in your !path twice and you are getting someone else’s or an old version