[WAM-IPE] Locations for WAM-IPE app and code: How can we track the previous revision changes after your re-organization?

[Samuel Trahan - NOAA Affiliate]

Naomi,

Also, another good command for getting differences is diff.  It is more
flexible and can recurse into externals.  It can also compare against
on-disk copies that are not from subversion, such as comparing against
nwprod.

svn co https://svnemc.ncep.noaa.gov/projects/nems/
branches/WAM-IPE_NEMS201606/src/module_MEDIATOR_SpaceWeather.F90 at 90097 old
svn co https://svnemc.ncep.noaa.gov/projects/nems/
branches/WAM-IPE/quasitrunk/src/module_MEDIATOR_SpaceWeather.F90 new

diff -rU3 -x.svn old new > my.diff

Meanings:

svn co https://... old = check out this branch in a directory called "old"
diff
  -r = recurse into subdirectories
  U3 = universal format diff with three lines of context (same format as
svn diff)
  -x.svn = do not walk into subversion metadata directories
  old new = diff the two directories

Another useful option is -w which ignores differences in whitespace.

  diff -rwU3 old new > my.diff

Sincerely,
Sam Trahan

On Thu, Mar 30, 2017 at 4:53 AM, Naomi Maruyama <naomi.maruyama at noaa.gov>
wrote:

> Hi Sam,
>
> Thank you very much for your re-organization.
>
> I have a quick question. How can we track the previous branch revision
> changes after your re-organization?
> Recently, Weiyu has some problems with running WAM-IPE after he made some
> changes to the WAM Z(height) calculation. Some of us are discussing to
> identify which versions of the code he used. For example, Weiyu's version
> was the revision number 90097 of the previous WAM-IPE_NEMS201606 branch.
> How can we do svn diff module_MEDIATOR_SpaceWeather.F90 between his
> branch version and the latest version of the trunk(90371)? Does this work?
>
> $ svn diff -r 90097:90371 module_MEDIATOR_SpaceWeather.F90
>
> Thanks.
>
> Regards,
> Naomi
>
>
> On 3/29/17 2:16 PM, Samuel Trahan - NOAA Affiliate wrote:
>
> Hi all,
>
> The WAM-IPE_NEMS201606 branches are gone.  The WAM-IPE application now
> resides here:
>
> https://svnemc.ncep.noaa.gov/projects/nems/apps/WAM-IPE/trunk
>
> The GSM and NEMS "quasi-trunks" are here:
>
> https://svnemc.ncep.noaa.gov/projects/nems/branches/WAM-IPE/quasitrunk
> https://svnemc.ncep.noaa.gov/projects/gsm/branches/WAM-IPE/quasitrunk
>
> There are cron jobs monitoring those three locations; you'll receive an
> email from wam-ipe at noaa.gov if anything changes.
>
> The WAM-IPE application has the following externals:
>
>               NEMS  -r90130 https://svnemc.ncep.noaa.gov/
> projects/nems/branches/WAM-IPE/quasitrunk
> NEMS/src/atmos/gsm  -r90126 https://svnemc.ncep.noaa.gov/
> projects/gsm/branches/WAM-IPE/quasitrunk
> NEMS/src/atmos/nmm  -r85687 https://svnemc.ncep.noaa.gov/
> projects/nems/external_comps/NMM
>             IPELIB          https://github.com/
> IonospherePlasmasphereElectrodynamics/ipe/tags/WAM-IPE-TAG-20170323/
>                IPE  -r85943 https://svnemc.ncep.noaa.gov/
> projects/ipe/branches/nuopc_cap
>            DATAWAM  -r73436 https://svnemc.ncep.noaa.gov/
> projects/nems/external_comps/DATAWAM/trunk
>            DATAIPE  -r65981 https://svnemc.ncep.noaa.gov/
> projects/nems/external_comps/DATAIPE/trunk
>
> Note that we're pointing to a specific revision or tag of everything.
> That lets us make tags of the application without having to make tags in
> each component.
>
> Sincerely,
> Sam Trahan
>
>
>
> --
> --------------
> Naomi Maruyama
> CIRES, Univ. of Colorado Boulder
> NOAA Space Weather Prediction Center
> phone: +1 303.497.4857
> email: naomi.maruyama at noaa.gov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/wam-ipe/attachments/20170330/ad2f7936/attachment-0001.html