Differences between revisions 29 and 30
Revision 29 as of 2014-01-17 08:52:28
Size: 11781
Comment:
Revision 30 as of 2014-01-17 08:58:10
Size: 11782
Comment:
Deletions are marked like this. Additions are marked like this.
Line 105: Line 105:
 * First light, track Uranus, check acquisition data, tunning algorithm etc.  * First light, track Uranus, check acquisition data, tuning algorithm etc.
Line 123: Line 123:
'' Do we need to transfer the Nasmyth offset into the pointing model (e.i. cut and paste the Namyth offset that were chosen in !PaKo into some of the P parameters, so that afterward in !PaKo we type Nasmyth offset = 0 0 to choose the reference detector we took for the pointing session) ? Practical question concerning observations at the telescope, not data processing => see with AS and JP. '' '' Do we need to transfer the Nasmyth offset into the pointing model (e.i. cut and paste the Nasmyth offset that were chosen in !PaKo into some of the P parameters, so that afterward in !PaKo we type Nasmyth offset = 0 0 to choose the reference detector we took for the pointing session) ? Practical question concerning observations at the telescope, not data processing => see with AS and JP. ''
Line 125: Line 125:
 * Skydips. Needed only to calibrate the total power coefficients (once fitted we will be able to calculate the total power in the line of sight at anytime). One skydip (= 2 scans, 1 down 1 up) at the end of this session. Following days: ONE SKYDIP PER DAY for reproducibility, and one each time the power on the KIDs is changed.  * Skydips. Needed only to calibrate the total power coefficients (once fitted we will be able to calculate the total power in the line of sight at any time). One skydip (= 2 scans, 1 down 1 up) at the end of this session. Following days: ONE SKYDIP PER DAY for reproducibility, and one each time the power on the KIDs is changed.

Useful information for observations: List of astronomical Target, Pako scripts, Real Time Analysis, Observing strategies

List of Astronomical Target for Nika January 2014 run7

FXD: First version (8 Jan 2014)

Back to the NIKA run7 page

The nominal NIKA frequencies for this run are 260 and 150 GHz (ie 1.15 and 2.00 mm).

References and results are written in this private page

1. Planets and Asteroids

Mars, Uranus, Neptune for photometric calibration (primary calibrators) and focal plane geometry.

(Venus, Jupiter, Saturn) too hot too big

Name

Right Ascension

Declination

Diam (arcsec)

Flux @ 1.15 mm Jy

Flux @ 2.00 mm

TB K

MARS

13:17:21.2240

-05:33:50.343

8.09x8.05

478.4

161.4

198.06

URANUS

00:34:32.7042

02:59:35.055

3.44x3.33

42.06

15.98

assumes 102@260, 113@150

NEPTUNE

22:23:58.5378

-10:43:13.926

2.18x2.12

21.03

7.15

125@100GHz only

1 CERES

14:

0:

0.5

1.2

0.4

2 PALLAS

?

<1

0.5

0.15

4 VESTA

13:30

-1:

0.4

0.5

0.16

21 LUTETIA

12:35

0:

0.1

1.2

0.4

Here are the ephemeris for all planets The near and far sidelobes could be measured with Jupiter and Saturn.

2. Usual bright quasars, secondary calibrators and strong galactic sources (end of the list is dedicated to polarisation)

  • for image quality, linearity checks, and pointing sessions

Bright source selection

Here is IRAM report on Secondary Calibrators

3. Weak Galactic sources

  • for photometric calibration checks

Weak galactic sources

4. External extended galaxies

  • for Science demonstration (mapping)

Nearby galaxies

5. High redshift sources

  • for Science demonstration (sensitivity)

Distant galaxies

Here is the full detailed formatted list Full list v1 with fluxes.

Here is the catalog for Pako has to be RENAMED to NIKA2014R7.sou on the pako computer.

Here is a list of IRAM pointing sources with fluxes at 3mm and 2mm (I miss fluxes at 1mm, SL) FluxForPointingSources


Interface with the telescope: Pako

Short manual on useful "Pako for Nika" see on Granada computers 2013_docs_for_observations/Pako_helpv16.txt

- Pako scripts are in the Pako subdirectory

- Before starting the pointing session, we may be requested to move the azimuth by 60deg to reset the inclinometer of the az axis.

- Always stay at more that 1 deg from the Sun. There are internal safeties that prevent the antenna to point to the Sun, but we may not get error messages.

- try to get sources uniformly distributed on the sky, hence give priority to high elevation sources that are usually harder to reach.

- Do one focus at the beginning. No need to do more focus than one every 2-3hours.

The antenna can point between 60 and 460 degrees in azimuth, between 20 and 80 degrees in elevation.

- If a source is available both at low and high azimuth, use command SET TOPO LOW (or SET TOPO HIGH) to stay on the source without moving.

- The minimum number of sources to observe for the pointing model is 15. 30 is good enough.

- the pointing sources should be observed on 'short' period, e.g. 3-4 hours to avoid daily pointing variations

Commissioning requirements and observations plan

Abstract

We can consider using 40 hours to test, calibrate and commission the instrument. Procedures will be tested several times, which include Pointing (Cross), Focus, OTF_Geometry, Skydip, Lissajous, OTF_Map. Tests include tuning, auto-tuning, robustness of data acquisition. Photometric calibration includes planets and secondary calibrators. Skydip and Lissajous sequences need to be better tested than before. Other sequences should be straightforward. The plateau systematics will be investigated via the OTG_geometry sequences. Near sidelobes can be measured by doing 5x5 map of of Jupiter or Saturn and use Pf variable.

Detailed version (Based on Run 6 program, updated on 16/01/2014, SL FXD RZ)

Before Tuesday 21 - First light, system check, choose reference detector

  • Alignment with laser. Then align radio axis by minimizing the background (manual adjustment of M5 with micrometric screws).
  • Run pakoNIKA (paKo Revision v 1.1.14.1 2013-06-01) => the antenna mount drive slowRate will be set to 8 Hz for all observations (if needed to go back to 1Hz as previous runs: let the operator reboot vac1, then use pakoNIKA2012).

  • First light, track Uranus, check acquisition data, tuning algorithm etc.
  • Start with Run 6 pointing model. First of all do a CROSS SCAN to see which is the reference detector (at the center of the cross), and to check synchronization (e.g. zig-zag between subscans). Then do a FOCUS, then check with a CROSS, then the first OTF_geometry on Uranus. Among few detectors at the center of the arrays choose one at 2 mm that is sensitive, stable and with also a stable and sensitive 1mm detector pointing at less than few arc-seconds from it (due to the atmosphere the 2mm band gives always better images, so it is better for pointing and focus); to set the reference detector use OFFSET a b /SYSTEM Nasmyth, and check with a cross. Once this is done do not change this reference anymore, except if some stability problem or else appears. On following scans, when it is needed to adjust the pointing use only SET POINTING (not SET OFFSET, which purpose is mainly to point off-source or to change the reference detector).

Tuesday 21 - OTF_Geometry & Pointing model session:

  • Cross + pointing Lissajous (do that systematically through this characterization run).
  • Focus + Focus_Liss (idem). Set focus, then redo cross for check. As set on the previous day, the reference detector is at 2mm, but check also the 1mm detector nearby; if the best focus is not at the same position for both band, take the best compromise (e.g. same ΔPeak/Peakmax for both bands).

  • Several OTF_geometry for reproducibility and statistics. These beam maps will be the main tool to characterize the instrument (field of view geometry, flat fields, stability, plateau, etc.). Check the 2mm reference detector chosen the previous day can be kept, otherwise make sure the information about change of ref detector is transmitted to all person analyzing the data. Subscans steps for OTF_geometry must be ≤ 5" otherwise there would not be enough oversampling at 1mm. Attention! The size of a scan must be the requested map size + the scan velocity x 2 seconds !

  • Pointing session. Observe 20 to 30 sources distributed in Az and El. Of course keep constant Nasmyth offsets during the whole session (it can still be changed latter during observations if one needs to change the reference detector), but always apply the pointing corrections when they are > 5" (otherwise we lose accuracy on the real position of the source and thus degrade the quality of the pointing model fit). For this commissioning run only do the pointing session with cross scans and Lissajous (time loss is expected to be almost negligible since the Lissajous will be running while analyzing the cross). After applying a pointing correction do another cross (not only to check the pointing is back on the source, but also to accumulate data for fitting the pointing model).

Fill the following table (Pointing X and Pointing Y are the the values entered in set pointing):

Scan

Object

Az

El

Pointing X

Pointing Y

Do we need to transfer the Nasmyth offset into the pointing model (e.i. cut and paste the Nasmyth offset that were chosen in PaKo into some of the P parameters, so that afterward in PaKo we type Nasmyth offset = 0 0 to choose the reference detector we took for the pointing session) ? Practical question concerning observations at the telescope, not data processing => see with AS and JP.

  • Skydips. Needed only to calibrate the total power coefficients (once fitted we will be able to calculate the total power in the line of sight at any time). One skydip (= 2 scans, 1 down 1 up) at the end of this session. Following days: ONE SKYDIP PER DAY for reproducibility, and one each time the power on the KIDs is changed.

Wednesday 22 - Polar setup:

  • OTF_geometry on Uranus during the whole session (with pointing and focus regularly).
  • Skydip (measure extended instrumental polar).

Thursday 23 - Geom and Focus:

  • Standard starting calibration sequence on Uranus: Cross, Pointing_Liss, Focus, Focus_Liss, Cross, OTF_geometry. TO DO EVERY DAY.
  • Focus Geometry: do OTF_geometry with 3 different set focus values (find best focus for other pixels than only the reference): 1st on axis (Z) AND THEN lateral focus (X then Y) + repeat at least once ==> At least 3x3x2 = 18 scans. Attention! There is a lateral focus command in PaKo, but apparently it doesn't stop the position of the secondary (M2) at various X and Y position but moves it continuously on a given range, like a cross scan. To be checked with JP and AS, though OTF_geometry at various values of X and Y focus is something different that a "cross lateral focus".

  • Accumulate beam maps: several OTF_geometry on the optimal "3D_focus" (==> statistics on pixels stability, FOV geometry, flat field, plateau, etc...).

  • Photometric calibration on primary and secondary calibrators with Lissajous scans and small OTF maps (Az El and/or few RA DEC for testing). Some secondary to observe: W3OH, K3-50A, MWC349, CRL2688, NGC7027, CepA, NGC7538. Bright quasar: 3C454.3, 3C84, OJ287, 3C111. Check geom: CygA, M82.
  • Few weak sources if the time (and weather) allows (Lissajous): check sensitivity.

Friday 24 - Polar characterization:

  • Planet and Quasar: (small) OTF and Lissajous.
  • Possibly extended sources: CasA, Crab.

Saturday 25 - Validate integration time:

  • Integrate on sources of medium to weak fluxes: WR147, IRC10420, some of the TAU sources (tbc), 4C05.19, APM08279, MM18423, PSS2322, SXDF, F10214. Lissajous.
  • Extended sources (OTF zigzag): CasA, Crab. Test various scan speed 10, 20, 30, 40, 50, 60 arcsec/s.
  • Test RA DEC OTF scans: NGC891.

Sunday 26 - Polar extended:

  • Extended sources from strong to weak: Crab, CasA, (Orion) KL, NGC7023NW (~1h per source).

Monday 27 - Backup:

  • If one of the above has suffered then redo it, otherwise try deep field (SXDF).

Science case demonstration

None this time since it is a commissioning run only.

Status of observations

Current status of observationsRun7

ListOfAstroTarget2014N7 (last edited 2014-01-22 19:24:33 by NikaBolometer)