Provide accessible configuration files for all publically stored runs

[rmholmes]

This is really important for the main ACCESS-OM2 Control Runs. For other runs it's more of a "would be nice".

All runs that were synced to /g/data/ using the sync_data.sh script already have these configurations saved in the git-runlog folder within the main archive directory.

Below is a list of runs that don't have the configuration files within their archieve:

/g/data/ik11/outputs/access-om2-01:
01deg_jra55v13_iaf_4hourly
01deg_jra55v13_ryf9091
01deg_jra55v13_ryf9091_5Kv
01deg_jra55v13_ryf9091_easterlies_down10
01deg_jra55v13_ryf9091_easterlies_up10
01deg_jra55v13_ryf9091_easterlies_up10_meridional
01deg_jra55v13_ryf9091_easterlies_up10_noDSW
01deg_jra55v13_ryf9091_easterlies_up10_zonal
01deg_jra55v13_ryf9091_k_smag_iso3
01deg_jra55v13_ryf9091_OFAM3visc
01deg_jra55v13_ryf9091_qian_ctrl
01deg_jra55v13_ryf9091_qian_wthmp
01deg_jra55v13_ryf9091_qian_wthp
01deg_jra55v13_ryf9091_qian_wtlp
01deg_jra55v13_ryf9091_rerun_for_easterlies
01deg_jra55v13_ryf9091_weddell_down2
01deg_jra55v13_ryf9091_weddell_up1
01deg_jra55v140_iaf
01deg_jra55v140_iaf_cycle2
01deg_jra55v140_iaf_cycle4
01deg_jra55v140_iaf_cycle4_OLD
01deg_jra55v140_iaf_cycle4_rerun_from_1980
01deg_jra55v140_iaf_cycle4-test
basal_melt_outputs

/g/data/ik11/outputs/access-om2-025:
025deg_jra55_iaf_omip2_cycle6_ext
025deg_jra55_ryf9091_gadi
025deg_jra55_ryf9091_gadi_noGM
025deg_jra55_ryf9091_gadi_norediGM

/g/data/ik11/outputs/access-om2:
1deg_jra55_iaf_ensemble_ndte_240
1deg_jra55_iaf_ensemble_snowpatch_0.005
1deg_jra55_iaf_ensemble_snowpatch_0.01
1deg_jra55_iaf_omip2_cycle1
1deg_jra55_iaf_omip2_cycle2
1deg_jra55_iaf_omip2_cycle3
1deg_jra55_iaf_omip2_cycle4
1deg_jra55_iaf_omip2_cycle5
1deg_jra55_iaf_omip2_cycle6
1deg_jra55_iaf_omip2fe03_cycle1
1deg_jra55_iaf_omip2spunup_cycle1
1deg_jra55_iaf_omip2spunup_cycle10
1deg_jra55_iaf_omip2spunup_cycle11
1deg_jra55_iaf_omip2spunup_cycle12
1deg_jra55_iaf_omip2spunup_cycle13
1deg_jra55_iaf_omip2spunup_cycle14
1deg_jra55_iaf_omip2spunup_cycle15
1deg_jra55_iaf_omip2spunup_cycle16
1deg_jra55_iaf_omip2spunup_cycle17
1deg_jra55_iaf_omip2spunup_cycle18
1deg_jra55_iaf_omip2spunup_cycle19
1deg_jra55_iaf_omip2spunup_cycle2
1deg_jra55_iaf_omip2spunup_cycle20
1deg_jra55_iaf_omip2spunup_cycle21
1deg_jra55_iaf_omip2spunup_cycle22
1deg_jra55_iaf_omip2spunup_cycle23
1deg_jra55_iaf_omip2spunup_cycle24
1deg_jra55_iaf_omip2spunup_cycle25
1deg_jra55_iaf_omip2spunup_cycle26
1deg_jra55_iaf_omip2spunup_cycle27
1deg_jra55_iaf_omip2spunup_cycle28
1deg_jra55_iaf_omip2spunup_cycle29
1deg_jra55_iaf_omip2spunup_cycle3
1deg_jra55_iaf_omip2spunup_cycle30
1deg_jra55_iaf_omip2spunup_cycle31
1deg_jra55_iaf_omip2spunup_cycle32
1deg_jra55_iaf_omip2spunup_cycle33
1deg_jra55_iaf_omip2spunup_cycle34
1deg_jra55_iaf_omip2spunup_cycle35
1deg_jra55_iaf_omip2spunup_cycle36
1deg_jra55_iaf_omip2spunup_cycle37
1deg_jra55_iaf_omip2spunup_cycle38
1deg_jra55_iaf_omip2spunup_cycle39
1deg_jra55_iaf_omip2spunup_cycle4
1deg_jra55_iaf_omip2spunup_cycle40
1deg_jra55_iaf_omip2spunup_cycle42
1deg_jra55_iaf_omip2spunup_cycle43
1deg_jra55_iaf_omip2spunup_cycle44
1deg_jra55_iaf_omip2spunup_cycle45
1deg_jra55_iaf_omip2spunup_cycle46
1deg_jra55_iaf_omip2spunup_cycle47
1deg_jra55_iaf_omip2spunup_cycle48
1deg_jra55_iaf_omip2spunup_cycle49
1deg_jra55_iaf_omip2spunup_cycle5
1deg_jra55_iaf_omip2spunup_cycle50
1deg_jra55_iaf_omip2spunup_cycle6
1deg_jra55_iaf_omip2spunup_cycle7
1deg_jra55_iaf_omip2spunup_cycle8
1deg_jra55_iaf_omip2spunup_cycle9
1deg_jra55_ryf9091_gadi

As far as I can tell, none of the runs stored in /g/data/cj50 have configs saved with the output.

[aekiss]

/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v140_iaf_cycle4 has a git-runlog and run summary, and for cycle 3 they are in /g/data/ik11/outputs/access-om2-01/01deg_jra55v140_iaf_cycle3 even though the data is on cj50.

Content on cj50 is published via thredds with a DOI so I'll have to see whether we revise these to add git-runlog.

[aekiss]

But in any case, all 0.1° IAF cycle run histories are available as branches on github:
https://github.com/COSIMA/01deg_jra55_iaf/commits/01deg_jra55v140_iaf
https://github.com/COSIMA/01deg_jra55_iaf/commits/01deg_jra55v140_iaf_cycle2
https://github.com/COSIMA/01deg_jra55_iaf/commits/01deg_jra55v140_iaf_cycle3
https://github.com/COSIMA/01deg_jra55_iaf/commits/01deg_jra55v140_iaf_cycle4
https://github.com/COSIMA/01deg_jra55_iaf/commits/01deg_jra55v140_iaf_cycle4_jra55v150_extension
and the other control run git histories are also on github. So if we do that for all the experiments it seems a bit redundant to also have repos in the output directories, so long as people know what github repo & branch to look for.

[rmholmes]

I agree. I've listed several options in the tutorial for finding the configurations of interest, this being only one.

"so long as people know what github repo & branch to look for." -> Exactly. The git-log in output directory is the easiest way to have this step done for people automatically. Otherwise, often the configuration files aren't available somewhere publically accessible.