|
|
| (613 intermediate revisions by 14 users not shown) |
| Line 1: |
Line 1: |
| __TOC__
| | #REDIRECT [[Main Page]] |
| | |
| | |
| ==OpenVMS Commands==
| |
| | |
| ===HowTo: Edit Scanco Submit Command Symbol===
| |
| | |
| In directory <code>DISK2:[MICROCT]MICROCT_SETUP_USER.COM</code> add the following line:
| |
| <pre>
| |
| $ SCANCO_SUBMIT_COMMAND :== SUBMIT/NOPRINT/QUE=SYS$SLOW /NOTIFY/LOG=SYS$SCRATCH:
| |
| </pre>
| |
| Then end session and log in again.
| |
| | |
| ===HowTo: Start a 3D evaulation from the terminal===
| |
| | |
| Warning: Do not change <code>uct_evaulation_v4.com</code> and <code>ipl_fixed_batch_v4.com</code> 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.
| |
| <pre>$ scanco_submit_command ue:uct_evaluation_v4.com/para=(xxx,yyy,zzz,…)</pre>
| |
| 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 <code>isq_to_aim_gobjbox.exe</code> and then give the relevant parameters. You can
| |
| <code>$ run um: isq_to_aim_gobjbox.exe </code>
| |
| to see what it's asking for.
| |
| By using gobjbox you do not need p3-p8. Therefore you can start the evaluation by giving:
| |
| <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 <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.]
| |
| 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.
| |
| | |
| ===HowTo: Get information about a sample or measurement from database===
| |
| The following will create a <code>sys$scratch:info.txt</code> file.
| |
| <pre>$ write_info</pre>
| |
| | |
| ===HowTo: Fix "last slice" error problem when extracting AIM from ISQ===
| |
| Sometimes the evaluation script (i.e., voi) converting the ISQ to an AIM fails because it tries to read one slice more than what is available in the ISQ data. The result of this failure is that the 3D analysis appears to fail and no .AIM or _SEG.AIM is created in the data directory. For example, it may have tried to read 261 slices, but there were only 260 slices available.
| |
| The easiest work around is to make sure that the white bounding box in the uct_evaluation program does not include the last slice (largest Z dimension). Scanco is aware of this problem and will fix it in future software releases (V5.2).
| |
| | |
| ===HowTo: Use the new UCT_BACKUP software===
| |
| New Features (i) You can now select multiple samples with the Shift and/or the Ctrl key; and (2) You can use the sample name filter field on top to display only names containing the filter string.
| |
| Start the move/copy by clicking on <code>'Start...'</code>
| |
| The <code>'Script...'</code> button is for advanced users.
| |
| Advanced Users:
| |
| Use of the 'Script...' button: this will generate a script,
| |
| <code>sys$scratch:archive.com</code>,
| |
| that you may submit in batch mode later (e.g. over night) by typing:
| |
| <pre>$ scanco_submit_command sys$scratch:archive.com/after=23:59</pre>
| |
| (In a multi-computer cluster setup, you may want to specify the exact queue name of the computer that has the tape hooked up by giving e.g. <code>/que=sceval_fast</code> )
| |
| Insert a tape, but do NOT mount the tape in the normal program. (If necessary: if it's a new tape, initialize it as usual). The batch job will be started one minute before midnight in the example above.
| |
| <code>$ show entry</code> will show you that it is holding until then.
| |
| See <code>$ help submit /after</code> and <code>$ help dcl_tips date_time example</code> for more help on this.
| |
| <b>Little Reminder:</b>
| |
| While the tape is running and writing to it, DO NOT LOG OUT, DO NOT INTERRUPT THE PROGRAM! This would make that tape unusable from this point on - you could still read from that tape up to this point, but could not add more scans to this tape.
| |
| What to do when tape is full? It then displays some message about continuing on another tape. Hit ctrl/c to interrupt the program, take a fresh tape, initialize it, select the remaining scans to archive again, hit 'start'.
| |
| And last but not least: WE STRONGLY URGE YOU TO DO THE WEEKLY BACKUP (SAFETY BACKUP OF USER DISK1 WITH YOUR DATABASES ON IT).
| |
| Two users DID experience disk crashes last year, and without the weekly backup, you may still have all scans on the data disk (e.g. disk2), but without the databases you cannot tell which scans belong the which sample!
| |
| How to do weekly backup: insert 'special' weekly backup tape, e.g. week_a, and
| |
| just hit 'Full backup to tape'.
| |