|
Size: 8961
Comment:
|
Size: 7704
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 34: | Line 34: |
| * [[attachment:GISMOSoftwareOperationalManual-Apr2013.pdf|GISMO Software Operational Manual]] by Steve Maher and Johannes Staguhn, April 2013 | * [[attachment:GISMOSoftwareOperationalManualMay2013.pdf]] by Steve Maher and Johannes Staguhn, May 2013 |
| Line 70: | Line 70: |
| == Observations == === pako scripts === * GismoObservingScripts provides examples and explanations about how to start !PaKo in order to run the telescope with GISMO, and about total power maps using Lissajous and On-the-fly patterns. Observations using the wobbler will not be offered for this run. The old page GismoHowToObserve is obsolete. * [[https://www.iram.es/IRAMES/mainWiki/GismoPakoNotes|Notes on paKo and NCS for GISMO 2012]] === Pointing Sources === [[http://www.iram.es/IRAMES/FluxMonitoring/PointingSources/plotPointingSources.html|Plots for Pointing Sources]] can be accessed within the IRAM network. These data are provided ONLY to help in the planning of observations, in particular to select pointing and focus sources at the IRAM 30-m telescope. They should not be used for any other purpose. === crush data reduction === * CrushExamples |
|
| Line 94: | Line 112: |
==== Observing scripts ==== * GismoObservingScripts provides examples and explanations about how to start !PaKo in order to run the telescope with GISMO, and about total power maps using Lissajous and On-the-fly patterns. Observations using the wobbler will not be offered for this run. The old page GismoHowToObserve is obsolete. * [[https://www.iram.es/IRAMES/mainWiki/GismoPakoNotes|Notes on paKo and NCS for GISMO 2012]] ==== Data reduction ==== To reduce GISMO data with crush, first log into your project account: ssh -X project_number@mrt-lx3.iram.es Raw data are stored in the directory ~/observationData/gismo. The scans are stored in a filing hierarchy, organised by source name, then an IRAM scan ID composed of a UT calendar date and a scan number. For example, the scan 113 taken on 2013-04-12 of M33 is stored as ~/observationData/gismo/M33/2013-04-12.113/M33_2013-04-12.113_gismo.fits. To reduce this scan with crush type in your terminal: crush gismo -default -datapath=~/observationData/gismo -object=M33 -date=2013-04-12 113 -outpath=~/crush_reduction -name=M33 In the case of faint sources (S/N<10) you can use the option "faint": crush gismo -faint -datapath=~/observationData/gismo -object=M33 -date=2013-04-12 113 -outpath=~/crush_reduction -name=M33_faint Other options to optimise the reduction are "bright" for strong sources (S/N>1000), "extended" for structures larger than the field of view, and "deep" for deep fields (faint point sources). It is possible to add several scans: crush gismo -faint -datapath=~/observationData/gismo -object=M33 -date=2013-04-12 113-116 120 -date=2013-04-13 1-6 -outpath=~/crush_reduction -name=M33_faint_allscans and also combine different fileds of view: crush gismo -faint -datapath=~/observationData/gismo -object=M33a -date=2013-04-12 113-116 120 -object=M33b -date=2013-04-14 21-23 -outpath=~/crush_reduction -name=M33ab_faint_allscans For a detailed description of crush's options and capabilities, see the [[http://www.submm.caltech.edu/~sharc/crush/document.html|crush documentation]]. |
GISMO
This page is maintained by IH, CK, SL and the GISMO team
Contents
Overview
|
Pixels |
Wavelength |
Bandwidth |
Sensitivity |
HPBW |
Field-of-View |
Spacing |
|
|
mm |
[GHz] |
[mJy sqrt(s) |
|
|
|
GISMO |
8x16 |
2 |
140-162 |
10 |
16.7" |
1.8'x3.7' |
13.75" |
The Goddard-IRAM Superconducting 2mm Observer (GISMO) is a bolometer camera for the IRAM 30m telescope. It has been build by Goddard Space Flight Center, in Greenbelt, Maryland under the lead of Johannes Staguhn. GISMO consists of 8x16 pixels with super conducting transition edge sensors (TES). The TES are read out by time domain SQUID multiplexers built at the National Institute for Standards (NIST), in Boulder, Colorado. The nominal bandwidth is 140-162 GHz (FWHM), pixels are spaced by 13.75", the telescope HPBW is 16.7". The sensitivity has improved relative to the April 2011 run to about 10 mJy sqrt(sec) (cf. report below). The field-of-view is 1.8'x3.7' . Two standard observing modes are offered, Lissajous curves and on-the-fly scans. Both work in total power, without switching the secondary. An automated pipeline merges the GISMO data with the telescope data streams to create FITS files which are automatically processed by the reduction software crush to create logs, pointing results, and a first quick view of the data. Typical overheads for single science targets on the sky are 60%. The relative flux stability is about 8% (cf. report below).
Call for proposals for the summer semester 2013
GISMO is offered again to the community:
Updated guidelines to estimate observing times (Billot et al. 2012).
Report on GISMO performance based on the pool run in April-2012 (Bruni et al. 2012).
crush data processing software will be used to reduce all data.
Documentation
GISMOSoftwareOperationalManualMay2013.pdf by Steve Maher and Johannes Staguhn, May 2013
GISMO NCS Software Interface and FITS File Description by Steve Maher, Attila Kovacs, Albrecht Sievers, April 2012
Publications
Dwek, Staguhn et al. 2011 ApJ,
Star and dust formation activities in AzTEC-3: A starburst galaxy at z = 5.3Arendt et al. 2011 ApJ,
The Radio - 2 mm Spectral Index of the Crab Nebula Measured with GISMOCapack et al. 2011 Nature,
A massive proto-cluster of galaxies at a redshift of z~5.3Dicker et al. 2009 ApJ,
90GHz and 150GHz observations of the Orion M42 region. A sub-millimeter to radio analysisBenford, Moseley, Zmuidzinas 2009 Journal of Physics
Direct detectors for the Einstein inflation probeIRAM Newsletter 2/2009
GISMO - The Goddard-IRAM Superconducting 2 Millimeter Observer tested at the IRAM 30m observatoryStaguhn et al. 2008 Journal of Low Temperature Physics, 151, 3, 709
GISMO, a 2 mm Bolometer Camera Optimized for the Study of High Redshift Galaxies
Support teams
Overall coordinator: Samuel Leclercq <leclercq@iram.fr> (IRAM/Grenoble)
- GISMO support team:
Johannes Staguhn <johannes.g.staguhn@nasa.gov> (PI)
- Elmer Sharp
- Steve Maher
- Dale Fixen
- Attila Kovacs (crush)
- IRAM/Granada support team:
Carsten Kramer (station manager, <kramer@iram.es>)
Israel Hermelo (bolometer pool manager, <hermelo@iram.es>)
Albrecht Sievers (friend of GISMO, <sievers@iram.es>)
Manuel Gonzalez (heterodyne pool manager, <gonzalez@iram.es>)
Nicolas Billot (30m scheduler, <billot@iram.es>)
Observations
pako scripts
GismoObservingScripts provides examples and explanations about how to start PaKo in order to run the telescope with GISMO, and about total power maps using Lissajous and On-the-fly patterns. Observations using the wobbler will not be offered for this run. The old page GismoHowToObserve is obsolete.
Pointing Sources
Plots for Pointing Sources can be accessed within the IRAM network. These data are provided ONLY to help in the planning of observations, in particular to select pointing and focus sources at the IRAM 30-m telescope. They should not be used for any other purpose.
crush data reduction
Observing Runs
April 2013 - 3rd pool run
Pool projects and observers
- Winter semester 2012 observations will be carried out as pooled observations from a dedicated pool account. M.Gonzalez will provide login information.
Progress of observations can be followed via the pool data base.
- GISMO NEXUS log
November 2012 - 2nd pool run
Two weeks of dedicated GISMO observations have been carried out during November 2012.
Pool projects and observers
Daily reports
April 2012 - 1st pool run
In September 2011, GISMO had for the 1st time been offered to the community. Two weeks of dedicated GISMO observations have been carried out during April 2012.
Daily reports
Test plan
TestPlan for the first days of the April run
Test runs 2007-2012
5th alignment run, March 2012
Go to the 5th run Wiki page (installation of GISMO at a permanent position with new optics, baffle and new filter)
4th test run, April 2011
Go to the 4th run Wiki page (restricted access, please send an email to SL to obtain the login information)
3rd test run, April 2010
2nd test run, October 2008