Versions Compared

Old Version 1

changes.mady.by.user Jeff Kern

Saved on

compared with

New Version 2

changes.mady.by.user Jeff Kern

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • Date:  
  • Time: 9:00 ET
  • Location: nraozoom04 

Next Meeting:  

Attendance:

    

Agenda:

  • Review reviewer rolls (closing the loop to make sure we have a common understanding) (Mark)
    • Reviewed rolls for reviewers.  Identified that there are two classes of reviewer (Feasibility and Scientific) and subclasses within.
    • Discussed if a SRP Chair is a type of SRP Member, decided to keep the role separate but recognize that most SRP Chairs are also Members.
  • Doodads:
    • Making
  •  Making sure we have common terms (see Dana’s suggestions below) and understanding of what was in the Doodad document so we can start putting it into the algorithm and conceptual architecture so we have a set of requirements for the team to go for a better implementation of the VLA Continuum and GBT use cases.
    • Agreed on general structure and approach.
    • Use name "Observing Instructions" in place of Doodad. 
  • Use of Dendrograms for grouping of phase calibrators and partitioning (Allie)
  • Definitions
    • Some suggested definitions from Dana (and of course my commentary):
  • Source.  This often means something in the sky that we want to observe.  It could be a calibrator or an astronomical object of interest.
  • Field.  Often used in interferometry to specify a region on the sky. Presumably since telescopes like the VLA produce images.  Otherwise this is similar to source.
  • Targets.  This sometimes means an astronomical object of interest.
Maybe we should just avoid these terms and use "Field Source" instead. The intent can then qualify the type of Field Source.
  • :
    • Agreed that the user facing object is a Field Source and it contains information both about the field of observation and the astronomical source.
    • Agreed that Rows in the TargetList are Targets
I’ve been thinking about this as well. ALMA uses FieldSource as the user facing spatial definition, so I was trying to stay connected to that.
    • Field Source: Specification of astronomical object we want to observe as well as the specification of the region we want to observe.
The
      • To Do: Clarify the relation between the Field Source
also contains a
      • and the Pointing Pattern
that specifies how the field will be achieved
      • .
    • Pointing Specification: Either a pointing center or in the case of a moving antenna, specification of the antenna motion.  This is what then belongs in the subscan as well as a reference to the FieldSource.


New Actions:

  •  Update the conceptual architecture with our better understood hierarchy of reviews. Mark Whitehead
  •  Check the system description of feasibility review especially in the case of the Observatory Site Review to ensure it is correct and consistent with the Conceptual Architecture (All)
  •  Integrate the "Doodad Doc" into the Algorithm Document, change to Observing Instructions Allison Costa
  •  Clarify communication path to SchedSoc Jeff Kern
  •  Clarify where the Pointing pattern is in relation to the Field Source 
  • Doodads --> Observing Instructions?
The Observation Planner uses the Calibration Strategy and the Scheduling Strategy to generate Observing Instructions.  Observing Instructions encapsulate the type of observing and answer two questions: (1) do I need to observe; and (2) how should I observe.I certainly like Observing Instructions better than Doodads and I like the way you formulated this above.

Open Actions:

Task report
pages68321335