isce3 icon indicating copy to clipboard operation
isce3 copied to clipboard

What should be the default `composite_release_id`?

Open gmgunter opened this issue 5 months ago • 1 comments

The CRID conventions for NISAR products are documented here: https://wiki.jpl.nasa.gov/display/NISARSDS/CRID+release+notification+process

The CRID convention for post-launch releases (after R4.0.8) changed recently:

  • EMMmmp
    • Environment
      • A = ADT
      • D = Development
      • T = Test
      • P = Prod
      • S = Science Ondemand
      • E or Q = Engineering or Quick-turnaround (TBD)
    • Major has 2 numerical digits
    • minor has 2 numerical digits
    • patch has 1 numerical digit

Each of the NISAR SAS runconfigs takes a composite_release_id as an optional input parameter, defaulting to "A10000".

  • RSLC https://github.com/isce-framework/isce3/blob/9df1acfcc42c2c5650e87e40daa90ce8729f4f23/share/nisar/defaults/focus.yaml#L83
  • GSLC/GCOV https://github.com/isce-framework/isce3/blob/9df1acfcc42c2c5650e87e40daa90ce8729f4f23/python/packages/nisar/products/writers/BaseWriterSingleInput.py#L689-L692
  • InSAR https://github.com/isce-framework/isce3/blob/9df1acfcc42c2c5650e87e40daa90ce8729f4f23/python/packages/nisar/products/insar/InSAR_base_writer.py#L953-L954

With the new CRID convention, this default value represents "ADT, major version 10". It doesn't seem like a good default for custom NISAR processing workflows.

Should we choose a different default CRID value? Perhaps one that can be easily recognized as a custom (invalid) CRID, like "Z00000"?

gmgunter avatar Aug 13 '25 19:08 gmgunter