Hi Brian
No problem. On that note, what is the purpose of "flush" in chemplugin? When there is inflow and outflow at an instance, isnt the solution anyway replaced with the inflowing solution in a chemplugin instance?
I am also not sure how chemplugin handles kinetic minerals when the run is extended.
When I extend the model, it seems like it is using the original kinetic mineral mass and not the endpoint mineral mass of the previous run. However, extend in chemplugin does use the endpoint solution chemistry and retain secondary minerals. I have tried to use the "pickup reactants" before the ExtendRun or within the original configuration but that doesnt work.
cp_dam.Config("pickup reactants")
cp_dam.ExtendRun(timeExt, "days")
I have also tried to remove the kinetic minerals and then let it perform the pickup. But that also doesnt work.
To test this I have included pyrite and calcite in the reservoir described above and then calcite was consumed in the 1st run. ExtendRun then starts again with the original calcite (and pyrite)content. However, it seems that secondary minerals in the system (like hematite) is retained.
See the gtplot image below.
Regards Johan