First time here? We are a friendly community of Power Systems Engineers. Check out the FAQ!
2015-09-13 22:20:00 -0500 | received badge | ● Famous Question (source) |
2015-09-02 02:44:33 -0500 | received badge | ● Notable Question (source) |
2015-08-28 16:08:20 -0500 | received badge | ● Popular Question (source) |
2015-08-28 13:44:17 -0500 | answered a question | Get area interchange from 230kV lines only My solution ended up using the |
2015-08-18 09:04:53 -0500 | asked a question | Get area interchange from 230kV lines only As the title suggests, I'm looking for a method to find the area interchange on the 230kV lines. When I enter Now, here's my question. I know that I can use a command such as The problem is that I am also interested in the interchange on the 230kV lines only: the value I've been searching around the API and can't seem to find anything to get this value. (it cannot simply be printed to the screen as the Is there any command which will get me this value? Thanks for any help. |
2015-06-10 10:50:56 -0500 | answered a question | Suppressing some PSSE output permanently suppresses all output If anyone is interested, here is how I solved my problem (quite simple): Whenever I want output to be suppressed, I make a call to Afterwards, when I want some output to go back to PSSE, I had to call |
2015-06-09 14:14:54 -0500 | received badge | ● Organizer (source) |
2015-06-09 14:12:29 -0500 | asked a question | Suppressing some PSSE output permanently suppresses all output I've followed the procedure outlined in the "Silencing PSSE output" article from whit.com. However, after calling blocks. Does anyone have an idea for how to remedy this problem? My program runs Here is the code I use for my silence method (This is contained inside a class; my program uses Tkinter GUI's so most of the code is wrapped up in a "Window" class): *EDIT: On subsequent runs, even text that comes before the |
2015-06-09 14:06:19 -0500 | received badge | ● Autobiographer |
2015-05-06 10:15:55 -0500 | received badge | ● Editor (source) |
2015-05-06 10:01:27 -0500 | asked a question | Python(2.5) script using Tkinter causes PSSE32 to freeze on second run Hello. Incoming wall of text: I'm having a problem with a script I wrote for PSSE v32 with Python v2.5 as the title suggests. The script is supposed to take in relevant generator data from an excel file. The spreadsheet is formatted as follows: Bus# Bus ID Bus Name PNRIS PERIS PMAX Changes Notes # 'str' 'str' # # # 'str' 'str' "Changes" and "Notes" are not important for this question, I just want the specifics of the excel file to be clear. Basically its the information about a generator, followed by 3 different possible power values that it might be set to. The script creates a subsystem with all of the relevant machines to be changed, and will set the PGen value of every machine in the subsystem to the user's selected power type. Choices are NRIS, NRIS + ERIS, ERIS, or PMAX. The power type selection is made using Tkinter, using 4 Radiobuttons. On the first run through the program, everything runs exactly how it is supposed to run. However, if I try to run the script a second time within the same instance of PSSE (IE, without closing the program and reopening it), PSSE locks up. This occurs whether I attempt to run the script on the same .sav file, or if I open another case. I understand that PSSE runs every subsequent Python script from where the previous one left off? I believe my problem has something to do with Tkinter. Earlier in the development process I encountered an error in which the second run *would* work, but the variable associated with the Radiobuttons would be stuck to whatever it was initialized as. One additional piece of information; when I run this script, other toolbar Python scripts will still work correctly after running it. However, the following, which again utilizes Tkinter: Will only print & return 1. Normally, if I run this script through PSSE using the toolbars, I can run it any number of times in a row and it will run as expected. The selection number is printed every time the selection changes, and "Final selection: #" is printed when OK is clicked. This may not be relevant, however, since it uses Tkinter I feel like it might be related to my problem. I'm new to PSSE (starting using it one week ago today) so I could easily be missing something fundamental. I'm running the script from PSSE using the custom toolbar icons. I cannot attach my .py file, as I'm new to this site and thus do not have enough Karma. It ... (more) |