isce-framework / isce-framework/isce3
Elevation Antenna Pattern dataset contains constant 1.0+0.0j (Placeholder Data?)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 239
- Forks
- 90
- Avg merge
- 13d 1h
- Merged PRs (30d)
- 5
Description
Description:
In test RSLC, GSLC, and GCOV datasets, all elevation antenna pattern values (in radar swath's extent) are exactly 1.0+0.0j (complex value), indicating no antenna pattern variation. This occurs even when EAP is enabled and an antenna pattern file was provided via the runconfig.
Are these placeholder values? If so, then because EAP was on, should those 2D complex datasets instead be populated with non-placeholder values?
Test Datasets Checked:
Datasets checked were produced by mission operations with CRID 05016. The RSLC's runConfigurationContents confirmed that EAP is enabled and that an antenna pattern file was provided: copy_of_RSLC_HDF5_runConfigurationContents_metadata.txt.
NISAR_L1_PR_RSLC_009_148_A_024_2005_DHDH_M_20260107T105830_20260107T105839_X05016_P_P_J_001NISAR_L2_PR_GSLC_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001NISAR_L2_PR_GCOV_001_149_D_080_2005_QPDH_A_20251003T130952_20251003T131016_X05016_N_P_J_001
HDF5 Location:
- RSLC:
/science/LSAR/RSLC/metadata/calibrationInformation/frequency[A|B]/elevationAntennaPattern/[HH|HV|VH|VV] - GSLC:
/science/LSAR/GSLC/metadata/calibrationInformation/frequency[A|B]/elevationAntennaPattern/[HH|HV|VH|VV] - GCOV:
/science/LSAR/GCOV/metadata/calibrationInformation/frequency[A|B]/elevationAntennaPattern/[HH|HV|VH|VV]
cc: @hfattahi @bhawkins @gshiroma @seongsujeong @rad-eng-59
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the listed RSLC, GSLC, and GCOV datasets at their elevationAntennaPattern HDF5 paths, then compare them with the attached runConfigurationContents metadata. Trace how the provided antenna pattern file and enabled EAP setting are reflected in those datasets. Done means determining whether the constant complex values are placeholders or expected output, and identifying the relevant processing or metadata behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100