<DIV>Dear Daniel</DIV>
<DIV> </DIV>
<DIV>I think you are right. The OBCS does not contain PTracer forcing. You need to employ RBCS to restore the PTracer.<BR></DIV>
<DIV>Cheers</DIV>
<DIV> </DIV>
<DIV>Chengyan</DIV>
<DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 12px; FONT-FAMILY: Arial Narrow; PADDING-BOTTOM: 2px; PADDING-TOP: 2px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px">------------------ Original ------------------</DIV>
<DIV style="FONT-SIZE: 12px; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px">
<DIV><B>From: </B> "mitgcm-support-request"<mitgcm-support-request@mitgcm.org>;</DIV>
<DIV><B>Date: </B> Thu, May 17, 2018 04:07 PM</DIV>
<DIV><B>To: </B> "mitgcm-support"<mitgcm-support@mitgcm.org>;<WBR></DIV>
<DIV></DIV>
<DIV><B>Subject: </B> MITgcm-support Digest, Vol 179, Issue 11</DIV></DIV>
<DIV><BR></DIV>Send MITgcm-support mailing list submissions to<BR>mitgcm-support@mitgcm.org<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support<BR>or, via email, send a message with subject or body 'help' to<BR>mitgcm-support-request@mitgcm.org<BR><BR>You can reach the person managing the list at<BR>mitgcm-support-owner@mitgcm.org<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of MITgcm-support digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. Output 2D slice from 3D simulation (Ruan Xiaozhou)<BR> 2. segmentation fault (Andreas Klocker)<BR> 3. ptracer and sponge (Daniel Goldberg)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Thu, 17 May 2018 03:35:13 +0000<BR>From: Ruan Xiaozhou <saberruan@hotmail.com><BR>To: "mitgcm-support@mitgcm.org" <mitgcm-support@mitgcm.org><BR>Subject: [MITgcm-support] Output 2D slice from 3D simulation<BR>Message-ID:<BR><DM5PR12MB19295B811982B2861D2917E7A0910@DM5PR12MB1929.namprd12.prod.outlook.com><BR><BR>Content-Type: text/plain; charset="utf-8"<BR><BR>Dear MITgcm users,<BR><BR>Hope this message finds you well. I have been trying to output 2D slice (YZ) data from a 3D simulation (because the 3D field is too large to be outputted at high frequency) but did not find proper locations in the diagnostics package. I?d really appreciate it if you could point me to the right directions.<BR><BR>Best,<BR>Xiaozhou<BR>--<BR>Xiaozhou Ruan<BR>Division of Geological and Planetary Sciences<BR>California Institute of Technology<BR>MC 131-24<BR>Pasadena, CA 91125<BR><BR>phone: +1 626-395-8715<BR>email: xiaozhour@caltech.edu<mailto:xiaozhour@caltech.edu><BR>web: http://www.its.caltech.edu/~xruan<BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20180517/dc7bd872/attachment-0001.html><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Thu, 17 May 2018 16:27:33 +1000<BR>From: Andreas Klocker <andreas.klocker@utas.edu.au><BR>To: "mitgcm-support@mitgcm.org" <mitgcm-support@mitgcm.org><BR>Subject: [MITgcm-support] segmentation fault<BR>Message-ID: <d299752c-4dd1-1994-9894-2ccdf87e196b@utas.edu.au><BR>Content-Type: text/plain; charset=UTF-8; format=flowed<BR><BR>Hi guys,<BR><BR>I've taken a working 1/24 degree nested simulation (of Drake Passage)<BR>with 42 vertical layers and tried to increase the vertical layers to 150<BR>(without changing anything else apart from obviously my boundary files<BR>for OBCS and recompiling with 150 vertical layers). Suddenly I get the<BR>following error message:<BR><BR>forrtl: severe (174): SIGSEGV, segmentation fault occurred<BR>Image PC Routine Line Source<BR>libirc.so 00002BA1704BC2C9 Unknown Unknown Unknown<BR>libirc.so 00002BA1704BAB9E Unknown Unknown Unknown<BR>libifcore.so.5 00002BA1722B5F3F Unknown Unknown Unknown<BR>libifcore.so.5 00002BA17221DD7F Unknown Unknown Unknown<BR>libifcore.so.5 00002BA17222EF43 Unknown Unknown Unknown<BR>libpthread.so.0 00002BA1733B27E0 Unknown Unknown Unknown<BR>mitgcmuv_drake24_ 00000000004E61BC mom_calc_visc_ 3345 mom_calc_visc.f<BR>mitgcmuv_drake24_ 0000000000415127 mom_vecinv_ 3453 mom_vecinv.f<BR>mitgcmuv_drake24_ 0000000000601C33 dynamics_ 3426 dynamics.f<BR>mitgcmuv_drake24_ 0000000000613C2B forward_step_ 2229 forward_step.f<BR>mitgcmuv_drake24_ 000000000064581E main_do_loop_ 1886 main_do_loop.f<BR>mitgcmuv_drake24_ 000000000065E500 the_main_loop_ 1904 the_main_loop.f<BR>mitgcmuv_drake24_ 000000000065E6AE the_model_main_ 2394 the_model_main.f<BR>mitgcmuv_drake24_ 00000000005C6439 MAIN__ 3870 main.f<BR>mitgcmuv_drake24_ 0000000000406776 Unknown Unknown Unknown<BR>libc.so.6 00002BA1737E2D1D Unknown Unknown Unknown<BR>mitgcmuv_drake24_ 0000000000406669 Unknown Unknown Unknown<BR><BR>First this error pointed to a line in mom_calc_visc.f on which<BR>calculations regarding the Leith viscosity are done. As a test I then<BR>used a Smagorinsky viscosity instead and now it crashes with the same<BR>error, but pointing to a line where Smagorinsky calculations are done. I<BR>assume I must be chasing a way more fundamental problem than one related<BR>to these two viscosity choices...but I'm not sure what this might be....<BR><BR>Has anyone got any idea of what could be going wrong here?<BR><BR>Thanks in advance!<BR><BR>Andreas<BR><BR><BR><BR>University of Tasmania Electronic Communications Policy (December, 2014).<BR>This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.<BR><BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Thu, 17 May 2018 09:07:26 +0100<BR>From: Daniel Goldberg <dngoldberg@gmail.com><BR>To: MITgcm-support@mitgcm.org<BR>Subject: [MITgcm-support] ptracer and sponge<BR>Message-ID:<BR><CAEhdavJ9PbX8SC-cM8RYJJEVODu6b71qNQLdDknDzZnRMeHTQg@mail.gmail.com><BR>Content-Type: text/plain; charset="utf-8"<BR><BR>Hello all<BR><BR>>From what i can tell, the obcs sponge facility is not implemented for<BR>PTRACERS? I just want to make sure this is correct before i set up RBCS for<BR>a passive tracer.<BR><BR>Many thanks<BR>Dan<BR><BR>-- <BR><BR>Daniel Goldberg, PhD<BR>Lecturer in Glaciology<BR>School of Geosciences, University of Edinburgh<BR>Geography Building, Drummond Street, Edinburgh EH8 9XP<BR><BR><BR>em: D <dgoldber@mit.edu>dan.goldberg@ed.ac.uk<BR>web: https://www.geos.ed.ac.uk/homes/dgoldber<BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20180517/0d23a5ed/attachment.html><BR><BR>------------------------------<BR><BR>Subject: Digest Footer<BR><BR>_______________________________________________<BR>MITgcm-support mailing list<BR>MITgcm-support@mitgcm.org<BR>http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support<BR><BR><BR>------------------------------<BR><BR>End of MITgcm-support Digest, Vol 179, Issue 11<BR>***********************************************<BR></DIV>