Qc2 Flag Specification

DRAFT

fw

For flagging spatial analysis of the available observation data.

Controlflag Setting	Description
fw=0	Ikke kontrollert
fw=1	Kontrollert. Funnet i orden
fw=2	Kontrollert. Observert verdis avvik fra beregnet verdi er større enn høy testverdi
fw=3	Kontrollert. Observert verdis avvik fra beregnet verdi er mindre enn lav testverdi
fw=4	Kontrollert. Observert verdis avvik fra beregnet verdi er større enn høyeste testverdi
fw=5	Kontrollert. Observert verdis avvik fra beregnet verdi er mindre enn laveste testverdi
fw=6	Original verdi mangler eller er forkastet av en annen QC2-kontroll. Interpolert/korrigert med beregnet verdi

(fw=7 Vi vil vurdere om interpolasjonsmetodikken (fw-kontrollen) selv kan forkaste en verdi. Foreløpig er vi litt tvilende til det, men holder muligheten åpen.)

The beregnet verdi/calculated value is the model value provided by th Qc2 algorithm used. The algorithm used is recorded in the “cfailed” string.

... To do: parse all flag group responses and document.

Dear Pål,
I respond to your two emails from the 17 February here together.
>Here you need to alter the check for flag f_fs being set into checking
>for the specific values of f_s which QC2 alone is able to set. fs=1,2,3
>should not imply qc2dDone=true, because fs=1,2,3 is set by QC1, not QC2.
>Similarly for the flag f_fd in qc2mDone.
Thank you for this input. I will include this in my branch of the kvalobs library code after which I will redo the regression testing etc, to see the effect on the flag generation.
> I guess you have done some kind of resetting of useinfo flags before
> running "setUseFlags(const kvControlInfo& cinfo) with the existing Qc2
> logic turned on"? If so, useinfo(7)=3,4 should not be reset, because the
> only place where these values are set is when decoding the original
> message (the values are set by the decoder).
Yes this explains a lot! I was just giving setUseFlags the value of the controlinfo and seeing what useinfo was generated without any prior initialisation of the useinfo. When I rerun the regression tests I will do something about this ... and maybe then the results will all be the same and it will be easier to later approve the update of the working libraries.
Thank you very much for the help.
Best regards, Paul
----- Original Message -----
Fra: "Pål Sannes" <Pal.Sannes@met.no>
Til: "Paul Emils Eglitis" <paule@met.no>
Kopi: "Lars Andresen" <larsa@met.no>, "Gabriel Kielland" <gabrielk@met.no>
Sendt: 17. februar 2010 16:26:37
Emne: Flag Testing for useinfo(7)
Pål Sannes wrote:
> Then at
> https://kvalobs.wiki.met.no/doku.php?id=kvoss:system:qc2:flag:regression
> there are a lot of observations where useinfo(7) has been changed from a
> positive value (3 or 4 - observasjon er meldt for tidlig/sent) into 0.
> This looks like a bug to me.
I guess you have done some kind of resetting of useinfo flags before
running "setUseFlags(const kvControlInfo& cinfo) with the existing Qc2
logic turned on"? If so, useinfo(7)=3,4 should not be reset, because the
only place where these values are set is when decoding the original
message (the values are set by the decoder).
The only values I have found for useinfo(7) in the Kvalobs database is
0, 3 and 4.
Pål
----- Videresent Melding -----
Fra: "Pål Sannes" <Pal.Sannes@met.no>
Til: "Paul Emils Eglitis" <paule@met.no>
Kopi: "Lars Andresen" <larsa@met.no>, "Gabriel Kielland" <gabrielk@met.no>, "Solfrid Agersten" <solfrid.agersten@met.no>
Sendt: 17. februar 2010 12:56:28
Emne: Re: Qc2 Flag and Cfailed settings - Flag Testing
Hi Paul,
I will update Flaggdokumentet with the new values for fw soon, but since
this will imply changes in setting of useinfo(2) also, I prefer to wait
with this until Vegard has implemented bug 1272 (I don't want to confuse
him with another unrelated change for useinfo(2)=2).
Regarding the last question in your email of 3 February, I noticed this
section in
https://kvalobs.wiki.met.no/doku.php?id=kvoss:system:qc2:flag:analysis
"The setUseFlags already anticipates the setting of user flags in
response to QC2 controls. However, most of the logic is commented out in
the operational code, as indicated below:
bool kvControlInfo::qc2dDone() const
{
return false;//flag( f_fs ) or flag( f_ftime ) or flag( f_fw ) or
flag( f_fstat );
}
...
bool kvControlInfo::qc2mDone() const
{
return false;//flag( f_fclim ) or flag( f_fd );
}
"
Here you need to alter the check for flag f_fs being set into checking
for the specific values of f_s which QC2 alone is able to set. fs=1,2,3
should not imply qc2dDone=true, because fs=1,2,3 is set by QC1, not QC2.
Similarly for the flag f_fd in qc2mDone.
Then at
https://kvalobs.wiki.met.no/doku.php?id=kvoss:system:qc2:flag:regression
there are a lot of observations where useinfo(7) has been changed from a
positive value (3 or 4 - observasjon er meldt for tidlig/sent) into 0.
This looks like a bug to me.
Pål
----- Original Message -----
Fra: "Pål Sannes" <Pal.Sannes@met.no>
Til: "Paul Emils Eglitis" <paule@met.no>
Kopi: "Lars Andresen" <larsa@met.no>, "Gabriel Kielland" <gabrielk@met.no>
Sendt: 17. februar 2010 16:26:37
Emne: Flag Testing for useinfo(7)
Pål Sannes wrote:
> Then at
> https://kvalobs.wiki.met.no/doku.php?id=kvoss:system:qc2:flag:regression
> there are a lot of observations where useinfo(7) has been changed from a
> positive value (3 or 4 - observasjon er meldt for tidlig/sent) into 0.
> This looks like a bug to me.
I guess you have done some kind of resetting of useinfo flags before
running "setUseFlags(const kvControlInfo& cinfo) with the existing Qc2
logic turned on"? If so, useinfo(7)=3,4 should not be reset, because the
only place where these values are set is when decoding the original
message (the values are set by the decoder).
The only values I have found for useinfo(7) in the Kvalobs database is
0, 3 and 4.
Pål