Page History

We added isProposerModified and isRequestedFiller in previous sprints (90) to OSDs and had the FE hooked up too but we had no way to set these fields because they can't be set in OSs. We modified the simulation suite to randomly set 20% of the OSDs generated to having either field as True. Otherwise, they are False.

Can't test this from FE yet  but should allow us to restore 1 AD to an AR.

To get a computed facility configuration, we needed the SubScans to have real Hardware Configurations, where a Hardware Configuration as a FE, BE, and Facility Configuration. This ticket gives Subscans Hardware Configurations. A different story (STT-2178) refactors hardware configs on OSs and OSDs, as they also have a property but it really should be computed off the subscans.

The except is the Allocated Hardware Configuration - this is not computed.

We added Not Prioritized to the Scheduling Priorities in Sprint 91 but it should show up on the Pressure Plot too

in Sprint 90, we added a lockout to OSD's scheduling priorities to prevent the prioritizor from changing the entry. this is the FE work to show the lockout 11.26.24 - works and priorization works.

in Sprint 90, we added needs_manual_generation flag to OSDs. this is FE work to show it. We still need to trigger it though, which is STT-2166

BE work

BE work for STT-2170 - big lift

Was actually done in sprint 90

11.7.24

11.7.24

BE work only

FE work to refactor FE model of Scans, as right now it is pulling them from OSs instead of OSDs. It should set the work to be able to interact with OSD better.

Show calculated OSD properties of total duration, duration per repeat count, total science target integration times and time on observing targets

This is a BE story only....

I expect to be able to modify OSD's Approved Time, Facility Configuration, Allocated Earliest/Latest Start/End Time and Allocated Earliest/Latest Date.

BE story for conflicts

I expect to see mark an AST as conflict and see visual confirmation of the conflict status per AST and on its host AD

BE story for "is allowed position disposition"

FE story to show badge and interact with "is allowed position disposition"

I expect to be able to see some visual indicator of "is allowed position disposition" and to toggle this on and off per AST

There isn't a way to show this yet

Want a computed facility configuration based on the scan list

Doesn't hit pressure plot yet. Prioritizer changes NP to N right now.

BE story for calculated properties (e.g.,total time)

Pushing to next sprint

BE work

OSDs should now have Disposition Constraints; Some fields were modified from previous definitions.

Service and Test work for STT-1543 so the changes don't break everything

endpoint work for STT-1543

This, along with STT-2140, is making it so all ASTLs are generated from OSs.

• Subscans with intents = on_source; Scans with intents = observe_target → Allocated Science Targets
• Per OS, find all Source+HardwareConfiguration combos (from subscans) → make 1 unique Allocated Science Targets per combo
  
  • add up the Acquisition Time across subscans for combo. We will assume for now that the sum of the Acquisition Time is the Requested Time (it must by definition be >=)
  • Assign prototype Scheduling Strategy, Calibration Strategy, and Pointing Pattern to AST
  • If Source+HardwareConfiguration exists in another OS, it is a different AST because we assume the scheduling and calibration strategies were different.

In the Prioritization Tools, the scheduler may want to leave comments that describe their choices. Technically, the comments live on the AD because there is not versioned Proposal entity. We want the comments to be Proposal level though. We decided to do this under the hood. When a comment is saved, it is saved for all ADs in the Proposal+Facility. 

A separate story is needed to deliver the saved comments to the TAC UI.

When the scheduler runs the prioritizer, they may want to prevent changes to particular OSDs' Scheduling Priority. We will give them a lock out to specify this behavior. A separate story will make the prioritizer understand this lockout.

At some point in the Simulation work, we added additional fake bands to the definition of VLA bands so that we could simulate proposals easier. When doing this, the sensitivity calculator's SEFD wasn't simultaneously updated to handle the additional band names. We aren't sure why continued to work for some time and suddenly in 0.2.4 broke. Regardless, we have fixed it. On Prod < 0.2.5, just don't ask for K, Ka, or Q band observations.

This is additional work identified in STT-2052. It is fixing how we calculate the Requested Time (sum of acquisition time) and commenting out the conditional "is_user_modified" → forcing all ASTLs to be generated from the OSs.

is proposer modified is on OSD

requires manual generation on OSD

Can't test this yet because the FE isn't hooked up but the algorithm at least should respect

Design Story for big data

Design Story Allocated Science Target List

Design log functionality

BE

FE Prototype

Simulation Suite for Publishing 10.22.24

domain model for Allocated Science Target List 

improve AV history log

closing breadcrumb trail should not close ATMV panel

atm panel primary

inactive save and delete buttons when read only

static order on time reservation list

new atm should be selected when created

I expect to be able to publish an AV if it is read only and not currently published to a place. 9.27.24

FS and SS should appear after an import. It currently needs a hard refresh to show them 9.26.24

ATMs should keep their Facility Configs unless actually modified by the user. 9.27.24 still see this

Also hardrefresh is back on Pressure Plots after configuring an ATM

This was done in Sprint 87 after other changes.

Entering Time Ranges and Duration in Time Reservations needs the Time Bins code brought to the FE. i think this works not. 9.27.24

Publishing and Prioritizing an AV should not depend on the read only state of the ATMV 10.1.24

If AVs and ATMVs are in the side by side panel view, a change to the OSD's SP should push a change to the pressure plot to have active feedback. 9.27.24

9.26.24 - badge appears without a refresh on publication

badge needs a refresh after cloning still

done. 9.27.24

9.26.24 - fixed - publishing an AV with an ATMV sets the ATMV to read only and the badge appears

Cloning an ATMV sets it to read only and the badge appears without a refresh

9.26.24 - publication destination names updated in PTools

9.26.24 - publication destination names in resources tab's names updated

9.27.24

9.27.24

9.27.24

9.27.24

9.26.24 - fixed. The save and delete buttons are hidden if the ATMV is read only

9.27.24

9.27.24

9.27.24 - Not a fan of where the Time Reservation tooltip is. See STT-2106

Upload a Time Reservation and Facility config should be persisted. 9.27.24

make the UI cleaner when no ATMs exist on an ATMV.

9.30.24 If no ATM exists, UI goes immediately into making an ATM

got fixed else where along the way.

10.1.24

10.1.24 apparently was fixed along with 2054 though we're not sure how

10.2.24

10.2.24

10.2.24

10.2.24

10.2.24

10.3.24

10.3.24

10.4.24

10.4.24 - something isn't quite right but I'll wait for Jen's merge for STT-2090 to hit

10.8.24 I think

10.4.24 FPO bits but that's okay

10.8.24 done

I expect to see Time Reservation and OSDs on pressure plots when this is done. The labels should be dynamically populated on the pressure plot. I should be able to see the plot without selecting an AV (i.e.,g no OSDs). Facility Configurations are respected by OSDs and Time Reservations; dates are not longer enforced for Time Reservations either.

I should be able to make changes to the scheduling priority for OSDs and that show up on the Pressure plot. 9.16.24 yes but there are remaining hardcoded labels

Time Reservation UI should be more informative for a general user. 9.18.24 - mostly done but the duration validation doesn't wrap around 24. I cannot reproduce the wrap around issue now. I think it is fixed.

I expect not to be able to save an ATM without specifying a Facility Configuration if applicable and the default should be Any. 9.16.24 I don't see this

9.18.24 The default is any and there is no way to not select something.

FE should disable fields in ATMV if it is read only. separate ticket for disabling save and delete button

There should be feedback in the simulation suite for successful uses of the simulate allocate and approval buttons.