Edit: Just remembered that you cannot use timestepping keywords inside the ACTION statement
While having to explicitly define timestep stages of water/polymer this causes us a problem - and on first glance can't think of a solution. Can you do without the ACTION statement? You may have to run the simulation to find when the watercut is reaching 60%, then edit deck to incorporate polymer flood after this... a pain, and especially awkward if you are doing many different runs, but possibly only solution given ACTION restrictions
Anyone else have an idea?





Reply With Quote

Bookmarks