|
Size: 7438
Comment:
|
Size: 7295
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ##acl NicolasBillot,hermelo,CarstenKramer,SamuelLeclerc:read,write,delete,revert,admin Default ##http://www.iram.es/IRAMES/mainWiki/Bolometers/ObservingSession = Observing session = Observations are carried from a dedicated pool account (ask the AoD for the login information). |
#acl hermelo,CarstenKramer,NicolasBillot,SamuelLeclerc:read,write,delete,revert,admin Default = Observing with NIKA2 = <<TableOfContents(3)>> '''Go to the [[http://www.iram.es/IRAMES/mainWiki/Continuum/NIKA2/Main| NIKA2]] main page.''' ---- == Starting PaKo == Log into the pool account (ask the AoD/operator for the login information), open a terminal and type: {{{ $ ssh -X mrt-lx1 $ goNIKA }}} == Observations queue == Open a terminal and type: {{{ $ ssh -X mrt-lx1 $ observationQueue }}} This will open a file browser with a list of all the jobs commanded. The display is automatically refreshed. Right-click to delete a job. ## Check the [[https://mrt-lx1.iram.es/mainWiki/NcsUG | NCS user guide wiki]] for more obs* commands. == Starting the NIKA2 pipeline == Open a terminal and type: {{{ $ ssh -X observer@nika2-a (ask the AoD for the password) $ IDL IDL> auto_nk_rta }}} It is also possible to reduce the scans manually: {{{ IDL> nk_rta, scanID (e.g. '20151019s132') }}} == Starting XEphem == Open a terminal and type: {{{ $ ssh -X mrt-lx3 $ useNCS $ azElToXephem.py & $ xephem & }}} Click on the tab "View" and open the "Sky View". The "cross hair" shows the coordinates the telescope is pointing at. The filled blue circles are the pointing sources. The size of the circle is proportional to the flux of the target. Click on the tab "Data" and go to "Files". In the new window go again to "Files" and load the catalog of the project that you are observing. {{ attachment:XEphem.png | XEphem example | width=850 }} == Pointing == Choose a nearby quasar as pointing and focus source (using e.g. XEphem): {{{ PAKO> source 0133+476 /cat iram-J2000.sou }}} Launch the '''nkpoint''' script: {{{ PAKO> @ nkpoint mode }}} where the keyword "mode" can adopt the values '''b''' for bright sources, '''f''' for faint sources or '''l''' for very faint sources that require the Lissajous pattern. Once the pointing is finished, enter the new pointing corrections: {{{ PAKO> set pointing PnewX PnewY }}} == Focus == The focus needs to be monitored and it needs to be corrected online! This should be done every three hours or so in the Z direction and every 24 hours in the X and Y direction. To check the quality of the focus, type: {{{ PAKO> @ focusliss axis }}} where the keyword axis can adopt the values X, Y or Z (i.e., the three axes of the subreflector). Once the focus is finisihed, enter the new focus value: {{{ PAKO> set focus Fnew /dir axis }}} Now the telescope is pointed and focused, and ready to start to observe. == Beam map (needs to be updated once we have an standard procedure) == The beam map consists in 3 ?'x?' maps with ~?" steps between rows and a duration ~?? minutes. Beam maps are designed to ensure the source is moved over all the detectors of the array, in order to characterize and calibrate them (field of view geometry, flat field, stability...). The aim is to calculate the actual pixel offsets in the focal plane (see figure below). To obtain a beam map go to a primary calibrator and launch the '''beammap.pako''' script: {{{ PAKO> @ beammap }}} == Skydips (needs to be updated once we have an standard procedure) == To run a skydip with NIKA type in !PaKo: {{{ PAKO> @ skydip_DYI }}} == Science targets == Observations of science targets are performed via on-the-fly and/or Lissajous maps. For example, for a 16'x12' on-the-fly map, with a position angle of 25 degrees, a tilt angle of 0 degrees (both measured '''anticlockwise'''), in equatorial coordinates (radec), just type: {{{ PAKO> @ nkotf 16 12 25 0 radec }}} For a 3'x3' Lissajous type: {{{ PAKO> @ nkliss 3 }}} A sequence of several scans can be loaded using scripts. For example, the script [[attachment:observe_NGC4449.txt | observe_NGC4449.pako]] combines several 14'x14' on-the-fly maps at different angles in the horizontal coordinate system (azel). ---- == Pool observations == Pool observations are carried from a dedicated pool account (ask the AoD for the login information). |
| Line 10: | Line 162: |
| For example, the file [[attachment:README_078-13.txt | ~/078-13/README_078-13.txt ]] shows you how to observe the project 078-13. <<TableOfContents(3)>> '''[[ http://www.iram.es/IRAMES/mainWiki/GISMO/Main | Go back to the GISMO Main Wiki ]]''' ---- == Choose a project == First log into the [[https://pools.iram.es | Pool data base]] (ask the AoD for the login information) and click on the GISMO tab. {{attachment:PoolDatabase.png}} |
For example, the file [[attachment:README_199-14.txt | ~/199-14/README_199-14.txt ]] explains you how to observe the project 199-14. === Choose a project === First log into the [[https://pools.iram.es | Pool data base]] (ask the AoD for the login information) and click on the GISMO/NIKA tab. {{attachment:PoolDatabase.png | Pool data base | width=850 }} |
| Line 28: | Line 172: |
| Only green projects can be observed. | Only green projects should be observed. |
| Line 31: | Line 175: |
| {{attachment:Visibility.png}} | {{attachment:Visibility.png | Visibility plot | width=850}} |
| Line 37: | Line 181: |
| Since project 103-13 sets first, you should first observe this project. | Since project 103-13 sets first, it is a good idea to observe this project. |
| Line 42: | Line 186: |
| ---- == Starting PaKo == To run the observations at 30m telescope it is necessary to start a !PaKo session. First log into the mrt-lx1 machine: {{{ ssh -X gismos-13@mrt-lx1.iram.es (ask the AoD for the password) }}} Then start PaKo: {{{ gopako pakodisplay pakoGISMO }}} With these commands, !PaKo will be running in the '~/PaKo/' folder. ---- == Project setup == The standard method to set the project information is through a !PaKo script (see for example [[attachment:setup_078-13.pako | setup_078-13.pako ]]). It is IMPORTANT to set the project accordingly before each observation in order to identify the scans observed for each project, keep control on the time used to observe each project, and write the data files in the right directory. For example, before to start to observe the project 078-13 you must type: {{{ PAKO> @ ~/078-13/setup_078-13.pako }}} When you will be doing tests, or if you have to stop by wind, or whatever, just tape "set project test". That way, no project will loose time due to technical problems, or bad weather. ---- == Catalog of sources == Before to start to observe a certain project it is necessary to load its catalog of sources. For example, for project 078-13: {{{ PAKO> SOURCE CATALOG ~/078-13/catalog_078-13.sou }}} This command will load the following list of sources: {{{ NGC4449 EQ 2000 12:28:09.408 +44:05:32.20 LSR 0.0 NGC4449-S EQ 2000 12:28:10.958 +44:05:26.30 LSR 0.0 NGC4449-N EQ 2000 12:28:12.966 +44:07:04.57 LSR 0.0 NGC4449-E EQ 2000 12:28:17.019 +44:06:30.04 LSR 0.0 }}} To select any of these sources just type: {{{ PAKO> source NGC4449-N }}} ---- == Telescope setup == Check in the PaKo display for the current pointing values (AZcurrent and and ELcurrent) and write them down. Choose a nearby quasar as pointing and focus source (using e.g. XEphem): {{{ PAKO> source 0133+476 /cat * }}} Launch the '''[[attachment:gismo_pointing.pako | gismo_pointing ]]''' script: {{{ PAKO> @ gismo_pointing }}} Check in the GISMO Nexus logsheet for the corrections in azimuth and elevation (columns pnt.dAZ and pnt.dEL). Calculate the new pointing values as: {{{ AZnew = AZcurrent + pnt.dAZ ELnew = ELcurrent + pnt.dEL }}} If the new pointing corrections are within 10" of the previous values, the GISMO array with its large field-of-view will still be well centered. A posteriori, crush will do the pointing corrections. Then, there is no need to update the pointing constants used by PaKo. If you still want to do so, say {{{ PAKO> set pointing AZnew ELnew }}} Check the focus using the '''[[attachment:gismo_focus.pako | gismo_focus ]]''' script: {{{ PAKO> @ gismo_focus Fcurrent }}} where Fcurrent is the current value of the focus. To calculate the new value of the focus open another terminal and use the python script ~/Focus/Focus.py : {{{ cd Focus/ python Focus.py }}} The python script will ask for the 1st scan of the focus sequence and the total number of scans (i.e., 5). Check if the two estimations shown (see image below) in the plot are consistent and set the new focus value: {{{ PAKO> set focus Fnew }}} '''IMPORTANT:''' The focus needs to be monitored every two hours or so, and it needs to be corrected online! {{attachment:Focus.png}} Now the telescope is pointed and focussed, and ready to observe the project. ---- == Science targets == Observations of science targets are performed via on-the-fly and/or Lissajous maps. For example, for a 6'x12' on-the-fly map rotated 25 degrees (measured North through West) type: {{{ PAKO> @ gismo_onthefly 16 12 25 }}} For a 3'x3' Lissajous type: {{{ PAKO> @ gismo_lissajous 3 }}} For sequences of scans it is strongly recommended to use scripts. For example, the script [[attachment:observe_NGC4449.pako | observe_NGC4449.pako]] consists on a long sequence of 10'x10' on-the-fly maps covering completely the galaxy NGC4449 and 3'x3' lissajous maps focused on the main star forming regions NGC4449-N, NGC4449-S, and NGC4449-E. To launch this script just type: {{{ PAKO> @~/078-13/observe_NGC4449 }}} ---- == Beam map == The beam map consists in a 5'x5' map with ~3" steps between rows and it takes ~18 min. Beam maps are designed to ensure the source is moved over the entire detector. The aim is to calculate the actual pixel offsets in the focal plane (see figure below). To obtain a beam map go to a primary calibrator and launch the '''[[attachment:gismo_beammap.pako | gismo_beammap.pako ]]''' script: {{{ PAKO> @ gismo_beammap }}} {{attachment:Beammap.png}} ----- == Skydips == Since the 4th GISMO pool skydips are fully integrated in the IRAM/GISMO pipeline. Before running a skydips, the observer has to de-activate the automatic relocking of the detectors: {{{ NEXUS -> Configuration -> Advanced -> De-activate automatic relock of detectors }}} Next, launch the '''[[attachment:gismo_skydip.pako | gismo_skydip ]]''' script: {{{ PAKO> @ gismo_skydip }}} At present, the observer then needs to switch-on by-hand the automatic relocking of the detectors: {{{ NEXUS -> Configuration -> Advanced -> Activate automatic relock of detectors }}} ----- Author: Israel Hermelo (IRAM 30m continuum pool manager) |
=== Project setup === The standard method to set the project is: {{{ PAKO> set project XXX-YY }}} However, for pooled observations this is often done using a setup script (see for example [[attachment:setup_199-14.txt | setup_199-14.pako ]]). For example, before to start to observe the project 199-14 you should type: {{{ PAKO> @ ~/199-14/setup_199-14.pako }}} It is IMPORTANT to set the project accordingly before each observation in order to identify the scans observed for each project, keep control on the time used to observe each project, and write the data files in the right directory. When you will be doing tests, or if you have to stop by wind, or whatever, just type "set project test". That way, no project will loose time due to technical problems, or bad weather. === Catalog of sources === Before to start to observe a certain project it is necessary to load its catalog of sources. Usually, this is automatically done within the setup script. If for some reason you need to load the catalog manually, type: {{{ PAKO> SOURCE CATALOG 199-14.sou }}} This command will load the catalog [[attachment:199-14.txt | 199-14.sou ]] with the position of NGC4449: To select this source, just type: {{{ PAKO> source NGC4449 }}} To select a source from the IRAM catalog of pointing sources, just type: {{{ PAKO> source pointing_source /cat iram-J2000.sou }}} ---- ---- Author: Israel Hermelo (Pool Manager of the IRAM 30m continuum cameras) |
| Line 229: | Line 233: |
| Created: 2013.10.25 Last update: 2014.01.14 |
Created: 2013.OCT.25 Last update: 2015.OCT.19 |
Observing with NIKA2
Contents
Go to the NIKA2 main page.
Starting PaKo
Log into the pool account (ask the AoD/operator for the login information), open a terminal and type:
$ ssh -X mrt-lx1 $ goNIKA
Observations queue
Open a terminal and type:
$ ssh -X mrt-lx1 $ observationQueue
This will open a file browser with a list of all the jobs commanded. The display is automatically refreshed. Right-click to delete a job.
Starting the NIKA2 pipeline
Open a terminal and type:
$ ssh -X observer@nika2-a (ask the AoD for the password) $ IDL IDL> auto_nk_rta
It is also possible to reduce the scans manually:
IDL> nk_rta, scanID (e.g. '20151019s132')
Starting XEphem
Open a terminal and type:
$ ssh -X mrt-lx3 $ useNCS $ azElToXephem.py & $ xephem &
Click on the tab "View" and open the "Sky View". The "cross hair" shows the coordinates the telescope is pointing at. The filled blue circles are the pointing sources. The size of the circle is proportional to the flux of the target. Click on the tab "Data" and go to "Files". In the new window go again to "Files" and load the catalog of the project that you are observing.
Pointing
Choose a nearby quasar as pointing and focus source (using e.g. XEphem):
PAKO> source 0133+476 /cat iram-J2000.sou
Launch the nkpoint script:
PAKO> @ nkpoint mode
where the keyword "mode" can adopt the values b for bright sources, f for faint sources or l for very faint sources that require the Lissajous pattern.
Once the pointing is finished, enter the new pointing corrections:
PAKO> set pointing PnewX PnewY
Focus
The focus needs to be monitored and it needs to be corrected online! This should be done every three hours or so in the Z direction and every 24 hours in the X and Y direction. To check the quality of the focus, type:
PAKO> @ focusliss axis
where the keyword axis can adopt the values X, Y or Z (i.e., the three axes of the subreflector).
Once the focus is finisihed, enter the new focus value:
PAKO> set focus Fnew /dir axis
Now the telescope is pointed and focused, and ready to start to observe.
Beam map (needs to be updated once we have an standard procedure)
The beam map consists in 3 ?'x?' maps with ~?" steps between rows and a duration ~?? minutes. Beam maps are designed to ensure the source is moved over all the detectors of the array, in order to characterize and calibrate them (field of view geometry, flat field, stability...). The aim is to calculate the actual pixel offsets in the focal plane (see figure below). To obtain a beam map go to a primary calibrator and launch the beammap.pako script:
PAKO> @ beammap
Skydips (needs to be updated once we have an standard procedure)
To run a skydip with NIKA type in PaKo:
PAKO> @ skydip_DYI
Science targets
Observations of science targets are performed via on-the-fly and/or Lissajous maps. For example, for a 16'x12' on-the-fly map, with a position angle of 25 degrees, a tilt angle of 0 degrees (both measured anticlockwise), in equatorial coordinates (radec), just type:
PAKO> @ nkotf 16 12 25 0 radec
For a 3'x3' Lissajous type:
PAKO> @ nkliss 3
A sequence of several scans can be loaded using scripts.
For example, the script observe_NGC4449.pako combines several 14'x14' on-the-fly maps at different angles in the horizontal coordinate system (azel).
Pool observations
Pool observations are carried from a dedicated pool account (ask the AoD for the login information). Each project has a folder within the home directory of the pool account with instructions on how to proceed. Read carefully the README file before to start. For example, the file ~/199-14/README_199-14.txt explains you how to observe the project 199-14.
Choose a project
First log into the Pool data base (ask the AoD for the login information) and click on the GISMO/NIKA tab.
Projects have different priorities from 6 (highest priority) to 1 (lowest priority). Green color indicates that the project is scheduled, orange that the project is on hold, and red that the project is finished. Only green projects should be observed. To check the visibility of these projects go to the visibility tab:
The red vertical line corresponds to the current time (UT). In this example there are four priority 5 projects. Project 077-13 is not visible at the current time. Project 079-13 is close to the low elevation limit so it is a bad option. Since project 103-13 sets first, it is a good idea to observe this project. After 2-3 hours change to project 100-13. In case that none of the priority 5 projects have weather requirements (see the README files) compatible with the current conditions, go for priority 4 projects and so on.
Project setup
The standard method to set the project is:
PAKO> set project XXX-YY
However, for pooled observations this is often done using a setup script (see for example setup_199-14.pako). For example, before to start to observe the project 199-14 you should type:
PAKO> @ ~/199-14/setup_199-14.pako
It is IMPORTANT to set the project accordingly before each observation in order to identify the scans observed for each project, keep control on the time used to observe each project, and write the data files in the right directory. When you will be doing tests, or if you have to stop by wind, or whatever, just type "set project test". That way, no project will loose time due to technical problems, or bad weather.
Catalog of sources
Before to start to observe a certain project it is necessary to load its catalog of sources. Usually, this is automatically done within the setup script. If for some reason you need to load the catalog manually, type:
PAKO> SOURCE CATALOG 199-14.sou
This command will load the catalog 199-14.sou with the position of NGC4449: To select this source, just type:
PAKO> source NGC4449
To select a source from the IRAM catalog of pointing sources, just type:
PAKO> source pointing_source /cat iram-J2000.sou
Author: Israel Hermelo (Pool Manager of the IRAM 30m continuum cameras)
email: hermelo@iram.es
Created: 2013.OCT.25
Last update: 2015.OCT.19