Hi Jia,
I have attached an updated script with wet-dry cycles and a re-hydration step in between weathering and evaporation. The way we have been doing this has been taking the weathering script (EW) run it, then pickup the system fluid, change the H2O back to 1, delete the pH (i.e., pH = ,so that it balances on this and save that file as the re-hydration script. (RH). Next we reopen the EW1 script run it, save the output file as the end of weathering solution (EW1), then take a simple evaporation script which picks up the system fluid, react -950 g H2O fix the fugacity of CO2(g) and H2S(g) and balance on pH. This then gives us the end of evaporation solution (EE1), which we save the output, and that is for 1 wet-dry cycle. Now we take the RH script open it up in a text file, copy the script in to the command window and run it to rehydrate the fluid that is in contact with our original 5% weathering of a rock, then save this output file as RH1. We then open a different text file for the evaporation script (the change from the first evaporation script is a full -1000 g H2O instead of -950 g H2O) and run this in the command window to get the second wet-dry cycle, save the output as EE2, then re-hydrate, save output, evaporate, save out put....till we get ten wet dry cycles. Now the script I have provided does all of this in on go, but only gives me the last cycle for the data when try to export solution chemistry(element concentrations in fluid and or select aqueous species) it from gtplot as a tab delineated spreadsheet. Now this is quite tedious and if I mess up in any of the cycles I have to start over in the process. So my questions are:
1. Can I save each output file automatically as the wet-dry script runs? I sorta have this figured out but cant get the subsequent cycles to save.
2. Is there a way to extract the data at each evaporation cycle instead of just seeing the final solution. (We are interested in the change in element concentrations at the end of each evaporation cycle).
Essentially I want to make this work more efficiently and be less time consuming, but also since I have a physical disability with limited dexterity in my hands that make it hard to have to constantly copy and paste things as well as constant mouse clicks for many hours of running and saving scripts. So I am curious if there are any steps to be made to make the GWB more inclusive and open to those that are not able-bodied. Currently it is suited for able bodied individuals.
Cheers,
Jaxon
1_EW-EE cycles.txt