tolemanator's profile - activity

For some reason Py39 wasn't installed with my PSSE v35, but 37 was, so after some playing around I got it to work. thanks!

I am trying to import and initialize PSSE35. Simply changing paths and system interpreters from what I have for version 34 isn't working.

PSSE version 34 (running with python 39, 32 bit): sys.path.append('C:\Program Files (x86)\PTI\PSSE34\PSSPY39')

PSSE version 35 (running with python 38, 64 bit) sys.path.append('C:\Program Files\PTI\PSSE35\35.2\PSSPY38')

ERROR: Traceback (most recent call last): File "C:/Users/nxt0v07/OneDrive - NEE/Python/Model builder/psse35test.py", line 154, in <module> import psse35 File "C:\Program Files\PTI\PSSE35\35.2\PSSPY38\psse35.py", line 34, in <module> EXAMPATH = psseloc.setpsseloc(svrsn) File ".\psseloc.py", line 384, in _setpsse_loc ImportError: DLL load failed while importing psscommon: The specified module could not be found.

In trying to get PSSE version 35 initialized properly, I tried running with python 39 32 bit and it threw bad magic number errors. I switched to python 38 since it didn't appear that python 39 was installed with my PSSE35 stuff, and it threw win32com errors so I switched to python 38 64 bit. The error above is what I'm trying to debug...

did you figure this one out? I have the same issue

I am trying to use python to script things in PSSE v35. The initialization code I have for v34 works and when mirroring for v35, I get a bad magic number error.

This works for v34, there are install files for 2.7, 3.4, 3.7, and 3.9 (using 3.9 as the interpreter) in the C:\Program Files (x86)\PTI\PSSE34 root:

sys.path.append('C:\Program Files (x86)\PTI\PSSE34\PSSPY39')

This not working for v35, there are install files for 2.7, 3.7, and 3.8 in the C:\Program Files\PTI\PSSE35\35.2 root:

sys.path.append(r'C:\Program Files\PTI\PSSE35\35.2\PSSPY38')

The error: Traceback (most recent call last): File "C:\Users\nxt0v07\OneDrive - NEE\Python\Model builder\idv_app.py", line 175, in <module> import psse35 File "C:\Program Files\PTI\PSSE35\35.2\PSSPY38\psse35.py", line 27, in <module> import os, psseloc ImportError: bad magic number in 'psseloc': b'U\r\r\n'

I was running the v34 script with python 39 but I downloaded and got 3.8, and now it's throwing "DLL load failed while importing psscommon: %1 is not a valid Win32 application." even though the 3.8 version I have is 32 bit. I now have switched to 64 bit which seems to have solved the Win32 error, but now it's looking for a file that doesn't seem to exist:

Traceback (most recent call last): File "C:/Users/nxt0v07/OneDrive - NEE/Python/Model builder/psse35test.py", line 152, in <module> import psse35 File "C:\Program Files\PTI\PSSE35\35.2\PSSPY38\psse35.py", line 34, in <module> EXAMPATH = psseloc.setpsseloc(svrsn) File ".\psseloc.py", line 384, in _setpsse_loc ImportError: DLL load failed while importing psscommon: The specified module could not be found.

I was doing that yesterday and for some reason it wasn't working then, but it is now! and yes I'm in pycharm. Thank you!

I was doing that yesterday and for some reason it wasn't working then, but it is now! and yes I'm in pycharm. Thank you!!

I'm trying to do something like: ierr = psspy.solutionparameters4([100, FDNSiter, 40, 100, 10],[1.6, 1.6, 1.0, 0.0001, FDNSaccn, FDNStoln, 1.0, 0.00001, FDNSbln, 0.7, 0.0001, 0.005, 1.0, 0.05, 0.99, 0.99, 0.1, 0.00001, 100.0])

It seems to be rejecting the variables I pass through like "FDNS_iter" even though I force the variable to be an integer type. It consistently throw an error of "Type Error: must be a real number, not a str" so somehow defining the variable as an integer isn't be recognized so I'm wondering if the PSSE API isn't able to pass variables through functions period.

I think I figured out the problem and it was not initializing the output file before starting to write to it, and sometimes it wouldn't find the file if it wasn't created quickly enough and then would default to the terminal. thanks for your help!

I am writing a script to batch build models and I have the solve log info (via progress_output) going to a text file output instead of the python terminal. Sometimes, without a reason I can determine, the output shows up in the terminal but then other times it gets redirected as intended. Any ideas?