[MITgcm-support] Problem With EXF Forcing Period

[Martin Losch]

Hi Senja,

quick guess: the data.exf that you sent, starts over at line 44, maybe that’s the problem?

Martin

> On 30. Oct 2019, at 16:37, Senja Walberg <senja.w at gmail.com> wrote:
> 
> 
> Hey,
> I am doing lake simulations and providing hourly meteorological forcing data through EXF. My data.exf and data file are attached. The respective files which are referenced are all prepared such that consecutive indices in the time dimension are separated by one hour. 
> 
> Attached is an image of my shortwave forcing showing that this is the case.
> <Shortwave Forcing.png>
> 
> 
> I am having an issue, however, where the forcing is in fact not being applied hourly, but daily. I have looked at the EXF energy diagnostic files (EXFqnet, EXFswnet, etc.) and made a plot which is attached, showing that a small amount of time (approx 4 and some days) has gone by in 2500+ hours in the simulation. The plotted field is a spatial average of the EXFswnet diagnostic.
> <Shortwave Radiation, EXFswnet.png>
>  
> 
> From my understanding, the "periods" of each EXF field are set correctly for hourly data. I also have another case running with different forcing, which is working fine. The only difference between these two cases is that the one I'm having issues with is expected to form ice, and so has been compiled with the SEAIce packaged enabled, while the one that is working fine was not. What could be causing this issue? Does it have anything to do with the OBCS field period being set to 86400?
> 
> Also, thanks to Jean-Michel for responding to my last inquiry-- that was very helpful.
> 
> Cheers,
> Senja
> <data.exf><data>_______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support