EXTPAR source code – in #11: EXTPAR / WebPEP

in #11: EXTPAR / WebPEP

<p> Dear Rolf </p> <p> Yes, the parameters for the <span class="caps"> SSO </span> parameterization are produced within <br/> EXTPAR. As far as the <span class="caps"> SSO </span> parameters are concerned, they relate to the <br/> slope of the orographie, to subgrid scale variability and the anisotropy <br/> of these fields. <br/> The <span class="caps"> EXTPAR </span> code is available for download when choosing the files tab <br/> if the <span class="caps"> EXTPAR </span> project has been selected. </p> <p> The <span class="caps"> SSO </span> fields over the ice shelf are computed as values for a sea <br/> point, i.e. all values are set to 0. </p> <p> What is the resolution of your grid, and what is the resolution of <br/> your alternative orography data set? For grid resolution finer than <br/> 3km you needn’t care about <span class="caps"> SSO </span> anyway, since the respective processes <br/> are resolved explicitly there. </p> <p> What is probably more relevant is the surface roughness that is also <br/> dependent on the variability of the subgrid scale orography and this <br/> is calculated in <span class="caps"> EXTPAR </span> , too. </p> <p> Regarding the filtering in int2lm, what filter options did you use there? </p> <p> I hope this answer is helpful to you. </p> <p> best regards </p> <p> Daniel Lüthi </p>

  @redc_migration in #90e47fa

<p> Dear Rolf </p> <p> Yes, the parameters for the <span class="caps"> SSO </span> parameterization are produced within <br/> EXTPAR. As far as the <span class="caps"> SSO </span> parameters are concerned, they relate to the <br/> slope of the orographie, to subgrid scale variability and the anisotropy <br/> of these fields. <br/> The <span class="caps"> EXTPAR </span> code is available for download when choosing the files tab <br/> if the <span class="caps"> EXTPAR </span> project has been selected. </p> <p> The <span class="caps"> SSO </span> fields over the ice shelf are computed as values for a sea <br/> point, i.e. all values are set to 0. </p> <p> What is the resolution of your grid, and what is the resolution of <br/> your alternative orography data set? For grid resolution finer than <br/> 3km you needn’t care about <span class="caps"> SSO </span> anyway, since the respective processes <br/> are resolved explicitly there. </p> <p> What is probably more relevant is the surface roughness that is also <br/> dependent on the variability of the subgrid scale orography and this <br/> is calculated in <span class="caps"> EXTPAR </span> , too. </p> <p> Regarding the filtering in int2lm, what filter options did you use there? </p> <p> I hope this answer is helpful to you. </p> <p> best regards </p> <p> Daniel Lüthi </p>
re replied

Dear Rolf

Yes, the parameters for the SSO parameterization are produced within
EXTPAR. As far as the SSO parameters are concerned, they relate to the
slope of the orographie, to subgrid scale variability and the anisotropy
of these fields.
The EXTPAR code is available for download when choosing the files tab
if the EXTPAR project has been selected.

The SSO fields over the ice shelf are computed as values for a sea
point, i.e. all values are set to 0.

What is the resolution of your grid, and what is the resolution of
your alternative orography data set? For grid resolution finer than
3km you needn’t care about SSO anyway, since the respective processes
are resolved explicitly there.

What is probably more relevant is the surface roughness that is also
dependent on the variability of the subgrid scale orography and this
is calculated in EXTPAR , too.

Regarding the filtering in int2lm, what filter options did you use there?

I hope this answer is helpful to you.

best regards

Daniel Lüthi

View in channel