[raptor]

Hello,

It is possible to export the results (ex: velocity) from Solidworks. Unfortunaly, exporting results is not available from the API.


Is there a way to retrieve the results directly from the result files (.FLD) ?
Is there any white paper regarding the file structure?

Thank you for any comments.

Regards,

[Boris_M]

Hi raptor,

what do you need the export for?
Maybe there is a way to do it depening on what you want to do with it.

Boris

[raptor]

Hi Boris,

Thank you for your reply.

I know it is possible to retrieve a result at a defined point with API.
However, it is really time consuming to retrieve all cells.
So, I would like a way to get the results for the entire domain more efficiently. And exporting to excel/ascii is not possible from the API.

I would like to display my results with VTK (Visualization Toolkit) in C++ to have advanced features. For example, to display a range of velocities isosurfaces (10 to 30m/s for example).
Loading the result directly from the file would be really more efficient.

Regards,

[Boris_M]

Hi raptor,

You can output the results in an XML file and with a little programming you would be able to output all values in a specified format into a file. You can ask for the value and store it the way you want it in an ASCII file.

I haven't used it for such a purpose but it should work.

Boris

[Boris_M]

Hi raptor,

One thing I'd like to add to my last post.
It is not possible to output the cell center coordinates and then therefore the values for that as the parameters in FloEFD are cell center based. But even with that there would be not really a geometry description of the mesh surface on bodies as the surfaces are not in the output.

Boris

[raptor]

Hi,

Thanks for comments.
I ve finally got a good result.
In flow simulation/floefd, the evaluation points are finally not a too bad idea.
I ve created a binary file based on the result of those points in the entire domain (cells).
In VTK, it is possible to create any display from this data. I still need to evaluate the accuracy compared to flow simulation outputs.

It gives more flexibility than the flow API. The API is still poor compared to normal user possibilities; and not only in output features. I had a lot of limitations like fluid selections.

[Boris_M]

Hi Raptor,

The API offers some interfacing but as most of the users are not programming experts their interest in the API is therefore low which makes a full flexible API a lower priority compared to adding new physics and other capabilities.

Boris

[raptor]

Hi Boris,

Yes, I can understand that.

Regards,