Once #2 is done, wrap the code in a function. Allow for parameter inputs (length of look-ahead, length of schedule to keep). Output charge state, charge/discharge data. Use outputs to ensure charge continuity and build record of activity of the full year.
To keep the 24-hour discharge constraint, each optimization will probably need to know the proceeding 23-hour discharge schedule. I suppose this could be done by passing in the entire discharge schedule up to that point and using the values as a constraint.
Once #2 is done, wrap the code in a function. Allow for parameter inputs (length of look-ahead, length of schedule to keep). Output charge state, charge/discharge data. Use outputs to ensure charge continuity and build record of activity of the full year.
To keep the 24-hour discharge constraint, each optimization will probably need to know the proceeding 23-hour discharge schedule. I suppose this could be done by passing in the entire discharge schedule up to that point and using the values as a constraint.