8 s$ b$ E) }! E7 a% O) qImportant Compatibility Notes 4 ]7 e- W1 e. N' J; U1 U PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. ( @3 m6 Z" e' E( f; Z2 _8 N
 PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. 0 H7 X" M. u2 F* {8 z) K
 PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. 1 r& D* `* `$ t$ x* X' q
As always, data files are always forward compatible. The above items deal with issues of $ ~3 W" x' p# d; P3 Y ~ v4 r/ i: w
backwards compatibility. + b8 k5 |7 k0 D5 E" m
Program Enhancements / v6 z& O' ^" E; e
The following program enhancements appear in PSS®E-31.1.0: ' M, Y( \1 @ c" j% O6 K3 d2 Y Addition of the remaining three Generic Wind model types. PSS®E now has support for all " ?# n* n) p4 ~$ ] \9 nfour industry-defined Generic Wind Models. Please review additional documentation ! J6 C, x0 q0 i Ndelivered with this release on these models. 8 V0 j3 ]! T9 u- g& Y l
 Revised IEC test network sample files names from 60609 to 60909. 5 o- _6 j- {7 N0 k, i) a% b: O4 c Additional messages from DYRE clarifying when compilation of models is needed. : s9 Z' Q2 a- d) f, f* V" l ~ Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. 6 J" g6 J2 q& \" T9 Z( X2 ~
 Added “dyntools” Python module to post process Dynamics simulation channel file output 3 _5 K3 f4 h& V7 a) k2 m5 z(*.out). Details of available functions can be accessed using help(dyntools) in the Command : H! O% h! o1 P5 k$ A% _- U( U8 nLine Input dialog. ) t2 v+ b1 u6 V" S1 s% i1 k D8 v
Program Corrections 8 ?# j, |0 Y8 U
The following program errors have been detected and corrected in PSS®E-31.1.0: ; Q8 j. m n/ G+ q+ R; W
 Improved handling of Line Relay models in the GUI. 5 e% n3 a4 S) ~+ s Fixed general issues with bus subsystem definition. 3 X7 Z+ R% J V1 i) P Fixed an issue where Diagram items weren’t being properly identified. 5 p) f0 D4 g3 t+ O( f4 U# i
 Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was & v+ g; ?' a& k2 R4 K% w% J# v! ^& M
being set inadvertently. 6 W: ^ M- u. }3 o Fixed an issue where the program would crash if the user attempted to define a bus 8 J! j9 F* x3 T/ c. S7 e: {subsystem from a context-click in the Diagram. + Y& M; k1 f. v; q+ C2 s8 s% v Fixed an issue where the program would crash if the user selected two knee-points in the - J" t, B! W2 ~4 ^4 z
Diagram and then did a context-click. * o& E9 i( w6 h3 d+ B9 s0 p Various other corrections. Siemens Energy, Inc. $ q7 `1 Y3 t0 ]3 j6 n; rRelease Notes for PSS®E-31.1.0 Siemens Power Technologies International $ ~' u; R! N2 i1 t5 n5 U 4 `3 q: a! E# X* Q6 _ 7 z+ v: L l- a" T. c8 u2 1/9/2009 8 G1 G& G9 z- s6 Y' a, eCompiler Information : S: i# Q4 a0 w) f2 o% K- W
General Information ( B8 W- N: U4 p$ f* mPSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. a5 L& |2 r" H3 o/ h2 \User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or # v( `; u- z& c G" j0 Z
programs that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the ; N. a" n' r% B$ c9 V( w; J- w7 a% C
10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing & L5 ?1 p( L& S" }: ?1 m/ fcode from different compiler versions. " p) P9 f \% ? P' ]6 UAdditional Notes % u) f; E ]4 t! A2 I. t. i** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and $ e G0 t- ^( H5 ]( k) ]C run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a 1 q, ^# T8 \: |; q5 u J
compiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, & B1 N5 t2 J, G6 Qor programs that call USRCAS. + O g- L% V- j, N5 p/ T4 L$ aIntel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take 8 j1 k/ h" F ?' W+ ?+ G
advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler " A2 x% j) m# E6 X' G
license. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under ' h3 E; W9 s7 o4 l
this offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that - h1 X' j. Q1 X- E k9 E
"Siemens PTI customer" is stated in the subject line. ) T! ^( }- l( w1 gUser-Written Model Notes 4 Z. Q1 m6 P6 Q# Q1 ]8 CPSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead $ L I* C0 q8 O$ @
of numbers. To retain backward compatibility of old Saved Case files, device names are now set to 0 K! q2 L g2 c! R6 a6 A
the old device number, left justified. For example, 1 becomes “1 “. However, User-Written 2 A+ R2 c% c( Y; s3 xmodels of these devices that are called in conec.flx and conet.flx will have to be modified to map / h6 m6 {/ B' s9 Y( P4 b0 c! Q6 }
the old device number to its corresponding new internal device index. Please contact PSS®E 7 a3 C1 @; F$ _( t/ i, c
support if you have any questions on how to proceed with this. + n2 e( J ?* E) j- _In addition, during the course of our in-house development and testing, we have noticed that the & q6 b% b' s, g2 r; t$ W8 ]
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran 0 u' S, E0 ?; r& A- A8 n$ \) x! l
when compiled with the CVF compiler would crash when compiled with the IVF compiler. When # R; z- k6 _# Z% Q+ ^; [
compiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, , X! u& ^9 q' U$ S
and consider compiling your code with some of the more advanced debugging and verification 8 B( k1 `. g! M1 [- f6 n- K4 @% d
features of the IVF compiler.