PST Postmortem. There were 41 PST helpdesk tickets submitted from the CfPs until the deadline. We discussed the following issues. Items 1-6 were brought up by LorantSjouwerman and items 7-8 were brought up by RickLively.
GOST 128 MHz dual/1MHz selection bug: this is known and did not get fixed in the Legacy version. LorantSjouwerman will note this in the GOST documentation (maybe as part of the knowledgebase).
GBT warning about 4 vs 8 bbc's: this is a bogus message similar to the VLBA message that we fixed. MarkClaussen will write up a JIRA ticket; he thinks he knows the sequence.
Proposal print: problems printing a proposal caused by an odd character in the filename for the ECT file. When printing the proposal the software must access the ECT PDF from the database but chokes on the filename. This may be a result of a Japanese OS. We briefly discussed how to proceed. We could constrain the ECT to choose a specific filename, but this does not give the user flexibility. This only happened once and therefore may not be too painful. LorantSjouwerman will create a JIRA ticket to at least track this issue.
Timeout at submission: a user submitted a proposal multiple times since the server would timeout. This could be do to poor internet connection on the user side. This is not so easy to reproduce but LorantSjouwerman will check the proposal size (e.g., large source list or big SJ file).
VLA elevation warning confusion upon automatic LST calculation: this appears to be an issue with a combination of high and low declination sources. Since the LST calculation algorithm is not written down anywhere RickLively will send LorantSjouwerman the code. We could request more information from the user but an underlying issue is that PST Sessions do not really map to telescope observing sessions (or SBs). Once we understand the reason for the warning we might want to add this to the knowledgebase.
Withdrew proposal once but we see several emails: this came from ToneyMinter where he claims to have only withdrawn the proposal once for a user but we received multiple emails. RickLively has checked the logs and does detect that the proposal was withdrawn multiple times.
Spaces in author's name in the disposition letter:RickLively said this is a software issue where a space is added to the name when copying from the user profile part of the database to the propsoal author part of the database. We agreed to ignore this issue since it does not really appear to effect anything. AnandCrossley, who fieled the ticket, will ask the user why this is important.
Sponsored proposal submitted for the wrong telescope: There are several reasons why this sometimes occurs, but this is most likely due to ignorance about Sponsored proposals.
Account Issues. AnandCrossley reported that he took care of all password reset and institutional tickets. There seemed to be more institutional requests than usual. Otherwise, no major issues.
Science. DanaBalser reported that we released proposals for review on Friday. Only a couple of SRPs have declared all of their conflicts thus far. We have several cases in several panels where there are not enough reviewers; that is, too many conflicts. He is aksing SRP members to relax their conflicts or recruiting reviewers from other panels to perform a review offline.
Technical. MarkClaussen reported only one issue: we still advertise frequency averaging but no longer allow this in the OPT. He sent out an email to the technical reviewers making them aware of this situation. This should not be an issue in most cases.