IDL procedures not implemented yet

Help
michael
2011-11-23
2013-06-03
1 2 > >> (Page 1 of 2)
  • michael
    michael
    2011-11-23

    Hi,

    I am trying to run a IDL program using GDL version 0.9.1
    on Fedora 16.

    I get these messages:

    # gdl spec.pro


    % Programs can't be compiled from single statement mode.
    % Parser syntax error: unexpected token: ,
    % Compiled module: SPEC_REPORT.

    % Compiled module: LOADCT.
    % LOADCT: Loading table Rainbow + white
    % Procedure not found: FILE_MKDIR
    % Execution halted at: $MAIN$         
    % Procedure not found: FILE_MKDIR
    % Execution halted at: $MAIN$         
    % Procedure not found: FILE_MKDIR
    % Execution halted at: $MAIN$         
    % Compiled module: FILE_LINES.
    % Parser syntax error: unexpected end of file
    % Parser syntax error: unexpected end of file
    % Subscript out of range _.
    % Execution halted at: $MAIN$         
    % Parser syntax error: unexpected token: ENDIF
    % Parser syntax error: unexpected token: ENDFOR

    …(program output)

    % Compiled module: SPEC_PLOT.
    % SPEC_PLOT: Procedure not found: PLOTSYM
    % Execution halted at: SPEC_PLOT           14 spec_plot.pro

    Am I correct that FILE_MKDIR and PLOTSYM are IDL procedures that are
    not yet available in GDL?

    Thanks,
    -Mike
    _

     
  • Hi,
    FILE_MKDIR is available since 0.9.2 (there's a Fedora package with this version - please update)
    The PLOTSYM procedure can apparently be downloaded from here: http://idlastro.gsfc.nasa.gov/ftp/pro/plot/plotsym.pro
    It uses the USERSYM routine which is implemented in the CVS version of GDL (since today).
    HTH,
    Sylwester

     
  • michael
    michael
    2011-11-23

    Hi,

    I have not used CVS ever. I will investigate how, but also ask here; how do I replace
    the current installed version (done with GUI) with the CVS version? 

    Thanks,
    -Mike

     
  • You don't need to use cvs, you can download a tarball of the current cvs version from the web:

    $ wget -Ogdl-cvs.tar http://gnudatalanguage.cvs.sourceforge.net/viewvc/gnudatalanguage/?view=tar
    $ tar xvf gdl-cvs.tar
    $ cd gnudatalanguage/gdl
    $ ./configure
    $ make
    $ make install

    There are many options for configure, e.g. -prefix=/opt/local if you want to install gdl in /opt/local or -python=no to disable the GDL-NumPy bridge, etc

    HTH,
    Sylwester

     
  • michael
    michael
    2011-11-23

    OK,

    I downloaded and did the 'configure' step (-with-wxWidgets=no; and also downloaded
    'pslib' from sourceforge because it is not available with the GUI software installer, it seems).

    Then I get this error for 'make':

    # make
    cd . && /bin/sh /usr/local/gnudatalanguage/gdl/missing -run automake-1.11 -gnu
    src/Makefile.am:70: Libtool library used but `LIBTOOL' is undefined
    src/Makefile.am:70:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
    src/Makefile.am:70:   to `configure.in' and run `aclocal' and `autoconf' again.
    src/Makefile.am:70:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
    src/Makefile.am:70:   its definition is in aclocal's search path.
    src/antlr/Makefile.am:15: Libtool library used but `LIBTOOL' is undefined
    src/antlr/Makefile.am:15:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
    src/antlr/Makefile.am:15:   to `configure.in' and run `aclocal' and `autoconf' again.
    src/antlr/Makefile.am:15:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
    src/antlr/Makefile.am:15:   its definition is in aclocal's search path.
    testsuite/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined
    testsuite/Makefile.am:1:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
    testsuite/Makefile.am:1:   to `configure.in' and run `aclocal' and `autoconf' again.
    testsuite/Makefile.am:1:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
    testsuite/Makefile.am:1:   its definition is in aclocal's search path.
    make: ***  Error 1
    # echo $LIBTOOL

    # grep AC_PROG_LIBTOOL configure.in
    AC_PROG_LIBTOOL

    Any suggestions?

    Thanks,
    -Mike

     
  • I'd try:

    $ libtoolize -f -i
    $ autoreconf
    $ ./configure …

    HTH,
    S.

     
  • michael
    michael
    2011-11-28

    Hi,

    The GDL program suggests submitting bug reports here, so I am.

    When I run this script in GDL,

    set_plot = 'x'
    window, 1, title = 'Time Sampling of the Entire Observations.', retain = 2 
    dates = indgen(2, /long)
    yy = indgen(2, /long)
    dates = 52984
    dates = 52989
    yy = 1
    yy = 1
    plot, dates, yy, psym = symcat(1), symsize = 0.3, $
    xstyle = 1, ystyle = 1, xrange = , $
    xtickformat = '(I6)', yrange = , $
    xtitle = 'Observation Dates (MJD)', background = 0, color = 255

    there are two problems.
    It does not plot both points, and the x-axis number labels are
    printed incorrectly, in my opinion.

    I am using a 'symcat.pro' that is from a 'coyote' library, dated 2006.

    Thanks,
    -Mike

     
  • Alain C.
    Alain C.
    2011-11-28

    thanks for this very useful post:

    1/ you found a bug in the new USERSYM procedure, which did not work when one or 2 points only are involved. I will try to solve that.

    2/ concerning the "plotting" way, we are dependant to plplot

     
  • Alain C.
    Alain C.
    2011-11-28

    USERSYM: should be now corrected in the CVS (please report as a bug any consequences)

     
  • michael
    michael
    2011-11-28

    Hi again,

    I get another error:

    % Compiled module: WRITE_PNG.
    % Compiled module: FITS_READ.
    % Compiled module: FITS_OPEN.
    *** glibc detected *** gdl: free(): invalid pointer: 0x08d0ce9c ***
    ======= Backtrace: =========
    /lib/libc.so.6
    /usr/lib/libstdc++.so.6(_ZdlPv+0x20)
    gdl(_ZN20FCALL_LIB_RETNEWNode4EvalEv+0x292)
    gdl(_ZN10ASSIGNNode3RunEv+0x3b)
    gdl(_ZN14GDLInterpreter9statementEP8ProgNode+0x51)
    gdl(_ZN14GDLInterpreter8call_proEP8ProgNode+0x1c)
    gdl(_ZN9PCALLNode3RunEv+0x12d)
    gdl(_ZN14GDLInterpreter9statementEP8ProgNode+0x51)
    gdl(_ZN14GDLInterpreter8call_proEP8ProgNode+0x1c)
    gdl(_ZN9PCALLNode3RunEv+0x12d)
    gdl(_ZN14GDLInterpreter9statementEP8ProgNode+0x51)
    gdl(_ZN14GDLInterpreter8call_proEP8ProgNode+0x1c)
    gdl(_ZN9PCALLNode3RunEv+0x12d)
    gdl(_ZN14GDLInterpreter9statementEP8ProgNode+0x51)
    gdl(_ZN14GDLInterpreter11interactiveEP8ProgNode+0x20)
    gdl(_ZN12DInterpreter11ExecuteLineEPSiy+0x6b3)
    gdl(_ZN12DInterpreter15InterpreterLoopERKSsRSt6vectorISsSaISsEES1_+0x340)
    gdl(main+0x56e)
    /lib/libc.so.6(__libc_start_main+0xf3)
    gdl
    =

    Is this a bug in GDL?
    I got the FITS file routines from 'idlastro.gsfc.nasa.gov'.
    Also I got some routines from 'coyote'.

    Thanks,
    -Mike

     
  • Thanks for this report.

    First, there was an bug fixed just three days ago in the CVS that had similar symptoms:
    https://sourceforge.net/tracker/?func=detail&aid=3441031&group_id=97659&atid=618683
    If you don't have the most recent CVS version, please try if updating it would help.

    If not, please post here a backtrace, that is the output from:

    $ gdb gdl
    gdb> run
    GDL> … excute the GDL commands that lead to the error
    gdb> bt

    Thanks,
    Sylwester

     
  • Alain C.
    Alain C.
    2011-11-28

    I just run the whole NRAO FITS test suite with AstroLib 6.0 without problem, using the current GDL CVS (It is stable since a long time but we have to take care of any regression). Could you please put somewhere the problematic FITS file ? I am ready to test.

    Alain

    PS: in fact we have a exchange of keywords in USERSYM, it will be fix ASAP.

     
  • michael
    michael
    2011-11-29

    Hi,

    OK. I installed the latest version of GDL and that fixed the crashing
    problem. I continue trying to get an IDL program to run under GDL.

    Since, the GDL introduction says to post feature requests to the forum
    also, I will. A 'write_gif.pro' and 'encode_gif.pro' would help. Or,
    for video (animations), 'write_ogv.pro'. Also, a minor IDL compatibility
    issue that I can easily work around, is to add the '/rev' option to the
    strmid (s, begin, , ) function.

    Thanks,
    -Mike

     
  • michael
    michael
    2011-11-29

    Hi,

    OK, I got my program to work. Thanks.

    Another minor feature request is the 'delvar' function.

    Thanks,
    -Mike

     
  • Alain C.
    Alain C.
    2011-11-30

    1/ very limited in functionnalities READ_GIF and WRITE_GIF, working on testsuite/Saturn.jpg (see working example in new files' headers) have been added in the CVS, please contribute.

    2/ PNG and JPEG should work better (wider capabilities), but we do not manage 4D cases (transparent) now, contributions welcome.

     
  • michael
    michael
    2011-12-01

    Hi,

    I installed GDL from 'gdl-cvs.tar', using ./configure, make, make install, with
    one option disabled 'wXwidgets=no'. Installation put '*.pro' files into directory
    "/usr/share/gnudatalanguage/lib/", except for "file_which.pro", at least. Is this
    intentionally omitted?

    Thanks,
    -Mike

     
  • astrogrl
    astrogrl
    2012-04-11

    Has the qromb function been written into GDL?  An online compilation suggests that it has, but when I run GDL 0.9.2, I get the following error:

    Function not found: QROMB

     
  • QROMB was added to GDL on January 10th 2012 and hence, as of now, it is only available in the CVS version. It will be inluded in the next release.
    HTH,
    Sylwester

     
  • Mark
    Mark
    2012-05-02

    Hi,

    Up several comments on this topic (back in 2011-11-28 it states that USERSYM is now available (from CVS). 

    I am working on OS X (10.7) and have installed the latest version available 1:0.9.2-3 (using Fink).  However, I still get the error "Procedure not found: USERSYM".  What can I need to do in order to get this (and likely other newer updates) for OS_X 10.7 (preferably using Fink)?

    Thanks,
    Mark

    Thanks,
    Mark          

     
  • Hi,

    You need a development version of GDL to use USERSYM (and many more new features!). It is available from the CVS repository. You can download it either using a CVS client or through the web interface, by following this link: http://gnudatalanguage.cvs.sf.net/viewvc/gnudatalanguage/?view=tar

    After downloading you need to compile GDL. I don't know of any pre-compiled or pre-configured packages using the CVS version.

    The new features will be available in the next release (no time set yet), and then they will be available in the packaged versions (e.g. Fink).

    HTH,
    Sylwester

     
  • Mark
    Mark
    2012-05-02

    Hi Sylwester,

    Thanks for the prompt response. I will give it a try as I would like to use the new features.

    Thanks,
    Mark

     
  • Mark
    Mark
    2012-06-27

    Hi,

    I tried to install the development version of GDL on my OS X 10.7, but I get a config error:

    checking for gsl_ran_binomial_knuth in -lgsl… no

    Error! Gnu Scientific Library (1.7 or higher) is mandatory

           (suitable Debian/Ubuntu package: libgsl0-dev)
           (suitable Fedora package: gsl-dev)

    When checking I do have a more recent version of GSL (1.15).

    Any suggestions on what next to try? 

    Has anyone else successfully configured the development GDL version on OSX 10.7?

    Thanks,
    Mark

     
  • Hi, please check the config.log file - the compilation errors from the test that produce the message you posted are there.
    HTH,
    Sylwester

     
  • Alain C.
    Alain C.
    2012-06-27

    I compile and test the core of GDL on OSX 10.7 very frequently (when the CVS changes). I have a local compiled GSL version, and just need to add the true path to ".configure", e.g.:
    http://aramis.obspm.fr/~coulais/IDL_et_GDL/GDLonOSX_10.6.3.html

    ./configure  -with-gsldir=/Path/To/GSL/gsl-1.14/Compilation/

    (last weeks I had problems with the cmake version on OSX but no time to explore)

     
1 2 > >> (Page 1 of 2)