Re: Himawari problem

Douglas Deans

On 29/10/2018 19:19, David J Taylor via Groups.Io wrote:
Meantime Eumetsat informed that the Himawari issue is caused in the data transfer from JMA to Eumetsat, resulting in intermittent and delayed data. There is thus far no solution or a resolution time frame available.
MSG Data Manager cannot cope with the haphazard data stream, resulting in a very high percentage of ignored data/images. The script developed by Miglus Thorsten collects the ‘random’ incoming segments until complete for an image, which can then be processed by the MSG Data Manager, albeit with varying delay. Recommended for people that need the Australasia/Pacific region.
Hopefully things will be normalized soon, keeping in mind that with the changing Goes-West parameters and Goes-17 not yet disseminated, the Pacific region is critically under-represented.
Ferdinand,  Thorsten,
I would be interested to know whether, with Thorsten's buffer running, you see any missed data in the Himawari stream.  My expectation is that the MSG Data Manager will log data as being received, even if it's too late to be of value.  With that assumption, I'm finding missing data even some 26 hours after it should have been sent.  I.e. it's not just a data buffering issue, but one of data being missing as well.
I'd welcome comments.

I am using EUMETCastView at the moment and that works differently as you know.
Since 07.00 this morning I am seeing 5 incomplete scans although there are many missing segments in some of them.
I can list them if anyone is interested.

By the way David your web site has been down for a number of hours.


Join to automatically receive all group messages.