id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
91	MetDB extract problem	Dave Offiler	Dave Offiler	"MetDB extract apparantly failing to decode/return expected number of GPSRO records. This is happening for local Desktop RPC, Mike's private OPS and operational OPS (Adrian reports latter mainly for QU18z runs) since 10 Nov.

Raised urgent remedy INC am 13/11. Brian Barwell assigned and investgating. Looks like problem running out of array space decoding a particular profile (similar to early days when we had to restrict MetDB BUGT to no more than 375 samples per profile). Brian has dug out that the replication count for frequency (should be 1 or 3 for Corrected BA only or L1+L2+C) is a Very Large Number. Futher, an example offending profile was a GFZ GRACE one at 01:17utxc on 12/11.

Looking at the original GFZ ROPP-text file, this particular file has only the header present; all the Level NPoints values are zero and there is no data content to the file. From the log files,
the BUFR encoder has attempted to encode this occultation and has output a BUFR file of some 150-off bytes and the generated BUFR is techncially entirely valid. This is too much of a coincidence for the MetDB problem; slthough the BUFR is correct, and MetDB stores it OK, MetDB extract is gagging on it. Hence such cases need to be suppressed."	defect	closed	normal	1.0	ropp_io	0.9	fixed	BUFR MetDB