Victor

About

Username
Victor
Joined
Visits
4,653
Last Active
Roles
Administrator

Comments

  • @Sergio I don't think so unless you recompile it. It might be time for me to look into updating Netgen more thoroughly soon. But as with a lot of things, it'll have to wait till after the upcoming release and might take me forever.
  • I'm unlikely to add CAD-like editing tools. To edit nodes/elements in bulk, you can edit the .liml file with a text editor or maybe spreadsheet. Multi-select for the outline tree is on my list but not yet sorry. Preview image is possible but low …
  • @dculp. Netgen 6 can mesh some models that the default one can't, as you've seen. But it's also slower and I think there are some cases where it does worse than the default one. There isn't really a clear advantage of the default over 6 other than…
  • @Sergio, yes it's a bit strange that you can change the CAD surfaces for a load but not a named selection. I've added that to my list but it's low priority.
  • You should be able to make a function for putting a node in the center of a circle using the Python API. I don't know the math of it, but the structure of the script could look like this: # Get the coordinates of the points that define the circle fr…
  • @prop_design, yes that's a graphics issue. For display, Mecway is just expanding the shells into prisms independently of each other, but CCX expands them into something like a frustrum shape consistent with their adjacent expanded elements. @disla,…
  • Hello J Eppinga If you're starting from a STEP file, you can define spherical and surface refinements that get applied when you generate the mesh. You can also specify a global maximum element size. For any mesh, there's a Refine x2 tool which doe…
  • Good news. There's an easy way to prevent the Array dimensions exceeded supported range error which can also occur elsewhere like displaying a big mesh or reading the solution from the CCX solver. Copy this Mecway.exe.config file to the same folder…
  • I used to think that too but it turns out they're still solved as single elements and only get expanded to one element per layer for the output. You may still get an improvement due to more integration points though.
  • If you do use laminates, it should be with CCX, as prop_design suggested, not the internal solver because only CCX laminates have stiffness in the normal direction. But, flat hex20 solids are pretty good with high aspect ratios. You may only need o…
  • Sorry if you're going to lose work. One workaround may be converting to quad4 if there are separate parts having no triangle elements (due to lack of tri3 shells with internal solver). Or maybe the CCX solver if you install one of the higher-memory …
  • It's part of force per length but beware that it can have huge errors. Sometimes averaging the values on adjacent nodes corrects that.
  • Yea, it used to, but it was causing problems when there was too much data, especially in dynamic response where the all the time steps can make it huge. I probably won't get it to reuse existing stress. It's a good idea but too low priority. I thi…
  • 1) You can do that using a face selection instead of a node selection. It's tricky to select the faces at the connection so what I did was select Plate's elements, use Mesh tools -> Disconnect elements, hide Flange, then select the now exposed fa…
  • The maximum number of nodes depends strongly on the connectivity of the mesh. I just solved a flat quad8 & tri6 shell mesh with 973000 nodes and it was OK. But if your model has a lot of T-connections or other ways that more elements share the s…
  • Sorry about that. It's been a frustration for others too. In some cases, it shows a warning, but probably not for velocity. Hopefully I can find a solution.
  • A few people have asked for this and I hope to later but it won't be in the next version (14).
    in Mesh quality Comment by Victor May 2021
  • This is a tricky design compromise. What happens now is if there are no field variables (such as first time solving a new model), it automatically adds most of the relevant ones that can't be generated after solving, and that includes velocity for …
  • Yes, the node values for UU, VV, etc. stresses are simply averaged from adjacent elements so they're meaningless at the join where U and V directions aren't uniquely defined. You should use element values instead (select Element values in the Table …
  • Can you be more specific about what stress data you want? Can it be derived from the existing stress or bending moment data?
  • You could add a table to model that's been solved then save it and copy that part of the .liml file to your unsolved file. It looks like this: Default displx
  • You have some good points there and this is a behavior that several people have questioned. Some general principles I'm trying to adhere to: * Support means a connection to ground or constraint of rigid body motion, not necessarily without impos…
  • That's intentional. Pinned support is at a higher level of abstraction and it makes a single pinned support for the entire selection by coupling all the nodes with constraint equations. It's suitable for putting a pinned support on the end of a beam…
  • I think you might be able to do this with CCX by adding an extra *STEP initial section with gravity to load it separately from the loads for buckling. From the CCX manual: All loads previous to a perturbation step are removed at the start of the ste…
  • Sure, though CCX beams aren't restricted to beam theory since they're more general solids. They also have the Poisson effect changing the cross-section area, for instance. I agree it's not right for the end to deform like that though. I might count …
  • Beware that some versions of CCX have a bug that excludes modes with a buckling much below 1. The version of CCX 2.16 that comes with Mecway 13.1 is OK but other 2.16's might not be. Disla's way of adjusting it so shift point is 1 avoids this bug. …
  • Yes, I wonder if that's the cause of the problem. Maybe it's just not deforming the beam far enough. It's correct for a zero displacement and loaded by a force, which is consistent with that reason.
  • It does look like that, especially with the zig-zag deformation shape. So perhaps B31 isn't really a coding bug but a theory bug. The B32R (line3) case isn't helped by more cube-shaped elements though.
  • Intel MKL Pardiso files are included with Mecway 13.1. You just need to get the CCX version that has been compiled for it according to step 2 in this comment. https://mecway.com/forum/discussion/comment/4863#Comment_4255 Or you can download MKL (no…
  • I saw your post on CCX forum so just to clarify in case of misunderstanding, it works for both static and modal with elastic support, not elastic bonded contact. In case that's no good, another workaround is to extrude a thin layer at either the sl…
Avatar

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!