all_probes: Jan2016
  1. What is the problem?
  2. Jan2016 - A solution?
  3. What if I DO want a custom set of probe positions?



What is the problem?

We are frequently needing information about the current probe positions. Moreover, we need a way of handling this on different machines and under different conditions. The "all_probes" script was designed to address these issues.




Jan2016

I have modified all_probes so that it produces command line output AND device-specific local files. The command runs on mcs as sco and astronomer, and it also runs on SCO's home linux system. NOTE: The mcs user is STILL responsible for insuring that a data dump has been performed prior to running all_probes. Below I demonstarte usage and show typical outputs for scohome and mcs runs:

 

Usage: all_probes Y
arg1 - perform cleanup? (Y/n)

On mcs (as sco) 
===============
[sco@mcs ~/work]$ all_probes Y 
Machine you are running from is: mcs
Probe positions from Dumpit.1_c: 
  0.13896  -0.07499 gc1
 -0.15999  -0.02400 gc2
  0.11998   0.11997 wf1
 -0.11999  -0.11998 wf2

[sco@mcs ~/work]$ ls 
probe.gc1  probe.gc2  probe.wf1  probe.wf2

[sco@mcs ~/work]$ cat probe.gc2 
 -0.15999  -0.02400 gc2


On scohome  
==========
% all_probes Y 
Machine you are running from is: sco
I am returning default probe positions:
  0.00000  -0.16000 gc1
  0.00000   0.16000 gc2
  0.16000   0.00000 wf1
 -0.16000   0.00000 wf2

% ls 
probe.gc1  probe.gc2  probe.wf1  probe.wf2 

% cat probe.wf2 
 -0.16000   0.00000 wf2






What if I DO want a custom set of probe positions?

Sometimes I want to be able to access a unique (custom) set of probe positions. I usually use this when I am working on a non-mcs machine (when I can not get to an updated Dumpit.1_c file). Sometimes, I have inserted a section in all_probes that recognizes a local file called "Probes.Current" if it is present. In such a case, the values (for all four probes!) are read from there. Just as in the normal all_probes run, the positions are written to standard out and to appropriate "probe.*" files. Here is an example:

 


% ls
Probes.Current 

% cat Probes.Current
  0.05000  -0.15000 gc1
  0.00000   0.15000 gc2
  0.14000   0.00000 wf1
 -0.13000   0.00000 wf2

% all_probes

Usage: all_probes Y
arg1 - perform cleanup? (Y/n)
Machine you are running from is: sco

Reading Telecen X,Y from a local Probes.Current file. 
0.05000 -0.15000 gc1
0.00000 0.15000 gc2
0.14000 0.00000 wf1
-0.13000 0.00000 wf2

% ls
probe.gc1  probe.gc2  Probes.Current  probe.wf1  probe.wf2 

% cat probe.*
0.05000 -0.15000 gc1
0.00000 0.15000 gc2
0.14000 0.00000 wf1
-0.13000 0.00000 wf2

 



Back to SCO CODES page