TTA Tools: Wednesday, 2 pm MT, 4 pm ET, 17 October 2018


CV-331/GB-137/SO-317, 331 Hub Audio 434-817-6286


  • Additional Use Cases
    • External Information (e.g., updated pulsar ephemeris)
    • Multiple Backends (e.g., multiple VLBA correlations)
    • Triggered
    • VLBA
  • AOB


Attending: DanaBalser, AnandCrossley, MarkClaussen, AmyMioduszewski, LorantSjouwerman

  • Additional Use Cases
    • External Information (e.g., updated pulsar ephemeris). We should add a new Allocation Request parameter called "External Dependencies". At a minimum we should have a check box that specifies if there are external dependencies and, if so, a text box to fill in the details. It would be very useful to capture more detailed information. That is, what information is being updated. This parameter should be set for target of opportunity proposals where the position is not know a priori.
    • Multiple Backends (e.g., multiple VLBA correlations). This comes in two flavors. (1) multiple back-ends. Here we need to specify one or more Allocation Requests depending on the details. For example, if we had HSA observations with Y1 and simultaneous observations with the VLA this would be two Allocation Requests. In contrast, if we had HSA observations with Y27 and wanted additional resources with the VLA (e.g., use DiFX and WIDAR) then this would be one Allocation Request. (2) Multiple correlations. This often occurs with the VLBA where they want to observe multiple fields and therefore multiple passes with the correlator. Currently, we capture the number of fields but not the details (e.g., phase centers). MarkClaussen, AmyMioduszewski, and LorantSjouwerman will try to determine if there is a set of parameters that can capture most cases.
    • Triggered. We discussed use case 4.2.5 (triggered VLA proposal). Currently, we capture the following information for a Triggered proposal (see below). This seems to be sufficient. The only issues now are dealing with quick response times. We agreed that (1-3) should be captured by the Allocation Type if Triggered is specified, and that (4-5) should be captured by the Allocation Constraints. That is, we put the constraints for all proposals in one place.
      1. Target type
      2. Origin of trigger
      3. Trigger event description
      4. Semester(s) and number of events
      5. Required response windows, with units
  • Action Items
  • Future Meetings
    • 24 October 2018: canceled due to TAC meeting.
    • 31 October 2018: start discussing (1) Resource specification (more details); (2) SRPD specification; and (3) Metrics.

-- DanaBalser - 2018-10-11
Topic revision: r2 - 2018-10-17, DanaBalser
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