Table results - the powerful mate to deal with result numbers
What the 'Table results' is?
The 'Table results' is pretty new GUI (Graphical User Interface) component helping user to deal with the results of calculations and checks in the numerical form using several interactive tools.
First version of Table results was introduced back in SCIA Engineer 14. Nevertheless, since then it is under continuous improvement development.
What is it good for?
Basically, the result of calculations on the model defined in SCIA Engineer is numbers having some meaning in the discrete geometrical points. In some cases there may be many dozens of thousands of numbers placed across the whole model and it is challenge for users to work effectively with such a large number of values. But these numbers are the core business of most of our clients. Therefore we bring you the interactive tool to deal with numerical results.
Why should I use it?
Most of our users are used to work with the 'Preview' window to see the results in the numerical form. This window gives user the view how the results will look on the paper. But, is that really necessary to know how the results will look on the paper during the modelling, checking of results, model optimisation and design? No. During this time you need the interactive tool offering you possibility to have numbers in your hand rather than seeing how they will look on the paper.
List of features is boring. If you're interested, read help. Let's rather share some stories with Table results features in action...
1) Show me places, where ...
Engineer Jack Johnson is watching the plot of 2D stresses result on his structure of arch bridge. He see the isobands in the 3D window and the numerical view in the Table results. He just wants to see in which places within the model the both sigma_x and sigma_y stress are bigger than zero and thus there is tension in both directions. He feels he gets lost...
After a while Jack realizes that recently he has read about new Table result feature 'section highlight'. This feature offers him to show the sign in the 3D window showing the exact geometrical position of some row in Table results. Jack just switches on the 'filtering row' and filter the whole long table to show only rows where the sigma_x > 0 AND sigma_y > 0. When the table is filtered, Jack just selects all remaining rows and using the context menu place the symbols. Now he see the model with several symbols placed to positions where both sigma_x and sigma_y stresses are bigger than zero.
2) Where have these strange results came from???
Engineer John Jackson is checking the results of reinforcement design of concrete office building. He is listing through the long table with many values representing the amount of reinforcement designed by Scia Engineer in every section of every beam in the structure. Beside that he has the rough estimations on the paper coming from his hand calculations. He is going through beams one by one and suddenly he see the number that is totally different to his hand calculation. He starts doubting the results coming from Scia Engineer because he see only the final value of reinforcement area but there is no intermediate calculation - this is the reason why he rather trust himself than the software.
John remembers the new Table result feature - 'detailed output on double-click'. In Table results he just double-clicks the cell containing suspicious value and the old print preview windows is opened with the detailed output containing all the equations with symbols, with substituted numbers and intermediate results. Now he can go through formulas one by one and compare intermediate results with his own hand calculations. Of course, he finally finds the mistake in his calculations - he forgot to add the diameter of the stirrup to the cover of the main reinforcement. Happy ending - 'detailed output on doubleclick' restored his trust in the Scia Engineer reinforcement design and today he will sleep well assured that buildings already designed by Scia Engineer won't collapse.
3) Optimisation, optimisation, optimisation ...
Bridge engineer H. Simpson is designing the new concrete slab bridge. He is in the early stage of the project and he's trying to choose the most effective height of the bridge slab so that costs for reinforcement and concrete will be as low as possible. He has already defined the model and now his procedure looks like:
1) change the thickness of the slab;
2) perform new FEM analysis;
3) go to the concrete service;
4) select correct properties and run the 2D reinforcement design;
5) note the slab thickness and the weight of the designed reinforcement;
6) going to the SLS check and see whether designed reinforcement fulfils the check;
7) Go to reactions and check whether reactions can be transferred to the subsoil...
He is getting little bit bored of repeating this long procedure again and again...
Mr. Simpson is basically interested only in few numbers that may told him whether the chosen thickness is safe and cost-effective. Until now he had to switch between Concrete and Results service, switch between particular checks, set correct properties... Now in Table results he can place several results into several tabs. Each particular tab containing result of some check becomes out-dated after the change of slab thickness. But each particular out-dated tab can be refreshed after new FEM analysis. To sum it up, now the Mr. Simpson can have all the interesting values important for his cost-evaluation placed on one place - in Table results. After each new calculation he just refresh outdated tabs, read the values and continue with next iteration.That will save him lots of time.
4) Output on first side, input on the second side
Two colleagues Mike and Carl are working on the same project of the office building with underground garage. Mike will design the overground part, Carl will take the overground part. When Mike finishes the model of overground part of the building, one of the outputs from model are reactions. On the other side, the reactions from the overground part are the input for Carl's model of underground part. Now they see the problem - how to take the reactions from one model and input them as load in another model?
The Table input and Table results have solution for this issue. Mike will just display reactions in Table results and easily copy&paste them into Excel for particular load-cases and sends the spreadsheet to Carl.
Carl prepares the model of the underground part. When he is defining load, we will just copy&paste reactions from spreadsheet into Table input as load from overground part of the structure. That's it.
Yes, we know that Table results is not perfect. We are aware of some weak spots and there may be others we do not even know about. But we're working hard on it to offer you the solution for reaching the goals regarding numerical results in the most direct and efficient way.
Do you have your own stories? Did the Table results help you in some situation? Do you have some work-flow regarding numerical results that may be covered using Table results? Get in touch at firstname.lastname@example.org or email@example.com.