Thursday, 9 am MT, 11 am ET, 28 September 2017


CV-331/AOC-152/GB-bsm, 331 Hub Audio 434-817-6286


  • 17B
    • VLA/17B-397/VLBA/17B-400 (Lewis, Dana)
  • 18A
  • 18B
    • PST Software Requirements (All)
  • AOB


Attending: DanaBalser, JaredCrossley, LewisBall, GarethHunt, BarryClark, MarkClaussen, AmyMioduszewski, RickLively, LorantSjouwerman


  • 17B
    • VLA/17B-397/VLBA/17B-400. These proposals were on embargo and yet the title/abstract were made public. We discussed the various ways this information is made public. (1) When a DDT is scheduled the scheduler (ToneyMinter [GBT], MarkClaussen [VLBA], and AmyMioduszewski[VLA]) will run a script to flip the public bit in the PST and then the PFT will display the title and abstract. (2) For the VLA/VLBA there is a DDT web page that is populated by MarkClaussen (VLBA) and HeidiMedlin (VLA). (3) For the GBT the title and abstract are made visible on the DSS page as well as via Twitter. BarryClark suggested that we just use the PFT; that is, one place. LewisBall will have discussions about our policy in this matter and how to proceed in the future.
  • 18A
    • SRP
      • Telecons. AmyMioduszewski reported that it took a while (4 days) to get feedback on a technical review due to folks traveling. MarkClaussen reported that the ISM SRP wanted to have previous reviews from re-submitted proposals available. (Currently they are available upon request.)
      • ETP. Two major issues with the ETP SRP. (1) One reviewer reversed scores and required some effort from GarethHunt and RickLively to fix. (2) One reviewer was able to enter an invalid score which skewed the normalization and therefore the ranks for some proposals. JIRA tickets have been entered to check the PST software and add better trapping of such problems in the future.
      • Linearize SRP Scores. DanaBalser reported that the SRP scores have been linearized. We are still waiting for some reviews to be finalized (text only) but this will not happen until next week. For the VLA/VLBA the disposition letters generate text from the PST database so this should not be a problem. The GBT disposition letters, however, use the GB PHT and thus everything needs to be finalized first.
    • TAC
      • PHT. RickLively will release several items that are currently on webtest to production. He will fix the one issue with Chandra time in the tables. There are a few tickets concerning disposition letters that he may get to later.
      • Large Proposal Telecon. There are only 4 Large proposals (2 GBT, 1 VLA, and 1 VLBA). The TAC info will not be ready in time to discuss the GBT proposals so that leaves 2. It was therefore decided to recommend to the TAC chair to cancel the Large Proposal Telecon and discuss the Large proposals with the other proposals during the face-to-face meeting.
      • Face-to-Face Meeting
        • Agenda: (Dana)
        • Logistics. JessicaUtley reported that all but one TAC member will be attending in person. The travel logistics are almost done.
        • Technical. We need to setup the room to handle one remote TAC member and several NRAO remote people. We also need to test the connection for one TAC member to attend the ALMA polarization meeting remotely.
  • 18B
    • PST Software Requirements. RickLively will organize tickets under an 18A filter.
      • GBT. One known item to remove "shared risk" from VEGAS. DanaBalser will add a JIRA ticket.
      • VLBA. Probably no major items. MarkClaussen will collect any items in the next week and create a JIRA ticket.
      • VLA. A few items. LorantSjouwerman has already added these to JIRA.
      • ETC. MarkClaussen will review current tickets and prioritize.
      • VLA sub-arrays. There was some discussion about VLA sub-arrays and whether this should be under Sessions. A while back we decided to remove it from Sessions. MarkClaussen will check that the documentation gives the correct advice (create one Session for different sub-arrays).

-- DanaBalser - 2017-09-26
Topic revision: r3 - 2017-09-28, 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