Size: 437
Comment:
|
Size: 2638
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
== Wish list for NIKA == | = Wish list for NIKA = |
Line 3: | Line 3: |
* The data reduction software should be able to correct for tracking deviations (added by IH on 20 Feb 2014) * User friendly procedure to correct lateral focus offsets (added by CK on 20 Feb 2014) * TAPAS log should list scan-number (added by CK on 22 Feb 2014) |
== Important == |
Line 7: | Line 5: |
Comment: We shall have a meeting in March to wrap-up the 1st pool run and to decide on what shall be prepared for the next run in Autumn. | === 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. 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. 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) 1. 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) 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. 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 1. Telescope warning is missing when a scan is stuck === 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 [[CoordinatesParamNCS|coordinate parameters from antMD (-> Elvin) and IMBFITS]]. 1. 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). 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. 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.
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)
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
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 ...