Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

audit-trails have reference/secondary acquisitions with differing track numbers #15

Open
niarenaw opened this issue Oct 25, 2021 · 0 comments
Assignees

Comments

@niarenaw
Copy link

Describe the bug
A previous bulk enumeration generated audit-trails where the reference and secondary acquisitions have differing track numbers even though each AOI should only be constrained to one track. This impacts a number of PGEs (ex. ops report creates an xlsx for each "track" in AOI).

To Reproduce
Example products for track 123:
S1-GUNW-acqlist-audit_trail-RM-M7S476-TN123-20171103T000000-20161102T000000-poeorb-b1a0
S1-GUNW-acqlist-audit_trail-RM-M0S0-TN123-20150424T000000-00000000T000000-poeorb-af21
S1-GUNW-acqlist-audit_trail-RM-M0S0-TN123-20150307T000000-00000000T000000-poeorb-73a1
S1-GUNW-acqlist-audit_trail-RM-M0S0-TN123-20150506T000000-00000000T000000-poeorb-60d9
@niarenaw has a script to find these for a given track number

Expected behavior
Each AOI (with only one track) should only have audit-trails where both the reference and secondary acqs have that one and only track.

Additional context
Proposed solution is to back-up each of these erroneous aduit-trail es docs and then purge them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant