Namespace conflict when coupled with CDEPS data components

[uturuncoglu]

Describe the bug
I am working on ESMF/NUOPC interface for WRF to couple with regional ocean model (NEMO). At this point, I am in a stage to testing the development with data ocean component but this creates an issue since I am using generic data component called CDEPS. WRF has some shared code copied from CESM like shr_orb_mod under phys/module_sf_clm.F and this conflicts with CDEPS ones. At this point, I am plaining to change the module names used under WRF to make them more specialized since they are belong to 2007 (I think) and the ones provided by the CDEPS are more up-to-date. Anyway, I just want to hear your feeling about it. My ultimate goal is to create PR once I have fully functional ESMF/NUOPC "cap" and tested under CESM framework.

To Reproduce
There is no strait forward way to reproduce this issue.

Expected behavior
Namespace conflict and build fails for coupled application.

Screenshots
N/A

Attachments
N/A

Additional context
N/A

[dudhia]

Our coupling software support is no longer here, but this looks like a valid issue to address to me.

[uturuncoglu]

@dudhia That is totally fine. Okay. I just want to get your opinion/suggestions. Anyway, I'll go ahead and fix the issue in the WRF source code. I think I could handle other issues without help. Best.