Editing Scanco Administration (section)

===Valid and Locked Settings for an eval script===

Each evaluation when running <code>UCT_EVALUATION</code> can be made <code>VALID</code> and <code>LOCKED</code>.

:<code>VALID</code>: The evaluation script shows up as an option to execute when running <code>UCT_EVALUATION</code>. When you notice script numbers missing in the list, it is because they have had <code>VALID=0</code>

:<code>LOCKED</code>: The evaluation script can be used, but the user cannot make changes to the script settings in <code>UCT_EVALUATION</code>. This is to protect from somebody causing an error in the script settings that affect all users.

It is not possible to delete a script, and it is not possible to add a script at an arbitrary script number. So, any newly added script gets the next monotonically increased script number. This can lead to scripts that have similar purposes being spread throughout the list of scripts, which is annoying.

It is possible to organize the scripts, although it is a fair amount of work and easy to make a mistake. As a normal user (e.g., 'xtremect2') run the script. If you are a different user you may need to set  the correct evalscript database first.

The most simple executable to run is

<pre>
run ut:UCT_UPD_EVALSCR_MISC.EXE

 <...snip...>
 * 578    127/563  (ML) Knee Segmentation
  579    128/569  NO PRINT - Patient Analysis 61µm, After manual corr. on GOBJ,NM
  580    128/570  NO PRINT - Patient Analysis 61µm, After manual corr. on GOBJ,NM
* 581    128/580  NO PRINT - Patient Analysis 61µm, After manual corr. on GOBJ,NM
  582    129/572  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
  583    129/573  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
* 584    129/574  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
Choose evalscript Record (IDX): [584]: 337
Description [XtremeCT II - Standard Radius Patient Analysis 61µm]: 
Valid [1]: 
Locked [1]: 
Favourite [0]: 
Category [32]: 

Save Record ? [Y]: 
</pre>

A more comprehensive executable that allows the user to edit parameters in the script is:

<pre>
run UT:UCT_UPDATE_EVALSCRIPT.EXE

<...snip...>
V IDX escript/Rec. Description
    1      1/1    XtremeCT Standard Patient Evaluation (RL,RR,TL,TR,CU)
    2      1/7    XtremeCT Standard Patient Evaluation (RL,RR,TL,TR,CU)
*   3      1/9    XtremeCT Standard Patient Evaluation (RL,RR,TL,TR,CU)
    4      2/2    QC1 Trabecular Morphometry
    5      2/8    QC1 Trabecular Morphometry
    6      2/384  QC1 Trabecular Morphometry
*   7      2/401  QC1 Trabecular Morphometry
    8      3/3    QC2
    9      3/6    QC2
   10      3/385  QC2
*  11      3/402  QC2
*  12      4/4    3D Segmentation of VOI, 1 solid objectAIM
*  13      5/5    3D Seg. of 2 VOIs: solid dense in transparent low dens obj obj
*  14      6/10   Bone Trab. Morphometry (3D Seg, 3D Calc, Print Sheet)et)eet)
*  15      7/11   Convert to DICOM
   16      8/12   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   17      8/13   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   18      8/14   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   19      8/15   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   20      8/16   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   21      8/17   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   22      8/18   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   23      8/23   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   24      8/24   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   25      8/33   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   26      8/57   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   27      8/58   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   28      8/71   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   29      8/72   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   30      8/79   RESOLUTION, Mimic, Std Pat Eval, copy to UR, submit AutoCont
   31      9/19   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   32      9/20   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   33      9/21   RESOLUTION, Standard Pat Eval, copy to UR, submit AutoCont
   34      9/22   RESOLUTION, XCT2STD, Std Pat Eval, copy to UR, submit AutoCont
 <snip>
  572    127/559  (ML) Knee Segmentation
  573    127/561  (ML) Knee Segmentation
* 574    127/563  (ML) Knee Segmentation
  575    128/569  NO PRINT - Patient Analysis 61µm, After manual corr. on GOBJ,NM
* 576    128/570  NO PRINT - Patient Analysis 61µm, After manual corr. on GOBJ,NM
  577    129/572  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
  578    129/573  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
* 579    129/574  XtremeCT II - Standard Radius/Tibia Patient Post-processing,NM
  580    130/0    New Record
Choose evalscript Record (IDX,*=Valid): [579]: 
</pre>

Press Enter many times until you are prompted with <code>Save [Y]</code>

The <code>*</code> indicates which scripts are active. You can see there are multiple versions of the same script in many cases. If you want to activate or deactivate a script you must use the IDX number (not the script number). For example, if you want to edit script 128, you select the active IDX, which is 576.

Copying script information from one IDX entry to another is a manual process you can do in <code>UCT_EVALUATION</code>. Be careful!

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