Closed qlangfitt closed 2 years ago
Just spent an hour looking into this. A few things:
It looks like rewiring the model was not needed. Changed the defin of API_O in the lookup table for the relevant product categories and now track API gravity through the storage tank and other stages. Should now give proper density calculations for those streams.
There seems to be inconsistent use of API gravity for upgraded fields (uses “API_grav” input for SCO in flow table, but not sheet calculations – Heavy Oil Upgrading M107).
I think the intent is that the API gravity input represents the post-diluted value. However, in practice OPGEE uses this value both for the (1) undiluted heavy oil API gravity and (2) the diluted product API gravity for oil sands fields (undiluted bitumen uses a secondary input specifically for bitumen instead). This is obviously evident from looking at Table 4.1 in the documentation where crude oil in reservoir and diluted/upgraded crude all use API_grav.
Related to this is that the smart default for GOR and heater/treater selection are based on the API gravity, but if the input API gravity is the post-diluted or post-upgraded value, then this seems incorrect.