The elastic support is just linear springs so acts symmetrically in tension and compression.
Version 19 (beta here https://mecway.com/download/mecway190_Beta5.msi ) has elastic compression-only supports for CCX which sounds like what you're looking…
I agree it's probably faster in typical cases to do something like that. I wonder about the worst cases though. What if the first 10 modes are all in the highest ND? Is that possible? Would it be much slower than finding all 10*ND modes? Maybe such …
Yea, I wondered about a heuristic. But what data can you build it from to be general enough? Maybe somebody comes along with a completely unexpected structure that looks like a Polish word used in English and it ends up performing worse than simply …
@disla, just a vague idea of an algorithm to find the lowest N modes:
* Solve for 1 mode of each ND.
* Pick the ND with lowest frequency mode and solve for an additional mode of that.
* Repeat until you can confirm you have the lowest N modes…
@hooshim. bonded contact with internal solver should be about as good or better than *TIE. Does it not work if you turn off *TIE?
Step by step instructions are included with the source code in Mecway's installation folder under ccx/ccx_win64_mkl_pa…
I haven't really been following this thread but a couple of thoughts:
As I understand it, i8 allows the solver to use more than ~32 GB. Since you only have 16 GB, Windows would need to use disk swapping which will either completely destroy performa…
374k nodes is just above the limit of what the default CCX included with Mecway can do. Download one with PastiX or Pardiso, or compile it using the source code distributed with Mecway to allow more nodes.
Or you can use cyclic symmetry to reduce t…
Nonuniform stress is pretty common for shells. The two solvers use different formulations, each with their own approximations, so the details of their errors are expected to be different.
In this model, the internal solver's quad8 seems to be about…
It just needs mesh refinement:
3543 nodes (your model):
FoS quad8 = 1.8
FoS tri6 = 2.3
14050 nodes (after Refine x2):
FoS quad8 = 2.1
FoS tri6 = 2.2
I have found, with the help of @disla, that the UV moment depends on the element node number order…
A 0 heat flux load really means 0 heat flux in addition to whatever else is there - conduction, other heat fluxes, convection, etc. So it has no effect. It's not a constrain that forces heat flux to be zero.
From the manual, it looks like ENER and ELSE are just for mechanical energy in dynamics.
Q = m*Cp*T is really heat added for temperature change T when Cp is constant, not total energy at temperature T.
What do you mean by internal energy here? The…
Face and element selection really need cleaning up. Partial and full lassoing could be part of the solution.
I almost exclusively use Select nodes with Show element surfaces off because it's more predictable and Edge detecting selection because it'…
That "h" bug should have been fixed in v17. So please update to the latest one if you haven't. Otherwise, could you send me the file to find out why it's still doing that?
However, it won't help the meshing and just show a generic error message.
I…
That's amazing.
Regarding importing the mesh, do they include *ELSETs, *SURFACEs, or anything that Mecway could merge with existing components/named selections when you import?
@Philipps, the shell elements aren't very good when they're distorted. It might only be a local effect that you can ignore, or locally refine it if that region is important.
This is an important point from @prop_design "Then just converting those elements back keeps the quad4 geometry, rather than what you originally started with." The final quad8 mesh will have mostly flat elements which can make the results wrong.
Qu…
My email is the one in the top-right corner of the page
It sounds like you've already used the procedure for meshing an STL file in the normal case where it works correctly - File -> Open then Mesh tools -> Automesh 3D.
All I can think of is either you scaled only some of the nodes as @disla suggested or scaled them to 0 in at least on dimension. Could you post the model or email it to me?
I see, sorry about this inability to mesh small-scale meshes. You'll have to scale it up using Mesh tools -> Scale before meshing. You can then scale it back to the correct size afterwards.
If you're opening a .stl file, you can choose units when you open the file and that will scale it.
If it's already in Mecway, ensure no nodes, faces or element are selected, then use Mesh tools -> Scale to scale it.
I can reproduce it now. It seems to be because of the pyramid elements at the edges of the refined region. I'll investigate further but it might turn out that the solution ends up being "don't use pyramids with node-surface coupling"
Mecway just e…
I'm not seeing that asymmetry. Could you post the model where it happens?
The fact that it depends on the order of refine and extrude suggests something's wrong with the mesh.
Are you sure the reference node is still at the center? If you create i…