Feature/issue 186 Optional NRT label in the filenames #187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub Issue: #186
Description
Filename regex pattern used for TEMPO collections fails because for NRT collections extra

_NRT_
label is included in the filename.For example, for standard collections, say
TEMPO_HCHO_L2_V04_20250101T000000Z_S001G01.nc
But in case of NRT collections, additional suffix
_NRT_
is present:TEMPO_HCHO_L2_NRT_V04_20250101T000000Z_S001G01.nc
So extra regex term needs to be included to capture optional
_NRT_
suffix, similarly to proxy term:Local test steps
Overview of integration done
Deployed updated batchee in a local Harmony environment and observed successful processing for NRT collections, as well as STANDARD collections.
NRT example:
STD example:
PR Acceptance Checklist
CHANGELOG.md
updated