- Date: //date
- Time: 9:00 ET
- Location: nraozoom04
Attendance:
Agenda:
- Sprint 32 Review
- I think it would be good to have a tool tip that has more detail about the scans. For example, we thought the OS was wrong because a calibrate flux scan had two on_source subscans. If it were a OnOFF OI, then we would have on_source/off_source. But this is a GBT Nod OI, where both subscans are on_source. You wouldn't be able to tell that though from the scan list. To have transparency in the scan list creation, because the user doesn't see the algorithm work, we need more information on the OS. That way, the user knows where to refer to in the algorithm document.
- The OS is, generally, as specified in
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-441 - GBT Peak OI has scan intent of calibrate_pointing whereas the Focus OI has calibrate_focus. It appears at first glance that the peak/ focus routine is missing but it is actually there.
- Added use case files to ttaReview page
Open Actions:
| Task report | ||
|---|---|---|
|