Changeset 16165 for branches/eam_branch_20080109/ippTasks/notes.txt

Timestamp:

Jan 19, 2008, 3:26:00 AM (19 years ago)

Author:

eugene

Message:

working on chip/hosts

File:

• branches/eam_branch_20080109/ippTasks/notes.txt (modified) (1 diff)

branches/eam_branch_20080109/ippTasks/notes.txt

@@ +1 @@
+
+2008.01.18
+
+  I'm working on the summit.copy.pro interaction with nebulous (and
+  those of the other ippTasks) and the assignment of jobs and data
+  locations to hosts on the basis of the chip/host relationship.  I
+  have defined a table which relates the chip (class_id) to the
+  desired host name.  There are a few places, and a few slightly
+  different ways, in which this gets used:
+
+  * choice of host for command execution:
+
+    every job which operates on a specific chip must be told the chip
+    host so it can run the job on that machine.  the information is
+    supplied in pantasks to the job with the 'host' command.  I've
+    made a pantasks macro 'set.host.by.camera' which takes the camera
+    and class_id, looks up the match in the chip/host table, and calls
+    the host command with the desired host.  If there is no match
+    (camera not listed in chip/host table or chip not listed in
+    table), the host is set to 'anyhost', which randomly chooses one.
+    I have used this command for all tasks which generate a pcontrol
+    command.  For the tasks which are performed at the camera level,
+    these are set to anyhost.  For the tasks which operate on stacks,
+    we can use the same structure to associate the skycell with a
+    host.  
+
+  * dsget output target:
+
+    dsget is called by pantasks in the task 'dsget'.  currently, dsget
+    accepts a --filename argument which specifies the output filename
+    to use.  we have to tell t
+  
+
+  * choice of output directory.   
+
+    the 
+
 
 2007.10.11