transp runs made on JET data are available for analysis by researchers at any collaborating institution. However, we would ask that you consider the following points, before commencing an analysis of this data -
- A common reason for not entering runs in the transp database is that they are in some way defective. Only runs with database entries should be considered for analysis
- Before using a run which was not made at your request, consult the author to be sure it is suitable for the intended purpose
- Consult the transp RO for advice before using legacy runs, where the author is no longer available.
- Avoid comparisons between runs made with different versions of the transp code; older runs can usually be repeated without much difficulty, if necessary.
- Use consistent run parameters ( choice of Eq. Solver etc ) for runs to be compared.
- Consult the Bugs index on the news pages, for a list of known and of previously solved problems.
- If data from a run is used in a publication, ask the author of the run to append a comment to the database, giving a reference to the published work.
- Publications should include appropriate references to the transp code; transp programmers need funding too.
The TranspData find command returns the Transp version used, database status etc for a transp run