How To's: Difference between revisions
| Line 22: | Line 22: | ||
*P3-5: start x (pos x), y, z | *P3-5: start x (pos x), y, z | ||
*P6-8: dim x, y, z | *P6-8: dim x, y, z | ||
The parameters p3-p8 come from the white bounding box. The problem is that when you start from the terminal you do not have these. This problem can be overcome by using the isq_to_aim_gobjbox.exe and then give the relevant parameters. You can | The parameters p3-p8 come from the white bounding box. The problem is that when you start from the terminal you do not have these. This problem can be overcome by using the <code>isq_to_aim_gobjbox.exe</code> and then give the relevant parameters. You can | ||
$ run um: isq_to_aim_gobjbox.exe | <code>$ run um: isq_to_aim_gobjbox.exe </code> | ||
to see what it's asking for. | to see what it's asking for. | ||
By using gobjbox you do not need p3-p8. Therefore you can start the evaluation by giving: | By using gobjbox you do not need p3-p8. Therefore you can start the evaluation by giving: | ||
$ scanco_submit_command ue:uct_evaluation_special_josh.com –/para=(1,dk0:[microct.data.0000275.0000245]c0000332.ISQ) | <pre>$ scanco_submit_command ue:uct_evaluation_special_josh.com –/para=(1,dk0:[microct.data.0000275.0000245]c0000332.ISQ)</pre> | ||
Note that you can make uct_evaluation_special_josh.com such that there is no need for P1 (change p2 to p1 in the script, etc). | Note that you can make <code>uct_evaluation_special_josh.com</code> such that there is no need for P1 (change p2 to p1 in the script, etc). | ||
[Alternatively to using the gobjbox you could use the normal isq_to_aim, but hard code the dim and pos.] | [Alternatively to using the gobjbox you could use the normal isq_to_aim, but hard code the dim and pos.] | ||
Then call whatever IPL files you want to call. Look into fixed_batch_v4 to see how we turn on the database always on the first line of every IPL part, and how we calculate parameters. | Then call whatever IPL files you want to call. Look into <code>fixed_batch_v4</code> to see how we turn on the database always on the first line of every IPL part, and how we calculate parameters. | ||
Revision as of 18:03, 9 August 2005
OpenVMS Commands
HowTo: Edit Scanco Submit Command Symbol
In directory DISK2:[MICROCT]MICROCT_SETUP_USER.COM add the following line:
$ SCANCO_SUBMIT_COMMAND :== SUBMIT/NOPRINT/QUE=SYS$SLOW /NOTIFY/LOG=SYS$SCRATCH:
Then end session and log in again.
HowTo: Start a 3D evaulation from the terminal
Warning: Do not change uct_evaulation_v4.com and ipl_fixed_batch_v4.com in .eval, but only work on your own file (i.e., eval_steve).
First, an explanation of how the normal evaluation runs by hitting the 'Start 3d' button.
$ scanco_submit_command ue:uct_evaluation_v4.com/para=(xxx,yyy,zzz,…)
There are 8 parameters:
- P1: number of print outs of our results sheet
- P2: the ISQ filename
- P3-5: start x (pos x), y, z
- P6-8: dim x, y, z
The parameters p3-p8 come from the white bounding box. The problem is that when you start from the terminal you do not have these. This problem can be overcome by using the isq_to_aim_gobjbox.exe and then give the relevant parameters. You can
$ run um: isq_to_aim_gobjbox.exe
to see what it's asking for.
By using gobjbox you do not need p3-p8. Therefore you can start the evaluation by giving:
$ scanco_submit_command ue:uct_evaluation_special_josh.com –/para=(1,dk0:[microct.data.0000275.0000245]c0000332.ISQ)
Note that you can make uct_evaluation_special_josh.com such that there is no need for P1 (change p2 to p1 in the script, etc).
[Alternatively to using the gobjbox you could use the normal isq_to_aim, but hard code the dim and pos.]
Then call whatever IPL files you want to call. Look into fixed_batch_v4 to see how we turn on the database always on the first line of every IPL part, and how we calculate parameters.