Date   

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 GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

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@blueyonder.co.uk
Twitter: @gm8arv


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


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.


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.


Re: cast-client-channels_xxxx.ini

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

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@blueyonder.co.uk
Twitter: @gm8arv


Re: Tellicast V2.4.4 'configuration.'

David J Taylor GM8ARV 🏴󠁧󠁢󠁳󠁣󠁴󠁿 🇪🇺
 

Hello All,

Goodness, I do feel like and old duffer!
[]
And, would somebody be kind enough to send me a sample/suggested HVS-1 'rcvd.channels.ini - as was, as a guide.


Much appreciated,

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

John,

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.

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


cast-client-channels_xxxx.ini

geojohnt@...
 

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.



Waiting for Segments in AVHRR

Andy Clarke
 

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


Re: Tellicast V2.4.4 'configuration.'

R. Alblas
 

John,

you can try/stop this any time. The only thing is that you need to enable all channels you would like to choose from, and if you decide not to use this program you need comment out channels not to receive as usual. (The original recv-channels.ini or cast-client-channels_bas.ini etc files are not touched by the program, just used.)

Rob.

On 06/17/2019 02:07 PM, geojohnt via Groups.Io wrote:
Hello Rob,

Thanks for that.

If/when, I get everything sorted out - and another receiver for HVS-2 and Sentinel,  - and probably by then needing a 2nd PC, I'll look at tidying things up.
Although I guess I should get that done now?

Best wishes,
John.

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

In a message dated 16/06/2019 21:36:16 GMT Standard Time, sat@... writes:

FYI:
There is a program 'ecast_chansel' which enables you to (de)select channels in an easy way. For each channel you can also define a nickname, so e.g.

EPS-10 is shown as METOP
EUMETSAT Data Channel 5 is shown as MSG RSS

or whatever you want.
For Linux and Windows.
See:

http://www.alblas.demon.nl/wsat/software/ecast_sel.html

Rob.


On 06/16/2019 01:15 PM, geojohnt via Groups.Io wrote:
John,

Hurrah! It's not just me?

Thanks for brightening up my day.

Regards,
John.

_________________

In a message dated 16/06/2019 11:56:08 GMT Standard Time, g3pha.morris@... writes:

Greetings John, Yes I have often wondered why EUMETCast don't identify which satellite
is allied to which channel in their listing. Would be most useful. John Morris.


Re: Tellicast V2.4.4 'configuration.'

geojohnt@...
 

Hello Rob,

Thanks for that.

If/when, I get everything sorted out - and another receiver for HVS-2 and Sentinel,  - and probably by then needing a 2nd PC, I'll look at tidying things up.
Although I guess I should get that done now?

Best wishes,
John.

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

In a message dated 16/06/2019 21:36:16 GMT Standard Time, sat@... writes:

FYI:
There is a program 'ecast_chansel' which enables you to (de)select channels in an easy way. For each channel you can also define a nickname, so e.g.

EPS-10 is shown as METOP
EUMETSAT Data Channel 5 is shown as MSG RSS

or whatever you want.
For Linux and Windows.
See:

http://www.alblas.demon.nl/wsat/software/ecast_sel.html

Rob.


On 06/16/2019 01:15 PM, geojohnt via Groups.Io wrote:
John,

Hurrah! It's not just me?

Thanks for brightening up my day.

Regards,
John.

_________________

In a message dated 16/06/2019 11:56:08 GMT Standard Time, g3pha.morris@... writes:

Greetings John, Yes I have often wondered why EUMETCast don't identify which satellite
is allied to which channel in their listing. Would be most useful. John Morris.


Re: Tellicast V2.4.4 'configuration.'

R. Alblas
 

FYI:
There is a program 'ecast_chansel' which enables you to (de)select channels in an easy way. For each channel you can also define a nickname, so e.g.

EPS-10 is shown as METOP
EUMETSAT Data Channel 5 is shown as MSG RSS

or whatever you want.
For Linux and Windows.
See:

http://www.alblas.demon.nl/wsat/software/ecast_sel.html

Rob.


On 06/16/2019 01:15 PM, geojohnt via Groups.Io wrote:
John,

Hurrah! It's not just me?

Thanks for brightening up my day.

Regards,
John.

_________________

In a message dated 16/06/2019 11:56:08 GMT Standard Time, g3pha.morris@... writes:

Greetings John, Yes I have often wondered why EUMETCast don't identify which satellite
is allied to which channel in their listing. Would be most useful. John Morris.


Re: formally [MSG-1] Tellicast V2.4.4 'configuration.' - now TC V2.14.4 'configuration.'

Douglas Deans
 

On 16/06/2019 12:13, geojohnt via Groups.Io wrote:
Hello Hugo,

The following sats are disseminated from the following folders :
E1H-EPS-10 : Metop C
E1H-RDS-1 : NPP (VIIRS-M)
E1H-TPG-1 : GOES-16
E1H-TPG-2 : Himawari-8
E1H-TPG-3 : GOES-17
E1H-TPG-4 : GOES-15 in nc format
Hope this helps,
Thanks very much for the useful information.
Right, gosh, several more satellites to 'process.'
I knew of course that GOES had 'moved stream' but, dare I say, wasn't sure 'where.'
So I need to set up my cast-client-channels_hvs-1.ini to send these individual data to specific files and not default as it is at present.
And this will be the case in cast-client-channels_bas.ini, as I'm still using TC V2.4.4a for BS.
Now, I copied a 4th MDM and named it Himawari and directed it to 'default' and it's processing and displaying Himawari data OK.
It seems to me from the above that I'll need a second copy of AVHRR Manager just for Metop C (at the moment)?
GOES 16 and 17 use ABI format (I believe) and I think David has a modified MDM for that.
So that leaves NPP VIIRS.
Er, is there a programme for that?
Best wishes,
John.
========================================================================

Yes Hugo's program EUMETCastView does NPP VIIRS and NOAA 20 VIIRS and indeed does all the satellites above in one program if you are interested. It does not do animations though but Hugo has said that he intends to add it to the program sometime.

Regards,
Douglas.


Re: Tellicast V2.4.4 'configuration.'

geojohnt@...
 

John,

Hurrah! It's not just me?

Thanks for brightening up my day.

Regards,
John.

_________________

In a message dated 16/06/2019 11:56:08 GMT Standard Time, g3pha.morris@... writes:

Greetings John, Yes I have often wondered why EUMETCast don't identify which satellite
is allied to which channel in their listing. Would be most useful. John Morris.


Re: formally [MSG-1] Tellicast V2.4.4 'configuration.' - now TC V2.14.4 'configuration.'

geojohnt@...
 

Hello Hugo,

>The following sats are disseminated from the following folders :
>E1H-EPS-10 : Metop C
>E1H-RDS-1 : NPP (VIIRS-M)
>E1H-TPG-1 : GOES-16
>E1H-TPG-2 : Himawari-8
>E1H-TPG-3 : GOES-17
>E1H-TPG-4 : GOES-15 in nc format

>Hope this helps,

Thanks very much for the useful information.

Right, gosh, several more satellites to 'process.'
I knew of course that GOES had 'moved stream' but, dare I say, wasn't sure 'where.'

So I need to set up my cast-client-channels_hvs-1.ini to send these individual data to specific files and not default as it is at present.

And this will be the case in cast-client-channels_bas.ini, as I'm still using TC V2.4.4a for BS.

Now, I copied a 4th MDM and named it Himawari and directed it to 'default' and it's processing and displaying Himawari data OK.

It seems to me from the above that I'll need a second copy of AVHRR Manager just for Metop C (at the moment)?
GOES 16 and 17 use ABI format (I believe) and I think David has a modified MDM for that.

So that leaves NPP VIIRS.
Er, is there a programme for that?

Best wishes,
John.




Re: Tellicast V2.4.4 'configuration.'

g3pha.morris@btinternet.com
 

Greetings John, Yes I have often wondered why EUMETCast don't identify which satellite
is allied to which channel in their listing. Would be most useful. John Morris.

On Saturday, 15 June 2019, 15:40:54 BST, geojohnt via Groups.Io <geojohnt@...> wrote:


Hello All,

Goodness, I do feel like and old duffer!

Having just updated all my SatSignal programmes and seeing a Himawari tab on the latest MDM I'm tentatively
experimenting with HVS-1 on Tellicast V2.14.4 running in parallel with TC V2.4.4a - for BS.

Now, my - what was recv.channel.ini - in the old version is 'empty' on the new version::

+++++++++
[channel]
name=*
receive_buffer_size=8000000
target_directory=\EUMETCast\received\hvs-1\default
tmp_directory=\EUMETCast\tmp\hvs-1

# DO NOT EDIT OR DELETE THE FOLLOWING SECTION!!!
[channel]
name=WWW-Channel
receive_buffer_size=8000000
target_directory=www/eumetsat
tmp_directory=www/tmp/
+++++++++

I've let HVS-1 run for around 3 hours and HTML Shell has shown these channels have been active during that time:
E1H-TPG2
E1H-TPL 1 
E1H-TPG 4E1H-EPS 10
E1H-RDS 1
TSL HVS-1

Looking in my EUMETCast > received > hvs-1 > default folder I have (5.44 GB):

goes 15 BZ2 files
(lots of) IMG_DK01B01 and DK01B01/B06/B09/B10/B11/B12/B14/B16, BZ2 files
IMG_DK01IR1/IR2/IR3/IR4, BZ2 files
IMG_DK01VIZ, BZ2 files
SVMC_npp_(date)_txxxxx_exxxxx, H5 files
W_XX-EUMETSAT_Darmstadt, SOUNDING...., BIN files

????

Now, I don't know what satellites VIS/IR data HVS-1 is disseminating and I've looked on David's website and
and found under 'Using EUMETCast' a table detailing Channel Names  - BS, HVS-1, HVS-2.
And a link to EUMETSAT's channel naming pages.

However, it/they, are not always explicit - saying things like third party geo rather than naming the individual satellites.

So, sorry for being so dumb, but what satellites VIS and IR data is disseminated on HVS-1 that isn't disseminated on BS?
And, would somebody be kind enough to send me a sample/suggested HVS-1 'rcvd.channels.ini - as was, as a guide.

Much appreciated,

Regards,
John Tellick

 




 


Re: formally [MSG-1] Tellicast V2.4.4 'configuration.' - now TC V2.14.4 'configuration.'

geojohnt@...
 

Hello All,

I told you I was an old duffer - the Subject should have been Tellicast V2.14.4 'configuration.'

Regards,
John

In a message dated 15/06/2019 15:40:53 GMT Standard Time, geojohnt@... writes:

Hello All,

Goodness, I do feel like and old duffer!

Having just updated all my SatSignal programmes and seeing a Himawari tab on the latest MDM I'm tentatively
experimenting with HVS-1 on Tellicast V2.14.4 running in parallel with TC V2.4.4a - for BS.

Now, my - what was recv.channel.ini - in the old version is 'empty' on the new version::

+++++++++
[channel]
name=*
receive_buffer_size=8000000
target_directory=\EUMETCast\received\hvs-1\default
tmp_directory=\EUMETCast\tmp\hvs-1

# DO NOT EDIT OR DELETE THE FOLLOWING SECTION!!!
[channel]
name=WWW-Channel
receive_buffer_size=8000000
target_directory=www/eumetsat
tmp_directory=www/tmp/
+++++++++

I've let HVS-1 run for around 3 hours and HTML Shell has shown these channels have been active during that time:
E1H-TPG2
E1H-TPL 1 
E1H-TPG 4E1H-EPS 10
E1H-RDS 1
TSL HVS-1

Looking in my EUMETCast > received > hvs-1 > default folder I have (5.44 GB):

goes 15 BZ2 files
(lots of) IMG_DK01B01 and DK01B01/B06/B09/B10/B11/B12/B14/B16, BZ2 files
IMG_DK01IR1/IR2/IR3/IR4, BZ2 files
IMG_DK01VIZ, BZ2 files
SVMC_npp_(date)_txxxxx_exxxxx, H5 files
W_XX-EUMETSAT_Darmstadt, SOUNDING...., BIN files

????

Now, I don't know what satellites VIS/IR data HVS-1 is disseminating and I've looked on David's website and
and found under 'Using EUMETCast' a table detailing Channel Names  - BS, HVS-1, HVS-2.
And a link to EUMETSAT's channel naming pages.

However, it/they, are not always explicit - saying things like third party geo rather than naming the individual satellites.

So, sorry for being so dumb, but what satellites VIS and IR data is disseminated on HVS-1 that isn't disseminated on BS?
And, would somebody be kind enough to send me a sample/suggested HVS-1 'rcvd.channels.ini - as was, as a guide.

Much appreciated,

Regards,
John Tellick

 






Re: Tellicast V2.4.4 'configuration.'

Hugo
 

Hi John,

The following sats are disseminated from the following folders :
E1H-EPS-10 : Metop C
E1H-RDS-1 : NPP (VIIRS-M)
E1H-TPG-1 : GOES-16
E1H-TPG-2 : Himawari-8
E1H-TPG-3 : GOES-17
E1H-TPG-4 : GOES-15 in nc format

Hope this helps,

Hugo


Tellicast V2.4.4 'configuration.'

geojohnt@...
 

Hello All,

Goodness, I do feel like and old duffer!

Having just updated all my SatSignal programmes and seeing a Himawari tab on the latest MDM I'm tentatively
experimenting with HVS-1 on Tellicast V2.14.4 running in parallel with TC V2.4.4a - for BS.

Now, my - what was recv.channel.ini - in the old version is 'empty' on the new version::

+++++++++
[channel]
name=*
receive_buffer_size=8000000
target_directory=\EUMETCast\received\hvs-1\default
tmp_directory=\EUMETCast\tmp\hvs-1

# DO NOT EDIT OR DELETE THE FOLLOWING SECTION!!!
[channel]
name=WWW-Channel
receive_buffer_size=8000000
target_directory=www/eumetsat
tmp_directory=www/tmp/
+++++++++

I've let HVS-1 run for around 3 hours and HTML Shell has shown these channels have been active during that time:
E1H-TPG2
E1H-TPL 1 
E1H-TPG 4E1H-EPS 10
E1H-RDS 1
TSL HVS-1

Looking in my EUMETCast > received > hvs-1 > default folder I have (5.44 GB):

goes 15 BZ2 files
(lots of) IMG_DK01B01 and DK01B01/B06/B09/B10/B11/B12/B14/B16, BZ2 files
IMG_DK01IR1/IR2/IR3/IR4, BZ2 files
IMG_DK01VIZ, BZ2 files
SVMC_npp_(date)_txxxxx_exxxxx, H5 files
W_XX-EUMETSAT_Darmstadt, SOUNDING...., BIN files

????

Now, I don't know what satellites VIS/IR data HVS-1 is disseminating and I've looked on David's website and
and found under 'Using EUMETCast' a table detailing Channel Names  - BS, HVS-1, HVS-2.
And a link to EUMETSAT's channel naming pages.

However, it/they, are not always explicit - saying things like third party geo rather than naming the individual satellites.

So, sorry for being so dumb, but what satellites VIS and IR data is disseminated on HVS-1 that isn't disseminated on BS?
And, would somebody be kind enough to send me a sample/suggested HVS-1 'rcvd.channels.ini - as was, as a guide.

Much appreciated,

Regards,
John Tellick

 




 


Re: Oh My Goodness - recovered HDD space!

geojohnt@...
 

David,

Thanks also for the advice.

Yes, I've got "Save in compact format" ticked - and "Save thumbnails."
"Combined data retention period" set to 4.
And yes, I (now) have V4.1.2.246.

Regards,
John.

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

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

John,
[]
Within the AVHRR Manager clear the ???Save segment files??? box
[]
Hope this helps,
Ferdinand
=====================================

Good advice, Ferdinand, to which I would add:

- use the "save in compact format" option
- set the "Combined data retention period" to an appropriate value
- ensure that you are using the current version V4.1.2

2661 - 2680 of 31105