Thanks for bringing up these problems. They include the issues that I'm most concerned about with the new configurations. Here are my thoughts:
File open time: I've seen a smaller increase in load time (50%) with a similar sized model. The 10x i…
Could you explain why different materials need it or not? It doesn't seem like it's just a function of material. For example, I've seen a recommendation not to use reduced integration on tet elements, and also not to use full integration on hex8 ele…
No, but I'll try to put CCX strain in for v7 final if it's simple.
The experimental part of reduced integration is that I don't know where to put it. I don't know where to put it because I don't know how it would be used. Maybe per component if it…
I just found that CCX's *TIE seems to be quite happy with constraints sharing its nodes. Sometimes it appears to release the contact where constraints are on slave nodes but not always. You can easily get bonded contact in to use *TIE by checking th…
That's a good idea to have it automatically remove the conflicting nodes. It won't be quite correct unless the constraint is on all DOFs so it would need to come with a warning, but still a worthwhile compromise.
You can use the GUI to remove the …
Yea that would make sense, but really it should not even make time=0 available at all when there's no data there. That's more of another problem for a future version.
While I can't answer your questions, that's a nice comparison! It's reasonable to expect speed to plateau. I don't expect that CCX is particularly optimized for running in parallel, unlike a supercomputer code. It's hard do that and probably not wor…
I see it happening now by solving several times, on both your model and one I made. Thanks for discovering this and isolating it to the multithreaded version! I'll try compiling with lower optimization or remove it if it's still going wrong.
Is that the ccx_MT.exe with Mecway or from Kwip? I can't reproduce the problem. Do you mind sending me a .liml or .inp file that does it? If it's going to be unpredictably wrong like this, I'd better remove it from Mecway.
I'm still not sure quite what's happening with Salome and whether it's a good idea to assume all .unv units are unreliable or not so I've added a persistent option in v7 beta 3 in Tools -> Labs -> Ignore units in .unv files which causes it to …
Thanks for the feedback. It currently doesn't let you solve two configurations at the same time. I'll look into it stopping the first solve because that doesn't sound like very good behavior.
I've also compiled the multithreaded version (ccx_MT.ex…
There are two possible things happening here:
A) Is it just showing a different default choice, so that you can easily switch to mm to read them? or
Is the physical meaning wrong, so that what should be 1 mm ends up as 1 m or 1000 mm?
For A),…
Yes, that's a missing feature of Mecway 6 sorry. However, version 7 which is now in beta does write *FILM for convection but not *RADIATE. Thanks for posting the Excel VBA code to generate them.
http://mecway.com/forum/discussion/401/version-7-beta
Thanks for finding these bugs with configurations. It should show two different results. I've been able to reproduce both the corrupted display and the common solution for both configurations and will fix them for the final release of v7. For the se…
You can copy the first 10000 lines of a large file quickly in PowerShell with:
gc -TotalCount 10000 InputFileName.liml > OutputFileName.liml
The number of lines for the model will be more than the number of nodes plus the number of elements…
The overall structure of the file is like this:
[ ... model definition ...]
[ ... model definition that was used for the solution ... ]
[ ... results data ...]
so if the end of the file is truncated or…
For the heat flux at the boundary, I think CCX calculates heat flux at the element integration points then extrapolates to the nodes whereas Mecway does it directly at the nodes. That might be the reason for the difference but I would still expect …
Thanks too Andrea. Just a warning - it doesn't capture bending and twisting moments that would exist with an offset joint like this. Sergio corrected that above by making it symmetric, although with rigid body instead of distributing coupling.
Thi…
This is because there are nodes on the slave surface of a bonded contact which are also slaves or other bonded contacts or constraints. The slave nodes aren't allowed to be part of any other constraint.
You could work around this by removing one e…
Not easily. You could generate the relevant parts of the liml file with a script or spreadsheet.
The equation:
3 = 1(1/m)×ux1 + 2(1/m)×uy2
is stored as:
However, perhaps there's another way to achieve what…
I see. It's too minor for including any time soon though. There's also the converse problem where it should average at boundaries like bonded contact with the same material and symmetry planes.
This is the flexible joint on beam under Loads & Constraints. It's sometimes a little tricky since you need to apply it to the end "face" of a beam. See Help -> Manual -> 10.9 Flexible joint on beam if you have trouble selecting the face.
…
I see an abstract here http://proceedings.asmedigitalcollection.asme.org/proceeding.aspx?articleid=1628315
It sounds like it would be more convenient - don't make so many lines, just a small number of planes? I'm surprised someone's come up with a…