Gary22212's profile - activity

Thanks Jeff!

Thanks Berwin!

Hi all,

Thanks for checking the question.

I have a project idv file (using RDCH to read raw data to existing cases) which is in v33 psse version. I would like to convert it to v34 idv file but couldn't find a convenient way except manually converting it.

Are there any bright ideas? Any help would be highly appreciated!

Thanks, Gary

Hi, thanks for checking this question.

I was wondering if anyone knows how to open PSSE v34 single-line diagram (SLD) files in PSSE v33? Are there any convenient ways or tricks?

Thanks in advance! Gary

Hi ffl, thanks for the answer, it really helpful!

Hi perolofl, that's make sense, I appreciate!

Hi ,

Thanks for coming in.

I was wondering what is the "metered on from end" in the transformer data record means ? What is the difference between checking and unchecking the option?

Sorry I am unable to paste the picture for unknow reason; you can easily find the "metered on from end" option by double click the 2-winding transformer in a SLD (diagram) file , or the "metered" option in the sheet of "2 winding" in a sav file.

I could not find the answer and any guidance is appreciated.

Gary

E.g, if we train a control module for the system, we need to keep interacting data with deep learning models and PSS/E packages for thousands of episodes. Thus the barrier exists. An expedient method is to use subprocess, but it would greatly decrease program efficiency. ...Thank you for your reply!

Thank you so much for your reply. Just have a little concerned, it seems that PSSe v.34.7 only works with python v.3.x in 32-bit version? So challenge still remains in interacting Pss/e with new python packages e.g.deep learning, which only available in py 3.6+ 64-bit version.

Dear everyone,

I know PSSe33 was built as a 32-bit application. and python2.7 of 32-bit works fine with PSSe33.04 in my work.

Does anyone know can PSSe work with python 3.6 of 32-bit? I tried but failed, the problem first happened at "import psspy", and the console indicates "bad magic number in psspy..."

Maybe there are problems in my settings, or there are restrictions in PSSe version?

And I also failed to make python of 64-bit (either 3.6 or 2.7) work with PSSe.

Thanks in advance!

Gary

Hi folks.

I guess this should be an old topic.

As you know, PSSE may only work well with python 2.7 32-bit, (v34 PSSE can work with python 3.4 32-bit but massive problems have been reported). However, given python 2.7 32-bit is out of maintenance now, and it doesn't compatible with many the state of art packages. As a result, more and more problems gradually revealed.

For example, it causes a lot of trouble when I use python 2.7 32-bit to call PSSE to carry out simulations, and then need to use some packages which only available in python 3.7+ 64-bit to analyze the simulation data.

Do you have any suggestions or tricks to solve the problem?

Thanks for you all.

you may create a download order and then obtain the new Xplore version from https://new.siemens.com/global/en/pro...

Yes, it works after the reduction. Thank for very much!

Exactly!!!

Dear everyone,

I have a question regarding the API: TYSL. As we know we need to perform CONG, CONL, ORDR, FACT, TYSL, etc.,prior to running the transient stability program. What makes me confused is what is the purpose of performing TYSL? The help documents said "Use this API to run switching study network solutions", but I still confused.

Thank you all in advance!

Gary

Hi all,

Thank you for coming to watch the question. I am trying to optimize the output from PSS/E then send the results back to PSS/E for further operations.

I found PSS/E doesn't work with Scipy package (a very popular optimization package in python), does anyone encounter the same problem before?

The code below is a concise example that shows the problem, in my IDE (Spyder), as long as you initialize PSS/E, the program is going to be stuck and die.

You are welcome to try the code：

import os, sys
# Set environment for psse33.04
PYTHONPATH = r'C:\Program Files (x86)\PTI\PSSE33\PSSBIN'
sys.path.append(PYTHONPATH)
os.environ['PATH'] += ';' + PYTHONPATH
import psspy
_i = psspy.getdefaultint()
_f = psspy.getdefaultreal()
import redirect
redirect.psse2py()
psspy.psseinit(buses=50)  # the optimization code doexn't work as long as you keep this line!!!

from scipy.optimize import minimize
import numpy as np

fun = lambda x : (x[0] - 0.667) / (x[0] + x[1] + x[2] - 2) # obj: min (x−2/3)/(x+y+z−2)
cons = ({'type': 'eq', 'fun': lambda x: x[0] * x[1] * x[2] - 1}, # xyz=1
        {'type': 'ineq', 'fun': lambda x: x[0] }, #x>0
        {'type': 'ineq', 'fun': lambda x: x[1] },#y>0
        {'type': 'ineq', 'fun': lambda x: x[2] }#z>0
       )
x0 = np.array((1.0, 1.0, 1.0)) # 
res = minimize(fun, x0, method='SLSQP', constraints=cons)
print('min value:',res.fun)
print('solution:',res.x)
print('success or not:', res.success)
print('message:', res.message)

Thanks in advance, any help will be appreciated.

A slight digression, I think psspy/psse really need to be updated to be compatible with 64-bit, 3.7 or higher version Python, given that python 2.7 is very old which will be out of maintenance from Jan 2020. ( ͡° ͜ʖ ͡°)

Thank you JConto and drsgao, The problem lies in the incompatibility between the new version of Scipy (version 1.2.2) and PSSPY. Actually, both are 32-bit versions in my PC. I degraded the Scipy to V 0.16.0, the same version as you used, then it worked.

Thank you very much, the problem was solved.