The general consensus I have heard from operational forecasters is that
this artifact, while annoying, does not significantly interfere with
feature identification. It is much more obvious in derived imagery (e.g.
RGBs and channel differences) than single-band CH7. It is also apparently
NOT affecting the L2 Fire Detection (FDC) products.
Hopefully, the engineers will be able to identify a fix or mitigation for
it.
On Thu, Jul 28, 2022 at 2:06 PM Ryan Hickman <ryan@xxxxxxxxxxxxxxxx> wrote:
> Thanks for sharing Mike!
>
> Unfortunate that we're experiencing this and certainly hope that it gets
> resolved. Having two non-nominal satellites in the same sector is
> unfortunate but a single band (Band 7/GOES-18) vs multiple bands (Band 10,
> 12 & 16/GOES-17) is obviously better. Looking forward to further
> information on what might be happening and potential correction or
> mitigation.
>
> On Thu, Jul 28, 2022 at 1:01 PM Mike Zuranski <zuranski.wx@xxxxxxxxx>
> wrote:
>
>> Greetings all,
>>
>> The upcoming GOES-18 Interleave period is on schedule to begin Monday 8/1
>> (though I'm unsure of what time). That's the good news.
>>
>> The bad news is during Post Launch Testing an anomaly was found with Band
>> 7 data that results in vertical lines appearing in its imagery. This
>> "Barcode Artifact" is still under investigation and will not be mitigated
>> in time for the upcoming interleave period, so these lines may be seen in
>> that or any other multispectral/RGB imagery using Band 7.
>>
>> While the root cause is still unknown, it is NOT the same type of cooling
>> issue that GOES-17 has. The cooling system on GOES-18 (and GOES-U/19) was
>> redesigned and it is performing nominally (Phew!).
>>
>> For more information see this message from OSPO:
>> https://www.ospo.noaa.gov/data/messages/2022/07/MSG_20220728_1550.html
>> There's a useful PowerPoint linked on that page with examples, but be aware
>> it's about 50MB in size.
>>
>> Felt this was worth sharing in advance of the interleave period so we
>> know to expect it and that it's not at all related to LDM, NOAAPort, other
>> software, etc..
>>
>> Best,
>> -Mike
>>
>> ======================
>> Mike Zuranski
>> Meteorology Support Analyst
>> College of DuPage - Nexlab
>> Weather.cod.edu <http://weather.cod.edu/>
>> ======================
>> _______________________________________________
>> NOTE: All exchanges posted to Unidata maintained email lists are
>> recorded in the Unidata inquiry tracking system and made publicly
>> available through the web. Users who post to any of the lists we
>> maintain are reminded to remove any personal information that they
>> do not want to be made public.
>>
>>
>> ldm-users mailing list
>> ldm-users@xxxxxxxxxxxxxxxx
>> For list information or to unsubscribe, visit:
>> https://www.unidata.ucar.edu/mailing_lists/
>>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> https://www.unidata.ucar.edu/mailing_lists/
>
--
Matt Foster, Science & Operations Officer
NWS Operations Proving Ground
7220 NW 101st Terrace
Kansas City, MO 64153
Google Voice: (816) 514-2977
https://weather.gov/opg
Follow us on Twitter @nwsopg
