- Collapse View
- Expand View
- Mark all as New
- Mark all as Read
- Float this IdeaStation to the Top
- Subscribe
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
Everyone knows that make proper mesh for complex geometry on the first try is impossible.
Robot makes perfect mesh, but, unfortunatelly uses only one core of CPU, so process is quite long on powerful computers.
Please, make multuthreading support for meshing and we can save a lot of precious hours :-)!
Quite long slabs on grade has irregular foundation pressure, thus they have to have irregularal elastic coefficient to calculate forces in slabs correctly.
Unfortunately, right now Robot has no capabilities to set non-constant elastic coefficient for the slabs.
Since 1 december 2011 steel code SNiP II-23-81 not used in Ukraine.
New Ukrainian RC code DBN B.2.6-98:2009 based on Eurocode 2.
Could you include an easier way to choose which analyses are performed (check boxes)...currently having to change to 'auxilliary' and then back to whatever it was previously is a bit of a pain when switching between say earthquake and footfall analyses. This would help speed up the calculation process.
I also think that editing of panels is in desperate need of updating with table input for geometry (I currently use the excel API that was posted on the forums and is a good intermediate step). Could we also limit the accuracy of geometry when setting up the model to a predefined limit (say either 1mm or 10mm...it would also be a nice feature to be able to go to 5mm)...it's a real pain when the coordinate has somehow become 18.450000023 or something.
Ta,
R
Working on my last project (it's an concrete structure, about 150 000 nodes and 170 000 FE-s) I was extremely annoyed by Robot Str 2013 general performance. For example, changing an load value is operation with time consumption not less that half of minute on quite modern hardware (core i7 etc.). Changing values in tables is not much quicker...
I understand that you can recommend to use diaphagms instead shell etc, but in general - performance of Robot is not the best one, I can say the worst one. Now it is 2013 year and yes, sometimes we have to analyse and calculate models with more than 3 bars...
Here I do not speak of calculating time, meshing time - it's only problem of general performance, for example, changing load values in large scale models. So, my Idea is to optimize code (I'm fully understand that it can take a lot of time) to make Robot works much quicker.
Problem: The table editing tools in Robot are slow and have poor functionality. Usually it is better to copy the table to Excel and edit it there, but this can cause trouble (example: planar loads on contour becoming planar loads in my experience). Besides, for small changes this should not be neccessary.
Solution: Advanced table editing module or two way link to excel for all tables. Allows quick editing of tables, making changes to the model only when the user clicks apply.
When running non-linear analysis, different combinations should be computed simultaneously in separate threads. This would make such calculation almost an order of magnitude faster.
