Editing Archive (section)

===How To: Evaluate a project (PRE)===

:* This is done in 2 steps: AIM extraction, AIM filtration.
:*Run the evaluation as user XUCT so that enough memory can be allocated for the job. To login as xuct on blund, type <code>blund</code> (see HowTo:).
:* <code>EVAL_HERZOG G 245</code> (runs the evaluation, with option G, on sample 245).
:* When <code>uct_evaluation</code> tool pops up, click <code>cancel</code> to get sample 245.
:*Select the <evaluation 3D> button, select <ROI>, then <start evaluation>.
:*Then <code>exit</code>.
:*To look at the latest <code>UCT_EVALUATION.LOG</code>, go to <code>cd scratch</code>
:*Once the AIM has been successfully extracted (it’ll be located in the measurement directory), start the second part of the analysis by typing: <code>EVAL_HERZOG SE 245</code> or <code>EVAL_HERZOG 245</code>. With no options defaults to GSE, and since option G is already processed, it skips to options <code>SE</code>.
::- Option <code>S</code> starts SAP with which the user can check that the AIM captures the data of interest.
::- Once you exit from SAP, the file is Gaussian filtered (option <code>E</code> in script), renamed to the PROJECTS directory, and the original ISQ file in the measurement directory is deleted.
:*Once the two steps of evaluation are finished, the filtered aims should be renamed to meaningful project names (see renaming HowTo's).
:*If anything goes wrong in the evaluation, goto the LOG directory in the HERZOG project to see the problem.