Wish list for NIKA

Important

IRAM-side

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.

2. 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)

   2. 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)

   3. when a focus scan is run, use by default (e.i. if the information is not specified in the PaKo command line) 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 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 these several values of focus to be tested are calculated automatically when the script is called; see the current script to see the necessity of the prompt mentioned here)

   4. when a skydip is run, use by default (e.i. if the information is not specified in the PaKo command line) 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)

3. 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.

4. 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
5. possibility to make subscans shorter than 10 seconds
6. automatic trigger of data reduction when a scan is finished
7. Telescope warning is missing when a scan is stuck
8. Access to NIKA observations in TAPAS mySQL data base + dedicated search interface (21-Mar-2014)

Neel-side

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 coordinate parameters from antMD (antenna FITS and Elvin broadcast) and IMBFITS.

2. auto-recovering of resonances

Nice-to-have

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).

2. focus film and otf_map films.
3. Things would be nice to have: ....... humidifiers to sleep better, NIKA resident Moonboots to walk and breath, helmet, logos to identify NIKA space ...