Hi Miguel,
I will try to explain further.
Coupla is the function that runs to adjust the radiation components where
Atmospheric forecast data overlaps with the station data. It normally runs from
8 hours back until the last observation data. Therefore the initial temperature
profile, itp should be made for the starting point of Coupla, i.e. 8 hours back
(defined as nDeltaTIndice in the array).
Balanc is run into the future, so to speak. Therefore the initial temperature,
itp profile should be for the last observation (defined as nLenObservation in
the array).
Hope this makes it clearer!
Best regards,
Esben
________________________________
Från: Miguel Tremblay <[email protected]>
Till: Esben Almqvist <[email protected]>
Kopia: [email protected]
Skickat: måndag, 21 november 2011 22:06
Ämne: Re: [Metro-developers] Initial
Hi Esben,
I've been quite busy in the last days.
Hopefully, I will have time to look at this later this week.
Best regards,
Miguel
--
Miguel Tremblay
Développeur METRo - METRo developer
https://gna.org/projects/metro/
Physicien - Physicist
Environnement Canada - Environment Canada
On 11/18/2011 04:00 PM, Esben Almqvist wrote:
Hi all!
>
>
>I have looked a bit at the code and found something that may be a bug.
>The function Initial is run before Coupla. It generates a temperature profile,
>dpItp which is used in Coupla and Balanc. Now the temperature at the beginning
>of Coupla should be different to the one when Balanc is run. As far as I can
>see, dpItp has values from the last observation. This ok for Balanc, but in
>Coupla I think it should be at the starting point of Coupla,
>i.e. nDeltaTIndice.
>
>
>So as far as I can see Initial should be run twice. Once for Coupla and once
>for Balanc. The following code is used to run Initial in macadam.c.
>
>
>330 f77name(initial)(dpItp , (dpRTO+1), (dpDTO+1), (dpTAO+1), &nOne, \
>331 &nLenObservation, &stTemperatureDepth.nSize,\
>332 &nIR40, &bFlat, npSwo, dpCapacity, dpConductivity);
>
>
>To run it for Coupla I suggest the following change:
>
>
>330 f77name(initial)(dpItp , (dpRTO+1), (dpDTO+1), (dpTAO+1), &nOne, \
>331
> &nDeltaTIndice, &stTemperatureDepth.nSize,\
>332 &nIR40, &bFlat, npSwo, dpCapacity, dpConductivity);
>
>
>On row 331 nLenObservation was changed to nDeltaTIndice.
>
>
>Am I thinking correctly?
>
>
>Best wishes of a good weekend,
>
>
>Esben
>
>
>
>________________________________
> Från: Miguel Tremblay <[email protected]>
>Till: Jonathan Rutz <[email protected]>
>Kopia: [email protected]
>Skickat: tisdag, 14 juni 2011 20:26
>Ämne: Re: [Metro-developers] SSI Code in METRo
>
>
>On 06/12/2011 10:24 PM, Jonathan Rutz wrote:
>[Metro-developers] SSI Code in METRo
>>Hello METRo Developers,
>>
>>One of the METRo inputs is the "Road Condition"
expressed in SSI code.
>>I've had some difficulty locating a good listing
of this code; would you
>>have the link to a good explanation?
>>
>>Thanks,
>>JonR
>>
Hi Jonathan,
>
>Did you look at this page ?
>http://documentation.wikia.com/wiki/Road_condition_%28METRo%29
>
>
>Miguel Tremblay
>METRo developer
>
>_______________________________________________
>METRo-developers mailing list
>[email protected]
>https://mail.gna.org/listinfo/metro-developers
>_______________________________________________
METRo-developers mailing list
[email protected]
https://mail.gna.org/listinfo/metro-developers
