We are trying to replicate results of an experiment using CABLE-POP that was published in 2023 from source code currently stored in GitHub. Experimental results using the source code downloaded and compiled from (https://github.com/CABLE-LSM/CABLE/tree/NESP2pt9_BLAZE) do not match the old results. We would like to compare differences in the source code between the two simulations, however have only the svn branch and revision number which is https://trac.nci.org.au/trac/cable/branches/Users/ab7412/GPP_temp (Revisions 9625 and 9627).
This link no long appears to be active.
Is there any way to get access to this revision through the GitHub repo?
Environment:
GitHub ; SVN repository
clairecarouge
(Claire Carouge, ACCESS-NRI Land Modelling Team Lead)
3
@AlisonBennett , I have some bad news. We did not save the branches/Users/ab7412/GPP_temp branch during the transition to git from SVN. So we won’t find these revision numbers in the CABLE repository. And we do not have the SVN repository anymore.
More generally, the commits that have been transferred from SVN, all have a line similar to this in the commit message:
For searching for an SVN revision number in the commit history (for example 9447), you can do:
git log --all --grep='git-svn-id:.*@9447'
which returns:
commit c5d0aecf363d5c629452b02dbf48286b5adcf543
Author: jxs599 <jxs599@b483b3d9-cc7d-4f55-9e4c-b4562452379e>
Date: Mon Jan 9 13:11:01 2023 +0000
''Trunk Update''
'''Type:'''
Reconcile
'''Ticket:'''
#360
__Overview__
Reconcile following update version of CABLE in ACCESS-CM2 and ESM15 and JAC
git-svn-id: https://trac.nci.org.au/svn/cable/trunk@9447 b483b3d9-cc7d-4f55-9e4c-b4562452379e
I have searched for 9625 and 9627 and these are not present.
Thank-you for checking. I suspected that was the case, although I had thought that the svn repository was to remain in a read only mode. The updates I’m interested in should also have been applied in the CABLE_TRENDY branch so I might be able to find them with your method if I can dig up the revision number.
clairecarouge
(Claire Carouge, ACCESS-NRI Land Modelling Team Lead)
6
Thanks @SeanBryan51 . I’m just summarising everything together for our future selves and others so we can hopefully select this summary as a solution.
Finding old SVN commits for CABLE
Check if commit exists in the CABLE repository
You can search the CABLE repository history for an SVN revision. If you want to look for revision 9447, for example:
$ git log --all --grep='git-svn-id:.*@9447'
commit c5d0aecf363d5c629452b02dbf48286b5adcf543
Author: jxs599 <jxs599@b483b3d9-cc7d-4f55-9e4c-b4562452379e>
Date: Mon Jan 9 13:11:01 2023 +0000
''Trunk Update''
'''Type:'''
Reconcile
'''Ticket:'''
#360
__Overview__
Reconcile following update version of CABLE in ACCESS-CM2 and ESM15 and JAC
git-svn-id: https://trac.nci.org.au/svn/cable/trunk@9447 b483b3d9-cc7d-4f55-9e4c-b4562452379e
If the revision is not in the CABLE repository
There is an archive git repository for CABLE. You can find all the branches of the CABLE SVN repository in that repository. Although the SVN branches are mixed into some common git branches (main, Share and Users). It is not possible to use the same method to find a specific SVN revision. But “git log” allows to search commits based on various criteria. So one could search on the author, for example, with git log --author="<name>" . Or one could search on dates, etc.