Dear Developers,
I wonder whether my problem is related to this FCI reader issue
From the discussion on github it seems to me that the 40 data
segments are sorted by time but all have the same slot time?!
Actually if I load the global scene with "pad_data=False" I can
again make composite 'airmass' and also composite 'natural_color'
though that takes extremely long processing times (Intel XEON
32GB RAM, moderately loaded with other satpy processing tasks).
'airmass'
real 4m24.796s
user 6m51.223s
sys 0m16.339s
'natural_color'
real 7m22.727s
user 22m8.219s
sys 1m17.345s
I can also make composite 'convection' and 'true_color_raw'.
But when I want to make composite 'true_color' it fails with
an error that might again point to a block sorting problem?!
(Debug output from composite 'true_color' attached below)
'convection'
real 9m16.715s
user 20m55.170s
sys 0m57.754s
'true_color_raw'
real 8m52.891s
user 23m6.892s
sys 1m9.177s
Now that "manufacturers" get first real time MTG FCI data via
EUMETCast I expect more users will have/report similar problems.
Best regards,
Ernst