Dynamic simulation has more D-STATE errors the second time it is run

asked 2024-08-21 00:27:21 -0600

Tassie Dave gravatar image

updated 2024-08-21 00:30:52 -0600

I have a normal dynamics case, (from the Australian NEM) with a dyr file, a .sav file and a set of dlls. I followed the normal dynamics simulation process, ( load the sav case, convert, load the dlls, start and run). I got 4 DSTATE warnings, which is OK. Then I re-load the .sav case, and follow the same process. But this time there are 44 D-STATE warnings. Also some of the the machine initial conditions are a little different the second time around. WTF??

  • How did PSSE know I was running the second time (how did it keep a state in its memory) since I have initialised PSSE, re-loaded the save case and ran psspy.start() a second time?
  • Are there any issue with re-loading dll files?
  • Does anyone know why PSSE messes up the names of the dll files sometimes(in the progress file, look for 'ibrary added')

Thanks for your ideas!

On this link you can find the python script I used, and the two progress output files

edit retag flag offensive close merge delete

Comments

A1: It might be not correctly redo the initialization then the progress still run on the same file. A2: I think there are no issue with re-loading dll, by my experience. The other questions I 'm not familiar with that, sorry.

YKC gravatar imageYKC ( 2024-08-21 20:16:19 -0600 )edit
add a comment