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

Compare with Current View Page History

« Previous Version 68 Next »

Updated 9.12.22 for v37.3

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 37


Solicitations for review

SolicitationCurrent Test Solicitation?Notes
test solicitationno; retired Sprint ??
a realistic-looking solicitationSprint 37

VLA: 4, P, L, S, C, X, Ku, K, Ka, Q

GBT: 4, P, L, S, C, X, Ku, K, Ka, Q (even if some are nonsensical for the GBT)

20DSprint 37

Specific Hardware Constraints:

GBT: P- and K-band (400 MHz, 22 GHz)

VLA: Ka- and L-band (33 GHz, 1.5 GHz)

Note: The Solicitation Json lists the basebands that are included in the solicitation.

Solicitation Specific Facility/Capability for testing


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




Helpful Files for Testing


FileUpdatedIntended CapabilityDescription

GBTmegamaser_FS_50.csv

Sprint 32GBT Spectral Line50 Field Sources from the Megamaser use case; the use case specifics a  rms line sensitivity of 6 mJy

GBTmegamaser_SS_1.csv

Sprint 32GBT Spectral Line1 Spectral Spec from Megamaser use case; Units are GHz, km/s, km/s

GBTSpectralLine_SS_2.csv

Sprint 32GBT Spectral Line

General GBT Spectral Line SS.

There are 2 SS in this file: KFPA and Q band

VLACont_polarization_FS_2.csv

Sprint 32VLA Continuum2 Field Sources from the polarization/continuum use case (W4); use case specifies a rms sensitivity of 100 microJy/bm. RA DEC in hms/dms.

VLAContinuum_SS_2.csv

Sprint 32VLA Continuum2 SS (C-, X-band); Units in GHz, GHz, GHz


Landing Page

DescriptionJIRAImplementedLast WorkingTestedStatus
  • Message of the Day on landing page

STT-754 - Getting issue details... STATUS


Sprint 34Sprint 37Sprint 37

WORKING

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

STT-342 - Getting issue details... STATUS

Solicitation Config Files


Sprint 16Sprint 16Sprint 30

HACK FOR RELEASE

Configure Field Source, SS, PP, CP





NOT IMPLEMENTED

Configure Advance Tab options





NOT IMPLEMENTED

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




NOT IMPLEMENTED
Solicitation Tab

Sprint 37.3Sprint 37.3

Only available to TTA Member



Navigation


DescriptionJIRA/BehaviorImplementedLast WorkingTestedStatus

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

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

<Sprint 29Sprint 37Sprint 37

WORKING

Saving within a CR

Capability Requests have their own save button. Though information looks like it is kept on the frontend, it is not in the backend without hitting save.

  • Change CR1 → don't save → navigate to CR2, change CR2 → save
    • Only changes to CR2 are kept
    • CR1 changes are not saved
  • Change CR1 → don't save → navigate to CR2, change CR2 → don't save → navigate to CR2 (changes are still present in front end) → save
    • Changes to CR1 are persisted
    • Changes to CR2 are not persisted
  • A refresh without hitting save does not persist work



  • steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment.
Saving and ARPersisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.



Observation Specification Generation

Popup warns user is overwriting their OS.

Pops up even if no OS is currently generated or if one cannot be generated (validation needed?)

If OS cannot be generated, tab is available but empty.




BUGS

Warning  "cannot generate OS"

  • OS exists for AR1 → add another AR→ immediately, warning appears
Navigate and Edit OS on fresh AR



Cannot Do

Create Proposal


Capability (General)

DescriptionJIRAImplementedLast WorkingTestedStatus
Scientific Justification

STT-935 - Getting issue details... STATUS

<Sprint 32Sprint 37.4Sprint 37.4

WORKING

Modify text (pdf file should be no more than 4 pages) or remove entirely

Persists, can upload, can delete, can replace, can view

General Allocation Request
<Sprint 32Sprint 37.4Sprint 37.4

Modify text or remove entirely

Can Select a Facility

Can add one or more AR

Can delete AR

General Capability Requests

STT-845 - Getting issue details... STATUS

< Sprint 32Sprint 37.4Sprint 37.4

WORKING

Can Delete

Can Add Multiples

Import Field Sources, Spectral Specs

STT-940 - Getting issue details... STATUS

STT-938 - Getting issue details... STATUS

STT-966 - Getting issue details... STATUS

Sprint 30Sprint 37.4Sprint 37.4

WORKING

Zeros import.

Widget matches well to headers

There are units on the headers at import

IGNORED

HMS DMS doesn't import 

Units not enforced on widget

Field Source and Spectral Specs

STT-939 - Getting issue details... STATUS

STT-937 - Getting issue details... STATUS STT-948 - Getting issue details... STATUS

STT-952 - Getting issue details... STATUS

< Sprint 30Sprint 37Sprint 37

WORKING

 Zeros persist

Negative Numbers work as expected

IGNORE FOR RELEASE

Units on fields

Precision


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

WORKING


Calibration Parameters

STT-942 - Getting issue details... STATUS

Sprint 32Sprint 37.4Sprint 37.4


WORKING


Performance Parameters

STT-941 - Getting issue details... STATUS

Sprint 32Sprint 37.4Sprint 37.4

WORKING


Advanced Tab


STT-949 - Getting issue details... STATUS

STT-941 - Getting issue details... STATUS


Sprint 36Sprint 37.4Sprint 37.3


WORKING

Filtering Works as expected

Import Works as expected; feedback on unsuccessful import is great!

Units exist on fields


ALMOST

Missing Angular Resolution for VLA

Need Units on Import Widget

  • Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and AS
    • Advanced tab and Performance parameters don't talk to each other? Unclear hierarchy and ownership between tabs
Science Target List

STT-951 - Getting issue details... STATUS

Sprint 32Sprint 37.3Sprint 37.3

HACK FOR RELEASE

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 30Sprint 37.3Sprint 37.4

HACK FOR RELEASE

working but not scientifically checked

BUGS

Cannot seem to affect the total time for VLA

Editing Observation Specification

STT-945 - Getting issue details... STATUS

< Sprint 30
Sprint 37.3


WORKING

Can add by target

Can add by Hardware (Simple)

Moving Scans works as expect

General Observation Specification


STT-943 - Getting issue details... STATUS

STT-946 - Getting issue details... STATUS

STT-952 - Getting issue details... STATUS

Sprint 32Sprint 32Sprint 37.3

WORKING

Times in tabs and summary are reporting consistently

Filtering works

IGNORE FOR RELEASE

Precision on entries

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

WORKING





Display Precision

  • Coordinate Units:
    • GMVA can have 1e-5 arcsecond precision astrometry. For degrees, this looks like 1e-9 deg
    • R.A. (J2000): 24.422080962 deg   Dec. (J2000): +33.159759164 deg  with precision to the 9th decimal place.
    • R.A. (J2000): 01:37:41.29966 Dec. (J2000): +33:09:35.08039 with a precision to the 5th decimal place.
  • Parallax  has a precision of 1e-5 milli arcsecond
  • Proper motions have a precision of 1e-5 milli arcsecond/yr
  • Radial Velocity has a precision of 1e-3 km/s
  • Flux Density units (peak or rms) have a precision of 1e-7
  • Line widths have a precision of 1e-5 km/s
  • Frequency (bandwidth, spectral resolution) has a precision of 1e-5 GHz or 1e-5 km/s
  • Angles (angular resolution, largest angular scale) 1e-5 arcsec













  • No labels