What's the import or open sequence of .frd and .inp files to keep Group information in "Solution"?

runinwindruninwind
The fundamental problem is that group information is not properly transferred from the model definition to the Solution section when using externally generated .frd files.

I had tried the following:

1. First importing the generated .inp file (containing model and groups) into Mecway

2. Then importing the corresponding .frd file (containing results)

This approach works, but in the attached image (see fig1, using both .frd and .inp files), the components under 'Solution' actually do not contain the grouping information shown in the upper part of the image. However, I found that when directly calling CalculiX solver within Mecway, the grouping information from the upper part is properly transferred to the lower part (as shown in another image attached, i.e., fig2, directly using .liml file)."

Please also find attached .frd, .inp files (both directly output from Mecway using ccx solver) and also Mecway .liml file. If I am not wrong, the .frd file already contains the element or material group information in element topo data field of .frd file.

So, what's the right import or open sequence of .frd and .inp files to keep Group information in "Solution"?

Comments

  • SergioSergio
    edited June 2025
    As far as I remember the .frd doesn´t keep that group information, is Mecway that creates that relationship. If you work outisde Mecway the importer probably cannot make that relation again, even if you have imported before the input file.

    Using Paraview with converted Calculix results is the same, you lost all the group information.
  • runinwindruninwind
    Thank you Sergio for your kind reply. If I am not wrong, I find that .frd do contains the group information. Please refer to the attached figures, there are three groups in element topo field. More exactly, the above .frd and .inp file is directly copied from the ccx solver called by Mecway. So, it is very strange that, after open the .frd file, Mecway do not identify the group information contained in .frd file.
  • VictorVictor
    Yea, like Sergio said, Mecway stores that information internally when you click solve and puts it back together with the solution afterwards. It doesn't read any group information from the .frd file, which won't always be the same as components in Mecway.

    You could trick Mecway by changing the setting for the CCX .exe to your own script that copies the .frd file into the place Mecway expects to find it.
  • runinwindruninwind
    Victor, thanks for your instructions. As you mentioned in the last comment "You could trick Mecway by changing the setting for the CCX .exe to your own script that copies the .frd file into the place Mecway expects to find it.", I am not very sure how to operate like this. Since I have only .frd and .inp file as attached above, would you please show a simple example or steps how to trick the Mecway? Thanks again
  • VictorVictor
    edited June 2025
    Here's how you can make it import the solution from test.frd. After setting it up like in the picture, have the input model in the modeler with the components/etc. and saved as test.liml then click Solve and it'll import a copy of test.frd as the solution, retaining the components.


  • runinwindruninwind
    Thank you for your constructive suggestion, but I am afraid I still can not recover the group information in the "Solusion"
  • VictorVictor
    Hard to know what's wrong. Here are the files I tried it on and it works. I made the shape of the model different in .liml file and .frd solution to make it clear that it didn't really solve it.
  • runinwindruninwind
    Thank you very much for your continuous help, Victor. I'm looking forward to the next update and I'm confident you'll be able to address the issues we've discussed. Keep up the great work!
  • VictorVictor
    It's not intended to be used this way so I might not change it. I imagine a solution would be to have the model open then import a .frd file and it would prompt if you want to use the components/orientations/named selections/etc. from the model. But if this workaround doesn't work, then that improvement won't work either. Fundamentally, there's not enough information in the .frd file to reconstruct all that. At best, it might be able to identify the material of each element but I'm not sure what material information is in the .frd file.
  • runinwindruninwind
    Thank you very much for your reply, and Mecway is found to be really very helpful.
Sign In or Register to comment.

Howdy, Stranger!

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

Sign In Register