| Version | Author | Date | Details |
|---|---|---|---|
| 1.0 | ms/rgm | 2000 May 20 | first draft |
| 1.1 | rgm | 2000 June 14 | updated various sections and added technical notes at the start |
1. Computers, accounts, networks
********************************
Accounts We Use:
----------------
We use the following accounts
- cirsi
- intobs (for running the observing software ONLY on lpss13. DO not use
elsewhere, or you may have problems)
- intguest (a general account)
- int_login (used ONLY on the alpha TCS display)
What Computers Where
--------------------
We use the following machines (May 2000 run, ip numbers may
change!). Addresses are: host.roque.ing.iac.es
**The CIRSI Computers:
- guestip0 (aka circc) - Win 95 PC mounted on the telescope. No monitor
connected, but one should be available in the dome in case of
problems. Runs PixCel acquisition software, and is controlled remotely.
- guestip1 (aka cirob) - Win machine running pcANYWHERE to guestip0,
which it controls. THIS IS IT'S ONLY PURPOSE. Run no other software
here.
- guestip2 (aka cirds) - linux machine running 'samba' where data is
written by guestip0 (circc). Run no other software here. 'Samba' may
not start automatically if you reboot (so don't!) but if you do:
(i) Log in as root
(ii) type /etc/rc.d/init.d/smb [status|stop|restart|start]
type /etc/rc.d/init.d/smb start
**The INT computers:
- lpss13 (161.72.6.6)- SparcStation 20 Observing machine, run observing
scripts etc. from here (in a pink xterm). Also has TCS info displays,
and CIRSI/TCS talkers, which displays error messages. DO NOT run
netscape here.
- lpss14 - has all INT data discs mounted on it. It's downstairs.
- lpss8 (161.72.6.10) - ULTRA60, powerful machine for data
reduction. Also use netscape here (and NOT on lpss13). This is for
data reduction and quick look at pointing etc. It's a good idea to log
on as intguest here, but have plenty of cirsi windows as well so that
you can write to both the cirsi homespace and the cirsi space on the
INT data discs.
[ Also, a useful step is to load the Starlink software (e.g. this gets
Gaia, coco). Only use lpss8 for data reduction and running this
software! use:
source /star/etc/login
source /star/etc/cshrc ]
Gaia can be used to produce CIRSI finding charts, details of which
will be added at the end of these notes soon.
Where to use what account
-------------------------
a) Log into circc (guestip0) as cirsi
b) Log into cirob (guestip1) as cirsi
c) Log into lpss13 as intobs
d) Log into lpss8 as intguest
e) Log into cirds (guestip2) as cirsi
f) (If required) Log onto LPAS2 on the Alpha TCS as int_login
The Current (May 2000) network arrangement
------------------------------------------
Currently, data taken by guestip0 (circc) is written to the linux
machine guestip2 via a network drive mounted on guestip0. This SHOULD
THEN BE copied at the end of the night to one of the /obsdata/int
discs on lpss14. Use ftp to do this. The next day, make DAT tapes.
You can FTP as needed to guestip2 (from e.g. lpss8) to get the data
when it is written - but don't do lots of ftp-ing, or the network
slows, causing problems with the data taking. (You tend to lose data
by dropping loops, a bad thing...).
2. Typical startup procedure (computers etc.).
**********************************************
IMPORTANT: Restart guestip0 every day. Use pcANYWHERE on guestip1 to
do this. REMEMBER: Close all programs (e.g. the filter controller)
before restarting, or odd things and crashes can occur on
reboot, doing this can avoid problems during the night. Reboot guestip1.
In the LILO prompt introduce "win95" (without quotes) (push TAB to see options).
- Start pcANYWHERE if not running on guestip1 (cirob). Change the path
destination of the FITS files for the current night in the "pixel.ini" file (see 20).
Also be sure to make this directory on guestip2.
- Double-click on 'Cirsi camera'. (It takes about 2 minutes for guestip0 (circc) to
boot, you cannot connect during this time..). If the windows appears
pink, minimising and then maximising the window should cure it.
- Start the filter controller as well, and check the filter is in
position (more details on this later).
- Now goto lpss13. If the TCS is running (i.e. and xterm with SYS> is
there) type 'shutdownobsys' in the xterm and then logout of
lpss13. This is useful to get a fresh start.
- Use TCSEXIT to exit the TCS software on the alpha TCS control (where
the TO sits). Restart the TCS software from the alpha TCS display (if
you have a TO, he/she will do this). ** Make sure you use versions
I13-1-2 and s7-1 of the software, or things won't work **. These are
older versions compatible with CIRSI, and are not the default options!
- Once the TCS is loaded, log into lpss13 as 'intobs'. Minimise the
orange window that appears. In the pink window, type 'obssys' and
select the CIRSI option (no.20 in May 2000)
- Check where startobssys is. Type 'alias startobssys' and you should
get
source $top/$system/bin/startcirsi.csh $OBSSTATION;echo "startobssys
done".
Also check the following responses:
SYS> echo $top
/int
SYS> echo $system
s7-1
- type 'cleanup' in case the last shutdown was unexpected.
- type 'startobssys' and lots of windows pop-up. You can minimise the
autoguider as we don't use it. arrange the others so you can see them
all, the infodisp in particular.
The observing system should now be running happily on lpss13. Next,
startup of CIRSI for Remote Control
- cd to cirsi directory ('cd cirsi')
- check that the CIRSI send command is in your path
The source for this is in:
/home/cirsi/soft/cirsi/remote/ing
see the README and send.c for more details
SYS> where send
./send
- Set the CIRSI environment variable for remote control
SYS> setenv CIRSI 161.72.36.150 (note: May 2000 value...)
- Now check the link to CIRSI using:
SYS> send status [should return BUSY or READY or rejected if PixCel not
started. Also sometimes get UNKNOWN which is a bit weird]
If PixCel is started and you still get a "connection reject"; check
the Pixel.ini file on the windows machine (guestip1) for:
(i) SOCKET 16421
(ii) 161.72.6.6 [if using lpss13.roque.ing.iac.es]
- Check the TCS link that gets the TCS headers
Note: This file is updated by the user 'intobs' and is
currently read by PixCel as 'cirsi'. The file is created
by user 'intobs' by the script 'CIRSIgetfits' from packets
created by the INT command archive. The file is found in:
/home/cirsi/header.fit
(i) make sure there is a file header.fit exists. If not
touch it and make it world writable. This will ensure the
protection is always OK. An alternative would be to
get PixCel to point to /home/intobs/header.fit OR
you could use
ln -s /home/cirsi/header.fit /home/intobs/header.fit
BUT you might need to change CIRSIgetfits to write
header.fits to the correct locations.
Test this all as follows:
SYS> archive [and watch the Talker to see if there is any errors. It
should take around 2 seconds. Sometimes we see the error
DMA_time out ... read cryostat ... [This probably means it is looking for
some WFC stuff]
SYS> CIRSIgetfits 0 0 0 0
should return quickly with
Written /home/cirsi/header.fit
- Check the path where the data is written on guestip0. Change using
'send path ' (and put quotes round the path) if necessary. This
path will probably be to guestip2 (cirds), a linux machine, hence
samba must be running there.
- (OPTIONAL) Now try CIRSIgo to take an exposure.
- Print out some logsheets (found in /home/cirsi/public_html/logsheets)
3. Typical Startup Procedures (Telescope)
*****************************************
** NOTE: you only get a TO for the first *2* nights of the run!! MAKE
SURE YOU KNOW HOW TO OPERATE THE TELESCOPE!!!!! get him to show you
early on. You really need to know how to open up and shut down; notes
are given in the CIRSI green folder which should be lying around
somewhere (or more likely in RGM's office at the IoA). **
Full details of the procedures are given on the TO's web page. Read
carefully... but the general order is (skeleton outline):
DURING THE AFTERNOON/DAYLIGHT:
i) Fill the CIRSI dewar and note the time in the observing log on the
TCS console.
ii) Check the vacuum pressure via the HV instrument on the CIRSI
instrument 'cage'. Note this and the temperatures displayed on
guestip1 pcANYWHERE and note in the log AND the web file found in
/home/cirsi/public_html/CirsiDewarStatus/). Channel 5 gives the
temperature inside the dewar, and should be around -184.
AFTER DINNER:
It's a good idea to fill the dewar again now as well.
i) Turn off all the stairwell lights and ensure the blinds are pulled
down. Close all the doors to the dome and turn out ALL the lights in
the corridors on the observing floor, as some light leakage can occur.
ii) If you have a TO, he/she will do most of the following, if not,
it's down to you!
iii) Turn on the dome lights if not on (on the TCS console)
iv) ** Turn on the oil pump (on engineering rack) **
v) Move the telescope to zenith (either use 'park zenith' in computer
mode or do it by hand in engineering mode).
vi) Zeroset the telescope. The HA position should be near 12 O'clock
position, and the DEC near 9:50.
vii) On the TCS console type 'zeroset HA target' and 'zeroset DEC
target'.
viii) Use HA and DEC [+/-] buttons and in 'SM' mode move the telescope
through the zeroset positions stated above. the TCS will beep and the
zeroset light flash when this is done. The telescope is now zeroset.
ix) Open the dome. Use RAISE MICRO until the OVERTRAVEL indicator goes
off, then RAISE MAIN until open. Repeat for the lower shutter if you
need to use it (only for objects lower then 57 degrees zenith
distance).
x) Open the primary mirror cover using the engineering rack.
xi) Turn on the dome vent fan if you want to use it ** NOTE don't do
this in humid conditions, or you'll bring the humidity inside the
dome! **
xii) Turn off the dome lights and pull the blind down.
xiii) Put the telescope in COMP mode by turning the key switch on the
TCS console. Both SM buttons must be lit for this to happen. The
telescope is now under computer control.
ixv) Ensure that none of the manual control buttons are lit on the TCS
console, or likely the telescope won't track or the dome won't move or
something like that.
IF YOU HAVE PROBLEMS WITH THE TELESCOPE: Call the Duty Engineer (name
& number on whiteboard, or use the intercom. Don't worry about
dragging them out of bed if you have a problem). If you have concerns
about the weather and whether to open, try the WHT TO.
4. LOADING CATALOGUES
*********************
The INT catalogues are in /int/cat which is writable by 'intobs'. So
if you prepare a catlogue as user 'cirsi' then you can only put it in
the write place as 'intobs'.
To load a catalogue type
SYS> cmd TCS USER "include sa57_tcs.dat"
There is also a script which will load some default catalogues you
might use every night. It is run by:
SYS> CIRSILoadCats
and it will load a list of specific catalogues, which you can
update. These catalogues will also show you the correct format, which
is important or the catalogues will not be loaded. Update this script
as you add more object catalogues. NOTE: Catalogue entries are
case-specific.
5. Apertures
************
The following apertures are defined:
- Aperture 0 - Centre of CIRSI, i.e. not on any chip!
- Aperture 1 - Centre of chip 1
- Aperture 2 - Centre of chip 2 etc.
- Some default apertures are loaded on startup; if you change them,
then use:
SYS> CIRSILoadApertures
and update this file as you change them at the start of a
run or night.
6. Checking the pointing
************************
(i) 'gocat' to a very bright star from the system bright star
catalog:
There is a copy of this on the CIRSI ING WWW homepage
The telescope will move there, and place the star on aperture 0.
(ii) type 'aperture 1' (moves the telescope so that the star is
centered on chip 1.
(iii) type 'send chip 1' [to select chip 1 only to be read out]
take a 10sec 1 loop exposure (use 'send loops 1' and 'send exptime 10')
(iv) measure the x, y cordinates of this star with imexamine
WRITE THE NUMBERS ON THE LOGSHEET AS A PERMANENT RECORD
(e.g. 384, 524)
(v) X-offset: Subtract 512 from X and multiple by 0.457" => -58
Add this to the existing Aperture 0 offset.
(vi) Y-offset: Subtract Y from 512 [YES, THE SENSE IS DIFFERENT]
Add this to the existing Aperture 0 offset.
(vii) type 'cmd TCS USER "ENTER APERTURE 0 x y" where x & y are the new
aperture 0 values.
(viii) ** VERY VERY IMPORTANT **
(i) 'gocat' back to the target.
(ii) 'aperture 1'
(iii) Repeat the exposure and CHECK that the star is now centred.
(iv) If it isn't: You've made a mistake (easy to do...) OR the
above senses are wrong (they are from May 2000)
The boring command in section (vii) could be put into a
script [rgm 20000614]
(ix) NOW edit the CIRSILoadApertures script to have the
new value of aperture 0. This will mean that you can quickly
reload it later in the night OR the next night. Spending a minute
doing this now will saave you pain later.
7. FOCUSING
***********
This can be quite time-consuming...
There are two approaches, either focusing on a standard star (which
appears not to be as reliable, as you only have one measurement per
focus value), or focusing on a field (good in more crowded
fields).. Either way, use the following approach:
i) Use 'send chip 1', 'send loops 1' and 'send exptime 10'
i) type 'focus xxxx' where xxxx is the just below the lower end of
where you wish to start the focus test from. [note the command will
not execute if value is the actual current value]
ii) type 'CIRSIfocus value_start value_step nsteps' (a script)
e.g. CIRSIfocus 48.5 0.1 7
USE 0.2 AT THE START OF A RUN OR AT THE START OF THE NIGHT
NOTE: 'value_start' cannot be the same as the current focus value, or
the script will stick (a TCS problem we believe). Also watch for
sticking, and use to break out of script if necessary.
The frames will be taken, with an offset between the first and
subsequent frames. This allows the first frame to be subtracted from
the others to remove sky. Use 'imexamine' in IRAF to determine the
FWHM. As a guide, the focus value in Hx May 2000 was around 49.2mm, and
the focus should not change drastically during a run as the focus is
temperature compensated.
NOTE: THE J FILTER OFFSETS HAVE NOT BEEN DETERMINED RELIABLEY YET
8. STANDARDS
A list of suitable standards is linked from the CIRSI web page, and is
also one of the default catalogues loaded in when using CIRSILoadCats
- these are from Persson et al. (1998). Select a suitable standard
from there (they all have numbers like 9148). If you choose a Persson
standard, the script 'CIRSIstandard' will do the observation. Usage
is:
CIRSIstandard StandardNumber RunNumber
<> values are optional. The script will place the standard on aperture
1, with default observation parameters of 'loops' = 3 (or the value of
'loops' on the command line) and 'exptime' = 10s (or the 'ExpTime'
value on the command line). It's a good idea to defocus slightly
beforehand. CIRSIstandard uses a simple 4 x 100" dither script to take
the observations, which places the standard on each quadrant of chip
one. If the run crashes, use CIRSIstandard again, but add the dither
position of the crash.
Some standards from May/June 2000 run were:
H
LCIRS 1441-0031 9155 11.7
LCIRS 1221-0010 9149 11.9
Lockman 1006+4101 9142 11.7
SA57 1214+3535 9148 11.4
ELAIS-N1 1559+4736 9162 11.9
ELAIS-N2 1631+3009 9166 11.5
By hand type
CIRSIdither dithpat_100_4
9. PROGRAM objects
Make sure the object is in the catalogue, then:
gocat