Debugging a Model.

The ill-condition error is the one we dread the most. One which can take days to solve, if we ever find it. Now I won't be able to help you with clearing this particular error at a snap. There are certain modelling techniques I follow to ensure an error free model.

While modelling the structure, connecting all the elements node to node is a must. This is an FEA software, you need the transfer of reactions whether it be loads, deflection or moments. As per my experience in RC structures, most of the errors/warnings can be solved through this. Minimize use of the option of all floors or use with caution. It helps when others work on your model too.

There goes the modelling basics, now let's get to the part of debugging. There are various kinds of errors, I might not remember all of it while I am writing this blog but I will try to answer the best I can.


Well for starters, standard solver would be the best. Although it takes much longer to analyse, it does give the error locations. You can set one load case to reduce the duration. 

At times, the standard solver is not of much help either. It gives non-existent coordinates, or one which really doesn't make any sense. My blog is particularly for this kind: 

  • Run the model. Check the type of error. One can get away just by knowing the different kinds of error, it requires experience though. 
  1. One example is, a mass source error usually associates with the diaphragm assignment. 
  2. The ~___ in the image below indicates a meshing error.

Notice the ~ in the labels.

  • Check the deflection animation. This will give you the anomaly in the model. Go for this first, rather than the standard solver. It will save time. An unconnected/orphan element will always displace differently, always.
  • An Eigen modal analysis is helpful too. You can check the contribution of each modes and figure out the anomaly. CSI recommends a dozen modes should be enough.
It might happen that the above doesn't help you either. I follow certain steps for it too.

  • Export the model as an e2k/f2k file for ETABS/SAFE. Import it back again. I don't really get why this helps but I guess it has something to do with the cache thing.
  • Delete portions of the model and run. Suppose you have a X story building. Run the base floors first, one at a time by deleting the other floors, till the top floor. This can get tricky and frustrating.
I once created a model with basement walls. And some portions of the wall (I had meshed it manually) had tension (FZ) reactions at the joints. A senior boss helped me figure it out. All the other sections were deleted and we worked only on that particular area. After many iterations, it was found to be a software issue. Re-modelling the walls and meshing it again was just fine.

So yeah, it does happen at times. And we have to figure it out as an Engineer.

Bonus point : Use Multi-threaded solver to check if your model has errors. It takes less time. Some errors can be found only after the analysis. For errors which show after creating an analysis model, just cancel the analysis and you can find the errors.


I will probably keep updating this blog as I learn more debugging techniques.

Comments

Popular posts from this blog

Ritz and Eigen.

Modifiers.

Slab On Grade in ETABS.