Configurable Resources / Add 2 New GBT Resources
NRAO Interactive Services Modification Request 4C2n308, June 2008
1. Introduction
The Resources page is comprised of telescope specific information. Therefore individuals at the local site specify any changes that are required for a given proposal cycle. The available resources evolve as new instruments are developed, existing instruments are modified, or as proposal pressure limits the available resources. These details are best managed by the local site. Therefore it would be useful to allow the individual sites to configure the Resource page.
2. Background
Currently, any changes in the Resource page is initiated at the local site. This information is then usually passed to the
E2E division and then to
OpenSky. A configurable Resources page would allow the local site to make changes directly and minimize the time to communicate these details and should in principle reduce any errors.
3. Requirements
Below are requirements for a GBT Resource page and examples of how such a configurable Resource page might work.
*
GBT Resource Specifications
*
GBT Resources Table
Here are the Resource Page changes for June 2008:
- Add back in the K, Ka, and Q-band receivers which were removed last cycle.
- Add MUSTANG: MUSTANG is a receiver and backend in one package. One should not be able to select MUSTANG as just the receiver or the backend. Maybe a warning message should be issued if this happens. There are no additional parmeters to be set but please place the following note where info about frequencies, bandwidths, etc. are listed:
"The Mustang bolometer array has 64 pixels and operates with a 20 GHz bandwidth centered at 90 GHz. Please contact Brian Mason (
bmason@nrao.edu) for more details and collaboration information."
- Add Zpectrometer: This is a backend that covers all three Ka receiver bands at the same time. It can only be used with the Ka-band receiver. If another receiver is selected then a warning should be issued. At this time there are no additional parameters to be set but please place the following note where info about frequencies, bandwidths, etc. are listed:
"The Zpectrometer has 14 GHz of instantaneous bandwidth that cover 26-40 GHz. Please contact Andy Harris (
harris@astro.umd.edu) for more details and collaboration information."
4. Design
Technical lead should provide a brief description of how this will be implemented in the code.
5. Deployment Checklist
Documentation? Systems/hardware/networking things needed for deployment?
6. Test Plan
6.1 Internal Testing
6.3 Integration/Regression Tests
Signatures
APPROVED: I acknowledge that my request is fully contained in this MR, and if the Open Sky (or other NIS or PST developers) deliver exactly what I specified, I will be happy.
ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests, and I am happy with the results.
Written |
- - - - - |
Checked |
- - - - - |
Approved by Scientific Sponsor |
- - - - - |
Accepted/Delivered by Sponsor |
- - - - - |
Symbols:
- Use
%X%
if MR is not complete (will display )
- Use
%Y%
if MR iscomplete (will display )
Discussion Area
--
DanaBalser - 19 Feb 2008