Add Zpectrometer Control To Configuration Tool

Modification Request #1 (C6 2006)

UNDER CONSTRUCTION

1. Introduction

The ZSpectrometer is a new backend whic will undergo commissioning this fall. After commissioning it will become a facility backend. To facitliate both commissioning and observing with the instrument, the config tool should be modified to support it.

2. Background

This link provides information on the [ZSpectrometer Manager. See NRAO Zpectrometer Wiki for general information on the backend.

3. Requirements

The config tool must recognize "zspectrometer" as a legal backend. MelindaMello What backend keyword should be used for the config tool for the zspectrometer? The following table contains all of the zspectrometer specifc Manager parameters.

WASP keyword	type	level	unit	description	Manager Parameter	comments
chopfreq	d	C	Hz	Cal (noise diode) firing frequency	chopfreq	Needs new name!
beclip#	s	C		Backend active channel range	bclip
defcold	s	W		Cold type for tcold=-1	defcold
defhot	s	W		Hot type for thot=-1	defhot
diagout	b	W		Write diagnostic files	diagout	We should probably use debugLevel for this since it is already part of the Manager.
exposure	d	C	s	Effective integration time	scanLength	This is different - the is the actual time, not requests
object	s	H		source name	source
obsid	s	H		scan number	scanNumber
projid	s	H		Project identification	projectId
tcaltype	s	W		Calibration algorithm	tcaltype
tcold	d	W	K	Cold load temperature	tcold
thot	d	W	K	Hot load temperature	thot

This is a strawman proposal as to how the config tool keywords might mapped to ZSpectrometer Manager parameters.

The tracking beam must be set to WASP. MelindaMello Is this information the actual beam offsets that the antenna writes to the fits files? If so, the config tool does not have this information readily available. It is possible that the config tool could use the the antenna database, but its not a clean separation of responsibilities. We need to understand how they (ZSpect) plan on using this info. If its just for data reduction, then Ray is going to put it into the SDFITs/ZSpectrometer MR.

The ZSpectrometer Managers parameter "exposure" will be set to the value of the config_tool keyword "tint".

The ZSpectrometer Managers parameter "tcaltype" will be set to

"zero" if the keyword = 'tp_nocal'
"cwswigs" if the keyword = 'sp_nocal'
"totpwr" if the keyword = 'tp'
"nobs" if the keyword = 'sp'

Is there an obsmode or just the tcaltype above?

Main.Melinda I have seen various names for the WASP programs linked on our web. What are the current "legal" names? The slides in wasp-slides-1.ps only describe 3 : tcal, totltpw and nobs. Yet other documentation lists the above programs.

The ZSpectrometer Managers parameter "chopfreq" will be set to the new ZSpectrometer specfic keyword "chopfreq".
The ZSpectrometer Managers parameter "thot" will be set to the new ZSpectrometer specfic keyword "thot".
The ZSpectrometer Managers parameter "defcold" will be set to the new ZSpectrometer specfic keyword "defcold".
The ZSpectrometer Managers parameter "defhot" will be set to the new ZSpectrometer specfic keyword "defhot".
The ZSpectrometer Managers parameter "bclip" will be set to the new ZSpectrometer specfic keyword "beclip". Valid input will be a tuple or list of the form [X,Y] or X,Y. Where X is the starting channel and Y is the end channel (both X and Y are inclusive).

MelindaMello Are these parameters set for all observing Programs or are they only required for some observing Programs?

MelindaMello I need valid ranges and default values for all config tool keywords. These are the startup defaults which may or may not be the defaults the config tool should use (if any). For example -1 as a default for exposure seems like a bad idea! beclip [1..9999) chopfreq = -1 defcold = 'sky' defhot = 'ambient' NOTE: are their illegal combinations of defcold and defhot? exposure = -1 tcaltype = 'vane' NOTE: tcaltype VANE, I know nothing about. tcold = 77 thot = -1 obsmode = 'undefined'

In addition the LO! must be removed from the ScanCoordinators?' device list for some if not all (?) configurations of the zspectromter?

4. Design

Currently LO!B is selected for all Configurations? If so, then the config tool must be modified to select the LO1 based on the backend parameter.

6. Deployment Checklist

What has to get done to integrate this completely into the system. This checklist must be completed before Cycle Integration Testing begins.

Communication with Computing group needed? No.
What documentation needs to be updated? None.
Training Needed? Is this being released to staff astronomers or everyone right now? General release.
Notification Needed? None.

Written	- MelindaMello - 02 Aug 2006
Checked
Approved by Sponsor	symbol - name - date
Approved by CCC	symbol - name - date
Accepted/Delivered by Sponsor	symbol - name - date

Symbols:

Use %X% if MR is not complete (will display )
Use %Y% if MR iscomplete (will display )

CCC Discussion Area

-- MelindaMello - 22 Aug 2006

Topic ModificationRequest1C606 . { Edit | Attach | Ref-By | Printable | Diffs | r1.1 | More }

Revision r1.1 - 22 Aug 2006 - 14:49 GMT - MelindaMello	Content copyright © 1999-2007 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.

Add Zpectrometer Control To Configuration Tool

Modification Request #1 (C6 2006)

1. Introduction

2. Background

3. Requirements

4. Design

6. Deployment Checklist

7. Test Plan

7.1 Internal Testing

7.2 Sponsor Testing

Signatures

CCC Discussion Area


NRAO Home > Green Bank \| Wiki Topic: GB > Software > ModificationRequest1C606

Changes \| Index \| Contents \| Search \| Statistics \| Go