8 Q! M" H d. p; j4 ?Important Compatibility Notes / v) `' `$ {5 U' N1 n PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. " e( P& m) c1 |/ T: o4 ?( p/ z PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. 4 p/ H5 l# P- l& j, J$ g8 R% Q2 [ PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. 2 K1 N# O5 H l$ H
As always, data files are always forward compatible. The above items deal with issues of 3 {* P! h# P! g7 ]" J6 Y" A7 Jbackwards compatibility. _$ V% k7 W1 c/ KProgram Enhancements 8 a" k" t( o+ e2 yThe following program enhancements appear in PSS®E-31.1.0: " l* z3 g" x1 a
 Addition of the remaining three Generic Wind model types. PSS®E now has support for all % m3 T/ P2 @3 \4 ?, o7 o
four industry-defined Generic Wind Models. Please review additional documentation / y6 ~# s3 q' Z. }& |( W. j) ~
delivered with this release on these models. ; y p6 E) `& s* ~2 P' U8 a( K Revised IEC test network sample files names from 60609 to 60909. 3 p! d! x, X' `0 c q$ b5 T; ] Additional messages from DYRE clarifying when compilation of models is needed. 1 h- ~- W# D( C7 M4 Y
 Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. ( u7 q/ O* c: m4 J# [ Added “dyntools” Python module to post process Dynamics simulation channel file output % b$ O. Q+ X& X: ^) N! o' F. m# b
(*.out). Details of available functions can be accessed using help(dyntools) in the Command 1 N% m0 V& `2 I( h/ iLine Input dialog. ! W; s8 `. V6 z3 |8 c- b e
Program Corrections $ S9 t) M( K' h! K2 a/ J, [The following program errors have been detected and corrected in PSS®E-31.1.0: # h# g: `5 p" ~1 N! y
 Improved handling of Line Relay models in the GUI. % G! W0 U" [) ?" k Fixed general issues with bus subsystem definition. 5 s4 a# t/ ~% L Fixed an issue where Diagram items weren’t being properly identified. * e/ i- O! L3 B) `" y+ c% x) I Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was ; M! ~2 m2 M: m; T- t
being set inadvertently. 1 k, e2 l& L, R# T" G2 y3 X5 p
 Fixed an issue where the program would crash if the user attempted to define a bus - \$ w) L u& ? O6 c" T; S
subsystem from a context-click in the Diagram. , z5 H' ^9 L2 R% G' J) \! J B& O Fixed an issue where the program would crash if the user selected two knee-points in the % ^. R; O2 D( G# k/ R% Q. M3 ?Diagram and then did a context-click. / G. Z4 \; v6 ~8 v m& w
 Various other corrections. Siemens Energy, Inc. ! Q3 [0 p. {$ J0 m9 h6 @
Release Notes for PSS®E-31.1.0 Siemens Power Technologies International : c3 t& Q; X- _4 g* s) e9 b ) L& b% G0 A1 H7 `: l7 ^
- n, Q; R4 U1 Z' @" }' H2 1/9/2009 1 j9 U7 H& }1 C5 c! V C0 I$ Z- u; u4 GCompiler Information * K2 y+ l5 D& U& N- a3 W* \0 y6 ]2 d
General Information # p5 m1 ~5 x# \- S" rPSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. 4 s+ b! F" P/ c" ^) |
User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or * x! z; @( T2 @. n5 |; z8 V5 mprograms that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the 0 u$ i/ C, b6 i4 Y) D9 X% e10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing ) E. B2 c$ ^$ K, ~% {0 g
code from different compiler versions. 0 j/ a8 ]2 g& M/ l, c; J F; ~
Additional Notes 9 l2 e' u$ p* k* C3 U7 e; _' v
** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and , l# ?! w4 A/ U& M9 o! o7 o3 A
C run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a . y. d" p2 t3 `# ~% N' I" d( w
compiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, 6 l% k( Q! Y& Zor programs that call USRCAS. Z2 A4 |9 V" H$ V3 [, q8 H
Intel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take 1 r; Z! k7 ?" B
advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler " Z/ E- ~2 F( C: l T7 ]
license. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under 9 f1 N6 \- N2 y3 E" W* Sthis offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that 1 j& O' s" j7 C7 x, `) u$ @
"Siemens PTI customer" is stated in the subject line. 8 ]! C5 }: g+ p- @2 U5 m
User-Written Model Notes- C! z g4 d3 r+ v- Q# i+ o; q9 D
PSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead 6 k! f' S* b# D
of numbers. To retain backward compatibility of old Saved Case files, device names are now set to ( @2 q1 Z: o4 |/ {5 Bthe old device number, left justified. For example, 1 becomes “1 “. However, User-Written 6 w$ ?9 j& n% {- O& ]) r! {9 vmodels of these devices that are called in conec.flx and conet.flx will have to be modified to map 0 E+ T! ^- z d9 {5 i3 I: }the old device number to its corresponding new internal device index. Please contact PSS®E & x5 K3 l2 S: t5 I: y# E# s& w6 S' [4 `
support if you have any questions on how to proceed with this. % y) N* k& I% B9 aIn addition, during the course of our in-house development and testing, we have noticed that the ! L8 ?! ?) Q( Y% D. v% R: [
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran ; }/ M! D8 y, V' c- I5 @
when compiled with the CVF compiler would crash when compiled with the IVF compiler. When 6 _& O3 _2 K" `4 x5 M
compiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, + D, w) |5 v# h
and consider compiling your code with some of the more advanced debugging and verification - `- H0 N. o5 |2 o+ X/ Efeatures of the IVF compiler.