Esben Almqvist wrote:
> Hi developers!
> 
> I have been looking at the way errors are handled in Metro. It seems that 
> Metro prefers to remove data as opposed to interpolate missing values. For ex 
> if the data at 13.00 and 14.00 are missing, Metro will start running from the 
> next proper value, in this case at 15.00. Am I interpreting this correctly? 
> However, it seems that the above is not always true. Sometimes error values 
> are interpolated. Does it matter if the error code of Metro (9999) is used or 
> an out of bounds value (-999)? 
> I suppose that if the input data is missing 30 hours ago, it does not make a 
> very large difference compared to if the data is missing during the coupling 
> phase. Does the model distinguish between important data and not so important 
> data? 
> Do you have a good description of how errors are handled?
> Thanks!
> Esben
> 

Hi Esben,

I am not sure that I understand what the problem is.

Are you talking about observation or atmospheric forecast data, or both?

In the atmospheric forecast, the missing data are interpolated. However, 
  data in the atmospheric forecast file at the beginning of period for 
the roadcast must be valid. If not, the next time step of the 
atmospheric forecast is used.

For the observation, in the coupling phase, if the data is invalid, the 
atmospheric forecast value is used if it covers this period. If not, the 
data are in the first place removed (this is done in 
metro_preprocess_qa_qc_observation.py) and then interpolated (in 
metro_preprocess_interpol_observation.py).  The same is done with 
forecast values (metro_preprocess_qa_qc_forecast.py and 
metro_preprocess_interpol_forecast.py).

Is this an answer to your question?

Best regards,

-- 
Miguel Tremblay
Physicien - Physicist
Centre météorologique canadien - Canadian meteorological centre (CMC)
Environnement Canada - Environment Canada
http://www.ec.gc.ca/

2121 Trans-Canada N. Suite 228 Téléphone/Phone: 514-421-4729
Dorval, Québec                 Fax: 514-421-4679
CANADA H9P 1J3                 courriel/email: [EMAIL PROTECTED]

_______________________________________________
METRo-developers mailing list
[email protected]
https://mail.gna.org/listinfo/metro-developers

Reply via email to