PST Postmortem. There were about 50 PST helpdesk tickets and a similar number of account tickets (see the table below). The two main problems from previous semesters were mostly solved. One was the calendar code that defines the various deadlines that is used to assign the proposal id. The only glitch is that the code that is used in the dashboard was still using the old code and produced an erroneous date. There is a temporary fix for now. The other was the code that generates the pdfs that caused a lot of printing problems and memory leaks. There were no reported server problems until after the deadline. There still exists some old code (jasper), however, and the plan is to replace this soon if possible. Several issues that were discussed:
Uploading Files. There is still a problem with Safari. This is a known problem but has yet to be fixed. Zero length files will be uploaded and cause printing problems. It appears that Chrome is having more problems than in the past. A perfectly fine thesis plan pdf was uploaded and caused problems when printing. Uploading with Firefox worked fine. It was noted that we have 8 year old code to render java (spring framework) that would be difficult to replace soon; however, this is not the problem with Safari. It was suggested that we make the Dashboard message more visible (construction icon, blinking) or a popup if you login using anything but Firefox.
Sources. There was one proposal with a source list of about 19,000. This was difficult to upload since the server would time out but the process would continue. In the end the user provided us with the list via the helpdesk. A discussion about source conflicts ensued. Currently the GBT check for conflicts for all sources using position and frequency. The VLA/VLBA uses only position and has a cutoff for the number of sources. We should revisit this policy.
DDT/Sponsored Proposals. We received several DDT and sponsored proposals during the deadline week. The sponsored proposals were all SHAO (one mistaken Other). These should be submitted later and this was due poor communication with SHAO (language, culture, etc.). Several DDT were not time sensitive and it was discussed whether we should update our policy for DDT. For example, we should not consider DDT that are exploratory during the two weeks before a deadline.
PST Review Issues.
Printing problems. The printing load is high during the review process since reviewers will attempt to print all of the proposals. So the problems listed above are magnified. The large source lists can be a real problem as well.
Flag issues. As in the past the review system has lots of flags in the database that sometimes get set improperly. The problem is hard to track down but easy to fix.
Conflicts. There are lots of conflicts for some reviewers. We decided to replace one reviewer who was conflicted on 2/3 of the proposals. This is in part due to larger collaborations and we have included some NRAO personnel.
Technical/Science Reviewer. We had once case of a person who was both a science and technical reviewer. This is not accommodated in the PST so we will handle the technical reviews manually.
PHT. No action on these item yet.
SRP Telecons. JessicaUtley reported that the dates are now being negotiated. The EGS panel may need to use the week before the proposed two week span since there is a meeting during the first telecon week and the second week is full for one reviewer. Since there are only 26 proposals we may be able to schedule just one meeting for the second week. MarkClaussen and DavidFrayer volunteered to help DanaBalser monitor the telecons. JessicaUtley will run most of the meetings but will solicit help if necessary.