Closed adybbroe closed 1 month ago
This is what I saw:
[DEBUG: 2024-10-25 15:10:15 : satpy.scene] Delaying generation of DataID(name='M12', wavelength=WavelengthRange(min=3.61, central=3.7, max=3.79, unit='µm'), resolution=742, calibration=<2>, modifiers=('nir_reflectance',)) because of incompatible areas
[DEBUG: 2024-10-25 15:10:15 : satpy.scene] Delaying generation of DataID(name='day_microphysics') because of dependency's delayed generation: DataID(name='M15', wavelength=WavelengthRange(min=10.263, central=10.763, max=11.263, unit='µm'), resolution=742, calibration=<2>, modifiers=())
[DEBUG: 2024-10-25 15:10:15 : satpy.scene] Delayed prerequisite for 'DataID(name='day_microphysics')': 'DataID(name='M15', wavelength=WavelengthRange(min=10.263, central=10.763, max=11.263, unit='µm'), resolution=742, calibration=<2>, modifiers=())'
[WARNING: 2024-10-25 15:10:15 : satpy.scene] The following datasets were not created and may require resampling to be generated: DataID(name='day_microphysics')
[DEBUG: 2024-10-25 15:10:15 : asyncio] Using selector: EpollSelector
Was puzzled why it delayed the creation of this, as I expected it to only use M-bands. There is a day_microphysics_hires
if you specifically want the high res version using I-bands. So I expected this one to use M-bands only!
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 96.09%. Comparing base (
118fc93
) to head (d6b8d01
). Report is 9 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Totals | |
---|---|
Change from base Build 11519299470: | 0.0% |
Covered Lines: | 53219 |
Relevant Lines: | 55318 |
This PR fixes a bug with the VIIRS low-resolution day-microphysics RGB using M-band.
It should use only M-bands! Currently it use the default nir-refelctance dataset, and that will then use the I-bands to try derive this. It should be forced to using the M bands.
AUTHORS.md
if not there already