I expect that the computation time might grow quadratically with the number of units it needs to shut down. So if your simulation has a pattern of decreasing loads you might see this trend. Otherwise, I'd be suspicious that something else is going on.
Also, I'm sure you are aware, but just as a reminder, the algorithm implemented here is only a heuristic and a pretty computationally expensive one at that. It is not suitable for large systems with lots of generators that need to be shut down. For such a case, it might make more sense to run it with all generators on with PMIN set to zero, then use generators with non-zero dispatches as a starting commitment for MATPOWER's current algorithm. -- Ray Zimmerman Senior Research Associate B30 Warren Hall, Cornell University, Ithaca, NY 14853 phone: (607) 255-9645 On Jul 2, 2013, at 10:47 AM, "Hardy, Trevor" <[email protected]> wrote: > Dr. Zimmerman and company, > > First of all, thank you for your efforts on MATPOWER and the continued > support you provide. It has been a wonderful tool to use. > > I’m using the smartmarket module on a 240 bus system over many one-hour > dispatch periods. I recently ran this system for one week of simulation time > (168 dispatch periods) and noticed that the computation time per period grows > quadratically as the simulation progresses. I’ve read the section of the > manual on the uopf function (called by the smartmarket function) and it is > not clear to me if this is expected behavior. If it is, is there anyway to > mitigate the growing computation time? > > Trevor Hardy > Wichita State University
