本帖最后由 apsal 于 2009-5-9 20:04 编辑 5 F" {) b8 `4 ~) d/ i, Z, A6 V% e9 c6 b0 D* s. ?5 F9 R, }0 B% J
Important Compatibility Notes # ^1 R! ~6 @: W- U- b5 H3 J PSS®E-31 SAV files are not compatible with pre-31 versions of PSS®E. 0 P& e* f8 I! ] PSS®E-31 SNP files are not compatible with pre-31 versions of PSS®E. # I$ Y T9 P& s2 j, O
 PSS®E-31 SLD files are not compatible with pre-31 versions of PSS®E. 7 A% W2 }0 B3 ?1 ?; e9 r" oAs always, data files are always forward compatible. The above items deal with issues of " u8 X" E/ Y, F$ I9 d
backwards compatibility. # g& e, r ?: G3 }8 e
Program Enhancements 3 N4 \, n" }' W2 i: v, V
The following program enhancements appear in PSS®E-31.1.0: 9 h4 v) I4 z: X
 Addition of the remaining three Generic Wind model types. PSS®E now has support for all 5 J3 d" b/ O, }0 U& @8 F5 u% R
four industry-defined Generic Wind Models. Please review additional documentation 2 X- T0 A' V2 Xdelivered with this release on these models. - j8 g+ d, J" \( z( P h Revised IEC test network sample files names from 60609 to 60909. ; I! @( ~, c) b7 f6 y Additional messages from DYRE clarifying when compilation of models is needed. 6 u& x4 p8 ]1 u3 _# J2 U( _ Added additional Dynamics models in the PSLF->PSS®E Dynamics converter program. 9 y& G; W) h6 f' x: Q6 D+ c Added “dyntools” Python module to post process Dynamics simulation channel file output - K/ g- u5 s" v! m) q, E" u(*.out). Details of available functions can be accessed using help(dyntools) in the Command % h9 x8 V4 T+ j5 a
Line Input dialog. 7 A% ?# ^0 C$ x4 d8 Y; MProgram Corrections 3 ` b5 B7 T# F0 k; T6 z
The following program errors have been detected and corrected in PSS®E-31.1.0: 7 m1 i% K) ^! d+ @5 {9 W( U% g
 Improved handling of Line Relay models in the GUI. h9 i) D. ?& q3 ^' o Fixed general issues with bus subsystem definition. 7 f. s9 }: h+ q1 N4 a Fixed an issue where Diagram items weren’t being properly identified. r: {) h3 ^9 i a, { Fixed an error in the two-winding transformer spreadsheet where the Auto-Adjust flag was # G7 x3 r/ k; bbeing set inadvertently. / V/ x/ v, X9 i: `0 d: w Fixed an issue where the program would crash if the user attempted to define a bus ( b3 b/ v( A) c. K4 n9 j Esubsystem from a context-click in the Diagram. $ F( R* L: D- c. b; A Fixed an issue where the program would crash if the user selected two knee-points in the % H- m- q5 B' P3 f* SDiagram and then did a context-click. 3 e R" g5 J( @; ~8 F
 Various other corrections. Siemens Energy, Inc. " X( I1 {) y1 v+ G' I* f+ X
Release Notes for PSS®E-31.1.0 Siemens Power Technologies International 4 u8 R" l1 R9 A$ z 6 m, t1 _) b- r: Z& p* C5 i 0 H. L9 e" } h$ v# z2 1/9/2009 / B) n5 ~3 t+ Z& _; Q8 g7 m9 c+ }
Compiler Information ) u( j; R" G, v& h* cGeneral Information 2 B& A0 |' f$ W$ M% YPSS®E-31 and all future planned releases use the Intel Visual FORTRAN (IVF) compiler. : |, @& @! ]9 c1 N; GUser-written software used with PSS®E-31 (e.g. Conec, Conet, user-written dynamics models, or ; T0 \% K0 ~% z+ y( h
programs that call USRCAS) must be compiled with Intel Visual FORTRAN (IVF) 9.1 or later (the : n' `' A1 _2 B1 }. D
10.1 compiler is recommended). PTI cannot provide support for problems that arise when mixing * }% l, K* \/ q8 K c N4 Pcode from different compiler versions. 5 U# W" k/ s8 m0 A: XAdditional Notes - F, X/ z3 n( q) t8 b$ x+ `/ {** Please note that purchase of the compilers is not necessary to run PSS®E. The FORTRAN and 8 H/ L! K+ C7 y* d2 m) e; K5 @& _
C run-time libraries will continue to be included with PSS®E, as in the past. The purchase of a $ b2 {6 _. y% d8 }5 i& C
compiler is required only if you are compiling Conec and/or Conet, user-written dynamics models, , F+ k A5 X1 M6 ~- T* E5 D0 j1 \or programs that call USRCAS. 2 W' q, b! K7 CIntel has offered a special discounted upgrade fee to Siemens PTI customers. In order to take ! r; o# ?: s' S
advantage of this offer, you will need to provide proof of your Compaq Visual FORTRAN compiler ; B; V5 S: u) m7 {. V& p' @" J: k8 W' \license. To purchase either the upgrade or a new license of Intel Visual FORTRAN compiler under 5 k4 |1 Q0 H, u# [this offer, you must contact Frankie Terlecki at frank.terlecki@intel.com. Please be sure that : G* f0 B+ J% n! k) \3 C
"Siemens PTI customer" is stated in the subject line. + M' M0 G. V; [/ j% { }# z% S4 ~+ B
User-Written Model Notes , X5 ^) r( ?4 GPSS®E-31 DC line and FACTS devices are now identified by 12-character devices names instead : Z% m4 K, E, \* F; d5 z
of numbers. To retain backward compatibility of old Saved Case files, device names are now set to 5 V6 I! ?; V2 \* L3 {* y9 B# Q. qthe old device number, left justified. For example, 1 becomes “1 “. However, User-Written 6 B+ W6 g! P; u! k( _: Rmodels of these devices that are called in conec.flx and conet.flx will have to be modified to map 2 r( e6 |! b" T: o" v2 C7 P. @8 U
the old device number to its corresponding new internal device index. Please contact PSS®E ) D" r# u8 h9 ]; B6 e. k
support if you have any questions on how to proceed with this. 0 P1 y& x1 J' R0 W4 x/ l% m' P5 x; PIn addition, during the course of our in-house development and testing, we have noticed that the 0 M* M# T7 v9 [" a$ r3 C& o
IVF compiler is a lot less forgiving in the area of un-initialized variables. Many times code that ran - J) N* y7 n( ^3 J1 i/ S6 ?) _& Kwhen compiled with the CVF compiler would crash when compiled with the IVF compiler. When / L U9 l' Z+ f, C
compiling your models with the IVF compiler for use with PSS®E-31, please be aware of this issue, ) d; }; R9 M! N+ X: q b* ^ t/ ?+ Land consider compiling your code with some of the more advanced debugging and verification $ s0 n& B" o# j0 U O- |features of the IVF compiler.