-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarifying sizing field #98
Comments
Any helps on this is greatly appreciated. |
I think you should consider the sizing field more of a relative value, partially because there are other factors that contribute to the actual element size like the sampling rate and the cleaving of the elements. The best way to approach manual sizing fields is probably to use Cleaver to generate one that is close to what you want, then to increase or decrease the values in the desired regions. The sizing field would have to be modified in another software. I have an example of how to do this in SCIRun, if that would help. |
Thanks for your explanations @jessdtate. I think that when we use a custom sizing field, all other options do not have thier effects anymore and the only thing that matters is the sizing field? Is this correct? |
Hello @jessdtate. I wanted to kindly remind you to send me the example that you have if it is possible for you. |
Hello,
I am using the custom sizing field option to manually determine the regions where I need fine/coarse mesh. I know that the sizing field determines the element size, but in what unit? How can I calculate the correct sizing field that leads to my desired mesh? Are the absolute values of the sizing field of different parts of a model important or their relative sizing fields values are taken into account? I still could not find the relation between the generated meshes and sizing values I give.
I think the documentation in this area is not very clear and clarifying this or introducing some useful samples/references is definitely helpful.
Thanks in advance.
The text was updated successfully, but these errors were encountered: