...
There are some tasks that would be useful if they were automated, as it would take me too long to compile the data by hand. For example, I need to identify source conflicts based on a variety of criteria. I also want OSDs associated with external facilities to be handled differently than OSDs of internal facilities. Finally, I want to use algorithms to help efficiently assign scheduling priorities to OSDs as it may well enough for most cases. That frees up time for me to concentrate on the edge cases and optimization. It is important that I can control which OSDs are having their SPs modified, so I would like a way to "lock" out changes temporarily so neither the system nor a manual edit can be applied until it is unlocked.
| Expand |
|---|
|
As a scheduler I want to identify Source Conflicts in the OSDs so I can make a note of them for the TAC. | As a scheduler I want ADs/OSDs that request multi semester observations to be clearly identified in the UI so I can understand how they impact future semesters. | As a scheduler I want ADs that have external facilities to be automatically marked with N so they won't be accounted for in the scheduling. | As a scheduler I want the system to generate SPs for OSDs because the algorithm may do the majority of the cases sufficiently. | As a scheduler I want to be able to initiate process multiple times so I can iterate on the assigned SPs given a ATM. |
|
|
| As a scheduler I want OSDs with SPs of N to not be modified by the algorithm because these OSDs are rejected and will not be scheduled. |
|
|
|
| As a scheduler I want OSDs with SPs that are locked to not be modified by the algorithm so the SPs of those OSDs do not change. |
|
|
|
| As a scheduler I want OSDs with SPs of F to not be modified by the algorithm because these are fixed dates. |
|
|
|
| As a VLA scheduler I want the automated algorithm to be the Prioritizer. |
|
|
|
| As a scheduler I want to be able to modify a system generated SP because I know better. |
|
|
...
