You are viewing an old version of this page. View the current version .
Compare with Current
View Page History
« Previous
Version 90
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 38
Solicitations for review
Solicitation Current Test Solicitation? Notes test solicitation no; retired Sprint 37 a realistic-looking solicitation Sprint 37
Gone after Sprint 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)
20D Sprint 37
Gone after Sprint 37
Specific Hardware Constraints:
GBT: P- and K-band (400 MHz, 22 GHz)
VLA: Ka- and L-band (33 GHz, 1.5 GHz)
Sem_25A Sprint 38 VLA and GBT have L – Q band available
Production Solicitation for v0.1
SC_GBT_24B Sprint 38 GBT only, L, S, and C band
Production Solicitation for v0.1
Note: The Solicitation Json lists the basebands that are included in the solicitation.
Solicitation Specific Facility/Capability for testing
a realistic-looking solicitation Capability Facility VLA Continuum GBT Spectral Line real VLA Sprint ?? > -- GBT -- Sprint 28 > VLA (replaced real VLA) Sprint 37.2
Helpful Files for Testing
File Updated Intended Capability Description Sprint 38 GBT Spectral Line 50 Field Sources from the Megamaser use case; the use case specifics a rms line sensitivity of 6 mJy Sprint 38 GBT Spectral Line 1 Spectral Spec from Megamaser use case; Units are GHz, km/s, km/s (extra spectral spec but can delete) Sprint 38 GBT Spectral Line General GBT Spectral Line SS.
There are 2 SS in this file: KFPA and Q band
Sprint 38 VLA Continuum 2 Field Sources from the polarization/continuum use case (W4); use case specifies a rms sensitivity of 100 microJy/bm. RA DEC in hms/dms. Sprint 38 VLA Continuum 2 SS (C-, X-band); Units in GHz, GHz, GHz
Current Report Landing Page Description JIRA Implemented Last Working Tested Status Message of the Day on landing page
STT-754
-
Getting issue details...
STATUS
Sprint 34 Sprint 37 Sprint 37 WORKING
but! it would be nice if there was more feedback when the save successful.
Solicitation Creation Description JIRA Implemented Last Working Tested Status Create a Simple Solicitation from JSON for
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 16 Sprint 16 Sprint 30 Configure Field Source, SS, PP, CP Configure Advance Tab options Update/Test a solicitation when a different one is Open and has submitted proposals NOT IMPLEMENTED Solicitation Tab Sprint 37.3 Sprint 37.3 Only available to TTA Member
A Proposal Prefix can be specified per solicitation
STT-866
-
Getting issue details...
STATUS
Navigation
Description JIRA/Behavior Implemented Last Working Tested Status As an Author, I would like to view my proposals.
in a list in a detailed view (Card) <Sprint 29 Sprint 37 Sprint 37 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 → saveOnly 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) → saveChanges to CR1 are persisted Changes to CR2 are not persisted A refresh without hitting save does not persist work
STT-976
-
Getting issue details...
STATUS
steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment. REVIEW
Saving and AR Persisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.
STT-976
-
Getting issue details...
STATUS
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.
STT-972
-
Getting issue details...
STATUS
<Sprint 35 Sprint 38 Sprint 38 Navigate and Edit OS on fresh AR Not Implemented
IGNORED FOR RELEASE
Submission Description JIRA Implemented Last Working Tested Status Submit a Proposal Proposal ID and timestamp generated Light Validation on Submission
STT-850
-
Getting issue details...
STATUS
STT-860
-
Getting issue details...
STATUS
STT-851
-
Getting issue details...
STATUS
Sprint Sprint Sprint
Vet Proposals Description JIRA Implemented Last Working Tested Status Sprint Sprint Sprint
Review Configuration Description JIRA Implemented Last Working Tested Status Sprint Sprint Sprint
Create Proposal
Capability (General) Description JIRA Implemented Last Working Tested Status Scientific Justification
STT-935
-
Getting issue details...
STATUS
<Sprint 32 WORKING
Persists, can upload, can delete, can replace, can view
General Allocation Request <Sprint 32 Can Select a Facility
Can add one or more AR
Can delete AR
Can rename
General Capability Requests
STT-845
-
Getting issue details...
STATUS
< Sprint 32 WORKING
Can Delete
Can Add Multiples
Can Rename
Import Field Sources, Spectral Specs
STT-940
-
Getting issue details...
STATUS
STT-938
-
Getting issue details...
STATUS
STT-966
-
Getting issue details...
STATUS
Sprint 30 WORKING
Zeros import.
Widget matches columns to headers mostly as excepted (doesn't match units)
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
STT-1003
-
Getting issue details...
STATUS
STT-1023
-
Getting issue details...
STATUS
< Sprint 30 WORKING
Zeros persist in fields
Entries persists
BUG
Negative Values in Dec DMS entry do not display correctly
GBT missing field of view shape text entries and labels for non point source requests
IGNORE FOR RELEASE
Units on fields
Precision
Selection of Calibration Parameters affects STL and OS Sprint 32 Sprint 37.3 Sprint 37.3 Calibration Parameters
STT-942
-
Getting issue details...
STATUS
Sprint 32 WORKING
VLAPolarization calibration triggersPol Angle scan Leakage scan GBTPolarization calibration triggers Test Source triggers test source scan flux density triggers flux density scan Performance Parameters
STT-941
-
Getting issue details...
STATUS
Sprint 32 WORKING
VLAAngular Resolution - degree + LAS - degree + RMS - Jy/beam GBTAngular Resolution - degree + RMS - Jy/beam Advanced Tab
STT-949
-
Getting issue details...
STATUS
STT-941
-
Getting issue details...
STATUS
STT-975
-
Getting issue details...
STATUS
STT-973
-
Getting issue details...
STATUS
STT-992
-
Getting issue details...
STATUS
STT-993
-
Getting issue details...
STATUS
Sprint 36 WORKING
Filtering Works as expected
Units exist on fields
Angular Resolution is present for VLA
Import Widget has units
BUG
Import Works as expected; feedback on unsuccessful import (was) great! Now it thinks nothing works when only 1 thing is bad. STT-993
REVIEW Relationship and hierarchy on Advanced Tab + Performance Parameters
Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and ASbehavior is understood in ticket 992. Need more feedback but behavior acceptable. Science Target List
STT-951
-
Getting issue details...
STATUS
Sprint 32 Sprint 37.3 Sprint 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
STT-977
-
Getting issue details...
STATUS
Sprint 30 HACK FOR RELEASE
working but not scientifically checked
Editing Observation Specification
STT-945
-
Getting issue details...
STATUS
< Sprint 30 Sprint 37.4 Sprint 37.4 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
STT-1005
-
Getting issue details...
STATUS
Sprint 32 WORKING
Times in tabs and summary are reporting consistently
Filtering works
IGNORE FOR RELEASE
Precision on entries
BUG
GBT time calculation uses bandwidth instead of spectral resolution.
One or more Capability Requests in an Allocation Request can generate one or more Observation Specifications <Sprint 32
Version Reports version 0.1 report
Landing Page
Description JIRA Implemented Last Working Tested Status Message of the Day on landing page
STT-754
-
Getting issue details...
STATUS
Sprint 34 Sprint 37 Sprint 37 WORKING
but! it would be nice if there was more feedback when the save successful.
Solicitation Creation
Description JIRA Implemented Last Working Tested Status Create a Simple Solicitation from JSON for
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 16 Sprint 16 Sprint 30 Configure Field Source, SS, PP, CP Configure Advance Tab options Update/Test a solicitation when a different one is Open and has submitted proposals NOT IMPLEMENTED Solicitation Tab Sprint 37.3 Sprint 37.3 Only available to TTA Member
Navigation
Description JIRA/Behavior Implemented Last Working Tested Status As an Author, I would like to view my proposals.
in a list in a detailed view (Card) <Sprint 29 Sprint 37 Sprint 37 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 → saveOnly 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) → saveChanges to CR1 are persisted Changes to CR2 are not persisted A refresh without hitting save does not persist work
STT-976
-
Getting issue details...
STATUS
steep learning curve. Tendency to neurotically spam the save is justified but the warning about Observation Specifications is then the punishment. REVIEW
Saving and AR Persisting information between AR works the same as CR save. Navigating between ARs does not persist data unless the save button used.
STT-976
-
Getting issue details...
STATUS
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.
STT-972
-
Getting issue details...
STATUS
<Sprint 35 Sprint 37.5 Sprint 37.5 Navigate and Edit OS on fresh AR Not Implemented
IGNORED FOR RELEASE
Create Proposal
Capability (General) Description JIRA Implemented Last Working Tested Status Scientific Justification
STT-935
-
Getting issue details...
STATUS
<Sprint 32 Sprint 37.4 Sprint 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 32 Sprint 37.4 Sprint 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 32 Sprint 37.4 Sprint 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 30 Sprint 37.4 Sprint 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 30 Sprint 37 Sprint 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 32 Sprint 37.3 Sprint 37.3 Calibration Parameters
STT-942
-
Getting issue details...
STATUS
Sprint 32 Sprint 37.4 Sprint 37.4 Performance Parameters
STT-941
-
Getting issue details...
STATUS
Sprint 32 Sprint 37.4 Sprint 37.4 Advanced Tab
STT-949
-
Getting issue details...
STATUS
STT-941
-
Getting issue details...
STATUS
STT-975
-
Getting issue details...
STATUS
STT-973
-
Getting issue details...
STATUS
STT-992
-
Getting issue details...
STATUS
STT-993
-
Getting issue details...
STATUS
Sprint 36 Sprint 37.4 Sprint 37.5 WORKING
Filtering Works as expected
Units exist on fields
Angular Resolution is present for VLA
Import Widget has units
BUG
Import Works as expected; feedback on unsuccessful import (was) great! Now it thinks nothing works when only 1 thing is bad. STT-993
REVIEW Relationship and hierarchy on Advanced Tab + Performance Parameters
Add FS, SS → Advanced tab → upload LAS, RMS for all sources → Performance → specify LAS, RMS, and ASbehavior is understood in ticket 992. Need more feedback but behavior acceptable. Science Target List
STT-951
-
Getting issue details...
STATUS
Sprint 32 Sprint 37.3 Sprint 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
STT-977
-
Getting issue details...
STATUS
Sprint 30 Sprint 37.3 Sprint 37.4 HACK FOR RELEASE
working but not scientifically checked
Editing Observation Specification
STT-945
-
Getting issue details...
STATUS
< Sprint 30 Sprint 37.4 Sprint 37.4 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 32 Sprint 37.5 Sprint 37.5 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 32 Sprint 37.4 Sprint 37.4
Misc
Hidden For later
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