[MITgcm-devel] [MITgcm-cvs] MITgcm/verification/lab_sea/results CVS Commit
Jean-Michel Campin
jmc at ocean.mit.edu
Thu Apr 28 16:32:28 EDT 2011
Hi Ian,
The short answer is "always" (i.e., for any changes),
although tittle changes with no impact on how MITgcm
works nor on how it can be used (such as changes in
commented lines, documentation changes, .cvsignore/cvs Header
type things, ...) can be skipped.
And what we don't want to miss in particular is:
a) when reference output changes, as I pointed out:
> >> Would be good to add a short comment in doc/tag-index about
> >> the experiment results that have been changed.
b) when this might affect any user (e.g., parameter/option changes)
Does not need to be long, but you can probably figure out from what
is in tag-index the type of information/documentation we put there.
Cheers,
Jean-Michel
On Thu, Apr 28, 2011 at 11:48:51AM -0700, Ian Fenty wrote:
> JM,
> Would you please detail for me the kinds of changes which must be documented in tag-index? I clearly don't know which conditions ought to trigger one.
> Thanks!
> Ian
>
>
> On Apr 28, 2011, at 11:26 AM, Jean-Michel Campin wrote:
>
> > Hi Ian,
> >
> > I think this is not very original (only the 3rd ? 4th ? times I am
> > making this comment this week) but still relevant:
> >> Would be good to add a short comment in doc/tag-index about
> >> the experiment results that have been changed.
> >
> > Jean-Michel
> >
> > On Wed, Apr 27, 2011 at 10:08:59PM -0400, Ian Fenty wrote:
> >> Update of /u/gcmpack/MITgcm/verification/lab_sea/results
> >> In directory forge:/tmp/cvs-serv5230/lab_sea/results
> >>
> >> Modified Files:
> >> output_adm.evp.txt output_adm.noseaicedyn.txt output_adm.txt
> >> Log Message:
> >>
> >> Updating of verification experiments now that SEAICE_SALINITY has
> >> been changed to SEAICE_VARIABLE_SALINITY and SEAICE_salinity has been
> >> changed to SIsalFRAC.
> >>
> >> Noticed that ICE2WATR was still being used to initialize the HSALT
> >> in the lab_sea verification experiments. Removed it from the code
> >> but that broke testreport. Hence, some lab_sea/results/*txt files
> >> had to be replaced.
> >>
> >> Now pretty sure that ICE2WATR has been complete neutralized.
> >>
> >> : Modified Files:
> >> : lab_sea/results/output_adm.evp.txt
> >> : lab_sea/results/output_adm.noseaicedyn.txt
> >> : lab_sea/results/output_adm.txt
> >> : lab_sea/input_ad/data.seaice lab_sea/input_ad.evp/data.seaice
> >> : lab_sea/input_ad.noseaicedyn/data.seaice
> >> : lab_sea/input.salt_plume/data.seaice
> >> : lab_sea/code_ad/SEAICE_OPTIONS.h lab_sea/code/SEAICE_OPTIONS.h
> >>
> >> : 1D_ocean_ice_column/input_ad/data.seaice
> >> : 1D_ocean_ice_column/input/data.seaice
> >> : 1D_ocean_ice_column/code_ad/SEAICE_OPTIONS.h
> >> : 1D_ocean_ice_column/code/SEAICE_OPTIONS.h
> >>
> >> : seaice_obcs/input/data.seaice
> >> : seaice_obcs/code/SEAICE_OPTIONS.h
> >>
> >> : global_ocean.cs32x15/code_ad/SEAICE_OPTIONS.h
> >> : global_ocean.cs32x15/code/SEAICE_OPTIONS.h
> >> :
> >> : offline_exf_seaice/code_ad/SEAICE_OPTIONS.h
> >> : offline_exf_seaice/code/SEAICE_OPTIONS.h
> >> : ----------------------------------------------------------------------
> >>
> >>
> >> _______________________________________________
> >> MITgcm-cvs mailing list
> >> MITgcm-cvs at mitgcm.org
> >> http://mitgcm.org/mailman/listinfo/mitgcm-cvs
> >
> > _______________________________________________
> > MITgcm-devel mailing list
> > MITgcm-devel at mitgcm.org
> > http://mitgcm.org/mailman/listinfo/mitgcm-devel
>
>
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel
More information about the MITgcm-devel
mailing list