You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running calwebb_image3 with 4 dithered Brightsky MIRI simulated data the combined image contains mostly zeros. This type of error was also reported in JP-1694.
When turning off outlier_rejection the combined data seems to contain data from the 4 dithers, but some of the image are highly distorted.
The below image (top 4 images ) are i2d files from cal_spec2. The bottom four images are the result of running the outlier detection step and setting save_intermediate_results = True. These images are the single images mapped to the output plane. These images show that something seems wrong with the WCS of the images.
!image-2020-12-11-09-30-15-866.png|width=563,height=275!
The data can be found at ███████████████████████████████████████████
The text was updated successfully, but these errors were encountered:
stscijgbot-jp
changed the title
Calspec3 not working correctly with MIRI dithered BRIGHTSKY data
Calimage3 not working correctly with MIRI dithered BRIGHTSKY data
Dec 11, 2020
Issue JP-1806 was created on JIRA by Jane Morrison:
There seems to be possibly two problems.
When running calwebb_image3 with 4 dithered Brightsky MIRI simulated data the combined image contains mostly zeros. This type of error was also reported in JP-1694.
When turning off outlier_rejection the combined data seems to contain data from the 4 dithers, but some of the image are highly distorted.
!image-2020-12-11-09-34-03-985.png|width=272,height=198!
The below image (top 4 images ) are i2d files from cal_spec2. The bottom four images are the result of running the outlier detection step and setting save_intermediate_results = True. These images are the single images mapped to the output plane. These images show that something seems wrong with the WCS of the images.
!image-2020-12-11-09-30-15-866.png|width=563,height=275!
The data can be found at ███████████████████████████████████████████
The text was updated successfully, but these errors were encountered: