$ c9 K! }+ F1 ZImportant Compatibility Notes # K0 _- H) |/ N3 e' T/ \) Y" \ PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. ' G. V# T) O% i+ ?. N" s
 PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. 7 r A- J7 e. T. A
 PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. ' C% N X5 ^. v" T2 w+ Q, y/ X
As always, data files are always forward compatible. The above items deal with issues of * @+ E: F* \. g: u+ T/ g0 B$ U2 t( A2 w
backwards compatibility. d& b5 a G: J: C5 Y
Program Enhancements ! A4 R/ N0 P) _The following program enhancements appear in PSS®E-31.1.0: $ x+ _8 V4 D; H9 | Addition of the remaining three Generic Wind model types. PSS®E now has support for all 3 N+ v, D$ j: ?8 Zfour industry-defined Generic Wind Models. Please review additional documentation 9 ^/ N7 Q; `. q6 f; v+ F3 _
delivered with this release on these models. 2 _6 V& w5 m/ h1 J+ l f7 w t6 l* A
 Revised IEC test network sample files names from 60609 to 60909. , ?$ V! J- s5 I, P+ P% f# {3 w
 Additional messages from DYRE clarifying when compilation of models is needed. ! F. ~9 E. Y+ D: }% n
 Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. & Z- k9 q" C g$ P/ E5 B' D
 Added “dyntools” Python module to post process Dynamics simulation channel file output 8 B2 r( p% l: T4 W, {, I; X5 @' u
(*.out). Details of available functions can be accessed using help(dyntools) in the Command 0 j4 W! p0 O% N' g# @4 H- P
Line Input dialog. 0 \! q W1 B+ aProgram Corrections $ m7 e+ u+ ^; g0 G: o( _
The following program errors have been detected and corrected in PSS®E-31.1.0: ; H, O# G4 P) y! t; M
 Improved handling of Line Relay models in the GUI. ' z: W# R2 C3 O! w5 a2 a Fixed general issues with bus subsystem definition. + s6 u6 r D$ ]) p! k& w) H Fixed an issue where Diagram items weren’t being properly identified. 7 w6 F) N4 S! ? ` j O _& P# `# x
 Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was 3 B7 Y! X5 w) J6 k' J' {
being set inadvertently. ; }/ {( O6 Z2 j8 C: m" O7 J1 } Fixed an issue where the program would crash if the user attempted to define a bus $ @4 ]2 ^/ `$ ?
subsystem from a context-click in the Diagram. ]) T9 X6 h1 F8 G5 k* N
 Fixed an issue where the program would crash if the user selected two knee-points in the " H+ i& k2 i* w, T+ Y+ [# P* _Diagram and then did a context-click. * k' U7 A/ e: z( {9 v' m& ]
 Various other corrections. Siemens Energy, Inc. 6 K8 s+ H- `% W, @8 ?4 A/ IRelease Notes for PSS®E-31.1.0 Siemens Power Technologies International 4 X4 _% Y1 O* _; f+ b ' T6 |1 s2 J/ W" i( k
" T! l6 j5 O/ g M, v2 A
2 1/9/2009 * H) [+ Y; {. E9 l2 O" p. ^* `
Compiler Information % A" [$ ^! E: z }. y9 v
General Information 2 v2 H$ m6 g$ z3 i2 `
PSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. 7 z; { y2 k: d. b# j
User-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or 9 H# _, p: C9 ^9 x! Sprograms that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the 5 |1 [2 E8 I* ^. u e
10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing / b: ~9 ^- x2 `( i0 Q. Qcode from different compiler versions. 3 k- E3 m2 N6 K
Additional Notes B* e; {: ~# {+ L** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and * e, _$ _: Z% W. u# t* OC run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a " C! e% }- K2 Xcompiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, 4 Z* u6 U; [5 L+ [- I' h7 z
or programs that call USRCAS. ! C" X9 \5 N+ t; T2 v6 D$ Y0 m% P6 Q
Intel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take 0 J$ X9 j" g# u) g! ^% y
advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler ' F# Q* E- o: Z& Z0 slicense. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under # \, n0 }8 A9 nthis offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that - h% C2 L. w8 E' s
"Siemens PTI customer" is stated in the subject line. & W x F/ b9 T& t$ uUser-Written Model Notes ' p1 {5 |% |+ R Q# H& Z! C3 e, _2 L3 KPSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead , H3 z4 q- [* u8 n5 p- N5 oof numbers. To retain backward compatibility of old Saved Case files, device names are now set to " t7 G8 I, S, H4 |; q
the old device number, left justified. For example, 1 becomes “1 “. However, User-Written * _5 G9 ~( N8 P3 t" V, _models of these devices that are called in conec.flx and conet.flx will have to be modified to map ! M G# u# V; c. s
the old device number to its corresponding new internal device index. Please contact PSS®E 5 B4 u9 H) m" S) `
support if you have any questions on how to proceed with this. 9 H6 h) f# j/ M6 bIn addition, during the course of our in-house development and testing, we have noticed that the : L8 \7 j( i5 K
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran 0 ]+ e" _" B+ ]' F) z2 p* p6 `
when compiled with the CVF compiler would crash when compiled with the IVF compiler. When . B* @4 ~* x8 ]
compiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, + h& D* A4 {% L& B; H: Cand consider compiling your code with some of the more advanced debugging and verification ( c7 \) G: W+ \$ p3 E s+ i
features of the IVF compiler.