You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have just started using Matpower recently to simulate the dispatchable load. However, I don't quite understand the principle of modifying multi-period load data in MOST. In the given example of the manual, the load is at bus 3, set as a negtive generator. The time-varying load is set at CT_LOAD_ALL_PQ bus. However, there is no CT_LOAD_ALL_PQ bus in the casefile 'ex_case3b'. So, on which bus(es) are the demand data is changed in different period?
Furthermore, I've checked the MOST function. It seems the power demand is always 0 at every bus at each tstep. How 'flow constraints' is built?
Can anyone please help me?
The text was updated successfully, but these errors were encountered:
The CT_LOAD_ALL_PQ identifier simply indicates that all (fixed and dispatchable) loads, active and reactive, should be modified (See Table 9-4 in the MATPOWER User's Manual).
Which buses are affected is determined by the rows field of the profile. If it is set to 0, that will affect loads at all buses. If you are seeing all zeros for loads, it may be because you are using CT REL (scaling) as the change type and the original values in the case file are zero.
Hi! I have just started using Matpower recently to simulate the dispatchable load. However, I don't quite understand the principle of modifying multi-period load data in MOST. In the given example of the manual, the load is at bus 3, set as a negtive generator. The time-varying load is set at CT_LOAD_ALL_PQ bus. However, there is no CT_LOAD_ALL_PQ bus in the casefile 'ex_case3b'. So, on which bus(es) are the demand data is changed in different period?
Furthermore, I've checked the MOST function. It seems the power demand is always 0 at every bus at each tstep. How 'flow constraints' is built?
Can anyone please help me?
The text was updated successfully, but these errors were encountered: