P66-502
P66-502: Active Asteroids and Other Unusual Solar System Objects
P.I.: Jane Luu
This is a ToO and SoftToO program for non-sidereal targets (rates < 50''/hour).
All observations will be triggered via the OB system.
ALFOSC instrument setup:
- Gr #3
- Slit_1.0''
- B(#74), V(#75), R(#76), i(#12)
The corresponding commands to run the tcs.asteph for the different objects are:
- tcs.asteph -t comet -n \"2017 K2\"
- tcs.asteph -n \"2023 JN16\"
- tcs.asteph -t comet -n 12P
- tcs.asteph -t comet -n \"2024 S1\"
- tcs.asteph -t comet -m optimal-ll -n \"2024 S1\"
In the case of spectroscopy, dont forget to set the parallactic angle, i.e. use tcs.asteph -m para -n \"NAME\"
Daytime calibrations:
The standard twilight flats are sufficient.
Run alfosc.alfosc-calibs in the morning after observations. This provides biases
for both modes with the window and/or binning used, as well as halogen flats and arc lamps
for the spectroscopy mode used.
Observing instructions:
The OB comments will indicate the preferred order of the OBs whether standards should be
taken before or after.
- Go to directory: cd ~/obs/scripts/66-502/
Do ls -lrt to see the scripts and run them as indicated in the trigger. Note
the target "NAME" as given in the trigger for use below.
- When the OB generator asks you to do the pointing
and differential tracking in another sequencer window , do it as follows:
- Use tcs.asteph -n "NAME" for imaging OBs
- Use tcs.asteph -m para -n "NAME" for spectroscopy OBs (parallactic angle)
this calls up JPL Horizons to get position and RA/DEC rates at the current UT.
Check that the output given in the terminal refers to the desired object.
- Cut and paste the sequencer commands output from tcs.asteph (the 4 last lines) one by one.
The 4th line starts the actual differential tracking and guiding:
tcs.reposition-guide-probe RA-rate DEC-rate
and you can check that this is happening by noting that the star box is moved to one edge of
the guide TV screen, and the guide star is entered.
- Now press return in the sequencer window where the
OB was started in order to continue the OB script and start the observations.
The star box is placed at the optimal position on the guide TV screen, the differential tracking and guiding is started.
The autoguider box will move at the differential tracking rates and guiding will stop when the box reaches the
edge of the monitor (size is 70''). These targets have expected rates below 50''/hour, and the rates
typically do not change over the time of the observations. Most likely the whole observation is
possible without having to reposition the star box on the autoguider screen, but if you
have to reposition, just repeat the above command:
tcs.reposition-guide-probe RA-rate DEC-rate
Note that the TCS will give a warning beep when there is 120 sec left before the star box reaches
the edge, then again at 90 and 60. Make sure you reposition before the edge is reached.
- In order to locate the target, which should be close to the centre of the CCD, you may need a finding
chart, especially for spectroscopy. In a browser on the Florence computer to your right, open either
of the links:
Note that for the Lowell astfinder you can enter the target name, set observatory to "950 la Palma",
FOV to 390'' for ALFOSC, and you have the possibility to set the time steps of the trajectory.
- In addition to comments in the OB queue, remember to fill the
tracking log of this program.
P66 tracking
P67 tracking
P68 tracking
P69 tracking
| Program Tracking |
| Proposal |
66-502 |
| Semester |
P70: 20241001 - 20250401 |
| Principal Investigator |
Jane Luu |
| Programme |
Active Asteroids and Other Unusual Solar System Objects |
| Instrument |
ALFOSC |
| Time Allocation |
2 triggers, 3h per target |
| Total Nights |
6h |
| Type |
ToO+SoftToO |
| Notes |
Override. Follow-up soft triggers during Nordic service or Technical nights |
| Total Time Spent |
03:54 (hh:mm)
|
| Proposal |
Date |
Time |
Type |
Targets |
Files |
Comments |
Status |
|
| 66-502 |
2024-10-02 |
00:00 |
ToO |
2024S1 |
ALHj020059 |
Observations tried, got one image with 6" seeing, but had to close due to high winds. Failed. |
Failed |
|
| 66-502 |
2024-10-03 |
00:23 |
ToO |
BD-12_2918, 2023jn16 |
ALHj030157 - ALHj030160, ALHj030168 - ALHj030175 |
Observed with clear sky, but bad seeing (around 2 acrsec). |
Observed |
|
| 66-502 |
2024-10-04 |
00:22 |
ToO |
2024s1, BD-12_2918 |
ALHj040188 - ALHj040199 |
Observed with clear skies, sub-arcsec seeing. Comet clearly visible |
Observed |
|
| 66-502 |
2024-10-05 |
00:20 |
ToO |
2024s1, BD-12_2918 |
ALHj050114 - ALHj050125 |
Observed in thin clouds with seeing around 1.3" |
Observed |
|
| 66-502 |
2024-10-06 |
00:00 |
ToO |
|
|
Could not observe targets due to high winds |
Failed |
|
| 66-502 |
2024-10-07 |
00:00 |
ToO |
2024s1, BD-12_2918 |
ALHj070348 - ALHj070359 |
Observed in clear skies with seeing around 1.3". Wrong target. Set to failed. |
Failed |
|
| 66-502 |
2024-10-08 |
00:18 |
ToO |
2024s1, BD-12_2918 |
ALHj080127 - ALHj080138 |
Observed in dusty skies with seeing around 1.0" |
Observed |
|
| 66-502 |
2024-10-09 |
00:17 |
ToO |
2024s1, BD-12_2918 |
ALHj090168-179 |
Dark sky good seeing high airmass |
Observed |
|
| 66-502 |
2024-10-10 |
00:22 |
ToO |
2024s1, BD-12_2918 |
ALHj100144 - ALHj100153 |
Clear skies and sub-arcsec seeing |
Observed |
|
| 66-502 |
2024-10-11 |
00:11 |
ToO |
BD-12_2918, 2024s1 |
ALHj110161 - ALHj110170 |
The standard star was observed with thin clouds and seeing around 2.0''. The observation of 2024s1 had
cloud coverage and I could not discern the target well in the exposures, so I set it as failed. |
Failed |
|
| 66-502 |
2024-10-12 |
00:00 |
ToO |
|
|
Missed due to observing restrictions caused by high winds. |
Failed |
|
| 66-502 |
2024-10-13 |
00:00 |
ToO |
- |
- |
Target could not be observed due to thin clouds present in the sky that did not meet the clear skies requirements set for the OB. |
Failed |
|
| 66-502 |
2024-10-14 |
00:00 |
ToO |
|
|
No observations due to bad weather |
Failed |
|
| 66-502 |
2024-10-16 |
00:22 |
ToO |
BD-12_2918, 2024s1 |
STHj160001 - STHj160010 |
Observed with clear skies. |
Observed |
|
| 66-502 |
2024-10-17 |
00:03 |
ToO |
2024s1, BD-12_2918 |
STHj170016 - STHj170025 |
Observed in clear skies with seeing around 0.7" far into morning twilight. This might have messed up the tracking of the target. |
Observed |
|
| 66-502 |
2024-10-18 |
00:22 |
ToO |
BD-12_2918, 2024s1 |
ALHj180201 - ALHj180202 ; ALHj180212 - ALHj180219 |
Target observed using blind tracking, the ending of the OB was past nautical twilight so it's probably not useful data, but the target seems visible in the first exposures of the OB. |
Observed |
|
| 66-502 |
2024-10-19 |
00:26 |
ToO |
BD-12_2918, 2024s1 |
ALHj190143 - ALHj190144 ; ALHj190159 - ALHj190164 |
Started exposures at 6:29 UT because before the target was too low for the telescope. Finished at 6:36 UT. Observed through some thin clouds after nautical twilight. |
Observed |
|
| 66-502 |
2024-11-05 |
00:12 |
ToO |
SA104_598, 2024s1 |
ALHk050309 - ALHk050310, ALHk050316 - ALHk050321 |
I did not identify the comet from the frames although it should had been there according to NOT Aladin. |
Observed |
|
| 66-502 |
2024-11-08 |
00:06 |
ToO |
- |
- |
Could not be observed due to thick clouds in the direction of the target. |
Failed |
|
| 66-502 |
2024-11-09 |
00:10 |
ToO |
SA104_598, 2024s1 |
ALHk090199 - ALHk090206 |
Target observed at 06:28 UT using blind tracking (tcs.asteph -t comet -g blind -n 2024 S1), with clear skies and seeing around 1.7 arcsec |
Observed |
|
The above information is collected from the ToO/Mon reports that have been created by the observer.
Should any of the observations have been carried out using the OB system, you will find additional information
HERE
|
