Topics

Problem processing HRV segment 17 on cycle 0900 October 13


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

--- In MSG-1@yahoogroups.com, Arne van Belle <a.van.belle@h...>
wrote:
Hello All,

I had a problem while processing HRV segment 17 from cycle 0900.
MDM (version 1.2.2.231) was halting with CPU usage 99%.
Arne,

That segment was faulty, in that the header data was wrong. I have
changed my program to fix that problem. A beta update(V1.2.4.236)
is available from my Web site.

I would have thought that the Tellique software would have not
delivered files incorrectly. However, there is no overall checksum
on the file, so it is impossible to be sure that the file is
intact. Obviously, in the system design architecture, it is assumed
that the transmission is error free at that point.

Cheers,
David


a_van_belle
 

Thanks David for your reply.

Must have been a local problem I guess.
Do have "Wait for segments" on.
I will send the faulty segment and will update to the latest MDM
version.

Greetings,
Arne van Belle


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

My H-000-MSG1__.......HRV....17 ...200310130900-C filesize is
308.934 bytes.

Can anyone that still has this raw data confirm if the filesize is
the same ?

Arne, if you have the data causing the hang, please send it for
testing. The current and released version is V1.2.2.235, by the
way.

I also noticed that HRV segment 1 from cycle 0300 October 13 was
still in the received map and this segment is missing in the 0300
HRV image. But this segment is not reported as missing segment. A
look at the Tellique log does show that HRV segment 1 cycle 0300
came in before HRV segment 24 cycle 0245 !

Can anyone confirm the missing segment 1 in HRV cycle 0300 ?
Arne, the image shows valid south-pole data here, I would not have
said that the bottom segment was missing or in any way truncated. I
agree with you on the timing, although such a sequence is not
unusual:

VRB:2003-10-13 03:03:57.824:Delivered file `received&#92;H-000-MSG1__-
MSG1________-HRV______-000001___-200310130300-C_' id
3f8a161b00237f07 from channel `EUMETSAT Data Channel 2'

VRB:2003-10-13 03:04:27.697:Delivered file `received&#92;H-000-MSG1__-
MSG1________-HRV______-000024___-200310130245-C_' id
3f8a162900237f29 from channel `EUMETSAT Data Channel 2'

If the program gets incomplete data - the actual data length does
not match the neader for example, or there is a data inconsistency,
most likely it will not attempt to decode the data into an image,
but at that point it will have already recorded that the segment was
received. I.e. the quality or otherwise of the segment does not
stop it being recorded.

Fuller detail on the segment 1 file:

VRB:2003-10-13 03:03:55.571:Received announcement for channel
`EUMETSAT Data Channel 2', address 224.223.222.21:2511 (subscribed)
VRB:2003-10-13 03:03:55.912:Connecting to data channel `EUMETSAT
Data Channel 2', address 224.223.222.21:2511 (invited)
MSG:2003-10-13 03:03:56.402:Connect to data channel `EUMETSAT Data
Channel 2', address 224.223.222.21:2511 completed (invited)
VRB:2003-10-13 03:03:57.464:Received filelist 3f8a161b00237f08 on
channel `EUMETSAT Data Channel 2'
VRB:2003-10-13 03:03:57.754:Received file 3f8a161b00237f07 on
channel `EUMETSAT Data Channel 2'
MSG:2003-10-13 03:03:57.754:All files of filelist 3f8a161b00237f08
received
VRB:2003-10-13 03:03:57.824:Delivered file `received&#92;H-000-MSG1__-
MSG1________-HRV______-000001___-200310130300-C_' id
3f8a161b00237f07 from channel `EUMETSAT Data Channel 2'
MSG:2003-10-13 03:03:57.824:Delivered all files of filelist
3f8a161b00237f08 from channel `EUMETSAT Data Channel 2'
VRB:2003-10-13 03:03:59.657:Received announcement for channel
`EUMETSAT Data Channel 2', address 224.223.222.21:2511 (subscribed)
VRB:2003-10-13 03:04:00.178:Connecting to data channel `EUMETSAT
Data Channel 2', address 224.223.222.21:2511 (invited)
VRB:2003-10-13 03:04:00.418:Disconnecting from data channel
`EUMETSAT Data Channel 2', address 224.223.222.21:2511 (channel
closed)
MSG:2003-10-13 03:04:00.448:Disconnect from data channel `EUMETSAT
Data Channel 2', address 224.223.222.21:2511 completed (channel
closed)


a_van_belle
 

Hello All,

I had a problem while processing HRV segment 17 from cycle 0900.
MDM (version 122.231) was halting with CPU usage 99%.

After an hour there wasn't any progress so I killed the process.
A reprocessing caused a hang at the same segment and had to be killed
again.
Only removing this segment and reprocessing solved the problem.

My H-000-MSG1__.......HRV....17 ...200310130900-C filesize is 308.934
bytes.

Can anyone that still has this raw data confirm if the filesize is the same
?


I also noticed that HRV segment 1 from cycle 0300 October 13 was still in
the received map and this segment is missing in the 0300 HRV image.
But this segment is not reported as missing segment. A look at the Tellique
log does show that HRV segment 1 cycle 0300 came in before HRV segment 24
cycle 0245 !

Can anyone confirm the missing segment 1 in HRV cycle 0300 ?


Greetings,
Arne van Belle