August 2, 2018 at 1:20 amjoepa_2017Subscriber
I am trying to manually mesh something using the LESIZE command in APDL. The documentation says that the syntax is the following:
LESIZE, NL1, SIZE, ANGSIZ, NDIV, SPACE, KFORC, LAYER1, LAYER2, KYNDIV
From what I understand, if I input a negative value for LAYER1, then the magnitude of LAYER1 should specify how many layers in the mesh have the size specified in SIZE.
For example, if I write: LESIZE, all, 0.1, , , 1, 1, -5, ,0
then I would expect that the value of -5 in LAYER1 implies that there should be 5 rows of elements with an edge size of 0.1. I am not observing this in the model. So either, I have misinterpreted the meaning of LAYER1 or I am missing something.
Any suggestions to get LAYER1 working would be appreciated. It seems like it would come in handy for my model.
August 2, 2018 at 2:33 pmjpasquerellAnsys Employee
I think multiplier means 5 * 0.1 = 0.5 so 0.5 should be used as the element size for layer 1. Is that what you are seeing?
August 2, 2018 at 7:17 pmjoepa_2017Subscriber
Maybe. However, if that is the case, why not just specify the element size to be 0.5 on the line to begin with?
August 2, 2018 at 8:10 pm
August 3, 2018 at 2:18 pmjpasquerellAnsys Employee
My initial reply was incorrect. See the test input below. It appears that setting layer2 to a non-zero value is also needed to get that type of mesh.
August 3, 2018 at 5:10 pmjoepa_2017Subscriber
The good news is that your code works as desired.
The bad news is that for some reason mine does not. I have even tried layer meshing on a very simple geometry. When I run the following code on a rectangle, I still only get 1 layer of elements that have the desired size. Here is a sample code from a simple rectangle; I don't see what would be incorrect with it:
!Define element type
August 3, 2018 at 5:22 pmjoepa_2017Subscriber
It looks like it only works when using esize rather than aesize... That's unfortunate
August 3, 2018 at 6:47 pmjoepa_2017Subscriber
Nevermind. It looks like the layer meshing works only when using esize rather than aesize. So, it is still possible to use if each area is meshed separately, and esize can be redefined between meshing each area.
- You must be logged in to reply to this topic.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- ANSYS Workbench Measuring within Design
- how to improve the inflation quality at sharp corners?
- check element type
- The mesh file exporter could not resolve cyclic dependencies in overlapping contact regions error
- How to resolve Mesh Failure
- Meshing Error
- Error in meshing
- Conformal vs Non-Conformal Mesh
- execution error inside the mesher. The process suffered an unhandled exception or ran out of memory
- inflation created stairstep mesh at some location
© 2023 Copyright ANSYS, Inc. All rights reserved.