Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Principle of modifying multi-period load data in MOST? #47

Open
tanzhongtan opened this issue Aug 19, 2024 · 1 comment
Open

Principle of modifying multi-period load data in MOST? #47

tanzhongtan opened this issue Aug 19, 2024 · 1 comment

Comments

@tanzhongtan
Copy link

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?

@rdzman
Copy link
Member

rdzman commented Aug 19, 2024

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.

For details on how profiles are used to change multiperiod data, see Section 5.1.6 in the MOST User's Manual, and Section 9.3.5 in the MATPOWER User's Manual.

Feel free to come back with more specific questions if this doesn't clear it up for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants