ESCOMP / ESCOMP/CAM

upstream repo for FV3 dycore development is changing - how best to track this switch

Open
#359 2 comments 0 reactions 4 assignees Assigned to @mvertens View on GitHub
question
Dominant language
No language data
Stars
91
Forks
183
Avg merge
6d 2m
Merged PRs (30d)
9

Description

Our current CAM/FV3 port - ESCOMP/FV3_CESM is forked from NOAA-EMC/GFDL_atmos_cubed_sphere which is itself a fork of the official GFDL FV3 source repository NOAA-GFDL/GFDL_atmos_cubed_sphere. I found out that FV3 development switched last week and is now taking place on the dev/emc branch of the official NOAA-GFDL/GFDL_atmos_cubed_sphere repository. I am assuming that we will want to track NOAA-GFDL and am unsure of the future of NOAA-EMC. I think we may be able to transition to using NOAA-GFDL directly in the future but we are not there yet and still need a ESCOMP repository that has CAM-specific modifications for the FV3 port. Should we create a new repo under ESCOMP that is a fork of NOAA-GFDL/GFDL_atmos_cubed_sphere?

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.