Editing Scanco Administration (section)

====UCT_EVALUATION customization====

When you start <code>UCT_EVALUATION</code> and select <code>Scripts</code> from the top menu, and then <code>Modify</code>, select a script. You can choose the radio button for <code>Basic</code> or <code>Advanced</code>. In the <code>Basic</code> you'll see something like this:

 Project: UPAT_XT2
 Eval-Script: UE:UCT_EVALUATION_V6.COM
 IPL-Script: UE:IPLV6_UPAT_E5E6_XT2.COM
 User-Script: UE:STARTER_UPAT_POSTPROCESS.COM

Make sure that IPL-Script always has a script named IPLV6_... and that User-Script always has names like EVAL_...

Switch into <code>Advanced</code> mode and you'll see all the variables explicitly set. For example, a typical <code>P1</code> value is:

 EVAL --> UE:UCT_EVALUATION_V6.COM|UE:IPLV6_UPAT_REDO_E5E6_XT2.COM|UE:STARTER_UPAT_POSTPROCESS.COM

If you select <code>EVAL</code> you will see the window at the bottom explain what each parameter is. For example for <code>EVAL</code> it says:

 EVAL: evalfile | iplfile | userfile0 | userfile1 [| userfileN ...] (Nmax = 5)

So, that means <code>Eval-Script</code> is <code>UE:UCT_EVALUATION_V6.COM</code>, <code>IPL-Script</code> is <code>UE:IPLV6_UPAT_REDO_E5E6_XT2.COM</code> and <code>User-Script</code> is <code>UE:STARTER_UPAT_POSTPROCESS.COM</code>.

When you run an evaluation with this script it will create a file in the measurement directory called something like <code>E0000684_EVAL_UPAT_XT2.COM</code>, which will contain:

 <--snip-->
 $ IPL_CALC2   :== 
 $ IPL_CALC3   :== 
 $ IPL_CALC4   :== 
 $ IPL_CALC5   :== 
 $ IPL_CALC6   :== 
 $ IPL_CALC7   :== 
 $!
 $! Defining entry point for IPL Loops:
 $!
 $ UCT_EVALUATION_CUSTOM_TARGET:
 $!
 $!
 $! Starting IPL
 $!
 $ @UE:IPLV6_UPAT_E5E6_XT2.COM
 $!
 $! User Procedure 0:
 $ SET NOON 
 $ @UE:UCT_EVALUATION_V6.COM -
 "EVAL:UE:UCT_EVALUATION_V6.COM||UE:UCT_EVALUATION_V6_UPAT_FILL_E5E6.COM|UE:UCT_EVALUATION_V6_CREATE_TIF.COM|UE:UCT_EVALUATION_V6_UPAT_PRINT_E5E6.COM" -
 <--snip-->

The <code>UCT_EVALUATION_V6.COM</code> does the parsing of all variables passed by the GUI and then writes a script that is executed, beginning with all definitions of all the symbols. It then calls the IPL-script, which is written to the output file (command procedure to be executed as a batch job) as

 write outfile "$ @UE:''iplfile'"

Your User-Script(s) are then <b>EXECUTED</b> during the parsing, so they need to add (write) content to the script rather than do something. So these scripts need to <b>WRITE</b> the <b>COMMANDS</b> of what has to be done later, not contain the commands itself. For example, rather than

 $ delete 'ipl_file'

It needs to be 

 $ write outfile "$ delete ''ipl_file'"

[[Image:Redirect.jpg|15px]] [[#top|''Return to Contents'']] or [[Main_Page|''Return to Main Page'']]