Confusion:LorantSjouwerman was concerned that the new structure would be confusing to our users and that we were not providing the user with enough information. For example, how to specify overhead which depends on many details (e.g., SB length). This is true with the current PST, but we should try to find ways to make things more transparent.
Optional Number of Sources:LorantSjouwerman felt this was confusing and suggested we remove it. All agreed that it was rather confusing but necessary if we have to specify all sources that may be observed. Maybe there is another way to do it.
Scheduling Section: The requirements document provides parameters and a textbox to help the user specify scheduling information. For example, monitoring a source. We discussed if adding a scheduling section just for this would be easier. It would be best to capture all info using parameters but this probably cannot be generalized (e.g., non periodic monitoring). GustaafVanMoorsel pointed out that we need not micro manage this info for the pressure plots which only need to be approximately correct.
Downstream Software: The requirements document specifies a way to generate sessions so that software downstream of the PST (e.g., PHT) does not require significant changes. BarryClark suggested that a manual interface might work better.
Strawman:DanaBalser noted that RafaelHiriart is working on a straw man interface to use for testing. Everyone thought this would be a useful next step.
BarryClark will design a user interface for manually editing Sessions in the PHT.
DanaBalser will check on the timeline for the straw man interface.