|
«
|
May
2012
|
»
|
| Su |
Mo |
Tu |
We |
Th |
Fr |
Sa |
|
|
|
1 |
2 |
3 |
4 |
5 |
| 6 |
7 |
8 |
9 |
10 |
11 |
12 |
| 13 |
14 |
15 |
16 |
17 |
18 |
19 |
| 20 |
21 |
22 |
23 |
24 |
25 |
26 |
| 27 |
28 |
29 |
30 |
31 |
|
|
|
Versioning Practices
- CQL3D, GENRAY
- Use CVS version control. "Major" code versions tagged in CVS, matching variable in code and incorporated into all output (.ps, netCDF, text). "Minor" versions may not be captured in CVS. Outputs (netCDF currently excepted) also include time of execution, uname output.
- M3D
- Uses CVS version control (uncontrolled branches exist). No mechanism to associate output/files with specific executable or source.
- NIMROD
- Uses SVN version control. Match run date with SVN repository to recover version. Variable set to SVN $Revision$ keyword, written to nimrod.out.
- TORIC
- Uses SVN version control. SVN version string and date are put into output files. Also stored as static variable in executable, visible with
strings. Input is also versioned.
- AORSA
- Is not presently version controlled. Fred has been attaching version numbers for his own purposes. He is presently at version 13. He actually uses two different sources (versions 12 and 13) that use different solvers. Version 13 uses the HPL package that is not presently available a NERSC
Created by
bernhold
Last modified
2007-11-08 14:34
|