time dependent forcing applied at incorrect time in timestep about cism HOT 2 OPEN

From @stephenprice on March 10, 2015 18:17

@matthewhoffman please look over my description here and edit it as necessary.

from cism.

From @matthewhoffman on March 11, 2015 2:54

@stephenprice , this looks good. I'll add that the problem with velocity when reading forcing at the end of the time step is that the velocity field that was read from file clobbers the velocity field that was calculated by the model - which clearly is bad. 👎

Another thought just crossed my mind - if the velocity values used by kinbcmask were in a different field (e.g., kinbcuvel, kinbcvvel), I think that would solve the problem and allow the values to be read at the end of the timestep - and more easily than other potential fixes. One thing to consider is that right now Glissade is only using a 2d field of values for the kinbc (it applies the basal uvel/vvel values throughout the entire column at every grid point that is masked) - so if we added new fields for the kinbc values, they would only need to be 2d fields (at least for now). We should give more careful thought to this potential solution when the time comes to address this.

from cism.