SAFE not considering opening in punching calculation when the opening is near the face of column.

[M_U]

I have a small opening which is at the face of the column. While calculating punching shear the software is not reducing the punching perimeter. The size of column is 24" x24". The slab is 8" thick. and the opening is 8"x8". I have attached the screenshots.
Does any have idea about this problem?

 

[bones206]

This is from the SAFE manual :

 

[M_U]

I have seen this in the manual. But I am confused why the software is not considering the opening just at the face of the column. As I move the opening away from the face of column around "d" distance, it starts considering the opening and reduces the punching perimeter.

 

[structSU10]

when the opening is near the face of the column does it cross over the critical section? If it is less than d it does not cross the critical section that is being analyzed.

 

[M_U]

Yes, the opening crosses the critical section. As the slab is 8" thick and the opening is 8"x8". It is crossing the critical section.

 

[bones206]

It might be a bug in the algorithm. You would expect it to be subtracting about 10” or so from the perimeter, right?

 

[M_U]

Yes, I am expecting from the software to reduce the perimeter by the width of the opening which is 8". But it is not reducing.

 

[bookowski]

SAFE is terrible at recognizing openings. It gets it wrong 1/2 the time. You have to check the perimeter for every column to make sure. Often if you move your opening by a tiny amount, say 0.05, it will recognize it. You can manually define the perimeter but the interface is terrible, better off to create your own spreadsheet and dump the safe data.

 

[M_U]

Thanks for the suggestions. I will use Spreadsheet for now. I hope in the latest versions they correct this issue.

 

[Celt83]

@M_U:
Make sure you issue a support ticket with them for this issue, if they don't get enough folks reporting it as an issue it may not be deemed critical enough to correct in the next update cycle.

 

[bookowski]

safe has had this bug since v12, i have corresponded probably 50x about it. i would not put money on them fixing it.