Thank you for your reply sir. Actually I have figured out the cause---The original case struct before reduction has a 'order' field that is not consecutive. If the original case runs a power flow, ext2int() will rearrange the inconsecutive orders and gen indices. But after reduction, the original inconsecutive order is also ruined somehow and ext2int() cannot rearrange gen indices.
------------------ ???????? ------------------ ??????: "Ray Daniel Zimmerman"<[email protected]>; ????????: 2020??3??31??(??????) ????1:21 ??????: "MATPOWER-L"<[email protected]>; ????: Re: Generator indices after network reduction using MPReduction() Thanks for bringing this to our attention. Unfortunately, I??m not very familiar with that code, since I didn??t write it. Can you create a minimal reproducible example that can be used to duplicate the problem? If so, would you mind creating a bug report in the mx-reduction issue tracker and attaching the files for the example? With that, maybe I can get the original author to have a look (no promises). Ray On Mar 27, 2020, at 8:24 PM, yangyang <[email protected]> wrote: Dear all, I am using MPReduction() in the extras folder to implement power network equivalence. But the power flow will report error sometimes, because the indices of the generators will not be arranged in the reduced network. Say, in the original case a generator is at bus 100, but after reduction there are only 90 buses and the index of the generator will not be rearranged. Is there any way to fix it? It seems that ext2int() cannot fix the bug. Thank you all.
