<div dir="ltr">Hi Matt and Martin,<br><br>Thank you both for your suggestions. I ran the model with T,S,U and V at boundary forcing as suggested by Matt.<br><div>Also as recommended by Martin, changed hFacMin =0.3 from 0.9, and set OBCSfixTopo=.TRUE. from FALSE. Also trying to improve</div><div>the grid simultaneously.<br></div><div><br></div><div>And that fixed the issue. Please refer to the figure attached. I also gave a run adding heat and moisture fluxes from NCEP reanalysis. <br></div><div>But it looks like Model SST is overestimating by ~1.25 degC when compared with WOA18 SST. Is it because fluxes are being fed in as <br></div><div>monthly climatology and not real time daily values? I simulated the model for 30 days.<br></div>Thanks again!<br><br>Regards<br>Kunal<br><br>------------<div dir="ltr" class="gmail_attr" style="color:rgb(136,136,136)">From: <b class="gmail_sendername" dir="auto">kunal madkaiker</b> <span dir="auto"><<a href="mailto:kunal.madkaiker02@gmail.com" target="_blank">kunal.madkaiker02@gmail.com</a>></span><br></div><div class="gmail_quote">Date: Fri, Jul 24, 2020 at 9:52 AM<br>To: MITgcm Support <<a href="mailto:mitgcm-support@mitgcm.org" target="_blank">mitgcm-support@mitgcm.org</a>><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">Dear MITgcm users,<div dir="ltr"><div><br></div><div>I am trying to simulate ocean currents along the West coast of India in a high resolution grid (360x780) for the month of September. For now, I am providing monthly climatology of August Temperature and Salinity as initial forcing along with September zonal and meridional wind stress. Currently, using the Orlanski scheme for obcs and no boundary forcings. Model is simulated for 10 days.<br></div><div><br></div><div>But the currents are not coming correct. The West Indian Coastal Current (WICC) which flows equatorward (during Sept) isn't being captured at all. After plotting the bathymetry, I observed that the currents are being veered northward by the Arabian sea continental shelf (Please refer to Picture1.png attached
(Day 04-10)). Is that possible? My bathymetry bin file is just a 2D mesh with depth values. Also, my coastal currents are very weak.</div><div><br></div><div>Attaching my data,data.obcs and data.exf file. Please let me know if any additional information is required from my end.</div><div>Kindly advise. All suggestions are welcomed.</div><div><br></div><div>Regards</div><div>Kunal<br></div></div>
<br><br><div dir="ltr" class="gmail_attr" style="color:rgb(136,136,136)">----------<br>From: <b class="gmail_sendername" dir="auto">Matthew Mazloff</b> <span dir="auto"><<a href="mailto:mmazloff@ucsd.edu" target="_blank">mmazloff@ucsd.edu</a>></span><br>Date: Fri, Jul 24, 2020 at 10:12 AM<br>To: <<a href="mailto:mitgcm-support@mitgcm.org" target="_blank">mitgcm-support@mitgcm.org</a>><br></div><br><br>1) You are setting U and V = 0 as an initial condition? Then likely U and V aren’t spun up yet after just 10 days. <br>
<br>
2) regional models are very sensitive to obcs. You aren’t prescribing a UVTS on the boundary? That will kill your coastal currents. <br>
<br>
Sounds like the problems are just with your (lack of) inputs<br>
<br>
Matt
> <data.obcs><bathymetry.png><data><data.exf><Picture1.png>_______________________________________________<br>
> MITgcm-support mailing list<br>
> <a href="mailto:MITgcm-support@mitgcm.org" target="_blank">MITgcm-support@mitgcm.org</a><br>
> <a href="https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!WJ7uZPG1M2dThC8r1pphYDlMIcAf9vYRKuuJejYIZeUqSlQmMjjY1ew3p3guXOG0Ug$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support__;!!Mih3wA!WJ7uZPG1M2dThC8r1pphYDlMIcAf9vYRKuuJejYIZeUqSlQmMjjY1ew3p3guXOG0Ug$</a> <br>
<br>
_______________________________________________<br>
MITgcm-support mailing list<br>
<a href="mailto:MITgcm-support@mitgcm.org" target="_blank">MITgcm-support@mitgcm.org</a><br>
<a href="http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support" rel="noreferrer" target="_blank">http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support</a><br>
<br><br><div dir="ltr" class="gmail_attr" style="color:rgb(136,136,136)">----------<br>From: <b class="gmail_sendername" dir="auto">Martin Losch</b> <span dir="auto"><<a href="mailto:Martin.Losch@awi.de" target="_blank">Martin.Losch@awi.de</a>></span><br>Date: Fri, Jul 24, 2020 at 3:09 PM<br>To: MITgcm Support <<a href="mailto:mitgcm-support@mitgcm.org" target="_blank">mitgcm-support@mitgcm.org</a>><br></div><br><br>Hi Kunal,<br>
<br>
I have no idea of the loca hydrography and circulation and don’t know what to expect, but there are few things that may be problematic in your setup:<br>
<br>
- check the forcing: the surface stresses are aligned with the grid direction, i.e. ustress is not directed towards the east, but towards increasing model index “i” (which is sometimes called “east” in the code). So your wind stress needs to be rotated according to your grid orientation before it is read by the model. Probably you have already thought about this<br>
- with your obcs settings there is no net flow through the open boundaries. Is that what you want? If the current system is only local, that this is OK but a quick google search tells me that the southward WICC should actually leave your domain. You’d need some sort of boundary conditions for that. I would suggest that you look into the Stevens boundary conditions (described in the documenation) where you can specify a barotropic flow field normal to the boundaries.<br>
- a 10-day simulation period may be very short for any system to develop<br>
- there’s no buoyancy forcing. Is that important or do you only want wind driven circulation?<br>
<br>
small things that you may want to adjust:<br>
- your viscosities are very high<br>
- your horizontal grid aspect ratio is very high (dx/dy = 2891.9791/939.661 = 3), that could cause numerical problems (e.g. CFL problems or stability problems with viscosity). If you can still change that ratio to 1, I would do that<br>
- for delZ/delR the rule of thumb is that delZ(k+1)/delZ(k) < 1.4, i.e. there shouldn’t be too large jumps in the grid spacing so that the numerical approximations are not compromised<br>
- hFacMin = 0.9 is close to turning off the partial cells. I’d use something like 0.3 or even 0.1 if possible. with your 5m grid spacing this may be problematic but you can set minimum thickness with hFacMinDz/hFacMinDr (=5 or 10)<br>
<br>
- OBCSfixTopo=.FALSE., is not a good choice, use the default (.True.)<br>
<br>
Hope that helps,<br>
Martin
> <data.obcs><bathymetry.png><data><data.exf><Picture1.png>_______________________________________________<br>
> MITgcm-support mailing list<br>
> <a href="mailto:MITgcm-support@mitgcm.org" target="_blank">MITgcm-support@mitgcm.org</a><br>
> <a href="http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support" rel="noreferrer" target="_blank">http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support</a><br><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div>
</blockquote></div></div>