...
Also, and that is not a detail, test_CalRecon.py must be called from a command-line prompt, and will directly issue cmt commands. Thus, the windows command-line shell must be configured for cmt. For a developer who usually work with MrVcmt, such a configuration is not
done by default. Typically, one lack the definition of %CMTPATH%, which can be done in the windows registries, or interactively at the dos prompt, or within some script myscript.bat which you call at the dos prompt before starting the validation. Example :
| No Format | ||||
|---|---|---|---|---|
| ||||
dos> set CMTCONFIG=VC8debug
dos> call D:\ground\applications\CMT\v1r18p20041201\mgr\setup.bat
dos> set CMTPATH=D:\Users\chamont\MyDevProject:D:\ground\GlastRelease\v6r0
dos> cd D:\Users\chamont\MyDevProject\CalRecon\src\test
dos> python validate.py
|
Input Data
On one hand, we tried to setup standalone jobs which do not depend on numerous external packages, especially Tkr ones. We want here to check the internals of CalRecon, and hope the global integration is checked at a higher level. Also, we want to modify CalRecon and to be able to check the validity of such changes, independantly of parallel Tkr changes.
...