[MITgcm-support] MITgcm-support Digest, Vol 216, Issue 17

[Hajoon Song]

Thank you all for the detailed information and suggestion!

Best,
Hajoon

> On Jun 25 2021, at 1:00 AM, mitgcm-support-request at mitgcm.org wrote:
> 
> Send MITgcm-support mailing list submissions to
> 	mitgcm-support at mitgcm.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> or, via email, send a message with subject or body 'help' to
> 	mitgcm-support-request at mitgcm.org
> 
> You can reach the person managing the list at
> 	mitgcm-support-owner at mitgcm.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MITgcm-support digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Using wind from exf in DIC package (Matthew Mazloff)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 24 Jun 2021 08:03:58 -0700
> From: Matthew Mazloff <mmazloff at ucsd.edu>
> To: mitgcm-support at mitgcm.org
> Subject: Re: [MITgcm-support] Using wind from exf in DIC package
> Message-ID: <8A60D9A3-6338-49E2-B3C6-019D287C0E46 at ucsd.edu>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Hajoon
> 
> Another option is that the BLING package does use EXF wspeed. 
> If you use the original bling 
> #define USE_BLING_V1
> in BLING_OPTIONS.h
> it is very similar (i.e. compatible with inputs) to the DIC package and it takes wind directly from EXF when useEXF = true.
> 
> You can see MITgcm/verification/global_oce_biogeo_bling
> for example inputs.
> 
> Matt
> 
> 
> 
> 
> 
>> On Jun 24, 2021, at 7:53 AM, Jonathan Lauderdale <jml1 at mit.edu> wrote:
>> 
>> Dear Hajoon,
>> 
>> Martin is correct that it?s not implemented - best place to start is dic_fields_update.F which is where pkg/dic gets its sea ice cover from elsewhere.
>> 
>> Cheers,
>> 
>> Jon
>> ___________________________________________________________________________
>> Dr. Jonathan M. Lauderdale
>> Research Scientist
>> Department of Earth, Atmosphere and Planetary Sciences 
>> Massachusetts Institute of Technology 
>> 77 Massachusetts Avenue (54-1518)
>> Cambridge, MA 02139, USA 
>> Office: +1 617 324 1568 
>> Cell   : +1 617 304 5661
>> Email: mailto:jml1 at mit.edu <mailto:jml1 at mit.edu>
>> Web: http://paocweb.mit.edu/people/jml1 <http://paocweb.mit.edu/people/jml1>
>> Twitter: https://twitter.com/jon_lauderdale <https://twitter.com/jon_lauderdale>
>> Git: https://github.com/seamanticscience <https://github.com/seamanticscience>
>> ___________________________________________________________________________
>> 
>> 
>> 
>>> On Jun 24, 2021, at 2:58 AM, Martin Losch <Martin.Losch at awi.de <mailto:Martin.Losch at awi.de>> wrote:
>>> 
>>> Hi Hajoon,
>>> 
>>> it?s probably not implemented, but what keeps you from using the exf variable wspeed (or sh) to overwrite ?wind? of dic? 
>>> Add an ?#include EXF_FIELDS.h? and then the variable is avaialble. You could even use #ifdef ALLOW_EXF/#else/#endif and possibly ?IF (useEXF) ? to switch between the two winds.
>>> 
>>> Martin
>>> 
>>>> On 24. Jun 2021, at 04:39, Hajoon Song <hajsong at mit.edu <mailto:hajsong at mit.edu>> wrote:
>>>> 
>>>> Dear all,
>>>> 
>>>> I wonder if there is an option to use the wind speed loaded or calculated in EXF package for the piston velocity in DIC package.
>>>> I am interested in whether the relative wind (useRelativeWind) can have a sizable impact on the air-sea CO2 exchange.
>>>> 
>>>> Currently, it seems that the wind speed is either initialized by 5 m/s or provided by DIC_windFile.
>>>> Or the wind speed can be updated when using ?ALLOW_OCN_COMPON_INTERF? and ?useImportWSpd?.
>>>> 
>>>> I would appreciate it if you can correct me if I am wrong.
>>>> 
>>>> Best regards,
>>>> Hajoon 
>>>> 
>>>> 
>>>> ---------------------------------------------
>>>> Hajoon Song, Assistant Professor
>>>> Department of Atmospheric Sciences
>>>> Yonsei University, Seoul, Korea
>>>> Tel: +82-2-2123-2579
>>>> _______________________________________________
>>>> MITgcm-support mailing list
>>>> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
>>>> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>>> 
>>> _______________________________________________
>>> MITgcm-support mailing list
>>> MITgcm-support at mitgcm.org <mailto:MITgcm-support at mitgcm.org>
>>> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
>> 
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20210624/9a2b68fc/attachment-0001.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support
> 
> 
> ------------------------------
> 
> End of MITgcm-support Digest, Vol 216, Issue 17
> ***********************************************