TTA Tools: Wednesday, 2 pm MT, 4 pm ET, 28 November 2018


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


  • Previous Action Items
    1. MarkClaussen, AmyMioduszewski, and LorantSjouwerman will try to determine if there is a set of parameters that can capture the different cases of multiple VLBA correlations.
    2. LorantSjouwerman will think about more detailed requirements using the intent to specify the VLA configuration(s).
    3. LorantSjouwerman will send around the document on setting up the VLA correlator. DONE.
    4. DanaBalser will update the requirements document. DONE.
  • Resource Specification
    • VLA Configurations
    • VLA Widar
    • GBT
  • AOB


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

  • Resource Specification
    • VLA Configurations. LorantSjouwerman did not get a chance to think about a better method but will do so in the next week.
    • VLA Widar. We discussed the proposal from LorantSjouwerman on how to configure Widar. The main difference compared to how the OPT currently works is to create the setup in the time independent Barrycentric frame first and then apply the Doppler corrections at validation for a given time. Here are the steps:
      1. Lines: specify rest frequencies
      2. Line Placement: create Barycentric line subbands. Software will determine the observing band, suggest 3-bit or 8-bit, and place the sub-bands. The user can override these values.
      3. Sub-bands: modify sub-bands and add continuum.
      4. Doppler: specify Doppler position.
      5. Doppler: Doppler switch.
      6. Basics: choose integration time (guess from configuration/band).
      7. Validation
    • VLBA. Could the same approach used for the VLA Widar correlator be used for the VLBA correlator? MarkClaussen is skeptical that this would be easy to do. AmyMioduszewski thinks this is doable but the constraints would have to be worked out. For example, there are constraints with the LO as well as other components. This is currently not done in the PST but Sched does check this and appears to be reliable. Currently, VLBA users typically read the documentation to figure out if what they are proposing is plaussible and then find out when using Sched.
    • GBT. Could the same approach used for the VLA Widar correlator be used for the VLBA VEGAS correlator? RyanLynch thinks this could be done. We might also consider how mapping would be specified. The user input necessary to specify a map is not too different than for a VLA mosaic. A field position and a field of view. There was some concern about allowing the software to suggest how best to produce the map (e.g., pointed versus OTF); a better approach might be to give the user options to select. ToneyMinter noted that there are often private backends (e.g, FLAG). But the GBT is not in scope for SRDPs, though it should not be ruled out, and therefore we can provide a textbox if necessary for the user to specify any details (as we do now).
  • Overview. We agreed that we really do not need both a novice and an expert mode. That is, the proposal above should work for both. At each step the user is allowed to override the decisions. We also agreed that the best approach would be to have only high level validation at each step (e.g., this field requires a decimal), and that once the steps were completed that a low level validation would be performed to make sure the configuration was possible. We agreed that the detailed requirements that provides the algorithm to configure the correlator would be in another document.
  • Action Items:
    1. LorantSjouwerman will think about more detailed requirements using the intent to specify the VLA configuration(s).
    2. DanaBalser will update the document by Monday (3 December) so people can read this before the next meeting.

-- DanaBalser - 2018-11-26

This topic: Software > TelescopeTimeAllocation > TTANewTools > TTAToolsMinute28Nov2018
Topic revision: 2018-11-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