Revision history [back]

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 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

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 initilises 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

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 initilises 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