Hi Mark, Two things. First, I'm waiting for the v0 code still (Mat is going to get it from titan for me, but if someone who already has access wants to push it to a temporary repo on github, I could "merge" it into our history from there). So, the short answer to your first question, is no. We don't have a "v0" we can checkout yet. I've been thinking the CESM tags are enough as well, for our purposes (and most other peoples purposes). Also, it would likely improve our software practices, rather than having people going back to a CAM or CLM tag / commit and working off of that. Incorporating the remaining history is not an easy task. At least, incorporating it in a way that makes it useful to keep. It's easy to export the trunk history of CAM and CLM individually, but not in a way that ties them directly to CESM / ACME. There are two main problems here. The first is that CAM and CLM have "mini-CESMs" that represent their stand-alone drivers. The second is that CESM has a completely different "full-CESM" that makes use of only a portion of the CAM and CLM directory structure. In order to migrate the history, first you need to export the svn history to git (pretty easy using git-svn). The second step is stripping out the mini-CESM (also pretty easy using filter branch, or subtree split). The third step may or may not be needed, but large data files need to be removed (fairly easy using filter branch, but can cause some issues). And the fourth and final step is the most complicated, you somehow need to "tie" each commit in the CAM / CLM trunk to a CESM tag, and use that as it's base. This last step is not easy to do at all, and requires a lot of manual intervention. All steps except the final step can be performed to preserve the history of each trunk, but the trunk will not be usable. Alternatively, the second and fourth steps can be skipped, but the histories need to remain separate. This is one of the things that I've been giving a lot of thought to, since NCAR specifically said they wanted to maintain the histories of each trunk. Hope that helps! I'll update you guys when I get a v0 up on github. Thanks, Doug On 06/09/2014 03:41 PM, Taylor, Mark A wrote:
Hi James,
Is there a "v0" tag in github that we can checkout? Can someone with a titan account automate a file by file diff with ~taylorm/codes/acme_v0 ? (and there is one more change in CICE, that we've implemented through soucecode modes, but that should be committed directly to the v0 tag).
I personally think the CESM tags is enough history for the ACME repository -- we can always get the detailed history from the CESM repository. But if it is easy, why not have as much history as possible?
Mark
*From:*Foucar, James G *Sent:* Monday, June 09, 2014 2:59 PM *To:* [email protected] *Cc:* Taylor, Mark A *Subject:* last remaining repo items
Hello repo team,
I'd like to try to set up a candidate repository by this Friday. There are a couple items that are preventing me from doing so:
1. A confirmation from someone (Doug, Mark?) that the codes we've put on github match the versions that we want for v0. 2. A decision on what we want our history to look like. The choices are what you see in ACME-Climate/single-repo-example (full history) vs. ACME-Climate/CESM_Version (just version snapshots).
Thanks,
-Jim
_______________________________________________ ACME-SE mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/acme-se