本帖最后由 apsal 于 2009-5-9 20:04 编辑 & z# z! B- y9 I3 N
: x6 f/ x0 G, C
Important Compatibility Notes - I. n! C; \7 s/ ?! c8 A PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. & ^2 l E- g! B5 o+ M/ x
 PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. , e- ^+ Y6 B( o' w/ P6 H& b2 ~
 PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. ' m4 ?' ]: D0 n
As always, data files are always forward compatible. The above items deal with issues of ; u- i' |( H- b& K4 h4 Bbackwards compatibility. 9 H* W/ G* u: P# w$ D6 W# L; LProgram Enhancements ! o$ S6 J# X( ?3 j& G2 q
The following program enhancements appear in PSS®E-31.1.0: + t1 Z% ], s9 r/ i0 A8 N Addition of the remaining three Generic Wind model types. PSS®E now has support for all 9 w9 s8 T8 e( W- W$ U. ?
four industry-defined Generic Wind Models. Please review additional documentation 4 I; X/ N1 g8 c& Y6 B, jdelivered with this release on these models. 4 I6 E% f) b6 R$ z
 Revised IEC test network sample files names from 60609 to 60909. 2 A( I1 W6 ^9 w, i% W. K. y
 Additional messages from DYRE clarifying when compilation of models is needed. * U6 j" d$ s# O6 s1 T" ^9 M Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. 8 j3 Q y" c' U3 i+ ], e0 I Added “dyntools” Python module to post process Dynamics simulation channel file output 3 s0 B7 U- t, `3 L- C(*.out). Details of available functions can be accessed using help(dyntools) in the Command ; [0 N( r- Y7 n8 yLine Input dialog. , b$ A: a% o" x+ BProgram Corrections - H( Y- N8 | J: GThe following program errors have been detected and corrected in PSS®E-31.1.0: & ]+ D1 B9 D3 C/ E6 ]6 O9 C, _- @ Improved handling of Line Relay models in the GUI. " _. ]- y. B( r2 f1 p7 k
 Fixed general issues with bus subsystem definition. & Z4 k# Z/ @/ ~ E7 u; m& b7 u) }
 Fixed an issue where Diagram items weren’t being properly identified. @2 q6 D9 w3 q+ h( [. q% K: A2 ~ Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was ) Z" `) G; x: `* T* p! s* }. Qbeing set inadvertently. 0 t& a0 U& D& T Fixed an issue where the program would crash if the user attempted to define a bus " p( D* G# w5 o, d; ^2 |
subsystem from a context-click in the Diagram. 6 }! Z$ L# m& k3 E- j0 d1 b. e
 Fixed an issue where the program would crash if the user selected two knee-points in the % u3 M2 z9 _( P, ?! p7 T% S
Diagram and then did a context-click. # {9 v0 L- ^; K) y Various other corrections. Siemens Energy, Inc. 3 W. R+ ^6 A5 M1 h$ S. C
Release Notes for PSS®E-31.1.0 Siemens Power Technologies International + t7 C3 b( p0 K: t0 S/ v' i7 j
, H: F* E: b. @ , R9 k; b9 G5 }" J
2 1/9/2009 3 O0 t: R' I/ j* U1 L, `' |Compiler Information $ U2 l) i" G! kGeneral Information " Q8 J! [; u2 W% V0 BPSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. 4 F) N, } a/ Y+ V
User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or 1 H) w# f9 r' j* T p
programs that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the ! k2 Z3 o4 g( Q+ p0 |' e$ Z10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing 0 X% u; J; D5 C$ @5 [
code from different compiler versions. ( |) k- M/ F9 I; B' bAdditional Notes * A! r$ Z0 y' A2 R! o
** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and + y8 g l5 X B) F7 ^. e
C run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a " N$ ^( N/ F5 o+ y9 `7 ]8 i) t. I
compiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, $ z( f" I, h& Y2 c0 M9 d
or programs that call USRCAS. $ E: N. B L' a" x" Q9 T/ b, y
Intel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take 1 ?9 L8 k5 _5 |! Xadvantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler % \0 H+ t- _( S1 A5 glicense. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under * [9 X1 W: _- W8 @ b- Y
this offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that 3 N7 @$ P5 P5 R1 T4 d; x% A"Siemens PTI customer" is stated in the subject line. 0 r- C% R, B( }8 p) xUser-Written Model Notes# {8 u0 M3 Z x2 S
PSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead , z' q0 j# E. xof numbers. To retain backward compatibility of old Saved Case files, device names are now set to ! U( S) e% s+ u+ T' s1 K9 [# y
the old device number, left justified. For example, 1 becomes “1 “. However, User-Written 4 \+ g1 g# j' x9 H( \models of these devices that are called in conec.flx and conet.flx will have to be modified to map / A, u" w/ V4 v7 c/ V0 J4 m
the old device number to its corresponding new internal device index. Please contact PSS®E ' e3 f4 j2 N* u+ q ~) y& [support if you have any questions on how to proceed with this. : q0 L) k/ u" n% h4 t, c
In addition, during the course of our in-house development and testing, we have noticed that the ' A3 l3 u9 L6 Q' f6 zIVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran - q0 r5 v8 J5 O. ~
when compiled with the CVF compiler would crash when compiled with the IVF compiler. When 1 [. e6 p! _0 P3 E# K1 Gcompiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, ( B# N; q3 P- ]' A- c# iand consider compiling your code with some of the more advanced debugging and verification : m+ D( o' b9 f
features of the IVF compiler.