|
[Sponsors] |
January 14, 2015, 22:35 |
When I do transient simulation, there comes the error ,please help
|
#21 |
New Member
Chen Di
Join Date: Apr 2014
Posts: 10
Rep Power: 12 |
It says:
------------------------------------------------------------------+ | *** INSUFFICIENT CATALOGUE SIZE *** | | | | ACTION REQUIRED : Increase the file catalogue size. | | | | If the situation persists please contact the CFX Customer Helpline | | giving the following details:- | | Current catalogue size : 28960 | +--------------------------------------------------------------------+ My element number is 34 million, so I wonder if it is the huge element number that leads to the memory size problem, but it is OK in steady simulation. Please help, thanks a lot... |
|
January 15, 2015, 06:41 |
|
#22 |
Senior Member
Marcin
Join Date: May 2014
Location: Poland, Swiebodzin
Posts: 313
Rep Power: 13 |
There are many reasons of this error.
Check your mesh quality. Make these mesh more coarse. Second check your BCs |
|
January 15, 2015, 13:21 |
|
#23 |
Senior Member
Join Date: Jun 2009
Posts: 1,880
Rep Power: 33 |
In the ANSYS Solver Manager, click on the Show Advanced Controls, go to the Solver tab and click on Detailed Memory Overrides and use a multiplier for the Catalogue Size.
If using the command line, cfx5solve, please use cfx5solve -help and read the details to modify the catalogue size (-smms ?) The software failed to selecting the proper catalogue size for its memory system. Hope the above helps, |
|
September 25, 2015, 05:47 |
|
#24 |
New Member
Niels Bessemans
Join Date: Apr 2013
Posts: 12
Rep Power: 13 |
I've encountered this problem as well, increasing the catalog size will solve the problem. But I'm wondering, what's actually the 'meaning' of the catalog size? Is it related to memory somehow?
Kind regards, Niels |
|
January 5, 2016, 22:57 |
|
#25 | |||
New Member
Join Date: Jan 2016
Posts: 3
Rep Power: 10 |
Quote:
regards. Quote:
Quote:
regards. Last edited by wyldckat; January 6, 2016 at 18:41. Reason: merged posts that were a couple of hours apart |
||||
January 5, 2016, 23:07 |
|
#26 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
When CFX starts a simulation it estimates the amount of memory it will require to run and grabs that chunk of memory. For most simulations the estimation is pretty good and this causes no problems. The solver solver requires additional memory as the solution progresses and if this rises above the amount initially estimated the solver will stop with a catalog size error.
In these cases the first thing to do is to increase the catalog size, x1.2 is usually enough but if you have the memory to spare x2.0 is good. In a small number of cases this does not work - this indicates a more fundamental problem with the simulation, where function requiring memory has proven far more complex and it should be, and this invariably means a problem in that function and the problem should be fixed (rather than just allocating more memory and hoping). |
|
January 6, 2016, 21:08 |
|
#27 | |
New Member
Join Date: Jan 2016
Posts: 3
Rep Power: 10 |
Quote:
|
||
January 7, 2016, 19:36 |
|
#28 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
The large mesh will not cause the error - the memory required for meshes is easy to calculate.
But complex interfaces can cause it. If the interface is more complex than normal the built in estimation can be wrong and lead to this error. But it is also a sign that the interface might not be well formed. Check the mesh for folds, bad quality elements and other badness near the interface. |
|
January 8, 2016, 11:03 |
|
#29 | |
New Member
Join Date: Jan 2016
Posts: 3
Rep Power: 10 |
Quote:
|
||
January 10, 2016, 02:18 |
|
#30 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
It is hard to be sure but that is a strong suspect. Try make the interface consist of a smaller number of separate faces if possible.
|
|
June 7, 2016, 02:13 |
|
#31 |
New Member
Millen
Join Date: Jan 2016
Posts: 7
Rep Power: 10 |
The error isn't caused by mesh at all. Its caused by the solver detirmining how much space/ memory is required to complete all the programmed iterations. By changing the catalogue allocation/ iteration size you can allow the computer to take up more space, or reduce the amount of space required.
|
|
June 7, 2016, 22:31 |
|
#32 |
Super Moderator
Glenn Horrocks
Join Date: Mar 2009
Location: Sydney, Australia
Posts: 17,870
Rep Power: 144 |
Posts #26 and #28 explain the source of this problem. If the error in memory estimate is small you can fix it with the catalog allocation parameter, but if that is enough you have to look at where the error in the estimation comes from. In my experience it is usually from large numbers of surfaces, interfaces or bodies; or very complex interfaces. It can also come from huge amounts of CEL expressions. To fix it you need to simpilfy the mesh faces/bodies or reduce the CEL.
|
|
February 3, 2021, 04:37 |
|
#33 | |
New Member
Join Date: Jun 2017
Posts: 8
Rep Power: 9 |
Quote:
|
||
August 16, 2024, 06:09 |
|
#34 |
New Member
TGS
Join Date: May 2023
Location: United Kingdom
Posts: 29
Rep Power: 3 |
Thank you very much for your answer. Also, need to use the suffix x with the multiplier.
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[snappyHexMesh] crash sHM | H25E | OpenFOAM Meshing & Mesh Conversion | 11 | November 10, 2014 12:27 |
critical error during installation of openfoam | Fabio88 | OpenFOAM Installation | 21 | June 2, 2010 04:01 |
OF 1.6 | Ubuntu 9.10 (64bit) | GLIBCXX_3.4.11 not found | piprus | OpenFOAM Installation | 22 | February 25, 2010 14:43 |
Phase locked average in run time | panara | OpenFOAM | 2 | February 20, 2008 15:37 |
fluent add additional zones for the mesh file | SSL | FLUENT | 2 | January 26, 2008 12:55 |