error in ncflint when using -x -v

Help
2014-04-16
2014-05-05
  • Keith Oleson
    Keith Oleson
    2014-04-16

    Hi,

    I am using nco-4.3.9

    When I try the following command:
    ncflint -O -x -v ZSOI -w 0,31 file1.nc file2.nc file3.nc

    I get the error:
    ncflint: ERROR nco_xtr_mk() reports user-supplied variable name or regular expression ZSOI is not in and/or does not match contents of input file

    It is true that ZSOI is not in any of the files, but the documentation says "Variables explicitly
    specified for exclusion with ‘-x -v var[,...]’ need not be present in the input file."

    The above command seems to work fine in nco-4.2.0

    I could remove the -x -v ZSOI but this command also needs to be robust when I am processing files where some have ZSOI in them and some don't.

    Any ideas on this?

    thanks,

    Keith

     
  • Charlie Zender
    Charlie Zender
    2014-04-16

    Thank you for this bug report Keith. I confirmed the existance of this bug in the current release and just committed a fix that will be in 4.4.4. From the draft ANNOUNCE:

    A. Restore former tolerance of -x for non-existent elements.
    NCO normally requires that variables and groups specified with -v
    and -g must match the input file contents. The exception is when
    the -x flag tells NCO to exclude these elements. This exception
    was broken since NCO 4.2.x, and is now working again. Now excluding
    non-existent variables should one again work, e.g.,
    ncks -O -x -v no_such_variable ~/nco/data/in.nc ~/foo.nc
    Thanks to Keith Lindsay for this bug report.

    If you have a chance, please try the latest snapshot (will be available on yellowstone this weekend) and let us know if it does not solve the issue for you.
    cz

     
  • Charlie Zender
    Charlie Zender
    2014-04-16

    Meant Oleson not Lindsay, sorry!

     
  • Keith Oleson
    Keith Oleson
    2014-04-17

    Thanks for the quick response. I'll try it and let you know.

     
  • Charlie Zender
    Charlie Zender
    2014-05-04

    Finally put this on Yellowstone in ~zender/bin/LINUXAMD64.

     
  • Keith Oleson
    Keith Oleson
    2014-05-05

    Tried this on yellowstone and it solves the problem, thanks!