[MITgcm-devel] NOOPTFILES obcs_init_fixed.F for linux_amd64_ifort+mpi_ice_nas

[Martin Losch]

Hi Dimitris,

in the past I have always included these files in the NOOPFILES list in the repository. You could have a second NOOPFILES list with potentially problematic files, or files that are no longer a problem and comment it out with appropriate comments.

Martin


> On 24. Jul 2018, at 06:58, Menemenlis, Dimitris (329C) <Dimitris.Menemenlis at jpl.nasa.gov> wrote:
> 
> I have run across a specific MITgcm configuration that requires that obcs_init_fixed.F be added to
> linux_amd64_ifort+mpi_ice_nas NOOPTFILES in order to integrate without segmentation fault on pleiades.
> What is best practice regarding NOOPTFILES ?  Do you want this exception added to MITgcm repository?
> For example, some of the current NOOPTFILES in the pleiades build options file may be outdated and
> no longer needed with current generation compiler.  But this is hard to test as the failure
> is usually model-configuration specific.
> 
> Let me know best way to proceed with this, Dimitris
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-devel