This change addresses an issue with remove_duplicate_dims() failing when being called a second time in test functions against a TEMPO dataset with duplicated dimensions. A separate copy of the test data is used to get expected results before subsetting.
Overview of work done
A data file copy is now created at the beginning of two test functions (test_subset_empty_bbox and test_specified_variables) that rely on opening the dataset more than once.
Overview of verification done
All of the test functions in the test_subset.py module were run and passed locally. In addition, five of the test functions, ...
test_subset_variables
test_subset_bbox
test_subset_empty_bbox
test_specified_variables
test_get_time_variable_name
..., were each run and passed against eight different TEMPO granules (Including Proxy and Science Team versions of O3PROF, HCHO, NO2, and CLD4).
Overview of integration done
Explain how this change was integration tested. Provide screenshots or logs if appropriate. An example of this would be a local Harmony deployment.
Github Issue: #168
Description
This change addresses an issue with
remove_duplicate_dims()
failing when being called a second time in test functions against a TEMPO dataset with duplicated dimensions. A separate copy of the test data is used to get expected results before subsetting.Overview of work done
A data file copy is now created at the beginning of two test functions (
test_subset_empty_bbox
andtest_specified_variables
) that rely on opening the dataset more than once.Overview of verification done
All of the test functions in the
test_subset.py
module were run and passed locally. In addition, five of the test functions, ...test_subset_variables
test_subset_bbox
test_subset_empty_bbox
test_specified_variables
test_get_time_variable_name
..., were each run and passed against eight different TEMPO granules (Including Proxy and Science Team versions of O3PROF, HCHO, NO2, and CLD4).Overview of integration done
Explain how this change was integration tested. Provide screenshots or logs if appropriate. An example of this would be a local Harmony deployment.
PR checklist:
See Pull Request Review Checklist for pointers on reviewing this pull request