Hi Ernst

With the upcoming mission swap between Meteosats 10 and 11 I assume that your GEO scripts will need changing

Am I right in thinking that all we need to do is just swap the MSG3 and MSG4 scripts ?

Kind Regards

Graham

On Sun, Mar 12, 2023 at 03:19 AM, Graham Woolf wrote:

Am I right in thinking that all we need to do is just swap the MSG3 and MSG4 scripts ?

This might depend on how  EUMETSAT will rename the files we get from those birds.
And then there are the entries in areas.yaml that contain the sat names and longitudes.

Ernst

Hi Ernst

Thanks - so not quite as straightforward as I thought !!

Regards

Graham

On Sun, Mar 12, 2023 at 04:15 AM, Graham Woolf wrote:

Thanks - so not quite as straightforward as I thought !!

According to:

https://www.eumetsat.int/meteosat-10meteosat-11-mission-swap

filenames will change but EUMETCast channels (and hopefully also multicast addresses) will remain.

So this sounds definitely like some hours to invest to get all going again. And in SPS you may not want
the new RSS files in the old MSG4 directories and also ffmpeg must know where to get the frames from.
Not yet talking about cron.cmd that must be changed as well to start the right scripts at the tight times ...

I expect a period of EUMETCast problems not only for amateurs. E10B and MGT are at the door as well.

Ernst

On Sun, Mar 12, 2023 at 04:15 AM, Graham Woolf wrote:

Thanks - so not quite as straightforward as I thought !!

Graham,

In an attempt to educate the user I branded my
scripts per satellite with a couple of comments
like segment filenames, longitude position and
area covered. Obviously when EUMETSAT moves
around satellites and renames the files we get,
then naming per service like FES, RSS, IODC would
have less impact. It took me 3 hours to get all
fixed again. Like renaming of the BASIC channels,
changing the Uplink provider and DVB-S2 signal
such surprises seem part of the EUMETCast game.

Ernst

P.S. Satpy 0.40 broke Himawari image generation.
       If you updated recently be sure to use 0.41.

"P.S. Satpy 0.40 broke Himawari image generation.
       If you updated recently be sure to use 0.41."

Correction:
************
P.S. Satpy 0.41 broke Himawari image generation.
       If you updated recently be sure to use 0.41.1

Satpy is still a fast moving target. Here is the fix:

https://github.com/pytroll/satpy/commit/856f404871b0db4a8eed82dc6246a4144c12ad9b

Ernst

Hi Ernst

I have successfully changed all the necessary files for the move to MET10

All I did was replace MSG4 with MSG3 in the file names in GEO-Scripts and then did the same in cron and webm cmd files , I didnt change any times or anything else in cron

In the actual geo scripts I just looked for glob and then changed the filename - I couldnt find any references to MSG3/4 in areas.yaml

It all seems to be working - I have correct images in the correct locations

I will do the same when MET11 comes back next week

Warm Wishes

Graham

On Wed, Mar 22, 2023 at 04:22 AM, Graham Woolf wrote:

It all seems to be working - I have correct images in the correct locations

Graham,

part of my 3 hours was the problem with Himawari and I also changed all the comments.
There is one place I found in GEOstuff.py where NWCSAF files are "globed" for MSG4.
I slightly changed that allowing for all MSG  (IODC MSG2 NWCSAF is distributed on ter).

Regards,
Ernst

... and of course I forgot to mention that GEOstuff.py must now allow MSG3 for MSLP charts.

Ernst