RE: Improving Operating Speed

["Albertson, Chris" <CAlbertson@primeadvantage.com>]

Here is what would need to be done.

What you want chris.exe to do
is the whole job of reading out the RAM card _and_ writing
out the data to two FITS files.  I have a dot.c file that
contains functions that will do this.  The function that
reads the RAM card simply does a "read" from the MKIV device.
The actual I/O is done in the Kernel level device driver.

So, one would have to swipe the I/O code out of the device
driver and write a "main" program that would call the functions
and read in site specific stuff (lat, long, name of site ...)
from a config file.  Well you can use my config file routine too
if you want or skip it and simply pass that data as
arguments.   It's really not that much to do.


> -----Original Message-----
> From: Tom Droege [mailto:tdroege@veriomail.com]
> Sent: Monday, January 29, 2001 3:15 PM
> To: Albertson, Chris; tass@listserv.wwa.com
> Subject: RE: Improving Operating Speed
> 
> 
> Chris and all,
> 
> OK, tell me where the work is?  I realize that there is work in the 
> smallest thing.  If you have written code that writes out a 
> .fts file, then 
> all that is left is to pass the arguments.  To me this looks like:
> 
> SHELL chris.exe, Vfilename, Ifilename, otherthings...
> 
> I already have the filenames.  I just need a name for the 
> .exe code.  We 
> can put in placekeepers for the otherthings.  Various times, 
> etc..  So is 
> this a huge task?  (I am challenged to write with a non - functioning 
> second letter of the alphaxet key.)
> 
> Am I missing something?
> 
> Tom Droege
>