|
Size: 4471
Comment:
|
Size: 3587
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| == 1st NIKA pool (8th run) == | == Important == |
| Line 5: | Line 5: |
| * The data reduction software should correct for tracking deviations. This is particularly important for 1mm observations under high wind, doing Lissajous scans. (added by IH on 20 Feb 2014) * Focus: (added by CK on 20 Feb 2014) * focus /dir x ! update pako manual for lateral focus scans * set focus /dir x ! allow easy way to correct for lateral focus offsets * '''When observing Lissajous maps at different focus positions to deduce the focus offsets, it'll be nice to do these maps as subscans and not as scans. This would make automatic data reduction easier. Please also declare this kind of observations as something different from 'lissajou' so we can identify these scans conviniently and not confuse them with regular lissajou maps.''' * Software: Ask the computer group to install some fits viewer (ds9 is the best option) on the observing computers (added by IH on 26 Feb 2014). (fv works fine also) * Remove this warning: '''W-LISSAJOUS, WARNING--CONDITION: Elevation must be less than 83.28 [deg]'''. It is annoying and confusing for the observers (added by IH on 01 Mar 2014). * --(In the automatic logsheets (TAPAS & Pool Data Base)make appear the scan number (SL 6 Mar 2014).)-- ''Already the case, checked 20 Mar 2014.'' * Modify telescope information stream (!PaKo & or ELVIN) and/or Camadia on NIKA side so that: * all the different types of Lissajous (focus, pointing, map) are identifiable with a specific name in the scan info data stream & in the automatic logsheets (currently they are all called Lissajous) (SL 20 Mar 2014) * when a focus scan is run the starting focus position is broadcast and usable by the NIKA IDL RTA software (quicklook) (SL 20 Mar 2014) * when a focus scan is run use by default (e.i. if the information is not specified in !PaKo) the current focus as the starting point (SL 20 Mar 2014) * when a skydip is run use use by default (e.i. if the information is not specified in !PaKo) the current azimuth+2' as the starting point (SL 20 Mar 2014) * Some items from the wish lists of [[WishNika6 |run 6]] an [[WishNika7 |run 7]] are still valid ! (SL 20 Mar 2014) |
=== IRAM-side === |
| Line 20: | Line 7: |
| 1. Focus: When observing Lissajous maps at different focus positions to deduce the focus offsets, it'll be nice to do these maps as subscans and not as scans. This would make automatic data reduction easier. 1. Modify telescope information stream (!PaKo & or ELVIN) and/or Camadia on NIKA side so that: 1. all the different types of Lissajous (focus, pointing, map) are identifiable with a specific name in the scan info data stream & in the automatic logsheets (currently they are all called Lissajous) (SL 20 Mar 2014) 1. when a focus scan is run the starting focus position is broadcast and usable by the NIKA IDL RTA software (quicklook) (SL 20 Mar 2014) 1. when a focus scan is run use by default (e.i. if the information is not specified in !PaKo) the current focus as the starting point (SL 20 Mar 2014); this has do be done for the future Focus-Lissajous scan which will include several subscans (item 1. above), but if this future scan is not ready for the next run, include this default focus in the current Lissajous focus scripts; for the moment there's a prompt in the the script asking for the current focus in order to calculate the values of focus positions that will be applied to the multiple Lissajous scans run in the script, the request is that the script calculates the several values of focus to be tested by itself without prompt; see the current script to understand better this request) 1. when a skydip is run use use by default (e.i. if the information is not specified in !PaKo) the current azimuth as the starting point (SL 20 Mar 2014); the current method to do skydips with NIKA is to use a script including the DYI-Tip source which coordinates has to be edited each time, the request is that the azimuth coordinate is by default the current coordinate of the telescope, not an azimuth prompted or edited manually in the script (remark: due to the fact that we use 2 subscans at several airmas values the standar TIP command of !PaKo can't be used with NIKA) |
|
| Line 21: | Line 16: |
| == 7th run == | 1. Use the run 7 data to determine the Nasmyth offsets of each pixels, then implement a look up table in NCS, with a selection tool, so that rather entering Nasmyth offset in !PaKo one can change the reference detector by selecting the number of the detector to use (e.g. enter in !PaKo: ref det 494). This possibility existed with MAMBO. |
| Line 23: | Line 18: |
| 1. Tuning in first subscan with an option in all pako commands: /tune /tsubtune 15 to be able to tune for a dedicated first subscan of 15 seconds 1. possibility to make subscans shorter than 10 seconds 1. automatic trigger of data reduction when a scan is finished |
|
| Line 24: | Line 23: |
| === Material to leave in the NIKA space at Pico Veleta (in the spiral room) === | 1. Telescope warning is missing when a scan is stuck |
| Line 26: | Line 25: |
| * Portable VNA-Spectrum Analyser (including transformer) -- OK * N.2 spare 2m fexible Minicircuits cables -- OK * N.4 semirigid cables used in run6 -- OK |
1. Access to NIKA observations in TAPAS mySQL data base + dedicated search interface (21-Mar-2014) |
| Line 33: | Line 27: |
| * Drawers containing a few tools, Norcan stuff, vacuum parts, '''arrays spares''', small RF spares (SMA, attenuators, mixers, filters etc.) -- OK | === Neel-side === |
| Line 35: | Line 29: |
| * Power supply and cables for ampli2 (already mounted in cryostat) - Yebes YL011 -- OK | 1. The data reduction software should correct for tracking deviations. This is particularly important for 1mm observations under high wind, doing Lissajous scans. See SL summary of [[CoordinatesParamNCS|coordinate parameters from antMD (-> Elvin) and IMBFITS]]. |
| Line 37: | Line 31: |
| * Polarization stuff: modulator motor/mechanics, HWP, polarizer -- OK | 1. auto-recovering of resonances |
| Line 39: | Line 33: |
| * Polystyrene container with ECOSORB for tones calibration off-Sky -- OK | == Nice-to-have == |
| Line 41: | Line 35: |
| * Spare "automate" for NIKA cryostat pumping stage -- Martino's coming with it GOING BACK TO GRENOBLE * list to be completed * Things would be nice to have: ....... humidifiers to sleep better, NIKA resident Moonboots to walk and breath, helmet, logos to identify NIKA space ... === Upgrade for observers === * Use the run 7 data to determine the Nasmyth offsets of each pixels, then implement a look up table in NCS, with a selection tool, so that rather entering Nasmyth offset in !PaKo one can change the reference detector by selecting the number of the detector to use (e.g. enter in !PaKo: ref det 494). This possibility existed with MAMBO. == 6th run == Here are things that could improve the smoothness of next Nika runs * Use real coordinates instead of commanded coordinates: see SL summary of [[CoordinatesParamNCS|coordinate parameters from antMD (-> Elvin) and IMBFITS]]. * Tuning in first subscan with an option in all pako commands: /tune /tsubtune 15 to be able to tune for a dedicated first subscan of 15 seconds * Focus with 5 lissajous subscans * TAPAS integration: entry as one line in a log book + additional field for NIKA specific * Improve on plot quicklook * possibility to make subscans shorter than 10 seconds * automatic trigger of data reduction when a scan is finished * focus film and otf_map films. * Improved skydip routine (with current Az as the default) * Webcam poiting the sky through the vertex of the primary * auto-recovering of resonances * Telescope warning is missing when a scan is stuck |
1. Remove this warning: '''W-LISSAJOUS, WARNING--CONDITION: Elevation must be less than 83.28 [deg]'''. It is annoying and confusing for the observers (added by IH on 01 Mar 2014). 1. focus film and otf_map films. 1. Things would be nice to have: ....... humidifiers to sleep better, NIKA resident Moonboots to walk and breath, helmet, logos to identify NIKA space ... |
Wish list for NIKA
Important
IRAM-side
- Focus: When observing Lissajous maps at different focus positions to deduce the focus offsets, it'll be nice to do these maps as subscans and not as scans. This would make automatic data reduction easier.
Modify telescope information stream (PaKo & or ELVIN) and/or Camadia on NIKA side so that:
all the different types of Lissajous (focus, pointing, map) are identifiable with a specific name in the scan info data stream & in the automatic logsheets (currently they are all called Lissajous) (SL 20 Mar 2014)
- when a focus scan is run the starting focus position is broadcast and usable by the NIKA IDL RTA software (quicklook) (SL 20 Mar 2014)
when a focus scan is run use by default (e.i. if the information is not specified in PaKo) the current focus as the starting point (SL 20 Mar 2014); this has do be done for the future Focus-Lissajous scan which will include several subscans (item 1. above), but if this future scan is not ready for the next run, include this default focus in the current Lissajous focus scripts; for the moment there's a prompt in the the script asking for the current focus in order to calculate the values of focus positions that will be applied to the multiple Lissajous scans run in the script, the request is that the script calculates the several values of focus to be tested by itself without prompt; see the current script to understand better this request)
when a skydip is run use use by default (e.i. if the information is not specified in PaKo) the current azimuth as the starting point (SL 20 Mar 2014); the current method to do skydips with NIKA is to use a script including the DYI-Tip source which coordinates has to be edited each time, the request is that the azimuth coordinate is by default the current coordinate of the telescope, not an azimuth prompted or edited manually in the script (remark: due to the fact that we use 2 subscans at several airmas values the standar TIP command of PaKo can't be used with NIKA)
Use the run 7 data to determine the Nasmyth offsets of each pixels, then implement a look up table in NCS, with a selection tool, so that rather entering Nasmyth offset in PaKo one can change the reference detector by selecting the number of the detector to use (e.g. enter in PaKo: ref det 494). This possibility existed with MAMBO.
- Tuning in first subscan with an option in all pako commands: /tune /tsubtune 15 to be able to tune for a dedicated first subscan of 15 seconds
- possibility to make subscans shorter than 10 seconds
- automatic trigger of data reduction when a scan is finished
- Telescope warning is missing when a scan is stuck
- Access to NIKA observations in TAPAS mySQL data base + dedicated search interface (21-Mar-2014)
Neel-side
The data reduction software should correct for tracking deviations. This is particularly important for 1mm observations under high wind, doing Lissajous scans. See SL summary of coordinate parameters from antMD (-> Elvin) and IMBFITS.
- auto-recovering of resonances
Nice-to-have
Remove this warning: W-LISSAJOUS, WARNING--CONDITION: Elevation must be less than 83.28 [deg]. It is annoying and confusing for the observers (added by IH on 01 Mar 2014).
- focus film and otf_map films.
- Things would be nice to have: ....... humidifiers to sleep better, NIKA resident Moonboots to walk and breath, helmet, logos to identify NIKA space ...