Versions Compared

Old Version 43

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 44

changes.mady.by.user Allison Costa

Saved on

Key

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

...

Section
Column


Solicitations for review

SolicitationCurrent Test Solicitation?
test solicitationno; retired Sprint ??
a realistic-looking solicitationretired Sprint 37
20DSprint 37yes since Sprint ??
Column
Solicitation Specific Facility/Capability for testing


a realistic-looking solicitationCapability
Facilityreal VLA ContinuumGBT Spectral Line
real VLASprint ?? >--
GBT--Sprint 28 >






...

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

Jira
showSummaryfalse
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-754


Sprint 34Sprint 37Sprint 37

Status
subtleTrue
colorgreen
titleworking

but! it would be nice if there was more feedback when the save successful.


Solicitation Creation

...

DescriptionJIRAImplementedLast WorkingTestedStatus

Create a Simple Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

Jira
showSummaryfalse
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-342

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

Status
subtleTrue
colourYellow
colorgreen
titleworkingunknown

Spectral Specs and Field Sources cannot be modified

Calibration Parameters; Performance Parameters coming soon.

Can specify what Capability Parameter Specifications are displayed per Solicitation Capability (Eventually, time capsule to past Solicitations)

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-614





Can set override flags for Target Override Matrix to allow Capability Parameter Specifications to be overridden

  • The correct overrides are shown in the TOM per Capability

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-739





Update/Test a solicitation when a different one is Open and has submitted proposals




...

DescriptionJIRAImplementedLast WorkingTestedStatus

As an Author, I would like to view my proposals.

  • in a list
  • in a detailed view (Card)

<Sprint 29Sprint 2937Sprint 2937


Create Proposal

...


Capability (General)

working
DescriptionJIRAImplementedLast WorkingTestedStatus

Can Delete Allocation Request; Capability Request; FS,

Can Rename AR,CR,FS, etc

Cannot Copy AR


< Sprint 32Sprint 32Sprint 32

Status
Working
subtletrue
colourGreenYellow
titleworking

Partially, can't seem to delete CR

Can Import Field Sources, Spectral Specs with CSV
Sprint 30Sprint 3037Sprint 3037

Status
subtletrue
colourYellow
colorgreen
titleworking

Entries with 0, 0.0 do not fill correctly into fields

Unit matching will be an issue.

Entries in FS, SS, etc persist on save
< Sprint 30Sprint 32*Sprint 3237Sprint 37

Status
subtletrue
colourYellow
colorgreen
titleworking

Except when 0 is entered for a value

*Front-end for VLA and GBT work similarly but the backend is different. GBT capabilities have an extended backend understanding of FS, SS, etc. VLA capabilities currently only store name and coord, for example, on a FS.

Selection of Calibration Parameters affects STL and OS
Sprint 32Sprint 32Sprint 32
Status
subtletrue
colorgreen
title



Modifying the TOM affects the Science Target List and the OS generation – Now is "Advanced" Tab and is part of the Capability Request

Jira
showSummaryfalse
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-658

Jira
showSummarytrue
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-693

Sprint 30
Sprint 30
  • (ahc) VLA: Sometimes this is true. Sometimes it is not true. The behavior is the same in real VLA and GBT Capabilities. Sources are being dropped from the TOM → STL.
    • (db) GBT: working

    Status
    subtletrue
    colourRed
    colorgreen
    titlebroken

    Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations
    		Sprint 30
    		Sprint 30
    • (ahc) the simple partitioning appears to be working, as well as the simple calibration strategy; The time calculation isn't displaying the information correctly in the GBT capability sometimes. I haven't tested the math behind the calculation.
    • (db) GBT: RMS and requested time calculation appears to be correct in Observation Specification but not in the Science Target List

    The STL contains the correct Source and Hardware Configuration name to reflect what is specified by the Capability Request + TOM

    • The Science Targets should have a Source name, which is specified by the Field Source
    • The Science Targets should have a Hardware Configuration name, which specified by the Spectral Spec

    Jira
    showSummaryfalse
    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-707




    Status
    subtletrue
    colourYellow
    titlenot implemented

    Edit a Observation Specification to add Scans/SubScans and can filter on an Obs Spec

    • Add Target
    • Cannot add HardwareConfiguartion

    		< Sprint 30Sprint 30

    Observation Specification has detailed and accurate information

    • e.g., Time on Observing Targets, Scan List, Overhead

    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-442

    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-617

    		Sprint 32Sprint 32Sprint 32

    Status
    subtletrue
    colorgreen
    titleworking

    One or more Capability Requests in an Allocation Request can generate one or more Observation Specifications
    		<Sprint 32Sprint 32Sprint 32

    Status
    subtletrue
    colorgreen
    titleworking

    ...