...
OSD - Observation Specification Disposition
PPR Proposal Process
To determine what time is available for the new proposals, I first have to build an Available Time Model (ATM). The ATM needs to know about pre-commited time from previous approved proposals (e.g., multi-semester, monitoring), sponsored time, maintenance periods, tests, and then also carry-over from the previous semester. I want to be able to import files to specify this information, inspect the imported information, and modify it on the fly as I need. The ATM also depends on the weather and the hardware sometimes (e.g., VLA configuration).
...
Once I am satisfied assigning scheduling priorities and providing comments for the TAC, I need to generate some reports for the TAC. I need both a summary of the ATM and the OSDs for my facility as well as an overview of the proposals/OSDs. I want these in different formats and I will both want a way to interact with the information associated with the Proposals in an efficient way when I'm at the TAC. I will likely do a lot of filtering by different proposal/OSD attributes. I also will want a way to generate a printed view of these summaries/reports because the TAC likes to look at pdfs toowant to export a Preliminary Facility Report based on a specified version of the ATM+OSDs. A Preliminary Facility Report includes the pressure plots for my facility and a csv with the data (TBD). I will take this data and the pressure plots and externally generate a pdf that is the Facility Report. Eventually, I will want to upload materials for the TAC to use during their discussions. For my facility, I want to upload the Facility Report (pdf) and a presentation (pdf). These documents should accessible through the TAC interface and their access is restricted to the TAC and TTA members. I may need to upload a different copy later, so I will want to replace (without versioning) the uploaded files.
For my proposals requesting my facility, I want to generate a Facility Proposal Summary, where the facility is VLA, VLBA, and GBT. This information should be generated into the TAC page so the TAC members can view it for their meeting. I may want to update the data in the Proposal Summary later for example, after the Large Proposal Meeting is finished.
Expand | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
|
Proposal Summary
A Proposal Summary is the primary way a TAC interacts with the proposals and the review process. It is likely an interface with specific details (see TAC meeting, the image linked under Facility Documents, summary.
OSR Proposal Process
As a TTA member for the OSR process, one or more of us will collaborate on reviewing a proposal. Typically for proposals in the OSR process, we don't modify the requests to the extent as in the PPR process: we either accept what they have proposed or decline it. It would be good to have the same tools to edit OSDs as the PPR process, but I won't define ATMs and build reports because this is just one proposal. I will have external information to understand the available time and if this proposal can be accommodated. After modifying OSDs, as a TTA member I perform the Science and Feasibility reviews as well as form the recommendations for Proprietary Time, Approved Time, Scheduling Constraints, and Scheduling Priorities. I need to modify these attributes and provide OSC Comments to the PI and Internal Comments for the OSC in case I want to capture any specific comments for the Director's Delegate's review or the PI. Once I have made my recommendations, I want to finalize and generator the . The report for the Director's Delegate's review is technically not part of the OSR. In practice there is no real report that is produced.
Expand | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...