[MITgcm-support] notUsingX/YPeriodicity

[ESTANISLAO GAVILAN PASCUAL-AHU]

Hi Pochini,

I am no sure about that option, but if you do not want to have a periodic open boundary (i.e. time dependent). You could just set the forcing period to zero. From the data file you could write this:
 periodicExternalForcing= .FALSE.,
 externForcingPeriod= 0.,
 externForcingCycle = 120000.,
 or from the the data.exf:
&EXF_NML_OBCS

 obcsNstartdate1=19781216,
 obcsNstartdate2=180000,
 obcsNperiod=0,
 obcsNrepCycle=120000,
 obcsSstartdate1=19781216,
 obcsSstartdate2=180000,
 obcsSperiod=0,
 obcsSrepCycle=120000,

 Kind regards,

Estanislao


> -----Original Messages-----
> From: mitgcm-support-request at mitgcm.org
> Sent Time: Wednesday, November 13, 2019
> To: mitgcm-support at mitgcm.org
> Cc: 
> Subject: MITgcm-support Digest, Vol 197, Issue 6
> 
> 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. notUsingX/YPeriodicity (Pochini, Enrico)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 12 Nov 2019 14:44:40 +0100
> From: "Pochini, Enrico" <epochini at inogs.it>
> To: mitgcm-support at mitgcm.org
> Subject: [MITgcm-support] notUsingX/YPeriodicity
> Message-ID:
> 	<CAFTyFMBkFvtQ9Nd4kHNDm8rK_Lcb2c=+1UMVwUt2gj3a+yN+iw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi all,
> 
> I am trying to deactivate the default behaviour of periodic boundaries. I
> tried setting in eedata notUsingXPeriodicity=.TRUE.,
> notUsingYPeriodicity=.TRUE., but the option is not recognized. Setting
> forcefully in eeparms_set.F, where it appears in COMMON block EEPARMS,
> cause the following error to appear:
> 
> *** An error occurred in MPI_Cart_rank
> > *** reported by process [3771400193,0]
> > *** on communicator MPI_COMMUNICATOR 3
> > *** MPI_ERR_ARG: invalid argument of some other kind
> > *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
> > ***    and potentially your MPI job)
> > 6 more processes have sent help message help-mpi-errors.txt /
> > mpi_errors_are_fatal
> > Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error
> > messages
> >
> 
> The two lines
> #define CAN_PREVENT_X_PERIODICITY
> #define CAN_PREVENT_Y_PERIODICITY
> are defined in CPP_EEOPTIONS.h
> 
> Does the periodic domain definition interact with OB specifications?
> Is there a way to solve it without setting bathymetry=0 at margins?
> 
> Thanks,
> 
> Enrico
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.mitgcm.org/pipermail/mitgcm-support/attachments/20191112/d2832dd0/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 197, Issue 6
> **********************************************