ERROR 33238: Not enough memory available on the hard disk for an out-of-core file
When I run my model with the default solver (I guess it is MOM), I get an error which says 'ERROR 33238: Not enough memory available on the hard disk for an out-of-core file' though I already have 8 GB of RAM and more than 200 GB of free HDD space. However, when I switch to FDTD solver, it doesn't show up the error, but it takes a really really long time. I have attached the model to this post. Please help me what to do with this error as I haven't found any good solutions yet.
Answers
-
Hi Lostarmour
Have you tried MLFMM?
0 -
Altair Forum User said:
Hi Lostarmour
Have you tried MLFMM?
I just tired that and I have another memory related error. ERROR 32476: Not enough memory available for dynamic allocation
0 -
Could you please attach the cfx?
0 -
Altair Forum User said:
Could you please attach the cfx?
I have now. Did you mean the cfs in my case?
0 -
The cfs is the session file. The cfx is the CADFEKO model.
0 -
Altair Forum User said:
The cfs is the session file. The cfx is the CADFEKO model.
Ah sorry I couldn't find it at first. Here it is.
0 -
You can use the default solver but with 'Coarse' meshing - this is more than sufficient for plane wave incidence. Also set the mesh growth factor (mesh, advanced tab) a bit coarser since there are some very fine detail.
0 -
Altair Forum User said:
You can use the default solver but with 'Coarse' meshing - this is more than sufficient for plane wave incidence. Also set the mesh growth factor (mesh, advanced tab) a bit coarser since there are some very fine detail.
With coarse meshing, I always run into mesh error like this. I am not sure how to get rid of these and I get these all the time.
ERROR 40619: Intersecting triangles found
See also message in the output file 08262019_Feko_two_blades_V2.out
0 -
The model contains very fine geometry, and usually there are tolerance issues with imported geometry.
You could consider to remove it, else refine the mesh, but this will then again increase the resources.
On the Mesh tab, unlink the mesh and use 'Find intersecting triangles'. This will give the labels with problems.
With opacity and a cutplane you can view them. Or in POSTFEKO enter the triangle numbers (given in the ASCII OUT file) under 'Find elements' on the Mesh tab in POSTFEKO to find them as well.
<?xml version="1.0" encoding="UTF-8"?>
0 -
I removed the intersecting triangles but how can I link the same mesh back? I can only see an option which says 'Use model mesh', which is I think doesn't do exactly what I want. How can I re-link it with the Geometry?
0 -
You cannot re-link mesh.
An alternative is to fix the CAD, which would then hopefully not contain these triangles.These two videos should also be helpful when working/fixing meshes.
https://connect.altair.com/CP/kb-view.html?kb=187249
https://connect.altair.com/CP/kb-view.html?kb=187250
0 -
Hi @lostarmour,
You should make all regions PEC and then use 'Simplify'. This deletes 24 (small) redundant faces:
<?xml version="1.0" encoding="UTF-8"?>
Then I found out that these areas are the tricky parts:
I closed these two and now it works 9,072 triangles (compared to 51,554 in the original model):
It solves in a couple of minutes. Please make sure to refine the mesh slightly and compare the results. This is just an example.
0 -
Altair Forum User said:
Hi @lostarmour,
You should make all regions PEC and then use 'Simplify'. This deletes 24 (small) redundant faces:
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?> Then I found out that these areas are the tricky parts:
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?><?xml version="1.0" encoding="UTF-8"?> I closed these two and now it works 9,072 triangles (compared to 51,554 in the original model):
It solves in a couple of minutes. Please make sure to refine the mesh slightly and compare the results. This is just an example.
I Still get the error after simplifying. I made them all of one material and then applied the simplify. Then, as you said it removed 24 redundant elements and I ran it and still I ran into memory issues. I am even doing it on a cluster. And I couldn't use your file because it is built on 2019 version and I am using a 2018 version. Please help.
0 -
0
