Skip to content

CICE-SCHISM coupling (UFS) updates #215

Open
SmithJos13 wants to merge 1 commit intoschism-dev:masterfrom
SmithJos13:feature/cice_updates
Open

CICE-SCHISM coupling (UFS) updates #215
SmithJos13 wants to merge 1 commit intoschism-dev:masterfrom
SmithJos13:feature/cice_updates

Conversation

@SmithJos13
Copy link

Changes to the initial implementation of CICE coupling for current working configuration in UFS-coastal. Bug fixes. Please tell me if you want me to add in CPP_FLAG (USE_CICE) protection commented out currently. Would have implications at the app level in UFS-coastal. @uturuncoglu tagged here as requested.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SmithJos13 : I don't think u changed GOTM, so can u plz remove this from PR?

allocate(sink0(npa),fraction0(npa),kk10(npa),kk20(npa))
#endif

!#ifdef USE_CICE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SmithJos13: it's good to keep your changes (which are related to CICE6 via UFS) isolated via CPP. I propose UFS_CICE.

!$OMP end parallel do
#endif /*not USE_ATMOS*/

!#ifdef USE_CICE
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add also UFS_CICE


!(2,npa). ocean-ice stress (junk if no ice) [m^2/s/s]
real(rkind),save,allocatable :: tau_oi(:,:)
!(npa). ocean-ice stress (junk if no ice) [m^2/s/s]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aren't tau_oi[xy] just components of tau_oi?

!>---------------------------------------------------
real(rkind), allocatable, save, target :: uvice(:)
real(rkind), allocatable, save, target :: vvice(:)
real(rkind), allocatable, save, target :: taux(:)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tau[xy] are too close to other existing names. Could we change them to something more distinct like tau[xy]_ice

real(rkind), allocatable, save, target :: taux(:)
real(rkind), allocatable, save, target :: tauy(:)
real(rkind), allocatable, save, target :: vsno(:)
real(rkind), allocatable, save, target :: vice(:)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also a common name; can we rename it?

@josephzhang8
Copy link
Member

Thx @SmithJos13. We are almost there. Can u address my question on tau_oi[xy]?

@SmithJos13
Copy link
Author

@josephzhang8 Do you want me to remove tau_oi[xy] and stick with tau_oi?

@josephzhang8
Copy link
Member

Yes, removing [xy] would be good to conserve memory. Thx

@josephzhang8
Copy link
Member

I'll wait for review from @uturuncoglu

@SmithJos13
Copy link
Author

Sounds good I'll update and make the consistent changes on schism esmf. we should review both before we Marge in case other vars need to change I'm about to submit the emsf pr

@SmithJos13
Copy link
Author

Do I need to use a different exchange routine or is call exchange_p2d(tau_oi) okay?

@SmithJos13 SmithJos13 force-pushed the feature/cice_updates branch from ae2ea60 to 98de8db Compare March 6, 2026 20:06
@SmithJos13
Copy link
Author

I just removed all the auxiliary commits from the PR

@josephzhang8
Copy link
Member

exchange_p2d

I see why u declared [xy] now. You can try to allocate those [xy] as pointers and then use them for exchange. This way it won't waste any memory.

@josephzhang8
Copy link
Member

Can you please show me where the exchange is done? I can fix it for you using swild* if they are inside SCHISM codes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants