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.

Sign up for GitHub

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

Jump to bottom

[New Feature]: Update DISP-S1 consistent database file to the new one generated on 2025-01-22 #1063

Closed
philipjyoon opened this issue Jan 23, 2025 · 1 comment
Closed

[New Feature]: Update DISP-S1 consistent database file to the new one generated on 2025-01-22 #1063

philipjyoon opened this issue Jan 23, 2025 · 1 comment
Assignees
@philipjyoon
Labels
enhancement New feature or request needs triage Issue that requires triage

Comments

@philipjyoon
Copy link
Contributor

philipjyoon commented Jan 23, 2025 •
edited
Loading

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No response

Describe the feature request

We want to use this file: s3://opera-pst-rs-pop1/transfer/DISP_S1_DB_JSON/opera-disp-s1-consistent-burst-ids-2025-01-22-2016-07-01_to_2024-12-31.json

Steps:

  1. Follow directions here to validate and copy over the file to the ancilliaries S3 location: https://wiki.jpl.nasa.gov/display/operasds/DISP-S1+DB+File+Validation+and+Replacement
  2. Update settings.yaml so that it points to the new file
  3. Run unit tests test_cslc_util.py and test_cslc_query.py to make sure that we don't have any new issues w the new file
    3.1 Update the unit tests as necessary
  4. run run_all_cslc_query_scenario_tests.sh on a deployed machine Mozart
    4.1 Update the scenario test files as necessary
@philipjyoon philipjyoon added enhancement New feature or request needs triage Issue that requires triage labels Jan 23, 2025
@philipjyoon philipjyoon self-assigned this Jan 23, 2025
philipjyoon added a commit that referenced this issue Jan 23, 2025
@philipjyoon
#1063: Updated consistent db file to 2025-01-22-2016-07-01_to_2024-12…
155c042 
…-31 version. Fixed a bug where we threw out the entire frame in the db if there are no sensing dates for that frame. Updated and cleaned upunit tests
@philipjyoon
Copy link
Contributor Author

Completed as described. Only validated historical scenario test because reprocessing and forward processing are still influx.

hhlee445 added a commit that referenced this issue Jan 27, 2025
@hhlee445
Merge pull request #1064 from nasa/1063_update_disp_s1_consistent_db
dcf5dcb 
#1063: Updated consistent db file to 2025-01-22-2016-07-01_to_2024-12…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philipjyoon philipjyoon

Labels
enhancement New feature or request needs triage Issue that requires triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hhlee445 @philipjyoon