You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Detailed TTA Tools Sprint Feedback Page

JSON files for Solicitations, field sources, and spectral spec generation available on git repository

Summary of Available Solicitations, Facilities, and Capabilities


Completed Last: Sprint 30


Solicitations for review

SolicitationCurrent Test Solicitation?
test solicitationno; retired Sprint ??
a realistic-looking solicitationyes since Sprint ??
Solicitation Specific Facility/Capability for testing


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







Solicitation Creation


DescriptionJIRAImplementedLast WorkingTestedStatus

Create Solicitation from JSON for

  • VLA
  • GBT

not implemented/requirements not in a story:

  • modify parameters such as frequency ranges on bands

STT-342 - Getting issue details... STATUS

Solicitation Config Files


Sprint 16Sprint 16Sprint 30 - ahc
  • (ahc) System hangs



Proposal Navigation



DescriptionJIRAImplementedLast WorkingTestedStatus

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

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

<Sprint 29<Sprint 29Sprint 29
  • (ahc) Does not seem to display correctly

Create Proposal



Capability (General)

DescriptionJIRAImplementedLast WorkingTestedStatus
Superset of UI elements for field sources

  STT-706 - Getting issue details... STATUS

Sprint 30
Sprint 30 - ahc
  • (ahc)There is a superset of elements for Field Sources but their behavior diverges between the capabilities. Notably, the fields reset themselves in the VLA and do not in the GBT
Modifying the TOM affects the Science Target List and the OS generation

STT-658 - Getting issue details... STATUS

Sprint 30
Sprint 30 - ahc
  • (ahc)Sometimes this is true. Sometimes it is not true. The behavior is the same in real VLA and GBT Capabilities. Sources are being dropping from the TOM → STL.
Simple partitioning, calibration strategy, and capability specific slew time and requested time calculations
Sprint 30
Sprint 30 - ahc
  • (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.

As a Product Owner, I would like the STL to contain 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

STT-707 - Getting issue details... STATUS





VLA Capability


DescriptionJIRAImplementedLast WorkingTestedStatus






DescriptionJIRAImplementedLast WorkingTestedStatus
See and Modify TOM
<Sprint 29


DescriptionJIRAImplementedLast WorkingTestedStatus








DescriptionJIRAImplementedLast WorkingTestedStatus






GBT Capability

DescriptionJIRAImplementedLast WorkingTestedStatus
As an Author, I would like to delete Field Sources and Spectral Specs in a Capability Request.

STT-708 - Getting issue details... STATUS

Sprint 30
Sprint 30 - ahc
  • (ahc) Works
DescriptionJIRAImplementedLast WorkingTestedStatus
Display and Modify TOM

STT-693 - Getting issue details... STATUS







DescriptionJIRAImplementedLast WorkingTestedStatus








DescriptionJIRAImplementedLast WorkingTestedStatus
See a Minimal OS

STT-699 - Getting issue details... STATUS

Sprint 30
Sprint 30 - ahc
  • (ahc) works
  • No labels