% ~% K) Y: k6 h* c& }" _1 Z" aImportant Compatibility Notes t4 V' f" K6 x$ b PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. 4 u0 l# s5 }# `; z; ^9 p- p3 T PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. ! U+ v- G0 F+ \- G' i. F J9 e, n PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. 6 F/ O h! W2 H; o# c, V( ^As always, data files are always forward compatible. The above items deal with issues of 3 J) j0 w0 Z0 } x1 E ~
backwards compatibility. 3 x% u$ }, e: L' l& lProgram Enhancements M4 K1 N- g3 f v3 J: A
The following program enhancements appear in PSS®E-31.1.0: + U* K' L5 q3 B& E Addition of the remaining three Generic Wind model types. PSS®E now has support for all - U/ ^. K/ B+ M! o( r
four industry-defined Generic Wind Models. Please review additional documentation & a8 F" Y7 g( J2 s' a1 h, j# b* ~) ~delivered with this release on these models. 5 Y: |2 s, |% Q Revised IEC test network sample files names from 60609 to 60909. G! a* z. N) y/ o8 W9 Y" N
 Additional messages from DYRE clarifying when compilation of models is needed. ) p1 u: a, ]" r
 Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. % O/ G8 h" p g" ~8 o* a
 Added “dyntools” Python module to post process Dynamics simulation channel file output 8 h8 P2 v! E* @, Z7 d p: [- F4 [(*.out). Details of available functions can be accessed using help(dyntools) in the Command 8 K; h* J- }! h. P1 Y
Line Input dialog. ) w5 B1 r7 y" OProgram Corrections 2 @1 l+ V: e) @# d/ y6 iThe following program errors have been detected and corrected in PSS®E-31.1.0: 7 ~: X5 f7 i9 y5 c. y- E1 d
 Improved handling of Line Relay models in the GUI. 9 q( @& Z/ K( } Fixed general issues with bus subsystem definition. 2 M' E# ^1 l" i2 Z) M' X Fixed an issue where Diagram items weren’t being properly identified. 7 y7 b% d% s; L4 z G5 u. ? Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was % R6 f* \/ c. ?' b
being set inadvertently. * r3 w u9 f: c' | Fixed an issue where the program would crash if the user attempted to define a bus 6 d- F O# q$ f. S; n* vsubsystem from a context-click in the Diagram. " w, K/ u: o0 x4 w. @9 U/ |8 z
 Fixed an issue where the program would crash if the user selected two knee-points in the 2 f+ U3 j+ `- ~Diagram and then did a context-click. : b0 h; Y7 Z8 I) _' g% W3 C7 ?
 Various other corrections. Siemens Energy, Inc. w2 b+ i8 S" {Release Notes for PSS®E-31.1.0 Siemens Power Technologies International . R7 d1 M$ S7 t1 E" z7 w* c7 [+ U ( o' L# }# n' u & ^% K! O" z0 K, `) [4 A2 `* Q
2 1/9/2009 + ]$ @7 f! \& d! V& W) R
Compiler Information ( c1 q( i1 ?6 }: ?5 TGeneral Information , p7 J1 }6 d% j& p0 W( x4 f( [PSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. " r! I' }9 K1 v& H7 u
User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or / @ H* \6 C y0 v" m
programs that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the ?. X4 N4 k9 J; m10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing 0 l7 }% A$ _7 m+ D( v
code from different compiler versions. # ^; ` A$ R: j5 c
Additional Notes ' O8 v/ g0 I4 d5 M** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and 7 w8 K# a7 ^1 Q- c7 Y
C run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a 4 Z. L9 m& a# W" o2 j# `compiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, 1 T& D0 V, Z& ^" }0 Hor programs that call USRCAS. 1 u& k* }( Y5 v8 \) }8 _
Intel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take # e0 j, g5 V. @ M; V
advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler # q! F' o p6 D, ]2 rlicense. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under - _; |$ c% X$ {( ]this offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that " D% ~$ _, E9 k c0 R2 {. m5 c"Siemens PTI customer" is stated in the subject line. 7 B; c. F/ z3 G! t, p. PUser-Written Model Notes5 o3 d- X5 \+ }& ~0 z/ X& l8 o
PSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead 4 ^$ ?$ t% [# H, H2 w4 C0 L
of numbers. To retain backward compatibility of old Saved Case files, device names are now set to ) k9 }3 r/ i4 r2 N: othe old device number, left justified. For example, 1 becomes “1 “. However, User-Written 5 c0 }. W; I; [* m* y) I% Dmodels of these devices that are called in conec.flx and conet.flx will have to be modified to map 7 G# L$ W3 N" n9 O# p0 `1 ~: R: |
the old device number to its corresponding new internal device index. Please contact PSS®E " `: @: B; A( b9 X, [# C7 Msupport if you have any questions on how to proceed with this. ( @3 I5 \) [9 o0 [: X
In addition, during the course of our in-house development and testing, we have noticed that the 9 U2 N @/ a4 Y
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran 9 `8 o, w! ^! A2 _+ ~8 h7 Y
when compiled with the CVF compiler would crash when compiled with the IVF compiler. When . x5 r3 x. X! Y2 N+ Kcompiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, ; m% M0 p/ j- h: V7 yand consider compiling your code with some of the more advanced debugging and verification 2 I& Q T5 W( c9 w9 Kfeatures of the IVF compiler.