如题, ]$ o3 N! P/ \8 W, p/ d p$ G
You lose, fella. The EMTP logic has detected an error condition, and is now going to terminate program execution. The following % b! z& L. P: e2 n9 ?$ K0 rmessage summarizes the circumstances leading to this situation. Where an otherwise-unidentified data card is referred to, or where & X, }4 H" w6 {1 ^, Z$ wthe "last" card is mentioned, it is the most recently read card of the input data that is meant. The 80-column image of this card : R* X9 y a, S7 \4 {: Jis generally the last one printed out prior to this termination message. But possibly this last-read card has not yet been ' {# m0 ]$ n4 a: Vdisplayed, so a copy follows: 2 q6 w8 [: Q! G+ i8 {4 E " " - ]/ U ^$ G$ Z6 Z, G" {5 ]: e KILL code number Overlay number Nearby statement number 6 V; L. q- X+ g- j4 s* F, p K 36 2 2254 " c8 u( q7 Z8 Q; {4 I! D- ~KILL = 36. Loops in TACS supplemental variables or devices have been observed for this data case, and they are illegal. A/ w7 _) Y" g( @2 Q' M* |9 y
tabulation of such looped blocks will be found immediately preceding the "/ERROR/ERROR/...." line that presaged the present error2 e$ Z) {; s* i
text. The common remedy is to add one zero-th order s-block to break each such loop, thereby decoupling the nonlinearities. An / b% {' K9 i* o9 f8 g1 d: d( C' Hanalogy can be made to the addition of distributed lines to decouple nonlinear elements.