Split TR_GridComp into separate repository

[tclune]

@mathomp4 feel free to outsource the details to others on SI team. Consult @christophkeller for any questions about any needed changes to directory structure and/or copying of dependencies in Chem_Base.

I've told GCHP that this could probably be done in ~ 1 week but that the SI team is very busy and this is lower priority, albeit easy.

[tclune]

Mentioning @sdeastham as well, as he may have advice if there are issues.

[mathomp4]

ETA: Please see below for how I did this for the second TR_GridComp

Well, I had some time and wanted something new to try.

I think I have a first good go (mainly testing things out). I've made a new TR_GridComp repo that I'm trying out now. I did this following this page using these commands:

mkdir MakeNewTRGridComp
cd MakeNewTRGridComp
git clone git@github.com:GEOS-ESM/GEOSchem_GridComp.git
cd GEOSchem_GridComp
git checkout main
git remote rm origin
git filter-branch --subdirectory-filter TR_GridComp -- --all
git reset --hard
git gc --aggressive
git prune
git clean -fd

That left me with just the TR_GridComp files. Now we push up to the new repo:

git remote add origin git@github.com:GEOS-ESM/TR_GridComp.git
git branch -M main
git push -u origin main

I then added a LICENSE.md and README.md

[mathomp4]

This is probably just the first step. Essentially, GEOSchem_GridComp loses TR_GridComp and mepo adds in @TR_GridComp with the exact same files.

[mathomp4]

I suppose we should think about making a "Tracer Team" here on GEOS-ESM for a CODEOWNERS file on the new repo. On Git the contributors to TR are (less @tclune, @sdrabenh, and myself):

• @mmanyin
• @gmao-esherman

Those are the @GEOS-ESM/chemistry-gatekeepers essentially.

[mmanyin]

Hi- I wrote the original module, and would like to help in the maintenance (preserving the strengths, and improving its shortcomings). Moving TR into its own module is a good first step.

[mathomp4]

Is there still a want to do this? I think the TR_GridComp I made long ago is probably still the same. I'm not sure there has been any updates.

[tclune]

I think there is still desire. There was still some discussion about the ordering of creating the repo vs refactoring. Arlindo argued it would be best to wait for the code cleanup. But Harvard indicated there was some value in getting the separate repo even in advance of the refactoring. What I don't recall is if there was a subsequent wrinkle that had as hold off, or if we were just waiting for someone to be squeaky enough to trigger the work.

[mmanyin]

There have been developments in TR, although some are waiting to be captured from the Icarus version and merged into Jason. I think that Elliot was asked to make TR compliant w/ ESMF best practices, although that would not start until he is done with the GOCART next-gen project.

[mathomp4]

Okay! Just wanted to make sure. I can always recreate the repo as TR advances (if needed)

[lizziel]

I am looking into including TR_GridComp in GCHP in the near future. Can you think of any reasons not to work with the new repo as it is now? There is the complication of the dependency on Chem_Shared since Chem_Shared is still in GEOSchem_GridComp. Do you have any plans to address this so that TR_GridComp is more portable?

[mathomp4]

@lizziel Well, the main reason is I should probably nuke TR_GridComp and re-make it. I figure once we got to the point that @mmanyin, @gmao-esherman, etc. were ready to split off TR, I could do it and then we'd have a TR with all the right history. I just don't want to split it off and have two TRs floating around in development. That way leads to madness!