Because in general, CAESAR II doesn't know what P2 is. Does P2 represent another operating condition, an upset condition, or a hydrotest condition (since the load case recommendation routines were designed before CAESAR II had a hydrotest option)?

Furthermore, there is no rule that says P2 must go with T2, or P3 with T3. There is a lot of capability in the "static load case editor". We recommend what we think is the <em>minimum</em> set of load cases to satisfy code compliance. The user must still evaluate the load cases to see if they are sufficient for all requirements.

Having made this statement, please be advised that we are currently working on a more advanced "static load case editor" which will allow users to define how load case recommendations are made, based on the existence of load types (P2, U1, etc).