Differences between revisions 10 and 43 (spanning 33 versions)
Revision 10 as of 2014-01-25 15:50:46
Size: 2758
Comment:
Revision 43 as of 2014-01-26 00:56:30
Size: 10450
Comment:
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
|| 118-119 || 15h30 || DIY-Tip || skydip_updown || 0 0, -1.4 || OFFSET -37 -30 /sys Nasmyth. '''error in scan 118: "-1 blocs manquants"'''. ''pipeline can't fit skydip down (scan 119)'' ||
|| 120 || 15h30 || DIY-Tip || skydip_up || 0 0, -1.4 || ||
|| || 15h45 || Uranus || cross || 0 0, -1.4 || ||
|| 118-119 || 15h30 || DIY-Tip || skydip_updown|| 0 0, -1.4 || OFFSET -37 -30 /sys Nasmyth. '''error in scan 118: "-1 blocs manquants"'''. ''pipeline can't fit skydip down (scan 119)'' ||
|| 120 || 15h45 || DIY-Tip || skydip_up || 0 0, -1.4 || find tau 0.44 @ 1mm ~ tau meter, 0.36 @ 2mm ||
|| 121 || 15h55 || Uranus || cross || 0 0, -1.4 || find pointing -55 -35 ! Normal: typo in Nasmyth offsets: -37 30 => OFFSET -37 -30 /sys Nasmyth||
|| 122 || 16h00 || Uranus || cross || 0 0, -1.4 || find pointing -2.3 -1.6 => OK now these values are in the expected range. ||
|| 123 || 16h06 || Uranus || pointliss || -2.3 -1.6, -1.4 || find pointing -5 -1.1 (accumulate stat for comparison between both method) ||
|| 124 || 16h10 || Uranus || focusp || -5 -1.1, -1.4 || find focus -1.42 @ 1mm, -0.97 @ 2mm. Very noisy; turbulent blue sky, wind.||
|| 125-129 || 16h16 || Uranus || focusliss || -5 -1.1, -1.4 || find focus -1.23 @ 1mm, -0.56 @ 2mm (accumulate stat for comparison between both method) ||
|| 130 || 16h25 || Uranus || cross || -5 -1.1, -1.2 || find pointing -4.6 2.1 ||
|| 131 || 16h30 || Uranus || pointliss || -5 -1.1, -1.2 || find pointing -5.5 3.2. ''Alain update RAW_X10 to test fix of file timing problem encountered yesterday.'' ||
|| 132 || 16h35 || Uranus || otfgeom || -5 3, -1.2 || ||
|| 133 || 16h35 || Uranus || otfgeom || -5 3, -1.2 || ''good file in X33, some "?" in the data control screen of X9 and X10 = some corruptions in the files; good file recovered from X33 at end of session, imbfits regenerated.'' ||
|| 134 || 16h50 || Uranus || cross || -5 3, -1.2 || find pointing -3.2 3.7 ||
|| 135 || 16h50 || Uranus || pointliss || -5 3, -1.2 || find pointing -2.2 4.1 ||
|| 136 || 17h10 || Uranus || focusp || -2.8 3.9, -1.2 || find focus -1.07 @ 1mm, -1.08 @ 2mm ||
|| 137-141 || 17h20 || Uranus || focusliss || -2.8 3.9, -1.2 || ''not usable. We have found the corruption problem: do not transfer files from X9 and X10 for local analysis during a scan'' ||
|| 142-146 || 17h30 || Uranus || focusliss || -2.8 3.9, -1.2 || find focus -0.3 @ 1mm, -0.4 @ 2mm => 1mm shift on M2 is prety big (Zemax shows huge effect on beam); is it due to sunset or wind ? ||
|| 147 || 17h44 || Uranus || pointliss || -2.8 3.9, -1.2 || find pointing -2.0 5.9. ''before scan set project 193-13 to check scan info goes in Israel's project in the TAPAS and Pool databases => NO''||
|| 148 || 17h45 || Uranus || pointliss || -2.8 3.9, -1.2 || find pointing -1.2 5.1. ''before scan set project t21 => back to our default ID. => in the databases: 147 is in t21, and 148 in 193-13 !!!''||
|| 149 || 17h50 || Uranus || focusp || -2.8 3.9, -0.7 || start with focus intermediate between 2 preceding focus scans, find focus -1.7 @ 1mm, -1.3 @ 2mm ||
|| 150-152 || 17h55 || Uranus || focusliss || -2.8 3.9, -0.7 || '''scan canceled: too much wind, observations stopped''' ||
|| 153-157 || 18h10 || Uranus || focusliss || -2.8 3.9, -0.7 || still windy, test if obs possible. find focus -1.06 @ 1mm, -0.79 @ 2mm. tracking errors important at Lissajous turns.||
|| 158 || 18h26 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s (default in cross script) '''no 2mm data: NIKEL 2 crashed''' ||
|| 159 || 18h26 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s '''no 2mm data: NIKEL 2 crashed''' ||
|| 160 || 18h35 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 0.9 6.0 ''Attention data on X9 corrupted, data on X10 OK, good file recovered at end of session, imbfits regenerated.''||
|| 161 || 18h35 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 1.4 5.0 ''data on X9 corrupted, data on X10 OK => NIKEL restarted from X10, params needed to be broadcast to X9. good file recovered at end of session, imbfits regenerated.''||
|| 162 || 18h35 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 0.6 5.4 ||
|| 163 || 18h40 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 1.4 5.4 ''scan not on X9 but on X10 => Alain fix on timing problem works, use X10 from now on; re-run nika_filing from X10 for imbfits''||
|| 164 || 18h50 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.1 3.4 (holes in data => flag out of res, big sky variation) ||
|| 165 || 18h55 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.0 3.2 (holes in data => flag out of res, big sky variation) ||
|| 166 || 18h55 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 240/16 = 15"/s find pointing 2.0 3.3 (big fluctuations in timelines. suggestion for offline processing: cut all to 120" around source and see how it improves) ||
|| 167 || 18h56 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.5 5.2 (check vertical blue bar in 4th subscan timeline from run_pointing.pro) ||
|| 168 || 19h00 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 480/16 = 30"/s find pointing 2.6 4.4 (fog is also there now...) : fit looks good ! ||
|| 169 || 19h00 || Uranus || cross || -2.8 3.9, -1 || test crosses speed in windy conditions. 480/16 = 30"/s find pointing '''canceled, too windy, observations stopped.''' ''Icy fog: need turn on antenna de-icer'' ||
|| || 21h00 || || || || ''wind not too bad on plot from IRAM weather page, but station anemometer screened to north wind; measure with the manual anemometer just outside the control room: 15-20 m/s regular with peaks at 25m/s => no obs possible''||
|| 170 || 23h16 || 3c84 || cross || 0 0, -2.4 || wind decreasing. test obs. '''canceled''' cross was still 480/16 = 30"/s, focus @ -2.4 ||
|| 171 || 23h16 || 3c84 || cross || 0 0, -1 || cross @ 120/12 = 10"/s (use that as default now) find pointing -44 -2 => forgot again Nasmyth offset ! ||
|| 172 || 23h16 || 3c84 || cross || 0 0, -1 || find pointing 1.8 -1.1 ||
|| 173 || 23h24 || 3c84 || focusp || 1.8 -1.1, -1 || find focus -1.3 @ 1mm -1.24 @ 2mm ||
|| 174-178 || 23h30 || 3c84 || focusliss || 1.8 -1.1, -1.3 || find focus -1.7 @ 1mm -1.3 @ 2mm ||
|| 179 || 23h35 || 3c84 || cross || 1.8 -1.1, -1.7 || find pointing 2.7 -0.7 ||
|| 180 || 23h40 || 3c84 || pointliss || 1.8 -1.1, -1.7 || find pointing 4 -1.0 ||
|| 181 || 23h45 || 3c84 || otfgeom || 3 -1, -1.7 || histogram FWHM vs Number of detectors peak is at ~12" @ 1mm, ~18.5" @ 2mm ||
|| 182 || 23h57 || 3c84 || otfgeom || 3 -1, -1.3 || histogram FWHM vs Number of detectors peak is at ~13" @ 1mm, ~18.2" @ 2mm => focusliss give better result, though FWHM still 30% bigger than theory... ||

NIKA, January 25th, 2014 / S6

Back to list of day to day logbook of observations

2014-01-25

  • TAPAS database, will be completed on Monday. Continue with manual log below.

Programm for today. View the poor weather conditions that prevented us to follow the program listed in the observation plan, we (SL) reorganise it. We will do continuum observations only (without the polariser).

  • Skydip.
  • Focus and Beam maps on Uranus. Centered on the refence detector: #494 of the 2mm array (#5 of the 1mm array is very close to it).
  • If the weather allows, resume pointing session.
  • If the weather allows, beam maps on Uranus: on focus 1st then investigation of 3D focus (=> 18 scans).

  • If weather not excellent but good enough for observations: quick test for the TAPAS data base, change project from t21 to 193-13 (Israel's project for the pool in Feb) do a Lissajou scan on any bright source nearby and check that the scan appears in the right table of the pool database. Then back to project t21.
  • If weather not excellent but good enough for observations: 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.
  • If weather not excellent but good enough for observations: check geom on CygA (and possibly M82 again).
  • If weather not excellent but good enough for observations: test various scan speed 10, 20, 30, 40, 50, 60 arcsec/s, first on bright quasar with geom (e.g. 3C454.3, 3C84, OJ287, 3C111), then on extended sources with large OTF zigzag (e.g. CygA, CasA, Crab, possibly M82 again).
  • If weather not excellent but good enough for observations: test various OTF Zig Zag orientations; in particular Ra Dec scan on NGC891.

Note: view the numerous polar obs done yesterday in rather good weather conditions, no polar observations foreseen today. Wait for Feedback from NIKA team in Grenoble for possible plan of additional polar obs tomorrow or day after tomorrow.

Remark for NIKA staff: Good data are on RAW_X9

OFFSET -37 -30 /sys Nasmyth => select detector 494 as reference

Scan

UT

Source

Command

Pointing X,Y, Focus

Comment

118-119

15h30

DIY-Tip

skydip_updown

0 0, -1.4

OFFSET -37 -30 /sys Nasmyth. error in scan 118: "-1 blocs manquants". pipeline can't fit skydip down (scan 119)

120

15h45

DIY-Tip

skydip_up

0 0, -1.4

find tau 0.44 @ 1mm ~ tau meter, 0.36 @ 2mm

121

15h55

Uranus

cross

0 0, -1.4

find pointing -55 -35 ! Normal: typo in Nasmyth offsets: -37 30 => OFFSET -37 -30 /sys Nasmyth

122

16h00

Uranus

cross

0 0, -1.4

find pointing -2.3 -1.6 => OK now these values are in the expected range.

123

16h06

Uranus

pointliss

-2.3 -1.6, -1.4

find pointing -5 -1.1 (accumulate stat for comparison between both method)

124

16h10

Uranus

focusp

-5 -1.1, -1.4

find focus -1.42 @ 1mm, -0.97 @ 2mm. Very noisy; turbulent blue sky, wind.

125-129

16h16

Uranus

focusliss

-5 -1.1, -1.4

find focus -1.23 @ 1mm, -0.56 @ 2mm (accumulate stat for comparison between both method)

130

16h25

Uranus

cross

-5 -1.1, -1.2

find pointing -4.6 2.1

131

16h30

Uranus

pointliss

-5 -1.1, -1.2

find pointing -5.5 3.2. Alain update RAW_X10 to test fix of file timing problem encountered yesterday.

132

16h35

Uranus

otfgeom

-5 3, -1.2

133

16h35

Uranus

otfgeom

-5 3, -1.2

good file in X33, some "?" in the data control screen of X9 and X10 = some corruptions in the files; good file recovered from X33 at end of session, imbfits regenerated.

134

16h50

Uranus

cross

-5 3, -1.2

find pointing -3.2 3.7

135

16h50

Uranus

pointliss

-5 3, -1.2

find pointing -2.2 4.1

136

17h10

Uranus

focusp

-2.8 3.9, -1.2

find focus -1.07 @ 1mm, -1.08 @ 2mm

137-141

17h20

Uranus

focusliss

-2.8 3.9, -1.2

not usable. We have found the corruption problem: do not transfer files from X9 and X10 for local analysis during a scan

142-146

17h30

Uranus

focusliss

-2.8 3.9, -1.2

find focus -0.3 @ 1mm, -0.4 @ 2mm => 1mm shift on M2 is prety big (Zemax shows huge effect on beam); is it due to sunset or wind ?

147

17h44

Uranus

pointliss

-2.8 3.9, -1.2

find pointing -2.0 5.9. before scan set project 193-13 to check scan info goes in Israel's project in the TAPAS and Pool databases => NO

148

17h45

Uranus

pointliss

-2.8 3.9, -1.2

find pointing -1.2 5.1. before scan set project t21 => back to our default ID. => in the databases: 147 is in t21, and 148 in 193-13 !!!

149

17h50

Uranus

focusp

-2.8 3.9, -0.7

start with focus intermediate between 2 preceding focus scans, find focus -1.7 @ 1mm, -1.3 @ 2mm

150-152

17h55

Uranus

focusliss

-2.8 3.9, -0.7

scan canceled: too much wind, observations stopped

153-157

18h10

Uranus

focusliss

-2.8 3.9, -0.7

still windy, test if obs possible. find focus -1.06 @ 1mm, -0.79 @ 2mm. tracking errors important at Lissajous turns.

158

18h26

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s (default in cross script) no 2mm data: NIKEL 2 crashed

159

18h26

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s no 2mm data: NIKEL 2 crashed

160

18h35

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 0.9 6.0 Attention data on X9 corrupted, data on X10 OK, good file recovered at end of session, imbfits regenerated.

161

18h35

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 1.4 5.0 data on X9 corrupted, data on X10 OK => NIKEL restarted from X10, params needed to be broadcast to X9. good file recovered at end of session, imbfits regenerated.

162

18h35

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 0.6 5.4

163

18h40

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 120/16 = 7.5"/s find pointing 1.4 5.4 scan not on X9 but on X10 => Alain fix on timing problem works, use X10 from now on; re-run nika_filing from X10 for imbfits

164

18h50

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.1 3.4 (holes in data => flag out of res, big sky variation)

165

18h55

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.0 3.2 (holes in data => flag out of res, big sky variation)

166

18h55

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 240/16 = 15"/s find pointing 2.0 3.3 (big fluctuations in timelines. suggestion for offline processing: cut all to 120" around source and see how it improves)

167

18h56

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 240/16 = 15"/s find pointing 1.5 5.2 (check vertical blue bar in 4th subscan timeline from run_pointing.pro)

168

19h00

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 480/16 = 30"/s find pointing 2.6 4.4 (fog is also there now...) : fit looks good !

169

19h00

Uranus

cross

-2.8 3.9, -1

test crosses speed in windy conditions. 480/16 = 30"/s find pointing canceled, too windy, observations stopped. Icy fog: need turn on antenna de-icer

21h00

wind not too bad on plot from IRAM weather page, but station anemometer screened to north wind; measure with the manual anemometer just outside the control room: 15-20 m/s regular with peaks at 25m/s => no obs possible

170

23h16

3c84

cross

0 0, -2.4

wind decreasing. test obs. canceled cross was still 480/16 = 30"/s, focus @ -2.4

171

23h16

3c84

cross

0 0, -1

cross @ 120/12 = 10"/s (use that as default now) find pointing -44 -2 => forgot again Nasmyth offset !

172

23h16

3c84

cross

0 0, -1

find pointing 1.8 -1.1

173

23h24

3c84

focusp

1.8 -1.1, -1

find focus -1.3 @ 1mm -1.24 @ 2mm

174-178

23h30

3c84

focusliss

1.8 -1.1, -1.3

find focus -1.7 @ 1mm -1.3 @ 2mm

179

23h35

3c84

cross

1.8 -1.1, -1.7

find pointing 2.7 -0.7

180

23h40

3c84

pointliss

1.8 -1.1, -1.7

find pointing 4 -1.0

181

23h45

3c84

otfgeom

3 -1, -1.7

histogram FWHM vs Number of detectors peak is at ~12" @ 1mm, ~18.5" @ 2mm

182

23h57

3c84

otfgeom

3 -1, -1.3

histogram FWHM vs Number of detectors peak is at ~13" @ 1mm, ~18.2" @ 2mm => focusliss give better result, though FWHM still 30% bigger than theory...

NK2014_Jan25 (last edited 2014-01-26 00:56:30 by NikaBolometer)