Versions Compared

Old Version 3

changes.mady.by.user Allison Costa

Saved on

compared with

New Version Current

changes.mady.by.user Allison Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Goals of Closeout

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-148

...

Goals of Project Creation

v0.4 Design VLA Project Creation

Project CreationUtilityVLA Hand OffGBT Hand OffDeferred
  • Create empty project for a proposal
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-140
  • View a Project associated with a Proposal
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-143



  • Track success of project creation
    • Jira
      serverDMS JIRA
      columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
      keySTT-142




PI read-only view to prior to handoff?


Project Data Model


ELVATTAT

Project

  • one to one with a Proposal (per Facility)


Program Block(s)

  • one or many per project
I think one is made per Allocation Disposition? Maybe that's not true. Need definition around PB

Scheduling Block(s)

  • one or many per Program Block
These are like our Observation Specification Dispositions

Scan List

  • 1 per SB
Same as ours

Scan(s)

  • one or many per Scan List
Same

Subscan(s)

  • one or many per Scan
Same

Source


TTAT SourceEVLA Source
Current Definition
  • Name
  • Nominal Position
  • Pointing Patterns
    • (These are VLA pointing patterns) 
    • Type: Single, Discrete, OTF
    • Single (is the case of 1 for Discrete really)
      • Position
      • Requested Time
    • Discrete:
      • Position per pointing
      • Requested time per pointing
      • number of pointings
    • OTF:
      • time per row
      • Position of first pointing in row
      • position of last pointing in row
      • number of rows

Notes

A Source is on one or more Allocated Science Targets and one or more SubScans. Note, if the Allocated Science Target is "is allowed positive disposition" then we would transform it for EVLA.


Attributes

Name

Need
Attributes

Nominal Position

Don't need
Attributes

Pointing Pattern Type

Don't need explicitly
Attributes

If single or discrete: Position per pointing

OTF: Position of first point in row/last point in row for each row

Need


Resource


TTAT Hardware ConfigurationEVLA Resource
Definition
  • Front End
    • Center Frequency
    • Bandwidth
    • Velocity Frame
  • Back End
  • Array Configuration (if applicable)



I think a Program Block is created per allocated Scheduling Priority?

We likely must decide what "Any" Array Configurations means


Project


TTAT ProjectEVLA Project


  • Project Code
  • Title (Proposal Title)
  • Telescope
  • Proposal Code (ID?)
  • Test Project?
  • Type
  • Allocated Time
  • Time Used
  • PIs and CoI

Program Block


TTAT AD → Program BlockEVLA Program Block


  • Name
  • Scheduling Priority
  • Allocated Time
  • Used Time
  • Completed?
  • Acceptable Configurations
  • Linked SBs (N/A for us)

Scheduling Block


TTAT OSD → SBEVLA SB

  • allocated cadence, repeat count, cadence tolerance
  • allocated earliest start time
  • allocated latest end time
  • allocated earliest start date
  • allocated latest end date
  • Scheduling Priority
  • allocated duration per repeat count
  • proprietary period
  • Generated ID
  • Name
  • Acceptable Configurations
  • Count
  • Completed
  • Total Time
  • Time per Execution
  • Schedule Type
  • LST Start Range
  • Earliest UT Start Date/Time
  • Latest UT Start Date/Time
  • Avoid Sunrise
  • Avoid Sunset
  • Max Wind Speed
  • Max API
  • Comments (to scheduler from PI)



TTAT Scan ListEVLA Scan List

this is a list of Scansthis is a list of Scans

Scan


TTAT ScanEVLA Scan

  • a group of one or more subscans
  • Scan Intent(s)
  • subscans are under the hood for EVLA?
  • Name
  • Scan Mode
  • Target Source
  • Hardware Setup
  • Scan Timining
  • Intents
  • Antenna Wrap
  • Reference Pointing
  • ....

SubScan


TTAT SubscanEVLA Scan

  • Source
  • Hardware Configuration
  • Acquisition Time
  • Setup Time
  • antenna trajectory (derived from Pointing Pattern)
  • Subscan Intent