ESCOMP / ESCOMP/CMEPS

Using CMEPS outside of CESM framework is getting way more complex

Open
#654 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Fortran
Stars
35
Forks
106
Avg merge
6d 5h
Merged PRs (30d)
4

Description

I think the current design of CMEPS is too complex. To compile CMEPS outside of the CESM framework you need to do lots of tricks/hacks and also get bunch of code from different places such as https://github.com/ESCOMP/CESM_share even if you are not using them. Even for experienced users it is not easy and getting more complex every day. Sometimes, you also need to provide CDEPS shared code and/or different compile flags also involves to generate template codes or use some capability which is already exit in CMEPS (like CESM aoflux calculation, why it is designed only used by CESM?). I think we need to think carefully to reduce this complexity if we really want to be a community software (or specifically mediator). My impression is that this approach is not sustainable and have makes the debugging and testing more and more difficult. Maybe in the past I raised same concerns but my impression is that CMEPS needs to be self contained software package that could be easily port to any application. This is my opinion but I am using CMEPS mostly outside of CESM framework and this is my observation. Anyway, I am happy to discuss more if you would like.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.