The PFL format of VecLen, Spacing, Samples... can be a serious performance bottleneck and isn't necessary. It is a bottle neck in that it either mandates that the source of terrain data adds those fields by default, otherwise it requires a reallocation to prepend those two fields. Let's use this current function signature as an example:
int ITM_P2P_TLS(double h_tx__meter, double h_rx__meter, double pfl[], <SNIP>)
Users who have data natively formatted as PFL (side note, what is the origin and meaning of pfl?) can still call the modified function with no overhead:
The PFL format of
VecLen, Spacing, Samples...
can be a serious performance bottleneck and isn't necessary. It is a bottle neck in that it either mandates that the source of terrain data adds those fields by default, otherwise it requires a reallocation to prepend those two fields. Let's use this current function signature as an example:we could switch to
Users who have data natively formatted as PFL (side note, what is the origin and meaning of pfl?) can still call the modified function with no overhead: