Guppi Upgrades

Modification Request #2 Q3 2011

1. Introduction

GUPPI is getting lots of use, and there are a couple of commonly used modes that could be better supported. One mode is the time-domain mode, where we collect raw voltages. Another is the low-bandwidth, high-resolution mode (the Toney Minter mode). These are both implemented in hardware/firmware, but not available in the machine to users. There are, I think, a few more modes that are not generally available to users, such as the coherent search modes.

2. Background

With infinite flexibility comes infinite complexity.

3. Requirements - For the sponsor to fill out

What are the implementation-independent requirements for this MR?

4. Design Strategy & Summary - For the software engineer to fill out

What is your plan? How are you going to fulfill the requirements?

5. Add Any More Sections That Are Appropriate

(Optional - Remove this section completely if no other sections are added.)

6. Deployment Checklist - For sponsor and/or software engineer

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

Note - The questions below are just to get you thinking. Remove irrelevant questions. Answer relevant ones, but don't keep the question text. And, please take a moment to think of anything else that needs to happen during deployment.

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

7. Test Plan

Critical!! ChangeControlCommittee will be reviewing these. Please send a link to this MR to ToneyMinter along with a suggestion for two reviewers when it is ready for CCC review.

Don't forget to include/acquire any additional GBT test time needed outside integration/regression testing! Get your requests in early!

Important! If possible, you should conduct as many of your tests as possible in offline modes and/or with a simulator. We should constantly endeavor to minimize our use of telescope time for testing!

7.1 Internal Testing - For the software engineer to fill out

This section covers things like unit testing, simulator testing, and any other tests required to make sure this MR is ready for sponsor/integration/regression testing.

7.2 Sponsor Testing - For the sponsor to fill out

This section is for the sponsor. What do you need to do in order to ensure that the MR is complete and correct? These tests are the prerequisite for sign off for the "accepted/delivered by sponsor" item in the "signatures" section.

7.3 Integration/Regression Tests - For the sponsor and/or software engineer to fill out

What do the integration/regression testers need to do in order to test this MR.


Signatures

APPROVED: To the best of my knowledge, the requirements section of this MR is complete and the other sections contain a reasonable plan forward. I have thought through this request, and believe it to be an important feature to implement or bug to fix.

ACCEPTED: I acknowledge that I have validated the completed code according to the acceptance tests.

Written symbol - name - date
Checked symbol - name - date
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 ALERT!)
  • Use %Y% if MR is complete (will display DONE)


CCC Discussion Area

Topic revision: r1 - 2011-05-12, JohnFord
 

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