RE: standard FITS libraries

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

Michael,

I see you now have a Mk IV camera.

I want to get the software effort off the ground.  Arne
is interested but the guy who runs NOFS' internal network
has some issues to work through.  Arne wants to get his
Mk IV control PC outside the NOFS firewall so I can get at
it from home.  We could then spit the software development
tasks.

If you want to joint the effort we ca work a three way split
of the remaining work.

The software is at present a kind of gold plated shell.  Lots
of bells and whistles but "no beef".  In other words lost of
support functions. It can queue commands, read/write the RAM
buffer.  Accept many concurrent client connects, ve gotten the
FORTRAN based starlib library, cfitsio and other to link.
Everything but send commands to a real Mk IV camera. I figure you
and Arne are better at figuring how many stepper motor steps
it would take to point at a given ra,dec them I am.  I know
a lot more UNIX internals then spherical trig.  You will see
if you look at the code that the functions to be filled in
are isolated, one function per dot.c file.  

For sample the is one file called something like "point_at.c"
that is given an ra and dec.  It has available utility functions
that can send commands to the STAMP and that will return the
current state of the camera extrapolated (dead reckoned) from the
last know point and rate.