Handling Pter reweighting in gracedb and automatic alerts

want to inform you about our options for updating our pterr in the case where the preferred event changes after RapidPE has finished. Keita brought this up during the Ops call as something they want implemented in gwcelery asap, for the (moved up) review deadline of September 21st. Vinaya and I just met with Cody to talk about how this might be implemented in gwcelery and we came up with two ideas: both involve gwcelery updating our pastro files with the new pterr value (and re-weighting our source classifications along with that of course). Vinaya and Cody were thinking of us just uploading the source classifications to gracedb and letting gracedb handle the reweighting/pterr part of it in all cases, for our first pastro results and any other possible versions when the preferred event changes. I expressed hesitation about this because it might rock the boat too much among the low latency crowd if we uploaded a different data product to gracedb, even if that part of it is not public. In my mind, the preferred event changes after rapid pe is done rarely enough that we could keep things as is and just have a command which uploads a new version of our pastro file in that specific case of the preferred event changing. I want to know what your thoughts are on this since I learned my lesson from last time about not consulting you first about pterr