Andrew Thibeault

Update on issue described above: I've determined the source of my problem with PSTCalc at least. In all my test cases I had a monitor in mode 4 (flicker). Whenever attempting to show or plot the monitor, I get the error: "Error 671 Reported From OpenDSS Intrinsic Function: Cannot close Monitor stream. Error Description: Floating point division by zero" I'm guessing that this is also the source of the errors I'm getting as described here, as I get the same error message in all cases where I read mode...

Understood, thanks Roger.

Is there any way to report bugs so that they doesn't get lost in the forum?

Hm, what I've found initially is troublesome: Running PstCalc while keeping my voltage array constant, and changing the dt parameter to values other than 1 second, doesn't change anything with the result. Even the length of the result array is the same. Feeding in a 86400 pt voltage array with a dt of 1 s, results in 143 pst values ( I think not 144 as I would initially expect as it seems like some time is cut off in the initialization of PstCalc ). Using the same 86400 pt array with a dt of .1 s,...

I want to clarify a point on this thread. Roger stated Basically, you will need to run is small time steps of 1 s or so. Then you do have to run for at least 10 minutes. There is an error because it is approximating the time domain waveform from rms solutions. It will assume the voltage is constant for 1 s, for example. This means that if I have load data with resolution finer than 1s, and I run my simulation at that resolution, the calculation will assume voltage is constant for that resolution...

Comparing the outputs of a monitor in mode 1 and a monitor in mode 4: Mode 1: hour t(sec) V1 VAngle1 V2 VAngle2 V3 VAngle3 etc. 0 1 276.143 -30.0397 276.143 -150.04 276.143 89.9603 etc. 0 2 276.143 -30.0397 276.143 -150.04 276.143 89.9603 etc. Mode 4: hour t(sec) Flk1 Pst1 Flk2 Pst2 Flk3 Pst3 0 1 276.143 -30.0397 276.143 -150.04 276.143 89.9603 0 2 276.143 -30.0397 276.143 -150.04 276.143 89.9603 The flicker monitor is outputing rms voltage and angle for each phase rather than instantaneous and short...

I have been struggling with this same issue. With the daily solution mode resolution finer than that of my loadshape, and loadshape interval>0 (hour not defined), the power at my load starts at the final value in my loadshape, then jumps to the first value after half the loadshape interval. The remaining load values are implemented at the expected interval defined in the loadshape. This issue is fixed if I set interval=0 and define hour array, so I guess that's how I'll be defining loadshapes from...