Date   
Re: cast-client-channels_xxxx.ini

David J Taylor
 

Hello All,


I'm configuring my hvs-1.ini (hopefully) and wonder if I need to also include:

receive_buffer_size=80000000
and tmp_directory=\EUMETCast\tmp\xxxx

In every channel entry?

Regards,
John.
===============================

John,

Please see the examples I just linked to.

I tried a greater bugger size (16 MB) for the HVS-1/2 instances, but I don't think it made a lot of difference to be honest. Better ways to reduce data loss!

The version supplied by EUMETSAT is a good template.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Meteosat Third Generation (MTG).

Douglas Deans
 

A very worthwhile read.
Go to the following page on the Eumetsat site :-

https://www.eumetsat.int/website/home/AboutUs/Publications/Brochures/index.html?lang=EN

and download the PDF listed as :-

Meteosat Third Generation - The case for preparing national users

Regards,
Douglas.

Configuring TC V2.14.4 .ini's.

geojohnt@...
 

David,

Thanks very much for the sample .ini configurations.

I was going to contact you 'off group' to hide my ignorance and embarrassment publicly, but I suspect that there may be a few users still using TC V2,4.4a who like me will have to - sooner, rather than later -  upgrade to the new/er version.
In fact I think it is now V2.14.5?
And, there are new EKU's coming out later this year.

Anyway, let's start at the beginning.
My HVS-1 path is:

Data disk E: > EUMETCast  > received  > hvs-1 > default

I am receiving and processing all 16 Himawari data files successfully with MDM-Himawari - originally via the 'default' folder.

My cast-client-channels_hvs-1.ini [and bas, afr-1, hvs-1, ter-1] are found here:

Data disk E: > Tools > EUMETCast client > EUMETCast - which is a different route. ???

Anyway, my earlier hvs-1 .ini configurations failed - I know not why - all data still going into 'default,' the hvs-1 'T' icon going yellow and a warning coming up on Tellicast HTML Shell Status to 'reset'.
It listed my 'faulty' configurations.

Having looked at your examples I had another go and voila, I now have:

E: > EUMETCast > received > hvs-1 > default, E1H-EPS-10, E1H-TPG-2, E1H-TPG-4 and E1H-TPL-1 folders.
These are the streams I see in Active Channels in TC HTML Shell.

As with your examples, I've left out tmp.
I presume that is OK.

Should I also increase the buffer to double, as you have?

I'm just awaiting confirmation of access to GOES-16 and GOES-17 data, so I will soon be downloading your ABI programme.

Thanks for resetting my brain, all seems to be in order now.

Regards,
John.

++++++++++++++++++++

In a message dated 18/06/2019 05:53:14 GMT Standard Time, gm8arv@... writes:

Sample files as requested:

https://www.satsignal.eu/wxsat/cast-client-channels-bas.ini.txt
https://www.satsignal.eu/wxsat/cast-client-channels-hvs-1.ini.txt

I've added the .TXT extension so that you can download them without any
malware warnings.  You could right-click, properties, unblock before use
and, of course, these are simply sample working files taken from my own
systems, and would need editing to suit your own data needs and directory
structure.

Re: cast-client-channels_xxxx.ini

geojohnt@...
 

David,

Sorry, I spent an hour fiddling before reading further emails?

Thanks for the added suggestion/clarification

Regards,
John.

+++++++++++++++++++++

In a message dated 18/06/2019 08:49:21 GMT Standard Time, gm8arv@... writes:

Please see the examples I just linked to.

I tried a greater
bugger size (16 MB) for the HVS-1/2 instances, but I don't
think it made a lot of difference to be honest.  Better ways to reduce data
loss!

The version supplied by EUMETSAT is a good template.

Cheers,
David

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

David,

Thanks very much for the sample .ini configurations.

I was going to contact you 'off group' to hide my ignorance and embarrassment publicly, but I suspect that there may be a few users still using TC V2,4.4a who like me will have to - sooner, rather than later - upgrade to the new/er version.
In fact I think it is now V2.14.5?
And, there are new EKU's coming out later this year.

Anyway, let's start at the beginning.
My HVS-1 path is:

Data disk E: > EUMETCast > received > hvs-1 > default

I am receiving and processing all 16 Himawari data files successfully with MDM-Himawari - originally via the 'default' folder.

My cast-client-channels_hvs-1.ini [and bas, afr-1, hvs-1, ter-1] are found here:

Data disk E: > Tools > EUMETCast client > EUMETCast - which is a different route. ???

Anyway, my earlier hvs-1 .ini configurations failed - I know not why - all data still going into 'default,' the hvs-1 'T' icon going yellow and a warning coming up on Tellicast HTML Shell Status to 'reset'.
It listed my 'faulty' configurations.

Having looked at your examples I had another go and voila, I now have:

E: > EUMETCast > received > hvs-1 > default, E1H-EPS-10, E1H-TPG-2, E1H-TPG-4 and E1H-TPL-1 folders.
These are the streams I see in Active Channels in TC HTML Shell.

As with your examples, I've left out tmp.
I presume that is OK.

Should I also increase the buffer to double, as you have?

I'm just awaiting confirmation of access to GOES-16 and GOES-17 data, so I will soon be downloading your ABI programme.

Thanks for resetting my brain, all seems to be in order now.

Regards,
John.
===============================

John,

It sounds as though you are making some progress - that's good.

Yes, 2.14.5 is current. I cheated an just copied the minimum files as I didn't want to go through all the reconfiguration again, and was uncertain whether the install.exe offered an "update the minimum" option. The minimum files are the tc-cast-client.exe and licence.ini.

It looks like I did leave out the tmp_directory, but that does restrict you to having all the data coming into one partition. I configure the tmp in the cast-client.ini. For the Basic Service I use a RAMdisk:

[parameters]
tmp_directory=Z:\EUMETCast\tmp

and for the HVS-1 (where I take the minimum data, a directory on the receiving drive (i.e. partition letter):

[parameters]
tmp_directory=L:\Tools\EUMETCast\tmp_2

I used a RAMdisk on BAS as I was upgrading from an earlier installation, and a separate physical HD on the HVS-1 system sort of a a test. With ONLY the HVS-1 data on that HD (a cheap 1 TB drive), there appears to be no need for a RAMdisk. Your configuration will vary!

I would strongly advise against the "default" directory, you can fill HDs very easily that way, and create an unnecessary workload for TelliCast and the HDs. Define all the channels you want, and comment out the default. I think you're already doing that.

It doesn't matter where the executable and the configuration files live.

Leave the buffer at the EUMETSAT suggested 8 MB value. As before, start with the minimum to prove things work, and then build up the other channels.

I'm running four MSG Data Managers on one PC (IODC, RSS, Himawari, 0-degree), and three on another PC (IODC, RSS, 0-degree/Himawari). On the third system it's still like the old days - the MDM IODC/RSS/0-degree) as that PC is BAS-only.

I'm running three Metop Managers on the systems with HVS-1 access, two on the BAS system, with the Metop-B instance as the NOAA-19 handler, as the Metop-A data is moving to HVS-1 soon.

Many ways to skin this cat!

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Re: Configuring TC V2.14.4 .ini's.

geojohnt@...
 

David,

Thanks very much for the useful comments and advice.

Ah, it sounds like from your comments that updating to the latest TC V2.14.5 wipes your channel ini configurations?
That's not very clever.
One would have thought(?) just the tc-cast-client.exe and licence.ini - as you copied over - were required.

Your comments on also having tmp files location in your channels ini (which I have left out) and comments on RAMdisk ahve given me something else to worry about.
You have said to put the tmp's back.
Should they reflect the channel - that is - tmp_directory=\EUMETCast\tmp\hvs-1\E1H-TPG-4 - or
tmp_directory=\EUMETCast\tmp\hvs-1 - which was/is, the sample suggestion of the programme?

Regarding RAMdisk I never understood, or have seen 'the path ' of data through the RAMdisk to the programmes.
I have a 997 MB RAMdisk running on BS (still) using TC V2.4.4a.

I'm presuming that my new HVS-1 data channels are not going though the RAMdisk also?
I thought the point of TC V2.14.4 was to eliminate the need for a RAMdisk but there has been discussion on this group in the past as to possible advantages of still using a RAMdisk - there is so much data coming in.

That will be something to 'do' when I move my BS to TC V2.14.4.

In the meantime with GOES-16 and GOES-17 data activated I need to download your ABI prgramme.
Do I need to run 2 copies - or does one copy have tabs for both satellites like MDM?

Regards,
John.

 ++++++++++++++++++++++++++++++++++++

In a message dated 18/06/2019 14:40:29 GMT Standard Time, gm8arv@... writes:

John,

It sounds as though you are making some progress - that's good.

Yes, 2.14.5 is current.  I cheated an just copied the minimum files as I
didn't want to go through all the reconfiguration again, and was uncertain
whether the install.exe offered an "update the minimum" option.  The minimum
files are the tc-cast-client.exe and licence.ini.

It looks like I did leave out the tmp_directory, but that does restrict you
to having all the data coming into one partition.  I configure the tmp in
the cast-client.ini.  For the Basic Service I use a RAMdisk:

[parameters]
tmp_directory=Z:\EUMETCast\tmp

and for the HVS-1 (where I take the minimum data, a directory on the
receiving drive (i.e. partition letter):

[parameters]
tmp_directory=L:\Tools\EUMETCast\tmp_2

I used a RAMdisk on BAS as I was upgrading from an earlier installation, and
a separate physical HD on the HVS-1 system sort of a a test.  With ONLY the
HVS-1 data on that HD (a cheap 1 TB drive), there appears to be no need for
a RAMdisk.  Your configuration will vary!

I would strongly advise against the "default" directory, you can fill HDs
very easily that way, and create an unnecessary workload for TelliCast and
the HDs.  Define all the channels you want, and comment out the default.  I
think you're already doing that.

It doesn't matter where the executable and the configuration files live.

Leave the buffer at the EUMETSAT suggested 8 MB value.  As before, start
with the minimum to prove things work, and then build up the other channels.

I'm running four MSG Data Managers on one PC (IODC, RSS, Himawari,
0-degree), and three on another PC (IODC, RSS, 0-degree/Himawari).  On the
third system it's still like the old days - the MDM IODC/RSS/0-degree) as
that PC is BAS-only.

I'm running three Metop Managers on the systems with HVS-1 access, two on
the BAS system, with the Metop-B instance as the NOAA-19 handler, as the
Metop-A data is moving to HVS-1 soon.

Many ways to skin this cat!

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

David,

Thanks very much for the useful comments and advice.

Ah, it sounds like from your comments that updating to the latest TC V2.14.5 wipes your channel ini configurations?
That's not very clever.
One would have thought(?) just the tc-cast-client.exe and licence.ini - as you copied over - were required.

Your comments on also having tmp files location in your channels ini (which I have left out) and comments on RAMdisk ahve given me something else to worry about
You have said to put the tmp's back.
Should they reflect the channel - that is - tmp_directory=\EUMETCast\tmp\hvs-1\E1H-TPG-4 - or
tmp_directory=\EUMETCast\tmp\hvs-1 - which was/is, the sample suggestion of the programme?

Regarding RAMdisk I never understood, or have seen 'the path ' of data through the RAMdisk to the programmes.
I have a 997 MB RAMdisk running on BS (still) using TC V2.4.4a.

I'm presuming that my new HVS-1 data channels are not going though the RAMdisk also?
I thought the point of TC V2.14.4 was to eliminate the need for a RAMdisk but there has been discussion on this group in the past as to possible advantages of still using a RAMdisk - there is so much data coming in.

That will be something to 'do' when I move my BS to TC V2.14.4.

In the meantime with GOES-16 and GOES-17 data activated I need to download your ABI prgramme.
Do I need to run 2 copies - or does one copy have tabs for both satellites like MDM?

Regards,
John.
========================================

John,

What I meant was that I was unsure whether the "install.exe" method would affect my channels file, so I assumed that it /might/ and hence just updated the two files. Of course, I may not get any changes which EUMETSAT advise (such as the buffer parameter), so I would only advise my method for experts.

You can put all the temp files wherever you like, so long as they are on the same partition (drive letter) as the final data. This allows you to have different data streams on different disks.

TelliCast builds the file in the temp location (e.g. RAMdisk) as the data comes in. Once the file is complete it is renamed to its final name and moved to its final location. A "move" operation can be done on the same drive just by manipulating the directories (quick), but if the destination is on a different drive a "copy" operation is required which costs much more disk I/O.

Very broadly speaking, if you have a separate physical hard disk for the data (or perhaps a separate physical disk for each service BAS/HVS-1/HVS-2) you can get away without a RAMdisk. If your HD is also used for other purposes (e.g. running my programs, making animations), a RAMdisk may be required. Likely if you ask the group you will get more answer than there are group members!

Run two copies of the GOES ABI Manager, with the .EXE files named differently. You can have both in the same directory:

~~~~~~~~~~~~~~~~~~~~~~~~~~~
GOES-ABI-Manager.txt
GoesAbiManager-G16.exe
GoesAbiManager-G17.exe
hdf5.dll
hdf5_hl.dll
msvcr120.dll
netcdf.dll
zlib1.dll
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

GOESS-16, GOES-17 DM.

geojohnt@...
 

David,

Looks like I will need two copies of 'GDM ' since the data folder names are different - hence Tellicast received flies location path.

Or, could

Regards,
John.


Re: GOESS-16, GOES-17 DM.

geojohnt@...
 

Sorry David,

Thinking out aloud and itchy 'enter' finger.

John

++++++++++++++

In a message dated 19/06/2019 16:09:30 GMT Standard Time, geojohnt@... writes:

David,

Looks like I will need two copies of 'GDM ' since the data folder names are different - hence Tellicast received flies location path.

Or, could

Regards,
John.


Re: Configuring TC V2.14.4 .ini's.

geojohnt@...
 

In a message dated 19/06/2019 15:49:09 GMT Standard Time, gm8arv@... writes:

>What I meant was that I was unsure whether the "install.exe" method would
>affect my channels file, so I assumed that it /might/ and hence just updated
>the two files.  Of course, I may not get any changes which EUMETSAT advise
>(such as the buffer parameter), so I would only advise my method for
>
experts.

Thanks for the clarification.
Perhaps in someone has updated to V2.14.5 they might confirm all ones user parameters remained intact?

>You can put all the temp files wherever you like, so long as they are on the
>same partition (drive letter) as the final data.  This allows you to have
>different data streams on different disks.

OK fine - I've restored them to EUMETCast\tmp\hvs-1.

Thanks for the RAMdisk explanation - I think I understand.
It's been such a long time since setting up my EUMETCast (only) computer, I can't remember what I did 'way back when.'

>Very broadly speaking, if you have a separate physical hard disk for the
>data (or perhaps a separate physical disk for each service BAS/HVS-1/HVS-2)
>you can get away without a RAMdisk.  If your HD is also used for other
>purposes (e.g. running my programs, making animations), a RAMdisk may be
>required.  Likely if you ask the group you will get more answer than there
>are group members!

Likely if you ask the group you will get more answer than there
are group members! 🤣

Looks like, with my one computer system, I'll have to have 2nd HDD for HVS-2 and Sentinel - or, another one computer system.

The present one will now be running 4 x MDM, Animator, AVHRR Manager, 2 x Metop Manager (+ another Metop C?), 2 x ABI Manager - and NOAA 20, whatever format that is/will be. 
 
Regards,
John.

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

From: geojohnt via Groups.Io
[]
Looks like, with my one computer system, I'll have to have 2nd HDD for HVS-2 and Sentinel - or, another one computer system.

The present one will now be running 4 x MDM, Animator, AVHRR Manager, 2 x Metop Manager (+ another Metop C?), 2 x ABI Manager - and NOAA 20, whatever format that is/will be.

Regards,
John.
=========================================

John,

With the large number of services now offering Sentinel derived data - some free of charge - I'm not that convinced that it's worth collecting. I wonder what others think?

The zero degree MSG Data Manager can handle Himawari data as well, but needs a little fiddling to get both into the single Manager, which can read both "Data Channel 4" and "EUMETSAT_Data_Channel_4". Use one for the BAS/Chan.4 data and the other for HVS-1/Himawari data. But using four is simpler. 3 x Metop, 2 x ABI. FOr a few more weeks there's also GOES-15 in EUMETSAT's format.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Re: Configuring TC V2.14.4 .ini's.

geojohnt@...
 

David,

Firstly, 'everything' is now running OK.
That is - HVS-1 using TC V2.14.4:

Himawari MDM all 16 spectral channels.
GOES-16 ABI all 16 spectral channels.
GOES-17 ABI all 16 spectral channels.

BS using TC 2.4.4a:

2 x MDM 12 spectral channels - 1 with FSD
1 x MDM 6 spectral channels.
2 x Metop Manager.
MSG Animator - 1 animation.
1 x AVHRR Manager.

Next step to change BS to TC V2.14.4 for BS.

Sentinel, well, their VIS channels are 'very' high resolution, aren't they?
This I would certainly want.

My HVS-1 default folder is still 'filling up' with goes 15 BZ2 files, npp H5 files, and Darmstadt sounding BIN files, despite having commented out - E1H-EPS-10, E1H-TPG-4, E1H-TPL-1 and E1H-RDS-1.

It seems there is another channel active dumping files into my default folder?
But I don't see this pop up on TC HTML Shell Active Channels.
Mind you, I don't sit there hours on end watching for it.

I see the HVS-1 channel table lists ..... EPS-1, 2, 3, 5, 6, 8, 10, 11.
So I guess it's one or more of these?

Regards,
John

++++++++++++++++++++

In a message dated 19/06/2019 17:54:05 GMT Standard Time, gm8arv@... writes:


John,

With the large number of services now offering Sentinel derived data - some
free of charge - I'm not that convinced that it's worth collecting.  I
wonder what others think?

The zero degree MSG Data Manager can handle Himawari data as well, but needs
a little fiddling to get both into the single Manager, which can read both
"Data Channel 4" and "EUMETSAT_Data_Channel_4".  Use one for the BAS/Chan.4
data and the other for HVS-1/Himawari data.  But using four is simpler.  3 x
Metop, 2 x ABI.  FOr a few more weeks there's also GOES-15 in EUMETSAT's

format.

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

-----Original Message-----
From: geojohnt via Groups.Io
Sent: Thursday, June 20, 2019 10:28 AM
To: MSG-1@groups.io
Subject: Re: [MSG-1] Configuring TC V2.14.4 .ini's.


David,

Firstly, 'everything' is now running OK.
That is - HVS-1 using TC V2.14.4:

Himawari MDM all 16 spectral channels.
GOES-16 ABI all 16 spectral channels.
GOES-17 ABI all 16 spectral channels.

BS using TC 2.4.4a:

2 x MDM 12 spectral channels - 1 with FSD
1 x MDM 6 spectral channels.
2 x Metop Manager.
MSG Animator - 1 animation.
1 x AVHRR Manager.

Next step to change BS to TC V2.14.4 for BS.

Sentinel, well, their VIS channels are 'very' high resolution, aren't they?
This I would certainly want.

My HVS-1 default folder is still 'filling up' with goes 15 BZ2 files, npp H5 files, and Darmstadt sounding BIN files, despite having commented out - E1H-EPS-10, E1H-TPG-4, E1H-TPL-1 and E1H-RDS-1.

It seems there is another channel active dumping files into my default folder?
But I don't see this pop up on TC HTML Shell Active Channels.
Mind you, I don't sit there hours on end watching for it.

I see the HVS-1 channel table lists ..... EPS-1, 2, 3, 5, 6, 8, 10, 11.
So I guess it's one or more of these?

Regards,
John
=================================

John,

GOES-15 information is here:

https://www.eumetsat.int/website/home/News/DAT_4167864.html

It's a temporary service, and I have a free program to handle the data.

Some of the sounding files will be handled by the Metop Managers, I recall.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Re: Configuring TC V2.14.4 .ini's.

geojohnt@...
 

David,

Thanks.

I think you alerted me to GOES-15 earlier but as it's only temporary now and only 9 degrees away from GOES-16, I won't bother - already far too much imaging to look at.

Was that 'some of the sounding files' referring to EUMETSAT Darmstadt SOUNDING BIN files being able to be processed by Metop Manger?

If so, I might try to run a third copy of MM and have a look.

Regards,
John

+++++++++++++++++++++

In a message dated 20/06/2019 11:16:48 GMT Standard Time, gm8arv@... writes:

GOES-15 information is here:

  https://www.eumetsat.int/website/home/News/DAT_4167864.html

It's a temporary service, and I have a free program to handle the data.

Some of the sounding files will be handled by the Metop Managers, I recall.

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

David,

Thanks.

I think you alerted me to GOES-15 earlier but as it's only temporary now and only 9 degrees away from GOES-16, I won't bother - already far too much imaging to look at.

Was that 'some of the sounding files' referring to EUMETSAT Darmstadt SOUNDING BIN files being able to be processed by Metop Manger?

If so, I might try to run a third copy of MM and have a look.

Regards,
John
===================================

John,

Yes, the GOES-15 is purely a transition arrangement, which is coming to an end - perhaps before the second half of the year. In any case, there are some issues with processing the data in real-time (the location information is sent /after/ the data, not before!).

Each Metop satellite offers data named like:

W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPA+AVHRR
W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPB+AVHRR
W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPC+AVHRR

These are air motion vectors, and the Metop Manager will handle them if the Process AVHRR polar winds box is checked, so if you're getting that data you need a third Metop Manager for Metop-C. That's on EPS-10 as it's from the AVHRR instrument.

The highest resolution Sentinel data is from Sentinel-2, and that's not on EUMETCast. The Sentinel-3 data (which is) is 300m resolution. I don't know whether anyone is still taking Sentinel data on a regular basis as it's readily available in image form from the Internet, and various folk have written quite complex processing scripts to make the most of the data. Folk here have written scripts to keep data for a particular area of interest up-to-date.

Interestingly, the data flow from the next generation of satellites is reported to be ten times what we have at the moment. How many transponders on which satellites will that take!

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Re: Configuring TC V2.14.4 .ini's.

geojohnt@...
 

David,

Thanks again for as usual interesting and informative responses.

Ah, right, the highest Sentinel data is not disseminated by EUMETCast, however 300 m is pretty good.
But one step at a time?


>Interestingly, the data flow from the next generation of satellites is
>reported to be ten times what we have at the moment.  How many transponders
>on which satellites will that take!

Well, as you know I'm receiving Eutelsat 9B - at 9 degrees east - with good signal strength on a 1 m dish aligned to Eutelsat 10.
In fact, since 9B has a higher power output than Eutelsat 10, wouldn't it be good if EUMETSAT used this satellite - also?

Regards,
John.

++++++++++++++++++++

In a message dated 20/06/2019 19:28:11 GMT Standard Time, gm8arv@... writes:

Yes, the GOES-15 is purely a transition arrangement, which is coming to an
end - perhaps before the second half of the year.  In any case, there are
some issues with processing the data in real-time (the location information
is sent /after/ the data, not before!).

Each Metop satellite offers data named like:

  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPA+AVHRR
  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPB+AVHRR
  W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPC+AVHRR

These are air motion vectors, and the Metop Manager will handle them if the
Process AVHRR polar winds box is checked, so if you're getting that data you
need a third Metop Manager for Metop-C.  That's on EPS-10 as it's from the
AVHRR instrument.

The highest resolution Sentinel data is from Sentinel-2, and that's not on
EUMETCast.  The Sentinel-3 data (which is) is 300m resolution.  I don't know
whether anyone is still taking Sentinel data on a regular basis as it's
readily available in image form from the Internet, and various folk have
written quite complex processing scripts to make the most of the data.  Folk
here have written scripts to keep data for a particular area of interest
up-to-date.

Interestingly, the data flow from the next generation of satellites is
reported to be ten times what we have at the moment.  How many transponders
on which satellites will that take!

Re: Configuring TC V2.14.4 .ini's.

David J Taylor
 

David,

Thanks again for as usual interesting and informative responses.

Ah, right, the highest Sentinel data is not disseminated by EUMETCast, however 300 m is pretty good.
But one step at a time?


Interestingly, the data flow from the next generation of satellites is
reported to be ten times what we have at the moment. How many transponders
on which satellites will that take!
Well, as you know I'm receiving Eutelsat 9B - at 9 degrees east - with good signal strength on a 1 m dish aligned to Eutelsat 10.
In fact, since 9B has a higher power output than Eutelsat 10, wouldn't it be good if EUMETSAT used this satellite - also?

Regards,
John.
================================

John,

Yes, there is so much data now that "one step at a time" is definitely a good idea! To that end, I'm not convinced that the catch-all entry in the channels list is a good idea, in fact you might almost argue that turning everything off and then asking "Where is such-and-such data?" might be a better way of working.

I don't know what EUMETSAT are planning for future satellite capacity, but something with a few more dB of signal, especially at the fringes of the coverage, would be most welcome.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv

Re: Configuring TC V2.14.4 .ini's.

Ian Deans
 

On 21/06/2019 12:26, geojohnt via Groups.Io wrote:

In fact, since 9B has a higher power output than Eutelsat 10, wouldn't it be good if EUMETSAT used this satellite - also?
Regards,
John.
=========================================================

John, they did use the satellite at 9 degrees for a while until the move to 10 degrees --- wish they would move back !!!!

Over the last few months I have seen a slow deterioration in the signal. In good conditions I could get 13.3 to 13.7 at various times of the day with a 1.1 metre dish, which was good for north of Dundee. Now however I am only seeing 12.8 to 13.2 and my dish is correctly aligned ---
disappointing.

Regards
Ian.

Re: Waiting for Segments in AVHRR

GERARD BOON
 

hi Andy,

Your issue resolved yet?

Gerard

Re: Waiting for Segments in AVHRR

David J Taylor
 

Hi,

I have been successfully downloading data from GEO16 & 17 using David's GoesAbiManager and have two instances running as he suggested grabbing data from "C:\EUMETCast\received\hvs-1\default". Have also put together some what I think are fantastic animations using GeoSatSignal as well. I have also successfully decoded what I believe is SEVIRI using MSG Data Manager from "C:\EUMETCast\received\bas\default"

EUTMESAT have just enabled NOAA19,METOPA,B &C as Basic Service and I have pointed AVHRR Manager to C:\EUMETCast\received\bas\default" but when I click Start the green gif shows and I just see waiting for segments. I have had this running for about 3 hours but not sure if I am just not waiting long enough? In teh raw folder, I have seen one file type which appears to reference METOPA in C:\EUMETCast\received\bas\default" named "W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPA+AMSUA_C_EUMC_20190617133423_65691_eps_o_l1.bin" and another in C:\EUMETCast\received\hvs-1\default which is of the file type "W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPC+GRAS_C_EUMR_20190617135520_03162_eps_t_l1.bin".

I've got the Kepler data updated in WKTrack (can I use this instead of my Yaesu FT818 instead of WXtoIMG as well?) and the ground station is showing along with the pass view in AVHRR.

I know this is probably a "schoolboy" question but I am struggling to see what I am doing wrong? There is nothing in the AVHRR event log tab.

I've only been doing this for about a month and this a sharp learning curve for me.

Thanks

Andy
===============================

Andy,

I've only just seen this message.

Files like: W_XX-EUMETSAT-Darmstadt,SOUNDING+SATELLITE,METOPA+AMSUA are ones which can be managed with the Metop Manager, continuous world-wide coverage. Those files are "sounding" data, microwave measurements of the atmosphere.

You mention the "AVHRR (Manager) Event Log tab". This program manages the EARS data - near real-time data over an extended Europe area. The EARS data is available for all three Metop satellites, and NOAA-19 too. The files come on Data Channel 1.

Yes, there is a lot of data, and I sometimes find it difficult to remember which data is on which channel! You've found the right place to ask for peer support, though.

Cheers,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv