Tetramesh Number of Layers Bug in HM2017?
Hello,
I am running into issues in HyperMesh 2017.2 getting the tetramesh number of layers parameter to force 2 full layers in narrow sections. I have tested with HyperMesh v13.0 and it behaves as expected but in 2017.2 it appears to ignore the number of layers parameter.
I've reached out to Altair support but gotten no feedback on this. Is there something else I am missing to get this working? I've attached an image showing the expected result in v13.0 compared to 2017.2.
Thanks,
Matt
<?xml version="1.0" encoding="UTF-8"?>
Answers
-
Altair Forum User said:
Hello @mblock90
It seems defect of HyperMesh2017.2.
This issue will resolve in HyperMesh 2019, I confirmed it at latest beta version.
Thanks,
ImotoDo you have any release date of Hypermesh 2019 yet?
0 -
We are public campany, so I cannot post those information to pablic space.
Please ask to our Acount Manager.
Thanks,
Imoto
0 -
I think the bug still persists in v2017.3 as well.
Q.Nguyen-Dai, were you able to find out when HW2019 might be released? My account manager said he doesn't have that info with him currently.
0 -
Altair Forum User said:
I think the bug still persists in v2017.3 as well.
Q.Nguyen-Dai, were you able to find out when HW2019 might be released? My account manager said he doesn't have that info with him currently.
Your account manager does not know. Mine neither. But Mr @Imoto knows and he does not want to talk about
/emoticons/default_tongue.png' srcset='/emoticons/tongue@2x.png 2x' title=':P' width='20' />
0 -
Altair Forum User said:
Hello,
I am running into issues in HyperMesh 2017.2 getting the tetramesh number of layers parameter to force 2 full layers in narrow sections. I have tested with HyperMesh v13.0 and it behaves as expected but in 2017.2 it appears to ignore the number of layers parameter.
I've reached out to Altair support but gotten no feedback on this. Is there something else I am missing to get this working? I've attached an image showing the expected result in v13.0 compared to 2017.2.
Thanks,
Matt
<?xml version="1.0" encoding="UTF-8"?>
Hi,
I faced this issue many times. Hm not generating properly even if we mention no.of layer in that tab.
one more thing I can suggest to get what you want. offset 2D shell elements(number of layers optional) through section/thickness, and then generate tet mesh.
note: make sure offset element layers should be on before generating tet.
hope you will definitely get what you want !
thanks
0 -
Altair Forum User said:
Do you have any release date of Hypermesh 2019 yet?
My friend says it will be released on this Apr-2019.
But i am still have to use hm13 OMG.
Look like new GUI is not Tk widgets anymore, it's nice!
0 -
Tinh, good to know that possible & speculated release date is close by even though nothing is set in stone yet. I was thinking that it is possible that GUI in HW 2019 will be updated to match the style of newer product range from Altair. I am also hoping for better & easier geometry clean up capabilities...something which has been demonstrated & active in some of the HM's competing products. In all the CAE packages that I've used so far for meshing, HM is the most capable & easier on most aspects. I do hope that Altair team has thought of & included further innovations in this aspect as well. One of the changes that I think is most important is easier analysis setup for different solvers i.e. automatic inclusion of necessary cards needed for each type of solution, easier creation of load cases etc. among others.
Anyways, excited to see what the new release brings. Sorry for OT.
0 -
Yeah, its ribbon GUI will be much more user friendly, mesh or setup analysis in some clicks...
But actually i like the old one. Altair wants to populate it, so i think many new users like ribbon GUI while don't know about FEM, and finally HM looks like... solidworks!
0 -
Altair Forum User said:
Yeah, its ribbon GUI will be much more user friendly, mesh or setup analysis in some clicks...
But actually i like the old one. Altair wants to populate it, so i think many new users like ribbon GUI while don't know about FEM, and finally HM looks like... solidworks!
Ohhh, noooooooooooooo !
0 -
So we are half way through May and still no signs of the release of elusive HW 2019.
Tinh, any news from your sources about an imminent release?
0 -
Sorry, I don't know.
He lies!
0 -
New release Hyperworks 2019 finally is here!!!
0 -
^^ Yes, I saw the announcement...yesterday.
Hyperworks X looks interesting...Anybody got a chance to try it out? Initial impressions? Need to wait till we get our updates.
0 -
Is this Tetramesh layer bug fixed in HW 2019?
On my end, the bug seems to persist. Did a small solid test but minimum number of elemental layers is not being enforced. Also found another bug with Start Up of Engineering -> Aerospace profile. This bug was there in HW 2017 AFAIK.
Will post screen shots of both early next week.
0 -
Here's my test with 2019.0:
0 -
^^Are you confirming the persistence of the bug in HW 2019 as well? Or is it working the way it is expected?
Here is what I am getting:
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
Or am I doing something wrong the above process?
Also, the other bug related to start up...
I usually start up in Engineering Solutions -> Aerospace profile. Further, I like to have View -> Toolbars -> HM -> Checks turned ON.
So first time I start up in Aerospace profile and turn ON the above tool bar as shown below
<?xml version="1.0" encoding="UTF-8"?>
Close HW Desktop and reopen it in SAME Aerospace profile and boom...Checks toolbar is not visible/retained. Have to manually enable it again. This does NOT happen if I choose Hypermesh -> Nastran profile. HW Desktop remembers that Checks tool bar was enabled and retains it when opened freshly...This bug was there in HW 2017x versions as well.
<?xml version="1.0" encoding="UTF-8"?>
0 -
I make a closed surface mesh firstly and fill with Tetra mesh.
0 -
OK. But can you clarify if the above Tetra layer bug is resolved in HW 2019 when you try it out?
0 -
As you can see on my screenshot: it works!
0 -
Ok. Thanks for clarifying this.
Obviously, I must be doing something wrong during meshing. So if I specify minimum number of layers, will it be enforced only if the specified element size is reasonable? In the screen shot I've posted, the thickness of the block is 1 unit and I am specifying an element size of 1, which is equal to thickness. So in cases like these, the number of layers cannot be enforced?
0 -
<?xml version="1.0" encoding="UTF-8"?>
0 -
I hope I am not beating on a dead horse here but this feature is still not working on my end. I tried a similar narrow rectangular strip with minimum layer set to 2 and HM 2019 could not enforce. Anyways, I don't use this feature a whole lot but the presence of this bug is still bugging me.
I hope Mr. @Imoto can check it again with Altair's development team.
My last on this...
0 -
Sorry, I don't know what happen with you, but it works well for me.
0 -
This is not defect, Volume tetra feature is doing the following process.
1st. Create the shell elements at face surfaces using specified element size.
2nd. Create the tetra mesh from shell elements.'Number of layers' does not effect to 1st process. if you want to get 3 layers for face element, you can create with automesh panel before using 'Volume tetra'.
Thanks,
Imoto
0
Altair Employee
