Dear STKO Team,
First, I want to express my gratitude for your support and assistance on this forum.
Recently, I've been attempting to run several analyses on a different processor in my computer (using a different set of GMs on a separate processor). The analysis appears to proceed correctly, but when it reaches 100% completion, it takes around 35 minutes, and I notice the processor is terminating as shown in the attached picture. However, some processor do not terminate even after waiting an additional hour or even more .
Assuming the analysis is complete, I close PowerShell, but when I check the output file, I find missing information, as illustrated in the next picture.
I've tried this on several computers but encounter the same issue.
I am uploading the model I am using for your reference.
Waiting for your kind reply,
Processor Takes too long to Terminate !
Re: Processor Takes too long to Terminate !
Dear STKO Team,
This is nothing , but kind reminder .
This is nothing , but kind reminder .
Re: Processor Takes too long to Terminate !
The problem is that those other processor are not finished yet.
You are not seeing the text on the command line just because it is written only for the process 0,
But as you can see from this message:
some processes are much longer in duration than others, for example process 2 has a duration of 85 seconds, almost 10 times more than the shortest ones. You just have to wait
You are not seeing the text on the command line just because it is written only for the process 0,
But as you can see from this message:
Code: Select all
Override duration @0 : 9.41
Override duration @1 : 7.92
Override duration @6 : 6.57
Override duration @7 : 19.79
Override duration @5 : 49.49
Override duration @4 : 40.74
Override duration @2 : 85.43
Override duration @3 : 9.0
Re: Processor Takes too long to Terminate !
Thank you for your response, STKO team.
It's clear to me now how things work, but in my case, the process is taking several hours, not 85 seconds. Did you try running my given model on your PC?
To clarify, after the analysis finishes and PowerShell shows 100%, I still have to wait for several hours. If I interrupt the process, I end up with files containing missing data.
Can i make a comment , like when all the processors are finished , i get a message a following message " ALL processors are done "
It's clear to me now how things work, but in my case, the process is taking several hours, not 85 seconds. Did you try running my given model on your PC?
To clarify, after the analysis finishes and PowerShell shows 100%, I still have to wait for several hours. If I interrupt the process, I end up with files containing missing data.
Can i make a comment , like when all the processors are finished , i get a message a following message " ALL processors are done "
Re: Processor Takes too long to Terminate !
Sorry you misunderstood what i meant.
I was referring to the duration of the ground motion (not the duration of the solution of the analysis):
If these processors take 1 hour to run about 10 seconds of analyses,
Override duration @0 : 9.41
Override duration @1 : 7.92
Override duration @6 : 6.57
Override duration @3 : 9.0
These will take 10 hours...
Override duration @7 : 19.79
Override duration @5 : 49.49
Override duration @4 : 40.74
Override duration @2 : 85.43
I was referring to the duration of the ground motion (not the duration of the solution of the analysis):
If these processors take 1 hour to run about 10 seconds of analyses,
Override duration @0 : 9.41
Override duration @1 : 7.92
Override duration @6 : 6.57
Override duration @3 : 9.0
These will take 10 hours...
Override duration @7 : 19.79
Override duration @5 : 49.49
Override duration @4 : 40.74
Override duration @2 : 85.43
As I said, the tcl script by STKO with OpenSeesMP only writes comments to the command line only from process 0, otherwise it would be a mess to see async output from all processorsTo clarify, after the analysis finishes and PowerShell shows 100%, I still have to wait for several hours. If I interrupt the process, I end up with files containing missing data.