TTA Tools: Wednesday, 2 pm MT, 4 pm ET, 05 December 2018


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


  • Metrics Specification
  • AOB


Attending: DanaBalser, JeffKern, AnandCrossley, MarkClaussen, AmyMioduszewski, LorantSjouwerman, RyanLynch, ToneyMinter

  • Metrics Specification. We discussed the following metrics.
    1. Sponsored observing: hours spent per month on open skies and sponsored observing over past 13 months. Pie + bar charts and line chart. The observed hours will come from software downstream, but we need to know if the proposal is sponsored or not. We need to add the following to our requirements: proposal code, allocation request code, and a parameter that specifies if the allocation request is closed or not (i.e., the sponsor does not want to be public). There needs to be a link from the allocation request code to the software database that contains the hours observed.
    2. Proposals with NRAO PIs: Number of proposals per cycle with NRAO PIs, for deadline and DDT proposals. We need to add a parameter to mark the primary institute when there are more than one included.
    3. Proposals submitted per cycle, for deadline and DDT proposals. This is at the allocation request level and included in the allocation type. We need to use different nomenclature since cycle has different meanings for ALMA and VLA.
    4. Oversubscription rate (proposals received / proposals approved), for deadline and DDT proposals. Should be okay.
    5. Number of proposals in support of theses submitted and accepted. We need to be able to tie the proposal code to the allocation request (or project) code.
    6. Observing hours by PI: US, foreign, unspecified. Observing hours by PI: Graduate student, AUI Staff, Other Observing hours by PI: Country Observing hours by US PI: US State We need to add the following new parameters at the proposal level: affiliation and professional status (e.g., student). For the affiliation we need to accommodate null values.
    7. Observing hours by SRP. We need to track the proposal code to the software downstream to associate the science category with hours observed. So there needs to be a link between the proposal code and allocation request (project) code. For the VLBA we need a legacy code since the VLBA cannot handle large strings. We agreed that for now we should just generate a legacy code as is done in the PST.
  • Plan:
    1. DanaBalser will update the next draft of the document by Friday (7 December 2019).
    2. The committee will read the updated document and we will iterate at the next two meetings (12 and 19 December 2019).
    3. Complete the metrics discussion at the 19 December 2019 meeting.
    4. Complete the document by 31 December 2019.

-- DanaBalser - 2018-12-04
Topic revision: r2 - 2018-12-05, 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