EVLA/VLBA/GBT Resources

NRAO Interactive Services Modification Request 1 S2 2011



1. Introduction

Any changes to the telescope specific resources

2. Background

3. Requirements

EVLA

  • We need a check when proposers do not change the Session LST range from the default 0000 - 2400. Sometimes this is valid, but most of the time it is just that the proposers don't change it based on the source(s) they are requesting to observe in that session. It causes lots of problems downstream for us. We would like at least some warning given that they haven't modified the LST range, prompting them to do so unless 0000 - 2400 is really correct. We had some discussion about when/where in the PST this should be done, but didn't come to a conclusion. Maybe Ashish or someone else from Open Sky can make a suggestion.

  • We need a way to re-inform the proposers when they select OSRO modes from EVLA resources to point out that they will get more than one subband per baseband. As a matter of fact, they get eight subbands per baseband. I suggest that to the right of where the OSRO Resource says Correlator: we put in something like the following. "This table shows the bandwidth, etc. per subband. Current OSRO modes give eight subbands per baseband." That is, if we can fit it in. Perhaps make it in red.

VLBA

  • For the VLBA, under Resources, we would like to remove the block on being able to check the GBT box if Wideband Observing System is checked.

  • In addition, under Resources, we would like to add a drop-down menu at the top, at the same level as Wavelength or Processor, for example. This menu would be labeled "Observing Mode" and have two choices "Standard" and "VLBA RSRO". Standard would lead to exactly what we have now, whereas "VLBA RSRO" would lead to exactly what we have now plus a text box at the bottom of the page whereby proposers could write into what they would like to accomplish in Resident Shared Risk Observing for the VLBA. The contents of this box would need to be written out on the cover page under VLBA Resources. I realize we don't have much real estate there, so we may have to iterate on how we get this information on the cover.

  • Finally, if "VLBA RSRO" is selected under the Resources page, we would like the page limit for the Scientific Justification to be augmented by two pages, so the limit for the justification would be six rather than the current four pages for "standard" proposals.

GBT

  • GBT Sensitivity Calculator: Replace current link with: https://dss.gb.nrao.edu/calculator-ui/war/Calculator_ui.html
  • Zpectrometer: This will now be considered a "private" backend without user support. So in addition to the current text please add a check box with the following text: "I have pre-approval from the instrument PI to use this instrument, and understand that the GBT staff does not provide any support for this back end." This is similar to what we have for GASP.
  • GASP: This backend will be retired and will no longer be available. Please remove it from the PST.
  • FPGA Spectrometer: Add a new backend called "FPGA Spectrometer". Basically follow the inputs used for the GBT Spectrometer backend.
    • Add one new field called "Cross-Polarization" with choices "yes" or "no". All modes support both yes and no.
    • Remove the field called "Sampling Level".
    • Add the following text below the input fields: "The FPGA Spectrometer will be available in shared risk mode. Click here for further information." I need to add the link.
    • Based on the selected receiver and bandwidth, the number of spectral windows is limited.
      • 1 beam receivers: PF1 340, PF1 450, PF1 600, PF1 800, PF2, L-band, S-band, C-band, and X-band.
      • 2 beam receivers are Ku-band, KFPA, Ka-band MM-F1, Ka-band MM-F2, Ka-band MM-F3, Q-band and W-band. (Note that only two beams of KFPA can be used with the new spectrometer for this proposal call; this will change for future proposal calls).
    • The number of modes for each bandwidth will change in future proposal calls as the spectrometer capabilities are increased. Here are the allowed modes:

Large Bandwidth, few spectral window Modes

Bandwidth (MHz) Sp Windows Beams Channels Res (kHz) Min Int (Sec)
1500 1 or 2 1 1024 1465 0.5
1500 1 2 1024 1465 0.5
1000 1 or 2 1 2048 488 0.7
1000 1 2 2048 488 0.7
800 1 or 2 1 4096 195 1.3
800 1 2 4096 195 1.3
500 1 or 2 1 8192 61 2.5
500 1 2 8192 61 2.5

Low Bandwidth, few spectral window Modes

Bandwidth (MHz) Sp Windows Beams Channels Res (kHz) Min Int (Sec)
400 1 or 2 1 16384 24 5
400 1 2 16384 24 5
250 1 or 2 1 32768 7.6 10
250 1 2 32768 7.6 10
100 1 or 2 1 32768 3.1 10
100 1 2 32768 3.1 10
50 1 or 2 1 32768 1.5 10
50 1 2 32768 1.5 10
25 1 or 2 1 32768 0.8 10
25 1 2 32768 0.8 10
10 1 or 2 1 32768 0.3 10
10 1 2 32768 0.3 10
5 1 or 2 1 32768 0.15 10
5 1 2 32768 0.15 10
1 1 or 2 1 32768 0.03 10
1 1 2 32768 0.03 10

Low Bandwidth, many spectral window Modes

Bandwidth (MHz) Sp Windows Beams Channels Res (kHz) Min Int (Sec)
30 8 or 16 1 4096 7.3 10
30 8 2 4096 7.3 10
15 8 or 16 1 4096 3.7 10
15 8 2 4096 3.7 10
10 8 or 16 1 4096 2.4 10
10 8 2 4096 2.4 10
5 8 or 16 1 4096 1.2 10
5 8 2 4096 1.2 10
1 8 or 16 1 4096 0.2 10
1 8 2 4096 0.2 10

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.2 Sponsor 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 ALERT!)
  • Use %Y% if MR iscomplete (will display DONE)


Discussion Area

-- DanaBalser - 201
Topic revision: r6 - 2011-06-17, MarkClaussen
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback