[MITgcm-support] MITgcm switch to TAF version 2 (discontinue flag "-v1")

[Patrick Heimbach]

To TAF users of MITgcm:

the latest MITgcm checkpoint64m (13-August-2013) contains a major change regarding the usage of TAF, based on a joint (and mutually approved) implementation between Fastopt and MITgcm developers. The switch enables TAF's new default functionality ("version 2"), which changes the way the TAF-generated code is being built. TAF flag "-v1" is no longer needed, and TAF users will be able to readily use latest TAF versions.

As per agreement, older (pre-checkpoint64m) MITgcm versions that still require "-v1" will be supported for another three years through frozen TAF version 2.3.8 and with corresponding TAF flag adjustments contained in MITgcm's repository under tools/adjoint_options/ (e.g., for checkpoint64l), although Fastopt will not be able to provide bug fixes for that TAF version.

Cheers
-Patrick

---
Patrick Heimbach | heimbach at mit.edu | http://www.mit.edu/~heimbach
MIT | EAPS 54-1420 | 77 Massachusetts Ave | Cambridge MA 02139 USA
FON +1-617-253-5259 | FAX +1-617-253-4464 | SKYPE patrick.heimbach

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1588 bytes
Desc: not available
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20130816/05864fa2/attachment-0001.p7s>