Changeset 43049 for trunk/ppImage

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

Location:

trunk/ppImage/src

Files:

• ppImageArguments.c (modified) (1 diff)
• ppImageParseCamera.c (modified) (1 diff)

trunk/ppImage/src/ppImageArguments.c

@@ -119 +119 @@
     pmConfigFileSetsMD (config->arguments, &argc, argv, "LINEARITY", "-linearity", "-linearlist");
     pmConfigFileSetsMD (config->arguments, &argc, argv, "NEWNONLIN", "-newnonlin", "-newnonlinlist");
-    pmConfigFileSetsMD (config->arguments, &argc, argv, "VALID.OVERSCAN", "-valid-overscan", "-valid-overscan-list");
+    pmConfigFileSetsMD (config->arguments, &argc, argv, "VALID_OVERSCAN", "-valid-overscan", "-valid-overscan-list");
     pmConfigFileSetsMD (config->arguments, &argc, argv, "PATTERN.ROW.AMP", "-pattern-row-amplitude", "-not-defined");
     pmConfigFileSetsMD (config->arguments, &argc, argv, "PATTERN.DEAD.CELLS", "-pattern-dead-cells", "-not-defined");

trunk/ppImage/src/ppImageParseCamera.c

@@ -124 +124 @@
     if (options->doMaskBadOverscan) {
         // if the file has been specified on the command-line (-valid-overscan file), then the file
-        // is identified by the VALID.OVERSCAN entry in config->arguments.  otherwise, load from the
-        // detrend system as type VALID.OVERSCAN
-        if (!ppImageDefineFile(config, input->fpa, "PPIMAGE.VALID.OVERSCAN", "VALID.OVERSCAN",
+        // is identified by the VALID_OVERSCAN entry in config->arguments.  otherwise, load from the
+        // detrend system as type VALID_OVERSCAN
+        if (!ppImageDefineFile(config, input->fpa, "PPIMAGE.VALID.OVERSCAN", "VALID_OVERSCAN",
                                PM_FPA_FILE_VALID_OVERSCAN, PM_DETREND_TYPE_VALID_OVERSCAN)) {
             psError(PS_ERR_IO, false, "Can't find a new non-linearity correction source");