Change in the incoming data: from MSG2 to MSG3

[Javier López]

Hi all,

 

A few days ago our incoming data changed its source from MSG2 to MSG3. I am having problems to generate products with the IR channels and I guess it has something to do with the calibration values, as the libraries show the following message when I run the programs:

 

[WARNING: 2013-01-31 13:40:25 : satin] Loading non calibrated data since calibration failed.
meteosatIR.py:95: RuntimeWarning: invalid value encountered in power
  1.055 * (arr ** (1.0 / 2.4)) - 0.055,

I have tried to modify the code in mipp making the update proposed in another thread for the change between Meteosat 9 and 10, but the result is the same.

 

Any help would be highly appreciated.

 

Regards,

 

Javier.

 

P.D: Seems that the problem affects mainly the IR channels, not the HRV.

[Martin Raspaud]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31/01/13 13:48, Javier López wrote:
> Hi all,
>
> A few days ago our incoming data changed its source from MSG2 to
> MSG3. I am having problems to generate products with the IR
> channels and I guess it has something to do with the calibration
> values, as the libraries show the following message when I run the
> programs:
>
> [WARNING: 2013-01-31 13:40:25 : satin] Loading non calibrated data
> since calibration failed. meteosatIR.py:95: RuntimeWarning: invalid
> value encountered in power 1.055 * (arr ** (1.0 / 2.4)) - 0.055, I
> have tried to modify the code in mipp making the update proposed in
> another thread for the change between Meteosat 9 and 10, but the
> result is the same.

Hi Javier,

A new version of mipp was released that should solve this problem. Can
you make sure you have mipp version 0.9.1 ?

Best regards,
Martin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJRCmr0AAoJEBdvyODiyJI4SgQH/0xsvVXrpPOFKjDoPNGqYbo5
BAqYnB/aei81x1OZCFwIMR2TKE0s+1YWFZNBPF7ZtdZwgVKynaXbkeYLNVr+Qg98
nAufP8txA7IkGj6RfDOSDUkHF/lAvrGl3G17tLD+wNybTc4UJbYs3lykyxqcBfYJ
xbUrcl5UKEbzEJZqYJYi4JgEqO0MSbuCUycSUxdNS5fqJAu+Mz0FUwP2Lscv37xd
pq3pQHBMcnyIB+Q+9qwTVRrs/yprIrFbV7zZT+2MqH42qKt4oaoMCB8T9PyuXDP+
rUxLK9mJVNfMHqKO5TzLuptJe3vL0NhP3P5QZ7gYVnXYyc9Cxf1YEYhW9U/uERQ=
=1O+G
-----END PGP SIGNATURE-----

[Javier López]

Nice! Installed and running. I thought it would be enough with the small change in the source code I found in the other thread but definitely this update seems to have solved the problem.

 

Thanks Martin.

 

Javier