IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jun 5, 2026, 10:55:58 AM (6 weeks ago)
Author:
eugene
Message:

use consistent names (VALID_OVERSCAN) for detrend type; fix a couple minor bugs in bad-overscan masking; use jpeg rules matching default chip

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/ppImage/src/ppImageParseCamera.c

    r43038 r43049  
    124124    if (options->doMaskBadOverscan) {
    125125        // if the file has been specified on the command-line (-valid-overscan file), then the file
    126         // is identified by the VALID.OVERSCAN entry in config->arguments.  otherwise, load from the
    127         // detrend system as type VALID.OVERSCAN
    128         if (!ppImageDefineFile(config, input->fpa, "PPIMAGE.VALID.OVERSCAN", "VALID.OVERSCAN",
     126        // is identified by the VALID_OVERSCAN entry in config->arguments.  otherwise, load from the
     127        // detrend system as type VALID_OVERSCAN
     128        if (!ppImageDefineFile(config, input->fpa, "PPIMAGE.VALID.OVERSCAN", "VALID_OVERSCAN",
    129129                               PM_FPA_FILE_VALID_OVERSCAN, PM_DETREND_TYPE_VALID_OVERSCAN)) {
    130130            psError(PS_ERR_IO, false, "Can't find a new non-linearity correction source");
Note: See TracChangeset for help on using the changeset viewer.