I've added your first request to here https://github.com/victorkemp/Mecway/issues/30
Could you clarify the second one? Are parts of the model absent in some phases? If not, maybe the existing configurations can work for that? Those allow you to app…
I notice PASTIX_MIXED_PRECISION = 1 (solver message shows "Arithmetic: Float") seems to be the default and I have to turn it off by PASTIX_MIXED_PRECISION = 0. Not sure if that's the case for everybody else but it seems like a bad default. I agree…
Version 20 is here https://mecway.com/download/oldversions/mecway200.msi
However, some concerns:
The bar has no constraints against rigid body motion. That's a common reason for contact failure. I tried constraining it in Y and Z but it ended up w…
No boolean mesh operations because it's too hard. That kind of thing is best done in CAD as @JohnM said and letting the automesher sort out the details.
You might have set it as the Default model. Clear that in Tools -> Options -> Default model.
Note that Mecway doesn't make a copy of the default model so if you edit it separately, the changed version will become the default model.
You can't use Numpy arrays but you can use a list of lists. Eg. to create a 4x3 "array" initialized to all zeros:
a = [[0] * 4 for i in range(3)]
and index it like
a[0][0] = 3
@German You can use the Python import functionality. I would think this sort of helper function makes more sense as a user-defined thing like that to keep the core API simpler.
@German it's OK to have duplicates for refine_x3() so you could omit the if n not in nodosref: line. Or if you need no duplicates for something else, use a dictionary with node numbers as keys like: nodosref={} for e in mw.named_selection("Refine")…
It might have a special kind of load like a force couple between surfaces for that? I don't think there's an easy way to do that with Mecway.
You could model the bolts as solids and use Pre-tension section on them, and connected to the plates by Co…
Thanks for all the feedback. Good to hear people will find some of these things helpful.
@Sergio, the bad element check doesn't measure quality but rather just checks for a non-positive Jacobian determinant (indicating non-positive element volume) …
Thanks @mmartin. Do you mind clarifying what do you had to do with environment variables for cores and threads? @bobs also had a problem with high core count: https://mecway.com/forum/discussion/1404/error-allocating-memory-error-different-outcomes-…
@pberry it sounds like it's locked up. Loading the mesh should take time proportional to the number of nodes or elements and this sounds way longer than that. For comparison, I just made a 2.3 M node mesh that took 2.5 minutes from the end of meshin…
Since the displacements of the truss elements aren't following the nodes they're attached to, that sounds like they're not really attached to those nodes. I'm not aware of a bug that causes them to not get connected by the solver. Check with View -&…
Not sure what you mean there. The CCX truss elements do get expanded to rectangles with none of their nodes at the original end node locations, but CCX internally connects them with MPCs. You can also get the solution to show them as line elements r…
If you're creating the truss elements using Mesh tools -> Create element or the toolbar icon for that, it should use the existing nodes you click on so there's no need to merge. Having the yellow circle appear around a node before you click it in…
I've heard of people modeling rebar in Mecway like this before, though with beams and possibly only linear.
If you were merging the nodes with Mesh tools -> Merge nearby nodes, it only acts on selected nodes (every member of the merge has to be …
@pberry any anyone else, here's v23 beta 1
https://mecway.com/download/mecway230_Beta1.msi
The relevant new feature is an option in Meshing parameters called Straighten bad elements which is on by default.
Haha, took me a while to realize.
To sign up, you have to answer an easy question that's the same for everyone. It's been a pretty good brick wall for almost all spammers but perhaps we'll start seeing them use AI to answer that.
For @aliva13 only. Sorry everyone else, I couldn't help myself.
Dear Forum User,
Thank you for sharing your insights and experience with our software. Your strategy of dividing models into separate files for calculations aligns with a common worka…
Good on you for refusing to accept the old fashioned ways of scrimping on computing power
I think I've seen all zero results before with either too big a mesh for the memory or too big for Pardiso/CCX, hard to tell which.
You might need a version…
Beam elements can capture global buckling and perhaps you can use the internal forces and bending moments from the solution to find local buckling using hand calculations in a spreadsheet or the formula feature in the solution?
If you do use solids…
I wouldn't have much hope for 8 million nodes on 32 GB of RAM, or even with any amount. I'm not sure what the limits really are but it depends on the matrix solver (Pardiso/Pastix/Spooles) and amount of RAM.
It sounds like you should be using shell…
Yes, you can't currently build a model from scratch with the API. Maybe start with one having placeholder loads?
The API isn't frozen, and I'm frequently adding to it to make it more complete. It was a late addition to Mecway that hasn't caught up …
Two ways:
Python script like you suggested:
* Easy to modify some aspects of the model such as node locations and most load values but not everything is available through the API.
* Access to some tools like mesh refinement and integration of …
That's great you found a solution.
set the higher-spec computer to 24 processors rather than 36
Perhaps I should get Mecway to limit number of threads. 24 is probably way too high to give any speed advantage.
Some ideas:
1. This first one is only relevant if you're using CCX compiled from the source in Mecway.
Mecway versions 19 and earlier restricted the in-core memory available to Pardiso to 14.4 GB. I don't think you're using this and shouldn't.
Ve…
You could move the shell nodes to join with the beam nodes and use Shell offset (in Element properties) to position the shell midplane at the correct distance.
Alternatively, you can generate all the beam elements quickly by selecting the nodes and…
You're right that those small radii cause it trouble. I got a solid mesh with the default meshing parameters. However, the small radius leads to a lot of badly shaped elements which you probably encountered.
Ways to correct that:
Turn off Fit mids…