8 y4 \6 S" J9 A. ^( zImportant Compatibility Notes 6 P! W( {5 u- g& d6 B; E0 u9 T
 PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. 9 Z2 {; y' V# s PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. ' D) D1 b5 Q5 ~8 v/ P PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. / `8 @% k$ y8 C% w1 \9 `2 J
As always, data files are always forward compatible. The above items deal with issues of . E0 J! m( i+ ^+ [ o9 W! y
backwards compatibility. 4 G' j, A) a) _! @3 B3 I7 W* W- |- N
Program Enhancements 7 g6 H, F$ J/ V# S. [. _! s
The following program enhancements appear in PSS®E-31.1.0: 9 D) y2 O1 Q( z3 g1 S' i8 p0 W
 Addition of the remaining three Generic Wind model types. PSS®E now has support for all # ]* X# h( m; p- j( T8 y8 xfour industry-defined Generic Wind Models. Please review additional documentation / H* p, L; s% A* M9 F$ jdelivered with this release on these models. 2 `: e6 z2 S! s Revised IEC test network sample files names from 60609 to 60909. 3 S4 G3 y4 R& i/ i Additional messages from DYRE clarifying when compilation of models is needed. 1 s% w; ^ B& V! i
 Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. 0 A7 r6 T, q9 `! i: a Added “dyntools” Python module to post process Dynamics simulation channel file output : \' Q" |7 s* f& w) E/ G5 `) R(*.out). Details of available functions can be accessed using help(dyntools) in the Command 1 s% D7 S; n6 H2 [0 S5 q4 B- X
Line Input dialog. " n! x) @* e. ~9 q$ M1 E
Program Corrections , m; ]. R3 G; C: x
The following program errors have been detected and corrected in PSS®E-31.1.0: - G/ V9 Q6 g+ }! f* _ Improved handling of Line Relay models in the GUI. 3 O E1 B4 K- N( @. o Fixed general issues with bus subsystem definition. / `4 ~! q* n$ L: f- s( W
 Fixed an issue where Diagram items weren’t being properly identified. ; z3 b. _, U+ Y0 j3 Y Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was 7 s" ~. R; o2 _/ x; b9 U+ X$ Ebeing set inadvertently. 4 ~! {6 X. l; d' R
 Fixed an issue where the program would crash if the user attempted to define a bus 2 W! r b( _/ `! t( Fsubsystem from a context-click in the Diagram. ! p; E4 G2 O- f+ E; Q
 Fixed an issue where the program would crash if the user selected two knee-points in the , D$ |$ c- L5 A) b; GDiagram and then did a context-click. d8 z: Y+ J3 z! b: {5 \3 _ j Various other corrections. Siemens Energy, Inc. ) S. _' j, o* {" b) X; Y1 K. Q, A3 LRelease Notes for PSS®E-31.1.0 Siemens Power Technologies International H$ {3 Q' F) D C- l$ J " ]2 b& i& o# d. E' C
. O6 [5 D/ W J/ G- s) z4 M
2 1/9/2009 6 O& _6 U B. f& dCompiler Information ! I+ _1 H# ^4 M0 s/ E- ?& YGeneral Information 1 P5 a. C7 v' S8 T2 B
PSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. $ U6 C. L1 b: a) q
User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or & e' c& O! }; d9 z9 q
programs that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the : u9 R) m8 l( O! D( E4 ~10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing . M; N3 \0 Q2 j1 R4 e/ M
code from different compiler versions. 7 J |" \5 O$ ^, E+ Q! |
Additional Notes , V& u6 Q1 l* S7 L" m4 z" f
** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and 3 t4 J" F2 Z5 V4 OC run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a . B+ Z0 Z5 K5 {8 g; X* fcompiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, 8 B. g( R5 Z. ^or programs that call USRCAS. 9 Q3 q7 K3 I3 O# T7 N3 ?Intel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take , ~' J0 Q8 b8 S7 L) G6 _advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler ! _8 I1 h- S" N7 G, f8 ]license. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under - {$ |* M/ V; P3 N% W t
this offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that 5 ?4 v9 x5 N* J/ F0 I1 s"Siemens PTI customer" is stated in the subject line. $ u$ v1 b0 w5 u3 A/ |. oUser-Written Model Notes. W4 y+ \ k5 ^; K
PSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead + `4 G$ p& B9 S0 ?1 z, O& Gof numbers. To retain backward compatibility of old Saved Case files, device names are now set to # _% W7 `7 |) e2 P/ x9 \
the old device number, left justified. For example, 1 becomes “1 “. However, User-Written ( d9 i( T3 l7 w
models of these devices that are called in conec.flx and conet.flx will have to be modified to map ( T& e1 F& v* t b+ b, V/ j/ @
the old device number to its corresponding new internal device index. Please contact PSS®E * [. |3 r. p |) T# Osupport if you have any questions on how to proceed with this. ; z; f7 B+ E% g/ D$ E X* ]2 C
In addition, during the course of our in-house development and testing, we have noticed that the 3 |0 C" O! @( G6 W( c
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran ; I5 h% g2 D+ B& ?when compiled with the CVF compiler would crash when compiled with the IVF compiler. When x. l6 g/ n9 X4 R3 h0 ccompiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, 1 ?( D E9 ^/ |' `and consider compiling your code with some of the more advanced debugging and verification 9 g h Q- z. z/ E [7 K4 I" h. A
features of the IVF compiler.