Skip to content

remove cprnc.pl and cprnc.ncl; use standard cprnc instead #14

Closed

Description

@billsacks

Bill Sacks < sacks@ucar.edu > - 2013-05-29 12:59:52 -0600
Bugzilla Id: 1716
Bugzilla CC: muszala@ucar.edu, rfisher@ucar.edu,

My understanding is that cprnc.ncl and its cprnc.pl wrapper exist only because the standard fortran-based cprnc wasn't able to compare files without a time dimension. As of cprnc_130529, this is fixed. So I propose removing these CLM-specific cprnc scripts, and switching testing to use the standard cprnc instead.

Advantages:

(1) no longer need to maintain these scripts

(2) I recently found a problem with the cprnc.ncl script - it doesn't flag files as different if they differ in where there are missing values (see bug 1714). The fortran-based cprnc handles this correctly

(3) The fortran-based cprnc gives you more information about differences than you can get from cprnc.ncl.

(4) Post-processing scripts that look at cprnc output (e.g., summarize_cprnc_diffs) don't work on cprnc.ncl output; so if we switch to using the fortran-based program, these post-processing scripts can be used.

Activity

  1. added this to the future milestone on Dec 16, 2017
  2. added
    enhancementnew capability or improved behavior of existing capability
    on Dec 16, 2017
  3. ekluzek commented on May 17, 2018

    @ekluzek
    Contributor

    We've done this, so closing.

  4. added a commit that references this issue on Nov 19, 2019
  5. added a commit that references this issue on Sep 16, 2021
  6. added a commit that references this issue on Dec 22, 2022
  7. added 2 commits that reference this issue on Aug 1, 2023
  8. added a commit that references this issue on Dec 8, 2023
  9. added a commit that references this issue on Jun 2, 2024
  10. added a commit that references this issue on Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementnew capability or improved behavior of existing capability

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions