As you say that could get quite unwieldy where a member could be designed to dozens or hundreds of load cases/combinations. I would say however, that if we were to provide a standard table as I illustrated, then we would make the data available with an OpenSTAAD function and it would be possible to create a table with a OS macro in the format you would like as others may want a similar table but also include the cause and/or parameter set. So the first stage would be to get the engine to record the data for each load case not just report the governing result case. This idea has been added to the backlog.
Sounds like you've thought about this. That might work but I was thinking more of putting them in order from highest to lowest for each member. Here's an example.
Highest SR's for each member
Next Highest
etc.
Beam
L/C
Stress Ratio
L/C
Stress Ratio
L/C
Stress Ratio
1
25
0.89
32
0.82
20
0.75
2
25
0.75
18
0.71
35
0.68
3
18
0.93
25
0.86
16
0.83
Of course, if you have dozens of load cases it would get unwieldy. Maybe just show the top 5 or 10. You could eliminate the member properties columns to make more room. An even better idea may be to store the information for each load case and let the user display it as he wants.
Thank you for posting your idea. I assume that the idea is that there is a method provided where it is possible to obtain the critical ratio for each load case that a member has been designed too and the clause that governed for that case. In other words this information for 3 members designed in 2 sets, one with 3 load cases 1to3 and the second designed for load cases 10 and 11:-
As you say that could get quite unwieldy where a member could be designed to dozens or hundreds of load cases/combinations. I would say however, that if we were to provide a standard table as I illustrated, then we would make the data available with an OpenSTAAD function and it would be possible to create a table with a OS macro in the format you would like as others may want a similar table but also include the cause and/or parameter set. So the first stage would be to get the engine to record the data for each load case not just report the governing result case. This idea has been added to the backlog.
Sounds like you've thought about this. That might work but I was thinking more of putting them in order from highest to lowest for each member. Here's an example.
Highest SR's for each member
Next Highest
etc.
Beam
L/C
Stress Ratio
L/C
Stress Ratio
L/C
Stress Ratio
1
25
0.89
32
0.82
20
0.75
2
25
0.75
18
0.71
35
0.68
3
18
0.93
25
0.86
16
0.83
Of course, if you have dozens of load cases it would get unwieldy. Maybe just show the top 5 or 10. You could eliminate the member properties columns to make more room. An even better idea may be to store the information for each load case and let the user display it as he wants.
Thank you for posting your idea. I assume that the idea is that there is a method provided where it is possible to obtain the critical ratio for each load case that a member has been designed too and the clause that governed for that case. In other words this information for 3 members designed in 2 sets, one with 3 load cases 1to3 and the second designed for load cases 10 and 11:-
Beam
Set
L/C
Clause
Actual Ratio
1
1
1
Eq.H1-3a(H1
0.610
1
1
2
Eq.H1-3a(H1
0.411
1
1
3
Eq.H1-1b
0.387
1
2
10
Eq.H1-1b
0.538
1
2
11
Eq.H1-1b
0.735
2
1
1
Eq.H1-1b
0.749
2
1
2
Eq.H1-1b
0.711
2
1
3
Eq.H1-3a(H1
0.398
2
2
10
Eq.H1-3a(H1
0.378
2
2
11
Eq.H1-3a(H1
0.476
3
1
1
Eq.H1-3a(H1
0.476
3
1
2
Eq.H1-3a(H1
0.385
3
1
3
Eq.H1-3a(H1
0.600
3
2
10
Eq.H2-1
0.242
3
2
11
Eq.H2-1
0.096
3
1
1
Eq.H2-1
0.407
3
1
2
Eq.H2-1
0.397
3
1
3
Eq.H2-1
0.284
3
2
10
Eq.H2-1
0.114
3
2
11
Eq.H2-1
0.334