10005
Comment:
|
12800
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= Informations useful for the observations: List of astronomical Target, Pako scripts, Observing strategies = | = Informations useful for the observations: List of astronomical Target, Pako scripts, Real Time Analysis, Observing strategies = |
Line 8: | Line 8: |
Line 29: | Line 30: |
Here is IRAM report on [[attachment:lisenfeld-2000-secondary-calibs-for-mambo.pdf|Secondary Calibrators]] | |
Line 32: | Line 34: |
for photometric calibration checks (secondary calibrators) | for photometric calibration checks |
Line 50: | Line 52: |
Here is the catalog for Pako [[attachment:NIKA2012N5v1.0.sou.txt]] has to be RENAMED to NIKA.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) [[attachment:ListAstroTargetNika3/IRAM_pointing_sources_with_fluxes.xls]] |
Here is the catalog for Pako [[attachment:NIKA2012N5v1.1.sou.txt]] has to be RENAMED to NIKA.sou on the pako computer (Done 5/11/2012) Here is a list of IRAM pointing sources with fluxes at 3mm and 2mm (I miss fluxes at 1mm, SL) [[attachment:ListAstroTargetNika3/IRAM_pointing_sources_with_fluxes.xls|FluxForPointingSources]] |
Line 57: | Line 60: |
Here is a short manual on useful "Pako for Nika" commands [[attachment:Pako_helpv10.txt]] |
Short manual on useful "Pako for Nika" commands: [[attachment:Pako_helpv13.txt]] (updated with PaKo commands specific for NIKA 14/11/12, SL) NEW (12/11/12): Hans' memo about the Tones tuning scripts in Pako: [[attachment:ncs30mProjectsPlanningNIKA.pdf]] |
Line 62: | Line 66: |
[[attachment:nini.pako]] => run the initial series of commands that always have to be run at the beginning of an observing session, updated with choice of receiver and backend allowing to get fits files, updated with correct focus and correct nasmyth offset deduced from pointing model session from 17 to 18/10/2011 night. | NEW (17/11/12): [[attachment:Maximum_OTF_speed_vs_Elevation.txt]] => a table showing the maximum velocities possible for the scans for various elevations. NEW init file for pako: ini.pako automatically loaded with the pakoNIKA command; the old nini.pako is deprecated and will cause errors if loaded. |
Line 92: | Line 98: |
== Status of observations == [[attachment:nika_source_list.xls|spread sheet of sources with integrated time]] ---- == Observing procedures and strategies for performances verifications and debugging == === Observations procedure as discussed between FXD, RZ, NP & SL on 30/5/2012 === 1. Use the EMIR pointing model as the starting reference, setting Nasmyth offsets to 0. |
== Real Time Analysis == New (12/11/12): Xavier's and Robert's memo to start real time Mopsic analysis: [[attachment:HelpMopsicSecurForWiki.txt]] (there is also a README in the directory, where the pointings & foci should be processed) Userl Manual for the Real time analysis: [[RealTime_User_Manual |User Manual RTAnalysis]] ---- == Recommandations for the Pointing Sessions == - Available pointing sources are displayed on Xephem, together with Antenna position. Fluxes are also displayed and given as "_mK" appended to the source name. - check Pako pointing source catalog - 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 TOTO 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 ---- == Observing procedures, strategies for performance verification and debugging == v1 starting from discussions between FXD, RZ, NP & SL on 30/5/2012 v2 2/10/2012 elaborate on results from previous runs 1. Use the NIKA pointing model as the starting reference, setting Nasmyth offsets to 0. (NIKA pointing model is close to EMIR one) |
Line 104: | Line 139: |
3. Do a "NIKA type" OTF-POITING 4. Implement Nasmyth correction to point on the central pixel 5. Check with POINTING 6. Idem using the WOBBLER (expected setup: SWOBBLER -25 25 ttphase 0.52 ; assymetric wobble impossible, must be wide enough w.r.t. beam, as fast as possible without being harmonic of something) 7. 1st crude FOCUS with wobbler ("classical" procedure): 6 subscans, 2mm shifts 8. 1st crude Focus without Wobbler: new NIKA style: one line OTF scan way and back; 3 scans, set focus between scans 2 mm shifts 9. 1st crude FOCUS with wobbler, 1mm shifts 10. 1st crude OTF-FOCUS (without Wobbler), 1mm shifts 11. 1st OTF-GEOMETRY (scan width = baseline x 2 + FOV + max pointing error = 1x2 + 2.5 + 1 + 0.5 = 5') 12. 1st OTF pointing session (as many quasar as possible in the 6 h slot, probably ~15 ?) => define the NIKA pointing model (15 is not enough stat for a clear determination, but should be OK at 1st order) 13. better FOCUS with wobbler ("classical" procedure): 6 subscans, 2mm shifts 14. better Focus without Wobbler: new NIKA style: one line OTF scan way and back; 3 scans, set focus between scans 2 mm shifts 15. better FOCUS with wobbler, 1mm shifts 16. better OTF-FOCUS (without Wobbler), 1mm shifts 17. better OTF-GEOMETRY (scan width = baseline x 2 + FOV + max pointing error = 1x2 + 2.5 + 1 + 0.5 = 5') 18. OTF-GEOMETRY for different foci => focus characteristics for all pixels 19. OTF pointing session => define a better NIKA pointing model 20. test skydip going at high airmass values (at least 3) 21. observe typical calibrators 1-20 Jy (e.g. OJ) 22. observe known fainter sources (e.g. Tau sources) 23. redo this procedure the next day |
3. Implement Nasmyth correction to point on a chosen central pixel 4. Check with POINTING 5. 1st crude Focus: FOCUS sequence 6. 1st OTF-GEOMETRY (scan width = baseline x 2 + FOV + max pointing error = 1x2 + 2.5 + 1 + 0.5 = 5') 7. OTF-GEOMETRY for different foci => focus characteristics for all pixels 8. 1st OTF pointing session (as many quasars as possible in the 8 h slot, probably ~20 ?) => define the NIKA pointing model (20 is not enough stat for a clear determination, but should be OK at 1st order) 9. test skydip going at high airmass values (at least 3) 10. observe typical calibrators 1-20 Jy (e.g. OJ) 11. observe known fainter sources (e.g. Tau sources) 12. redo this procedure the next day |
Line 130: | Line 154: |
For skydips: do a frequency sweep at each airmass step => up to airmass = 3 or 4. This will give the position of the resonance frequency = total power. Each step has to be done manually; in the future implement Pako script and CAMADIA to to the frequency sweep automatically at each step. How to investigate the plateau, beam broadening etc. => gain of amplifiers and power on the tone are the hardware parameters that we will change => write the information in Wiki log pages (this is in the raw data anyway, but discuss with Alain to get all the info in the FITS). IMBFITS format: keep same structure as before run (e.g. with a fixed number of pixels close to the maximum available, not a varying number of pixels), except the implementation of Wobbler information (TTL = 0 - 40, with numbers in between = blancking) |
For skydips: for each subscan, a calibration is done in order to find the central frequency of each kid IMBFITS format: keep same structure as before run (e.g. with a fixed number of pixels close to the maximum available, not a varying number of pixels) |
Line 140: | Line 162: |
So far (01/06/2012) we identify 3 hardware parameters we could play on: |
Here we will use Uranus, which is fainter than Mars and should yield a representative plateau for fainter sources. We will try crosses with different setting |
Line 144: | Line 166: |
* Move the tones frequencies by a small amount to place them on a different location on the slope of the resonance => at least 3 scans * Repeat the procedure at least twice to check repeatability => '''14 scans minimum''' ==> This should allow us to determine whether the plateau is a pure electronic effect, and have ideas on what causes it. |
In any case, scatter off-resonance tones across the frequency range of both arrays. This should allow us to determine whether the plateau is a pure electronic effect, and have ideas on what causes it. === Sensitivity optimization === In order to measure the sensitivity, we should just make small OTF on Neptune (or a bright quasar or MWC349) for calibration then a the same on an empty field for noise measurement. Repeat this sequence with different settings. * Power on kids * Delta f (maybe?) * One day, stabilize at 200 mK to measure the sensitivity of the arrays (2mm array should be better). Need for a correct focal plane geometry == Science demonstration requirement == We want to show typical science demonstration data in five areas where we can compare our results with previous (Mambo, Laboca, JCMT, Bolocam) bolometer array results. We have about 16 hours for 7 days. Taking out 5 hours for calibration (calibration on planets and secondary calibrators, pointing, focus, skydip), we are left with 11x7=77 hours of science scans, which we spread this way, with the sources in order of priority: 1. Dense Galactic regions (15h) 2. Extended galaxies (12h) M82, M87, CygA, NGC1068, 3. Faint sources (14h) 4. Deep survey (16h) 5. Clusters of galaxies (20h) Here is a priority list of targets (see the complete list above). 1. Galactic regions, From brighter to fainter 1.1. Large map of OrionLBS23SM 1.2. Large map of DR21 1.3. Large map of Crab, CasA 1.4. Map of NGC2023 1.5. Map of the horsehead 2. Extended galaxies 2.1. M82 2.2. NGC1068 2.3. M87 2.4. CygA 2.5. NGC891 2.6. NGC3690 3. Faint point sources 3.1. Galactic faint sources 3.2. high redshift objects starting with 10 mJy sources at 1mm: Arp220, 4C05.19, APM08279+5255, HSO_ID017, HSO_ID081, HSO_ID011, HSO_ID130, F10214+4724, HLSW01, BR1202-0725, BRI1335-0417, SBS1408+567, H1413+517, MM18423, SMMJ2135 4. Deep survey: The idea is to cover a field with 1mJy rms sensitivity at 1mm and 0.5mJy at 2mm, this is about one hour per camera FOV (about one arcmin^2). Map should be 4x4 arcmin. Exact field to be decided. 5. Clusters of galaxies Priority is on detection 5.1. RXJ1347-1145 (6h) 5.2. A665 (7h) 5.3. MACS0717 or MS0451 (7h) [[attachment:Simu_SZ.pdf|Internal memo: Simulation of tSZ observation with NIKA]] [[attachment:Simu_NIKA.pdf|Internal memo: Simulation of NIKA]] In case of a strong and not-understood plateau, the mapping of high-contrast extended targets should be limited. The search for point-sources should be reinforced. ---- == Status of observations == [[attachment:nika_source_list.xls|spread sheet of sources with integrated time]] |
Informations useful for the observations: List of astronomical Target, Pako scripts, Real Time Analysis, Observing strategies
List of Astronomical Target for Nika End 2012 run5
FXD: First version for planets (14/06/2012)
v2 (2/10/2012) prepare Thursday teleconf
1. Planets Mars, Uranus, Neptune for photometric calibration (primary calibrators)
Name |
Right Ascension |
Declination |
Size (arcsecond diameter) |
Flux @ 1.25 mm |
Flux @ 2.05 mm |
MARS |
18:19:04.1164 |
-24:29:49.029 |
4.41*4.38 |
132.072 Jy |
45.448 Jy |
URANUS |
00:18:45.6410 |
01:14:00.476 |
3.59*3.49 |
51.637 Jy |
17.897 Jy |
NEPTUNE |
22:10:45.6241 |
-11:54:23.087 |
2.23*2.18 |
18.926 Jy |
6.566 Jy |
Here are the ephemeris for the planets
2. Usual bright quasars
- for image quality and linearity checks
3. Strong Galactic sources
- for secondary calibration and science
Strong galactic sources Here is IRAM report on Secondary Calibrators
4. Weak Galactic sources
- for photometric calibration checks
5. External extended galaxies
- for Science demonstration (mapping)
6. High redshift sources
- for Science demonstration (sensitivity)
7. Deep survey and SZ sources
- for Science demonstration (sensitivity)
Deep survey and cluster of galaxies
Here is the full detailed formatted list Full list with fluxes
Here is the catalog for Pako NIKA2012N5v1.1.sou.txt has to be RENAMED to NIKA.sou on the pako computer (Done 5/11/2012)
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" commands: Pako_helpv13.txt (updated with PaKo commands specific for NIKA 14/11/12, SL)
NEW (12/11/12): Hans' memo about the Tones tuning scripts in Pako: ncs30mProjectsPlanningNIKA.pdf
Here is a collection of Pako scripts to gain time and have a reference on the observations we will do (to use them rename the files without the .txt, 2nd version updated with slower mapping speed to minimize tracking errors, 3rd version include pako line continuation sign (-)):
NEW (17/11/12): Maximum_OTF_speed_vs_Elevation.txt => a table showing the maximum velocities possible for the scans for various elevations.
NEW init file for pako: ini.pako automatically loaded with the pakoNIKA command; the old nini.pako is deprecated and will cause errors if loaded.
ListAstroTargetNika3/OTF_pointing.pako => OTFMAP 100"x84" in 22 subscan x 10 s = 4+1 ~= 5 min (10"/s) with 2.6 samples (subscan step) per convolved 1mm HPBW (for pointing & focus). 10s = minimum subscan time possible (Pako doesn't authorizes less), hence the choice of subscan length. Scan height changed from 60" to 92" to have more margins for the useful pixels.
ListAstroTargetNika3/OTF_geometry.pako => OTFMAP 300"x220" in 56 subscan x 20 s = 19+3 ~= 22 min (15"/s) with 2.6 samples (subscan step) per convolved 1mm HPBW (for the array geometry = pixels map in sky)
ListAstroTargetNika3/OTF_ps.pako => OTFMAP 140"x90" in 19 subscan x 14 s = 4+1 ~= 5 min (10"/s) with 2 sample (subscan step) per convolved 1mm HPBW (for point source observations)
ListAstroTargetNika3/OTF_2x2.pako => OTFMAP 120"x120" in 25 subscan x 12 s = 5+1 ~= 6 min (10"/s) with 2 samples (subscan step) per convolved 1mm HPBW (for extended source < 2')
ListAstroTargetNika3/OTF_5x5.pako => OTFMAP 300"x300" in 51 subscan x 20 s = 17+3 ~= 20 min (15"/s) with 1.7 samples (subscan step) per convolved 1mm HPBW (for extended source < 5')
ListAstroTargetNika3/OTF_10x10.pako => OTFMAP 600"x600" in 41 subscan x 30 s = 20+4 ~= 24 min (20"/s) with 0.7 samples (subscan step) per convolved 1mm HPBW (for very extended source < 10')
ListAstroTargetNika3/OTF_faint_source.pako => OTFMAP 120"x80" in 21 subscan x 12 s = 4.2+0.8 ~= 5 min (10"/s) with 2.6 samples (subscan step) per convolved 1mm HPBW (for faint sources)
ListAstroTargetNika3/OTF_deep_field.pako => OTFMAP 360"x360" in 61 subscan x 20 s = 20+4 ~= 24 min (18"/s) with 1.7 samples (subscan step) per convolved 1mm HPBW (for faint sources)
ListAstroTargetNika3/OTF_sz.pako => OTFMAP 360"x240" in 41 subscan x 20 s = 14+3 ~= 17 min (18"/s) with 1.7 samples (subscan step) per convolved 1mm HPBW (for faint sources)
ListAstroTargetNika3/OTF_moon.pako => OTFMAP 2000x 2000 in 34 subscan x 40 s = 23+3 ~= 26 min with 0.17 samples (subscan step = 60) per convolved 1mm HPBW (to look at the moon in bad weather)
Here's an excel sheet which helps to find the best focus thanks to a 2nd order polynomial line trend fitting on beam width and amplitude (note that amplitude is much more robust):
Best focus with basic 2nd order polynomial
Real Time Analysis
New (12/11/12): Xavier's and Robert's memo to start real time Mopsic analysis: HelpMopsicSecurForWiki.txt (there is also a README in the directory, where the pointings & foci should be processed)
Userl Manual for the Real time analysis: User Manual RTAnalysis
Recommandations for the Pointing Sessions
- Available pointing sources are displayed on Xephem, together with Antenna position. Fluxes are also displayed and given as "_mK" appended to the source name.
- check Pako pointing source catalog
- 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 TOTO 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
Observing procedures, strategies for performance verification and debugging
v1 starting from discussions between FXD, RZ, NP & SL on 30/5/2012 v2 2/10/2012 elaborate on results from previous runs
- Use the NIKA pointing model as the starting reference, setting Nasmyth offsets to 0. (NIKA pointing model is close to EMIR one)
- Do a "classical" POINTING (cross)
- Implement Nasmyth correction to point on a chosen central pixel
- Check with POINTING
- 1st crude Focus: FOCUS sequence
- 1st OTF-GEOMETRY (scan width = baseline x 2 + FOV + max pointing error = 1x2 + 2.5 + 1 + 0.5 = 5')
OTF-GEOMETRY for different foci => focus characteristics for all pixels
1st OTF pointing session (as many quasars as possible in the 8 h slot, probably ~20 ?) => define the NIKA pointing model (20 is not enough stat for a clear determination, but should be OK at 1st order)
- test skydip going at high airmass values (at least 3)
- observe typical calibrators 1-20 Jy (e.g. OJ)
- observe known fainter sources (e.g. Tau sources)
- redo this procedure the next day
Note: good focus depend on geometry which depend on focus ==> iterative process.
How to find the elevation axis with the observation ? This is degenerate with the pointing model => Iterative approach => accumulate statistics. Due to the degeneracy one as to make a choice on the strategy for the definition of the center of rotation of the array (rotation with elevation of the sky image). After discussions the next days: at the start of the run we will choose the best of the 4 pixels at the center of the array and define it as the center for the pointing model.
For skydips: for each subscan, a calibration is done in order to find the central frequency of each kid
IMBFITS format: keep same structure as before run (e.g. with a fixed number of pixels close to the maximum available, not a varying number of pixels)
Strategy to investigate the Plateau
Since we see the plateau on 31/05/2012 pointing scans with crosses patterns, we will use these fast scans to investigate the plateau, the width should be larger than the plateau itself, that is to say bigger than the array with margins ==> 3 arcmin widths.
Here we will use Uranus, which is fainter than Mars and should yield a representative plateau for fainter sources. We will try crosses with different setting
Limit the total power in the acquisition line: play with 2 different values of the DAC => at least 2 scans
Limit the number of tones generated (e.g. probe all pixels, or only one which means generating only one tone, or only one part of the array) => at least 2 scans
In any case, scatter off-resonance tones across the frequency range of both arrays.
This should allow us to determine whether the plateau is a pure electronic effect, and have ideas on what causes it.
Sensitivity optimization
In order to measure the sensitivity, we should just make small OTF on Neptune (or a bright quasar or MWC349) for calibration then a the same on an empty field for noise measurement. Repeat this sequence with different settings.
- Power on kids
- Delta f (maybe?)
- One day, stabilize at 200 mK to measure the sensitivity of the arrays (2mm array should be better).
Need for a correct focal plane geometry
Science demonstration requirement
We want to show typical science demonstration data in five areas where we can compare our results with previous (Mambo, Laboca, JCMT, Bolocam) bolometer array results. We have about 16 hours for 7 days. Taking out 5 hours for calibration (calibration on planets and secondary calibrators, pointing, focus, skydip), we are left with 11x7=77 hours of science scans, which we spread this way, with the sources in order of priority:
- Dense Galactic regions (15h)
- Extended galaxies (12h) M82, M87, CygA, NGC1068,
- Faint sources (14h)
- Deep survey (16h)
- Clusters of galaxies (20h)
Here is a priority list of targets (see the complete list above).
- Galactic regions, From brighter to fainter
- 1.1. Large map of OrionLBS23SM 1.2. Large map of DR21 1.3. Large map of Crab, CasA 1.4. Map of NGC2023 1.5. Map of the horsehead
- Extended galaxies
- 2.1. M82 2.2. NGC1068 2.3. M87 2.4. CygA 2.5. NGC891 2.6. NGC3690
- Faint point sources
- 3.1. Galactic faint sources 3.2. high redshift objects starting with 10 mJy sources at 1mm:
- Arp220, 4C05.19, APM08279+5255, HSO_ID017, HSO_ID081, HSO_ID011, HSO_ID130, F10214+4724, HLSW01, BR1202-0725, BRI1335-0417, SBS1408+567, H1413+517, MM18423, SMMJ2135
- 3.1. Galactic faint sources 3.2. high redshift objects starting with 10 mJy sources at 1mm:
- Deep survey: The idea is to cover a field with 1mJy rms sensitivity at 1mm and 0.5mJy at 2mm, this is about one hour per camera FOV (about one arcmin^2). Map should be 4x4 arcmin. Exact field to be decided.
- Clusters of galaxies
Priority is on detection
- 5.1. RXJ1347-1145 (6h) 5.2. A665 (7h) 5.3. MACS0717 or MS0451 (7h)
In case of a strong and not-understood plateau, the mapping of high-contrast extended targets should be limited. The search for point-sources should be reinforced.