Versions Compared

Old Version 48

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 49

changes.mady.by.user Allison Costa

Saved on

Key

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

...

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
titleunknown

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




Solicitation Tab


Sprint 37.3

Only available to TTA Member



Proposal Navigation

...


DescriptionJIRAImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37


...

Sprint 37green< Greenkey

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

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

<Sprint 32Sprint 37.3Sprint 37.3

Can Delete Allocation Request; Capability Request; FS,

Can Rename AR,CR,FS, etc

Cannot Copy AR

< Sprint 32Sprint 32Sprint 32

Status
subtletrue
colourGreen
colorRedgreen
titlestatus

Modify text: pdf file should be no more than 4 pages.

Can Delete Allocation Request; Capability Request; FS,

Can Rename AR,CR,FS, etc

Cannot Copy AR

Jira
Cannot delete CR false
Jira
showSummary
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-846

Can Import Field Sources, Spectral Specs with CSVSprint 30Sprint 37

845

< Sprint 32Sprint 32Sprint 32

Status
subtletrue
colourRed

color

titlestatus

Cannot delete CR 

Can Import Field Sources, Spectral Specs with CSVZeros import.

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-940
HMS DMS doesn't import 

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-938
Entries in FS, SS, etc persist on saveSprint 30Sprint 37Sprint 37

Status
subtletrue
colour

Red
colorgreen
titlestatus

Zeros import.


HMS DMS doesn't import 

Entries in FS, SS, etc persist on save Zeros persist

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-

937

Negative Numbers work as expected

939

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-937
< Sprint 30Sprint 37Sprint 37

Status
subtletrue
colourGreen
colorgreen
titlestatus

 Zeros persist

Negative Numbers work as expected939



Selection of Calibration Parameters affects STL and OS
Sprint 32Sprint 32Sprint 32



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

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

Sprint 32Sprint 36Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Calibration parameter tab has no buttons not in VLA Continuum

Polarization Calibration Button missing in GBT Spectral Line


Performance Parameters

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

Sprint 32Sprint 36Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Angular Resolution missing from Performance Parameters and Advance Tab in VLA Continuum 

Advanced Tab



Sprint 36
Sprint 37.3

Status
subtletrue
colourRed
colorgreen
titlestatus

Filtering Works as expected

Import Works as expected

Missing Angular Resolution for VLA

Science Target List

Jira
showSummarytruefalse
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-693951

Sprint 32Sprint 30Sprint 3037.3Sprint 37.3

Status
subtletrue
colourYellow
colorgreen
titlestatus

Removed from all tabs as it should only accessible to Product Owners and that role hasn't been configured

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
STT-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 3237.3

Status
subtletrue
colourRed
colorgreen
titleworking

Times in tabs and summer are reporting consistently

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

Status
subtletrue
colorgreen
titleworking

...