[RegCNET] Lateral Boundary Treatment (fwd)
Richard Anyah
anyah at cep.rutgers.edu
Thu Oct 2 18:02:52 CEST 2008
Hi Bi,
I am using Intel 64.
I will let you know if it works using Diego's advice.
Richard
>
> Hi, Richard:
>
> Which 64-bit CPU ? AMD64 or Intel 64 ?
>
> I know the ../../Commons/env/liblinux64/libnetcdf.a works with
> SGI Intel 64-bit Cluster, and ../../Commons/env/liblinuxamd64/libnetcdf.a
> works with our AMD64 cluster (with pgf90).
>
> Anyway, it seems to me that the netcdf library got from unidata is
> always the best one. Can you try to find the right one from
> http://www.unidata.ucar.edu/ ?
>
> By the way, once you find the right one, could you please send me a copy?
>
> Thanks and Regards,
> Xunqiang Bi
>
> On Thu, 2 Oct 2008, Richard Anyah wrote:
>
>> I am getting this error while compiling RegCM3 using ifort compiler on
>> (64-bit)Linux redhat 5.0 Enterprise.
>>
>> ld: skipping incompatible ../../Commons/env/liblinux64//libnetcdf.a when
>> searching for -lnetcdf
>>
>> I hope somebody has come across the same problem before and can advice
>> how
>> to resolve it.
>>
>> Richard
>>
>>
>>
>>>
>>> ---------- Forwarded message ----------
>>> Date: Thu, 25 Sep 2008 12:51:16 +0200 (CEST)
>>> From: XUNQIANG BI <bixq at ictp.it>
>>> To: Hang Wai Tong <hangwai127 at yahoo.com.hk>
>>> Subject: Re: [RegCNET] Lateral Boundary Treatment
>>>
>>>
>>> On Thu, 25 Sep 2008, Hang Wai Tong wrote:
>>>
>>>> Could you please give me more example on how to tune anudg ?
>>>> For example, if i increase the buffer zone size, how should I
>>>> tune anudg to balance the LBC forcing?
>>>>
>>>> Tong Hang Wai
>>>
>>> When I say to balance the LBC forcing, I mean that you have two
>>> experiments: for example,
>>>
>>> one 50km resolution domain (100*80), with 12 grid buffer zone; and
>>> one 25km resolution domain (200*160), with 23 grid buffer zone.
>>>
>>> In this case, you can not use the same anudg for the two run and
>>> make the comparision between them. Instead, you need to increase
>>> the anudg in the 2nd experiment.
>>>
>>> See the lines in nudge,F
>>>
>>> nudge.F: xfune(mm,kk)= dexp(-dble(mm-2)/anudg(kk))
>>> nudge.F: xfune(mm,kk)= dexp(-dble(mm-2)/anudg(kk))
>>> nudge.F: xfune(mm,kk)= dexp(-dble(mm-2)/anudg(kk))
>>> nudge.F: xfune(mm,kk)= dexp(-dble(mm-2)/anudg(kk))
>>> nudge.F: xfune(mm,kk)= dexp(-dble(mm-2)/anudg(kk))
>>>
>>> At the same location, you should get roughly the same xfune,
>>>
>>> Regards.
>>> Bi Xunqiang
>>>>
>>>> --- 2008å¹´9æ25æ¥ ææåï¼XUNQIANG BI <bixq at ictp.it> 寫éï¹
>>>> å¯ä»¶äºº: XUNQIANG BI <bixq at ictp.it>
>>>> 主é¡: Re: [RegCNET] Lateral Boundary Treatment
>>>> æ¶ä»¶äºº: "guogl" <guogl at ieecas.cn>
>>>> å¯æ¬(CC): regcnet at lists.ictp.it
>>>> æ¥æ: 2008 9 25 ææå ä¸å 3:24
>>>>
>>>> Hi, Guo:
>>>>
>>>> In parame file under RegCM/Main, the two parameters, nspgx and nspgx,
>>>> decide the buffer zone width.
>>>>
>>>> In param.F, the array anudg (with size of kx) decides the weight
>>>> factor of the LBC forcing. If you increase the size of buffer zone,
>>>> you need also tuning this array to balance the strength of LBC
>>>> forcing.
>>>>
>>>> Hope it helps,
>>>> Bi Xunqiang
>>>>
>>>> On Thu, 25 Sep 2008, [gb2312] guogl wrote:
>>>>
>>>>> Hi
>>>>> How to modify the value of "buffer area" when treating Lateral
>>>> Boundary? Can you tell me which file I should modify? Thanks!
>>>>>
>>>>>
>>>> GuoLong Guo
>>>>>
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> Dr. Xunqiang Bi email:bixq at ictp.it
>>> Earth System Physics Group
>>> The Abdus Salam ICTP
>>> Strada Costiera, 11
>>> P.O. BOX 586, 34100 Trieste, ITALY
>>> Tel: +39-040-2240302 Fax: +39-040-2240449
>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~_______________________________________________
>>> RegCNET mailing list
>>> RegCNET at lists.ictp.it
>>> https://lists.ictp.it/mailman/listinfo/regcnet
>>
>>
>>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dr. Xunqiang Bi email:bixq at ictp.it
> Earth System Physics Group
> The Abdus Salam ICTP
> Strada Costiera, 11
> P.O. BOX 586, 34100 Trieste, ITALY
> Tel: +39-040-2240302 Fax: +39-040-2240449
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
More information about the RegCNET
mailing list