Hello all, I am interested in developing interface limits for MOST. Is anyone else working on that? If so, please let me know. First time developing anything with Matpower or MOST, but do have a bit of experience working with the programs. Working with Dr. Zimmerman, made a day-ahead and real-time market model with a generator startup notification constraint. Feel free to reach out if interested in any of that. Coming to a transaction paper soon!
Going to copy and paste Dr. Zimmerman's comments on incorporating Interface Flow Limits into MOST. **** You are correct about the interface limits not being implemented yet in MOST. I assume you are familiar with Section 7.5.2 on Interface Flow Limits in the MATPOWER Manual <http://www.pserc.cornell.edu/matpower/docs/MATPOWER-manual-6.0.pdf> and have probably already taken a look at <http://www.pserc.cornell.edu/matpower/docs/ref/matpower6.0/toggle_iflims.ht ml> toggle_iflims(), which is where the constraints are constructed in the userfcn_iflims_formulation() function. If not, that'd be the place to start. It would be great to have you implement this feature in MOST if you are able. I don't know of anyone else working on it. I would suggest using the existing format for the input data and simply constructing the constraints for each scenario, contingency and period in a way identical to that in <http://www.pserc.cornell.edu/matpower/docs/ref/matpower6.0/toggle_iflims.ht ml> toggle_iflims(). In terms of coordinating the inclusion into MATPOWER, the best way is to follow the MATPOWER Contributors Guide <https://github.com/MATPOWER/matpower/blob/master/CONTRIBUTING.md> to fork, clone and update the MOST repository on GitHub <https://github.com/MATPOWER/most> , then create a pull request when everything is ready for me to review. **** Any comments or additional thoughts welcome! Best, Steve _____________________________________________________________ Stephen M. Burchett, P.E. | ECSE Department | Rensselaer Polytechnic Institute 551.482.3477 | <mailto:burc...@rpi.edu> burc...@rpi.edu
