Looping through GM & scaling factor

[BrownTrout_NZ]

Hi STKO team

I am facing an issue with incremental dynamic analyses. When I was dealing with a single Ground Motions and various intensities, it was working perfectly as per STKO's examples with some slight modifications. I generated some python code to extract displacement history from those different intensities in a text file to draw IDA curves successfully.

Now I have implemented (looping through)different GMs on top of the intensity. The python code I edited from STKO example properly create sub folders for different intensities for a given GM, but 3 monitor pop ups show completely meaning less movement. It looks like these analyses are mixed up in the monitor. It also looks like the analysis was performed for the first GM index only. The TCL files appear to have generated correctly.

Capture 1.PNG (449.92 KiB) Viewed 2529 times

Capture5.PNG (36.79 KiB) Viewed 2529 times

Upon inspection of the PLT files, the out put is completely stuffed up with gaps etc as per below snip.

Capture3.PNG (39.58 KiB) Viewed 2529 times

I want to have one monitor each ( with roof disp history, shear vs disp and acceleration) for a given GM. so in this instance, 3 monitors each showing one GM case with different intensities much the same as when I had one GM and different intensities.

The other thing I noticed is that all analyses appear to stop at 21% without any warning. I am sure the file works as I have been verifying the parameters etc.

Capture2.PNG (130.34 KiB) Viewed 2529 times

Could someone please look into the attached files and recommend some recommendations to rectify the issue ?

Your assistance is much appreciated as usual.

1 storey base study - ductility - TH - PARAM.zip

(186.44 KiB) Downloaded 112 times

[STKO Team]

It seems that you are using incorrectly the multiple processors. I see 3 subdirs for 3 gms but I see more opensees windows

[STKO Team]

The issue was the list of working_directories being allocated outside the GM loop.
Instead it should be inside the GM loop because in the second inner loop you assume it has the size of the parameters.

Finally you should start the monitor only once, outside of the outer loop

[BrownTrout_NZ]

Wow, that is exactly what I wanted. Greatly appreciated....

[STKO Team]

You're welcome