The node ID maybe a bit difficult, since they may be generated with different node naming sequencies. I call the file data through an independant function, the function input is X, Y, Z coordinate and output is coordinate pressure value. This function will be called directly from the user functions, you can see this form my previous attached codes. The file itself is of similar formats you mentioned. But again, this should not be really relevantly since it is dealt by sperate function and the values can be returned directly (function input: file name, X,Y,Z, output: p_re, p_im).
Code: Select all
x y z p_re p_im
...
raback wrote: ↑07 Jul 2020, 20:20 Hi
Before going to analyze the code I would take a step back. In what format is your data at the boundary available? Is it on the same nodes as the boundary condition uses, or are the meshes nonconforming? Do you maybe have the luxury of knowing the nodal indexes?
I would guess that you have something likeYou should first read all the data and create mapping to this tabulated data by some search algo.Code: Select all
x y z p_re p_im ...
-Peter