Discontinuous results from imported 3D field data

fang yanwei
fang yanwei Altair Community Member
edited December 2023 in Community Q&A

Hi,

When I import 3D field data in EDEM and query it via EDEM API, I get strange and discontinuous results (like picture below), which is far from the original field.

image

I tried to squeeze 3D field data into several 2D x-plane and the results truned reasonalbe. But I also loss plenty of field structure infomation by doing this.

Does anyone know how to solve this?

Thanks a lot!!!

Fang Yanwei

2023.12.01

 

Tagged:

Answers

  • Stephen Cole
    Stephen Cole
    Altair Employee
    edited December 2023

    Hi Fang,

    How does the field data display in the EDEM analyst, could you show vector or contour plot of the data in the Analyst?


    Regards

    Stephen

  • fang yanwei
    fang yanwei Altair Community Member
    edited December 2023

    Hi Fang,

    How does the field data display in the EDEM analyst, could you show vector or contour plot of the data in the Analyst?


    Regards

    Stephen

    Hi Stephen,

    Thank you for replying!


    My original data has dense region and sparse region mixed, which I think is the most likely reason for the error. The plot of density in EDEM shows like the picture below. Only a part of the field is able to show.

    image

    image

    image


    Sliced data looks better, entrie field plot well.

    image

    image

    image

    Regards

    Fang Yanwei

    2023.12.01

    2.png 238.7K
  • Stephen Cole
    Stephen Cole
    Altair Employee
    edited December 2023

    Hi Stephen,

    Thank you for replying!


    My original data has dense region and sparse region mixed, which I think is the most likely reason for the error. The plot of density in EDEM shows like the picture below. Only a part of the field is able to show.

    image

    image

    image


    Sliced data looks better, entrie field plot well.

    image

    image

    image

    Regards

    Fang Yanwei

    2023.12.01

    Hi Fang, 

    The field as shown in EDEM does look reasonable, when you query it with an API or with the in-build drag models EDEM takes the closes 8 points or vectors and then does inverse distance weighting function to get the point or vector to apply to the specified particle.

    So I would expect some smoothing of the data, you can change the number of points to query or alternatively consider modifying the field so it is more uniform.

     

    Regards

    Stephen