Differences between revisions 61 and 62
⇤ ← Revision 61 as of 2014-02-17 05:31:19 →
Size: 7857
Editor: NikaBolometer
Comment:
← Revision 62 as of 2014-02-17 05:52:36 → ⇥
Size: 8156
Editor: NikaBolometer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * Update the pointing model, ie put in the right p11cor, p12cor values as well as the elevation offset p7cor  * Update the pointing model, ie put in the right p11cor, p12cor values as well as the elevation offset p?cor
Line 37: Line 37:
Calibration periods will be interspersed at regular intervals.
Line 38: Line 39:
Guidelines for calibration scans:
 * (Observer responsibility) Pointing every 1h or less. Focus every 2/4 hours, more often at sunrise and sunset.
 * (NIKA team responsibility t21) otf_geom every 6 hours. Skydips every 12 hours.

NIKA run #8 February 2014

Back to the NIKA run 8

Goals of the run

Scientific run including Guaranteed time proposals and open time proposals in the same NIKA pool

NIKA people on call (Telephone number)

Telephones

Preparation of the run

Observing slots: Real schedule

Real schedule 1st week New v2 Real schedule 2nd week

Program

The calibration time, 5/2 hours per day from Sat 15 to Monday 17, will be used to test the standard calibration sequences.

  • The run7 parameters were Nasmyth (-37,-30) set Pointing (-16,-2) and p11cor, p12cor=0,0 (NasInPointingModel) with Detector 494 being the reference

  • Tune kids on a quasar (Track). Cross on 6 quasars with Nas=0,0: find pointing corr. (Method suggested by Juan and Carsten 16/2/2014)
  • Update the pointing model, ie put in the right p11cor, p12cor values as well as the elevation offset p?cor
  • KID optimisation
  • Pointliss. Focus and Focusliss
  • otf_geometry
  • Liss 5min weak source
  • otf_geom again
  • Liss 5min weak source
  • skydip
  • Check all procedures ( bright and faint sources)
  • Observe at least one of the brightest asteroids. Check that orbital elements are ok and that fluxes are ok.

The scientific time will be managed in a common NIKA pool. Official 1st NIKA IRAM observing pool here. Calibration periods will be interspersed at regular intervals.

Guidelines for calibration scans:

  • (Observer responsibility) Pointing every 1h or less. Focus every 2/4 hours, more often at sunrise and sunset.
  • (NIKA team responsibility t21) otf_geom every 6 hours. Skydips every 12 hours.

Travel plans

February presence at Pico (Dash (-) is for travel on 1stDay-1, FinalDay+1, X is night at Pico, D is for day only presence not night) and Grenoble This table is the NIKA team input table. Here is the official room occupancy plan for external pool and IRAM observers (maintained by Israel Hermelo).

Name @PICO

Thu 13

Fri 14

Sat 15

Sun 16

Mon 17

Tue 18

Wed 19

Thu 20

Fri 21

Sat 22

Sun 23

Mon 24

Tue 25

Wed 26

Thu 27

Fri 28

Nicolas P.

-

X

X

X

X

D

-

Martino C.

-

X

X

X

X

X

X

X

D

Alexandre

-

X

X

X

X

X

X

X

X

-

Alessandro

-

X

X

X

X

X

X

X

D

-

Barbara

-

X

X

X

X

D

-

Laurence

-

X

X

X

X

D

Juan

-

X

X

X

X

D

Remi

-

X

X

X

X

X

X

X

D

Xavier

-

X

X

X

X

X

X

D

-

Nello

-

X

X

X

X

X

X

X

X

D

Frederic

-

X

X

X

X

D

Number of people

0

2

2

2

4

5

6

6

5

5

4

6

6

5

5

5

room requirement

0

1

1

1

3

3

3

3

3

3

2

3

3

3

3

3

Name @Grenoble

13

14

Sat 15

Sun 16

17

18

19

20

21

Sat 22

Sun 23

24

25

26

27

Fri 28

Nicolas P.

x

X

X

X

X

X

X

Martino C.

X

X

-

Andrea

X

X

X

X

X

X

Alain

X

X

X

X

X

X

X

?

Alessandro

X

X

X

X

X

X

Barbara

-

X

X

X

X

X

X

Juan

X

X

X

X

X

X

X

X

X

Remi

X

X

X

X

X

Xavier

X

X

X

X

X

X

X

Frederic

X

X

X

X

X

* Min room requirement gives the minimal number of room required at the telescope, implying several persons can share room in case the occupancy at the telescope is such that single rooms can't be provided to all (according to Dec 5 2013's status of the telescope room schedule everybody can have a single room).

February presence at Grenoble, for offline data analysis and Real Time Support

GoalsPrepStaffN8 (last edited 2014-02-18 09:01:07 by CarstenKramer)